Configuring signaling between MSC Servers

MSC Server Integration

Parameter name
SIP_MAX_FORWARDS
(052:0011)

DSCP_FOR_SIGNALING
(053:0009)

RETRY_AFTER_INTERVAL
(052:0018)

Description

Default values

Indicates what should be the

default value of Max-Forwards SIP
header field. This field is relevant if
SIP is used non-point-to-point
towards the CPS.

Allowed values:
1-70

Gives the DiffServ Code Point

(DSCP) value to be used with
sockets. The parameter gives the
operator the possibility to request a
given QoS for SIP signaling.

Default value:
022h

Defines how long the sender must

wait before retrying the request.

Allowed values:
30-300 s (decimal)

Default value: 70

The default value

is 030H, but the
parameter should
be adjusted to
correspond AF41
Per Hop Behavior, that is 22h

Default value: 60
s
SIP_INVITE_RETRANS
(052:000)

Number of retransmissions for

INVITE messages.

Allowed values
:1-10 (decimal)
Default value: 7

SIP_NON_INVITE_RETR
(052:0004)

Number of retransmissions for non- Allowed values:

INVITE messages.
1-11 (decimal)
Default value: 11

SIP_TIMER_T1
(052:0001)

Initial value of retransmission timer. Allowed values :

500-4000 ms
(decimal)
Default value:
500 ms

SIP_TIMER_T2
(052:0002)

T2 timer for the retransmission of

requests other than INVITE.

Allowed values :
4000-12000 ms
(decimal)
Default value:
4000 ms

Table 8

10.3.1

PRFILE parameters used to configure SIP and SIP-I

Configuring SIP-I interface

Before you start
Complete the following tasks before configuring SIP-I interface.
1. Integrate IP/DNS configuration.

90

Id:0900d8058076789b

MSC Server Integration

Configuring signaling between MSC Servers

2. Create the UPDs.

Each different transport type requires independent UPDs.
3. Attach the MGWs to the UPDs.
Each UPD can have more than one MGW.
Steps
1

Create SIP-I circuit group (RCC)

ZRCC:TYPE=<circuit group type>,NCGR=<name of circuit
group>,CGR=<number of circuit group>:LSI=<line signalling>,
ASI=<auxiliary signalling>,FQDN=<fully qualified domain
name>:INR=<incoming register signalling>,TREE=<analysis
tree>,NCCP=<name of call control parameter set>;
Example
ZRCC:TYPE=SIP,NCGR=MSS2SIPT,CGR=3000:LSI=DISU4,ASI=SPO123,FQ
DN=MSC2.OP ERATOR.COM:INR=IMCKL,TREE=100,NCCP=SIP02:;

Configure remote port based on outgoing circuit group.

A different remote port can be defined for every outgoing trunk circuit group with the
help of MML configurable route level SIP parameters. For more information, see
Section MML configurable route level SIP parameters in Feature 1671: NVS Call
Handling (Standalone and Application Server Mode), Feature Activation Manuals.
1. Create parameter set for the FQDN of the outgoing CGR if it has not been
created yet:
ZJNC:FQDN="<fqdn of the outgoing CGR>::;
ZJNC:FQDN="private.mss2.operator.com"::;
2. Set the remote port parameter:
ZJNM:FQDN="<fqdn of the outgoing CGR>":PORT=<remote port>;
Example:
ZJNM:FQDN="private.mss2.operator.com":PORT=5070;

Configure route level SIP parameters

1. Add host name to FQDN.
With this MML, an FQDN can be attached as host to the FQDN of an existing
CGR. In practice, the assigned host uses the same CGR as the FQDN configured in the CGR.
ZJNA:FQDN="<FQDN configured in an CGR>":HOST="<FQDN/IP
address assigned to the same CGR>";
Example:
ZJNA:FQDN=public.mssl.operator.com:HOST=public.group0.mssl.operator.com;
2. Create and copy the parameter set.
With this MML, a parameter set can be created (or copied and already existing
one) for every FQDN that is configured in an existing CGR. Hosts assigned to
this FQDN use the same parameter set.
ZJNC:FQDN="<Destination FQDN>":FQDNSRC="<SourceFQDN>";
Example:
ZJNC:FQDN="mssl.operator.com";

Configure SIP version name in MIME

Id:0900d8058076789b

91

Configuring signaling between MSC Servers

MSC Server Integration

A string that contains not more than eight characters (note that string is not null terminated) can be configured with the JNM MML command, such as the ISUP name.
Example:
ZJNM:FQDN="APOLLONSIPIN.ZSC.COM"::ISUPVR="itu-t92+";
5

Configure Number format for non + (INT) numbers

The FQDN (route) level configuration allows to define the type of the number that
should be set if the type of the received number is not known (because it is not international, that is, starting with '+').
The parameter sets the right format that is used towards the call control. The
mapping of numbers from call control towards SIP is not influenced.
Example:
ZJNM:FQDN="APOLLONSIPOUT.ZSC.COM"::NUMFOR=UNU;

THE ORDER IS <CdPN><ACgPN><CgPN>

CdPN - Called Party Number
ACgPN - Additional Calling Party Number
CgPN - Calling Party Number
DEFAULT IS NUMFOR=UUU
IN CONFIGURED NUMBER FORMAT THE FOLLOWING NOTATION IS USED:
U: NUMBER WITHOUT + IS UNKNOWN (DEFAULT)
N: NUMBER WITHOUT + IS NATIONAL

Configure URI usage

