Hi Mark,
I understand your point. But it is not a bug, it is an expected and strange behavior (although is a little stupid).
The problem is not directly related to the "Conference Default IP Bandwidth" parameter, it is related to the "IP bandwidth" in the scheduling page, because if you set conference IP bandwidth to 6144, the problem occurs, even if the global Conference Default IP bandwidth is set to 4096 or less. But in fact, it is not that parameter alone, the fact here is, TMS cannot schedule a conference and set TC endpoints to dial out using 6144 Kbps of bandwidth, because the Maximum bandwidth supported by TC endpoints is 6000.
That's why you can schedule CTS to CTS and CTS to TB, because in both cases TMS will set the CTS endpoint to start the point to point conference by dialling out using bandwidth of 6144, because CTS is able to dial out using 6144, but TC endpoints not.
To prove this, do this:
- Go to system navigator, choose any TC endpoint and go to "settings" tab, take a look at the "Maximum IP bandiwdth" field, the value is 6000 and cannot be changed.
- Still, go to "call status" page and try to make a call using 6144, that won't work, unless you choose 4096 or a less value or choose max
In my opinion, this is a stupid behavior, because I think that TMS should set the endpoint to dial out using its maximum bandwidth supported rather than inserting a MCU to route the call, or it should at least show a warning message when scheduling informing that you cannot set 6144 Kbps for TC endpoints, or it should give us the option to set a custom bandwidth value instead just a list with few values.
Also, If you call out from TC endpoints using system navigator, you can set banwidth to "max", so that the endpoint can dial out using its maximum capacity. However, when scheduling, we don't have this option, instead, TMS inserts the MCU without asking and without advising anything!! That is bad! =/
You can raise a feature request in order to have this behavior changed, although I agree that it could be treated as a bug or at least as known limitation.
Paulo Souza
Please rate replies and mark question as "answered" if applicable.
Paulo Souza
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
