You can implement BSR at a single location by using the BSR commands in vectors. Using BSR across a network is more complex and requires additional administration.
A series of consider location steps in a multisite BSR vector contacts several remote locations. You must define the locations, determine how the server contacts each location, and set up VDNs and vectors to handle the communication between the origin server and the remote servers.
Note:
You can use any combination of split or skill numbers, VDN numbers, and vector numbers to support a single customer application or call type across a network. For clarity and simplicity, use the same BSR Application Plan number and the location numbers on all servers for a given application.
You must also set up the ISDN trunk groups, parameters for information forwarding (UUI Transport), and administer the numbering plans and the AAR/ARS tables.
Multisite BSR starts with the active VDN for a call, as determined by VDN Override rules. If you want any specific VDN or vector pair to interflow calls using multisite BSR, you must create a specific application for the VDN or vector. A multisite application must contain the elements shown in the following table.
BSR application elements |
Purpose |
The primary VDN |
The primary VDN is the active VDN for a call at the origin server, as defined by the VDN Override rules. Therefore, the primary VDN in a BSR application does not have to be the VDN that originally received the incoming call. The primary VDN links its assigned vector to a BSR application plan and sets BSR Available Agent Strategy. |
The primary vector that handles the incoming call on the origin server |
The primary vector contacts the specified remote servers, collects information, compares the information, and delivers or queues the call to the resource that is likely to provide the best service. |
An application plan |
The application plan identifies the remote servers and specifies the information to be used to contact each server and to route calls. |
Two VDN or vector pairs on each remote server:
|
Status poll VDN or vector The status poll vector compares splits at the location and replies to the origin server with information on the best of the splits. Each remote server in a given application must have a dedicated status poll VDN or vector. |
Interflow VDN or vector When a given remote server is the best available, the origin server interflows the call to the VDN or vector on the remote server. Each remote server in a given application must have a dedicated interflow VDN or vector. The steps in this vector deliver or queue the call to the best resource found by the status poll vector. |
To create a multisite BSR application, first create an application plan on the origin server.
Note:
Remember that the terms local, origin, and remote are relative terms. In most networks that use multisite BSR, every server can interflow calls to other servers and receive interflowed calls from other servers. Therefore, every server in the network can have all the elements described in the table. For clarity in the following discussions, local or origin means a server that decides whether to interflow a call. Remote means a server that is polled by the origin server.
