Message to management              
Автоматическое поднятие карточки клиента через WebSocket Binotel. Решение основных ошибок

Automatic raising of a client card through WebSocket Binotel. Solving Major Mistakes

List of possible errors


1. Solving a problem if the function of automatically raising a client’s card, organized through the service, has stopped working «WebSocket Binotel».

The solution to the above errors.



1. Question:

The function of automatically raising a customer card, organized through the service, has stopped working «WebSocket Binotel».


Answer:

Identification of the cause of the problem:


1. Check if the Websocket Client Binotel service is running , if not, start, fig. 1. 
 If the service is turned off, then the service operation log can be found in the system log, fig. 4, fig. 5.

If a connection break occurs, periodic reconnection attempts will automatically be made.


2. Check the latest entries of the LOG file of the Websocket Client Binotel service (located in the folder next to the service EXE file, Fig. 2, Fig. 3).

In the log files everything should be clear to the system administrator, by them you can understand on which side the problem is. On the side of the Binotel virtual telephone exchange or in "1C:Підприємство".

Examples that can be seen in the log file of the Websocket Client Binotel service:

  • Are messages coming from Binotel

Such records are as follows:

06.09.2019 15:52:26: {"eventName": ……

  • Are there any connection errors with the WebSocket Binotel service:

Such records are as follows:

06.09.2019 11:33:21: ERROR: Connect timed out.(Error code 1)


Fig. 1. The magazine "Services". The Websocket Client Binotel service is running.


Fig. 2. Websocket Client Binotel service card, directory where the service is located.




Fig. 3. The log file of the Websocket Client Binotel service.



Fig. 4. System event log. Logging that the WebSocket Client Binotel service has stopped.




Fig. 5. System event log. Log entry that the WebSocket Client Binotel service is running.


3. If after repeated attempts the connection is not restored then:

  1. Check the network (Internet availability on the server where the service is installed).

  2. Check if the virtual ATC Binotel is working.

  3. Test the service manually using a browser extension (for example Simple Websocket Client https://chrome.google.com/webstore/detail/simple-websocket-client/pfdhoblngboilpfeibdedpjgfnlcodoo?hl=ru)


If after connecting an authorization request comes:

{"status":"Connected to Binotel WebSocket. Please, authorise!","connectedAt":1567775879}

So everything is OK.

4. If all else fails, contact the NCT support team by writing an email: s@nct.ua





Company "NCT"


09.09.2019

Back to the list