My opinion is that its far far away from optimal.
The combination of MCU+VCS+TMS has some lacks regarding SIP and h323.
Like you have to reserve two number spaces, one for the h323 prefix
like 500xxx and then a unique range like 400 for the first mcu 500 for the next one
to not get in trouble, and then you can not even limit this range in the TMS, ...
Depending on your deployment simply disabling sip on the mcu might also help
as the VCS is anyhow doing a great job in interworking.
But even then some TMS versions still list the non prefixed sip aliases as a valid address.
When we got the MCU a long time ago we had already filed a feature request which
never seemed to have been processed to fix the "prefix dilemma"
I cant really understand why they can not have one parameter "prefix each single numeric sip registrations
with this value" and bang you could also have your sip registrations working nicely.
But yes, disabling sip registrations and using a prefix will work, you might lack the presence info,
but from what I recall that showed always green anyhow, even in a call (would be cool to see the
presence status incl . the amount of participants)
