Alias of random conference in TMS

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

• Conductor BBFRR planned Conference in TMS - granularity alias missing

  Hi all

  I've been supported configuration for regular calls of telepresence with driver X2.1 and TMS 14.2.2.

  Everything is fine - the only thing miss me, and I wonder about is regex support to the boss of the Alias in aliases for telepresence driver tab in TMS.

  The only variable that actually "is" is the % sign. It corresponds to the 5 channels of digit numbers starting with 10000.

  Is it possible to use 'normal' regexes here as in CUCM bosses or VCS search rules?

  I wish I could write an E.164 range has for example, as [email protected] / * / or

  40955511\[email protected] / * / -while I have 100 alias in this form.

  So far, all my efforts proved fruitless, as everything that I entered as a model of Alias, ends with a completely ridicilous regular expression on the far right, which makes me think of nothing is supported except the % sign. A way to change or modify it?

  Support of all thoughts of eut or TAC?

  Anyone with a similar experience?

  If it doesn't "stick" I guess I'll have to find an exotic way to the use of models of translation.

  Another question:

  With BBFRR, this alias tab alias PTC Conference is one that is driven by XML endpoint?

  Thank you

  Mihail

  Hi Mihail,

  In TMS 14.1 and 14.2, it is hard coded as '%' grows to 10000. However, this was changed to 14.3, which will allow us to release later in July. The draft of 14.3 release notes:

  

  Kjetil-

• 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.

• 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

• 5320 MCU in TMS - booking Conference

  I have a new 5320 MCU configured and managed in the TMS.  I can create a conference directly on the MCU, add participants, and it will dial a number and join the participants to the call correctly.  However, if I try to book a conference at TMS by selecting the participants and resource MCU, MCU does not connect endpoints for the call.  If I look at the details of calls that it said shows the following.  It's like he is waiting for the client to call the bridge, not the MCU outbound calls to customers?

  Participants will connect using this route:

  Customer MOVI ==> Bridge

  Hi if it is customer movi you attempt to dial, you must assign the automatic Conference connect and then add outgoing call participants where you type the movi/jabber address manually. You can see the connection setting tab before saving the Conference to see how the call will be set up (if the mcu expectd the customer allowing to switch or the mcu dial out). Customer MOVI has not automatically as regular endpoints generally have for the SCM cannot guarantee the call will implement.

  /Magnus

  Sent by Cisco Support technique iPhone App

• 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

• Issue of booking TMS

  When we booking the meeting via the TMS,

  How can we get the E.164 Alias of conference?

  (Except we see that conference mcu status.)

  Sometimes need to provide some temporary participants.

  

  Thank you!

  Do not know the 5330, but I suspect THAT TMS will treat it the same way as it does our 4520, so three ways; either add a participant to the Conference as "entering", in which case the E.164 Alias appears under details of connection for this participant, or; go to control Congress centre, find the relevant Conference, place your cursor on the details of mcu under "Remote" (far right) and you will see a window that lists all the details of mcu, including the E.164 Alias for this conference.

  Third option would be to make the 'public' Conference and let the participants dial to the auto attendant and then navigate to the Conference here.

  /Jens

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

• TMS 14.3 - PIN is not required for endpoints imersive

  Hi people,

  I am facing a strange with TMS 14.3 + driver problem XC2.2 + TP Server 3.1. This is what happens:

  Schedule us a conference in TMS conductor like MCU, click an alias that points to the server TP conference bridge. The Conference has a self-generated PIN 6-digit. We use the type of conference "No connection", where all participants must manually dial into the Conference and insert the PIN.

  Well, when at the request of conference starts, all participants can join the Conference successfully using ID number and then insert the PIN code. However, for the endpoints imersive telepresence (CTS 3000), when the user dials the ID number, it is connected to the conference without having to insert the PIN, TP Server don't ask the user to insert the PIN, endpoint imersive is automatically connected to the Conference after dialing the digital ID.

  I have no idea why this is happening, and I confirm that this happens only for CTS 3000, the same problem does not occur for 500 CTS, for example, which is registered to the same CUCM with the same version of firmware. Extra points that I realized:

  • This problem seems to be related to MSDS. Because, if I create an alias Chief conductor associated with a model of the Conference which has applied the PIN, so the problem does not occur. All the endpoints are required to insert the PIN, 3,000 CTS. But when planning through TMS, the problem occurs.
  • The problem happen if the CTS 3000 is selected in the list of participants when planning or not. In addition, no matter if the CTS 3000 is the first, second or last member to join the Conference, the problem always happen in any time.
  • No matter if I use Conference alias set of a driver to be "imersive" in configuration of TMS or alias of the common, the problem still occurs.
  • In the web page of the server TP, I can see the Conference he indicated "PIN protected" information

  Everyone here knows about a problem like this before?

  I'd appreciate any suggestions really.

  Concerning

  Paulo Souza

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

  CDETS ID is: CSCum29993.

  VR

  Patrick

