Jump to content

FASTDEVICE

Members
  • Posts

    437
  • Joined

  • Days Won

    26

Posts posted by FASTDEVICE

  1. Wouldn't it be easier to give each branch their own account and tie them together using DIDs and landline devices? I.e. ext 9000 is a callflow with a landline device that reaches the main DID of another branch where the caller can be greeted by the auto-attendant of that branch and then enter an extension. You will need to pay the 2600hz DID and device fee but it's a solid solution and provides separation of operating hours. I do wish 2600hz would give us the ability to call between accounts without that tax. If 2600hz is reading this, we don't need BLF across accounts just an inexpensive way to tie accounts together. ;)

    Alternatively, create callflows using vars and branching which is not available through the UI and would need to be implemented programmatically using the API. I don't recommend as changing callflows modified this way would be difficult.     

  2. On ‎11‎/‎27‎/‎2018 at 4:47 PM, mc_ said:

    Some time after Advanced Callflows was ported from Kazoo UI to Monster, the ability to have a "failure" child on the pivot callflow was introduced in case the HTTP request failed or the response was invalid.

    Hey @mc_ I remember you pointing out the usage for the failure child but I seem to have lost my notes. Would you please refresh my memory and I'm sure others want to know as well, the JSON usage for the Pivot callflow failure? Big Thanks! 

  3. @Darren Schreiber I agree with you ** mostly ** the issue with a Shoutcast stream is, a load balancer doesn't solve the issue entirely. Any interruption, regardless of the transition time causes the fault. With failover, the next set of callers will hear the stream but the current ones may or may not be lost. Therefore, there is no 100% way to be bulletproof using a streaming service.  

    @esoare there is failover for Pivot.  

  4. I don't think Yealink's button type of URL supports a post. You probably don't need to send a POST for a disposition code but if required, you can send a post using a webhook callflow element. Instead of having the trigger be a button on the phone, the user dials an extension that correlates to the disposition code instead. 2600hz made configuring a callflow webhook rather easy with the inclusion of a new UI webhook widget under Advanced Callflows.  

  5. I think 911 is handled in the "no_match" path, and from there not sure how it's further handled. However, it should be straight forward to add a webhook to the "no_match" path and use something like IFTT or Zapier to extract the variables and send an email. The only issue is testing, it's 911, you know.. ;) police may arrive.

    @Baze that implementation is super cool!

×
×
  • Create New...