AlarmReceiver causing asterisk to crash

I have an asterisk server setup, and I trying to get AlarmReceiver to work.
everything appears to be setup correctly, but when I call into the sip account it rings ok, but when it answers the call it appears that asterisk reloads.
If I cancel the call before the ring timeout everything seems ok, it is only after alarmreceiver answers the call.
I have checked and alarmreceiver is installed.
If I change the trunk to ring an extension everything appears to work fine, and I have speech between the two.
Does anyone have any ideas as to what is causing the server to reload?

If I hangup before it answers I get the following :-

[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:1] Set(“SIP/Voipfone-00000004”, “__FROM_DID=xxxxxxxx”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:2] Set(“SIP/Voipfone-00000004”, “CDR(did)=xxxxxxxx”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:3] ExecIf(“SIP/Voipfone-00000004”, “0 ?Set(CALLERID(name)=xxxxxxxx)”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:4] Set(“SIP/Voipfone-00000004”, “__CALLINGPRES_SV=allowed_not_screened”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:5] Set(“SIP/Voipfone-00000004”, “CALLERPRES()=allowed_not_screened”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [xxxxxxxx@from-pstn:6] Goto(“SIP/Voipfone-00000004”, “custom-myalarmreceiver,s,1”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Goto (custom-myalarmreceiver,s,1)
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [s@custom-myalarmreceiver:1] NoOp(“SIP/Voipfone-00000004”, “Alarm received”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [s@custom-myalarmreceiver:2] Answer(“SIP/Voipfone-00000004”, “”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [s@custom-myalarmreceiver:3] Ringing(“SIP/Voipfone-00000004”, “”) in new stack
[2012-09-16 12:14:26] VERBOSE[10379] pbx.c: – Executing [s@custom-myalarmreceiver:4] Wait(“SIP/Voipfone-00000004”, “2”) in new stack
[2012-09-16 12:14:28] VERBOSE[10379] pbx.c: == Spawn extension (custom-myalarmreceiver, s, 4) exited non-zero on ‘SIP/Voipfone-00000004’

If I allow it to answer I get :-

[2012-09-16 12:18:02] VERBOSE[10009] netsock.c: == Using UDPTL TOS bits 184
[2012-09-16 12:18:02] VERBOSE[10009] netsock.c: == Using UDPTL CoS mark 5
[2012-09-16 12:18:02] VERBOSE[10009] netsock2.c: == Using SIP RTP TOS bits 184
[2012-09-16 12:18:02] VERBOSE[10009] netsock2.c: == Using SIP RTP CoS mark 5
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:1] Set(“SIP/Voipfone-00000005”, “__FROM_DID=xxxxxxxx”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:2] Set(“SIP/Voipfone-00000005”, “CDR(did)=xxxxxxxx”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:3] ExecIf(“SIP/Voipfone-00000005”, “0 ?Set(CALLERID(name)=xxxxxxxx)”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:4] Set(“SIP/Voipfone-00000005”, “__CALLINGPRES_SV=allowed_not_screened”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:5] Set(“SIP/Voipfone-00000005”, “CALLERPRES()=allowed_not_screened”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [xxxxxxxx@from-pstn:6] Goto(“SIP/Voipfone-00000005”, “custom-myalarmreceiver,s,1”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Goto (custom-myalarmreceiver,s,1)
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [s@custom-myalarmreceiver:1] NoOp(“SIP/Voipfone-00000005”, “Alarm received”) in new stack
[2012-09-16 12:18:02] VERBOSE[10473] pbx.c: – Executing [s@custom-myalarmreceiver:2] Answer(“SIP/Voipfone-00000005”, “”) in new stack
[2012-09-16 12:18:03] VERBOSE[10473] pbx.c: – Executing [s@custom-myalarmreceiver:3] Ringing(“SIP/Voipfone-00000005”, “”) in new stack
[2012-09-16 12:18:03] VERBOSE[10473] pbx.c: – Executing [s@custom-myalarmreceiver:4] Wait(“SIP/Voipfone-00000005”, “2”) in new stack
[2012-09-16 12:18:05] VERBOSE[10473] pbx.c: – Executing [s@custom-myalarmreceiver:5] AlarmReceiver(“SIP/Voipfone-00000005”, “”) in new stack
[2012-09-16 12:18:05] WARNING[10473] channel.c: Codec mismatch on channel SIP/Voipfone-00000005 setting write format to slin from ulaw native formats 0x8 (alaw)
[Sep 16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/logger.conf’: [Sep 16 12:18:10] VERBOSE[10481] config.c: == Found
[Sep 16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/logger_general_additional.conf’: [Sep 16 12:18:10] VERBOSE[10481] config.c: == Found
[Sep 16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/logger_general_custom.conf’: [Sep 16 12:18:10] VERBOSE[10481] config.c: == Found
[Sep 16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/logger_logfiles_additional.conf’: [Sep 16 12:18:10] VERBOSE[10481] config.c: == Found
[Sep 16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/logger_logfiles_custom.conf’: [Sep 16 12:18:10] VERBOSE[10481] config.c: == Found
[2012-09-16 12:18:10] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: [2012-09-16 12:18:10] VERBOSE[10481] config.c: == Found
[2012-09-16 12:18:11] VERBOSE[10481] manager.c: == Manager registered action DataGet
[2012-09-16 12:18:11] VERBOSE[10481] loader.c: Asterisk Dynamic Loader Starting:
[2012-09-16 12:18:11] VERBOSE[10481] config.c: == Parsing ‘/etc/asterisk/modules.conf’: [2012-09-16 12:18:11] VERBOSE[10481] config.c: == Found
[2012-09-16 12:18:11] NOTICE[10481] loader.c: 2 modules will be loaded.
Followed by what looks to be an asterisk reload.

I am not sure why I am getting the codec mismatch, this does not appear when it is setup as an extension.

I am running ASTERISK 2.10.0.1 , i think with FREEPBX.

Any help to sort this would be most appriciated.
Thanks
Andy

There is no Asterisk 2.x.x.x. It went straight from 1.8.x to 10.x

If you are using currently supported version, please see wiki.asterisk.org/wiki/display/ … +Backtrace

You should then check to see if it has already been reported on issues.asterisk.org/jira, and, if not report, attaching backtraces

I do seem to remember some recent issues being reported there, relating to Alarm Receiver.

Thanks David
There does appear to have been some problems, along with a patch.
Question now is, how would I install the patch? I can only find the app_alarmreceiver.so file and no app_alarmreveiver.c file.
Thanks
Andy

It would appear I am running version Asterisk 1.8.9.3 , which i guess wont have the patch installed.
Thanks

I ran into problems with getting the alarmreceiver module to function too. There seems to be a problem with the alarmreceiver module and/or dsp.c module re: dtmf. I had the module working for years with an old version of Asterisk but could not get the alarmreceiver module to work with Asterisk 10 or 11. However it works perfectly with Asterisk 8.18.0

I used a PBX in a Flash distro.

FYI - I wrote up a very detailed procedure for the alarmreceiver module at the link below if interested:

viewtopic.php?f=1&t=84955