Guest

Cisco PGW 2200 Softswitch

Multiple Inbound IP Trunks

  • Viewing Options

  • PDF (245.4 KB)
  • Feedback
Multiple Inbound IP Trunks

Table Of Contents

Multiple Inbound IP Trunks

Feature Description

Benefits

Prerequisites

Restrictions or Limitations

Related Documents

Upgrading to Support This Feature

Provisioning Tasks

Creating a New Inbound SIP Trunk

Adding a SIP Path

Adding a SIP Link

Adding a New Inbound Trunk Group

Mapping IP Traffic to a Trunk Group

Enabling Inbound Trunk Groups and Specifying Screening Properties

Creating a New Inbound EISUP Trunk

Adding an External Node

Adding an IP Path

Adding an IP Link

Deleting IP Links

Adding a New Inbound Trunk Group

Mapping IP Traffic to a Trunk Group

Enabling Inbound Trunk Groups and Specifying Screening Properties

Modifying an Incoming IP Trunk

Retrieving Incoming IP Trunk Properties

Deleting an Incoming IP Trunk

Troubleshooting Provisioning Settings

Monitoring and Maintaining the Feature

Measurements

Disabling Inbound IP Trunk Groups

Provisioning Examples

SIP Provisioning Example

EISUP Provisioning Example

Software Changes for This Feature

Measurements

Billing Interface

Originating Trunk Group (Tag: 4008)

Components

Properties

Provisioning Worksheets

Obtaining Documentation and Submitting a Service Request

Glossary


Multiple Inbound IP Trunks


Feature History

Release
Modification

9.7(3)

The Multiple Inbound IP Trunks feature was introduced on the Cisco PGW 2200 Softswitch.


This document describes the Multiple Inbound IP Trunks feature. The feature is described in the following sections:

Feature Description

Upgrading to Support This Feature

Provisioning Tasks

Monitoring and Maintaining the Feature

Provisioning Examples

Software Changes for This Feature

Obtaining Documentation and Submitting a Service Request

Glossary

Feature Description

The Multiple Inbound IP Trunks feature extends the PGW's ability to separate Session Initiation Protocol (SIP) and Extended ISUP (EISUP) traffic into multiple inbound trunk groups on a single interface. You can define inbound trunk groups based on source address, subnet, port number, or a combination of these items.

Separating incoming IP traffic into distinct trunk groups allows you to apply unique provisioning properties to each trunk group. This feature is useful in a multivendor SIP environment because it allows you to manage multiple SIP implementations.

The Multiple Inbound IP Trunks feature also improves security by adding the option to discard new messages that do not match the characteristics of defined inbound trunk groups. You can apply this option to SIP INVITE, REFER, and NOTIFY messages and EISUP Initial Address Message (IAM) messages.

Benefits

The Multiple Inbound IP Trunks feature provides the following benefits:

Allows you to separate SIP or EISUP traffic on a single interface into multiple trunk groups

Allows you to define custom provisioning treatment for each trunk group

Simplifies handling of multiple SIP and EISUP implementations

Allows you to set the PGW to discard unrecognized SIP INVITE, REFER, and NOTIFY messages and EISUP IAM messages

Provides support for SIP traffic on ports other than the default port (5060)

Prerequisites

The Cisco PGW 2200 must be running Cisco MGC software Release 9.7(3). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.7(3) at http://www.cisco.com/en/US/partner/docs/voice_ip_comm/pgw/9/release/note/rn973.html

Restrictions or Limitations

This feature has the following limitations:

The PGW analyzes incoming traffic based on source address and/or destination port only. The PGW cannot analyze traffic based on provisioning properties.

The traffic-filtering capabilities introduced in this feature are not intended to replace an external firewall device. We recommend that you deploy the PGW in an environment with external firewall protection.

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

Upgrading to Support This Feature

To install this feature, upgrade to patch S13P13 or greater. For instructions on how to install patches, see the Cisco MGC Installation and Configuration Guide.


