Call Vectoring methods used with the AT&T In-Band Transfer Connect service

Last Updated : May 27, 2013 |

The BSR feature invokes the AT&T In-Band Transfer Connect℠ service. You can administer an interflow VDN in the BSR Application table to route to a near-end Communication Manager VDN. The VDN causes the execution of a *T announcement vector step rather than setting the same interflow VDN number to route directly to a VDN on a far-end Communication Manager.

You must administer the BSR location on the BSR Application Plan screen to enable a BSR polling vector to identify a BSR best location and route the incoming call to the location. The BSR Application Plan must meet the following requirements:

  • The plan must include at least one interflow VDN that is associated with the vectors that include the vectors steps necessary for successful invocation of the AT&T In-Band Transfer Connect℠ service.

  • The Net Redir field associated with a location where AT&T In-Band Transfer Connect℠ is used must be set to n.

Example: The following example shows how you can use BSR with the AT&T In-Band Transfer Connect℠ service to implement call redirection. In the example, local interflow and not remote interflow VDN numbers are assigned on the BSR Application Plan screen.

                  BEST SERVICE ROUTING APPLICATION

Number: 1    Name:        Maximum Suppression Time: 60      Lock? y

Num  Location Name   Switch Node     Status Poll VDN   Interflow VDN    Net Redir?
1    Omaha             320           95022011          4004                 n
2    Paris             320           95022111          4005                 n
3    Sydney            320           95032211          4006                 n

The example application plan lists VDN extension numbers that are local to Communication Manager. Each VDN is associated with vectors that are designed to invoke the AT&T In-Band Transfer Connect℠ service operations.

Each vector associated with the interflow VDNs listed in the application plan includes the following steps:

1. announcement 1234 [*8 and PSTN number for remote site]
2. wait-time 2 secs hearing silence
3. disconnect after announcement none

In the vector example, step 1 provides the extension for an announcement that plays the DTMF digits. Step 2 includes a wait-time step to give the PSTN switch time to process the in-band information sent by the announcement in the preceding step before the call is disconnected at Step 3. The disconnect command sends an ISDN DISCONNECT message that includes the Information Forwarding data for the call in a codeset 0 or 7 UUI IE element.

Important:

The type of Information Forwarding data sent to the PSTN depends on how the UUI IE Treatment field on the Trunk Features page of the Trunk Group screen is administered:

If the UUI IE Treatment field is set to Service Provider, the ASAI user data is forwarded to the PSTN in the ISDN DISCONNECT message. If the UUI IE Treatment field is set to Shared, the call center-related data described in NCR and Information Forwarding is forwarded to the PSTN in the ISDN DISCONNECT message.

You can use the call vector example to begin the AT&T In-Band Transfer Connect℠ service with non BSR vector programming. To execute the example vector in a non-BSR vector call flow, apply the guidelines and notes related to the *T announcement format.