Rick Guyton Posted July 17, 2019 Report Share 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" Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 17, 2019 Report Share 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... Link to comment Share on other sites More sharing options...
Guest David Posted July 17, 2019 Report Share 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! Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 17, 2019 Author Report Share Posted July 17, 2019 (edited) 9 minutes ago, 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! 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) Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 17, 2019 Report Share Posted July 17, 2019 Just now, 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. Or even better, make a way to set the variable ourself 😄 Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 17, 2019 Author Report Share Posted July 17, 2019 @David Oh, and BTW many phones will scroll the line name if it goes over the max length. Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 17, 2019 Report Share Posted July 17, 2019 Just now, Rick Guyton said: @David Oh, and BTW many phones will scroll the line name if it goes over the max length. Ditto, and then you can't see anything lol Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 23, 2019 Author Report Share 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?? Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted July 23, 2019 2600Hz Employees Report Share 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. Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 23, 2019 Author Report Share Posted July 23, 2019 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_! Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 23, 2019 Report Share Posted July 23, 2019 12 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. Thank you! Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted July 23, 2019 2600Hz Employees Report Share 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. Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 24, 2019 Report Share Posted July 24, 2019 2 hours ago, 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. 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! Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted July 24, 2019 2600Hz Employees Report Share 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. Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 24, 2019 Report Share Posted July 24, 2019 58 minutes 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. Hmm okay, so TLDR how long until this fixed will be pushed to production for hosted? Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 24, 2019 Author Report Share Posted July 24, 2019 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. Link to comment Share on other sites More sharing options...
2600Hz Employees mc_ Posted July 24, 2019 2600Hz Employees Report Share 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. Link to comment Share on other sites More sharing options...
Rick Guyton Posted July 31, 2019 Author Report Share 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! Link to comment Share on other sites More sharing options...
Karl Stallknecht Posted July 31, 2019 Report Share Posted July 31, 2019 1 hour ago, 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! Ditto!!!!! 😄 Link to comment Share on other sites More sharing options...
Guest David Posted August 1, 2019 Report Share 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. 😎 Link to comment Share on other sites More sharing options...
Recommended Posts