I´ve added an unsupported VC-Endpoint to TMS with System Type: Room.
If i check the Scheduling Settings on TMS for this endpoint, I can see that I only can schedule incoming, but no outgoing calls.
We´re using OBTP and if i book this Endpoint in a Multipoint Meeting, I get a TMS routing error, because of the missing outgoing call feature enablements.
Is there a way to enable the outgoing scheduling for this endpoint type?
Is there a way to configure the device type manually e.g. as MXP880 to get the outgoing features?
Is there maybe a flag in the DB, were I can set the device type manually?
Right, that is a valid point, and is actually something we will be looking into changing in a future release. Bug reference ID: CSCtx73847.
We haven't decided what the new behavior will be, but we'll probably just reserve MCU ports for the 'room' type systems to dial in to, and then let users dial in to the conference manually (as we cannot control the 'room' or give it a calendar).
The 'room' system type is meant for endpoints that TMS doesn't support, but that can registered to the gatekeeper or SIP registrer (and thus be dialled by other endpoints). As TMS cannot control the endpoint, it cannot force the endpoint to dial out to someone, but TMS's routing logic allows incoming calls, as it assumes that the gatekeeper / SIP registrar can route calls to it.