03-15-2018 08:19 AM - edited 03-20-2019 09:59 PM
I can not believe that Cisco has classified this as a "cosmetic" concern. When a user access VM thru Jabber, there is no indication that the VM message is a Dispatch message. It creates confusion when the user tries to delete it. It will not delete, and worse, it gives no reason why. The message must be accessed using the phone to accept it. Why can't there at least be an announcement "Marked for dispatch" like when the user is listening to messages on the phone. Come on, these are both Cisco products. Why can't they play nicely together?
03-30-2018 08:51 AM
We want to deploy dispatch messaging. But this is one of our concerns.
What if people just listen to the message via Jabber, and multiple people are returning the call? At least let the user know it is a dispatch message, perhaps a color or visual flag in the UI, a way to action the message via Jabber, or like you said... an audio prompt. Just something.
03-30-2018 08:55 AM
04-11-2018 12:10 PM
04-11-2018 12:17 PM - edited 04-11-2018 12:17 PM
We actually just tried submitting it as a bug last week. But got told to submit it as a product enhancement request to our account manager. (still waiting to hear back)
I would suggest everyone else do the same. Maybe if enough of us submit a product enhancement request, it will get fixed.
09-05-2018 09:44 PM
I also have just bumped into this one and it's really annoying. Our environment's 80% Jabber
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide