Topic Location: ClientView Pane Reference
This pane is used to customize an SS7 or CAS signaling variant. When configuring a Signaling Variant, the following happens:
A new variant is created and user then configures an SS7 stack or CAS Channel Group based on that variant. The appropriate messages will be sent to the physical IMG at the appropriate time in the configuration automatically. For example, if the user creates an SS7 variant and under that variant the SS7 Route components are modified, those modifications are sent to the physical IMG only when an SS7 route is configured under an SS7 stack based on the created variant.
NOTE: Once a custom variant is assigned to an SS7 stack or CAS Channel Group you cannot modify or delete an existing entry in the variant. The entry must be deleted and re-added
NOTE: If a variant is assigned to a CAS channel group or SS7 stack the variant cannot be deleted. The entry must be deleted and re-added
Dialogic IMG EMS -> Signaling Variants -> Signaling Variant -> Variant Entry
This field indicates the base variant to be used. This field will be automatically populated based on the Variant Type field in the Signaling Variant object pane that this Variant Entry is being added to.
The PPL component to be configured. This drop down menu will be different for each Variant. (CAS, SS7, SIP-T)
0x01 E1 PPL Component (Only if system is configured as E1)
0x03 T1 PPL Component (Only if system is configured as T1)
The PPL Entity to be configured.
PPL Tables
PPL Timers (10ms increments)
PPL Config Bytes
The PPL table Entity ID is set by the Variant ID. Each Variant has a different set of ID's. See Below
If the PPL Entity is PPL Tables the ID = 1
If the PPL Entity is PPL Timers the ID = 0-255
If the PPL Entity is PPL ConfigBytes the ID = 1-1000
If the PPL Entity Type is PPL Config Bytes the ID = 1-1000
If the PPL Entity Type is PPL Tables, field is "not used"
If the PPL Entity Type is PPL Timers the ID = 0-255 and the PPL Value field becomes PPL Timer Value. 0-65535 (0 to 655 sec)
The PPL Entity File field is used to select the .cfg file which contains the PPL configuration messages to download for that component. This field is available when the PPL Entity type selected is PPL Tables or when the PPL Component ID is 0xFF – Generic File. All the .cfg files should be in the path:
/opt/cantata/IMG/config/Variant/”VariantName” (Software 10.3.3 to 10.5.0)
on the Linux host.
Use this field to add comments.
This field indicates the base variant to be used. This field will be automatically populated based on the Variant Type field in the Signaling Variant object pane that this Variant Entry is being added to.
The PPL component to be configured. This drop down menu will be different for each Variant. (CAS, SS7, SIP-T)
|
0x0f L3P CIC |
0x1b ISUP CGRR |
0x33 MTP3 RTPC |
0x3d MTP3 |
0x82 ISUP DCO |
|
0x12 ISUP SPRC |
0x1c ISUP GBUS |
0x34 MTP3 RTRC |
0x3e MTP3 |
0x83 ISUP CR0 |
|
0x13 ISUP CCI |
0x1d ISUP GBR |
0x35 MTP3 TCBC |
0x3f MTP3 |
0x84 INTERWORKING |
|
0x14 ISUP CRI |
0x1e MTP2 HMUT |
0x36 MTP3 TCOC |
0x40 MTP3 |
0x61 L4CH |
|
0x15 ISUP BLS |
0x26 MTP3 HMRT |
0x37 MTP3 TCRC |
0x41 MTP3 |
0x62 L4CM |
|
0x16 ISUP BLR |
0x2b MTP3 LLSC |
0x38 MTP3 TLAC |
0x76 ISUP CQS |
0xa7 ISUP ACM |
|
0x17 ISUP CRS |
0x2c MTP3 LSAC |
0x39 MTP3 TPRC |
0x77 ISUP CQR |
0xff Generic File |
|
0x18 ISUP CRR |
0x2d MTP3 RSRT |
0x3a MTP3 TSFC |
0x78 ISUP CVS |
|
|
0x19 ISUP UCIC |
0x2e MTP3 RTAC |
0x3b MTP3 TSRC |
0x79 ISUP CVR |
0x01 T1 |
|
0x1a ISUP CGRS |
0x33 MTP3 RTCC |
0x3c MTP3 SLTC |
0x80 ISUP CCO |
0X03 E1 |
The PPL Entity to be configured are.
PPL Tables
PPL Timers (10ms increments)
PPL Config Bytes
When the Component ID is 0xFF (Generic File) the PPL Entity Type field manages which point in the configuration the file set when the PPL Entity File field is sent to the node. The choices for the PPL Entity Type field are:
Stack
Link
Route
Destination
E1
T1
If the PPL Entity is PPL Tables the ID = The ID of the signaling variant. 1-10
If the PPL Entity is PPL Timers the ID = 0-255 and the PPL Value field is PPL Timer Value. 0-65535 (0 to 655.35 sec)
If the PPL Entity is PPL ConfigBytes the ID = 1-1000
If the Component ID is 0xff Generic File then the Entity ID is "Not Used"
This field applies to PPL Config Bytes only. The Value for the Config Byte to be configured.
If the PPL Entity is PPL Tables the PPL Entity Value is "Not Used"
If the PPL Entity is PPL Timers the ID = 0-255
If the PPL Entity is PPL ConfigBytes the ID = 1-1000
If the Component ID is 0xff Generic File then the Entity Value is "Not Used"
The PPL Entity File field is used to select the .cfg file containing the PPL configuration messages to download for that component. This field is available when the PPL Entity type selected is PPL Tables or when The PPL Component ID is 0xFF – Generic File.
All the .cfg files should be in the path:
/opt/cantata/IMG/config/Variant/”VariantName” (Software 10.3.3 to 10.5 0)
on the Linux host.
Use this field to add comments.
This field indicates the base variant to be used. This field will be automatically populated based on the Variant Type field in the Signaling Variant object pane that this Variant Entry is being added to.
The PPL component to be configured. The only component that can be selected is:
0xff Generic File
The PPL Entity to be configured.
SIP-T Message format
Not Used
Not Used
The PPL Entity File field is used to select the .cfg file containing the PPL configuration messages to download for that component. This field is available when the PPL Entity type selected is PPL Tables or when The PPL Component ID is 0xFF – Generic File.
All the .cfg files should be in the path:
/opt/cantata/IMG/config/Variant/”VariantName” (Software 10.3.3 to 10.5.0)
on the Linux host.
Use this field to add comments.
This table shows a list of the configured Variant entries under the Signaling variant.