SERVER EDITION WEBSOCKET

[smartedge1]

We have SE primary and secondary on R11.1.3 on Remote site A and B .Phones in site A are registered to primary while phones in site B are registered to secondary server . I noticed We cant make calls from site A to B if we make it a websocket server /client but if works if we change the transport type to proprietary we are able to make calls . I am finding this worrisome because SE documentation mentioned that the link between primary and secondary link should be websocket . I will appreciate your inputs .

 

[derfloh]

Did you check the SSA alarms? There can be various reasons why the websocket connection doesn’t work. Untrusted certificates, blocked ports, wrong password…

 

[smartedge1]

Yes i can see that the websocket trunk is out of service on system status . I set the security level to unsecured . I can ping the IP address of both sites in system status lines page . Can you advise on what i can check ?.

 

[derfloh]

One side must be master one must be Slave. Passwords must be identical. Make sure you don‘t have duplicate IPs one one site

 

[smartedge1]

There is no conflict on the system the web-socket server and client is showing out of service . Attached is the screenshot and monitor logs for your reference . I will appreciate your help.

 

[nnaarrnn]

You have zero administered channels. Give both sides some channels to work with and reconnect that line/path.

 

[smartedge1]

Thanks everyone , the web-socket is working now . We changed the port of the web-socket client port from 80 to 443 and the line became in service . Thanks everyone .

 

[derfloh]

Then it was a firewall issue. See my hint for "blocked ports" in my first reply.