FASTDEVICE

A potential Allstate client has the quote. Fonality wants their business in the worst way as they are now throwing in Polycom VVW 201 phones for free. The only reason I'm still in the race is my reputation for quality voice service thanks to 2600hz!  I'll see what I can do on getting them to give me the quote.   

Yes. The enable fee is a barrier to entry for some of us. I was hoping you were offering two tiers of call queues; basic and advanced. The thought was basic would be part of your standard hosted offering. 

@Rick, I'm not going after call centers, but some of our clients enjoy the idea of a queue instead of direct to voicemail. Perhaps you can work out a wholesale rate and allow us to be resellers on your account for those clients? It would probably mean onboarding new clients only, but at least it's an affordable option for many of us smaller operators.   

Promotional Pricing: Advanced Call Queues https://www.fonality.com/offers/ultimate-savings Terms and Conditions: Offer valid for new install Fonality customers who sign up on or before February 28, 2017. Subscription-based Public Cloud or Private Cloud services only with minimum one-year agreement. Not valid for one-time purchase agreements or Hybrid-Hosted® solution. Minimum subscription of 5 seats. Offer valid for Fonality Ultimate Edition only. Customer is responsible for taxes, regulatory fees, and shipping costs. Fonality's standard Terms of Service and License Agreement apply. Changes and additions after the promotional period will be at regular price. No other discounts may apply, but additional restrictions may. Ask your sales representative for details. Normal Pricing and Features: Unlimited Basic Call Queues https://www.fonality.com/pricing

Fonality is now including unlimited basic Queues w/ their service at $24.99 per user/ per month and as a special offer Advanced call queues for the same $24.99 per user/ per month. 2600hz buy-in cost to enable queues is rather expensive and that doesn't include per-queue pricing.  I don't want to lose another account over not having queues, any thoughts on a way to stay competitive?

Webhooks and websockets are intended for different purposes. Hooks are intended for server-to-server communication, and sockets are server-to-client (browser) communication. I'd expect both will be fully supported. 

I find webhooks to be highly reliable, but as mentioned, my experience is with answer. Webhooks is known to fire twice for each trigger, but @Darren states that's by design. However, you mention they sometimes fire with each leg of a call. In which case(s) of the five are you getting a trigger for both legs of a call being destroyed? as I mentioned before, test each scenario and look for how many call legs are identified and the disposition value of the inbound call leg.

Thanks for doing the testing! The purpose of the webhook is to trigger your code when the channel is destroyed. I'm more acquainted with channel_answer, but I'm guessing channel_destroy will trigger when a call leg is hung-up. This will be your semi real-time hook to query the CDRs for the disposition value. Again, the code should delay enough for the CDR to be present, query for the disposition value, do some check to see if the call_id has already been used (if not, store it), and then notify your client(s). I don't think the disposition value is contained in the webhook, but here is a very good site to capture that kind of data: http://requestb.in/ and investigate.

There appears to be five missed call scenarios:Extension RingingExt. to VM answersMenu/ Media answersMenu to Extension RingingMenu to Extension to VM answersTest each scenario and look for how many call legs are identified and the disposition value of the inbound call leg.   "disposition": "NO_ANSWER",

One other note, you'll need to play with the timing or save the call_id in a database to prevent sending duplicates.

We show missed calls in our call analytics, not as a real-time notification. I'm thinking for real-time here is what I would do: Create a webhook using the trigger, "channel_destroy" the hook fires off code on your server that first delays enough for the CDR to appear in the database (sometimes this could take a few seconds or longer) and then the code queries the CDRs looking for any <in the last say, minute> that are "hangup_cause": "ORIGINATOR_CANCEL",or "billing_seconds": "0", "call_direction": "inbound",Then, email or sms a notification to the user.

Here is what you probably want to look for: "billing_seconds": "0", "call_direction": "inbound",

@Karl, the answer is simple. You are going to get NORMAL_CLEARING in the event that any callflow element answers the call. You probably have a menu/ auto attendant or some media playing prior to ringing through to the destination.  

We use ORIGINATOR_CANCEL and billing seconds zero to show missed calls. We don't use LOSE_RACE as it's implied the call was answered elsewhere. For a close to real-time notification, I'm thinking the trigger event is channel_destroy. 

As per Logicwrath, download Postman from the Chrome store. - Change the verb to "PUT" and on the line enter http://api.zswitch.net:8000/v2/user_auth - Under the tabs, Headers; Key = Content-Type and value = application/json - Under the tabs, Body, raw; enter what Logicwrath provided. Press send! the return value "auth_token" is the token. And, yes it is a long string. Hope that helps.

I was able to create a callflow of *981001 that points to a VM. That solves the dial issue.

@lazedo - automagically a part of the feature started working around two days ago. My BLF is responding RED to new voice messages. However, my BLF key's value is set to *981001 and when I press the button it dials *981001 resulting in an error. When I manually dial or have the BLF key dial that value the phone responds with "unable to comply." 

@lazedo - automagically a part of the feature started working around two days ago. My BLF is responding RED to new voice messages. However, my BLF key's value is set to *981001 and when I press the button it dials *981001 resulting in an error. When I manually dial or have the BLF key dial that value the phone responds with "unable to comply." 

right, our extensions and vm numbers are one and the same. However, it's not working on my account. I'll send in a ticket.

My understanding is, I should subscribe a BLF to <*98><extension> on the hosted platform I.e. *981001. And, if I were to dial say, *981001, it should take me to the vmbox of extension 1001. Am I understanding that correctly?

When do you expect the feature to be active as it's not functional at the moment?

Was this released in v4.0?

At the moment we can do logging and screen popups on most CRMs, but don't support CTC in the CRM unless the CRM has an API to allow for such a feature.

It's a .net application that can integrate with web and fat client CRMs. Most notably eAgent CRM, but can easily be modified for many uses. It logs inbound and outbound calls to the CRM and even tracks call history independent of the CRM w/ click-to-call for convenience. http://www.fastdeviceusa.com/harmony Now that websockets is being released we are going to rewrite the application to support more features and introduce a web only version.  

Under the Webhooks app, for each active webhook there is an option to "show list of attempts." This in turn generates a filtered report of attempts. If you configured a webhook with a long url the report headers are misaligned and the report won't generate.