Hey Klaus,<br><br>It was solved by commenting the fix_nated_contact() in my route section<br>that deals with NAT. In that section, if was found that NAT is required then<br>it does:<br>force_rport();<br>fix_nated_contact(); // which is not commented
<br><br>are there any side-effects to doing this?<br><br><br>Regards,<br>Lir.<br><br><br><div><span class="gmail_quote">On 7/24/07, <b class="gmail_sendername">Klaus Darilion</b> <<a href="mailto:klaus.mailinglists@pernau.at">
klaus.mailinglists@pernau.at</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I suspect you are using fix_nated_contact twice. Use it only in route[],
<br>but not in failure_route[]<br><br>klaus<br><br>liran tal wrote:<br>> Hey everyone,<br>><br>> I'm using sequential forking and on one of the scenarios there appears<br>> to be a problem.<br>><br>> When OpenSER attempts to find the first most relevant destination for the
<br>> call the SIP headers are ok. If the first destination that OpenSER attempts<br>> to contact is offline/unreachable it continues to the next one in turn in<br>> which<br>> it produces a bad Contact header which looks like this:
<br>><br>> Contact: <sip:101@192.168.0.1:5060sip:101@192.168.0.1:5060><br>><br>> As you can see it's writing the sip information twice for some reason.<br>> Has anyone seen this happen before?<br>
> Also, where should I be looking at to find the problem?<br>><br>><br>> Thanks,<br>> Lir.<br>><br>><br>><br>> ------------------------------------------------------------------------<br>><br>
> _______________________________________________<br>> Users mailing list<br>> <a href="mailto:Users@openser.org">Users@openser.org</a><br>> <a href="http://openser.org/cgi-bin/mailman/listinfo/users">http://openser.org/cgi-bin/mailman/listinfo/users
</a><br></blockquote></div><br>