I need some help.
I am running asterisk 220.127.116.11 + 18.104.22.168 Add Ons + Dahdi + tools 22.214.171.124 on a CentOS 4.7 box with kernel 2.6.9-78.EL.
I have two Snom phones 320 and a 360 with firmware 7.3.14 and an older Aastra 480i with the latest 1.4.3 firmware.
If I try to park a call with the Snom phone using either park+orbit funciton key or simply do a blind transfer using the transfer button on either the Snom or Aastra, Asterisk crashes with the following messages:
[quote]*CLI> == Using SIP RTP CoS mark 5
– Executing [204@t01-inbound:1] Answer(“SIP/t01-chris-08d587f0”, “”) in new stack
– Executing [204@t01-inbound:2] Dial(“SIP/t01-chris-08d587f0”, “SIP/t01-chris4”) in new stack
== Using SIP RTP CoS mark 5
– Called t01-chris4
– SIP/t01-chris4-08d52e60 is ringing
– SIP/t01-chris4-08d52e60 answered SIP/t01-chris-08d587f0
– Packet2Packet bridging SIP/t01-chris-08d587f0 and SIP/t01-chris4-08d52e60
== Spawn extension (t01-inbound, 204, 2) exited non-zero on ‘SIPPeer/SIP/t01-chris-08d587f0’
– Started music on hold, class ‘default’, on SIP/t01-chris4-08d52e60
== Parked SIP/t01-chris4-08d52e60 on 701@parkedcalls. Will timeout back to extension [t01-inbound] , 1 in 60 seconds
– <SIP/t01-chris-08d587f0> Playing ‘digits/7.ulaw’ (language ‘en’)
– <SIP/t01-chris-08d587f0> Playing ‘digits/0.ulaw’ (language ‘en’)
– <SIP/t01-chris-08d587f0> Playing ‘digits/1.ulaw’ (language ‘en’)
*** glibc detected *** free(): invalid pointer: 0x08d63c7c ***
However, if I transfer from the Aastra phone or use an attended transfer on the Snom, is seems to work OK. That is, if I dial 700 and wait for the digits and music, it works fine.
The problem doesn’t happen on the release of Asterisk 1.4.23
I think that there was an issue earlier this month (last month) with Polycom phones. I think it was fixed but not too sure. It also may be something to do with the extension that exits non zero ?
While I have half a clue about what I am doing, I was wondering if anyone could help me with the other missing 50%
If you need things like sip.conf, features.conf, or release versions of gcc I can provide if it will help.
Has anyone else experienced this ?? If so, do they know the work around ?