Rick Guyton
-
Posts
628 -
Joined
-
Days Won
41
Content Type
Profiles
Forums
Resource Library: Monster UI Apps for KAZOO
Events
Downloads
Posts posted by Rick Guyton
-
-
Hey provisioner team... You know what would be really awesome? If you could assign a username to a BLF key. Normally you'd setup a BLF key, then in the label section typing "102 Jenny", then in the value section "102". Instead, it'd be great if you could just pick Jenny out of a list.
I know what you are thinking... Rick that's kind of stupid, it wouldn't really save very much time. Yea, your right... Until Jenny leaves and is replaced by Sara. Now, I just have to rename Jenny to Sara and all 512 phones I've already configured with Jenny's name automatically update.
What think? -
Le sigh, no... Most of our users just call us and have us do all the things anyhow. Kind of feels like a waste for us by ourselves. I'd love to have it for my more self-motivated users though.
-
Hey Karl, are you sure? I thought for standard CID it was User -> Device -> Company. And for 911 it's Device -> User -> Company
-
He he he, yea... that's a deep well. QOS in general is just a way of tagging a packet of data with it's priority. What happens after that is up to whatever network devices look at it. Even some LAN switches might look at the packet and prioritize it over general data. This usually isn't necessary, but in some high local load situations it could be nice. Wireless APs might look at it. But it's mostly routers that watch it. Many people just stick the QOS tag on there and hope for the best with their ISP. Cox is pretty good about respecting that in my market and CenturyLink seems to aswell. But, others like integra seem to chuckle at the thought.
So, we do some bandwidth management aswell. Mikrotik, DD-WRT and Sonicwall folks do this a lot. I'm pretty sure Meraki does too, but in the background, hidden away. :) Basically, instead of relying on your ISP to treat your packets right, you intentionally pinch down how much data you allow through your router. So, if you have a 50/10 connection from your ISP, you might only "allow" 45/9 through your router. Now you are the bottleneck so you control who goes through first and last. There's a lot of ways to accomplish this HTB is my personal favorite. Others will scoff at me for this, that's ok. There's pros and cons all over the place... -
Geez Vern, I want more clients like yours. :) Merakis are nice. No doubt there.
-
Yea, I mean any connection can go south on you. Even fiber connections go down. But, the idea is to make sure you aren't walking into a service line with problems. Here in AZ, we'll see temps over 110 mid-day and it'll drop down under 80 at night. That causes massive moment just in the copper itself. A great connection at noon might spit and sputter near closing time. I've gotten a bunch of clients by setting up continuous pings and watching the results in real time. I tell people that I'll resolve these type of problems on the front end as long as they agree to sign up with us if we can make the numbers work out. Sometimes they have a bad switch, sometimes the WAN GW needs to be replaced or have some QOS setup on it, or I need to call up the ISP and give them hell to fix their end. The Icinga instance and Pis are just to automate this process really.
-
Yea, it does on the front end. But at this point, I have an image that I can put onto an SD card, pop into a Pi and then it all manages itself...
-
You probably don't have access to the reseller section of this forum. If you are reseller ping someone at 2600 and they'll give you access. Don't worry, you're not missing much on that thread. It basically says that there's no silver bullet answer to this question and that speed test.net is about as good as you can get
-
We are actually trying something new on this. We are going to try runing continuous pings to local IPs, Local GW Ip, DOCSIS modem (where applicable), WAN GW ip and Google/L3 DNS servers. We are going to run this for a few days to a week in the hopes that we will get a really good snapshot of the quality of the connection. We are using an Icinga server on Linode to record and present the data and rasperry Pis to collect the data on the client's side. I'll let you all know how it goes...
EDIT: Oh yea, ADSL sucks, just don't do it. Even if it's ok now, it's going to die a horrible death. Fiber backed/Ethernet switched DSL is ok. Cable connections are our go to. If you can get fiber to your door OMG awesome. -
-
I think the T27 is effected too
-
Yea, we just always do the crazy thing and do AccountUser1@clearingvoice.com. Doesn't seem to be any other way than doing something even more crazy/stupid like na@na.com
-
Geez guys, RFC1149's been around forever and is tried and true. Why re-invent the wheel?
-
That does suck. I don't know What The Fhone was going on there. But, I could see how that'd leave a bad taste in your mouth. I'm glad you could get it working with your polys. And there's still time, we'll bring you over from the dark side. ;)
-
Yealinks have a ton of remote control features. That and their XML app features and all the BLFs are why I'm so into them. Eventually we hope to be able to control the phones like we are onsite. The features are there, we just need to do some dev work to get it going.
Anyhow, more directly, after you enable remote control on yealinks you can go to http://PhoneIPHere/screenshot and grab a screenshot. -
-
I love the CSV idea and having a template name in the CSV would make onboarding a breeze. But I don't want to get feature greedy and delay that copy thing a day longer than necessary. :)
-
I get that. Just curious. Every once in a while one of my clients will stumble on the call recording in the GUI and want to set it up. Right now I don't have a very good solution for storing them and making them available for the client to listen to. So it's not very fun to tell them it basically doesn't work. It'd be nice to be able to honestly be able to tell them that we are working towards being able to store those recordings into a cloud provider.
-
Will we be able to store call recordings there too? The current method is kind of rough...
-
Wait, can 2600hz dump faxes to google drive, dropbox, ect???
-
Wow, very cool solution. I've never really neaded this solution before. But, I'm glad to have this one in my tool belt! Do you guys use any particular speaker with it? Or are you usually tieing into an existing speaker?
-
No, I'm saying that if you're using a Fax over HTTPS solution, it probably wasn't invented by Vitelity.
You are right there. Seems to be an AudioCodes innovation.In reality, you could probably just contact AudioCodes you could buy the same device/service
I could be wrong, but my understanding is that you need to run AudioCodes software in your cluster. So those of us on the hosted platform at least can't...which is kind of cheating.
Yes, yes it is cheating and I love it for that. :)Frankly if it's still this critical and in demand, perhaps 2600hz should sign up for the AudioCodes solution and implement it.
+1 for that! -
whether that be an API, email or an HTTPS Fax device
Darren, are you saying that there's an HTTPS fax device that's compatible with 2600hz? We use Vitelity almost exclusively as well because of the AudioCodes HTTPS fax device. If 2600hz has a similar device, I'm switching tomorrow. :) -
Also, one advantage the copy utility would have over an account wide phone model template is accounts with multi locations. multi locations accounts sometimes want different park numbers or different user BLFs. For example, Tempe will have Parks 101-108 then the receptionist on their BLFs, Peoria will have 201-208 and their receptionist, Tucson 301-309, ect, ect. If you implemented the copy utility then we'd just have to setup one phone for Tempe, one for Peoria and one for Tucson then copy, copy, copy.
CSR for SSL to monster platform
in Product Discussion
Posted