CommunicationModeCommand versus RequestMode versus TerminalCapabilitySet (Q67)

The information in this article applies to:

CommunicationModeCommand appears at first glance to be somewhat redundant with RequestMode and TerminalCapabilitySet. Its added value is apparently to describe the structure of a conference, e.g., who's in it and what type of connections they are or should be using.

Use CommunicationModeCommand to change the conference centralization (centralized, decentralized, or hyrbid). Use RequestMode to change modes (the set of media being transmitted by an EP). Use TerminalCapabilitySet only when those two messages will not work, such as at the beginning of a session. Actually, for a session with G.723.1 audio, it might be prudent to always follow CommunicationModeCommand with RequestMode, because the former could eliminate a previous bit-rate stipulation