cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
942
Views
0
Helpful
7
Replies

caller-id command not under dial peer

Hi, I'm trying to configure caller id on a 2610, H232 gateway and the command is not under the dial peer. The IOS is 12.2.(15)T13. It is connected to the PSTN via an FXO port and I'm trying to get the caller ID, from the PSTN, on the 7960 phones. CM ver is 4.1.3. How can I enable caller ID to come through? Thanks.

7 Replies 7

Michael Owuor
Cisco Employee
Cisco Employee

Hello,

Could you confirm that the FXO card is one that supports caller-id? Specifically verify that it is one of these:

VIC-2FXO-M1, VIC-2FXO-M2, VIC-4FXO-M1, VIC2-2FXO, VIC2-4FXO

Regards,

/Mao.

Yes, this is a VIC-2FXO card.

Hi Anthony,

The VIC-2FXO card does not support inbound caller-id from the PSTN. You would need to use one of these cards for caller-id to work:

VIC-2FXO-M1, VIC-2FXO-M2, VIC-4FXO-M1, VIC2-2FXO, VIC2-4FXO, or MRP3-8FXOM1

See also:

http://www.cisco.com/en/US/products/hw/routers/ps274/products_tech_note09186a00800b53c7.shtml#features

Regards,

/mao

CSCO11098440
Level 1
Level 1

Before you attempt, please check these commands whether there is or not:

• caller-id enable-Enables and disables Caller ID. Default is Caller ID disabled. This enables or disables the transmission of Caller ID on an FXS port and enables or disables reception of Caller ID on an FXO port.

• [no] caller-id block-Blocks or unblocks Caller ID. The default is Caller ID unblocked. This command blocks or unblocks the Caller ID of all calls that originate from this port. This command is available only on FXS voice ports.

For Example:

interface ethernet 0/1

ip address 10.10.1.1 255.255.255.0

!

voice-port 1/1/0

caller-id enable

!--- Enables Caller ID feature.

!

dial-peer voice 100 pots

destination-pattern 9913050

port 1/1/0

You can turn on several debugs in order to troubleshoot the Caller ID feature on the routers. The voice port module (VPM) signaling debugs (debug vpm signal) track the debugs with the Caller ID feature turned on.

The output for the debug is like that:

Debugs for an FXO Port Receiving Caller ID Correctly

Nov 20 10:40:15.861 EST: [1/0/0] htsp_start_caller_id_rx

Nov 20 10:40:15.861 EST: [1/0/0] htsp_set_caller_id_rx:BELLCORE

Nov 20 10:40:15.861 EST: htsp_timer - 10000 msec

Nov 20 10:40:17.757 EST: [1/0/0, FXOLS_RINGING, E_DSP_SIG_0100]

Nov 20 10:40:17.757 EST: fxols_ringing_not

Nov 20 10:40:17.761 EST: htsp_timer_stop

Nov 20 10:40:17.761 EST: htsp_timer - 10000 msec

Nov 20 10:40:18.925 EST: [1/0/0] htsp_stop_caller_id_rx

Nov 20 10:40:21.857 EST: [1/0/0, FXOLS_RINGING, E_DSP_SIG_0000]

Nov 20 10:40:23.857 EST: [1/0/0, FXOLS_RINGING, E_DSP_SIG_0100]

Nov 20 10:40:23.857 EST: fxols_ringing_not

Nov 20 10:40:23.861 EST: htsp_timer_stop htsp_setup_ind

Nov 20 10:40:23.861 EST: [1/0/0] get_fxo_caller_id:Caller ID received.

Message type=128 length=31 checksum=74

Nov 20 10:40:23.861 EST: [1/0/0] Caller ID String 80 1C

01 08 31 31 32 30 31 35 34 30 02 07 35 35 35 31 32 31 32

07 07 4F 7574 73 69 64 65 74

Nov 20 10:40:23.865 EST: [1/0/0] get_fxo_caller_id

calling num=5551212 calling name=Outside calling time=11/20 15:40

Nov 20 10:40:23.869 EST: [1/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

Nov 20 10:40:23.873 EST: fxols_wait_setup_ack:

Nov 20 10:40:23.873 EST: [1/0/0] set signal state = 0xC timestamp = 0

Nov 20 10:40:23.985 EST: [1/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0100]

fxols_proceed_clear

Nov 20 10:40:23.985 EST: htsp_timer_stop2

Nov 20 10:40:24.097 EST: [1/0/0, FXOLS_PROCEEDING,E_DSP_SIG_0110]

fxols_rvs_battery

Nov 20 10:40:24.097 EST: htsp_timer_stop2

Nov 20 10:40:24.733 EST: [1/0/0, FXOLS_PROCEED_RVS_BT,E_HTSP_PROCEEDING]

fxols_offhook_proc

Nov 20 10:40:24.733 EST: htsp_timer - 120000 msec

Nov 20 10:40:24.745 EST: [1/0/0, FXOLS_PROCEED_RVS_BT,E_HTSP_VOICE_CUT_THROUGH]

fxols_proc_voice

If you can observe the lines that begins with "Nov 20 10:40:23.865 EST: [1/0/0] get_fxo_caller_id

calling num=5551212 calling name=Outside calling time=11/20 15:40"

fom the output, you gather the caller-id information from the PSTN to the router. But if not, you can assign fix caller-id, I don't know it is ok for you ?

Regards,

Ahmet Can KETEN

Thanks for your response. There is no caller-id command under the voice port or the dial peer. There is only a "carrier-id" under the dial peer. Below is the output from the debug on the VPM. What else can I do?

*Mar 1 04:05:11.787: htsp_timer_stop htsp_setup_ind

*Mar 1 04:05:11.787: [1/0/1] get_local_station_id calling num= calling name= calling time=00/00 00:00

Here are the digits I entered during the menu:

*Mar 1 04:05:24.496: htsp_digit_ready(1/0/1): digit = 2

*Mar 1 04:05:39.292: htsp_digit_ready(1/0/1): digit = 3

Hello My Friend,

To check whether the caller_id enable or not you should control the related voice port that is connected to the PSTN line. I mean, write caller-id enable command either under the config mode OR if it doesn't work write it to the under voice-port (FXO);

Router(config)# caller-id enable

Like this. Then get debug output again. Please inform me whether your problem continues or not ? By the way, does assigning fix caller-id number to your FXO port help to you ? If it helps, you can use the command under the related voice port:

Router(config-voiceport)# station-id number number

Regards,

Ahmet Can KETEN

The caller-id command is not available under the voice port nor the dial peer nor in enable mode. I tried the "fix caller-id" command and it doesn't take anywhere. I get the 'invalid input detected' error whenever I try to add any of these commands anywhere.

I haven't tried the station-id command yet; what exactly does it do?

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: