15 Nov
2007
15 Nov
'07
7:57 p.m.
Ricardo Martinez wrote:
Hi Andres..
Thanks for your reply.. that's the weird part.. my configuration is based on the
"Getting Started document"... so .. in my onreply_route i have :
if (client_nat_test("1")) {
Maybe this nat_test is not evaluating to true. Are you sure you know
what client_nat_test("1") checks for? Put some LOG message in there to
see if it is hitting the statemenet as true. Try with a
client_nat_test("19") and see what happens. (actually in our version it
is nat_uac_test("19")).
fix_nated_contact();
};
i don't understand why is not working...
Ricardo.-
-----Mensaje original-----
De: Andres [mailto:andres@telesip.net]
Enviado el: jueves, 15 de noviembre de 2007 12:07
Para: Ricardo Martinez
CC: serusers(a)lists.iptel.org
Asunto: Re: [Serusers] ACK Problem : Not routed to NAT'd port
--
Andres
Technical Support
http://www.telesip.net
I don't understand why the the ACK message is
routed to port 5060 and
not to
the port 62447 like the INVITE or the final OK. Is this maybe a
configuration problem?.
Its probably a config issue. When the call is answered, your SER has to
rewrite the Contact with the right port
U 100.100.100.99:5060 -> 100.100.100.50:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP
100.100.100.50;rport=5060;branch=z9hG4bK404c94810000005a43b2b7ee000053dc0000
010f.
Contact: <sip:551100000684@100.100.100.231;user=phone>.
If not, then the ACK is not going to go to the right port (62447).
This will normally be accomplished by your onreply_route.
For example:
onreply_route[1] {
fix_nated_contact();
};
My ser.cfg is based on the onsip.org configuration
documents plus some
modifications by me.
Can someone help me here
Thanks in advance
Ricardo Martinez.-
------------------------------------------------------------------------
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers