[cisco-voip] EMCC with SME

[Brian Meade]

You'll want just a single dedicated EMCC PSTN access SIP Trunk here.  It
will use that to communicate with the visiting cluster for PSTN calls.

On Tue, Apr 21, 2015 at 5:00 PM, Leslie Meade <Leslie.Meade at lvs1.com> wrote:

>  ​Ok, by looking at the diagram again. Instead of creating new SIP trunks
> to point to the other cluster. I can reuse my existing SME Trunks for the
> task.
>
>
>  ------------------------------
> *From:* bmeade90 at gmail.com <bmeade90 at gmail.com> on behalf of Brian Meade <
> bmeade90 at vt.edu>
> *Sent:* Tuesday, April 21, 2015 1:48 PM
> *To:* Leslie Meade
> *Cc:* cisco-voip (cisco-voip at puck.nether.net)
> *Subject:* Re: [cisco-voip] EMCC with SME
>
>  The EMCC config file transfers is all done via TFTP.
>
>  The EMCC SIP Trunk only comes into play when trying to route calls back
> to the visiting cluster.
>
>  Here's a diagram of how the EMCC SIP Trunk is used-
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fsgd-802-cm/fsemcc.html#wp1457098
>
>
> On Tue, Apr 21, 2015 at 4:34 PM, Leslie Meade <Leslie.Meade at lvs1.com>
> wrote:
>
>>  ​So I know that in order to make this work you need SIP trunks between
>> clusters.  And what i understand the SIP trunks only carry the
>> communication for the EMCC config. Question is what if there is a SME
>> between both clusters ? If the SIP trunks only carry EMCC information and
>> nothing to do with call routing i believe it is ok to place sip trunks that
>> terminate on each others Publisher and bypass the SME.
>>
>>
>>
>>
>> ​
>>
>>
>>
>> _______________________________________________
>> 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/20150421/9823969b/attachment.html>