I realize I’m running the test code but I’m wondering if anyone else has seen this before. It didn’t do this in 1.2.13 so I’m wondering what changed.
If we try to park an incoming call it gets hung up right away. Here’s the console output:
— set_address_from_contact host ‘192.168.250.100’
– SIP/101-08b1af20 answered Zap/3-1
– Started music on hold, class ‘default’, on channel ‘Zap/3-1’
– Stopped music on hold on Zap/3-1
– Executing [700@internal:1] Park(“SIP/101-08b19998”, “”) in new stack
== Parked SIP/101-08b19998 on 701@parkedcalls. Will timeout back to extension [internal] s, 1 in 90 seconds
– Added extension ‘701’ priority 1 to parkedcalls
– Playing ‘digits/7’ (language ‘en’)
[Nov 27 14:20:06] WARNING[17040]: chan_sip.c:12491 handle_response: Notify answer on an owned channel?
– Playing ‘digits/0’ (language ‘en’)
– Playing ‘digits/1’ (language ‘en’)
[Nov 27 14:20:08] WARNING[17040]: chan_sip.c:12491 handle_response: Notify answer on an owned channel?
– Started music on hold, class ‘default’, on channel ‘SIP/101-08b19998’
== Spawn extension (internal, s, 1) exited KEEPALIVE on ‘SIP/101-08b19998’
== Spawn extension (aa-open, s, 1) exited non-zero on ‘Zap/3-1’
– Hungup ‘Zap/3-1’
– Stopped music on hold on SIP/101-08b19998
– Started music on hold, class ‘default’, on channel ‘SIP/101-08b19998’
– Stopped music on hold on SIP/101-08b19998
– Started music on hold, class ‘default’, on channel ‘SIP/101-08b19998’
– Stopped music on hold on SIP/101-08b19998
== SIP/101-08b19998 got tired of being parked
Any ideas? I haven’t changed any of our config files and we’re only running the trunk version because of the sccp fixes for the Cisco 7920 phones. I’ll go back to 1.2.13 if I need to.
Thanks!
Tom