12-21-2022 08:01 AM
We have fax lines setup that are connected to VG224. Recently more and more of the fax lines just ring. We never get to the fax tones.
We have been working with our provider and Cisco and no one can figure out what the issue is. And with VG224s being EOS, they won't go into them extensively.
Most of the programming on the VGs have been there for 5+ years.
Also, our former voice engineers programmed the VGs that random ports are SCCP and some are MGCP. I have one that has ports 12, 14, and 17 as MGCP and the rest are SCCP.
Does anyone have any ideas as to what I need to look for, try or ask our provider to look for in CUCM?
12-21-2022 09:10 AM
Hi,
Did you try to disable ECM on theV VG?
no mgcp fax ecm
Can you also specify which kind of PSTN line are you usig?
Thanks a lot
BR
Carlo
12-21-2022 11:59 AM
I have been comparing the config with another one that is working and no mgcp fax ecm is not on either of them.
Kind of PSTN line we are using - so you mean E or T1? Honestly not sure. When we moved to our managed provider we ported all the numbers over to them.
12-21-2022 12:37 PM
12-21-2022 08:06 PM
Router01#debug vpm signal
Voice Port Module signaling debugging is enabled
Router01#debug vtsp tone
This CLI command is now 'debug voip vtsp tone'
Router01#term mon
Router01#
Dec 22 03:59:01.815: htsp_timer_stop3 htsp_setup_req
Dec 22 03:59:01.819: htsp_process_event: [0/0, FXSLS_ONHOOK, E_HTSP_SETUP_REQ]fxsls_onhook_setuphtsp_progress
Dec 22 03:59:01.819: [0/0] set signal state = 0x0 timestamp = 0
Dec 22 03:59:01.819: [0/0] htsp_set_caller_id_tx calling num=+1XXXXXXXXXX display_info=WIRELESS CALLER called num=1XXXXXXXXXX
Dec 22 03:59:01.819: [0/0] Caller ID String 80 27 01 08 31 32 32 32 30 33 35 39 02 0A 36 30 37 36 38 34 38 36 39 31 07 0F 57 49 52 45 4C 45 53 53 20 43 41 4C 4C no 45 52 3E
Dec 22 03:59:01.819: [0/0] htsp_set_caller_id_tx_time Caller ID:FSK_DURING_RING
Dec 22 03:59:01.819: [0/0] htsp_start_caller_id_tx string length=42
Router01#htsp_call_feature:feature 12
Dec 22 03:59:01.823: htsp_process_event: [0/0, FXSLS_WAIT_OFFHOOK, E_HTSP_POWER_RINGING]fxsls_callback_ringing
Dec 22 03:59:01.823: [0/0] set signal state = 0x0 timestamp = 0htsp_alert
Router01#
Dec 22 03:59:05.392: htsp_timer_stop3
Router01#htsp_call_feature:feature 34
Dec 22 03:59:21.360: htsp_timer_stop3
Dec 22 03:59:21.360: htsp_process_event: [0/0, FXSLS_WAIT_OFFHOOK, E_HTSP_STOP_RINGING]fxsls_stop_ringing
Dec 22 03:59:21.360: [0/0] set signal state = 0x4 timestamp = 0
Dec 22 03:59:21.360: htsp_process_event: [0/0, FXSLS_WAIT_OFFHOOK, E_HTSP_RELEASE_REQ]fxsls_waitoff_release
Dec 22 03:59:21.360: [0/0] set signal state = 0x4 timestamp = 0
Router01#
Dec 22 03:59:32.585: htsp_process_event: [0/0, FXSLS_ONHOOK, E_DSP_SIG_1100]fxsls_onhook_offhook htsp_setup_ind
Dec 22 03:59:32.585: [0/0] get_local_station_id calling num= calling name= calling time=12/22 03:59 orig called=
Dec 22 03:59:32.593: htsp_process_event: [0/0, FXSLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]fxsls_check_auto_call
Router01#
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