Incoming CLID through FXO port

wissamnad · ‎12-06-2012

Hi all,

I am getting a strange caller id on my 292 extension such as (22428, 22112, ...) whenever I try to call from the PSTN to the number associated to the voice port 0/0/1. I don't have any translations implemented. If the line provided from the Telco is directly connected to an analog telephone, the clid is correct but whenever its received by the router the caller id is showing 5 or 4 digits which doesnt make any sense.

I have the following config on a H323 voice gateway:

voice-port 0/0/1

trunk-group PSTN

connection plar opx 292

caller-id enable

dial-peer voice 1 pots

trunkgroup PSTN

description Calls to Fix land Lines

destination-pattern [2]........

!

dial-peer voice 2 pots

trunkgroup PSTN

description Mobile Calls

destination-pattern 9........

forward-digits all

!

dial-peer voice 5 pots

trunkgroup PSTN

description International Calls

destination-pattern 00T

forward-digits all

!

dial-peer voice 6 voip

destination-pattern 2..

session target ipv4:192.168.1.31

!

dial-peer voice 7 pots

incoming called-number .

paolo bevilacqua · ‎12-06-2012

Take "debug vpm signal" with "term mon" to see if CLID is right.

wissamnad · ‎12-06-2012

I already tried it, I called from a line 22XXXXXXX (which is another FXO port on the same router) and it seems that some digits are being stripped from the caller id (digits stripped randomly from the middle and the end), please have a look, the calling number is in bold

Dec 6 21:27:54.757: htsp_timer_stop3 htsp_setup_req

Dec 6 21:27:54.757: htsp_process_event: [0/0/1, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_setup

Dec 6 21:27:54.757: [0/0/1] set signal state = 0xC timestamp = 0

Dec 6 21:27:54.757: htsp_timer - 1300 msec

Dec 6 21:27:56.057: htsp_process_event: [0/0/1, FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER]fxols_wait_dial_timer htsp_dial

Dec 6 21:27:57.881: htsp_process_event: [0/0/1, FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE]fxols_wait_dial_done htsp_progress

Dec 6 21:27:57.881: htsp_timer - 350 msec

Dec 6 21:27:57.881: htsp_call_bridged invoked

Dec 6 21:27:57.893: htsp_process_event: [0/0/1, FXOLS_WAIT_CUT_THRU, E_HTSP_VOICE_CUT_THROUGH]fxols_handle_cut_thru

Dec 6 21:27:57.893: htsp_timer_stop

Dec 6 21:27:59.021: htsp_process_event: [0/0/2, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

Dec 6 21:27:59.021: htsp_timer - 125 msec

Dec 6 21:27:59.149: htsp_process_event: [0/0/2, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

Dec 6 21:27:59.149: htsp_timer - 10000 msec

Dec 6 21:27:59.149: htsp_timer3 - 5600 msec

Dec 6 21:27:59.149: [0/0/2] htsp_start_caller_id_rx:BELLCORE

Dec 6 21:27:59.149: htsp_start_caller_id_rx create dsp_stream_manager

Dec 6 21:27:59.149: [0/0/2] htsp_dsm_create_success returns 1

Dec 6 21:28:00.073: htsp_process_event: [0/0/2, FXOLS_RINGING, E_DSP_SIG_0100]

Dec 6 21:28:00.073: fxols_ringing_not

Dec 6 21:28:00.073: htsp_timer_stop

Dec 6 21:28:00.073: htsp_timer - 10000 msec

Dec 6 21:28:00.893: [0/0/2] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE_SM_CALLERID_RX

Dec 6 21:28:00.893: htsp_process_event: [0/0/2, FXOLS_RINGING, E_HTSP_CALLERID_RX_DONE]

Dec 6 21:28:00.893: htsp_timer_stop

Dec 6 21:28:00.893: htsp_timer_stop3

Dec 6 21:28:00.893: [0/0/2] htsp_stop_caller_id_rx. message length 20htsp_setup_ind

Dec 6 21:28:00.893: [0/0/2] get_fxo_caller_id:Caller ID received. Message type=4 length=20 checksum=8F

Dec 6 21:28:00.893: [0/0/2] Caller ID String 04 11 B0 31 B0 32 32 B0 32 37 32 32 B6 34 32 B5 38 B0 31 8F

Dec 6 21:28:00.893: [0/0/2] get_fxo_caller_id calling num=224281 calling name= calling time=01/02 148:27

Dec 6 21:28:00.893: fxols_callerid_done: call being answered

Dec 6 21:28:00.897: [0/0/2] htsp_dsm_close_done

Dec 6 21:28:00.897: htsp_process_event: [0/0/2, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

Dec 6 21:28:00.897: fxols_wait_setup_ack:

Dec 6 21:28:00.897: htsp_timer - 6000 msec

Dec 6 21:28:00.897: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_prochtsp_alert_notify

Dec 6 21:28:00.905: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)

Dec 6 21:28:03.981: htsp_timer_stop3

Dec 6 21:28:04.001: htsp_process_event: [0/0/1, FXOLS_OFFHOOK, E_HTSP_RELEASE_REQ]fxols_offhook_release

Dec 6 21:28:04.001: htsp_timer_stop

Dec 6 21:28:04.001: htsp_timer_stop2

Dec 6 21:28:04.001: htsp_timer_stop3

Dec 6 21:28:04.001: [0/0/1] set signal state = 0x4 timestamp = 0

Dec 6 21:28:04.001: htsp_timer - 2000 msec

Dec 6 21:28:04.013: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Dec 6 21:28:04.013: htsp_timer_stop

Dec 6 21:28:04.013: htsp_timer_stop2

Dec 6 21:28:04.945: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_DSP_SIG_0100]fxols_proceed_clear

Dec 6 21:28:04.945: htsp_timer_stop2

Dec 6 21:28:04.945: htsp_timer - 6000 msec

Dec 6 21:28:06.001: htsp_process_event: [0/0/1, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout

Dec 6 21:28:06.001: htsp_process_event: [0/0/1, FXOLS_ONHOOK, E_DSP_SIG_0100]

AES-CME#

Dec 6 21:28:10.945: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_HTSP_EVENT_TIMER]fxols_disc_confirm

Dec 6 21:28:10.945: htsp_timer_stop

Dec 6 21:28:10.945: htsp_timer_stop2

Dec 6 21:28:10.945: htsp_timer_stop3

Dec 6 21:28:10.945: htsp_process_event: [0/0/2, FXOLS_PROCEEDING, E_HTSP_RELEASE_REQ]fxols_offhook_release

Dec 6 21:28:10.945: htsp_timer_stop

Dec 6 21:28:10.945: htsp_timer_stop2

Dec 6 21:28:10.945: htsp_timer_stop3

Dec 6 21:28:10.945: [0/0/2] set signal state = 0x4 timestamp = 0

Dec 6 21:28:10.945: htsp_timer - 2000 msecu all

Dec 6 21:28:12.945: htsp_process_event: [0/0/2, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout

Dec 6 21:28:12.949: htsp_process_event: [0/0/2, FXOLS_ONHOOK, E_DSP_SIG_0100]

paolo bevilacqua · ‎12-06-2012

That seems bad, try updating IOS.