MGW integration to MSS

Nokia Switching Core Network - MSSMGWITG

MGW integration to MSS - Mc interfaceTraining Document

M13

6-246350Issue v.1

Nokia Networks Oy

1 (34)

MGW integration to MSS - Mc interface

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Oyj. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Oyj 2010. All rights reserved.

2 (34)

Nokia Networks Oy

6-246350Issue v.1

Contents

Contents1 Objectives 4

2 Introduction 5 2.1 Signalling and Protocols........................................................................................................ 8 2.2 Broadcast 8 3 Introduction to MGW integration to MSS................................................................................. 10 3.1 Differences between integrated and standalone MSC Server concept................................12 4 Configuring IP connectivity for MSC Server...........................................................................13 4.1 Example of TCP/IP configuration ........................................................................................ 15 4.2 Configuring IP version 4 interface........................................................................................ 16 4.3 Configuring IP version 6 interface........................................................................................ 17 5 SIGTRAN 18 5.1 SCTP configuration.............................................................................................................. 20 5.2 SIGTRAN signalling link set and route set configuration......................................................20 6 H.248 (or MEGACO)............................................................................................................... 22 6.1 Creating a Multimedia Gateway........................................................................................... 24 6.1.1 Create Multimedia Gateway in MSS................................................................................. 25 6.1.2 Create Multimedia Gateway in MGW................................................................................ 27 7 Configuring TDM resources for integrated MSS.....................................................................30 7.1 Create interconnect TDM on MSS side................................................................................ 30 7.2 Create interconnect TDM on MGW side..............................................................................31

6-246350Issue v.1

Nokia Networks Oy

3 (34)


1

ObjectivesAt the end of this module the student will be able to:

Name and draw the control plane protocols used in MSS Build the protocols above IP for enabling SS7 links between MSS and MGW and make the states of the interfaces "UP" Define the protocol structure in MSS for device control protocol H.248 needed between MSS and MGW Create the needed TDM resources for integrated MSS between MSS and MGW. Created IWF/CDS interface Verify the integration by changing the state of all signalling interfaces and circuits (in case of integrated MSS) to "Working"

4 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

2

IntroductionThis section explains the interfaces in the MSS based on reference architecture as defined in 3G.PP Rel.4 and Rel.5. The interfaces and connections are presented in the next figures.

MSS interfaces in release 4

Realization of interfaces with release 4 A-interface

A-interface is used to transmit speech, data and signalling between MSS and BSS. When A-interface is connected to MGW, BSSAP signalling is routed from MGW to MSS using SIGTRAN, hence MGW acts as Signalling Gateway.Iu-CS Interface

The Iu-CS interface is used to carry circuit switched traffic between 3G RAN and MGW. This interface is ATM based and uses AAL2. The Iu-CS Control Plane is connected from the RNC to the MSS via MGW. The MGW acts as signalling gateway. The RANAP signalling is routed from MGW to MSS using SIGTRAN.

6-246350Issue v.1

Nokia Networks Oy

5 (34)


Nc Reference Point

The Nc reference point describes the interface between VMSS and Gateway MSS. Over the Nc interface Network-Network based call control signalling is performed. BICC CS-2 is supported. BICC CS-2 is bearer independent call control signalling, since it will support both ATM and IP based core networks. Alternatively SIP is supported in Nc if core network is based on IP transport.Mc Reference Point

The Mc reference point describes the control interface between MSS and MGW or GCS (Gateway Control Server) and MGW. The used control protocol is H.248.Nb Reference Point

The Nb reference point describes the interface between MGWs. Over the Nb interface all user data are transmitted. It could be created as an IP or ATM based backbone.Interface towards HLR

The interface towards the HLR could be still TDM based MAP signalling or IP based sending of MAP messages via SIGTRAN.IN and GPRS

There are no changes.

6 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

SCE

CPS

MAP CAP/INAP

HLR/HSS

CAP/INAP

SIP

BSC

MAP

MAP

GSM

VMSSSIP, BICC CS-2

GCS

H.248

ISUP H.248

RNC

A

MGW

MGW

Iu-CS

Packet Core NW

PSTN/ISDN

WCDMA

Figure 1.

MSS Interfaces in release 5

New interfaces with release 5 GCS - CPS

SIP protocol will be available in order to enable interworking between CS Domain and IMSC and D Reference Points

The C reference point describes interface between Gateway MSS and HSS. The D reference point describes interface between VMSS and HSS. Interfaces are implemented by using MAP over legacy SS7 or MAP over IP (SIGTRAN M3UA).

6-246350Issue v.1

Nokia Networks Oy

7 (34)


MSS - SCE Interface

This is the interface between the MSS and the Service Creation and Execution environment (SCE). The supported protocols are CAP phase 3 and Core INAP CS-1.

1

Signalling and ProtocolsFollowing figure gives an overview what are the available signalling and protocols in Nokia MSS product towards packet based network.

Figure 2.

Signalling protocols in MSC server

2

BroadcastIn the release 4 configuration it is, like before, better to set the sending of broadcast messages. In case of (RANAP) reset messages this could reduce the amount of problems. Steps: Local broadcasts:OBC:,,:,:;

8 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

Remote broadcasts:OBM:,,:,:;

6-246350Issue v.1

Nokia Networks Oy

9 (34)


3

Introduction to MGW integration to MSSThe main idea of Release 4 and introduction of MSC Server concept is to separate control plane (Signalling) and user plane (User data) from each other. Control plane should be transferred and handed to MSC Server, whereas User plane is transferred between MGWs. MGWs are like external group switches of the MSS. Mc interface is used between MSC server and MGW and acts as control interface. MSC server controls resources inside MGW through this interface. Mc interface is based on H.248 (ITU-T) standard. Similar standard is defined by IETF, which is called MEGACO. H.248 uses either SCTP or TCP over IP. In Nokia MEGACO is based on SCTP. H.248 does not need user adaptation, means no MTP3 function is involved. In Rel. 4 network, MGW acts as Signalling gateway. It receives control plane from RAN (MTPb on ATM), BSS (MTP on TDM) and from PSTN or other PLMN (MTP over TDM). Control plane is transferred to MSC server. Towards MSC Server, MGW has signalling interface over IP. This interface is called SIGTRAN. SIGTRAN uses SCTP (stream control Transport Protocol) over IP as lower layer. In Nokia the SIGTRAN is realized as the M3UA (MTP user adaptation) layer to allow transfer of user parts and application parts messages. In case you have realized all CCS7 connections IP based, means using SIGTRAN, then no GSW (Group switch Hardware), CCSU and ET PIU are needed in MSS any longer. This means all connections towards HLR, SRRi or SGSN are using SIGTRAN. BSUs are still needed, also in case all BSCs are connected direct to MGW, because of BSSAP program block (AIF). In summary, between MSS standalone and MGW following interfaces are possible

SIGTRAN H.248

10 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

Figure : Hardware of standalone MSS

6-246350Issue v.1

Nokia Networks Oy

11 (34)


1

Differences between integrated and standalone MSC Server concept

Hardware of integrated MSS

In case of Integrated MSC server, BSS and PSTN could be still connected directly to MSS. Beside this there is possibility that MSS provides IWF functionality for circuit switched data calls. In either case, there is need to created additional interface between MSS and MGW to pass user plane between them. This interface is based on TDM connections. For BSS connectivity, this interface is called Interconnection TDM. In summary, between MSS and MGW following interfaces are possible

SIGTRAN H.248 Interfaces for Integrated MSC server (one PCM for speech, in case of connected BSS and one PCM for CS data calls)

12 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

4

Configuring IP connectivity for MSC ServerBoth SIGTRAN and MEGACO require IP connectivity between MSC server and MGW. This section describes IP connectivity. You can configure IP connectivity of the MSS to external IP network using Ethernet cablings and internal switches integrated inside the network element. The following figure represents how IP connectivity is offered from the signaling units of the MSS towards external site router or switch equipment. The signaling units are not directly connected to the external router/switch but via integrated LAN switch, that is, ESB20 or ESB20_A. Note also, that CP710A CPU is used as an example CPU, other CPUs, which have dual LAN interfaces (e.g. CP-550B) may also be used.

Figure 3.

IP connectivity of signalling units

6-246350Issue v.1

Nokia Networks Oy

13 (34)


Before you start

The integration of the MSS to IP network in the PLMN requires the following prerequisites: 1. Plan both the public and private IP addresses (including the version of IP) to be used in MSS network element as well as in other network elements and hosts. 2. Plan site environment. More detailed description of reference site example can be found from MSC Server Site Integration. 3. Plan core IP network. More detailed description can be found from 3G Backbone Solution Description.Note

Consider the following issues in order to achieve redundancy in the MSS.

Each CPU should have at least two Ethernet LAN ports EL0 and EL1 (CP-550A or CP-710A). With this arrangement it is possible to switch to another port when the link (Ethernet connection) between the CPU and/or LAN switch (LANU) fails. Each CPU should have one logical IP address. The logical address itself remains the same also after N+1 redundant (signalling) unit switchover. The CPU can also have physical IP address, however that address should not be used in signalling traffic configurations (at DNS or SCTP level). Domain Name Server (DNS) configuration is required for certain applications, such as call control signalling SIP. It is possible to use MSS functionality with CPUs having only one LAN port but in that case no LAN redundancy can be offered in case of switch or LAN cabling failures, except in case of signaling units. Forced switchover of LAN interface can be executed using the QRW command (IPv4) or the Q6W command (IPv6). Signalling units (e.g. CCSU, SIGU, ISU) can be configured for SCTP multihoming. In this case both EL0 and EL1 will have different logical IP addresses in different subnet. (see the example below). Both interfaces are used, one is primary path and second is secondary path. When the computer units are not used for multihoming (e.g. units like OMU, CHU), same logical IP address is given to both EL0 and EL1 port. At a time only one out of EL0 and EL1 is active. Active interface assumes given logical IP address.

14 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

4.1

Example of TCP/IP configuration

Figure 4.

Example of IP connectivity of signalling units for SCTP

Figure 5.

IP connectivity for units used for SCTP

Figure 6. IP connectivity for units not used for SCTP

6-246350Issue v.1

Nokia Networks Oy

15 (34)


2

Configuring IP version 4 interfaceSteps

1. Configure internal ESB20 LAN switches 2. Configure IP network interfaces to each individual signalling unit (xSU) from where the IP connectivity is required (QRN). Numbered interface should have logical IPv4 address which is tied to both interfaces of the CPU in question. ZQRN:,,::::::state:; You can check the correct execution with the QRI command. 3. Configure TCP/IP parameters for signalling units (QRT) Each CPU, besides IPv4 network interface, can also have Fully Qualified Domain Name (FQDN) as well as other parameters. The following command can be used to give hostname for the signalling unit. ZQRT:,:HOST=:; 4. Configure static route (QRC) Define static route of the next hop router with the QRC command. ZQRC:,::::::; 5. Configure DNS-related parameters (QRK) Access Domain Name Service (DNS) servers. Note that the command needs to be given only once per MSS network element. ZQRK:,,,:; After IPv4 network interface has been configured it is possible to test the connectivity to the signalling unit by for example, pinging the IP address of signalling unit from an external device.

16 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

4.3

Configuring IP version 6 interfaceSteps

1. Configure internal ESB20 LAN switches 2. Configure IPv6 network interfaces to each individual signalling unit (xSU) from where the IP connectivity is required (Q6N) Numbered interface should have logical IPv6 address which is tied to both interfaces of the CPU in question. ZQ6N:,::,L::state:; You can check the successful execution with the Q6I command. 3. Configure TCP/IP parameters for signalling units (Q6T) Use the Q6T command to define specific values to the IPv6 interface-specific parameters:

