02-22-2017 01:48 AM - edited 03-17-2019 09:37 AM
All,
I have a situation with an outbound FXO call failing. I have collected debugs and can see the following:
Feb 21 15:34:25 GMT: Orig called num:399
Feb 21 15:34:25 GMT: htsp_process_event: [0/1/0, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_setup
Feb 21 15:34:25 GMT: [0/1/0] set signal state = 0xC timestamp = 0
Feb 21 15:34:25 GMT: htsp_timer - 1300 msec
Feb 21 15:34:25 GMT: //198765/0F71498683D3/CCAPI/cc_api_call_proceeding:
Interface=0x225AA89C, Progress Indication=NULL(0)
Feb 21 15:34:26 GMT: htsp_process_event: [0/1/0, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_power_denial_detected
Feb 21 15:34:26 GMT: htsp_timer2 - 1000 msec
Feb 21 15:34:26 GMT: htsp_timer_stop
Feb 21 15:34:27 GMT: htsp_process_event: [0/1/0, FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER2]fxols_power_den_disc
Feb 21 15:34:27 GMT: htsp_timer_stop
Feb 21 15:34:27 GMT: htsp_timer_stop2
Feb 21 15:34:27 GMT: [0/1/0] set signal state = 0x4 timestamp = 0
This is the FXO port cfg:
voice-port 0/1/0
timing hookflash-out 50
timing guard-out 1000
Any ideas why all of a sudden this is failing?
KR,
D
02-22-2017 01:54 AM
In the htsp events it can be seen that the port is detecting a power denial
Feb 21 15:34:26 GMT: htsp_process_event: [0/1/0, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG_1100]fxols_power_denial_detected
Try using no supervisory disconnect signal and see if this helps or not.
Regards
Abhay
02-22-2017 07:53 AM
Thanks Abhay. Unfortunately this didn't fix the issue. I am going to test with a POTS handset attached to the FXO to ensure the line is good.
D
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide