Table of Contents
Advertisement
Advice of Charge — No new capabilities are added for the NCR feature for the Advice of
Charge PSTN feature. The Advice of Charge feature should be used with the same
trunk facilities used for the NCR feature.
BCMS — No change is made to BCMS for support of NCR. redirected calls are tracked
as completed calls since the PSTN disconnects the incoming facility of the original call
when the call is redirected to another site.
Enhanced Information Forwarding — For the NCR feature, Enhanced Information
Forwarding transports User-to-User information (UUI) for the incoming ISDN call to the
PSTN endpoint that receives the redirected call. The use of the Enhanced Information
Forwarding capability with NCR (the recommended configuration) requires that the
incoming call trunk group be assigned as "shared" (i.e., the UUI IE treatment field
is set to shared). However, if the trunk group is set up as service provider, only the ASAI
user information (or user information provided by the incoming ISDN call) will be
included in the UUI IE sent on a non-shared basis to the redirected-to PSTN endpoint.
NCR supports Information Forwarding for AT&T In-band Transfer and Connect service.
Look-Ahead Interflow — NCR activation using the route-to number vector step does
note require Look-Ahead Interflow to be active to provide multi-site capabilities, which
are required for considering remote locations and access to the BSR Application Plan
form.
Service Observing by VDN — If the Service Observing by VDN feature is used to
service observe a VDN, where the NCR feature is used to redirect incoming ISDN calls,
the service-observer will hear the same tones, music, and/or announcements heard by
the incoming caller before the NCR feature reroutes the call to another PSTN endpoint.
When the NCR operation is completed, the service-observer will be dropped as an
observer of the incoming call and placed in the service-observing queue associated with
the VDN.
Trunk-to-Trunk Transfer — If the NCR feature is optioned and the ASAI Third-Party
make Call/transfer operation is used to redirect an incoming ISDN to a PSTN endpoint,
the Trunk-to-Trunk Transfer field on the System-Related Customer Options for
must be set to y for the call redirection to succeed. If the route-to number or BSR
queue-to-best vector step uses the NCR feature to redirect an incoming ISDN call
to a PSTN endpoint, the Trunk-to-Trunk Transfer customer option does not have to be
set to y.
VDN Return Destination — If the VDN Return Destination feature is administered for the
VDN that is associated with a vector that causes the NCR feature to be invoked, the
VDN Return Destination feature will be canceled when the call is redirected by NCR.
CMS, Visual Vectors, and Supervisor — CMS Reporting and/or administration on public
network calls that have been rerouted to another public network endpoint using NCR will
be provided by the following Lucent products:
— Release 3 Version 6 (R3V6) CMS or later (reporting), administration of ~r with R3V9
— Release 6 Avaya CMS Supervisor or later (reporting)
Network Call Redirection (NCR) (Category A only)
Issue 1.0 May 2003
197
Advertisement
Table of Contents