IP Forwarding; defining whether the CPU forwards IP packets not belonging to it Hop limit; defining the maximum value of hops for an IP packet sourced by CPU Router advertisement; defining whether the CPU listens to the IPv6 router advertisements

ZQ6T:,:IPF=,HLIM=,RADV=:; 4. Configure static route (Q6C) Define static route of the next hop router with the Q6C command. ZQ6C:,:::::; 5. Configure DNS-related parameters (Q6K) Access Domain Name Service (DNS) servers. Note that the command needs to be given only once per MSS network element. ZQ6K:,,,,,::,:; After IPv6 network interface has been configured it is possible to test the connectivity to the signalling unit by for example, pinging the IP address of signalling unit from an external device.

6-246350Issue v.1

Nokia Networks Oy

17 (34)


5

SIGTRANThe configuration of SIGTRAN consists of an SCTP part and an M3UA part. The SIGTRAN M3UA (SS7 MTP3-User Adaptation Layer) provides the applications with the same services as the MTP3 in the SCN (Switched Circuit Network). It routes the MTP layer 3 messages from the applications to the correct IP resources (SCTP associations). The M3UA supports the transfer of the messages of any protocol layer that is identified to the MTP Level 3 layer as a user part. The list of these protocols include for example the following: ISUP (ISDN User Part), TUP (Telephone User Part), and SCCP (Signalling Connection Control Part). The TCAP or RANAP messages are transferred transparently by the M3UA as SCCP payload, as they are SCCP-User protocols.)

Figure 7 SIGTRAN based signalling link concept

The M3UA signalling channels always lead to a SEP (Signalling End Point) network element. The STP (Signalling Transfer Point) function between SCNIP and IP-IP networks is supported when both networks share a SPC (Signalling Point Code). Most of the SS7 signalling functionality remains identical to the existing SCN (Switched Circuit Network) signalling. The SIGTRAN feature

18 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

affects only the transport layer of the SS7 signalling: It provides a new adaptation layer designed to fit the MTP layer 3 messages on the IP network. For this reason some of the existing concepts have been redefined. When the IP is used as transport media, the concept of signalling channel refers to a logical resource instead of a physical resource (PCM-TSL). The SIGTRAN M3UA signalling channel acts as a link to the logical SCTP association set which leads to the next network element. An SCTP association set consists of a group of SCTP associations, each of which is an IP resource allocation. The concepts of signalling link set and signalling route set remain as defined by the ITU-T. SIGTRAN can be used between a Signalling Gateway (SG) and a Media Gateway Controller (MGC) or between any other exchanges like an MSC and a HLR SCTP is a reliable transport protocol operating on top of a potentially unreliable connectionless packet service such as IP. It offers acknowledged error-free nonduplicated transfer of datagrams (messages). Detection of data corruption, loss of data and duplication of data is achieved by using checksums and sequence numbers. A selective retransmission mechanism is applied to correct loss or corruption of data. Nokia M3UA implementation enables the use of M3UA in three different configurations:

Signalling Gateway - Application Server (SG-AS), IP Server - IP Server (IPS-IPS), or Signalling Point Management Cluster (SPMC).

Figure 8 Example of SG-AS configuration

6-246350Issue v.1

Nokia Networks Oy

19 (34)


SIGTRAN signalling links must be used between MSC server and MGW or GCS in Nokia Release 4 configuration.

1

SCTP configurationBefore configuring SIGTRAN signalling transport it is assumed that an appropriate IP configuration has been created (See chapter 4) Steps: 1. Create an association set (OYC) ZOYC::; Role=server/client Role can be either 'S' as server or 'C' as client. The nature of association set is server-client where the server side waits for the SCTP layer initialization from the client side. Usually, the MSS should be the server while the signalling gateway should operate as the client. 2. Add associations to the association set (OYA) ZOYA::,:; One signalling unit can belong to multiple association sets, but inside one association set the unit can only be connected to one association. 3. Check the associations (OYI) Verify that the associations were created correctly and that they have correct IP addresses by using the command OYI. OYI::A:; 4. Modify association set parameters if needed (OYM)

