<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
We are sip trunking CUCM 6.x to UConn 7. No issues that I am aware
of, though I believe the engineer who set it up chose SIP over TCP
rather than UDP for some reason. Might have had to do with failover.
If you want a contact, shoot me an e-mail or phone call and I'll get
you in touch with him.<br>
<br>
<br>
On 12/1/2010 11:10 AM, Lelio Fulgenzi wrote:
<blockquote
cite="mid:1260310073.751122.1291219835303.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0,
0, 0);">what I read in different spots was DTMF and
compatibility with old SCCP phones which would likely need an
MTP.<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 id="zwchr"><b>From: </b>"Jason Aarons (US)"
<a class="moz-txt-link-rfc2396E" href="mailto:jason.aarons@us.didata.com"><jason.aarons@us.didata.com></a><br>
<b>To: </b>"Sandy Lee" <a class="moz-txt-link-rfc2396E" href="mailto:Sandy.Lee@dti.ulaval.ca"><Sandy.Lee@dti.ulaval.ca></a>, "Lelio
Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a>, "voyp list"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><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<br>
<br>
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
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;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="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;
font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto: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;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);">Hi Lelio,</span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
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; font-family:
"Calibri","sans-serif"; color:
rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color:
rgb(31, 73, 125);">Sandy.</span><span style="font-size:
10pt; font-family:
"Calibri","sans-serif"; color:
navy;"></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt;
font-family: "Calibri","sans-serif";
color: rgb(31, 73, 125);"> </span></p>
<div>
<div style="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; font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto: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; font-family:
"Verdana","sans-serif"; 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>
<hr size="1">
<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>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Bill Simon - <a class="moz-txt-link-abbreviated" href="mailto:bills@psu.edu">bills@psu.edu</a> - (814) 865-2270
<a class="moz-txt-link-freetext" href="http://tns.its.psu.edu/">http://tns.its.psu.edu/</a></pre>
</body>
</html>