100% found this document useful (2 votes)

291 views

SIP Advanced Exercise Solutions

Uploaded by

Abdaraof Hemmes

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (2 votes)

291 views

SIP Advanced Exercise Solutions

Uploaded by

Abdaraof Hemmes

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 74

SIP/SIP-I Advanced in MSS15

Solution to Exercises

03815-LZU1089846 Rev A
SIP/SIP-I Advanced in MSS15

DISCLAIMER

This document is a training document and contains simplifications.

Therefore, it must not be considered as a specification of the
system.

The contents of this document are subject to revision without

notice due to ongoing progress in methodology, design and
manufacturing.

Ericsson shall have no liability for any error or damage of any kind
resulting from the use of this document.

This document is not intended to replace the technical

documentation that was shipped with your system. Always refer to
that technical documentation during operation and maintenance.

This document was produced by Ericsson.

• The document is to be used for training purposes only and it is

strictly prohibited to copy, reproduce, disclose or distribute it in
any manner without the express written consent from Ericsson.

-2 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

Table of Contents

Exercise 1 SIP Protocol .................................................... 4

Part 1 – SIP Basic Knowledge .....................................................4
Part 2 – SIP Trace Analysis .........................................................9

Exercise 2 SIP-I Message analysis ................................. 19

Exercise 3 SIP/SIP-I Configuration ................................. 20

4.1 Check SIP-I route configuration.......................................... 21
4.2 Configure a SIP-I route between MSC Servers .................. 42

Exercise 4 Check Feature Data configuration ............... 64

Exercise 5 SIP parameters configuration ...................... 71

6.1 ASN........................................................................................ 71
6.2 Route Set information ......................................................... 71

03815-LZU1089846 Rev A © Ericsson AB 2015 -3 -

SIP/SIP-I Advanced in MSS15

Exercise 1 SIP Protocol

PART 1 – SIP BASIC KNOWLEDGE

1. What is SIP used for?

SIP stands for Session Initiation Protocol and it’s used as a

signaling protocol that controls initiation, maintenance and
termination of interactive multimedia sessions.

2. What is the RFC that defines SIP?

SIP is defined in RFC 3261 of the Internet Engineering Task

Force (IETF).

3. What are some of the SIP functionalities?

Session Setup – establishment of a session to the parties

Session Handling – modification and termination of an active

session

User location – capability to find out the location of the user

User capabilities – determination of the media capabilities of

the devices

User availability – determination of willingness to engage in

the session

4. What are the SIP Network Elements?

User Agent (UA) – logical function that initiates or responds

to SIP transactions.

User Agent Client (UAC) – logical function that initiates SIP

requests and accepts SIP responses.

User Agent Server (UAS) – logical function that accepts SIP

requests and sends back SIP responses.

Proxy – intermediate entity responsible for forwarding SIP

requests to the target UAS or another proxy on behalf of the
UAC. It also forwards SIP responses from the UAS to the
UAC.

-4 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

Redirect Server – UAS that generates 300 class SIP

responses to requests it receives

Registrar Server – UAS that accepts SIP REGISTER requests

and updates the information from the request message into a
location database.

Back-to-Back User Agent (B2BUA) – intermediate entity that

processes incoming SIP requests as a UAS. To answer the
incoming request, the B2BUA acts as a UAC, generates a SIP
request, and sends it on the network.

5. What is a SIP URI? And what is it format?

URI stands for Uniform Resource Identifiers and it’s used and
a SIP address that identifies a user or a resource within the
SIP domain. The SIP URI could be in two formats:

Sip:user@domain:port

Sip:user@host:port

The user field could be a name or a telephone number, for

example, it could be “sip:Daniel@ericsson.com” or
“sip:1239084000@ericsson.com”. The port is an optional
field. The default port number for a SIP URI is 5060.

The public SIP address of a user is referred as Address-of-

Record (AOR). An AOR is a SIP URI that is globally routable.

6. What are the types of SIP messages?

There are SIP Requests and SIP Responses. SIP Requests are
messages sent from client to server to invoke a SIP operation.
Some examples are:

INVITE – invitation to participate in a session or modify

characteristics of a previously established session

ACK – request confirmation that the UAC has received the

response to an INVITE request

OPTIONS – query a UAS about its capabilities

BYE – request the termination of a previously established

session

CANCEL – cancel an in-progress request, such as INVITE

REGISTER – register the current location information with SIP

servers

03815-LZU1089846 Rev A © Ericsson AB 2015 -5 -

SIP/SIP-I Advanced in MSS15

SIP Responses are messages sent from server to client to

indicate the status of a SIP Request sent previously. Some
examples are:

Informational response – 1xx (provide some information to

the server while the recipient still processes the request).

Final response – 2xx, 3xx, 4xx, 5xx and 6xx (final status of a
SIP Request). A 2xx class indicates successful processing of
the SIP Request. A 3xx class indicates that the SIP request
needs to be redirected to another UAS for processing. A 4xx,
5xx or 6xx class indicates failure in processing the SIP
Request.

7. What is the structure of a SIP message?

A start-line, header fields, an empty-line, an optional message

body.

A start-line can be a Request-line (Request messages) or a

Status-line (Response messages). The Request-line specifies
a reason-phrase, the SIP address, and the SIP version. The
Status-line specifies the SIP version, the SIP status-code, and
an optional reason-phrase.

Some of the header fields could be:

Via – indicates the path where the response needs to be sent

From – URI of the sender

To – URI of the recipient

Call-ID – identifies a series of SIP messages (must be

identical for all SIP requests and responses within a dialog)

CSeq – Command Sequence is an integer value used by the

sender to match requests and responses

Content-Type – indicates the type of message body

Content-Length – indicates the size of the message body (in

bytes)

Contact – identifies a SIP URI (used during SIP registration)

The empty-line indicates the end of header fields.

-6 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

8. IP phone A wants to communicate with IP phone B. Describe a

SIP Set up and Tear down process involving a SIP Proxy.

IP phone A SIP Proxy IP phone B

1 INVITE
2 100 TRYING
3 INVITE
100 TRYING 4
180 RINGING 5
180 RINGING 6
200 OK 7
200 OK 8
9 ACK

CONVERSATION 10 RTP/UDP

BYE 11
12 200 OK

1) A sends an INVITE Request to the Proxy. The Request

contains a unique CALL-ID, A UA address (in the
Contact field), A URI (in the From field) and B URI (in the
To field).

2) The Proxy accepts the INVITE Request and sends a 100

Trying Response to A.

3) Using B URI, the Proxy looks up B UA address in the

Location Server Database and forwards the INVITE
Request to B.

4) B accepts the INVITE Request and sends a 100 Trying

Response to the Proxy.

5) B UA sends a 180 Ringing Response to the Proxy

indicating that his phone is ringing.

6) The Proxy forwards the 180 Ringing Response to A UA.

A UA starts playing a ringback tone.

7) B answers the call. B UA sends a 200 OK Response to

the Proxy. The Contact header specifies B UA address.

8) The Proxy forwards the 200 OK Response to A.

9) A UA acknowledges the 200 OK Response and sends an

ACK directly to B UA.

03815-LZU1089846 Rev A © Ericsson AB 2015 -7 -

SIP/SIP-I Advanced in MSS15

10) A and B start the conversation. Packets are sent over

RTP/UDP.

11) B disconnects the call. B UA sends a BYE Request to A

UA.

12) A acknowledges the BYE Request by sending a 200 OK

Response to B UA.

13) End of call.

-8 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

PART 2 – SIP TRACE ANALYSIS

Analyze the trace below and answer the questions.

1. What is the format of a SIP message?

A start line (Request-Line), a message header and a message body.

2. What kind of SIP request is that? What is the purpose of the

request?

This is an INVITE request. The purpose of the request is to invite a user

to participate in a multimedia session. Look at method field (Method:
INVITE).

3. What information you have available on the start-line?

A reason-phrase (INVITE), a SIP address (sip:211106520@213.58.159.3)

and the SIP version (SIP/2.0).

03815-LZU1089846 Rev A © Ericsson AB 2015 -9 -

SIP/SIP-I Advanced in MSS15

4. Who is this request intended to?

sip:211106520@1.193.21.73. The To field indicates to whom the request

was sent.

5. Who sent the request?

sip:unavailable@213.58.143.21. The From field indicates the originator

of the request.

6. What is the Contact field used for?

The Contact field is used as a direct route to contact the sender. It’s
usually composed by a username and a fully qualified domain name
(FQDN), but it could also contains an IP address for systems that do
not use Domain Name Systems, such as DNS.

7. What is the function of the Max-Forwards parameter?

It’s used for limiting the number of hops a request can make on the
way to its destination.

8. What information can you use to uniquely identify the call?

The call-ID field. The call-ID is generated by a combination of a random

string and the domain or IP address of the sender. In this case,
91ks2p2bw8pkpgn2@213.58.143.21

9. What information can you use to order transactions within a

dialog between SIP nodes?

The Command Sequence field (CSeq). In this case, 318 INVITE. The
CSeq number is incremented for each new request within a dialog.

10. What is the difference between Via field and Contact field?

The first one (Via) defines the address at which the sender expects to
receive responses to its requests. The second one (Contact) defines
the direct address the sender could receive new requests.

11. What information do the fields Content-type and Content-

length carry?

The content-type field carries information about the media type present
in the message body. In this case, the message body holds SDP
information about an application (application/sdp). The content-length
indicates the length of the message body in bytes (238).

- 10 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

1. What kind of SIP response is that? What is the purpose of the

response?

This is an informational response. The purpose of this message is to

provide some information to the sender while the recipient still
processes the request. Look at start-line (SIP/2.0 100 Trying).

2. What information you have available on the start-line?

The SIP version (SIP/2.0), a status-code (100), and a reason-phrase

(Trying)

3. What fields are copied from the INVITE request?

The Via, From, To, and CSeq header fields.

4. Is there a Message Body?

No. The Content-Length field contains value “0”.

03815-LZU1089846 Rev A © Ericsson AB 2015 - 11 -

SIP/SIP-I Advanced in MSS15

1. What kind of SIP response is that? What is the purpose of the

response?

This is an informational response. The purpose of this message is to

provide some information to the sender while the recipient still
processes the request. Look at start-line (SIP/2.0 180 Ringing).

2. What information you have available on the start-line?

The SIP version (SIP/2.0), a status-code (180), and a reason-phrase

(Ringing).

3. Is there a Message Body?

No. The Content-Length field contains value “0”.

4. What new parameter is added in the To field?

The SIP tag parameter. The tag parameter contains a random string
that was added to the URI by the recipient. The tag parameter in the
From field was added by the sender in the INVITE request.

- 12 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

1. What kind of SIP response is that? What is the purpose of the

response?

This is a success response. The purpose of this message is to provide

a final response to the request. Look at start-line (SIP/2.0 200 OK).

2. What information you have available on the start-line?

The SIP version (SIP/2.0), a status-code (200), and a reason-phrase

(OK).

3. Is there a Message body?

Yes. The content-type field informs that the message body carries SDP
information (application/sdp). The content-length indicates that the
message body is 185-byte long.

03815-LZU1089846 Rev A © Ericsson AB 2015 - 13 -

SIP/SIP-I Advanced in MSS15

Below the Message Body of the 200OK message is expanded, so you can
answer the following questions.

1. What kind of information you can find on the message body?

The message body contains SDP information describing the type of

media for a session the recipient was invited. The Session Description
Protocol will provide information such as IP address, port, codecs, etc.

