This chapter describes how to implement the QSIG for Tool Command Language Interactive Voice Response (Tcl IVR) 2.0 feature. Q.SIG support is required for European countries to interconnect enterprise customers to a wholesale voice solution. The feature provides transparent Q.SIG interworking with a Tcl IVR 2.0 voice application on a Cisco IOS voice gateway. This functionality can be enabled using a new CLI on the POTS or VoIP dial-peer. Prior to this feature, Q.SIG messages were interpreted by the Tcl IVR 2.0 application, rather than passed transparently to the remote endpoint.
Feature benefits include the following:
Increased interconnection options for VoIP wholesale providers
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Configuring QSIG for Tcl IVR 2.0
Perform the prerequisites that are listed in the "Prerequisites for Configuring an ISDN Voice Interface" section.
Ensure that the VCWare version used for the Cisco AS5300 is compatible with the Cisco IOS image being used.
VCWare applies only to the Cisco AS5300.
Before configuring IVR Version 2.0 features, do the following:
Download the Tcl scripts and audio files to be used with this feature. Store them on a TFTP server configured to interact with your gateway access server.
Create the IVR/Tcl application script to use when configuring IVR. Store it on a server or at a location where it can be retrieved by the gateway access server. Then configure the server to use IVR with the application that you created.
Configure the dial peer on incoming POTS or VoIP dial peers.
Restrictions for Configuring QSIG for Tcl IVR 2.0
Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces". In addition, the following apply:
This feature is applicable to only the following:
VoIP and POTS dial peers
Tcl IVR version 2.0 only; not version 1.0
Information About QSIG for Tcl IVR 2.0
Q.SIG support is required for European countries to interconnect enterprise customers to a wholesale voice solution. The Q.SIG for Tcl IVR 2.0 feature provides transparent Q.SIG interworking when using a Tcl IVR version 2.0 voice application on a Cisco IOS voice gateway. This functionality can be enabled using a new CLI on the POTS or VoIP dial-peer. Prior to this feature, Q.SIG messages were interpreted by the Tcl IVR 2.0 application, rather than passed transparently to the remote endpoint.
General information about ISDN voice interfaces is presented in the "Information About ISDN Voice Interfaces" section.
Creates the application to be used with your IVR script and indicates the location of the corresponding Tcl files that implement this application. The location can be a URL, directory, or TFTP server.
Exits the current mode.
Configuring Supplementary Service for a POTS Dial Peer
To configure supplementary service for a POTS dial peer, perform the following steps.
The supplementary-servicepass-through command controls the interpretation of supplementary service (QSIG, H.450, and so on) on a gateway. When the CLI is enabled (that is, set to passthrough mode), the supplementary service message (usually in Q.931 facility message) is transparently sent to the destination gateway without any interpretation (raw). When the CLI is not enabled (the default), the supplementary service message is decoded and interpreted by the gateway. This CLI is available under VoIP or POTS dial peers.
This CLI has effect only if a Tcl IVR 2.0 application is configured on the same dial peer. The default session application always performs transparent Q.SIG interworking. Tcl IVR 1.0 applications always interpret and consume the Q.SIG supplementary services messages.
Command or Action
Enters privileged EXEC mode. Enter your password when prompted.
Router# configure terminal
Enters configuration mode.
Router(config)# dial-peer voice 99 pots
Enters voice dial-peer configuration mode for the specified POTS dial peer.
Router(config-dial-peer)# application ap1
Specifies the application that handles incoming voice calls associated with this dial-peer.
Configures supplementary service feature to transparently pass supplementary service to the next gateway.
Exits the current mode.
Verifying QSIG and Supplementary Service
To verify QSIG and supplementary service, perform the following steps (listed alphabetically).
Use this command to display the status of all ISDN interfaces, including active layers, timer information, and switch-type settings.
Use this command to display the basic router configuration.
Configuration Example for QSIG for Tcl IVR 2.0
The following sample output is typical of that for implementation of supplementary service. ISDN supplementary service messages from PBX 1 are sent transparently to PBX 2 by routers 1 and 2 as if PBX 1 and PBX 2 were connected directly to each other.
QSIG for Tcl IVR 2.0: Sample Network Topology
Router# show running-configBuilding configuration...Current configuration :3531 bytes!version 12.2service timestamps debug datetime msec localtimeservice timestamps log datetime msec localtimeno service password-encryptionservice internal!hostname router!no logging buffered!resource-pool disable!ip subnet-zeroip host jurai 188.8.131.52ip host dirt 184.108.40.206ip host CALLGEN-SECURITY-V2 220.127.116.11 18.104.22.168!trunk group 323!isdn switch-type primary-ni!voice service pots!fax interface-type modemmta receive maximum-recipients 0partition flash 2 8 8!controller T1 0 framing esf clock source line primary linecode b8zs ds0-group 1 timeslots 1-4 type e&m-fgb dtmf dnis cas-custom 1!translation-rule 1 Rule 1 ^.% 1!interface Ethernet0 ip address 172.19.140.96 255.255.255.0 no ip route-cache no ip mroute-cache squelch reduced!interface Serial1:23 no ip address no keepalive shutdown!ip classlessip route 0.0.0.0 0.0.0.0 172.19.140.1ip route 22.214.171.124 255.255.255.255 126.96.36.199no ip http server!snmp-server community public RWsnmp-server packetsize 4096!call rsvp-sync!voice-port 0:1!mgcp profile default!dial-peer cor custom!dial-peer voice 650 voip destination-pattern 650....... session target ipv4:188.8.131.52!dial-peer voice 100 pots application debit-card incoming called-number 650233.... direct-inward-dial supplementary-service pass-through port 0:1!dial-peer voice 1001 voip incoming called-number 650233....!dial-peer voice 12345602 voip supplementary-service pass-through!dial-peer hunt 6!line con 0 exec-timeout 0 0 logging synchronous level allline aux 0line vty 0 4 exec-timeout 60 0 password lab login!end
General ISDN References
"Overview of ISDN Voice Interfaces" --Describes relevant underlying technology; lists related documents, standards, MIBs, and RFCs; and describes how to obtain technical assistance
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.