Brandon Guy

A Collection of Information and Projects from over the years. 

Device Operator Console

Device operator Console is a quick tool built to support Poly devices running UC Software. These devices include the Poly CCX, Trio, and VVX devices running a release of 5.9.x or later.

This tool leverages many of the open APIs in the UC Software to provide a remote operating solution for these devices.

Download the most recent version

You can find a zip of the published software here:

Google Drive Share (Version 1.1.0.5)


Abbreviated Feature List

  • Remote Screen Viewing
  • Remote Device Operation
  • Call Control
  • Active Call Statistics
  • Modular Room View (For Trio V+ and Daisy-Chained Trios)

Normal Disclaimer

This Tool is provided free of charge with no implied warranty on behavior. The application does not collect nor send any data to any location other than the device you are connected to.

This application WILL enable the RestAPI of the device and WILL enable the screen capture functionality. Both of these interfaces will still require the administrator password of the device to access.

I’ve built the tool using Visual Studio and published using the ClickOnce Technology. Although the application does have the ability to auto update, this has not currently been implemented. You can read more about ClickOnce here on the Microsoft documentation portal.

Update: Depending on your system, ClickOnce may not be allowed to install by default, a fantastic write up on the ClickOnce behavior with Windows can be found on here: https://www.gonnalearn.com/your-administrator-has-blocked-this-application-because-it-potentially-poses-a-security-risk-to-your-computer/

Known Limitations

  • You must have enabled the Web Server functionality.
    • either http or https may be used
  • You cannot use the default password of ‘456’.
  • VisualPro devices cannot be displayed
  • Control only works for devices in Generic or Skype for Business Base Profiles. Devices in Teams or Zoom Base Profile cannot be controlled, but can be viewed.

Version History

Version 1.1.0.5

  • Resolved an issue with Trios running version 7.2 or later whereby they would not load

Version 1.1

  • Fixed a CSRF security issue when updating to UCS version 7.x with Visual+ units.

