To add my 2c, if the performance is a **really big** concern, the
solution with transaction flags as mentioned by Alex is one of the best.
In request route test for to-tag and then setflag(x). Then in
onreply_route[...] or failure_route[...] test if isflagset(x).
The other suggestions are also ve
I’ve tested it, and it worked.
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Olle
E. Johansson
Sent: Tuesday, July 12, 2016 3:56 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Detect 200 OK for ReINVITE
On 12 Jul 2016, at 15:18, Grant Bagdasari
> On 12 Jul 2016, at 15:18, Grant Bagdasarian wrote:
>
> Hi,
>
> Is it possible in Kamailio, or SIP in general, to detect if a 200 OK is for a
> ReINVITE?
>
Not from the 200 OK, but the matching INVITE you can check if there’s a to-tag
in Kamailio and SIP.
In Kamailio, if you are stateful
lashov
Sent: Tuesday, July 12, 2016 3:21 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Detect 200 OK for ReINVITE
Don't know about detect, but you could set a transaction-persistent flag or AVP
when processing the reinvite request. This will also be testable in the
Don't know about detect, but you could set a transaction-persistent flag or AVP
when processing the reinvite request. This will also be testable in the
onreply_route.
-- Alex
--
Principal, Evariste Systems LLC (www.evaristesys.com)
Sent from my Google Nexus.
Hi,
Is it possible in Kamailio, or SIP in general, to detect if a 200 OK is for a
ReINVITE?
Regards,
Grant
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/ma
