© 2013 IBM Corporation

IBM Sametime Audio/VideoOpen MicJanuary 9, 2013

Ginni Saini | Level 2 Support EngineerMichael Altman | Level 2 Support Engineer IBM Collaboration Solutions

2

Agenda

■ Media server─ Basic configuration─ Concepts─ Preferred install options─ Best practices

■ Q&A

3

Sametime Media Manager

■ Runs on WebSphere Application Server

■ Administered using the centralized Sametime System Console (SSC)

■ Uses the Session Initiation Protocol (SIP) to provide support for point-to-point and multi-point calls

■ Designed to support standard audio and video codecs so that it works with other external audio and video vendors

■ Uses three components─ SIP Proxy Registrar─ Conference Manager─ Packet Switcher

4

■ Requirements before installing Sametime Media Manager─ LDAP─ DB2─ Sametime System Console server─ Sametime Community Server

■ Use the “All components” deployment plan to install a stand-alone Media Manager in proof-of-concept environments

■ During install, choose “Cell” configuration or “Primary Node” configuration, depending on the deployment type you wish to have

─ Cell─ Primary Node

Sametime Media Manager

5

Cell vs PN install

■ Cell─ CELL plans - each component (or the all in one) will have its own ISC and

Deployment Manager ─ Decentralized administration

■ PN (recommended)─ Uses the System Console as its deployment manager─ Centralizes all WebSphere and Sametime administration─ Has the advantage to scale up simply by adding additional secondary nodes

quickly─ Fast migration from pilot to production

■ Primary Node federated into the SSC is the recommended configuration■ SSO needs to be configured between the deployment manager for the Media Manager

components and the Community Server(s)

6

Planning and organizing the size of your deployment

■ Before you install any Sametime components, know whether you are installing a small-scale deployment or an enterprise-scale deployment

■ In the case of an enterprise-scale deployment, you must also decide if you will be using clustered servers to distribute the load

■ The size of your deployment affects installation choices

■ Logical naming conventions for application server hostnames

■ Map out a diagram showing how you want to deploy your environment. It should include hostnames and IP addresses of the components

■ Logical naming conventions for deployment plan names e.g. AVSIPPRPN or SPRPN

■ Know your administration names and passwords

■ Use root for UNIX or run setup executables using admin rights/account for Windows

■ Simplify the install path e.g. C:\IBM\Websphere or C:\Websphere

7

Sametime 8.5 Media Manager consists of three server components

1. SIP Proxy/Registrar

2. Conference Manager

3. Packet Switcher

8

1. SIP Proxy/Registrar

■ The SIP Proxy and Registrar handles SIP-based call routing, endpoint registration for users and the media server components; Packet Switcher and Conference Manager

─ Directs conference participants to Conference Manager servers

─ Responsible for location service and forwarding SIP messages to a destination

─ Requires access to LDAP

─ Can install multiple SIP Proxy/Registrar components and cluster them for high availability and failover

9

2. Conference Manager

■ The Conference manager hosts TCSPI adapters (one internal and one external) and provides conference focus functions (as in RFC 4353)

─ Manages all conferences, including point-to-point and multipoint

─ Works with the client to establish the SIP session for the call

─ Requires access to LDAP and Proxy/Registrar (including transport protocol: UDP, TCP, TLS)

You can install multiple Conference Manager components and cluster them for high availability and failover.

10

3. Packet Switcher

■ The Packet switcher routes audio and video to multi-point and web meeting participants based on voice-activated switching

■ Functions as an MCU by routing audio and video data between participant endpoints.

Note that point-to-point A/V calls do not use the Packet switcher.

■ Responsible for receiving and sending media streams from endpoints to other endpoints in a conference

■ Works on audio streams to determine the active video stream to send to the participants, a process known as Voice-Activated Switching (VAS)

■ Requires access to LDAP, Conference server, and media ports (range of ports for audio and video – UDP traffic)

■ If the switchers are installed on the same machine, ensure that are no port conflicts

■ Should not be a member of a WebSphere Application Server cluster; instead, each Packet Switcher is deployed as a non-clustered (primary) node

■ The Packet switcher cannot be clustered, but there can be multiple switchers

11

