Telepresence news

We have the solution of Cisco telepresence into place for about 1 year.  We have a VCS/VCSe/MCU/TMS13.1.2 (old Yes, but we're the upgrade that we have just had our set smartnet at level.  "We were without him a little).

We are experiencing a weird problem with units not being not to place calls after a certain situation (we don't know what causes).

Basically, we get an error message saying that we cannot deliver to the host, but the units themselves, we are able to ping and traceroute, and VCS.

A reboot seems to fix the problem, but I don't think it's practical.  October I'll finally take a class to get a better understanding, but looking for help that TACS cannot understand it or the assigned tech cannot.

03/09/2013-09:55:45 number connection error Source:, number of Destination: h323:172.xxx.xxx.xxx, Code of Cause: no route to the destination

The devices can ping each other and a traceroute works from endpoints and vcs/vcse/tms

IN THE LOGS I SAW CALL REECTED WITH A UNKNOWN REASON CODE RESPONSDE

Also, what causes a call to be rejected with a reason

Now I got it.  =)

Well, if record you at TMS as a room, you leave all the option H323 in white, so that the only SIP information will be imported in the telephone directory. In addition, you can completely disable H323 scheduling for the system, so only one SIP will be used.

It is an example that should work fine:

Do not configure not any H323 field, then you will be able to have directories in TMS for the system with only the information of SIP. Then, when users dial tactile device using phone book, only the SIP URI will be used, so you won't have to dial IP H323 and you have the call is routed to the VCS highway.

I hope this helps.

If it solves your problem, please, mark your topic as replied.   =)

Concerning

Paulo Souza

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

Tags: Cisco Support

