Jamvee™UC Release Notes – v4.3

1. General Release Overview

1.1  Jamvee™ UC Service Release 4.3 – Release Date January 31, 2015

This release correlates with the following component versions:

  • Jamvee UC PC Client Release:  v4.1.3.52
  • Jamvee UC Mac Client Release:  v4.1.3.52
  • Jamvee UC iOS Client Release:  v4.0.0
  • Core Release:  R1.6.11
  • Edge Release:  R1.6.11
  • Synergy Release: v3.4.3
  • Service Management Tools:  Portal SW 3.1.1
  • SDP components:  CM043, CM043.1
  • Documentation:  v4.2-20141101

2New Features

2.1 Distributed Conferencing

This feature is a new capability of the call bridge infrastructure (Core Servers) that allows a single jamvee UC conference to span multi- conference bridges in different PoPs on the Tata communications Global Meeting Exchange network (i.e. NY, London, Singapore or Sydney). This capability allows conference participants from different regions to be connected to the closest jamvee call bridge and the conference is then cascaded between two or more call bridges. This maximizes the user’s quality of experience by ensuring each participant connect s to the closest bridge to where they are located and reducing the impact of poor network performance (e.g. packet loss, jitter or latency ) related to the public Internet .


2.2 Partial Support for Telepresence Interoperability Protocol (TIP)

This capability allows users to dial-in to a jamvee™ UC conference using immersive telepresence equipment (single or multi-screen systems) from Cisco and other suppliers that are compatible with the Telepresence Interoperability Protocol (TIP).

  • Currently only Cisco CTS and TX systems running TIP v8 are supported. Equipment from other vendors have not been tested. If your Cisco CTS or TX system is using an earlier version of TIP then it will need to be upgraded to a later software release before it will interoperate with the jamvee™ UC™ service.

The following TIP issue is not resolved and will affect telepresence systems on Tata Communications’ TPaaS network.  We expect the current limitations to be resolved in a future release. 

  • Hold/Resume may cause intermittent call drops from Cisco CTS500, CTS1000 and TX9000 endpoints.  If this should happen, the temporary workaround is to dial back into the conference.
  • Calls from telepresence equipment longer than 3 hours continuous duration may be timed out and disconnect. Simply disconnect and redial back in during the time 3 hour time window to extend for a further 3 hours. 

2.3 Audio Conferencing Keypad Controls

Audio Conferencing Keypad control allows users to control certain aspects of the audio portion of a jamvee™UC conference using the keypad on the following:

  • Phone via the PSTN
  • Lync 2010 and 2013 desktop client
  • Video conferencing room system, device or application (operating in SIP Mode) connecting to jamvee™ UC over the Internet or on a dedicated connection

 Note: This capability is not currently available via the jamvee™ UC Desktop/Mobile Apps .  It will be supported in a future release.

Host Controls

*96 – will mute all participants on all call legs on the conference (e.g. Lecture mode). 

*97 – this command will unmute all participants on all call legs on the conference

*93 – this command will terminate/disconnect all parties in the conference

*6 – will toggle the local audio mute/unmute for the host.

Participial Controls

*6 – will toggle local audio mute/unmute for a specific user. If the host has muted all the participants, *6 will unmute the local audio for a specific user.


2.4 Dial-Out for H.323 Video Calls

This capability allows the Jamvee™ conference host and authorized members of this jamvee™ Room to dial-out using the Jamvee™ UC PC apps as follows:

  • Add-in Internet reachable H.323 capable video endpoints (e.g., room systems, desktop video systems, etc.) in to a jamvee™ Room at any time using IP address dialling. If the user has the IP address, open the “ Call Panel ”, click “Invite people to join call button , enter the IP Address dial string (e.g. and click the “ Call” button.
  • Move the jamvee™ UC app audio and video from the user’s computer or iPad to an Internet reachable H.323 compatible video room or desktop system using IP address dial ling. If the user has the IP address of the target room or desktop video system, click the “ Connect phone or video device ” button, click “Add Device button , enter the IP Address dial string (e.g., the desired device name and whether it’s a single or dual screen video system, click “ Save”, select the device from the listing and click “ Connect ”.
  • Place a call to an Internet reachable H.323 capable video endpoint (e.g., room systems, desktop video systems, etc.) using IP address dia l ling. If the user has the IP address of the target video system, click the “+Call ” button, enter the IP Address dial string (e.g., and click the “ Start Call” button.


Note: is for illustration purposes only.
Please use the IP address of the device you wish to connect to.

3. Improvements

Removed the incoming video layout with the film strip overlay in active speaker mode. The default incoming video layout for certain endpoints (e.g., Lync clients, video room systems, video applications, etc.) that cannot choose a jamvee™ video layout has been changed from “active speaker with a film strip overlay of other attendees” to “active speaker with the film strip stacked below the active speaker” layout. This changes does not impact the jamvee™ UC Desktop/Mobile Apps.



4. Retired Features


5. Fixed Issues in this release

5.1 Core and Edge Servers


Issue ID


Core & Server Ver.


Some participants showed up as “unknown” in the roster on the jamvee™ UC desktop apps.



Call timer in the jamvee™ UC apps continued to increment in SIP calls after call termination.



Lync clients were exhibiting sub-standard video quality



Content being shared was treated as a video streams between call bridges.



Content being shared was not viewable on TIP endpoint video screens.



CTS3000 endpoint stopped transmitting video after 15 minutes.



Lync client calls into a jamvee™ Room did not connect reliably.



The Active participant count in the jamvee™ UC apps was not correctly displayed when using distributed Call Bridges.



Multiple TIP endpoints could not present simultaneously .



TIP endpoint hold/resume operational issues.



Frequent video resolution changes with Lync clients and EX60 systems in a jamvee™ conference



1080p video support for TIP endpoints was not operational.



When dia l ling an unknown Lync URI the call would appear to connect.



Lync video calls in to a jamvee™ Room established with no audio



Call setup issues with Avaya SM 6.1.7



Cisco CTS endpoint call drops after a re i nvite .



All active calls are dropped



TIP calls generate inaccurate high round trip time messages



Polycom RealPresence Group unit fails to receive content if joining the call after the presentation has started.



3rd party SIP video applications display error message “Unsupported: timer”.



Lync AVMCU calls disconnected at 16 minutes



After a Call Bridge reset, TURN server may need resetting



Old DHCP addresses not cleared from server.



Unencrypted calls could join jamvee™ Rooms requiring encryption.



Unable to login to Web Bridge with delays of approximately 550ms.



Significant amounts of jitter could be experienced in TIP calls.  TIP systems interpret proper spacing of RTP packets according to transmit bandwidth as jitter.  A workaround has been implemented.



Connection from Call Bridge to Web Bridge issues seen when connecting by WebRTC Client from OS X Safari.



Misleading message displayed for mismatching key/cert pair.  The error message has been changed.



First few seconds of the video stream get fragmented.  With MTU set for an interface when making a call the MTU determination took a few seconds.



Jamvee™ Room activated in error by guest-initiated chat.  A room could be activated by a guest if a Lync client user is a guest in the room.



Desktop  and WebRTC clients unable to log in.  This was caused by a momentary failure of the Call B ridge to connect to the master jamvee™ Room database during the login process.


6. Known Limitations

Issue ID




Hold/Resume causes call drops from CTS500, CTS1000 and TX9000 endpoints.



Video communications may not be established when using the older jamvee™ Video Apps while in a jamvee™ UC™ conference.



7. Special Installation/Upgrade Instructions


Special note for users of the jamvee™ app running on the Microsoft Windows Operating System:

If you have not re-installed or downloaded the application since November 1, 2014 you will need to do so in order to access the new features after the system upgrade. To do this please perform the following steps:

  • Uninstall your current jamvee™ UC app:  
  1. Quit the jamvee™ UC app, if it is running
  2. Click Windows Start
  3. Click Control Panel
  4. Click Programs and Features
  5. Locate and double-click on the  cid:image012.jpg@01CFF516.5E248110 or cid:image013.png@01CFF516.5E248110 program that appears
  6. Follow the prompts to uninstall it
  • Next, click on the link below to install the current version of the windows app:



Special note for users of the jamvee™ app running on the Apple Mac Operating System:

  1. Click here to download the new Jamvee™ UC for Mac App
  2. Open the dmg file and drag the ‘ Jamvee™ UC’ icon into the Applications folder within the window that opens up.
  3. If you already have an older version of the Jamvee™ UC for Mac App installed in the Applications folder, a prompt asks whether you want to replace it with the new one that you are moving. Select Replace.   This will overwrite the previous version and if, for example, you have a shortcut in the dock this will now automatically launch the new version .

Note: If you first remove an older Jamvee™ UC for Mac App from the Applications folder and then copy the new one into it, clicking on the dock shortcut no longer works and the icon becomes a question mark because the icon still searches for the previous application version. Launching the new version from the Applications folder will result in a separate dock shortcut being created. Follow the instructions above to avoid this issue,


v4.2 01 20141101