[asterisk-users] Asterisk 18.12.1 to 18.15.0 upgrade seems to have introduced a behavior where PJSIP is unable to send a response to OPTIONS (seems to resolve after anywhere a period of time)

[Joshua C. Colp]

On Wed, Dec 7, 2022 at 11:34 AM Joshua C. Colp <jcolp at sangoma.com> wrote:

> On Wed, Dec 7, 2022 at 11:26 AM Dan Cropp <dan at amtelco.com> wrote:
>
>> On two VMs, we encounter a strange behavior when we upgrade from 18.12.1
>> to 18.15.0 (also tried 18.15.1 last night).
>>
>> When we roll the VMs back to 18.12.1, we don’t see the behavior repeat.
>>
>>
>>
>> We have a Kamailio VM front ending the asterisk.
>>
>>
>>
>> It sends OPTIONS messages periodically.
>>
>>
>>
>> After startup (and also after reloading configuration settings), we see
>> periods where the response can’t be sent.
>>
>> After a period of time, it suddenly starts working.
>>
>>
>>
>  I haven't seen this before, and haven't seen any other reports of it so
> far. The OPTIONS code itself hasn't changed between the two. There was a
> fix for a crash in send_stateful_response so adding log messages to the
> error cases is likely needed to see in particular which one is failing.
>
>
Ha, those changes haven't even landed yet. It's pretty much a thin wrapper
over PJSIP stuff in 18.15.1. The PJSIP versions are also fairly close too.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20221207/f060719a/attachment.html>