Gel-presentation SX20 to MXP endpoints

Similar Questions

• Cisco TMS - custom with MXP endpoint command problem

  Hi all

  I have try to disable the RCDO H264 with the TMS custom custom on all the endpoints (to solve a customer problem with lync2013)

  It works for the endpoint of C SERIES but does not work for the MXP endpoint.

  I have try it with this command:

  You have already encountered this problem?

  Do you know a solution?

  Thank you in advance

  Samy

  What version of TMS are you currently using?

  I have TMS 14.3.1, and if you are looking for in models of configuration in TMS under MXP, you should see the configuration item to disable this option for you.

  In any case...

  Off

  May be easier to use the TMS configuration, but the string above should work.

  I hope this helps.

  VR

  Patrick

• Configuration model does not not on TMS MXP endpoints

  Hi team,

  We have a TMS 14.3.1 versioned and also many MXP and C series Endpoints.We was created on TMS configuration model to make the control of end of Far off on each endpoint. We created the model in TMS with the following selection of the 'avancΘs selection' IE Conference Farend of Mode of control in all systems. When we put it on the systems of the series C and series MXP, concluded that the model is working very well with endpoint endpoint C series but not even working on MXP endpoints. We rebooted the system and created the configuration template only for the MXP endpoint with conference Farend Mode control, end of the wrench and Far end camera Control and found doesn't work is not on the system.

  Our all the endpoints MXP are on versions F9.3.1.Please suggested in this

  What role selected must be selected as model for end so that he can work on the MXP endpoints.

  Concerning

  Tarun

  Not 100% sure what you want to do.

  Block the FECC for remote sites cannot control this system or disable FECC on this endpoint

  not being able to control the remote site.

  

  FECC is to disable to get controlled by remote control, the key is to disable the site remotely by remote control.

  If it does not you check if you can set via the api endpoint itself.

  Make a mark on the tms using http to manage could also show you what you use the template.

  If this does not help and you do not get a better answer here and you have a valid

  service contract, consider this escalation to Cisco TAC.

  Please remember useful frequency responses and identify useful or correct answers.

• Question of presentation SX20

  Hi all

  We have a SX20 behaving strange while someone shares/present the contents of the remote location.

  When the remote site is sharing the content first, the local site with the Sx20 is not able to receive the content. To make it work, the SX20 site must share first, and after that the two sites can share content without problem.

  Have a hard time to isolate the problem, we tried to change cables and a factory reset, but nothing has worked. Any help is very appreciated.

  Software version: TC7.3.3.c84180a

  Installed options: DualDisplay

  High definition

  NaturalPresenter

  Thank you

  One-way content is usually a firewall issue.  Have you checked that the firewalls between the two ends are corretcly configured to allow media streams.  With the fact that you can get it to work by opening the ports from one end, sounds much like there is some incoming block.

  Otherwise, we will need a little more detail on the configurations at each end.  Do you have the details on what is endpoint end?  Is that what this SX20 another, or something else?  Call control mechanisms are in place at both ends (VCS, CUCM, autonomous)?  Which protocol of appeal are used (H.323 or SIP)?

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

• Connect the sx20 with polycom endpoint

  Hi guys

  I would like to know if there are special requirements to connect fast sx20 Cisco with other brands of for example, Polycom, Lifesize, Sony telepresence... Customer has 3 locations and now want to replace one with the sx20

  I'm not good in technical issues

  TKS a lot

  You may need the licence Multisite to the Conference, you will also need a public static IP address depends on who's going to make the call.

  other than that just set up the H323 section in the faucet of the configuration and you're ready to go.

• Strange behavior of edge 95 MXP endpoint

  Hi Experts,

  I have a Codec on the client side (Germany), it's an edge 95 MXP with software version F9.3.1 PAL. Every time when I call from my 150 MXP, video calling is disconnected by this Code after 58 seconds. When I make the call of this Codec to my 150 MXP, it's fine. Everyone knows that kind of situation before?

  Thank you

  Jerry

  The difference between incoming and outgoing is usually a firewall - a dynamic firewall will allow the movement of return for outbound connections, but an incoming connection will have specific rules created to allow traffic to the inside.

• Disconnection of call for the endpoint MXP

  Hello world

  We have 1 special issue of one of our series mxp endpoint, where the call disconnects in between it the call, we call for our local endpoint in India on another mxp parameter to the United Kingdom on a dedicated IP link.

  The two endpoints are registetered to a common gatekepper.

  IM attaching the Syslog and Syslog 4 of our local endpoint 3 mxp mxp for your reference, please check the logs & suggest what could be the reason of disconnection of the call here.

  Thanks in advance

  Nikhil

  Hi Nikhil,

  Newspapers showing your EP get no response from the return of unity to end a call is disconnected.

  This problem is the network problem, check firewall, router configuration.

  H.245 Peer H323CC-1 entity does not meet the demands of round-trip time

  H.245 Peer H323CC-1 entity is presumed down. Disconnectiong.

  Kind regards

  Dharmmesh

• Problem with Edge95 MXP and H.264 DualVideo (H.239)

  Hi experts,

  We try to make a MXP Edge95 serve H.264 codec for presentation to Radvision/Scopia MCU using H.323 signalling Protocol and H.239 as standard presentation. But it seems to only use as H.263 codec.

  When the presentation is started from endpoint Edge95 MXP, only main video appears on remote side (except H.263 is used for presentation)

  Presentation at the start of the side remote, only main video appears on the endpoint Edge95 MXP (except H.263 is used for presentation)

  -H.239 is obviously active, all video codecs are enabled (H.263 and H.264)

  -Video quality is set to Motion for main Cam and sharpness for PC

  See attached Wireshark packet captures.

  --

  Filippo Zangheri

  Hello

  This is an expected behavior for MXP. He always uses for presentation h263 / duo video.

  Kind regards

  Dharmmesh

• SX20 call SIP

  Hello

  I would like to know, is it possible to call the SX20 of another endpoint with the address ([email protected] / * /) without registering to VCS

  Appeal of sense as a standalone device at the other end.

  If so, could you guide me.

  Best regards

  Titebiket Mohamed Yatim

  Why do you do this? If its between cisco/tandberg/3 rd party

  equipment and its able to use h323, I would have preferred that.

  Stand alone sip very likely work properly behind the NAT.

  To do this, I highly recommend using a VCS-E

  Not to mention to factory default, it would be just to write what you wrote.

  Maybe you want to set the call by default sip Protocol and also play

  with the DefaultTransport framework for sip, but you can simply dial the ip address.

  Please remember useful frequency responses and identify useful or correct answers.

• How to get out Mcu put snap in the sx20 codec

  As I've attached image, I raised lite snap shot box, I can not MCU snaps into the sx20 codec.

  We use MCU (5300 series), Gatekeeper & sx20 codec as endpoint device.

  I see that the call is using encryption, instant end do not appear if the call is encrypted.

  I do not know what version of the software that you use, but there is a change in behavior for snapshots between TC7.2 and 7.3, see each of the admin guide below for details.  Note that end snapshots are deleted, as well as a new 'notification of surveillance '.

  SX20 Admin Guide TC7.2, pg 19.

  SX20 Admin Guide TC7.3, pg 13.

  There is a very long back and just discuss the TC7.3 release regarding snapshots (link below), but the behavior will change slightly in TC7.3.3.  However, I don't know if end snapshots will come back or not.

  tc730-websnapshots-broken-even-further-design

• Static severe Audio connection endpoint Polycom HDX series

  Greetings,

  I'm looking for ideas on the question.

  We experience severe (and immedate, connecting) levels of static audio when Cisco (SX20 or C40) endpoint connects to a Polycom HDX endpoint.  Cisco endpoints are running TC7.2.1.  This doesn't happen when you connect between Cisco endpoint to an endpoint of Polycom VSX.

  If HDX endpoint connects to a Cisco endpoint, in addition, there is no problem.  This only happens during a call from Cisco to HDX endpoint.  All connections are made via H.323 SIP not.

  All units are stored on the same device of control VCS.  VCS rolls X8.5.1 and shows no errors or questions.

  Any thoughts would be appreciated.

  Thank you

  -TM

  This is a bug in TC7.2.1

  See here

  CSCuq94402

  CSCur78783

  Symptom
  Get a white noise for audio and not video

  Condition
  Use TC7.2.1 and Polycom with software version 3.0.5 and call using H323 with active encryption.

  Workaround
  Disable encryption, call using SIP, downgrade from TC7.1 or earlier version of Polycom or wait for TC7.3.0 and xConfiguration H323 1 encryption KeySize value profile: Max1024bit

  We have disabled encryption until TC7.3.3 is released.

  7.2.1 is originally models C20 revive the call

  7.1.4 has vulnerability shellshock

• Phone type Edge 95 MXP found in CM8.6

  Hi all

  I try to add new phone device in the handler calls 8.6

  However, I can't find the type of phone Edge 95 MXP.

  I need to download any firmware, or choose another type of similar phone?

  Thank you

  Sam

  Hi Sam,

  Unfortunately MXP endpoints are still not supported for registering for the CUCM. Support is available for the series C and Ex-material of the series right now. You can see the release notes of the MXP software for updates in the future.

  Kind regards

  Saint André

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

• CTS update - EDGE95 (MXP) / license MS

  Hello people,

  You can make the difference between:

  L. 95-85-SM

  Order L-MXP-PAK for E-Manager APM Edg95/85MXP Upgrdeto MS

  and

  L-EDGE-MS

  Order L-MXP-PAK for Upg MS for on-board Legacy systems

  * Mandatory update MXP95

  * License APM is required?

  Thank you!

  MXP endpoint has three statuses of option "characteristic".

  (1) standard - no option

  (2) BNP - feature enable APM

  (3) MS & APM - activate Multisite functionality and NPP.

  MXP Endpoint able to configure only one key feature, when you install MS option key, it actually enable APM function at the same time.

  So purchase MS option key does not require to purchase license APM separately.

  Please note, above does not not endpoint C-series.

  C-series installation endpoint support multiple keys and function option able to install multisite (MS) and APM separately option button.

• TMS directory failed in the endpoints of series C after the migration of the device to the virtual computer

  Hi all

  We have migrated the 12.8 TMS from the device to the TMS 13.0 on the VM platform. There is no matching TMSPE and mainly used for management and directory service.

  Once the migration is complete on the platform of the VM, we found that endpoint C-series could not receive phonebook of TMS (while 95 MXP endpoints works very well with the TMS directory).

  The end point of series C, we check the Configuration-> directory server 1: URL. The link is converted from http:// /tms/public/external/phonebook/phonebookservice.asmx http:// tms/public/external/phonebook/phonebookservice.asmx.

  (In addition, we check the authorization of the two phone book page, and there is no IIS issue).

  In the 95 MXP endpoint, it can receive the telephone directory unit VM MSD and MSD.

  Best regards

  Ben

  Hi Ben,

  As confirmed by the curl command - you don't have access to the web page as an anonymous user.  You have to fix your permissions.  One of the fastest ways to do would be to try to reinstall the MSDS on the server again - this should reconfigure the IIS settings required for TMS.

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