On 4/29/13 10:48 AM, Aman wrote:
> Nope Paul, no response from UAS to INVITE.
>
> This seems to be UAS is broken. Thanks a lot for your help.
So in this case your UAC should eventually time out the INVITE transaction.
At this point you need to ask the supplier of the UAS (or maybe the
middle box
On 4/28/13 4:47 AM, Aman wrote:
> Thanks Paul for your response.
>
> CANCEL is correctly formed, here are the INVITE and CANCEL messages sent
> by UAC,
OK. It looks valid to my eye.
(Note that the use of user=phone is incorrect, because the user part is
not valid tel uri syntax. But this is unre
Can you provide the complete INVITE and CANCEL messages?
Normally, when a CANCEL is sent there is as yet no dialog.
The rules for forming the CANCEL message mean that in such cases there
will be no to-tag in the CANCEL. The exception to that would be if you
sent a re-INVITE within an established
Hi All,
Stuck on a scenario, want to understand what should be the UAC behavior if
it receive "481 Call/Transaction Does Not Exist" for the CANCEL it sent to
terminate the transaction.
RFC3261 is not much clear on this part, here is the call flow,
UACUAS
---
