<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Several users of our product have reported no audio when using our VoIP mobile app on cellular networks. Our server product and our mobile app rely on the TCP SIP socket’s source address being the same as the audio’s source address. When
the addresses don’t match, the server has no way to know the two addresses are a single device.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have a packet capture from one user’s server that shows a single mobile device communicating from two different IP addresses: one for the TCP SIP connection (166.181.252.181), and a second one for the UDP RTP audio (166.181.255.39).
In this capture, our server sends audio to 166.181.252.181 and discards the inbound audio from 166.181.255.39. The port numbers in the audio packets from the 39 address match the port numbers negotiated over the TCP connection with the 181 address, which
is why I believe them to be the same device.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We retested today with the same customer device but connecting to a different server. In today’s test, the capture shows that the TCP SIP connection arrived from 166.181.251.203 and the UDP RTP arrived from 166.181.255.32.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">All of these addresses are in a block assigned to “Wireless Data Service Providers' Corporation (SPCo)”. The user reports their carrier as US Cellular, which is a voting member of SPCo.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does anyone have a technical contact at US Cellular we can ask about this? Has anyone observed this multiple-address NAT being employed by other service providers?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you! <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Scott Ventura<o:p></o:p></p>
<p class="MsoNormal">Senior Software Engineer<o:p></o:p></p>
<p class="MsoNormal">Allworx<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all
copies of the original message and any attachments.
</body>
</html>