TMSXE and TMS defaults - Close, but not quite there

[Bill Lundin]

We just installed a trial of the TMSXE service. It works fairly well, but there are a few behaviors that might be show stoppers for us. Any advice would be most welcomed. 1) For a call that TMS recognizes needs to pull in an MCU, can the default Visibility be set to Private vs. Public? 2) Is there any way to set a password PIN to be 5 digits instead of 3? 3) Is there a way to have a reservation type of "No Connect" not bounce all the early callers of a P2P call at the exact time of the reservation?

Without a fix to these three situations, I think I'm back to the drawing board. Thanks in advance for an and all help.

Sent from Cisco Technical Support iPad App

[Kjetil Ree]

Hi Bill,

1. No, TMS will never create conferences as "private" on an MCU.
2. No, it will always be three digits.
3. Not sure what you mean. In point to point calls, TMS won't instruct the receiving endpoint to bounce the call. This is outside of TMS's control.

Edit: I see your point now about the "no connect" p2p conference. This is indeed bad behavior from TMS's side, but I cannot think of a workaround.

Regardsm

Kjetil

[Bill Lundin]

Thanks for the quick reply. Unfortunate on all three points.

Sent from Cisco Technical Support iPad App