<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18783"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=828294901-20062009><FONT color=#0000ff
size=2 face=Arial>We have many customers running 4.x releases of CM (in addition
to 5.x, 6.x and some recent 7.x), As long as you are running a version of CM
that supports SIP, we are more than willing to work with you on any
implementation hurdles you may run across. My personal worry if it were me would
be that if support is needed from Cisco for anything in the 4.x train, it is
going to be pretty hard to come buy.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=828294901-20062009></SPAN><FONT color=#0000ff size=2
face=Arial><SPAN class=828294901-20062009>Feel free to contact me at any time
with any questions you may have. I may not be able to give you specific details
on other customer implementations, but we are here to help in any way we
can.</SPAN></FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT
size=2></FONT></FONT></FONT> </DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2>T<SPAN
class=828294901-20062009>hanks,</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=828294901-20062009></SPAN><SPAN
class=828294901-20062009></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>J<SPAN class=828294901-20062009>im
Pender</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=828294901-20062009></SPAN><SPAN
class=828294901-20062009></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>T<SPAN class=828294901-20062009>eam Lead Data Network
Engineering</SPAN></FONT></FONT></FONT></DIV>
<DIV><SPAN class=828294901-20062009></SPAN><SPAN
class=828294901-20062009></SPAN><FONT face=Arial><FONT color=#0000ff><FONT
size=2>P<SPAN class=828294901-20062009>AETEC
Communications</SPAN></FONT></FONT></FONT><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Scott
Voll<BR><B>Sent:</B> Friday, June 19, 2009 6:03 PM<BR><B>To:</B>
tednugent73@gmail.com<BR><B>Cc:</B> Cisco VoIPoE List<BR><B>Subject:</B> Re:
[cisco-voip] SIP Trunk to Paetec ITSP<BR></FONT><BR></DIV>
<DIV></DIV>specially with pre cm 5.x I would defently make them buy a CUBE. But
that's just my two cents.
<DIV><BR></DIV>
<DIV>Scott<BR><BR>
<DIV class=gmail_quote>On Fri, Jun 19, 2009 at 10:57 AM, <SPAN dir=ltr><<A
href="mailto:tednugent73@gmail.com">tednugent73@gmail.com</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>Uggh.. This keeps getting better the more I dig into it...
they're running CM4.2 which I know requires a hardware based MTP to pull DTMF
out of band, however other than that and the potential port issues on the
firewall what are the implications of running an ITSP trunk on 4.x? I’ve
always thought of SIP trunking (SIP anything) pre-5.x as a novelty at best…
Are there any features/functionality that might be missing and/or should I
pressure them to upgrade to CM6.x+ beforehand (not even sure if that’s an
option at this stage in the game)? I’m loading up the SRND as we speak but any
real world feedback is greatly welcome. Thanks Matt and Paul for your
responses!<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></BODY></HTML>