How to change LineUri number for CsExUmContact? There seem to be no option thru powershell.

Commandlet: Set-CsExUmContact

Thanks!
Uddan

Hi
Not sure if I am in the correct forum.

Following environment:
Exchange 2016 hybrid with Office 365
Skype for Business onprem with sip trunk

Skype is only used onprem only because PSTN calling is not yet supported in our country.
Exchange mailboxes are moved to Exchange Online, hybrid config is still in place.

Unanswered calls are going to voicemail, so far so good.
If a user calls to voicemail using the voicemail number he must enter his mailbox extension, then he gets "... is no a valid mailbox extension"
I have a test user with an onpremise his mailbox. If he calls to voicemail he is recognized, must enter his pin and everything works.

I followed different articles including https://blogs.technet.microsoft.com/nexthop/2016/03/29/integrate-on-premise-lync-or-skype-for-business-with-office-365-unified-messaging-um/, everythig seems to be configured correctly, but online user are not able to call to voicemail.

Any suggestions would be apreciated.

Regards
Peter

Sometimes, during troubleshooting, I turn up UM logging. I'd like to find a listing of what the ID:'s are for the menus. (Both in 2010 and 2016)

Like

0callDiscriminator

0100

0PersonalAutoAttendant100

0PersonalAutoAttendant101

0700701

0700702

0700703

and so on.  I'm just looking for a guide to what the ID's mean.  Thanks

Hi guys,

We've just noticed that internal calls are dropping when not answered instead of going to Voicemail and it seems to be isolated to just 1 of our 7 offices. If we call the same number from a mobile phone the voicemail works fine.

We are running a Hybrid Skype for Business on prem/Exchange Online environment

Handsets are Polycom VVX500's

Each office has its own provisioning server

Thanks in advance for the assistance.

Hi, after some assistance as i cant find much UC info online.

I am migrating from exchange 2013 to exchange 2016. Would like to run hybrid in the interim as it will take time to migrate all mailboxes. If i migrate a mailbox to the new server, voicemail does not work for that user....?

first question - Do i need to run the ExchUCUtil.ps1script on the new server or are the settings already in place?

Second question- If i do need to run the script, will this effect the current UM policy on the Ex 2013 UM server? We currently have the company IVR's running on the Ex 2013 UM server.

Thankyou in advanced

Hi

I have a basic question.. I hope somebody can help me... :)

I want to integrate Exchange 2013 with Lync 2013

I have a large organization with several Exchange mailbox and CAS servers. I was used to configure UM in Exchange 2010 where only one server had the UM rol, but now in Exchange 2013 all servers are UM so my question is,

Do I have to configure Exchange UM certificate in all Exchange servers because the user can be in any mailbox server? or can I configure only a few servers and this servers will route the message to the user even if that mailbox server is not UM?

I hope my question is clear.. English is not my first lenguage

Thanks in advance

Isaac

Hi 

I have a new Exchange 2016 Environment and have enabled the Windows Firewall. Exchange does add the Firewall rules by self. I have test with a User UM (Voicemail) works.

If I start the UM Test-cmdlet there's end in a timeout if the Firewall is on. i can't se something in the logs. What can I do to resolve this issue?

Test-UMConnectivityReasonForFailure:Waitfor the diagnostic sequence response. timed out after 20 seconds.

Greets
Florian

Dears,

We have Exchange 2013 with CU 15 now we are planing to integrate Cisco IM Presence 12.5, can you please let me know ho wto integrate with Exchange 2013, Please share the steps 

Your prompt reply will be highly appreciated 

Thanks  

Yasar Altaf

Hi,

When trying to remove a UMDialplan, e.g. "Test", it fails with error "There are UM users who are associated by their UM mailbox policy with the dial plan."

The ExchangeOnline is used for UM.

Removed all users from UM with following commands:
Disable-UMMailbox -Identity email
Set-csUser account -HostedVoicemail $false
Grant-CSHostedVoicemailPolicy -identity account -PolicyName ""

Checked if still mailboxes are related to UMDiaplan with:
Get-UMMailbox -ResultSize Unlimited | ? {$_.UMDialPlan -eq "Test"}
No results, so i suppose no UMMailboxes are related to this UMDialplan anymore

Removed UMmailboxpolicy from the UMMailbox successful with command:
Remove-UMMailboxPolicy -Identity "Test Default Policy"

Last step to remove UMDialPlan "Test" with command:
Remove-UMDialPlan -Identity "Test"
returns with error "There are UM users who are associated by their UM mailbox policy with the dial plan."

Any suggestions how to get the UMDialPlan removed?
Thanks in advance,

Patrick

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)

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.

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.

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.

Hello,

We recently added an HAProxy load-balancer for our Exchange server, and everything runs fine through it.

Then, we decided to change the internal records (autodiscover, ews, mail) to also point to those HAProxy (because we have some services using EWS that can gain from having the connectivity to the Exchange servers load balanced). Before that, the internal DNS records were pointing directly on the Exchange servers.

