05-18-2014 11:54 PM - edited 03-16-2019 10:50 PM
Hi,
I have customer complain that fxo port open before the extension answer the call which cause the call to be charged by telecom company
the gateway is registered with call manager using mgcp
so is there any configuration like opx in h323
05-19-2014 09:56 AM
Will probably need some debugs such as "debug vpm signal" so we can see what is being sent out on the analog port for one of these calls.
05-19-2014 11:09 PM
this debug output
i called direct line fxo port which registered with mgcp and the port opened before the extension answer the call
port configuration
!
voice-port 0/0/1
cptone BE
timing hookflash-out 50
timing guard-out 1000
impedance complex2
caller-id enable
caller-id alerting line-reversal
caller-id alerting dsp-pre-allocate
debug output
May 20 05:59:01.080: [0/0/1] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE_SM_CALLERID_RX
May 20 05:59:01.080: htsp_process_event: [0/0/1, FXOLS_ONHOOK, E_HTSP_CALLERID_RX_DONE]
May 20 05:59:01.080: [0/0/1] htsp_stop_caller_id_rx. message length 11
May 20 05:59:01.080: [0/0/1] htsp_dsm_close_done
May 20 05:59:02.308: htsp_process_event: [0/0/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
May 20 05:59:02.312: htsp_timer - 125 msec
May 20 05:59:02.440: htsp_process_event: [0/0/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
May 20 05:59:02.440: htsp_timer - 10000 msec
May 20 05:59:03.296: htsp_process_event: [0/0/1, FXOLS_RINGING, E_DSP_SIG_0100]
May 20 05:59:03.296: fxols_ringing_not
May 20 05:59:03.296: htsp_timer_stop
May 20 05:59:03.296: htsp_timer_stop3 htsp_setup_ind
May 20 05:59:03.296: [0/0/1] get_fxo_caller_id:Caller ID received. Message type=129 length=11 checksum=00
May 20 05:59:03.296: [0/0/1] Caller ID String 44 31 32 32 32 38 39 32 30 30
May 20 05:59:03.296: [0/0/1] get_fxo_caller_id calling num=122289200 calling name= calling time=05/20 08:59
May 20 05:59:03.304: htsp_process_event: [0/0/1, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
May 20 05:59:03.304: fxols_wait_setup_ack:
May 20 05:59:03.304: [0/0/1] set signal state = 0xC timestamp = 0fxols_check_auto_call
May 20 05:59:03.308: htsp_process_event: [0/0/1, FXOLS_PROCEEDING, E_HTSP_SETUP_ACK]
May 20 05:59:03.308: htsp_process_event: [0/0/1, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect
May 20 05:59:03.308: htsp_timer_stop
May 20 05:59:03.320: htsp_call_bridged invoked
May 20 05:59:03.324: htsp_process_event: [0/0/1, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
May 20 05:59:03.324: htsp_process_event: [0/0/1, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
May 20 05:59:03.576: htsp_process_event: [0/0/1, FXOLS_CONNECT, E_DSP_SIG_0110]fxols_rvs_battery
May 20 05:59:03.576: htsp_timer_stop2
May 20 05:59:03.576: htsp_timer_stop2
06-02-2014 11:09 AM
There is how FXO port will answer the call, as soon as it gets an setup indication on the wire, it would go off hook to establish the call on IP Leg.
you may also see the behavior, when an IP phone makes an outgoing call via FXO port, call shows as connected on IP phone, whereas called number is still ringing.
Behavior may change when configuring answer supervision on voice-port. But one drawback which is been usually seen is caller that ip phone callers missing ringback on PSTN calls.
Additionally below said debugs would help more.,
debug vpm signal
debug voip vtsp all
debug mgcp packets ( Assuming you are still running MGCP )
debug voip ccapi inout
Thanks,
Amit
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: