>From Callmanager, there maybe few less steps. There is the benefit of not assign directory numbers for the vm ports with sip but port setup completed correctly numbers should not matter (separate partition and all that). <div>
The SIP integration is has simpler route logic and less touch points if you have to change anything.<div><br></div><div>From the Unity the SIP setup is similar to the SCCP port setup. There are a few caveats with transfer that I have not run into yet such as no MOH with supervised transfer. <br>
<div><br></div><div><br clear="all">Best Regards,<br><br>Mike Lydick<br><br><br>
<br><br><div class="gmail_quote">On Tue, Nov 30, 2010 at 4:36 PM, 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">I'm working on the migration from CUCM v4.1(3) to v7.1(x).<span><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><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></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></div></div>