Conductor BBFRR planned Conference in TMS - granularity alias missing

Similar Questions

• Why the MCU is automatically added to the conferences in TMS?

  Info:

  Endpoints: Tandberg 6000 MXP & 95 MXP

  TMS: 13.2.2

  Codian MCU 4510: Software version 4.4

  Tandberg GK: N6.3

  Tandberg BC: Q6.3

  When I create a conference at TMS and want an end point to compose our system to an MCU on another site (confined), the our local MCU is automatically added to the Conference, for some reason any.  For example, if I create a conference with room 123 and number 'Dial Out' external 2222222, TMS adds MCU of our system and forces to compose both room 123 and 2222222, which is totally useless.  This should be simply, what is the endpoint is, a direct line to 2222222.  Why the MCU is being added?  This will use licenses MCU in haste when it is not necessary at all.

  I went through TMS > administration tools > Configuration > General settings, network settings and conference settings and cannot understand why the MCU is added.  If we dial manually, no problem.  My goal is to automate the entire composition, however.

  Pointers?  I put some of the parameters of the TMS > Admin Tools > Configuration > Conference settings below.

  

  Luke

  Hello

  Reduce the bandwidth of conference help? TMS could add a MCU if it detects that one or more participants do not support the bandwidth conference.

  Kind regards

  Kjetil

• Alias of random conference in TMS

  I am using TMS 14.6.0 + GST 4.1 + driver 3.0.2

  Anyway is to create a conference with an alias at random?

  In fact I use the current incremental alias, but I would use the prefix + random alias in order to secure my solution. Any suggestion?

  The only way is to use one alias incremental, where TMS will use the first available number in the range that you define to use in settings of drivers as soon as the booking of a conference.  It's not a way at this time to the TMS to pour the alias random product or not repeat an alias used previously.

  It has grown over the years by several people to ask questions about such a feature, be able to use the digital ID random or non-recurring, but I don't think that happened anywhere.  This is a discussion about this a few years back.

  How-avoid-Numeric-ID-Repeating-MCU-based-Call-when-Scheduling-TMS

  If this is something you want, contact your account manager and see if they can open a feature request for you. I would be and a few others that would be + 1 know the request.

• Planning of the TMS/head of Orchestra/CUCM

  Hi guys,.

  I'm usually confused as the scheduling how works between CUCM (CM) and Conductor (TC).

  Current configuration:

  CUCM: 10.5

  Conductor: XC3.0.2 and I have lot of vTPS and MCU

  TMS: 14.6.2

  Ad-hoc and Renedevous works between CUCM and conductor, but I can't find any reference (blind) how intergrate CUCM and conductor.

  I currently use the SIP Trunk for appointment to call Schdeuled numbers, it works but once I try to create and trunk identical sip rather by sending to the actual ip address of drivers instead of the virtual IP address, I get the below error:

  Thank you guys.

  Event = "a request arrives on an IP address that is not configured as an appointment or ad-hoc IP address".

  Hello

  You must add two IP address under location, ad hoc and other conference for appointment.

  You must create a SIP Trunk of CUCM to address IP Rendezvous for video calling Rendezvous.

  Create one SIP Trunk, the other pointing to the Ad-hoc IP address and then map it under the conference as resources of ad-hoc conference bridge.

  Steps to follow:

  Go to system > network interfaces > IP and then add two IP address in the same subnet as the IP address of a conductor.

  Refer to page 35 of the document below.

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/con...

  Now go to go ├a Conference Setup > locations.

  Map IP ad hoc for the Ad Hoc conference settings.

  Same map IP address of appointment for the conference date settings.

  See page 38 and 48 of the same document.

  Note If you select the type of conference both under location then under the same place, you will get two ad-hoc and option address IP Rendezvous.

  Kind regards

  RACLOT

