You are here: CSP API Reference > 1 EXS & SwitchKit API Messages > SS7 Signaling Stack Configure 0x005C
SS7 Signaling Stack Configure 0x005C
SwitchKit Name
SS7SignalingStackConfig
Type
EXS API and SwitchKit API message
Description
Use this message to define a signaling stack, which includes assigning an OPC and a variant. You can also use this message to deconfigure a signaling stack.
NOTE: PCM encoding for CICs controlled by the signaling stack is defaulted based on the network signaling variant. ANSI stacks default to u-law regardless of the physical link type. ITU stacks default to A-law. To change the encoding format see the PCM Encoding Format message.
Sent by:
SwitchKit Code
Configuration
SS7SignalingStackConfig (
Node = integer,
Slot = integer,
Stack = integer,
OPC = integer,
NumModules = integer,
Data = byte array);
C Structure
typedef struct {
UBYTE Slot;
UBYTE Stack;
int OPC;
UBYTE NumModules;
UBYTE Data[218];
} XL_SS7SignalingStackConfig;
C++ Class
class XLC_SS7SignalingStackConfig : public XLC_OutboundMessage {
public:
UBYTE getSlot() const;
void setSlot(UBYTE x);
UBYTE getStack() const;
void setStack(UBYTE x);
int getOPC() const;
void setOPC(int x);
UBYTE getNumModules() const;
void setNumModules(UBYTE x);
const UBYTE *getData() const;
UBYTE *getData();
void setData(UBYTE *x);
EXS API Hex Format
MESSAGE (White) |
RESPONSE (Gray) |
||
Byte |
Field Description |
Byte |
Field Description |
0 |
Frame (0xFE) |
0 |
Frame (0xFE) |
1, 2 |
Length (0x00NN) |
1, 2 |
Length (0x0007) |
3, 4 |
Message Type (0x005C) |
3, 4 |
Message Type (0x005C) |
5 |
Reserved (0x00) |
5 |
Reserved (0x00) |
6 |
Sequence Number |
6 |
Same Sequence Number |
7 |
Logical Node ID |
7 |
Logical Node ID |
8 : |
Address Method 0x00 - Individual AEs
|
8, 9 |
The meaning of these fields depends upon the value of the Entity field in the message.
Product License Data The following value can be received: 0x007F Software module still locked. This value is returned when |
10 |
Checksum |
||
Number of AEs to follow |
|
||
AEs |
|||
: |
OPC (four bytes) The address assigned to the Excel platform by the network. Every point code in the API messages will always be 4 bytes long, with the first byte (MSB) as zero. See the SS7 section of the API Developer's Guide: CCS for an explanation of how to convert the 4 bytes into ITU and ANSI point codes.
0x00000000–0x00FFFFFF:
0x00000000–0x00003FFF: If using the BT IUP protocol, the maximum range for OPC is 14 bits.
0xFFFFFFFF: |
||
13 |
Number of Modules (n) |
||
11 |
Module 1: Type 0x01 MTP (Message Transfer Part) 0x02 ISUP (ISDN User Part) 0x03 L3P (Layer 3 Plus) 0x04 TUP (Telephone User Part) 0x05 L3P TUP/BT IUP (Layer 3 Plus for Telephone User Part/BT IUP) 0x06 SCCP 0x07 TCAP When using BT IUP, you must configure MTP. For example, if you are configuring the ISUP Call Control User Part, then you would send this message with three sets of module
When using the BT IUP variant, the Module Variant is 0x02. You must also configure module types 0x01and 0x03. For example, in an E1 configuration, you would specify Module Type 0x01 with a variant of 0x01, Module 3 with a variant of 0x01, Module 4 with a variant of 0x02, and Module 5 with a variant of 0x02. |
||
: |
Module 1: Variant (see information below this table) |
||
: |
Module n: Type |
||
: |
Module n: Variant |
||
: |
Checksum |
Module Variant
The following variants are tested and supported.
Value |
Description |
Modules |
---|---|---|
0x00 |
ANSI ‘97 |
All Modules |
0x01 |
ITU-TS ‘97 |
All Modules |
0x02 |
BT IUP |
Module Types 4 & 5 when BT IUP is required |
0x03 |
SSUTR2 |
Module Types 4 & 5 when BT IUP is required |
0x08 |
JT |
Module Type 1 only |