<html dir="ltr"><head><style id="axi-htmleditor-style" type="text/css">p { margin: 0px; }</style></head><body style="font-size: 10pt; font-family: Arial; background-image: none; background-repeat: repeat; background-attachment: fixed;">On the other hand, if you can get SIP/TLS over TCP going, do in fact do that. You'll work around a lot of NAT and ALG issues because the ALGs can't see the traffic. Most of them don't even look at 5060/tcp as well, so TCP is often enough.<br><br>TCP is good for being behind multiple layers of NAT (your cradlepoint being one, and the carrier being the other) because NAT devices treat TCP better because they know whether a session is still up or not (UDP is stateless, so you often have to keep your registration timers very low in order to make things work right consistently).<br><br>I've had good luck with G722 but if you're not sure you'll always have 4g, I've had much better luck with iLBC over 3G than any other protocol. It's not widely supported but my 3g/4g experience has mostly been with xlite on an ipad 3G or an android handset to asterisk, both of which support it. (as well as TCP, TLS and SRTP)<br><br>-Paul<br><br>On Fri, 07/25/2014 12:41 PM, Jared Geiger <jared@compuwizz.net> wrote:<br><blockquote style="border-left: 2px solid rgb(00, 00, 204); padding-left: 4px; margin-left: 16px;"><div dir="ltr">I would suggest getting a static IP from the carrier. The Carrier Grade NAT that US mobile providers use could make stationary phones lose registration without it. On LTE, you'll be fine with almost any codec that you want. I typically use ulaw and g722 over 4G LTE with no problems. If you are doing it over a 3G connection, stick with g729.<div>
<br></div><div>TCP isn't mandatory, I use UDP signaling and don't have issues on T-Mobile, Sprint, or Verizon LTE. I have not tried AT&T LTE and VoIP. I would suggest talking with the carrier you chose to see what their session timeout value is. You'll want to set your registration time lower than this to keep the Internet session up. You may be able to even set the session refresh rate in the cradlepoint itself. I have not used them though.</div>
<div><br></div><div>Good luck and report back!</div><div><br></div><div>~Jared</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 24, 2014 at 7:54 PM, Colton Conor <span dir="ltr"><<a href="mailto:colton.conor@gmail.com">colton.conor@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><pre style="white-space:pre-wrap;color:rgb(0,0,0)">What are the recommended settings to successfully implement VoIP over 3G/4G
data connection? Assume we are talking about using Polycom phones, and the
3G/4G data connection comes from a Cradlepoint router that is plugged in
with AC power and has high gain antennas. The device will be stationary, so
we will not have to worry about tower handoffs breaking the connection.
This will be for fixed wireless aiming at a cell tower. I assume packet loss will be a big concern as we have no control or QoS abilities. Plus, the speed fluctuates so much.
I have read to use G.729 codec, and TCP for signaling to bypass firewalls.
Besides that, what other settings are recommended? Changes in MTU? Changes
in voice payload ms? Is there a better codec to use? Header compression?</pre></div>
<br>_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br><a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br></blockquote></body></html>