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. And see here for current known issues.

New Member

Cisco 3800 FXO ports with caller-id issue.

Hi all,

I have a customer who is facing caller-id issue in the fxo port. Call flow as follow, PSTN---> FXO---->H323---->CUCM. Customer located in saudi arabia(where caller id standard is ETSI-DTMF).

I have tried to configure the voice port as below,

voice-port 0/1/2

supervisory disconnect dualtone mid-call

input gain 3

no comfort-noise

cptone BE

timeouts initial 0

timeouts interdigit 5

timeouts call-disconnect 1

timeouts ringing 5

timeouts wait-release 1

connection plar opx 5XXXX

impedance complex2

caller-id alerting line-reversal

We have tested the provider line connecting directy to display analog phone , where i can get the caller-id in first ring.  Then we did some debugs and found that i don't see any data in the caller-id field(Debugs attached).

I have checked the bug tool kit, where i don't see any bugs related to the IOS version (Version details attached). Under the voice port only i can configure one of these commands, not all of them.

caller-id alerting line-reversal or caller-id alerting dsp-alloc or caller-id alerting ring 2.

Any feedback regarding the issue would be appreciated.

Regards

Kajen

Everyone's tags (5)
1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

The AA script should be receiving the calling number already, and is not a codec issue.

You may need to take more debugs about.

Please remember to rate useful posts clicking on the stars below

10 REPLIES
Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

Try resetting input gain to default, or lower.

Also try updating IOS.

If still not working, contact the TAC.

New Member

Cisco 3800 FXO ports with caller-id issue.

Thanks for the reply Paolo.

I tried to upgrade the IOS of the gateway and configure the voice port with "caller-id alerting dsp-pre-alloc".. After that caller ID started to work for direct IP phones. But i wanted to route this FXO port through the Auto attendant DN(Unfortunately am not able to get the caller-id through the auto attendant".

I know it is some kind of codec mismatch. But customer has configured the auto attendant in the router it self as a "application with script". How do we configure the codec for this and make the caller-id work?

expecting your kind response.

regards

Kajen

Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

The AA script should be receiving the calling number already, and is not a codec issue.

You may need to take more debugs about.

Please remember to rate useful posts clicking on the stars below

New Member

Cisco 3800 FXO ports with caller-id issue.

By the way , below error am facing when i debug the call which directed to auto attendant..

htsp_process_event: [0/1/2, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

Regards

Kajen

New Member

Cisco 3800 FXO ports with caller-id issue.

Now the issue is little bit different. When i configure the voice port to reach aa-pilot , i can only hear some tone(not the aa message). I can see the called id received in fxo port but audio prompt not playing.

But when i configure voice port with "connection plar opx XXXXX(IP phone DN)" , i can get the caller id(main issue sorted out).

But how will i make my aa works with caller id??

Appreciate your input

Regards

Kajen

Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

As mentioned before, caller ID works normally with AA.

To debug AA (which AA ?, there is to check config, look debugs, etc. You can seearch forum there are many threads about.

Thank you for the nice rating and good luck!

New Member

Cisco 3800 FXO ports with caller-id issue.

I have been troubleshooting this issue for a long time now. and whenever i configure the caller-id alerting to dsp, am getting the same error with "not EFXS 2"...

Find the configuration for application and voice-port below. Debug vpm signal for this configuration also attached.

application

  service autoatt flash:its-CISCO.2.0.3.0.tcl

  paramspace english language en

  paramspace english index 1

  param operator 59301

  paramspace english location flash:

  paramspace english prefix en

  param aa-pilot 59999

voice-port 1/1/2

supervisory disconnect dualtone mid-call

no battery-reversal

no vad

cptone BE

timeouts call-disconnect 1

timeouts wait-release 2

connection plar opx 59999

impedance complex2

caller-id alerting dsp-pre-allocate

AlfozanVGW1(config-voiceport)#do debug vpm signal

Voice Port Module signaling debugging is enabled

AlfozanVGW1(config-voiceport)#

*Aug 13 17:23:17.733: %ENVMON-4-FAN_LOW_RPM: Fan 1 service recommended

*Aug 13 17:23:21.445: [1/1/2] htsp_dsm_feature_notify_cb  returns 2 id=DSM_FEATURE_SM_CALLERID_RX

*Aug 13 17:23:21.445: htsp_process_event: [1/1/2, FXOLS_ONHOOK, E_HTSP_CALLERID_RX_DONE]

*Aug 13 17:23:21.445: [1/1/2] htsp_stop_caller_id_rx. message length 11

*Aug 13 17:23:21.445: [1/1/2] htsp_dsm_close_done

*Aug 13 17:23:21.637: htsp_process_event: [1/1/2, FXOLS_ONHOOK, E_DSP_SIG_0000]fxols_onhook_ringing

*Aug 13 17:23:21.637: htsp_timer - 125 msec

*Aug 13 17:23:21.765: htsp_process_event: [1/1/2, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

*Aug 13 17:23:21.765: htsp_timer - 10000 msec

*Aug 13 17:23:22.953: htsp_process_event: [1/1/2, FXOLS_RINGING, E_DSP_SIG_0100]

*Aug 13 17:23:22.953: fxols_ringing_not

*Aug 13 17:23:22.953: htsp_timer_stop

*Aug 13 17:23:22.953: htsp_timer_stop3 htsp_setup_ind

*Aug 13 17:23:22.953: [1/1/2] get_fxo_caller_id:Caller ID received. Message type=129 length=11 checksum=00

*Aug 13 17:23:22.953: [1/1/2] Caller ID String 44 35 35 35 38 30 39 38 37 37

*Aug 13 17:23:22.953: [1/1/2] get_fxo_caller_id calling num=555809877 calling name= calling time=08/13 17:23

*Aug 13 17:23:22.953: htsp_process_event: [1/1/2, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

*Aug 13 17:23:22.953: fxols_wait_setup_ack:

*Aug 13 17:23:22.953: htsp_timer - 6000 msec

*Aug 13 17:23:22.957: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc

*Aug 13 17:23:25.973: htsp_call_bridged invokedhtsp_alert_notify

*Aug 13 17:23:25.973: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_HTSP_ALERT]fxols_offhook_alerthtsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Aug 13 17:23:27.465: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

*Aug 13 17:23:27.465: htsp_timer_stop htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Aug 13 17:23:28.773: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_DSP_SIG_0100]fxols_proceed_clear

*Aug 13 17:23:28.773: htsp_timer_stop2

*Aug 13 17:23:28.773: htsp_timer - 6000 msechtsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Aug 13 17:23:33.273: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_DSP_SIG_0000]fxols_proceed_ring

*Aug 13 17:23:33.273: htsp_timer_stop htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Aug 13 17:23:34.573: htsp_process_event: [1/1/2, FXOLS_PROCEEDING, E_DSP_SIG_0100]fxols_proceed_clear

*Aug 13 17:23:34.573: htsp_timer_stop2

*Aug 13 17:23:34.573: htsp_timer - 6000 msechtsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)htsp_call_service_msghtsp_call_service_msg not EFXS (2)

*Aug 13 17:23:37.733: %ENVMON-4-FAN_LOW_RPM: Fan 1 service recommended

*Aug 13 17:23:37.901: htsp_timer_stop3

*Aug 13 17:23:37.909: htsp_process_event: [0/0/0:0(13), R2_Q421_OG_ANSWER, E_HTSP_RELEASE_REQ]

*Aug 13 17:23:37.909: r2_q421_clr_fwd(0/0/0:0(13)) E_HTSP_RELEASE_REQ

*Aug 13 17:23:37.909: r2_reg_channel_disconnected(0/0/0:0(13))

*Aug 13 17:23:37.909: r2_q421_clr_fwd(0/0/0:0(13)) Tx CLEAR FWDvnm_dsp_set_sig_state:[R2 Q.421 0/0/0:0(13)] set signal state = 0x8

*Aug 13 17:23:37.909: htsp_timer - 1000 msec

Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

That message can probably be ignored. The reason why AA doesn't work must be another. Note you also have a fan problem.

New Member

Cisco 3800 FXO ports with caller-id issue.

Hi Paolo,

Thanks for the reply. Can you list some possibility of causes the AA message is not picking up from FXO? This is really weired. I have changed every possible options in the voice port, still i don't see any luck. When i change the caller-id option from "dsp" to any other, caller id is failing.

When the plar configures to any IP phone, i can see the caller-id clearly.

Regards

Kajen

Hall of Fame Super Gold

Cisco 3800 FXO ports with caller-id issue.

Usually the reason is a configuration problem, that is why I indicated before you have to look at AA configuration and traces.

1210
Views
0
Helpful
10
Replies
CreatePlease login to create content