AnotherUCBlog > Exchange, S4B, O365

Share my findings in the Microsoft unified communication world



O365 – PST Import with Azure Storage Explorer error

Dear all,

If you have issues trying to upload pst files to Azure using Azure Storage Explorer and the SAS URI provided by the O365 Import PST wizard, try to use “Azure Stack API” instead of “Default Azure API”

Reload the tool and you should be able to upload your PST files.

I know this is not a supported way to upload your pst but in my case, AzCopy wasn’t working…

Found that thanks to SilentSausage in this github post :


Publish Office Online Server (WAC) with F5 issue

Hi Everyone,

Today, I faced an issue where I implemented an Office Online server (formerly know as Office Web App server or WAC) for a customer. Presentation was working well internally but was stuck in Loading when trying from an external connection.

This Office Web App server was published via an F5.

So I launched Fiddler and enabled HTTPS decryption like below:

Launch Fiddler -> Tools -> Fiddler Options -> HTTPS -> Decrypt HTTPS traffic -> Install fiddler Root Certificate

This makes me able to retrieve the complete URL


And I tried to access this URL from my web browser and got this error :

The requested URL was rejected. Please consult with your administrator.

Your support ID is: 3105466502033495217

[Go Back]

I did the same test from an internal connection and got the presentation in the web browser so I knew that the F5 was sending this error.

The IT guy who is managing the F5 found that it was caused by a parameter called “Enforcement Mode” in the “Application Security” part. It was set to “Blocking” and as soon as he changed it to “Transparent”, Presentation started to work externally.


Hope this will help you


Audiocodes Mediant – Forking/Alternative routing E1 and SIP

Hi everyone,

It has been while I’v not written anything here but this week I encountered a weird behavior that I want to share with you.

It started with the wish to set up a coexistence between a SIP telephony provider, a Skype for Business and an Alcatel OXE. As the Alcatel OXE was not having SIP board so we had to use an E1 trunk. To do so, we chose an SBC Audiocodes Mediant 800C.

This is just the beginning of the story because the customer wanted to give the choice to his users to use the Alcatel or Skype for Business at any time so we had to use call forking…

Then the nightmare started…

To do call forking with an Audiocodes, you have to set up two IP-To-IP routing rules and the first one has to be configured like this :

  • Alternative Route Options = Route Row
  • Group Policy = Forking

Like below :

As this rule is supposed to route calls to Alcatel, the Destination Type is “gateway”.

The second IP-To-IP routing rule will have to be configured like this :

  • Alternative Route Options = Group Member Ignore Inputs
  • Group Policy = Sequential

Like below :

As this rule is supposed to route calls to Skype for business, the Destination Type is “IP Group”, the Destination IP Group is “IPG_SFB” and the Destination SIP Interface is “SIP_SFB”.

And “voilà” !!! So we took a phone and tried to call a number that is available both on Skype and Alcatel but only the Alcatel ring….

Having a look at the Syslog from the Audiocodes, we saw only one call to the Alcatel which was the case but going through the log, we saw that error after the INVITE :

We can see that it lacks of UDP ports… After a call to an Audiocodes trainer, he told us that Alternate routing and Call Forking with E1 need UDP ports to create the second call session.

After we enabled UDP ports on the SIP provider interface, the error disappeared and calls arrived both on Skype and Alcatel phone.

Below is the trace of the two calls :

To summarize, if you want to do call forking or alternative routing with an Audiocodes Mediant, SIP PBX and E1 PBX, enable UDP ports on your SIP interfaces.

Hope this will save you time 😉

SKYPE FOR BUSINESS – User unable to change his status

Hi Everyone,

This week I received a call from a customer saying that he can’t change his status and other users are seeing him with a different presence information…

As presence information are stored in the SQL database, I said to myself there is an issue with the user account in the database.

So I launched the SQL management studio and connect to the RTC instance. Then type the query : Select * from [rtc].[dbo].[Resource] WHERE [UserAtHost]='<SIPURI>’

I found the user and his resourceid, keep it in mind.

Delete the account from the Control Panel or by powershell and relaunch the previous query.

I still found the user but with a different resourceid.

So I delete it with the query : DELETE FROM [rtc].[dbo].[Resource] WHERE [UserAtHost]='<SIPURI>’

I wait for some minutes and recreate the Skype account using the Control Panel or Powershell and VOILA. The user was able to change his status and the others were seeing him correctly.



SfB/Polycom – VVX IPPhones BToE (Shared desktop/VDI)

Here is the situation :

  • Skype for Business
  • Client running Windows 7 under Citrix Xendesktop
  • Wyse terminals
  • Polycom IPPhones VVX

With the release of Polycom BtoE v3.7, Polycom is supporting VDI Citrix Xendesktop environment (HDX Optimization needs to be disabled) for BToe with VVX Phones running UCS v5.7.

We have found that when you install the software with a user, pair the phone with this user using the manual pairing (code pairing). You can sign out and then sign in (windows session), the pairing is restored automatically. If on the same machine, you log on with another user and then sign out and sign in again, the pairing is not restored automatically until you repair the BTOE installation…

This is due to the software not trying to create the following registry values if they do not exist when performing the first pairing for the user who did not install the BTOE software:

[HKEY_CURRENT_USER\Software\Polycom\Polycom BToE Connector]




After deploying a GPO to create those values at log on (create not update), the software is able to register the pairing code and pairing is automatically restored after a sign out sign in.

This issue also occurs in a “normal” enviroment (without Citrix XenDesktop) where desktop are shared between multiple users.

FYI, the pairing code change when the phone change his IP address. The pairing code is kept after a phone reboot.

Hope this will save you time


EXCHANGE/SFB/UM – Callee voicemail language issue

Hello all,

I had an interesting behavior found by customer recently, he tolds me that when he is reaching the voicemail of one of his user (skype call), voicemail language is in English no matter the UM dialplan…

When I tried to call the user from my mobile, I got the voicemail in the right language (french in our example).

I performed multiple tests and got those results :

  • Internal Skype call -> wrong voicemail language
  • Skype call from federated partner -> right voicemail language
  • PSTN call -> right voicemail language

I compared the Skype for Business logs between internal call and federated partner call and found no difference, the same UM diapl plan was called…

Then I finally found that it was due to the caller mailbox language ! If the caller is having an Exchange mailbox in English then he will reach a voicemail in English.

So this is not an issue but it is per design !


Lync/SfB – Simultaneous ringing not working

Hi all,

New day, new challenge !

We faced an issue where users who use/used the Skype for Business mobile client were not able to get simultaneous ringing working…

Even they disconnect and uninstall the application, simultaneous ringing was no more working for their mobile device set in AD but it was working with another number.

Then I launched the lync debug tool and saw that it was trying to reach the sip address (the phone number to reach was on an iPhone)

So I tried to test the push notification with this command on the front-end server :

Test-CsMcxPushNotification -AccessEdgeFqdn EdgeServerFQDN

So I followed the article to configure push notifications :

Then simultaneous ringing start to work again for those users who were using the mobile app.



Domino/Exchange – Perform offline migration nsf to pst

Hi all,

If you cannot or don’t want to have a direct connection between your “old” domino servers and your Microsoft Exchange servers, then you can use Quest Notes Migrator for Exchange to convert nsf files to pst. Here is how to do it :

  1. Export names.nsf (NAB) from domino server and copy it on NME server
  2. Launch the NME program and perform the SQL configuration and logs folder path then close NME
  3. nme1
  4. nme2
  5. In ini conf file, add the following parameters:











  1. With SQL management studio, create the domino server from where the names.nsf is coming with the command below:

INSERT INTO [NME40DB].[dbo].[T_NMEServers] (NMEServerGUID,DisplayName,ServerType,ServerName,HostName) values (‘12345678-1234-1234-1234-123456789123′,’DominoServerName‘,1,’DominoServerName‘,’DominoServerName‘)

For example :

INSERT INTO [NME40DB].[dbo].[T_NMEServers] (NMEServerGUID,DisplayName,ServerType,ServerName,HostName) values (‘12345678-1234-1234-1234-123456789123′,’CHMAMA01′,1,’CHMAMA01′,’CHMAMA01’)

  1. Launch again NME and perform the “Discover Notes Information” by adding the “names.nsf” you got from step 1 this will help NME to translate Domino user names into Exchange user names
  2. nme3 nme4 nme5
  3. Then you can start your migrations/conversions by creating the collection of mailboxes you want to migrate and then launch the locate Notes datastore to define where to search the nsf files :
  4. nme6 nme7
  5. Finally you can launch the migration with the final step “Migrate user data”



SFB – Dial-In number displayed twice for new Skype meeting

Hi all,

On a fresh install of Skype for Business, I created one and only one dial-in number but this one wear appearing twice when creating a “New Skype meeting” from Outlook.

We discover that this was the case only when using Outlook 2010 or 2013 with the Skype for Business client 2016.

This was not the case when using Outlook 2016 or OWA.

The only workaround I found was to create a second dial-in number for a different language (One for English and one for French) then both numbers were appearing and no duplicates.

FYI, I was running Skype for Business Server 2015 with CU4.

Hope it will save you time troubleshooting.


Create a free website or blog at

Up ↑