Spy hangup crashing Asterisk (1.12.1)

This is something new I’ve just discovered on my new installation of 1.12.1 (wasn’t occurring on 1.2.3, our old box):

CLI:

3 active IAX channels
== Done Spying on channel IAX2/voipgate-14
h1033634*CLI>
Disconnected from Asterisk server
Executing last minute cleanups

i.e. a spy hangup is crashing our whole asterisk process.

Full Log looks like this:

Sep 15 12:29:04 VERBOSE[11707] logger.c: – Accepting AUTHENTICATED call from 84.73.7.247:
> requested format = gsm,
> requested prefs = (),
> actual format = ulaw,
> host prefs = (ulaw|alaw|gsm|speex|ilbc),
> priority = mine
Sep 15 12:29:04 VERBOSE[12779] logger.c: – Executing ChanSpy(“IAX2/911-2”, “|q”) in new stack
Sep 15 12:29:04 DEBUG[11698] channel.c: Avoiding initial deadlock for 'IAX2/911-2’
Sep 15 12:29:05 VERBOSE[12779] logger.c: == Spying on channel IAX2/voipgate-8
Sep 15 12:29:05 NOTICE[12779] app_chanspy.c: Attaching IAX2/911-2 to IAX2/voipgate-8
Sep 15 12:29:05 DEBUG[12779] channel.c: Spy ChanSpy added to channel IAX2/voipgate-8
Sep 15 12:29:05 DEBUG[11707] chan_iax2.c: Ooh, voice format changed to 4
Sep 15 12:29:05 DEBUG[12293] channel.c: Building translator from alaw to SLINEAR for spies on channel IAX2/voipgate-8
Sep 15 12:29:05 DEBUG[12293] channel.c: Building translator from alaw to SLINEAR for spies on channel IAX2/voipgate-8
Sep 15 12:29:05 DEBUG[11707] chan_iax2.c: Peer lastms 117, historicms 117, maxms 2000
Sep 15 12:29:09 DEBUG[11707] chan_iax2.c: Immediately destroying 2, having received hangup
Sep 15 12:29:09 DEBUG[12779] channel.c: Spy ChanSpy removed from channel IAX2/voipgate-8
Sep 15 12:29:09 VERBOSE[12779] logger.c: == Done Spying on channel IAX2/voipgate-8

Whereby * crashes.

This is ONLY happening with when hangup is pressed whilst spying on the voipgate (or other provider) channel. When hangup is sent whilst spying on our “internal” extensions (which are also out in the internet), system works normally (i.e. hangup of spy with no * crash)

any ideas?

no word on this? i’ve posted it as a bug…

I am experiencing the same problem. Does anyone know a workaround / solution?

I am experiencing the same problem. Does anyone know a workaround / solution?