Training ITP A Hughes and VSSP v0.1

Cisco ITP in eServGlobal IN
Configuring Hughes and V.SSP
PS and Support Internal Training

Diegem
Dennis Hagarty
Implementation Practice
7 September 2006
© 2006 eServGlobal Ltd

Configuration of the SUA (Hughes) Stack
Configuring Hughes and V.SSP | 2 | © 2006 eServGlobal

Hughes TCAP Interface Configuration
 N.B. I will only concentrate on the major Sigtran parameters

 Need to update three types of files:
 SLEE.cfg to define the SUA TCAP (Hughes) Interfaces for the SLEE
 A script (something like hssScIf.sh) to start each SUA interface
 peers.conf to define the ITPs to be our Signalling Gateways
 TCAP Interface Technical Manual (3.4.28-01.01) is the bible

 The SUA startup script is executed by the SLEE at startup
 One can have multiple peers files:
 e.g. to define the secondary network interfaces on the ITP to be
primary for some services/traffic types…
 e.g. where there are separate ITP in different sites, the file can be
named based on the site where they are deployed to avoid confusion

SLEE.cfg
 Declare the interfaces to the SLEE (at least one)

INTERFACE=<interface-name> <Script-file-name> <Script-file-dir> EVENT
 Example of the interface declarations (one for Camel, one USSD)

INTERFACE=hssScIf-CAP hssScIf-CAP.sh /IN/service_packages/SLEE/bin EVENT
INTERFACE=hssScIf-USSD hssScIf-USSD.sh /IN/service_packages/SLEE/bin EVENT
(This means that /IN/service_packages/SLEE/bin should contain two script files, one called hssScIf-
CAP.sh and one called hssScIf-USSD.sh to execute on startup).
 Declare the SSN/Service Key of each interface to the SLEE (Hex)

SERVICEKEY=INTEGER 0x1<SSN><Service-key> <Service-Name>
(The SSN should be 2 Hex digits, and the Service key be 8 Hex digits, total length = 9 Hex digits)
 Example of the SSN and Service Key declarations (Hex)

SERVICEKEY=INTEGER 0x1920000019A PREPAID #SSN 146, SK 410 for Camel
SERVICEKEY=INTEGER 0x19300000037 ussdgw #SSN 147, SK 55 for USSD Gateway
SERVICEKEY=INTEGER 51 USSDCB #Service Key 51 for USSD Call Back
(The service keys must be agreed with the operator. One simple way to learn them is to check the
SLEE log files to see and message like “Unrecognized service key xxxxxxxxx”)

Hughes Camel Start-up File 1/8
 This is the hssScIf startup file:

exec ../bin/hssSccpTcapInterface \
-pc <PC-of-SUA> -ssns <SSNs-of-SUA> -stps <ITP1-PC,ITP2-PC> -proto INAP \
-rcbase <Route-Context> -rcstep 10 -inapssns 146 -mapssns 8 \
-port <SCTP-Port-#> -netaddr <Prim-IP> -secondary_netaddr <Sec-IP> \
-peerfile <Name-of-peers-file> -qos <Return-on-error_and_SCCP_Class> \
-retaddr nonstd -retssn <SSN> -retri 0 -retgt 4,0,1,4,<Returned-Cg-GT> \
-rto_init 350 -rto_min 250 -rto_max 750 -bundling_time 5 -hb_interval 2 \
-tx_buffers 3000 -rx_buffers 3000 -sendorigaddr true -conntimer 1 \
-assoc_max_retrans 6 -path_max_retrans 3 -maxSctpModeRetry 10 \
-maxdids 132000 -sleekey 0x01 -hss_stats 0 \
>> /IN/service_packages/SLEE/tmp/hssScIf-CAP.log 2>&1

 Declare the SS7 parameters of the interface:

-pc <PC-of-SUA> -ssns <SSNs-of-SUA> -stps <ITP1-PC,ITP2-PC> -proto INAP \
-rcbase <Route-Context> -rcstep 10
 The SPC of the AS configured for this UAS on the ITP
 A comma separated list of SCCP subsystem numbers (SSNs) that the
TCAP will register to and should agree with the ITP AS definitions
 A comma-separated list of STP point codes to which the interface
