Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

again caller id problem

hi

can someone help me with this, i have a caller id problem on my FXO ports

debug vpm shows:

get_fxo_caller_id:Caller ID receive failed. parseCallerIDString:checksum mismatch.

i tried to find what's this checksum mismatch related to and caused by but no luck

please can u help

here is some output of debug command:

*Sep 16 10:32:08.248: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

*Sep 16 10:32:08.248: TGRM: reg_invoke_tgrm_call_update(0, 0, 0, 65535, 1, TGRM_CALL_PENDING, TGRM_CALL_VOICE, TGRM_DIRECTION_IN)

*Sep 16 10:32:08.248: htsp_timer - 125 msec

*Sep 16 10:32:08.376: htsp_process_event: [0/0/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

*Sep 16 10:32:08.376: htsp_timer - 10000 msec

*Sep 16 10:32:08.376: htsp_timer3 - 5600 msec

*Sep 16 10:32:08.376: [0/0/0] htsp_start_caller_id_rx:BELLCORE

*Sep 16 10:32:08.376: [0/0/0] htsp_dsm_create_success returns 1

*Sep 16 10:32:09.340: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]

*Sep 16 10:32:09.340: fxols_ringing_not

*Sep 16 10:32:09.340: htsp_timer_stop

*Sep 16 10:32:09.340: htsp_timer - 10000 msec

*Sep 16 10:32:10.556: [0/0/0] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE_SM_CALLERID_RX

*Sep 16 10:32:10.556: htsp_process_event: [0/0/0, FXOLS_RINGING, E_HTSP_CALLERID_RX_DONE]

*Sep 16 10:32:10.556: htsp_timer_stop

*Sep 16 10:32:10.556: [0/0/0] htsp_stop_caller_id_rx. message length 25htsp_setup_ind

*Sep 16 10:32:10.556: [0/0/0] get_fxo_caller_id:Caller ID receive failed. parseCallerIDString:checksum mismatch.

*Sep 16 10:32:10.556: [0/0/0] Caller ID String 80 18 01 08 30 39 31 36 31 34 33 33 02 0A 30 35 30 34 39 31 30 37 34 37 07 00 00

*Sep 16 10:32:10.556: [0/0/0] get_local_station_id calling num= calling name= calling time=09/16 10:32 orig called=

*Sep 16 10:32:10.560: TGRM: reg_invoke_tgrm_accept_call(1, TGRM_CALL_VOICE, TGRM_DIRECTION_IN, 0, 0, 0, 65535)

*Sep 16 10:32:10.560: TGRM: Calling vtsp_tsp_call_setup_ind().

*Sep 16 10:32:10.560: fxols_callerid_done: call being answered

*Sep 16 10:32:10.560: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

here some sh run of related configuration:

trunk group FXO

hunt-scheme round-robin

voice-port 0/0/0

trunk-group FXO

supervisory disconnect dualtone mid-call

connection plar opx 200

caller-id enable

!

voice-port 0/0/1

trunk-group FXO

supervisory disconnect dualtone mid-call

connection plar opx 200

caller-id enable

!

voice-port 0/0/2

trunk-group FXO

supervisory disconnect dualtone mid-call

connection plar opx 200

caller-id enable

please help

thanks

3 REPLIES
Silver

Re: again caller id problem

Receiving caller ID in FXO ports is not supported in MGCP gateways but only in H323 gateways. If you want to receive caller ID in your gateway using FXO ports, you must configure your router as H.323 gateway. Currently, only PRIs and FXS ports support caller ID on MGCP gateways.

New Member

Re: again caller id problem

Hi,

I have the same problem with a single 2851 router using CME 7.0. I have a EVM-HD-8FXS with 2 -6FXO cards and another 2 FXO HWIC.

A part of config:

voice-port 2/0/8

connection plar opx 100

caller-id enable

!

voice-port 2/0/9

connection plar opx 100

caller-id enable

!

voice-port 2/0/10

connection plar opx 100

caller-id enable

!

voice-port 2/0/11

connection plar opx 100

caller-id enable

The debug vpm signal shows the exact error message.

What could be wrong?

New Member

Re: again caller id problem

You have subscribe Caller ID service from your PSTN provider.Some providers will charge for this service.

HTH

Please rate useful comments.

Tom

291
Views
0
Helpful
3
Replies