Caution Because the Multiple Incoming IP Trunks feature modifies PGW provisioning tables, we strongly recommend that you back up the current configuration before you upgrade and apply the back up configuration if the upgrade fails. Any configuration based on S13P13 is not backwards compatible.

Provisioning Tasks

The Inbound IP Trunks feature allows you to create an inbound IP trunk group by mapping traffic from a defined IP address, port number, or a combination of these elements to an existing trunk group. Inbound IP trunk groups allow you to apply one or more sets of provisioning properties to inbound IP traffic.


Note This feature does not affect the provisioning commands used to create SIP and EISUP links or define inbound trunk groups.


The following sections describe how to create an inbound IP trunk:

Creating a New Inbound SIP Trunk

Creating a New Inbound EISUP Trunk

Additional information about provisioning is available in the Cisco MGC Software Release 9 Provisioning Guide in the following sections:

Planning for Provisioning

http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/R9PlnPrv.html

MML Basics

http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/R9MMLCfg.html

Creating a New Inbound SIP Trunk

The following sections describe how to create a new inbound IP trunk for SIP traffic.

Adding a SIP Path

Adding a SIP Link

Adding a New Inbound Trunk Group

Mapping IP Traffic to a Trunk Group

Enabling Inbound Trunk Groups and Specifying Screening Properties

The instructions to create a SIP path, SIP link, and inbound trunk group are optional—they apply only if you do not have existing SIP links and inbound trunk groups. This feature does not affect the provisioning commands used to create SIP connections or inbound trunk groups.

Adding a SIP Path

Use the prov-add:sippath command to add a SIP signaling path.

prov-add:sippath:name="sippath-1", mdo="IETF_SIP", desc="SIP sigpath"

Adding a SIP Link

You can create up to 2 SIP IP links and edit them to add up to 100 new listening ports per SIP IP link using the following commands.

prov-add:SIPLNK:NAME="sip-sigchan-1", DESC="SIP link 1", SVC="sip-sigpath", 
IPADDR="Virtual_IP_Addr1", PORT=5060,PRI=1

prov-add:SIPLNK:NAME="sip-sigchan-2", DESC="SIP link 2", SVC="sip-sigpath", 
IPADDR="Virtual_IP_Addr2", PORT=5060, PRI=2

prov-ed:SIPLNK:NAME="sip-sigchan-1", PORT=5061
prov-ed:SIPLNK:NAME="sip-sigchan-2", PORT=5061


Note You must define all SIP IP links with the same set of listening ports. In the preceding example, the port parameter was edited twice, one per SIP IP link.


Using Nonstandard Port Numbers

To add a new SIP link with a port number other than 5060, use the prov-ed:siplnk command to modify the port value for the SIP link.

prov-add:siplnk:name="siplnk1", svc="sippath-1", ipaddr="IP_ADDR1", port=5060
prov-ed:siplnk:name="siplnk1", port=5076


Note You must apply the same set of nonstandard port numbers to each SIP link. When you use a nonstandard port number, you must apply the prov-ed:SIPLNK command to each SIP link you define.


Adding a New Inbound Trunk Group

Use the prov-add:trnkgrp command to create a new trunk group for inbound SIP traffic. The SIP_IN trunk group type is for SIP only.

prov-add:trnkgrp:name="1000", svc="sippath-1", type=SIP_IN
prov-add:trnkgrp:name="1010", svc="sippath-1", type=SIP_IN
prov-add:trnkgrp:name="1040", svc="sippath-1", type=SIP_IN

Mapping IP Traffic to a Trunk Group

Use the prov-add:ipinmapping command to define the traffic that the PGW forwards to the new trunk group. You can define the incoming SIP traffic based on incoming IP address, subnet mask, port number (the SIP port on the PGW), or a combination of these elements.

prov-add:ipinmapping:name="sipinmapping-1", sigsvc="sippath-1", allowedIP="10.0.14.145", 
sipport=5063, trnkgrpNum=1000

prov-add:ipinmapping:name="sipinmapping-3", sigsvc="sippath-1", sipport=5064, 
trnkgrpNum=1010