• Conductor / vTPS - special Conference multi-party merger fails

  Hi all.

  I installed this same scenario several times for other clients without previous problem.

  When you try to merge the 3rd participant VC, the merge fails. The message "Unable to merge" OSD endpoint

  Conductor dialed says"disconnected B2BUA call on penetration saying"Timed out waiting for the acknowledgement.

  The current environment is:

  Conductor: 4.2

  Virtual GST: 4.3

  CUCM: 10.5.2

  MX700 & MX300: S/W CE8.2.1

  Newspapers of a conductor has the below

  016 08 - 08 T 12: 59:33.425 + 10:00 conferencefactory.controller: Level = "INFO" Event = 'a conference has been removed." Conference_name = "0010351100040x5c57e406b51ad5c4" Conference_unique_identifier = "c9c8420c47ef8d873abbf138adbf3e5c8b0931b3" Conference_bridge_address = "10.244.200.242" Conference_bridge_conference_name = "0010351100040x5c57e406b51ad5c4" Conference_bridge_UUID = "57212b6d-5ba2-4b48-a7d3-68e4693be648" elements UTCTime = "2016-08-08 02:59:33, 425"
  2016-08 - 08T 12: 59:33.218 + 10:00 conferencefactory.controller: Level = "INFO" Event = 'a conference has been marked for deletion." Conference_name = "0010351100040x5c57e406b51ad5c4" Conference_unique_identifier = "c9c8420c47ef8d873abbf138adbf3e5c8b0931b3" Conference_bridge_address = "10.244.200.242" Conference_bridge_conference_name = "0010351100040x5c57e406b51ad5c4" Conference_bridge_UUID = "57212b6d-5ba2-4b48-a7d3-68e4693be648" elements UTCTime = "2016-08-08 02:59:33, 218"

  Any ideas would really be appricated. I've enabled diagnostics logging, but don't see anything in there that I can identify as being the issue

  Hi, I had this problem today as well. We have solved the problem by changing a timer to the default value.

  Could you please check the following Service parameter:

  SIP message size entrants Max: 11000

  Please see the following link for more information.

  http://www.Cisco.com/c/en/us/support/docs/conferencing/Telepresence-Serv...

  See you soon!

• TMSPE Dial Plan Configuration in TMS

  I work on the migration of TMS Agent legacy at TMSPE, and I noticed the following in the commissioning of TMS options:

  Note: Video Address Pattern and Device Address Pattern must be configured for  provisioning and FindMe to function properly.
  

  I am use to the legacy fill method only in the device URI to create the video address SIP that we use.  However, how can I go of this unique method of configuration to the new address TMSPE, and that each of the new address types are if they were separate or the same?

  Thank you

  Address of the video is the FindMe address, the address of device model is, well, just the address of the device; that is the address of JabberVideo (Movi) users. The address of video template is used only if you use FindMe, otherwise not.

  See: https://supportforums.cisco.com/thread/2179099?tstart=120

  /Jens

• Question TMS and conductor - conferences to improve safety by using conference

  Hi people,

  Currently, I implement some projects involving Cisco Telepresence conductor and I was wondering the benefits that conductor brings to the video network, it's really a great solution!

  Discover the benefits of the conductor, I created the following deployment:

  

  It works very well! The customer is very satisfied with the level of security when using this deployment. Their multi-point conferences is safer now.

  Well, when I created this topology I considered not how the environment would work when planning conferences, with TMS and conductor because this client has yet to TMS. Then, I was just shocked when I opened the TMS deployment guide e conductor and find the following statement:

  Note: The exposed conductor TelePresence conference type is not supported in Cisco TMS. Only models conference using the conference meeting type are supported.

  Page 13 - http://www.cisco.com/en/US/docs/telepresence/infrastructure/tms/config_guide/TelePresence_Conductor_with_Cisco_TMS_Deployment_Guide_XC1-2_TMS14-1.pdf

  I almost jumped the bridge... Now, I know that my great topology no longer works with TMS.

  Well, here are my questions:

  Why do we have this limit?

  That Cisco plans to fix this?

  The guide is related to the conductor XC1-2 and 14-1 TMS, something has changed in TMS 14.2.2 and XC2.1?

  I'd appreciate any help really, really!

  Thanks in advance.

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

  Paulo Souza wrote:
  [...] I am wondered the benefits that Conductor brings to the video network, it is really a great solution!

  Agreed! The driver of the telepresence really is a great product.

  Why do we have this limitation?

  Because the feature was never implemented on the side TMS. It was decided that the other characteristics are more important and should be a priority. There is nothing on the type of conference 'Read' which is inherently incompatible with the TMS, but work needs to be done first.

  Examples:

  • The control of conference centre: you will probably see the entries in double Conference if you are using a 'read' conference
  • TMS does not differentiate between the presidents and guests during the creation of scheduled conferences 'Conference' on the conductor.

  None of them are very difficult to solve from a development point of view, but they are not trivial to apply or test either.

  Does Cisco have plans to fix that?
  

  Nothing specific is planned, don't. As always: if it is a problem to your customer, make a request to feature through your account manager or another Cisco point of contact.

  The guide is related to Conductor XC1-2 and TMS 14-1, has any thing been changed  in TMS 14.2.2 and XC2.1?
  

  Conductor XC 2.1 and TMS 14.2.2 is a combination not supported, but nothing has been changed to

  2.2 XC and 14.3 TMS: types of conference 'Read' are not yet supported.

  Best regards

  Kjetil

