<div>I just completed a Paetec dynamic sip T1. In my implentation the SIP is acutally run over their MPLS. I ended up doing a IPIPGW to translate between the provider and CUCM 6.1.3.</div>
<div>Let me know if you need configuration examples.</div>
<div> </div>
<div>Dustin<br><br></div>
<div class="gmail_quote">On Fri, Jun 19, 2009 at 12:50 PM, Matt Slaga (US) <span dir="ltr"><<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p><span style="COLOR: #1f497d">If you are willing to open up SIP (5060) and UDP range (usually 16384-32768, but I’ve seen some SIPTs require 1024-65535) through the firewall, you can terminate directly to UCM 4.1 and later (UCM 5.x and later preferred). Obviously, this is not the recommended solution. I’d love to see Cisco add this functionality to their ASA as kind of a SIP-proxy/edge to allow SIP trunks through to UCM directly but still be protected. I hear that functionality is coming for Microsoft with the next Microsoft OCS release.</span></p>
<p><span style="COLOR: #1f497d"> </span></p>
<p><span style="COLOR: #1f497d">You may require an advanced IOS gateway with DSPs to handle DTMF conversion if the SIP provider only supports inband dtmf.</span></p>
<p><span style="COLOR: #1f497d"> </span></p>
<div style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<p><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><a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a><br>
<b>Sent:</b> Friday, June 19, 2009 12:38 PM<br><b>To:</b> Cisco VoIPoE List
<div class="im"><br><b>Subject:</b> [cisco-voip] SIP Trunk to Paetec ITSP</div></span>
<p></p></p></div>
<p> </p>
<p><span style="FONT-FAMILY: 'Times New Roman','serif'; FONT-SIZE: 12pt">Has anyone had any experience (good bad or otherwise) with SIP Trunking to Paetec/USLEC? I have a new client that has ordered SIP Trunks at 3 locations through Paetec. They are looking for us to help them implement the solution in 3 weeks and I’m not seeing any CUBEs or IADs on the order and of course Paetec has assured them that they are not required…? I’m coming into this late as the “design” (or lack thereof) is already in place and I’d like to know if there is anything that I should be ready for. I don’t have a ton of experience with SIP trunks, at least not with Paetec but I know that faxing is always an issue and you’d need CUBE at a minimum just to get that working, anything else or any other comments on Paetec or SIP as a whole? TIA for any insight.</span></p>
</div></div>
<div>
<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>
</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>