prov-add:ipinmapping:name="sipinmapping-2",sigsvc="sippath-1",allowedIP="10.0.14.145", 
allowedIPNetmask="255.255.255.128", trnkgrpNum=1040

prov-ed:siplnk:name="siplnk1",port=5063
prov-ed:siplnk:name="siplnk1",port=5064

Mapping Multiple IP Ranges to a Single Trunk Group

You can map multiple IP ranges to a single inbound trunk group by creating two different sipinmapping entries to the same trunk group.

prov-add:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1", allowedIP="10.0.14.145", 
allowedIPNetmask="255.255.255.128", trnkgrpNum=1040

prov-add:ipinmapping:name="sipinmapping-2", sigsvc="sippath-1", allowedIP="10.0.15.145", 
allowedIPNetmask="255.255.255.128", trnkgrpNum=1040

Enabling Inbound Trunk Groups and Specifying Screening Properties

Use the prov-add or prov-ed command to modify the ipinscreening property in order to enable incoming IP trunk groups and specify whether the PGW permits traffic that does not match defined incoming IP trunk group properties. In the following example, the PGW is set to discard incoming traffic that does not match a existing incoming IP trunk groups:

prov-add:sigsvcprop:name="sippath-1", ipinscreening=1

For more information about the ipinscreening property, see "Properties".


Creating a New Inbound EISUP Trunk

The following sections describe how to create a new inbound IP trunk for EISUP traffic.

Adding an External Node

Adding an IP Path

Adding an IP Link

Adding a New Inbound Trunk Group

Mapping IP Traffic to a Trunk Group

Enabling Inbound Trunk Groups and Specifying Screening Properties

The instructions to create an external node, IP path, IP link, and inbound trunk group are optional—they apply only if you do not have existing EISUP links and inbound trunk groups. This feature does not affect the provisioning commands used to create EISUP connections or inbound trunk groups.

Adding an External Node

Use the prov-add:extnode command to add an EISUP link to another PGW node.

prov-add:extnode:name="pgw-1", type="MGC", desc="External Node PGW2200-1"

Adding an IP Path

Use the prov-add:eisuppath command to add a new EISUP signaling path.

prov-add:eisuppath:name="eisuppath-1", desc="Eisuppath signalling service to PGW-1", 
extnode="pgw-1", custgrpid="tr01"

Adding an IP Link

Use the prov-add:iplnk command to add a new IP link for EISUP traffic.

prov-add:iplnk:name="eisuplnk-1", desc="Iplnk#1 to PGW-1", svc="eisuppath-1", 
ipaddr="IP_Addr1", port=5001, peeraddr="10.20.1.11", peerport=5001, pri=1, iproute=""

Deleting IP Links

You can delete IP links two ways.

1. The following command deletes all the links that share the same link name.

prov-dlt:siplnk:name="sip-sigchan-1"

2. With the following command deletes only the link "sip-sigchan-1" with port 5061.

prov-dlt:siplnk:name="sip-sigchan-1", port=5061

Adding a New Inbound Trunk Group

Use the prov-add:trnkgrp command to create a new trunk group for inbound EISUP traffic. The IP trunk group type applies to EISUP only.

prov-add:trnkgrp:name="2000", svc="eisuppath-1", type=IP

Mapping IP Traffic to a Trunk Group

Use the prov-add:ipinmapping command to define the traffic that the PGW forwards to the new trunk group. You can define the incoming EISUP traffic based on the incoming IP address, subnet mask, port number, or a combination of these elements.

prov-add:ipinmapping:name="eisupinmapping-1", sigsvc="eisuppath-1", allowedIP="10.20.1.1", 
trnkgrpNum=2000

Enabling Inbound Trunk Groups and Specifying Screening Properties

Use the prov-add or prov-ed command to modify the ipinscreening property in order to enable incoming IP trunk groups and specify whether the PGW permits traffic that does not match defined incoming IP trunk group properties. In the following example, the PGW is set to discard incoming traffic that does not match existing incoming IP trunk groups:

