When using unicast music on hold,how many streams will be sent to endpoints if a corporate marketing department has a customized message that is played whenever a customer is placed on hold?

Question

Options

• Aone
• Bone for each message in the music on hold system
• Cone for each endpoint placed on hold
• Done per instance of music on hold in the server

• A
  3% (2)
• B
  2% (1)
• C
  88% (52)
• D
  7% (4)

Explanation

With unicast music on hold, a separate, dedicated audio stream is sent to each endpoint individually - so if 50 customers are on hold simultaneously, 50 independent streams are transmitted, making C correct. This contrasts with multicast, where a single stream is broadcast to all listeners at once.

Why the distractors are wrong:

• A (one stream) describes multicast behavior, not unicast.
• B (one per message) confuses the number of audio files in the MOH library with the number of active streams - these are unrelated.
• D (one per MOH instance on the server) is a fabricated concept; stream count in unicast is driven by connected endpoints, not server instances.

Memory tip: Think of "uni" in unicast as "unique" - each held endpoint gets its own unique stream, so stream count always equals endpoint count.

No community discussion yet for this question.