Operation
In order to deliver a call to the resource that can provide the best service, the consider command collects and compares information. Whether you use singlesite BSR, multisite BSR, or both, consider steps work very much the same.
Each consider command collects status data from one split or skill. Splits or skills on the same Communication Manager are identified by number. Remote locations must be identified by a location number assigned on the BSR Application screen. For more information, see Avaya Aura® Call Center Elite Feature Reference.
Consider commands are written in a series of more than two steps called a consider series. The first step in a consider series collects status data from a resource and saves the data to a buffer. The next consider step collects status data on the assigned split or skill and compares the new data to the data in the buffer. If the existing data in the buffer indicates that the first split or skill can provide better service to the call, the data for the first split or skill remains in the buffer as the best data. If the second split or skill can provide better service to the call, the status data replaces the data already in the buffer. Each subsequent step works in the same way, collecting data from one resource, comparing the data to the best data found up to that point and replacing the best data only if the resource tested by the current step can provide better service to the caller. This series ends when a queue-to best, or check-best command delivers or queues the call, or when a reply-best command returns the best resource data to a primary vector on the origin Communication Manager.
The first consider step in a series shortens the Call Vectoring 15-step time out from 1.0 to 0.2 seconds. The time out is shortened for BSR vectors only, that is, vectors that use the consider series, in order to reduce real-time delays for call processing and to reduce the incidence of race conditions in multisite BSR applications.