prov-add:sigsvcprop:name="eisuppath-1",ipinscreening=1

For more information about the ipinscreening property, see "Properties".


Modifying an Incoming IP Trunk

The following examples show how to use the prov-ed command to modify the properties of inbound SIP and EISUP trunk groups:

prov-ed:trnkgrp:name="1000", svc="sippath-1", type=SIP_IN
prov-ed:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",allowedIP="10.0.14.145", 
sipport=5063, trnkgrpNum=1000
prov-ed:sigsvcprop:name="sippath-1",ipinscreening=1

Retrieving Incoming IP Trunk Properties

The following examples show how to use the prov-rtrv command to retrieve the properties of inbound SIP and EISUP trunk groups:

prov-rtrv:trnkgrp:name="1000"
prov-rtrv:ipinmapping:name="sipinmapping-1"
prov-rtrv:ipinmapping:"all"

Deleting an Incoming IP Trunk

The following examples show how to use the prov-dlt command to delete inbound SIP and EISUP trunk groups:

prov-dlt:trnkgrp:name="1000"
prov-dlt:ipinmapping:name="sipinmapping-1"

Troubleshooting Provisioning Settings

Use the following items to troubleshoot provisioning data for this feature:

If the PGW does not receive any incoming IP traffic

If you expect traffic on a particular port, verify that the port is configured on the SIP or IP link.

If the PGW is receiving traffic on the wrong trunk group

Verify that the ipinscreening settings enable inbound trunk group processing.

Verify that the ipinmapping settings forward the traffic to the appropriate trunk group.

If there is no configuration error

Use SIP or EISUP IOCC debug utilities to capture an MDL trace for use in diagnosing the problem.

For more information about troubleshooting provisioning data, see the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.

Monitoring and Maintaining the Feature

The following sections describe how to monitor and maintain the Multiple Inbound IP Trunks feature.

Measurements

The SP: IPIN REJ TOT measurement allows you to view the number of calls rejected due to ipinscreening property settings. For more information about measurements, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference.

Disabling Inbound IP Trunk Groups

To disable inbound IP trunk groups defined by the ipinmapping function, set the ipinscreening property equal to 0. This setting sets the PGW to use only the default inbound SIP and EISUP trunk groups.

For more information on operational tasks for the rest of the Cisco MGC software, see the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.

Provisioning Examples

This section provides provisioning examples for this feature. Additional provisioning examples for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

SIP Provisioning Example

________________________________________
; Start Provisioning Session
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-sta::srcver="active",dstver="incoming_ip_trunks",confirm
________________________________________
; Adding a SIP Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sippath:name="sippath-1",mdo="IETF_SIP",desc="SIP sigpath"
________________________________________
; Adding a SIP Link
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:siplnk:name="siplnk1", svc="sippath-1",ipaddr="IP_ADDR1",port=5060
________________________________________
; Adding New Inbound Trunk Groups
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrp:name="1000", svc="sippath-1", type=SIP_IN
prov-add:trnkgrp:name="1010", svc="sippath-1", type=SIP_IN
prov-add:trnkgrp:name="1040", svc="sippath-1", type=SIP_IN

________________________________________
; Mapping Incoming IP Traffic to a Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:ipinmapping:name="sipinmapping-1", sigsvc="sippath-1", allowedIP="10.0.14.145", 
sipport=5063, trnkgrpNum=1000
prov-add:ipinmapping:name="sipinmapping-3", sigsvc="sippath-1", sipport=5064, 
trnkgrpNum=1010
prov-add:ipinmapping:name="sipinmapping-2", sigsvc="sippath-1", allowedIP="10.0.14.145", 
allowedIPNetmask="255.255.255.128", trnkgrpNum=1040

prov-ed:siplnk:name="siplnk1", port=5063
prov-ed:siplnk:name="siplnk1", port=5064

________________________________________
; Enabling Inbound Trunk Groups and Specifying Screening Properties
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="sippath-1",ipinscreening=1

EISUP Provisioning Example

________________________________________
; Start Provisioning Session
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-sta::srcver="active",dstver="incoming_ip_trunks",confirm
________________________________________

; Adding an External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:extnode:name="pgw-1",type="MGC",desc="External Node PGW2200-1"
________________________________________
; Adding an IP Path
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:eisuppath:name="eisuppath-1",desc="Eisuppath signalling service to 
PGW-1",extnode="pgw-1",custgrpid="tr01"
________________________________________
; Adding an IP Link
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:iplnk:name="eisuplnk-1",desc="Iplnk#1 to 
PGW-1",SVC="eisuppath-1",ipaddr="IP_Addr1",port=5001,peeraddr="10.20.1.11",peerport=5001, 
pri=1,iproute=""
________________________________________
; Adding a New Inbound Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:trnkgrp:name="2000", svc="eisuppath-1", type=IP
________________________________________
; Mapping Incoming EISUP Traffic to a Trunk Group
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:ipinmapping:name="eisupinmapping-1",sigsvc="eisuppath-1", 
allowedIP="10.0.14.145", trnkgrpNum=2000
________________________________________
; Enabling Inbound Trunk Groups and Specifying Screening Properties
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sigsvcprop:name="sippath-1",ipinscreening=1
________________________________________

Software Changes for This Feature

The following sections contain software changes related to this feature:

Measurements

Billing Interface

Components

Properties

Provisioning Worksheets

Measurements

The Multiple Inbound IP Trunks feature introduces the measurement shown in Table 1.

Table 1 New Measurement 

MML Counter Group:Name

Description
Related Components

Logging Interval

SP: IPIN REJ TOT

Added in Release 9.7. Total number of rejected calls due to ipinscreening

SIP path/EISUP path

15, 60, 24


For more information about measurements, see the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.

Billing Interface

The Multiple Incoming IP Trunks feature utilizes Call Detail Record (CDR) tag 4008, Originating Trunk Group. Table 2 summarizes the properties of the Originating Trunk Group tag.


Note This feature does not modify the Originating Trunk Group tag.


For more information about CDRs, see the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.

Originating Trunk Group (Tag: 4008)

Table 2 Originating Trunk Group  

Name: Originating Trunk Group

Tag: 4008

Source: MDL/Engine

Description/Purpose: Holds the originating trunk group number.

Format: BE

Length in Octets: 2

Data Value: The trunk group number ranges from 1 to 16,384 for ANSI and 1 to 4096 for ITU.

Extended Data Value: No extended value.

General Information: When creating Bellcore AMA Format (BAF) records downstream, this tag supports only 4 digits for the trunk group number. This makes the practical limit 9999.

MGC Release: Release 9.8 or later.

Answered (1010)

Deselected (1020)

Aborted (1030)

Release (1040)

Interrupted (1050)

Ongoing (1060)

Maintenance (1070)

External DB (1080)

End of Call (1110)

Y

N

Y

N

N

N

N

N

Y


Components

The following sections discuss the provisioning components that are added, modified, and deleted for this feature. For information on the rest of the components in the Cisco MGC software, see the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

IPINMAPPING

The ipinmapping component allows you to define mapping between a single SIP or EISUP interface and multiple IP trunk groups using incoming IP address, subnet mask, port number, or a combination of these elements. You can define up to 10,000 IP trunk groups using the ipinmapping component.

The component MML name is as follows:

MML Name—IPINMAPPING

The IP link service component structure is shown in Table 3.

Table 3 Ipinmapping Component Structure   

Parameter MML Name
Parameter Description
Parameter Value

Name

The primary key to identify an ipinmapping entry

A unique name used to describe the ipinmapping rule entry. This field must have a unique value.

Desc

Description

A description of the trunk group.

Sigsvc

SIP sigpath or EISUP sigpath

The signal path to which the ipinmapping rule applies.

AllowedIP

Allowed IP address

The incoming SIP IP address allowed on the trunk. This parameter is optional.

AllowedIPNetMask

Allowed net mask

The subnet mask allowed on the trunk. This parameter is optional.

Note If this parameter is blank, the PGW uses the default subnet mask value of 255.255.255.255.