Sadly, after doing so, the Instant Messaging on OWA stopped working, and the logs were showing SignIn Timeout. We made sure the S4B servers are well allowed to contact the HAProxy, we saw EWS and Autodiscover flow without issues, but still it wouldn't work.

So to summarize:

S4B Servers -->  (resolve DNS)  --> Exchange Servers: OWA IM Working

S4B Servers -->  HAProxy(s) Virtual IP  --> Exchange Servers:  OWA IMnot Working

As soon as we changed the Hosts file on the S4B front end servers to point back to Exchange Servers directly, it worked back.

Does anyone have any experience with this? Is this scenario not supported?

Thank you

Hi,

I'm in the process of setting up Exchange 2013 hybrid deployment. I've run ldFix and fixed all the errors it reported except for an issue with the existing dial plan which has spaces in it:

"CN=User Name,OU=Human Resources,OU=User Names,DC=my-corp,DC=local",user,proxyAddresses,character,EUM:6508;phone-context=Dial Plan.my-corp.local,EUM:6508;phone-context=DialPlan.my-corp.local

Obviously it doesn't like the spaces in the dial plan name. I've tried creating a new dial plan without spaces, but I can't complete the setup as the gateway is on the original dial plan.

What's the best way to move 200+ users to the new dial plan without interrupting service to them?

Thanks!

I had 2 accounts with G Suite but now I have backup of those email id as ".mbox" files and these are just idle on my system and I am in urgent need of important emails and these are really crucial for me.

Please suggest me effective way or any solution that can be lifeline of email backup

I have now move to Microsoft Office 365 account. Now I am not running my part-time business of Electronics, I had some unforeseen situation I faced and due to that I had to close my part-time business and so now I become afull time blogger.

Please suggest me on urgent basis.

Thank you

Hello,

We are running Exchange 2013 CU 3 and Lync 2013 rollup 8.  For the most part, UM is working smoothly.  Callers are able to call our main number (auto attendant) and transfer to a user's extension. No problem.

We have configured a Lync response group to serve as our operator...and this is where the issue begins.  If we configure the response group with a five digit extension like our regular users, and set the operator extension as that 5 digit number, the auto attendant replies "Sorry, I couldn't transfer your call."  If I switch the response group to a full E164 number and enter that as the operator extension (minus the +, of course) it works.  While the response group is configured with the 5 digit extension, I can call it from within Lync without issue by extension...the problem only surfaces when the auto attendant tries to transfer.  The application log on the UM server throws two events:

1136, MSExchange Unified Messaging

Log Name:      Application
Source:        MSExchange Unified Messaging
Date:          1/29/2015 9:37:20 AM
Event ID:      1136
Task Category: UMCore
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xxxxx
Description:
An error occurred while transferring a call to "52000". Additional information: The call transfer type is "Blind.", the transfer target is "phone number". Call ID: "a29b56c9-35e5-4e1b-b199-a4d389cd54ee". Referred by:"".

Log Name:      Application
Source:        MSExchange Unified Messaging
Date:          1/29/2015 9:37:20 AM
Event ID:      1079
Task Category: UMCore
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xxxx
Description:
The VoIP platform encountered an exception RequestUri=sip:xxxxx:5066;transport=Tls;ms-opaque=4c80a8b56130406c RequestMessageType=NOTIFY
Microsoft.Rtc.Signaling.FailureRequestException:The transfer operation failed. For more information, refer to the message data in the exception.
   at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
   at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)
   at Microsoft.Rtc.Collaboration.Call.EndTransferCore(IAsyncResult result)
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.BlindTransferSessionState.Call_TransferCompleted(IAsyncResult r)
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SubscriptionHelper.<>c__DisplayClass67`1.<>c__DisplayClass6a.<WrapCallback>b__66()
   at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.<CatchAndFireOnError>b__b()
Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at Microsoft.Rtc.Signaling.FailureRequestException..ctor(String message, Exception innerException, SipRequestData requestData)
   at Microsoft.Rtc.Collaboration.Call.CallTransferAsyncResult.Refer_StateChanged(Object sender, ReferStateChangedEventArgs e)
   at Microsoft.Rtc.Signaling.ReferStateChangedEventArgs.Microsoft.Rtc.Signaling.IWorkitem.Process()
   at Microsoft.Rtc.Signaling.WorkitemQueue.ProcessItems()
   at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessing()
   at Microsoft.Rtc.Signaling.SerializationQueue`1.ResumeProcessingCallback(Object state)
   at Microsoft.Rtc.Signaling.QueueWorkItemState.ExecuteWrappedMethod(WaitCallback method, Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 during the call with ID "a29b56c9-35e5-4e1b-b199-a4d389cd54ee". This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the server. The server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.

Any ideas?  Everything I've found seems to suggest disabling refer support within Lync, but that's already done---and on the whole, the issue is only affecting transfers to a response group via 5 digit extension. 

Thanks in advance :)

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!

Enable-UMMailbox -Identity "Email Address"  -UMMailboxPolicy "Default Policy"  -Extensions  1234567890 -PIN 1234567890  -SIPResourceIdenti

fier "Email Address" -PINExpired $true -Verbose

