Cisco IOS Tcl IVR and VoiceXML Application Guide - 12.3(14)T and later - Configuring Telephony Call-Redirect Features [Cisco IOS Software Releases 12.3 T]

Table Of Contents

Configuring Telephony Call-Redirect Features

Contents

Prerequisites

Restrictions

Information About Telephony Call-Redirect Features

Benefits

GTD Parameters

Release-to-Pivot

Two B-Channel Transfer

ETSI Call Transfer

How to Configure Telephony Call-Redirect Features

Configuring Call-Transfer Method for Voice Applications

Configuring the Parameter Routing Method

Configuring the Call Rerouting Method

Verifying the Call-Transfer Method for Voice Applications

Troubleshooting Tips

Enabling RTPvt

Enabling TBCT for Trunk Groups

Configuring Outbound Dial Peer for TBCT Calls

Configuring TBCT Call Limits

Terminating Billing for Active TBCT Calls

Verifying TBCT

Enabling ETSI Call Transfer

Configuration Examples

TBCT Trunk Group Example

TBCT with Notify on Clear Example

ETSI Call Transfer Example

Where to Go Next

Additional References

Configuring Telephony Call-Redirect Features

Call-redirect features enable call transfer, call forwarding, and call disconnect capabilities on Cisco voice gateways. Voice applications support the Release-to-Pivot (RTPvt) and ISDN Two B-Channel Transfer (TBCT) call-redirect features, and have expanded abilities to receive and send generic transparency descriptor (GTD) information. These features are grouped under the feature name "Voice Application Call Control Enhancements."

For more information about this and related Cisco IOS voice features, see the following:

•Overview of Cisco IOS Tcl IVR and VoiceXML Applications

•Entire Cisco IOS Voice Configuration Library—including library preface and glossary, other feature documents, and troubleshooting documentation—at http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_voice_configuration_library_glossary/vcl.htm

Note For releases prior to Cisco IOS Release 12.3(14)T, see the previous version of the Cisco Tcl IVR and VoiceXML Application Guide at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vvfax_c/tcl_leg/index.htm

Feature History for Telephony Call-Redirect Features

Release

Modification

12.3(1)

The Voice Application Call Control Enhancements feature was introduced.

12.3(8)T

The ETSI Call Transfer feature was introduced.

12.3(14)T

A new command-line interface structure for configuring Tcl and IVR applications was introduced and affected the commands for configuring this feature.

Contents

•Prerequisites

•Restrictions

•Information About Telephony Call-Redirect Features

•How to Configure Telephony Call-Redirect Features

•Configuration Examples

•Where to Go Next

•Additional References

Prerequisites

General

•Cisco voice gateway must have Cisco IOS Release 12.3(1) or later.

•Cisco voice gateway must have the prerequisite configuration that is described in the "Prerequisite" section of the Cisco IOS TCL IVR and VoiceXML Application Guide.

RTPvt

•Cisco voice gateway must support the Cisco SC2200 signaling controller. For configuration instructions, see the Cisco SC2200 Signaling Controller documentation.

TBCT

•PRI must subscribe to TBCT service from the ISDN switch provider.

•You must write a TCL IVR 2.0 script or VoiceXML 2.0 document that specifies carrier ID properties for TBCT trunks. For information, see the TCL IVR API Version 2.0 Programmer's Guide or Cisco VoiceXML Programmer's Guide.

•Authentication, Authorization, and Accounting (AAA) must be configured on the Cisco voice gateway. For instructions, see the Cisco IOS Security Configuration Guide, Release 12.3.

•ISDN switch must notify the Cisco voice gateway when calls clear to support billing.

GTDs

•GTD generation must be enabled on the Cisco voice gateway. For configuration steps, see the following resources:

–GTD for GKTMP Using SS7 Interconnect for Voice Gatekeeper Version 2.0

–R2 and ISUP Transparency for Voice Gateways Version 2.0

