<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So do how do we get to where we "don't tweak"? Again, as Packet8 being the reference point, they seem to run into this problem very <i>in</i>frequently now from what I can tell...<div><br></div><div>- Darren</div><div><br><div><br><div><div>On Aug 21, 2010, at 11:16 AM, Jim Gurol wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Darren,<br><br>I had a similar issues when moving customers from one platform to another.<br>One had an SBC, one didn't. The one with SBC controller handled these NAT<br>problems without any tweaks, while the one without the SBC, sometimes needed<br>tweaking on customer CPE.<br><br>Jim Gurol<br>California Telecom<br><a href="http://www.californiatelecom.com">www.californiatelecom.com</a><br><br><br>-----Original Message-----<br>From: voiceops-bounces@voiceops.org [mailto:voiceops-bounces@voiceops.org]<br>On Behalf Of Darren Schreiber<br>Sent: Saturday, August 21, 2010 10:15 AM<br>To: VoiceOps@voiceops.org<br>Subject: [VoiceOps] "...but it works with Packet8"<br><br>Hi folks,<br><span class="Apple-tab-span" style="white-space:pre"> </span>We provide a fully redundant VoIP service to our customers where<br>they hook up two cheap Internet connections to our special little box and we<br>load-balance / failover across them. We have been running into periodic<br>issues with SIP ALG and such typical VoIP crippling technologies when<br>hooking up our equipment, requiring us to get into the client's router and<br>turn off SIP ALG (or Cisco "fix-up" features). Specifically we have issues<br>with 2Wire devices, which are very very popular. We've been assuming this is<br>standard/par-for-the-course behavior.<br><br><span class="Apple-tab-span" style="white-space:pre"> </span> We have a partner who is reselling our service and he has asked me<br>a few times why our service requires any tweaks at all. He is literally<br>replacing Packet8 phones with our service. We are utilizing the old Packet8<br>phones so it is not a model and unlikely a firmware issue. Something we are<br>doing in our way of configuring these phones is fundamentally different then<br>Packet8. The reseller feels we should not have to mess with the clients<br>router. I'm starting to think he has a valid point.<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>So, my question is, why does Packet8 work so well behind so many<br>firewalls? I don't think their Aastra firmware is all that different then<br>stock Aastra firmware. So my thoughts are:<br>- They might be using TCP signaling for SIP call setup instead of UDP?<br>- They might be ignoring the contents of SIP packets and rewrites and using<br>rather "aggressive" settings on the switch side to figure out routing based<br>solely on network headers (we use the actual SIP packets)<br>- They force rport?<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>I'm just guessing at this point, but the reseller has a valid point<br>- we should be able to compete with this directly.<br><br><span class="Apple-tab-span" style="white-space:pre"> </span>Let me know your thoughts or if you have any advice on<br>best-practices for setting up Aastras (and other phones) to behave nicely<br>across firewalls that have SIP ALG *enabled*. Sorry if this is a lame or too<br>broad a question. Any tips & tricks you've used are helpful.<br><br>Thanks much,<br><br>Darren Schreiber<br>Co-Founder - VoIP, Inc. - (415) 886-7900 www.2600hz.org - Free VoIP Software<br>www.voipkb.com - FreeSWITCH Trainings<br><br><br>_______________________________________________<br>VoiceOps mailing list<br>VoiceOps@voiceops.org<br>https://puck.nether.net/mailman/listinfo/voiceops<br><br></div></blockquote></div><br></div></div></body></html>