Composition of MCU 8510

Similar Questions

• Reset a password MCU 8510

  Hello

  I need to reset the password for administrator MCU 8510, steps to this process.

  MCU 8510 version 4.1

  Kind regards

  Oscar R.

  Hi friend

  If you have forgotten your password for your Cisco acquired TANDBERG/Codian product that you need to restore the device to factory settings to reset. This will remove all the configuration, including the passwords.

  When you restore your device to factory settings you will need a copy of your activation keys. If you do not, contact Cisco customer support. When you contact Cisco customer support, you will need to provide the serial number and the MAC address of your unit. This information is located on a label on the rear panel of the unit.

  To return your unit to its factory settings and reset the password:

  1. Connect a terminal series to your machine console port using the settings on the label on the rear panel.
  2. Restart the device and watch the output on the terminal of the series. After a few seconds, you will see the message "4.2 (0.36) Cisco TelePresence MCU 8510 (build from 6.17 (0.36))' or similar."
  3. Type reset_config and press enter. (Type reset_password and press enter if you are using an IP gateway. Note This command can be used at any time, not just at the time when the unit is set to zero, and no settings except the details of admin password will be restored).
  4. Type Yes or y and press enter. The device will now reboot again.
  5. When the startup is complete, type status on the terminal series to see the IP address that the unit acquired by using DHCP. Also set a static IP address on the port of a using the static command.
  6. Connect to the web interface of the unit and connect you using "admin" and no password. A warning message on the banner of the web page will tell you that you need a key to activate product.
  7. Go to settings > Upgrade and enter the activation of the device keys. After the activation keys are applied, you will be able to use your device again.

  To change the password, go to the users.

  Reference - http://www.cisco.com/en/US/docs/telepresence/infrastructure/articles/cisco_telepresence_resetting_password_restoring_factory_settings_kb_13.shtml

  Concerning

  Paulo Souza

• MCU 8510 - TMS - SX10 (SIP only)

  Hi all

  I have a question where we have a new SX10 which I added to the MSDS and can make calls to a fine. However when I add it to a conference using the MCU it tells me that the connections settings will change, then deletes all the connections in total of parameters. Addition of 10 other endpoints at the same conference without the SX10 and it works fine (although it is trying to connect on H323 which is fine).

  Why when I add the SX10 at the same conference must kill the connection settings for all units and there is no way to change?

  Why can't I just MCU dial the SX10 via SIP only and the rest stay that H323?

  This is what it looks like before you add the SX10 unit

  capture.jpg

  

  It's what happens after you have added the SX10 and select OK to popup its will change the parameters of connection

  Capture1.jpg

  

  Anyone has any idea why?

  I just did some tests, make sure that the endpoint you are trying to add to the Conference has the same allow incoming and outgoing, planning of the options checked in TMS as your MCU.

• MSD vs MCU recompose the behavior

  In TMS, there is an option, 'Attempts to connect for scheduled calls' and a 'time of connection for calendar (in seconds) calls' of coorisponding.  There is also a similar function within the MCU 8510, "Failed preconfigured participants renumbering of behavior."

  1. Plan us all of our meetings within TMS, how these two systems to coordinate the recall of failed calls and participants, or do at all?
  2. When you use an MSDS, it overrides the MCU Redial function?
  3. As TMS adds all regular calls in the list of preconfigured participants, what callback behavior method would be the most beneficial or practical since it is located in the TMS and MCU 8510?

  'Connection Timeout for planned guest' TMS and the "bis participating preconfigured failure behavior" on MCU service similar recomposition.

  If you use "connection for calls Timeout to demand" on MSDS, then "Failed preconfigured participants behavior redial" on MCU must be configured to as 'never bis.

  For recommendation, if you are investigating CCC and conference log on TMS, recommend to use "Connection for scheduled calls Timeout" TMS as well as you can manage the call log callback instead of wait for the update of MCU call State.

• MSE 8510 TelePresence Server Migration - Issue of license

  I am following the process of conversion to a MCU 8510 into a server TS 8710.

  I ordered and received the migration SKU 0-dollar and have the code PAK

  Part number of top-level

  L-8000-CHLIC-PAK MSE 8000 chassis Licenses PAK PIDs

  Option part number
  L-8000-TSMO telepresence screen Option Migration, order L-8000-CHLIC-PAK

  Key question: will be recorded against this pak:

  1. The SN # MSE 8050 supervisor blade
  2. The SN # MSE chassis
  3. The SN # 8510 blade to be converted.

  There are good docs on the conversion process of loading software and the process.

  But nothing that I could find references exactly what SN # to use when registering the PAK for this process.

  The option TSMO key will apply to the MSE 8000 chassis.

  You are right, that the document is not clear where to apply, but it is also mentioned (very badly) on pg 12, in the section reference to the function keys.

• 8710 GST MSE and MSE 8510 blade clustering

  These can simple questions, but I can't seem to find clear answers to these questions. You can cluster telepresence MCU MSE 8510 blade with GST MSE 8710 blades? And if yes, what version of the software do I need to have each blade running? I'm looking to upgrade our MCU at GST and I want to just make sure I have all the info I need. Thank you.

  Hello Eddie,

  You can only cluster the same blades.  Example, MCU with other 8510 8510 s up to 3 blades and GST 8710 with other 8710 s up to 4 blades.  The exception to this rule is if you are migrating your MCU 8510 to GST blades by installing the MCU to the GST software on the 8510, see Running_TS_Software_on_MCU_MSE8510 on how to do this, so these blades MCU 8510 now becomes and should then be treated as GST 8710 blades.

  All blades that should be included in a cluster must be running the same version of the software.

• How to educate the MCU conferences hosted on another MCU

  Hello

  We have the MSE 8510 and MSE 8710 MCU. The auto attendant is configured on the MCU 8510.

  The Conference is organized on the MCU 8710, external participants connect to AA cannot join the same Conference because the 8510 MCU is not abreast of conferences hosted on a different MCU.

  How can we get the MCU 8510 abreast of conferences organized on the MCU 8710?

  It is not possible to link the two conference bridges.  You mention that when external participants dial in the auto attendant 8710, the 8710 doesn't have an auto attendant.  Why not have dial and then directly to the Conference on the 8710?

• Meeting room PIN in the dial string

  Hello world

  We are eager to apply the pins for the composition in meeting rooms, however for external users, we would like that the possibility for this PIN to be in the dial string, so they did not need to use a keyboard to enter DTMF tones. For example, if a user wants to dial for 1111 meeting and use a PIN of 9999, it would be great if they could use something like [email protected]/ * /.

  Is this possible?

  We're sliding a VCS-control and VCS-highway with a microcontroller of MSE 8510.

  Thank you

  Mark

  Currently, it is not possible to do what you are looking for, endpoints do not know how to call or to handle this type of connection string.  There is another discussion of the question even that says here: composition-codian-mcu-password.  I tried it myself all the time different ways I could think of, and none worked.

• MCU8510

  Hello.. Team,

  We use MCU 8510, whenever we create the Conference through TMS, we are not able to see the name of the site in all of the sites linked to the Conference.

  Please let us know settings must be made alongside MCU to enable the feature.

  Kind regards

  Vikas

  SIP has its own configuration to display name, see Configuring SIP of your endpoint, there should be a "Full name" field

• Telepresence peripheral infrastructure of AutoSave

  I am looking for an option Save my devices of Infrastructure of telepresence automatically at regular intervals.

  Unfortunately the TMS does not support the slot machines.

  MCU 8510

  TS 8710

  IDSN GW

  Conductor

  We have these huge and manual backup is not easy.

  One possible method would be useful.

  You can automatically save the 8510 MCU and TS 8710 using supervisor blade, it saves on the card compact flash.  This is controlled from the supervisor's Web page, select the blade MSE and save then option.  If your ISDN GW is a blade MSE, you might be able to do the same.

  No reviews for Condcutor, sorry.

• Why replace MSE 8510 MCU 4.4 with Telepresence Server (3.1)

  We have a with MCU 4.4 MSE 8510. Looking at the software accessible to the general public, that looks like that I could replace the software with the telepresence instead server software.

  Why I do this? What can I win (and lose) by? I don't have any old CTS systems, just Jabber, MXP and C systems. Is telepresence server software that is actively developed while the old software MCU is not?

  Thank you

  I agree with you, Codian MCU is the best.   =)

  This is why I think Cisco is not going to add MCU multi-screen support, because if MCU multi-screen support, I don't know that all customers would not want to migrate to server TP or buy a new server TP.

  But because of these two main features of server TP, we think about its use, who are the multimonitor support and support for the optimization of the resources with the driver.

  Many Cisco! As always... In this way, they can keep the two products on the market, MCU and GST.

  Paulo Souza

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

• MSE 8510 MCU Chair vs participants comments

  What is the difference between a Chair and feedback from participants, and which is considered to be someone to be a president and another guest?

  I have the following options set on our MCU and no matter how I compose in, even a non registered endpoint that is not on our VCS, I always give me the level of control for users of Chair set.

  MCU type: MSE 8510 v4.3

  In the menu call for Chair: 3 - advanced level

  In the menu request for comments: level 1 - Local

  Thanks, Patrick

  > What is the difference between a Chair and feedback from participants, and which is considered to be someone to be a president and another guest?

  A conference will not begin before the first President of the joints.

  Endpoint to participate as guests (participate in the Conference with guest ID) will see a silent screen black/along with the text of the display "waiting for the Chair of the Conference" and an audio prompt after five seconds, then every minute thereafter.

  Addition to above, you can control the behavior when the last president left the Conference (it's the only when invited remain setting).

  The two options are:

  -All participants are disconnected (default)

  -All participants can continue the Conference until the last of them disconnects (non-action)

• Cisco MSE 8510 MCU - comments PIN does not work

  Hello

  We have a few conferences on 8510 blade. Each conference is the main AXIS and the comments set up PIN. When I dial in the Conference, main SPINDLE works fine but the PIN prompt does not work.

  I tried to deal with the PIN of an endpoint, then the guest PIN from the other end, but the Conference does not accept the feedback PIN. I can use the good main SPINDLE on the two end points.

  Anyone know what may be the issue?

  I just tested this without 8510, no problem at all.

  Can you give us a screenshot of the configuration of your conference?

  I had used the same digital ID for Chair and comments, with a different PIN for each.  When I connected as Chairman, I went straight in.  When I connected as a guest, I went straight in, but I got a quick saying saying President to arrive or to connect.

• 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

• Cisco VCS and composition to an IP address

  I have a question about the composition of address Ip and VCS. In the Administrator's guide, he says that VCS determines that an IP address that will be called if it is:

  -is the IP of a locally registered endpoint

  -Beach one of the subzone of address membership rules is the responsibility of intellectual property

  The second point is that of interest. As part of the way in which it is presented, I take this means that if a subarea membership rule has a range of IP addresses that includes the address of a non-registered endpoint then VCS will still attempt to place the call to the endpoint not registered regardless of the setting "Calls for unknown IP addresses" (under the numbering plan). For example,.

  Assume the end point has (EP - A) is enrolled in a VCS control that is configured to use the mode indirectly for "calls to unknown IP addresses. The idea here is that there is a highway of VCS. Suppose that there is an end point (EP - B) on the internal network that EP - A wants to call. EP - B is behind the firewall, but it does is not registered in the VCS - C. Finally, suppose the SCV - C has a subarea (let's call it "Internal-Unregistered") with a membership of 10.10.10.0/24 rule.

  Now, if the address IP of EP - B is 10.10.10.10 and EP - A dials by IP, will be the call successfully established? Based on the Administrator's guide, the VCS will see the EP - B IP as "known." The Administrator's guide does, really, that the call would be placed. I'm stuck sorta messaging RAS, since EP - B would not be exchanging messages with the VCS - C RAS.

  I also wonder about calls from unregistered endpoint. EP - B could call EP - A directly. I don't want to support this behavior in the design (I recommend rather using the numbering of the URI. I am considering set up the Alias of relief on the VCS - C to channel calls from unknown devices to an attendant on the MCU. Regardless, what I was asking is the following:

  If I have a membership rule subarea as above and EP - B sends a message of call setup to the VCS - C, the VCS - C would still see the call as coming from the default Zone of the local area? The reason I wonder is because of the way the Administrator's guide defines "known IP addresses.

  Thanks in advance.

  Kind regards

  Bill

  Hi Bill,

  to answer your question about the first scenario (where EP at dials the address IP of the EP B), VCS would attempt to place the call if there is a rule of type search 'AnyIPAddress' for the local area on the VCS - C (and assuming that the previously mentioned subzone containing 10.10.10.0/24 exists). VCS would be in this case send a message of CONFIGURATION H225 EP B.

  For the second scenario, where EP B contains the IP of the EP, EP B would send that an INSTALLATION H225 EP EP a. message would then for the message INSTALLATION with an INSTALLATION containing a reason 'routeCallToGatekeeper", instructing EP B to dial the address IP of VCS instead, since the VCS want to be included in the call, signaling path.

  To answer your last question, with regard to the area in which a call of an endpoint not registered (when the IP address of endpoint belongs to a subnet-type subfield) comes on, the answer is that the appeal turns on the default Zone. Calls will be local area if the call comes from a real end point recorded.

  I hope this helps.

  -Andreas