<div dir="ltr">Alright notes taken so far is to obtain a static IP with the wireless carrier to avoid their Carrier Grade NAT. <span style="color:rgb(84,84,84);font-family:arial,sans-serif;line-height:18.200000762939453px">We already paid $500 to get static IPs from Verizon, so we are good to go there.</span><div>
<br></div><div>In addition use TCP for SIP. I believe we already use TCP for the SIP signaling as we use the <span style="color:rgb(84,84,84);font-family:arial,sans-serif;line-height:18.200000762939453px">TCPpreferred setting on the Polycom VVX line, and our service provider supports TCP with their Acme Packet / Broadsoft setup. Just the signaling is TCP right? The RTP media is still UPD I assume?</span></div>
<div><span style="color:rgb(84,84,84);font-family:arial,sans-serif;line-height:18.200000762939453px"><br></span></div><div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px">Of course we would like to use a wideband codec, but I have heard narrowband codecs work better due to less data traffic (which as you know data is expensive on wireless). Looks like G.729 and iLBC are the most supported narrowband codecs today. What are the thoughts about both of these codecs? Which is better? I assume the session border controller or softswitch would transcode the call to G.711 to send it out over the PSTN, so do either of these codecs transcode or sound better when converted to G.711? Are there any other codecs besides these two?</span></font><br>
</div><div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px"><br></span></font></div><div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px">I assume we are going to be dealing with alot of packet loss whether its going to 3G or 4G. We are also going to be dealing with high latency on 3G. Since we have no control over both of these issues, what other recommendations do you have? I have heard changing the ptime can help, and certain codes have different ptime settings. I have also read about trying to keep the MTU size down, and using SIP header compression helps. I don't know much about this. </span></font></div>
<div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px"><br></span></font></div><div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px">Any more advice would be appreciated. </span></font></div>
<div><font color="#545454" face="arial, sans-serif"><span style="line-height:18.200000762939453px"><br></span></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 2:50 PM, Alex Balashov <span dir="ltr"><<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1 on using TCP for traversing many layers of NAT of varying quality + getting around the infantile thumb-sucking that passes for ALG-"assisted" NAT traversal.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Alex Balashov - Principal<br>
Evariste Systems LLC<br>
Tel: <a href="tel:%2B1-678-954-0670" value="+16789540670" target="_blank">+1-678-954-0670</a><br>
Web: <a href="http://www.evaristesys.com/" target="_blank">http://www.evaristesys.com/</a>, <a href="http://www.alexbalashov.com/" target="_blank">http://www.alexbalashov.com/</a><br>
<br>
Please be kind to the English language:<br>
<br>
<a href="http://www.entrepreneur.com/article/232906" target="_blank">http://www.entrepreneur.com/<u></u>article/232906</a></font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<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/<u></u>mailman/listinfo/voiceops</a><br>
</div></div></blockquote></div><br></div>