Jump to content

tomas_

Members
  • Posts

    785
  • Joined

  • Last visited

  • Days Won

    20

Posts posted by tomas_

  1. Hi @MattForrest!

    We have a PHP script which is setup to run as preflow on the account, invoked by Pivot (made in Callflows app).
    This script can for intance handle presences (connected to calendar services, with a voice saying that a user is in a meeting and when he/she will be back, etc).
    I guess it would not be that hard to add functionality to check if any of the user's devices is in use and then disconnect the call with a busy tone / response.

    More info here:
    https://docs.2600hz.com/dev/applications/callflow/doc/preflow/
    https://docs.2600hz.com/dev/applications/pivot/doc/
    https://docs.2600hz.com/dev/applications/pivot/doc/kazoo/hangups/

     

  2. Late reply, again. Stumbled upon this issue when trying to connect to WSS websocket in another subject. Turned out that I've been trying to use the wrong certificate files, at least this time.
    Note to self (and others with same issue); Use the correct certs, and make the haproxy.pem like this if you're using Let's Encrypt / Certbot:

    cat fullchain.pem privkey.pem | tee haproxy.pem

    This time I got it working with the config from Kazoo docs, don't know if your settings will work also, @RuhNet (it probably will);
    https://docs.2600hz.com/supported/applications/blackhole/doc/#wss-considerations

  3. Hi!

    I've just set up a new cluster with Kazoo 4.3 and encountered this issue also. I noticed that the /tmp folder of Freeswitch server was filling up with a lot of call recordings (mp3 files), and found the "Received HTTP error 0 trying to save" error in Freeswitch logs. Also "Error Storing File" in Kazoo console log.
    Also the recordings isn't found when trying to get them from recordings API.

    It started when adding another Kazoo / Ecallmgr server, before that there was no issue at all. And it's only when Freeswitch tries to save the media to the new, second Kazoo / Ecallmgr server, it works perfect to the first one.

    Somehow I noticed the "proxy_store_acls" setting in system_config/media (Bigcouch /_utils/document.html?system_config/media), and when adding the IP addresses for both Freeswitch servers there it seems that the problem is gone!
    Needs some more testing to be sure, but all it seems like every recording is saved properly.

    image.png.7da35b8ce2708eb954218e14333f8cee.png

    I haven't seen this in any docs or guides anywhere.

    Br - Tomas

     

  4. Ah, no - Forgot to change the config.js.
    I'm a bit confused with all ports...  Now I've enabled wss in config.js:

    socket: 'wss:mydomain.com:5443'

    And which ports should I use in the haproxy.cfg?
    This is my setup now (7777 in listen section and 5443 in backend)

    image.png.69e557d526bc1949121e8f39ef036ee5.png

    Is this correct?
    When trying this i get Layer4 connection problem, info: "Connection refused"

    Also tried to set 5443 in listen and 5555 in backend, then I get Layer7 wrong status, code: 400, info: "Bad Request"  instead...

     

  5. Thanks!

    I still having troubles getting the HAProxy to work. Even if I know it's not in your app you might have some ideas?
    Can it be the haproxy.pem file that isn't correct? Not sure exactly which files from letsencrypt/certbot that should be included?

    I'm getting errors in the HAProxy log:  

    Health check for server kapps-blackhole/ourdomain.com failed, reason: Layer7 wrong status, code: 400, info: "Bad Request", check duration: 0ms, status: 0/2 DOWN.
    kazoo-websockets~ kapps-blackhole/<NOSRV> 12/-1/-1/-1/12 503 212 - - SC-- 1/0/0/0/0 0/0 "GET / HTTP/1.1"

    I've added this in haproxy.cfg:
    image.png.4b1371ae0bfe957c2069ee4ebb3f17fe.png

     

  6. Hi!
    Long time, haven't tested this until now.

    I can't get the realtime info to work, guess it's something with the websockets?
    I'm getting "Subscribing to Websockets..." in the web console log, and when I try to change parameters in the config.js i sometimes getting error from the browser. When using the correct parameters ("socket: 'ws:myserver.com:5555'") the error messages disappears but it stil isn't updating the switchboard in realtime.

    Br - Tomas

×
×
  • Create New...