From igorolhovskiy@gmail.com Wed Jun 12 13:45:53 2019 From: Igor Olhovskiy To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] dialog:end event route Date: Wed, 12 Jun 2019 14:45:38 +0300 Message-ID: <3092c04c-d85d-48af-a7ae-ff8093e15f38@Spark> In-Reply-To: <622fc4a6-1edb-eebc-2a1e-66a546f03d78@gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1876730497==" --===============1876730497== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Ok. More details. I have INVITE and on fr_inv_timer expiry I'm catching timeout in failure_rout= e, but not within dialog:failed. Yes, INVITE is not completing with 200 from other side, but it's actually not= completing with any request from other side at all. It's terminated internal= ly by Kamailio. And on dialog:failure in this case I see a strange OPTIONS packet. Regards, Igor On Jun 12, 2019, 12:36 +0300, Daniel-Constantin Mierla ,= wrote: > Can you be more specific about: "I can't get which dialog failed exactly"? > What do you want to get? Which attribute/value related to dialog? > Cheers, > Daniel > On 12.06.19 10:57, Igor Olhovskiy wrote: > > Yes, sorry, `dialog:failed` exactly. > > > > Issue I found is quite strange. Schema of testing is > > > > A calling B through Kamailio. B is not answering, jut keep sending 180. > > On dialog:failed I have this code: > > > > event_route[dialog:failed] { > > xlog("L_ALERT", '[DIALOG:FAILED] "req":"$rm", "cs":"$cs", "dst":"$du", "f= rom":"$fU", "to":"$tU", "cid":"$ci", "si":"$si", "sp":"$sp", "kts":$TV(Sn)' += "\n"); > > } > > Quite simple. But when actual dialog failed on fr_inv_timer excite, in lo= gs I have > > ALERT: