I'm sorry...I even put in my message "here is the block of code" and then forgot to paste it in. The code looks like this:<br><br> if(proto==TCP and t_check_status("200") and !$(ct{uri.param,transport}) ) {<br>
xlog ("Need to add transport to this one");<br> #subst("/^Contact\:(.*)/Contact:\1;transport=tcp/");<br> };<br><br>Basically the problem is if the response 200 is received TCP, but there is no transport, then add it.<br>
<br>Please let me know if this is enough information.<br><br>Thanks.<br clear="all"><br>-dg<br>
<br><br><div class="gmail_quote">On Wed, Aug 18, 2010 at 7:46 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Daniel,<br>
<br>
For sure you an overlapping of changes (multiple changes over the same<br>
part of the message). What is the scripting you use to add the<br>
transport=tcp stuff ?<br>
<br>
Regards,<br>
Bogdan<br>
<div class="im"><br>
Daniel Goepp wrote:<br>
> First, let me state that I don't believe this is a problem with<br>
> OpenSIPS, but rather me just trying to fix a user agent that is not<br>
> doing the right thing. The problem is that the 200 OK that we get<br>
> back from the phone is not putting the transport in explicitly (ugh).<br>
> So OpenSIPS passes this along time, and we get an ACK back, but the<br>
> ACK is then not explicit either, and OpenSIPS defaults to sending it<br>
> UDP (but it should be TCP). The problem is that if we try to fix this<br>
> by adding it on the reply, we break things pretty bad. I believe this<br>
> is because fix_nated_contact is not playing nice with my manual fix.<br>
><br>
> If my reply just has fix_nated_contact, it's all nice relaying fine with:<br>
><br>
> Contact: "2060" <sip:2060@<my_public_ip>:48278>.<br>
><br>
> However if I add this block of code right after or before fixing nated<br>
> contact, I get:<br>
><br>
> Contact: "2060" <<a href="http://sip:2060@10.0.1.9:5060" target="_blank">sip:2060@10.0.1.9:5060</a><br>
</div>> <<a href="http://sip:2060@10.0.1.9:5060" target="_blank">http://sip:2060@10.0.1.9:5060</a>>>.;transport=tcpsip:2060@<my_public_ip>:39803<br>
<div class="im">><br>
> OUCH, that ain't never gonna work!<br>
><br>
> Thoughts on how I can work around a mis-behavin' phone?<br>
><br>
> Thanks<br>
><br>
> -dg<br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Bootcamp<br>
20 - 24 September 2010, Frankfurt, Germany<br>
<a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>