03-27-2017 07:35 AM
03-27-2017 07:49 AM - edited 03-27-2017 01:25 PM
Seems like you would need to have an email account with UM, Exchange 3 plan likely, and have a generic Voicemail AA account created. It is how we integrate with UM for 365 now with an Avaya On Prem PBX. After hours, it routes the call to the VM for call coverage/voicemail. Then users can listen the next morning to the voicemail in that other email account which you have assigned delegation rights to gain access to. Just like any user. I have 2 email/E3 accounts dedicated to handle to night AA's, which gives user an option to press 0, or stay on the line to leave a general message in the voicemail box. Or, after the greeting, if there are no options, I just route it to the voicemail box upon picking up, and play the actual voicemail box greeting and say leave a message, no AA greeting/file involved. Not sure how to do this with Skype AA though. Doing testing now.
03-27-2017 07:51 AM
I don't want to have to license department's voicemail in the cloud with licenses I just need something that just works seemless with Skype Online. We are 100% Skype for Buisness Online but cannot move our auto attendant or queueing till we have general voicemail access.
03-27-2017 08:02 AM
I gotcha. We are entirely Exchange Office 365 E3 customers. Just doing testing with cloud PBX due to other issues with an OnPremise.
Just provding and option/solution to the issue. It is the only way we can make UM/Exchange work so off hours there is a voicemail box, and in order for that, you need a full E3 license so you can assign UM/Voicemail functions to the mailbox.
Avaya and other phone vendors don't even offer this function/feature in their Avaya S8300/G450 VoIP PBX. Auto attendant is built into one of the modules/cards in the PBX, but it can't do anything but then route the call, do options/coverage paths and of course, route it to an extension, which in our case is a generic email account with UM/Voicemail and extension assigned to it.
Then assign other user as delegates in Exchange to that email account, shows up in the Outlook listen/route/forward or delete voicemail as needed that way.
Where do you think this voicemail is going to land once it hits the AA and they have an option to do something like leave a message? The mechanism to provide voice mail services anyway? Just curious, because something/somewhere has to be able to take the voicemail from the caller, convert and store it someplace, like a send to email, or local voicemail server/service. Which is Exchange Online in the Cloud pbx they offer.
Not sure how you can get around it. I know, it is like $20 per AA to do this, but not sure what the other options are. Been out of other PBX/UM/Auto attendant area for years though, maybe I'm just not familiar with other PBX/Cloud offerings and how they would handle a VM from AA.
03-27-2017 08:09 AM
I just really like to avoid having a Exchange Mailbox for this - I rather it be perhaps a Shared Mailbox - or a distro group you cannot forward the Auto Attendant to Voicemail after the person doesn't answer anyways even doing queuing this cannot work for us till we can do Voicemail after hours and during holiday's and when they are away from their desk.
03-27-2017 09:02 AM
03-27-2017 09:18 AM
Why can't we have a general mailbox that just emails users in a group that there's a voicemail and attaches the WAV that would just be too simple.
03-27-2017 09:49 AM - edited 03-27-2017 01:26 PM
Correction about the voicemail rule working. As mentioned, the rules don't work but manually for VM in Exchange.
Again, I'm not familiar with other auto attendants but Avaya's and NEC PBX systems, and Cisco CM/UM as well. Someone shed some light what the thinking is here and what system is also going to act like the VM system? The Auto Attendant function in Skype for Business PBX functionality will have voicemail?
Want to know more and what other systems offer to accomplish this as well.
03-27-2017 09:57 AM
Gotcha. I see what you are saying, some players like Ringcentral are putting a voicemail function built into the product to accomplish this feature for people that might not have a full onpremise, or Unified message/VM system.
Interesting feature then. Thanks for that.
I'm evaluating replacing our onpremise, but auto attendant is required, so I have methods to kind of work around that now with Microsoft's AA and lack of this feature you say Ringcentral has.
Call queuing as well, along with 4 digit dialing, there are a whole lot of things that are just missing from Skype for Business PBX in the cloud that the on premise has I know.
Sounds like ti Need to keep looking at solutions like 8x8 or others until MS can get this all sorted and features. Sounds like a 2yr timeframe at this rate from today?
03-27-2017 12:17 PM
Keith, one thing that I've tried but have been unable to do is set up a mail flow rule in Exchange to get the voicemail out of a generic E3 account into an actual user's email account. It seems that the process of receiving the voicemail notifcation email is an internal process that bypasses the way Exchange normally captures and forwards emails based on mail flow rules.
I can delegate out the generic mailbox to users but they still have to remember to go look for it since it isn't in their primary inbox.
In your post it sounds like you were able to forward these out. Where you able to confirm this works?
This seems like a glaring feature that is missing from AA.
03-27-2017 01:19 PM
You know, I think you are right. If I recall, if you setup a rule for something like, Subject: Voice Mail, which the system shows, the only way the rule worked was when it was manually run. It didn't seem to be a server rule that understood the voicemail function and would never route it/forward it automatically.
We just delegate access to the receptionist, she see it in her Outlook on the left pane, and she can view/forward/listen etc do what is needed. Last resort, login to the OWA account for the general voicemail user we created that the night calls get routed to after the AA.
I see where this is definitely a useful and needed function, and would prevent wasting an E3 license for every auto attendant, especially if you have like 5-10 of them that needed to route to a VM for different areas. End up costing $1000/yr+ just to handle some voicemails after the auto attendant did it's thing after hours.
03-28-2017 06:56 PM
I watched "Skype Academy: Auto Attendant" (Link to YouTube Video) published March 28, 2017 on YouTube and it contradicts what I've been seeing with regards to AA and VM.
Verbatim from a slide in the video prezo:
"Auto Attendant - provides automated interactive system for incoming calls...Can have an Operator or Voicemail as backup"
The speaker then indicates, in a subsequent slide, that after business hours, you can give callers an option to leave a voice mail from the Auto Attendant.
On that same slide, he also says that the "Operator can be Cloud PBX enabled user, Call Queue, Auto Attendant, or Voicemail"
Is it possible this is a planned feature?
03-29-2017 12:14 AM
I understood that if you select Transfert to "Person in your Company" and select a user if this user doesn't answer will automatically go to voice mail if this user was enable for VM
03-29-2017 06:38 AM - edited 03-29-2017 06:42 AM
Yes, believe this was covered earlier, or in another thread. Basically need to have a user with UM/Voicemail enabled in your O365 tenant, then the AA routes to a "person". So it will costs you a full E3 license to enable UM/Voicemail.
What happens to the calls after the greeting?
If you select Redirect Call, the options are Route to a Person In your company, Call Queue or AA.
If you select the person, of course, they need to be UM/Voice enabled and have the mailbox setup. We do this currently with another PBX that integrates with Exchange UM features in the cloud.
03-29-2017 07:14 AM
What I am needing is this.
If a user calls into a queue and its the IT Helpdesk and nobody is available I need it to go to a general our IT Group.
If someone calls the HR department and nobody answers it needs to go to the HR general mailbox
If someone calls into our company and doesn't answer we would like our CEOs assistant and our front desk person get the voicemail.
04-12-2017 03:40 PM
04-13-2017 06:59 AM
I don't see any different solution when you need it to route to voicemail box when not answered/or after pressing a button.
You still need a mailbox enabled with voicemail features to take a voicemail. That is an Exchange UM function.
Skype for Business in General, even a hosted 3rd party solution I was looking at didn't even seem to have that function either. They utilize Exchange UM/AA features. Maybe there are some other companies that can do this, Mitel etc..I know can. But Skype doesn't seem to have that in general across any platform.
They would have to implement an auto attendent function prior/outside of any other AA/Exchange UM function, that can take/implement a custom greeting you store, and then keep/store a voicemail in a format that is accessible or routable to somebody via SMTP.
This more of a traditional and newer cloud PBX feature that I've only found a few providers can do. MS Skype doesn't seem to be one of them unless a custom third party has implemented a work around for it, and none I've talked to have.
Good luck. I'm looking at hosted 3rd party Skype, not MS Cloud. Or somebody like Mitel cloud who can do these things. And some things are still not able to be met, like 4 digit dialing, except Mitel.
04-13-2017 07:38 AM
I agree that for now it's needed but MS needs to look into adding support for Shared O365 Email boxes being enabled to recieve voicemail. This would allow teams to use the same shared mailbox as a central location for email and voicemail. It also removes the requirement for a e5 or cloud PBX license plus the additional cost of Cloud PTSN for every shared Voicemail. The cost for a general voicemail box makes SfB Cloud uncompetative with most other cloud offerings.
Most companies only have a requirement for 1 or 2 group or shared VM's so utilizing the same concept as shared mailboxes in O365 seems like a no brainer.
07-31-2017 05:22 PM
Any update on this?
It's a lot of bucks for features that should have been availabled from day 1 when AA was GA!
I didn't find anything on O365 roadmap either. At least, if we could have a confirmation that's it's coming...
09-18-2017 06:59 PM - edited 09-18-2017 07:01 PM
09-18-2017 06:59 PM - edited 09-18-2017 07:01 PM
Is there a status on this feature?
BTW if you are interested in this feature, please vote this up!
Someone had the same idea, why couldn't you use a Shared Mailbox for this or something that can be a shared resource??
The extremely frustrating part is that you have to sell people on using an E3 and a PSTN plan to just capture VM's!
09-18-2017 07:05 PM
09-18-2017 07:05 PM
Agree'd, telling a user they need to spend money to add a voicemail box is rediculous.
I would love to spend 15 minutes with the dev team to really sort out the feature the small to mid sized businesses need.
11-10-2017 06:58 AM
Any update on this for planning? We can't switch over till this feature is there.
04-10-2018 11:28 AM
Any update on this? I was trying a workaround by having a seperate user & mailbox for the call queue messages, but I am unable to forward the voicemails to a group - Exchange rules and Mailbox rules do not work on the voicemails.
05-14-2019 12:16 AM
This is hot off the press!
Service update notification
The service updates for Auto Attendant and Call Queues were completed successfully this week. The updates introduce new capabilities, namely:
1. Centralized holiday tables that can be reused across apps. You will find it under Org wide settings
2. You can assign Direct Routing numbers to Auto Attendant and Call Queues (as of today DR with AA/CQ support Teams users only)
3. You can assign a hybrid number to AA/CQ (currently in preview)
4. You can assign Multiple numbers to an auto attendant or call queue
5. Round Robin routing option is introduced in call queues
The updates prepare the services as well for the upcoming features:
6. Transfer out to PSTN from auto attendant and call queues
7. Extension dialing from auto attendant
8. Voicemail shared mailbox for auto attendant and call queues
05-28-2019 02:44 PM
2 years later, and no progress?? We also need a queue voice mail option. When the caller reaches a "team" like customer service and they are all on a call, it would be logic that a queue automatically gets the call via a voicemail so customers don't have to wait 15 minutes and get disconnected. That is a bad user experience, I can't believe this has not been implemented.
05-29-2019 07:51 AM
They have made progress...but with the stopping of UM/Exchange for Cloud Voicemail, switching to Teams...glad I went with CallTower to host my Skype for Business. They are going to upgrade to 2019, so we will be good for years more.
Only thing is to find an alternative to auto attendant and delivering voicemail seemlessly into an O365 Exchange mailbox like it does now since SBC controllers won't be support and the UM/Exchange feature no longer being offered. Vendor is working on some solutions to work around and provide that feature and functions I guess.
Won't be moving to MS Teams/Skype anytime soon though. Some of these basic functions like you all have mentioned, like a call queue for main numbers or other features we use that aren't support still are kind of a let down.
MS has too many things going on and can't focus on core features/functions with all of their products they have. Piece meal instead of complete features and focus on product rollout IMO.