extremerotary

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?

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!

@Josh Robbins 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!

@denverUser 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!

@Karl Stallknecht 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.

@Jack Noe 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" />

@Jack Noe 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" />

Spot on. Pivot is the ultimate flexibility for those who are familiar with programming!

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" />

@amn 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/

@martin 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!

@ErikM 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).

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.

@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?

Hey @Dolphin Your question is a bit loaded :-) Users alone have no real issue in Kazoo. I think you're asking about devices. How many are you looking to support? We have quite a few ourselves. Are you asking about a multi-zone deployment, a single server, something hosted by 2600, or something unique? These devices, are you thinking of devices that register, or devices that are forwards like a cell phone? Any idea of the number or ratio of each? There are various test tools that 2600 uses to load test each build that's produced. I'm unclear if the data is published anywhere, i'd defer to @Darren Schreiber to better attack that question. Load tests are created in the 'Make Busy' framework (opensource and available on github). In my experience, there are a few ceilings per zone, but since it's easy enough to create a new zone, the scaling is almost infinite. If you're looking to scale your products out of, say, an Asterisk-based platform to something more enterprise-level, Kazoo has what you need, and they're a great organization to support your growth. They've been putting up with me for almost four years now!

@Rick Guyton I believe there is also a parameter when creating a queue, that, if an agent rejects a call, it automatically sets them to away. Again, not optimal, but works. I know that Mark and his team are actively working on giving qubicle more intelligence and visibility into agents being on non-queue calls.

@Tuly Hey, As some additional information... Call park puts the call into a parking slot (obviously haha). When it does that, Kamailio stores a record of the call-id and the target-uri used for the fast-pickup role. The NOTIFY is then sent to the phone(s). It contains the call-id and the target-uri. So, when using automata, pushing the park button a second time triggers the Polycom to send an INVITE to the target-uri which starts with kfp+ (kazoo fast pickup). So your customers may notice that when they call the parking slot using the BLF button, it does not call *3x, but rather this odd string. This is normal. Please note that not all Kamailio boxes are aware of the 'fast pickup' target-uri across other boxes. This means that if the call was parked using Kamailio 1, the device cannot send the INVITE to pick up the parked call to Kamailio box #2.

@Jack Noe Hey Jack, There is a limit to how many "hops" you can have in callflows. I'll have to double check the exact number. I want to say it's around 30 or 35 "hops". When callflows branch to other callflows, that's considered 1 "hop". As a safety mechanism to prevent looping, if the callflow application branches too many times in a single call, the callflow is terminated to prevent the loop. Not exactly what you're describing, but I figured I'd lend my 2 cents to answer your initial question.

@Jack Noe Hey Jack, Inbound or outbound calls? Can you provide a call example with SIP signalling to look at?

A question was posed about how to set an offnet resource to match more than one regex pattern match in the rules[ ] array. There are 2 methods to achieve this behavior. Both (as far as I know) are acceptable, and vary only in readability. When viewing a carrier document in the offnet database in couch, you'll notice there is an array element for "rules". In the world of regular expressions, capture groups are separated by a pipe "|". So if you're looking for one regular expression to match more than one string, you can use the method listed below. In my example, I want this carrier to match a specific number in Italy, and also any calls to the Netherlands, country code 31. In order to match, the number must be exactly "+390805345208", OR +31 followed by at least 9 digits. "rules": [ "^\\+(390805345208)$|^\\+((31)\\d{9,})$" ] Looking above, this may be hard for some people to read, so it can also be written as 2 individual expressions because the rules element is an array: "rules": [ "^\\+(390805345208)$", "^\\+((31)\\d{9,})$" ]