Regular telepresence Conference

Similar Questions

• Licenses of telepresence

  Hi all

  Hope this does not sound very stupid. What is the difference between the following license two of the Cisco telepresence room:

  (1) LIC-MX200-MS - MX200 G2 MultiSite Option

  (2) LIC-TP-SMP-EP - shared multi-party Lic for 1 session simultaneous Inc. 2 RMS license.

  Thanks in advance,

  The Multisite option key is so you can use the feature embedded four-way Conference the MX200 G2, where you can connect up to three other participants without needing a dedicated as a server MCU/telepresence conference bridge.  You can learn more about the multisite functionality in the MX200 G2 data sheet.

  Multiparty license shared for those who have the conductor and a telepresence server, licensed SMP can host a single conference with several participants up to the capacity of the telepresence server.  See the multiparty license - a-ice for more information.

• 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

• Failover of telepresence conductor

  Hello

  We have a conductor & two telepresence conference bridge.

  We are in the phase of deployment & assuming telepresence are registered in the conductor & driver is connected to 10.5 CUCM via SIP Trunk.

  In this scenario, a conductor is a single point of failure. If the driver fails, CUCM will not be able to communicate with the telepresence.

  What happens if the driver goes down? Users will not be able to make Conference calls? To reach the failover can I set up 2 different SIP trunks in CUCM, one for CUCM to the driver & second for CUCM to TP & assign priorities?

  We have a gateway ISDN CTI-3241-GWISDNK9 as well. What is the best place to deploy the ISDN gateway in network? is it connected with driver or CUCM?

  For the planning of conferences, which is also the best place for the costume of telepresence management? must connect with the driver or with CUCM?

  Kind regards

  Francisco

  Hello Francisco -.

  To answer your question: what happens if the driver goes down?

  Because CUCM sees the conductor as the conference bridge, as the telepresence server is located behind the driver, no conference that use the driver would be able to begin to be.  It would be the same as if you were using TelePresence server directly with CUCM and it should fail, no conference using the TP server would be able to start.  The same would apply even if you have used the TMS.

• Telepresence server, control assets drops Conference after 30 seconds

  Much of community support.

  I have the following Setup:

  10.5 (1) version CUCM

  Conductor of telepresence Version XC2.3

  Telepresence Virtual Server Version: 4.0 (2.8)

  EX60 TC 7.1.4

  Cisco 9971, Firmware 1.0000 SR1

  Some other phones (7962, 6941)

  All the end points are saved to CUCM.

  When I do a conference appointment without active active control, everything works fine.

  When I activate the active control (according to ActiveControlDeploymentGuideR3.pdf) the Conference ends after 30 seconds.

  the Conference ends even if I have only one participant at the Conference and any of the phones that I use.

  In CUCM, I configured the relevant parameter in the SIP profile (according to ActiveControlDeploymentGuideR3.pdf)

  on the EX60 I use Active Control, so I see the list of participants and I am able to change the layout of the Conference within these 30 seconds.

  any ideas why this happens?

  the journal of the conductor shows nothing statement

  the telepresence server log looks like this:

  327	14:17:09.170	APP	Info	Conference "8080.MeetMe_mtg' created
  328	14:17:09.264	SIP	Info	Incoming call on 192.168.33.xxx:37124
  329	14:17:09.264	APP	Info	"' Call 24: incoming new SIP call of '[email protected] / * /"
  330	14:17:09.379	APP	Info	Call 24: 'Buero_EX60_Test' has now joined Conference "8080.MeetMe_mtg".
  331	14:17:09.386	IX	Info	Call 24: no encrypted connection to 192.168.xx.xx:31135 for protocols: ping, xccp
  332	14:17:09.814	CMGR	Info	Call 24: ActiveControl negotiated
  333	14:17:46.736	SIP	Error	Call 24: end of appeal because INVITE it transaction timeout
  334	14:17:46.736	CMGR	Info	Call 24: disconnection, '[email protected] / * /"-timeout.
  335	14:17:46.736	APP	Info	Call 24: shoot call them "Buero_EX60_Test" - destroy at request end. timeout
  336	14:17:46.736	SIP	Error	Call 24: BYE transaction failed because the network error
  337	14:17:46.740	SIP	Warning	Cannot determine the destination for the incoming message transaction
  338	14:17:46.741	SIP	Warning	Request received from out-of-call
  339	14:17:48.989	APP	Info	Conference "8080.MeetMe_mtg": deleted via API (not of participants)

  Journal of the conductor, it seems that CUCM closes the connection to RE-INVITE during the transition between the lobby.

  There are several possible reasons, but the best way to determine "why" would be to open a track on CUCM.  More precisely a SDI/SDL (are later versions of CUCM SDL only) track on the CUCM 10.0.2.52 node.  Search for RE-INVITE him entering the IP phone and examine the lines of nearby log for some reason why.

  Alternatively, you can try a few other things:

  #1: Look in Service CUCM settings in the editor, then Cisco Call MAnager to the advanced parameter 'Maximum incoming message size' (there is an Advanced button, you must click above to expose this setting).  If you upgraded your CUCM from an earlier version, this value may need door to 11000 to manage RE-INVITE him to the conductor.

  #2: try disabling the Protocol iX on the SIP, conductor profile and the alias of the meeting of the conductor.

  MP.

