8 Nov
2005
8 Nov
'05
2:11 p.m.
Hi,
NatHelper documentation says fix_nated_contact is rewriting contact
header with request source address:port but it seems the function
doesn't work properly with my SER config...
Indeed, when you analyze a SIP Request Packet you have the following :
Message Header :
Contact : <sip:352621@192.170.10.32:5060> #192.170.10.32:5060 is
the private IP/Port
and if this function was working properly, I understand you should get
the following :
Message Header :
Contact: <sip:352621@80.114.25.8:2014> #80.114.25.8:2014 is the
public IP/Port
But the SIP packets that are getting out from SER Proxy to SIP Registrar
Server have not their contact header field modified with public IP/Port...
So, is the function not working ? or something else ?
Thanks,
9 Nov
9 Nov
12:31 a.m.
New subject: [Users] Help with NATHelper module and fix_nated_contact() function
Hi!
Make sure your function is really called. Put log statements before and
after the fix_nated_contact function and watch syslog (/var/log/syslog )
for the log statements, e.g.:
log("before fix natted contact\n");
fix_nated_contact();
log("after fix natted contact\n");
you could also use xlog and pseudo variables to log the contact before
and afterwards the changes.
regards
klaus
Anthony Chapellier wrote:
Hi,
NatHelper documentation says fix_nated_contact is rewriting contact
header with request source address:port but it seems the function
doesn't work properly with my SER config...
Indeed, when you analyze a SIP Request Packet you have the following :
Message Header :
Contact : <sip:352621@192.170.10.32:5060> #192.170.10.32:5060 is
the private IP/Port
and if this function was working properly, I understand you should get
the following :
Message Header :
Contact: <sip:352621@80.114.25.8:2014> #80.114.25.8:2014 is the
public IP/Port
But the SIP packets that are getting out from SER Proxy to SIP Registrar
Server have not their contact header field modified with public IP/Port...
So, is the function not working ? or something else ?
Thanks,
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
11 Nov
11 Nov
1:10 p.m.
New subject: [Users] Help with NATHelper module and fix_nated_contact() function
Hello,
On 11/09/05 00:31, Klaus Darilion wrote:
Hi!
Make sure your function is really called. Put log statements before
and after the fix_nated_contact function and watch syslog
(/var/log/syslog ) for the log statements, e.g.:
log("before fix natted contact\n");
fix_nated_contact();
log("after fix natted contact\n");
you could also use xlog and pseudo variables to log the contact before
and afterwards the changes.
the change will not be reflected in the pseudo-variable
corresponding to
contact header. It is kept inside openser as a diff to the old content
of the message.
Cheers,
Daniel
regards
klaus
Anthony Chapellier wrote:
Hi,
NatHelper documentation says fix_nated_contact is rewriting contact
header with request source address:port but it seems the function
doesn't work properly with my SER config...
Indeed, when you analyze a SIP Request Packet you have the following :
Message Header :
Contact : <sip:352621@192.170.10.32:5060> #192.170.10.32:5060
is the private IP/Port
and if this function was working properly, I understand you should
get the following :
Message Header :
Contact: <sip:352621@80.114.25.8:2014> #80.114.25.8:2014 is the
public IP/Port
But the SIP packets that are getting out from SER Proxy to SIP
Registrar Server have not their contact header field modified with
public IP/Port...
So, is the function not working ? or something else ?
Thanks,
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
6954
days inactive
6957
days old
2 comments
3 participants
participants (3)
-
Anthony Chapellier -
Daniel-Constantin Mierla -
Klaus Darilion