NCR operations by Call Vectoring method

Last Updated : Sep 08, 2012 |
Note:

The following description does not apply when the AT&T In-Band Transfer and Connect℠ service is used with NCR.

  1. The PSTN switch sends an incoming ISDN call to Communication Manager, where the call enters vector processing.

  2. One of the following occurs:

    • If the Communication Manager trunk group and PSTN or VPN switch are configured to use an NCT-type redirection protocol, the redirecting Communication Manager returns an ISDN CONNECT message to the PSTN switch. Any of the following vector commands can be used to return the message:

      • announcement

      • collect x digits

      • converse-on split

      • wait hearing music

      • wait hearing (announcement extension) then (continue, music, ringback or silence)

      Note:

      If the redirecting Communication Manager does not execute one of the listed vector steps, a CONNECT message is automatically returned to the PSTN switch.

    • If the server trunk group and PSTN or VPN switch are configured to use the NCD redirection protocol, a CONNECT message is not sent to the PSTN switch. Therefore, when the NCD protocol is applied, none of the listed vector commands are included in call vectors that implement NCR.

  3. Call processing proceeds to either a route-to number ~r or to a BSR queue-to best vector step. Depending on which type of redirection is administered for the incoming trunk group, either NCT-type or NCD processes are initiated. In either case, a FACILITY message is sent to the public network over the D-channel associated with the incoming trunk to invoke redirection of the call.

    Note:

    The following items pertain to the PSTN or VPN endpoint number and to the receiving vector for the interflow location.

  4. The PSTN or VPN switch indicates redirection success or failure consistent with the protocol-specific operations described in NCR options supported by PSTNs. An unsuccessful NCR attempt results in one of the following outcomes:

    • If an NCT-type protocol is used, the redirecting Communication Manager establishes a trunk-to-trunk connection.

    • If the NCD protocol is used and the Avaya DEFINITY version is earlier than load 37 of Release 10, vector processing continues to the next vector step that follows the queue-to best vector step without any best local BSR call treatment.

    • If the NCD protocol is used, the call can be redirected to the best location by means of a trunk-to-trunk connection. However, the ability of the originating server to establish such a trunk-to-trunk connection depends on the specific features of the NCD protocol in use.