should round-robin route outward messages (IP addresses taken from
peers.conf are used to initiate SCTP associations)
 The protocol to be conveyed by this TCAP interface
 Routing Context IDs are allocated incrementally starting from this
number. They must:
 Be unique within the network, and
 Match those configured in AS of the ITP signalling gateway
 rcstep is what is added to Rout. Context each time it is incremented
 hssScIf startup parameters for IP and declaring SSN formats:

-inapssns 146 -mapssns 8 -port <SCTP-Port-#> -netaddr <Prim-IP> \
-secondary_netaddr <Sec-IP> -peerfile <Name-of-peers-file> \
 inapssns is a comma-separated list of the SCCP subsystem numbers
(SSNs) that the TCAP interface will treat as INAP (regardless of the
default protocol defined by -proto)
 mapssns is a comma-separated list of the SCCP subsystem numbers
(SSNs) that the TCAP interface will treat as MAP (regardless of the
default protocol defined by –proto)
 port is the local port to bind to when creating the SCTP associations
 netaddr is the local primary IP address to bind to for SCTP
 secondary_netaddr is the local secondary IP address to bind to
 peerfile is the name of the peers file in the SLEE/etc directory

 hssScIf returned traffic SCCP headers:

-qos <Return-on-error_and_SCCP_Class> -retaddr nonstd -retssn <SSN> \
-retri 0 –retpc <Returned-SPC> -retgt 4,0,1,4,<Returned-Cg-GT> \
 qos is a combination of the class and message handling value to use
on messages sent out of interface. Allowed values:
 0 Use SCCP class 0 (unordered delivery) service
 1 Use SCCP class 1 (ordered delivery) service
Note: Add 128 (0x80) to specify that SCCP should return messages on
transmission error
 If retaddr=nonstd, the TCAP stack can perform the non-Q.774
behaviour of allowing the TC-User to override the SCCP cgPA of TC-
END messages (Q.774 only allows overrides of the first TC-Cont)
 Any of retri, retssn, retgtt, retpc being defined will indicate to use this SCCP
Calling Party Addr. in the first TC-Continue that it sends out (by default the
TCAP will use the SCCP destination address of the first incoming message)

 hssScIf startup:
-rto_init 350 -rto_min 250 -rto_max 750 -bundling_time 5 -hb_interval 2 \
-tx_buffers 3000 -rx_buffers 3000
 rto_init is the initial SCTP retransmission timeout (RTO) in msec

 rto_min is the minimum allowed SCTP RTO in msec
 rto_max is the maximum allowed SCTP RTO in msec
 bundling_time is number of msec to wait to allow a bundle of CLDT
messages to be collected into a single Ethernet frame for transmission
 hb_interval is the number of seconds between heartbeats over any
one of the SCTP interfaces which have not received any traffic since
the last heartbeat (doesn’t seem to be precisely honoured)
 tx_buffers and rx_buffers is the number of buffers that SCTP
maintains per association transmit (receive) free queue. The Hughes
SCTP stack maintains three free queues per association

 SCTP Timer setup (mostly):

-sendorigaddr true -conntimer 1 -assoc_max_retrans 6 -path_max_retrans 3
-maxSctpModeRetry 10 -maxdids 132000
 If sendorigaddr is set to true the TCAP interface will send the SCCP
origination address as well as the destination addr. to the TCAP stack
 conntimer is the number of seconds between retries when an attempt
is being made to renew a connection to the peer
 assoc_max_retrans is the maximum number of times that SCTP will
attempt communication with a peer before deleting an association
 path_max_retran is the max number of times that SCTP will try to
retransmit on a path before considering a path unreachable. It is used
in conjunction with assoc_max-retrans
 maxdids is the maximum number of concurrent TCAP dialogues that
can be handled by the interface.

 Other various parameters:

-sleekey 0x1 -hss_stats 0 -hopcount <0-15> -asmode <Mode> \
>> <Name-of-Log-file> 2>&1
 Base SLEE service key value to use – 0x1 represents a base SLEE
service key of 0x10000000000 (see first slide on SSN and SK)
 hss_stats being zero will disable the statistics tracking and logging
