MLPP Relay in PRI to SIP/ISUP Interworking Feature Module

Transcription

1 MLPP Relay in PRI to SIP/ISUP Interworking Feature Module Document Release History Publication Date January 24, 2011 Comments Initial release of document. Feature History Release Modification 9.8(1) The MLPP Relay in PRI to SIP/ISUP Interworking feature is introduced on the Cisco PGW 2200 Softswitch software. This document describes the MLPP Relay in PRI to SIP/ISUP Interworking feature. This feature is described in the following sections: Feature Description, page 2 Supported Standards, MIBs, and RFCs, page 3 Provisioning Tasks, page 3 Provisioning Examples, page 4 Obtaining Documentation and Submitting a Service Request, page 8 Glossary, page 8 Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA USA

2 Feature Description Feature Description The MLPP Relay in PRI to SIP/ISUP Interworking feature for the Cisco PGW 2200 Softswitch supports MLPP for PRI-PRI and PRI-SIP/ISUP interworking without local handling and vice versa. With this feature, Cisco PGW 2200 Softswitch interoperates PRI with SIP peers such as CUCM and switches interoping with SS7 in the customer deployment/pstn to facilitate PRI-SIP and PRI-ISUP prioritized call handling transparently. Benefits This feature provides the following benefit: Enables MLPP for PRI-PRI and PRI-SIP/ISUP interworking without local handling and vice versa. Prerequisites The Cisco PGW 2200 Softswitch must be running software Release 9.8(1). The prerequisites for Release 9.8(1) can be found in Release Notes for the Cisco PGW 2200 Softswitch Release 9.8(1) at: Restrictions or Limitations The MLPP Relay in PRI to SIP/ISUP Interworking feature has the following limitations: Cisco PGW 2200 Softswitch only supports MLPP relay information in the SIP-PRI and ISUP-PRI interworking and PRI-PRI call scenarios. No local handling is supported in this feature. On PRI, Cisco PGW 2200 Softswitch will not maintain any MLPP information (domain, priority) for circuits No pre-emption or LFB procedure will be originated or supported In the context of SIP, prioritized call handling requests will not be authenticated or authorized No pre-emption or queueing will be possible for SIP calls An MLPP call will be treated as a regular PRI-PRI, ISUP-PRI, PRI-ISUP, SIP-PRI, or PRI-SIP call on Cisco PGW 2200 Softswitch, with no preferential treatment An MLPP precedence call for which circuit is reserved during preemption can be used by another call before the pre-empting call arrives at Cisco PGW 2200 Softswitch Cisco PGW 2200 Softswitch cannot map the MLPP User Indicator that is received in the ALERTING to SIP in PRI-SIP scenario when generating the ALERTING for SIP-PRI scenarios, Cisco PGW 2200 Softswitch always sends the value as successcalledusernotmlppsubscriber for MLPP calls (the original INVITE has the Resource-Priority header). The UPDATE carrying the Resource-Priority header that is different from the one (if present) in the original INVITE, cannot be relayed in the PRI, and will be ignored. This limitation is because that only SETUP can carry the initial MLPP information. 2

3 Provisioning Tasks Related Documents The MLPP Support for ISUP and SIP Interworking and SIP-to-SIP Transparency feature is related to the MLPP Relay in PRI to SIP/ISUP Interworking feature. The document that contains additional information related to phase 1 of MLPP support on Cisco PGW 2200 Softswitch is available at: html. Supported Standards, MIBs, and RFCs This section identifies the new or modified standards, MIBs, and RFCs that are supported by this feature. Standards Q735.3 MLPP for SS7 Q955.3 MLPP for DSS1 MIBs No new or modified MIBs are supported by this feature. For more information on the MIBs used in the Cisco PGW 2200 Softswitch, see the list of Cisco PGW 2200 Softswitch MIBs at: RFCs RFC4412 Communications Resource Priority for the Session Initiation Protocol RFC4411 Extending the SIP Reason Header for Pre-emption Events Provisioning Tasks This section describes the provisioning tasks for this feature. To use this feature, perform the following task: PGW must be configured at the PRI trunk group level. This means that MlppSupport must be set to 1 on the PRI trunk group. For example: prov-add:trnkgrpprop:name="233", mlppsupport="1" prov-ed:profile:name="sip-prof1", mlppsupport="1" prov-ed:profile:name="sip-prof1", mlppnamespace="q735" prov-add:trnkgrpprop:name="233", mlppni="049" 3

4 Provisioning Examples Provisioning Examples This section provides provisioning examples pertaining to this feature. You can find additional provisioning examples for the Cisco PGW 2200 Softswitch software in the Cisco PGW 2200 Softswitch Software Release 9.8 Provisioning Guide, which is available at: Provisioning Example of MLPP Support for ISUP The following sample MML command establishes MLPP support for ISUP: ; Start a New Provisioning Session prov-sta::srcver="new",dstver="mlpp_isup" ; Add a new dialplan named "1111" numan-add:dialplan:custgrpid="1111", OVERDEC="NO" ;Add OPC/DPC details ;; prov-add:opc:name="stim-opc",desc="stim opc",netaddr="1.1.1",netind=2,type="trueopc" prov-add:dpc:name="stim-dpc",desc="stim dpc",netaddr="1.2.1",netind=2 ;Add ss7 link ;;; prov-add:ss7path:name="ss7path1",desc="ss7 path to stim",mdo="isupv2_german",custgrpid="1111",side="network", DPC="stim-dpc",OPC="stim-opc",M3UAKEY="",ORIGLABEL="",TERMLABEL="" ;Add SLT/STIM details: ;;; prov-add:extnode:name="stim1",desc="ss7 stim",type="slt",isdnsigtype="n/a",group=0 prov-add:sessionset:name="stim-set1",extnode="stim1",ipaddr1="ip_addr1",peeraddr1=" ",PORT=7000,PEERPORT=7000,TYPE="BSMV0" ;Add SS7 Linkset and Links: prov-add:lnkset:name="lkset1",desc="ss7 linkset to stim",apc="stim-dpc",proto="ss7-itu",type="ip" prov-add:ss7route:name="ss7rt1",desc="ss7 route to stim",opc="stim-opc",dpc="stim-dpc",lnkset="lkset1",pri=1 prov-add:c7iplnk:name="c7lnk1",desc="ss7 link to stim",lnkset="lkset1",slc=0,pri=1,timeslot=0,sessionset="stim-set1 ;Add MGCP path: ;; prov-add:extnode:name="mgcp1",desc="mgcp stim",type="as5300",isdnsigtype="n/a",group=0 prov-add:mgcppath:name="stimpath1",desc="mgcp path to pype",extnode="mgcp1" prov-add:iplnk:name="stim-iplnk1",desc="mgcp to pype",svc="stimpath1",ipaddr="ip_addr1",port=2427,peeraddr="10.0.2,21",peerport=2427,pri=1,iproute="" ;Add trunk grp: 4

