Jump to content

tomas_

Members
  • Posts

    785
  • Joined

  • Last visited

  • Days Won

    20

Posts posted by tomas_

  1. Hi!
    Today it happened again, this time with bigger impact - Many databases discarded when an old, removed couchdb node (with old databases) went online after a power outage and somehow synced the old database with the other nodes. (Not good at all, you learn something each day! ;) ).
    (Since time we've started to make tar backups of the /srv folders on each db node also, but the last few days the disks went full and our automatic VPS script to increase disk storage wasn't working. Bad luck!!)

    So we started to restore databases which was backed up by our script running couchdb-dump, but then we ran into the issues in my post above!
    The number docs was easily fixed, just replace the + sign in the number/doc id with %2B. Sed is a really good tool, to fix we just ran:

    sed -i -e 's/_id":"+/_id":"%2B/g' number*

     

    However, the issues still remains. Anyone that can see why?
    There must be other out there using the couchdb-dump tool which has the same issues?

    Br - Tomas

  2. Our Android and iOS app actually has this feature also ;)
    It's using native Google and Apple Push functionality (via OneSignal), sending a push notice before the mobile rings (initiated by Kazoo webhook Channel Create). It shows who's calling and which number was called etc.
    However it's not sent until Kazoo trying to ring the device, so a delay in Kazoo wouldn't send the Push earlier (however we can modify the push sending mechanism to trigger when Kazoo rings a user instead).

  3. We have developed an advanced "Presence" system for Kazoo. Here the users can set 9 different presence statuses with different ending date or time ("Lunch", "Meeting", "Vacation", "Business trip" etc).
    On the phone, they can dial *23*1 for 1 hour lunch, or *23*1*1330 for lunch until 13:30.
    Other presences are "Meeting"; *23*2*1415 (Meeting until 14:15), or "Vacation"; *23*4*0921 ("Vacation until 21st september) etc.

    The system automatically answers calls to the user having an active presence, and speaks "The person you are trying to reach is on lunch and will be back at 13 30" or "...is on vacation and will be back at september the 21st" etc.

    We also have a smartphone app (iOS & Android) where the user can select presence status (among many other functions).

    Please send me a PM if this can be of any interest :)

    Br Tomas

  4. You can do this with Pivot and Preflow. We've done this in a lot of different ways, mostly using PHP scripts.
    First, create the callflows you want to route the calls to, then check in Futon / CouchDB for the Callflow ID's. (however this might be possible to integrate directly into the PHP script instead of making different pre-defined callflows).
    Then create a callflow with a Pivot request, pointing to the PHP script.
    The PHP script then can route the call to the correct Callflow ID, it just has to return '{"module":"callflow","data":{"id":"<callflow_id>"}}'

    To make the Pivot script run every time a call is being connected in you can select that as Preflow in the Callflow app -> Account Settings -> Misc -> Preflow.

    Example Pivot callflow below:
    image.png.843ba929107574f2e0489bb5a3d8ee82.png

    Example PHP script:

    <?php
    header("content-type: application/json");
    $nextcallflow="0219483204983";
    die ('{"module":"callflow","data":{"id":"'.$nextcallflow.'"}}');

     

  5. I don't know if it's possible to integrate into Monster UI, we are running the Call Center app in a separate Kazoo UI installation (but on the same server). Our Call Center customers need to login at Kazoo UI separately.

    You also need to know that the Call Center app isn't very good, however it lets you setup and manage ACDC queues and agents, and the agents can see all calls in the queue(s), and also log in and out from the queues. That's about it.
    A lot of small bugs exists, one is that the call list isn't sorted correctly (calls gets in random positions and not in order they called in) etc.

    But it meets the absolutely most basic needs to provide a call queue service to customers.

  6. Hi!
    This is (as I can see) exactly the same issue that we've tried to solve from day 1 using Kazoo. It's a rather big issue for some of our clients!
    We've solved it in a rather dirty way, however it's working, see post below.

    It would be nice with another solution, like a setting in ring groups for outbound CID or something similar...
    The solution that @Rick Guyton is showing just solves the problem for manual outbound calls, not calls from a ring group etc.

    See (one of) my previous post regarding this;

     

  7. Just tested the minimum recording time. It doesn't work as I expected.
    The caller (who is recording the voicemail message) doesn't get any information that the message was too short and not saved. Freeswitch says "Saved" anyway, but the log says "attachment length is 1820 and must be larger than 3000 to be stored".

    In FusionPBX the caller was informed, like "The message recorded was too short, try again" or similar...

    To get advantage of this option, there must be some "feedback" to Freeswitch that the message wasn't saved.

  8. We're using a custom back-end that communicates with the mobile app.

    Main reason for this is that the app was originally developed for another PBX (FusionPBX). Another reason is that we use functions not available in Kazoo, also security issues.

    For now the back-end needs to be installed at the Kazoo server, our intention is to make the back-end communicate with the hosted platform also. The idea is that we host the back-end for those customers.

×
×
  • Create New...