Voice Lab - w/H.323 gateway - calls from/to another site not being placed

nicolas.sebastian · ‎12-07-2009

Hello Everyone!!

I'm really newby on this so I hope maybe one of you experts guys could help me with this..

the topology is the following.. (also attached)

I'm running cucm7 on a vmware machine for one site (siteA) and cucm-e for another site (siteB), both sites are interconected.

On siteA I have an h.323 gateway (cisco 2600 router-running a voice capable IOS).

I've added in cucm7 the h.323 gateway, created the route group, the route list, and the route pattern pointing to siteB.

On the gateway I have the corresponding dial-peer pointing to siteA cucm7, and another poiting to SiteB cucm-e. Also SiteB cucm-e has one dial-peer pointing to h323 gw on SiteA.

My problem is that I cannot place calls from one site to another :(.. seems that the call it's being stucked in the h323 gateway.. but i'm not sure

here the configs of the h323 gw and cucm-e

H.323 GATEWAY----------------------------

!
!
gateway
!
voice service voip
h323
no call service stop
call start fast
!
exit
exit
!
int f0/0

ip address 192.168.1.151
h323-gateway voip interface
h323-gateway voip h323-id site01
exit
!
voice class codec 100
codec pref 1 g729r8
codec pref 2 g729br8
exit
voice class h323 600
h225 timeout tcp establish 10
h225 timeout setup 10
exit
voice service voip
h323
h225 timeout tcp call-idle never
exit
exit
!
!
dial-peer voice 1 voip
description to->siteA
destination-pattern 5[1-4]..
session target ipv4:192.168.1.100 --- this is the cucm7
voice-class codec 100
voice-class h323 600
exit
!
!
dial-peer voice 2 voip
description to->siteB
destination-pattern 3[234]..
session target ipv4:172.16.10.100 --- this is the cucm-e
voice-class codec 100
voice-class h323 600
exit

------------------------------------------------------------

CUCM-E configs----------

!
telephony-service
max-ephones 20
max-dn 70
keepalive 15
!system message CUCM-Express SiteB
create cnf-files
ip source-address 172.16.10.100 port 2000
!
!
ephone-dn 1
number 3210
name SiteB - PhoneA
!
ephone-dn 2
number 3211
name SiteB - PhoneB
!
exit
ephone 1
mac 000a.419e.7524
type 7960
button 1:1
exit
!
ephone 2
mac-address xxxx.xxxx.xxxx
type xxxxx
button 1:2
exit
!
!
dial-peer voice 1 voip
description to->siteA
destination-pattern 5[1234]..
session target ipv4:192.168.1.151
codec g729r8
exit
!

------------------------------------------------------

btw, no routing problems..

ANY IDEAS WOULD BE APPRECIATED

Kenneth Mohammed · ‎12-07-2009

Hello,

What exactly is happening when you make the call? Do you have h323 bound to an interface?

Example:

interface FastEthernet0/0

ip address 1.1.1.1 255.255.255.0

h323-gateway voip bind srcaddr 1.1.1.1

You should have this on both gateways.

Hope that helped, if so please rate.

nicolas.sebastian · ‎12-07-2009

Thx Kenneth,

yes, both gateways have the "h323-gateway voip bind srcaddr " command on the F0/0 interface

when I place a call from one site to another I get "bussy" tone

Kenneth Mohammed · ‎12-07-2009

In which direction are you experiencing the busy tone?

nicolas.sebastian · ‎12-07-2009

both directions - from cucm7 and also from cucm-e

Kenneth Mohammed · ‎12-07-2009

On the cucme, try changing the destination-pattern to the IP of the cucm. On the cucm, be sure that your route patterns for the cucme extensions point to the correct gateway.

Hope that helped, if so please rate.

nicolas.sebastian · ‎12-07-2009

ok, I'll try with that. if I point the dial-peer to the cucm7 instead of the h323gw should I make any additional change on the cucm config?

thx

Kenneth Mohammed · ‎12-07-2009

Is the cucme router configured cucm as an h323 gateway or intercluster trunk? I would configure the cucme router in the cucm as either a gateway or intercluster trunk. Then configure the route patterns in cucm for the cucme extensions to point there. On the cucme, configure your dialpeer for the cucm extensions to point to the IP of the cucm. Make sure that the partition of the cucm extensions are visible to the calling search space of the gateway or intercluster trunk, or calls from cucme to cucm will not work. Conversely, make sure that the route pattern for calls to cucme is in a partition that is visible to the cucm phone calling search space, or calls from cucm to cucme will not work. Hope that makes sense.

Hope that helped, if so please rate.

ragulan_dms · ‎12-07-2009

Hi ,

Here you are using CCM and CCME to talk through the Gateway. So gateway act as IP to IP gateway ( both the call legs are IP). Hence you may need to enable H323 to H323 calls, So Can you try whether the following command works,

voice service voip

allow-connection h323 to H323