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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

2800 Voice gateway caller ID

I question wether or not Verizon is passing Caller-ID to one

of our phone lines. Can some please tell me the debug command i can use to view the incoming and outgoing phone information?  I thought it was

debug dialer events, but i appear to be wrong

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: 2800 Voice gateway caller ID

If u r using telnet  did u enter terminal mon command to see the debugs in the telnet window ?

Also, is the monitor logg enabled? Enter "logg mon debug" in global config.

If consoled in, make sure you have console logging enabled (logg con deb)

Or use, bufferred logging (logging buffer 2000000 deb)

Just issue clear log to empty logging buffer before placing your test call and once done,

capture show log output in a text file.

12 REPLIES
Cisco Employee

Re: 2800 Voice gateway caller ID

Sounds like its an analog line connected to FXO port on the GW ?

If that's the case, you want to run deb vpm signal.

For ISDN/PRI, run deb isdn q931

For SIP connex, run deb ccsip mess

HTH.

Cisco Employee

Re: 2800 Voice gateway caller ID

debug isdn Q931 or debug voip ccapi inout will give you that info.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: 2800 Voice gateway caller ID

deleted this info

New Member

Re: 2800 Voice gateway caller ID

deleted info

New Member

Re: 2800 Voice gateway caller ID

Here is more information...

show call active tells me that the original calling number and the calling name are blank

CallingNumber=

OriginalCallingNumber=

Cisco Employee

Re: 2800 Voice gateway caller ID

can u pl. capture  debug vpm signal   for one call where CLID fails ?

New Member

Re: 2800 Voice gateway caller ID

I can not get this command to  produce any output.

Cisco Employee

Re: 2800 Voice gateway caller ID

If u r using telnet  did u enter terminal mon command to see the debugs in the telnet window ?

Also, is the monitor logg enabled? Enter "logg mon debug" in global config.

If consoled in, make sure you have console logging enabled (logg con deb)

Or use, bufferred logging (logging buffer 2000000 deb)

Just issue clear log to empty logging buffer before placing your test call and once done,

capture show log output in a text file.

New Member

Re: 2800 Voice gateway caller ID

looks like i forgot some basics here. I was forgetting the command term mon. Everything else was done....

Anyways, here is what we got..


009175: Oct 12 13:48:14.025 edt: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing
009176: Oct 12 13:48:14.025 edt: htsp_timer - 125 msec
009177: Oct 12 13:48:14.153 edt: htsp_process_event: [0/0/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wai
t_ring_min_timer
009178: Oct 12 13:48:14.153 edt: htsp_timer - 10000 msec
009179: Oct 12 13:48:14.153 edt: htsp_timer3 - 5600 msec
009180: Oct 12 13:48:14.153 edt: [0/0/0] htsp_start_caller_id_rx:BELLCORE
009181: Oct 12 13:48:14.153 edt: [0/0/0] htsp_d
MAINT-RTR01#sm_create_success  returns 1
009182: Oct 12 13:48:14.937 edt: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]
009183: Oct 12 13:48:14.937 edt: fxols_ringing_not
009184: Oct 12 13:48:14.937 edt: htsp_timer_stop
009185: Oct 12 13:48:14.937 edt: htsp_timer - 10000 msec
MAINT-RTR01#
009186: Oct 12 13:48:18.816 edt: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0000]
009187: Oct 12 13:48:19.752 edt: htsp_process_event: [0/0/0, FXOLS_RINGING, E_HTSP_EVENT_TIMER3]fxols_snoop_cl
id_stop
009188: Oct 12 13:48:19.752 edt: htsp_timer_stop3
MAINT-RTR01#
009189: Oct 12 13:48:20.936 edt: htsp_process_event: [0/0/0, FXOLS_RINGING, E_DSP_SIG_0100]
009190: Oct 12 13:48:20.936 edt: fxols_ringing_not
009191: Oct 12 13:48:20.936 edt: htsp_timer_stop
009192: Oct 12 13:48:20.936 edt: htsp_timer_stop3
009193: Oct 12 13:48:20.936 edt: [0/0/0] htsp_stop_caller_id_rx. message length 0htsp_setup_ind
009194: Oct 12 13:48:20.936 edt: [0/0/0] get_fxo_caller_id:Caller ID receive failed.  parseCallerIDString:no d
ata.
009195: Oct 12 13:48:20.936 edt: [0/0/0] get_local_station_id calling num= calling name= calling time=10/12 13
:48  orig called=
MAINT-RTR01#
009196: Oct 12 13:48:20.940 edt: htsp_process_event: [0/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
009197: Oct 12 13:48:20.940 edt: fxols_wait_setup_ack:
009198: Oct 12 13:48:20.940 edt: [0/0/0] set signal state = 0xC timestamp = 0fxols_check_auto_call
009199: Oct 12 13:48:20.948 edt: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook
_proc
009200: Oct 12 13:48:20.948 edt: htsp_timer - 120000 msec
009201: Oct 12 13:48:20.948 edt: [0/0/0] htsp_dsm_close_donehtsp_alert_notify
009202: Oct 12 13:48:20.980 edt: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_aler
thtsp_call_service_msghtsp_call_service_msg not EFXS (2)
MAINT-RTR01#htsp_call_service_msghtsp_call_service_msg not EFXS (2)
009203: Oct 12 13:48:37.837 edt: htsp_call_bridged invokedhtsp_call_service_msghtsp_call_service_msg not EFXS
(2)
009204: Oct 12 13:48:37.841 edt: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_VOICE_CUT_THROUGH]fxols_
proc_voice
009205: Oct 12 13:48:37.845 edt: htsp_process_event: [0/0/0, FXOLS_PROCEEDING, E_HTSP_CONNECT]fxols_offhook_co
nnect
009206: Oct 12 13:48:37.845 edt: htsp_timer_stop
MAINT-RTR01#
009207: Oct 12 13:48:42.076 edt: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_DSP_SIG_1100]fxols_offhook_disc
009208: Oct 12 13:48:42.076 edt: htsp_timer2 - 350 msec
009209: Oct 12 13:48:42.428 edt: htsp_process_event: [0/0/0, FXOLS_CONNECT, E_HTSP_EVENT_TIMER2]fxols_disc_con
firm
009210: Oct 12 13:48:42.428 edt: htsp_timer_stop
009211: Oct 12 13:48:42.428 edt: htsp_timer_stop2
009212: Oct 12 13:48:42.428 edt: htsp_timer_stop3
009213: Oct 12 13:48:42.428 edt: htsp_timer_stop3
009214: Oct 12 13:48:42.444 edt: htsp_process_event: [0/0/0, FXOLS_REMOTE_RELEASE, E_HTSP_RELEASE_REQ]fxols_of
fhook_release
009215: Oct 12 13:48:42.444 edt: htsp_timer_stop
MAINT-RTR01#
009216: Oct 12 13:48:42.444 edt: htsp_timer_stop2
009217: Oct 12 13:48:42.444 edt: htsp_timer_stop3
009218: Oct 12 13:48:42.444 edt: [0/0/0] set signal state = 0x4 timestamp = 0
009219: Oct 12 13:48:42.444 edt: htsp_timer - 2000 msec
MAINT-RTR01#
009220: Oct 12 13:48:44.443 edt: htsp_process_event: [0/0/0, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_o
ut_timeout
009221: Oct 12 13:48:44.443 edt: htsp_process_event: [0/0/0, FXOLS_ONHOOK, E_DSP_SIG_0100]

Cisco Employee

Re: 2800 Voice gateway caller ID

Nops, don't see telco delivering any CLID name or number on line connected to 0/0/0:

GW DSP gets reday to rec. called ID:

009180: Oct 12 13:48:14.153 edt: [0/0/0] htsp_start_caller_id_rx:BELLCORE


couple rings / 6 secs later.....

009193: Oct 12 13:48:20.936 edt: [0/0/0] htsp_stop_caller_id_rx. message length 0
009194: Oct 12 13:48:20.936 edt: [0/0/0] get_fxo_caller_id:Caller ID receive failed.  parseCallerIDString:no data.
009195: Oct 12 13:48:20.936 edt: [0/0/0] get_local_station_id calling num= calling name= calling time=10/12 13

New Member

Re: 2800 Voice gateway caller ID

So what does the BELLCORE mean at the end?  Thank you all very much for the help and i will rate.

Cisco Employee

Re: 2800 Voice gateway caller ID

You are welcome.

Bellcore/Telcordia is the default  and most common standard we use for Caller ID reception/transmission.

589
Views
0
Helpful
12
Replies