VERBOSE: [17:18:43.857 GMT] Enable-UMMailbox : Runspace context: Executing user: Executing user organization:

, Current organization: , RBAC-enabled: Enabled.

VERBOSE: [17:18:43.872 GMT] Enable-UMMailbox : Initializing Active Directory server settings for the remote Windows PowerShell session.

VERBOSE: [17:18:43.872 GMT] Enable-UMMailbox : Active Directory session settings for 'Enable-UMMailbox' are: View Entire Forest: 'False', Default Scope: 'idir.BCGOV',

Configuration Domain Controller: 'Wagon.idir.bcgov', Preferred Global Catalog: 'Server', Preferred Domain Controllers: '{ Server }'

VERBOSE: [17:18:43.872 GMT] Enable-UMMailbox : Beginning processing Enable-UMMailbox

VERBOSE: [17:18:43.872 GMT] Enable-UMMailbox : Instantiating handler with index 0 for cmdlet extension agent "Admin Audit Log Agent".

VERBOSE: [17:18:43.888 GMT] Enable-UMMailbox : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }},

Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }

VERBOSE: [17:18:43.904 GMT] Enable-UMMailbox : Searching objects "EmailAddress" of type "ADUser" under the root "$null".

VERBOSE: [17:18:43.904 GMT] Enable-UMMailbox : Previous operation run on domain controller 'Server'.

VERBOSE: [17:18:43.904 GMT] Enable-UMMailbox : The current object has been processed by the cmdlet extension agent with index 0.

VERBOSE: [17:18:43.904 GMT] Enable-UMMailbox : Processing object "Users/DisplayName".

VERBOSE: [17:18:43.966 GMT] Enable-UMMailbox : Searching objects "Default Policy" of type "UMMailboxPolicy" under the root "$null".

VERBOSE: [17:18:43.966 GMT] Enable-UMMailbox : Previous operation run on domain controller 'Server'.

VERBOSE: [17:18:44.158 GMT] Enable-UMMailbox : Admin Audit Log: Entered Handler:Validate.

VERBOSE: [17:18:44.158 GMT] Enable-UMMailbox : Admin Audit Log: Entered ClassFactory:InitializeConfig.

VERBOSE: [17:18:44.189 GMT] Enable-UMMailbox : Admin Audit Log: Exited ClassFactory:InitializeConfig.

VERBOSE: [17:18:44.198 GMT] Enable-UMMailbox : Admin Audit Log: Exited Handler:Validate.

VERBOSE: Enabling UM mailbox "EmailAddress" with UM mailbox policy "Default Policy".

VERBOSE: [17:18:44.199 GMT] Enable-UMMailbox : Resolved current organization: .

VERBOSE: [17:18:44.452 GMT] Enable-UMMailbox : Admin Audit Log: Entered Handler:OnComplete.

Mailbox 'EmailAddress' couldn't be initialized for Unified Messaging: There was an error accessing the mailbox using EWS. The requested operation failed with

ResponseCode "ErrorInternalServerError". Details : An internal server error occurred. The operation failed..

    + CategoryInfo          : NotSpecified: (:) [Enable-UMMailbox], RecipientTaskException

    + FullyQualifiedErrorId : [Server=,RequestId=a6e32ca1-aec6-4948-8019-99dc789b428a,TimeStamp=4/30/2020 5:18:44 PM] [FailureCategory=Cmdlet-RecipientTaskException]

    B31A567F,Microsoft.Exchange.Management.Tasks.UM.EnableUMMailbox

    + PSComputerName        :

Hi,

I need solution to blocking additional user mobile devices, but not block or quarantine existing user mobile devices that has connected to Exchange by using Active-Sync device.

I have followed as article below, but this impacted to existing all user mobile devices.

https://www.cgoosen.com/2012/11/controlling-activesync-device-access-on-exchange-2013/

https://practical365.com/exchange-server/preventing-new-activesync-device-types-from-connecting-to-exchange-server-2010/

Is it possible to block only new mobile device that will be add by users, but still keep existing all connected devices?

Hi,

I am in a Exchange 2013 environment with Skype for Business 2015 on-prem. I am also using Outlook 2016. If I map a shared mailbox (i.e. a mailbox that is actually configured as shared) to my Outlook as an additional Exchange mailbox and then try to setup a Skype for Business meeting I get the following error:

"You cannot schedule the Skype Meeting because you are not UC enabled or there may be configuration issues with your
account. MAke sure ou are signed in to the same account you use for Microsoft Outlook...."

It is correct that the mailbox is not UC enabled as it is just a standard shared mailbox but my users would like to set up Skype for Business against it. Is there are way to do this?

At the moment, if I log into Outlook Web Access and open this shared mailbox in a separate window I am able to create an Skype Meeting without issues. So I am not sure why it works in OWA like that but not on Outlook. Also I have full rights to this as well. 

The other "workaround" we have is to create a skype meeting on my own calendar and then copy the meeting link over to the one on the shared mailbox. It's a clunky method and not ideal.

Most of the issues I found around this are to do with Office 365 but in my case both Exchange and Skype are on-prem installations.

Any suggestions appreciated.