No MOH for supervised transfer, but I have never offered this feature to subscriber or a feature for attendants.<div><br></div><div>I personally default to sip trunks to simplify the Callmanager dialplan. Best example is multiple CM clusters using the same unity cluster, it scales better to use SIP.</div>
<div><br></div><div>I have not been able to get the secure sip trunks working however.</div><div><br clear="all">Best Regards,<br><br>Mike Lydick<br><br><br>
<br><br><div class="gmail_quote">On Wed, Dec 1, 2010 at 11:10 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div style="font-family:Verdana;font-size:10pt;color:#000000">what I read in different spots was DTMF and compatibility with old SCCP phones which would likely need an MTP.<div class="im"><br><br><span><br><span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr></div><b>From: </b>"Jason Aarons (US)" <<a href="mailto:jason.aarons@us.didata.com" target="_blank">jason.aarons@us.didata.com</a>><br>
<b>To: </b>"Sandy Lee" <<a href="mailto:Sandy.Lee@dti.ulaval.ca" target="_blank">Sandy.Lee@dti.ulaval.ca</a>>, "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>>, "voyp list" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Sent: </b>Wednesday, December 1, 2010 11:06:54 AM<br><b>Subject: </b>RE: [cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration<div><div></div><div class="h5"><br><br><div><p class="MsoNormal">
<span style="font-size:11pt;color:rgb(31, 73, 125)">I’d like to know what the “known SIP issues” are ? In general I still stick with SCCP out of habit but I’d like to have known what was on his/her mind.</span></p><p class="MsoNormal">
<span style="font-size:11pt;color:rgb(31, 73, 125)"> </span></p><div><div style="border-right:medium none;border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10pt">From:</span></b><span style="font-size:10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Sandy Lee<br>
<b>Sent:</b> Wednesday, December 01, 2010 10:53 AM<br><b>To:</b> Lelio Fulgenzi; voyp list<br><b>Subject:</b> Re: [cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration</span></p></div></div><p class="MsoNormal">
</p><p class="MsoNormal"><span style="font-size:11pt;color:rgb(31, 73, 125)">Hi Lelio,</span></p><p class="MsoNormal"><span style="font-size:11pt;color:rgb(31, 73, 125)"> </span></p><p class="MsoNormal"><span style="font-size:11pt;color:rgb(31, 73, 125)">When I migrated from 4.1(3) to 7.1(3), I tried the SIP trunk, because I tought it would be simplier. I ran into a few issues and after discussing with my SE, he recommended the SCCP approach, as there are known issues with the SIP one. Nice to know “before”. Maybe it was because I also had another SIP trunk to my legacy PBX through TIMG. Will never know, but SCCP works fine for me.</span></p>
<div><p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:11pt;color:rgb(31, 73, 125)"> </span></p><p class="MsoNormal" style="margin-bottom:12pt"><span style="font-size:11pt;color:rgb(31, 73, 125)">Sandy.</span><span style="font-size:10pt;color:navy"></span></p>
</div><p class="MsoNormal"><span style="font-size:11pt;color:rgb(31, 73, 125)"> </span></p><div><div style="border-right:medium none;border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-left:0.5in"><b><span style="font-size:10pt">From:</span></b><span style="font-size:10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Tuesday, November 30, 2010 4:36 PM<br><b>To:</b> voyp list<br><b>Subject:</b> [cisco-voip] SIP trunk vs. SCCP ports for CUCM v7 and UCxN v7 integration</span></p></div></div><p class="MsoNormal" style="margin-left:0.5in">
</p><div><p class="MsoNormal" style="margin-right:0in;margin-bottom:12pt;margin-left:0.5in"><span style="font-size:10pt;color:black">I'm working on the migration from CUCM v4.1(3) to v7.1(x).<br><br>I think it would be much simpler if I am able to create a SIP trunk from CallManager v7 to Connection. <br>
<br>Has anyone seen any huge differences between an SCCP and a SIP integration? Do things generally continue to work the same?<br><br><br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)</span></p>
</div></div><p></p><hr size="1"><p></p>
<p><strong>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</strong></p></div></div></div></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>