Media Manager Components (cont')

■ All Media Manager components are WebSphere-based applications■ These components can be on a single machine or distributed across multiple

WebSphere nodes■ Security is enabled by default. Use TLS or SSL to allow servers to communicate. TLS

transport is recommended when using media encryption■ It is expected that all of these components will reside within the same subnet/network

location and that traffic between them will not be restricted■ If you plan to cluster, keep in mind that components cannot be clustered over a WAN

For more details on each component, refer to the Sametime wiki for 8.5.2.The following is a link on our wiki documentation about planning your Media Manager installation:

Planning a Sametime Media Manager installation on Linux or Windows

12

Audio/Video considerations

■ Review the Detailed System Requirements document■ Media Manager is supported only on Windows and Linux platforms■ Can support only one stand-alone Media Manager server, or one

cluster of Media Manager servers■ IPv6 addressing is not supported■ Default maximum number of participants in a single conference set to

20 - can be adjusted to accommodate network requirements■ LDAP directory must have the email field populated for every user■ Network Address Translator (NAT) and firewall support

─ TURN Server enables Sametime clients to send and receive AV communications across a NAT or firewall

13

Clustering Media Manager

■ Only the Conference Manager and SIP Proxy and Registrar can be clustered ─ The Packet switcher cannot be clustered, but there can be multiple switchers ─ The Conference Manager will balance the requests among the available Packet Switchers

■ The “All components” installation cannot be used for clustering ■ At least three machines are required for vertical clustering where each

component uses the SSC deployment manager: ■ When you cluster, you must have a WAS SIP Proxy for that cluster and

community server goes through it■ WAS SIP Proxy server can be used on the same machines with the following

exceptions:

─ No more that 1 WAS SIP proxy per node / host─ WAS SIP Proxy should not be deployed on nodes running a Packet Switcher

■ Steps can be found in Sametime 8.5.2 Information Center topic “Clustering Sametime Media Manager components.”

14

Port ranges – default ports using the TCP option

Note: port reference may change depending on size/type of deployment

Also look here on the wiki - Ports used by Sametime servers

15

Media Server deployment – Install SPR example UI

16

Media Server deployment – Install SPR example UI

17

Media Server PN deployment - Example

18

Media Server PN deployment – SIP PR

19

Media Server PN deployment - CM

20

Media Server PN deployment - PS

21

Locating and administering your media servers in the Integrated Solutions Console

22

Applications listed in ISC for Media Server

23

Locating the Virtual Hosts used by the Media Manager

24

Conference Manager assigned Virtual Hosts

25

SIP Proxy and Registrar assigned Virtual Hosts

26

Relation between ISC config settings and STAVConfig.xml for the SIP Proxy and Registrar

NOTE:● STAVConfig.xml lists the ports that are in use in the config● If you do a non-clustered install, the defaults will be correct in the STAVConfig.xml - this is true for

both the all-in-one and the separated node installs

27

Registered bindings after server install

28

Registered bindings

29

Architecture for small, highly secure deployment with TURN server

30

Best Practices for ensuring a good audio/visual experience■ Use a supported camera, and use the camera manufacturer's drivers instead

of the generic Windows drivers■ Use the latest manufacturer camera drivers■ Use latest manufacturer video card drivers■ All participants must be connected to the same community used by the Media

Manager. All participants must be using Sametime 8.5.x clients. Latest version preferred

■ Verify function with clients on same network subnet first■ Use bitrate appropriate for your users / equipment / environment■ Bandwidth considerations - One of the key factors affecting video quality is

available network bandwidth. Tune your bandwidth settings to what is appropriate for all users

■ The higher the video resolution, the more bandwidth is required for better quality. Adjust and manage video bit-rates accordingly on the Media Manager Video Resolution configuration page

31

Client considerations

■ All 8.5.x clients (8.5.0, 8.5.1, and 8.5.2) can interoperate with each other and use any 8.5.0, 8.5.1, or 8.5.2 servers

■ Some hotfixes or specific configuration may be required IF you are using TLS■ Refer to the following IBM Technotes for details:

─ “Using Transport Layer Security (TLS) with the Sametime Media Manager 8.5.2 server and pre-8.5.2 Sametime clients in a clustered environment” (#1567676)

– Link: http://www.ibm.com/support/docview.wss?uid=swg21567676

─ “Unable to initialize computer and it can't be used at this time. SIP 401 SIP 503” (#1470263)

– Link: http://www.ibm.com/support/docview.wss?uid=swg21470263

■ Clients require Media Manager server running Release 8.5.1 or later to be able to make or receive computer audio or video calls

■ Clients running releases earlier than 8.5.2 cannot have audio and video communications across a Network Address Translator (NAT) or firewall

32

Troubleshooting resources

■ General troubleshooting tips can be found in the IBM Sametime wiki

■ To collect diagnostic data (logs and trace files) to review, either on your own or when working with IBM Support, refer to the technote:

─ “Collecting Data: Lotus Sametime Media Manager” (#1428735)

■ Common issues

─ You can search technotes about known audio/video issues or frequently asked question on the IBM Support website

─ Some common issues seen that can be resolved usually with simple config changes are: poor video quality, UDP port conflicts, n-way calls not working, etc.

33

Future Open Mics

During 2013, we will cover the following IBM Sametime topics:

■ Clustering■ TURN server■ SIP EDGE Proxy

Visit our Support Technical Exchange page for details on future events.

Our Open Mic schedule is also available on our IBM Collaboration Solutions Support Facebook page (facebook.com/IBMLotusSupport).

34

Press *1 on your telephone to ask a question.

IBM Collaboration Solutions Support pagehttp://www.facebook.com/IBMLotusSupport ICS Support@IBM_ICSsupport