Lync 2013 on Server 2016 meet now not working

Question

Lync 2013 on Server 2016 meet now not working

Aemilianus Kehler 101

I'm at my wits end.

I setup a whole new topology on a single Standard standalone Lync 2013 server on server 2016 (don't even ask me why still that old instacne and not a newer one, it's a sore subject that'll just trigger me).

I setup everything in a test environment and everything was working. We decided to test it with just a couple of us in IT, and sure enough the one thing I couldn't test (meet now with audio video, since it was all VMs without those hardware), doesn't work.

Yes, I have the latest May 2021 Lync CU installed.

Yes, I've done the Install-CSDatabase to resolve the issue after CU updates.

Yes, I've double checked all Simple URLs are correct.

Yes, I've run Enable-CSComputer.
2 Warnings: WARNING: No patterns found. Skipping rewrite rule creation for Web Scheduler.
Nothing related to meeting/conferencing

Yes, I've checked the Lync Control Panel and all Services are green.

Yes, I've Checked Event viewer, as how I cleaned up all other issues noted from CU update.

Yes, I've enabled verbose logging on the client. Main errors include:

"ERROR :: CRTCCccpDecoder::GetEndpointTypeFromText - unknown session-type:
WARN :: not expecting focus entity in getConference response
ERROR :: CUccOutgoingInviteOperation::Execute: HRESULT API failed: 80ee000b = hr. StartNegotiation on Media Flow failed
ERROR :: CUccPresenceDeviceInstance::ProcessValue - Timezone string is unexpected format (length 0, expected 14). Assuming timezone is GMT
ERROR :: SIP_URL::InternalInitialize Didn't find host while parsing SIP URL []"

The only one that seems relevant is the Media Flow one.

Yes, I've disabled the firewall on both server and client.
Yes, I created a dedicated open firewall rule on the Firewall between client and server.

Client is Skype For Business Office 2013, with all latest patches. 15.0.5233.1000

It makes me feel like a service issue on the FE side, but the logs are 100% clean there... I just can't figure it out! Driving me nuts! HELP!

Aemilianus Kehler 101 Reputation points

2021-06-30T15:37:23.597+00:00

This is just a internal communication, from internal user to internal FE. No Edge services to consider.

I Googled, and Googled, I found this technet post: https://social.technet.microsoft.com/Forums/en-US/e3661ff7-8b85-44fa-bf4a-cc9077dbec7f/warning-no-patterns-found-skipping-rewrite-rules-creation-for-meet-simple-urls?forum=lyncdeploy

But for some reason my lync server doesn't even have the Get-CSProvisionServiceConfiguration cmdlet?

NOTE 1 We had Lync2013 in a primary domain, and its still working 100% running on 2008R2
NOTE 2 New Lync server deployed in New Resource Domain. Yes msRTCSIP-OriginatorSID is properly populated as that's how main login works.
Aemilianus Kehler 101 Reputation points

2021-06-30T15:52:01.427+00:00

NOTE 3 Symptoms are as follows: Click File -> Meet Now
New Chat Window pops up (if all appdata cache files are cleared) takes about 10 seconds before a prompt of how to connect audio appears (select Skype app to call in).
Chat Windows open with participants listed, and then "You have left the call" and a rejoin button.
If I click rejoin, rarely it will connect me in for about 10 seconds before again stating "You have left the call". Most of the time it simply goes right back to just "you have left the call"

1 answer

Your answer

Aemilianus Kehler 101 Reputation points

2021-06-30T15:37:23.597+00:00

This is just a internal communication, from internal user to internal FE. No Edge services to consider.

I Googled, and Googled, I found this technet post: https://social.technet.microsoft.com/Forums/en-US/e3661ff7-8b85-44fa-bf4a-cc9077dbec7f/warning-no-patterns-found-skipping-rewrite-rules-creation-for-meet-simple-urls?forum=lyncdeploy

But for some reason my lync server doesn't even have the Get-CSProvisionServiceConfiguration cmdlet?

NOTE 1 We had Lync2013 in a primary domain, and its still working 100% running on 2008R2
NOTE 2 New Lync server deployed in New Resource Domain. Yes msRTCSIP-OriginatorSID is properly populated as that's how main login works.
Aemilianus Kehler 101 Reputation points

2021-06-30T15:52:01.427+00:00

NOTE 3 Symptoms are as follows: Click File -> Meet Now
New Chat Window pops up (if all appdata cache files are cleared) takes about 10 seconds before a prompt of how to connect audio appears (select Skype app to call in).
Chat Windows open with participants listed, and then "You have left the call" and a rejoin button.
If I click rejoin, rarely it will connect me in for about 10 seconds before again stating "You have left the call". Most of the time it simply goes right back to just "you have left the call"

Answer 1

Sharon Zhao-MSFT 25,761 Microsoft External Staff

@Aemilianus Kehler ,

You could try the following steps to fix your problem:

Disable conferencing feature in Lync server 2013, Topology Builder as below:
Publish Topology.
Install or Update Skype for Business Server System in Lync server 2013 - Deployment Wizard.
Reenable conferencing feature in Lync server 2013, Topology Builder.
Publish Topology.
Install or Update Skype for Business Server System in Lync server 2013 - Deployment Wizard.
Start services in Lync server 2013 - Deployment Wizard.
Then, test if you can use Meet Now feature.

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Aemilianus Kehler 101 Reputation points

2021-07-05T14:10:04.203+00:00

Thanks so much for the suggestion. I did as you suggested and when I went to enable conferencing the OK button got greyed out with a notice when I hover over the red x...

"You must select an OWA server"

I wonder if this was part of the problem, cause I'll admit I didn't define this area when I first published as I thought we didn't have an actual OWA server configured, but iI double checked the old server and OWA field was NOT defined. I guess the wizard didn't validate this initially, but here it does? strange.

I put in a value I don't think resolves to anything, but it did accept it... lets see what happens...

Weird Now when I click meet now. It asks me if I want to skype or reg call almost instant which is good, but as soon as I enter it now states "The Call was unsuccessful" and instantly beeps at me 3-4 times. Any idea?

When I click on the "Call was unsuccessful" it states "The Conferencing service is not available. Please wait and try again. If this problem persists, contact myself."

NOTE 1 when I went to check my old working server, I noticed a service that was not present on the new server "Lync Server Web Conferencing". Not sure what to make of this, but both servers have Lync Server IM Conferencing services running.
Aemilianus Kehler 101 Reputation points

2021-07-05T15:04:36.417+00:00

I'm not sure exactly what I did, I just removed mediation services from the topology, published it, when it run step2- Setup or Remove Lync Server components (which oddly didn't check off as being completed), saw that it completed successfully and now again showed green checked off, clicked start services.