2

SIGTRAN signalling link set and route set configurationSteps:

20 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

1. Create signalling link set and IP signalling link (NSP) Create the IP signalling link together with the signalling link set which is used to exchange MTP signalling messages. ZNSP:,,::; When defining IP signalling link, the signalling link set is established automatically. However, the signalling route set needs to be created and signalling link set attached to it before any signalling transfer can take place. 2. Create signalling route set normally (NRC). 3. Allow activation of signalling links (NLA) 4. Activate signalling link (NLC). 5. Allow activation of signalling routes (NVA) 6. Activate created signalling routes (NVC) SCCP and subsystem configuration steps are the same as normally (NFD).

6-246350Issue v.1

Nokia Networks Oy

21 (34)


6

H.248 (or MEGACO)In Nokia MSC Server the user plane resources can be physically present in either the MSS (Integrated solution), referred as internal resources, or in the Multimedia Gateway referred as external resources. Nokia MSS has three different types of resources. Alternatives are due because of the possibility to have simultaneously both internal and external resources in use.

Only internal resources are in use (Integrated MSS) The integration process of the MSCi functionality of Nokia Integrated MSS is described separately in MSC/HLR integration. Only external resources are in use (both Integrated and Standalone MSS), meaning that all resources that are controlled by the MSC Server are located in MGWs. Both internal and external resources are in use (Integrated MSS), possible when, for instance, MSCi has been upgraded to the MSS network element and resources that were controlled by the MSCi become internal resources of the MSS.

H.248 or MEGACO is the interface between MSS and MGW to control user plane resources. This interface is realized by establishing control connection between signalling unit (CCSU / SIGU) in MSS to signalling unit (ISU) in MGW. In MSS, this is implemented by creating MGW and in MGW it is implemented by creating virtual MGW. You can divide each Release 4 level Nokia MGW into number of virtual MGWs. Each virtual MGW is identified by:

name and number, IP address of ISU signalling unit, IP port number and address of controlling signalling unit of MSS.

The virtual MGW has dedicated TDM resources as well as other parameters. You can configure each virtual MGW at MSS side as a normal MGW, there is no difference between the physical and logical MGW from the MSC Server's point of view. It is strongly recommended to divide large physical MGWs into several virtual MGWs so as to share load caused by the resource control traffic and the functionality evenly at the MSS-side. User plane resources for MSC server can be created only after H.248 interface is created between MSS and virtual MGW.

22 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

Note One Signalling unit in MGW can have 5 control interfaces i.e. it can be divided into 5 virtual MGWs. Each signalling unit can only process a limited number of simultaneous calls. Currently, the limit is 2000 calls per signalling unit. One MSS can, in theory, control up to 100 MGWs. In normal occasions, the practical number is estimated to be less than ten MGWs.

Figure 9. Example of H.248 connection between MSS and MGW

6-246350Issue v.1

Nokia Networks Oy

23 (34)


Before you start

The MSS has to be aware of the existence and capabilities of the MGW before any resources located in that MGW can be used. This is enabled via the auditing and registration process.To configure H.248 control interface for MSC Server

1.

Add new MGW Select the signalling unit at MSS side, which communicates with the MGW.

2.

Configure MGW a. b. c. d. e. f. Add MGW to MSS's MGW database. Select the signalling unit in MSS side, which communicates with the MGW. Configure H.248 specific data. Configure E.164 address of the MGW. Configure each virtual MGW 's domain name and IP address. Configure peer MSS's IP addresses and domain names of each virtual MGW.

3.

Register MGW a. b. Check that registration is enabled from the MGW at MSS side. Activate registration process in the MGW.

1

