Guest

Cisco PGW 2200 Softswitch

Support of PAID Tel URI Feature Module

  • Viewing Options

  • PDF (127.9 KB)
  • Feedback
Support of PAID Tel URI Feature Module

Table Of Contents

Support of PAID Tel URI Feature Module

Feature Description

Benefits

Prerequisites

Restrictions or Limitations

Related Documents

Supported Standards, MIBs, and RFCs

Provisioning Tasks

Enable the Support of Tel URI

Provisioning Examples

Software Changes for This Feature

Properties

New Properties

Obtaining Documentation and Submitting a Service Request

Glossary


Support of PAID Tel URI Feature Module


Document Release History

Publication Date
Comments

August 23, 2010

Initial release of document.


Feature History

Release
Modification

9.8(1)

The Support of PAID Tel URI feature is introduced on the Cisco PGW 2200 Softswitch software.


This document describes the Support of PAID Tel URI feature. This feature is described in the following sections:

Feature Description

Supported Standards, MIBs, and RFCs

Provisioning Tasks

Provisioning Examples

Software Changes for This Feature

Obtaining Documentation and Submitting a Service Request

Glossary

Feature Description

The Support of PAID Tel URI feature enables the Cisco PGW 2200 Softswitch to parse the Telephone Uniform Resource Identifier (tel URI) information, and pass it from the P-Asserted-Identity (PAID) header to Calling Line Identification (CLI) of ISUP message.

Before this feature, when the Cisco PGW 2200 Softswitch received a PAID header from SIP, it stored the SIP URI of the PAID and used it to build the calling party number. Tel URI in PAID header was ignored.

With this feature, when both tel URI and SIP URI are present in the message, the Cisco PGW 2200 Softswitch uses the tel URI in preference to SIP URI. If a SIP INVITE message contains multiple PAID headers, the Cisco PGW 2200 Softswitch uses the first Tel URI of PAID header.

The following examples shows an incoming PAID header with tel URI:

P-Asserted-Identity: "ego ego"<tel:+4533591161>

The Cisco PGW 2200 Softswitch does not support the instance where other parameters are present in the tel URI. For example, PGW does not support the following type of Tel URI in PAID:

tel: +1-800-234-5678;cic=2345

The Support of PAID Tel URI feature addresses the support of tel URI in PAID header for SIP-to-ISUP calls and ISUP-to-SIP calls. All the variants of ISUP and the protocols that use ISUP, including EISUP, are supported. This feature is not applicable to SIP-SIP calls. That is, in SIP-SIP calls, tel URI is not passed to the other SIP side or terminating SIP side. Except for the URI, no other parameters are supported for this feature. The Cisco PGW 2200 Softswitch does not support Tel URI of any form in any of the SIP headers.

Benefits

This feature provides the following benefits:

Enables the Cisco PGW 2200 Softswitch to parse tel URI in PAID for SIP-ISUP call flow.

Enables the Cisco PGW 2200 Softswitch to map tel URI instead of SIP URI to the calling party number on the ISUP side.

Prerequisites

The Cisco PGW 2200 Softswitch must be running software Release 9.8(1). Prerequisites for this release can be found in Release Notes for the Cisco PGW 2200 Softswitch Release 9.8(1) at:

http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/release/note/rn981.html

Restrictions or Limitations

The Support of PAID Tel URI feature has the following limitations:

This feature does not apply to SIP-SIP calls. It is only effective for the SIP-ISUP calls. For the SIP-to-SIP call, the PAID header with tel URI is removed. The other part of the SIP INVITE message is forwarded transparently to the other side.

The Cisco PGW 2200 Softswitch does not support any additional parameters in tel URI.

Related Documents

This document contains information that is strictly related to this feature. The documents that contain additional information related to the Cisco PGW 2200 Softswitch can be found at:

http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html

Supported Standards, MIBs, and RFCs

This section identifies the new or modified standards, MIBs, and RFCs that are supported by this feature.

Standards

No new or modified standards are supported by this feature.

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 Cisco PGW 2200 Softswitch MIBs at:

http://www.cisco.com/iam/PGW_MIBS/index.html

RFCs

This feature is in compliance with the following RFC:

RFC 3966—The tel URI for Telephone Numbers

Provisioning Tasks

This section describes provisioning tasks for this feature.

To use this feature, you need to perform the following task:

Enable the Support of Tel URI

For the complete provisioning examples, see the "Provisioning Examples" section.

Enable the Support of Tel URI

To enable the support of tel URI in PAID, use the following commands to provision the SupportTelURIinPAID property to the SIP profile:

mml> prov-add:profile:name="sip-prof1",type="SIPPROFILE",custgrpid="1111", 
mgcdomain="10.78.170.33"
mml> prov-ed:profile:name="sip-prof1",SupportTelURIinPAID="1"

Provisioning Examples

This section provides a provisioning example for this feature. Additional provisioning examples for the Cisco PGW 2200 Softswitch can be found in Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide. Additional dial plan examples for the Cisco PGW 2200 Softswitch can be found in Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide.

________________________________________
; Start a New Provisioning Session
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-sta::srcver="new",dstver="paid-prov"

________________________________________
; Add a new dialplan named "1111"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:dialplan:custgrpid="1111",overdec="NO"

________________________________________
; Add OPC, DPC, and External Nodes (ITP)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
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
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="10.0.2.240",PORT=7000,PEERPORT=7000,TYPE="BSMV0"

________________________________________
;Add an SS7 Signaling Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7PATH:NAME="ss7path1",DESC="ss7 path to stim",MDO="Q761_BASE",CUSTGRPID="1111", 
SIDE="network",DPC="stim-dpc",OPC="stim-opc",M3UAKEY="",ORIGLABEL="",TERMLABEL=""
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 an External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
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.246",PEERPORT=2427,PRI=1,IPROUTE=""

________________________________________
; Add an SS7 Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrp:name="233",svc="ss7path1",type="TDM_ISUP",SELSEQ="LIDL"
prov-ed:trnkgrpprop:name="233",custgrpid="1111"

________________________________________
; Add Trunks and Route List
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:switchtrnk:name="1",trnkgrpnum="233",span="ffff",cic=1,cu="mgcp1",spansize=31, 
endpoint="s0/ds1-1/1@sh-rusa"
prov-add:rttrnkgrp:name="233",type=1,reattempts=1,queuing=0,cutthrough=0,resincperc=0
prov-add:rttrnk:weightedTG="OFF",name="rt233",trnkgrpnum=233
prov-add:rtlist:name="rtlst233",rtname="rt233",distrib="OFF"


________________________________________
; 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"
prov-add:profile:name="sip-prof1",type="SIPPROFILE",custgrpid="1111",mgcdomain="10.0.3.4"
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="10.0.2.91",srvrr=0,sipproxyport=5060,version="2.0", 
cutthrough=1,extsupport=1
prov-add:rttrnk:weightedTG="OFF",name="rg235",trnkgrpnum=235
prov-add:rtlist:name="rlst235",rtname="rg235",distrib="OFF"

________________________________________
; Provision the Trunk Group profile for SupportTelURIinPAID
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sip-prof1",SupportTelURIinPAID=1

________________________________________
; Dial Plan Routing to SS7 Side
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resultset:custgrpid="1111",name="rset233"
numan-add:resulttable:custgrpid="1111",name="rtab1",resulttype="ROUTE",dw1="rtlst233", 
setname="rset233"
numan-add:bdigtree:custgrpid="1111",callside="originating",digitstring="233", 
setname="rset233"

________________________________________
; 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

Software Changes for This Feature

The following section contains software changes related to this feature:

Properties

Properties

This section describes the new property for this feature. For more information on the other properties, see Cisco PGW 2200 Softswitch Release 9 MML Command Reference.

New Properties

Table 1 describes the new property for this feature.

Table 1 New Property for the Support of PAID Tel URI Feature 

Property
Description

SupportTelURIinPAID

SIP profile property. Indicates whether the Cisco PGW 2200 Softswitch supports tel URI in PAID header. When the SupportTelURIinPAID property is set to 0 on the sip profile, the PAID will not be passed in the IAM as CLI. When this property is set to 1 on the sip profile, the PAID information will be passed in the IAM as CLI.

Valid values:

0—Disable

1—Enable

Default value: 0.


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:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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 2 Expansions 

Acronym
Expansion

CLI

Calling Line Identification

ISUP

ISDN User Part

MML

Man-Machine Language

PAID

P-Asserted-Identity

PGW

PSTN Gateway

SIP

Session Initiation Protocol

Tel URI

Telephone Uniform Resource Identifier