[asterisk-bugs] [JIRA] (ASTERISK-23864) Asterisk crashing when connecting to PJSIP device

Rusty Newton (JIRA) noreply at issues.asterisk.org
Tue Jun 17 09:12:56 CDT 2014


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

Rusty Newton edited comment on ASTERISK-23864 at 6/17/14 9:12 AM:
------------------------------------------------------------------

Ah I see that Asterisk is responding to this options right before crashing.

{noformat}
<--- Received SIP request (531 bytes) from UDP:190.134.55.175:5060 --->
OPTIONS sip:lx.gmc.uy SIP/2.0
Via: SIP/2.0/UDP 190.134.55.175:5060;branch=z9hG4bK664e4f79
Max-Forwards: 70
From: "asterisk" <sip:b68d677bcb7d at 190.134.55.175>;tag=as617550b3
To: <sip:lx.gmc.uy>
Contact: <sip:b68d677bcb7d at 190.134.55.175:5060>
Call-ID: 7df140065277b0d454aaad4b546607f9 at 190.134.55.175:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 12.0.0
Date: Tue, 17 Jun 2014 00:07:18 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
{noformat}


I noticed the user-agent in the options. Did you mean that the other Asterisk system (b68d677bcb7d) is using chan_sip for its channel driver? As opposed to the b68d677bcb7d pjsip device on the crashing system?

Edit: Just saw your comment "sorry, my bad... the device b68d677bcb7d is using the old sip driver. The Asterisk that's crashing is only using pjsip."

We refer to PJSIP/b68d677bcb7d or SIP/b68d677bcb7d as devices, so that was causing confusion. I understand now what you mean.


was (Author: rnewton):
Ah I see that Asterisk is responding to this options right before crashing.

{noformat}
<--- Received SIP request (531 bytes) from UDP:190.134.55.175:5060 --->
OPTIONS sip:lx.gmc.uy SIP/2.0
Via: SIP/2.0/UDP 190.134.55.175:5060;branch=z9hG4bK664e4f79
Max-Forwards: 70
From: "asterisk" <sip:b68d677bcb7d at 190.134.55.175>;tag=as617550b3
To: <sip:lx.gmc.uy>
Contact: <sip:b68d677bcb7d at 190.134.55.175:5060>
Call-ID: 7df140065277b0d454aaad4b546607f9 at 190.134.55.175:5060
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX 12.0.0
Date: Tue, 17 Jun 2014 00:07:18 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
{noformat}


I noticed the user-agent in the options. Did you mean that the other Asterisk system (b68d677bcb7d) is using chan_sip for its channel driver? As opposed to the b68d677bcb7d pjsip device on the crashing system?


> Asterisk crashing when connecting to PJSIP device
> -------------------------------------------------
>
>                 Key: ASTERISK-23864
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23864
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 12.1.1, 12.3.0
>         Environment: Ubuntu 14.04 LTS
>            Reporter: Gervasio Marchand
>            Assignee: Gervasio Marchand
>         Attachments: backtrace1211.txt, backtrace123.txt, error.log, pjsip.conf
>
>
> The extensions.conf is something like this
> {noformat}
> [incoming]
> exten => nrousa,1,GotoIf($["${CALLERID(num)}" = "11231231234"]?validatepin,2)
> exten => validatepin,2,DISA(9999,supercontext)
> [supercontext]
> exten => 9,1,Dial(PJSIP/linea at b68d677bcb7d)
> {noformat}
> The caller comes into incoming on the nrousa extension, the caller id
> matches and then it does the DISA call validating the pin... I enter the
> pin right, then dial 9 and that's when it crashes.
> I saw this on 12.1.1 and Ubuntu 12.04 LTS. I then installed an Ubuntu 14.04 LTS and downloaded Asterisk 12.3 and the issue is still there.
> You can find attached the backtraces of the issue both on 12.3 and 12.1.1



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



More information about the asterisk-bugs mailing list