TMS-conductor Schedule error "Instance allocation failed: Guid should contain 32 digits with 4 dashes"

sdeltoro1 — Sun, 17 Mar 2019 23:57:48 GMT

What is the resolution to successfully integrate TMS 14.1 to Conductor 3.0.?.
VCS 8 is integrated to conductor via B2BUA, but using Policy same result.

TMS successfully creates conference on MCU that is behind Conductor. the problem is that Conference always remain permanent (no end date), and TMS cant dial-out to participants.
TMS message:
Conductor-TMS Schedule error "Instance allocation failed: Guid should contain 32 digits with 4 dashes"

"Instance allocation failed: Description: {"status": "error","info":"conference" already present"
Instance: No contanct with master system, 3 successive polls failed

"Instance Allocate Failed, conference is not automatically connected.

Thanks and Regards

Hi, Please, move this post to

dpetrovi — Tue, 10 Mar 2015 12:09:20 GMT

Hi,

Please, move this post to TelePresence community to get TP and TMS experts' assistance. This community is for Cisco WebEx Meetings Server and Cisco Unified MeetingPlace.

Kind regards,

-Dejan

topic TMS-conductor Schedule error "Instance allocation failed: Guid should contain 32 digits with 4 dashes" in Collaboration Applications

TMS-conductor Schedule error "Instance allocation failed: Guid should contain 32 digits with 4 dashes"

Hi, Please, move this post to