When I went to check the services this time both Lync Server IM Conferencing and Lync Server Web Conferencing were there. Seems when I click Meet now I'm not getting booted which is nice, but it also doesn't go right into "You're the only one on the call" like the old server did. Will do a bit more testing and follow up. Thanks for the advice, after a bit more testing I can mark your reply as the answer.

UPDATE Problem persists, same issue try to click meet now, then instantly "You have left the call"
Aemilianus Kehler 101 Reputation points

2021-07-06T19:15:05.823+00:00

The issue appears to be blockage of ... something by the firewall between server and client.

While I had indicated I opened the firewall between the two initially the rule was fully open from client to server. After further diagnostics by my colleague. It was determined that it was unable to determine the "candidates" for ICE: http://lyncdude.com/2014/10/23/simple-understanding-of-media-traversal-in-lync/index.html

It was noticed that STUN was denyed from server to client. Though this shouldn't be required for internal comms.

For still unknown reason, everything worked only once a full open security rule was created to allow all traffic from the server to the client. (This is a standalone instance).

However it was not able to determine afterwards in the logs what traffic was needed, as it couldn't be seen once the rule was allowed, even though there was logging on the rule.

Any ideas? Of course this now becomes a finger pointing game at the firewall.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-07-07T05:59:13.767+00:00

@Aemilianus Kehler ,

Could you join the scheduled meeting or Skype audio/video call normally?

It seems a much more complicated problem. And after I read some official documents, I find that Windows Server 2016 is not an official certified Operating System for Lync server 2013. Here is the reference link. This could be a factor in your scenario.

To avoid some unknown issues, it is suggested to deploy Lync Server 2013 on a supported OS.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-07-09T09:42:56.573+00:00

@Aemilianus Kehler ,
Do you have any update now?
Please feel free to drop us any note.
Have a nice day!
Aemilianus Kehler 101 Reputation points

2021-07-12T17:14:35.173+00:00

As I already stated it was a blockage of UDP port 1024-60,000 FROM the Lync Server to the Lync Client.

Even though all documentation and technical diagrams show nowhere those UDP ports ranges from the server to the client.

Again also note I do NOT have an edge server, it was quite evident by Lync's media connection setup to utilize an edge server. This added to the confusion and mix up.

For some unknown reason again, the only way to make it work was to create a rule opening UDP ports 1024-60,000 from the server to the client. Only then would Lync be able to properly connect to the participant list provided to it.

Don't know why, some magic that doesn't seem to be discussed in even the most technical blogs.
Aemilianus Kehler 101 Reputation points

2021-07-12T17:17:01.237+00:00

I would have never thought of that, if it wasn't for corporate politics and funding, this wouldn't be an issue. In the real world we have to work with what we have.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-07-14T07:22:52.57+00:00

@Aemilianus Kehler ,
I will discuss with other engineers about this problem. If there is any useful information, I will share with you as soon as possible.
Sharon Zhao-MSFT 25,761 Reputation points Microsoft External Staff

2021-07-16T08:03:36.977+00:00

@Aemilianus Kehler ,
I get no related information about this problem now.
I will keep paying attention to this issue. Any update I will post here.
Thanks for your understanding.

Share via

Lync 2013 on Server 2016 meet now not working

1 answer

Your answer