2. What SDP attributes can you see on this message? Identify if

they are mandatory or optional.

Mandatory types: SDP Version (v), Owner/creator and session identifier

(o), Session name (s), and Time description (t).

Optinal types: Media name and transport address (m) and Media
attributes (a).

3. What is SDP version used?

0. Check on SDP Version(v) attribute. Currently that is the only version

available.

- 14 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

4. What is the session ID?

4819. Check on Owner/creator and session identifier attribute, under

session ID field.

5. What is the IP address that the media should be received?

213.58.159.21. Check on Owner/creator and Session identifier, under

field “connection address”

6. What is the session name?

“-“ (dash). That’s the default value and must not be left empty.

7. What information does the time description provide?

The time description provide the start and stop time of the session. At
setup those times are unknown, so they carry the “0” value.

8. What type of media will be exchanged? What could be other

values for media type?

Audio. Check on the Media name and transport address attribute (m),
under media type parameter. Other types of media available are: video,
application, data and control.

9. What RTP port will be used for the media session?

21826. Check on the Media name and transport address attribute (m),
under media port parameter.

10. What is the protocol used for media exchange?

RTP/AVP. This is the protocol used for voice calls.

11. What are the payload formats that can be used for the
session?

ITU G.729 represented by the media format number 18 and telephone

event represented by the media format number 98.

12. When is it necessary to specify a rtpmap?

There are static and dynamic payload types. A dynamic payload types,
such as audio, must be complemented with an rtpmap attribute line.
The additional information provided is the encoding name (G.729) and
the clock rate (8000).

03815-LZU1089846 Rev A © Ericsson AB 2015 - 15 -

SIP/SIP-I Advanced in MSS15

1. What kind of SIP request is that? What is the purpose of the

request?

This is an ACK request. The purpose of the request is to confirm the

reception of the final response (200 OK). Look at method field (Method:
ACK).

2. What information you have available on the start-line?

A reason-phrase (ACK), a SIP address (sip: 213.58.159.3:5060) and the

SIP version (SIP/2.0).

3. What messages make the three-way handshake used to

establish SIP sessions?

INVITE, 200OK and ACK.

- 16 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

1. What kind of SIP request is that? What is the purpose of the

request?

This is a BYE request. The purpose of the request is to terminate the

call after completion of media exchange. Look at method field (Method:
BYE).

2. What information you have available on the start-line?

A reason-phrase (BYE), a SIP address (sip:unavailable@213.58.143.21)

and the SIP version (SIP/2.0).

03815-LZU1089846 Rev A © Ericsson AB 2015 - 17 -

SIP/SIP-I Advanced in MSS15

1. What kind of SIP response is that? What is the purpose of the

response?

This is a success response. The purpose of this message is to provide

a final response to the request. Look at start-line (SIP/2.0 200 OK).

2. What information you have available on the start-line?

The SIP version (SIP/2.0), a status-code (200), and a reason-phrase

(OK).

3. What fields are copied from the BYE request?

The To, From, Call-ID, CSeq and Via header fields.

- 18 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

Exercise 2 SIP-I Message analysis

Study the protocol analyzer printout on the following pages and try to find the
answer to the following questions:

Look at the message

1 What transport is used UDP or TCP?

UDP

2 What is the value of the Request URI?

sip:+9440000@ni2sip.ericsson.com;user=phone

3 What is the Contact address?

sip:+9450001@192.168.200.197

4 Which SIP methods are supported by the sender?

INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK,UPDATE and INFO

5 What kind of content is included in the body of the message?

SDP + encapsulated ISUP message

6 At what IP address and Port number does the sender want to receive the
media?

192.168.162.213 port 4110

7 What is the content-type of the encapsulated ISUP message?

application/isup; version=ITU-T92+; base=itu-t92+

8 What is the called party number?

9440000

03815-LZU1089846 Rev A © Ericsson AB 2015 - 19 -

SIP/SIP-I Advanced in MSS15

Exercise 3 SIP/SIP-I Configuration

SIP-I Configuration in MSC S DB and MSC-S BC
Your task is to configure SIP-I routes for a MSC-S BC and MSC-S DB.

The reference for this exercise is the User Guide for SIP and SIP with
Encapsulated ISUP, Signaling, and MSC Server. See the figure 2 in this
User Guide for the sequence of steps in the procedure.

Configuration of the MGCF in the MSC-S DB and MSC-S BC is performed in

a number of steps. The general order of definition is:

1) IP stack configuration

2) Local host data

3) Remote host data

4) Routes & Traffic data

VOICE MGG -ALLMG

MGG
MGW-ALLMG
TIM MGW CLARO

BCMSC.OPERATOR.GT DBMSC.OPERATOR.GE

- 20 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

4.1 CHECK SIP-I ROUTE CONFIGURATION

Before you start the definition check how the SIP-I is defined, both in the
MSC-S DB and MSC-S BC.

Open a log file in Winfiol before you send the printouts. You will need this
information later on.

1) IP Stack Configuration – take a note of the host IP address:

IHIFP: NVIF=BC-SIP; - MSC-S BC

VIRTUAL ETHERNET INTERFACE DATA

NVIF
BC-SIP
VID DID STATE MTU STACK
2676 8742 UP 1436 TIPSPU
NETMASK ARP BASEIP RANGE
255.0.0.0 NO - -
255.0.0.0 NO - -
END

IHIFP:NVIF=BC-SIP,ALL; - MSC-S BC

<ihifp:nvif=bc-sip,all;
VIRTUAL ETHERNET INTERFACE DATA

NVIF
BC-SIP

VID DID STATE MTU HWADDRESS

STACK
2676 8742 UP 1436 66-55-44-33-22-11
TIPSPU

IP NETMASK ARP BASEIP

RANGE
3.3.3.68 255.0.0.0 NO -
-
3.3.3.71 255.0.0.0 NO -
-

END

IHIFP:VIF=ETHA-150; - MSC-S DB
VIRTUAL ETHERNET INTERFACE DATA
VIF DID STATE MTU HWADDRESS
ETHA-150 8738 UP 1436 66-55-44-33-22-11
IP NETMASK ARP

03815-LZU1089846 Rev A © Ericsson AB 2015 - 21 -

SIP/SIP-I Advanced in MSS15

2.2.2.22 255.0.0.0 YES

END

2) Take a note of all SIP and SIP-I related interface routes including default
interface routes.

IHRHP;

3) Check the base local host name:

IBLNP; -- MSC-S BC

<IBLNP;
SIP SIGNALLING LOCAL HOST NAME
NAME
BCMSC.OPERATOR.GT
NETID
OPERATOR.GT
END

IBLNP; -- MSC-S DB

<IBLNP;
SIP SIGNALLING LOCAL HOST NAME

NAME
DBMSC.OPERATOR.GE

NETID
OPERATOR.GE

END

IBLSP:SID=ALL; -- MSC-S BC

<IBLSP:SID=ALL;
SIP SIGNALLING LOCAL HOST SOCKETS DATA

SID IPADD LPN SIDSTATE PTI

UDP-0 3.3.3.68 5060 OPEN
UDP-1 3.3.3.71 5060 OPEN
TCP-0 3.3.3.68 5060 LISTEN
TCP-1 3.3.3.71 5060 LISTEN

END

IBLSP:SID=ALL; -- MSC-S DB

<IBLSP:SID=ALL;

- 22 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

SIP SIGNALLING LOCAL HOST SOCKETS DATA

SID IPADD LPN SIDSTATE PTI

UDP-0 2.2.2.22 5060 OPEN
TCP-0 2.2.2.22 5060 LISTEN

END

4) Check the remote hosts.

If there is an IP address defined, explain what that means?

ANSWER: The IP address means that MSC uses Static IP instead of

Dynamic IP by using DNS.

IBHOP:HOST=ALL; -- MSC-S BC

<IBHOP:HOST=ALL;
SIP SIGNALLING REMOTE HOST DATA
HOST IPADD TRN RPN TSBUF TRBUF

GTSTP 7.7.7.195 1 5060

NAME
DBSTP.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GEMSC 2.2.2.22 1 5060
NAME
DBMSC.OPERATOR.GE
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTATCF 3.3.3.75 1 5060
NAME
ATCF.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GEATCF 2.2.2.25 1 5060
NAME
ATCF.OPERATOR.GE
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTIMS 3.3.3.76 1 5060
NAME
IMS.OPERATOR.GT
SUPV SSTATE

03815-LZU1089846 Rev A © Ericsson AB 2015 - 23 -

SIP/SIP-I Advanced in MSS15

HOST IPADD TRN RPN TSBUF TRBUF

GEIMS 2.2.2.26 1 5060
NAME
IMS.OPERATOR.GE
SUPV SSTATE

END

IBHOP:HOST=ALL; -- MSC-S DB

SIP SIGNALLING REMOTE HOST DATA

HOST IPADD TRN RPN TSBUF TRBUF
GTSTP 7.7.7.195 1 5060
NAME
DBSTP.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTMSCA 3.3.3.68 1 5060
NAME
BCMSC.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTMSCB 3.3.3.71 1 5060
NAME
BCMSC.B.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTATCF 3.3.3.75 1 5060
NAME
ATCF.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GEATCF 2.2.2.25 1 5060
NAME
ATCF.OPERATOR.GE
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GTIMS 3.3.3.76 1 5060
NAME
IMS.OPERATOR.GT
SUPV SSTATE

HOST IPADD TRN RPN TSBUF TRBUF

GEIMS 2.2.2.26 1 5060
NAME

- 24 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

IMS.OPERATOR.GE
SUPV SSTATE

END

5) Check if Dynamic DNS is defined:

IHRGP: NSGID=ALL; (DNS can be the same for BC and DB)

<IHRGP: NSGID=ALL;

SERVER GROUP NAME: GT_DNS

NAME SERVER LIST:
NSIP SRCIP SRCTYPE
3.3.3.76 -
SUFFIX LIST:
SUFFIX
.
SERVER GROUP NAME: GT.MSC

NAME SERVER LIST:

NSIP SRCIP SRCTYPE
193.180.17.1 193.180.17.100 BASE
SUFFIX LIST:
SUFFIX
.
SERVER GROUP NAME: GT.IMS
NAME SERVER LIST:
NSIP SRCIP SRCTYPE

SUFFIX LIST:
SUFFIX
.
END

<ihrpp:nsgid=all;
DNS RESOLVER PARAMETER DATA

RESOLVER PARAMETERS:
APISTATE OTIM ACLTYPE ACL
ENABLE 2000 HIGH NOALARM
LOW NOALARM

NAME SERVER GROUP PARAMETERS:

NSGID PRIOR MAXTM MINTM REATG REATNS NDOTS
GT_DNS 3 500 200 6 2 1
GT.MSC 3 500 200 6 2 1
GT.IMS 3 500 200 6 2 1

NAME SERVER PARAMETERS:

NSGID NSIP SUPTM NSSTATE FIN

03815-LZU1089846 Rev A © Ericsson AB 2015 - 25 -

SIP/SIP-I Advanced in MSS15

GT_DNS 3.3.3.76 20 ALIVE -

GT.MSC 193.180.17.1 20 ALIVE -

END
<

6) Check the route set:

IBROP:RSI=ALL; -- MSC-S BC

<IBROP:RSI=ALL;
SIP SIGNALLING ROUTE SET INFORMATION DATA
RSI NHOP DEST IPG TRN DOMID RSINUM
GEMSC GEMSC 1 1
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GEMSC2 GTSTP GEMSC 1 2
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTSTP GTSTP 1 5
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTSTP2 GEMSC GTSTP 1 6
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTATCF GTATCF 1 51
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GEATCF GEATCF 1 52
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTIMS GTIMS 1 53
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

- 26 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

END

IBROP:RSI=ALL; -- MSC-S DB

<IBROP:RSI=ALL;

SIP SIGNALLING ROUTE SET INFORMATION DATA

RSI NHOP DEST IPG TRN DOMID RSINUM
GTMSCA GTMSCA 1 1
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE
RSI NHOP DEST IPG TRN DOMID RSINUM
GTMSCB GTMSCB 1 2
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTMSCA2 GTSTP GTMSCA 1 3
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTMSCB2 GTSTP GTMSCB 1 4
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTSTP GTSTP 1 5
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTSTP2 GTMSCA GTSTP 1 6
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GTSTP3 GTMSCB GTSTP 1 7
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GEATCF GEATCF 1 51
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

03815-LZU1089846 Rev A © Ericsson AB 2015 - 27 -

SIP/SIP-I Advanced in MSS15

GTATCF GTATCF 1 52
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

RSI NHOP DEST IPG TRN DOMID RSINUM

GEIMS GEIMS 1 53
SRC1 SRC2 TSBUF TRBUF TRNO DIR
0 BT
SUPV SSTATE

END

7) Check SIP-I Versions&Profiles

SGVPP: EIVP=ALL; (EIVP can be the same for BC and DB)

<SGVPP: EIVP=ALL;
ENCAPSULATED ISUP VERSION PROFILE DATA

EIVP EIVPSTATE BASEID BASENAME VERSIONNAME PID

1 ASSIGNED 2 ITU-T92+ ITU-T92+ 0

SCI
1
EIVP EIVPSTATE BASEID BASENAME VERSIONNAME PID
2 ASSIGNED 4 ANSI00 ANSI00 0

SCI
2
EIVP EIVPSTATE BASEID BASENAME VERSIONNAME PID
3 ASSIGNED 6 ETSI356 ETSI356 0

SCI
3
END

8) Check what is the SIP version implemented:

SGTCP: SCI=ALL; -- MSC-S BC

<SGTCP: SCI=ALL;
SIP TRUNK CONFIGURATION INFORMATION DATA

SCI ADMSTATE SIPTYPE SIPIMPL EIVP

1 CONFIGURED SIPI SIPI-ITUT-C 1

ROUTE RTEADMSTATE RTEGLSTATE RTEBLSTATE

SI_DB_O ACTIVATED WORKING
SISTP2O ACTIVATED WORKING

SCI ADMSTATE SIPTYPE SIPIMPL EIVP

2 DEFINED SIPI SIPI-ANSI 2

- 28 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

ROUTE
NONE
SCI ADMSTATE SIPTYPE SIPIMPL EIVP
3 DEFINED SIPI SIPI-ITUT-C 3

ROUTE
NONE
SCI ADMSTATE SIPTYPE SIPIMPL
4 CONFIGURED SIP SIP-3GPP

ROUTE RTEADMSTATE RTEGLSTATE RTEBLSTATE

S_DB2_O ACTIVATED WORKING
S_STP_O ACTIVATED WORKING
SGTAT_O ACTIVATED WORKING
SGEAT_O ACTIVATED WORKING
SGTIM_O ACTIVATED WORKING

END

SGTCP: SCI=ALL; -- MSC-S DB

<SGTCP: SCI=ALL;

<sgtcp:sci=all;
SIP TRUNK CONFIGURATION INFORMATION DATA

SCI ADMSTATE SIPTYPE SIPIMPL EIVP

1 CONFIGURED SIPI SIPI-ITUT-C 1

ROUTE RTEADMSTATE RTEGLSTATE RTEBLSTATE

SIBCA_O ACTIVATED WORKING
SIBCB_O ACTIVATED WORKING
SISTP2O ACTIVATED WORKING
SISTP3O ACTIVATED WORKING

SCI ADMSTATE SIPTYPE SIPIMPL EIVP

2 DEFINED SIPI SIPI-ANSI 2

ROUTE
NONE
SCI ADMSTATE SIPTYPE SIPIMPL EIVP
3 DEFINED SIPI SIPI-ITUT-C 3

ROUTE
NONE
SCI ADMSTATE SIPTYPE SIPIMPL
4 CONFIGURED SIP SIP-3GPP

ROUTE RTEADMSTATE RTEGLSTATE RTEBLSTATE

SBCA2_O ACTIVATED WORKING
SBCB2_O ACTIVATED WORKING
S_STP_O ACTIVATED WORKING
SGEAT_O ACTIVATED WORKING
SGTAT_O ACTIVATED WORKING

SCI ADMSTATE SIPTYPE SIPIMPL

03815-LZU1089846 Rev A © Ericsson AB 2015 - 29 -

SIP/SIP-I Advanced in MSS15

5 DEFINED SIP SIP-3GPP

ROUTE
NONE
END

9) Check the SIP routes:

EXROP: DETY=SIPCO; -- MSC-S BC

<EXROP: DETY=SIPCO;

ROUTE DATA
R ROUTE PARAMETERS
M_SIP_O DETY=SIPCO TTRANS=1 FNC=7
M_SIP_I DETY=SIPCO PRI=10 FNC=7
SI_DB_O DETY=SIPCO TTRANS=1 FNC=3
R=SI_DB_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=1
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SI_DB_I DETY=SIPCO PRI=10 FNC=3
R=SI_DB_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=1 PREFURI=1
MGG=ALLMG
S_DB2_O DETY=SIPCO TTRANS=1 FNC=3
R=S_DB2_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=2 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
S_DB2_I DETY=SIPCO PRI=10 FNC=3
R=S_DB2_O
R2=M_SIP_I
MIS2=1 BO=255

- 30 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=2
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
S_STP_O DETY=SIPCO TTRANS=1 FNC=3
R=S_STP_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=5 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
S_STP_I DETY=SIPCO PRI=10 FNC=3
R=S_STP_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=5
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SISTP2O DETY=SIPCO TTRANS=1 FNC=3
R=SISTP2I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=6
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SISTP2I DETY=SIPCO PRI=10 FNC=3
R=SISTP2O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=6 PREFURI=1
MGG=ALLMG
SGTAT_O DETY=SIPCO TTRANS=1 FNC=3
R=SGTAT_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

03815-LZU1089846 Rev A © Ericsson AB 2015 - 31 -

SIP/SIP-I Advanced in MSS15

URITYPE=1 BCIND=6 NF=1

SCI=4 RSIID=51 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SGTAT_I DETY=SIPCO PRI=10 FNC=3
R=SGTAT_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=51
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SGTIM_O DETY=SIPCO TTRANS=1 FNC=3
R=SGTIM_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=53 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SGTIM_I DETY=SIPCO PRI=10 FNC=3
R=SGTIM_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=53
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SGEAT_O DETY=SIPCO TTRANS=1 FNC=3
R=SGEAT_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=52 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SGEAT_I DETY=SIPCO PRI=10 FNC=3
R=SGEAT_O
R2=M_SIP_I
MIS2=1 BO=255

- 32 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=52
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG

END

Answer: MSC-S BC

The MAIN route name is:__ M_SIP_O & M_SIP_I__ <= FNC=7

The Traffic route name is: __ S_DB_O & S_DB_I__ <= FNC=3

The RSI attached to this route is: _1_____ <= RSIID=1

The SCI attached to this route is: _1________ <= SCI=1

EXROP: DETY=SIPCO; -- MSC-S DB

R ROUTE PARAMETERS
M_SIP_O DETY=SIPCO TTRANS=1 FNC=7
M_SIP_I DETY=SIPCO PRI=10 FNC=7
SIBCA_O DETY=SIPCO TTRANS=1 FNC=3
R=SIBCA_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=1
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SIBCA_I DETY=SIPCO PRI=10 FNC=3
R=SIBCA_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=1 PREFURI=1
MGG=ALLMG
SIBCB_O DETY=SIPCO TTRANS=1 FNC=3
R=SIBCB_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=2
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SIBCB_I DETY=SIPCO PRI=10 FNC=3

03815-LZU1089846 Rev A © Ericsson AB 2015 - 33 -

SIP/SIP-I Advanced in MSS15

R=SIBCB_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=2 PREFURI=1
MGG=ALLMG
SBCA2_O DETY=SIPCO TTRANS=1 FNC=3
R=SBCA2_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=3 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SBCA2_I DETY=SIPCO PRI=10 FNC=3
R=SBCA2_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=3
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SBCB2_O DETY=SIPCO TTRANS=1 FNC=3
R=SBCB2_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=4 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SBCB2_I DETY=SIPCO PRI=10 FNC=3
R=SBCB2_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=4
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
S_STP_O DETY=SIPCO TTRANS=1 FNC=3
R=S_STP_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1

- 34 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

SCI=4 RSIID=5 PROPDLS=1

PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
S_STP_I DETY=SIPCO PRI=10 FNC=3
R=S_STP_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=5
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SISTP2O DETY=SIPCO TTRANS=1 FNC=3
R=SISTP2I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=6
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SISTP2I DETY=SIPCO PRI=10 FNC=3
R=SISTP2O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=6 PREFURI=1
MGG=ALLMG
SISTP3O DETY=SIPCO TTRANS=1 FNC=3
R=SISTP3I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 G729ABO=1 RSIID=7
PROPDLS=1 PREFURI=1 T38REIN=0
MGG=ALLMG
SISTP3I DETY=SIPCO PRI=10 FNC=3
R=SISTP3O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

HRTCP=2 URITYPE=1 NF=1
SCI=1 T38REIN=1 G729ABO=1
RSIID=7 PREFURI=1
MGG=ALLMG
SGEAT_O DETY=SIPCO TTRANS=1 FNC=3
R=SGEAT_I
R2=M_SIP_O
MIS2=1

03815-LZU1089846 Rev A © Ericsson AB 2015 - 35 -

SIP/SIP-I Advanced in MSS15

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=51 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SGEAT_I DETY=SIPCO PRI=10 FNC=3
R=SGEAT_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=51
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG
SGTAT_O DETY=SIPCO TTRANS=1 FNC=3
R=SGTAT_I
R2=M_SIP_O
MIS2=1

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 BCIND=6 NF=1
SCI=4 RSIID=52 PROPDLS=1
PREFURI=1 HRTCP=2 T38REIN=0
G729ABO=1
MGG=ALLMG
SGTAT_I DETY=SIPCO PRI=10 FNC=3
R=SGTAT_O
R2=M_SIP_I
MIS2=1 BO=255

GENERIC PARAMETERS IN ROUTE OWNER

URITYPE=1 FCIND=2 NF=1
SCI=4 G729ABO=1 RSIID=52
PREFURI=1 HRTCP=2 T38REIN=1
MGG=ALLMG

END
<

Answer: -- MSC-S DB

The MAIN route name is: M_SIP_O & M_SIPI__ <= FNC=7

10) Check if the SIP routes are unblocked:

BLORP;

No SIP routes should be blocked.

- 36 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

11) Check the following RCs and analyze them:

MSC-S BC - 1060, 200, 2001, 2002, 2003, 2004 and 2100

Answer: RC=2001 leads to SI_DB_O route towards the MSC-S DB. If

such route is blocked other alternatives are tried. The last option is a
BICC route.

<anrsp:rc=2000;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2000 YES P01=1 NRC=2001

END

<anrsp:rc=2001;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2001 YES P01=1 R=SI_DB_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2002

END

<anrsp:rc=2002;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2002 YES P01=1 NRC=2003

END

<anrsp:rc=2003;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2003 YES P01=1 R=S_STP_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2

03815-LZU1089846 Rev A © Ericsson AB 2015 - 37 -

SIP/SIP-I Advanced in MSS15

00 0
ISC FCP D
0
P01=2 NRC=2004

END

<anrsp:rc=2004;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2004 YES P01=1 R=S_STP2O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2100

END

<anrsp:rc=2005;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA

END

<anrsp:rc=2100;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2100 YES RO -10
&&-19 P01=1 R=B_210_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -20
&&-29 P02=1 R=B_220_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -30

- 38 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

&&-39 P03=1 R=B_230_O MM1 COT EST SI

ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -40
&&-49 P04=1 R=B_240_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -0
&&-9
&-50
&&-255 P05=1 R=B_200_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P05=2 NRC=2200

END
MSC-S DB - 200, 2001, 2002, 2003,
2004

MSC-S DB

MSC-S DB - 200, 2001, 2002, 2003, 2004 and 2100

Answer: RC=2001 leads to SI_BC_O route towards the MSC-S BC. If

such route is blocked other alternatives are tried. The last option is a
BICC route.

<anrsp:rc=2000;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2000 YES P01=1 NRC=2001

END

<anrsp:rc=2001;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 39 -

SIP/SIP-I Advanced in MSS15

ROUTING CASE DATA

OPERATING AREA
RC CCH BR ROUTING SP DATA
2001 YES P01=1 R=SI_BC_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2002

END

<anrsp:rc=2002;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2002 YES P01=1 R=S_BC2_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2003

END

<anrsp:rc=2003;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2003 YES P01=1 R=S_STP_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2004

END

<anrsp:rc=2004;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2004 YES P01=1 R=S_STP2O MM1 COT EST SI
ESS ESR
0 0 1
1

- 40 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P01=2 NRC=2100

END

<anrsp:rc=2100;
ROUTING CASE DATA
OPERATING AREA
RC CCH BR ROUTING SP DATA
2100 YES RO -10
&&-19 P01=1 R=B_310_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -20
&&-29 P02=1 R=B_320_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -30
&&-39 P03=1 R=B_330_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -40
&&-49 P04=1 R=B_340_O MM1 COT EST SI
ESS ESR
0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
RO -0
&&-9
&-50
&&-255 P05=1 R=B_300_O MM1 COT EST SI
ESS ESR

03815-LZU1089846 Rev A © Ericsson AB 2015 - 41 -

SIP/SIP-I Advanced in MSS15

0 0 1
1
BNT RN SPR
OLI OLI2
00 0
ISC FCP D
0
P05=2 NRC=2200

END

4.2 CONFIGURE A SIP-I ROUTE BETWEEN MSC SERVERS

Pre-requisite-
MSC-S BC

1. Print the LOAD BALANCER CONTROLLER DATA using the command

LBIDP;

<LBIDP;
LOAD BALANCER CONTROLLER DATA

BASEIP KAI KAM CUPS CUPL SKSTATE ILB

192.168.1.103 1000 3 1000 15000 OPEN 2

END

If the BASEIP parameter is obtained in the printout LOAD BALANCER

CONTROLLER DATA then print the IP addresses configured on the named
virtual interface INT-SIG using command IHIFP.

IHIFP:NVIF=INT-SIG;

<IHIFP:NVIF=INT-SIG;
VIRTUAL ETHERNET INTERFACE DATA
NVIF
INT-SIG

VID DID STATE MTU STACK

1001 8740 UP 1500 TIPSPU

NETMASK ARP BASEIP RANGE

255.255.255.0 YES 192.168.1.103 28
END

- 42 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

If the BASEIP parameter is not obtained in the printout LOAD BALANCER

CONTROLLER DATA or the same BASEIP is not obtained in the printout
VIRTUAL ETHERNET INTERFACE DATA this means that the internal
signaling subnet INT-DCP must be configured with LBIDC command.

CONFIGURE A SIP-I ROUTE INSIDE MSC-S BC

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@
@@@@ CREATE SIP DT (The steps below are from OPI)
@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@ Step 1 - SKIP - IHIFI IS ALREADY DEFINED on SEA - SKIP
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IHIFP:NVIF=BC-SIP;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 2 - Define SIP DT for BC - Own side
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Define Name to show up in Wireshark !

exit;
mml -cp allbc
IBLNC:NAME1="BCMSC.OPERATOR.GT", NETID1="OPERATOR.GT";
exit;
mml
IBLNP; ! here shows only 1 name ...A... - this is a bug !

! Define the Sockets to use for SIP in BC !

IBLSI: SID=TCP-0, IPADD="3.3.3.68", LPN=5060;
IBLSI: SID=UDP-0, IPADD="3.3.3.68", LPN=5060;
IBLSP: SID=ALL;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 3 - Define SIP DT for DB - Other side
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Define Name to show up in Wireshark !

IBHOI: HOST=GTSTP, NAME1="DBSTP.OPERATOR.GT", TRN=1, RPN=5060;
IBHOI: HOST=GEMSC, NAME1="DBMSC.OPERATOR.GE", TRN=1, RPN=5060;

IBHOI: HOST=GTATCF, NAME1="ATCF.OPERATOR.GT", TRN=1, RPN=5060;

IBHOI: HOST=GEATCF, NAME1="ATCF.OPERATOR.GE", TRN=1, RPN=5060;

IBHOI: HOST=GTIMS, NAME1="IMS.OPERATOR.GT", TRN=1, RPN=5060;

IBHOI: HOST=GEIMS, NAME1="IMS.OPERATOR.GE", TRN=1, RPN=5060;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 43 -

SIP/SIP-I Advanced in MSS15

IBHOP: HOST=ALL;

! Create Dynamic DNS !

IHRGI: NSGID=GT_DNS;
IHRGC: NSGID=GT_DNS, NSIP=3.3.3.76; ! IP to real DNS !
IHRGP: NSGID=ALL;

! Create Static DNS !

IBHAI: HOST=GTSTP,IPADD="7.7.7.195";
IBHAI: HOST=GEMSC,IPADD="2.2.2.22";

IBHAI: HOST=GTATCF,IPADD="3.3.3.75";
IBHAI: HOST=GEATCF,IPADD="2.2.2.25";

IBHAI: HOST=GTIMS,IPADD="3.3.3.76";
IBHAI: HOST=GEIMS,IPADD="2.2.2.26";

IBHOP: HOST=ALL;

! Create Route Set !

IBROI: RSI=GEMSC, RSINUM=1, DEST=GEMSC;
IBROI: RSI=GEMSC2, RSINUM=2, DEST=GEMSC, NHOP=GTSTP;
IBROI: RSI=GTSTP, RSINUM=3, DEST=GTSTP;
IBROI: RSI=GTSTP2, RSINUM=4, DEST=GTSTP, NHOP=GEMSC;

IBROI: RSI=GTATCF, RSINUM=51, DEST=GTATCF;

IBROI: RSI=GEATCF, RSINUM=52, DEST=GEATCF;
IBROI: RSI=GTIMS, RSINUM=53, DEST=GTIMS;
IBROI: RSI=GEIMS, RSINUM=54, DEST=GEIMS;
IBROP: RSI=ALL;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 4a - Define SIP DT - SIP Versions & Profiles
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Create SIP-I Protocol Versions !

SGVPI: EIVP=1, BASEID=2, VERNAME=ITUT92;
;
SGVPI: EIVP=2, BASEID=4, VERNAME=ANSI00;
;
SGVPI: EIVP=3, BASEID=6, VERNAME=ETSI356;
;
SGVPP: EIVP=ALL;

! Create SIP Profiles !

SGTCI: SCI=1,SIPTYPE=SIPI,EIVP=1,SIPIMPL=4;
;
SGTCI: SCI=2,SIPTYPE=SIPI,EIVP=2,SIPIMPL=5;
;
SGTCI: SCI=3,SIPTYPE=SIPI,EIVP=3,SIPIMPL=4;
;
SGTCI: SCI=4,SIPTYPE=SIP,SIPIMPL=6; ! SIP to IMS !
;
SGTCP: SCI=ALL;

- 44 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 4b - Define SIP DT - Create & Unblock sIP Routes
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Create SIP Main Route !

EXROI: R=M_SIP_O&M_SIP_I, DETY=SIPCO, FNC=7;
;
EXROP: DETY=SIPCO;

! Create SIP-I & SIP Traffic Routes - towards GE_DB !

EXROI: R=SI_DB_O&SI_DB_I, DETY=SIPCO, FNC=3; ! SIP-I directly !

;
EXROI: R=S_DB2_O&S_DB2_I, DETY=SIPCO, FNC=3; ! SIP via STP !
;
EXROP: DETY=SIPCO;

! Create SIP-I & SIP Traffic Routes - towards GT_STP !

EXROI: R=S_STP_O&S_STP_I, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROI: R=S_STP2O&S_STP2I, DETY=SIPCO, FNC=3; ! SIP-I via DB !
;
EXROP: DETY=SIPCO;

! Create SIP Traffic Routes - towards ATCF !

EXROI: R=S_GTATO&S_GTATI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROI: R=S_GEATO&S_GEATI, DETY=SIPCO, FNC=3; ! SIP directly !
;

! Create SIP Traffic Routes - towards vIMS!

EXROI: R=S_GTIMO&S_GTIMI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROI: R=S_GEIMO&S_GEIMI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROP: DETY=SIPCO;

! Add outgoing SIP Main Route !

EXRBC: R=SI_DB_O, R2=M_SIP_O;
;
EXRBC: R=S_DB2_O, R2=M_SIP_O;
;
EXRBC: R=S_STP_O, R2=M_SIP_O;
;
EXRBC: R=S_STP2O, R2=M_SIP_O;
;
EXRBC: R=S_GTATO, R2=M_SIP_O;
;
EXRBC: R=S_GEATO, R2=M_SIP_O;
;
EXRBC: R=S_GTIMO, R2=M_SIP_O;
;
EXRBC: R=S_GEIMO, R2=M_SIP_O;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 45 -

SIP/SIP-I Advanced in MSS15

;
EXROP: DETY=SIPCO;

! Add incoming SIP Main Route !

EXRBC: R=SI_DB_I, R2=M_SIP_I;
;
EXRBC: R=S_DB2_I, R2=M_SIP_I;
;
EXRBC: R=S_STP_I, R2=M_SIP_I;
;
EXRBC: R=S_STP2I, R2=M_SIP_I;
;
EXRBC: R=S_GTATI, R2=M_SIP_I;
;
EXRBC: R=S_GEATI, R2=M_SIP_I;
;
EXRBC: R=S_GTIMI, R2=M_SIP_I;
;
EXRBC: R=S_GEIMI, R2=M_SIP_I;
;
EXROP: DETY=SIPCO;

! Set NF-1, MIS2=1 - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_DB2_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP2O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTATO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEATO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTIMO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEIMO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=SI_DB_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_DB2_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP2I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTATI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEATI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTIMI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEIMI, RGPAR=NF-1, MIS2=1;
;
EXROP: DETY=SIPCO;

- 46 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

! Set G729ABO-1 - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_DB2_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP2O, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTATO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEATO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTIMO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEIMO, RGPAR=G729ABO-1;
;
EXRBC: R=SI_DB_I, RGPAR=G729ABO-1;
;
EXRBC: R=S_DB2_I, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP_I, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP2I, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTATI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEATI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTIMI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEIMI, RGPAR=G729ABO-1;
;
EXROP: DETY=SIPCO;

