bostjanc
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
Hi Everyone,
I am pulling my hair out over the UMCR on my Exchange 2013.
I have Lync working correctly, everything working as expected, and all aspects of Exchange are working, except for the Call Router. Whenever I restart the CallRouter I receive 2 warnings in the app eventlog with id 1621 stating that the Client Access server isn't currently enabled, so the UMCR won't listen on any TCP/UDP ports. There are no other error messages, and the services start correctly.
I am able to telnet to both 5060 and 5061 on localhost (it is running in Dual mode), but nothing is listening on the external address.
I have rebuilt the UM Dial Plans multiple times, and disabled the firewall on the host.
The full event log message is:
Log Name: Application
Source: MSExchange Unified Messaging
Date: 30/05/2013 12:08:49 PM
Event ID: 1621
Task Category: UMCallRouter
Level: Warning
Keywords: Classic
User: N/A
Computer: MITSG-EX-01.mitsg.local
Description:
The Client Access server isn't currently enabled and the Microsoft Exchange Unified Messaging call router can't listen on any TCP/UDP ports. Any existing connections will be disconnected.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Unified Messaging" />
<EventID Qualifiers="32772">1621</EventID>
<Level>3</Level>
<Task>8</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-05-30T02:08:49.000000000Z" />
<EventRecordID>39704</EventRecordID>
<Channel>Application</Channel>
<Computer>EXCHANGESERVER.testingdomain.local</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
any help saving my hair would be greatly appreciated!
Hello,
in specifics cases we would like to be able to play a sound by the Exchange UM but not allow the caller to let a message. It would just be an information sound.
We could use the Auto Attendant but, the user has then to wait for the timeout (which is long and apparantly not editable).
Any suggestion would be appreciated.
Hi,
I have an issue somewhere within Exchange relating to Unified Messaging. If someone leaves me a voicemail i receive it into my outlook no problem and can listen to it there. However if i dial my voicemail box from Lync directly it tells me i have no messages. I'm really confused as to where the issue can lie on this one as i know i am getting voicemails however am unable to retrieve them if i choose to do it via lync.
Any suggestions or advice would be greatly appreciated.
Many thanks,
D.
On 11/3 my exchange 2013 cu7 server generated event id 1657:
Log Name: Application
Source: MSExchange Unified Messaging
Date: 11/9/2015 3:07:35 PM
Event ID: 1657
Task Category: UMCore
Level: Warning
Keywords: Classic
User: N/A
Computer: servername
Description:
DTMF map update failed for recipient "<guid>". Tenant: "Enterprise", Run Id: "500a6ef7-ba88-46b1-8123-a1fda2313553", Error: Unable to read recipient.
This same event has occurred everyday since, at 3:07pm. The GUID is different each day. We are not using Unified Messaging, though the service is started on the mail server.
What is going on? Thx
Hi everyone,
We're happy to announce that TechNet forums for Exchange Server 2016 are now available! You can add them to your forum list by clicking on View all under the blue Ask a question button on the left side of the page. We have forums for:
If you have an Exchange 2016 question, please post it to the Exchange Server 2016 forum that fits best. If you have any questions about the new forums, or if you're not sure where to post your question, head on over to the Exchange Server 2016 - General Discussion forum and we'll get you sorted.
EXISTING EXCHANGE 2016 POSTS - We're moving all Exchange 2016 questions and discussions posted to the Exchange 2013 forums over to the Exchange 2016 forums. If you can't find a post you're looking for, it's probably been moved to its new home over in the Exchange 2016 forums.
Thanks for your patience and understanding as we rev up the new forums!
David.
Senior Technical Writer - Exchange. This posting is provided "AS IS" with no warranties, and confers no rights.
I created a Transport Rule to standardize the signatures of the users. The signature is attached in the outgoing email successfully. However, the color, style of fonts are not changed according to the html code, either the <img> tag to the logo on the website.
The server is exchange 2010, not 2013. Many thanks!
We have a 2010 environment with one UM server. We are planning to upgrade the 2010 environment to 2013 and including the UM role of course. Of course, this runs fine, after installing the Exchange 2013 this runs fine in co-existence with the 2010.
But what about UM. Can we install an UM 2013 server in co-existence with 2010 and how do we manage the cutover, or phase out of 2010 UM?
I know this document: https://technet.microsoft.com/library/dn169226%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396
But it does not explain whether co-existence is supported, when the switch over is and whether the UM service will still be available. It says you need move the UM mailbox to 2013 but later configure the dialplans, hunt groups and gateways and so on. But will UM traffic go via the 2010 or proxied to the 2013 Um server?
This problem has me flummoxed.
Our infrastructure is larger than this, but for the purposes of resolving the issue, we have two sites with three Exchange 2013 MB/UM/CAS servers each (two DAGs of two active members in each site, with the standby third in the remote site). All Exchange 2013 servers are on CU8. Both sites use CUCM and Lync (I'm pretty sure Lync isn't part of the problem, but it is part of the environment). We have had Site A's CUCM-Ex2013 UM integration running for more than a year, but are just now getting it running in Site B.
We also still have Exchange 2010 installed. Getting CUCM-Ex2013 running is part of the prerequisite for migrating off Exchange 2010. CUCM-Ex2010 integration works in both sites.
For Ex2013, CUCM is configured with one SIP trunk for call routing, referenced by IP to port 5060 of each of Site B's active Ex2013 servers-- Servers B1 and B2-- and two SIP trunks to each of Server B1 and B2 for UM workers, referenced by FQDN to ports 5062-5068. SIP route patterns have also been configured for Servers B1 and B2, to handle SIP redirects from the Exchange Call Router.
Exchange UM is configured with several dial plans, one of which is for CUCM. A pilot number-- 2533-- is configured in the dial plan. For testing, I created a second pilot number-- 2532-- in the same dial plan.
The CUCM route pattern for 2533 currently points at the Exchange 2010 UM server, and that system is fully functional. 2532 points at the Exchange 2013 call routing trunk.
With Exchange logging set to high for UMCore, UMWorkerProcess, and UMCallRouter, I see the following events when calling 2532:
Event ID: 1650
The Microsoft Exchange Unified Messaging Call Router received a call with the following parameters:
Calling Party: "sip:+[calling number]@[CUCM IP]",
Called Party: "sip:2532@[Server B2 IP]",
Diversion Information: "",
Referred-By Header: "",
Call ID "ad3cf500-65511a3b-e8b-1141050a@[CUCM IP]",
Remote Peer "[CUCM IP]".
Event ID: 1622
A call received with the following parameters:
Calling party: "sip:+[calling number]@[CUCM IP]",
Called party: "sip:2532@[Server B2 IP]",
Diversion information: "",
Referred-By Header: "",
Call ID "ad3cf500-65511a3b-e8b-1141050a@[CUCM IP]"
was succesfully routed to "sip:2532@[Server A2 FQDN]:5062;transport=Tcp".
As you can see in the second event, instead of routing the call to a server in Site B, it is instead being routed to a server in Site A. Both Exchange call routers do this, and they also do it when I reconfigure CUCM to send the existing 2533 DN to Exchange 2013. When 2532 is directed at Exchange 2010, calling works.
Finally, when I point 2532 directly at one of the Exchange 2013 worker trunks, calling works: Exchange 2013 UM on that server answers the call and plays the welcome message.
So something screwy is going on with the call routing in Exchange 2013, and I am at a loss as to why.
A few months ago we "tested" Exchange Online and determined it was not suitable for our company's requirements. I only tested with a few accounts - my own one of them. Currently, we're running Lync 2013 and Exchange 2013 on-premises without issue except that I, and only I, cannot access my voicemail. I had migrated my mailbox back to on-premises from EO and everything else Exchange-related works for me. Icanaccess my VM via the subscriber access line but if I try to "Call Voice Mail" from either my Lync LPE (Polycom CX600) or client, it says I'm "unavailable or may be offline" on the client or "Call unsuccessful. Voice Mail is unavailable right now. Please try later." on the LPE. When I look at the Lync server logs, it's indicating the following:
Attempts to route to servers in an Exchange UM Dialplan failed
No server in the dialplan [Hosted__exap.um.outlook.com__company.onmicrosoft.com] accepted the call with id [ee002254d9ab4a99c752d940a77be205].
Cause: Dialplan is not configured properly.
Resolution:
Check the configuration of the dialplan on Exchange UM Servers.
Which is telling us it's trying to call out to EO for my UM. But I migrated my mailbox to on-premises? If I look at my account in Exchange, it shows my mailbox on-prem and UM enabled with our on-prem UM mailbox policy and dial plan. I've tried disabling UM and re-enabling but it doesn't change anything. My EUM address is correct. I looked at my AD attributes and found nothing out of the ordinary. Reviewing the Lync client logs after attempting a call to UM results in an error like below:
<reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting"><error toUri="sip:j.doe@company.com;opaque=app:voicemail" callId="93a481bc5b7c45868057fad842297441" fromTag="5dbd6e36cd" toTag="5C3A9BA30F5AC52DAE32D0D0A2674C15" contentType="multipart/alternative;boundary="----=_NextPart_000_0035_01CF2726.7DF989E0";call-type=audiovideo" responseCode="480" requestType="INVITE"><diagHeader>52086;reason="The conversation could not be established as the remote party is not available";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"</diagHeader><progressReports><progressReport><diagHeader>13007;reason="Request was proxied to an application.";source="lyncpoolfqdn.company.COM";targetApp="voicemail";appName="InboundRouting"</diagHeader></progressReport><progressReport><diagHeader>15008;reason="Routing to UM for Subscriber Access";source="lyncpoolfqdn.company.COM";dialplan="Hosted__exap.um.outlook.com__company.onmicrosoft.com";umserver="exap.um.outlook.com";appName="ExumRouting"</diagHeader></progressReport><progressReport><diagHeader>15023;reason="Re-directing request to the destination in 303";source="BL20C00EDG02.LYNC0C001.LOCAL";Destination="sip:j.doe@uminternal.um.prod.outlook.com:5061;ms-organization=company.onmicrosoft.com;transport=Tls;ms-fe=pod51034.um.prod.outlook.com";appName="ExumRouting"</diagHeader></progressReport><progressReport><diagHeader>15621;reason="The specified mailbox is not enabled for Unified Messaging. User: j.doe@company.com. PrimarySmtpAddress: </progressReport></progressReports></error></reportError">j.doe@company.com.";source="lyncpoolfqdn.company.COM";dialplan="Hosted__exap.um.outlook.com__company.onmicrosoft.com";umserver="exap.um.outlook.com";responsecode="403";msexchsource="BY2PR01CA001.prod.exchangelabs.com";appName="ExumRouting"</diagHeader></progressReport></progressReports></error></reportError>
Any ideas? Thanks!
When a missed call or voicemail email is sent to the recipient's mailbox, it includes a footer with Caller ID information.
For example:
You received a voice mail from XXX at XXXX.
Caller-Id: | XXXX |
Job Title: | XXXX |
Company: | XXXX |
Work: | 12345 |
Mobile: | 54321 |
Email: | XXXXX |
How can we go about filtering out the mobile field in the email template, and is it possible to do this on a user-by-user (or AD group by AD group) basis?
I know removing the mobile number from the user's telephone properties in AD will make it disappear, but we want to maintain it in AD, just not include it in UM emails.
I had Lync 2013 on premises with voicemail hosted on Office 365 Exchange online, all configured and working for a POC. However I have since moved these POC users back to on-premises Exchange. Now here lies the problem.
for these users, the “HostedVoiceMail” attribute changes from null back to "$True". If I run the “Set-csuser –identity Domain\Username –HostedVoiceMail $Null” command again it will set it, but that will disappear as soon as Azure AD Connect sync runs again.
I found this article but its the old Dir Sync tool which I cant seem to find the flow attributes in the new Azure AD Connect tool.
DURP
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?
Hi All,
i am doing an integration between SfB & Exchange 2013 but i am facing an issue and need your urgent support:
while the unified messaging is exist in the Exchange Admin center, UM Call Router settings is not exist
also there is an error that the unified messaging role is Not Added !!
please Experts direct me of how to add the UM Role in a running Exchange Server 2013
thanks,
Hi all,
I have an Exchange 2013 server (all roles) along with Skype 2015 and a Asterisk trunk. I have a number for Auto Attendant that is no longer working, it has been for months since first setup. There were no changes (im solo admin) to any system but now when you call the Auto Attendant number (A SIP number hosted by our SIP Provider), it appears to connect as i see it on the Asterisk channels, but I just get an engaged tone and it hangs up. Voicemail acess has also stopped working. But the other number for Skype conferencing is wokring fine. Im pretty sure there is an issue with Exchange UM, but I cant see anything wrong at all, hardly any event logs.
I have rebooted all of the servers, checked partner application health, run traces with OCS Tracer, and many more checks as per Google results.
The only alerts of relevance are from Skype:
The Mediation Server service has received a call that does not support comfort noise. This event is throttled after 5 calls from a single Trunk peer.
The Mediation Server service has received a call that does not support comfort noise from the Trunk, <AsteriskIP>;trunk=<AsteriskIP>
Cause: The Trunk does not support comfort noise.
Resolution:
Please ensure the comfort noise option on the Trunk has been enabled.
But i think that may be a red herring.
Any pointers much appreciated. Can I reinstall any components perhaps, without impacting users?
Thanks, Carl.
Hi,
I'm trying to run a powershell cmdlet that will give me a list of all our UM-enabled accounts that don't have the Personal Operator property populated.
I can run the following to show me which accounts have a particular Operator extension assigned:
Get-UmMailbox | ForEach { If($_.OperatorNumber -Eq 3000){$_.Name}}Sometimes this field gets neglected during account creation and we're trying to find the accounts that don't have it set. What would be the command for that? Also, is there a search filter within EMC that can do the same?
Thanks.
Rory
Rory Schmitz
Hello,
Thanks in advance for your help.
We are about to roll out Skype for Business in my company with UM.
(These below are my server Exchange 2013 specs)
Windows Server 2012 R2 x64 with Exchange 2013 CU8
Virtualized on VMWare 5.5, machine version 8, 8 CPU cores and 36GB memory.
Yesterday we enabled UM and the CPU went crazy hitting constantly a 100%... and making VMWare to start moving the server between hosts for balancing. Therefore the Exchange server crashed and we have to go into Mimecast continuity.
Taking it from this point I wonder...
What are the requirements for UM?
Does it need extra CPUs? Extra memory?
Could this be related with a certificate issue we have between one of our skype server and Exchange (TLS Connection)?
I would appreciate if I can pick up someone's brain on this.
Regards