Solved: CUCME 7.0: Rings twice before actual extension rings

gmgarrian · ‎03-23-2009

I have a CUCME 7.0 site that uses a 1MB FXO line for incoming calls. That port is configured to call extension 4000, which is as an overlay on multiple phones/dns. When calling the 1MB line the caller hears two rings before extension 4000 actually rings on the phone.

Is there anyway to eliminate those "non rings?"

Rob Huffman · ‎03-23-2009

Hi Gregory,

You may be seeing this issue due to Caller ID being enabled on the FXO;

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 Telcordia 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 is 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 is 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.

From this good doc;

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

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎03-23-2009

Hi Gregory,

You may be seeing this issue due to Caller ID being enabled on the FXO;

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 Telcordia 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 is 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 is 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.

From this good doc;

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

Hope this helps!

Rob

gmgarrian · ‎03-23-2009

That may be the issue. I'll try that out. Thanks!

Report Inappropriate Content · ‎03-23-2009

on the subject of FXO whats the deal when an incoming FXO call rings to a plar opx IP station which answers and hears silence. Then the fxo caller just hears continuous ringing.

I have googled and googled and cant find anything about this. So any help would be greatly appreciated....

Report Inappropriate Content · ‎03-23-2009

disregard, in grasping at random straws I figured out it was a codec issue.