LD caller ID issue - CME with FXO

[jtwardowski]

After initial troubleshooting i noticed issue with caller_id on ingress FXO port.

System is running std configuration, port info here:

callagent#show voice port 2/0/0

Foreign Exchange Office 2/0/0 Slot is 2, Sub-unit is 0, Port is 0
Type of VoicePort is FXO
Operation State is DORMANT
Administrative State is UP
The Last Interface Down Failure Cause is Administrative Shutdown
Description is not set
Noise Regeneration is enabled
Non Linear Processing is enabled
Non Linear Mute is disabled
Non Linear Threshold is -21 dB
Music On Hold Threshold is Set to -38 dBm
In Gain is Set to 0 dB
Out Attenuation is Set to 3 dB
Echo Cancellation is enabled
Echo Cancellation NLP mute is disabled
Echo Cancellation NLP threshold is -21 dB
Echo Cancel Coverage is set to 64 ms
Echo Cancel worst case ERL is set to 6 dB
Playout-delay Mode is set to adaptive
Playout-delay Nominal is set to 60 ms
Playout-delay Maximum is set to 1000 ms
Playout-delay Minimum mode is set to default, value 40 ms
Playout-delay Fax is set to 300 ms
Connection Mode is plar opx
Connection Number is 800
Initial Time Out is set to 10 s
Interdigit Time Out is set to 10 s
Call Disconnect Time Out is set to 5 s
Ringing Time Out is set to 180 s
Wait Release Time Out is set to 5 s
Companding Type is u-law
Region Tone is set for CA

Analog Info Follows:
Currently processing none
Maintenance Mode Set to None (not in mtc mode)
Number of signaling protocol errors are 0
Impedance is set to 600r Ohm
Station name None, Station number None

Caller ID Info Follows:
Standard BELLCORE
Caller ID is received after 1 ring(s)
Translation profile (Incoming):
Translation profile (Outgoing):

Voice card specific Info Follows:
Signal Type is loopStart
Battery-Reversal is enabled
Number Of Rings is set to 1
Supervisory Disconnect is signal
Answer Supervision is inactive
Hook Status is On Hook
Ring Detect Status is inactive
Ring Ground Status is inactive
Tip Ground Status is inactive
Dial Out Type is dtmf
Digit Duration Timing is set to 100 ms
InterDigit Duration Timing is set to 500 ms
Pulse Rate Timing is set to 10 pulses/second
InterDigit Pulse Duration Timing is set to 750 ms
Percent Break of Pulse is 60 percent
GuardOut timer is 400 ms
Minimum ring duration timer is 125 ms
Hookflash-in Timing is set to 600 ms
Hookflash-out Timing is set to 400 ms
Supervisory Disconnect Timing (loopStart only) is set to 350 ms
OPX Ring Wait Timing is set to 6000 ms

Debug for local calls shows called_id coming thru:

Dec  9 11:40:31.505 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc

Dec  9 11:40:31.505 EST: [2/0/0] htsp_dsm_close_donehtsp_setup_req

Dec  9 11:40:31.505 EST: htsp_process_event: [50/0/11.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup

Dec  9 11:40:31.505 EST: htsp_ephone_start_caller_id_tx calling num=6138186442 calling name = called num=800 orig called num=

Dec  9 11:40:31.509 EST: [50/0/11.1] set signal state = 0x0 timestamp = 0

Dec  9 11:40:31.509 EST: efxs_onhook_setup: local target is available

htsp_alerthtsp_alert_notify

Dec  9 11:40:31.513 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alert

Dec  9 11:40:33.985 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_EVENT_TIMER3]

Dec  9 11:40:34.253 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Dec  9 11:40:31.505 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc
Dec  9 11:40:31.505 EST: [2/0/0] htsp_dsm_close_donehtsp_setup_req
Dec  9 11:40:31.505 EST: htsp_process_event: [50/0/11.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
Dec  9 11:40:31.505 EST: htsp_ephone_start_caller_id_tx calling num=6138180559 calling name = called num=800 orig called num=
Dec  9 11:40:31.509 EST: [50/0/11.1] set signal state = 0x0 timestamp = 0
Dec  9 11:40:31.509 EST: efxs_onhook_setup: local target is available
htsp_alerthtsp_alert_notify
Dec  9 11:40:31.513 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alert
Dec  9 11:40:33.985 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_EVENT_TIMER3]
Dec  9 11:40:34.253 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

Debug for LD shows “failed”:

Dec  9 11:39:32.138 EST: htsp_timer_stop
Dec  9 11:39:32.138 EST: htsp_timer_stop3
Dec  9 11:39:32.138 EST: [2/0/0] htsp_stop_caller_id_rx. message length 0htsp_setup_ind
Dec  9 11:39:32.138 EST: [2/0/0] get_fxo_caller_id:Caller ID receive failed.  parseCallerIDString:no data.
Dec  9 11:39:32.138 EST: [2/0/0] get_local_station_id calling num= calling name= calling time=12/09 11:39  orig called=
Dec  9 11:39:32.138 EST: htsp_process_event: [2/0/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]
Dec  9 11:39:32.142 EST: fxols_wait_setup_ack:
Dec  9 11:39:32.142 EST: htsp_timer - 6000 msec
Dec  9 11:39:32.142 EST: htsp_timer_stop3
Dec  9 11:39:32.146 EST: htsp_process_event: [2/0/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc
Dec  9 11:39:32.146 EST: [2/0/0] htsp_dsm_close_donehtsp_setup_req
Dec  9 11:39:32.146 EST: htsp_process_event: [50/0/11.1, EFXS_ONHOOK, E_HTSP_SETUP_REQ]efxs_onhook_setup
Dec  9 11:39:32.146 EST: htsp_ephone_start_caller_id_tx calling num= calling name = called num=800 orig called num=
Dec  9 11:39:32.146 EST: [50/0/11.1] set signal state = 0x0 timestamp = 0
Dec  9 11:39:32.146 EST: efxs_onhook_setup: local target is available

When connecting reg analog phone, we can see caller ID on local and LD calls.

We try diff cptone (US and CA), set caller_id after 2^nd ring and dsp-preallocation on caller_id.

No luck..

Any suggestions what else can be check/done?

[jtwardowski]

changes suggested above allows to see LD Caller ID now, thanks!

few caveats:

- on local incoming calls, phone doesn't ring until 5th ring at calling phone.

- on LD calls, phone rings after 3 rings at calling phone

- disconnect issues: line is not dropped if calling party disconnect after 5-6 (1-2 on called phone) ring.

More on the original settings:

ingress line is FXS (voip over cable internet)

CME will go away as primary system, CUCM (BE) will take over. CME will remain as SRST only.

Cust will also use SIP trunk.

question:

how to adjust rings? std 1 ring delay is OK, 4 rings delay is quite hard to explain to cust. from calling party perspective if there's no answer after 2-3 rings most likely nobody will answer. Waiting for 6-7 rings is unusual.

Happy New Year:-)

[Jeremy Combs · Accepted solution]

The router is waiting for the carrier to provide the Caller ID information before it is going to pass that call on to CME. Your configuration is set to wait for up to 5 rings and for whatever reason your provider is taking up to 5 rings for that information to get delivered on your LD calls which is why it is taking so long. That is unacceptable and not your fault. I'd open a case with the carrier and have them fix the issue. With your debugs and timer set to 5 rings you should be able to clearly show it's taking 5 rings. If its in the US I'm sure the FCC has guidelines saying 5 rings is unacceptable. Don't let the carrier bully you.

Sent from Cisco Technical Support iPad App

[jtwardowski]

test on std analog phone connected directly to FXS shows LD caller ID after 2nd ring. I'm not sure if i can chaise telco..

What about bug CSCse71319  ?

Why there's so extensive delay on local calls (4 rings on calling phone before called ID is ringing)?

LD calls are way better - 2 rings on calling phone before called ID start ringing

Regards

[Jorge Armijo · Accepted solution]

Hi,

The delay is caused by the caller-id alerting ring 4, it will wait 4 rings to receive the caller ID and then it will pass the call, not before that time. So if each ring takes about 1 sec, so you'll have 4 sec delay to hear the phone ringing.

--
Jorge Armijo

Please remember to rate helpful responses and identify helpful or correct answers.

[paolo bevilacqua · Accepted solution]

That is "FXO Delayed Caller ID Delivery'

http://www.cisco.com/en/US/docs/ios/12_4/12_4x/release/notes/rn3800xw.html#wp369137

Alo, you can try ring 3, or that "debug vpm sinal" to see exactly when calle-ID is received on both types of calls.

If you don't have support for it in your image, try 12.4(15)T14.

[Jorge Armijo]

Hey jtwardowski,

Please remember to rate helpful posts and mark correct answers!

--
Jorge Armijo

Please remember to rate helpful responses and identify helpful or correct answers.

[jtwardowski]

Finally I was able to create pressure on provider -  the issue is related to "long distance distinctive ring mode" that have impact on caller id presentation. They don't really know why it's happening. work around - disable distinctive ring for incoming LD.

Thanks to all of you for assistance and support and Happy New Year!