Summary:ASTERISK-11685: Periodic app_page pthread_mutex_lock segfault
Reporter:Mitch Sharp (bluecrow76)Labels:
Date Opened:2008-03-19 12:15:22Date Closed:2008-03-19 12:18:54
Versions:Frequency of
Environment:Attachments:( 0) asterisk-1.4.18-app_page-pthread_mutex_lock-segfault.txt
Description:We installed this system on March 11 running asterisk 1.4.18.  We are getting periodic crashes on the system when paging.  I initially thought it may be related to the console/dsp device, so I removed it from the Page list and it still crashed.

I am installing 1.4.19-rc3 today to see if anything in there will fix the issue, but I can't see anything obvious from the ChangeLog that would help the situation.

We page between 50-100 times per day.  Below are the dates and times that it crashed:

Mar  7 07:38 core-2008-03-07T07:38:20-0600
Mar 11 13:05 core-2008-03-11T13:05:38-0500
Mar 14 09:34 core-2008-03-14T09:34:57-0500
Mar 18 11:27 core-2008-03-18T11:27:29-0500

As you can see it is not consistent.

All the SIP devices that are being paged are Polycom IP 550's running 3.0.0 firmware.


This is the dialplan that does the paging:

exten => dopage,1,Answer
exten => dopage,n,NoCDR
exten => dopage,n,Set(CALLERID(name)=Page:${CALLERID(name)})
exten => dopage,n,SIPAddHeader(Alert-Info: Auto Answer)
exten => dopage,n,Set(TIMEOUT(absolute)=60)
exten => dopage,n,Page(${PAGEGROUP},s)
exten => dopage,n(hangup),Hangup
exten => dopage,n(busy),Set(TIMEOUT(absolute)=10)
exten => dopage,n,Busy

exten => 70,1,Set(PAGEEXT=${EXTEN})
exten => 70,n,Set(PAGEGROUP=console/dsp&SIP/xxxxxxxxxx221&SIP/xxxxxxxxxx222&SIP/xxxxxxxxxx223&SIP/xxxxxxxxxx224&SIP/xxxxxxxxxx225&SIP/xxxxxxxxxx226&SIP/xxxxxxxxxx227&SIP/xxxxxxxxxx228&SIP/xxxxxxxxxx229&SIP/xxxxxxxxxx230&SIP/xxxxxxxxxx231&SIP/xxxxxxxxxx232&SIP/xxxxxxxxxx233&SIP/xxxxxxxxxx235&SIP/xxxxxxxxxx236&SIP/xxxxxxxxxx237&SIP/xxxxxxxxxx238&SIP/xxxxxxxxxx239&SIP/xxxxxxxxxx244&SIP/xxxxxxxxxx246&SIP/xxxxxxxxxx248&SIP/xxxxxxxxxx249&SIP/xxxxxxxxxx250&SIP/xxxxxxxxxx252)
exten => 70,n,Goto(dopage,1)
Comments:By: Mark Michelson (mmichelson) 2008-03-19 12:18:54

This is the same issue as 12038, which has been fixed.