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
-
-
14 minutes ago, Plau said:
So there's a security flaw with a number of the older firmwares, so I'm working on updating all the Polycoms to newer versions of the firmwares that doesn't have the security flaw. I was originally going to update to 5.8.4, but it looks like I'll have to go to 5.9.3 because of this issue. Once we have it QAed, then we'll announce the release to Production.
To be clear, I updated to 5.9.2 and it works. 5.9.3 wouldn't be necessary unless there are other needs.
-
7 minutes ago, Plau said:
Looks like it's an issue with the older firmwares. It's resolved in 5.9.2.
Awesome research Plau, thanks! I've upgraded to 5.9.2 and confirmed it's fixed. Any idea when that beta tag will be removed from it? I really hate running beta anything
-
Not sure I completely understand the scenario. But, have you considered doing a Pivot script for this? You could setup a callflow that reaches out to your server, your server could offer code options, user presses a corresponding code, done. Just a thought...
-
1 hour ago, Plau said:
I guess I wasn't that clear when I wrote my post earlier. It doesn't happen on Blind Transfers, but will always happen on Attended Transfers. It only happens when a Transfer button is pressed before the phone is no longer on an active call. That's why it doesn't happen the second time you press *. You can't recreate it when the phone boots up and press * for this same reason.
Blind Transfers doesn't actually fix the issue, it's more of you won't run into it because it's a problem that only occurs with Attended Transfers.
Oh, thanks Plau, I misunderstood what you were saying. Thanks for the clarification!
-
2 hours ago, Rally IP Admin said:
Try factory reset and wipe off all call histories. What's the firmware version?
f/w is the provisioner default of 5.4.6
This phone was very recently wiped clean and provisioned from provisioner. Plau and Baze have both replicated it, so I don't think it's the phone's config.
More info, I did change the default transfer type to blind. And at first I did think this fixed it. BUT, then I did an attended transfer and it happened again. So, apparently, pressing the star button after doing any attended transfer causes "10" to be dialed instead of *. Very strange stuff...
BTW, @esoare the embedded video works, thanks!!
-
Nice, thanks Eugene!
-
1 minute ago, Plau said:
I'll reach out to Poly to see if they can shed some light on this issue.
Thanks Plau!
-
Just now, Plau said:
I just tested it on my end on a VVX601 and I do see it happening. I never noticed before because I would only dial off hook or pushed the speaker button.
I was able to avoid the 10 popping up when pushing * by setting the transfer type to Blind (both through the phone and provisioning the Polycom with the default transfer type as Blind)
Did this use to work before? Or is this something recent?
Thanks for looking Plau! I couldn't tell you honestly, I have been pretty hard core Yealink for quite some time. It's only recently that I've dipped a toe into Polycom again. Do you think you guys could use your contacts at Poly to get more info? Obviously, switching the default transfer type to blind isn't going to be a good fix.
-
Hey @Plau Any thoughts on this?
-
Ok, more, it doesn't appear to have anything to do with parking itself. It happens on the first call after ANY transfer. Video attached below (this time as a web link). I get a call from 1002, transfer to 1003. Then, press * and instead of dialing *, it dials 10. So strange...
-
Just now, Baze said:
Oh i see - should have watched video first. can you paste your dial plan?
Heh, to be fair I've been fighting with the video, probably wasn't there when you looked.
It's the provisioner defaults for this phone
Quote*xxT|xxxxT|[2-9]11|0T|011xxx.T|[1][2-9]xxxxxxxxx|[2-9]xxxxxxxxx|[2-9]xxxT|x.T|*xx.T|**xx.T
-
@Baze: I think that only applies if you are using keys to parking. I'm just using a transfer to *3 in this part. Thanks for the heads up, I'll be doing it based on keys next... Probably saved me another post.
@Karl Stallknecht: I'm seeing why youtube is such a thing. I'm trying to get it into a format that plays on Firefox and under the max attachment size.... Got video working, just no audio
-
I'm creating a series of end user training videos right now. And I've run into an interesting issue on Polycom phones. Whenever I park a call, then go to retrieve it, the phone dials a 10 instead of *. Video attached (sorry for the quality, I had to compress it a lot) Any thoughts on what would cause this? How to fix it?
https://photos.app.goo.gl/CbrryvqgiwWnXtqi9
Every time I do a park by transferring this happens...
-
On #1, I know Yealink and 2600hz have a partnership to enable phones that are setup on Kazoo to directly and automatically be placed onto RPS. However, a few years ago, you just had to get your own RPS account from yealink, then login there and point them to the provisioner. Then, they'd provision, but it was a two step process, one on yealink's site and one on Kazoo. I think HTEK said they have a similar setup. That they have a portal that you can log into to push down inital configs. I'd check with whatever distributor you used to get access.
-
@Karl Anderson Thanks a bunch! It looks like the callback feature is working on option 9 now! Would it be possible to get the VM instructions to list off this option? I notice that option 4 to go back and option 6 to go forward a message also aren't on the VM instructions. EXTREMELY helpful either way, thanks again!
-
-
2 hours ago, mc_ said:
PR - pull request on the git repo. Once the PRs are opened and merged into the 4.3 and master (5.0) branches, new RPMs will be created containing the fix. We'll also likely hot-patch the platforms we manage to alleviate the issue.
Timing for the updates/hot-patches is unknown until the PRs are accepted and we see what the OPS workload is. But we'll update here when things are live on the various systems we manage.
Do we have access to the provisioner git? I thought it was private.
-
10 minutes ago, mc_ said:
We're meeting about this today. Should have an idea of what next steps are then. Sorry for the disruption; hopefully things will be sorted out and a proper announcement can be sent around all this.
Thanks for the update @mc_!
-
Any update on this? I just had to change the name of 50 some odd devices in one of my accounts. And while that was an annoying amount of manual work to have to do, I now have to update each of their provisioning profiles now too and that takes even longer... Is there a work around at all aside from manually changing each??
-
-
While I was doing my Noise Cancellation Test, I noticed that nothing was populating under "Stored Recordings". However, I was able to access them via my AWS S3 bucket portal. Anyone else have this issue?
-
2 minutes ago, Darren Schreiber said:
THIS
IS
AWESOME!
2 minutes ago, Baze said:This is amazing!! One less thing on my to do list which I'm thrilled about.
Really nice work, Rick.
Thanks Guys!
-
During KazooCon, Yealink and Polycom both promoted their sound cancellation features. I decided to do some testing on these features to see just how effective they are. I thought I'd share my results and testing methodologies with you all.
Testing Methodology
I created an audio file that included music, conversations, kids playing and dogs barking. I've included it here for you as TestBackground.wav.
Then, I made custom configuration profiles for each setting I wanted to test. Yealink only has 4 (Off, 1, 2 and 3). While Polycom says there's no limit to the size of the variable you can use in their threshold. I noticed that 8 was the default level. And after searching around I found some people setting it as high as 150. So, I used 8, 10, 20, 50, 100 and 200 for my tests. For each of the profiles, I also changed the line name so that I could insure that my custom config was applying correctly. On the polycoms, I had to include my entire account reg line to do this, so I've stripped that data out. But, otherwise, you can download the custom files I used below as well.
I played the sound at my computer and put the phone about 12' away and 4' down from my speakers. I don't have a decibel meter or anything, but the speakers were almost all the way up. And I'd say that the music was very loud, the conversations sounded like being in an extremely busy convention center, the kids sounded like they were in my office playing and the dog was about as loud as if it was barking in my face. If that helps... Very loud that is to say.
Then I made a callflow that dumped to just playing silence and setup call recording to capture the results.
After doing this I noticed that every single test category failed to completely mask the background sounds at the very high level I initially set them at. So, I also did another round for both phones on their highest cancellation level and a lower background noise level.
My test devices were a Polycom VVX410 and a Yealink T53
Results
I have to say, even as a Yealink guy, I was very impressed with the Polycoms. And, less so with the Yealinks. I struggled to notice really any difference with the Yealink acoustic shield on vs off and certainly could find almost no difference between the different levels. There doesn't appear to be any down side to enabling the cancellation on either of the phone, even at the highest levels the voice didn't sound distorted. However, I did notice that at higher levels, the Polycoms sound like they are muted when the operator isn't talking. Is that a good or a bad thing? I'll let you decide for yourself, but I like it personally. I've included my test result recordings here as well so you can listen to them it you'd like.
When I tested at lower background volume levels, I did notice that the T53 did perform better than I expected even with the acoustic shield off. This might be due to the new microphones that they were talking about at the convention as well. But again, I struggled to notice any difference between acoustic shield being off and on.
At the end of the day, as a Yealink guy, this VVX 410 is staying on my desk and setup with Acoustic Fence & threshold set to 200.
A Few Notes
I'd say the best test hands down was the VVX 410 with softer background noise and a threshold of 200. But, even then, if you listen carefully, you can still hear my kids a little bit. 200 isn't the maximum threshold. I wonder if it would get even better at a higher level? I'd be interested to know if anyone tries it.
Acoustic Fence seems to be supported since F/W 5.3 if enabled by provisioning. However, the setting is not available in the UI in any version that's supported on the provisioner. I upgraded to the newest F/W through the web interface on the phone. After that, I could access the setting, but only in the phone's menus, not via the WebGUI.
Hope you find this valuable! If someone wants to duplicate my testing, I'd love to see if you find similar results. I've included everything you need to fully duplicate the test here.
T53_LowerNoise_Acoustic_Shield_3.mp3
T53_LowerNoise_Acoustic_Shield_Off.mp3
VVX410_Acoustic_Fence_Thresh_8.mp3
VVX410_Acoustic_Fence_Thresh_10.mp3
VVX410_Acoustic_Fence_Thresh_20.mp3
VVX410_Acoustic_Fence_Thresh_50.mp3
VVX410_Acoustic_Fence_Thresh_100.mp3
VVX410_Acoustic_Fence_Thresh_200.mp3
-
@David Oh, and BTW many phones will scroll the line name if it goes over the max length.
VVX410 dials "10" when pressing star after parking
in Hardware Endpoints
Posted
Thanks again Plau! Happy you are looking out for us. Just wanted to be sure I was clear.