Audio and video meeting support for mobile users

IBM® Sametime® Mobile Meetings clients connect to the Sametime Proxy Server for audio and video support. How they connect is determined by the Meeting Server configuration and whether they connect through an authenticating proxy.

If the Meeting Server configuration on the mobile client uses an authenticating proxy (also called a reverse proxy), it connects to the Sametime Proxy server using the same authenticating proxy address, port, and credentials. Therefore the authenticating proxy should be configured to direct traffic to the appropriate server, either by using the Client-Type in the HTTP header (meetings traffic uses the STM Meetings value, and Sametime proxy traffic uses the Sametime Mobile value) or by using the URL path (meetings traffic uses a path that begins with /stmeetings, while the Sametime Proxy uses /stwebapi).

If the Sametime Proxy Server must be on a different authenticating proxy address or port, you must add the following custom configuration parameter to the Meeting Server configuration:
"mobile.stProxySSLAddress":"https:\/\/auth_proxy_server:authproxy_port"
When clients connect to the Meeting Server, they use the following rules to determine how to connect to the Sametime Proxy Server:
  1. If the client connects to the Meeting Server through an authenticating proxy and there is no mobile.stProxySSLAddress configuration parameter in the server configuration, the device connects to the Sametime Proxy Server using the same authenticating proxy address, port, and credentials as the connection to the Meeting Server. This is the default scenario and requires no changes to the server configuration.
  2. If the client connects to the Meeting Server through an authenticating proxy and finds a mobile.stProxySSLAddress configuration parameter in the server configuration, then the device connects to the Sametime Proxy Server using the address and port specified by the configuration parameter. If the connection attempt encounters a 401 Basic Authentication challenge, the same credentials that were used with the Meeting Server connection are used.
  3. If the client connects to the Meeting Server without using an authenticating proxy (as is the case when a mobile client uses a VPN or the Meeting Server is internet accessible), then the device connects to the Sametime Proxy Server using the address and port found in the meetingroomcenter.stProxySSLAddress configuration parameter. This is the same parameter the browser client uses to make the connection to the server, so it is generally already present in the server configuration.