Contents
New features
YateMMI has a few new features that will help with easier set-up configuration.
-
Roaming numbers can now be set using YateMMI interface
-
S-CSCF URIs can now be set using YateMMI interface
-
IMS configuration: Activation, Configure S-CSCF URI(s) from YateMMI interface
-
Settings of Combine attach options from specific sections in YateMMI
-
Extended Network mapNetwork information for the already configured equipment
Extend network map to include additional information:
- YateUCN:
- S1AP SCTP Listener(s) from MME/SGSN step.
- Local ip:port
- VLR SIP Listener && P-CSCF Listener from VLR/CSCF step
- IPv4:Secure port
- SIP Listeners && SIP Connections from Accounts step
- SIP Listeners: IPv4/IPv6 address – Port
- SIP Connections – Registrar IP: Registrar Port
- S1 GTP interface(s) / S5 GTP interface(s) / S8/Gp/Gn GTP interface(s) from GTP step
- IPv4 GTP-U address
- IPv4 GTP-C address
- if no gtpc address, then it’s same as the gtpu one
- HTTP (for Management IP)
- S1AP SCTP Listener(s) from MME/SGSN step.
- YateUCN5G
- All from YateUCN +
- NGAP SCTP Listeners from AMF step
- Local IP:Local Port
- Additional Connections / Instances / Connections to YateNRF/SEPP from CAPIF Step
- HTTP (for Management IP)
- YateSMSC/YateOTA
- Server Listeners from SMPP Server step
- Client Connections from SMPP Client step
- * Verify for ocs diameter connection is displayed for smsc in network map
- HTTP (for Management IP)
-
For the moment we generate automatically the “netinfo” section only for Home Network
Wizard improvements
YateMMI has new impoved wizards for setting up YateUCN, Network Settings, YateSMSC & YateOta.
-
Option to set Node params for YateUCN (This section holds various settings like: activation of automatic Routing Rule generation)
-
Configure what Visited Network advertises in MME/AMF (mme-amf features) & Combined Attach options
-
Added option to configure P-CSCF IP for “IMS” APN per YateUCN.
-
Network settings wizard improvements
Network Settings first time set-up
- When setting for the first time Network Settings both SS7 and Diameter support will be suggested as enabled.
- When setting for the first time Network Settings, “Diameter Realms” from Diameter step is suggested based on the MCC and MNC value set in General step.
Example:- Diameter Realms – epc.mnc030.mcc001.3gppnetwork.org
Added option to enable IMS support in Network Settings
- When setting for the first time Network Settings, the IMS support is initially disabled in General step.
- When the IMS support is enabled by the user, a completely new field will be displayed in Diameter step from Network Settings.
- This new field is called “IMS Domain” (similar format to ‘Realms‘) and its value will be automatically suggested based on the MCC and MNC value set in the General step.
- If the IMS support is disabled, “IMS domain” field won’t be displayed in Diameter step from Network Settings and cannot be set.
- The user can edit the “IMS domain“.
- If the length of the MNC value is lower than 3 characters, “0” will be added in front of the existing value ( from 41 to 041 ). This behavior applies only when the value of the “IMS domain” is built.
- If for any reasons MCC/MNC values are modified, the the user has to also update the value of the “IMS Domain“.
Notes:
In order to use IMS you have to configure a set of parameters for YateUCN/YateUCN5G. Check the guide for setting up IMS here.
-
YateSMSC/Yate OTA wizard improvements
Added option to set bind parameters per SMPP Client Connection for YateSMSC/YateOTA equipment.
System Type – “system_type“: Optional. String. Type of system that is binding.
Address Type of Number – “addr_ton“: Optional. Keyword/integer: Address Type of Number for SME address parameters. Defined values are unknown(0), international(1), national(2), network-specific(3), subscriber(4), alphanumeric(5), abbreviated(6). Any integer value will be encoded as is.
Numeric Plan Indicator – “addr_npi“: Optional. Keyword/integer: Numeric Plan Indicator (NPI)for SME address parameters. Defined values are unknown(0), isdn(1), data(3), telex(4), land-mobile(5), national(8), private(9), ERMES(10), internet(14), WAP-ClientId(18). Any integer value will be encoded as is.
Address Range – “address_range“: Optional. String: String containing regexp or IP address specifying a set of SME addresses serviced by the ESME client.
General improvements/fixes
-
improved configuration API JSON of the YateSTP and YateHSS/HLR equipmentIf the “MSISDN Prefixes” is not set in Network Settings, its value (in YateSTP and YateHSS/HLR configuration JSON) will be built using the CC and the NDC value from Network Settings, if they are set.
-
if not set, value "udp,tcp" will autofill for field "Type" from P-CSCF Listener of YateUCN/YateUCN5G
-
implemented button that refreshes the PCAP prefixes when retrieving captures in Debug tabButton is displayed after you download your captures
-
improved display of the warning to restart equipment on the following changes:– Edit S1 AP GTP Listener from MME/SGSN step of YateUCN/YateUCN5G
– Edit Tunnels from GGSN/PGW step step of YateUCN/YateUCN5G.
– Edit S1 GTP Interface from GTP step of YateUCN/YateUCN5G
– Edit S5 GTP Interface from GTP step of YateUCN/YateUCN5G
– Edit S8/Gp/Gn GTP interface(s) from GTP step of YateUCN/YateUCN5G.
– Edit GMSC step of YateUCN/YateUCN5G. (Fields: “In Route”, “HLR GT”, “SRI Timeout”, “Max Hops”, “CF Notify”, “No Unknown”, “Early SRI”, “Camel phases”, “Camel phase 4 CSIs”)
– Edit Server Address field from Client Connections table of SMPP Client step from YateSMSC
-
added a batch maximum accepted range to prevent memory exhaustionThe maximum accepted range of IMSI|MSISDN|ICCID|Subscriber ID in ‘Batch operations’ is by default 1000. This value can be changed by setting $max_range_batch parameter in MMI config.php file
-
fixed Network Settings "extra params" automatically updating to equipment type "all"' in some cases
-
setting a limit to the "get_operator" requests frequency to a default of 1 request/day“get_operator” requests is used to check for the operator mismatch.
The frequency can be changed from config.php file by setting $get_operator_frequency.
For example if you set “$get_operator_frequency = 4;” then “get_operator” request will be performed every 6 hours (24h/4 = 6h). -
fixed PHP 8 fatal errors that occurred when YateHSS/HLR request times out
-
fixed PHP warning when the License update "cancel" button is used in MGMT node
-
removed zerofill of database numeric variablesAs of MySQL 8.0.17, the ZEROFILL attribute is deprecated for numeric data types.
Validations were added in MMI so database table will now be compatible with newer version of MySQL, but at the same time will accept previous format.
Related articles:
-
An introduction to YateMMI.
-
First time user guide for the YateMMI.
-
Blocking subscriber services for mobile networks with YateHSS/HLR
-
Detailed user access levels rules
-
Guide to make a 5G Core network setup
-
Guide of node params usage and configuration.
Our solutions
-
First time user guide for the YateMMI.
-
How YateMMI decides to reconfigure equipment
-
YateUCNunified LTE/GSM+GPRS core network, including SGSN, GGSN, GMSC, MME, SGW, PGW