Real Easy One: Connecting CUCME to CUCM

Answered Question
May 4th, 2009

This is a dead easy one.

How do I accomplish the following:

1) CUCME (SCCP) to CUCM (SCCP) not using a gatekeeper

2) CUCME (SIP) to CUCM H.323 again not using a gatekeeper

(no transcoding required)

(all internetworking gear except CUCME is non Cisco)

I am close to falling asleep thinking about how to do this. In both cases using a non-GK controlled trunk on the CUCM I can get calls from CUCME -> CUCM but no calls in the opposite direction. I am sure it is easy and I apologize in advance....

Thank you for any help.

I have this problem too.
0 votes
Correct Answer by Adrian Saavedra about 7 years 7 months ago

Hi Dale,

Just to add a comment, it's always important to keep in mind some topics discussed in the SRND of CUCME, such as:

Cisco Unified CallManager Express Call Transfer and Forward:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/clproc.html

Connecting Multiple Cisco Unified CallManager Express Systems with VoIP:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/multcme.html

Integrating Cisco Unified CallManager Express with Cisco Unified Call Manager:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/intcmecm.html

Hope these references helps you sometime.

Best regards,

- Adrián.

Correct Answer by Jaime Valencia about 7 years 7 months ago

in fact it is really easy

on CUCME configure the voip dial-peers pointing to the CUCM with the appropriate destination patterns

make sure you bind all your h323 signaling to an interface

on CUCM configure an H323 gateway using the CUCME signaling address, for calls to CUCME just configure the route pattern and use the GW in a route list or directly under the route pattern config

An h225 trunk also works but most commonly configuring CUCME as H323 GW is more than enough

HTH

java

if this helps, please rate

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Jaime Valencia Mon, 05/04/2009 - 18:32

in fact it is really easy

on CUCME configure the voip dial-peers pointing to the CUCM with the appropriate destination patterns

make sure you bind all your h323 signaling to an interface

on CUCM configure an H323 gateway using the CUCME signaling address, for calls to CUCME just configure the route pattern and use the GW in a route list or directly under the route pattern config

An h225 trunk also works but most commonly configuring CUCME as H323 GW is more than enough

HTH

java

if this helps, please rate

Correct Answer
Adrian Saavedra Mon, 05/04/2009 - 18:51

Hi Dale,

Just to add a comment, it's always important to keep in mind some topics discussed in the SRND of CUCME, such as:

Cisco Unified CallManager Express Call Transfer and Forward:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/clproc.html

Connecting Multiple Cisco Unified CallManager Express Systems with VoIP:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/multcme.html

Integrating Cisco Unified CallManager Express with Cisco Unified Call Manager:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/intcmecm.html

Hope these references helps you sometime.

Best regards,

- Adrián.

d.chulhan Tue, 05/05/2009 - 04:32

Thank you java & Adrian! This is definitely the direction. Ratings on the way.

Actions

This Discussion