Telepresence: Cisco vs Polycom

My personal opinion.
Both systems work really well; and I'd be happy to highly recommend both.However, as a general rule, the Cisco kit is a bit more expensive than the Polycom. The argument could be made that the difference between the two is that Cisco is a hand made suit and Polycom is off the peg.
It comes down to what your requirements are; you actually may need the Cisco system in order to meet your specific needs. If you don't know what those are, you should really get a second supplier in to talk to you. 

Hi there.We'll be needing a telepresence solutions for our conference room. I'm in the process of evaluating hardware (on paper only, no hands-on expirience) so I wanted to check with you guys. We'd like ot have a solution with person/face tracking/framing, meaning "Eaglyeye producer" (Polycom) or "Speaker Track" (Cisco) and fitting it into our budget.I ended up contacting a Polycom & Cisco dealer who told me that Polycom is years behind Cisco (?), but I'm not sure he was honest with me. Right now, I've narrowed it down to "Cisco SX80 Speaker Track 60" (some $17k) and "Group 300-720p with Eagle Eye Producer" (some $11k). Price difference is big so I'm afraid I'm comparing apples and oranges (am I?). And of course, there is an issue with Cisco having only 30 day warranty and you're pushed to get some expensive maintenance contract...
This topic first appeared in the Spiceworks Community

Similar Messages

  • CTS to Polycom Telepresence using Polycom Infrastructure

    Hello,
    I am trying to determine how to successfully connect a CTS system (TX9000, CTS-1300, T3) to a Polycom Telepresence device using Polycom infrastructure.  I have got this interop to work using the Interop key using a TPS and Cisco infrastructure.  I am trying to see if there is any working model/documentation using Polycom infrastructure only.
    Note: I already have what Polycom says is required. MPMX cards, TIP keys etc.  I am just trying to figure out what needs to be in place along side all that on the Cisco side.  (Polycom cannot give me a clear answer on this. They just say it should work)
    Thank you.

    If you do not have a DMA, you should register the OTX and ATX to CUCM as the SIP registrar.  You can leave the H.323 side registered to CMA if you want to use it for management purposes.  You will need to use SIP when calling CTSs so you can use TIP.
    Upgrade your HDX codecs to 3.0.5.  Your CUCM and CTS versions should work.
    Set up a normal SIP trunk in CUCM and point it to the RMX's signaling IP address (not the management address).  Make sure that the trunk classifies the calls as "OnNet".  This is not the default so you will have to set it in the trunk config.
    You will need to point the RMX to CUCM.  Under IP Network Services, under SIP Servers, type in the IP address of the CUCM Publisher under Server IP Address and Server Domain Name.  Also use the IP address as your outbound proxy server.  Make sure your Transport type is TCP (not TLS).  The SIP Server Type is Generic.
    In the RMX conference profile, set the Line Rate to 4096.  Under Advanced, you should have a "TIP Compatibility" field.  If you don't, you're having a license issue.  Set the field to "Video and Content".
    Your meeting rooms need to correspond to the CUCM route pattern.  For example, in CUCM you could point 5555X to the RMX.  Your meeting rooms should use IDs in the 55550 to 55559 range.
    Thanks, Jeff

  • H323 Video End Point calling Cisco Video Point seamlessly-How to Implement

    Dear All,
    Undergoing following scenario which as per technology should work but not able to implement it:
    1) Components available - CUCM 7.x, Polycom Video Phone (H323) , Cisco 7985 Video Phone , Normal PBX Phone
    Requirement:
    1) To assign a valid extension to all the Phone irrespective of whether it is Polycom, Cisco or PBX Phone
    2) All the phone can talk to each other seamlessly
    In case of PBX Phone= PBX Phone can reach to Cisco or Polycom unit via a PBX gateway. The calls from PBX phone is only Audio as PBX phone are not having Video support
    Polycom Video phone can call Cisco 7985 without any access code.
    Polycom and Cisco 7985 should register with their Valid DN to cisco Call Manger 7.x.
    Any pointer toward the config for implementing this will be of great help
    Regards
    M

    You can't loop anything you want.  You have to plan for it.  Have you planned for it?  The best you can do with it is add a couple of dissolves, then loop it.

  • Mondopad on a Cisco platform

    Has anyone been able to register and use a Mondopad on their Cisco VCS platform?  We have a freebie that would like to be used internally but I have had no luck.  We currently have this as our backbone
    VCS Control 7.0.3
    VCS Expressway 7.0.3
    MCU 4.4
    TMS 13.1.2
    No problems with Cisco or Polycom devices and we also use Jabber Video I just do not want to put too much effort in this if it will not work.

    Hello Dave,
    I have a bunch of these here that I have registered to our VCS.
    The Mondopad Shell that runs has a built in SIP client. Wording for it's configuration is a bit different to what I would expect and some features are still "in the air" however I managed to get them to work on our VC network using the VCS's.
    Some simple things in the clients configuration to note.
    Display Name = alias
    Address = alias@domain
    Register = SIP DOMAIN NAME
    Port = 5061
    Username = user credential to connect to VCS - can't be blank - I have entries in the local database on the VCS for this
    Password = for above - can't be blank
    Proxy Server = SIP SERVER ADDRESS
    Proxy Port = 5061
    SIP Transport = TCP
    SIP Security = TLS
    Encyption = None
    On the VCS side I found it was best to create a Subzone for these Mondopads as I found they had issues calling Jabber unless I did this. Within the Subzone for the Mondopads I have to select Media Encryption Mode to "Best Effort" for calls to be successful.
    I am yet to get these devices to be managed by TMS or to recieve a phone book from TMS.
    I am happy to help or listen to any other ideas you guys have for these.
    I have also written a document and sent it to Infocus in regards to configuration for these on the Cisco VCS.
    Thanks, Craig

  • Bandwidth requirement for voice calls

    Hi All,
    Need expertise advise on the following concern about voice call.
    1. Bandwidth requirement for video call across all other endpoint(using Polycom / Lifesize end point at their end)
        a)Standard Video
        b)1K HD Video
        c)4K HD Video
    2. Plus can we determine bandwidth required for all the following below:
    a. 1 to 1 VC  end point ( Cisco TP – Cisco TP)
    b. Bridge call  ( Cisco TP to Polycom / Lifesize)
    c. 1 to 1 VC end point ( Cisco TP – Polycom / Lifesize)

    Thanks for the info Wayne. I missed out information about the endpoint.
    Client using CTS 3010.  Acoording to datasheet it says 
    11.9 Mbps (1080p, 30 fps best motion handling), 10.1 Mbps (1080p, 30 fps better motion handling), 8.8 Mbps (1080p, 30 fps good motion handling)
    6.4 Mbps (720p, 30 fps best motion handling), 4.5 Mbps (720p, 30 fps better motion handling), 3.1 Mbps (720p, 30 fps good motion handling)2
    My question is does the bandwidth required for both ways or only one way?
    And I'm aware CTS 3010 doesn't support 4K video.

  • I have Cisco TelePresence SX10 and content sharing is not working when I am dialing through the bridge

    I have Cisco TelePresence SX10 and content sharing is not working when I am dialing through the bridge, I can share the content if I drag and drop from RMX, but if schedule the call in Resource manager or manually dial in from device the content is not going to other hand, I have tried to turn off encryption as well but still same issue. can you please help me out with this. I am from Lion co and purchased sx 10 recently.
    regards
    Hemang

    Can you please provide us with a little more information on your systems and configuration / topology, such as, what call control are you using (Cisco VCS, CUCM, other?). what type of "Bridge" are you using (is this a Cisco MCU, or Cisco TelePresence Server, or other device?), what versions of the software are on each of the devices, etc.  The more information we have about your environment will help us assist you better.  But saying that, if all your core equipment isn't Cisco, you may have more luck in the forums for the manufacturer of such equipment (ie Polycom's Support Community).
    Wayne
    Please remember to rate responses and to mark your question as answered if appropriate.

  • Cisco Jabber for Telepresence 4.6.3 Setting for "Webex Telepresence" Cloud Service

    I am looking for the server setting that can be installed into the Cisco Jabber for Telepresence Client (MOVI) that will allow it to connect to the "Webex Telepresence" cloud service.  I cannot find a download anywhere that has the infomation re-configured for the "Webex Telepresence" service.
    Thanks for your help in advance
    Tim
    Well after a few hours of searching i have the Answer
    The Client can be downloaded from: http://download.telepresence.webex.com/MCX/4.6.3.17194/WIN/JabberVideo_4.6.3GA.exe
    This will come with the following setting pre-configured: Sign-in Setting > Internal Server: https://boot.telepresence.webex.com/tmsagent/api/rest/devices/movi/provisioning
    If you have the JabberVideo Client installed and just want to change where it gets provisioned from VCS or Webex Telepresence then you should be able to use your current client and just change the internal server settings and clear the external setting.
    Then you will need to use your Webex Telepresence Login ID and Password.
    Hope this helps Someone.
    Tim
    Message was edited by: Timothy Shire

    A1: Because it can use either (webex or CUPS), there are two deployment modes, all is on the documentation if you haven't gone thru it.
    You type in what it's asking, nothing more. Choose one, and then use the CUPS hostname, DNS is basically mandatory, the PC needs name resolution for all you have configured (VM/CUCM/etc)
    A2: No, it can be IM&P, full UC and phone mode. No, Full UC and phone mode use the PC for media termination, deskphone control uses the phone for media. Did you change the parameters during install for phone mode??? If not, it's not in phone mode.
    A3: No, that can be many things, DNS, connectivity, credentials, etc
    You mention DNS is not used, so, most likely that's the problem.
    I'd strongly recommend you to review the whole deployment guide for Jabber for Windows.
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Ask the Expert: Cisco TelePresence for the Enterprise

    Welcome to the Cisco® Support Community Ask the Expert conversation.  This is an opportunity to learn and ask questions about Cisco Telepresence® for the enterprise. 
    Cisco experts Jaret, Fernando, and Fred will be covering all Cisco TelePresence products.  Topics include Cisco TelePresence endpoints and TelePresence infrastructure such as the Cisco TelePresence Video Communication Server (VCS), Cisco Expressway Series, Cisco Unified Communication Manager (CallManager), Cisco TelePresence Servers (MSE 8710, on Virtual Machine, etc.), MCU (MSE 8510, etc.), Cisco TelePresence Management Suite (TMS), and all other Cisco TelePresence related devices.
    Jaret Osborne is an 8-year Cisco Advanced Services veteran.  In his Advanced Services tour, Jaret has covered all aspects of Cisco Unified Communications and TelePresence products, including both enterprise and service provider verticals. Most recently Jaret has been working with global service providers supporting their Cisco TelePresence as a Service offerings while also incubating new cloud services at Cisco.
    Fernando Rivas is a Cisco Advanced Services NCE, starting in the Cisco Technical Assistance Center (TAC), 2007, on the Collaboration Technology Team mastering the Cisco Unified Communication  technologies and specialized in call control CUCM,VCS) and  conferencing (MeetingPlace, Telepresence). In 2011, he joined Cisco Advanced Services as a member of the Cisco Collaboration team and participated in several Cisco TelePresence and video-related technologies deployments. Currently he is a member of the Video Cloud Technology Team, supporting video exchanges in several and architecting new private video cloud solutions for large enterprises. Fernando holds a routing and switching CCIE® certification (22975).
    Fred Mollenkopf  is a Cisco Advanced Services Network consulting engineer working at Cisco for the last 7 years. Fred has led some of the largest Cisco Unified Communication and Collaboration deployments done for Cisco customers and partners. Over 15 years’ experience in data networking with a specialization in Cisco Unified Communications in 2004. Currently he is a member of the SP Video Advanced Services Team, supporting SP video exchanges and the Cisco Telepresence solutions.  Fred maintains an active CCIE® in Voice (17521).
    Remember to use the rating system to let Jaret, Fernando, and Fred know if you have received an adequate response. 
    Because of the volume expected during this event, Jaret, Fred, and Fernando might not be able to answer every question. Remember that you can continue the conversation in the Collaboration, Voice and Video Community, under the sub-community TelePresence, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Tenaro,
    Additionally here are the most common login issues.  Unfortunately this includes items related to Presence implementation but I commented where we did not use these in our lab setup for CUCM Phone Capabilities only.  
    Login Issues
    Problem:
    Jabber Unable to Sign-in Through MRA
    Solution
    This can be caused by a number of things, a few of which are outlined below.
     1.  Collaboration Edge SRV record not created and/or port 8443 unreachable
    For a jabber client to be able to login successfully using MRA, a specific collaboration edge SRV record must be created and accessible externally. When a jabber client is initially started it will make server DNS SRV queries:
    _cisco-uds : this SRV record is used to determine if a CUCM server is available.
    _cuplogin : this SRV record is used to determine if an IM&P server is available.
    _collab-edge : this SRV record is used to determine if MRA is available.
    If the jabber client is started and does not receive an SRV answer for _cisco-uds and _cuplogin, and does receive an answer for _collab-edge then it will use this answer to try to contact the Expressway-E listed in the SRV answer.
    The _collab-edge SRV record should point to the FQDN of the Expressway-E using port 8443. If the _collab-edge SRV is not created, or is not externally available,  or if it is available, but port 8443 is not reachable, then the jabber client will fail to login.
     2.  Unacceptable or No Available Certificate on VCS Expressway
    After the jabber client has received an answer for _collab-edge, it will then contact the expressway using TLS over port 8443 to try to retrieve the certificate from the expressway to setup TLS for communication between the jabber client and the expressway.
    If the Expressway does not have a valid signed certificate that contains either the FQDN or domain of the Expressway, then this will fail and the jabber client will fail to login.
    If this is occurring, the you should use the CSR tool on the Expressway, which will automatically include the FQDN of the expressway as a Subject Alternative Name.
    MRA requires secure communication between the Expressway-C and Expressway-E, and between the Expressway-E and external endpoints.
    Expressway-C Server Certificate Requirements:
    The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation.  The Expressway-C should automatically include these in the CSR provided that an IM&P server has already been discovered on the Expressway-C.
    The names in FQDN format of all Phone Security Profiles in CUCM configured for TLS and used on devices configured for MRA. This allows for secure communication between the CUCM and Expressway-C  for the devices using those Phone Security Profiles.
    Expressway-E Server Certificate Requirements:
    All domains configured for Unified Communications. This includes the domain of the Expressway-E and C, e-mail address domain configured for Jabber, and any presence domains.
    The Chat Node Aliases configured on the IM&P servers. This is required if you are doing XMPP federation. 
    The MRA Deployment guide describes this in greater detail on pages 17-18. (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Ac...
    Note: In our lab for testing Phone Capabilities only, we did not include the Chat Node Aliases in the certificate as we were not using IM&P.
     3.  No UDS Servers Found in Edge Config
    After the Jabber client successfully establishes a secure connection with the Expressway-E, it will ask for its edge config. This edge config will contain the SRV records for _cuplogin and _cisco-uds. If these SRV records are not returned in the edge config, then the jabber client will not be able to proceed with trying to login.
    To fix this, make sure that _cisco-uds and _cuplogin SRV records are created internally and resolvable by the Expressway-C
    More information on the DNS SRV records can be found on page 10 of the MRA deployment guide for X8.1.1 (http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X8-1/Mobile-Remote-Access-via-Expressway-Deployment-Guide-X8-1-1.pdf)
    Note: In our lab for testing Phone Capabilities only, we did not include the DNS SRV for _cuplogin.
     4.  The Expressway-C logs will indicate the following error: XCP_JABBERD  Detail="Unable to connect to host '%IP%', port 7400:(111) Connection  refused"
    If Expressway-E NIC is incorrectly configured, this can cause the XCP server to not be updated. If the Expressway-E meets the following criteria, then you will likely have this issue:
    Using a single NIC
    Advanced Networking Option Key is installed
    Use Dual Network Interfaces option is set to “Yes”
    To correct this problem, change the “Use Dual Network Interfaces” option to “No”
    The reason this is a problem is because the Expressway-E will be listening for the XCP session on the wrong network interface, which will cause the connection to fail/timeout. The Expressway-E listens on TCP port 7400 for the XCP session. You can verify this by using the netstat command from the VCS as root.
    Note: We used a Dual Network Interface Expressway for testing but were not using XCP, so this was not applicable to us.
     5.  VCE-E Server hostname/domain name does not match what is configured in the _collab-edge SRV.
    If the Expressway-E Server hostname/domain name does not match what was received in the _collab-edge SRV answer, the jabber client will not be able to communicate to the Expressway-E. The Jabber client uses the xmppEdgeServer/Address element in the get_edge_config response to establish the XMPP connection to the Expressway-E.
    This is an example of what the xmppEdgeServer/Address would look like in the get_edge_config response from the Expressway-E to the Jabber client:
    <xmppEdgeServer>
    <server>
    <address>ott-vcse1.vcx.cisco.com</address>
    <tlsPort>5222</tlsPort>
    </server>
    </xmppEdgeServer>
    To avoid this, make sure that the _collab-edge SRV record matches the Expressway-E hostname/domain name. Enhancement CSCuo83458 has been filed for this. 
    Note: This was one of our issues when we first setup.  We adjusted our Expressway-E to insure the below:
    System > Administration > System Name this was the FQDN
    System > DNS > System Host Name was the host portion of the FQDN
    System > DNS > Domain Name was the domain portion of the FQDN
    System > Clustering > Cluster Name (FQDN for Provisioning) was the FQDN
     6. Unable to log into certain IM&P servers. VCS logs say "No realm found for host cups-example.domain.com, check connect auth configuration"
    From the Expressway-E, go to Configuration -> Unified Communications -> IM&P Servers. Open each server and click "Save" again. Not sure exactly why this happens.
    Note:  This was N/A to our test and can be ignored with Phone Capabilities only.
    Thanks
    Fred

  • How to connect Wireless microphone to Cisco Telepresence SX20

    Hi,
    Does anyone try to connect Wireless microphone to the second microphone input (Cisco Table Mic 20 microphone is connected to the first microphone input)? Is this connection OK if I want to use both 2 micphone types?

    I have connected single- and dual-channel Revolabs microphones the C20, with very good success.  I have also connected a single-channel Revolabs and a second connection to ClearOne Converge Pro DSP, also with very good success.  I have not tried to connect a TelePresence 20 Microphone on one input and a single-channel Revolabs on the other.  My customers either require a totally wireless solution or a wireless and an installed microphone solution.  We are just starting to order the SX20, so I will be testing wired and wireless combinations to validate their compatibility.
    The Revolabs receiver has a 3.5mm TRS (Tip-Ring-Sleeve), while the C20/SX20 has a 3.5mm TRRS (Tip-Ring-Ring-Sleeve).  Revolabs makes a cable that resolves the differences between them but it does not transmit the muting function on the Revolabs microphone to the codec.  Muting takes place by using the remote or the Cisco touch panel.
    http://www.revolabs.com/professional-product-skus/hd-single-or-dual-channel-product-skus  (single- and dual-channel Revolabs wireless mics)
    3.5mm Balanced Male Connector to 3.5mm Male 4 Conductor - Part# 07-35MBTO35M4-01

  • Any ways to receive calls only from address book on Cisco Telepresence SX20?

    I have been receiving numerous unknown calls on my conference call device and I would like to know if there are any ways to block these calls or even possibly only receive calls on the address book.

    In the Bug Search, I see this info (it won't let me cut and paste the rest of the page but it's bug search CSCue55239:
    Last Modified:
    Feb 3,2015
    Status:
    Fixed
    Severity:
    2 Severe
    Product:
    Cisco Telepresence Integrator C Series
    Support Cases:
    103
    When it says "Status:  Fixed" and Known Fixed Releases: is a version older than the one we use, does that mean that the problem should be resolved from that firmware version forward? Also wondering if "Fixed" means that we still need to do the workaround to fix the problem on ALL versions of firmware, or just the ones prior to 6.2.0 ? Thanks.
    Known Affected Releases:
    (1)
    5.1.2
    Known Fixed Releases:
    (1)
    6.2.0

  • Cisco Telepresence and Meeting Place Integration with Third Party Call Pros

    Dear colleages:
    i want to ask if Cisco Telepresence can integrate with 3rd party call processing systems.
    as my project has already existing Nortel Communication Server 1000,
    which supports:
    Operating System: VXWorks and Linux
    Network Signaling Protocols: H.323v4, MCDN, SIP, LDAP, QSig, QSS, in band and DPNSS
    Trunking Support:
    IP:IP Virtual Trunks using IP Peer Networking over H.323 or SIP
    Digital: DTI, ISDN-PRI, ISDN-BRI
    Analog: Loop and Ground Start CO, FX, WATS, two or four wire E&M, four wire DX, DID, TIE, RAN Paging.
    and i want to build Video Converence system over the WAN.
    please to tell me if that integration is possible and what is the design components that is required for such project to be handled from A- to Z.
    Regards,

    I have been told that i need to use SIP protocol API instead of TAPI to have a TRUE VOIP Windows solution.
    Could you guys please tell me the difference between SIP API and TAPI?
    And could you please suggest a way which API (SPI or TAPI) the OnCast solution is based on (http://www.litescape.com/oncastsoftware.html) - we have to develop something similar.
    Thank you for your replies,
    Alexey

  • Passing args to: Cisco Telepresence Movi.msi

    Hi -
    I'm working with Movi 4.2 and am using the Cisco Telepresence Movi.msi because I'm creating my own installer.
    I'm trying to pass these arguments to it for a silent install:
    /quiet DOMAIN=transport-you.com EXTERNALVCS=transport-you.com HIDEADVANCEDLOGIN=1
    The Movi_Administrator_Guide_4-2.pdf says I can set these properties but for some reason it's failing when I run it. Here's an example error msg:
    The system cannot find the file DOMAIN=transport-you.com.
        while executing
    "::InstallJammer::actions::$component $this"
    Error in action LaunchFile
    What am I missing here?

    Hi Mattew!
    Use the .exe installer file provided in the zip file!
    The MSI would be used if you want to build your own software package.
    From the admin guide:

  • Cisco 2811 routers to route video over ip for polycom equipment.

    Hi forum,
    We are currently using polycom equipments over ISDN links for video conferencing, however, we intend to switch to our EIGRP E1 lines for that. all our sites are currently using 2811 routers to route both data and voip traffic. How do I provision the network so that I can use my E1 lines for video over ip, How should I design it?
    Besides, How do i provide video over ip service to my mobile users who vpn into my network.
    Thanks and best regards,
    paul

    first, on provisioning your network for video over ip, make sure you can implement the QoS required to provide a clear, unchoppy video stream.
    your design could look something like the following:
    polycom >> network >> router >> E1 >> router >> network >> user
    (very basic description, you may require more detail depeding on your needs)
    also, for video over ip to your vpn users, you might be able to use something like cisco IPTV or the likes. (depending on the type of video you want to provide your users)
    please see the following link for video over ip for polycom:
    http://www.cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a0080111c1b.shtml#configqos
    please see the following link for more QoS for video conferencing info:
    http://www.cisco.com/en/US/tech/tk543/tk757/technologies_tech_note09186a0080094968.shtml
    please see the following link for info on video over ipsec vpn:
    http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns241/netbr09186a0080125154.html

  • Why cisco c40 doesn't complete a call to a room from Polycom RMX system?

    Dear All,
    I am trying to complete a call to a virtual room at Polycom RMX system, but Cisco C40 cannot complete the call. The format required by Polycom is "<ip>##idroom##passroom" but it doesnt work.
    I have tryed room@<ip> but it also doest work.
    Does anybody know how to fix this problem?

    The format "required by Polycom" doesn't comply with any standard what-so-ever.
    Their proprietary "URI dialling" format is IP##Alias, which is only supported by them and LifeSize, however, RMX does support Annex O, Alias@domain (alternatively Alias@IP), which happens to be the standard.
    First things first; what software version is the C40 running? If it's an earlier version than TC4.2 then URI dialling won't work unless the C40 is registered with a GK and/or VCS etc.
    If you are running TC4.2 and later, contact the other party and get them to confirm their RMX has been configured to support Annex O.
    You should, alternatively, be able to dial the IP address and then enter the Alias and, if required, PIN using DTMF.
    There is yet another option, but you'll need at least a VCS for that, and it is a bit messy; https://supportforums.cisco.com/discussion/11407121/vcs-search-rules-and-polycom
    /jens
    Please rate replies and mark question(s) as "answered" if applicable.

  • Is it possible to create a cisco config file based on a polycom config file?

    Hello,
    We have 12 spa509g phones that are barely working with our provider (voxox).
    My provider gave me the config files that are used to set up polycom phones as those are the only phones they support.
    Features that currently work: incoming calls, outgoing calls, blind transfer, voicemail, call hold
    Features that do not work: call presence - solid orange lights, attended transfer, paging 
    I've upgraded the firmware to 7.5.6 and configured the phone through the GUI as much as i can but I can't seem to enable the above features.
    Any help would be highly appreciated as I'm about to buy polycom phones if we can't figure the configuration out.
    Attached are the configuration files from voxox concerning polycom phones. confidential data says "removed"
    If anyone thinks that this is possible, I can send a copy of my current cisco configuration file. 
    Thanks,
    Philip

    Well, I have no polycom phone, not I have personal experience with voxox. I wish the following document may help a lot - it describe Polycom configuration somewhat. As you have no Polycom, you have no current <mac>-directory.xml. So you don't know the device name you should subscribe to. But it seems to be a DID-number.
    Just try it.
    On the other side, ask Voxox for help. Don't ask for configuration files, ask for configuration instructions expressed in terms of the SIP protocols. Consider switch to more friendly and technically skilled VoIP operator if they will not understand what the SIP stand for ...
    By the way, wrong forum. Your issue has nothing to do with XML Phone Application interface. I'm not sure someone will respond you here.

Maybe you are looking for