Variant Entry

Description:

The Variant Entry pane is used to customize an SS7 or CAS signaling variants. When configuring a Signaling Variant, the following happens:

When a new variant is created; the user can then configure an SS7 stack based on that variant. The appropriate messages will be sent to the physical IMG at the appropriate time in the configuration automatically.

For example:

An SS7 variant is created and under that variant the SS7 Route components are modified. The routing modifications are sent to the Physical IMG so when an SS7 route is configured under the SS7 stack just created and modified, the routing components will use specifications/routing based on the created variant.

 

Note: Once a custom variant is assigned to an SS7 stack or CAS Channel Group it cannot modified or deleted. To modify an existing entry in the variant, the entry must be first deleted and re-added

 

Accessing this Pane:

Dialogic IMG EMS -> Signaling Variants -> Signaling Variant -> Variant Entry

SC_Tree_VariantEntry.png

 

Previous Configuration Required:

Signaling Variant

 

Next Configuration Tasks (CAS):

Digit Mapping

Filter/Timer Configure

Inpulsing Parameters

Inseize Instruction

Outseize Instruction

 

Related Topics:

Signaling Variant

Configuring CAS

Creating Custom SS7 Variants

 

 

Field Descriptions (CAS)

ClientView Default Pane:

SC_Variant_Entry_10.5.0.png

 

 

Base Variant:

The Base Variant field indicates the base variant to be used. This field will be automatically populated based on the 'Base Variant' and 'Variant Type' fields that were initially configured in the 'Signaling Variant' object pane.

 

PPL Component ID:

The PPL component to be configured. This drop down menu will be different for each Variant. (CAS, SS7, SIP-T)

 

0x01 E1 PPL Component - Automatically populated if system is configured as E1.

0x03 T1 PPL Component - Automatically populated if system is configured as T1.

 

PPL Entity Type:

The PPL Entity is selected from drop down menu. Below are the selections:

PPL Tables

PPL Timers (10ms increments)

PPL Config Bytes

 

PPL Entity ID:

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 = 2

If the PPL Entity is PPL Timers the ID = 0-255

If the PPL Entity is PPL Config Bytes the ID = 1-1000

 

PPL Entity Value:

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)

If the PPL Entity Type is PPL Config Bytes the ID = 1-1000

 

 

PPL Entity File:

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 loaded into the following directory on the GCEMS server:

/opt/dialogic/IMG/config/Variant/”VariantName” (Software 10.5.1 +)

 

Comments:

Use this field to add comments.

 

 

 

 

Field Descriptions (SS7):

ClientView Default Pane:

SC_Variant_Entry_10.5.0_SS7.png

 

 

Base Variant:

The Base Variant field indicates the base variant to be used. This field will be automatically populated based on the 'Base Variant' and 'Variant Type' fields that were initially configured in the 'Signaling Variant' object pane.

 

PPL Component ID:

The PPL component to be configured. This drop down menu will be different for each Variant. (CAS, SS7, SIP-T)

 

       

0x0f  L3P CIC

0x1f ISUP HGBR

0x36 MTP3 RTPC

0x47 ISUP HGBS

0x10  L3P LINK

0X20 MTP2 AERM

0x37 MTP3 RTRC

0x76 ISUP CQS

0x12 ISUP CPC

0X21 MTP2 CC

0x38 MTP3 TCBC

0x77 ISUP CQR

0x13 ISUP SPRC

0X22 MTP2 IAC

0x39 MTP3 TCOC

0x78 ISUP CVS

0x14 ISUP CCI

0X23 MTP2 LSC

0x3a MTP3 TCRC 0x79 ISUP CVR

0x15 ISUP CRI

0X24 MTP2 RC

0x3c MTP3 TLAC 0x80 ISUP CCO

0x16 ISUP BLS

0X25 MTP2 SUERM

0x3d MTP3 TPRC

0x81 ISUP CRCS

0x17 ISUP BLR

0x26 MTP2 TXC

0x3f MTP3 TSFC

0x82 ISUP DCO

0x18 ISUP CRS

0x2b MTP3 HMDT

0x40 MTP3 TSRC

0x83 ISUP CRO

0x19 ISUP CRR

0x2c MTP3 HMRT

0x41 MTP3 SLTC

0x84 INTERWORKING

0x1a ISUPUCIC

0x2d MTP3 LLSC

0x42 ISUP HLB 0x85 ISUP SSC

0x1b ISUP CGRS

0x2e MTP3 LSAC

0x43 ISUP HRB

0x61 L4 CH

0x1c ISUP CGRR

0x33 MTP3 RSRT

0x44 ISUP CRCR

0x62 L4 CM

0x1d ISUP GBUS

0x34 MTP3 RTAC

0x45 ISUP MGBS

0xA8 ISUP ACC

0x1e ISUP GBUR

0x35 MTP3 RTCC

0x46 ISUP MGBR

0xff Generic File

 

 

PPL Entity Type:

The PPL Entity is selected from drop down menu. Below are the selections:

PPL Tables

PPL Timers (10ms increments)

PPL Config Bytes

 

When the Component ID is 0xFF (Generic File) the PPL Entity Type field manages where and when in the configuration file being sent that the Variant Entry information is sent to the node. The choices for the PPL Entity Type field are:

Stack

Link

Route

Destination

E1

T1

 

PPL Entity ID:

 

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 = 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"

 

PPL Entity Value:

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"

 

PPL Entity File:

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 loaded into the following directory on the GCEMS server:

 

/opt/dialogic/IMG/config/Variant/”VariantName”    (Software 10.5.1 +)

 

Comments

Use this field to add comments.

 

 

Field Descriptions (SIP-T)

ClientView Default Pane:

SC_Variant_Entry_10.5.0_SIPT.png

 

Base Variant:

The Base Variant field indicates the base variant to be used. This field will be automatically populated based on the 'Base Variant' and 'Variant Type' fields that were initially configured in the 'Signaling Variant' object pane.

 

PPL Component ID:

The PPL component to be configured. The only component that can be selected is:

0xff Generic File

 

PPL Entity Type:

The PPL Entity to be configured. The only component that can be selected is:

SIP-T Message format

 

PPL Entity ID:

Not Used

 

PPL Entity Value:

Not Used

 

PPL Entity File:

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 loaded into the following directory on the GCEMS server:

 

/opt/dialogic/IMG/config/Variant/”Variant Name”  (Software 10.5.1 +)

 

 

Comments

Use this field to add comments.

 

Display Table:

This table shows a list of the configured Variant entries under the Signaling variant.