5 Provisioning Examples ; prov-add:trnkgrp:name="233", svc="ss7path1",type="tdm_isup",selseq="lidl" prov-ed:trnkgrpprop:name="233",custgrpid="1111" ;ADD MLPP support on ISUP trunkgroup ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; prov-ed:trnkgrpprop:name="233",mlppsupport="1",mlppni="049" ;Add Trunk CICS and Endpoints: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; prov-add:switchtrnk:name="1",trnkgrpnum="233",span="ffff",cic=1,cu="mgcp1",spansize=31,end point="s0/ds1-1/1@sh-rusa" prov-add:rttrnkgrp:name="233",type=1,reattempts=1,queuing=0,cutthrough=0,resincperc=0 ;Add Trunk Routes: ;;;;;;;;;;;;;;;;;;;;;; prov-add:rttrnk:weightedtg="off",name="rt233",trnkgrpnum=233 prov-add:rtlist:name="rtlst233",rtname="rt233",distrib="off" numan-add:resultset:custgrpid="1111",name="rset233" numan-add:resulttable:custgrpid="1111",name="rtab1",resulttype="route",dw1="rtlst233",setn ame="rset233 ;Add digitstring to routeset: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="233",setname="rset 233" ; Save the Provisioning Session prov-dply Provisioning Example of MLPP Support for ISDN The following sample MML command establishes MLPP support for ISDN: ; Start a New Provisioning Session prov-sta::srcver="new",dstver="mlpp_isdn" ; Add a new dialplan named "1111" numan-add:dialplan:custgrpid="1111", OVERDEC="NO" ;Add a STIM details ;;;;; prov-add:extnode:name="sh ",desc=" for MGCP",TYPE="AS5300",ISDNSIGTYPE="N/A",GROUP=0 ;Add a MGCP PATH prov-add:mgcppath:name="mgcp ",desc="mgcp sh ",extnode="sh " prov-add:sigsvcprop:name="mgcp ",mgcpdomainnameremote="s0/ds1-0/1@sh-rusa" 5

6 Provisioning Examples prov-add:iplnk:name="clink25-1",desc="mgcp link to sh ",svc="mgcp ",ipaddr="ip_addr1",port=2427,peeraddr=" ",peerport=24 27,PRI=1,IPROUTE="" ;Add ISDN DCHAN ;;;;;;;;;;;;;;;;;;;;;;;;;; prov-add:ipfaspath:name="bh25ni2",desc="ni-2 service to AS ",EXTNODE="sh ",MDO="ETS_300_172",CUSTGRPID="1111",SIDE="network",ABFLAG= "n",crlen=2 prov-add:sessionset:name="gw25set",extnode="sh ",ipaddr1="ip_addr1",peeraddr1=" ",port=7007,peerport=7007,type="ipfas" prov-add:dchan:name="ni2dchn1",desc="ip link-backhaul svc NAS ",SVC="bh25ni2",PRI=1,SESSIONSET="gw25set",SIGSLOT=0,SIGPORT=0 ;Add a ISDN trunk grp ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; prov-add:trnkgrp:name="888", CLLI="GW-25-NI2", SVC="bh25ni2",TYPE="TDM_PRI" prov-ed:trnkgrpprop:name="888",custgrpid="1111" prov-add:switchtrnk:name="1", trnkgrpnum="888", span="ffff", cic=1, cu="sh ", spansize=24,endpoint="s0/ds1-0/1@sh-rusa" prov-add:rttrnkgrp:name="888",type=7,reattempts=3,queuing=0,cutthrough=2,resincperc=0 ;ADD MLPP support on ISDN trunkgroup ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; prov-ed:trnkgrpprop:name="888",mlppsupport="1",mlppni="9004" ;Add a Trunk Routes: ;;;;;;;;;;;;;;;;;;;;;;;;;;; prov-add:rttrnk:weightedtg="off",name="rt888",trnkgrpnum=888 prov-add:rtlist:name="rtlist888",rtname="rt888",distrib="off" numan-add:resultset:custgrpid="1111",name="pri-888" numan-add:resulttable:custgrpid="1111",name="result888",resulttype="route", dw1="rtlist888",setname="pri-888" ;Add digitstring to routeset: ;;;;;;;;;;;;;;;;;;;;;;;;;;;;; numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="888",setname="pri- 888" ; Save the Provisioning Session prov-dply Provisioning Example of MLPP Support for SIP The following sample MML command establishes MLPP support for SIP: ; Start a New Provisioning Session prov-sta::srcver="new",dstver="mlpp_sip" ; Add a new dialplan named "1111" numan-add:dialplan:custgrpid="1111", OVERDEC="NO" 6

