Has anyone been able to figure out a way to disable the greetings on a UM enable mailbox? I really just want the beep, not the "You have reached the Voicemail box of "Stephen Hawking", after the tone leave a message...". I
want just the tone and to leave a message.
I have tried just having a silent personal greeting, but I still get the spiel of "After the tone leave a message..."
Thoughts or ideas anyone?
Korbyn
Melissa
Our shop is a current Exchange 2010 shop, going to 2013 next month. In our 2010 config, we have our IP Gateway configured to point to a single 2010 UM server for voice mail that then goes to our mailbox servers depending on where your mailbox is located at.
When we go to 2013, we will have multiple 2013 servers all running UM cause of the new design.
Our IP gateway (Avaya Session Manager) cannot round robin between different IPs, so I need to figure out a way to load balance / round robin UM traffic so I don't get until a configuration where the gateway is pointed at a single 2013 server (single point of failure), plus also causing increased CPU / memory utilization on that single server.
I know UM traffic isn't load balanced in the general sense like we do for MAPI / ActiveSync / OWA traffic, but what are my options for making sure UM traffic is evenly distributed across all 2013 servers.
Gateway send 5 digital to exchange UM, UM say greeting everytime and can't leave voice mail to the UM mailbox.
Any hits.
Thanks.
Hi, I'm currently investigating a problem I have in my exchange 2013 server.
We migrated from 2010 to 2013, and now I'm decommissioning 2010 mailbox servers.
I then dismounted my old database, and now I've this event prompting, seems now exchange is unable to deliver voicemail notifications.
What's turning me crazy, it's the server trying to open mailbox "Microsoft system attendant". now I'm scared about removing this DB, containing this "mailbox" that i can't find anywhere (just with ASDI Edit in the DC) so I can't migrate it or nothing.
(I'm aware that this service is not used anymore, that's why I don't understand this issue).
this is the EVENT:
The Microsoft Exchange Unified Messaging service on the Mailbox server encountered an error while trying to process the message with header file "C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\voicemail\092540a2-50b1-4b91-b408-c3595a677e25.txt".Error details: "Microsoft.Exchange.UM.UMCore.MailboxUnavailableException: "MessageType:CDR Database:CN=OLDDATABASE,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=COMPANYNAME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=COMPANY,DC=com Exception:Cannot open mailbox /o=Companyname/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OLDMAILBOXSERVER/cn=Microsoft System Attendant.." ---> Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException: Cannot open mailbox /o=CompnayName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=OLDMAILBOXSERVER/cn=Microsoft System Attendant. ---> Microsoft.Mapi.MapiExceptionLogonFailed: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231)Hi,
I would like to change the default location of an Exchange 2010 where voicemails are temporally stored. C:\Program Files\Microsoft\Exchange Server\V14\UnifiedMessaging\voicemail to a different location. is there a powershell command to change list location? if not is there a method to do this?
Thanks
Scott
After enabling Lync User Unified Messaging (environment: exchange 2013 & Lync 2013 server), the user recieves default voice mail which starts with: "PLEASE LEAVE A MESSAGE FOR ---and pronunciation his name and SURNAME".
Is there a way to change this greeting centrally on Lync or Exchange? Or the only way is that this can be done on user's machine?
bostjanc
This is an integration of Exchange 365 with Skype for Business. We have to use some complicated normalization rules because we still have PBXs connected via tie-line. The PBX system uses a set of numbers prepended to the called number the call to the appropriate PBX to be handed off to the carrier. In the example below 7711321 is prepended to the called number (Mobile) so that the PBX can route the call to another PBX via tie-line. This is done behind the scene and the users should not have to see this in their contacts list. When configuring Skype the "UseNormalizationRules" option is set to false, however, the contacts phone number are still showing up as normalized. After setting the UseNormalizationRules to false we did an Update-CsAddressBook and gave it ample time to replicate (over night). Is there a way to not normalize the numbers in the address book?
--------------------------------------
Identity : Global
RunTimeOfDay : 1:30 AM
KeepDuration : 30
SynchronizePollingInterval : 00:05:00
MaxDeltaFileSizePercentage : 20
UseNormalizationRules : False
IgnoreGenericRules : False
EnableFileGeneration : True
MaxFileShareThreadCount : 300
EnableSearchByDialPad : True
EnablePhotoSearch : True
PhotoCacheRefreshInterval : 1.00:00:00
We have a situation where we have some SfB EV users and some users that are non Skype using Exchange Online for UM.
When I set this up, can they share a dial plan? If so, what should the URI type be to allow them both access to dial in and check messages?
Thanks,
Chad
Hi folks,
I'm in a Exchange 2013 environment. When I create a new user and enable UM, the Voice Mail tab gives this error:
-----------
500-----------
For some other users, this tab is visible without errors. I already spent a business day searching for this error, but I found something only for O365 (license issue). This is not applicable in my on-premises site.
Is there someone that had this issue and is able to show me the way to solve?
Thanks in advance!
Stefano
Our Exchange 2016 UM service, since being installed a few weeks ago, has several times inexplicably stopped answering calls. Calls to the UM number result in a busy tone, and nothing is logged in the event logs. The service was restarted and then all appears to work.
We used Exchange 2010 UM for years and it worked virtually flawlessly, and this specific problem never happened. Within a few weeks 2016 has broken several times. Just about everything about 2016 is impossibly buggy. Is anyone else having this sort of problem with Exchange 2016?
Hi,
We are working on a requirement in which we wanted to connect to individual exchange accounts via OAuth2.
The requirements is as follows:
We have a MailServer system which will send the Voice mails to exchange accounts of the user as well as to our own custom application. We are in the process of identifying which is the best way to connect to exchange server for these voice mails to sync them between the custom application and Exchange server.
I have checked this link (http://blogs.msdn.com/b/exchangedev/archive/2014/03/25/using-oauth2-to-access-calendar-contact-and-mail-api-in-exchange-online-in-office-365.aspx) for the information. But the link says we need a redirect uri to get the authorization code which in turn would be used for requesting an access token. To my understanding this is a Three-Legged process. Is there any two-legged authentication for exchange and Office 365 so that i can connect to all the accounts in an organization without the authorization code?
Thank you
Regards,
Aditya
I'm trying to um-enable mailboxes (kinda hope that's obvious from enable-ummailbox). Most of them work fine. On one mailbox in particular, I'm getting the error above (Extension 2909 is already assigned to another user on dial plan UM-4Digits or on an equivalent dial plan). The problem is that extension is not already assigned, except to the user in question.
I've tried get-aduser -filter { msrtcsip-line -like "*2909" } and get-aduser -filter { officenumber -like "*2909" } and both return only the user account of the user that owns the mailbox that I'm trying to um-enable.
I've also tried looking through the mailboxes for the extension in question with Get-Mailbox | ForEach-Object { $_ | Where-Object { $_.extensions -like "2909" } } and get-mailbox | ForEach-Object { $_ | Where-Object { $_.emailaddresses -like "*2909*" } } but both return nothing (when run for another extension that is assigned, each returns a single mailbox).
Is there something else that I'm missing?
Hi,
Can anyone help me on how do I connect to Exchange server (need to connect to 2013, 2016 and Office 365 based on the user account) and get the emails of a User in that Exchange server via OAuth2?
I have gone through few articles describing it
Here are the list of them
1. https://azure.microsoft.com/en-us/documentation/articles/active-directory-authentication-scenarios/
2. https://msdn.microsoft.com/en-us/library/office/dn626019(v=exchg.150).aspx
But I'm bit confused, as those articles are implying different procedures to implement for Exchange 2013, 2016 and Office 365.
I needed a "Client Credential Flow" of OAuth2 to connect to them. But I wanted to have a Single server to server application which can talk to 2013, 2016 and Office 365
Thank you
I'm hoping someone can help me out. We are using Exchange 2010 UM with an audio codes gateway from our Nortel CS1000. When a caller dials into the Auto Attendant they can press 3 to be Transferred my EXTN. The call is transferred and it rings 3 times, if I don't answer the caller hears "Sorry I couldn't transfer your call" and then they are back in the Auto Attendant menu options again.
I want the caller to end up in my voice mail if I don't answer. This isn't an issue for only my extn/voice mail. It is the same for all users.
If you dial the speech enabled AA and say my name or any other users name the call is transferred and does the same as explained above.
I'm not sure if this is an audio codes issue or an Exchange issue. The phones on the PBX are all programmed to go to voice mail after 4 rings.
I appreciate all the help I can get,
Lynn
I have a need to place an AA in a branch office. We have Lync 2013 and Ex2013. On the Lync side, we have a survivable branch appliance. On the exchange side, we have 2 mailbox/cas servers in our core datacenter.
I want to place a mailbox/cas in the branch to provide local AA services.
I've stood up the branch mailbox/CAS, created a SIP URI dialplan, integrated it with Lync, and associated ONLY the branch mailbox/CAS server with the branch dialplan. Finally, I created an AA associated with the branch dialplan. I called the AA, and it picked up. So, I thought, "mission accomplished"....until I looked at the SIP traffic.
Even though my branch dialplan was only authorized to the branch mailbox/CAS server, the AA audio is played from one of our core maibox/CAS servers. The SIP trace shows the call hitting the branch mailbox/CAS and being redirected to the core servers.
Can anyone help me understand why this is and how I can force this AA to only be answered on this branch server?
I have an Exchange 2013 deployment with mailbox servers in regional datacenters. These datacenters are very far apart. I have an issue now where calls destined for our Auto Attendant B in datacenter B are being routed to a mailbox server in datacenter A, which is around 300,000 miles away from datacenter B. My network is excellent. It is 100% fiber, however, the almost unbelievable distance between my datacenters introduces around 3.2 seconds (roundtrip) of latency in the audio for my Auto Attendant B calls. Therefore, it is absolutely necessary that Auto Attendant calls to datacenter A be routed to my mailbox servers in datacenter A and Auto Attendant calls to datacenter B be routed to my mailbox server in datacenter B.
I have 2 SIP URI dialplans, Dialplan A and Dialplan B. To keep administrative effort minimal, Dialplan A is authorized only on CAS and Mailbox Server A which is in datacenter A. Dialplan B is authorized only on CAS and Mailbox Server B which is in datacenter B. Auto Attendant A is provisioned under dialplan A. Auto Attendant B is provisioned under dialplan B.
I have SIP gateways in each datacenter. They are conveniently named SBC-A and SBC-B. SBC-A is in datacenter A and SBC-B is in datacenter B. SBC-A routes all inbound Auto Attendant calls to the UM Call Router Service running on CAS and Mailbox Server A. SBC-B routes all inbound Auto Attendant calls to the UM Call Router Service running on CAS and Mailbox Server B.
I've performed a SIP trace on the calls in question. I see the call come in through SBC-B and route to CAS and Mailbox Server B. I then see a 302/Moved Temporarily redirecting the call to CAS and Mailbox Server A. Then, the RTP stream is established with the mailbox role on CAS and Mailbox Server A. Then, the freakishly long distance between CAS and Mailbox Server A and SBC-B causes the audio experience to be unbearably laggy.
My question to this forum is, why would calls to Auto Attendant B, coming into datacenter B through SBC-B, be redirected to CAS and Mailbox Server A? How do I force these calls to remain in their respective datacenters and not be redirected to the other datacenter?
Hi there,
We are running Exchange 2013\Skype For Business 2015 and for the most part, everything works as intended.
However, I was recently notified that while dialing a user's five-digit extension from the UM AA works, if you attempt to search for a user...either dialing by name or via speech, the user is located as expected and the transfer is initiated.
Whereas dialing the extension directly would then connect to the user and ring their desk phone, when utilizing the directory lookup, the call seems to transfer successfully, but what it actually does is just go back to the auto attendant.
I was able to resolve this by changing the telephone field in AD for my own account to simply be my five digit extension, but on the whole this isn't practical, as we have a lot of other systems that populate their data via AD, some of which are shared externally, and thus we need the full e 164 path... 123-456-7890;ext=12345. I've verified that our normalization rules work, and in fact we actually extract just the extension from that string and pass that within the dial plan. Dialing the extension alone works, calling a number in that format within Skype works...but no matter what I've tried, when the auto attendant attempts to transfer the call it just goes into an endless loop of autoattendant.
Any idea what I could look at? Additionally, since we know that if UM sees only the five digit extension in the telephone AD attribute, is there some way to configure UM to look at another attribute...perhaps a less visible attribute that we could"hide" the extension in?
Hi All,
after excute this command
Enable-UMMailbox -Extensions 100 -SIPResourceIdentifier "testuser1@domain.com" -Identity "domain\TestUser1" -UMMailboxPolicy "UMMailboxPolicy"
error appeared and it seems no one has error before "
Unified Messaging can't validate or generate a UM PIN for mailbox 'Test@noorsat.com' : An error occurred while accessing the
user's mailbox. Details: The request failed with HTTP status 405: Method Not Allowed"
please advice?