Similar Questions

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

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

  • The CTS-CTRL-DVC8 is compatible with the Cisco MX200 G1 telepresence?

    Hi team,

    Please confirm whether CTS-CTRL-DVC8 = (Cisco TelePresence Touch device) is compatible with the Cisco MX200 G1 telepresence.

    Thank you very much.

    Sorry, misread the Gen1 in your message.  Yes, the 8 Touch works with old Gen 1 MX200 of TC software running.  This is mentioned on the MX200 data sheet.  Older hardware (MX Gen1 and C40/60/90) press the 8 only and cannot be upgraded to the new software for THIS.

  • Telepresence

    Dear all,

    I am new to Cisco TelePresence field.

    And I need to learn more about Cisco Telepresence.

    Although I've done projects for Cisco IPT. (CME, CUE, CUCM, CU etc..)

    But I want to learn Cisco Telepresence, can you please drivers myself who study documents that I should follow and where I should start learning this product

    desgin and implementation point of view.

    Your review in this regard will be be highly commendable.

    Await your response.

    Kind regards

    Malik.

    Hi Malik.

    These are some links, which I also use to refer

    http://www.Cisco.com/en/us/docs/Telepresence/cts_admin/cts_documentation_roadmap/CTSdoc_rd_map.html

    https://learningnetwork.Cisco.com/docs/doc-6013

    Kind regards

    Vivek

  • TelePresence VLAN

    We have a Manager Communications Group to serve our PBX.  We recently bought a new telepresence system and a 2nd CM cluster that is dedicated to the CTS.  Telepresence SRND States to put the CTS codec in the VLAN voice. There is no mention of this VLAN to the 2nd cluster dedicated to CM in.  I don't think that we can have clusters of 2 CM on the same VLAN voice then what would be the best practice to set the codec and the cluster of CM for the CTS?  Thank you.

    http://www.Cisco.com/en/us/docs/solutions/enterprise/video/tpendpts.html

    Hello

    It's more a question of CUCM SRND, but based on our CUCM SRND take a look at this:

    http://www.Cisco.com/en/us/docs/voice_ip_comm/CUCM/srnd/7x/netstruc.html#wp1043629

    In general, servers of Cisco Unified Communications Manager (Unified CM) clusters, including the multimedia resource servers, reside in a data center or server farm environment. [...] Because these servers and resources are essential to voice networks, Cisco recommends distributing all servers in clusters CM unified, gateways voice hardware and centralized centralized resources among multiple switches physical and, if possible, several physical locations within the campus. This allocation of resources to ensure that, given a hardware failure (for example, a switch or switch line card failure), at least some servers in the cluster will be always available to provide telephony services. In addition, walkways, and material resources will be always available to provide access to the PSTN and to provide auxiliary services.    In addition to being distributed physically, these servers, gateways and material resources should be distributed between the VLANS separated or subnets so that, if a broadcast storm or a denial of service occurs on one VLAN, not all services and voice connectivity will be disrupted.

    ...

    There is the potential for a large number of devices in a single VLAN or broadcast domain to generate large amounts of broadcast traffic periodically, which can be problematic. A good rule of thumb is to limit the number of devices per VLAN to about 512, which equals two subnets of class C (that is, a class C address of subnet 23 bits masked). Typical access layer switches include the stackable Cisco Catalyst 2950, 3500XL, 3550 and 3750, as well as the Cisco 3560 and the larger, high-density Catalyst 4000 and 6000 switches.

    Note The recommendation to limit the number of devices in a single VLAN of Communications unified about 512 is not only due to the need to control the amount of broadcast traffic VLAN. For Linux Unified CM-based server platforms, the ARP cache has a limit of 1024 devices. Installation of Unified CM in a VLAN with an IP subnet that contains devices more than 1024 can cause Server Unified CM ARP cache fills up quickly, which can seriously affect the communications between the Unified CM server and other Unified Communications endpoints. Although the size of the ARP cache on server based on Windows Unified CM platforms is developing dynamically, Cisco recommends a limit of 512 devices in any VLAN regardless of the operating system that is used by the Unified CM server platform.

    To answer your question, Yes, separate the VLAN for CUCM, not only for clusters, servers (one cluster contains 1 to 20 servers (super cluster))

    Let us know if you have any questions

  • Cannot change the video presentation of telepresence

    When I join a telepresence SX20 one of our WebEx MeetingCenter conferences, we are unable to choose a layout on the SX20. It uses only the small size main speaker (or split screen), with the film strip separate from participants on the lower 25% of the screen. We can press 2 on the remote SX20, or end camera control allows you to select a new layout (it highlights blue), but it never goes to this provision.

    Is there an option in MeetingCenter that blocks the layout to the participants of telepresence? I can't found.

    Am I missing some config somewhere?

    Thank you

    Tony

    Video endpoints will always see participants WebEx within one component, and that they see is based on which is the active speaker, however other connected video settings will be visible within their own separate streams.  You can change the layout of the endpoint using DTMF (2 and 8) or FECC, but the layout changes will only see if you have more than one point of video endpoints connected to the meeting of cloud of CMR.  The control of the layout with the content on the screen, it seems that this provision is fixed and cannot be changed.

  • in how many ways could connect a different company of telepresence?

    Hi all

    I am new in the field of video conferencing and telepresence.

    I would like to know how many ways there are to log to a different company to do a telepresence session.

    Currently I am an infrastructure management of telepresence in which all the other location are 30 Km away and are all part of the same intranet.
    Obviously, we have a VCSC and VCSe and a MCU.

    If I do not have an intranet, and I want to connect to a different location, how can I do? VPN? Is it possible to use only the public internet?

    for example, if I have 3 location (200 km) and each location offers free SSDL (declining from 4 Mbps to 4 Mbps), can I connect them?
    I thought to use for example a VCS Espress starter pack in one place and 3 codec SX20.
    Is it possible to have a 720 p call given the distances?

    Just to add to the comment of the juriss; be sure to include 20% overhead for each call, when you calculate the bandwidth you can use. I.e. for a 768 Kbps call, you will need a minimum of 922 kbps available b & w.

    I would create a separate subfield on the VCS E existing for these systems to register, allowing you to specify the b/w max available within the area, as well as max eligible b & w by appeal. This way you won't have to worry about potential problems caused by a connection at a higher rate.

    /Jens

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

  • Telepresence room adds CTM

    I try to add a new room to use CTM but can't seem to make it appear.  Here's what I did:

    1) created a new codec and phone in CUCM

    (2) using the Management Console Exchange - create new boxes to the letters of room - Site.Telepresence

    (3) in the room mailbox properties add custom - address [email protected] / * / -SIP (e-mail type)

    (4) user account in Exchange for the CTM Manager - tpsuper

    (5) using Exchange Management Shell - assign CTM Manager - tpsuper full access in the calendar folder of the mailbox of room

    Add-mailboxpermission - identity "Site.Telepresence" - accessRights FullAccess-user tpsuper

    (6) set to allow meetings to be placed on the IP phone

    Set-MailboxCalendarSettings-Identity Site.Telepresence - DeleteSubject $false

    Set-MailboxCalendarSettings-Identity Site.Telepresence - AddOrganizerToSubject $false

    (7) approval auto set to on

    Game-MailCalendarSettings - Identity Site.Telepresence - AutomateProcessing AutoAccept

    (8) connect to OWA as tpsuper

    (9) in OWA - open the other box - Site.Telepresence

    (10) to add name to House of Codec - [email protected] / * /

    (11) in CTM - discover the rooms

    There are several other pieces that appear in the MLC, but not the new room that I created.  The rooms of other agents have been created by someone else.

    What did I miss?

    dtom,

    Hello! Have you moved the MAC address of available controlled in the APPUSER? Otherwise, move it to controlled devices and make another discovery of room in the CTM. The endpoint must also be registered.

    jeffkin

  • End of sale (EoS) / end of life (EoL) information on Cisco TelePresence system 1700 MXP

    I have a question about the EoL (http://www.cisco.com/c/en/us/products/collaboration-endpoints/eos-eol-po...) policy and the announcement of EoS/EoL Cisco TelePresence system 1700 MXP (http://www.cisco.com/c/en/us/products/collateral/collaboration-endpoints...).

    According to the policy of the EoL, paragraph 4 ter, "after the first year and for the operating system SW - if available - we will offer bug fixes, versions of maintenance, workarounds or patches for a period of 4 years for operating system software."  Therefore, it is 5 years after the Date of the EoS, which could make the OS support close on 28/02/2017 EoL products.  I'm one to believe that a product and its applicable operating system are good as long as the company provides patches for bugs/flaws.

    My question is about the migration of the product suggestions.  The suggestion is to "migrate to the Cisco EX Series (the EX60 or solution EX90) telepresence system."  However, when the announcement of EoS/EoL EX60 inspection, the "SW maintenance communicated End Date of: HW, SW OS ' 06 07, 2016.  Note that it is not the end of Maintenance SW verbiage in 1700 MXP EoS/EoL announcement.  I'm under the assumption that the new product within OS support only one model exceeded?  Why anyone would follow the suggested migration if I get fewer months support OS than an older model?  Should I go out of date on the announcement of the EoS/EoL, or use the 5-year rule as shown in the end of life policy.

    If I am interpreting this wrong, please do not hesitate to correct me.  I am trying to understand the explicit verbiage in the end of life and ads EoS/EoL policy.

    As the 1700 MXP announcement was published in 2011, at that time, the EX60/90 was a legitimate substitute. However years later, endpoints EX Series are now EOS, you should look at alternatives for the EX series instead.

    The announcement of the EOS/EOL indicates a date of end of software support, you should go there. The reason that ad 1700 MXP does not list one could be that the date of assumption of the software had already spent or they simply don't have the list at the time. Looking at the latest version of the software for the 1700 MXP, it's F9.3.3 in 2014, I highly doubt, there will be another, but you never know given that other points of MXP endpoints that are not past their published end date of software support.

  • Conductor of telepresence on dial

    Hey guys,.

    I'm running into a problem where I can not the conductor of telepresence to dial on a TCS alias record.  I configured a location and a car participant made up, but when I have 2 people to participate in the Conference I never see the driver dial a number in the alias of the record.  I have checked the VCS logs and see nothing.  I'm sure I'm missing something stupid, but any help would be appreciated.  This is a new installation of net.

    Looks like you have a misconfigured port somewhere check your settings bridge conference Chief of Orchestra and conductor in your VCS area, make sure that all ports that you use match as well as the Protocol. The logs show that you use TLS, so you'll want to port 5061.

    Sent by Cisco Support technique iPhone App

  • Cisco TelePresence

    Dear all,

    I am new to Cisco TelePresence, and I want to learn this technology.

    Can anyone share implementation guides or desgin from the point of view of learning.

    I'll be very grateful.

    Kind regards

    Malik.

    Hi Malik.

    Here are some links... However if you are looking for the community you get simillar multiple threads

    http://www.Cisco.com/en/us/docs/voice_ip_comm/uc_system/design/guides/videodg/videodg.PDF

    http://www.Cisco.com/en/us/docs/solutions/enterprise/video/TP-book.html

    see you soon

    Alok

  • Questions of telepresence

    Hi all

    Forgive my ignorance here, but I'm pretty new on the side of Cisco telepresence and video endpoint. I'm not seeing all the benefits by using endpoint of Cisco as the EX90 series DX, etc. on my desk when I could just simply use the computer which is already on my desk with a webcam and Skype?

    I don't see how Cisco trying to establish video endpoints more than that by also introducing capabilities to be used as a second monitor but also to completely replace your landline. I also see the benefits in its use of TeleMed setting as well where doctors can visit patients, I understand that part, but it helps my office is whee I get lost. Maybe it's just a matter of using video to work with your teammates and totally get away using just audio for calls in the future. It really makes a difference.

    I'm just trying to hear from anyone out there who may have been more in this industry longer than me or more exposure with the Cisco vision in this area.

    Making me think! Thanks :)

    Just do an Internet search for telepresence v Skype - you will find many articles on the subject.

    A quick summary would be that it comes down to reliability, Image quality, flow of traffic and security.

    For social interaction (which is the kind of thing that you'd be using Skype for) you are usually not affected if there is the odd audio blip, pixelation, abandonment, logout, etc.  Where that aren't something you'd like to have in a business meeting or business communications.

    A few sample links:

    Wayne
    --
    Remember the frequency responses and mark your question as answered as appropriate.

  • Will there be a new commissioning Guide in the works?

    Hi, I'm looking for a commissioning guide that is updated.  The new Jabber Cisco telepresence admin guide asks the reader to find in my version of TMS Provisioning Deployment Guide.  Now that I've installed Extensions commissioning, I can't find a guide that works.  Maybe I missed it.

    Darren

    http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/tmspe/Install_Guide/Cisco_TMSPE_Deployment_Guide_1-0.PDF

  • Telepresence - administrator password

    We have a client that requires us to change administrator passwords each quarter, and we need to change the password for the first time.

    I wanted to know if we run into any problems by changing the passwords on the CUCM, VCS VCS Expressway, MSE8000, TPS and TCS.

    Are there any traps or order that we follow?

    1. I wanted to make sure that the VCS, CUCM, MSE, and GST will have any issues registering with TMS.

    2. the VCS Cluster will have a problem?

    3. This can affect the OpenDS TMS?

    4. all the problems with TMSXE?  The TMSXE server is managed by another team, and we will not change this administrator login and password.

    Here is the list of the versions:

    CUCM - 8.6.2.2000 - 2

    TMS - 13.2

    TMSXE - 3.0.2.0

    VCS - v7.0.2

    VCS Expressway - V7.0.2

    MSE8000 - 2.2 (1.17)

    Telepresence Server - 2.2 (1.54)

    TC - v5.3

    Thank you

    Bryan Darnell

    Hi Bryan,.

    1. once change the admin password on these devices, you can update the TMS with the new password of the device tab connection from each device so that it can access using the new admin password

    2. There should be no effect on the VCS cluster, because each peer can have a different password for the user "admin".

    3. no effect on replication opends, as this is handled by different accounts

    see you soon

    Karim

Maybe you are looking for