![]() |
ISDN Voice Configuration Guide, Cisco IOS Release 15M&T
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
QSIG Support for Tcl IVR 2.0
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
QSIG Support for Tcl IVR 2.0Last Updated: December 4, 2012
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: Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 module. 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
Before configuring IVR Version 2.0 features, do the following:
Restrictions for Configuring QSIG for Tcl IVR 2.0Restrictions are described in the "Restrictions for Configuring ISDN Voice Interfaces". In addition, the following apply: Information About QSIG for Tcl IVR 2.0Q.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.
How to Configure QSIG for Tcl IVR 2.0
Configuring QSIGTo configure QSIG, perform the following steps.
DETAILED STEPS
Configuring Supplementary Service for a POTS Dial PeerTo configure supplementary service for a POTS dial peer, perform the following steps.
DETAILED STEPS
Configuring Supplementary Service for a VoIP Dial Peer
SUMMARY STEPS
DETAILED STEPS
Verifying QSIG and Supplementary Service
SUMMARY STEPS
DETAILED STEPS
Configuration Example for QSIG for Tcl IVR 2.0The 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.
Router# show running-config
Building configuration...
Current configuration :3531 bytes
!
version 12.2
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
no service password-encryption
service internal
!
hostname router
!
no logging buffered
!
resource-pool disable
!
ip subnet-zero
ip host jurai 223.255.254.254
ip host dirt 223.255.254.254
ip host CALLGEN-SECURITY-V2 15.90.60.59 1.82.0.0
!
trunk group 323
!
isdn switch-type primary-ni
!
voice service pots
!
fax interface-type modem
mta receive maximum-recipients 0
partition 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 classless
ip route 0.0.0.0 0.0.0.0 172.19.140.1
ip route 223.255.254.254 255.255.255.255 1.8.0.1
no ip http server
!
snmp-server community public RW
snmp-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:1.8.50.14
!
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 all
line aux 0
line vty 0 4
exec-timeout 60 0
password lab
login
!
end
Additional ReferencesReferences Mentioned in This Chapter
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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|