• TMS - conductor alias reusable

  Hi people,

  I have an environment with TMS 14.3 + XC 2.2 driver. I configured aliases of the conductor in TMS a range, something like 99XXXX.

  Well, according to the documentation and tests I've done, TMS reuses always aliases in this range, for example, if I schedule a conference to happen today, THAT TMS will receive number 990000, if planning a new conference happen tomorrow, TMS will reuse the number 990000, since it became available.

  Is there a way to change this behavior? I need MSDS to use the range before returning to start. Is this possible?

  Thanks in advance.

  Paulo Souza

  My answer was helpful? Please note the useful answers and do not forget to mark questions resolved as "responded."

  Paulo,

  Currently, there is no way to change this behavior. As conferences finishing TMS will come out their identity papers to become available for new conferences.

  Adam

• Conference TMS uses the wrong bandwidth with BBFRR

  Hi all

  I m currently faced with the following question:

  When booking a conference through TMS directly or through Outlook (with TMSXE) the bandwidth Conference when using BBFRR will be set to 1152 kbps regardless of the configured default 4096 Kbps or immersive IP broadband bandwidth in the World Conference of TMS. During a call directly to the conference expected the default bandwidth configured on the endpoint will be used. This brings me to the presumption that it has something to do with the maximum setting of IP bandwidth on each endpoint in TMS (see screenshot). You cannot change this setting because endpoint is saved to CUCM.

  TMS conference settings:

  tms_conference_setting.PNG

  

  Endpoint settings:

  tms_ip_bandwidth.PNG

  

  I have no idea where this parameter, and I hope that someone here in the field can help me fixing this problem.

  It's my current setup:

  -CUCM 10.5.2

  -TMS 14.6

  -TMSXE 4.1

  -Conductor XC3.0

  -vTPS 4.1

  -TC7.3.0 on all the endpoints (MX300G2, MX800, SX10/80)

  Thank you

  Dennis

  Looks like you hit a bug - fixed in TMS 14.6.1

  https://Tools.Cisco.com/bugsearch/bug/CSCus51732