Restrictions

•TBCT supports the National ISDN-2 (NI-2) standard for T1 only. E1 interfaces are not supported.

•An outgoing TBCT call must use the same trunk group as the incoming call.

•GTD parameter transport is supported for H.323 only; it is not supported for SIP.

Information About Telephony Call-Redirect Features

To configure call-control features, you should understand the following concepts:

•Benefits

•GTD Parameters

•Release-to-Pivot

•Two B-Channel Transfer

•ETSI Call Transfer

Benefits

•RTPvt enables optimal routing of calls in ISUP networks.

•TBCT optimizes PRI resources by freeing up the gateway's bearer channels.

•User is charged only once for a redirected call.

•Cisco voice applications can append and override GTD parameters for redirected calls.

GTD Parameters

GTD objects are used to represent ISDN User Part (ISUP) messages, parameters, and R2 signals. These objects are encapsulated into existing signaling protocols (for example, H.225), facilitating end-to-end transport. Using GTD as a transport mechanism for signaling data in Cisco IOS software provides a common format for sharing signaling data among various components in a network and for interworking various signaling protocols.

GTD enhancements introduced in this feature include the following:

•VoiceXML applications can append and override GTD parameters on incoming call legs.

•VoiceXML applications can access GTD parameters on outgoing call legs after a transfer is complete using VoiceXML shadow variables.

•TCL IVR applications can append and override GTD parameters.

For detailed information about GTD parameters and how to implement them in a voice application, see the following resources:

•TCL IVR API Version 2.0 Programmer's Guide

•Cisco VoiceXML Programmer's Guide

Release-to-Pivot

Release-to-Pivot (RTPvt) is a call-redirect method for SS7 networks. It allows a switch to release a call to another switch located earlier in the call path when the originating switch determines that the call should be connected to a new destination number. The preceding switch reoriginates the call directly to the new destination address.

RTPvt provides optimal rerouting capabilities. It frees up trunking and switching resources by rerouting calls that would otherwise be hair-pinned. Hairpinning occurs when an incoming PSTN call cannot be delivered over IP so the call is looped back out to the PSTN. RTPvt is equivalent to the ISDN PRI Two B-Channel Transfer standard.

The following describes the call flow for a release to pivot scenario:

1. The PSTN caller dials a destination number on switch B, for example, 555-0112.

2. The originating switch A, which is pivot-capable, sends an ISUP message with the Called Party Number (555-0112) and Redirect Capability (RDC) parameter to switch B.

3. Switch B answers the call.

4. Switch B determines that the call must be redirected to a new destination number (555-0199).

5. Switch A performs the pivot reroute and sends an ISUP message with the new Called Party Number (555-0199) to switch C.

Figure 9-1 illustrates the preceding call-flow scenario:

Figure 9-1 Release-To-Pivot Example

For a TCL application, RTPvt can be invoked at different stages of the call flow, depending on the redirect capability of the originating switch. For a VoiceXML application, RTPvt can be invoked only after the call is answered.

Two B-Channel Transfer

Two B-Channel Transfer (TBCT) is a call-transfer standard for ISDN interfaces. This feature enables a Cisco voice gateway to request an NI-2 switch to directly connect two independent calls. The two calls can be served by the same PRI or by two different PRIs on the gateway. This feature is based on Telcordia GR-2865-CORE.

TBCT makes efficient use of resources by releasing two B channels after a call transfer. Blind transfer of PSTN calls can happen outside the Cisco gateway without tying up gateway resources.

Although the gateway is not involved after calls are transferred, billing continues as though the calls are still connected to the gateway. Customers using this feature need to have special agreements with their ISDN service provider regarding billing, or optionally, the gateway can subscribe to get notification from the switch when a transferred call clears.

To use TBCT, the following conditions must be met:

•PRI interface is subscribed to TBCT service from ISDN service provider.

•Both calls are voice calls.

