UM Service won't start

November 7, 2013, 12:54 am

≫ Next: UM 2013 does not answer calls

≪ Previous: 2010 vs 2013 Virtualized Unified Messaging System Requirements?

Hello. I have a new installation, domain and Exchange server, with Windows 2012 server and Exchange 2013 CU2. The server is configured and users can send and receive emails with outlook or web app. The problem is with the "Microsoft Exchange Unified Messaging" service. It is set to Automatic but can't start. The event viewer records the errors below. I don't use unified messaging services at all and haven't configured anything in Exchange EMC for unified messaging (dialing plans or anything other)

Event id 1430:

The Microsoft Exchange Unified Messaging service on the Mailbox server ended the process umservice (PID=10460) due to an internal inconsistency or an unrecoverable situation.

Event id 1038:

The Microsoft Exchange Unified Messaging service wasn't able to start. More information: "Microsoft.Exchange.UM.UMCore.UMServiceBaseException: The Microsoft Exchange Unified Messaging service encountered an error. The UM worker process encountered a fatal error during startup.

at Microsoft.Exchange.UM.UMService.UMService.InternalStart()

at Microsoft.Exchange.UM.UMCore.UMServiceBase.StartService()

at Microsoft.Exchange.UM.UMCore.UMServiceBase.OnStartInternal(String[] args)"

Event id 1001:

The UM worker process (UMWorkerProcess.exe) couldn't start. More information: A file couldn't be converted for playback over the telephone: An error occurred in the Audio Compression Manager: The operation completed successfully.

Thank you for your help.

↧

UM 2013 does not answer calls

November 12, 2012, 7:27 pm

≫ Next: Lync 2013 with Exchange 2013 UM Voicemail delivery delay

≪ Previous: UM Service won't start

I've gone through the setup about a billion times (at least that's what it feels like) - but I've never been able to successfully have Exchange 2013 UM answer any phone calls to either the mailbox service or any configured auto-attendant.

To make sure I wasn't crazy, I have reinstalled Exchange 2010 in a 100% identical configuration, and she answers with absolutely no problems what-so-ever. Users are led to their mailbox, the autoattendent routes calls accordingly, etc.

. . . But moving back into a 2013 environment, in a 100% identical configuration, the server itself never actually answers any of the calls.

Would anybody happen to have any ideas on where I could go to check out the issues here?

↧

Lync 2013 with Exchange 2013 UM Voicemail delivery delay

November 25, 2013, 6:09 am

≫ Next: Auto Attendant / Unified Messaging DOWN On Production please help! Lync 2013

≪ Previous: UM 2013 does not answer calls

We are currently having an issue where it appears that a voicemail is left for the user, but it doesn't get delivered for 20 minutes. This is not constant, but has been creeping up on a regular basis. I have some info below that seems to support this. Anyone have any ideas? I cannot understand why it would be taking 20 minutes for UM to process a voicemail and deliver it to the mailbox.

The pipeline statistics log shows that the voicemail was sent at 3:32:47 PM (We are GMT -6)

SentTime,WorkId,MessageType,TranscriptionLanguage,TranscriptionResultType,TranscriptionErrorType,TranscriptionConfidence,TranscriptionTotalWords,TranscriptionCustomWords,TranscriptionTopNWords,TranscriptionElapsedTime,AudioCodec,AudioCompressionElapsedTime,CallerName,CalleeAlias,OrganizationId
11/21/2013 21:32:47,c8d2ba82-e2cd-4b7e-b530-cee5b6e2a0da,SMTPVoiceMail,en-US,Skipped,AudioQualityPoor,0.1921112,24,2,0,00:01:02.9052573,G711,00:00:00.0090007,,person,

The message tracking log shows the SMTP receive being at 3:56:03 PM.

RunspaceId : ddf7889b-3e53-4b15-a42f-64bca7c8e411
Timestamp : 11/21/2013 3:56:03 PM
ClientIp : 2.2.2.2
ClientHostname : SERVER02
ServerIp : 2.2.2.2
ServerHostname : SERVER02
SourceContext : 08D0B391ED127EBF;2013-11-21T21:56:03.592Z;0
ConnectorId : SERVER02\Default SERVER02
Source : SMTP
EventId : RECEIVE
InternalMessageId : 15998753179082
MessageId : <0e7b3f00-86fb-452d-a252-d19b5d9e5423@SERVER01>
Recipients : {person@domain.com}
RecipientStatus : {}
TotalBytes : 128569
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : Voice Mail (15 seconds)
Sender : MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com
ReturnPath : MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com
Directionality : Undefined
TenantId :
OriginalClientIp : 1.1.1.1
MessageInfo : 0cI:
MessageLatency :
MessageLatencyType : None
EventData : {[FirstForestHop, SERVER02], [ProxiedClientIPAddress, 1.1.1.1],
[ProxiedClientHostname, SERVER01], [ProxyHop1,
SERVER02(3.3.3.3)], [DeliveryPriority, Normal]}

The message tracking log shows that the message was sent to the mailbox at 3:56:04 PM. Note the timestamp on the SourceContext line for ClientSubmitTime. It shows 21:32:47 (3:32:47).

RunspaceId : ddf7889b-3e53-4b15-a42f-64bca7c8e411
Timestamp : 11/21/2013 3:56:04 PM
ClientIp :
ClientHostname : SERVER01
ServerIp :
ServerHostname : SERVER01
SourceContext : 08D0B396BCB6EF39;2013-11-21T21:56:04.361Z;ClientSubmitTime:2013-11-21T21:32:47.582Z
ConnectorId :
Source : STOREDRIVER
EventId : DELIVER
InternalMessageId : 15998753179082
MessageId : <0e7b3f00-86fb-452d-a252-d19b5d9e5423@SERVER01>
Recipients : {person@domain.com}
RecipientStatus : {}
TotalBytes : 129788
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : Voice Mail (15 seconds)
Sender : MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com
ReturnPath : MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@domain.com
Directionality : Undefined
TenantId :
OriginalClientIp : 2.2.2.2
MessageInfo : 2013-11-21T21:56:03.576Z;SRV=SERVER02:TOTAL=0;SRV=SERVER02
:TOTAL=0;SRV=SERVER01:TOTAL=0
MessageLatency : 00:00:01.1690000
MessageLatencyType : EndToEnd
EventData : {[MailboxDatabaseName, MN-EX-DB1], [E2ELatency, 1], [DeliveryPriority, Normal]}

↧

Auto Attendant / Unified Messaging DOWN On Production please help! Lync 2013

November 25, 2013, 11:17 am

≫ Next: DSX-80/160 and Exchange 2013

≪ Previous: Lync 2013 with Exchange 2013 UM Voicemail delivery delay

Our Lync 2013 production environment was acting a bit funky on Friday last week. At one point outbound calls were not working so I restarted our Dialogic DMG 1008 gateway. This fixed the outbound calls but took out our inbound calls. Calls were no longer being answered by our Auto Attendant.

I found this very odd because the Gateway is independent of our domain and the Unified Messaging environment. I believe I've dug myself in a hole trying to fix this.

I have it set up currently so inbound calls work ONLY if they go directly to someone's extension. Like right now its set up to be routed to our guy with extension 28. The original Auto Attendant was on extension 62.

I went through following this: http://blog.schertz.name/2010/11/lync-and-exchange-um-integration/

As I have done in the past and set up a new Dial Plan and Attendant. After which I ran the exchucutil.ps1. I noticed the first time I ran exchucutil it did NOT have either Dial Plan listed at the end next to my pool and gateway. I ran it again and this time it DID have them.

For some reason there is an old pool I created a long time ago showing up in the util, despite being unused and not associated with any UM servers, it also creates a 1:8 gateway instead of a 1:1 gateway for this pool. For my correct pool it creates the 1:1

Next I went ahead and ran the OcsUmUtil on the Lync server. I created my auto attendant object here, gave it the phone number +15005005000;ext=70 (new extension for new Auto Attendant) and added it, it successfully created the AD contact.

Last I changed my Lync Dial plan to route to the new AA at extension 70 instead of the currently working user on 28. It did not work. It acted the same as with my old Auto Attendant. Kept ringing. I keep seeing these errors in Event Viewer on my Lync Server:

An attempt to route to an Exchange UM server failed.

The attempt failed with response code 504: EXCH03.domain.com.
Request Target: [Lync05Plan@EXCH03.domain.com], Call Id: [cded26d3-3d96-4cb3-9439-2631c34e736d].
Failure occurrences: 32, since 11/24/2013 9:57:15 PM.
Cause: An attempt to route to an Exchange UM server failed because the UM server was unable to process the request or did not respond within the allotted time.
Resolution:
Check this server is correctly configured to point to the appropriate Exchange UM server. Also check whether the Exchange UM server is up and whether it in turn is also properly configured.

And:

Attempts to route to servers in an Exchange UM Dialplan failed

No server in the dialplan [Lync05Plan.andomain.auroranorthsoftware.com] accepted the call with id [1c5d57b5b9744718bc93e46c246df75b].
Cause: Dialplan is not configured properly.
Resolution:
Check the configuration of the dialplan on Exchange UM Servers.

While see the following in the Logging Tool/Snooper:

TL_ERROR(TF_CONNECTION) [0]22E8.36F8::11/25/2013-18:20:38.655.0001b39e (SIPStack,SIPAdminLog::WriteConnectionEvent:1207.idx(452))[1880424289] $$begin_record
Severity: error
Text: Failed to complete outbound connection
Peer-IP: xxx.xxx.xxx.xxx:5061
Connection-ID: 0x1BDE01
Transport: TLS
Result-Code: 0x8007274d
Data: fqdn="EXCH03.domain..com";peer-type="InternalServer";winsock-code="10061";winsock-info="The peer actively refused the connection attempt"

and

TL_ERROR(TF_DIAG) [0]22E8.36F8::11/25/2013-18:20:38.655.0001b3c8 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:1207.idx(784))[3669543787] $$begin_record
Severity: error
Text: Message was not sent because the connection was closed
SIP-Start-Line: INVITE sip:05Plan2-AA.05Plan2@EXCH03.domain.com:5061;transport=tls;maddr=EXCH03.domain.com SIP/2.0
SIP-Call-ID: 2d7a0a16-f087-4fe7-8bad-b49253ad62e2
SIP-CSeq: 3844 INVITE
Peer: 75.150.107.65:5061

and

TL_INFO(TF_PROTOCOL) [5]1E80.2E68::11/25/2013-18:20:25.966.00014401 (S4,SipMessage.DataLoggingHelper:1844.idx(774))[1750660461]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_1A15E97>], 192.168.1.168:5068->192.168.1.101:1146
SIP/2.0 480 Temporarily Unavailable
FROM: "Cell Phone VT"<sip:5555555555@gateway01.domain.com:5068;user=phone>;tag=3C513246313536410027993E;vnd.pimg.port=4
TO: <sip:15555555555@192.168.1.168:5068;user=phone>;tag=acc5b84aa;epid=EB28B8B7B9
CSEQ: 2 INVITE
CALL-ID: 01B22B023893000E000000A8@gateway01.domain.com
VIA: SIP/2.0/TCP 192.168.1.101:5068;branch=z9hG4bK9236B40944FADD4616133A3D2A57C40C

↧

DSX-80/160 and Exchange 2013

November 20, 2013, 2:07 pm

≫ Next: Voice Mail Preview in GERMAN?

≪ Previous: Auto Attendant / Unified Messaging DOWN On Production please help! Lync 2013

Hello Forum Members,

email for the users is fine.

We have a customer that is using a DSX-80/160 to send voice mail to users via Exchange.

This worked (works) fine for the Exchange 2007 server - using a username and password on the domain. "voicemail@ourdomain.com"

We are current running in co-exist mode - but the DSX-80/160 cannot pass the send mail test to the new

server -- the port used is 25. We can telnet to the new server (Windows 2k12 with Exch 2013).

We can an error message from the DSX - saying it cannot verify user/password.

Any ideas here?

Thanks

Eric H.

Group Oliver

Network and Server Installs

↧

Voice Mail Preview in GERMAN?

November 30, 2013, 10:48 am

≫ Next: Exchange Server 2010 SP3 Installation with UM Language Pack Error

≪ Previous: DSX-80/160 and Exchange 2013

Hello,

since exchange 2010 I am looking forward to a Voice Mail Preview in GERMAN.

Is Voice Mail Preview in GERMAN supported in CU3?

Best wishes and many thanks in advance

Dirk

↧

Exchange Server 2010 SP3 Installation with UM Language Pack Error

December 4, 2013, 4:09 am

≫ Next: Exhange 2007 second receive connector

≪ Previous: Voice Mail Preview in GERMAN?

Hi All,

Kindly help me in this issue, When I Install Exchange Server 2010 SP3, I faced an error in UM role setup as the below,

and when i searched on it i found solution like "Download the UM language packs and tried to install directly" so i downloaded "UMLanguagePack.en-US" from the below URL:

http://www.microsoft.com/en-eg/download/details.aspx?id=36769

and when i tried to install it, i faced the below error:

also i searched on this error and i found solution in registry as the below:

Try remove registry key for the above error :

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\<Your Version >\UnifiedMessagingRole\LanguagePacks"

and after i did it, i found first error be solved and the second error still the same as the below:

Error:
A Setup failure previously occurred while installing the UnifiedMessaging role. Either run Setup again for just this role, or remove the role using Control Panel.

Is there a solution on this issue please i wanna solve it As soon as possible?

Thanks in advance,

↧

Exhange 2007 second receive connector

December 4, 2013, 7:41 am

≫ Next: Receive and Send fax

≪ Previous: Exchange Server 2010 SP3 Installation with UM Language Pack Error

I have sbs2008 i want to add another second receive connector for new system that i have installed that sends email to outside the office. If i send emails inside the network there is no problem.

my network is 192.168.1.0 when i try to add another receive connector i get error message.

↧

Receive and Send fax

December 3, 2013, 10:46 pm

≫ Next: gammar files not updating

≪ Previous: Exhange 2007 second receive connector

We need to be able to receive fax messages on one single um-enabled Mailbox using Exchange 2013.

Is there a way to configure that without having a fax server solution? If we NEED a fax server, what kind of fax server do we need ?

Regards.

Alaa.

↧

gammar files not updating

December 6, 2013, 10:39 am

≫ Next: UM Service Rejected Calls %

≪ Previous: Receive and Send fax

Hi,

Icreate anauto-attendantwith voice recognitionandfileGammarfilesdoes notupdate.Irestart theservicetheMicrosoftExchangeMailboxAssistantsservice anditstill does not work.ThereafterIinstall thecu2 and Istill have the sameproblem.Thelanguage packhas beeninstalled with the cu2too.It is nowtwo weeks thatI have this problemand Irestart theexchangeserver.Someone hasalreadysaid hewants to issue.

Thanks

↧

UM Service Rejected Calls %

December 9, 2013, 8:53 am

≫ Next: Configuring Rule Groups

≪ Previous: gammar files not updating

Hello,

I receive the following alert from SCOM but I don't know how to troublshoot it,

alert context:

Alert: UM Service Rejected Calls % over the last 1 hour - Red (> 10).

Source: Telephony - Inbound - UM-server-name (Unified Messaging) - ADC

Path: UM-server-name (Unified Messaging) - Microsoft.Exchange.2010.UnifiedMessaging.Telephony.Inbound:UM-server-name (Unified Messaging) ;Telephony - Inbound - UM-server-name (Unified Messaging) Last modified by: System Last modified time: 12/9/2013 6:58:08 PM Alert description: TimeSampled: 2013-12-09T17:50:19.0000000+02:00

ObjectName: MSExchangeUMAvailability

CounterName: % of Inbound Calls Rejected by the UM Service Over the Last Hour

Value: 61

--------------------------

how can I determine these failed rejected calls, and what the word "call" means? voice mail, missed call? knowing that I have lync reporting service installed but I don't know if it can help since the UM is an exchange server.

Thank you

Mohammad, IT NOC Team

