Bitswap

Archive for the ‘4.07 IP-IP Gateway/CUBE’ Category

Configuration for IP-to-IP Gateway

Posted by Andy on May 7, 2009

Example 8-12 Configuration for IP-to-IP Gateway

voice service voip

allow-connections h323 to h323

supplementary-service h450.2

supplementary-service h450.3

supplementary-service h450.12

h323

emptycapability

h225 id-passthru

h225 connect-passthru

h245 passthru tcsnonstd-passthru

interface Loopback0

ip address 2.1.1.1 255.255.255.0

h323-gateway voip interface

h323-gateway voip id IPIPGW-zone ipaddr 1.1.1.1 1719

h323-gateway voip h323-id IPIPGW

h323-gateway voip bind srcaddr 2.1.1.1

dial-peer voice 1 voip /* To Unified CM endpoints */

destination-pattern 4…

session target ras

dtmf-relay h245-alphanumeric

codec g729r8

no vad

dial-peer voice 1 voip /* To Unified CME endpoints */

destination-pattern 3….

session target ras

dtmf-relay h245-alphanumeric

codec g729r8

no vad

via Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 7.x РCall Processing  [Cisco Unified Communications Manager (CallManager)] РCisco Systems.

Advertisements

Posted in 4.00 Implement and Troubleshoot Voice Gateways, 4.03 H.323, 4.07 IP-IP Gateway/CUBE | Leave a Comment »

Lab #1

Posted by Andy on March 26, 2009

Register phones according to table 1 of https://bitswap.wordpress.com/2009/03/25/t/

1D 7940 as SIP on CME1
43 7960+7914 as SCCP on CME1
CD 7961 as SIP on CME2
8A 7940 as SCCP on CME2
E7 7960 as SIP on CM
9B 7960 as SIP on CM
31 7941 as SCCP on CM

Test call completion, calling/ed name presentation , issues
CM1->CM2(forwarded to neighbor)
CM1->CM2(forwarded to CM1)
CM1->CM2(forwarded to CM)

CM->CM2(forwarded to neighbor)
CM->CM2(forwarded to CM1)
CM->CM2(forwarded to CM2)

Connect CM & CME via H323 trunk (full mesh)
Test call completion, calling/ed name presentation , issues

1. Default configuration.
2. H.450 extension turned on

Connect CM & CME via gatekeeper-controlled H.323 trunk
1. Default configuration.
2. H.450 extension turned on

Connect CM & CME SIP trunk(full mesh)
1. Default configuration.
2. REFER off

Connect CM & CME via ip-ip gateway (SIP)
1. Default configuration.

Posted in 2.00 Implement and Troubleshoot CUCM Endpoints, 3.00 Implement and Troubleshoot CUCME Endpoints, 4.06 H.323 RAS, 4.07 IP-IP Gateway/CUBE | Tagged: | Leave a Comment »