Re: Unknown Number FXO

ali nasser · ‎02-27-2011

Hi,

I have CME with 12 Port's FXO when some one call from outside i am getting unknown number i check with Telco the feature is there. i enable the following debug's

• debug vpm signal
• debug vtsp dsp
• debug vtsp session

Feb 27 13:33:31.572: %SYS-5-CONFIG_I: Configured from console by vty0 (10.150.30
.38)
Feb 27 13:33:37.268: htsp_process_event: [0/2/1, FXOLS_ONHOOK, E_DSP_SIG_0000]fx
ols_onhook_ringing
Feb 27 13:33:37.268: htsp_timer - 125 msec
Feb 27 13:33:37.396: htsp_process_event: [0/2/1, FXOLS_WAIT_RING_MIN, E_HTSP_EVE
NT_TIMER]fxols_wait_ring_min_timer
Feb 27 13:33:37.396: htsp_timer - 10000 msec
Feb 27 13:33:38.264: htsp_process_event: [0/2/1, FXOLS_RINGING, E_DSP_SIG_0100]
Feb 27 13:33:38.264: fxols_ringing_not
Feb 27 13:33:38.264: htsp_timer_stop
Feb 27 13:33:38.264: htsp_timer_stop3
Feb 27 13:33:38.264: [0/2/1] htsp_stop_caller_id_rx. message length 0htsp_setup_
ind
Feb 27 13:33:38.264: [0/2/1] get_fxo_caller_id:Caller ID receive failed. parseC
allerIDString:no data.
Feb 27 13:33:38.264: [0/2/1] get_local_station_id calling num= calling name= cal
ling time=02/27 16:33 orig called=
Feb 27 13:33:38.264: [0/2/1] htsp_dsm_close_done
Feb 27 13:33:38.264: htsp_process_event: [0/2/1, FXOLS_WAIT_SETUP_ACK, E_HTSP_SE
TUP_ACK]
Feb 27 13:33:38.264: fxols_wait_setup_ack:
Feb 27 13:33:38.264: htsp_timer - 6000 msec
Feb 27 13:33:38.272: htsp_process_event: [0/2/1, FXOLS_PROCEEDING, E_HTSP_PROCEE
DING]fxols_offhook_prochtsp_alert_notify
Feb 27 13:33:38.300: htsp_process_event: [0/2/1, FXOLS_PROCEEDING, E_HTSP_ALERT]
fxols_offhook_alert
Feb 27 13:33:38.324: htsp_call_bridged invoked
Feb 27 13:33:38.324: htsp_process_event: [0/2/1, FXOLS_PROCEEDING, E_HTSP_CONNEC
T]fxols_offhook_connect
Feb 27 13:33:38.324: [0/2/1] set signal state = 0xC timestamp = 0
Feb 27 13:33:38.324: htsp_timer_stop
Feb 27 13:33:38.324: htsp_process_event: [0/2/1, FXOLS_CONNECT, E_HTSP_VOICE_CUT
_THROUGH]fxols_connect_proc_voice
Feb 27 13:33:57.420: htsp_digit_ready(0/2/1): digit = 0
Feb 27 13:33:57.900: htsp_digit_ready(0/2/1): digit = 0
Feb 27 13:33:58.420: htsp_digit_ready(0/2/1): digit = 0
Feb 27 13:33:59.660: htsp_digit_ready(0/2/1): digit = 1
Feb 27 13:34:05.644: htsp_timer_stop3
Feb 27 13:34:05.644: [0/3/3] htsp_stop_caller_id_rx. message length 0htsp_setup_
req
Feb 27 13:34:05.644: [0/3/3] htsp_dsm_close_done
Feb 27 13:34:05.644: htsp_process_event: [0/3/3, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]
fxols_onhook_setup
Feb 27 13:34:05.644: [0/3/3] set signal state = 0xC timestamp = 0
Feb 27 13:34:05.644: htsp_timer - 1300 msec
Feb 27 13:34:05.920: htsp_process_event: [0/3/3, FXOLS_WAIT_DIAL_TONE, E_DSP_SIG
_0110]fxols_disc_clear
Feb 27 13:34:05.920: htsp_timer_stop2
Feb 27 13:34:05.920: htsp_timer - 1300 msec
Feb 27 13:34:07.220: htsp_process_event: [0/3/3, FXOLS_WAIT_DIAL_TONE, E_HTSP_EV
ENT_TIMER]fxols_wait_dial_timer htsp_dial
Feb 27 13:34:08.040: htsp_process_event: [0/3/3, FXOLS_WAIT_DIAL_DONE, E_DSP_DIA
LING_DONE]fxols_wait_dial_done htsp_progress
Feb 27 13:34:08.040: htsp_timer - 350 msec
Feb 27 13:34:08.040: htsp_call_bridged invoked
Feb 27 13:34:08.040: htsp_call_bridged invoked
Feb 27 13:34:08.040: htsp_process_event: [0/3/3, FXOLS_WAIT_CUT_THRU, E_HTSP_VOI
CE_CUT_THROUGH]fxols_handle_cut_thru
Feb 27 13:34:08.040: htsp_timer_stop
Feb 27 13:34:08.040: htsp_process_event: [0/2/1, FXOLS_CONNECT, E_HTSP_VOICE_CUT
_THROUGH]fxols_connect_proc_voice
PBK_Makkah#

this the output

please advice.

Regards,

Christopher Graham · ‎02-27-2011

The telling line is:

Feb 27 13:33:38.264: [0/2/1] get_fxo_caller_id:Caller ID receive failed. parseC
allerIDString:no data.

Looks like the caller ID is not recognized. You mentioned that the issue is intermittent. Do you know if the issue is limited to a single port, or VWIC? There may be static or noise in the line that is preventing the tone from being recognized as CLID. If you are familiar with the PCM capture process, you can get a PCM capture, open a TAC case, and have them decode the capture to see what is being received on the port.

jijopaul · ‎02-27-2011

Hi,

Caller ID is an analog service by which a telephone central office (CO) switch sends digital information about incoming calls. The Caller ID name delivery feature for analog Foreign Exchange Station (FXS) ports was first introduced in Cisco IOS® Software Release 12.1(2)XH. It is available on all subsequent Cisco IOS software releases. This feature is available and configurable on a per-port basis to phones connected to analog FXS voice ports. This feature is also available on analog Foreign Exchange Office (FXO

The [no] caller-id enable command enables or disables the transmission of Caller ID on an FXS port, and enables or disables reception of Caller ID on an FXO port.

Issue the caller-id enable command to enable the Caller ID name for inbound PSTN calls on the FXO port.

You must configure the alerting method when the Caller ID standard, specified by locale through the cptone command, is not Bellcore/Telcordia. If you do not configure the alerting method, the default caller-id alerting ring 1 command is applied. The command that you enter is determined by the Bellcore/Telcordia or ETSI standard that your service provider uses for Caller ID

Note:

This command works only if the gateway is configured as H.323 with the Cisco CallManager. If a Media Gateway Control Protocol (MGCP) configuration is used, Caller ID is not supported on the FXO port

Note:

Caller ID is disabled by default.

After trying this if you still facing any problem .

Remove the phone line from FXO port and connect a analogue phone directly and see wheather you are recieving CLID from telco.

After connecting directly to a phone If you are recieving CLID then try to change the cptone in FXO ports to some another CP tone .