! Set HRTCP-2 - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_DB2_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP2O, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTATO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEATO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTIMO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEIMO, RGPAR=HRTCP-2;
;
EXRBC: R=SI_DB_I, RGPAR=HRTCP-2;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 47 -

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_DB2_I, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP_I, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP2I, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTATI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEATI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTIMI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEIMI, RGPAR=HRTCP-2;
;
EXROP: DETY=SIPCO;

! Set MGG-ALLMG - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_DB2_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP2O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTATO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEATO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTIMO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEIMO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=SI_DB_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_DB2_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP2I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTATI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEATI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTIMI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEIMI, RGSPAR=MGG-ALLMG;
;
EXROP: DETY=SIPCO;

! Set PREFURI-1 - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGPAR=PREFURI-1;
;
EXRBC: R=S_DB2_O, RGPAR=PREFURI-1;

- 48 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_STP_O, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP2O, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTATO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEATO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTIMO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEIMO, RGPAR=PREFURI-1;
;
EXRBC: R=SI_DB_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_DB2_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP2I, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTATI, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEATI, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTIMI, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEIMI, RGPAR=PREFURI-1;
;
EXROP: DETY=SIPCO;

! Set URITYPE-1 - for both outgoing and incoming !

EXRBC: R=SI_DB_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_DB2_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP2O, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTATO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEATO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTIMO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEIMO, RGPAR=URITYPE-1;
;
EXRBC: R=SI_DB_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_DB2_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP2I, RGPAR=URITYPE-1;
;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 49 -

SIP/SIP-I Advanced in MSS15

EXRBC: R=S_GTATI, RGPAR=URITYPE-1;

;
EXRBC: R=S_GEATI, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTIMI, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEIMI, RGPAR=URITYPE-1;
;
EXROP: DETY=SIPCO;

! Only for Outgoing - Specific SIP parameters !

! Set SCI - only for outgoing !

EXRBC: R=SI_DB_O, RGPAR=SCI-1; ! SIP-I !
;
EXRBC: R=S_DB2_O, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_STP_O, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_STP2O, RGPAR=SCI-1; ! SIP-I !
;
EXRBC: R=S_GTATO, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GEATO, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GTIMO, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GEIMO, RGPAR=SCI-4; ! SIP !
;
EXROP: DETY=SIPCO;

! Set DNSEF - only for outgoing !

EXRBC: R=SI_DB_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_DB2_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_STP_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_STP2O, RGPAR=DNSEF-0;
;
EXRBC: R=S_GTATO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GEATO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GTIMO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GEIMO, RGPAR=DNSEF-0;
;
EXROP:DETY=SIPCO;

! Set RSIID - only for outgoing !

EXRBC: R=SI_DB_O, RGPAR=RSIID-1;
;
EXRBC: R=S_DB2_O, RGPAR=RSIID-2;

- 50 - © Ericsson AB 2015 03815-LZU1089846 Rev A

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_STP_O, RGPAR=RSIID-3;
;
EXRBC: R=S_STP2O, RGPAR=RSIID-4;
;
EXRBC: R=S_GTATO, RGPAR=RSIID-51;
;
EXRBC: R=S_GEATO, RGPAR=RSIID-52;
;
EXRBC: R=S_GTIMO, RGPAR=RSIID-53;
;
EXRBC: R=S_GEIMO, RGPAR=RSIID-54;
;

EXROP:DETY=SIPCO;

EXRBC: R=SI_DB_I, BO=255;

;
EXRBC: R=S_DB2_I, BO=255;
;
EXRBC: R=S_STP_I, BO=255;
;
EXRBC: R=S_STP2I, BO=255;
;
EXRBC: R=S_GTATI, BO=255;
;
EXRBC: R=S_GEATI, BO=255;
;
EXRBC: R=S_GTIMI, BO=255;
;
EXRBC: R=S_GEIMI, BO=255;
;
EXROP: DETY=SIPCO;

! Unblock SIP Routes !

BLORP;
BLORE: R=M_SIP_O;
;
BLORE: R=SI_DB_O;
;
BLORE: R=S_DB2_O;
;
BLORE: R=S_STP_O;
;
BLORE: R=S_STP2O;
;
BLORE: R=S_GTATO;
;
BLORE: R=S_GEATO;
;
BLORE: R=S_GTIMO;
;
BLORE: R=S_GEIMO;
;
BLORP;

03815-LZU1089846 Rev A © Ericsson AB 2015 - 51 -

SIP/SIP-I Advanced in MSS15

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 5 - Define SIP DT - Routing Analysis
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@@ ANBSP:B=ALL,RC=1060; ! Next Routing Case = 2000 !

@@ More about B-Number analysis in course: MSS Network Config !

ANRSP:RC=2000;
ANRSI:RC=2000,P01=1, NRC=2001;
ANRAI:RC=2000;

ANRAR:RC=2001; ! It is ok, if this command fails !

ANRZI:RC=2001; ! It is ok, if this command fails !
ANRSP:RC=2001;
ANRPI:RC=2001;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=SI_DB_O;
ANRSI:P01=2, NRC=2002;
ANRPE;
ANRAI:RC=2001;
ANRSP:RC=2001;

ANRAR:RC=2002; ! It is ok, if this command fails !

ANRZI:RC=2002; ! It is ok, if this command fails !
ANRSP:RC=2002;
ANRPI:RC=2002;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_DB2_O;
ANRSI:P01=2, NRC=2003;
ANRPE;

ANRAI:RC=2005;
ANRSP:RC=2005;

ANRAR:RC=2003; ! It is ok, if this command fails !

ANRZI:RC=2003; ! It is ok, if this command fails !
ANRSP:RC=2003;
ANRPI:RC=2003;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_STP_O;
ANRSI:P01=2, NRC=2004;
ANRPE;
ANRAI:RC=2003;
ANRSP:RC=2003;

ANRAR:RC=2004; ! It is ok, if this command fails !

ANRZI:RC=2004; ! It is ok, if this command fails !
ANRSP:RC=2004;
ANRPI:RC=2004;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_STP2O;
ANRSI:P01=2, NRC=2100;
ANRPE;
ANRAI:RC=2004;
ANRSP:RC=2004;

ANRAR:RC=3504; ! It is ok, if this command fails !

ANRZI:RC=3504; ! It is ok, if this command fails !
ANRSP:RC=3504;

SIP/SIP-I Advanced in MSS15

ANRPI:RC=3504;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GEIMO; ! when vIMS !
ANRSI:P01=2, NRC=2100;
ANRPE;
ANRAI:RC=3504;
ANRSP:RC=3504;

ANRAR:RC=3503; ! It is ok, if this command fails !

ANRZI:RC=3503; ! It is ok, if this command fails !
ANRSP:RC=3503;
ANRPI:RC=3503;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GTIMO; ! when vIMS !
ANRSI:P01=2, NRC=3504;
ANRPE;
ANRAI:RC=3503;
ANRSP:RC=3503;

ANRAR:RC=3502; ! It is ok, if this command fails !

ANRZI:RC=3502; ! It is ok, if this command fails !
ANRSP:RC=3502;
ANRPI:RC=3502;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GEATO;
ANRSI:P01=2, NRC=3503;
ANRPE;
ANRAI:RC=3502;
ANRSP:RC=3502;

ANRAR:RC=3501; ! It is ok, if this command fails !

ANRZI:RC=3501; ! It is ok, if this command fails !
ANRSP:RC=3501;
ANRPI:RC=3501;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GTATO;
ANRSI:P01=2, NRC=3502;
ANRPE;
ANRAI:RC=3501;
ANRSP:RC=3501;

CONFIGURE A SIP-I ROUTE INSIDE MSC-S DB

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@
@@@@ CREATE SIP DT (The steps below are from OPI)
@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@ Step 1 - SKIP - IHIFI IS ALREADY DEFINED on SEA - SKIP
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IHIFP:VIF=ETHA-150;

SIP/SIP-I Advanced in MSS15

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 2 - Define SIP DT for DB - Own side
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Define Name to show up in Wireshark !

IBLNC:NAME1="DBMSC.OPERATOR.GE", NETID1="OPERATOR.GE";
IBLNP;

! Define the Sockets to use for SIP in BC !

IBLSI: SID=TCP-0, IPADD="2.2.2.22", LPN=5060;
IBLSI: SID=UDP-0, IPADD="2.2.2.22", LPN=5060;
IBLSP: SID=ALL;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 3 - Define SIP DT for DB - Other side
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Define Name to show up in Wireshark !

IBHOI: HOST=GTSTP, NAME1="DBSTP.OPERATOR.GT", TRN=1, RPN=5060;
IBHOI: HOST=GTMSC, NAME1="BCMSC.OPERATOR.GT", TRN=1, RPN=5060;

IBHOI: HOST=GTATCF, NAME1="ATCF.OPERATOR.GT", TRN=1, RPN=5060;

IBHOI: HOST=GEATCF, NAME1="ATCF.OPERATOR.GE", TRN=1, RPN=5060;

IBHOI: HOST=GTIMS, NAME1="IMS.OPERATOR.GT", TRN=1, RPN=5060;

IBHOI: HOST=GEIMS, NAME1="IMS.OPERATOR.GE", TRN=1, RPN=5060;

IBHOP: HOST=ALL;

! Create Dynamic DNS !

IHRGI: NSGID=GE_DNS;
IHRGC: NSGID=GE_DNS, NSIP=2.2.2.27; ! IP to real DNS from vIMS !
IHRGP: NSGID=ALL;

! Create Static DNS - No need to ask DNS !

IBHAI: HOST=GTSTP,IPADD="7.7.7.195";
IBHAI: HOST=GTMSC,IPADD="3.3.3.68";

IBHAI: HOST=GTATCF,IPADD="3.3.3.75";
IBHAI: HOST=GEATCF,IPADD="2.2.2.25";

IBHAI: HOST=GTIMS,IPADD="3.3.3.76";
IBHAI: HOST=GEIMS,IPADD="2.2.2.26";

IBHOP: HOST=ALL;

! Create Route Set !

IBROI: RSI=GTMSC, RSINUM=1, DEST=GTMSC;
;
IBROI: RSI=GTMSC2, RSINUM=2, DEST=GTMSC, NHOP=GTSTP;
;
IBROI: RSI=GTSTP, RSINUM=3, DEST=GTSTP;
;
IBROI: RSI=GTSTP2, RSINUM=4, DEST=GTSTP, NHOP=GTMSC;

SIP/SIP-I Advanced in MSS15

IBROI: RSI=GEATCF, RSINUM=51, DEST=GEATCF;

;
IBROI: RSI=GTATCF, RSINUM=52, DEST=GTATCF;
;
IBROI: RSI=GEIMS, RSINUM=53, DEST=GEIMS;
;
IBROI: RSI=GTIMS, RSINUM=54, DEST=GTIMS;
;
IBROP: RSI=ALL;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 4a - Define SIP DT - SIP Versions & Profiles
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Create SIP-I Protocol Versions !

SGVPI: EIVP=1, BASEID=2, VERNAME=ITUT92;
;
SGVPI: EIVP=2, BASEID=4, VERNAME=ANSI00;
;
SGVPI: EIVP=3, BASEID=6, VERNAME=ETSI356;
;
SGVPP: EIVP=ALL;