It is possible to configure the URI format that is used in the 'From', 'To' and 'Request'
URI header fields. TEL URI is used on all interfaces by default.
IN URI USAGE THE FOLLOWING NOTATION IS USED:
D: DEFAULT (STANDARD BEHAVIOUR)
T: TEL (E.g. tel:+361234567)
S: SIP (E.g. sip:user@domain.com)
(E.g. sip:+361234567@domain.com;user=phone)
THE ORDER IS <Request URI><From><To>
TELURI=DDD

Example:
ZJNM:FQDN="APOLLONSIPIN.ZSC.COM"::TELURI=TST;
7

Create user plane analysis

1. Plan user plane analysis, that is, which establishment method, parameters are
the results of analysis towards certain peer MSSs.
2. Create user plane analysis leading to the created UPDs.
3. Define sufficient result parameters for the outgoing and incoming call cases.
For instructions, see Creating user plane analysis configuration.

Create route and attach it to the routing hierarchy (RRC, RRM)

ZRRC:EXT:ROU=<route number>,OUTR=<outgoing register signalling>,STP=<starting point for outgoing signalling>,NCGR=<name
of circuit group>,NCCP=<name of call control parameter set:;
Example

92

Id:0900d8058076789b

MSC Server Integration

Configuring signaling between MSC Servers

ZRRC:EXT:ROU=301,OUTR=OMIK2,STP=2,NCGR=MSS2SIPT,NCCP=BASICOUTPSTNPBX:;
9

Set neighbour node functionality (RCM)

When SIP for telephony signaling is used, the neighbour node functionality is set to
'MSS' to indicate that the peer network element is actually another MSS. Use the
RCM command.

10 Modify the circuit-group-level data (RCM)

The circuit-level data has to be modified so that the UPDR is also attached correctly
to the circuit group.
ZRCM:NCGR=MSS2SIPT:UPDR=10;

g An appropriate UP analysis has to be created which uses this UPDR value as

one attribute.
11 Set UPDR to route (RRM)
The UPRD is set to the route in order to attach the user plane resources, that is, all
UPDs dedicated to IP version 4 or version 6 connectivity towards the MGWs of
another MSS.
ZRRM:ROU=<route number>,NEF=<network element functionality>,UPDR=<UPD reference>:;
Example
Attach UPDs with IP version 4 capability to a route.
ZRRM:ROU=301,NEF=MSS,UPDR=120:;
12 Create analysis and charging
Create call control analysis and charging for traffic of SIP-I connection.
For instructions, see Routing and Analyses, Operating Instructions.

10.3.2

Configuring SIP interface

Before you start
Complete the following tasks before SIP interface configuration.
1. Integrate IP/DNS configuration.
2. Create UPDs.
Each different transport type requires independent UPDs.
3. Attach MGWs to UPDs.
Each UPD can have more than one MGW.
Steps
1

Create SIP circuit group (RCC)

ZRCC:TYPE=<circuit group type>,NCGR=<name of circuit
group>,CGR=<number of circuit group>:LSI=<line signalling>,ASI=<auxiliary signalling>,FQDN=<fully qualified domain
name>:INR=<incoming register signalling>,TREE=<analysis
tree>,NCCP=<name of call control parameter set>;
Example

Id:0900d8058076789b

93

Configuring signaling between MSC Servers

MSC Server Integration

ZRCC:TYPE=SIP,NCGR=IMS1SIP,CGR=3001:LSI=DISU6,ASI=SPO120,FQD
N=CSCF1.OPE RATOR.COM:INR=IMCKL,TREE=200,NCCP=SIP01;
2

Create user plane analysis

1. Plan user plane analysis, that is, which establishment method, parameters are
the results of analysis towards certain peer MSSs.
2. Create user plane analysis leading to the created UPDs.
3. Define sufficient result parameters for the outgoing and incoming call cases.
For instructions, see Section Creating user plane analysis.

Create route and attach it to the routing hierarchy (RRC, RRM)

ZRRC:EXT:ROU=<route number>,OUTR=<outgoing register signalling>,STP=<starting point for outgoing signalling>,NCGR=<name
of circuit group>,NCCP=<name of call control parameter set:;
Example
ZRRC:EXT:ROU=888,OUTR=OMIK2,STP=2,NCGR=BICCL1,NCCP=SSAP:;

Set neighbour node functionality (RCM)

When SIP is used the neighbour node functionality is set to 'CSCF' to indicate that
the peer network element is the CSCF of IM subsystem. Use the RCM command.

Set UPDR to route (RRM)

The UPDR is set to the route in order to attach the user plane resources, that is, all
UPDs dedicated to IP version 4 or version 6 connectivity towards the MGWs of
another MSS.
ZRRM:ROU=<route number>,NEF=<network element functionality>,UPDR=<UPD reference>:;
Example
Attach UPDs with IP version 4 capability to a route.
ZRRM:ROU=301,NEF=MSS,UPDR=100:;

Create analysis and charging

Create call control analysis and charging for traffic of SIP connection.
For instructions, see Routing and Analyses, Operating Instructions.

10.4

Configuring ISUP and other narrowband C7 signalings

Purpose
The signaling configuration depends on where the actual user plane resources are
physically located. If the resources are located in the MGW, follow the below steps in
order to integrate those resources to the control plane configuration of the MSS.
However, if the resources are located in the MSS, the integration steps are available in
MSC and HLR Integration, Operating Instructions.
Although you have to always use the same termination identity (for example, 102-1) in
both the MSS and the MGW which corresponds to the pulse code modulation (PCM)
number in the MGW, you can still configure the circuit groups having the same termination identifier. This is possible because it is not the termination identifier alone that iden-

94

Id:0900d8058076789b