extremerotary
-
Posts
265 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by extremerotary
-
-
On 3/14/2018 at 5:52 PM, SPC-Tim said:
I am on the hosted system with 2600hz, how could I go about making this happen?
Clumsy, but you could register line 1 to user A, and line 2 to user B, then log in/out on the correct line. I know, I know, terrible workaround, but functional
-
On 3/22/2018 at 9:27 AM, Jack Noe said:
Hi all.
Im trying to configure a polycom 4000 conference phone with 2600,
I cannot find in the phone where to put in the the provisioning URL.
Does anyone have a phone set up, and can show me a snapshot of the place to put in the provisioning URL ?
What firmware version are you running on it? Anything prior to 3.3 does not have the provisioning server info available in the GUI. You can check by (on the phone) going to menu > status > application (doing this from memory, so i may be a bit off). I believe these phones support at least 4.0, so you should be able to upgrade the firmware to achieve this, but it's not necessary if you can physically reach the phone.
-
11 hours ago, Mattia said:
Hello guys,
I'm trying to understand more from conferences. I see that you can enter using a moderator pin and, if you do it, you will be a moderator in that conference (member_type = 'moderator' on conference_channel_vars). Ok, so: what can a moderator do? and how?
I saw API for mute/kick and so on but that are not limited to moderators (I should use API restriction in that case or something similiar...)
Is there the possibility to kick/mute/deaf/... someone through DTMF if I am moderator? And also can a non-moderator do these actions?
Thanks in advance
P.S. I'm using Kazoo 4.0
Hey Mattia,
There are a lot of conference options in the works! Currently, the main functionality comes from the APIs. They give a wide range of moderator options via a programmed UI to do things within conferences. We've had very good success with using them ourselves in our UI. One obstacle we are facing is, in a clustered federated environment is that during a nightmare transfer of a caller to a conference running on a different freeswitch server, some channel vars are not passed to the receiving freeswitch server, so the conference event emitted is missing some data (such as owner_id for an on-nat call). We are currently working with 2600 and the freeswitch team to resolve that. But yeah, the APIs are where the real controls come into play!
-
Looks great guys! I also understand there are some performance enhancements in 4.2, so don't forget to showcase them!
As part of the qubicle updates, will there be an event emitted when an agent gets on and off a non-queue call since qubicle is now aware of non-queue calls?
"Added ability to load all queues and recipients with single API call" - What is this new API call?
Any update on wiretap with the queues?
As part of the call recording storage updates:
"Improvements to Call Recording storage - Ensure storing call recordings to an HTTP URL works as expected (Google Drive / AWS)"
Does that indicate that these storage options are supported in 4.2? -
On 2/21/2018 at 9:37 AM, Logicwrath said:
In my past experience if you do not have something in the main "Fax Sent Receipts" field then none of the users will receive a fax sent receipt. It effectively disabled the sent receipts entirely. As a work around you can submit a fake email or unmonitored email or public folder/shared mailbox in the "Fax Sent Receipts" field and then all users should get their own fax sent receipts as well as the person listed in the field.
So you mean, if nothing is in there, notifications are disabled, but if I put some bogus address in there I, as the sender, will get the notification (in addition to the bogus email)?! That would work!
-
Hey Josh,
There is an unsupported module for eavesdrop (written by a third-party) that works okkkkay...It only does eavesdrop, and not whisper or barge. In the hosted platform, there are significant updates required to give/restrict this person from listening to that person, etc. So the business logistics behind it require some deep thought and forward planning + development.
I wonder if the community would be interested in funding 2600 to make it their own and incorporate it into their code base and hosted platform. Unfortunately it's one of those things that customers ask for, and will never use, and so it's never gotten much traction. I've only ever confirmed that it works to "listen in", and it's current state is rudimentary and needs quite a bit of love, for it's rather easy to circumvent the "permissions" required to validate the caller is allowed to listen to the other user.
-
Hey guys,
When an email-to-fax is sent using faxboxes, is it possible to configure the notification to only be sent to the email address that sent the fax? For example, if the smpt_permission_list was "@2600hz.com" and James sent an outbound fax, if the notifications.outbound.email.send_to is set to fax@2600hz.com, then everyone in the distribution list would have a copy of the fax attachment, and know that James sent out a mass advertisement fax about pivot. I would like it if only james@2600hz.com received the PDF attachment and notification that the fax was successful (or failed).
Also, 2 side questions:
1. Can the notification email be configured to not attach the PDF (using notify, not teletype)?
2. What is the "media" element on the faxboxes document used for?
-
Hey guys,
Does anyone out there have a setup guide for configuring storage to use Google Drive? I read a very good article on the doc site regarding storage plans for S3, but I'm looking to use Google Drive.
I understand the basics, but I'm cloudy on exactly how to configure this. For example, from the doc site I see the schema for the storage attachment google_drive. I get everything except "settings.oauth_doc_id". The description is "Doc ID in the system 'auth' database". Does anyone have a guide on how to create this doc and how to setup the oauth in google for this purpose?
Thanks!
-
Hey, can you provide the log lines above and below the error from kamailio, and answer a few questions?
- What version of kazoo, ecallmgr, freeswitch, and kamailio are you running? I understand that it's a registration question with Kamailio, but all the versions together will help to isolate if it's a versioning issue between anything. You can use 'rpm -qa | grep {{ something }}' to find out the installed versions (where {{ something }} == "kazoo" for example). Then, if running version 4.0+, from the command line, you can run 'kazoo-applications status' to see what version(s) are actually running (as opposed to installed). This output will also help in general to see what apps you have running, etc.
- Is this a single-server install?
- I'm sure you've triple-checked the SIP creds, but I have to ask!
Feel free to remove any personal info from the logs, like IPs or realm names and I'll take a look!
-
Let's see if we can get a quick response from the team. I'd be interested in setting a "media_id" on a conference doc, but it doesn't look like it functions that way on their doc site.
-
Are you using the fast-pickup role in kamailio? That's required for this. Hmm, in fact, typing this, you may need to enable the replaces header. Add this:
<voIpProt voIpProt.SIP.strictReplacesHeader="0" />
-
The below would be an example of creating 2 BLF keys. One for 203 and one for 204. I am assuming that, when the extension is idle, that you want the BLF to just dial their extension. In some situations, customers want it to intercom when they dial the extension. In that situation you would add a '*0' in front of their extension number in the callAddress (I.E. *0203). I believe in firmware version 3.3+, you can upload a config file via the phone GUI. So, simply copy this code, adjust the user's names for display purposes, and save as a .cfg file. Somewhere in the Settings (i think) in the UI, you can 'import config' or something like that. Just upload your .cfg file, and BOOM! It'll restart and you can test.
<call call.directedCallPickupString="" call.directedCallPickupMethod="native" /> <attendant attendant.resourceList.1.address="203" attendant.resourceList.1.callAddress="203" attendant.resourceList.1.label="John Smith" attendant.resourceList.1.type="automata" attendant.resourceList.2.address="204" attendant.resourceList.2.callAddress="204" attendant.resourceList.2.label="Carson Wentz" attendant.resourceList.2.type="automata" />
-
21 hours ago, FASTDEVICE said:
Not messy at all, and that solution has been discussed in-depth several times on the forum. I even use that method in my after-hours menu options for forwarding. However, I was thinking more on the lines of allowing the user to set the forward number from the outside. If the number is static and won't change, then using time-of-day as an off/on switch works great.
Spot on. Pivot is the ultimate flexibility for those who are familiar with programming!
-
On 1/2/2018 at 4:40 PM, FASTDEVICE said:
This is a job for Pivot.
Hmm. I agree this is a great application for pivot!
A user could also use a less elegant solution perhaps by using a time of day. Kind of like, "all the time ring my phone". Then set the "all other times" to forward to a specific number. Then the user could create a callflow to toggle that specific time of day. It's messy, but would probably solve the use-case.
-
I don't know how this translates to the advanced provisioner, so hopefully another member can give some instruction, but below are the configuration parameters you'll want to use. These enable the device to use the replaces header in a directed-call pickup situation when the BLF is ringing. So, from a use case:
You are watching extension 101 on your device. A call comes in and rings extension 101. Your BLF lamp is flashing for 101. You push the BLF key and intercept the call that was ringing 101.
<call call.directedCallPickupString="" call.directedCallPickupMethod="native" /> <attendant attendant.resourceList.1.address="{{ line_key.extension_number }}" attendant.resourceList.1.callAddress="{{ line_key.extension_number }}" attendant.resourceList.1.label="{{ line_key.label }}" attendant.resourceList.1.type="automata" />
-
Are you a hosted customer of 2600hz, or are you asking "As a service provider, how do others handle resellers/customers bringing their own carriers?" - I ask, because I don't know how 2600hz hosted platform handles those.
As a service provider with your own cluster you have a few options. You can create carriers in the offnet database that require that flag in order for them to be used. Then, in those accounts, you'll set that flag on the devices. This will fulfill the outbound requirement. Inbound is pretty straight-forward; add them to your ecallmgr ACLs, and the numbers will route as they will.
There is also some functionality in the 'resource' callflow module (newer version of 'offnet') that allows for a specific account to have its own carrier list. For more dev info on that, take a read on this article and let me know if you have additional questions: https://docs.2600hz.com/dev/applications/callflow/doc/resources/
-
Welcome back!
There have been significant improvements in Kazoo in the past few years. Check out the doc site for starters. There are some tutorials on system installation of the 4.1 version, and a lot, lot more documentation on the APIs and other inter-workings of the application. It's a developer's best tool!
https://docs.2600hz.com/sysadmin/doc/intro/about/
I absolutely love your enthusiasm and willingness to contribute; that goes really far around here. Unfortunately I'm not able to answer a lot of those questions because I'm not a hosted customer of 2600hz, and I don't know the issues that you were running to in the past.
From my experience working with their APIs, everything that you've listed in bullets 1 and 2 is working. Call rating I'm a little fuzzy on because we don't use that particular feature. The limits in jonny5 work great.
I have no experience with braintree.
I can't speak to 2600's position on carriers, so those questions I'll leave to @Darren Schreiber
As for documentation - I guess it depends what kind you are interested in creating. That will determine the best place for them, and I know Darren can also assist with that question. Great to have you back in the community! I look forward to helping you out where I can!
-
Hey Erik,
Thanks for the feedback! Have you filed a feature request at 2600hz.atlassian.net yet? I know the qubicle team is working on reports. There are some data points already available that you can take advantage of if you are running your own cluster. Let me know if you are, and I can provide some help in that area. Otherwise, I think you're waiting on 4.2 for better reporting (I could be wrong on the version, but i believe it's 4.2).
-
On 11/28/2017 at 2:59 PM, Jack Noe said:
outbound calls
Hey Jack,
Can you provide a call example? Sometimes there are session timers that would cause this. Other times there are limits for the termination provider. There are a lot of variables in play, and some logs or a call example would be helpful.
-
Hey Jack,
There are a lot of factors to consider when displaying call recordings in a UI. Mainly surrounding permissions. I don't believe Monster has these permission sets [yet]. Utilizing their data store component, you can immediately send files elsewhere that could be accessed in a UI like AWS or google drive. So this could work for you if that's something you can set up given your current position with 2600. I.E. I don't know if you host your own cluster or use their hosted product.
In our UI, an administrator sets permissions on the user that is logging in. They set whose recordings the user can access, and what actions they can perform on those recordings. For example, the sales manager can access the sales people's recordings, and his own recordings. For his recordings, he can download them, stream them, lock them, and take notes on them. For his sales people, he can do all those actions, read the sales people's notes, add more notes, and even delete the recordings. But then, like the support manager, they can't even see the sales people's recordings. So i hope you can see how complex the permissions are, and if this is something you want, I suggest filing a feature request in the JIRA portal - 2600hz.atlassian.net . There are a lot of HIPPA compliance around the storage and retrieval of recordings too, so that's a factor to consider when developing a UI for them :-)
-
The 201 uses the same parameters as other VVX models running the same firmware, so you'll be good to go.
-
@mc_ - you beat me to it!
Based on conversations I've had about our own scalability, Kamailio servers support between 25-50K devices per box. This number varies based on BLF subscriptions and SIP timers such as keep-alive OPTION messages, REGISTERs, and general call volume. Kamailio is cluster-able, so with the use of SRV records, you can spread the devices out across many servers. I suggest doing N+1 to ensure that if a single server or zone goes down, the remaining infrastructure can take on the rest of the load.
FreeSWITCH scaling is more reliant on usage data in calls per second, and whether certain features are turned on like video, encryption, etc.
I'm not sure I agree with James on the 'lots' of growing pains, but as mentioned, in every deployment there are different use-cases and potential ceilings that have never been hit before. The one thing I can say is that 2600 has addressed every issue we're ever had with scaling very professionally and prioritized based on any customer impact.
-
Apologies, I hit the 'submit' button a bit fast!
Out of your 250K, are they all hosted, or are there some behind premise-based PBXs? If some, how many would you say fall into that category?
-
What kind of usage are you talking?
Do your end users have a heavy usage on any single feature, say, like BLF, call park, forwarding, or anything like that?
Whisper/eavesdrop on hosted?
in Product Discussion
Posted
@Josh Robbins
Were you able to get this to work in your private cloud? If not, PM me and i'll walk you through it. But again, it's not supported by 2600, so if they do an update and break it... oh well!