Sipport

Allowed SIP port

The SIP TCP or UDP port number allowed on the trunk. This parameter applies to SIP sigpaths only and is optional.

Trnkgrpnum

Trunk group number

The number used to identify the trunk group.


Parameter Analysis

The PGW compares incoming SIP traffic against ipinmapping entries in the following order:

1. IP address and port number

2. IP address only

3. Port number only

The PGW compares incoming EISUP traffic against ipinmapping entries using IP address only.

Matching to IP Traffic to ipinmapping Entries

For incoming IP traffic to match an ipinmapping entry, the following criteria must be true:

IP address and port number:

The incoming IP address falls within the address range defined by the AllowedIP and AllowedIPNetMask parameters.

The destination port of the incoming SIP message matches the port number defined by the sipport parameter.

IP address only:

The incoming IP address (the SIP proxy source IP or EISUP H323SourceAddress) falls within the address range defined by the AllowedIP and AllowedIPNetMask values.

Port number only:

The destination port of the incoming SIP message matches the sipport defined in the ipinmapping entry.

When the PGW finds a match between incoming traffic and an ipinmapping entry, it forwards the traffic to the trunk group defined for that ipinmapping entry.


Note If incoming traffic matches multiple ipinmapping entries, the PGW applies the longest matching rule.


Properties

The Multiple Inbound IP Trunks feature introduces one new provisioning property.

Property
Definition

*.ipinscreening

The ipinscreening property determines whether incoming IP trunk groups defined by the ipinmapping function are enabled. Ipinscreening also determines whether the PGW accepts or denies incoming IP traffic that does not match defined incoming IP trunk groups.

Valid values:

0 = The ipinmapping function is disabled. The PGW processes inbound SIP and EISUP traffic on the default trunk groups.

1 = The ipinmapping function is enabled. The PGW discards incoming traffic that does not match an existing ipinmapping entry. The PGW evaluates messages using the source IP address and destination port.

2 = The ipinmapping function is enabled. The PGW sends incoming traffic that does not match an existing ipinmapping entry to the default incoming trunk group.

This setting requires that you specify a default inbound trunk group for SIP links. A default inbound trunk group is not required for EISUP links—if a default inbound trunk group is not defined, the PGW uses the trunk group with the BTechprefix property set to NULL.

Note If a message matches multiple ipinmapping table criteria, the PGW applies the most detailed match.

Default value: 0


Provisioning Worksheets

This section contains worksheets for the provisioning components required for this feature. For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.

Table 4 Multiple Inbound IP Trunks Worksheet Example  

Incoming IP Trunk Group
Trunk Group Number
Service
Source IP
Subnet
Port

sippath-1

1000

SIP

10.0.14.145

255.255.255.128

5063

           
           
           
           
           
           
           
           

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 5 Acronym Expansions and Definitions  

Acronym
Expansion

CDR

Call Detail Record.

EISUP

Extended ISUP. The protocol used for the signaling path to a PGW in an external physical location.

IAM

Initial Address Message, a message used in ISUP (ISDN User Part).

IP

Internet Protocol.

ISUP

ISDN User Part. An SS7 protocol layer that defines the protocol used to prepare, manage, and release trunks that carry voice and data between calling and called parties.

MGC

(Cisco) Media Gateway Controller. The software used on the Cisco PGW 2200 Softswitch.

MML

Man-Machine Language. Industry standard command line language used to manage telecommunications network elements, including the PGW 2200 softswitch.

PGW

PSTN Gateway

SIP

Session Initiation Protocol. A protocol developed by the IETF MMUSIC Working Group as an alternative to H.323. SIP equips platforms to signal the setup of voice and multimedia calls over IP networks.

TCP

Transmission Control Protocol. A connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack.

UDP

User Datagram Protocol. A connectionless transport layer protocol used in the TCP/IP protocol stack. UDP is a simple protocol that exchanges datagrams without acknowledgments or guaranteed delivery, requiring that error processing and retransmission be handled by other protocols.