Interpreter output debug signal in E&M

felixlino · ‎01-23-2008

*Jan 17 20:56:09.871: htsp_timer_stop3

*Jan 17 20:56:09.875: htsp_process_event: [0/2/0, EM_WAIT_FOR_ANSWER, E_HTSP_RELEASE_REQ]em_wait_answer_release

*Jan 17 20:56:09.875: em_stop_timers

*Jan 17 20:56:09.875: htsp_timer_stop

*Jan 17 20:56:09.875: htsp_timer_stop2 em_onhook (0)

*Jan 17 20:56:09.875: [0/2/0] set signal state = 0x0 timestamp = 0

*Jan 17 20:56:09.875: em_start_timer: 400 ms

*Jan 17 20:56:09.875: htsp_timer - 400 msec

*Jan 17 20:56:10.275: htsp_process_event: [0/2/0, EM_GUARD_ALL, E_HTSP_EVENT_TIMER]em_guard_all_timer

*Jan 17 20:56:10.275: em_stop_timers

*Jan 17 20:56:10.275: htsp_timer_stop

*Jan 17 20:56:10.275: em_start_timer: 3000 ms

*Jan 17 20:56:10.275: htsp_timer - 3000 msec

*Jan 17 20:56:10.275: htsp_process_event: [0/2/0, EM_PARK, E_DSP_SIG_0000]em_park_onhook

*Jan 17 20:56:10.275: htsp_timer_stop

*Jan 17 20:56:10.275: htsp_timer_stop2 htsp_report_onhook_sig

pcameron · ‎01-27-2008

the voice port 0/2/0 waited for an answer signal from the PBX. Since this is the same debug output related to the call drop after 3 minutes that was on the IPtel forum, it means you need to add 'auto-cut-through' under the voiceport, or get the PBX techs to programme their PBX properly to provide answer supervision when the PBX extension is picked up.