 Feedback
|
Table Of Contents
Fax and Data Call Translations on the PGW 2200
Supported Standards, MIBs, and RFCs
Prerequisites for Using This Feature
Modifying the BCMOD Result Type
Deleting the BCMOD Result Type
Modifying the HLCMOD Result Type
Deleting the HLCMOD Result Type
Troubleshooting Dial Plan Data
Signaling Channel Troubleshooting Procedures
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Fax and Data Call Translations on the PGW 2200
Document Release History
December 29, 2005
Initial version of the document.
July 17, 2006
Added a note on page 16 to resolve CSCsc75586.
Feature History
This document describes the Fax and Data Call Translations on the PGW 2200 feature.
This feature is described in the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
•
•
Feature Overview
The Fax and Data Call Translations on the PGW 2200 feature provides the ability to change an ISUP call to a fax or data call. This feature provides support on the Cisco PGW 2200 to change the Bearer Capability and High Layer Compatibility information elements (IEs) in outgoing Initial Address Messages (IAMs) based on the dialed called party number. The Cisco MGC can use the BCMOD and HLCMOD result types to change outgoing IAM message parameters to allow calls from the public switched telephone network (PSTN) to called (B-numbers) in the Global System for Mobile Communications (GSM) network for ISUP calls.
This feature provides the following:
•
•
Benefits
Ability to Change an ISUP Call to a Fax Call
By changing the Bearer Capability IE in the outgoing IAM, an ISUP call from the PSTN can be translated to a fax call in the GSM network.
Ability to Change an ISUP Call to a Data Call
By changing the High Layer Compatibility IE in the outgoing IAM, an ISUP call from the PSTN can be translated to a data call in the GSM network.
Restrictions
If there are HLCMOD or BCMOD result type-related dial plan provisioning changes made after the gs049/nn041 upgrade, then there is a need to downgrade to the previous patch level. You must use the config-lib utility to revert back to the latest configuration used at that downgraded patch level.
Call translation works for scenarios in which the terminating call control (TCC) is ISUP.
Currently only ITU ISUP variants are supported.
Related Documents
This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are listed below:
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Cisco Media Gateway Controller Hardware Installation Guide.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Management Information Base Guide.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites for Using This Feature
You must have Cisco MGC software Release 9.5(2). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.5(2).
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
Provisioning Prerequisites
This section lists the data that you must gather to successfully provision this feature. For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Collecting External Node Data
The external node component type represents another node with which the MGC communicates. You must be ready to enter the following data about the node:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Provisioning Procedures
Provision the transport path between the Cisco PGW 2200 and the external Cisco media gateway nodes. Communication between the Cisco PGW 2200 and the Cisco media gateways is provisioned so that there is a reliable communication path between the two platforms.
This provisioning is performed when a new external node is added to the Cisco PGW 2200. This section covers the following provisioning topics:
•
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate the changes you have made.
•
•
•
For more detailed information about provisioning your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver="curr_ver",dstver="mod_ver"Where:
•
–
–
Note
•
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you would enter the following command:
prov-sta::srcver="ver1",dstver="ver2"Once a provisioning session is underway, you can use the prov-add, prov-ed, and prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to provision this feature. For more information on provisioning other components on your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes, as described in the "Saving and Activating Your Provisioning Changes" section or ending your provisioning session without saving and activating your changes, as described in the "Ending a Provisioning Session Without Activating Your Changes" section.
Saving and Activating Your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution
The prov-cpy MML command is used to save and activate your changes on simplex Cisco MGC (single-host) systems.
Note
Caution
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs in a continuous-service system. This command should not be used on a Cisco MGC in a simplex configuration.
Note
Ending a Provisioning Session Without Activating Your Changes
If you want to end a provisioning session without saving and activating the changes you have entered, enter the prov-stp MML command. This command ends your current provisioning session, and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways you can use this command to retrieve provisioning data are described in the following sections:
•
•
•
•
•
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component in your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:name=MML_nameWhere:
•
•
For example, to view the provisioning data for an SS7 signaling service called ss7svc1, you would enter the following command:
prov-rtrv:ss7path:name="ss7svc1"The response to the command is dependent upon the component type associated with the desired component. For example, to view the properties for an SUA routing key called suakey1, you would enter the following command:
prov-rtrv:suakey:name="suakey1"Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:allRetrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:"all"Where: component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
For example, to view the provisioning data for all SS7 signaling services, you would enter the following command:
prov-rtrv:ss7path:"all"Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2004-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:variantsCreating Dial Plan Data
The following sections describe the tasks related to creating a dial plan for this feature:
•
Dial Plan Prerequisites
This section lists the data that you must gather to successfully create a dial plan as part of this feature. For more information on planning dial plans for other functions of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Dial Plan Basics
Use the procedures in this section describe how to add, modify, and delete dial plan data and to retrieve that data.
•
•
For more detailed information about creating a dial plan for your Cisco MGC, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Adding Dial Plan Data
The order in which you provision dial plan tables is important. Many tables refer to other tables that must be defined first. The following list identifies the recommended sequence for dial plan provisioning:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
To begin the process of creating a dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> numan-add:component:custgrpid=cust_groupID,param_name="param_value",...Where:
•
•
•
•
For example, to provision a route result type called resultone, you would enter the following command:
mml> numan-add:resulttable:custgrpid="t777",resulttype="route",setname="setone", name="resultone",dw1="rtlistone"Modifying an Element of Your Dial Plan Data
To modify an existing dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> numan-ed:component:custgrpid="cust_groupID",param_name="param_value",...Where:
•
•
•
•
For example, to modify a result table, you would enter the following command:
mml> numan-ed:resulttable:custgrpid="t777",resulttype="route",setname="setone", name="resulttwo",dw1="rtlistone"Deleting an Element from Your Dial Plan Data
To delete an element from your dial plan, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> numan-dlt:component:custgrpid="cust_groupID",name="MML_name"Where:
•
•
•
For example, to delete a result set called setone, you would enter the following command:
mml> numan-dlt:resultset:custgrpid="t001",name="setone"Retrieving Dial Plan Data
You can use the numan-rtrv MML command to retrieve information about your current dial plan settings. The ways in which you can use this command to retrieve dial plan data are described in the following sections:
•
•
Note
Retrieving Data for an Individual Component
You can retrieve dial plan data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> numan-rtrv:component:custgrpid="cust_groupID",name="MML_name"Where:
•
•
•
For example, to retrieve the settings for a result set called setone, you would enter the following command:
mml> numan-rtrv:resultset:custgrpid="t001",name="setone"Retrieving Data for All Components of a Particular Type
You can retrieve dial plan data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml> numan-rtrv:component:custgrpid="cust_groupID","all"Where:
•
•
For example, to retrieve the settings for all result sets in your dial plan, you would enter the following command:
mml> numan-rtrv:resultset:custgrpid="t001","all"Dial Plan Procedures
This section contains the procedures required for provisioning the dial plan data for this feature. For more information on creating dial plans for other functions of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Adding the BCMOD Result Type
To create the bearer capability table and add the BCMOD result type, complete the following steps:
Step 1
mml> numan-add:dialplan:custgrpid="dpl1",overdec="yes"Step 2
mml> numan-add:resultset:custgrpid="dpl1",name="set1"Step 3
mml> numan-add:BC:cusgrpid="dpl1",name="bc-04",ocval="9090A3"Step 4
mml> numan-add:resulttable:custgrpid="dp11",resulttype="BCMOD",dw1="bc-04",setname="set1", name="bc1"Where:
•
•
•
•
•
•
Step 5
Modifying the BCMOD Result Type
The BCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-ed MML command to modify the bearer capability table.
To modify the BCMOD result type, complete the following steps:
Step 1
mml> numan-ed:resulttable:cusgrpid="dpl1",resulttype="BCMOD",dw1="bc-05",setname="set1", name="bc1"Where:
•
•
•
•
•
•
This command modifies the BCMOD result type in the result table.
Step 2
mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1"Step 3
Deleting the BCMOD Result Type
The BCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-dlt MML command to delete an entry in the bearer capability table.
To delete an entry in the bearer capability table, complete the following steps:
Step 1
mml> numan-dlt:resulttable:cusgrpid="dpl1",resulttype="BCMOD",dw1="bc-05",setname="set1", name="bc1"This command deletes the BCMOD result type from the result table.
Step 2
mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1"Step 3
Adding the HLCMOD Result Type
Create the high-level capability table and add the high-level capability result type (HLCMOD) to the dial plan to modify the high level capability in the outgoing IAM by performing the following steps:
Step 1
mml> numan-add:dialplan:custgrpid="dpl2",overdec="yes"Step 2
mml> numan-add:resultset:custgrpid="dpl2",name="set3"Step 3
mml> numan-add:HLC:cusgrpid="dpl1",name="hlc-04",ocval="9184"Step 4
mml> numan-add:resulttable:custgrpid="dp12",resulttype="HLCMOD",dw1="hlc-04", setname="set3",name="result03"Where:
•
•
•
•
•
•
Step 5
Modifying the HLCMOD Result Type
The HLCMOD result type is used during A-number or B-number analysis to modify the bearer capability in the outgoing IAM. You can use the numan-ed MML command to modify the bearer capability table.
To modify the HLCMOD result type, complete the following steps:
Step 1
mml> numan-ed:resulttable:cusgrpid="dpl1",resulttype="HLCMOD",dw1="hlc-05",setname="set1", name="result03"Where:
•
•
•
•
•
•
This command modifies the HLCMOD result type in the result table.
Step 2
mml> numan-rtrv:BC:custgrpid="dpl1",setname="set1"Step 3
Deleting the HLCMOD Result Type
The HLCMOD result type is used during A-number or B-number analysis to modify the high-level capability in the outgoing IAM. You can use the numan-dlt MML command to delete an entry in the high-level capability table.
To delete an HLCMOD result type from the result table, complete the following steps:
Step 1
mml> numan-dlt:esulttable:cusgrpid="dpl1",resulttype="HLCMOD",dw1="hlc-05",setname="set1", name="result03"This command deletes the HLCMOD result type from the result table.
Step 2
mml> numan-rtrv:BC:custgrpid="dpl1",setname="set3"Step 3
Troubleshooting Dial Plan Data
The following sections contain troubleshooting procedures related to dial plan creation:
•
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Signaling Channel Troubleshooting Procedures
The following sections are procedures used to resolve problems associated with the Cisco MGC node's signaling connections to other networks:
•
Verifying Proper Loading of a Dial Plan
Step 1
If the dial plan was not loaded correctly, reload the dial plan by saving and activating your dial plan again as described in the "Saving and Activating Your Provisioning Changes" section.
If there are no logs that indicate that the dial plan was loaded incorrectly, proceed to Step 2.
Step 2
Dial Plan Examples
This section provides the following examples of dial plan provisioning for this feature. Additional examples of dial plan provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
mml> prov-sta::srcver="new",dstver="mod_ver01",confirmmml> numan-add:dialplan:custgrpid="T005",overdec="YES"mml> numan-add:resultset:custgrpid="T005",name="set001"mml> numan-add:resulttable:custgrpid="T005",setname="set001",name="result-bc", resulttype="BCMOD",dw1="data-2400-bc02"mml> numan-add:resulttable:custgrpid="T005",setname="set001",name="result-hlc", resulttype="HLCMOD",dw1="fax-hlc01"Reference Information
The following sections contain reference material related to this feature. Information is included on the following areas:
Result Type Definitions
Result analysis provides the capability to group actions into result sets that can be attached at different points of analysis. The main attachment points are: Pre-analysis, A-number analysis, B-number analysis, and Cause analysis.
The following result type definitions are added for this feature. For information on other result type definitions for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Table 1 shows the result type added for this feature.
Result Type Definitions
The following paragraphs contain definitions of the result types listed in Table 1.
BCMOD
The BCMOD result type is returned from A-number (the calling number) or B-number analysis (the called number) analysis indicating if the bearer capability name. The BCMOD result type dataword1 value indicates the bearer channel characteristics as being either fax or data and a baud rate.
Valid dataword1 BC Name values are: A string of as many as 20 alphanumerical characters
Note
Table 2 provides an example BCMOD result type values for dataword1 and a corresponding octet values (ocval).
Table 2 BCMOD Result Type BC Name and Octet Coding Value
fax-bc01
9090A3
data-2400-bc02
90902343403BD3
data-4800-bc03
90902345403BDC
data-9600-bc04
90902348403BDC
HLCMOD
The HLCMOD result type is returned from A-number (the calling number) or B-number analysis (the called number) indicating if the high layer compatibility name. The HLCMOD result type dataword1 value indicates the high layer compatibility characteristics as being either fax or data and a baud rate.
Valid dataword1 HLC Name value is: A string of as many as 20 alphanumerical characters
Table 3 is an example of an HLCMOD result type value for dataword1 and a corresponding octet value (ocval).
Dial Plan Worksheets
This section contains worksheets for the dial plan components required for this feature. For worksheets covering the rest of the dial plan components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.
Table 4 can be used for planning the BCMOD or HLCMOD result type and corresponding table entry.
Table 4 BCMOD / HLCMOD Result Type Worksheet
Dial plan
Result set name
Result table name
Result type
—dw1
—dw2
—dw3
—dw4
Set name
BC/HLC table entry
BCMOD/HLCMOD
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Cisco will continue to support documentation orders using the Ordering tool:
•
http://www.cisco.com/en/US/partner/ordering/
•
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
•
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.htm
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 5 contains expansions of acronyms and technical terms used in this feature module.
