Hi Alan,
Yes, the CANCEL is received before sending the INVITE to the UAS.
Technically speaking (as coding), we can do both - handle the canceling
process in the proxy (200 OK to CANCEL and 487 to INVITE, without
sending anything further to UAS) , or to delay the CANCEL until the
INVITE is
It is fine to cancel in the proxy alone. There are at least two relevant bits
in 3261; Section 9.2 says “a stateful proxy might respond to it and generate
some CANCEL requests of its own” … But you don’t need to send any CANCELs since
you haven’t sent anything out. And Section 16.10:
While a
Bogdan-Andrei Iancu writes:
> Yes, the CANCEL is received before sending the INVITE to the UAS.
>
> Technically speaking (as coding), we can do both - handle the canceling
> process in the proxy (200 OK to CANCEL and 487 to INVITE, without
> sending anything further to UAS)
Hello,
What should be the correct and most efficient way for a proxy to handle
an incoming CANCEL for a INVITE still under processing. The detailed
scenario is :
* INVITE is received, the transaction is created, 100 Trying is sent back
* the routing logic is invoked (this may take even 1
Thank you Alan, Thank you Dale,
It seems we have a winning option here.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 10.10.2016 17:09, Dale R. Worley wrote:
Bogdan-Andrei Iancu writes:
Yes, the CANCEL is received