<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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@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=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I have been working with Opensips for a few weeks now. I’ve got everything going pretty good except for the fact that connection through a trunk is dropping after 32 seconds. Twilio claimed that this was due to the ack r-uri not containing the address in the 200 ok contact header. I examined it and found that to be the case. The Contact header in the 200 ok is <a href="sip:172.18.46.46:5060">sip:172.18.46.46:5060</a>. After it comes into contact with opensips it changes to the ip address of the trunk. So whenever it’s sending the ack back it’s not traversing on the other end. I’ve run into a brick wall here and I really would be thrilled if someone could help me to get some insight on this issue. </p><p class=MsoNormal><o:p> </o:p></p></div></body></html>