! Create SIP Profiles !

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 4b - Define SIP DT - Create & Unblock SIP Routes
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

! Create SIP Main Route !

EXROI: R=M_SIP_O&M_SIP_I, DETY=SIPCO, FNC=7;

EXROP: DETY=SIPCO;

! Create SIP-I & SIP Traffic Routes - towards GT_BC !

EXROI: R=SI_BC_O&SI_BC_I, DETY=SIPCO, FNC=3; ! SIP-I directly !
;
EXROI: R=S_BC2_O&S_BC2_I, DETY=SIPCO, FNC=3; ! SIP via STP !
;
EXROP: DETY=SIPCO;

! Create SIP-I & SIP Traffic Routes - towards GT_STP !

SIP/SIP-I Advanced in MSS15

EXROI: R=S_STP_O&S_STP_I, DETY=SIPCO, FNC=3; ! SIP directly !

;
EXROI: R=S_STP2O&S_STP2I, DETY=SIPCO, FNC=3; ! SIP-I/SIP via BC !
;
EXROP: DETY=SIPCO;

! Create SIP Traffic Routes - towards ATCF !

EXROI: R=S_GEATO&S_GEATI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROI: R=S_GTATO&S_GTATI, DETY=SIPCO, FNC=3; ! SIP directly !
;
! Create SIP Traffic Routes - towards vIMS !
EXROI: R=S_GEIMO&S_GEIMI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROI: R=S_GTIMO&S_GTIMI, DETY=SIPCO, FNC=3; ! SIP directly !
;
EXROP: DETY=SIPCO;

! Add outgoing SIP Main Route !

EXRBC: R=SI_BC_O, R2=M_SIP_O;
;
EXRBC: R=S_BC2_O, R2=M_SIP_O;
;
EXRBC: R=S_STP_O, R2=M_SIP_O;
;
EXRBC: R=S_STP2O, R2=M_SIP_O;
;
EXRBC: R=S_GEATO, R2=M_SIP_O;
;
EXRBC: R=S_GTATO, R2=M_SIP_O;
;
EXRBC: R=S_GEIMO, R2=M_SIP_O;
;
EXRBC: R=S_GTIMO, R2=M_SIP_O;
;
EXROP: DETY=SIPCO;

! Add incoming SIP Main Route !

EXRBC: R=SI_BC_I, R2=M_SIP_I;
;
EXRBC: R=S_BC2_I, R2=M_SIP_I;
;
EXRBC: R=S_STP_I, R2=M_SIP_I;
;
EXRBC: R=S_STP2I, R2=M_SIP_I;
;
EXRBC: R=S_GEATI, R2=M_SIP_I;
;
EXRBC: R=S_GTATI, R2=M_SIP_I;
;
EXRBC: R=S_GEIMI, R2=M_SIP_I;
;
EXRBC: R=S_GTIMI, R2=M_SIP_I;
;
EXROP: DETY=SIPCO;

SIP/SIP-I Advanced in MSS15

! Set NF-1, MIS2=1 - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_BC2_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP_O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP2O, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEATO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTATO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEIMO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTIMO, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=SI_BC_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_BC2_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP_I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_STP2I, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEATI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTATI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GEIMI, RGPAR=NF-1, MIS2=1;
;
EXRBC: R=S_GTIMI, RGPAR=NF-1, MIS2=1;
;
EXROP: DETY=SIPCO;

! Set G729ABO-1 - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_BC2_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP_O, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP2O, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEATO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTATO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEIMO, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTIMO, RGPAR=G729ABO-1;
;
EXRBC: R=SI_BC_I, RGPAR=G729ABO-1;
;
EXRBC: R=S_STP_I, RGPAR=G729ABO-1;

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_GEATI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTATI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GEIMI, RGPAR=G729ABO-1;
;
EXRBC: R=S_GTIMI, RGPAR=G729ABO-1;
;
EXROP: DETY=SIPCO;

! Set HRTCP-2 - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_BC2_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP_O, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP2O, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEATO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTATO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEIMO, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTIMO, RGPAR=HRTCP-2;
;
EXRBC: R=SI_BC_I, RGPAR=HRTCP-2;
;
EXRBC: R=S_BC2_I, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP_I, RGPAR=HRTCP-2;
;
EXRBC: R=S_STP2I, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEATI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTATI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GEIMI, RGPAR=HRTCP-2;
;
EXRBC: R=S_GTIMI, RGPAR=HRTCP-2;
;
EXROP: DETY=SIPCO;

! Set MGG-ALLMG - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_BC2_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP_O, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP2O, RGSPAR=MGG-ALLMG;

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_GEATO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTATO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEIMO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTIMO, RGSPAR=MGG-ALLMG;
;
EXRBC: R=SI_BC_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_BC2_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP_I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_STP2I, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEATI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTATI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GEIMI, RGSPAR=MGG-ALLMG;
;
EXRBC: R=S_GTIMI, RGSPAR=MGG-ALLMG;
;
EXROP: DETY=SIPCO;

! Set PREFURI-1 - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGPAR=PREFURI-1;
;
EXRBC: R=SI_BC2O, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP_O, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP2O, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEATO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTATO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEIMO, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTIMO, RGPAR=PREFURI-1;
;
EXRBC: R=SI_BC_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_BC2_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP_I, RGPAR=PREFURI-1;
;
EXRBC: R=S_STP2I, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEATI, RGPAR=PREFURI-1;
;
EXRBC: R=S_GTATI, RGPAR=PREFURI-1;
;
EXRBC: R=S_GEIMI, RGPAR=PREFURI-1;

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_GTIMI, RGPAR=PREFURI-1;
;
EXROP: DETY=SIPCO;

! Set URITYPE-1 - for both outgoing and incoming !

EXRBC: R=SI_BC_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_BC2_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP_O, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP2O, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEATO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTATO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEIMO, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTIMO, RGPAR=URITYPE-1;
;
EXRBC: R=SI_BC_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_BC2_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP_I, RGPAR=URITYPE-1;
;
EXRBC: R=S_STP2I, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEATI, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTATI, RGPAR=URITYPE-1;
;
EXRBC: R=S_GEIMI, RGPAR=URITYPE-1;
;
EXRBC: R=S_GTIMI, RGPAR=URITYPE-1;
;
EXROP: DETY=SIPCO;

! Only for Outgoing - Specific SIP parameters !

! Set SCI - only for outgoing !

EXRBC: R=SI_BC_O, RGPAR=SCI-1; ! SIP-I !
;
EXRBC: R=S_BC2_O, RGPAR=SCI-1; ! SIP-I !
;
EXRBC: R=S_STP_O, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_STP2O, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GEATO, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GTATO, RGPAR=SCI-4; ! SIP !

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_GEIMO, RGPAR=SCI-4; ! SIP !
;
EXRBC: R=S_GTIMO, RGPAR=SCI-4; ! SIP !
;
EXROP: DETY=SIPCO;

! Set DNSEF - only for outgoing !

EXRBC: R=SI_BC_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_BC2_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_STP_O, RGPAR=DNSEF-0;
;
EXRBC: R=S_STP2O, RGPAR=DNSEF-0;
;
EXRBC: R=S_GEATO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GTATO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GEIMO, RGPAR=DNSEF-0;
;
EXRBC: R=S_GTIMO, RGPAR=DNSEF-0;
;
EXROP:DETY=SIPCO;

! Set RSIID - only for outgoing !

EXRBC: R=SI_BC_O, RGPAR=RSIID-1;
;
EXRBC: R=S_BC2_O, RGPAR=RSIID-2;
;
EXRBC: R=S_STP_O, RGPAR=RSIID-3;
;
EXRBC: R=S_STP2O, RGPAR=RSIID-4;
;
EXRBC: R=S_GEATO, RGPAR=RSIID-51;
;
EXRBC: R=S_GTATO, RGPAR=RSIID-52;
;
EXRBC: R=S_GEIMO, RGPAR=RSIID-53;
;
EXRBC: R=S_GTIMO, RGPAR=RSIID-54;
;
EXROP:DETY=SIPCO;

EXRBC: R=SI_BC_I, BO=255;

;
EXRBC: R=S_STP_I, BO=255;
;
EXRBC: R=S_GEATI, BO=255;
;
EXRBC: R=S_GTATI, BO=255;
;
EXRBC: R=S_GEIMI, BO=255;

SIP/SIP-I Advanced in MSS15

;
EXRBC: R=S_GTIMI, BO=255;
;
EXROP: DETY=SIPCO;

! Unblock SIP Routes !

BLORP;
BLORE: R=M_SIP_O;
;
BLORE: R=SI_BC_O;
;
BLORE: R=S_STP_O;
;
BLORE: R=S_GEATO;
;
BLORE: R=S_GTATO;
;
BLORE: R=S_GEIMO;
;
BLORE: R=S_GTIMO;
;
BLORP;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ Step 5 - Define SIP DT - Routing Analysis
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@@ ANBSP:B=ALL,RC=1060; ! Next Routing Case = 2000 !

@@ More about B-Number analysis in course: MSS Network Config !

ANRSP:RC=2000;
ANRSI:RC=2000,P01=1, NRC=2001;
ANRAI:RC=2000;

@@ Try SIP-I Directly to BC

ANRAR:RC=2001; ! It is ok, if this command fails !
ANRZI:RC=2001; ! It is ok, if this command fails !
ANRSP:RC=2001;
ANRPI:RC=2001;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=SI_BC_O;
ANRSI:P01=2, NRC=2002;
ANRPE;
ANRAI:RC=2001;
ANRSP:RC=2001;

@@ Try SIP to BC via STP

ANRAR:RC=2002; ! It is ok, if this command fails !
ANRZI:RC=2002; ! It is ok, if this command fails !
ANRSP:RC=2002;
ANRPI:RC=2002;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_BC2_O;
ANRSI:P01=2, NRC=2003;
ANRPE;
ANRAI:RC=2002;
ANRSP:RC=2002;

SIP/SIP-I Advanced in MSS15

@@ Try SIP to STP Directly

ANRAR:RC=2003; ! It is ok, if this command fails !
ANRZI:RC=2003; ! It is ok, if this command fails !
ANRSP:RC=2003;
ANRPI:RC=2003;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_STP_O;
ANRSI:P01=2, NRC=2004;
ANRPE;
ANRAI:RC=2003;
ANRSP:RC=2003;

@@ Try SIP to STP via BC

ANRAR:RC=2004; ! It is ok, if this command fails !
ANRZI:RC=2004; ! It is ok, if this command fails !
ANRSP:RC=2004;
ANRPI:RC=2004;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_STP2O;
ANRSI:P01=2, NRC=2100;
ANRPE;
ANRAI:RC=2004;
ANRSP:RC=2004;

ANRAR:RC=3503; ! It is ok, if this command fails !

ANRZI:RC=3503; ! It is ok, if this command fails !
ANRSP:RC=3503;
ANRPI:RC=3503;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GTIMO;!
ANRSI:P01=2, NRC=2100;
ANRPE;
ANRAI:RC=3503;
ANRSP:RC=3503;

ANRAR:RC=3503; ! It is ok, if this command fails !

ANRZI:RC=3503; ! It is ok, if this command fails !
ANRSP:RC=3503;
ANRPI:RC=3503;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GEIMO;
ANRSI:P01=2, NRC=3504;
ANRPE;
ANRAI:RC=3503;
ANRSP:RC=3503;

ANRAR:RC=3502; ! It is ok, if this command fails !

ANRZI:RC=3502; ! It is ok, if this command fails !
ANRSP:RC=3502;
ANRPI:RC=3502;
ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GTATO;
ANRSI:P01=2, NRC=3503;
ANRPE;
ANRAI:RC=3502;
ANRSP:RC=3502;

ANRAR:RC=3501; ! It is ok, if this command fails !

ANRZI:RC=3501; ! It is ok, if this command fails !
ANRSP:RC=3501;
ANRPI:RC=3501;

SIP/SIP-I Advanced in MSS15

ANRSI:P01=1, SP=MM1, ESS=1, ESR=1, R=S_GEATO;

ANRSI:P01=2, NRC=3502;
ANRPE;
ANRAI:RC=3501;
ANRSP:RC=3501;

Exercise 4 Check Feature Data configuration

ASN ACCESSIBILITY SUPERVISION AND INTELLIGENT ROUTING
ASN Accessibility Supervision and Intelligent Routing consist of two
functions: ASN Accessibility Supervision function and Early Exit (EE)
function.

Let us check if those features are activated in the test plant:

1) Feature related verifications:

- To check the feature availability, print the following feature parameter, which is under
license management control:

DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=ASNINTRTF;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=ASNINTRTF;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

ASNINTRTF SIPSUPPORTF 15893 1 FEATURE IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 1 UNDEF 0

END

- The check the feature activation status for accessibility supervision, print the customer
parameter:
DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=ASNSUPACT;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=ASNSUPACT;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

SIP/SIP-I Advanced in MSS15

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

ASNSUPACT SIPSUPPORTC 15897 1 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 1 UNDEF 0

END

- The parameter globally activates the function and manages the early exit timer value:
DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=EEXITTIME;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=EEXITTIME;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

EEXITTIME SIPSUPPORTC 15896 10 SEC CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 10 UNDEF 0

END

Note: ASNEE timer AXE parameter EEXITTIME needs to be bigger than the biggest
expected call set-up time in the network.

- Print information of ASN Accessibility supervision data (observe SUPV and SSTATE)
IBHOP:HOST=ALL;

- Information if supervision on HOST is started, availability of HOST.

IBLLP;

- Print the IP address black list.

IBSDP;

- Prints ASN supervision parameters and check the SBL (route blocking state):
SGTCP:SCI=ALL;

- The following commands can be given to print route parameters for early exit timer:

EXROP:DETY=SIPCO,RGPAR=TEXIT;

EXROP:DETY=SIPCO,RGPAR=DEEX;

- The alarm SIP ROUTE UNAVAILABLE is raised when outgoing SIP traffic route
becomes unavailable due to detected inaccessibility of the ASN. Check with ALLIP.

Note: ASN is supervised with probing OPTIONS requests. Probing

mechanism depends on timers (TAC, TIN) and event counters (NAC, NIN)
that provide hysteresis mechanism for IP address/ASN state change.

SIP/SIP-I Advanced in MSS15

CALL MEDIATION NODE (CMN) FOR SIP-I

The function ’Call Mediation Node for SIP-I’ allows the operator to save
Media Gateway (MGw) resources when not needed.

- To check the feature availability, print the following feature parameter, which is under
license management control:

DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=CMNSIPIF;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=CMNSIPIF;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

CMNSIPIF SIPSUPPORTF 5726 0 FEATURE IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END

- The check the feature activation status, print the customer parameter:
DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=CMNSIPIC;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=CMNSIPIC;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

CMNSIPIC SIPSUPPORTC 16379 0 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END

SIP/SIP-I Advanced in MSS15

- The check the Session Keep Alive timer, print the customer parameter:
DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=CMNSKATIME;

<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=CMNSKATIME;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

CMNSKATIME SIPSUPPORTC 16381 15 MIN CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 15 UNDEF 0

END

- Print the route data to find all SIP-I route(s) with activated Session Keep Alive mechanism :
EXROP:DETY=SIPCO,RGPAR=CMNSKA;

HD VOICE WITH G.722

This feature enables G.722 based HD Voice connections for IMS
Interworking and IP Interconnect calls.

- To check the feature availability, print the following feature parameter for AMR-WB over
G.722:
DBTSP:TAB=AXEPARS,SETNAME=GSMMSCF,NAME=G722AVAIL;

<DBTSP:TAB=AXEPARS,SETNAME=GSMMSCF,NAME=G722AVAIL;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

G722AVAIL GSMMSCF 15881 0 FEATURE IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END

- Check Codec information:

DBTSP:TAB=AXEPARS,NAME=ACTIVATION8,SETNAME=AXEMGCFCODECC;
<DBTSP:TAB=AXEPARS,NAME=ACTIVATION8,SETNAME=AXEMGCFCODECC;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

SIP/SIP-I Advanced in MSS15

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

ACTIVATION8 AXEMGCFCODECC 15872 0 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END
DBTSP:TAB=AXEPARS,NAME=PRIORITYSIP8,SETNAME=AXEMGCFCODECC;

<DBTSP:TAB=AXEPARS,NAME=PRIORITYSIP8,SETNAME=AXEMGCFCODECC;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

PRIORITYSIP8 AXEMGCFCODECC 15873 7 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 7 UNDEF 0

END

DBTSP:TAB=AXEPARS,NAME=PRIORITYSIPI8,SETNAME=AXEMGCFCODECC;
<DBTSP:TAB=AXEPARS,NAME=PRIORITYSIPI8,SETNAME=AXEMGCFCODECC;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

PRIORITYSIPI8 AXEMGCFCODECC 15874 7 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 7 UNDEF 0

END

Note: In order to achieve HD Voice with G.722 several features are needed:
- TrFO Interworking with SIP and SIP-I
- MGCF for Interworking with IMS
- MGCF for Interworking with SIP-I based Networks
- AMR-WB Speech (in case of call to 2G or 3G access)

AMR-WB / HD VOICE
In MSS 13A AMR-WB codec was also made available over SIP/SIP-I.

SIP/SIP-I Advanced in MSS15

- To check the feature availability, print the following feature parameter for AMR-WB over
SIP/SIP-I:
DBTSP:TAB=AXEPARS,SETNAME=GSMMSCF,NAME=AMRWBAVAIL;

<DBTSP:TAB=AXEPARS,SETNAME=GSMMSCF,NAME=AMRWBAVAIL;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

AMRWBAVAIL GSMMSCF 7415 1 FEATURE IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 1 UNDEF 0

END

- To check the feature availability, print the following feature parameter for TrFO
Interworking with SIP and SIP-I, which is under license management control:

DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=E2ECODNEGAVAIL
;
<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTF,NAME=E2ECODNEGAVAIL;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

E2ECODNEGAVAIL SIPSUPPORTF 15850 1 FEATURE IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END

- The parameter controls the activation of the feature TrFO Interworking with SIP and SIP-
I:

DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=E2ECODNEGACT;
<DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=E2ECODNEGACT;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

E2ECODNEGACT SIPSUPPORTC 15878 0 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

SIP/SIP-I Advanced in MSS15

END

- The parameter indicates if precondition mechanism is supported on incoming and

outgoing SIP and SIP-I routes:
DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=PRECONDACT;

< DBTSP:TAB=AXEPARS,SETNAME=SIPSUPPORTC,NAME=PRECONDACT;
ACT MSC-S 14B BC AD-1 TIME 140713 0321 BC0

DATABASE TABLE

BLOCK TAB TABLE WRAPPED

PARA AXEPARS YES

NAME SETNAME PARID VALUE UNIT CLASS DISTRIB

PRECONDACT SIPSUPPORTC 15888 0 CUSTOM IMMED
STATUS FCVSET FCVALUE DCINFO FCODE
UPDATED FALSE 0 UNDEF 0

END

- The following commands can be given for useful SIP/SIP-I route parameter information:
EXROP:DETY=SIPCO,RGPAR=FLBL;
EXROP:DETY=SIPCO,RGPAR=PRECOND;
EXROP:DETY=SIPCO,RGPAR=IDA;
EXROP:DETY=SIPCO,RGPAR=ICP;
EXROP:DETY=SIPCO,RGPAR=WBCTP;

Note: In order to achieve AMR WB Speech over SIP (-I) several features are needed:
- TrFO Interworking with SIP and SIP-I
- AMR-WB Speech
- MGCF for Interworking with SIP-I based Networks
- MGCF for Interworking with IMS (in case of connection to IMS)

SIP/SIP-I Advanced in MSS15

Exercise 5 SIP parameters configuration

6.1 ASN
OPI: SIP and SIP with Encapsulated ISUP Signaling, MSC Server

Configure the Early Exit functionality in such way that the call establishment
attempt is abandoned if not responding in 10 seconds:

1) In node level: EEXTTIME=10

2) In route level: EXRBC: R= <route name>, RGPAR=TEXIT=10;

3) What is the parameter of IBHOP command used for printing remote

host configuration data for all defined remote hosts in the network with
activated/deactivated ASN accessibility supervision?

IBHOP: SUPV=ON;

4) Use the command IBSDC to enable modification of supervision

parameters in such way that:

OPTIONS will be sent to accessible ASN every 30 seconds, while towards

inaccessible ASN, OPTIONS will be sent every 5 seconds. ASN will be
considered accessible after three successful responses to OPTIONS are
received from previously inaccessible ASN.ASN will be considered
inaccessible after five unsuccessful responses to OPTIONS from previously
accessible ASN.

IBSDC: TAC=30,TIN=5,NAC=3,NIN=5;

6.2 ROUTE SET INFORMATION

The objective of this exercise is to identify the “routing” parameters for

the different RSI types shown in the figure.

OPI: SIP and SIP with Encapsulated ISUP Signaling, MSC Server

6.2.1 ) Following is an example for defined network remote hosts, domains and
RSIs including graphic abstraction on Figure below. The RSI discrimination is based
on the matching of the hosts indicated in the Via header of the SIP request with the
remote hosts and/or domain defined on the configured RSIs.

SIP/SIP-I Advanced in MSS15

Having that in mind try to match the corresponding DEST, SRC, NHOP and DOMID
RSI parameters for the traffic cases pointed out in the figure.

2.1) CASE 1:
One entry in Via header:
Via: SIP/2.0/UDP icscf.ims.net:5060; H1 matched (DEST)
Via: SIP/2.0/UDP bgcf.ims.net:5060;

RSI = DEST =H1 SRC1 =H2

2.2) CASE 2:

Via: SIP/2.0/UDP proxy.imsnet.com:5060;

Via: SIP/2.0/UDP icscf.imsnet.com:5060;
Via: SIP/2.0/UDP host.imsnet.com:5060;

RSI = NHOP=H6 DEST =H3 SRC1 =H4

2.3) CASE 3:
Via: SIP/2.0/TCP host.ims.net:5060;

RSI = DOMID=D1

Configuration of Hosts and Domains:

H1 "icscf.ims.net" 145.30.33.24
H2 "bgcf.ims.net" 145.30.33.23
H3 "icscf.imsnet.com" 145.20.20.21

SIP/SIP-I Advanced in MSS15

H4 "bgcf.imsnet.com" 145.20.20.22
H5 "tss40.st.ericsson.net"
H6 "proxy.imsnet.com" 145.20.20.10
H7 "sbg100.cncore.com"
H8 "sbg200.cncore.com"
D1 "ims.net"
D2 "imsnet.com"
D3 "zg.ericsson.net"

6.2.2 ) One artificial network example is shown on figure below where the
network topology with both Remote Hosts and Domains is applied.

What are the RSI objects and relations that should be configured for each
case?

