SIP-I Protocol Feature Module
Document Release History
Publication Date
Comments
July 2009
Added mapping details from the ISUP connected number parameter to the
SIP P-Asserted-Identity header.
February 2009
Updated for the Russian SIP-I support.
November 2008
Initial release of document.
Feature History
Release
Modification
9.8(1)
Added support for Russian SIP-I.
9.8(1)
The SIP-I Protocol feature was introduced on the
Cisco PGW 2200 Softswitch.
This document describes the SIP-I Protocol feature and includes the following sections:
•
Feature Overview, page 2
•
Supported Standards, MIBs, and RFCs, page 6
•
Provisioning Tasks, page 6
•
Provisioning Examples, page 13
•
MML Command Reference, page 15
•
Software Changes for This Feature, page 17
•
Troubleshooting the Feature, page 27
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page 31
•
Mapping Details, page 31
•
Glossary, page 37
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2008–2009 Cisco Systems, Inc. All rights reserved.
SIP-I Protocol Feature Module
Feature Overview
Feature Overview
SIP-I (SIP with encapsulated ISUP) is an ITU-defined SIP extension which allows IP networks to
provide services that are supported by ISUP networks, for example, malicious call identification. The
feature allows the Cisco PGW 2200 Softswitch to interwork between SIP-I and ISUP, and also to
interwork between SIP-I and other protocols such as SIP, H.323, PRI, and QSIG. Where PSTN services
are required in IP networks, SIP trunks with SIP-I support can be the preferred method for supplying
these services, because the ISUP content is encapsulated in SIP message headers.
The SIP-I Protocol feature is useful in a next-generation network (NGN) emulation model, where the
Cisco PGW 2200 Softswitch, working with the Cisco BTS 10200 Class 5 softswitch in a SIP solution,
communicates with other NGNs using SIP-I. This new feature is also useful for bridging existing PSTN
networks without TDM interconnections being required.
This feature introduces a SIP-I interface license. For more information about the SIP-I interface license
on the Cisco PGW 2200 Softswitch, see the Licensing Features for the Cisco PGW 2200 Softswitch at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/9.7_3_/FlexLM.html
See the following lists of ISUP services interworking and transmitting with SIP-I on the
Cisco PGW 2200 Softswitch.
Supported ISUP Services Interworking with SIP-I (Profile C)/SIP (Profile B)
•
Malicious Call Identification (MCID)(SIP-I only)
•
Call Diversion (CFB, CFNR, CFU, CD)
•
Connected Line Presentation and Restriction (COLP/COLR)
•
Calling Line Presentation and Restriction (CLIP/CLIR)
•
Number Portability (NP)
•
Call Hold (HOLD)
•
Terminal Portability (TP)
•
B-controlled Release (CCL) (for Russian SIP-I only)
•
Call Offering (ACM/SUS/RNG) (for Russian SIP-I only)
Supported ISUP Services Transiting with SIP-I
•
SUB-addressing (SUB)
•
Malicious Call Identification (MCID)
•
Call Waiting (CW)
•
Call Diversion (CFB, CFNR, CFU, CD)
•
Conference Calling (CONF)
•
Three Party (3PTY)
•
Explicit Call Transfer (ECT)
•
User-to-User Service (UUS)
•
Direct-Dialling-In (DDI)
•
Connected Line Presentation and Restriction (COLP/COLR)
•
Calling Line Presentation and Restriction (CLIP/CLIR)
•
Completion of Calls to Busy Subscriber (CCBS)
SIP-I Protocol Support
2
SIP-I Protocol Feature Module
Feature Overview
•
Number Portability (NP)
Figure 1 shows how service providers interwork the ISUP services using this SIP-I Protocol feature. In
this figure, PGW B interconnects different ISUP variants and other protocols like ISDN, DPNSS, and
EISUP on the SIP trunk with SIP-I support.
ANSI
ISUP
UK
ISUP
GERMAN
ISUP
FINNISH
ISUP
RUSSIAN
ISUP
Interworking Between Service Providers with SIP-I
MGC A
MGC B
MGC C
MGC D
SIP-I
version=ansi00
base=ansi00
SIP-I
version=isupv3-uk
base=etsi356
SIP-I
version=q761german
base=itu92+
SIP-I
version=isupv2-finnish96
base=etsi356
SIP-I
version=Q761_97VER_RUSS
base=itu92+
MGC E
EISUP
PGW B
ANSI
UK
ISUP
UK
GERMAN
ISUP
GERMAN
FINNISH
ISUP
FINNISH
RUSSIAN
ISUP
RUSSIAN
ISDN
ISDN
SIP/SIP-I
/SIP-GTD
SIP
DPNSS
ISDN
DPNSS
5060
ANSI
ISUP
SIP/SIP-I
/SIP-GTD
DPNSS
EISUP
EISUP
PGW A
EISUP
HSI(EISUP)
280871
Figure 1
Figure 2 shows the SIP-I being used on multiple incoming SIP trunk groups. In this figure,
Cisco PGW 2200 Softswitches interwork ISUP variants, ISDN, SIP, HSI (EISUP), DPNSS, and EISUP
using multiple incoming SIP trunk groups on which different SIP-I versions are provisioned. PGW A
interworks TDM, SIP, and H.323 protocols to SIP-I. PGW B interconnects SIP-I variants to the TDM,
SIP, and H.323 protocols on multiple incoming SIP trunk groups with SIP-I support.
SIP-I Protocol Support
3
SIP-I Protocol Feature Module
Feature Overview
Figure 2
SIP-I Used on Multiple Incoming SIP Trunk Groups
Route
ANSI
ISUP
UK
UK
ISUP
GERMAN
GERMAN
ISUP
FINNISH
FINNISH
ISUP
RUSSIAN
RUSSIAN
ISUP
ISDN
SIP
DPNSS
EISUP
ISDN
SIP/SIP-I
/SIP-GTD
DPNSS
SIP-I
6060
version=ansi00
base=ansi00
SIP-I
7060
version=isupv3-uk
base=etsi356
PGW
A
SIP-I
8060
version=q761german
base=itu92+
SIP-I
9060
version=isupv2-finnish96
base=etsi356
SIP-I
4060
version=Q761_97VER_RUSS
base=itu92+
PGW
B
ANSI
ISUP
ANSI
UK
ISUP
UK
GERMAN
ISUP
GERMAN
FINNISH
ISUP
FINNISH
RUSSIAN
ISUP
RUSSIAN
ISDN
SIP/SIP-I
/SIP-GTD
DPNSS
EISUP
EISUP
ISDN
SIP
DPNSS
EISUP
5060
HSI(EISUP)
EISUP
SIP
EISUP
HSI(EISUP)
280872
ANSI
Figure 3 shows the SIP-I being used on a single incoming SIP trunk group. In this figure,
Cisco PGW 2200 Softswitches interwork ISUP variants, ISDN, SIP, HSI (EISUP), DPNSS, and EISUP
using a single incoming SIP trunk group which has SIP-I support. This single incoming SIP trunk group
of PGW B dynamically adapts to the incoming SIP-I message version.
SIP-I Protocol Support
4
SIP-I Protocol Feature Module
Feature Overview
Figure 3
SIP-I Used on a Single Incoming SIP Trunk Group
Route
ANSI
ANSI
ISUP
UK
UK
ISUP
GERMAN
GERMAN
ISUP
FINNISH
FINNISH
ISUP
RUSSIAN
ISDN
SIP
DPNSS
EISUP
ISDN
SIP/SIP-I
/SIP-GTD
DPNSS
EISUP
EISUP
SIP-I
version=isupv3-uk
base=etsi356
PGW
A
5060
SIP-I
version=q761german
base=itu92+
SIP
SIP-I
version=isupv2-finnish96
base=etsi356
SIP-I
version=Q761_97VER_RUSS
base=itu92+
PGW
B
ANSI
UK
ISUP
UK
GERMAN
ISUP
GERMAN
FINNISH
ISUP
FINNISH
RUSSIAN
ISUP
RUSSIAN
ISDN
ISDN
SIP/SIP-I
/SIP-GTD
SIP
DPNSS
DPNSS
EISUP
EISUP
EISUP
HSI(EISUP)
280874
HSI(EISUP)
RUSSIAN
ISUP
SIP-I
version=ansi00
base=ansi00
ANSI
ISUP
Benefits
The feature allows service providers to offer a complete VoIP interconnection which can handle PSTN
services that the traditional TDM ISUP interconnection supports. Among all the IP interconnection
forms (such as SIP, SIP-I, and H.323), SIP-I interconnections can be the destination of choice if service
providers require PSTN service interworking.
The Cisco PGW 2200 Softswitch supports ITU, ANSI, German, UK, Finnish, and Russian ISUP
encapsulated in SIP-I messages, which allows a high degree of interworking for many services across a
SIP-I configured link.You can provision the closest base or the closest country-specific SIP-I variant if
you are using SIP-I for other ISUP variants. The service interoperability level between SIP-I and other
protocols such as SIP, H.323, PRI, and QSIG, is lower than the interoperability level between SIP-I and
ISUP, but is nearly equivalent to the interoperability level between those protocols and ISUP today.
Prerequisites
The Cisco PGW 2200 Softswitch must be running Cisco PGW 2200 Softswitch software Release 9.8(1).
Prerequisites for this release can be found in the Release Notes for Cisco PGW 2200 Softswitch
Release 9.8(1) at
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/pgw/9/release/note/rn981.html.
SIP-I Protocol Support
5
SIP-I Protocol Feature Module
Provisioning Tasks
Restrictions or Limitations
The SIP-I Protocol feature has the following limitations:
•
Currently the Cisco PGW 2200 Softswitch does not support SIP precondition (the ability to require
that the SIP participant reserve network resources before continuing with the session).
•
Currently the Cisco PGW 2200 Softswitch supports only en-bloc signaling on the SIP side for SIP-I.
The Cisco PGW 2200 Softswitch supports overlap signaling on the TDM ISUP side.
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 are at
http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html.
Supported Standards, MIBs, and RFCs
Standards
This feature is in compliance with the following standards:
•
ITU-T Recommendation Q.1912.5 (2004) Interworking between Session Initiation Protocol (SIP)
and ISDN User Part
•
ETSI EN 383 001: Telecommunications and Internet Converged Services and Protocols for
Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and ISDN
User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]
•
T1.679-2004: Interworking between Session Initiation Protocol (SIP) and ISDN User Part
•
ND1017-2006: Interworking between Session Initiation Protocol (SIP) and UK ISDN User Part (UK
ISUP)
•
Ficora GFI 0301: Guidelines for Implementation ISUP-SIP Interworking Profile C (Finland ISUP)
MIBs
No new or modified MIBs are introduced by this feature.
For more information on the MIBs used in the Cisco PGW 2200 Softswitch software, see the
Cisco PGW 2200 Softswitch Release 9 Management Information Base Guide at the following URL.
http://www.cisco.com/iam/PGW_MIBS/index.html
Provisioning Tasks
This section describes how to provision this feature and includes four parts:
•
Provisioning an Incoming SIP Trunk Group, page 7
•
Provisioning an Outgoing SIP Trunk Group, page 9
•
Enabling the Route Preference, page 11
•
Additional Provisioning for Finnish SIP-I, page 11
SIP-I Protocol Support
6
SIP-I Protocol Feature Module
Provisioning Tasks
Provisioning an Incoming SIP Trunk Group
SIP-I Version Name and ISUP Variant Mapping
The Cisco PGW 2200 Softswitch uses the version subparameter in the Content-Type header of a SIP-I
INVITE message to identify SIP-I variants. In order to specify the SIP-I variants supported on the
incoming trunk groups, you can add a file, sipIVersion.dat, through MML commands, and associate it
with the incoming trunk group SIP profiles. The following provisioning example is applicable to specific
networks.
Add Mapping Entries in sipIVersion.dat File
prov-add:sipiversion:profilename="BT",version="X-UKISUP",mdo="ISUPV3_UK_SIPI"
prov-add:sipiversion:profilename="BT",version="etsi356",mdo="ISUPV3_UK_SIPI"
prov-add:sipiversion:profilename="BT",version="itu-t92+",mdo="Q761_99VER_BASE_SIPI"
prov-add:sipiversion:profilename="US",version="itu-t92+",mdo="Q761_99VER_BASE_SIPI"
prov-add:sipiversion:profilename="US",version="ansi00",mdo="ANSISS7_STANDARD_SIPI"
prov-add:sipiversion:profilename="GERMAN",version="isupv2-german",mdo="ISUPV2_GERMAN_SIPI"
prov-add:sipiversion:profilename="FINNISH",version="isupv2-finnish96",mdo="ISUPV2_FINNISH9
6_SIPI"
prov-add:sipiversion:profilename="RUSSIAN",version="Q761_97VER_RUSS",mdo="Q761_97VER_RUSS_
SIPI"
The commands listed in the preceding example generate the following SIP-I mapping table.
SIP-I Mapping Profile
Name
SIP-I Version in Content-Type
SIP-I Variant
BT
X-UKISUP
ISUPV3_UK_SIPI
BT
etsi356
ISUPV3_UK_SIPI
BT
itu-t92+
Q761_99VER_BASE_SIPI
US
itu-t92+
Q761_99VER_BASE_SIPI
US
asnsi00
ANSISS7_STANDARD_SIPI
GERMAN
isupv2-german
ISUPV2_GERMAN_SIPI
FINNISH
isupv2-finnish96
ISUPV2_FINNISH96_SIPI
RUSSIAN
Q761_97VER_RUSS
Q761_97VER_RUSS_SIPI
Edit a Mapping Entry
prov-ed:sipiversion:profilename="BT",version="etsi356",mdo="ISUPV3_UK_SIPI"
Retrieve a Mapping Entry
prov-rtrv:sipiversion:profilename="BT",version="etsi356"
Delete a Mapping Entry
prov-dlt:sipiversion:profilename="BT",version="etsi356"
SIP-I Protocol Support
7
SIP-I Protocol Feature Module
Provisioning Tasks
Add a SIP Profile
prov-add:profile:name="sipi-in",type="SIPPROFILE",sipmimebodysupport="4"
Note
To support both SIP and SIP-I on the incoming trunk group and support SIP-I on the outgoing trunk
group, the Cisco PGW 2200 Softswitch requires the property sipMimeBodySupport to be set to 4.
For detailed property information, see the “Properties” section on page 18.
Attach the SIP-I Mapping Profile to the SIP Profile
prov-ed:profile:name="sipi-in",sipiingressversionmap="BT"
Note
You attach the SIP-I mapping profile BT to the SIP profile sipi-in by the preceding command. According
to the preceding SIP-I mapping table, the incoming trunk group supports three SIP-I versions of the SIP-I
mapping profile BT in Content-Type of the SIP-I messages.
(Optional) Attach the ISUP TMR Profile to the SIP Profile
prov-add:profile:name="isup01",type="ISUPTMRPROFILE",t6="120000",
variant="etsi356",t2="180000",t9="60000",t33="12000",validation="OFF"
prov-ed:profile:name="sipi-in",isuptmrprofile="isup01"
Attach the SIP Profile to the Trunk Group
prov-add:trnkgrpprof:name=”2000”,profile=”sipi-in”
Incoming SIP-I Message Processing
Figure 4 shows how Cisco PGW 2200 Softswitch starts a SIP-I variant to process a specific SIP-I
message on the incoming SIP trunk group based on your provisioning. From the source IP of the
incoming SIP-I message, Cisco PGW 2200 Softswitch selects the trunk group 2000. With the selected
trunk group, Cisco PGW 2200 Softswitch selects a SIP-I mapping profile according to the value of the
property sipMimeBodaySupport and the property SipIIngressVersionMap. Based on the selected SIP-I
mapping profile and the Content-Type field in the SIP-I message, Cisco PGW 2200 Softswitch starts
ISUPV3_UK_SIPI as the SIP-I variant to process the incoming SIP-I message.
SIP-I Protocol Support
8
SIP-I Protocol Feature Module
Provisioning Tasks
Figure 4
Processing SIP-I Messages on the Incoming SIP Trunk Group
1
Source IP Listening Trunk
Port
Group
10.0.5.1
5060
2000
10.0.5.2
5060
3000
10.0.6.1
5060
4000
10.0.6.2
5060
5000
2
IP 10.0.5.1
INVITE
Content-Type:
application/isup;
version=etsi356;
base=etsi356
3B
Encapsulated ISUP
Message IAM
Trunk
Group
2000
sipMimeBodySupport
SiplingressVersionMap
4
BT
3000
3 or 4
GERMAN
4000
3 or 4
GERMAN
5000
3 or 4
GERMAN
3A
SIP-I
Variant
BT
X-UKISUP
ISUPV3_UK_SIPI
BT
etsi356
ISUPV3_UK_SIPI
BT
itu-t92
Q761_99VER_BASE_SIPI
US
itu-t92
Q761_99VER_BASE_SIPI
4
Decode
encapsulated
ISUP message as
ISUPV3_UK
280851
SIP-I
SIP-I
Mapping Version
Profile
Provisioning an Outgoing SIP Trunk Group
Add a SIP Profile
prov-add:profile:name="sipi-out",type="SIPPROFILE",sipmimebodaysupport="4"
Note
To support both SIP and SIP-I on the incoming trunk group and support SIP-I on the outgoing trunk
group, the Cisco PGW 2200 Softswitch requires the property sipMimeBodySupport to be set to 4.
For detailed property information, see the “Properties” section on page 18.
Provision the SIP-I Version on the SIP Profile
prov-ed:profile:name="sipi-out",sipiegressisupversion="isupv2-german"
Provision the SIP-I Variant on the SIP Profile
prov-ed:profile:name="sipi-out",sipiegressmdo="ISUPV2_GERMAN_SIPI"
SIP-I Protocol Support
9
SIP-I Protocol Feature Module
Provisioning Tasks
Provision the Handling Property on the SIP Profile
prov-ed:profile:name="sipi-out",sipiegresshandling="2"
Note
To always add “handling=required” to the Content-Disposition header of the INVITE message, the
Cisco PGW 2200 Softswitch requires the property SipIEgressHandling to be set to 2.
For detailed property information, see “Properties” section on page 18.
(Optional) Provision the SipICANCELEncapREL Property on the SIP Profile
To make the encapsulated REL message required in the SIP-I CANCEL message, you need to provision
the SipICANCELEncapREL property as follows:
prov-ed:profile:name="sipi-out",sipicancelencaprel="1"
(Optional) Attach the ISUP TMR Profile to the SIP Profile
prov-add:profile:name="isup02",type="ISUPTMRPROFILE",t6="120000",variant="isupv2-german",t
2="180000",t9="60000",t33="12000",validation="OFF"
prov-ed:profile:name="sipi-out",isuptmrprofile="isup02"
Attach the SIP Profile to the Trunk Group
prov-add:trnkgrpprof:name="3000",profile="sipi-out"
Outgoing SIP-I Message Processing
Figure 5 shows how Cisco PGW 2200 Softswitch transforms the incoming ISUP messages to the
outgoing SIP-I messages if the route preference is enabled. The Cisco PGW 2200 Softswitch selects a
route from the route analysis after a German ISUP initial address message (IAM) comes in. If the route
preference is enabled, Cisco PGW 2200 Softswitch selects the trunk group 3000 based on the trunk
group property SipIEgressMDO. The other trunk group properties, sipMimeBodySupport,
SipIEgressHandling, and SipIEgressISUPVersion, determine the content of SIP-I header fields in the
outgoing SIP-I messages.
Note
If the route preference is not enabled, Cisco PGW 2200 Softswitch selects an outgoing trunk group in
the route as the result of the route analysis. The trunk group property SipIEgressHandling provisioned
on this trunk group determines the content of SIP-I header fields in the outgoing SIP-I messages.
SIP-I Protocol Support
10
SIP-I Protocol Feature Module
Provisioning Tasks
Processing SIP-I Messages on the Outgoing SIP Trunk Group
Trunk
Group
3000
sipMimeBodySupport
SipIEgressMDO
4
ISUPV2_GERMAN_SIPI isupv2-german
2
4000
3 or 4
ISUPV3_UK_SIPI
X-UKISUP
1
5000
3 or 4
ISUPV3_UK_SIPI
etsi356
2
3
PGW
UK
ISUP
INVITE
TG 3000
GERMAN
ISUP
1
SipIEgressHandling
4
ANSI
ISUP
IAM
SipIEgressISUPVersion
TG 4000
2
TG 5000
SIP-I
Processor
SIP-I Message
Route List
5
Content-Type:
application/isup;
version=isupv2-german;
base=etsi356
Content-Disposition:
signal; handling=required
280873
Figure 5
Encapsulated ISUP
Message IAM
Enabling the Route Preference
numan-add:resulttable:custgrpid="1000",setname="set-7",name="rp",resulttype="SIPI_CONTROL"
,dw1="1"
Note
SIPI_CONTROL is a new result type introduced in this feature. To enable the SIP-I route preference, the
Cisco PGW 2200 Softswitch requires the dw1 to be set to 1.
It is possible to configure the Cisco PGW 2200 Softswitch so that, for calls between ISUP and SIP
trunks with SIP-I supported, the Cisco PGW 2200 Softswitch tries to route the calls using the SIP trunk
on which the corresponding SIP-I variant is available to match the ISUP trunk. Use the SIPI_CONTROL
result type in dial plans to achieve this.
For detailed information on this result type, see the “Result Type Definitions” section on page 26. For
detailed information on the dial plan, see the Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/dial_plan/guide/dplan.html.
Additional Provisioning for Finnish SIP-I
Finnish SIP-I has some specific message requirements which require additional provisioning:
•
Add Meter Pulse Message Support, page 12
•
Give ISUP Encapsulation Priority over SIP Headers, page 12
•
Map the Cause Code, page 12
•
Stop the Hop Counter and Satellite Indicator From Increasing, page 12
•
Set Calling Party Number (CgPN) APRI to Presentation Restricted, page 13
SIP-I Protocol Support
11
SIP-I Protocol Feature Module
Provisioning Tasks
Add Meter Pulse Message Support
Currently the Cisco PGW 2200 Softswitch supports meter pulse message (MPM) which is required in
Finnish ISUP. Finnish SIP-I encapsulates MPMs in INFO messages in order to interwork this Finnish
ISUP service among service providers. For details on provisioning MPM support for Finnish ISUP on
the Cisco PGW 2200 Softswitch, see the section, Provisioning Tasks, of the feature guide Meter Pulse
Messages Support at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/9.5_1_/FMmpm.html.
Give ISUP Encapsulation Priority over SIP Headers
Finnish SIP-I requires that within an incoming SIP-I message, the parameters in the encapsulated ISUP
message has higher priority over the ones in the SIP header when the device decodes the SIP-I message.
To achieve this on the Cisco PGW 2200 Softswitch, you need to provision the SipICLICOLPreference
property for the SIP profile used for Finnish SIP-I.
prov-ed:profile:name="sipi-in",sipiclicolpreference="1"
Note
To make encapsulated ISUP content has higher priority over SIP headers in the decoding of incoming
SIP-I messages, set the SipICLICOLPreference to 1.
For detailed property information, see “Properties” section on page 18.
Map the Cause Code
According to Ficora GFI 0301: Guidelines for Implementation ISUP-SIP Interworking Profile C
(Finland ISUP), Finnish SIP-I map the cause code 24 to the SIP status code 503 Service Unavailable.
You need to manually map the cause code 24 (internal cause value IC_REJECTED_BY_FEATURE
(169) by default) to 503 Service Unavailable (internal cause value IC_SERVICE_UNAVAIL(209) by
default):
numan-add:resultset:custgrpid="1111",name="cause-set-1"
numan-add:cause:custgrpid="1111",setname="cause-set-1",causevalue= 169
numan-add:resulttable:custgrpid="1111",setname"cause-set-1",name="cause-tbl-1",resulttype=
"CAUSE",dw1=209
Note
For details on the ISUP cause codes and the internal cause codes on the Cisco PGW 2200 Softswitch,
see Appendix B, Cause and Location Codes in Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide
at the following URL.
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/dial_plan/guide/dplan.html
Stop the Hop Counter and Satellite Indicator From Increasing
The hop counter has no value change for an ISUP to Finnish SIP-I call. There is no satellite circuit in
the connection according to the Ficora GFI 0301. If you have provisioned the CircHopCount and the
SatelliteInd properties to other values, you need to set them to default values in the common profile:
prov-add:profile:name="sipicommon",type="COMMONPROFILE",circhopcount="0"
prov-ed:profile:name="sipicommon",satelliteind="0"
SIP-I Protocol Support
12
SIP-I Protocol Feature Module
Provisioning Examples
prov-ed:profile:name="sipi-in",commonprofile="sipicommon" (using Finnish SIP-I on incoming
trunks)
or
prov-ed:profile:name="sipi-out",commonprofile="sipicommon"(using Finnish SIP-I on outgoing
trunks)
Set Calling Party Number (CgPN) APRI to Presentation Restricted
Finnish SIP-I requires the CgPN APRI be set to presentation restricted.
prov-ed:profile:name="sipi-in",restrictpresifnopaid="1"
Provisioning Examples
This section provides a provisioning example for this feature. Additional provisioning examples for the
Cisco PGW 2200 Softswitch software can be found in the Cisco PGW 2200 Softswitch Release 9.8
Provisioning Guide.
________________________________________
; Add SIP-I Mapping Table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sipiversion:profilename="BT",version="X-UKISUP",mdo="ISUPV3_UK_SIPI"
prov-add:sipiversion:profilename="BT",version="etsi356",mdo="ISUPV3_UK_SIPI"
prov-add:sipiversion:profilename="BT",version="itu-t92+",mdo="Q761_99VER_BASE_SIPI"
prov-add:sipiversion:profilename="US",version="itu-t92+",mdo="Q761_99VER_BASE_SIPI"
prov-add:sipiversion:profilename="US",version="ansi00",mdo="ANSISS7_STANDARD_SIPI"
prov-add:sipiversion:profilename="GERMAN",version="isupv2-german",mdo="ISUPV2_GERMAN_SIPI"
prov-add:sipiversion:profilename="FINNISH",version="isupv2-finnish96",mdo="ISUPV2_FINNISH9
6_SIPI"
prov-add:sipiversion:profilename="RUSSIAN",version="Q761_97VER_RUSS",mdo="Q761_97VER_RUSS_
SIPI"
________________________________________
; Add a SIP Profile for the Incoming SIP Trunk Group with SIP-I Support
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:profile:name="sipi-in",type="SIPPROFILE",sipmimebodysupport="4"
________________________________________
; Attach the SIP-I Mapping to the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-in",sipiingressversionmap="BT"
________________________________________
; (Optional) Attach the ISUP TMR Profile to the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:profile:name="isup01",type="ISUPTMRPROFILE",t6="120000",
variant="etsi356",t2="180000",t9="60000",t33="12000",validation="OFF"
prov-ed:profile:name="sipi-in",isuptmrprofile="isup01"
________________________________________
; Attach the SIP Profile to a Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrpprof:name=”2000”,profile=”sipi-in”
________________________________________
; Add a SIP Profile for the Outgoing SIP Trunk Group with SIP-I Support
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:profile:name="sipi-out",type="SIPPROFILE",sipmimebodaysupport="4"
SIP-I Protocol Support
13
SIP-I Protocol Feature Module
Provisioning Examples
________________________________________
; Provision the SIP-I Version on the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-out",sipiegressisupversion="isupv2-german"
________________________________________
; Provision the SIP-I Variant on the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-out",sipiegressmdo="ISUPV2_GERMAN_SIPI"
________________________________________
; Provision the Handling Property on the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-out",sipiegresshandling="2"
________________________________________
; (Optional) Make ISUP REL message encapsulation required in the SIP-I CANCEL message
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-out",sipicancelencaprel="1"
________________________________________
; (Optional) Attach the ISUP TMR Profile to the SIP Profile
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:profile:name="isup02",type="ISUPTMRPROFILE",t6="120000",variant="isupv2-german",t
2="180000",t9="60000",t33="12000",validation="OFF"
prov-ed:profile:name="sipi-out",isuptmrprofile="isup02"
________________________________________
; Attach the SIP Profile to a Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrpprof:name="3000",profile="sipi-out"
________________________________________
; Enable the Route Preference
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resulttable:custgrpid="1000",setname="set-7",name="rp",resulttype="SIPI_CONTROL"
,dw1="1"
________________________________________
; (For Finnish SIP-I Only) Give ISUP Encapsulation Priority over SIP Headers
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-in",sipiclicolpreference="1"
________________________________________
; (For Finnish SIP-I Only) Map the Cause Code
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
numan-add:resultset:custgrpid="1111",name="cause-set-1"
numan-add:cause:custgrpid="1111",setname="cause-set-1",causevalue= 169
numan-add:resulttable:custgrpid="1111",setname"cause-set-1",name="cause-tbl-1",resulttype=
"CAUSE",dw1=209
________________________________________
; (For Finnish SIP-I Only) Set Hop Counter and Satellite Indicator to Default Values
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:profile:name="sipicommon",type="COMMONPROFILE",circhopcount="0"
prov-ed:profile:name="sipicommon",satelliteind="0"
prov-ed:profile:name="sipi-in",commonprofile="sipicommon" (using Finnish SIP-I on incoming
trunks)
or
prov-ed:profile:name="sipi-out",commonprofile="sipicommon"(using Finnish SIP-I on outgoing
trunks)
________________________________________
; (For Finnish SIP-I Only) Set CgPN APRI to Presentation Restricted
SIP-I Protocol Support
14
SIP-I Protocol Feature Module
MML Command Reference
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-ed:profile:name="sipi-in",restrictpresifnopaid="1"
MML Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other
MML commands are documented in the Cisco PGW 2200 Softswitch Release 9 MML Command
Reference at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/command/reference/mmlref_1.html.
New MML Commands
This section contains the MML commands that are new for this feature.
PROV-ADD:SIPIVERSION:PROFILENAME—Add an Entry to the sipIVersion.dat File (Release 9.8(1))
Purpose:
Adds an entry in the sipIVersion.dat file.
Syntax:
prov-add:sipiversion:profilename="SIP-I mapping profile
name",version="SIP-I version in Content-Type",mdo="SIP-I variant name"
Input
Description:
•
PROFILENAME—MML name of a SIP-I mapping profile. This name can be up
to 20 alphanumeric characters in length.
– The name must start with an alphabetic character.
Example:
•
VERSION— SIP-I version defined by the operator and used in the SIP-I message
Content-Type header field. One SIP-I mapping profile can have more than one
SIP-I version defined on the Cisco PGW 2200 Softswitch. This parameter value
can be up to 128 characters in length.
•
MDO—SIP-I variant name mapped to the SIP-I message ParamContent field.
This name can be up to 40 alphanumeric characters.
The MML command shown in the following example adds a mapping from SIP-I
version X-UKISUP to SIP-I variant ISUPV3_UK_SIPI in the SIP-I mapping profile
BT:
mml>prov-add:sipiversion:profilename="BT",version="X-UKISUP",mdo="ISUPV3_
UK_SIPI"
Comments:
Performance Impact Category: A
SIP-I Protocol Support
15
SIP-I Protocol Feature Module
MML Command Reference
PROV-ED:SIPIVERSION:PROFILENAME—Edit an Entry in the sipIVersion.dat File (Release 9.8(1))
Purpose:
Edits an entry within a SIP-I mapping profile in the sipIVersion.dat file.
Syntax:
prov-ed:sipiversion:profilename="SIP-I mapping profile
name",version="SIP-I version in Content-Type",mdo="SIP-I variant name"
Input
Description:
•
PROFILENAME—MML name of a SIP-I mapping profile. This name can be up
to 20 alphanumeric characters in length.
– The name must start with an alphabetic character.
Example:
•
VERSION—SIP-I version defined by the operator and used in the SIP-I message
Content-Type field. One SIP-I mapping profile can have more than one SIP-I
version defined on the Cisco PGW 2200 Softswitch. This parameter value can be
up to 128 characters in length.
•
MDO—SIP-I variant name mapped to the SIP-I message ParamContent field.
This name can be up to 40 alphanumeric characters.
The MML command shown in the following example edits the mapping from SIP-I
version “X-UKISUP” to SIP-I variant ISUPV3_UK_SIPI in the SIP-I mapping profile
BT:
mml>prov-ed:sipiversion:profilename="BT",version="X-UKISUP",mdo="ISUPV3_U
K_SIPI"
Comments:
Performance Impact Category: A
PROV-RTRV:SIPIVERSION:PROFILENAME—Retrieve an Entry in the sipIVersion.dat File
(Release 9.8(1))
Purpose:
Displays the information for one entry within a SIP-I mapping profile in the
sipIVersion.dat file.
Syntax:
prov-rtrv:sipiversion:profilename="SIP-I mapping profile
name",version="SIP-I version in Content-Type"
Input
Description:
•
PROFILENAME—MML name of a SIP-I mapping profile. This name can be up
to 20 alphanumeric characters in length.
– The name must start with an alphabetic character.
•
Example:
VERSION—SIP-I version defined by the operator and used in the SIP-I message
Content-Type header field. One SIP-I mapping profile can have more than one
SIP-I version defined on the Cisco PGW 2200 Softswitch. This parameter value
can be up to 128 characters in length.
The MML command shown in the following example displays the information of the
entry for SIP-I version X-UKISUP in the SIP-I mapping profile BT:
mml>prov-rtrv:sipiversion:profilename="BT",version="X-UKISUP"
Comments:
SIP-I Protocol Support
16
Performance Impact Category: A
SIP-I Protocol Feature Module
Software Changes for This Feature
PROV-DLT:SIPIVERSION:PROFILENAME—Delete an Entry in the sipIVersion.dat File (Release 9.8(1))
Purpose:
Deletes an entry within a SIP-I mapping profile in the sipIVersion.dat file.
Syntax:
prov-dlt:sipiversion:profilename="SIP-I mapping profile
name",version="SIP-I version in Content-Type"
Input
Description:
•
PROFILENAME—MML name of a SIP-I mapping profile. This name can be up
to 20 alphanumeric characters in length.
– The name must start with an alphabetic character.
•
Example:
VERSION—SIP-I version defined by the operator and used in the SIP-I message
Content-Type header field. One SIP-I mapping profile can have more than one
SIP-I version defined on the Cisco PGW 2200 Softswitch. This parameter value
can be up to 128 characters in length.
The MML command shown in the following example deletes the mapping for the
SIP-I version X-UKISUP in the SIP-I mapping profile BT:
mml> prov-dlt:sipiversion:profilename="BT",version="X-UKISUP"
Comments:
Performance Impact Category: A
Modified MML Commands
No MML commands are modified for this feature.
Related MML Commands
You need to provision MPM for the Finnish ISUP variant before you use Finnish SIP-I. See the MML
commands for provisioning MPM on the Cisco PGW 2200 Softswitch at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/9.5_1_/FMmpm.html.
Software Changes for This Feature
The following sections contain software changes related to this feature:
•
Alarms, page 17
•
Properties, page 18
•
Result Type Definitions, page 26
Alarms
This section lists the alarms that are added for this feature. For information on the other alarms for the
Cisco PGW 2200 Softswitch software, see the Cisco PGW 2200 Softswitch Release 9 Messages
Reference at
SIP-I Protocol Support
17
SIP-I Protocol Feature Module
Software Changes for This Feature
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/system/message/errmsg.html.
Unsupported SIP-I Call
Description
This alarm is triggered when the Cisco PGW 2200 Softswitch rejects an unsupported SIP-I call.
Severity
Informational (non-service affecting)
Cause
The Cisco PGW 2200 Softswitch raises the alarm in any one of the three following cases:
•
If the property sipMimeBodySupport is set to 3 (only SIP-I supported on the incoming trunk group)
and the Content-Disposition header in the incoming SIP-I message contains “handling=required”,
the Cisco PGW 2200 Softswitch cannot find any matched SIP-I mapping profile or version entry in
the configuration.
•
The property sipMimeBodySupport is set to 0 (only SIP supported on the incoming trunk group),
and the Content-Disposition header in the incoming SIP-I message contains “handling=required”.
•
If the property sipMimeBodySupport is set to 3 (only SIP-I supported on the incoming trunk group),
the Cisco PGW 2200 Softswitch receives a SIP INVITE message.
Type
Processing error alarm
Action
Perform the following steps:
1.
Check the sipMimeBodySupport property value to make sure that SIP/SIP-I call is allowed on the
incoming trunk group.
2.
Check the SipIIngressVersionMAP property value on the incoming SIP trunk group.
3.
Use the following command to see whether the Cisco PGW 2200 Softswitch selects the correct
SIP-I variant:
prov-rtrv:sipiversion:profilename="SIP-I mapping profile name",version="SIP-I version
in Content-Type"
Properties
The properties identified in this section are used for the SIP-I Protocol feature. After confirming which
SIP-I protocol standard you are following (see the “Supported Standards, MIBs, and RFCs” section on
page 6), you can provision these properties according to that specific SIP-I protocol.
For information on other properties of the Cisco PGW 2200 Softswitch software, see the
Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/prvgde.html
SIP-I Protocol Support
18
SIP-I Protocol Feature Module
Software Changes for This Feature
New Properties
Table 1 describes the new SIP profile and domain profile properties used for this feature.
Table 1
New Properties
Property
Description
isuptmrProfile
This property indicates the Level 2 ISUP TMR profile that is attached to a SIP profile.
Valid values: any string up to 128 characters in length.
Default value: NULL.
Dynamically reconfigurable: yes.
LRNDigitCCPr
efix
This property indicates whether the function is enabled: the Cisco PGW 2200 Softswitch adds a prefix to
the destination country code in CC_DIG for the call to the location routing number and changes the NOA
code to international. This is an outgoing trunk group property. This property is for PSTN emulation
services (SIP/SIP-I).
Valid values: boolean (0 = not enabled, 1 = enabled).
Default value: 0.
Dynamically reconfigurable: yes.
LRNDigitCCrm This property specifies a country code digit string to which the RNDigitCCrm is compared if the NOA code
is International. If the digits match, the matched digits are removed from the location routing number and
the NOA code is set to National. This is an incoming trunk group property. This property is for PSTN
emulation services (SIP/SIP-I).
Valid values: NULL or any string up to 5 digits.
Default value: NULL.
Dynamically reconfigurable: yes.
PropagateDelay
Counter
This property indicates the propagation delay increase value (measured in milliseconds) which the
Cisco PGW 2200 Softswitch adds to the propagation delay of the incoming message. The outgoing
message carries the calculation result. This property is for PSTN emulation services (SIP-I).
Valid values: integer (0 to 255).
Default value: 0.
Dynamically reconfigurable: yes.
RestrictPresIfN
oPAID
This property indicates whether the Cisco PGW 2200 Softswitch sets the CgPN APRI of the outgoing
ISUP message to presentation restricted when the incoming SIP-I message does not contain the
P-Asserted-Identity header. This property is for PSTN emulation services (SIP/SIP-I).
Valid values: boolean
where:
0 = If the incoming SIP-I message does not contain the P-Asserted-Identity header, the
Cisco PGW 2200 Softswitch sets the CgPN APRI of the outgoing ISUP message according to the ITU-T
Recommendation Q1912.5.
1 = If the incoming SIP-I message does not contain the P-Asserted-Identity header, the
Cisco PGW 2200 Softswitch sets the CgPN APRI of the outgoing ISUP message to presentation restricted.
Default value: 0.
Dynamically reconfigurable: yes.
SIP-I Protocol Support
19
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 1
New Properties (continued)
Property
Description
SIPCOLPReqEn This property specifies whether the COLP request for SIP-originated calls is enabled or not. This property
abled
is for PSTN emulation services (SIP/SIP-I).
Values: boolean (0 = not enabled, 1 = enabled).
Default value: 0.
Dynamically reconfigurable: yes.
SipEgressEarly
DialogRelType
This property indicates whether the Cisco PGW 2200 Softswitch sends the CANCEL message or the BYE
message for the Early Dialog release. This property is for Q.1912.5 compliance.
Valid values: boolean (0 = send the CANCEL message, 1 = send the BYE message).
Default value: 0.
Dynamically reconfigurable: yes.
SipEgressGN2F This property controls how the Cisco PGW 2200 Softswitch maps the generic number to the SIP From
romScreenInd
header. This property is for PSTN emulation services (SIP/SIP-I).
Valid values: integer (from 0 to 3)
where:
0 = UPVP and UPNV
If the screen indicator subparameter in the incoming ISUP message is UPVP or UPNV and the property
value is 0, the Cisco PGW 2200 Softswitch maps the generic number to the SIP From header.
1 = UPVP
If the screen indicator subparameter in the incoming ISUP message is UPVP and the property value is 1,
the Cisco PGW 2200 Softswitch maps the generic number to the SIP From header.
2 = UPNV
If the screen indicator subparameter in the incoming ISUP message is UPNV and the property value is 2,
the Cisco PGW 2200 Softswitch maps the generic number to the SIP From header.
3 = always mapping
If the property value is 3, the Cisco PGW 2200 Softswitch always maps the generic number to the SIP
From header.
Default value: 0.
Dynamically reconfigurable: yes.
SipICANCELE
ncapREL
This property indicates whether the encapsulated REL message is required or not in the CANCEL message.
This property is a non-essential SIP-I-specific property.
Valid values: boolean (0 = not required, 1 = required).
Default value: 0.
Dynamically reconfigurable: yes.
SIP-I Protocol Support
20
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 1
Property
New Properties (continued)
Description
SipICLICOLPre This property indicates which parameters the CLI/Connect number takes as preference, SIP header or ISUP
ference
parameters. This property is a non-essential SIP-I-specific property.
Valid values: boolean.
0 = CLI/Connect number takes SIP header parameters as preference.
1 = CLI/Connect number takes ISUP parameters as preference.
Default value: 0.
Dynamically reconfigurable: yes.
SipIConfusionH This property indicates whether to terminate the ISUP confusion message or transport this message
andling
transparently. This property is a non-essential SIP-I-specific property.
Valid value: boolean.
0 = terminate the ISUP confusion message.
1 = transport the ISUP confusion message transparently.
Default value: 0.
Dynamically reconfigurable: yes.
SipIEgressHand This property indicates the value of handling the disposition parameter in the Content-Disposition header
ling
field of the ISUP MIME body in SIP-I messages. This property is set on outgoing trunk groups with SIP-I
support. If it is set to 2, “handling=required” is always added to the INVITE Content-Disposition header.
If it is set to 0, “handling=required” is added only if there is a to-be-encapsulated IAM message with
user-to-user information; otherwise, “handling=optional” is added. This property is an essential
SIP-I-specific property.
Valid value: integer (from 0 to 2)
where:
0 = Content-Disposition header is “Content-Disposition:signal; handling=required” only if there is a
to-be-encapsulated IAM message with user-to-user information; otherwise, Content-Disposition header is
“Content-Disposition:signal; handling=optional”.
1 = Content-Disposition header is “Content-Disposition:signal; handling=optional”.
2 = Content-Disposition header is “Content-Disposition:signal; handling=required”.
Default value: 1.
Dynamically reconfigurable: yes.
SipIEgressISUP This property indicates the version subparameter used in the Content-Type header field for SIP-I messages
Version
on the outgoing SIP trunk group. This property is an essential SIP-I-specific property.
Valid values: NULL or any string up to 128 characters in length.
Default value: NULL.
Dynamically reconfigurable: yes.
SIP-I Protocol Support
21
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 1
New Properties (continued)
Property
Description
SipIEgressMDO This property indicates the SIP-I variant name on the outgoing SIP trunk group. This property is an
essential SIP-I-specific property.
Valid values: NULL or any string up to 40 alphanumeric characters.
Default value: NULL.
Dynamically reconfigurable: yes.
SipIFacilityReje This property indicates whether to terminate the ISUP facility reject message or transport this message
ctHandling
transparently. This property is a non-essential SIP-I-specific property.
Valid values: boolean.
0 = terminate the ISUP facility reject message.
1 = transport the ISUP facility reject message transparently.
Default value: 0
Dynamically reconfigurable: yes.
SipIIngressVersi This property indicates the SIP-I mapping profile name which is defined in the SIP profile name field of
onMAP
the sipIVersion.dat file. This property is an essential SIP-I-specific property.
Valid values: NULL or the string defined in the SIP-I mapping profile name field of the sipIVersion.dat
file, like BT.
Default value: NULL.
Dynamically reconfigurable: yes.
SipIngressLNP
Handling
This property controls whether the Cisco PGW 2200 Softswitch maps the SIP routing number and the
telephone number to the called party number and the generic address ISUP parameters. This property is
for PSTN emulation services (SIP/SIP-I).
Valid values: boolean (0 = no mapping, 1 = mapping)
Default value: 0.
Dynamically reconfigurable: yes.
SIP-I Protocol Support
22
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 1
Property
New Properties (continued)
Description
SipInsertReason This property indicates whether a reason header containing the cause code is required or not. This property
Header
is for Q.1912.5 compliance.
Valid values: integer (from 0 to 2)
where:
0 = do not insert the reason header.
1 = add the reason header in Q.850 format.
2 = add the reason header in ANSI format.
Default value: 0.
Dynamically reconfigurable: yes.
SipIToiw2
This property indicates the Toiw2 timer value measured in seconds. This property is for Q.1912.5
compliance.
Valid values: integer (from 4 to 14).
Cause for initiation: Sending of INVITE.
Termination criterion: On receipt of 18x, or 200 OK INVITE.
Action At expiry: Send early ACM
Default value: 4.
Dynamically reconfigurable: yes.
Updated Properties
The following existing sigpath properties are added to the SIP sigpath in this feature.
•
ADigitCCPrefix
•
ADigitCCrm
•
BDigitCCPrefix
•
BDigitCCrm
•
CCOrigin
For Finnish SIP-I, you can provision the following properties in the common profile.
•
AOCEnabled
•
CircHopCount
•
CLIPEss
•
PropagateDelayCounter
•
SatelliteInd
Table 2 describes SIP profile properties which have modified values in this feature.
SIP-I Protocol Support
23
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 2
Updated Properties
Property
Description
InhibitSipFr
omMapping
The value 5 is added in this feature. This property determines the mapping from the incoming SIP message to
the ISUP CLI. This property is for PSTN emulation services (SIP/SIP-I).
Valid values:
•
0 = If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN, and map the E164 number
in username in From header to GN (additional CgPN). If the PAID/RPID E164 number is not present, map
the E164 number in username in From header to CgPN.
•
1 = Ignore the From header, and map the PAID/RPID E164 number to CgPN.
If the remote party ID or P-Asserted-ID header is present and the InhibitSipFromMapping property = 1,
then disable mapping the SIP From header to the generic number. If the remote party ID or P-Asserted-ID
header is not present and the InhibitSipFromMapping property = 1, then disable mapping the SIP From
header to the calling party number.
•
2 = Ignore the PAID/RPID, and map the E164 number in the username in From header to CgPN.
•
3 = If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN, and map the E164 number
in Display name in From header to GN (additional CgPN). If the PAID/RPID E164 number is not present,
map the E164 number in the username in From header to ISUP CgPN, and map the E164 number in the
displayname in From header to GN (additional CgPN).
•
4 = If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN, and map the E164 number
in the username in From header to GN (additional CgPN). If the PAID/RPID E164 number is not present,
ignore From header.
•
5 = If the PAID/RPID E164 number is present, map the PAID/RPID to CgPN, and map the E164 number
in username in From header to GN (additional CgPN). If the PAID/RPID E164 number is not present, map
the E164 number in the username in From header to ISUP CgPN, and map the E164 number in
displayname in From header to GN (additional CgPN).
Note
The value 4 is available only in Release 9.7(3). The value 5 is available only in Release 9.8(1).
Default value: 0.
Dynamically reconfigurable: yes.
SIP-I Protocol Support
24
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 2
Property
Updated Properties (continued)
Description
sipMimeBod The values 0, 3, and 4 are added in this feature. This property indicates how SIP, SIP-T, SIP-GTD, and SIP-I
ySupport
are supported on one trunk group. This property is an essential SIP-I-specific property.
Valid values: integer (from 0 to 4)
where:
•
0 = only SIP supported
•
1 = SIP-T supported
•
2 = SIP-GTD supported
•
3 = Only SIP-I supported on the incoming trunk group, SIP and SIP-I supported on the outgoing trunk
group
•
4 = SIP and SIP-I supported on both the incoming and outgoing trunk groups
Default value: 0.
Dynamically reconfigurable: yes.
Support183
The values 1, 2, and 5 are added in this feature. This property indicates how the Cisco PGW 2200 Softswitch
supports the 183 response code. This property is for Q.1912.5 compliance.
Valid values: integer (from 0 to 5).
where:
0 = 183 not supported
1 = Q1912.5 supported without SDP in 180 message
2 = Q1912.5 supported with InbandInfo check
3 = 183 supported
4 = always send 183
5 = Q1912.5 supported
Default value: 3.
Dynamically reconfigurable: yes.
Table 3 describes the original ISUP sigpath properties which you can provision in the common profile
for this feature.
SIP-I Protocol Support
25
SIP-I Protocol Feature Module
Software Changes for This Feature
Table 3
Properties Provisioned in the Common Profile
Property
Description
T2
This property indicates the ISUP T2 timer value measured in millisecond seconds. This property is for PSTN
emulation services (SIP-I).
Valid value: 180000
Cause for initiation: Receives a user generated SUS (user Initiated TP service) in order to unplug the terminal
from the socket and plug it in another one.
Termination criterion: At receipt of resume (user) message.
Action at Expiry: Initiate release procedure.
Default value: 180000
T6
This property indicates the ISUP T6 timer value measured in millisecond seconds. This property is for PSTN
emulation services (SIP-I).
Valid value: 2000 - 120000
Cause for initiation: Receives SUS (network)
Termination criterion: At receipt of resume (network) message or release message.
Action at Expiry: Initiate release procedure.
Default value: 120000.
T33
This property indicates the ISUP T33 timer value measured in millisecond seconds. This property is for PSTN
emulation services (SIP-I).
Valid value: 12000 - 15000
Cause for initiation: Sends an MCID request in an Information Request message
Termination criterion: At receipt of at the receipt of an Information Response
Action at Expiry: Initiate release procedure.
Default value: 15000.
CLIPEss
This property indicates whether/how to request the Calling Line Identity (CLI) in MCID service. This
property is for PSTN emulation services (SIP-I).
Valid value: 0, 1, 2
0 = CLI not requested
1 = CLI requested if not provided and call is dropped if CLI is not available
2 = CLI requested if not provided and call is continued regardless if CLI is available or not
Default value: 0
Result Type Definitions
Table 4 describes the result type added for this feature. For information on other result type definitions
for the Cisco PGW 2200 Softswitch software, see the Cisco PGW 2200 Softswitch Release 9.8 Dial Plan
Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/dial_plan/guide/dplan.html.
SIP-I Protocol Support
26
SIP-I Protocol Feature Module
Troubleshooting the Feature
New Result Type Definitions
84 SIPI_CONTROL
Enable the route 0 (not used)
preference
Dataword4
0 (not used)
0 (not used)
Pre-analysis
Dataword3
Cause
Dataword2
Result Type
Valid For
B-digit analysis
Dataword1
End Point
Result Type
Intermediate
Result Number
Analysis
Points
A-digit analysis
Table 4
x
SIPI_CONTROL
A new result type SIPI_CONTROL is added to enable the SIP-I route preference and to overwrite the
outgoing SIP-I related configuration parameters on outgoing trunk group. Currently this result type is
used to enable the SIP-I route preference only.
Dataword 1: enable the route preference
1 = Enable the route preference
Troubleshooting the Feature
This section describes troubleshooting procedures for this feature:
•
Incoming SIP-I calls fail.
SIP-I Protocol Support
27
SIP-I Protocol Feature Module
Troubleshooting the Feature
Step 1
Step 2
Action
Description
Check the property
sipMimeBodySupport on the
incoming trunk group.
The Cisco PGW 2200 Softswitch requires this property to be set
to 3 or 4 in order to support SIP-I on the incoming trunk group.
Check the SIP-I interface license.
Use the MML command, rtrv-lics:all, to check if the SIP-I license
is available. The following example gives you an example of
using this command to check the SIP-I license.
For property details, see Properties, page 18.
mml> rtrv-lics:all
The following system output is truncated. The bottom line
indicates that the SIP-I interface license is available.
MGC-01 - Media Gateway Controller 2009-02-23
01:53:48.371 EST
M RTRV
"LMAgent:
----------------------------------------------------------------PGW Fully Featured License
9.8 permanent
----------------------------------------------------------------Interface Name
Entitled
Provisioned
SS7Interface
Y
Y
PRIInterface
Y
N
PBXInterface
Y
N
INAPInterface
Y
N
LIInterface
Y
N/A
SBEInterface
Y
N
SIPIInterface
Y
Y
Step 3
Step 4
Check the property
SipIIngressVersionMap on the
incoming trunk
The Cisco PGW 2200 Softswitch requires this property to be set
to the desired SIP-I mapping profile on the incoming trunk group.
Check the entry of that desired
SIP-I mapping profile in
sipIVersion.dat.
Check if entry of that desired SIP-I mapping profile is correctly
provisioned in sipIVersion.dat.
See Provisioning Tasks, page 6.
1.
Check if the SIP-I version field of that entry matches the
version subparameter in the Content-Type in the incoming
SIP-I INVITE message.
2.
Check if the SIP-I variant field of that entry is correctly
provisioned using the following command:
prov-rtrv:sipiversion:profilename="BT",version="etsi
356"
For details on how to add, edit, and delete records in the
sipIVersion.dat, see Provisioning Tasks, page 6.
•
Outgoing SIP-I calls fail.
SIP-I Protocol Support
28
SIP-I Protocol Feature Module
Troubleshooting the Feature
Action
Description
Step 1
Check the property
sipMimeBodySupport on the
outgoing trunk group.
The Cisco PGW 2200 Softswitch requires this property to be set
to 3 or 4 in order to support SIP on the outgoing trunk group. For
property details, see the “Properties” section on page 18.
Step 2
Check the SIP-I interface license.
See Step 2 in the previous troubleshooting procedure for failed
incoming SIP-I calls.
Step 3
Check the Content-Disposition
parameter in the outgoing SIP-I
INVITE message.
If it is "handling=optional", change the SipIEgressHandling
property on the outgoing trunk group to 2. See the “Provisioning
Tasks” section on page 6.
Step 4
Check the SIP-I version defined in Check if the SIP-I version defined in SipIEgressISUPVersion
SipIEgressISUPVersion property. property on the outgoing trunk group matches the SIP-I version
of the peer devices.
•
Ringback tones are missing.
SIP-I Protocol Support
29
SIP-I Protocol Feature Module
Troubleshooting the Feature
Action
Step 1
Provision the
property
support183 on
the incoming
trunk group.
Description
•
If the terminating side cannot play the remote ringback tone, you can provision
the support183 property:
– 0 (183 not supported) = The Cisco PGW 2200 Softswitch sends a 180
Ringing without SDP.
– 1 (Q1912.5 supported without SDP in 180 message) = The
Cisco PGW 2200 Softswitch sends a 180 Ringing without SDP.
– 2 (Q1912.5 supported with InbandInfo check) = The
Cisco PGW 2200 Softswitch sends a 180 Ringing without SDP.
– 3 (183 supported) = The Cisco PGW 2200 Softswitch sends a 180 Ringing
without SDP.
•
If the terminating side can play the remote ringback tone and the alerting
signaling includes the InbandInfo indicator, you can provision the support183
property:
– 2 (Q1912.5 supported with InbandInfo check) = The
Cisco PGW 2200 Softswitch sends a 180 Ringing with SDP.
– 3 (183 supported) = The Cisco PGW 2200 Softswitch sends a 183 Session
Progress with SDP.
– 4 (always send 183) = The Cisco PGW 2200 Softswitch sends a 183 Session
Progress with SDP.
– 5 (Q1912.5 supported) = The Cisco PGW 2200 Softswitch sends a 180
Ringing with SDP.
•
If the terminating side can play the remote ringback tone but the alerting signaling
does not include the Inbandinfo indicator, you can provision the support183
property:
– 4 (always send 183) = The Cisco PGW 2200 Softswitch sends a 183 Session
Progress with SDP.
– 5 (Q1912.5 supported) = The Cisco PGW 2200 Softswitch sends a 180
Ringing with SDP.
•
(Finnish SIP-I only) Finnish SIP-I doesn’t work.
Action
Description
Step 1
Check the MPM
provisioning on the
Cisco PGW 2200 Softs
witch
For details on provisioning MPM support for Finnish ISUP on the
Cisco PGW 2200 Softswitch, see the section, Provisioning Tasks, of the
feature guide Meter Pulse Messages Support at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/feature/module/
9.5_1_/FMmpm.html.
Step 2
Check the property
For Finnish SIP-I, encapsulated ISUP takes precedence over SIP headers.
SipICLICOLPreference Make sure the SipICLICOLPreference property is set to 1.
For more information on operational tasks for the rest of the Cisco PGW 2200 Softswitch software, see
the Cisco PGW 2200 Softswitch Release 9 Operations, Maintenance, and Troubleshooting Guide at
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/maintenance/guide/omtguide.html.
SIP-I Protocol Support
30
SIP-I Protocol Feature Module
Obtaining Documentation, Obtaining Support, and Security Guidelines
If you still have problems with this feature, get the MDL trace and contact the Cisco TAC.
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, 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.
Mapping Details
This section contains additional information which may be useful for you to understand specific
mapping details of parameters. The heavy vertical line in the tables indicates where the mapping takes
place. Different combinations of input message parameters and the Cisco PGW 2200 Softswitch
properties on the left of the heavy vertical line have corresponding mapping results on the right. These
tables are not limited to SIP and ISUP mapping.
Table 5 describes the mapping from SIP header fields to ISUP message parameters under control of the
property InhibitSipFromMapping. Table 6 describes the mapping from the address complete message
(ACM) to 180 Ringing /183 Session Progress under control of the property Support183. Table 7
describes the mapping from the call progress message (CPG) to 180 Ringing /183 Session Progress
under control of the property Support183.
Table 5
Mapping of SIP Header Fields to ISUP CgPN/GN/PN/GAP Address Subparameter Under Control of the
InhibitSipFromMapping Property
SIP Header Fields
Property
P-Asserted
-Identity
Field
From Field
InhibitSipFr
omMapping Address Signal in CgPN1 Fields
Present in
E164
format5
Present in
E164
format
0
4
ISUP Parameter Fields
Address
Address Signal in GN2 or GA3 Signal in
Fields
PN4 Fields
From the E164 number in username of Address signal: from the
PN should
SIP P-Asserted Identity.
E164 number in username of be the same
SIP From header
as GN.
5
1
Absent
3
Address signal: from the
E164 number in
displayname of SIP From
header
2
From the E164 number in username of Absent
SIP From header
SIP-I Protocol Support
31
SIP-I Protocol Feature Module
Mapping Details
Table 5
Mapping of SIP Header Fields to ISUP CgPN/GN/PN/GAP Address Subparameter Under Control of the
InhibitSipFromMapping Property (continued)
SIP Header Fields
Property
P-Asserted
-Identity
Field
From Field
InhibitSipFr
omMapping Address Signal in CgPN1 Fields
0
Absent or
the field not 1
in E164
3
format
ISUP Parameter Fields
Address
Address Signal in GN2 or GA3 Signal in
Fields
PN4 Fields
From the E164 number in username of Absent
SIP P-Asserted Identity.
4
5
2
Absent or
the field
not in
E164
format
Present in
E164
format
0
2
3
5
1
Absent
•
From the E164 number in
username of SIP From header if
username is present in SIP From
header
Absent
The E164 number in
displayname of SIP From
• From the E164 number in
header is mapped to GA/GN
displayname of SIP From header if if username present in the
displayname is present in SIP From SIP From header is already
header and
mapped to CgPN.
InhibitSipFromMapping = 3
Absent
Absent
Absent
Absent
4
Absent or
the field not
in E164
format
Any valid
value
(integer, 0
to 5)
1. CgPN = calling party number.
2. GN = generic number (Q1912.5/EN 383 001, ND 1017 only).
3. GA = generic address (T1.679 only).
4. PN = presentation number (ND1017 only).
5. For SIP-URI in the P-Asserted-Identity or the From header field, if the field userinfo is E164 number with parameter “user=phone” or the field userinfo
is E164 number with respectSipUriUserParm value set to 0, the Cisco PGW 2200 Softswitch treats the SIP-URI as E164 format.
SIP-I Protocol Support
32
SIP-I Protocol Feature Module
Mapping Details
Table 6
Mapping ISUP Address Complete Message (ACM) to 180/183 Under Control of the Property Support183
Local
Called Party Status SDP2
Indicator in BCI1
Ready
Support183 Property
InbandInfo in OBCI3
Message Sent to SIP
Subscriber free
4 (always send 183)
Any
183 Session Progress
Any other
Any
180 Ringing
0 (183 not supported)
Any
180 Ringing
4 (always send 183)
Any
183 Session Progress
3 (183 is supported)
Has inband indicator
183 Session Progress with
SDP
No inband indicator
180 Ringing
No
Yes
1 (Q1912.5 supported without SDP
in 180)
5 (Q1912.5 supported)
2 (Q1912.5 supported with
InbandInfo)
No indication or
connect when free
No
Yes
Any valid value (integer, 0 to 5)
Any
•
In Profile C4
183 (ACM) Session
Progress
•
In Profile B
Not interworked
0 (183 not supported)
Any
180 Ringing
3 (183 is supported) or 4 (always
send 183)
Any
183 Session Progress
1 (Q1912.5 supported without SDP Any
in 180)
•
In Profile C
183 (ACM) Session
Progress
•
In Profile B
Not interworked
5 (Q1912.5 supported)
2 (Q1912.5 supported with
InbandInfo)
Has inband indicator
No inband indicator
183 Session Progress
•
In Profile C
183 (ACM) Session
Progress
•
In Profile B
Not interworked
1. BCI = Backward Call Indicator.
2. SDP = Session Description Protocol.
3. OBCI = Optional Backward Call Indicator.
4. For details of the Profile B and Profile C definitions, see the ITU-T Recommendation Q.1912.5 (2004) Interworking between Session Initiation Protocol
(SIP) and Bearer Independent Call Control Protocol or ISDN User Part.
SIP-I Protocol Support
33
SIP-I Protocol Feature Module
Mapping Details
Note
Table 7
Table 6 is not applicable for SIP to SIP B2BUA. This table is for SIP-I involved calls and SIP-to-EISUP
calls. For details on whether or not the Cisco PGW 2200 Softswitch includes SDP in 180/183 messages,
see the troubleshooting procedure when ringback tones are missing in the “Troubleshooting the Feature”
section on page 27.
Mapping ISUP Call Progress Message (CPG) to 180/183 Under Control of the Property Support183
Event Indicator in Event Local SDP2
Information of CPG1
Ready
Support183 Property
Message Sent to SIP
000 0001 (“alerting”)
180 Ringing
Either
1 (Q1912.5 supported without SDP in 180)
5 (Q1912.5 supported)
2 (Q1912.5 supported with InbandInfo)
1 (183 not supported)
180 Ringing
3 (183 supported)
4 (always send 183)
000 0010 (“progress”)
No
1 (Q1912.5 supported without SDP in 180)
183 Session Progress
•
In Profile C3
183 (CPG) Session Progress
•
In Profile B
Not interworked
5 (Q1912.5 supported)
2 (Q1912.5 supported with InbandInfo)
Values other than 1, 2, or 5
Yes
1 (Q1912.5 supported without SDP in 180)
Not interworked
•
In Profile C
183 (CPG) Session Progress
•
In Profile B
Not interworked
5 (Q1912.5 supported)
2 (Q1912.5 supported with InbandInfo)
Values other than 1, 2, or 5
000 0011 (in-band
information or an
appropriate pattern is
now available)
No
1 (Q1912.5 supported without SDP in 180)
183 Session Progress
•
In Profile C
183 (CPG) Session Progress
•
In Profile B
Not interworked
5 (Q1912.5 supported)
2 (Q1912.5 supported with InbandInfo)
Values other than 1, 2, or 5
Yes
1 (Q1912.5 supported without SDP in 180)
Not interworked
•
In Profile C
183 (CPG) Session Progress
•
In Profile B
Not interworked
5 (Q1912.5 supported)
2 (Q1912.5 supported with InbandInfo)
183 (CPG) Session Progress
Values other than 1, 2, or 5
183 Session Progress
1. CPG = call progress message
2. SDP = Session Description Protocol
3. For details of the Profile B and Profile C definitions, see the ITU-T Recommendation Q.1912.5 (2004) Interworking between Session Initiation Protocol
(SIP) and Bearer Independent Call Control Protocol or ISDN User Part
SIP-I Protocol Support
34
SIP-I Protocol Feature Module
Mapping Details
Note
Table 7 is not applicable for SIP to SIP B2BUA. This table is for SIP-I involved calls and SIP to EISUP
calls.
Table 8 describes the mapping from the ISUP connected number parameter to the SIP
P-Asserted-Identity header.
Table 8
Mapping the ISUP Connected Number Parameter to the SIP P-Asserted-Identity Header
ISUP Connected
Number Parameter
NOA
Value
national (significant) number
SIP P-Asserted-Identity
Header
tel URI or SIP URI
1
international number
address signals
•
If NOA value is national
(significant) number, the
format of address signals
is NDC2+ SN3.
•
If NOA value is
international number, the
format of address signals
is CC4 + NDC + SN.
Value
CC (country code) is added to
connected address signals to construct
an E.164 number in the URI. The
number is prefixed with a plus sign.
Complete connected address signals are
mapped to construct an E.164 number
in the URI. The number is prefixed with
a plus sign.
tel URI or SIP URI5
CC + NDC+ SN as an E.164 number in
the URI. The number is prefixed with a
plus sign.
1. A tel URI or a SIP URI with “user=phone” is used according to operator policy.
2. NDC = national destination code
3. SN = subscriber number
4. CC = country code
5. A tel URI or a SIP URI with “user=phone” is used according to operator policy.
Note
Cisco PGW 2200 Softswitch does not split the address signal into the format, CC + NDC + SN. You can
manipulate the address signal (for example, adding CC, or removing CC) by means of dial plan.
Table 9 is a matrix of calling line identification (CLI) suppression values based upon the incoming PSTN
signaling settings and the SIP property cgpnInclude. The property cgpnInclude determines whether the
call setup message includes CLI or not.
SIP-I Protocol Support
35
SIP-I Protocol Feature Module
Mapping Details
Table 9
CLI Suppression in a SIP Environment Under Control of cgpnInclude
cgpnInclude Value (of
Terminating/Outgoing Received CLI
SIP Trunk Group)
(in IAM1)
Received
CLIR2 (in IAM)
Displayname Field in the
Outgoing Message From
Header
Username Field in the Outgoing
Message From Header
Not applicable
Not available Not available
Unknown
Unknown
0 (do not include)
Available
0 (no
restriction)
CLI
CLI
0 (do not include)
Available
1 (restriction)
Anonymous
Anonymous
1 (include)
Available
0 (no
restriction)
CLI
CLI
1 (include)
Available
1 (restriction)
Anonymous
CLI
1. IAM = initial address message
2. CLIR = Calling Line Identification Restriction
Table 10 is a matrix of generic number (GN) suppression values based upon the incoming PSTN
signaling settings and the SIP property cgpnInclude. The property cgpnInclude determines whether the
call setup message includes GN or not.
Table 10
GN Suppression in a SIP Environment Under Control of cgpnInclude
cgpnInclude Value (of
Terminating/Outgoing
SIP Trunk Group)
Displayname Field in the
Received GN Outgoing Message From
APRI2 (in IAM) Header
GN (in IAM1)
Not applicable
Not available Not available
Unknown
Unknown
0 (do not include)
Available
0 (no
restriction)
Address signal of GN
Address signal of GN
0 (do not include)
Available
1 (restriction)
Anonymous
Anonymous
1 (include)
Available
0 (no
restriction)
Address signal of GN
Address signal of GN
1 (include)
Available
1 (restriction)
Address signal of GN
Address signal of GN
Username Field in the Outgoing
Message From Header
1. IAM = initial address message
2. APRI = Address Presentation Restricted Indicator
Table 11 is a matrix of presentation number (PN) suppression values based upon the incoming PSTN
signaling settings and the SIP property cgpnInclude. The property cgpnInclude determines whether the
call setup message includes PN or not.
Table 11
PN Suppression in a SIP Environment Under Control of cgpnInclude
cgpnInclude Value (of
Terminating/Outgoing
SIP Trunk Group)
Received PN
(in IAM1)
Not applicable
Not available Not available
Unknown
Unknown
0 (do not include)
Available
PN if present for the ISUP
variant
PN if present for the ISUP variant
SIP-I Protocol Support
36
Displayname Field in
Received PN Outgoing Message From
APRI2 (in IAM) Header
0 (no
restriction)
Username Field in Outgoing
Message From Header
SIP-I Protocol Feature Module
Glossary
Table 11
PN Suppression in a SIP Environment Under Control of cgpnInclude (continued)
cgpnInclude Value (of
Terminating/Outgoing
SIP Trunk Group)
Received PN
(in IAM1)
Displayname Field in
Received PN Outgoing Message From
APRI2 (in IAM) Header
Username Field in Outgoing
Message From Header
0 (do not include)
Available
1 (restriction)
Anonymous
Anonymous
1 (include)
Available
0 (no
restriction)
PN if present for the ISUP
variant
PN if present for the ISUP variant
1 (include)
Available
1 (restriction)
Anonymous
PN if present for the ISUP variant
1. IAM = initial address message
2. APRI = Address Presentation Restricted Indicator
Glossary
Table 12
Acronyms and Expansions
Acronym
Expansion
ACgPN
additional calling party number (value of number qualifier indicator within
the generic number)
ACM
address complete message
APRI
Address Presentation Restricted Indicator
BCI
Backward Call Indicator
CC
country code
CdPN
called party number
CgPN
calling party number
CIC
carrier identification code (ANSI)
CLI
calling line identification
CPG
call progress message
GN
generic number (ITU/ETSI)
ISDN
Integrated Services Digital Network
ISUP
ISDN User Part
LNP
Local Number Portability
MGC
media gateway controller
MIME
Multipurpose Internet Mail Extensions
NDC
National Destination Code
NOA
nature of address indicator
OBCI
Optional Backward Call Indicator
PGW
PSTN Gateway
PN
presentation number (UK)
PSTN
public switched telephone network
REL
release message
SIP-I Protocol Support
37
SIP-I Protocol Feature Module
Glossary
Table 12
Acronyms and Expansions (continued)
Acronym
Expansion
SDP
Session Description Protocol
SIP
Session Initiation Protocol
SIP-I
SIP with encapsulated ISUP
SIP-T
Session Initiation Protocol for Telephones
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good,
Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks;
Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card,
and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA,
CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus,
Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast,
EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream,
Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV,
PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0910R)
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.
© 2008–2009 Cisco Systems, Inc. All rights reserved.
SIP-I Protocol Support
38