↧

Configuring Rule Groups

December 10, 2013, 8:02 am

≫ Next: Multiple Primary EUM Addresses for a user mailbox - Set As Reply

≪ Previous: UM Service Rejected Calls %

Hi, everyone!

I'm trying to configure a Dialing Rule so that when someone attempts to dial extension 505 (1330688xxxx;ext=505) from the Auto Attendant they're transferred to extension 502 instead. The "number mask" field didn't like the format with "ext=505" and when it comes to Exchange, I've had to just say "505" in the past, so that's what I put and I put 502 in the "Dialed Number."

Unfortunately, this seemed to have no affect. I added the Rule to the AA settings.

We're on Exchange 2010 SP3.

Can anyone help me understand what may be going on?

Thanks!

-Eric

↧

Multiple Primary EUM Addresses for a user mailbox - Set As Reply

December 13, 2013, 8:40 am

≫ Next: Exchange 2013 um fax with Lync integrated

≪ Previous: Configuring Rule Groups

My question is for Exchange 2010 SP3 - but am also wondering if this occurs in a 2013 environment as well.

I've enabled a user for UM with a mailbox policy and extension number, now I want to add a secondary address to the mailbox using the Exchange Management Shell (this is to script user creation - I don't want to use the GUI) - and I want this new address to become the primary EUM (Set As Reply). When I add the new address, I use the following:

Set-Mailbox -identity alias -EmailAddresses @{add="EUM:firstname.lastname@domain.com;phone-context=diaplan.domain.com"}

This command works and I get the new address added as a primary BUT the original address is still listed as the primary as well.. so now I have 2 EUM (capitalized) addresses and it's causing issues. If you add through the GUI - you would have to pick one as the "Reply Address".

From technet documentation, it states that the EUM address first in the list of EmailAddresses would be the primary, but this is not the case either.. as they both are listed as EUM:

Any help or a better method would be appreciated. If you have a 2013 environment to test on, I'd like to know if maybe it's fixed in 2013 - then I'll feel better about moving forward without a fix if needed. Thanks all.

↧

Exchange 2013 um fax with Lync integrated

December 16, 2013, 10:53 pm

≫ Next: Attachment Content-Disposition does not satisfy with the specification http://www.ietf.org/rfc/rfc2183.txt

≪ Previous: Multiple Primary EUM Addresses for a user mailbox - Set As Reply

Hi!

We are planning to deploy Exchange Um and integrate this with our Lync enterprise Voice users. We are also looking at replacing some older fax solutions. When I started to read the Exchange UM documentation I noticed this:

"Sending and receiving faxes using T.38 or G.711 isn't supported in an environment where Unified Messaging and Microsoft Office Communications Server 2007 R2 or Microsoft Lync Server are integrated. "

Does this mean that if we integrate Exchange and Lync we will not be able to configure FAX in Exchange UM?

-UC

↧

Attachment Content-Disposition does not satisfy with the specification http://www.ietf.org/rfc/rfc2183.txt

December 17, 2013, 1:53 am

≫ Next: Remove Dial Plan Error

≪ Previous: Exchange 2013 um fax with Lync integrated

RFC 2183 tells that the Content-Disposition header field is defined as follows:

creation-date-parm := "creation-date" "=" quoted-date-time
modification-date-parm := "modification-date" "=" quoted-date-time

But when we send a message with the attachment we have dates without quotes:

Content-Disposition attachment;
	filename="Data.xml";
	size=28306;
	creation-date=Fri, 13 Dec 2013 11:37:14 GMT;
	modification-date=Fri, 13 Dec 2013 11:37:14 GMT

Is this a bug of the Exchange Server 2013?

↧

Remove Dial Plan Error

December 4, 2012, 2:11 pm

≫ Next: Powershell - Holiday Schedule Issue

≪ Previous: Attachment Content-Disposition does not satisfy with the specification http://www.ietf.org/rfc/rfc2183.txt

Hello,

I'm trying to remove a dial plan in Exchange 2013, but it keeps telling me that "This dial plan is associated with server SERVER_NAME." I've tried removing it thru EAC and powershell using remove-umdialplan, but both of them fail stating that it's associated with one of my servers.

