Rick Guyton

@Karl abut DYN: Yea, I like DNSMadeEasy, but they don't support NAPTR rescords last I checked. We were using them because they have that ANAME feature and we were using that thinking they cached the IP. Turns out not, if you use an ANAME on DNSMadeEasy, it'll stop resolving if the name you were pointing to stops resolving. Opps... So as soon as I'm done with this MikroTik golden config, I'l going to deploy brand new DNS with EasyDNS + GoogleDNS. 

Hey Karl: Thanks! I didn't know you were using IPs still and having this issue. There goes that idea. I mean on the plus side, you probably didn't even notice the DYN outage. :)

Yea, I do use the advanced provisioner and that's where I'll make my changes to try it out.

This morning, I ran into this with two clients at three locations. 1) Buffalo running DD-WRT 2) Cox comunications all in one router 3) Netgear Prosafe I've been working with Jeff on some MikroTik configs. I'm getting pretty close to a fully functional config. When I have that I'll see if replacing the router works.

Yea, I'm really worried we are getting that report fatigue too. You can hear it in their voice when they call. And the wort part it I really don't know what to tell them. I'm starting to feel like a cat in a Skinner box swatting at every lever I can to make this issue stop... I think I'm going to try inputting IP addresses instead of host names for the SIP servers. Maybe that'll help? Ugh.

Thanks for the update eugine! At least I don't feel like I'm going crazy over here.

Also, parking seems to be involved a lot. Anyone seeing BLF issues with parking?

Well, guys, no dice here. I just had 2 different clients call me to tell me that their lights were going crazy today. apparently they are having issues where all of the lights will start flashing simultaneously and not stop. This problem is infuriating... Anyone have any more ideas???

Hey Aaron, can you please expand? I'm confused as well. Is there a new way to do it in 4.0? I'm about to deploy this en masse. But, I dont' want to do it if I'm going to have to re-do it in a month. Or if it would have been much simpler in 4.0.

I got confirmation from multiple 2600hz people that all of the main conference and engineering track info was recorded and will be released. I saw the cameras 3 of them actually and the record icon on all of them. So they have it for sure. Probably just need a bit to edit it all together. So I'll let you all watch that. It's a ton of info. But my big take aways are: Holy crap web sockets are awesome. So is the call center, conference, operator console and webRTC phone apps that are all fully functional in 4.0. Partially because they are all powered by web sockets and are theirfore all realtime. We can sell cellular service again. This time at wholesale rates! But there's a few qualifiers if you want to go now as opposed to a few weeks from now. Oh and Sprint doesn't really suck anymore and I figured out why. I'm about to take off. Im sure their are things I'm leaving out. I still have the agenda, I'll look at it a little later today and do my best to summarize the downstairs stuff I attended since it wasn't recorded.

Lol, that would be maddening. Are you still stuck at the airport or are you using inflight wifi? What's with airbnb and discrimination? I have to admit as a middle aged white guy I don't get that much. I really never realized how much it still goes on until we adopted our daughter. Crazy how much more you get "random" security checks leaving Walmart... Ugh. Shoot me an email when you get in if you are up for a beer or something. Rick@getclarity.biz. Darren: thanks! At least there's a reason I guess. :)

Ouch, both times I've come out I've hit a delay due to fog. You'd think they'd have that figured out by now. :) I'm staying near Portsmouth Square. It's less than a 10 min walk. Trying AirBnb for the first time. Little anxious about it. But I was anxious about Uber too. Kinda funny considering how into tech I am.

Hi all! Just landed in SF for KazooCon. Anyone else here early?

Yea, I've never played with the alert headers. I don't know if that messes with things. I just wanted to let you know that CID doesn't mess with it really so you weren't afraid to change them. :)

Yea, we've seen this too. CID change won't trigger it from my experience. But, changing the MAC or the SIP creds seems to do it for me.

It looks like he's using Kazoo 4 already. That might be a lot of the mods you are seeing. :)

Yes, firewall can defiantly cause this. These clients are all behind known PfSense or Mikrotik routers though. With configs we use very widely.

Thanks for letting me know Eugine. I don't, but I heard of people doing that.

Hello all, as you may have seen from my previous posts, we've been having a heck of a time with BLF for a long time now. When I went to a training event in SF @ 2600hz, Darren mentioned something about a previous issue that they had resolved a while back with BLF. He was telling me that there's a BLF dialog message ID that's incrementally updated by +1 every time a new BLF message is sent. This ID is tracked by each phone separately and if the tracking ID the phone receives in a BLF message doesn't match what it has on file, it's discarded. Now the issue they had and resolved was that it would transmit the same tracking ID to all phones and it would match on some, but not others. They've since fixed that(a long time ago). But, it got me thinking... I can think of a bunch of ways a single message might be lost over time especially when you are talking over a period of weeks or months. And in that scenario, from what I understand, the phone will stop responding to BLF updates correctly until it reboots or completely looses/regains registration. And then I remembered an obscure setting I read in the Yealink provisioning guide... "out_dialog_blf_enable" Yealink says "It enables or disables the phone to handle NOTIFY messages out of the BLF dialog for account X." Erika? Well, I've deployed it for a few clients that were complaining about having to reboot their phones every couple days to make sure their lights work correctly. And since then, they haven't had any problems. But, I have a pretty small sample. So, I'm hoping some of you might be willing to try this for some of your clients to see if it helps you all before I roll it out to everyone.  So, long story short, if you use Yealink and are having BLF issues, try this and PLEASE let me know if it helps them out or if you see any unexpected behavior.  Via GUI: 1) Account Tab 2) Advanced 3) Set "Out Dialog BLF" to enabled. 4) Rinse/Repeat for any other accounts you might have subscribing to BLfs. Screenshot: http://prnt.sc/cq9j7i Via Provisioning: 1) Add this line to your provisioning profile:  account.1.out_dialog_blf_enable=1 Again, if you try this please let me know either way if it does or does not work for you. Thanks!!!

Hi David, thanks for your feedback. These particular clients are all on the same cluster. But, you are defiantly correct, BLF problems are vastly reduced by pointing all phones in a domain to the same cluster.

Yep, got word from 2600 the other day. The number is the number of phones subscribers to that entry. WMI is message waiting indicator, BLF is busy lamp field and PR is for presence. Basically different status indicator protocols. There's no way of seeing what the status "should be" according to the servers.

Hi Matt, last I heard it was.

Sorry Matt, I was wrong, you can't do a *72 after coming in through a DISA. How would the system know what device to forward?? I think this is something you could accomplish through a Pivot callflow. But, I don't know a heck of a lot about them.

Ugh, yea, I didn't think about that. There would be no associated device off a DISA, so how would it know what device to forward... If you setup out of office codes like I've laid out here: https://helpcenter.2600hz.com/2600hz/topics/best-practice-out-of-office. You could toggle those via the DISA... But you'd have to use a landline device in your call flow and you wouldn't be able to update the number from the outside...

Thanks, I really liked that 3cx article. It'll tell me what I'm looking at in a PCAP. I'm off to get a PCAP now. Thanks!