MixMonitor casues asterisk 1.2.3 to terminate

Asterisk Asterisk Support
1

I had posted this on the BSD forum, but no answer there, so will try it again here.

I am testing MixMonitor on Asterisk 1.2.3 on FreeBSD 5.4

The following batch of extensions:

exten => 299,1,Answer()
exten => 299,n,MixMonitor(manuel.gsm)
exten => 299,n,SayDigits(12345670)
exten => 299,n,StopMonitor()
exten => 299,n,Hangup()

runs ok until hangup. At that point Asterisk terminates. (That is the process terminates with a signal 11)

PS: Problem still exists on 1.2.4

Anybody else seen this problem?

PS: Signal 11, or officially know as “segmentation fault”, means that the program accessed a memory location that was not assigned.

2

Just to add on this, I’m running Linux with asterisk 1.2.7.1 (was doing the same thing with older 1.2 version) and I got this problem also, but not on every calls, it append arround 1/5 of the times.

I still need to do more test on this (I’m working on production environnement, so I can test only at night) But the crash occur mostly when mixmonitor is started and then I end up in voicemail. Then the recording of the voicemail msg and the mixmonitor goes well until I hangup. Againg asterisk crash 1/5 of the times at this point.

I know there seems to still have a lot of bugs on app_mixmonitor

But there is people using mixmonitor here in production environnement without problems ?

Thanks for advise !

3

mixmonitor is buggy as hell - i know 1.2.7 had several bugfixes in it, but i don’t think they have it completely solid yet.

you might check the bugtracker, perhaps there are a few patches you could utilize.