Contents
From release tag 6005
Starting with release tag 6005, there’s a new feature that lets me set configurations on all YateUCN devices at once using Node Params. Here’s how I go through it to make sure everything’s set up just right.
In Node Params I can select YateUCN to set a couple of options:
VLR - generate routing for roaming numbers
In order to automatically generate routing for roaming numbers on all YateUCN equipment I check VLR specific box:
- From Network Settings, I go to Node params
- I select Equipment Type YateUCN
- In the VLR section, I make sure to check “Generate routing for roaming numbers“
Notes:
For this configuration to work properly, I need to remove any previous setup of roaming numbers in Scripts/Routing.
The files written in Scripts/Routing will have priority. Even if I select “Generate routing for roaming numbers”, the custom files in Scripts/Routing won’t be overwritten.
Also, if I want to enable the routing for roaming numbers on a specific YateUCN equipment, it can be set up individually from the VLR/CSCF step for each equipment.
S-CSCF - generate routing for S-CSCF URIs
In order to automatically generate routing for S-CSCF URIs on all YateUCN equipment, I do these steps:
- From Network Settings → Node params
- I select the Equipment Type: YateUCN
- In the S-CSCF section, I check “Generate routing for S-CSCF URIs“
Notes:
Any existing S-CSCF URI routing in Scripts/Routing must be removed for this config to work properly.
The files written in Scripts/Routing will have priority. Even if I select “Generate routing for roaming numbers”, the custom files in Scripts/Routing won’t be overwritten.
- If I want to enable the routing for S-CSCF URIs on a specific YateUCN equipment, it can be set up individually from the VLR/CSCF step for each equipment.
Do not confuse with S-CSCF SIP URI, which can only be set individually in each equipment, as it must be unique for each YateUCN/YateUCN5G.
MME features for IMS support
To enable MME features on all YateUCN equipment, I do these steps:
- Network setting→Node Params and I select YateUCN/YateUCN5G Equipment type.
Then, under MME features, I turn on “Advertise IMS support” and any other options that match my setup requirements.
Here are the options I usually consider enabling:
- 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)
Notes:
If I want to enable these only on specific equipment, I can configure it individually in each YateUCN under the MME/SGSN step.
Combined attach options
To enable Combined attach on all YateUCN equipment, I do these steps:
- Network setting→ Node Params I select YateUCN/YateUCN5G Equipment type.
Then, I set the CSFB parameters based on my network plan.
CSFB parameters are configured for each YateUCN equipment with MME support active. Here’s what each CSFB option does:
- Combined – Pretends the CS attach from local MME to the local VLR succeeded even if it didn’t.
- Fake CSFB – Pretends CSFB is available towards local MME even if local VLR does not support it, it’s faked attached. When enabled, supports CSFB via MTRR though foreign network. The ‘Combined’ parameter needs to be true for this to be considered.
- Fake CSFB no reg – Fakes CSFB without sending an internal register. This parameter should be enabled if CS location update is not available in local VLR – MAP protocol is not available. This parameter is ignored if CSFB is not faked.
- PLMN for CS combined attach – The PLMN Identity for CS combined attach when routing fails. This is the PLMN identity with which the CS attach is done to the local VLR.
This parameter can also be set per equipment from the MME wizard step, in which case that value will be prioritized over the one set here. - LAC for CS combined attach – Location Area Code for CS combined attach when routing fails. This is the LAC with which the CS attach is done to the local VLR.
Valid values 0 – 65533. This parameter can also be set per equipment from the MME wizard step, in which case that value will be prioritized over the one set here.
Notes:
To set these options differently for a specific YateUCN equipment, I can do that from the MME/SGSN wizard step for each one. The individual equipment settings will override the global setting from Node Params.
