From ovoshlook@gmail.com Wed Oct 11 12:13:28 2017 From: Yuriy Gorlichenko To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint Date: Wed, 11 Oct 2017 13:13:19 +0300 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1381178919==" --===============1381178919== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi. Got debug 3 information and found next (here is pastebin link with dump https://pastebin.com/ALHQkM9E) After NOTIFY was created i trying to handle it by tm:local-request route and found there one thing afnter changed $fs and $ru with $du DEBUG: tm [uac.c:329]: t_run_local_req(): apply new updates without Via to sip msg as i understood it applies changes but not uses it for redirect request throught needed socket. Shoud i use msg_apply_changes() or something ike that? 2017-10-04 16:13 GMT+03:00 Yuriy Gorlichenko : > May be debug=3D3 level says more? I will try to collect it. I don't think it > is a bug. I think somethig wrong at my side, but can not find anything > > 2017-10-04 14:58 GMT+03:00 Yuriy Gorlichenko : > >> I mean i tried to change $du and print it. It was changed but notify was >> set to original ruri. I know that it worked for register requests and >> invite. I built services using it. >> >> I found this trouble only with NOTIFY >> >> On Oct 4, 2017 14:35, "Daniel-Constantin Mierla" >> wrote: >> >>> Can you print $du there and see if it set? looks like it is not routed >>> by r-uri, but dst uri. >>> >>> Cheers, >>> Daniel >>> >>> On 03.10.17 22:58, Yuriy Gorlichenko wrote: >>> >>> Found that at the tm:local-request $ru modifies but anyway - request >>> sent to old RURI. >>> INFO: NOTIFY to WS, update RURI >>> >>> -- here is making >>> $ru =3D $ru+";transport=3Dws"; >>> --- >>> >>> INFO: NOTIFY to WS, new RURI: sip:94e51c30bdf28de52519(a)93.81 >>> .99.68:54733;gr=3Durn:uuid:88b3033f-e65d-4694-ac45-2a1d1a44501 >>> c;transport=3Dws >>> >>> --- for now $ru is updated >>> >>> -- but here also same result: >>> >>> INFO: presence [notify.c:1619]: send_notify_request(): NOTIFY >>> sip:94e51c30Bdf28de52519(a)d0c20d13-e5b4-4649-821e-9ab8ec94b141 via >>> sip:94e51c30bdf28de52519(a)93.81.99.68:54733;gr=3Durn:uuid:88b30 >>> 33f-e65d-4694-ac45-2a1d1a44501c on behalf of >>> sip:8dc08f881f2105dD3d75(a)d0c20d13-e5b4-4649-821e-9ab8ec94b141 for event >>> presence : 3biad4n635ugovv7vmjv >>> >>> >>> 2017-10-03 21:31 GMT+03:00 Yuriy Gorlichenko : >>> >>>> Can not find any entry of this device at the active watchers. >>>> Suppose after module found sockets mistmatch and didnt got NOTIFY >>>> response it removes entry from active watchers... >>>> >>>> I added handling at the event route as you sugested and tried to do next >>>> >>>> Firs i tried fix $ru here but it does not work >>>> Also tried to force socket but same >>>> >>>> >>>> I see at the logs that first kamailio says about proto mistmatch and >>>> only then calling event_route[tm:local-request]... >>>> >>>> This is my log with most important variables for understanding >>>> >>>> INFO: