Downloads |
 Feedback
|
Table Of Contents
Upgrading to Support This Feature
Creating a New Inbound SIP Trunk
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 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
Troubleshooting Provisioning Settings
Monitoring and Maintaining the Feature
Disabling Inbound IP Trunk Groups
Software Changes for This Feature
Originating Trunk Group (Tag: 4008)
Obtaining Documentation and Submitting a Service Request
Multiple Inbound IP Trunks
Feature History
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:
•
Upgrading to Support This Feature
•
•
•
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:
•
•
•
•
•
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:
•
•
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
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
The following sections describe how to create an inbound IP trunk:
•
•
Additional information about provisioning is available in the Cisco MGC Software Release 9 Provisioning Guide in the following sections:
•
http://www.cisco.com/en/US/docs/voice_ip_comm/pgw/9/provisioning/guide/R9PlnPrv.html
•
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.
•
•
•
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=1prov-add:SIPLNK:NAME="sip-sigchan-2", DESC="SIP link 2", SVC="sip-sigpath", IPADDR="Virtual_IP_Addr2", PORT=5060, PRI=2prov-ed:SIPLNK:NAME="sip-sigchan-1", PORT=5061prov-ed:SIPLNK:NAME="sip-sigchan-2", PORT=5061
Note
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=5060prov-ed:siplnk:name="siplnk1", port=5076
Note
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_INprov-add:trnkgrp:name="1010", svc="sippath-1", type=SIP_INprov-add:trnkgrp:name="1040", svc="sippath-1", type=SIP_INMapping 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=1000prov-add:ipinmapping:name="sipinmapping-3", sigsvc="sippath-1", sipport=5064, trnkgrpNum=1010prov-add:ipinmapping:name="sipinmapping-2",sigsvc="sippath-1",allowedIP="10.0.14.145", allowedIPNetmask="255.255.255.128", trnkgrpNum=1040prov-ed:siplnk:name="siplnk1",port=5063prov-ed:siplnk:name="siplnk1",port=5064Mapping 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=1040prov-add:ipinmapping:name="sipinmapping-2", sigsvc="sippath-1", allowedIP="10.0.15.145",allowedIPNetmask="255.255.255.128", trnkgrpNum=1040Enabling 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=1For 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.
•
•
•
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.
prov-dlt:siplnk:name="sip-sigchan-1"2.
prov-dlt:siplnk:name="sip-sigchan-1", port=5061Adding 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=IPMapping 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=2000Enabling 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=1For 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_INprov-ed:ipinmapping:name="sipinmapping-1",sigsvc="sippath-1",allowedIP="10.0.14.145",sipport=5063, trnkgrpNum=1000prov-ed:sigsvcprop:name="sippath-1",ipinscreening=1Retrieving 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:
•
–
•
–
–
•
–
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_INprov-add:trnkgrp:name="1010", svc="sippath-1", type=SIP_INprov-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=1000prov-add:ipinmapping:name="sipinmapping-3", sigsvc="sippath-1", sipport=5064,trnkgrpNum=1010prov-add:ipinmapping:name="sipinmapping-2", sigsvc="sippath-1", allowedIP="10.0.14.145",allowedIPNetmask="255.255.255.128", trnkgrpNum=1040prov-ed:siplnk:name="siplnk1", port=5063prov-ed:siplnk:name="siplnk1", port=5064________________________________________; Enabling Inbound Trunk Groups and Specifying Screening Properties;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;prov-add:sigsvcprop:name="sippath-1",ipinscreening=1EISUP 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
The Multiple Inbound IP Trunks feature introduces the measurement shown in Table 1.
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
For more information about CDRs, see the Cisco Media Gateway Controller Software Release 9 Billing Interface Guide.
Originating Trunk Group (Tag: 4008)
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:
•
The IP link service component structure is shown in Table 3.
Parameter Analysis
The PGW compares incoming SIP traffic against ipinmapping entries in the following order:
1.
2.
3.
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:
•
–
–
•
–
•
–
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
Properties
The Multiple Inbound IP Trunks feature introduces one new provisioning property.
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
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
