TMS - conductor alias reusable

Similar Questions

• 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 & conductor error

  All,

  If you him schedule a conference with the driver on MSDS, I try to add an external connection participating via H323 and I get the following error:

  "No possible route the conductor of 1.1.1.1.

  If we change the dial on the SIP protocol and use the same IP address, it works very well.

  What and where is head of Orchestra/TMS checking when trying to add this participant?

  Thank you

  Justin Ferello
  Technical Support Specialist
  KBZ, a Cisco authorized dealer
  http://www.KBZ.com
  e/v: [email protected] / * /

  Hi Justin,

  TMS deliberately rejects H.323 scheduling direct dial-out mode of a conductor, as we can not guarantee that the driver is able to call them. There are no plans to change the behavior, but you can as always drop a feture request via your account manager.

  Kind regards

  Kjetil

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

• 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

• Limit a range of MCU E164 alias in TMS

  Hi all

  I have a port MCU 4501running 4.3 6HD in TMS 13.2.2.  I want to booking of installation using a track of E164 number say 10002 to 10009.  When I created the MCU in TMS it detects that it has 12 ports (6 audio video and 6) and reserve 12 E164 numbers for her!  It is a problem in my scenario that the client was only given 10 numbers to play with 1000 X and I'm reserving for AA 10000 and 10001 for a permanent conference, letting me 8 other usable numbers.  Using a prefix MCU ID 1000 and digital of each conference from 2 I can generate numbers 10000 to 10009 very well.  The problem is that I want more never 1000010, 100011 and 100012 generated that it takes to 6 numbering plan numbers and just used work with CUCM and shortest match composition!

  I saw a MPS in TMS where E164 ports / URI is configurable in TMS, but I can't see a way to limit the range down to a pool of 8 in. for the 4501.  All the fields I want to change in the settings edit view are grayed out.  A look at the MCU itself I can see that you can book ports, but I won't physically be reserved, I just want the E164 alias be limited to a choice of 8 rather than 12.

  Am I missing something obvious here?

  Any ideas or input greatly appreciated

  Gurp

  That's what it should look like:

  

  After 1109, 1110 follows and so on.

  Kjetil-

• 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

• Conductor XC2.2 and TMS 14.3 automatic connects

  Hello

  I've also seen a topic on current versions of beta XC2.2 conductor and TMS 14.3, so I'll post my question here.

  I use the conductor with VCS, CUCM, MCU 4505 and TS. I am able to create ad hoc via CUCM and VCS and regular calls through TMS conferences.

  If I create a conference with automatic connect and the conductor in the call I can see that the MCU or TS tries to achieve a participant, but not with the URI. To use my email address (findme ID) to call me, but instead, it uses strange URI identifiers: [email protected]/ * /: 5073

  1.1.1.1 is the IP address of the driver. On the front part @ I do not know where it comes from, but it looks like an internal identifier.

  These are the logs of the MCU for a test with a participant conference to be connected automatically:

  13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: "Videokonferenz 101" is 13307 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], numerische Favorites auf ID '88800010 '. 13308 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], pine Favorites auf "114". 13309 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Gast-PIN options auf "114". 13310 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], busy 'public '. 13311 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] content mode set to 'convert '. 13312 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [Audio = deaktiviert] 13313 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [video = deaktiviert] 13314 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], Layoutsteuerung uber FECC/DTMF "use FECC and relief to DTMF". 13315 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], maximum Dauer Favorites auf 'permanent '. 13316 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Ende Favorites auf "kein Enddatum. 13317 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] auto remove time limit set to "600 seconds". 13318 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 API-Endpunkt-Einstellungen Info: Endpunkt [e922d880ee1854c242ba94e69b113af: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added 13319 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 Info API-Endpunkt-Einstellungen: Endpunkt [3805: [email protected]/ * /: 5073] via API Conference "Videokonferenz 101" added zu 13320 13:38:36 API admin /HTTP/TCP/1.1.1.1:38149 Info API-Endpunkt-Einstellungen: Endpunkt [3806: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added

  Unfortunatetly newspapers are in German, but I think you can see that there are a few strange added URI.

  If I create a conference without a conductor the log shows the URI:

  13386 14:07:14 /HTTP/TCP/172.21.10.12:52001 Info API-Endpunkt-Einstellungen admin API: Endpunkt [Paul Woelfel: [email protected] / * /] via API zu Conference ' 1234 - Videokonferenz 07/08/2013 "added.

  1.1.1.1 is the IP of the conductor (of course not the real IP ;-))

  Someone at - test the latest versions as expirenced this question?

  Hi Paul,.

  You use the conductor and VCS B2BUA deployment? If so, this behavior is correct. MCU must not call endpoint directly, MCU must compose a unique URI of the driver, something like [email protected]/ * /, so Condcutor will take this URI and route the call to VCS replacing this strange URI of the right destination SIP URI according to what you have planned.

  But to make it work, MCU must not be registered for VCS, MCU should only be integrated with driver, without registration, SIP and H323 for VCS.

  Can you confirm what type of deployment you have? What integration between your MCU and conductor?

  Concerning

  Paulo Souza

  Please note the answers and mark it 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