I ran get-umcallroutersettings on both of my Exchange 2013 UM servers and the DialPlan parameter is set to null on both.

Is there another spot in the EAC that ties the server to the dial plan?

Thank you,

Zach

↧

Powershell - Holiday Schedule Issue

October 23, 2013, 9:14 am

≫ Next: Source IP for outgoing calls

≪ Previous: Remove Dial Plan Error

I am trying to use powershell to set a holiday schedule for multiple auto attendants but am testing on just one. It looks like it applies ok but does not work. When it should be active I get a "user does not have a valid mailbox on the system ... goodbye"

I have verified the format of the audio file. If I create the holiday manually and browse to the same file it works fine.

Not getting why adding it with powershell makes it fail to work. I set the date for today to test.

script

-----

Set-UMAutoAttendant -Identity Depere -HolidaySchedule "Christmas,D:\Holidays\gschtest.wav,10/22/2013", "Christmas Eve,D:\Holidays\gschtest.wav,10/23/2013"

Any help would be appreciated as I would rather automate the process for upcoming holidays.

Thanks

↧

Source IP for outgoing calls

June 5, 2013, 3:01 pm

≫ Next: New Top Support Solutions blog

≪ Previous: Powershell - Holiday Schedule Issue

Running Exchange 2013 CU1.

IP gateway is expecting SIP to come from a specific IP address. Is there any way to configure outgoing calls to the UM IP gateway to send from a specific IP address?

↧

New Top Support Solutions blog

December 19, 2013, 10:17 pm

≫ Next: dialing rules not normalizing - can't transfer via auto attendant menu

≪ Previous: Source IP for outgoing calls

Hello

As part of our efforts to keep our communities informed about the most relevant content that address the top questions that we are getting in out forums and other support channels we want to introduce the new “Top Solution Content” blog (http://blogs.technet.com/b/topsupportsolutions).

In this blog you will find up-to-date and valuable information about Microsoft top support solutions for several of our popular products in the Server and Tools portfolio. You can use the tags (http://blogs.technet.com/b/topsupportsolutions/archive/tags) to easily locate the product of your preference or visit the home page to see what’s going on for the different Microsoft Enterprise and developer products. As a blog you can also subscribe to post and comments using the RSS feeds.

We hope this will reduce time and effort when you are looking for relevant content. Enjoy it!

Thanks

Microsoft Support team

↧

dialing rules not normalizing - can't transfer via auto attendant menu

December 20, 2013, 3:52 am

≫ Next: Unbale to add Exchange 2007 UM role

≪ Previous: New Top Support Solutions blog

Under Exchange 2010 we were never able to get 4 digit extensions in auto attendant menus to transfer - we would get the "the call could not be transferred - returning to main menu" message. We specified the whole 11 digit DID instead and transfers worked, so we stuck with that for the last couple of years. I now realize the latter worked because our Global Dial Plan in Lync had a normalization rule for 11 digits (but not for 4). It never occurred to me before because we only use User Dial Plans and the fact that Exchange normalizes via the Global Dial Plan in Lync doesn't appear to be well documented.

Fast forward to our Exchange 2013 migration, which is now complete, and all the AA settings came over as they were before and still work. BUT we have our first changes to be made now that the holidays are approaching, and we've discovered that in 2013 the gui forces you to use the number of digits your dial plan extensions are set for (in our case 4) - it won't accept the 11 digit workaround any more (existing 11 digit values continue to transfer properly).

The problem with using the Global Dial Plan in Lync to normalize is that we have 3 different user dial plans, and there are some overlapping extensions between them - so the global dial plan won't work for us.

My understanding is that Exchange dialing rules should be used to normalize the numbers before they get passed to Lync - but it doesn't seem to work. I created a dialing rulefor number pattern xxxx with +1619683xxxx as the
dialed number, but it doesn't work. Snooper shows that the plain 4 digits are still getting passed directly to Lync with no normalization, and fail.

Anyone know how to get the dialing rules to normalize properly?

Thank you!

↧