-
Posts
1,768 -
Joined
-
Days Won
4
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by mc_
-
-
Perfect! Thanks
-
OK, mind filing a feature request in JIRA?
-
If on your own system, you can configure the minimum and maximum recording time in system_config, see https://docs.2600hz.com/dev/core/kazoo_voicemail/doc/README/#system-config-settings
I'm not sure what the hosted system's setting is; you could file a support ticket to find out.
-
Sweet, glad it is working!
-
Did you try the play callflow like this?
{"module":"play" ,"data":{"id":"/{ACCOUNT_ID}/{MEDIA_ID}"} ,"children":{...} }
-
If you upload media to Kazoo via the API, you can reference it in the "play" callflow with "/{ACCOUNT-ID}/{MEDIA-ID}" I believe
-
There is a simplistic quickstart guide that will show you some basic API commands.
Endpoints dial numbers, some endpoints carry around a caller ID so you "know" who is calling. Numbers are assigned to callflows which determine what to do with the caller - put them in a conference, connect them other endpoints, play a recording, put the caller in a conference, etc.
Triggering calls from a website typically requires using Click-To-Call. You can also front the request with your own server and call the conference dial command from your server.
-
Community-supported call queue app is acdc - open source, free to use on your own installation.
Qubicle is our paid call center application. There is talk of a "lite" version being free to use / open source but nothing available yet. When the app store is ready, there will be a way to purchase Qubicle for self-managed installations.
-
Please open a new thread and include logs related to the registration attempt, how you created the device and callflow, and anything else that might be relevant.
-
It needs to match your hostname.
-
Awesome! Good to hear...
-
Jonny5 needs to be turned on and authz enforced in ecallmgr to get rating of a call going.
-
You'll probably want two resource docs, each each with the "rules" regex to match your patterns.
-
You can do this using a combination of Pivot and the "set_cid" callflow action. You could also look at the "check_cid" callflow for branching based on the caller id name; if set as a preflow, that might actually work as well without having to call out to a Pivot endpoint.
-
@dvbrusselen thanks for asking! I can assure you someone else will have questions like these and not feel comfortable asking. Plus it can help highlighting where doc improvements could be made, or where inconsistencies lie that we're blind to, or things like that.
-
Kazoo logs from the server would be useful. Use the call-id to grep the kazoo log to see what was done during that call.
-
Callflows have two ways to determine if a call should be executed by a callflow:
1. The "numbers" array is a list of possible dialed numbers (or letters/unicode) that must match exactly. So "numbers":["2005","+12229992005","marvin"] would execute the callflow if any of those are dialed (after normalization).
2. The "patterns" array is a list of regexes that is used to match the dialed number.
"numbers" will be tried first followed by "patterns".
I don't know if the Advanced Callflows app exposes the ability to do patterns so you may have to use the API to do so.
Your pattern should work:
> re:run(<<"*259194712386">>, <<"^\\*25([0-9]*)$">>, [{capture, all_but_first, binary}]).
{match,[<<"9194712386">>]}Put it in the "patterns" array and it should work fine. If not, please pull logs of the call attempt so we can look at what callflows did.
-
I agree with @tomas_ at this point. Let us know if it doesn't work after clearing the browser cache or using a "private" tab in the same browser.
-
Also, please include the full request logs (the request id is a random uuid so no need to obfuscate it).
-
Are you setting the restriction on a particular device, a user, or an account? You can define "call_restriction" on the entity of choice that maps a number classifier (like tollfree, us-did, etc) and whether to allow/deny calls to those types of numbers.
-
Not that I'm aware of. Could be a nice enhancement to the branding app / notification templates. You can file a feature request at https://tickets.2600hz.com
-
It seems there is a bash script sitting in front of the actual sup escript that is failing to pass along the command line args properly. I'm looking into it.
Bypass-able thusly:
/opt/kazoo/bin/kazoo escript lib/sup-4.2.28/priv/sup.escript -? Usage: sup [-?] [-n [<node>]] [-c [<cookie>]] [-t [<timeout>]] [-v] [<module>] [<function>] [args ...] -?, --help Show the program options -n, --node Node name [default: kazoo_apps] -c, --cookie Erlang cookie [default: change_me] -t, --timeout Command timeout [default: 0] -v, --verbose Be verbose <module> The name of the remote module <function> The name of the remote module's function
But I'm working on a fix for the bash script sitting in front of this invocation
-
Try the long arg version 'sup --help' (although, sup -h worked for me so not sure).
-
You'll probably want to capture the network traffic to see what PHP is putting on the wire to the server. Or see if the PHP cURL stuff can write verbose logs to a file or something. I copy/pasted your JSON to use for my cURL command locally and it processed fine. Let's see what your script is putting on the wire and maybe it will reveal why the JSON is corrupted when Kazoo receives it.
rfc4235 and rfc4662
in Starting Out and Training
Posted
AFAICT Kamailio supports RFC 4662 (https://www.kamailio.org/w/interoperability/)
So Kazoo should support it or adding support should be straightforward. Can't speak authoritatively on that though; have you tried it?