Jump to content

Joseph Watson

Customers
  • Posts

    47
  • Joined

  • Days Won

    1

Posts posted by Joseph Watson

  1. The algo product line is perfect for this. They are very simple to setup and basically function as a IP Phone. When you go to add the new device in smartpbx, select the option for your device brand is not listed, see screenshot:

    image.png

    This will provide you with a username and password for the SIP registration. You will need this in the algo. Also note that the algo doesn't generally handle outbound proxy registration well, so you will need to use the realm/domain as the sip host.

    Create a new callflow and assign it an extension, I like to you 9999 for paging. Then assign the device to it.

    When the extension is called, kazoo will send an invite to the algo. The device will then answer the call, start the media and play a beep. The caller then can make their announcement.

     

  2. Hey everyone,

    Keep good data on telephone numbers is very important. In the documentation, as well as the code, there is talk of a port_out number state as part of the DID lifecycle. The number state is useful because it transitions the number into another state and also removes the number from any hunting actions thus forcing calls to go outbound. It also effectively removes it as a provisionable number within the database.

    I am able to check a DID into this state manually be editing the numbers doc in the database, but this is of course a scary process and something you do not want to let your standard provisioning folks do. So how can I transition a number into this state without messing with the database directly.

    Thanks,
    Joe

  3. 33 minutes ago, FASTDEVICE said:

    Our SMS to Email gateway is code complete and in beta testing with a couple providers.  We should be ready by next week for additional beta testers. 

    I am support interested in helping to test. Let me know what we can do to be of assistance.

  4. So I have an update. After doing some debugging, I found that the customer just deleted the AWS Access Key. I attempted to update the storage plan with a new key, but it appears that kazoo is still looking for the old key. What can I do now?

     

    kz_att_s3:271(<0.17218.4495>) S3 error: {aws_error,{http_error,403,"Forbidden",<<"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>AKIAJXP6D4AAZFZOJ2YA</AWSAccessKeyId>

  5. The permissions are set fine. New recordings are going into the bucket, and we can access them via the API. Its any recordings we transferred from the old bucket over to the new bucket we have an issue with. I need to somehow update those records so they reflect the right bucket or something.

    There has to be a sup command to do this.

  6. Hey there,

    I have a storage plan configured which points to an AWS bucket we configured for a customer. That customer now wants to host their own bucket which is fine. We transferred any recordings or files to the customer's bucket, but now when you try to access the files via the kazoo api, it fails. Do we need to "update" something somewhere since we change the bucket?

    Thanks,

    Joe

  7. I was just going to tell you, This looks like it could be an issue making quorum. In order for new DBs to be written to the cluster you need to have a quorum. If you have a node that's not responding correctly it can cause issues with the data handlers waiting for a response.

    Also if you are doing cluster replication over the WAN, that could be an issue as well if the nodes are to far apart and have high RTT. If that the case you may want to think about configuring your node into zones, which is a short term solution. Really doing cluster replication over WAN/Internet is not a "great" idea.

     

  8. On 9/4/2019 at 12:04 PM, Darren Schreiber said:

    ACDC is an old, unsupported call center module that doesn't work across federated zones and now actually has less features than Qubicle. Qubicle is one of the few paid products 2600Hz has to try and support/fund the overall project. Some folks are still attempting to maintain ACDC though so I believe it does work.

    The two are not intended to be compatible with each other and formal inclusion of ACDC at all is going to be dropped in 5.x.

    We would recommend integrating with Qubicle and it's event/feature set.

     

    Are you offering Qubicle yet to open source users. If so I would like to understand the pricing.

×
×
  • Create New...