Cisco Gateway Basic configuration
In order to activate the IVR on the voice gateway you only need to specify where applying the IVR. This will be done once because the further operations will be automatically managed by IVR Manager itself.
Supposing you have the company PSTN number 870978651 configured as follow:
dial-peer voice 1 pots incoming called-number 870978651 direct-inward-dial port 1/0
and you would like to add the main dispatcher running the day and night behavior as previously configured.
You only need to add the following command: service sv_main
The dial peer will become as follow:
dial-peer voice 1 pots service sv_main incoming called-number 870978651 direct-inward-dialport 1/0
Also add in global configuration mode the command:
application global service alternate DEFAULT
Should the dispatcher fail to load, the DEFAULT IVR Behavior will apply, i.e passing through the call without treating.
Cisco Gateway Advanced configuration
On Cisco voice gateways you can have for voice configuration:
- pots dial-peer
- voip dial-peer
Each of these can handle incoming and outgoing leg. Examples:
dial-peer voice 1 pots description THIS IS A POTS DIAL-PEER HANDLING AN INCOMING LEG USED FOR CALLS FROM PSTN incoming called-number 2978651 ! dial-peer voice 2 pots description THIS IS A POTS DIAL-PEER HANDLING AN OUTGOING LEG USED FOR CALLS TO PSTN destination pattern 0T port 1/0:15 (depending on the physical ISDN PRI/BRI or analog ports installed) ! dial-peer voice 3 voip description THIS IS A VOIP DIAL-PEER HANDLING AN INCOMING LEG. incoming called-number 7… dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 4 voip description THIS IS A VOIP DIAL-PEER HANDLING AN OUTGOING LEG. destination-pattern 8000 session target ipv4:<ip_address> dtmf-relay h245-alphanumeric codec g711ulaw no vad
But you can also collapse incoming and outgoing leg on the same dial-peer:
dial-peer voice 5 voip incoming called-number 7… destination-pattern 8000 session target ipv4:<ip_address> dtmf-relay h245-alphanumeric codec g711ulaw no vad
IVR on Voip dial-peer
Until this chapter we have always seen IVR scripts applied on pots dial-peer.
An important feature of IVR based on Cisco gateways is the capability to apply an IVR script to a voip dial-peer more than to a pots one.
Following a sample configuration of such case:
application global service alternate DEFAULT ! voice service voip allow-connections h323 to h323 ! voice translation-rule 9 rule 1 /.*/ /646/ ! voice translation-profile ivrmanager translate called 9 ! dial-peer voice 1 voip service sv_main translation-profile incoming ivrmanager incoming called-number 8888 // 8888 is a virtual number to catch the call for the IVR script dtmf-relay h245-alphanumeric codec g711ulaw no vad
Please, notice that an IVR behaviour triggered by a voip dial-peer cannot transfer to another IVR Manager dispatcher defined on the same router.
This article was:
Thank you for your feedback!