[cisco-voip] SIP between CUCM clusters

[Erick Wellnitz]

I have deployed SIP between a 6.1 cluster and an 8.6 cluster for migration
purposes.

It worked perfect once I configured it correctly.

Make sure each side only points to CUCM nodes in the CM group of the
trunk's device pool...if that makes sense.  Or, I believe you could check
the 'run on all nodes' box in the trunk configuration for both/all clusters.


On Fri, Jul 12, 2013 at 8:08 AM, Russell Chaseling
<rchaseling at plannet21.ie>wrote:

> I’m also looking at deploying SIP trunks between two CUCM 8.6 clusters for
> IP calling for the simple reason that I believe that presence status can be
> shared between the two ie IP Phone BLF and CUEAC BLF (particularly CUEAC
> BLF)****
>
> ** **
>
> **1)      **First questions is have I heard this right? Will BLF work
> between 2 x CUCM clusters? ****
>
> **2)      **Has anyone deployed SIP trunks between clusters in
> production? If so is it worth the pain?****
>
> ** **
>
> Cheers****
>
> Russell****
>
> ** **
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Ryan Ratliff
> *Sent:* 05 June 2013 15:24
> *To:* Carlo Calabrese
> *Cc:* 'Cisco-voip'
> *Subject:* Re: [cisco-voip] SIP between CUCM clusters****
>
> ** **
>
> You can use SIP trunks between CUCM clusters in lieu of ICTs.   The 8.x
> SRND specifically states that QSIG-tunneled SIP trunks have feature parity
> with H.323 ICTs.****
>
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/trunks.html#wp1122456
> ****
>
> ** **
>
> The SIP trunk features available in the current release of Unified CM make
> SIP the preferred choice for new and existing trunk connections. The QSIG
> over SIP feature provides parity with H.323 intercluster trunks and can
> also be used to provide QSIG over SIP trunk connections to Cisco IOS
> gateways (and on to QSIG-based TDM PBXs). The ability to run on all
> Unified CM nodes and to handle up to 16 destination IP addresses improves
> outbound call distribution from Unified CM clusters and reduces the number
> of SIP trunks required between clusters and devices. SIP OPTIONS ping
> provides dynamic reachability detection for SIP trunk destinations, rather
> than per-call reachability determination. SIP Early Offer support for voice
> and video calls (insert MTP if needed) can reduce or eliminate the need to
> use MTPs and allows voice, video, and encrypted calls to be made over SIP
> Early Offer trunks.****
>
> ** **
>
> In general anything you can do to reduce the complexity of your call flows
> makes your life that much easier both in configuration and troubleshooting.
>  ****
>
> ** **
>
> -Ryan ****
>
> ** **
>
> On Jun 5, 2013, at 8:32 AM, Carlo Calabrese <carlo_calabrese2006 at yahoo.com>
> wrote:****
>
> ** **
>
> This is the problem I am having. Intercluster turnks are H323 based not
> sip. I have them built now, but it breaks all sorts of stuff.****
>
> multicast, not building rtp streams correctly. Dropped calls DTMF.****
>
>  ****
>
> *From:* Kenneth Hayes [mailto:kennethwhayes at gmail.com]
> *Sent:* Wednesday, June 05, 2013 3:26 AM
> *To:* Carlo Calabrese
> *Subject:* Re: [cisco-voip] SIP between CUCM clusters****
>
>  ****
>
> That would be call a Intercluster trunk. Build it like you would a regular
> SIP trunk but instead of selecting SIP trunk go to Trunk->Add New->Trunk
> type should be InterCluster Trunk Non-Gatekeeper Controlled" put in the
> required information and I'm not sure if MTP is needed or not it's been
> awhile since I've done a ICT but that should get you going. Also you will
> have to make sure you have the correct PT's and CSS on both ends and
> dial-plan modifications.****
>
>  ****
>
> On Wed, Jun 5, 2013 at 12:19 AM, Carlo Calabrese <
> carlo_calabrese2006 at yahoo.com> wrote:****
>
> Has anyone done a sip trunk between CUCM clusters? I am running 8.6 in
> production and 8.0 in the lab.****
>
> I can make it work with intercluster trunks ok. But I keep running into
> odd bugs with calls going from sip to h323 back to sip****
>
> Or can you point me in the right direction.****
>
>  ****
>
> Thanks.****
>
>  ****
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
>  ****
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ** **
>
> _______________________________________________
> 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/20130712/c8f48366/attachment.html>