Hi,
We need to implement a solution to support on the same dual-resilient system, both M3UA IPSP and ASP connections. Our system is made up of 2 SCPs sharing the same Point Code.The IPSP connection is towards a single MSS, each SCP having connection to the same MSS.The ASP connection is towards two separate STPs, each SCP connected to only one STP.
I've checked the "Enabling Dual-Chassis Fault Tolerance with the Dialogic® DSI SIGTRAN Stack" application note and searched through this forum, but did not found any mention if this configuration is possible and some example system/config.txt files. From what I found, basically the solutions are presented as different, never together, however since slightly different commands are used for them, it may be possible to combine.
Has anyone did this configuration? And can share some sample config files?
Thank you,Catalin
Thanks to Dialogic who prepared DPK Release 6.4.4 for Windows, this configuration works fine now on this platform.
For Linux, it was already supported in 6.6.1.
This release allows M3UA to be configured with multiple associations connecting to the same remote Destination Point Code (DPC). This is achieved by adding a Local Application Server (LAS) parameter to the SNRAI command to ensure that each Remote Application server (RAS) has a unique combination of DPC and LAS. The full syntax of the SNRAI command is as follows:
SNRAI:RAS=,[DPC=,][RC=,][NASP=,][TRMD=,][SNMP=,][LAS=];
See below a sample configuration to support both M3UA IPSP and ASP-SG connections:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* CNSYS - configuration of local side
* CNSYS: [IPADDR=,][IPADDR2=,][IPADDR3=,][IPADDR4=,][PER=,][DAUD=,][DUAL=,][AUTOACT=,][SNMP=];
* Set IPADDR to the SIGTRAN address of THIS machine
* Set IPADDR2 if THIS machine has a second SIGTRAN IP address
CNSYS:IPADDR=1.1.1.1,per=0,DUAL=A,SNMP=Y;
*
* SNAPI - Local AS Initiate
* we may want to define more than 1 LAS, for example one for GSM, one for ISUP, one for CDMA, numerated by LAS
* SNAPI:LAS=,[RC=,][SS7MD=,][TRMD=,][SNTYPE=,][OPC=,][TID_START=,][TID_END=,][TID_VALUE=,][SSR_ID=];
* OPC - own point code - get from operator
* RC - Routing context - get from operator
* SS7MD - SS7 variant - ITU14, ITU16, ITU24, ANSI
SNAPI:LAS=1,OPC=1,TRMD=LS,SS7MD=ANSI;
SNAPI:LAS=2,OPC=1,TRMD=LS,SS7MD=ANSI,RC=9;
* SNSLI - configuration of the peer M3UA association
* SNSLI:SNLINK=,IPADDR=,[SG=,][SS7MD=,][IPADDR2=,][IPADDR3=,][IPADDR4=,] [HIPADDR=,][HIPADDR1=,][HIPADDR2=,][HIPADDR3=,][HIPADDR4=,][HPORT=,][PPORT=,][SNEND=,][SNTYPE=,][M2PA=,][M2PA_VER=,][NA=,][M3UAHBT=,][SNMP=,][RTXI=,][RTXD=,][RTXB=];
* Multiple links may be configured, numerated by SNLINK
* Set IPADDR to ipaddress of remote peer. IPADDR2 if a second peer address is applicable
* Set HIPADDR to ipaddress of local machine. HIPADDR2 if a second local address is applicable
* PPORT - remote peer port
* HPORT - host port
* NA - Network Appearance - get from operator
* SG - each remote SG is numerated separately. if there are 2 links for the same entity, same SG may be used
SNSLI:SNLINK=1,IPADDR=2.2.2.2,HIPADDR=1.1.1.1,SNEND=C,SNTYPE=M3UA,PPORT=3000,HPORT=3000,SNMP=Y,NA=1;
SNSLI:SNLINK=2,IPADDR=3.3.3.3,HIPADDR=1.1.1.1,SNEND=C,SNTYPE=M3UA,PPORT=3300,HPORT=3300,SNMP=Y,NA=2,SS7MD=ANSI,SG=2;
* SNRAI - SIGTRAN Remote AS Configuration
* SNRAI:RAS=,[DPC=,][RC=,][NASP=,][TRMD=,][SNMP=,][LAS=];
* set DPC to remote ASP point code
SNRAI:RAS=1,DPC=2,LAS=1; * current link with MSS
* SNALI - SIGTRAN AS List Initiate
* SNALI: SNAL=,RAS=,SNLINK=;
SNALI:SNAL=1,RAS=1,SNLINK=1; * current link with MSS
* SNRTI - SIGTRAN Route Initiate
* SNRTI:SNRT=,[DPC=,][LAS=,][SNTYPE=,][SSN=,][OPTIONS=,][SNMP=];
SNRTI:SNRT=1,DPC=3,LAS=2,SNMP=Y; * to reach STP1
* SNRLI - SIGTRAN Route List Initiate
* Define Signaling Route to Signaling Gateway relationship
* SNRLI:SNRL=,SNRT=,[SG=,][RAS=,][OPTIONS=];
SNRLI:SNRL=1,SNRT=1,SG=2;
* SNLBI - SIGTRAN Local AS Bind Initiate - Bind LAS to SG
* SNLBI: SNLB=,LAS=,[RAS=,][SG=,][RC=,][SNRK=];
SNLBI:SNLB=1,LAS=1,RAS=1;
SNLBI:SNLB=2,LAS=2,SG=2,RC=9;