•Both calls use the same PRI or both PRIs are part of the same trunk group.

•Incoming call is answered.

•Transfer-to number is placed as a separate call.

ETSI Call Transfer

Support is provided for European Telecommunications Standards Institute (ETSI) explicit call transfer functionality on Cisco IOS gateways. The ECT supplementary service enables a user who has two calls, each of which can be either an incoming call or an outgoing call, to connect one of the active calls to another active or alerting call.

Note As of Cisco IOS Release 12.3(8)T, ETSI call transfer is supported only for active calls, not for calls on hold.

ETSI call transfer is enabled using the TBCT for Trunk Groups feature. See Enabling TBCT for Trunk Groups for more information.

How to Configure Telephony Call-Redirect Features

See the following sections for configuration tasks for call-control features.

•Configuring Call-Transfer Method for Voice Applications (required)

•Enabling RTPvt (required)

•Enabling TBCT for Trunk Groups (required)

•Configuring Outbound Dial Peer for TBCT Calls (required)

•Configuring TBCT Call Limits (optional)

•Terminating Billing for Active TBCT Calls (optional)

•Enabling ETSI Call Transfer (optional)

Configuring Call-Transfer Method for Voice Applications

You can configure the call-transfer method on the gateway or through properties in the VoiceXML document or Tcl script. For information on configuring the call-transfer method by using VoiceXML or Tcl properties, see the Cisco VoiceXML Programmer's Guide or Tcl IVR API Version 2.0 Programmer's Guide, respectively.

Note The call-transfer method specified in a VoiceXML document or Tcl script takes precedence over the method specified in the Cisco gateway configuration. Any value that is configured on the gateway is ignored if the same attribute is specified using a VoiceXML or Tcl property.

Configuring the Parameter Routing Method

The param mode command is used to configure the default behavior of the callsetup package during the initial attempt to place a call to the specified destination. The callsetup package is used by applications and other packages to place outbound call legs and interwork them with incoming call legs.

To configure the parameter routing method, perform the following steps:

SUMMARY STEPS

1. enable

2. configure terminal

3. application

4. service service-name

5. paramspace callsetup mode {redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | rotary}

6. exit

7. package callsetup

8. param mode {redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | rotary}

DETAILED STEPS

Step 1 Enable privileged EXEC mode:
enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:
configure terminal
Example: Router# configure terminal
Step 3 Enter application configuration mode to configure applications and services:
application
Example: Router(config)# application
Step 4 Enter service parameter configuration mode:
service service-name
Example: Router(config-app)# service fax_detect
Step 5 Configure the callsetup parameterspace mode:
paramspace callsetup mode {redirect | redirect-at-alert | redirect-at-connect | 
redirect-rotary | rotary}
Example: Router(config-app-param)# paramspace callsetup mode redirect-rotary

Step 6 Exit the parameterspace configuration mode:
exit 
Example: Router(config-app-param)# exit

Step 7 Enter callsetup package parameter configuration mode:
package callsetup
Example: Router(config-app)# package callsetup
Step 8 Configure the parameter mode:
param mode {redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | 
rotary}
Example: Router(config-app-param)# param mode redirect
Configuring the Call Rerouting Method

The param reroutemode command is used to configure the default behavior of the callsetup package during the redirect attempt to place a call to the specified destination.This scenario occurs when the initial attempt at placing a call to the original destination is redirected by the destination endpoint to a new endpoint.

To configure the call rerouting method, perform the following steps:

SUMMARY STEPS

1. enable

2. configure terminal

3. application

4. service service-name

5. paramspace callsetup reroutemode {redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | rotary}

6. exit

7. package callsetup

8. param reroutemode {redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | rotary}

DETAILED STEPS

Step 1 Enable privileged EXEC mode:
enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:
configure terminal
Example: Router# configure terminal
Step 3 Enter application configuration mode to configure applications and services:
application
Example: Router(config)# application
Step 4 Enter service parameter configuration mode:
service service-name
Example: Router(config-app)# service fax_detect
Step 5 Configure the callsetup parameterspace mode:
{redirect | redirect-at-alert | redirect-at-connect | redirect-rotary | rotary}
Example: Router(config-app-param)# paramspace callsetup reroutemode redirect-rotary

Step 6 Exit parameter configuration mode:
exit 
Example: Router(config-app-param)# exit

Step 7 Enter callsetup package parameter configuration mode:
package callsetup
Example: Router(config-app)# package callsetup
Step 8 Configure the parameter reroute mode:
param reroutemode {redirect | redirect-at-alert | redirect-at-connect | 
redirect-rotary | rotary} 
Example: Router(config-app-param)# param reroutemode redirect
Verifying the Call-Transfer Method for Voice Applications

To verify the call-transfer method for voice applications, use the show running-config command.
application
.
.
.
!
 package callsetup
  param mode redirect-rotary
  param reroutemode redirect
.
.
.
service fax_detect flash:app_fax_detect.2.1.2.2.tcl
  paramspace callsetup mode redirect-rotary
  param pin-len 4
  paramspace app_debitcard warning-time 60
.
.
.
Troubleshooting Tips

If the call-transfer configuration is not successful, verify the following:

•The applications are loaded on the dial peer.

•The parameters and parameterspaces you are configuring are contained in the applications.

Enabling RTPvt

No additional Cisco IOS configuration is required on the gateway to implement RTPvt, other than configuring the call-transfer method as described in the "Configuring Call-Transfer Method for Voice Applications" section. A TCL IVR script or VoiceXML document triggers RTPvt in response to the GTD Redirect Capability (RDC) parameter.

For detailed information on triggering RTPvt through a TCL IVR script or VoiceXML document, see the following documentation:

•TCL IVR API Version 2.0 Programmer's Guide

•Cisco VoiceXML Programmer's Guide

Enabling TBCT for Trunk Groups

To enable TBCT on multiple PRIs, all PRIs must be configured as part of the same trunk group. To create the trunk group and enable TBCT, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. isdn switch-type switch-type

4. trunk group name

5. carrier-id name [cic]

6. isdn supp-service tbct [notify-on-clear]

7. exit

8. interface serial controller:timeslot

9. trunk-group name [preference_num]

10. exit

11. Repeat Steps 8 to 10 for each interface added to the trunk group.

DETAILED STEPS

Step 1 Enable privileged EXEC mode:

enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:

configure terminal
Example: Router# configure terminal
Step 3 Specify the central office switch type on the PRI:

isdn switch-type switch-type
Example: Router(config)# isdn switch-type primary-ni
To support TBCT, the switch type must conform to the NI-2 standard. For ETSI Call Transfer, the switch type should be primary-net5.

Step 4 Enter trunk group configuration mode for the named trunk group:

trunk group name
Example: Router(config)# trunk group 1
Step 5 Specify the carrier associated with the trunk group:

carrier-id name [cic]
Example: Router(config-trunk-group)# carrier-id north1
Step 6 Enable TBCT support for the trunk group:

isdn supp-service tbct [notify-on-clear]
Example: Router(config-trunk-group)# isdn supp-service tbct notify-on-clear

Note For ETSI Call Transfer, notify-on-clear is not supported.

Step 7 Exit trunk group configuration mode and return to global configuration mode:

exit
Example: Router(config-trunk-group)# exit
Step 8 Enter interface configuration mode for a PRI that you want to assign to the trunk group:

interface serial controller:timeslot
Example: Router(config)# interface serial 0:23

Note Controller value is platform-dependent.

Step 9 Assign the PRI to the trunk group:

trunk-group name [preference_num]
Example: Router(config-if)# trunk-group 1
Use the name of the trunk group that was defined by using the trunk group command in Step 4.

Step 10 Exit interface configuration mode and return to global configuration mode:

exit
Example: Router(config-if)# exit
Step 11 Repeat Steps 8 to 10 for each interfaces that you want to add to the trunk group.

Configuring Outbound Dial Peer for TBCT Calls

The gateway must send an outgoing TBCT call over the same trunk as the incoming call. To assign the trunk group to an outbound dial peer and select the outbound dial peer based on the carrier ID, perform the following steps.

Note You must also specify carrier ID properties in the TCL IVR script or VoiceXML document. For information on setting the carrier ID properties for TBCT, see the TCL IVR API Version 2.0 Programmer's Guide or Cisco VoiceXML Programmer's Guide.

SUMMARY STEPS

1. enable

2. configure terminal

3. dial-peer voice number pots

4. trunkgroup name

5. carrier-id target name

6. exit

DETAILED STEPS

Step 1 Enable privileged EXEC mode:

enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:

configure terminal
Example: Router# configure terminal
Step 3 Enter dial-peer configuration mode for a POTS dial peer:

dial-peer voice number pots
Example: Router(config)# dial-peer voice 100 pots
Step 4 Associate the trunk group with this dial peer:

trunkgroup name
Example: Router(config-dial-peer)# trunkgroup 1
Use the name of the trunk group that was defined by using the trunk group command in Step 4 of the "Enabling TBCT for Trunk Groups" section.

Step 5 Specify the carrier ID that is used as the match criteria when selecting an outbound dial-peer:

carrier-id target name
Example: Router(config-dial-peer)# carrier-id target north1
Set this target carrier ID to match the source carrier ID that was specified in Step 5 of the "Enabling TBCT for Trunk Groups" section.

Step 6 Exit dial-peer configuration mode and return to global configuration mode:

exit
Example: Router(config-trunk-group)# exit

Configuring TBCT Call Limits

This section includes the commands for setting limits on the number and duration of active TBCT calls that the gateway tracks.

Note Configuring TBCT call limits is relevant only if you have enabled the ISDN switch to notify the gateway when a call clears and you use the notify-on-clear keyword with the isdn supp-service tbct command.

SUMMARY STEPS

1. enable

2. configure terminal

3. tbct max calls number

4. tbct max call duration minutes

DETAILED STEPS

Step 1 Enable privileged EXEC mode:

enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:

configure terminal
Example: Router# configure terminal
Step 3 Specify the maximum number of active TBCT calls that are allowed by the gateway:

tbct max calls number
Example: Router(config)# tbct max calls 50
Step 4 Specify the maximum number of minutes before a TBCT call is cleared by the gateway:

tbct max call duration minutes
Example: Router(config)# tbct max call duration 10

Terminating Billing for Active TBCT Calls

SUMMARY STEPS

1. enable

2. tbct clear call {all | interface [call-tag]}

DETAILED STEPS

Step 1 Enable privileged EXEC mode:

enable
Example: Router> enable
Enter your password if prompted.

Step 2 Terminate billing for one or more TBCT calls:

tbct clear call {all | interface [call-tag]}
Example: Router# tbct clear call T1-6/0

Verifying TBCT

SUMMARY STEPS

1. show running-config

2. show call application voice application-name

3. show call active voice redirect tbct

DETAILED STEPS

Step 1 Use the show running-config command to verify that the application is configured on the gateway and that its transfer method is set to one of the redirect options, for example:
Router# show running-config
...
!
application
 service callme tftp://10.10.10.1/scripts/call.vxml
paramspace callsetup mode redirect
!
Step 2 Use the show call application voice command to verify that the application is loaded onto the gateway and to verify the redirect method. The following example shows output for the application named callme:
Router# show call application voice callme
VXML Application callme
    URL=tftp://10.10.10.1/scripts/call.vxml
    Security not trusted
    No languages configured
    It has: 0 calls active.
            0 incoming calls
            0 calls handed off to it
            0 call transfers initiated
            0 pages loaded,  0 successful
            0 prompts played
            0 recorded messages
            The transfer mode is 'redirect'
    Interpreted by Voice Browser Version 2.0 for VoiceXML 1.0 & 2.0.