within Hughes SCTP/SUA stack (recommended when # stacks > 1)
 hopcount being set to zero or greater indicates that outgoing
messages will be sent as XUDTs to include this SCCP header field
 asmode defines the traffic mode of the ASP within the AS and can be:
 1 = override (there is a primary and a secondary ASP in the AS)
 2 = load share (default – the traffic is load-shared between the ASPs in AS)
 3 = broadcast (the data is sent to all ASPs in the AS)
 The last piece defines a log file for sysout and syserr

 This is an example of one customer hssScIf file:

-pc 8435 -ssns 146 -rcbase 100 -port 14001 -stps 8439,8440 \
-netaddr 97.32.12.76 -secondary_netaddr 97.32.12.140 \
-retgt 4,0,1,4,919827002400 -peerfile peers-CAP.conf \
-rto_init 350 -rto_min 200 -rto_max 500 -bundling_time 5 \
-conntimer 1 -hb_interval 2 -tx_buffers 3000 -rx_buffers 3000 \
-assoc_max_retrans 6 -path_max_retrans 3 -inapssns 146 -mapssns 8 \
-retssn 146 -retaddr nonstd -conntimer 5 -maxdids 132000 \
-sendorigaddr true -sleekey 0x01 -retri 0 \
-qos 0x81 -maxSctpModeRetry 10 -hss_stats 0 -rcstep 10 \
-proto INAP >> /IN/service_packages/SLEE/tmp/hssScIf-CAP.log 2>&1

Defining peers.conf 1/2
 This file in SLEE/etc defines the signalling gateways

 Must contain the PCs from the –stps command in hssScIf
peers
# Signalling Gateway Peers
peer ( 2 SG 2 <ITP1-PC> <SUA-Port> <Primary-IP> <Secondary> )
peer ( 3 SG 3 <IPC2-PC> <SUA-Port> <Primary-IP> <Secondary> )
dummy 2:
 Must contain the last line (don’t ask)

 Must have spaces before the “peer (”
 Must have spaces before and after “(“ or “)”
 Order of the IP addresses is IMPORTANT. Primary IP must
be first, and be the logical partner to that in netaddr and
second address the logical partner to secondary_netaddr

Defining peers.conf 2/2
 The format of a peer configuration option for an ASP is:

peer ( <id> SG <sgid> <pc> <port> <prim_ip> <sec_ip> <TRAFFIC-MODE> )
 id = the unique SUA identifier for the SG
 sgid= the signalling gateway (SG) the SGP belongs to
 pc = the pointcode of the SG.
 port = the SCTP port for the SUA stack on the remote SG
 prim_ip = the primary ip of this SG
 sec_ip = the secondary ip of this SG
 Traffic mode is optional parameter and must agree with asmode

 If left blank it means default load-share mode (asmode=2)
 If specified with asmode = 1 (Override traffic mode):
 OVERRIDE-ACTIVE means override mode, with this ASP active
 OVERRIDE-INACTIVE means override mode, with this ASP inactive

Configuration of the V.SSP

V.SSP Overview
 VSSP (also called UCA-I) is a ISUP call control agent

 It’s a virtual SSP, because it doesn’t actually have any trunks
 Used for services like USSD Call-back:
 Subscriber A sends a USSD string with the B party number in it
 USSD string is routed back to the home HLR
 HLR sends the USSD string to the USSD Gateway
 USSD gateway sends (eventually) an InitialDP to the V.SSP
 V.SSP tells its mated SSP to setup a call back to Subscriber “A”
 When the call in answered, V.SSP tells its mated SSP to setup a new
call to “B” number specified in the USSD string over another trunk
 If the first trunk is looped together with the second, you have the two
legs of the call (A-leg and B-leg) talking to each other – a phone call!!

Normal SSP Coupling
 SSPs are linked together with voice trunks and signalling

 The trunks and signalling can be on the same E1 (“F” links)
 Sometimes the signalling can go via an STP (“A” links)
PC 250
Signalling Link Signalling Link
STP
MSC MSC
PC 100 PC 200
Voice Trunks
Signalling Link
MSC MSC
PC 100 PC 200
Voice Trunks

ISUP Call Setup
 When a call is placed to an out-of-switch number, the originating

SSP transmits an ISUP initial address message (IAM) to
reserve an idle trunk circuit from the originating switch to the
destination switch (http://www.pt.com/tutorials/ss7/isup.html)
 The IAM includes the originating point code, destination point
code, circuit identification code of the trunk, dialled digits and,
optionally, the calling party number and name.
 CICs are usually serially allocated from the first E1:
 1 – 31
 33 – 63
 65 – 95
 97 – 127
 … etc
 EACH end of the trunk must agree to the numbering order!!!!

SSP to V.SSP Coupling
 What if we coupled an SSP via signalling links but not voice links?
 The signalling can go via an STP (in the case the ITP) to V.SSP
 We loop the trunks from the SSP back into the same SSP
 That way, we can tell the SSP to set up an “A leg” of a call, then
connect up the “B leg” of the call on the looped-back pair of the
first! Then, the “A party” will hear the “B party” and vice versa.
PC 250
Signalling Link Signalling Link
MSC
PC 100
Looped-back Voice Trunks PC 200

Configuring V.SSP 1/5
 With the V.SSP, we have two files to configure:

 m3ua.config – contains the M3UA ASP and SG configuration info
 vssp.config – contains the details of CICs and SSPs
 m3ua.config
asp port <Port-Num> addrs {<Primary-IP>,<Secondary-IP>};
sgp <SGP-Name> port <Port-Num> addrs {<Primary-IP>,<Secondary-IP>};
 asp clause defines the local ASP

 Port-num is the port number to locally bind to (standard: 2905)
 Primary and Secondary IP are the local IP addresses to bind to
 sgp clause defines the SGP information for the SG (ITP)

 SGP Name will be used later
 Port-num is the remote port number to connect to (standard: 2905)
 Primary and Secondary IP are the remote IP addresses to connect to

 m3ua.config
gateway <SG-Name>
{
sgp <SGP-Name> key <Routing-Context> ;
pc { <PC-of-this-SG>,<PC-of-the-remote-SSP> };
}
as pc <V.SSP-PC> gateway {<SG-Name-1>,<SG-Name-2>};
 gateway clause (normally 2 of them) defines the SG(s)

 SG name will be used in the AS definition
 Routing context must be the value used on the ITP for the AS
 pc clause is an MTP3 routing declaration

 PC of the this SG is the ITP point code
 SSP PC is the PC of the remote SSP that lies behind it
 as clause is the AS definition with the V.SSP point code

 SG-Name is the name of the SG in the gateway clause declaration

 vssp.config
set option debug;
set option mtp debug;
set option startup time 15;
set option syslog;
connect <VSSP_pc>/<SSP_pc>/<incoming_cic> to
<VSSP_pc>/<SSP_pc>/<outgoing_cic> [ for <number-of-CICs> ] ;
connect 200/100/1 to 200/100/33 for 31;
connect 200/100/65 to 200/100/97 ;
 Various debug options to start (please turn off in production)
 VSSP PC must be declared in the m3ua.config (“as” clause)
 SSP PC must have a route in the m3ua.config (“pc” clause)
 incoming-CIC number is assumed looped to outgoing-CIC no.
 “for nn” is a way of repeating the command for “nn” CICs

 vssp.config
connect 200/100/1 to 200/100/33 for 31;
connect 200/100/65 to 200/100/97 ;
.
.
.
connect 200/100/94 to 200/100/126 ;
connect 200/100/95 to 200/100/127 ;
connect 200/111/1 to 200/111/33 for 31;

connect 200/111/65 to 200/111/97 for 31;
 This (eg) says that E1 with CICs 1-31 is looped to CICs 33-63
 The “for 31” is the most common
 You can write it out long-hand, if you really want to
 0, 32, 64, 96, 128, etc are never used. Why?
 Each combination of V.SSP and SSP usually starts CICs from 1

 Example m3ua.config
asp port 2905 addrs {192.168.100.20,192.168.100.150};
sgp itp1 port 2905 addrs {192.168.100.50,192.168.100.180};
sgp itp2 port 2905 addrs {192.168.100.51,192.168.100.181};
gateway sg1
{
sgp itp1 key 200;
pc {250,100};
}
gateway sg2
{
sgp itp2 key 200;
pc {251,100};
}
as pc 200 gateway {sg1,sg2};

Aligning ITP and UAS Configurations

Example Sigtran Configuration – UAS
 hssScIf.sh
#!/bin/ksh
-pc 3212 -ssns 12,146 \
-sendorigaddr true \
-port 14001 \
-rcbase 101 -netaddr 172.20.66.66 \
-secondary_netaddr 172.20.66.98 \
-stps 3210,3211 \
-maxdids 132000 \
-asmode 1 –conntimer 5 \
-rto_init 1000 -rto_max 5000 -rto_min 500 -hb_interval 10 \
-assoc_max_retrans 6 -path_max_retrans 3 -maxSctpModeRetry 10 \
-sccp itu -proto any \
-inapssns 12 \
>> /IN/service_packages/SLEE/tmp/hssScIf.log 2>&1
 peers.conf
peers
peer ( 2 SG 1 3210 15000 172.20.66.68 172.20.66.100 )
peer ( 2 SG 1 3211 15000 172.20.66.69 172.20.66.101 )
dummy 2:

Example Sigtran Configuration - ITP
 SUA
 Defines the local IP port for incoming SUA connections
cs7 point-code 3210
cs7 sua 15000

local-ip 172.20.66.68
local-ip 172.20.66.100
assoc-retransmit 6
path-retransmit 3
retransmit-timeout 500 5000
tx-queue-depth 2000
 ASP
 Builds the IP streams for each ITP – UAS connection
cs7 asp SYDSCP01-ASP 14001 15000 sua
remote-ip 172.20.66.66
remote-ip 172.20.66.98
 AS
 Sets the Point Code and SSN for each ASP
cs7 as SYDSCP01-AS sua
routing-key 101 3212 si sccp ssn 12
asp SYDSCP01-ASP

Sigtran Configurations
 hssScIf.sh  SUA
#!/bin/ksh cs7 point-code 3210
-pc 3212 -ssns 12,146 -port 14001 \ cs7 sua 15000
-sendorigaddr true \ assoc-retransmit 6
path-retransmit 3
-rcbase 101 -rcstep 10
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-secondary_netaddr 172.20.66.98 \ local-ip 172.20.66.102
-stps 3210,3211 -maxdids 132000 \
-asmode 1 -conntimer 5 \  ASP
-rto_init 1000 -rto_max 5000 \ cs7 asp SYDSCP1-ASP 14001 15000 sua
-rto_min 500 -hb_interval 10 \ remote-ip 172.20.66.66
-assoc_max_retrans 6 \ remote-ip 172.20.66.98
-path_max_retrans 3 \
-sccp itu -proto any \  AS
-inapssns 12,146 \ cs7 as SYDSCP1-AS1 sua
 peers.conf asp SYDSCP1-ASP
peer ( 2 SG 1 3210 15000 172.20.66.70 cs7 as SYDSCP1-AS2 sua
172.20.66.102 ) routing-key 111 3212 si sccp ssn 146
peer ( 3 SG 2 3211 15000 172.19.40.197 asp SYDSCP1-ASP
172.19.40.229 )

Sigtran Configurations - STP/ITP Point Code
UAS ITP
-sendorigaddr true \ assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
-sccp itu -proto any \  AS
cs7 as SYDSCP1-AS1 sua
-inapssns 12,146 \ routing-key 101 3212 si sccp ssn 12
peer ( 2 SG 1 3210 15000 172.20.66.70 cs7 as SYDSCP1-AS2 sua
172.20.66.102 ) routing-key 111 3212 si sccp ssn 146
peer ( 3 SG 2 3211 15000 172.19.40.197 asp SYDSCP1-ASP
172.19.40.229 )

Sigtran Configurations – ITP SUA Port
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
-sccp itu -proto any \ cs7 as SYDSCP1-AS1 sua
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – IP Addresses
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – Retransmission Parameters
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – Timeout Parameters
UAS ITP
assoc-retransmit 6
path-retransmit 3
-rcbase 101 -rcstep 10 retransmit-timeout 500 5000
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – UAS SUA Port
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – ITP ASP and SUA Instance
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – UAS IP Addresses
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – Routing Keys
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – UAS Point Codes
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

Sigtran Configurations – Sub-System Numbers
UAS ITP
assoc-retransmit 6
path-retransmit 3
-netaddr 172.20.66.66 \ local-ip 172.20.66.70
-stps 3210,3211 -maxdids 132000 \
 AS
peer ( 2 SG 1 3210 15000 172.20.66.70
172.20.66.102 )
asp SYDSCP1-ASP
peer ( 3 SG 2 3211 15000 172.19.40.197
172.19.40.229 )

ITP Command Set Categories
 Global Options and Commands

 Configuration of a Low Speed and High Speed Link (64Kb/2Mbit)
 Link and linkset commands, including M2PA linksets
 M2PA commands
 M3UA commands
 Peer, mated SG and SGMP commands
 SUA (AS and ASP) commands
 MTP3 Routing
 Global Titles
 Debug commands
 Troubleshooting

Training ITP A Hughes and VSSP v0.1

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Training ITP A Hughes and VSSP v0.1

Transféré par

Droits d'auteur :

Formats disponibles

Cisco ITP in eServGlobal IN

Configuring Hughes and V.SSP

PS and Support Internal Training

© 2006 eServGlobal Ltd

Configuring Hughes and V.SSP | 2 | © 2006 eServGlobal

 N.B. I will only concentrate on the major Sigtran parameters

 TCAP Interface Technical Manual (3.4.28-01.01) is the bible

Configuring Hughes and V.SSP | 3 | © 2006 eServGlobal

 Declare the interfaces to the SLEE (at least one)

 Example of the interface declarations (one for Camel, one USSD)

 Declare the SSN/Service Key of each interface to the SLEE (Hex)

 Example of the SSN and Service Key declarations (Hex)

Configuring Hughes and V.SSP | 4 | © 2006 eServGlobal

 This is the hssScIf startup file:

Configuring Hughes and V.SSP | 5 | © 2006 eServGlobal

 Declare the SS7 parameters of the interface:

 hssScIf startup parameters for IP and declaring SSN formats:

Configuring Hughes and V.SSP | 7 | © 2006 eServGlobal

 hssScIf returned traffic SCCP headers:

Configuring Hughes and V.SSP | 8 | © 2006 eServGlobal

 rto_init is the initial SCTP retransmission timeout (RTO) in msec

Configuring Hughes and V.SSP | 9 | © 2006 eServGlobal

 SCTP Timer setup (mostly):

Configuring Hughes and V.SSP | 10 | © 2006 eServGlobal

 Other various parameters:

Configuring Hughes and V.SSP | 11 | © 2006 eServGlobal

 This is an example of one customer hssScIf file:

Configuring Hughes and V.SSP | 12 | © 2006 eServGlobal

 This file in SLEE/etc defines the signalling gateways

 Must contain the last line (don’t ask)

Configuring Hughes and V.SSP | 13 | © 2006 eServGlobal

 The format of a peer configuration option for an ASP is:

 Traffic mode is optional parameter and must agree with asmode

Configuring Hughes and V.SSP | 14 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 15 | © 2006 eServGlobal

 VSSP (also called UCA-I) is a ISUP call control agent

Configuring Hughes and V.SSP | 16 | © 2006 eServGlobal

 SSPs are linked together with voice trunks and signalling

Configuring Hughes and V.SSP | 17 | © 2006 eServGlobal

 When a call is placed to an out-of-switch number, the originating

 EACH end of the trunk must agree to the numbering order!!!!

Configuring Hughes and V.SSP | 18 | © 2006 eServGlobal

Looped-back Voice Trunks PC 200

Configuring Hughes and V.SSP | 19 | © 2006 eServGlobal

 With the V.SSP, we have two files to configure:

 asp clause defines the local ASP

 sgp clause defines the SGP information for the SG (ITP)

Configuring Hughes and V.SSP | 20 | © 2006 eServGlobal

 gateway clause (normally 2 of them) defines the SG(s)

 pc clause is an MTP3 routing declaration

 as clause is the AS definition with the V.SSP point code

Configuring Hughes and V.SSP | 21 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 22 | © 2006 eServGlobal

connect 200/111/1 to 200/111/33 for 31;

Configuring Hughes and V.SSP | 23 | © 2006 eServGlobal

as pc 200 gateway {sg1,sg2};

Configuring Hughes and V.SSP | 24 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 25 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 26 | © 2006 eServGlobal

cs7 sua 15000

Configuring Hughes and V.SSP | 27 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 28 | © 2006 eServGlobal

Configuring Hughes and V.SSP | 29 | © 2006 eServGlobal