• TMS-> Scheduler conductor calls

  Hello

  I m configuration of a conductor (x3.0.3) with a microcontroller for planning appeals in tms 14.6. Previosly, I set up requires ad hoc and appointment and works very well.

  At tms, I added the conductor, but when I added the alias configuration, an error "unable to connect the driver to telepresence to check the configuration of the alias. I think that the configuration is correct, name, alias boss and priority it s even the configuration of the alias the conductor.

  I read another post but I Don t know if it s mandatory that the bridge, bridge pool and services preferences are dedicated for Scheduler calls. I have only 1 mcu, then I have can´t set several bridge...

  Can you help me add aliases on MSDS?

  Kind regards!

  The match of alias in TMS must be in the format of the actual address, not a regular expression.  The only exception is if you plan to use a variable in your speech that represent the numbers that are filled by a digital ID in the settings of conductor in MSDS.  See tasks 3 and 7 of the guide I linked in the my first answer on MSDS alias configuration ID and numeric base.

  Example of my config TMS and conductor.  Note the {\d{3} in the driver alias correspond to the digital ID 3-digit base where TMS will insert it into the alias instead of the %, which will allow any person handing Chief conductor to match the alias TMS generated since it is adding 3 numbers because of the digital ID.

  • Alias of conductor - (871005\d{3})(@domain\.com)?
  • TMS alias - [email protected]/ * /.
  • MSD digital ID base - 100

  Looking at the alias you are trying to configure, you want to have some numbers inserted into the address represented by \d.  According to what your digital ID base, I would do the following.

  • Conductor alias - 51\d{#}(@domain\.com)?
    • # number must represent the number of digits of your digital card, if you are only using a single digit, and then use only \d and remove the {#}.
  • TMS alias - [email protected]/ * /.

  (@domain\ .com)? helps the driver to match the alias with and without the portion of the field incoming calls.

• Resilliency planning TMS with driver

  Hi all

  We plan to put our cluster 8710 2 blades behind the conductor, now programmed with WebEx conferences are supported. We also add an additional 8710.

  Here is what I intended with respect to the design of driver:

  Service preference

  Hen Bridge 1-8710 cluster

  Marked for planning

  Used for the CMR / appointment conferences only failing 8710 in pool 2

  Blade 2-8710 pool deck

  Unmarked for planning

  Used for only scheduled conferences if 8710 cluster in pool 1 fails

  If an existing scheduled conference is set to start at, say 10:00 and 09:00 8710 at the Bridge Pool 1 cluster fails, conductor forward this conference automatically to the Bridge Pool 2?

  We all want CMR / appointment conferences to automatically use the default Bridge Pool 2 and don't use Bridge Pool 1 if the 8710 in Bridge Pool 2 fails.

  The above version works for my scenario?

  What you have above, is correct for the planning, see example 2 of the planning section of the examples of the conductor with the TMS Deployment Guide.  However, in the case of a failover bridge, TMS does not guarantee that there are enough resources as the secondary bridge is shared with the announcement of conferences ad hoc it is not enabled for the planning, so TMS will monitor not his ability to do that there are enough resources for scheduled conferences.

  Regarding your failover scenario, if a bridge fails, conductor detects this and start to use either the next bridge in the pool or service preferences.  I'm not sure of the time, but it will happen in a minute or two.

  However, you will need an additional service for RMC preference / conferences appointment containing the pools two bridge in order reverse just like what you listed, but in this case, none of the bridges will be marked for planning.

• TMS with a cluster of conductor?

  Hi, would appreciate any guidance.

  I built a group of conductor that I added to TMS for the purpose of planning appeals.

  I'm afraid that TMS does not seem very "cluster aware". All 3 devices (2 drivers + driver managed MCU) appear in the tab MCU, which does ' t seems correct.

  How a failure of conductor is managed by TMS? It is based on the standard MCU failover?

  How managed MCU port count works in a cluster?

  Thank you!

  Clusters of TMS and conductor is not currently supported.

  Sent by Cisco Support technique iPad App

• TMS Video Conference MAster API commands

  I have a scenario where we use the master setting of Video conference in TMS to try to set some parameters in a room that are controlled by a third-party controller.

  So if a site is the master we configure profiles as back camera on the monitor back on the sharing of specific content etc...

  I went through the document of the API to find answers, but I can't find what I'm looking for.

  When TMS books call all of this info stored locally on the codec before the beginning of the call?  So I could query codec to find out if he was master in the next cal...

  I found that the subject of conferences has the info I need, but I don't know how to access it.  I could go in and leave the data I need I think.

  My good that process would be to get the call ID once we first booked and updated the list of session on the codec, then go to the object of the reservation for this ID call and parse the xml file.

  I know it's weird but I am is my correct thought that there is a file object of booking for each call?

  HI Brandon,.

  If I understand your question, you can run the command on a TC endpoint:

  xcommand booking list

  This will provide information about the meeting, as well as the following line:

  * r BookingsListResult booking 1 role: Master

  If it is not master it will say slave

  Hope that answers your question

  Sebastian

• Protocol default conference when booking through TMS?

  trying to set up a conference using TMS to book and add participants.

  the booking works very well, I add my end points + the MCU.

  Conference starts... but endpoints do not join.

  When I look at the MCU - I see that this is a conference H323 - but my environment is exclusively SIP... then do not join endpoints.

  tried to create a model of default conference where I could put the default call Protocol - but I do not see where to set this variable.  Given a task in TMS under MCU settings where I could uncheck the box to allow incoming and outgoing H323 composition... still do not get connected participants.

  Preconfigured participant status

  Type	Name	Status
  H.323	Regional center	Unable to connect to the remote party
  H.323	Florida Regional	Unable to connect to the remote party
  H.323	Texas regional office	Unable to connect to the remote party

  someone knows how to do this?

  Thank you
  Paul

  HI Paul.  If you can verify something for me on your endpoints in MSDS.  Go to systems Navigator and choose an end point.  Once he arrives, click the System tab.  Then click on change settings.  Scroll down and you will see the MSD booking Options.  Uncheck all the other than SIP and Save.

  Do this on the same three endpoints, book again and let us know the result if you can?

  Thank you.

  VR

  Patrick

• Cisco TMS assigns a numeric ID for the MCU Conference Scheduler

  Hey Cisco

  I create a conference planner tms 14.6, the Conference is to create, but the digital ID is not available until this conference began.

  picture attached

  I need see digital ID before.

  I've not being updated to 14.6 TMS, but in 14.4 and I'd be surprised if this had been changed to 14.6, you can specify a system to switch to the MCU, in which case the address is displayed as below in the screenshot;

  mcu2.gif

  

  or, you can find the address by locating the Conference in the conference control center, then place the cursor on the MCU and you should see a small window showing all the relevant address, as seen in the screenshot; below

  MCU.gif

  

  /Jens

  Please note the answers and score the questions as "answered" as appropriate.