[cisco-voip] SIP trunk between CCM 4.1.3 and CUCM 6.1.1

[Ryan Ratliff]

I've done it here in the lab so it's certainly possible.  You'd have to look
at traces to see why the calls are failing.
 

-Ryan 

 

  _____  

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of c3voip
Sent: Wednesday, October 08, 2008 1:06 PM
To: 'Voice Noob'
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] SIP trunk between CCM 4.1.3 and CUCM 6.1.1



An ICT is fine, but I currently have both CCM 4.1.3 and CUCM 6.1.1 in my lab
so I wanted to explore all options of setting up trunks between the 2.  I'm
just curious as to why I can get a SIP trunk to work between
Asterisk/Trixbox and CCM 4.1.3, but I can't get one to work between CCM
4.1.3 and CUCM 6.1.1.  Seems like the same vendor would account for that and
it would be straightforward.

 

-C

 

From: Voice Noob [mailto:voicenoob at gmail.com] 
Sent: Wednesday, October 08, 2008 12:05 PM
To: c3voip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] SIP trunk between CCM 4.1.3 and CUCM 6.1.1

 

Why wouldn't you just use an ICT? I often wonder why people always want to
move everything to SIP when it is simply just not ready for enterprise
deployments yet.

On Wed, Oct 8, 2008 at 10:08 AM, c3voip <c3voip at nc.rr.com> wrote:

Is there some kind of trick to setting up a SIP trunk between CCM 4.1.3 and
CUCM 6.1.1 servers?

 

I think I have everything setup properly, but I can't send calls from phones
on 4.1.3 to phones on 6.1.1, but calls go the other way ok.

 

This is not a partition/CSS issue, since everything is <None>.  I can setup
an ICT and it works fine, but the SIP trunk is not working in the one
direction.

 

Thanks,

-C

 

 


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081008/31c50e9d/attachment.html>