mc_
-
Posts
1,768 -
Joined
-
Days Won
4
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by mc_
-
-
I think the endpoint callflow actions, like device, user, etc, should be extended to support custom_sip_headers in the "data" portion. Then when building the endpoints, the CSHs can be applied after the endpoints are built to any endpoints found. I don't think setting CSHs on the kapps_call record affects anything (at least not with a cursory browsing).
-
Can you put the custom SIP header on the resource document itself? Or create a clone resource for these "group" calls that has it set (and use flags to indicate whether to use the vanilla resource or the SIP-header-ed resource)?
-
Your request has gotten complex enough that I think you need to engage consulting services. Please contact sales@2600hz.com to further this request; it's beyond the scope of normal PBX / call center functionality at this point.
-
Sure, use the hangup callflow action or send a custom SIP response if you like. You can also use the 'webhook' callflow action to send a custom webhook to your server, which you can use to insert call information into your database.
-
For routing based on the dialed number, use the "patterns" instead of "numbers" array to match dialed numbers. Otherwise you can use the callflow action to route based on Caller ID
-
For outbound calls via FreeTDM, resources support setting the TDM flags necessary. Set the gateway (
gateways.[].endpoint_type) type to freetdm, then set "span", "channel_selection", etc to configure the channel in FreeSWITCH.For numbers, you can add the number just like any other number; you'll want your resource to have an appropriate regex to be chosen to route the calls. -
@Morpho9 You might check out 2600Hz's Global Infrastructure product. Then you get the team, the support, and the experience behind your platform! And you get to support the open source efforts as well.
-
Correct. Kazoo will still try to read the voicemail, for instance, for playback during a call to check a voicemail box. Kazoo will not delete attachments, however, if the metadata is deleted. Where the attachment resides is transparent to the higher level apps like Crossbar - the low-level driver will fetch the attachment and hand it up to Crossbar, cf_voicemail, wherever it is needed.
-
Hi!
First, I would at least upgrade to 3.22, the last stable version of the 3.x series. This should be straightforward enough, if you've been tracking releases thus far. Ideally you would upgrade to 4.1 which would make error reports like this much more valuable.
As for the missing CHANNEL_DESTROY events, it's hard to say where things are getting lost without logs. If you can get debug logs of a call where the caller hangs up during cf_play but the callflow continues to record/acdc queue, it might be easier to see where things get out of sync.
Again, I would recommend upgrading your Kazoo version and re-test unless you're prepared to patch your system yourself.
-
@Graham Nelson-Zutter I'll put this in my queue for tomorrow. Will let you know what I find and we can compare notes. Would obviously like to support AMI users as well! Guess I finally have to learn AWS stuff
-
@Graham Nelson-Zutter just to add, when I wrote the storage blog article, I just signed up for S3, got my access and secret tokens, plugged them in as in the article, and got uploads working. It's possible/probable that's not the typical way folks setup their S3 accounts (I have pretty much no knowledge of S3 or Amazon properties). So I can only say that the instructions presented in the blog worked for me for a minimalist setup on S3.
Obviously it would be great to have more detailed instructions for other S3 setups and adjust the code accordingly (if necessary).
-
Ah, I see the issue. The 'offnet' callflow action is specifically for global carrier usage (and considered deprecated). It predates BYOC and local resource usage; it is kept for backwards compatibility only (and explicitly sets use_local_resources to false).
Change 'offnet' to 'resources' in the callflow action and the local resource(s) should be used.
https://docs.2600hz.com/dev/applications/callflow/doc/resources/
-
If you updated via API, caches are flushed automatically. If via the DB, you'll want to issue 'sup stepswitch_maintenance reload_resources' I think (something along those lines).
-
Logs! Specifically callflow's and stepswitch's - debug level.
-
Webhooks, HTTP requests per-event, are too heavy for the relatively rapid nature of qubicle events. Websockets is the more appropriate way to receive them. You can read about them here
-
I haven't tested in a while, but you should be able to set the "Accept" header to "Accept: text/csv" and get the API response as a CSV directly.
-
No, CDRs are read-only via API.
-
Because I linked it over there, here's a presentation from 2016 on pivot
-
@esoare I gave a presentation at KazooCon 2016. Any programming language that can receive an HTTP request and respond appropriately will work.
-
You can create directories that sort by first or last name. Assign the ID returned by Crossbar to the directory callflow action and it should sort accordingly
-
I think this is a great suggestion! I've been using Couch 2 (well, the master branch that I update every week or so) to good effect. We'll have to wait and see how operations feels about migrating existing installations from BigCouch to Couch 2. I think that's the main holdup at this point.
Would love to hear experiences others have with migrations and with running Couch 2 vs BigCouch.
-
What about signing emails with PGP?
-
At the moment, just the ref docs: https://docs.2600hz.com/dev/applications/crossbar/doc/tasks/
-
@Rick Guyton it appears so. I cURL'd /v2/tasks and got the listing of available tasks.
call group with special sip headers
in Product Discussion
Posted
@Marcin Muzylo You'd need to file a ticket in JIRA and either hope it gets scheduled or talk to an account rep (or sales) about getting/paying to get it scheduled. A PR with the implementation would always be accepted too