Status poll vector in a multisite BSR with slow networks

Last Updated : Feb 01, 2013 |

Each receiving server in a multisite application must have a status poll vector. To collect information from the locations, each consider location command in the primary vector places a status poll to the status poll vector for the appropriate server.

The following example shows the status poll vector on the server at location 3.

BSR example of status poll vector at location 3

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

The status poll vector compares skills 2, 11, and 21, identifies the best skill, and sends information back to the origin server through the reply-best command. Note that user adjustments are applied to skills 11 and 21 to adjust the EWT. When EWT adjustments are applied at both the origin and remote servers, both adjustments are added at the origin server.

If skill 11 has the best adjusted EWT at location 3, the skill data, including a user adjustment of 20, is returned to the origin server by the reply-best command.

The first consider series queues the call to local skill 1. If the second consider series identifies location 2 as the best remote resource, the check command in step 10 recalculates the current and unadjusted EWT of the call in skill 1. The check command compares the calculated value to the unadjusted EWT of location 2. If the call’s actual (unadjusted) EWT can be improved by more than 30 seconds, the call is interflowed.

Note:

BSR uses adjusted EWT to determine the best resources in the consider series. Once the best resource is identified, subsequent expected-wait and wait-improved conditionals use the actual EWT values.