[cisco-voip] EMCC vs Cluster SIP trunk with call forwarding

Tue May 10 10:45:11 EDT 2016

Alternatively you could create a pilot on the 9.1 system to use the 10.5 voicemail rather than sending the calls across the CUCM SIP trunk. Just send it via a SIP trunk directly to CUC.

Hank

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of "george.hendrix at caci.com<mailto:george.hendrix at caci.com>" <george.hendrix at caci.com<mailto:george.hendrix at caci.com>>
Date: Tuesday, May 10, 2016 at 10:30
To: "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] EMCC vs Cluster SIP trunk with call forwarding

Guys,

  We currently have two separate CUCM clusters (9.1 and 10.5).  The 10.5 cluster would be the home cluster and the 9.1 cluster would be the remote/visiting cluster.  Which of the two would be the better option to go with?

1.      Phone is setup on 9.1 cluster and a SIP trunk between the two clusters.  Call forwarding for busy, etc. is passed over the SIP trunk to the voicemail pilot on the 10.5 cluster.

2.      Use EMCC between the clusters where the 10.5 cluster would be the home cluster.

Also, when using EMCC, the phone is actually registered with the 9.1 cluster, but the user login is with the 10.5 cluster (the extension).  Would the actual call (RTP to other phones and PSTN) access be controlled by the home cluster?  Wouldn’t the phone subnet also need to be able to reach the home cluster PSTN gateways and phones?  Basically, anything it may need RTP access to?

Thanks,

Bill Hendrix | Network/VoIP Engineer
Ph. 813.281.3109
george.hendrix at caci.com<mailto:george.hendrix at caci.com>
[cid:image001.png at 01D15CFD.0CE91C20]

itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160510/d378060b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2584 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160510/d378060b/attachment.jpg>