Creating a Multimedia GatewayBefore you start, decide about the following MGW related issues before proceeding A suitable name for the MGW IP address or host name of the MGW A suitable CCSU or SIGU signalling unit in MSS to handle H.248 traffic caused by the MGW

24 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

Note One signalling unit in MSS may control more than one MGW. Each MGW adds H.248 signalling and additional CPU processing load for the signalling unit. The theoretical limit for one signalling unit is 10 MGWs. However, it is recommended that less than five MGWs are configured to use the same signalling unit. Each CPU can handle about 2000 simultaneous calls.

IP address of MSS's signalling unit (CCSU or SIGU) Bearer Control Unit identifier of MGW This identifier is sent to the succeeding MSS via BICC signalling which can be used in the peer MSS's user plane analysis to determine a suitable MGW. The E.164 address of MGW

Note If you configure this parameter, the Nokia MSS is capable of optimising call related connections to use the same physical MGW in some occasions. The MSS carries out the optimisation by comparing the MGW (E.164) address received from other MSC Servers with this configured address when selecting own MGW.

6.1.1

Create Multimedia Gateway in MSSBefore creating MGW in MSS there must be an IP address given to signalling unit (CCSU or SIGU). Steps: 1. Create MGW in MSS (JGC)ZJGC:DMN=,ADDR=,PORT=,NAME=;

Example:ZJGC:DMN=MGW1.OPERATOR.COM,NAME=MGW1HKI:GROU=1001,DROU=1001, UTYP=CCSU,UINX=2,UADDR="192.168.10.15",LBCU=5,IWF=T,TRFO=T,IPATM=F;

2.

Check the visibility of MGW (JGI)

ZJGI:MODE=:NAME=,MGWID=,E164=;

Example:ZJGI:MODE=0:NAME=MGW1HKI;

6-246350Issue v.1

Nokia Networks Oy

25 (34)


3.

Modify MGW data (JGM)

Not all the MGW data can be specified with the 'create' command, but sometimes it is necessary to define additional data using the 'modify' command. A typical example of this is configuring an interconnecting TDM route for the MGW. Note It is also possible to change the MGW registration allowed status using the 'modify' command.JGM:( NAME = |MGWID = ):( [ [ DMN = |ADDR = ],PORT = ]: |[ ROU = |UTYP = |UINX = |UADDR = |E164 = |LBCU = |TRFO = |IPATM = |REGA = ] );

Example: Define the interconnecting TDM route number 532 to MGWOULU1 and allow registration.ZJGM:NAME=MGWOULU1::ROU=532,REGA=Y;

4.

Modify registration of MGW (JGR)

The MSS allows configured MGW to register after this step. However, if for some reason (such as software upgrade, maintenance or other) some MGW need to be taken down for a while, unregistering is possible by giving the J command. R G Example Clear all calls gracefully (without losing any calls) from MGW and unregister it from the MSS.ZJGR:MODE=0:NAME=MGW1HKI:METHOD=0,REGA=F;

Note It is possible that in case H.248 connection is broken between MSS and MGW that the MGW has alternative addresses (in Nokia MGW up to five alternative addresses can be defined) to connect in case of failures. However, make sure to verify that these alternative addresses point to the same MSS network element. Otherwise, the control plane and user plane resources are not controlled correctly. Note For modifying some TDM resources, you deny registration first and allow the registration afterwards again.

26 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

6.1.2

Create Multimedia Gateway in MGWNote Before creating VMGW in MGW there must be an IP address given to signalling unit (ISU). The H.248 control protocol has to be configured separately for each ISU unit. Steps: 1. Create Virtual Media Gateway (JVC) A maximum of five Virtual Media Gateways (VMGW) can be configured into one ISU unit.

Note The MSC Server IP addresses (primary and secondary) that are specified to a particular Virtual Media Gateway must always be located within the same physical MSC Server network element. However, the different Virtual Media Gateways of one Multimedia Gateway network element can be connected to various physical MSC Server network elements.ZJVC:(VMN=,UINX=): (OIP=,| ODN=,) OPN=: [CGR=, A2T=]: [TTY= | 1 def, CTY= | 0 def]: [PIP=, | PDN=]: [SIP=, | SDN=]: [DUR= | 1 minute def];