The VXML Script is:
------------------
<?xml version="1.0"?>
<vxml version="1.0">
   <form id="record_to_ram">
      <record name="myrec" 
              beep="true" 
              maxtime="10s" 
 --More-- 
Translating "Program"
              dtmfterm="true" 
              finalsilence="10ms"
              type="audio/basic;codec=g711ulaw">
          <prompt><audio src="flash:record.au"/></prompt>
        <filled namelist="myrec">
            <prompt><value expr="myrec"/></prompt>
            <clear namelist="myrec"/>
        </filled>
      </record>
   </form>
</vxml>
Step 3 Use the show call active voice redirect tbct command to verify that an active call is using TBCT, for example:
Router# show call active voice redirect tbct
TBCT:
        Maximum no. of TBCT calls allowed:No limit
        Maximum TBCT call duration:No limit
Total number TBCT calls currently being monitored = 1
ctrl name=T1-2/0, tag=13, call-ids=(7, 8), start_time=*00:12:25.985 UTC Mon Mar 1 1993
Tip For a detailed description of the output from these commands, see the Cisco IOS Voice Command Reference, Release 12.3 T.

Enabling ETSI Call Transfer

To enable support for ETSI call transfer for multiple PRIs, you must configure the PRIs as part of the same trunk group on the gateway. To create the trunk groups and enable ETSI call transfer, perform the following steps.

SUMMARY STEPS

1. enable

2. configure terminal

3. isdn switch-type switch-type

4. trunk group name

5. isdn supp-service tbct

6. exit

7. dial-peer voice number pots

8. destination-pattern [+] string [T]

9. trunk-group name [preference_num]

10. exit

11. interface serial controller:timeslot

12. trunk-group name [preference_num]

13. exit

14. Repeat Steps 11 to 12 for each interface added to the trunk group.

DETAILED STEPS

Step 1 Enable privileged EXEC mode:

enable
Example: Router> enable
Enter your password if prompted.

Step 2 Enter global configuration mode:

configure terminal
Example: Router# configure terminal
Step 3 Specify the central office switch type on the PRI. For ETSI Call Transfer, the switch type must be primary-net5.

isdn switch-type switch-type
Example: Router(config)# isdn switch-type primary-net5
Step 4 Enter trunk group configuration mode for the named trunk group:

trunk group name
Example: Router(config)# trunk group 1
Step 5 Enable ETSI support for the trunk group:

isdn supp-service tbct
Example: Router(config-trunk-group)# isdn supp-service tbct

Note For ETSI Call Transfer, notify-on-clear is not supported.

Step 6 Exit trunk group configuration mode and return to global configuration mode:

exit
Example: Router(config-trunk-group)# exit
Step 7 Enter dial-peer configuration mode for a POTS dial peer:

dial-peer voice number pots
Example: Router(config)# dial-peer voice 100 pots
Step 8 Enter the destination pattern for the dial peer. For example, if you enter the telephone number of a user, and TBCT or ETSI Call Transfer is configured on the trunk group, calls to that user will be transferred using only PRIs in the trunk group that has TBCT or ETSI Call Transfer configured.
destination-pattern [+] string [T] 
Example: Router(config-dial-peer)# destination-pattern +5557922
Step 9 Associate the trunk group with this dial peer:

trunkgroup name
Example: Router(config-dial-peer)# trunkgroup 1
Step 10 Exit dial-peer configuration mode:

exit
Example: Router(config)# exit
Step 11 Enter interface configuration mode for a PRI that you want to assign to the trunk group:

interface serial controller:timeslot
Example: Router(config)# interface serial 0:23

Note Controller value is platform-dependent.

Step 12 Assign the PRI to the trunk group:

trunk-group name [preference_num]
Example: Router(config-if)# trunk-group 1
Use the name of the trunk group that was defined by using the trunk group command in Step 4.

Step 13 Exit interface configuration mode and return to global configuration mode:

exit
Example: Router(config-if)# exit
Step 14 Repeat Steps 11 to 12 for each interfaces that you want to add to the trunk group.

Configuration Examples

This section provides the following configuration examples:

•TBCT Trunk Group Example

•TBCT with Notify on Clear Example

•ETSI Call Transfer Example

TBCT Trunk Group Example
!
isdn switch-type primary-ni
!
!
trunk group  1
 carrier-id north1
 isdn supp-service tbct
!
trunk group  2
 carrier-id south2
 isdn supp-service tbct
...
controller T1 1/0
 framing esf
 clock source line primary
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/1
 framing esf
 clock source line secondary 1
 linecode b8zs
 pri-group timeslots 1-24
!
interface Serial1/0:23
 no ip address
 no logging event link-status
 isdn switch-type primary-ni
 isdn incoming-voice modem
 trunk-group 1
 no cdp enable
!
interface Serial1/1:23
 no ip address
 no logging event link-status
 isdn switch-type primary-ni
 isdn incoming-voice modem
 trunk-group 2
 no cdp enable
...
application
 service tbct-app tftp://server1/scripts/TBCTalert.vxml
!
dial-peer voice 100 pots
 service tbct-app
 incoming called-number 5550112
 direct-inward-dial
 port 1/1:23
!
dial-peer voice 101 pots
 trunkgroup 1
 carrier-id target north1
!
dial-peer voice 102 pots
 trunkgroup 2
 carrier-id target south2
! 
TBCT with Notify on Clear Example
...
interface Serial1/1:23 
 no ip address 
 isdn supp-service tbct notify-on-clear 
 isdn switch-type primary-ni 
 isdn incoming-voice modem 
! 
ETSI Call Transfer Example

The following is a sample configuration of the ETSI Call Transfer Feature:

Trunk Group Configuration
...
trunk group 1
isdn supp-service tbct
...
dial-peer voip 10 pots
! Configures the POTS dial peer and points it to trunk group 1
...
destination-pattern 000000001
trunkgroup 1
...
int s0:23 
trunk-group 1
! Includes interface s0:23 in trunk group 1
...
int s1:23 
trunk-group 1
! Includes interface s1:23 in trunk group 1
...
int s2:23
trunk-group 2
! Includes interface s2:23 in trunk group 2
...

PRI Configuration
...
int s0:23	
isdn supp-service tbct
...
dial-peer voice 20 pots
! Configures the POTS dial peer and points it to trunk group 1
...
destination-pattern 000000002
port 0:D
! Points interface s0:23 to this dial peer
...
Where to Go Next

•To configure properties for audio files, see "Configuring Audio File Properties for Tcl IVR and VoiceXML Applications".

•To configure voice recording using a VoiceXML application, see "Configuring VoiceXML Voice Store and Forward".

•To configure properties for speech recognition or speech synthesis, see "Configuring ASR and TTS Properties".

•To configure a VoiceXML fax detection application, see "Configuring Fax Detection for VoiceXML".

•To configure session interaction for a TCL IVR 2.0 application, see "Configuring Tcl IVR 2.0 Session Interaction".

•To configure support for SIP and TEL URLs, see "Configuring SIP and TEL URL Support" on page 245.

•To monitor and troubleshoot voice applications, see "Monitoring and Troubleshooting Voice Applications".

Additional References

•—Describes how to access Cisco Feature Navigator; also lists and describes, by Cisco IOS release, TCL IVR and VoiceXML features for that release

•Overview of Cisco IOS Tcl IVR and VoiceXML Applications—Describes underlying Cisco IOS TCL IVR and VoiceXML technology; also lists related documents, standards, MIBs, RFCs, and how to obtain technical assistance