Rick Guyton Posted July 17, 2019 Report Posted July 17, 2019 I've noticed that recently, the line name that shows up on provisioned phones is no longer the device's name. It's now the user's First and Last name. For example, previously if I had a device named "201 Ricks Home Phone" and it was assigned to me, Rick Guyton, the phone would display "201 Ricks Home Phone" as the line name. Now, it just lists "Rick Guyton" as the line name. It would be better, I think if it either went back to the device name OR used the user's primary extension number then first and last name. So, the phone would read "201 Rick Guyton"
Karl Stallknecht Posted July 17, 2019 Report Posted July 17, 2019 Yeah this is super annoying - users are now telling us they don't know what their extension is. I wish it would be restored to the device name...
Guest David Posted July 17, 2019 Report Posted July 17, 2019 I like the idea @Rick Guyton suggested, with a slight variance: {{user.presence_id}} {{user.first_name}} I've always preferred that formatting with just the first name due to limited display length on some phone screens. I'll pass this feedback over to our Provisioning team. Thank you for sharing your input!
Rick Guyton Posted July 17, 2019 Author Report Posted July 17, 2019 (edited) On 7/17/2019 at 11:26 PM, David said: I like the idea @Rick Guyton suggested, with a slight variance: {{user.presence_id}} {{user.first_name}} I've always preferred that formatting with just the first name due to limited display length on some phone screens. I'll pass this feedback over to our Provisioning team. Thank you for sharing your input! Expand Might I suggest taking a poll or something? I would not personally care for this. There's a lot of Joe, John, Mary and Lindas out there. Edited July 17, 2019 by Rick Guyton (see edit history)
Karl Stallknecht Posted July 17, 2019 Report Posted July 17, 2019 On 7/17/2019 at 11:35 PM, Rick Guyton said: Might I suggest taking a poll or something? I would not personally care for this. There's a lot of Joe, John, Mary and Lindas out there. Expand Or even better, make a way to set the variable ourself 😄
Rick Guyton Posted July 17, 2019 Author Report Posted July 17, 2019 @David Oh, and BTW many phones will scroll the line name if it goes over the max length.
Karl Stallknecht Posted July 17, 2019 Report Posted July 17, 2019 On 7/17/2019 at 11:52 PM, Rick Guyton said: @David Oh, and BTW many phones will scroll the line name if it goes over the max length. Expand Ditto, and then you can't see anything lol
Rick Guyton Posted July 23, 2019 Author Report Posted July 23, 2019 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??
Administrators mc_ Posted July 23, 2019 Administrators Report Posted July 23, 2019 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.
Rick Guyton Posted July 23, 2019 Author Report Posted July 23, 2019 On 7/23/2019 at 7:04 PM, 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. Expand Thanks for the update @mc_!
Karl Stallknecht Posted July 23, 2019 Report Posted July 23, 2019 On 7/23/2019 at 7:04 PM, 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. Expand Thank you!
Administrators mc_ Posted July 23, 2019 Administrators Report Posted July 23, 2019 Consensus is to revert back to the pre-existing functionality and let you guys continue to operate as you did before this change. Look for PRs for 4.3 and master in the next day or two.
Karl Stallknecht Posted July 24, 2019 Report Posted July 24, 2019 On 7/23/2019 at 9:58 PM, mc_ said: Consensus is to revert back to the pre-existing functionality and let you guys continue to operate as you did before this change. Look for PRs for 4.3 and master in the next day or two. Expand Sorry, can you please clarify? What is PRs? Does this mean it will be fixed in the next day or two and live in production? Thank you!
Administrators mc_ Posted July 24, 2019 Administrators Report Posted July 24, 2019 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.
Karl Stallknecht Posted July 24, 2019 Report Posted July 24, 2019 On 7/24/2019 at 5:20 PM, 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. Expand Hmm okay, so TLDR how long until this fixed will be pushed to production for hosted?
Rick Guyton Posted July 24, 2019 Author Report Posted July 24, 2019 On 7/24/2019 at 5:20 PM, 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. Expand Do we have access to the provisioner git? I thought it was private.
Administrators mc_ Posted July 24, 2019 Administrators Report Posted July 24, 2019 @Rick Guyton the change occurred in KAZOO, in how the data was sent to the provisioner service. The PRs have been issued and merged. Hotpatches to hosted will be scheduled when OPS can do it; not sure on the timing.
Rick Guyton Posted July 31, 2019 Author Report Posted July 31, 2019 Thanks @mc_ and @David for you assistance on this! I just setup a 15 person office and went to go fix all their device names in the provisioner, but it was already done!
Karl Stallknecht Posted July 31, 2019 Report Posted July 31, 2019 On 7/31/2019 at 6:23 PM, Rick Guyton said: Thanks @mc_ and @David for you assistance on this! I just setup a 15 person office and went to go fix all their device names in the provisioner, but it was already done! Expand Ditto!!!!! 😄
Guest David Posted August 1, 2019 Report Posted August 1, 2019 Thanks @Rick Guyton and @Karl Stallknecht!! I'd like to forward all of my thanks and appreciation to @mc_ as he is clearly the superior tiki dancer. 😎
Recommended Posts