Controlling architecture and services

Controlling architecture and services

One mailbox serves as the host for a Carbonio Chats meeting and also stores the meeting’s status. That mailbox has a communication duty with a videoserver instance to initiate and manage meetings.

As a result, every mailbox has an own connection pool that can be managed using the Carbonio CLI. Simple commands may be used to manage the service:

• beginning the connection pool

zextras$ carbonio chats doStartService chats-video-server-connection-pool

• Put an end to the connection pool.

zextras$ carbonio chats doStopService chats-video-server-connection-pool

• Verify the state of a connection pool. This command provides details about the node that it is running on.

zextras$ carbonio chats clusterstatus

     isFullySynced                                       true
     servers
      <ip_server>
          online                                          true
          min_api_version                                 1
          max_api_version                                 22
     meeting_servers
         <ip_videoserver>:8188
             id                                           123
             hostname                                     <ip_videoserver>:8188
             status                                       online
             servlet_port                                 8090
             last_failure
             local_meetings_hosted                        2

This data is included in the output of this command:

• The status will read “offline” rather than “online” if the distant Carbonio VideoServer is unavailable or otherwise inaccessible.
• The minimum API versions (min_api_version and min_api_version) that the server supports
• If the most recent attempt to connect to the video server was unsuccessful, last failure  displays an error message (such as Unauthorised request (wrong or missing secret/token) or a generic Runtime Exception). When the connection is made, the message is removed.
• The number of meetings held on the current mailbox is reported by the local_meetings_hosted  function.