When dialling fxo rings twice then rings on the phone

[cameronallison1]

Hi There,

I've setup and CME router with several pstn lines connected to FXO ports. When dialled externally the caller rings twice and then the handset (7975) rings.

Any help would be greatly appreciated

See debug output below

*Nov  5 12:24:07.621: htsp_process_event: [0/2/0, FXOLS_CONNECT, E_HTSP_EVENT_TIMER2]fxols_disc_confirm

*Nov  5 12:24:07.621: htsp_timer_stop

*Nov  5 12:24:07.621: htsp_timer_stop2

*Nov  5 12:24:07.621: htsp_timer_stop3

*Nov  5 12:24:07.621: htsp_timer_stop3

*Nov  5 12:24:07.649: htsp_process_event: [0/2/0, FXOLS_REMOTE_RELEASE, E_HTSP_RELEASE_REQ]fxols_offhook_release

*Nov  5 12:24:07.653: htsp_timer_stop

*Nov  5 12:24:07.653: htsp_timer_stop2

*Nov  5 12:24:07.653: htsp_timer_stop3

*Nov  5 12:24:07.653: [0/2/0] set signal state = 0x4 timestamp = 0

*Nov  5 12:24:07.653: htsp_timer - 2000 msec

*Nov  5 12:24:09.205: htsp_process_event: [0/2/0, FXOLS_GUARD_OUT, E_DSP_SIG_0000]fxols_guard_out_ringing

*Nov  5 12:24:09.205: htsp_timer_stop fxols_onhook_ringing

*Nov  5 12:24:09.205: htsp_timer - 125 msec

*Nov  5 12:24:09.333: htsp_process_event: [0/2/0, FXOLS_WAIT_RING_MIN, E_HTSP_EVENT_TIMER]fxols_wait_ring_min_timer

*Nov  5 12:24:09.333: htsp_timer - 10000 msec

*Nov  5 12:24:09.333: htsp_timer3 - 5600 msec

*Nov  5 12:24:09.333: [0/2/0] htsp_start_caller_id_rx:BELLCORE

*Nov  5 12:24:09.333: htsp_start_caller_id_rx create dsp_stream_manager

*Nov  5 12:24:09.333: [0/2/0] htsp_dsm_create_success  returns 1

*Nov  5 12:24:10.297: htsp_process_event: [0/2/0, FXOLS_RINGING, E_DSP_SIG_0100]

*Nov  5 12:24:10.297: fxols_ringing_not

*Nov  5 12:24:10.297: htsp_timer_stop

*Nov  5 12:24:10.297: htsp_timer - 10000 msec

*Nov  5 12:24:12.205: htsp_process_event: [0/2/0, FXOLS_RINGING, E_DSP_SIG_0000]

*Nov  5 12:24:13.293: htsp_process_event: [0/2/0, FXOLS_RINGING, E_DSP_SIG_0100]

*Nov  5 12:24:13.297: fxols_ringing_not

*Nov  5 12:24:13.297: htsp_timer_stop

*Nov  5 12:24:13.297: htsp_timer_stop3

*Nov  5 12:24:13.297: [0/2/0] htsp_stop_caller_id_rx. message length 0htsp_setup_ind

*Nov  5 12:24:13.297: [0/2/0] get_fxo_caller_id:Caller ID receive failed.  parseCallerIDString:no data.

*Nov  5 12:24:13.297: [0/2/0] get_local_station_id calling num= calling name= calling time=11/05 12:24  orig called=

*Nov  5 12:24:13.297: htsp_process_event: [0/2/0, FXOLS_WAIT_SETUP_ACK, E_HTSP_SETUP_ACK]

*Nov  5 12:24:13.297: fxols_wait_setup_ack:

*Nov  5 12:24:13.297: [0/2/0] set signal state = 0xC timestamp = 0fxols_check_auto_call

*Nov  5 12:24:13.301: htsp_timer_stop3

*Nov  5 12:24:13.305: htsp_process_event: [0/2/0, FXOLS_PROCEEDING, E_HTSP_PROCEEDING]fxols_offhook_proc

*Nov  5 12:24:13.305: htsp_timer - 120000 msec

See voice port config

voice-port 0/2/0

trunk-group voicepstn

translation-profile incoming isdnIN

supervisory disconnect dualtone mid-call

disc_pi_off

compand-type a-law

cptone AU

timeouts call-disconnect 5

timeouts wait-release 5

connection plar (removed) XXXXXXXXXXX

impedance complex1

description (removed) XXXXXXXXXXX

bearer-cap Speech

caller-id enable

[Rob Huffman]

Hi there,

Maybe you could leverage this OPX command

FXO Delayed Caller ID Delivery

Before Cisco IOS Release 12.4(11)XW, Foreign Exchange Office (FXO)  Caller ID in North America was delivered between the first and second  ring cycles based on the GR-30-CORE standard. FXO software was  configured to wait for Caller ID delivery before initiating the call  setup for the next leg. As a result, the destination endpoint did not  start ringing until after 1.5 to 2 ring cycles on the FXO port.

Beginning with Cisco IOS Release 12.4(11)XW, the immediate keyword has been added to the connection plar opx command.  When this keyword is included in the syntax, the FXO port sets up calls  immediately so that the ring-cycle discrepancy is eliminated, and the  perception of the number of rings is the same for both the caller and  the called party. When the Caller ID is available, it is forwarded to  the called number. If the called party answers the call before the  Caller ID has been forwarded, then the Caller ID update will not be  forwarded to the display at the called party.

---

Note This  feature does not require that Caller ID be enabled. If Caller ID is  enabled, it will be handled as described here. The fundamental benefit  of this enhancement is to ring the destination party immediately.

---

This feature is critical for service organizations that have service  level agreements (based on calls being answered within a specified  number of ring cycles) with their customers.

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

Cheers!

Rob

"Why do the best things always disappear " 

- The Band

[paolo bevilacqua]

You should remove the caller-id enable"command, as no caller id is being received.