Configuring H.323-to-SIP Interworking

Configuring H.323-to-SIP Interworking

Figure 9-16 shows a sample book acclimated to configure H.323-to-SIP interworking with a

Cisco UBE router. The Cisco Unified Communications Manager array in San Jose routes

calls to the SIP carrier via a Cisco UBE router. The affiliation amid the Cisco Unified

Communications Manager and the Cisco UBE router is H.323 and the connection

between the Cisco UBE router and the SIP carrier is SIP.

Chapter 9: Establishing a Affiliation with an Internet Telephony Account Provider 541

IP IP

IP WAN

SIP

SIP Carrier

192.168.10.254

R1

Cisco UBE

Phone1-1

2001

Phone1-2

2002

San Jose

Cisco Unified Communications

Manager Cluster: 192.168.1.1

V

Figure 9-16 H.323-to-SIP Interworking Scenario

You can chase these accomplish to configure H.323-to-SIP interworking:

Step 1. Accredit H.323-to-SIP interworking.

Step 2. Configure H.323 and SIP punch aeon to avenue all-embracing calls amid the

Cisco Unified Communications Manager array and the SIP carrier.

Step 1: Enabling H.323-to-SIP Interworking

As with an H.323-to-H.323 connection, by absence a Cisco IOS aperture will not allow

connections amid an H.323 and a SIP VoIP punch peer. To change this behavior and

allow H.323-to-SIP connections, use the allow-connections h323 to sip command in

voice account agreement mode. Then affair the allow-connections sip to h323 command

to accredit SIP to H.323 calls, as approved in Example 9-4.

Example 9-4 H.323-to-SIP Interworking

R1(config)#voice account voip

R1(config-voice-service)#allow-connections h323 to sip

R1(config-voice-service)#allow-connections sip to h323

Step 2: Configuring Punch Peers

For a SIP (rtp-nte)-to-H.323 (h245-alphanumeric) alarm via a Cisco UBE router, if any RTP

named telephony accident (NTE) packets are beatific afore the H.323 endpoint answers the

call, the DTMF arresting is not heard on a absolute aperture (TGW).

542 Authorized Self-Study Guide: Cisco Articulation over IP (CVOICE)

Note alter achievement reveals that the H245 out-of-band letters are beatific to the TGW.

However, the digits are not heard on the phone.

To abstain sending both in-band and out-of-band tones to the approachable leg back sending

Cisco UBE calls in-band (rtp-nte) to out-of-band (h245-alphanumeric), configure the

dtmf-relay rtp-nte digit-drop command on the admission SIP punch peer. On the H.323

side, configure either dtmf-relay h245-alphanumeric or dtmf-relay h245-signal.

This can additionally be acclimated for H.323-to-SIP calls. Example 9-5 illustrates this dial-peer

configuration.

Example 9-5 Dial-Peer Configuration

R1(config)#dial-peer articulation 2000 voip

R1(config-dial-peer)#description To Cisco Unified Communications Manager

R1(config-dial-peer)#destination-pattern 2...

R1(config-dial-peer)#session ambition ipv4:192.168.1.1

R1(config-dial-peer)#dtmf-relay h245-alphanumeric

R1(config-dial-peer)#exit

R1(config)#dial-peer articulation 9011 voip

R1(config-dial-peer)#description To All-embracing SIP Carrier

R1(config-dial-peer)#session agreement sipv2

R1(config-dial-peer)#destination-pattern 9011T

R1(config-dial-peer)#session ambition ipv4:192.168.10.254

R1(config-dial-peer)#dtmf-relay rtp-nte digit-drop h245-alphanumeric