<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>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. <br>
</p>
<p><br>
</p>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> bmeade90@gmail.com <bmeade90@gmail.com> on behalf of Brian Meade <bmeade90@vt.edu><br>
<b>Sent:</b> Tuesday, April 21, 2015 1:48 PM<br>
<b>To:</b> Leslie Meade<br>
<b>Cc:</b> cisco-voip (cisco-voip@puck.nether.net)<br>
<b>Subject:</b> Re: [cisco-voip] EMCC with SME</font>
<div> </div>
</div>
<div>
<div dir="ltr">The EMCC config file transfers is all done via TFTP.
<div><br>
</div>
<div>The EMCC SIP Trunk only comes into play when trying to route calls back to the visiting cluster.</div>
<div><br>
</div>
<div>Here's a diagram of how the EMCC SIP Trunk is used- <a href="http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fsgd-802-cm/fsemcc.html#wp1457098">http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_0_2/ccmfeat/fsgd-802-cm/fsemcc.html#wp1457098</a></div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Apr 21, 2015 at 4:34 PM, Leslie Meade <span dir="ltr">
<<a href="mailto:Leslie.Meade@lvs1.com" target="_blank">Leslie.Meade@lvs1.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr" style="font-size:12pt; color:#000000; background-color:#ffffff; font-family:Calibri,Arial,Helvetica,sans-serif">
<p></p>
<p style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:16px">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.<br>
</p>
<p style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:16px"><br>
</p>
<p style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:16px"><br>
</p>
<div><br>
<br>
</div>
<p><br>
</p>
</div>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>