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

caller-id on VIC2-2FXO: can't tell whether it's working or not

Hi there, is there any missing command here below?

voice-port 2/1

cptone BR

connection plar 5000

caller-id enable

!

voice class h323 1

h225 timeout tcp establish 5

telephony-service ccm-compatible

!

dial-peer voice 5 voip

description to CM-IPT, attendant

destination-pattern 5000

voice-class h323 1

session target ipv4:192.168.3.10

The DN 5000 is a pilot point number, redirecting to a single attendant, who was supposed to identify the external calling party before forwarding to another IP phone.

The service provider guaranteed the DTMF signal (used in BR) is being supplied to this interface. A detail I noticed is the output of "debug voip ccapi inout" command:

*Nov 29 02:33:33.645: //-1/5EE20AF980F3/CCAPI/cc_api_display_ie_subfields:

cc_api_call_setup_ind_common:

cisco-username=

----- ccCallInfo IE subfields -----

cisco-ani=

cisco-anitype=0

cisco-aniplan=0

cisco-anipi=0

cisco-anisi=0

dest=5000

cisco-desttype=0

cisco-destplan=0

cisco-rdie=FFFFFFFF

cisco-rdn=

cisco-rdntype=0

cisco-rdnplan=0

cisco-rdnpi=0

cisco-rdnsi=0

cisco-redirectreason=0

I once came to a conclusion that I was not receiving clid info by observing the "cisco-ani=" field, which is blank, differently from the situation when I receive the calling info correctly.

Can anyone guess what could be the error?

Thanks in advance

5 REPLIES
Silver

Re: caller-id on VIC2-2FXO: can't tell whether it's working or n

Sometimes the caller-id is provided after the first ring, sometimes after the second ring.

Trying using these commands one by one to see what applies to your setup.

caller-id alerting ring 1

caller-id alerting ring 2

It might be a good idea to do a shut/no shut on the ports after you apply these commands.

A quick test would be to plug a regular phone with Caller-ID display to that line and check out when the caller-id gets displayed and apply the commands accordingly.

Regards,

Anup

New Member

Re: caller-id on VIC2-2FXO: can't tell whether it's working or n

tks Anup for your insight

i've tried every combination possible for a voice port, except attenuation, which has been removed from cli

the person who was in charge of CO informed the calling number info was being passed during the 1st ring, and he also claimed he checked with a phone device equipped with identification display

would it be sth very particular to Brazil's CO's?

Hall of Fame Super Gold

Re: caller-id on VIC2-2FXO: can't tell whether it's working or n

haep,

I do noy have information to positively confirm that Brazil BINA standard is supported.

On the other hand, if you have it working somewhere else, same BINA standard, something must be wrong on the telco side.

New Member

Re: caller-id on VIC2-2FXO: can't tell whether it's working or n

tks 4 your response.

indeed, i'm dealing with Brazil CO.

could you be more specific, you're saying that brazil BINA could possibly not work with router's fxo port, in any configuration?

the debug vpm signal returned the following msg:

*Mar 17 03:06:06.460: [1/0] htsp_dsm_feature_notify_cb returns 2 id=DSM_FEATURE

_SM_CALLERID_RX

*Mar 17 03:06:06.460: htsp_process_event: [1/0, FXOLS_ONHOOK, E_HTSP_CALLERID_RX

_DONE]

*Mar 17 03:06:10.448: htsp_process_event: [1/0, FXOLS_ONHOOK, E_DSP_SIG_0000]fxo

ls_onhook_ringing

*Mar 17 03:06:10.448: htsp_timer - 125 msec

*Mar 17 03:06:10.576: htsp_process_event: [1/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVEN

T_TIMER]fxols_wait_ring_min_timer

*Mar 17 03:06:10.576: htsp_timer - 10000 msec

*Mar 17 03:06:11.496: htsp_process_event: [1/0, FXOLS_RINGING, E_DSP_SIG_0100]

*Mar 17 03:06:11.496: fxols_ringing_not

*Mar 17 03:06:11.496: htsp_timer_stop

*Mar 17 03:06:11.496: htsp_timer - 10000 msec

*Mar 17 03:06:15.436: htsp_process_event: [1/0, FXOLS_RINGING, E_DSP_SIG_0000]

*Mar 17 03:06:16.480: htsp_process_event: [1/0, FXOLS_RINGING, E_DSP_SIG_0100]

*Mar 17 03:06:16.480: fxols_ringing_not

*Mar 17 03:06:16.480: htsp_timer_stop

*Mar 17 03:06:16.480: htsp_timer_stop3

*Mar 17 03:06:16.480: [1/0] htsp_stop_caller_id_rx. message length 0htsp_setup_i

nd

*Mar 17 03:06:16.484: [1/0] get_fxo_caller_id:Caller ID receive failed. parseCa

llerIDString:no data.

*Mar 17 03:06:16.484: [1/0] get_local_station_id calling num= calling name= call

ing time=03/17 03:06 orig called=

*Mar 17 03:06:16.496: htsp_process_event: [1/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SET

UP_ACK]

*Mar 17 03:06:16.496: fxols_wait_setup_ack:

*Mar 17 03:06:16.496: [1/0] set signal state = 0xC timestamp = 0fxols_check_auto

_call

*Mar 17 03:06:16.516: htsp_process_event: [1/0, FXOLS_PROCEEDING, E_HTSP_PROCEED

ING]fxols_offhook_proc

*Mar 17 03:06:16.516: htsp_timer - 120000 msec

*Mar 17 03:06:16.520: [1/0] htsp_dsm_close_done

*Mar 17 03:06:16.772: htsp_process_event: [1/0, FXOLS_PROCEEDING, E_DSP_SIG_0110

]fxols_rvs_battery

observing this output it seems that telco side is not sending the clid info, however, as i mentioned before, they already checked it out with a regular phone device, that's why i try to find sth in the router itself.

regards,

Gold

Re: caller-id on VIC2-2FXO: can't tell whether it's working or n

ani=0 means CLID is not being received with the setup. So, you might want to check with your Telco is they are sending it

256
Views
5
Helpful
5
Replies