Note The JVC command can be used to specify only one secondary MSC Server IP address. 2. Modify Virtual Media Gateway (JVM) If there is a need to specify more than one secondary MSC Server IP address, use theJVM command. Note that a maximum of 5 secondary MSC Server IP addresses can be configured into one Virtual Media Gateway.

6-246350Issue v.1

Nokia Networks Oy

27 (34)


Note The MSC Server IP addresses (primary and secondary) that are specified to a particular Virtual Media Gateway must always be located within the same physical MSC Server network element. However, the different Virtual Media Gateways of one Multimedia Gateway network element can be connected to various physical MSC Server network elements. When adding the secondary MSC Server addresses with the JVM command, the default parameter values can be used for following parameters: internal circuit group number (CGR), analysis tree number for AAL2 (A2T), transport type (TTY), coding type (CTY), and duration (DUR).ZJVM:(VID=, VMN=): (CGR=, A2T=: TTY=, CTY=: [PIP=, | PDN=]: SNUM=, [SIP=, | SDN=]: DUR=);

3.

Register Virtual Media Gateway (JVR)ZJVR:(VID=..., | VMN=): [REGA= | 0 def, MET= | 0 def, DEL=];

4.

Interrogate Virtual Media Gateway (JVI) Use the JVI command to interrogate the Virtual Media Gateway data. The H.248 control protocol connection is active when the Virtual Media Gateway registration status is 'registration allowed'.ZJVI: (VID=..., | VMN=);

Note For modifying some TDM resources, you deny registration first and allow the registration afterwards again. Expected outcome After successful assignment of the IP address to network interface, the system outputs an execution printout indicating that the specified IP address has been created. After successful creation of the Virtual Media Gateway, the system outputs an execution printout indicating that the specified Virtual Media Gateway has been created. After successful registration of the Virtual Media Gateway, the system outputs an execution printout indicating that the specified Virtual Media Gateway has been registered to the primary/secondary MSC Server. Unexpected outcome

28 (34)

Nokia Networks Oy

6-246350Issue v.1

Glossary

If an error occurs when assigning the IP address to network interface, the system outputs an error-specific execution error message. The network interface can be modified and the IP address can be removed by using the QRN command. If an error occurs when creating the Virtual Media Gateway, the system outputs a general MML execution error message. The Virtual Media Gateway can be modified by using the JVM command and it can be deleted by using the JVD command. If an error occurs when registering the Virtual Media Gateway, the system outputs a general MML execution error message. The registration information of the Virtual Media Gateway can be updated by using the JVR command.

6-246350Issue v.1

Nokia Networks Oy

29 (34)


7

Configuring TDM resources for integrated MSSWhen integrated MSC server is used there exist a number of signalling interfaces, which use PCM links instead of IP, also speech data could be transmitted via TDM resources. For instance when BSC (2G) is connected directly to MSC server instead of MGW. Also connections to HLR and IN SCP may still use PCM links to carry MAP/CAP signalling. In some cases it is possible that the PSTN is connected to MSC server. Actual implementation depends on the customer network structure. In this case the procedure is the same as for standard MSC/HLR.

1

Create interconnect TDM on MSS side1. Check connected functions of used ET with ZWTI. The ET used for interconnection must have the function ETT00 for TSL 0 and the function INTC for all other TSLs. (Create with ZWTP) Create CGR, with the type SPE (special), use INTC and MGW=name of before created MGW (ZRCC)|NCGR = |CGR

2.

RCC : [ TYPE = = ] : Type SPE (block 2 and 3)

[ HUNTED = ] :[ INR = |TREE = |USE spe cgr> ] ; IF USE = INTC or OLCM (MSC Server) [ MGW = ] ;

=

MGW integration to MSS

Documents

Transcript of MGW integration to MSS