locked
Voicemail Forwarding Scope RRS feed

  • Question

  • Hi Folks.  We've recently migrated from Exchange 2010 SP3 to Exchange 2013 SP1 CU7.

    Previously, our users report that they could use the Voice Access feature to forward a message to anyone in the organization by saying "Forward Message to xyz".  After the upgrade, they are limited to users in their personal contacts.

    I suspect this is a scoping issue, but can't find where to define the scope.

    Thoughts?

    Thanks

    Thursday, April 2, 2015 10:41 PM

All replies

  • Call forwarding feature have got some limitations from lync 2013.  i have shared some links, that will help to understand better about call forwarding in Lync and UM as well.

    http://ucken.blogspot.in/2013/01/Lync-Call-Forwarding-SimulRing.html

    https://technet.microsoft.com/en-us/library/dd335138(v=exchg.150).aspx

    Monday, April 6, 2015 11:09 AM
  • Thanks Rajkumar

    This issue is with transfering received voicemail messages, not calls.  I can create a 'Call Answering Rule' in ECP, and search the entire directory without issue.

    In our case, the the mailbox owner uses the 'Voice Access' feature to access their voicemail, and wishes to transfer the message to another recipient that is not in this users' contacts.  After saying "Forward Message To John Smith", the voice prompt very clearly says: 'To which contact would you like to send this message'.

    Conversely, If the user just sais "Forward Message", the voice prompts asks the user to use the touch tone to perform a directory search -- which works, but defeats the purpose of using the voice access.

    This makes no sense.  Users should be able to forward messages to anyone in the organization without needing to have them as contacts.

    Especially when this was working fine in Exchange 2010!

    Thanks.


    Thursday, April 9, 2015 6:44 PM