Page 1540 of 1814 Recorded Announcement for Calls Diverted to External Trunks553-2901-301 Standard 9.00 January 2002This feature operates on a route basis and is controlled by a the RANX promptin LD 16, for calls diverted to external trunks.Operating parametersThe RANX feature is supported only for external CO routes. Thecorresponding RANX prompt in LD 16 appears when the trunk type is:• A Central Office Trunk (COT) and is not configured as a Radio Paging(RPA) trunk. The trunk has to be configured as an outgoing oroutgoing/incoming trunk. The feature is not applicable for trunksconfigured solely for data traffic.• A Direct Inward Dialing (DID) trunk configured as an outgoing oroutgoing/incoming trunk. The feature is not applicable for trunksconfigured solely for data traffic.The RANX feature requires a Recorded Announcement (RAN) machine inthe same node as the outgoing route.If the RAN trunk is configured with supervision, the calling party who isconnected to the RAN trunk will be charged from the time the answer signalis sent.This feature is supported network wide in a Meridian Customer DefinedNetwork (MCDN) environment; no other private network protocols aresupported.Since Digital Private Network Signaling System (DPNSS1) does not supportany information concerning redirection, this feature is not supported in aDPNSS1 network.If a telephone is forwarded to a trunk configured with the RANX feature andthe party that calls the extension is supposed to dial additional digits, this isnot always possible. If the calling party dials digits when being provided withRAN, those digits will be lost since they are not buffered.If the outgoing trunk, or the telephone from which the call originated, timesout during the RAN, it is not possible to dial additional digits after the RANis terminated.
