Rick Guyton

Were those MACs assigned in another account before? I've seen problems there. Long story short, most times, if you just delete the device(s) and come back in an hour it'll play nice.

Perfect, that's what I was looking for. Somewhere to point and say that it's documented to work this way. Thanks Baze!!

Ah, see that's what I was thinking and that was what I was seeing from my tests. But, I wanted to make sure it wasn't just randomly working that way.

I have a client that wants to be able to close their office manually for staff meetings. What happens if there are two TODs that are true simultaneously? In other words, what if office hours TOD is open AND Staff Meeting TOD is open at the same time? Example call flow below: http://i.imgur.com/Dy8IVJD.png Do I have to do something more like this instead? http://i.imgur.com/QEzqDDk.png I know the latter will work, but it just seems overly complex.

On the last reseller call, I told you guys I'd give you our best practice for allowing clients to force their office open, closed or reset back to schedule. This is our process. BTW, this looks WAY worse than it is. Do it a couple times, and you can complete all of this in just a few minutes. SETTING UP BUTTONS: 1) Pick three sequential start codes to use. i.e. *89, *90 & *91 (We don't have a standard for what codes to use, recommendations would be awesome) For us, the first number is always for force open, the second is always for force close and the third is always for reset to schedule. 2) Creating your "Force Open" callflow. a) Open ADV callflows, then create a new callflow. b) Click Add number, extension radio box, then *89 in this case. c) Drag over a manual presence action and assign it ID: *89, make status busy. (this will make our OPEN light turn red when pressed) d) Drag over a manual presence action and assign it the next feature code number *90 in this case, make status Idle. (this will turn off the closed button's busy lamp if it was enabled previously) e) Drag over Enable Time Of Day and select the TOD you are toggling. f) Save Changes g) Click the Label icon and label the call flow *89 {TOD CONTROLLED} Open. In my example this controls a time of day for a company called Walker. So my label is *89 Walker Open When you are finished it should look like this: http://i.imgur.com/ubfOvgY.png 3) Creating your "Force Closed" callflow. The rest of these callflows are very similar. To reduce confusion, I always keep the lowest Presence on top (the open feature) and the middle presence below that (the close feature). So the only things that change are the status of the lights, the end function of TOD and the label. So, I'd basically duplucate Step 2, but set the extension to *90, set *89 to Idle, set *90 to busy and use the DISABLE time of day. Result should look like this: http://i.imgur.com/ACb7RLy.png 4) Creating your "Reset" callflow. Set EXT to *91. Both *89 & *90 should be idle now, use RESET time of day function at the end. Result should look like this: http://i.imgur.com/YRYq5AE.png 5) Finally, you use 3 buttons on the phones and subscribe them to *89 (OPEN), *90 (CLOSE), *91 (REST Schedule) TRAINING CLIENTS: First things first, I tell the clients to press the buttons and WALK AWAY. I tell them that she doesn't like to be hung up on and they will regret it if they do so. (wife joke happens more than I'm proud of here) Why? Well, if the client's supper fast on that hook switch, I've seen the system complete the BLF status, but never get to the TOD change. So, the lights will show something different than what's going on. Then I explain how the buttons work. I tell my clients that the Open button will open the office until the end of time. I tell them to use this if they want to open the office early one day. But, to press the reset button after normal hours start otherwise the'll surely forget to do it when they leave. Then I tell my clients to use the closed button for vacations, holidays, ect. I explain they they can just hit the closed button on their way out the door after normal business hours and the system will just stay closed until they come in 2-3 days later are RESET normal operation. Again, I explain CLOSED will keep them closed until the end of time. I touch on the reset button real quick, but usually they get it by then. END EFFECT: For 5 minutes making the call flows and another five or ten explaining how the buttons work, I NEVER have to deal with holidays. And the end users can very easily manage this stuff themselves. The lights provide a reminder when the office is manually forced open or closed. So, I never really get calls about why calls aren't coming through. They look at their phone and realize it immediately.  FUTURE EXPANSION: It's bothersome to me how many buttons this takes up. I've been playing with the idea of making a single button that leads the client into a menu system to open, close or reset office hours. Then making that single feature "busy" when closed "ringing" when open and idle when reset back to schedule. If I find a client that'd benefit from this I'll do it an post my results. So far, it's just not that big a deal to me since the phones I use have so many programmable buttons. Good Luck!!!

That's really cool. I didn't know that they released that. We're trying to standardize our router hardware right now actually. Microtik is really interesting, but we have very little best practices information on it and even fewer local experts we can reach out to. Le sigh

Thanks!! We are using Icinga2+Graphina on linode for server. Raspberry Pi 3s + Raspbian Lite + Icinga2 Client + These nifty cases http://amzn.to/1sRU1R5 for the endpoint data collection.

Ok, I know there was a lot of controversy on this. But we finally got out monitoring tool up and running. This particular client is having sporadic issues where their latency jumps to 2000+ms Next time it happens, I should be able to tell where the chink in the armor is...  http://i.imgur.com/a66Hg0f.png

Hey Aaron, any update on this?

Hey Aaron, any update on this?

Here's how we've done it before... I'm not sure if it works anymore as our only client that required it went out of business. We'd setup a ring group with 5 difference devices all 0 delay, 26 second ring time. Then, we'd setup a cellular device as a 6th option with a 40 second delay and a 25 second ring time. Finally, we'd setup a timeout on the ring group itself of 25 seconds ( Don't think this is exposed in the GUI anymore, but you can get at it via API) In normal operation, the group would ring the 5 phones, then the ring group timer would time out, so the cell would never ring. BUT if ALL devices in the ring group were de-registered, the ring group would skip them and start ringing the cell phone. It's been a while since Iv'e needed to do this, but it DID work at one point... Give it a whirl.

So, we can send SSL certs in now for the Portal? Will the SSL also apply for the provisioner? Any requirements? Will wildcard certs work? For instance, if I got *.sip.clearingvoice.com would that work? Would the provisioner use my SSL as well?

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.

We're in

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?