Scenario Source Location

The Monitoring Solution service operates multiple data centers around the world including the United States, Europe and Asia. The main objective of these different data centers is to replicate scenarios where end users are located in those geographies, and carrying out the relevant scenario. This is an important consideration, as potentially issues will arise that are only evident in certain geographies (for example, slow network connectivity impacting session establishment or audio quality). For each scenario, Monitoring Solution makes it possible to specify which location the scenario should be executed from. This allows various scenarios to be validated including:

-     Scenarios from all data centers

-     Specific scenarios are executed from Europe

-     Specific scenarios are executed from Asia

-     All scenarios executed in the United States

-     Each scenario can be independently specified.

In addition to the frequency of scenarios, it is important to note that each source location is independent and replicates an end user scenario and its associated resources.  The following server and user factors need to be taken into consideration when deciding on whether or not a scenario should be validated from multiple data centers:

-     Edge Server

Most Lync or Skype for Business deployments deploy a single set of Edge Servers within a primary data center, with which all roaming end users access Lync or Skype for Business. However, some deployments deploy multiple sets of Edge Servers geographically dispersed, and focus on allowing users to access the Edge Servers based on their geographical location. To replicate Edge Server scenarios, Monitoring Solution’s flexibility for scenarios allows for the specification for which Edge server FQDN is to be used. It is expected that the relevant Edge Servers will be aligned with the Scenario Source location.

-     Source User and Target User

To replicate end user behaviors, Monitoring Solution must act as an end user. Monitoring Solution not only performs the same action, but also has an identity that is considered to be the same as an end user. A Source User that initiates the relevant action (for example, making an Outbound PSTN call) is required for all scenarios.

A Target User that is receiving the call is required for all scenarios except the Outbound scenario (which only requires a Source User). These Source and Target Users need to be homed on a Lync or Skype for Business pool as would be the case with real Lync or Skype for Business end users. This mechanism ensures that:

-     Pool to Pool scenarios are validating behavior between two pools (for example, the Source User is homed on Pool A, and the Target User is homed on Pool B).

-     Gateways are available from relevant pools (for example, the Source User is homed on Pool A in the organization’s United States data center and is making a call to a gateway located in Switzerland).

NOTE:

For the Dial-In Conference Scenario and the Audio Conference Scenario:

-     The Source User is referred to as the Organizer

-     The Target User is referred to as the Attendee

 TIP:

It is recommended to consider the location of the organization’s end users, and target the end user scenarios based on their behavior. For example, if an end user located in Asia rarely makes calls to a United States Outbound PSTN number, then coverage of this scenario is not required or is of lower priority and less frequent.

The table below outlines whether a Source User or Organizer and a Target User or Attendee are required for each scenario, and whether the relevant end user needs to be enabled for Unified Communications (UC):

Important:

An end user account must exist for both the Source User or Organizer and the Target User or Attendee. Therefore, a user account must exist in AD, which has a:

–   Domain Account

–   Password

–   SIP URI enabled

–   Associated phone number, for Lync or Skype for Business where the account is enabled for UC.