cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
240
Views
5
Helpful
8
Replies

CISCO IOS ROUTER - CALLER ID ISSUE

edwincharles
Beginner
Beginner

Hi,

When we recieve an incoming call, the phone display "unknown number".

It was working before, there has been no changes done in the config.

we have tested the pstn line by using an analog phone, and it displays the caller-id

 

CALL FLOW

PSTN- FXO (2921 router) - CUCM - IP Phones

voice-port 0/0/0
translation-profile incoming out
supervisory disconnect dualtone mid-call
supervisory custom-cptone TAC
no vad
cptone SA
timeouts call-disconnect 1
timeouts wait-release 1
connection plar opx 5555
caller-id enable
caller-id alerting line-reversal
caller-id alerting dsp-pre-allocate
!

debug vpm signal 

 

 

000090: Aug 28 13:26:46.955: %VOICE_IEC-3-GW: C SCRIPTS: Internal Error (Interface busy): IEC=1.1.182.11.26.0 on callID 615 GUID=E9AD7C8000010000000001560BC71BAC
000091: Aug 30 11:56:52.711: htsp_dsp_message: SEND_SIG_STATUS: state=0x0 timestamp=27870 systime=465059865
000092: Aug 30 11:56:52.711: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
000093: Aug 30 11:56:52.711: htsp_timer - 125 msec
000094: Aug 30 11:56:52.839: htsp_process_event: [0/0/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer
000095: Aug 30 11:56:52.839: htsp_timer - 10000 msec
000096: Aug 30 11:56:53.803: htsp_dsp_message: SEND_SIG_STATUS: state=0x4 timestamp=28959 systime=465059974
000097: Aug 30 11:56:53.803: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]
000098: Aug 30 11:56:53.803: fxols_ringing_not
000099: Aug 30 11:56:53.803: htsp_timer_stop
000100: Aug 30 11:56:53.803: htsp_timer_stop3
000101: Aug 30 11:56:53.803: [0/0/0] htsp_stop_caller_id_rx. message length 0
000102: Aug 30 11:56:53.803: htsp_timer3 - 20 msec
000103: Aug 30 11:56:53.803: [0/0/0] htsp_dsm_close_done
000104: Aug 30 11:56:53.823: htsp_process_event: [0/0/0, FXOLS_STOP_CALLERID_DELAY, E_HTSP_EVENT_TIMER3]
000105: Aug 30 11:56:53.823: htsp_timer_stop
000106: Aug 30 11:56:53.823: htsp_timer_stop3 htsp_setup_ind
000107: Aug 30 11:56:53.823: [0/0/0] get_fxo_caller_id:Caller ID receive failed. parseCallerIDString:no data.
000108: Aug 30 11:56:53.823: [0/0/0] get_local_station_id calling num= calling name= calling time=08/30 11:56 orig called=
000109: Aug 30 11:56:53.823: fxols_callerid_done: call being answered
000110: Aug 30 11:56:53.827: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
000111: Aug 30 11:56:53.827: fxols_wait_setup_ack:
000112: Aug 30 11:56:53.827: htsp_timer - 6000 msec
000113: Aug 30 11:56:53.827: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_prochtsp_alert_notify
000114: Aug 30 11:56:53.859: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alert
000115: Aug 30 11:56:53.919: htsp_call_bridged invoked
000116: Aug 30 11:56:53.919: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_connect
000117: Aug 30 11:56:53.919: [0/0/0] set signal state = 0xC timestamp = 0
000118: Aug 30 11:56:53.919: htsp_timer_stop
000119: Aug 30 11:56:53.923: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
000120: Aug 30 11:57:01.007: htsp_digit_ready(0/0/0): digit = 1
000121: Aug 30 11:57:01.407: htsp_digit_ready(0/0/0): digit = 1
000122: Aug 30 11:57:01.887: htsp_digit_ready(0/0/0): digit = 6
000123: Aug 30 11:57:02.287: htsp_digit_ready(0/0/0): digit = 6
000124: Aug 30 11:57:05.823: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
000125: Aug 30 11:57:09.991: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_VOICE_CUT_THROUGH]fxols_connect_proc_voice
000126: Aug 30 11:58:01.479: htsp_timer_stop3
000127: Aug 30 11:58:01.511: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_RELEASE_REQ]fxols_offhook_release
000128: Aug 30 11:58:01.511: htsp_timer_stop
000129: Aug 30 11:58:01.511: htsp_timer_stop2
000130: Aug 30 11:58:01.511: htsp_timer_stop3
000131: Aug 30 11:58:01.511: [0/0/0] set signal state = 0x4 timestamp = 0
000132: Aug 30 11:58:01.511: htsp_timer - 2000 msec
000133: Aug 30 11:58:03.511: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout
000134: Aug 30 11:58:03.511: fxols_dsp_prealloc_clid_wait. Line reversal alerting DSP preallocation done
000135: Aug 30 11:58:03.511: [0/0/0] htsp_start_caller_id_rx:Mode DTMF. Alerting 0xC4
000136: Aug 30 11:58:03.511: htsp_start_caller_id_rx create dsp_stream_manager
000137: Aug 30 11:58:03.511: htsp_dsp_message: RESP_SIG_STATUS: state=0x4 timestamp=0 systime=465066945
000138: Aug 30 11:58:03.511: [0/0/0] htsp_dsm_create_success returns 1
000139: Aug 30 11:58:03.515: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

8 Replies 8

b.winter
VIP Advocate VIP Advocate
VIP Advocate

It would be helpful for the community, if you would state, which issue you have with the caller ID ...
"having issue with caller ID" is not a problem description

edwincharles
Beginner
Beginner

Hi,

When we recieve an incoming call, the phone display "unknown number".

It was working before, there has been no changes done in the config.

we have tested the pstn line by using an analog phone, and it displays the caller-id

 


@edwincharles wrote:

Hi,

When we recieve an incoming call, the phone display "unknown number".

It was working before, there has been no changes done in the config.

we have tested the pstn line by using an analog phone, and it displays the caller-id

 


What do you mean by that? You tested an outgoing call from an analog phone to the PSTN and caller ID was displayed?

If you're not getting caller ID on your inbound calls and you've made no changes, it would be best to raise it with your telephone provider. 

Dmytro Benda
Beginner
Beginner

Hi, read this post please:

https://community.cisco.com/t5/ip-telephony-and-phones/fxo-interface-receive-calling-nuber-fail/td-p/2731202 

Try to configure:
caller-id alerting ring 2

And also check if your cptone setting is correct. I see from your config that it is set for SA (Saudi Arabia). 

My Cisco Unified Communications Blog

Sadav Ansari
VIP Rising star VIP Rising star
VIP Rising star

The first thing to check in FXO port configuration is the cptone setting. Typically Cisco FXO port recognizes normally the Caller ID, if the cptone parameter is set to US

As I can see,  cptone is SA Pls try to change cptone to US.


Pls rate if its "Helpful". If this answered your question pls click "Accept As Solution".

I doubt that it is needed to set it to US. The cptone command does a ton of things, like ring cadence and frequency for example. So setting that to something that does not match the country where the router is deployed is not a great idea.



Response Signature


Hello Roger,

I saw in some cases its worked with change cptone to US, Hopefully it will its just for testing.

edwincharles
Beginner
Beginner

Dears,

Thankyou everyone for the support,

Caller-ID issue has been solved, considering for Saudi STC FXO, please find the current config working for FXO

 

voice-port 0/0/0

translation-profile incoming out

supervisory disconnect dualtone mid-call

supervisory custom-cptone TAC

supervisory dualtone-detect-params 1

cptone SA

timeouts call-disconnect 1

timeouts wait-release 1

connection plar opx 5555

caller-id enable

caller-id alerting ring 2

!

 

Getting Started

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:

Recognize Your Peers