Contents
From release tag 6005
Starting with release tag 6005, IMS configuration is possible directly from the YateMMI interface.
For multiple YateUCNs that have the IMS configured, I have now the option to activate automatic generation of routing for S-CSCF SIP URI
Required
Before jumping into the IMS setup, here’s what I make sure is ready:
-
Diameter configured
-
Data sessions working over Diameter
For setting up IMS support these are the settings that are required in order for IMS support to work:
-
IMS support & IMS domainIMS support enabled & IMS domain configured in Network Settings
-
MME featuresmme_features options checked
-
Combined attach optionsfake_combined; fake_csfb; fake_csfb_no_reg; mme_features; cs_plmn cs_lac
-
Dedicated APN - IMS access pointDedicated APN for IMS, configured in Network Settings – APNs step
-
CSCF support enabledIn YateUCN – Edit equipment
-
P-CSCF listenerIn YateUCN – Edit equipment
-
S-CSCF SIP URIIn YateUCN – Edit equipment
-
IMS TunnelFrom YateUCN – GGSN/PGW or Tunnel step
-
IMS profileIn Profile Management, add domain and S-CSCF URI
-
IMS ActiveActive on SIMs & Subscribers ( IMS active, IMS profile & IMPI/IMPU configured)
-
Configurations in JSON "networks_info"(Those are automatically configured depending on the info inserted in YateMMI)
IMS configuration in YateMMI
IMS Support & Domain - (Step 1) Configuring IMS support & IMS domain.
IMS can be configured in Network Setting. Initially the IMS support on my new equipment is Disabled.
To activate it:
I go to Network setting→ General step → Enable IMS Support → Go to DIAMETER step →and here I can set the IMS Domain.
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. (“IMS Domain will be suggested only on fist set-up, on Edit it has to be manually written).
- Ex: “ims.mnc${MNC}.mcc${MCC}.3gppnetwork.org”.
Notes:
If the IMS support is disabled, the “IMS domain” field won’t show up in the Diameter step from Network Settings. If it’s not enabled, then I cannot set an IMS domain.
The “IMS domain“ is editable.
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, I have to also update the value of the “IMS Domain”.
MME features - (Step 2) MME features configuration
For multiple YateUCN that have the IMS configured, MME features can be enabled on all of YateUCN machines from Network Setting.
- From Network setting→I go to Node Params and select YateUCN/YateUCN5G Equipment type.
Or for enabling MME features on a single equipment, I edit directly from YateUCN in Equipments.
- From Equipment →I select the YateUCN/YateUCN5G equipment to edit→MME/SGSN →I enable the options in the MME features that are required for my network.
From MME features, I can enable “Advertise IMS support” and all the options that fit the criteria I need.
- Advertise IMS support
- Advertise Extended Service Request support (advertises support of NAS Extended Service Request message; used for CSFB)
- Advertise ePCO support (advertises support of NAS extended PCO IE)
- Advertise emergency bearer support (advertises support of emergency attach; this is recommended to be true in a production network that handles emergency calls, but false in testing environment or if the network is not yet interconnected for emergency service)
- CP-CIoT (Enables support of CIoT control plane data transfer – transfer of user data using NAS signalling instead of radio bearer/GTP-U)
- UP-CIoT (enables support of CIoT user plane optimization – suspend/resume S1 context instead of re-negotiating it when user is active)
- S1U data (advertises support for S1-U – regular, GTP-U – data transfer also when CIoT optimization is negotiated with UE)
Combined attach options - (Step 3) Configuring combined attach options
For multiple YateUCN that have the IMS configured, Combined attach can be enabled on all of YateUCN machines from Network Setting.
- From Network setting→ I go to Node Params and select YateUCN/YateUCN5G Equipment type.
Or for enabling Combined attach them on a single equipment, I edit directly from YateUCN in Equipments.
- From Equipment →I select the YateUCN/YateUCN5G equipment to edit→MME/SGSN →for enabling the options in the Combined attach options/CSFB section
The following parameters of YateUCN/YateUCN5G are required:
- Combined
- Fake CSFB
- Fake CSFB no reg
- PLMN for CS combined attach
- LAC for CS combined attach
Dedicated APN - IMS access point - (Step 4) IMS access point configuration:
For multiple YateUCN that have the IMS configured, IMS access point can be configured on all of YateUCN machines from Network Setting.
- Network settings: Diameter →APNs → IMS
(When I set the APN from Network Settings, it will automatically appear in the Equipment section too).- P-CSCF IPv4 is what I also set up in VLR/CSCF (Equipment) for P-CSCF Listener
- GGSN/PGW Adress is also what I configure for S8 interface in GTP (Equipment)
In the right image there’s an example of how I set-up the APN for IMS. - IMS Subsystem has to be enabled.
- From Equipment → go to GGSN/PGW →in the “Tunnels” section add an IMS Tunnel
Or for configuring APN for IMS on a single equipment, I edit directly from YateUCN in Equipments.
- Equipment (YateUCN):
- I go to APNs → IMS → setting up PGW & P-CSCF (only if it hasn’t been set already from Network Settings)
- Then, from GGSN/PGW →in the “Tunnels” section I add an IMS Tunnel
CSCF support - (Step 5)Edit Equipment
I go to Equipment → Edit Equipment (YateUCN) and make sure that CSCF support is ACTIVE
P-CSCF Listener - (Step 6) Configure P-CSCF Listener
From Equipment → Edit Equipment (YateUCN)→ VLR/CSCF step →I add the P-CSCF Listener
- An IPv4 or IPv6 address is mandatory.
- Both transport protocol (UDP/TCP) are set by default. Comma separated list of protocol is used for the listener type. It’s a mandatory field.
- Secure type:
- Secure: Boolean. Generate protected (IPsec) listener also.
- Secure Only: Boolean. Generate only the protected listener.
S-CSCF SIP URI - (Step 7) Configuring S-CSCF SIP URI(s) and activate the routing generation
I go to Equipment (YateUCN) → VLR/CSCF step →to enable “Generate routing for S-CSCF URIs” & to add S-CSCF URI value(s)
Generate routing for S-CSCF URIs:
In the S-CSCF section I can choose to activate “generate routing” on the Equipment if it’s not already enabled from Network Settings or set in regexroute/scripts. There is always the option to set the routing with a custom file, manually.
To enable automatic generation of routing on all YateUCN equipment with the IMS configured, I follow these steps:
Network Settings → Node Params and select YateUCN/YateUCN5G Equipment type and check the box for “Generate routing for S-CSCF URIs”. In order to modify something on this page, I have to click “Modify” button from the bottom left corner.
Add S-CSCF SIP URI value(s):
- This value(s) will be used to generate voice call routing rule(s) from other node(s) to this node. Multiple S-CSCF SIP URIs can be inserted separated by comma.
- The suggested value is:
sip:${equipment_name}.${ims_domain}
The value should have the following structure:
sip:${equipment_name}.ims.mnc${MNC}.mcc${MCC}.3gppnetwork.org - Example:
sip:ucn1.ims.mnc001.mcc001.3gppnetwork.org
IMS profile - (Step 8) Profile Management
I go to Profile Management → IMS Profile → press Add or Add default profiles
Subscriber manager - (Step 9) Subscribers & SIMs
In order to configure it, I go to Subscriber Management → Subscribers & SIMs
- Subscribers → IMS section:
- Active
- IMS Profile
- IMPI
- IMPU
- SIMs → check you have:
- IMS Active
- IPPI
- IMPU
Notes:
IMPU/IMPI can be checked either in SIM or Subscribers. Double check should not be neccessary.