[OpenSIPS-Users] loose_route: loop on ACK requests
Noel R. Morais
noelrocha at gmail.com
Wed Mar 18 00:33:31 CET 2009
No, it doesn't appear :(
for some reason the code
modules/rr/loose.c linha 905:
if (is_myself(&_m->parsed_uri.host, _m->parsed_uri.port_no))
returns true and it acts as a strict router but it is a loose route :(
I'm crazy here, tree days trying to find a solution without success .....
Thanks
On Mon, Mar 16, 2009 at 10:29 PM, Robert Dyck <rob.dyck at telus.net> wrote:
> Does "rewriting Request-URI with blahblah" appear anywhere in your debug?
> This would be the output from the rewrite_uri function in dset.c file.
>
> On Monday 16 March 2009, you wrote:
>> Robert, you are right.
>>
>> I'm using loose routing all the way but for some reason the
>> loose_route function for the ACK is acting as a strict router.
>>
>> follow bellow the debug code regarding this ACK. 192.168.191.188 is
>> the opensips ip address:
>>
>>
>> Mar 16 17:18:00 openser opensips[9057]: ***BEFORE loose_route: ACK
>> ruri:[sip:6715551131062860 at 192.168.193.20:5060]
>> from:[sip:551135880091 at 192.168.193.20]
>> to:[sip:6715551131062860 at 192.168.191.188;user=phone]
>> Mar 16 17:18:00 openser opensips[9057]: DBG:core:parse_headers: flags=200
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 36), called
>> from parser/parse_rr.c: do_parse_rr_body(63)
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 36),
>> returns address 0x81f4a14 frag. 0x81f49fc (size=44) on 1 -th hit
>> Mar 16 17:18:00 openser opensips[9057]: DBG:rr:is_preloaded: is_preloaded:
>> No Mar 16 17:18:00 openser opensips[9057]: DBG:core:grep_sock_info:
>> checking if host==us: 14==15 && [192.168.193.20] == [192.168.191.188]
>> Mar 16 17:18:00 openser opensips[9057]: DBG:core:grep_sock_info:
>> checking if port 5060 matches port 5060
>> Mar 16 17:18:00 openser opensips[9057]: DBG:rr:after_strict: Next hop:
>> 'sip:192.168.191.188;lr=on;ftag=1c1682753440;did=043.0c936ea3' is
>> loose router
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 60), called
>> from parser/msg_parser.c: set_dst_uri(738)
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 60),
>> returns address 0x81f3b48 frag. 0x81f3b30 (size=68) on 1 -th hit
>> Mar 16 17:18:00 openser opensips[9057]: DBG:core:parse_headers:
>> flags=ffffffffffffffff
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 60), called
>> from parser/msg_parser.c: set_ruri(705)
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 60),
>> returns address 0x81f4ba0 frag. 0x81f4b88 (size=72) on 1 -th hit
>> Mar 16 17:18:00 openser opensips[9057]: DBG:rr:after_strict: The last
>> route URI: 'sip:192.168.191.188;lr=on;ftag=1c1682753440;did=043.0c936ea3'
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 32), called
>> from data_lump.c: del_lump(298)
>> Mar 16 17:18:00 openser opensips[9057]: params (0x81a7a00, 32),
>> returns address 0x81f3ae8 frag. 0x81f3ad0 (size=48) on 1 -th hit
>> Mar 16 17:18:00 openser opensips[9057]: DBG:rr:run_rr_callbacks:
>> callback id 1 entered with <>
>> Mar 16 17:18:00 openser opensips[9057]: DBG:core:parse_headers: flags=48
>> Mar 16 17:18:00 openser opensips[9057]: DBG:rr:run_rr_callbacks:
>> callback id 0 entered with <>
>> Mar 16 17:18:00 openser opensips[9057]: DBG:uac:restore_from: getting
>> 'vsf' Route param
>> Mar 16 17:18:00 openser opensips[9057]: DBG:uac:restore_from: route
>> param 'vsf' not found
>> Mar 16 17:18:00 openser opensips[9057]: ***AFTER loose_route=TRUE: ACK
>> ruri:[sip:192.168.191.188;lr=on;ftag=1c1682753440;did=043.0c936ea3]
>> from:[sip:551135880091 at 192.168.193.20]
>> to:[sip:6715551131062860 at 192.168.191.188;user=phone]
>>
>> On Fri, Mar 13, 2009 at 2:27 AM, Robert Dyck <rob.dyck at telus.net> wrote:
>> > Very peculiar. The RURI was rewritten with the URI in the Route header.
>> > Does your script rewrite it? This usually only happens when the route set
>> > shows a next hop and the next hop is a strict router. If loose routing is
>> > in effect all the way, the RURI does not change.
>
>
>
More information about the Users
mailing list