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

[Brian Meade]

EMCC may be over-complicated especially if you just are doing it for one
phone/user.

For EMCC, the PSTN access would normally be through the home cluster.

You can use the Adjunct CSS or EMCC CSS to send calls back across the SIP
trunk to the other cluster if you want though.

On Tue, May 10, 2016 at 10:30 AM, <george.hendrix at caci.com> wrote:

> 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
>
> [image: cid:image001.png at 01D15CFD.0CE91C20]
>
>
>
> _______________________________________________
> 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/20160510/7abe56e6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2584 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160510/7abe56e6/attachment.jpg>