Table Of Contents
ISDN Generic Transparency Descriptor (GTD) for Setup Message
Prerequisites for ISDN GTD for Setup Message
Restrictions for ISDN GTD for Setup Message
Information About ISDN GTD for Setup Message
Benefits of ISDN GTD for Setup Message
Feature Design of ISDN GTD for Setup Message
ISDN IE to GTD Parameter Mapping
Mapping for Called Party Number (CPN), Calling Party Number (CGN) and Redirecting Information (RGN)
Mapping for Calling Party Number (CGN)
Mapping for Redirection Information (RNI)
Mapping for Originating Line Information (OLI)
Mapping for Bearer Capability (USI and TMR) Parameters
How to Configure ISDN GTD for Setup Message
Configuring ISDN GTD for Setup Message
Configuring OLI IE to Interface with MCI Switches
Configuring the OLI IE Identifier
Configuration Examples for ISDN GTD for Setup Message
Configuring GTD Mapping Example
ISDN Generic Transparency Descriptor (GTD) for Setup Message
The ISDN Generic Transparency Descriptor for Setup Message feature provides support for mapping ISDN information elements (IEs) to corresponding GTD parameters. The following IEs and parameters are supported:
•
Originating Line Information (OLI)
•
Bearer Capability (USI and TMR)
•
Called Party Number (CPN)
•
Calling Party Number (CGN)
•
Redirecting Number (RGN, OCN and RNI)
Feature Specifications for the ISDN Generic Transparency Descriptor for Setup Message Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for ISDN GTD for Setup Message
•
Restrictions for ISDN GTD for Setup Message
•
Information About ISDN GTD for Setup Message
•
How to Configure ISDN GTD for Setup Message
•
Configuration Examples for ISDN GTD for Setup Message
Prerequisites for ISDN GTD for Setup Message
You must configure your VoIP network and Cisco IOS gateways to allow sending and processing of ISDN Q.931 Setup messages.
Restrictions for ISDN GTD for Setup Message
The ISDN GTD for Setup Message feature does not support ISDN BRI calls.
Information About ISDN GTD for Setup Message
To configure the ISDN GTD for Setup Message feature, you need to understand the following concepts:
•
Benefits of ISDN GTD for Setup Message
•
Feature Design of ISDN GTD for Setup Message
•
ISDN IE to GTD Parameter Mapping
Benefits of ISDN GTD for Setup Message
•
Allows VoIP service providers to develop custom call treatments and enhanced service offerings based on call origination
•
Allows service providers to correctly identify the source of a call, bill appropriately, and settle accurately with other network providers
Feature Design of ISDN GTD for Setup Message
The ISDN GTD for Setup Message feature allows the delivery of information elements present in ISDN Setup messages to Toolkit Command Language (TCL) scripts, RADIUS accounting servers and routing servers in VOIP networks. This allows TCL scripts and routing servers to access ISDN signaling information to provide enhanced features and routing services. In particular the OLI IE present in AT&T (TR-41459 ISDN PRI UNI Specification) and MCI Setup messages can be passed to the `originating-line-info' VSA in RADIUS Start Accounting messages to identify the originating caller.
Federal Communications Commission (FCC) regulations mandate that pay telephone operators be compensated by network operators for 1-800 number calls made from their pay telephones. Prior to the implementation of the ISDN GTD for Setup Message feature, network operators had no way to identify calls made from their pay telephones. This inability resulted in network operators having to compensate pay telephone operators directly from their own revenues. In addition, network operators had no billing records to validate pay telephone operators' settlement requests to prevent fraud. The ISDN GTD for Setup Message feature provides Cisco networks the ability to correctly identify the source of a call. This feature allows networks to do the following:
•
Extract Originating Line Information (OLI) to identify pay telephone calls and pass on applicable charges
•
Generate billing records that can be used to validate pay telephone operator settlement requests. For information on accounting records and RADIUS billing, refer to RADIUS VSA Voice Implementation Guide.
The ISDN GTD for Setup Message feature provides the flexibility to identify other types of originated calls (from prisons, hotels, and so forth) and allows you to use the TCL interface to define custom services for these types of calls. For more information on TCL application programming, refer to TCL IVR API Version 2.0 Programmer's Guide.
In addition to passing OLI, this feature supports GTD mapping for Bearer Capability, Called Party Number, Calling Party Number, and Redirecting Number IEs.
Cisco implements this feature on Cisco IOS gateways by providing a mechanism to allow creating and passing the Q931 Setup message and its parameters in a GTD format. The Setup message, received by the gateway to initiate call establishment, is mapped to the GTD Initial Address Message (IAM). Generic transparency descriptors represent parameters within signaling messages and enable transport of signaling data in a standard format across network components and applications. The GTD mechanism allows them to share signaling data and achieve interworking between different signaling types. This feature supports only ISDN PRI and Non-Facility Associated Signaling (NFAS) calls.
ISDN IE to GTD Parameter Mapping
ISDN messages, used to signal call control, are composed of information elements and follow the format specified in ITU-T Q.931. The ISDN GTD for Setup Message feature supports only the mapping of Q931 Setup messages to GTD IAM messages. This section defines ISDN to GTD mapping for supported IEs and GTD parameters. Throughout this document parameters are referred to by both the parameter name, and the three character GTD code.
Table 1 defines the mapping of ISDN IEs to GTD parameters. The GTD mechanism also passes the following parameters for which there are no corresponding ISDN IEs:
•
Calling Party Category (CPC)
•
Forward Call Indicators (FCI)
•
Protocol Name (PRN)
Table 1 ISDN IEs Mapped to GTD Parameters
Note
GTD mapping allows a maximum of two redirecting number (original called number) IEs per call. If only one IE is present in the incoming Setup message, then both RGN and OCN parameters are built by the ISDN stack and the RGN and OCN parameters will contain the same values. If two IEs are present, then OCN contains information specified in the first IE and RGN contains information for the second IE. RNI contains redirection reasons. If only one IE is present then both the redirection reason (rr) field and original redirection reason (orr) field in the GTD RNI parameter contain the redirection reason indicated in the IE. When two IEs are present, then the GTD orr field indicates the redirection reason of the first IE and the GTD rr field indicates that of the second IE.
Mapping for Called Party Number (CPN), Calling Party Number (CGN) and Redirecting Information (RGN)
This section defines mapping for fields and values common to the CPN, CGN, and RGN GTD parameters carried in the GTD IAM message.
Table 2 defines mapping for ISDN type of number fields to GTD nature of address (noa) fields.
Table 2
Type of Number to Nature of Address Mapping
Table 3 defines mapping for ISDN numbering plan identification fields to GTD numbering plan indicator (npi) fields.
Table 3
Numbering Plan Identification to Numbering Plan Indicator Mapping
Table 4 defines mapping for ISDN and GTD presentation indicator (pi) fields.
Table 4
Presentation Indicator Mapping
Mapping for Calling Party Number (CGN)
Table 5 defines mapping for ISDN and GTD screening indicator (si) fields.
Table 5
Screening Indicator Mapping
Mapping for Redirection Information (RNI)
Table 6 defines mapping for the ISDN reason for redirection fields to GTD original redirection reason (orr) and redirection reason (rr) fields in the GTD RNI parameter.
Table 6 Reason for Redirection to Original Redirection Reason and Redirection Reason Mapping
Mapping for Originating Line Information (OLI)
Table 7 defines mapping for OLI fields.
Table 7 Originating Line Information Mapping
Mapping for Bearer Capability (USI and TMR) Parameters
The ISDN Bearer Capability IE is mapped to the GTD User Service Information (USI) and Transmission Medium Requirements (TMR) parameters. Table 8 defines mapping for coding standard fields and values.
Table 8 ISDN to GTD Coding Standard Mapping
Table 9 defines ISDN to GTD mapping for information transfer capability fields and values.
Table 9 Information Transfer Capability Mapping
Table 10 defines mapping for transfer mode fields and values.
Table 10 Transfer Mode Mapping
ISDN Transfer Mode GTD Transfer Mode (mode)0—circuit mode
c—circuit mode
2—packet mode
p—packet mode
Table 11 defines mapping for information transfer rate fields and values.
Table 11 Information Transfer Rate Mapping
Table 12 defines mapping for transmission medium requirements.
Table 12
Transmission Medium Requirements Mapping
Table 13 defines mapping for structure fields and values.
Table 13 Structure Mappings
Structure Structure (str)0—default
0—default or unknown
1—8 kHz integrity
1—8 kHz integrity
4—service data unit integrity
2—service data unit integrity
7—unstructured
3—unstructured
Table 14 defines mapping for configuration fields and values.
Table 14 Configuration Field Mapping
Table 15 defines mapping for establishment fields and values.
Table 15 Establishment Field Mapping
Table 16 defines mapping for symmetry fields and values.
Table 16 Symmetry Field Mapping
Table 17 defines mapping for Layer 1 protocol fields and values.
Table 17 Layer 1 Protocol Mapping
Table 18 defines mapping for synchronization fields and values.
Table 18 Synchronization Mapping
ISDN Synchronous/Asynchronous GTD Synchronization (sync)0—synchronous
y—synchronous
1—asynchronous
n—asynchronous
Table 19 defines mapping for negotiation fields and values.
Table 19 Negotiation Mapping
ISDN Negotiation GTD Negotiation (neg)0—in-band negotiation not possible
0—in-band negotiation not possible
1—in-band negotiation possible
1—in-band negotiation possible
Table 20 defines mapping for user rate fields and values.
Table 20 User Rate Mapping
Table 21 defines mapping for intermediate rate fields and values.
Table 21 Intermediate Rate Mapping
ISDN Intermediate Rate GTD Intermediate Rate (int)1—8 kbps
08—8 kbps
2—16 kbps
16—16 kbps
3—32 kbps
32—32 kbps
Table 22 defines mapping for network independent clock on transmission fields and values.
Table 22 Mapping for Network Independent Clock on Transmission
ISDN Network Independent Clock on TX ISDN Network Independent Clock on TX (txnic)0—not required to send data
n—not required to send data
1—required to send data
y—required to send data
Table 23 defines mapping for network independent clock on reception fields and values.
Table 23 Mapping for Network Independent Clock on Reception
ISDN Network Independent Clock on RX GTD Network Independent Clock on RX (rxnic)0—cannot accept data
n—cannot accept data
1—can accept data
y—can accept data
Table 24 defines mapping for flow control on transmission fields and values.
Table 24 Mapping for Flow Control on Transmission
ISDN Flow Control on TX GTD Flow Control on TX (txfl)0—not required to send data
n—not required to send data
1—required to send data
y—required to send data
Table 25 defines mapping for flow control on reception fields and values.
Table 25 Mapping for Flow Control on Reception
ISDN Flow Control on RX GTD Flow Control on RX (rxfl)0—cannot accept data
n—cannot accept data
1—can accept data
y—can accept data
Table 26 defines mapping for rate adaptation header fields and values.
Table 26 Mapping for Rate Adaptation Header
Table 27 defines mapping for multiframe establishment support for data link fields and values.
Table 27 Mapping for Multiframe Establishment (MFE) Support
ISDN MFE Support in Data Link GTD MFE Support in Data Link (mf)0—MFE not supported
n—MFE not supported
1—MFE supported
y—MFE supported
Table 28 defines mapping for mode of operation fields and values.
Table 28 Mode of Operation Mapping
Table 29 defines mapping for logical link identifier negotiation fields and values.
Table 29 Logical Link Identifier (LLI) Mapping
ISDN LLI Negotiation GTD LLI Negotiation (lli)0—default
0—default
1—full protocol negotiation
1—full protocol negotiation
Table 30 defines mapping for assignor and assignee fields and values.
Table 30 Mapping for Assignor and Assignee
Table 31 defines mapping for in-band and out-of-band negotiation fields and values.
Table 31 Mapping for Inband and Out-of-Band Negotiation
Table 32 defines mapping for fields and values for number of stop bits.
Table 32 Mapping for Number of Stop Bits
ISDN Number of Stop Bits GTD Number of Stop Bits (stp)1—1 bit
1—1 bit
2—1.5 bit
3—1.5 bit
3—2 bits
2—2 bits
Table 33 defines mapping for fields and values for number of data bits.
Table 33 Mapping for Number of Data Bits
ISDN Number of Data Bits GTD Number of Data Bits (dat)1—5 bits
5—5 bits
2—7 bits
7—7 bits
3—8 bits
8—8 bits
Table 34 defines mapping for parity information fields and values.
Table 34 Parity Mapping
ISDN Parity Information GTD Parity (par)0—odd
o—odd
2—even
e—even
3—none
n—none
4—forced to 0
0—forced to 0
5—forced to 1
1— forced to 1
Table 35 defines mapping for duplex mode fields and values.
Table 35 Duplex Mode Mapping
Table 36 defines mapping for modem type fields and values.
Table 36 Modem Type Mapping
Table 37 defines mapping for Layer 2 protocol fields and values.
Table 37 Layer 2 Protocol Mapping
Table 38 defines mapping for Layer 3 protocol fields and values.
Table 38 Layer 3 Protocol Mapping
How to Configure ISDN GTD for Setup Message
This section contains the following procedures.
•
Configuring ISDN GTD for Setup Message (optional)
•
Configuring OLI IE to Interface with MCI Switches (optional)
Configuring ISDN GTD for Setup Message
This feature is enabled by default; no configuration tasks are required to enable this feature. This task reenables the feature if it was disabled by using the no isdn gtd command.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface
4.
isdn gtd
DETAILED STEPS
Configuring OLI IE to Interface with MCI Switches
You must configure the Cisco IOS gateway to support the switch variant from which the gateway receives ISDN signaling. For a gateway that interfaces to an MCI switch or PBX, the OLI IE identifier for the MCI ISDN variant, as defined in CPE Requirements for MCI ISDN Primary Rate Interface, (014-0018-04.3D-ER, revision 4.3D, February 10, 1998), is configurable. Select the IE value that indicates OLI information to configure gateway support for the MCI ISDN variant.
Configuring the OLI IE Identifier
This task configures the OLI IE identifier value to support the MCI switch interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface
4.
isdn ie oli value
DETAILED STEPS
Examples
Use the show running-config command to verify configuration for the ISDN GTD for Setup Message feature. If GTD mapping is enabled, which is the default setting, the show running-config output does not display the isdn gtd command.
In the following sample out put, the isdn gtd command is disabled and the OLI IE value is set to 1F:
Router# show running-configBuilding configuration...Current configuration :4112 bytes!version 12.2no parser cacheservice timestamps debug datetime msecservice timestamps log uptimeno service password-encryption!hostname Router!boot system flash:c5300-i-mz.122-4.2no logging bufferedenable secretenable password!username guam passwordusername user1 passwordusername user2 passwordspe 2/0 2/7firmware location system:/ucode/mica_port_firmware!!resource-pool disable!ip subnet-zerono ip domain lookupip domain name cisco.comip host nlab-boot 172.21.200.2ip host dirt 172.69.1.129ip host dsbu-web.cisco.com 172.19.192.254 172.71.162.82ip host lab 172.19.192.254!isdn switch-type primary-niisdn gateway-max-interworking!!trunk group 1carrier-id cd1max-retry 2hunt-scheme random!!trunk group 2max-retry 2hunt-scheme random!!!voice service voip!!!no voice hpi capture bufferno voice hpi capture destination!!fax interface-type modemmta receive maximum-recipients 0!!controller T1 0framing esfclock source line primarylinecode b8zspri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 0no yellow generationno yellow detection!controller T1 1framing esfclock source line secondary 1linecode b8zspri-group timeslots 1-24 nfas_d backup nfas_int 1 nfas_group 0no yellow generationno yellow detection!controller T1 2framing esflinecode b8zspri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 0no yellow generationno yellow detection!controller T1 3framing esflinecode b8zspri-group timeslots 1-24no yellow generationno yellow detection!!interface Ethernet0ip address 10.0.44.29 255.255.255.0no ip route-cacheno ip mroute-cacheno cdp enable!interface Serial0:23ip address 10.1.1.2 255.255.255.0dialer map ip 10.1.1.1 name host 1111dialer-group 1isdn switch-type primary-niisdn protocol-emulate networkisdn T310 30000isdn negotiate-bchanisdn bchan-number-order descendingno cdp enable!interface Serial3:23ip address 10.9.9.9 255.255.255.0dialer map ip 10.8.8.8 name host 8888dialer map ip 10.8.8.8 255.255.255.0dialer-group 1isdn switch-type primary-net5isdn protocol-emulate networkisdn incoming-voice modemisdn disconnect-cause 126no isdn outgoing display-ieisdn ie oli 1Fno isdn gtdno cdp enable!interface FastEthernet0no ip addressno ip route-cacheno ip mroute-cacheshutdownduplex autospeed autono cdp enable!interface Group-Async1no ip addressencapsulation pppdialer in-banddialer-group 1no keepalivegroup-range 1 96!interface Dialer1ip address 10.2.2.2 255.255.255.0encapsulation pppno ip route-cacheno ip mroute-cachedialer remote-name hostdialer-group 1no fair-queue!interface Dialer2no ip addressno cdp enable!interface Dialer5ip address 10.1.1.1 255.0.0.0encapsulation pppno ip route-cacheno ip mroute-cachedialer in-banddialer map ip 10.1.1.2 name host 1234567dialer-group 1ppp authentication chap!ip default-gateway 10.0.44.1ip classlessip route 0.0.0.0 0.0.0.0 10.0.44.1ip route 0.0.0.0 0.0.0.0 Ethernet0no ip http server!!access-list 101 permit ip any anydialer-list 1 protocol ip permitno cdp run!snmp-server enable traps ttysnmp-server enable traps isdn layer2snmp-server host 10.1.1.1 public!call rsvp-sync!voice-port 0:D!voice-port 3:D!!mgcp profile default!dial-peer cor custom!!!dial-peer voice 2 voipdestination-pattern 111session target ipv4:10.0.45.87!dial-peer voice 10 potsdestination-pattern 9999direct-inward-dialport 3:Dprefix 9999!dial-peer voice 20 voipdestination-pattern 000000002.session target ipv4:10.0.44.28!dial-peer voice 50 potsdestination-pattern 2222direct-inward-dial

