TMS Scheduled Conferences don't connect with TC7.0.1

[Wayne DeNardi]

I am experiencing an issue with conferences scheduled from TMS (version 14.1.1) with endpoints running TC7.0.1 software.

The conference is created in TMS correctly, and messages appear on the devices that the scheduled conference is due to start (and end), but the conference fails to connect.

A sample of the conference log from TMS is as follows:

8/01/2014   10:31:42 AM	User		Conference   Created
8/01/2014   10:31:42 AM	network service		Conference   Started
8/01/2014   10:31:42 AM	network service	POLYCOM	Meeting   allocated on port: 1
8/01/2014   10:31:42 AM	network service	POLYCOM	Sent message to   participant POLYCOM: Scheduled call being connected
8/01/2014   10:31:43 AM	network service	EX90	Allocation   failed: hostAddress: 10.108.134.33, description: GetDocument Failed. URL: https://10.108.134.33/putxml, base   exception: The underlying connection was closed: An unexpected error occurred   on a send.
8/01/2014   10:31:43 AM	network service	EX90	Sent message to   participant EX90: Scheduled call being connected
8/01/2014   10:31:44 AM	network service	EX90	Allocation   failed: hostAddress: 10.108.134.33, description: GetDocument Failed. URL: https://10.108.134.33/putxml, base   exception: The underlying connection was closed: An unexpected error occurred   on a send.
8/01/2014   10:31:44 AM	network service	EX90	Allocation   failed: hostAddress: 10.108.134.33, description: GetDocument Failed. URL: http://10.108.134.33/putxml, base   exception: The remote server returned an error: (500) Internal Server Error.
8/01/2014   10:31:45 AM	network service	EX90	Allocation   failed: hostAddress: 10.108.134.33, description: GetDocument Failed. URL: https://10.108.134.33/putxml, base   exception: The underlying connection was closed: An unexpected error occurred   on a send.
8/01/2014   10:31:45 AM	network service	EX90	Allocate failed,   conference is not automatically connected
8/01/2014   10:32:19 AM	User		Conference end   time changed from 01/08/2014 11:25:24 to 01/08/2014 10:33:00
8/01/2014   10:32:19 AM	network service	EX90	Sent message to   participant EX90: New end time: 10:33 AM
8/01/2014   10:32:19 AM	network service	POLYCOM	Sent message to   participant POLYCOM: New end time: 10:33 AM
8/01/2014   10:32:51 AM	network service	EX90	Meeting released   on port 1

Note 10.108.134.33 is the IP address of the EX90.

If I downgrade the endpoint(s) back to TC6.3.0 (or earlier), the conference connects correctly and the error mesages from the EX90 are not in the log.

Edit: If I get TMS to schedule the call in the opposite direction (ie, the Polycom, or non TC software endpoint, to the EX90) the call also connects properly.  It's only an issue if the TC7.0.1 device is set to initiate the call.

Wayne

--

Please remember to rate responses and to mark your question as answered if appropriate.

[Patrick Sparkman]

Chad - Is there an eta when this might be fixed?  I'm hesitant to upgrade our codecs to TC7.x because we have about 100 conferences already scheduled in TMS that the layout would need to be changed to workaround this issue.  The OpenSSL issue that is currently going on right now, will make us have to upgrade the codecs (as that issue has been detected by us and others running C-Series codecs), and I'd hate to upgrade and then find out our conferences fail to connect.

[Kjetil Ree]

Hi Patrik,

It has been resolved in TMS 14.4. We expect to release 14.4 in early May.

Regards,
Kjetil

[Chad Johnson]

Hi Patrick,

Bug CSCum50651 is planned to be fixed in 14.4. I don't have a commitment date on when it will be released. Unfortunately I am not working in the TelePresence group anymore so I am not part of the updates.

Maybe Kjetil will be able to add an ETA in regards to when 14.4 is being released.

Chad