Interflow vector in a multisite BSR with slow networks

Last Updated : Sep 08, 2012 |

When a call is interflowed to any of the remote locations, the interflow vector on that server accepts the interflowed call from the origin server. It also executes the same consider series as the status poll vector to identify the current best resource, in case conditions have changed since the status poll. The following example shows such an interflow vector.

BSR example of interflow vector at location 2

1. consider skill 2   pri m  adjust-by  0
2. consider skill 11  pri m  adjust-by 20
3. consider skill 21  pri m  adjust-by 30
4. reply-best
Caution:

BSR will not operate correctly unless the consider series in the status poll vector and the interflow vector use the same splits/skills with the same queue priorities.

If the call is queued to a remote resource by step 10 in the primary vector, is the call removed from the local queue that it entered in step 4? When a call is interflowed, the call is removed from any queues at the origin server and any audible feedback at the origin server is terminated.

The second consider series can compare local and remote resources. If it does, and if step 10 queues the call to another local skill, will the call be removed from the local queue that it entered in step 4?

No. In general, the server can queue a call to as many as 3 local splits or skills simultaneously. BSR does not change this limit.