Instant Messaging Details Test

Instant messaging (IM) enables your users to communicate with each other in real time on their computers using text-based messages. Both two-party and multiparty IM sessions are supported. A participant in a two-party IM conversation can add a third participant to the conversation at any time. When this happens, the Conversation window changes to support conferencing features. Skype for Business and Communicator clients when involved in a one to one communication, is often referred to as peer-to-peer. Technically, the two clients are communicating in a one to one conversation, with the Instant Messaging multipoint control unit (IMMCU) in the middle. The IMMCU is a component of Front End Server. Placing the IMMCU in the required communication workflow allows call detail recording and other features that the Front End Server enables. Communication is from a dynamic source port on the client to the Front End Server port TLS/TCP/5061 (assuming the use of the recommended transport layer security). By design, peer-to-peer communication (as well as multi-party IM) is possible only when Skype for Business Server and the IMMCU is active and available. Therefore, administrators may constantly require to monitor the ImMCU. The Instant Messaging Details test helps the administrators accompolish this task. This test reports the current health and draining status of the ImMCU server and also helps administrators identify the number of active conferences, users connected to the server and the SIP connections that were throttled.

Target of the test : A Microsoft Skype for Business server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the target Microsoft Skype for Business server that is to be monitored.

Configurable parameters for the test
Parameters Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port at which the specified host listens. The default port is 5060.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Current MCU health

Indicates the current health of the ImMCU server.

 

The values that this measure can report and their corresponding numeric values have been listed in the table below.

Measure Value Numeric Value
Normal 0
Loaded 1
Full 2
Unavailable 3

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the current health of the ImMCU server. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents i.e., 0 to 3.

Draining state

Indicates the current draining state of the ImMCU server.

 

The values that this measure can report and their corresponding numeric values have been listed in the table below.

Measure Value Numeric Value
Not requesting to drain 0
Requesting to drain 1
Draining 2

Note:

By default, this measure reports the above-mentioned Measure Values while indicating the draining status of the ImMCU server. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents i.e., 0 to 2.

When a server is drained, it stops taking new connections and calls. These new connections and calls are routed through other servers in the pool. A server being drained allows its sessions on existing connections to continue until they naturally end. When all existing sessions have ended, the server is ready to be taken offline.

Throttled SIP connections

Indicates the number of SIP connections that were throttled on the server.

Number

If the value of this measure is greater than 1, then it indicates that the peer is not processing the requests on time which may be due to an overload condition of the peer.

Active conferences

Indicates the number of conferences that are currently active on the ImMCU server.

Number

 

Connected users

Indicates the number of users currently connected to the ImMCU server.

Number

 

IMDN failure rate

Indicates the rate at which the Instant Message Delivery Notification failure messages were sent from the server.

Sent/Sec