52 thoughts on “Device Operator Console

  • Daniel
    April 24, 2020 at 10:42 am

    Hi Brandon,

    Thanks for sharing this useful tool. Have there been any updates released for this tool since you posted this?

    • Brandon
      June 10, 2020 at 6:17 pm

      I haven’t gotten anything else added into the tool, as life has been a bit crazy.

      I do intend on buttoning up a few things like adding drag support as well as making a quicker way to capture the device screen and exporting it to support customers making their own custom user documentation. I also want to clean up a few workflows for dialing and line selection and add in a way to send digits through a 4×3. if there are some things you’d like to see changed or added, feel free to leave the comments and I’ll work through them as I can.

    • Damon
      January 14, 2022 at 5:13 pm

      Brandon this is a very helpful tool. Unfortunately 7.2 doesn’t like it. Pretty please take a look at it. Thanks

      • Brandon
        May 26, 2022 at 12:20 pm

        Sorry for the delay in getting it resolved, but the latest version just posted is working with Trios running the 7.2 and 7.3 release. Give it a shot and let me know if you are still running into difficulties.

        • Silviya
          June 20, 2022 at 9:24 am

          Hi Brandon,

          The link for the .5 version is leading to the .4 (can see same version after install and the Application folder shows .4 in Drive). Tried to reinstall, but same version appeared…
          Do you have a link to the newest .5 version to try accessing 7.2.x devices?

          Thank you so much for your great tool 🙂

          Best Regards
          Silviya

          • Brandon
            July 8, 2022 at 9:35 am

            Thanks for pointing out. Sorry for missing this. Seems like WordPress didn’t like when I updated the link when I posted the new build. I just checked and it’s pointing to the fixed version.

  • John
    April 27, 2020 at 11:37 am

    Hi, great app, I don’t seem to be able to interact with it in Teams mode at all or in Skype for Business mode get it to let me enter my admin password is that a bug or by design of the solution?

    • Brandon
      June 10, 2020 at 6:14 pm

      Correct, currently the RestAPI controls do not control the android applications, only the native Poly application.

      When running with Skype for Business mode, while this is the Poly Application, the keypad that is used in this interaction is actually an android application keyboard, which we can’t send a command to over the API interface.

      I’m trying to stick to only using externally facing public APIs with this tool so that it can be shared externally, so it is a limitation at this point in time.

  • Aaron G.
    October 15, 2020 at 12:38 am

    It would be most helpful if there was a console and/or debug option for this tool. Right now I’m having a heck of a time getting it to work and have no idea why it isn’t. I’ve tried multiple VVX phones now to no avail. Perhaps a basic user manual or notepad document contained within the ZIP file that has instructions?

    I love the concept of this tool but have yet to successfully use it to comment on it’s functionality. It very well could be operator error but the UI is simple enough I’d like to think that’s not where I’m getting hung up (VoIP joke).

    -Aaron

    • Brandon
      November 21, 2020 at 8:03 pm

      I am hoping to get a few updates into the tool over the holiday. I was going to try to work in some debug logging to help out in these scenarios. The most common problem I’ve seen has been related to firewalls, but it could absolutely be something else going on.

    • Dave
      December 30, 2021 at 4:48 am

      Is there a possibility for an unattended installation and an install dat doesn’t not install in the user directory but in a specified directory.

      • Brandon
        May 26, 2022 at 12:22 pm

        I would need to investigate this and the feasibility of it. With the packaging of the app I do not believe I have that flexibility but I’m not confident on that answer.

        That said, I was actually thinking about investigating what it would take to migrate it to a PWA so that it wouldn’t have to be installed, or it could be installed if you wanted it, but then again would need to find the time.

  • chito
    October 22, 2020 at 2:44 am

    This is very helpful especially that we are working from home most of the time. Would just like to know how to navigate to the next page of the display.

    • Brandon
      November 21, 2020 at 8:05 pm

      I have been meaning to add in some overlay controls to simulate swiping for this very reason. Right now there isn’t a way to drag across the screen.

  • Nick
    April 16, 2021 at 11:32 am

    This tool has been incredibly helpful, and I am so glad that I was able to come across it. I do run into some bugs such as the app crashing when disconnecting from a Trio and entering in the IP for another device. We use Trios in the Zoom Room Profile and would love for the ability to virtually interact with the screen. I saw in a previous comment that there isn’t a way to send swipes, but is there a way to send virtual taps? Are there plans to release any updates?

    • Brandon
      June 28, 2021 at 4:29 pm

      Clicks are working, but the API doesn’t extend to the android layer, which means that I cannot click into the Android Numpad, nor can I click into the Android app if you are running Zoom or Teams.

  • Joe
    May 7, 2021 at 1:57 am

    Hi Brandon,
    I really love(d) your tool, as this helped us so much in the past! But since we installed 7.0.0.4269 on our Trio 8800s, we cannot establish a connection any more, the tool always just crashes after some seconds.. 🙁
    Do you have any idea, if we can do anything here to make it run again? Or are there plans to make a new version, that works also with the newer firmware releases?

    BIG THX in advance 🙂

    • Brandon
      June 28, 2021 at 4:28 pm

      I’ve just uploaded version 1.1 which i’m finding to address this issue. Give it a go and let me know if you are still running into issues.

  • Josh
    May 13, 2021 at 9:22 pm

    Very cool – you don’t know how long I was looking for a way to capture the VVX screen for documentation purposes.

    Curious – does this use the uixml node (api/v1/mgmt/uixml) of the rest API & then represent the results as an image on the screen? Or is there a way to directly pull the image via the API?

    • Brandon
      June 28, 2021 at 4:29 pm

      I’m actually using the device feature of Screen Capture. Thanks for the feedback!

  • Stephan Botha
    June 1, 2021 at 7:03 am

    Good day Brandon. Hope you are well.
    Frist of all, thanks for this amazing program, without it I’m lost.
    However I need to ask some advice. Since today I receive the following error when opening the application, and have no idea how to solve it
    Any advice will be welcomed, thanks

    PLATFORM VERSION INFO
    Windows : 10.0.19041.0 (Win32NT)
    Common Language Runtime : 4.0.30319.42000
    System.Deployment.dll : 4.8.4270.0 built by: NET48REL1LAST_C
    clr.dll : 4.8.4300.0 built by: NET48REL1LAST_C
    dfdll.dll : 4.8.4270.0 built by: NET48REL1LAST_C
    dfshim.dll : 10.0.19041.1 (WinBuild.160101.0800)

    SOURCES
    Deployment url : file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/AV/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application

    IDENTITIES
    Deployment Identity : Device Operator Console.application, Version=1.0.0.12, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=msil

    APPLICATION SUMMARY
    * Installable application.

    ERROR SUMMARY
    Below is a summary of the errors, details of these errors are listed later in the log.
    * Activation of C:\Users\stephan.botha\Zutari\Zutari IT Operations – General\0.Zutari Operations\Zutari Infra Build\AV\Polycom Teams\DOC-Published-1.0.0.12\Device Operator Console.application resulted in exception. Following failure messages were detected:
    + You cannot start application Device Operator Console from this location because it is already installed from a different location.
    + You cannot start application Device Operator Console from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/AV/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application it is already installed from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application. You can start it from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application or you can uninstall it and reinstall it from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/AV/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application.

    COMPONENT STORE TRANSACTION FAILURE SUMMARY
    No transaction error was detected.

    WARNINGS
    * The manifest for this application does not have a signature. Signature validation will be ignored.

    OPERATION PROGRESS STATUS
    * [2021/06/01 13:02:08] : Activation of C:\Users\stephan.botha\Zutari\Zutari IT Operations – General\0.Zutari Operations\Zutari Infra Build\AV\Polycom Teams\DOC-Published-1.0.0.12\Device Operator Console.application has started.
    * [2021/06/01 13:02:08] : Processing of deployment manifest has successfully completed.

    ERROR DETAILS
    Following errors were detected during this operation.
    * [2021/06/01 13:02:08] System.Deployment.Application.DeploymentException (DeploymentUriDifferent)
    – You cannot start application Device Operator Console from this location because it is already installed from a different location.
    – Source: System.Deployment
    – Stack trace:
    at System.Deployment.Application.ApplicationActivator.CheckDeploymentProviderValidity(ActivationDescription actDesc, SubscriptionState subState)
    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
    — End of stack trace from previous location where exception was thrown —
    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
    at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
    at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
    — Inner Exception —
    System.Deployment.Application.DeploymentException (DeploymentUriDifferent)
    – You cannot start application Device Operator Console from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/AV/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application it is already installed from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application. You can start it from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application or you can uninstall it and reinstall it from location file:///C:/Users/stephan.botha/Zutari/Zutari%20IT%20Operations%20-%20General/0.Zutari%20Operations/Zutari%20Infra%20Build/AV/Polycom%20Teams/DOC-Published-1.0.0.12/Device%20Operator%20Console.application. If you reinstall the application, be aware that you might lose any customizations that you made to the application.
    – Source:
    – Stack trace:

    COMPONENT STORE TRANSACTION DETAILS
    No transaction information is available.

    • Brandon
      June 28, 2021 at 4:31 pm

      I think the new version I just published resolves this issue. Give it a go and let me know

  • Nick
    June 21, 2021 at 6:18 pm

    Hi Brandon,

    This is an incredibly helpful tool, and has definitely saved us some headache for our remote sites. Any word regarding updates? If you are looking for beta testers, I’m happy to volunteer.

    • Brandon
      June 28, 2021 at 4:32 pm

      No interfaces available today to take advantages of for the zoom device interaction sadly. Been toying with some thoughts, but just haven’t had much down time to explore them. Something in particular you are looking for?

  • Mark
    June 23, 2021 at 1:52 pm

    I’m having issues downloading DOC. Is the link on this page still the right place to download?

    • Brandon
      June 28, 2021 at 4:33 pm

      Yes, just updated the link to point to the new build. It should take you to a google drive share, which should enable you to download the full ZIP. Just checked and it was working for me in an incognito, but if it’s not working for you, let me know. Thanks

  • Brandon
    June 28, 2021 at 4:35 pm

    Thanks all for the support and understanding. Things have been busy and crazy, so I haven’t had a lot of cycles to put towards this. I did just update to fix an issue whereby the app was crashing in certain deployments with version 7.x or later. If you are still running into issues, feel free to reply and I’ll keep a closer eye here to keep tabs on it.

  • Ben
    July 14, 2021 at 11:09 am

    Hey Brandon, any chance this will be open sourced? There are a few things that I would like to add (like, support for the support for SimulateTextInput API call), so that I don’t have to run those things in a different script. Heck, maybe even add some other API support (reboots, push/pull configuration options, etc.)

    Any chance we will see the code up on Github?

    • Brandon
      September 19, 2021 at 6:42 pm

      Let me investigate this and get back to you

  • Chris
    August 24, 2021 at 3:49 am

    Hi Brandon,

    I absolutely love this tool. It has been fantastic especially in these more remote working times.
    But with the move to Teams and essentially all our Poly phones now moving to the Teams profile, is there any way this tool could be updated to support control of them? Or even devices like the Poly X50?
    We have these devices in offices around the world and has been amazing so would love to keep using!

    • Brandon
      September 19, 2021 at 6:44 pm

      Control of the Android apps is not currently possible as the API interface happens at an application layer and not at the OS layer which means control of the 3rd party apps is not possible today. Hope to have some updates for this in the future though.

      As for the Studio X devices, today the API interfaces are not robust enough to provide the same capabilities.

  • Tom
    October 5, 2021 at 11:20 am

    Hi Brandon,

    Any chance you have this hosted somewhere else, maybe GitHub? We prohibit access to Google Drive, and Box, and….

    Thank you!

    -Tom

    • Brandon
      May 26, 2022 at 12:37 pm

      Ben above was also asking me about moving it to opensource which putting on github would resolve. The repository is in and of itself in azure devops so just need to open that up more broadly. Will look into it.

  • Nicolas
    October 8, 2021 at 2:42 am

    Hi Brandon,
    Thank you for this very nice tool.
    When I click on Show Displays the application crashes. Here is the error message :

    Application : Device Operator Console.exe
    Version du Framework : v4.0.30319
    Description : le processus a été arrêté en raison d’une exception non gérée. –> Unknown exception
    Informations sur l’exception : System.Net.Sockets.SocketException
    à System.Net.Sockets.Socket.InternalEndConnect(System.IAsyncResult)
    à System.Net.Sockets.Socket.EndConnect(System.IAsyncResult)
    à System.Net.ServicePoint.ConnectSocketInternal(Boolean, System.Net.Sockets.Socket, System.Net.Sockets.Socket, System.Net.Sockets.Socket ByRef, System.Net.IPAddress ByRef, ConnectSocketState, System.IAsyncResult, System.Exception ByRef)

    Informations sur l’exception : System.Net.WebException
    à System.Net.HttpWebRequest.EndGetResponse(System.IAsyncResult)
    à System.Threading.Tasks.TaskFactory`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].FromAsyncCoreLogic(System.IAsyncResult, System.Func`2, System.Action`1, System.Threading.Tasks.Task`1, Boolean)
    à System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
    à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
    à System.Runtime.CompilerServices.TaskAwaiter`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResult()
    à TrioOperatorConsole.mrView+d__16.MoveNext()
    à System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
    à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
    à System.Runtime.CompilerServices.TaskAwaiter`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResult()
    à TrioOperatorConsole.mrView+d__20.MoveNext()
    à System.Runtime.CompilerServices.AsyncMethodBuilderCore+c.b__6_0(System.Object)
    à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    à System.Windows.Threading.DispatcherOperation.InvokeImpl()
    à System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    à MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
    à System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
    à MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
    à System.Windows.Threading.DispatcherOperation.Invoke()
    à System.Windows.Threading.Dispatcher.ProcessQueue()
    à System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    à MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
    à MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
    à System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    à System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    à System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
    à MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
    à MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
    à System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
    à System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
    à System.Windows.Application.RunDispatcher(System.Object)
    à System.Windows.Application.RunInternal(System.Windows.Window)
    à System.Windows.Application.Run(System.Windows.Window)
    à System.Windows.Application.Run()
    à TrioOperatorConsole.App.Main()

    • Brandon
      May 26, 2022 at 12:27 pm

      Hi Nicholas, if you are still running into this issue, what version of Trio software are you running so I can see if I can reproduce.

      • Nicolas
        June 20, 2022 at 10:33 am

        Hi Brandon,
        My Trio are running firmware 5.9.5.3182.
        I didn’t test version 1.1.0.5 of your software because the download link point to the 1.1.0.4
        Regards,

        • Brandon
          July 8, 2022 at 9:38 am

          I just updated the link, you should be able to pull down the 1.1.0.5 version. But with that version of software, the 1.1.0.4 should have been working just fine as well.

  • Diego Franco
    October 25, 2021 at 7:17 pm

    Thank for the release of this fantastic tool, one question, is there a way to scroll down for an option? I have tried with the mouse also keyboard buttons but I’m unable to, I’m just trying to get an option that is till the end of the options but for this I need to scroll down, thank you.

    • Brandon
      May 26, 2022 at 12:26 pm

      Hi Diego, are you asking regarding navigating the menu? There is a ‘simulate touch / drag extension ‘ that I was playing with but was not able to get it to reliably register through the app framework.

  • Ben
    November 11, 2021 at 1:04 pm

    Hey Brandon, it looks like this tool might be broken as of 7.2.0. All of a sudden after updating, I get a “connection to the device failed” error. Same config before and after, and I can still pull sceenshots directly via /capturescreen and PDSM-E.

    Offer is still there to help if you open source this :).

    • Brandon
      May 26, 2022 at 12:24 pm

      Hi Ben, Sorry for the delay in getting it resolved, but the latest version just posted is working with Trios running the 7.2 and 7.3 release. Give it a shot and let me know if you are still running into difficulties. Had to do with a change in the health check of the connection and how the Trios identify themselves on the network. There were some changes with 7.2 that I needed to adjust for. Should be good to go now.

  • Michael
    March 6, 2022 at 6:12 pm

    Hey Brandon,

    This tool has made my life so much easier.
    The only tweak I would love to see, I have some Poly VVX 201 units we are resetting to Teams. The reset I can do remotely, but once they reset and update, the default admin password changes back to 456, and I cannot remote to them with DOC until I physically change the admin password on the phone. Not always ideal for remote sites.
    Is there any way to make DOC work with the default admin password? or add a password change feature?

    Thanks!

    • Brandon
      May 26, 2022 at 12:20 pm

      Unfortunately, there is not a way to accomplish this today. It has to do with the security model and alignment to California State Bill 327 whereby web access with the default admin password is not allowed, so you have to out of box it and then it would work. I am working on a few workflows with Poly Lens to help automate and bring a device back from factory reset to a good remotely accessible state for devices not on a corp net, but that probably doesn’t help much for now. The best solution today would be if the device is added to our ZTP solution it would talk to ZTP on first boot after the reset and you could specify an updated admin password there. That would boot strap and get it going for you.

  • David Wolf
    March 22, 2022 at 11:05 pm

    Hi Brandon! I was wondering if this application works with 7.2.x? It seems to be getting a 200 response but the app reports “Connection to the Device Failed” I’ve tested with 7.2.0 and 7.2.2.

    • Brandon
      May 26, 2022 at 12:15 pm

      Hey David, Sorry for the delay in getting it resolved, but the latest version just posted is working with Trios running the 7.2 and 7.3 release. Give it a shot and let me know if you are still running into difficulties.

  • Bertrand
    March 29, 2022 at 1:21 pm

    Hi Brandon,
    First many thanks for this helpful tool.
    I’ved juste update a Trio C60 in firmware 7.2.xxx.
    DOC deosen’t work from this version of firmware.
    It worked perfectly in version 7.1.xxx.
    Do you know if this is a parametter to push on the device or maybe an upgrade of the app?
    Many thanks

    • Brandon
      May 26, 2022 at 12:14 pm

      Sorry for the delay in getting it resolved, but the latest version just posted is working with Trios running the 7.2 and 7.3 release. Give it a shot and let me know if you are still running into difficulties.

  • Todd
    April 4, 2022 at 1:41 pm

    Hi Brandon,

    Having some issues getting it to work with Poly 7.2.0.12362. We were on 7.1.0.8045 and it was working with no issues. We are using COD 1.1.7849.28935.

    • Brandon
      May 26, 2022 at 12:14 pm

      Sorry for the delay in getting it resolved, but the latest version just posted is working with Trios running the 7.2 and 7.3 release. Give it a shot and let me know if you are still running into difficulties.

  • James
    June 17, 2022 at 7:42 am

    Hi Brandon,

    First off, this tool is fantastic, congrats! The only problem I have (and it seems to be random), but on some devices I get a “Whoops… Looks like something went wrong” and we cannot see the phone. We can still control it, but we cannot see the screen. This is a problem as for the CCX phones, we really want to see the code on the phone. Is this to be expected on some devices/firmwares?

    • Brandon
      July 8, 2022 at 9:37 am

      Thanks James. The Whoops screen shows up whenever the tool has a web transport error when accessing the screen. I don’t test against every release of software, but I do expect that it should be working pretty reliably for the screencapture function. What software version are you running?

  • Chris
    August 23, 2022 at 8:25 pm

    Hi Brandon,

    Sorry I know you are very busy!
    With Microsoft releasing the Teams Azure Communication APIs now, is it possible to setup the app to be able to work with Teams devices?
    Like Trios, CCX, X50, G7500, TC8 touch panels etc?

    Thanks!

Leave a Reply to Tom Cancel reply

Your email address will not be published. Required fields are marked *.

*
*
You may use these <abbr title="HyperText Markup Language">HTML</abbr> tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>