• Questions of permanent conference MCU 4501

  Hi, I've created several permanent conferences on MCU.

  Permanent Conference sometimes appear as finished. Operators of swear that they have not finished their manually.

  Also, then I put the Conference, by changing its properties and 'permanent' checkbox control, he suddenly starts to all former in conference, even if there is NO preconfigured participant.

  This caused a lot of havoc and disruptions, by calling the BIG BOSSES and so on.

  Any suggestions?

  Software MCU:

  Version	4.3 (2.30)
  Variant	6.18 (2.30)

  Yes, it's what I expected to happen. When you add participants to a permanent conference using TMS, they are added as preconfigured participants, but TMS never deletes them. See bug CSCtr35038 for more information.

• Meter "Remaining time" on page Conferences MCU

  Hello!

  During the planning of a conference at TMS involving a MCU, once the Conference begins the time remaining, such as expressed in the MCU is 15 minutes more than what you have planned.

  Is it a kind of fill that TMS sends to the MCU, a bit like TMS as one endpoint in a special appeal as being occupied for the next 5 minutes?

  This is seen in the following combinations: TMS14.3 (beta) / MCU 4.4 (3.54) & TMS13.0/MCU 4.3 (2.32)

  Thank you!

  Hello

  It is in fact be design. TMS does like that to ensure that MSDS is the tearing down of the Conference; We do not want the MCU to demolish SE for example if there are subtle differences between the MCU and TMS.

  Kind regards

  Kjetil

• TMS 14.3 - auto connect problem - multiple call attempts

  Hi people,

  I have a client with an environment with TMS 14.3, conductor XC 2.2, VCS 7.2.2 TP Server 3.1 and CUCM 8.6.2. They have several items on VCS and several endpoints of CTS/TX registered to CUCM Cisco and Polycom endpoints. There is a trunk SIP between CUCM and VCS. Conductor is integrated with VCS by using the B2BUA deployment model. TP server is behind the driver used as multipoint resource only for conferences scheduled through TMS.

  We are having problems when planning a Conference at TMS using type "Auto-connect" and setting driver to dial a number to the selected participants. For some end points when the meeting starts, conductor made several calls try to participants, even after participants answering the call. For example, conductor connects to an endpoint 3000 CTS, CTS answers the call and connect to the meeting, but a few seconds later, conductor's call another attempt at the endpoint, then endpoint answers the second call and put the first call on hold.

  This problem occurs for the following parameters:

  • Endpoints of Polycom HDX series
  • CUCM items of endpoint CTS/TX
  • Outside dial participants (those selected on the tab 'External' to the planning page)

  The problem does not occur for any endpoint TC registered in VCS.

  As a troubleshooting step, the client was trying to configure TMS to try to connect to the participants once (using the "Attempts to connect for scheduled calls" setting value 1), but the issue still occur.

  Tomorrow, I'll be on the customer's site to check if this strange behavior has been generated by TMS or by the chef himself. I really think that it is some sort of bug. I don't know that their environment has been configured properly according to the Cisco documentation, because I was the person who made the project.

  I'd appreciate any suggestions really.   =)

  Thanks in advance.

  Paulo Souza

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

  Hi Paulo,

  a few days back we had seen this problem and I filed the bug "CSCui90143."

  Currently, we anticipate that this problem occurs because the MSD is not able to understand the message of feedback from the conductor.

  I hope that clarifies. I don't have to if you want to be able to access the bug or not.

  Rgds

  Alok