[OpenSIPS-Users] Fixing the Contact Header for NAT
Juan Backson
juanbackson at gmail.com
Thu Nov 27 13:30:42 CET 2008
Hi,
Sorry for double posting for the same problem. This second post was meant
to nail down on the exact issue for the first post. I am very sorry for any
inconvenience caused.
Inaki,
In the 200OK received by the nated client, the Contact is :Contact: <
sip:1000 at 192.168.1.100:33756>
Opensips did not add the Record-Route even though I did specify
fix_nated_contact in on_reply_route. Do you have any idea why that is the
case?
Thanks alot for all your help.
JB
On Wed, Nov 26, 2008 at 7:47 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:
> El Miércoles, 26 de Noviembre de 2008, Juan Backson escribió:
> > I am having a problem with using B2BUA -> Opensips -> xLite behind NAT.
> > When the B2BUA sends back a 200OK, it is received by the SIP client
> behind
> > NAT, but the SIP client does not response properly with ACK when the
> xLite
> > is not in the same local LAN as the Opensips. If xLite is connected
> within
> > the local LAN of Opensips, then xLite can response properly with ACK. I
> > think this is due to Contact header not properly configured, but I did
> use
> > fix_nated_contact() inside the onreply_route[1].
>
>
> Well, how is the Contact the callee receives in the 200 OK?
> Does OpenSIPS add Record-Route?
>
> --
> Iñaki Baz Castillo
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20081127/5ab9614b/attachment.htm
More information about the Users
mailing list