OK, I managed to figure out why you get the private IP in the location
table - that's because you are saving the registration in the onreply
route, where you no longer have access to the fix_nated_contact() value.
To fix your issue, you need to do the following:
a. specify a mcontact_avp[1] in your script:
modparam("registrar", "mcontact_avp", "$avp(register)")
b. just after fix_nated_contact() on your REGISTER request, store the
changed contact in that AVP:
fix_nated_contact();
$avp(register) = $ct.fields(uri);
Doing these two changes to your script should store the real IP in the
location table.
[1]
http://www.opensips.org/html/docs/modules/2.4.x/registrar.html#idp5598160
Best regards,
On 11/01/2017 10:24 AM, Răzvan Crainea wrote:
Can you print $ct.fields(uri) instead of $ct?
Also, please post the output on pastebin.com.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 10/31/2017 03:47 PM, Răzvan Crainea wrote:
Hi, Dragomir!
Please post the logs I asked you to.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
On 10/31/2017 03:45 PM, Sumit Birla wrote:
X-Lite figures out its public IP and uses that in Via: and Contact:
headers unless you set ‘Firewall traversal method’ to ‘None’ in the
account settings.
On Oct 31, 2017, at 9:14 AM, Dragomir Haralambiev
<[email protected] <mailto:[email protected]>> wrote:
When REGISTER received from X-lite all is OK. Here part from
REGISTER message:
REGISTER sip:OpenSip_IP:Opensips_port;transport=UDP SIP/2.0
Via: SIP/2.0/UDP
219.101.241.150:64726;branch=z9hG4bK-524287-1---39ee8718032a1a5a;rport
Contact:
<sip:[email protected]:64726;transport=UDP;rinstance=d6122d9250e9d0bd>
Here "Via" contains real IP (this is Route IP).
When REGISTER received from Yealink VoIP phone I have problem. Here
part from REGISTER message:
REGISTER sip:OpenSip_IP:Opensips_port SIP/2.0
Via: SIP/2.0/UDP 192.168.2.207:5062;branch=z9hG4bK77238423
Contact: <sip:[email protected]:5062
<http://sip:[email protected]:5062/>>
Here "Via" contains not real IP (this is Yealink IP).
What I do ?
2017-10-31 14:18 GMT+02:00 Răzvan Crainea <[email protected]
<mailto:[email protected]>>:
So you did manage to fix your problem?
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com <http://www.opensips-solutions.com/>
On 10/31/2017 02:17 PM, Dragomir Haralambiev wrote:
Hi,
Thanks for your replay.
I execute fix_nated_contact() after fix_nated_register().
Here part of my script:
if (isflagset(NAT)) {
if (is_method("REGISTER")) {
fix_nated_register();
setbflag(NAT_BFLAG); # nat register
}
fix_nated_contact();
}
In this case fix_nated_contact() will be fix contact records
in location table.
2017-10-31 14:02 GMT+02:00 Răzvan Crainea <[email protected]
<mailto:[email protected]>>:
Hi, Dragomir!
fix_nated_register() does not change the contact of the
message, fix_nated_contact() does that.
Please print the Contact header as I instructed earlier
and send back the script trace. Also, please post the logs
on pastebin.com <http://pastebin.com/> or something, don't
do it directly in the email.
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
<http://www.opensips-solutions.com/>
On 10/31/2017 12:40 AM, Dragomir Haralambiev wrote:
What will I do to solve this problem?
2017-10-27 11:50 GMT+03:00 Dragomir Haralambiev
<[email protected] <mailto:[email protected]>>:
Oct 27 11:47:32 web /usr/local/sbin/opensips[30490]:
57995010: REGISTER before fix_nated_register
<sip:[email protected]:5060
<http://192.168.2.196:5060/>>[1]
Oct 27 11:47:32 web /usr/local/sbin/opensips[30490]:
57995010: REGISTER after fix_nated_register
<sip:[email protected]:5060
<http://192.168.2.196:5060/>>[1]
2017-10-27 10:41 GMT+03:00 Răzvan Crainea
<[email protected] <mailto:[email protected]>>:
Hi, Dragomir!
Can you also print the Contact header ($ct[1]).
[1]
http://www.opensips.org/Documentation/Script-CoreVar-2-4#toc26
<http://www.opensips.org/Documentation/Script-CoreVar-2-4#toc26>
Best regards,
Răzvan Crainea
OpenSIPS Developer
www.opensips-solutions.com
<http://www.opensips-solutions.com/>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
