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_
-
-
Looks like the device supports Sprint's LTE band so I suspect its possible but can't say with authority. Worth contacting sales@2600hz.com to see if its as simple as getting you a SIM.
-
What config files did you change? You can have Kamailio receive traffic from phones over TCP and send it to FreeSWITCH over UDP just fine.
Bigger picture, what are you trying to accomplish?
-
Basic idea is here: https://docs.2600hz.com/dev/core/kazoo_auth/doc/oauth/#using-google-drive-for-voicemails
Doc needs cleanup to render better though. Use https://github.com/2600hz/kazoo/blob/master/core/kazoo_auth/doc/oauth.md
-
Have you captured the Kazoo/FreeSWITCH logs of an attempt? If we could see those it would help figure out where things are going awry.
-
A couple quick thoughts I had:
- Branch based on caller id - presumably internal calls will have internal CID (3-5 digits typically). Branch to user->voicemail. If CID is longer branch to voicemail.
- Assign two extensions - a "public" and a "private". So internal callers know to dial 5xxx and external callers get 4xxx (or whatever scheme makes sense).
-
Actually, I wonder if you could route based on the caller ID first. Then you can encode the Time-of-day route to match what the allowed calling times are for each device/user.
-
Can you give me a concrete example of what your dial_plan is, the number dialed, and your callflow configs?
-
- The "Request" username is normalized to e164 if possible from the get-go. Depending on your e164_converters, they may correct the request to something not accounted for in your dial_plan.
- The classifiers are in the number_manager config. You use the classifier name as a key into the call_restriction object to allow/deny/inherit.
- The classifier key is used (so in the example "tollfree_us", "unknown", etc would be the values to use in the call_restriction object.
- Pretty print is only used for display purposes in the UI; unrelated to call processing
- You have to escape the backslash to make it literal to make the regex be valid. See here for example
-
I can't think of an easy way to encode this in the callflow JSON structure, personally. You can create an account-wide restriction using the "no_match" callflow and the time-of-day callflow action.
You can always send the call to Pivot and create a script that controls outbound dialing rules there, of course.
-
1. You could use Pivot and maintain the list of device->allowed_numbers in a db. Then you can create a UI where you/the facility can manage what numbers a device can dial.
2. You could create a "dial_plan" object on the device that whitelists the allowed numbers and rewrites all others to a "can't dial this number" recording (like adding a prefix "BARRED" and having a callflow pattern for "BARRED{\\d+}")
Those are two quick thoughts with no testing so buyer beware
-
Probably though I find the docs site comes up using duckduckgo. I don't think we've tuned it much and should probably add redirects from the wiki somehow. The big push is getting content moved over; making it discoverable to the search engines hasn't been prioritized yet.
-
Also, there was open-source carrier management in KazooUI but there hasn't been one in Monster open-sourced yet. I don't know the timeline but I'm pretty sure the intent is to open-source it once its "finished".
-
Your assurance is that you can fork the open source work and maintain a copy yourself. AFAIK there are no open-source components in Monster or Kazoo that have been changed to closed source.
-
I will throw in doing similar things on the server side (never hurts to have redundancy!):
1. Classifiers can be used to restrict/allow dialing numbers. In your example, a classifier for "\\+?1900\\d+" could be added to deny access to these numbers
2. Dial plans can convert "local" dials to appropriate representations. You can prepend area codes, country codes, add access codes, whatever is needed.
These will operate independent of the phone manufacturer which is nice in case a phone is misconfigured, tampered with, credentials stolen, etc. Good security is built in layers (just like ogres and cakes)!
-
Perhaps you could share where its failing and we could go from there? How did you install Erlang? What version? Etc...
-
@Andreas Mueller you might want to use CentOS 7 and the install instructions here: https://docs.2600hz.com/sysadmin/doc/install/install_via_centos7/
In any case, walking through those steps might help you figure out what is wrong in your existing system as well.
-
The install guide has a lot of those commands as part of setting up a server. Want to contribute a v4 cheat sheet to the sysadmin repo?
-
I don't think this is currently possible. I know there's work done to make conference profile generation more flexible but don't immediately recall if that includes account-specific overrides.
-
I believe this is controlled in the conference profile config in the conference system_config doc. "moh-sound" for the default profile is "$${hold_music}"
-
Perhaps it would be better if you specify your requirements and we can tell you if Kazoo meets the need? Of if there's something in RestComm that you can't find in Kazoo, maybe we can point you in the right direction?
-
The wiki is in the process of being deprecated. Some of the pages were "auto-imported" into the docs site but require refreshing and updating to render properly. For instance, the SUP page can be found here. It needs love though; want to make the updates and issue a pull request? There's an edit link on the page if you're signed into Github.
-
Hi @Luigi and welcome! You will want to check out our Global Infrastructure program. You can also reach out to the sales team to talk through your requirements, hopes, and dreams. They'll walk you through your options, give you a demo of what the platform looks like, etc.
-
And to be clear, this is changing so that the billing component is more general and less tied to braintree. Not sure on roadmap / timeline but it is an active priority.
-
I assume base url is http://server.com:8000/v2 (v1 is deprecated and should not be used anymore).
Bridge calls between accounts using Pivot
in Product Discussion
Posted
Not really. Most operators still bill account A for calling account B, even if the call doesn't leave the system. You might assign "internal" DIDs to your accounts' callflows that you track (that aren't route-able); since you track them you could "dial" "abc123" to route to account A's "123" callflow? Hacky but....