alex2605

Hi, Went through a lot of the functions in KES and found out yesterday that it was indeed “host intrution prevention”. Simply disabled the different functions one at a time. By default the application went to “low restricted” group where it cannot access the microphone. Added the application to “trusted” and tested again where it worked.

Hi, We have started to roll out a softphone but we see some issues with KES. If we completely disable KES on a device the softphone works as is, as soon as KES is active we cannot use the softphone. Softhpone will start but some functionality will not work as outgoing calls. From a Wireshark dump we can see the application mostly communicates via port 443. In our KSC we have tried to disable the firewall, web control, application control, add the application to trusted applications in Network Settings. It only works if we completely disable KES. I can’t seem to see what would block the connection. Are there reports or logs on KSC or on the client that we can take a look at?

Thank you! It worked. Now we can try to get some information out with the API :)

When POSTing to https://servername:13299/api/v1.0/login with the following headers: Authorization: KSCBasic user="x", pass="x", internal="1" Content-Type: application/json X-KSC-VServer: x Content-Length: 2 I get the following message back: “Authentication failure”. The user has full admin access, and can login to the KSC MMC console. According to the documentation the user, pass and X-KSC-VServer should all be endcoded with Base64.