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
-
-
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!
-
Hrm, I don't think it's router config. One of my clients is using a highly standardized router & firmware across all their locations. They have no issues at most locations. But, one does so regularly.
-
We seem to have never ending issues with BLF. I understand that some at 2600hz kind of write this off and think it's just for "old line key" users. And that is true to some extent. But, none the less it is vitally critical to the operation of some of our client's businesses. I've had two clients call me today to tell me that they are having more BLF issuses. So I believe there is a problem once again. But, the frustrating part to me is that I don't know how I'm supposed to even start diagnosing these issues. Can someone, anyone, please give me a concrete method to diagnose and resolve problems with BLF?
I know that there's the presence tab under the debugging tool. But, I have know idea wat BLF states 1,2,3,4 or 5 mean or what PR stands for. Even if I did though, what about situations where some phones show different lights than others? Obviously, some phones will be in line with what the server's status is, while others won't. What can cause that? What can be done to prevent it? -
What do you want is a DISA. It's available in advanced call flows. It asks for a pin code and then allows you to dial as if you were in the system. I never thought about using that to forward phones. Good idea!
-
Awesome, that'b be great!
-
@FASTDEVICE Yes, that's what we are needing too. Sure would be nice if it could be done without requiring a redundant license on the child account. But, heck I'd even pony up for that at this point...
-
Hi Josh, I've seen settings for this under Advanced callflows -> Devices -> (Pick a Device) -> Advanced -> Audio. And in the provisioner under the Lines section, in the advanced settings at the bottom.
I have NOT tried this yet though! I had a client what as supper worried about it, then management changed and they didn't care anymore. So, I left it. But, when I was talking to 2600 I remember them telling me to go into these two areas and make sure I was using the zswitch.net domain and not a white labeled one. Maybe give that a try? Please post back and let us know how it goes!
EDIT: I'm not sure how "supported" this is though... FYI -
So..... about that redundancy issue with Peerless... Resolved???
-
Totally agree. Don't forget about call recordings! I kind of hate that call recordings is in the UI at all since it's almost completely non-functional for clients. Oh any analytics of any kind. :)
But stability is king in our book and 2600 is kind of hard to beat on that front. -
LOL, ok. Thanks for the clarification. I was raging for a minute there I'll admit. :)
-
I'm confused. Peerless is one of their providers... Why wouldn't they fully support them?
Darren was talking about why peerless failed the way it did above and siad they were resolving it. I was just wanting a status update on that. -
Hey Darren, can we please get an update on the redundancy issue with peerless? Has this been resolved?
-
So, I've been thinking about this a lot. Ya know, if there are conflicting extension numbers, there's a really easy work around for this. You could just add the star coded extension in the parent account. For example, If you have ext 100 in ClientAccount1, and another ext 100 in ClientAccount2 you could just add *60100 to the ext 100 callflow in ClientAccount1, then *61100 in ClientAccount2. If a user inside either account dialed 100, it'd goto THEIR ext 100. But, ClientAccount2 could dial *60100, it wouldn't be valid in their account, so it'd go searching in ClientAccount1, find it then route it.
So, nevermind my last post, I think all you caveats would be fine. How do we get this ball rolling? -
I tried to sign up for a whitepages.com account to change the caller ID and couldn't figure it out. Maybe I'm just not tech savvy enough. :) I also found an 800 number on T-Mobile's site and the option they say to press is no longer valid. If you drill down into their menus they pretty much redirect you to the site. My hate for the service is growing by the minute.
Editing device in "Advanced Callflows" resets "Advanced Provisioner" settings back to defaults
in Product Discussion
Posted