I've been using the $dd variable to apply some workarounds for NAT hairpinning problems (by forcing mediaproxy), however i just realized that 1. When the received column in the Location database isn't populated (ie the client is using stun and a lookup() is executed for that username, the $dd variable is null even though the ruri contains a vaild ip:port
This makes the $dd variable not ideal to be used to check the destination IP address of locally registered clients
Is it supposed to work this way?
As an intern solution, i was able to execute "fix_nated_register()" for ALL registrations (previously i was only executing it for nat clients)
tavis
Tavis P wrote:
I've been using the $dd variable to apply some workarounds for NAT hairpinning problems (by forcing mediaproxy), however i just realized that
- When the received column in the Location database isn't populated
(ie the client is using stun and a lookup() is executed for that username, the $dd variable is null even though the ruri contains a vaild ip:port
the destination URI will only be used if it is different than the request URI. Thus you can check if $dd is empty/null and use $rd
regards Klaus
This makes the $dd variable not ideal to be used to check the destination IP address of locally registered clients
Is it supposed to work this way?
As an intern solution, i was able to execute "fix_nated_register()" for ALL registrations (previously i was only executing it for nat clients)
tavis
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Klaus Darilion wrote:
Tavis P wrote:
I've been using the $dd variable to apply some workarounds for NAT hairpinning problems (by forcing mediaproxy), however i just realized that
- When the received column in the Location database isn't populated
(ie the client is using stun and a lookup() is executed for that username, the $dd variable is null even though the ruri contains a vaild ip:port
the destination URI will only be used if it is different than the request URI. Thus you can check if $dd is empty/null and use $rd
regards Klaus
Ahh, thank you
How would you recommend to check for null values? The only method i've found so far is doing a regex match
This makes the $dd variable not ideal to be used to check the destination IP address of locally registered clients
Is it supposed to work this way?
As an intern solution, i was able to execute "fix_nated_register()" for ALL registrations (previously i was only executing it for nat clients)
tavis
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
If not wrong, if you push a pseudo-variable that's empty to an AVP, you get the "NULL" string - this might be useful to you - use avp_print() to see if so.
regards, bogdan
Tavis P wrote:
Klaus Darilion wrote:
Tavis P wrote:
I've been using the $dd variable to apply some workarounds for NAT hairpinning problems (by forcing mediaproxy), however i just realized that
- When the received column in the Location database isn't populated
(ie the client is using stun and a lookup() is executed for that username, the $dd variable is null even though the ruri contains a vaild ip:port
the destination URI will only be used if it is different than the request URI. Thus you can check if $dd is empty/null and use $rd
regards Klaus
Ahh, thank you
How would you recommend to check for null values? The only method i've found so far is doing a regex match
This makes the $dd variable not ideal to be used to check the destination IP address of locally registered clients
Is it supposed to work this way?
As an intern solution, i was able to execute "fix_nated_register()" for ALL registrations (previously i was only executing it for nat clients)
tavis
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Klaus Darilion -
Tavis P