[asterisk-bugs] [JIRA] (ASTERISK-30342) Receive OPTIONS message, sometimes cannot send response "Unable to send response (-1)"

[Dan Cropp (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260811#comment-260811 ] 

Dan Cropp commented on ASTERISK-30342:
--------------------------------------

Thank you Joshua.

You are absolutely correct (as usual).  Removing the allow_reload (or setting it to no) did solve the problem.
Closing the issue.



> Receive OPTIONS message, sometimes cannot send response "Unable to send response (-1)"
> --------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30342
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30342
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 18.15.0, 18.15.1
>         Environment: Ubuntu 20
>            Reporter: Dan Cropp
>            Assignee: Dan Cropp
>         Attachments: debug_log, messages, pjsip.conf
>
>
> We have two Asterisk VMs front ended by a Kamailio box.
> Kamailio sends OPTIONS messages to Asterisk to determine if it's still alive.
> Whichever one has been alive for the longest, is treated as the active Asterisk.
> Everything has been working awesome when running Asterisk 18.12.1.
> Yesterday, we upgraded the boxes to Asterisk 18.15.0 and started seeing some Asterisk unable to send responses to the OPTIONS messages from Kamailio.  It seems to only happen for a period of time, then it suddenly starts working.
> It appears as though the OPTIONS message is processed correctly, but when it attempts to send the response it fails.
> ERROR[1281] res_pjsip/pjsip_options.c: Unable to send response (-1)
> What is really strange is that after a period of time, it suddenly is able to successfully send responses to OPTIONS messages from Kamailio.
> If we then change the configurations and tell asterisk reload, the same issue repeats.



--
This message was sent by Atlassian JIRA
(v6.2#6252)