• Home
  • My Tools
  • Visio Stencils
  • Online Tools
  • PS Scripts
  • PS One Liners
  • Downloads
  • Product Review
  • About

Smarter Together

~ by I.M.H.O.

Smarter Together

Category Archives: Unified Messaging

No Presence for Fedrated partners – Event ID 11

08 Wednesday Jun 2016

Posted by Paul Bloem in Error Codes, Event ID, Federation Issue, Lync DNS Records overview, Lync Edge, O365, Office 365, SRV, SRV Record, Uncategorized, Unified Messaging, voicemail

≈ 2 Comments

Tags

Event ID 11, ms-diagnostics: 1008;reason="Unable to resolve DNS SRV record", Troubleshooting

Problem

Came across a deployment with the following 2 issues:-

  1. federated partners were showing up as presence unknown
  2. unable to call voicemail (hosted in O365)

When trying to send messages to these “unknown” federated partners I got “This message wasn’t sent due to company policy”.

So why did I try to message a contact with a presence status of “unknown? Simply because the federated contact could see my users presence and send me IM’s, I was even able to respond to these IM’s although the presence was still “unknown”.

Presence Unknown

Troubleshooting

A quick look at the client side logs revealed an error in the presence Subscribe message

CSeq: 1 SUBSCRIBE
Via: SIP/2.0/TLS 172.11.12.13:24164;ms-received-port=24164;ms-received-cid=FC9300
ms-diagnostics: 1008;reason=”Unable to resolve DNS SRV record“;domain=”ucsorted.com”;dns-srv-result=”NegativeResult”;dns-source=”InternalCache”;source=”access.ucsorted.com”
Server: RTC/6.0
Content-Length: 0

Taking a look at the users (client side) local event log I found the same error.

Event Log

Event ID 11
A SIP request made by Lync failed in an unexpected manner (status code 80ef01f8).

Response Data
504  Server time-out
ms-diagnostics:  1008;reason=”Unable to resolve DNS SRV record“;domain=”ucsorted.com”;dns-srv-result=”NegativeResult”;dns-source=”InternalCache”;source=”access.ucsorted.com”;OriginalPresenceState=”0″;CurrentPresenceState=”0″;MeInsideUser=”No”;ConversationInitiatedBy=”6″;SourceNetwork=”5″;RemotePartyCanDoIM=”Yes”

Clearly there is some issue with either the federation SRV record or resolving the federation SRV record.

Checking the SRV record from the Edge server I can see that this record is not found. Checking the DNS for the Edge server I noticed that the interfaces are pointing to the internal DNS servers.

Solution

We have 2 options here:-

  1. Configure the Edge Server to point to a public (external) DNS server where the SRV record for _sipfederationtls._tcp.domain.com is valid (frowned upon by some security folks)
  2. Add the SRV record for _sipfederationtls._tcp.domain.com to the internal DNS, making sure that the target FQDN is the Public Access FQDN of the Edge Server.

NOTE

Here is a little reason why you may want to avoid using the common sip.domain.com DNS name for your Edge Servers Access FQDN (only..). Internally the sip.domain.com record was generally configured to resolve to the front end pools, if we now need an internal SRV record for _sipfederationtls._tcp.domain.com then targeting this to sip.domain.com will simply get to the Front End Pool and not to the Federation point at the Access Edge FQDN.

 

 

Advertisement

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on WhatsApp (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to share on Pocket (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Skype (Opens in new window)
  • Click to email a link to a friend (Opens in new window)
  • Click to print (Opens in new window)

Like this:

Like Loading...

How to use UM Voicemail for Cell\Mobile calls

12 Friday Feb 2016

Posted by Paul Bloem in Unified Messaging, voice mail, voicemail

≈ 1 Comment

Tags

Mobile Voicemail to Exchange UM

I don’t know about you but I certainly miss a lot of calls during any given day. Mostly because I don’t take calls when already in conversation (consider it a bit disruptive) and especially not when I am in meetings. OK so I get lots of voicemail..

Voicemail is one of those necessary evils, something I love to hate.

When getting voicemail via my Skype for Business client to the Unified Messaging platform, I do love..

  • how I can forward on the voicemail and add a note as I do so
  • how I can archive and keep copies of a message
  • how I can write rules around who reaches me and when
  • I get to choose which messages I want to listen to without having to follow a tedious DTMF dial pad process that offers the oldest voicemails first

When getting voicemail on my cell phone, I hate how..

  • even if I say save the message, its still going to be deleted in 10 or 15 days
  • I have no visual reminder associated with the actual message to tell me the number of the caller was, instead a DTMF selection reads the callers number to me
  • if I have multiple messages, I have to listen to each message in sequence. Sure I can skip a message BUT I still need to listen to the first bit to determine if its what I am looking for.

In a perfect world, I’d like to get my voicemail delivered to my UM mailbox every time, regardless of the source being SkypefB\Lync or Mobile\Cell network.

Configuring Mobile and UM for one Voicemail Box

Overview of steps as follows:-

  1. Configure the mobile phone to send calls to you OWN DDI\DID in Skype for Business as a voicemail destination
  2. Setup UM to send calls from your Mobile number to voicemail

So lets get started..

Changing the default voicemail service offered by your carrier may appear to be next to impossible. There are multiple reasons a call may land in voicemail. You may need to cater for each of these.

The table below indicates the forward type and the codes required to manage them.

Forward Type Description Set and Enable Disable Enable Delete Check Status
Forward if no answer Will forward calls to another location if the call is not answered after a set period of time *61*[dest]*11*[sec]# #61*11# *61*11# ##61*11# *#61*11#
Forward if busy Forwards calls to another location if you are using your phone and you have either disabled call waiting or if you are in the process of making an outgoing call *62*[dest]*11# #62*11# *62*11# ##62*11# *#62*11#
Forward if unavailable Forwards calls to another location if the handset is off or outside of service area *67*[dest]*11# #67*11# *67*11# ##67*11# *#67*11#

Note

  • The codes may differ for your carrier
  • The code 11 is used to indicate voice calls, additional codes exisit for data, text etc.

So lets assume that my Cell\Mobile Number is +6421 123 456 and my Skype\Lync DDI\DID is +649 97 012 345 as we go through the setup.

On my iPhone its done as follows:-

Forward No answer

Using the phone dialler, call *61*+64997012345*11*20# using the phone’s keypad. 

11 = Voice Calls & 20 = seconds before forwarding is triggeredForward no Answer Code.PNGForward no answer confirm

 

 

 

 

 

 

 

 

 

 

Repeat for Forward Busy and Unreachable.

Checking the Status

Using the phone dialler, call *#61*11# using your phone’s keypad. 

Status Check

So now we have unanswered, busy and unreachable calls to mobile\cell going to the Lync\SkypefB Client.

At this point the calls will follow the rules as per any call to your Lync\SkypefB client. Of course we can now configure some personal options specifically for calls from mobile to Exchange UM.

Configuring Voicemail for Calls from Mobile is done in OWA.

From the Options Menu item select Phone and add a new Voicemail Call Answering Rule, I have called mine Mobile Voicemail.

OWA Phone

Defining the Call Answering Rule we will first specify that the call is from my Cell\Mobile number.

To do that select The Caller is.. in the drop down box

Call is from

Check the box “Calling from these phone numbers” and specify your mobile\cell number.

New Call Answering Rule

Click the + sign to add the number and the OK button to save

Calling from these numbers

Next we need to tell the rule what to do, so from the Do the following drop down box, select “Provide the caller with these option”

Caller Options

Click on Select Options, you will notice that the default option to leave a voice message is selected, simply click the OK Button to accept

leave a voicemail

Your new call answering rule should now look similar to the image below. Click on the Save button to save

save new call answering rule.jpg

Ensure that the Call answering Rule is enabled by clicking the On Box and click save one more time.

enable call answering rule.jpg

Now for testing..

Get someone to ring your mobile\Cell and leave the call as unanswered, the call should launch through to your Lync\SkypefB client. This allows you to either answer the call, or if you are busy\Offline the call will fire through to Unified Messaging Voicemail.

Sorted..

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on WhatsApp (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to share on Pocket (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Skype (Opens in new window)
  • Click to email a link to a friend (Opens in new window)
  • Click to print (Opens in new window)

Like this:

Like Loading...

How to configure Office 365 Unified Messaging with Skype for Business

11 Wednesday Nov 2015

Posted by Paul Bloem in Office 365, Unified Messaging, voicemail

≈ 10 Comments

Tags

Office 365 Unified Messaging

Configuring Skype for Business and Office 365 Unified Messaging for Voicemail is a fairly simple task. Of course no task should be undocumented, so here goes.

Environment

On premise Skype for Business 2015 deployment
Mail delivered via Office 365
On premise users synchronised back to Office 365 via DirSync

NOTE: UM connectivity, in this case is done via Federation to Office 365. So it goes without saying that a working Edge infrastructure is required. Also Federation needs to be enabled (and working)

First we will configure the Skype for Business Front End Pool

From the Skype Front End Server
1. Ensure that Federation is enabled for the Edge Configuration (Federation needs to be enabled in the Topology). Confirm by the following cmdlet:-

Get-CsAccessEdgeConfiguration

RoutingMethod

To change AccessEdgeConfiguration:-

Set-CsAccessEdgeConfiguration -enablepartnerdiscovery $true -UseDnsSrvRouting -AllowFederatedUsers 1

NOTE Partner discovery may be either enabled or disabled.

2. Adding O365 as a hosting provider for UM

New-CsHostingProvider -Identity “Exchange Online” -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFqdn “exap.um.outlook.com” -IsLocal $False -VerificationLevel UseSourceVerification

exap.um.outlook.com

3. Make sure these changes have been replicated (don’t continue until it has!)

Force Replication with:

Invoke-CsManagementStoreReplication

Confirm with Replication Successfully completed:

Get-CsManagementStoreReplicationStatus

check replication

4. We now need to add the Hosted Voicemail policy, The Office 365 Tenant Name is required for this. The policy is added with the following cmdlet:

NOTE “CloudUM” in my case is the name I gave the on premise UM Policy

New-CsHostedVoicemailPolicy -identity CloudUMPolicy -Destination exap.um.outlook.com -Description “Office 365 Voicemail” -Organization “tenantname.onmicrosoft.com”

CloudUM

TIP: To find the Organization name login to O365 Admin Portal. Don’t use the same Tennant name as the on premise SIP domain as that will resolve to on premise and, of course, for voicemail it needs to resolve to O365

The Organization Name is also the *Default Domain as defined in the Admin Center in the Company Profile page

Skype for Business Office 365 Unified Messaging

Skype for Business Office 365 Unified Messaging

Next, we need to configure Office 365

From the Office 365 Portal

  1. Navigate to Unified Messaging (Office 365 Admin Center – Exchange – Unified Messaging
exchange

2. Add a new UM Dial Plan by clicking on the +

UM Dial Plan

3. Complete the New UM Dial Plan Page as per your requirements and click Save

Office 365 Dial Plan
 4. To assign the Subscriber access number, edit the UM Dial Plan you just created.
UM Edit
5. Click on configure
Subscriber access configure
6. Select Outlook Voice Access and add the DDI\DID assigned to the ExUmContact on premise as DisplayNumber (see next step)
OVA DDI

Next we head back to Skype for Business

  1. Create the UM Contact

New-CsExUmContact -displaynumber +613456789 –sipaddress SIP:EX_UM_365_SA@ucsorted.com -registrarpool pool01.ucsorted.com -ou “OU=IT,OU=UCSorted,DC=com”

TIP: I often come across a request to change Subscriber Access number, use Set-ExUmContact to change it if you need too.

NOTE: By specifying the “DisplayNumber” the LineUri is also set (I know its odd)

New-CsExUmContact

2. Assign the Hosted Voicemail Policy to the EX UM Contact

Grant-cshostedvoicemailpolicy –identity “CN={f169db8b-….DC=au” –policyname CloudUMPolicy

TIP: I am not very fond of copying the identity in this manner. Since I have added only the 1 exumcontact I just do the following:-

Get-CsExUmContact | Grant-CsHostedVoicemailPolicy -PolicyName CloudUMPolicy

Then we switch to Exchange Online PowerShell

TIP: Use the following script to connect to EOL:

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

Exchange Online

Next,

Set-UMmailboxpolicy -identity “Office 365 UM Default Policy” -SourceForestPolicy “OnPremUMPolicy”

TIP: The identity is that of the Office 365 UM Mailbox Policy (not the UM Dial Plan)

The following step only applies if UM is already deployed on premise and this UM deployment is part of migrating UM to O365. This is done from the on premise exchange environment.

Set-UMmailboxpolicy -identity “On Premise UM Policy” -SourceForestPolicy “CloudUMPolicy”

Finally, time to configure users

IMPORTANT

You cannot have a spilt setup where UM is in O365 and the user mailbox is on premise or vice versa.

2 steps are required for enabling users for UM in O365:-

  1. From SkypefB – Grant the user the Hosted Voicemail Policy and enable the user for Hosted Voicemail
  2. From O365 – Enable the user for UM

Within Skype for Business 2015 PowerShell

Grant-cshostedvoicemailpolicy –identity “paulb” –policyname CloudUMPolicy

get-csuser –identity “paulb”

Set-csuser –identity “paulb” –hostedvoicemail $true

Within O365 Exchange Admin Center

Navigate to Recipients (Office 365 Admin Centre – Exchange – Recipients)

Find the user you would like to enable for UM and click Enable

O365 Recipients

Browse for the O365 UM Mailbox Policy and click next

UM Mailbox Policy

Provide the required extension number and PIN settings, click Finish to complete.

UM Extension

Of course synchronization by way of DirSync is required to ensure that the account is enabled for unified messaging.

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on WhatsApp (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to share on Pocket (Opens in new window)
  • Click to share on Pinterest (Opens in new window)
  • Click to share on Tumblr (Opens in new window)
  • Click to share on Skype (Opens in new window)
  • Click to email a link to a friend (Opens in new window)
  • Click to print (Opens in new window)

Like this:

Like Loading...
← Older posts

IMHO YouTube Channel

Follow Smarter Together on WordPress.com

Enter your email address to subscribe and receive notifications of new posts.

Join 674 other subscribers

Show your appreciation by donating

Archives

Category

ABS ABServer ADContacts Address Book AddressBook AddressBook Service Communicator contacts CX500 Devices DHCP DNS Edge Server Error Codes event id Exchange UM 2010 GAL Install Guide Lync 2013 Tools Lync Edge Lync Tools Microsoft Teams Monitoring Polycom Powershell Scripts Product Review QOS Quick Reference Guide Reskit RGS RTC Database SIP SIP Options Skype for Business Skype for Business Monitoring Skype for Business Tools SQL Teams TMG Tool Tools Troubleshoot Edge UC Sorted Tools UM Uncategorized Unified Messaging visio Visio Stencil voicemail

Blog at WordPress.com.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
  • Follow Following
    • Smarter Together
    • Join 63 other followers
    • Already have a WordPress.com account? Log in now.
    • Smarter Together
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...
 

    %d bloggers like this: