Hi Pat,
In additon to my firend Paolo's great tips (+5 "P" )
connection plar opx immediate
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
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen
