Hi Klaus, thnx for your reply. Can you show me how your RR's and Route are looking like? (In INVITE and 200 reply from UA)
It might be that I have a UA problem and the formatting of my sip messages are wrong.
br hw
tor, 28,.09.2006 kl. 13.31 +0200, skrev Klaus Darilion:
I have no problems with 1.0.0:
in loose_route: if (check_route_param("nat=both")) { xlog("L_INFO","$ci NAT traversal for requester and responder\n"); .... t_relay();
In main route block I have add_rr_param(";nat=both"); ... record_route(); t_relay();
regards klaus
Helge Waastad wrote:
Hi, thats what's strange.... I have run debug=7 and the only thing I see is:
find_cmd_export_t: found <check_route_param>(1) in module rr [/usr/lib/openser/modules/]
I'm running 1.1.0
I'm doing: if (loose_route()){ check_route_param("nat=yes") }
tor, 28,.09.2006 kl. 13.06 +0300, skrev Bogdan-Andrei Iancu:
Helge,
what openser version are you using?
try to run in debug and look for: DEBUG:rr:check_route_param: params are <.......>
regards, bogdan
Helge Waastad wrote:
Hi, I'm checking for a Re-Invite (Hold)
The Invite from the UA is like this:
SIP MESSAGE 1 10.46.11.132:5060() -> xxx.xxx.xxx.xxx:5060() UDP Frame 1 28/Sep/06 10:45:38.0422 TimeFromPreviousSipFrame=0.0000 TimeFromStart=0.0000 INVITE sip:67512388@10.46.11.101:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.46.11.132;branch=z9hG4bKeb3ee7f3572b7f4b Route:sip:xxx.xxx.xxx.xxx;lr=on;ftag=9f2aeb7dd809d46d;nat=yes;did=3c4.85d80b74 Route:sip:yyy.yyy.yyy.yyy;lr=on;ftag=9f2aeb7dd809d46d;nat=yes
I do a check_route_param("nat=yes")
Should not this work?
from the doc it says check_route_param: The function checks if the URI parameters of the local Route header (coresponding to the local server)
I'm also calling the function after loose_route()
br hw
tor, 28,.09.2006 kl. 11.35 +0300, skrev Bogdan-Andrei Iancu:
Hi Helge,
doesn't matter how you added the RR hdr - via record_route(), record_route_preset() or append_hf(). When you receive a sequential request, check_route_param("") will check the params of the corresponding Route hdr. Maybe it is a reg exp problem or the Route does not contain the param you are looking for...
regards, bogdan
Helge Waastad wrote:
Hi, I was just wondering if the check_route_param("") works on record_route_preset Routes?
It never hits when my Route: are, f.ex like xxx.xxx.xxx.xxx:<port>;nat=yes
Is this true?
br hw