System Status on TMS

[VCsupport17]

Hi Community,

We have TMS version 14.6 and managing the video conferences servers (Conductor, Telepresence Servers, Expressway Core, TCS).

I have scheduled a video conference using the TMS smart scheduler and works fine. Endpoints are automatically connected on the conference when conference starts. Under Systems > Navigator, Conductor status is in call as expected. But how about the status of the Telepresence Server that was used for that conference, it just display Alive status. What should be the expected status?

Also, if there is a traversal call, the Expressway Core status is just showing "Idle". It should show In Call  when there is an active traversal call?

Thanks in advance.

[Patrick Sparkman]

The status you see for TelePresence Server is normal, as it is managed by Conductor, it won't show the same status and information as if it was directly managed by TMS.

If the Expressway is in use, even for a traversal call, I think it should show an "In Call" status.  Do you see anything under the Active Calls tab on the Expressway, what if you do a force refresh?

[VCsupport17]

Hi Patrick,

Thank you for your answer.

On the Expressway call status, i can see active call. I did not try to force refresh. I will check on this and let you know.

Thanks.

[collinks2]

Hello Patrick,

It has been a while. I am having a similar case. I have just installed TMS but it is running in demo. I have added my call manager,telepresence server and telepresence conductor. I am trying to add the conference alias in the TMS but the alert says no matching aliases with the conductor.the service preference is showing none. The status of the conductor under system settings in TMS is showing idle. What could be the problem?

[Patrick Sparkman]

What is your exact conference alias in Conductor?

How do you have configured for the Numeric ID settings for Conductor in TMS, under Settings > Extended Settings?

[collinks2]

Hello Patrick,

thanks for the response . The conference alias in conductor is (9940)@(.*) while the conference alias in TMS is  (9940)@(.*). the reg expression in TMS is showing 

(\(9940\)@\(\.*\)).*

Numeric Base id is 9940

numeric step is 1

numeric quantity is unlimited

[Patrick Sparkman]

Try the following:

Conductor: (\d{4})@(.*)

TMS: %@domain

The % in the TMS alias is a variable for your Numeric ID, which is created using your Numeric ID Bass and Step, and your Conductor alias has to match what that Numeric ID will become.  You should consider making your Conductor regex more specific though.  For example, instead of (\d{4}) which will match any 4 digit number such as 1000-9999, you could use (99\d{2}) which will match 9940-9999.  What appears before the \d, must be present in the dial string, and \d will match any single digit, unlike \d{#} which will match any digit by the number of times you specify # to be.

Something else to consider is to make your TMS alias use the variable better, instead of 9940 being your Numeric ID Base, you could use 00 for example, which would make your TMS alias be 99%@domain, the end results being an alias in the range of 9900-9999.  Otherwise if you have a Base of 9940 and a Step of 1, with an unlimited Quantity, you could potentially go beyond a four digit alias.

You can also be specific and specify a domain, to allow users to dial the same conference alias from either an H.323 endpoint (which will not append its domain) or a SIP endpoint (which will append its domain), use: (\d{4})(@example\.com)?

[collinks2]

Hello Patrick,

it worked! i have been ale to schedule the first conference. Thanks a lot for your help. can i schedule more than one conference since the conductor is running in free mode?

However,am seeing the following error in the TMS

Time Zone set in TMS for system is different from Time Zone on system. - In TMS: 01:00:00, On System: 00:00:00. - TMS will update the time zone on the system when editing the time zone in TMS. Alternatively the time zone may be manually changed on the system.
	System Warning Ticket - Invalid release key - The release key is not valid; if you do not have a valid key, contact your Cisco support representative - Add a release key
	The system has an incorrect community name

[Patrick Sparkman]

The number of conferences you can schedule and number of participants per conference will depend your TelePresence Server's license count, be it screen licenses or Multiparty.  Screen licenses are participant based and you can have as many conferences as you want so long as you have enough licenses to connect participants, whereas Multiparty licenses are conference based and you can have as many participants as you want so long as you have enough hardware capacity.

You should update the Time Zone either in TMS or directly on Conductor under System > Time.

Release key warning can be ignored as you're running Conductor Essentials, which is the free version and doesn't require a release key, however the message will still display.

Community name can be updated within Conductor under System > SNMP, default is "public".

[collinks2]

Hello Patrick,

sorry, am a bit confused on the screen license and multiparty license,does mean that the screen license determine the number of participants per  conference session while multiparty determine the number of conference session?

The status of the Tele Presence shows that number of screen licenses is 4,

Each time ,i want to have two conference sessions,alarm will trigger in the conductor with a warning message that  the conference bridge has reached its limit

On the issue of conference layout, am only seeing the active speaker while i cant see others.i have set it to ' EQUAL' in both TMS and Conductor. However am still working on it.

[Patrick Sparkman]

Screen licenses will determine the total number of participants connected to the TelePresence Server at once, no limit on the number of conferences.

Multiparty licenses will determine the total number of conferences you can have active at once, no limit on the number of participants, however the max number of participants is determined by the available hardware capacity.

The conference quality in Conductor will determine the total number of participants you can have connected, take a look at Tables 6 and 8 of the TelePresence Server Data Sheet for more information.  I assume you have the conference quality set too high, which can cause you to consume more screen licenses per participant than you have available.

The default layout is Active Presence, but you can set any layout to be the default in the conference template under advanced parameters within Conductor.

[collinks2]

Hello Patrick,

Thank you for the enlightenment. The picture is getting clearer. I understand now that i cant schedule  more than one conference at once without Multiparty License.You mentioned also that a Hardware platform determines the max no of conferences. Does it mean that the VTS 8 CORE  is not supported for Multiparty license?

I have cleared the error of zone mismatch,snmp community and the conference layout.

I have set the video content  to 360p... with 720p,5fs. According to the  TS data sheet , this content is 1screen per 4 calls. Since i have 4 screen license,it should have 16calls which means 16 participants.

The status of my telepresence shows 3 calls for 3 end points

[Patrick Sparkman]

You can schedule more than one conference with screen licenses, your only limit is the amount of screen licenses you have will determine the total number of participants connected at once regardless of the number of active conferences.  It can be confusing, I know.

360p30 video + 720p5 content is .25 screen license per participant (what you see in the data sheet is fractions, so 1/4 = .25), which means you can connect up to 16 participants at once.

Can you provide a screenshot of your conference template.

[collinks2]

Hello Patrick,

i think am getting you now. Assuming my screen license allows me to connect 8 participants at once in a conference and i split it into two as follows :

Conference A.................4 participants

Conference B.................4 participants.

Then conference A and B can be scheduled at once.

However,if try to add another participant,the no will be increased to 9 since am limited to 8. see attached the screen shot of the conference template.

I want to ask if it is possible for users to dial in when TMS is installed .

[Patrick Sparkman]

Disable "Allow Multiscreen", unless you actually have multiscreen endpoints, you should set this to disabled.