ShowTable of Contents
Before starting troubleshooting make sure
- A Media Manager Server is installed without errors, configured properly and must have all of its components running.
- All WebSphere fixes required by Media Manager are already applied as per this technotes
- Latest cumulative hotfix applied on client and server (recommended)
- AV policies must be set correctly in SSC
- The policy 'Voice and video capabilities available through the Sametime Media Server' under 'Sametime Instant Messaging Default Policy' must be enabled.
- For embedded clients, the policy 'Allow all Sametime Connect features to be used with integrated clients (IC)' under 'Sametime Instant Messaging Default Policy' must be enabled.
Troubleshooting First steps
Start off with test clients on same network subnet as server – Take firewalls / NAT out of equation
Disable client and server firewalls
Confirm Point-to-Point, then 3-way call.
- P2P will connect clients together with connections in both directions
- 3-way (or larger) will cause all traffic to flow through server
Debug AV calls first, then move to AV in meetings
Do not add additional network complexity until this setup is working correctly
Troubleshooting Video
Minimum video card memory – 128M
Lower sometimes works, but may see problems later
16M always fails
Memory required depends on resolutions / bitrates
DirectDraw drivers used heavily for decoding. Use latest / greatest video drivers for best performance
Video is processor intensive
Troubleshooting Webcams
Always use Manufacturer's drivers
Most installation instructions state to install drivers before plugging in camera, to avoid UVC drivers
Use WindowsUpdate to get the latest drivers
Many crashes have been traced back to issues in old webcam drivers
Troubleshooting UVC Cameras
UVC = USB Video Class
http://en.wikipedia.org/wiki/USB_video_device_class
Generic Windows driver when nothing more specific is found – like thumb drive
Shows up in logs / selections as “USB Video Device”
Drivers are broken in XP SP1, mostly work in SP2, and fully work in SP3
Always better to have full drivers that regonize device specifics. (Focus, other camera features do not work with generic drivers)
Some cameras only use UVC drivers – but many show up as UVC initially, but do not implement the spec completely, and cause crashes later. Very camera specific.
Troubleshooting AV Policies
SSC: Media Manager Server/User Policy Attribute Verification
- http://
:9080/stpolicy/policy/av.default.policy
- http://:9080/stpolicy/policy/av.anonymous.policy
- http://:9080/stpolicy/serverpolicy/
- http://:9080/stpolicy/policy/
SSC: Media Manager Policy Attribute Verification from UI
- From Manager Policies > Media Manager tab > New button. Give e.g. auido_only policy name, update the values accordingly and save the changes.
- Click Assign button assign it to user or group depending on the requirement. Client Assign and Done. (Refresh interval is 1 hour that can be changed from comm. sever see the section below for the details)
SSC: Media Manager Policy Attribute Verification from UI
-Click Find the Active Policies and search for that user, select the user and click Find Active Policies. We can see and verify that the policy is assigned correctly to the user/group.
Community Server: Policy Attribute Verification
-For confirming stpolicy service is working fine we need to change one debug flag value to 5 i.e.by default set POLICY_DEBUG_LEVEL=1 in sametime.ini file on community server:
[Debug]
UCM_SNIFF=0
POLICY_DEBUG_LEVEL=5
VPDIR_IGNORE_BROWSE=1
VP_DELAY_SNIFF=0
UCM_DELAY_SNIFF=0
Restart Community server it will start generating the the detailed policy logs under domino trace directory.
stpolicy_