Sending 481 response

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alexander Agranovsky wrote:
> Yep, BYE definitely doesn't have a To: tag (since 100 Trying doesn't  
> contain it ;-))

Yeah, the UA layer is only interested with handling requests with To 
tag in it. If the request doesn't have To tag, it will be forwarded 
to application (which in this case is not interested in handling BYE 
outside any dialogs!).

  -benny

> - Alex
> 
> On Nov 4, 2007, at 6:33 AM, Benny Prijono wrote:
> 
>> Alexander Agranovsky wrote:
>>> Just noticed a scenario:
>>>
>>> An endpoint sends CANCEL to freshly initialized PJSIP stack (say,
>>> after crash, debugger restart etc). PJSIP properly responds with 481.
>>>
>>> Then, the endpoint proceeds to send BYE for the same call. This is
>>> pretty much invalid (since 481 has already been returned for
>>> transaction on the same dialog), however the point is -- PJSIP never
>>> responds to this BYE allowing for (and processing) a bunch of
>>> retransmissions. If 481 was sent as a response to these, the outcome
>>> would be better, IMHO.
>>>
>>> Not a critical issue, of course, but would be interesting to know why
>>> the 481 is never sent for BYE?
>> In my test, 481 *is* returned for BYE outside any dialog. Maybe in
>> your case, the BYE doesn't have a To tag?
>>
>>   -benny





[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux