.png.a3319222f564382ca8ea6cbd2d50b91e.png)
FASTDEVICE
-
Posts
437 -
Joined
-
Days Won
26
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by FASTDEVICE
-
-
It appears that when a call gets forwarded, the system creates two call recordings; the first being, "Your call cannot be completed as dialed..." and the other a proper recording of the conversation.
-
I'm getting a lot of zero length files being created. Is anyone else having this issue? I'm not looking for coding solution to prevent them, but just curious what scenarios are creating them.
Also, I'm getting a lot of, "This call cannot be completed as dialed" recordings. Any thoughts on how these get created? -
This is something I've discussed with Aaron several years back. Glad to hear it may be available soon.
-
I haven't looked at what *98 passes as arguments, but "me thinks" it's possible.
-
2600hz is working with me to resolve the BLF resetting to idle after 24 hours. As for the auto-login I'm assuming your using the "Check Voicemail" advanced widget in Advanced Callflows. If so, it will always ask for box and password.
-
Truly, there is no NAPTR record for the Server Host/ Realm. I understand it getting the SRV record for Proxy, but Server Host has none... that's where I'm confused.
-
I just check and the 2600hz provisioner places a port 0 in for the Server Host. How does the Server Host manage to figure out the proper port of 7000 when set to zero?
-
I see this working differently from manufacturer to manufacture. On Yealink there is only one option to enable Transport type, but on Polycom you can enable the Proxy separately from the Server Host. I'm assuming that on Yealink you must still set the Server Host's port to 7000 or your going to get DNS failures???
-
I want to start a thread for questions related to the use of DNS NAPTR.
My understanding is that we are to use this method for Outbound Proxy, but I'm uncertain how it applies to the Server Host aka realm. -
Still waiting on some clarification on using MWI... Is it necessary or not to enable?
-
I was wondering how important it is to enable MWI Subscription. The voicemail indicator appears to work regardless of it being enabled or disabled. Is there a preference and why?
-
@lazedo, been testing this feature and while it works initially, the BLF resets to idle state every 24 hours.
-
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 Ringing
- Ext. to VM answers
- Menu/ Media answers
- Menu to Extension Ringing
- Menu to Extension to VM answers
"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",
Is it possible to setup local survivability?
in Product Discussion
Posted