• No conference active on driver of telepresence

  Hello

  Can you help me with a problem with the driver of telepresence, the problem is that I can´t see active special conferences Telepresence driver when I do an ad hoc a C40 conference, it seems that is using its own resources for conferences because I can only add 4 participants and the fifth participant is audio only. I think that driver telepresence will not take place on videoconferencing. Teleprecense conductor conference bridge is registered with CUCM, I added a MRG and MRGL is applied to the C40. I hope you can help me with this.

  Kind regards.

  OK, maybe that's your problem. The Multipoint should say MediaResourceGroupList or MRGL. I think its because of the TC version you are running. I would consider going later and try again.

• Language of conference Cisco Telepresence Server

  Hey community...

  I have a request for a German text within conferences...

  for example "you are the only appeal to this conference.

  Telepresence conductor (Version XC3.0.3)

  Telepresence Server (Version 4.1 (2.33))

  does anyone have any advice for me?

  Thanks :)

  Hello

  These messages can be configured by using the advanced > settings customized in the conductor model.

  I would recommend something like:

  {"customOnlyVideoParticipantMessage": "German insert here", "useCustomOnlyVideoParticipantMessage": true}

  The complete list of the attributes that you can configure is available on page 57 from http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/ts/...

  Kind regards

  James

• Failed to create the Conference on virtual server of telepresence

  Hi all

  I installed Virtual Server of telepresence and injected the LIC-AES-VTS-PMP-K9, LIC-VTS-PMP-INTOP, LIC-VTS-PMP-K9-LIC-VTS-PMPUWL-1SL. I wonder why I can't create the conference room. When I access the Conference menu, there is no button to create the Conference.

  Thank you.

  With virtual Server of telepresence that you will not be able to manage or create conferences directly on the server TP, you must use the conductor to create and set up conferences.  The virtual server TP is identical to the pluralistic media 310/320, to see how the virtual model differs from other models TP server, they are listed in the Cisco_TelePresence_Server_on_Virtual_Machine_Release_Notes_3-1 xbottom of pg 2.

  To learn more about the managed mode remote TelePresence Sever in use with the conductor, you can learn more on this subject in the Cisco_Telepresence_Server_Release_Notes_3-0_2-48, pg 2.

• Conference of ad-hoc using telepresence virtual server and conductor

  I'm working on the implementation of a system of telepresence with 10.5 CUCM, telepresence Server version 4.2 (4.18) and telepresnce conductor version XC3.0.3 (both are installed on a virtual machine), I tested with a Codec SX80 with phones and telepresence 60 model 8941 SpeakerTrack.  I have some doubts about the features out.

  When I created an ad hoc conference and a third participant, this last participant's audio call only.  The conductor, I have 5 alarms and don't know how to fix them, look at joint file, talk about each alarm:

  -Alarm feature encryption key, there is a guide that is not clear to me using a Windows Server, is there another guide for this?

  -Alarm of telepresence server capacity which depends on the license?  I only have a single screen license

  I appreciate all the help that could help me solve this problem.

  Kind regards

  Juan Carlos Arias

  LIC-SW-EXP-K9 is your series Expressway.

  I don't know the part number for the telepresence server encryption key, but I think it is $0, you should be able to send [email protected] / * / and if you don't receive a PAK that he asks for it.

  Your conference models look correct, don't know what the problem could be just the hand.

  Multisite option key is not required, it is to allow the microcontroller embedded on the endpoints, for example your SX80.  In this case, you use driver with a server of telepresence to host conferences, so it is not necessary.

• Presentation Conference custom conductor, telepresence Server

  I am trying to set up a layout custom Conference, through layout of custom settings of my conductor (according to the model of the Conference), as shown below

  I can't seem to change the layout of layout custom default "5".

  I have the settings customized according to the guidelines below and restarted the driver after the changes have been made; no luck

  I followed the instructions as indicated

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

  capturecond.jpg

  

  {'customLayout': '39', 'customLayoutEnabled': 'true', 'newParticipantsCustomLayout': 'true'}

  conductor version: 3.0.3

  The telepresence Server version: 4.1

  Hi Dennis,

  You are right that the GST has 4 conference layout options.

  -Jonathan

• How to manage the assets Conference on Telepresence server controlled by the conductor

  Colleagues, Hello.

  How to add additional participants to the already begun scheduled conference or permanent on Telepresence server controlled by the conductor? Or so... How to make the call to the Conference on the telepresence server controlled by a number of additional connected participants of the conductor?

  I do not know the TMS, but I do not see active conference control features in its options. On the telepresence server, there is limited management capacities.

  A driver controlled TelePresence server has no conference control what so ever, as its all managed by TMS. In TMS you use Conference Control Center under surveillance to manage the scheduled conference. Conference ad hoc permanent that's not demand through TMS, endpoints will have to deal in itself.

• Video-conference using SX 20 and telepresence ISDn device link

  Hello

  I have a cisco SX 20 and device connection isdn telepresence device. the procedure via below I have configured and coupled unit SX and telepresence

  Step: 1

  address configured static Ip add via remote control.

  Step: 2

  using static ip, I have connection to the SX 20 device, using the browser. (ip 10.1.1.2)

  Step: 3

  Configuration--> devices--> manage ISDN link--> click--> click combined with research

  Step 4

  In ISDN configuration of the link--> I have ISDN numbers entered the repertoire. Subsequently, it works fine.

  Problem:

  End of test, cancel us the twinning of the device and restart the SX 20. Subsequently, we are unable to pair the device of telepresence.

  While click Display message (No. DEVICES DETECTED) the search button.

  Please share the solution on an urgent basis.

  Thanks in advance.

  Rgds

  Vetri

  Did restart the ISDN link solves your problem?

• How to get the video conference on the two HDMI ports simultaneously in the telepresence codec sx20 o/p?

  I tried to get video output in both output HDMI port SX20 codec, but when I'm on one device to the other display is turned off, so my question is, I can't exit on both screens at the same time? If so, how?

  Hello

  First of all what you should check that the "videos > monitors: role" is set to Dual and you can then configure the output HDMI mode primary, secondary or presentation only.

  This can be done through the WEB user interface or via the CLI over SSH

  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/endpoint/quick-set...

  If your search "Video monitors" in this document, you will see the orders if necessary.

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

• Presentation of the action does not work during the Conference

  Hello world

  Here's the background
  -CUCM 10.5
  -Telepresence conductor XC4.1
  -Telepresence Server (VM) 4.2
  -Endpoint: MX300

  I have problem when sharing a presentation at the Conference meeting.
  It doesn't seem to work.
  However, the part of presentation works with success during a normal 2-way call

  I read an article by cisco,
  http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/con...

  A field is related to the function of presentation,

  Allow the content
  (Available when the preference of Service has a type of telepresence MCU Conferencing Bridge)
  Whether or not, participants will be able to send video content, such as a presentation.

  Yes: one lane will be reserved on each cascade TelePresence MCU and TelePresence MCU primary specifically for content. Use this setting to enabled WebEx conferences.

  No: the participants will not be able to send content, regardless of the number of ports available on the MCU. Content can always be displayed, since some end points provide content in their main video channel.

  The default value is Yes.

  Need MCU allow sharing feature? or I missed something?

  Thanks in advance

  Sam

  Allow that content is available only when the conference bridge is an MCU and does not apply to a server of telepresence.  The only thing you need to do within the Orchestra, is ensure that "content quality" within the model of the Conference is not set to 'Off', see the top of pg 61 of the guide that you have linked to your post.  Also, make sure you have enabled on the SIP Trunk to driver in CUCM BFCP.