7 Provisioning Examples ; Add a SIP Signaling Path prov-add:sippath:name="sip-path",desc="sipsigpath",mdo="ietf_sip",origlabel="", TERMLABEL="" prov-add:siplnk:name="sip-link1",desc="siplink",svc="sip-path",ipaddr="ip_addr1", PORT=5060,PRI=1 prov-add:trnkgrp:name="100",clli="sipin-path",svc="sip-path",type="sip_in",selseq="lidl", qable="n",default=1 prov-add:profile:name="sip-prof1",type="sipprofile",custgrpid="1111",mgcdomain=" " prov-add:trnkgrpprof:name="100",profile="sip-prof1" ; Add SIP Trunk Groups prov-add:trnkgrp:name="235",clli="sip-path",svc="sip-path",type="ip_sip",selseq="lidl", qable="n" prov-add:trnkgrpprof:name="235",profile="sip-prof1" prov-add:siprttrnkgrp:name="235",url=" ",srvrr=0,sipproxyport=5060,version="2.0", cutthrough=1,extsupport=1,domainbasedrtgsupport=0 prov-add:rttrnk:weightedtg="off",name="rg235",trnkgrpnum=235 prov-add:rtlist:name="rlst235",rtname="rg235",distrib="off" ; Dial plan routing to SIP side numan-add:resultset:custgrpid="1111",name="rset235" numan-add:resulttable:custgrpid="1111",name="rtab235",resulttype="route",dw1="rlst235", setname="rset235" numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="235", setname="rset235" ; Save the Provisioning Session prov-dply Provisioning Example of MLPP Support This section provides a provisioning example for the MLPP support feature. ; Start a New Provisioning Session prov-sta::srcver="new",dstver="mlpp-prov-sip" ; Add a new dialplan named "1111" numan-add:dialplan:custgrpid="1111", OVERDEC="NO" ; Add a SIP Signaling Path prov-add:sippath:name="sip-path",desc="sipsigpath",mdo="ietf_sip",origlabel="", TERMLABEL="" prov-add:siplnk:name="sip-link1",desc="siplink",svc="sip-path",ipaddr="ip_addr1", PORT=5060,PRI=1 prov-add:trnkgrp:name="100",clli="sipin-path",svc="sip-path",type="sip_in",selseq="lidl", qable="n",default=1 prov-add:profile:name="sip-prof1",type="sipprofile",custgrpid="1111",mgcdomain=" ",,mlppnamespace="q735",mlppsupport="1" prov-add:trnkgrpprof:name="100",profile="sip-prof1" ; Add SIP Trunk Groups prov-add:trnkgrp:name="235",clli="sip-path",svc="sip-path",type="ip_sip",selseq="lidl", qable="n" prov-add:trnkgrpprof:name="235",profile="sip-prof1" prov-add:siprttrnkgrp:name="235",url=" ",srvrr=0,sipproxyport=5060,version="2.0", cutthrough=1,extsupport=1,domainbasedrtgsupport=0 prov-add:rttrnk:weightedtg="off",name="rg235",trnkgrpnum=235 7

8 Obtaining Documentation and Submitting a Service Request prov-add:rtlist:name="rlst235",rtname="rg235",distrib="off" ; Dial plan routing to SIP side numan-add:resultset:custgrpid="1111",name="rset235" numan-add:resulttable:custgrpid="1111",name="rtab235",resulttype="route",dw1="rlst235", setname="rset235" numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="235", setname="rset235" ; Save the Provisioning Session prov-dply Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: Subscribe to the What s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0. Glossary Table 1 provides a list of acronyms used in this document, and their expansions. Table 1 Acronym ISDN ISUP LFB MGC MLPP PGW PRI PSTN SIP Expansions Expansion Integrated Services Digital Network ISDN User Part Look Ahead for Busy Cisco Media Gateway Controller MultiLevel Precedence and Preemption PSTN Gateway Primary Rate Interface Public Switched Telephony Network Session Initiation Protocol Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) 8

9 Glossary Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental Cisco Systems, Inc. All rights reserved. 9

10 Glossary 10