RSI NHOP DEST DOMID SRC

RSI1 - H03 - H04
RSI2 H01 H05 - -
RSI3 H02 H05 - -
RSI4 - - D01 -
RSI5 H01 - D02 -
RSI6 H02 - D02 -

Local Host = ‘‘mscs.ericsson.hr’’

remote Host H01 = ‘‘sbg1.ericsson.hr’’
remote Host H02 = ‘‘sbg2.ericsson.hr’’
remote Host H03 = ‘‘icscf.ims2.ericsson.hr’’
remote Host H04 = ‘‘bgcf.ims2.ericsson.hr’’
remote Host H05 = ‘‘tss.external.com’’
Domain D01(1) = ‘‘ims1.ericsson.hr’’
Domain D02(1) = ‘‘ims.external.com’’

SIP/SIP-I Advanced in MSS15

6.2.3) Analyze the following configuration and answer the question.

What are the two possible actions to trigger DNS resolving?

1) IP address is removed by command IBHAE. If that was the last

IP address defined for the remote host, next SIP call will trigger
a DNS resolving (A-query). In case an ASN sets IP address in
the Via header, this action shall be avoided, because of
possible problems with RSI discrimination.

2) DNS enforcement. Route parameter DNSEF is set to value 1, 2 or 3.

 Define remote hosts:

IBHOI:HOST=ICSCF1,NAME1="ICSCF.IMS.ERICSSON.SE",RPN=5
060,TRN=0;

IBHAI:HOST=ICSCF1,IPADD="191.110.12.13";

Define RSI:

RSI number 1:

IBROI:RSI=IMS1,DEST=ICSCF1,SRC1=BGCF1,SRC2=BGCF2,
RSINUM=1;

Analysis and Modeling of Radio Wave Propagation
No ratings yet
Analysis and Modeling of Radio Wave Propagation
298 pages
3g Call Flow
No ratings yet
3g Call Flow
14 pages
B No Analysis 1111
100% (1)
B No Analysis 1111
27 pages
Slides SIP SIP-I Advanced in MSS15
100% (3)
Slides SIP SIP-I Advanced in MSS15
257 pages
Huawei Csoftx3000 Signaling Protocols
No ratings yet
Huawei Csoftx3000 Signaling Protocols
23 pages
SIP Header MSG Format
100% (1)
SIP Header MSG Format
40 pages
Voice over LTE: VoLTE
From Everand
Voice over LTE: VoLTE
Miikka Poikselkä
4.5/5 (2)
Sip Report All
100% (1)
Sip Report All
80 pages
AMOS MGW-V4-V3 Commands Bis
No ratings yet
AMOS MGW-V4-V3 Commands Bis
2 pages
2 Signaling Connection Control Part SCCP
100% (1)
2 Signaling Connection Control Part SCCP
12 pages
M-MGW Basics
100% (1)
M-MGW Basics
25 pages
Data Transcript Example For MSC Server R13.2
67% (3)
Data Transcript Example For MSC Server R13.2
783 pages
3-The Session Initiation Protocol
No ratings yet
3-The Session Initiation Protocol
42 pages
Call Flow at MNP Scenario
100% (1)
Call Flow at MNP Scenario
22 pages
Call Management in GSM
100% (1)
Call Management in GSM
48 pages
MGW Boards
100% (1)
MGW Boards
10 pages
No 7 (SCCP&TCAP&INAP)
100% (1)
No 7 (SCCP&TCAP&INAP)
48 pages
Troubleshooting and Maintenace For CS Core
100% (3)
Troubleshooting and Maintenace For CS Core
29 pages
SMS Flow
100% (1)
SMS Flow
2 pages
Comandos Basicos GSM HLR/VLR: Comandos Pag 2..6 Anexos Equivalencias Categorías TDMA/GSM
100% (1)
Comandos Basicos GSM HLR/VLR: Comandos Pag 2..6 Anexos Equivalencias Categorías TDMA/GSM
6 pages
3 GSM Traffic Management
100% (1)
3 GSM Traffic Management
58 pages
Normalization CDR
100% (1)
Normalization CDR
7 pages
Ericsson Core Sts and Kpi
100% (3)
Ericsson Core Sts and Kpi
24 pages
Signal Flow in Mobile in
100% (1)
Signal Flow in Mobile in
36 pages
MSC Troubleshooting With MGW
No ratings yet
MSC Troubleshooting With MGW
28 pages
GSM Call Path Course
100% (1)
GSM Call Path Course
75 pages
Call Flow For Various PPS Call Scenario
100% (2)
Call Flow For Various PPS Call Scenario
30 pages
SMSC Call Flow
100% (1)
SMSC Call Flow
3 pages
Lazy Startup Blade Cluster 13a
100% (1)
Lazy Startup Blade Cluster 13a
82 pages
Sip Error Codes
100% (4)
Sip Error Codes
36 pages
SIP Response Codes
100% (1)
SIP Response Codes
4 pages
GSM Introductory Overview
100% (1)
GSM Introductory Overview
49 pages
13 International Roaming
100% (1)
13 International Roaming
10 pages
Intro To SIP I - SIP T
No ratings yet
Intro To SIP I - SIP T
17 pages
Traffic Case Description - Mobile Originating Calls
100% (3)
Traffic Case Description - Mobile Originating Calls
13 pages
GSM Architecture and Interfaces
No ratings yet
GSM Architecture and Interfaces
25 pages
Health Check MG W
100% (1)
Health Check MG W
8 pages
AXE - CAMEL Trigger Table - Config
0% (1)
AXE - CAMEL Trigger Table - Config
9 pages
Traffic Case Charging
100% (1)
Traffic Case Charging
79 pages
Authentication in GSM
100% (1)
Authentication in GSM
14 pages
Unit 3: GSM Roaming Scenarios and Handover
100% (2)
Unit 3: GSM Roaming Scenarios and Handover
53 pages
IMS - Charging Management (3GPP TS 32.260)
No ratings yet
IMS - Charging Management (3GPP TS 32.260)
118 pages
VAS
No ratings yet
VAS
50 pages
iFC Initial Filtering Criterion
No ratings yet
iFC Initial Filtering Criterion
3 pages
MML Commands
100% (1)
MML Commands
375 pages
GSM Voice Mail Service TDM Call PDF
No ratings yet
GSM Voice Mail Service TDM Call PDF
68 pages
AXE Equipment Management: User Guide
100% (2)
AXE Equipment Management: User Guide
61 pages
HLR Redundancy Description
100% (1)
HLR Redundancy Description
14 pages
3GPP Ims
100% (2)
3GPP Ims
16 pages
SS7 Signaling Basic
No ratings yet
SS7 Signaling Basic
23 pages
SGSN User Guide
100% (1)
SGSN User Guide
486 pages
GSM Call Setup
No ratings yet
GSM Call Setup
6 pages
Diameter Protocol A Complete Guide
From Everand
Diameter Protocol A Complete Guide
Gerardus Blokdyk
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
SIP Introduction
No ratings yet
SIP Introduction
7 pages
Next Generation Networks: Lectures 6, 7, 8 Session Initiation Protocol (SIP)
No ratings yet
Next Generation Networks: Lectures 6, 7, 8 Session Initiation Protocol (SIP)
40 pages
SIP Overview
100% (1)
SIP Overview
36 pages
Session Initiation Protocol (SIP)
No ratings yet
Session Initiation Protocol (SIP)
77 pages
Sip
No ratings yet
Sip
58 pages
التربية الاسلامية - استرشادية - داخل ليبيا-أساسي-2020-4998
No ratings yet
التربية الاسلامية - استرشادية - داخل ليبيا-أساسي-2020-4998
17 pages
LTE RAN and Services Multi-Period Planning: Dmytro Ageyev Ali Al-Ansari
No ratings yet
LTE RAN and Services Multi-Period Planning: Dmytro Ageyev Ali Al-Ansari
3 pages
مهمة في cell planning
No ratings yet
مهمة في cell planning
47 pages
LTE N: C C P: Etwork Overage and Apacity Lanning
No ratings yet
LTE N: C C P: Etwork Overage and Apacity Lanning
6 pages
Cisco Sdwan Design Guide
No ratings yet
Cisco Sdwan Design Guide
101 pages
Lab-01 Introduce to IP Address
No ratings yet
Lab-01 Introduce to IP Address
6 pages
Unit 7
No ratings yet
Unit 7
5 pages
Ribbon CommunicationsEdgeMarc 4806 and 4808 Datasheet (1)
No ratings yet
Ribbon CommunicationsEdgeMarc 4806 and 4808 Datasheet (1)
4 pages
Anti Ban Host
100% (1)
Anti Ban Host
271 pages
Aws Networking Fundamentals
100% (2)
Aws Networking Fundamentals
75 pages
User Manual Totolink N300RT (English - 58 Pages)
No ratings yet
User Manual Totolink N300RT (English - 58 Pages)
2 pages
Copilot: Instructions
No ratings yet
Copilot: Instructions
12 pages
xrdocs_io_ncs5500_tutorials_bgp_evpn_irb_configuration
No ratings yet
xrdocs_io_ncs5500_tutorials_bgp_evpn_irb_configuration
11 pages
The Evolution From PPPoE To IPoE Sessions PDF
No ratings yet
The Evolution From PPPoE To IPoE Sessions PDF
34 pages
DHCP Relay - Duplicate IPs: R:juniper
No ratings yet
DHCP Relay - Duplicate IPs: R:juniper
1 page
Router 04102019
No ratings yet
Router 04102019
7 pages
Dynamic VTI Easy VPN
No ratings yet
Dynamic VTI Easy VPN
2 pages
Chapter 2 Review Questions
No ratings yet
Chapter 2 Review Questions
2 pages
Introduction of Routing Protocols
No ratings yet
Introduction of Routing Protocols
11 pages
MX BNG 17.x-18.x new features v02 (ENG)
No ratings yet
MX BNG 17.x-18.x new features v02 (ENG)
48 pages
11 - First Hop Redundancy Protocol
No ratings yet
11 - First Hop Redundancy Protocol
17 pages
300-415 Exam Dumps Questions
No ratings yet
300-415 Exam Dumps Questions
56 pages
Naufal
No ratings yet
Naufal
9 pages
1 PDF
No ratings yet
1 PDF
1 page
error-viptela
No ratings yet
error-viptela
2 pages
Proxy Kampret
No ratings yet
Proxy Kampret
4 pages
Chapter 7: Ripv2: Ccna Exploration Version 4.0 Ccna Exploration Version 4.0
No ratings yet
Chapter 7: Ripv2: Ccna Exploration Version 4.0 Ccna Exploration Version 4.0
60 pages
Staying Anonymous
No ratings yet
Staying Anonymous
8 pages
01 01 RN23821EN31GLA0 MCBSC Architecture
No ratings yet
01 01 RN23821EN31GLA0 MCBSC Architecture
62 pages
BGP Route Reflectors and Route Filters
No ratings yet
BGP Route Reflectors and Route Filters
12 pages
Packet Tracer: Conexión de Un Router A Una LAN
No ratings yet
Packet Tracer: Conexión de Un Router A Una LAN
12 pages
Log
No ratings yet
Log
787 pages
Torku-13.2.7 Packet Tracer - Use Ping and Traceroute To Test Network Connectivity
No ratings yet
Torku-13.2.7 Packet Tracer - Use Ping and Traceroute To Test Network Connectivity
7 pages
CN Assignment 3 2022-23
No ratings yet
CN Assignment 3 2022-23
4 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.