• Integration of TMS/TMSXE/conductor and Exchange

  Just installed new TMS/TMSXE/conductor for a customer and the initial test was OK but have a question.

  When TMSXE sends the notification to inviting him with the information that the meeting has been scheduled and information to others to call for the meeting, is there a way for TMSXE to also send information to people who have been invited as well?

  The client thinks it would be a pain to make the cut and past in humans invite you again

  If there is somewhere in the documentation that I missed, plase let me know.

  Thank you.

  TMS will not send e-mail confirmation of booking to anyone else that the person who at the request of the Conference.  By the TMSXE user's Guide, the Scheduler will send the e-mail confirmation for guests, or paste its content in the original meeting invitation.

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

• TC cannot connect to TMS on demand conference

  Hello community,

  I sent TCS in our video conference infrastructure and SIP Trunk to CUCM.

  I can do by opening a web session of the TCS for manual registration and dial points endpoint or lectures on the conductor using SIP.

  But if I do the Conference planning on recording of the Conference, the TCS and TMS don't auto connect to the Conference. Registration (SIP URI) alias are configured on TCS.

  I see on the connection of conference TMS setting the driver calls the CHT by using the h.323 protocol but TCS is not registered with the h.323 Gatekeeper. It's using a SIP trunk to CUCM. Is this a limitation if the TCS uses SIP trunk?

  tcs_error.jpg

  

  Thank you.

  ACCOUNT that is configured with CUCM planning only is not supported yet in TMS using the recording during a conference booking. See cisco-tms-cant-schedule-sip-recordings-tcs for more details, the solution is to add the alias to record with a participating entry model or the phone book.

• Conductor create no MCU conference

  Deployment:

   CUCM 10.5 MCU5310 4.5 Conductor XC3.0.2

  I have a CUCM - conductor - MCU deployment and I am trying to set up the Conference date. I can call from end to bridge conference and point, by a busy year and the conductor I see the following:

   2015-03-02T17:27:02+01:00 conferencefactory.controller: Level="INFO" Event="An incoming call request has been rejected because the conference is not present." Conference_name="991115.my.meeting.alias" Destination-alias="[email protected]/* */" Detail="Can not create a scheduled conference. Scheduler must create conference before it can be used" Requester_(VCS/Unified_CM/client)_address="10.10.10.6" Source_protocol="SIP" Unauthenticated_source_aliases="[[email protected]/* */]" UTCTime="2015-03-02 16:27:02,99" 

  I see on the call history

   B2BUA rejected call on the Ingress with 486 Busy Here (Policy lookup response)

  On Journal MCU and Traces SIP I see nothing new, but on the driver of the Conference Bridge status is fine

   MCU (No description available); TelePresence MCU Enabled, Active. Utilisation: 0%

  No idea what could be the problem? i thing conductor to MCU something isn't good.

  Your question would be more place in the section of telepresence to the forums where these devices are more actively discussed in the conferences section you have posted in.  You can move your discussion by editing your message and change the categories at the bottom.

  It seems that you have either the Conference alias or the defined template to not allow incoming calls create the Conference, which means that only a planning as TMS application can create the Conference using the API of a conductor.

  Check the following in the conductor

  • Conference models > [model] > at the request of conference
  • Conference alias > [aliases] > Conference to create

  Also, sometimes people forget to have encryption enabled on the MCU and configured the MCU for the driver to use port 5061.  Which can also cause the Conference to fail.

• TMS CMR model

  Hi all

  If I created the driver model und TMS Provisioning for the personal meeting room, I have the opportunity to create the digital model Alias since then, this model can be generating or also from Active Directory {office phone}

  but the problem I have is that my phone number in the active direcory is stored with the space, I red the

  example is my desk phone: 123 45 67

  My Regex to insert the last 4digit with a prefix:

  \d{1}\s?\d{1}\s?\d{1}\s?\d{1}$

  880145 67

  After that I installed the CMR room, I have the right number but also with space.

  No idea how to remove the space?

  Because the problem is the digital Alias is also the conductor under the same shape created.

  Aatched a screenshot.

  A popular entry.

  Thank you

  Best regards

  Georg

  I'm not able to test it using TMSPE, because our phone entries have a hyphen '-', but try the following regex.

  (\d{2)} (\d{2})$

  https://regex101.com/r/zW9rM2/1

• Cannot add the conductor on the model of CMR TMSPE

  We strive to set up video-conference planning. Conductor and vTS are already integrated. Conductor is also integrated through the trunk SIP CUCM, for both ad hoc and permanent meeting. We were able to add the conductor on TMS as a device and TMSPE CMR model. But when we turn on HTTPS and signed a driver's certificate, unable to connect the driver TMSPE. We tried to create, sign and load the certificate for TMS, but still not able to connect. I hope you can help us. TMS is running on license eval. Conductor is essential and STM have 5 licenses of the screen. I've seen some answers on a few forums about Java version used with TMSPE.

  15.2.1 TMS

  TMSPE 1.7

  Update Java 8 102

  Conductor XC 4.2

  4.3.1.14 vTS

  Have you enabled 4096-bit encryption on the server where it is installed TMSPE by doing the required Java software changes indicated in the Notes of version 1.7 TMSPE? If you do not, TMSPE will not be able to communicate to the driver.

  You mention that you are trying to set up a schedule with TMS and conductor, generated TMSPE CMRS are not able to be used for planning. To set up planning, you need to configure Conference models/alias etc. on driver as well as in TMS, refer to the 'Conference on-demand management' section of the CMR premises Deployment Guide Release 7.0 - primary (for Unified CM) on pg 41.