iOS 9 is here! And like most iPhone owners I downloaded iOS 9 yesterday and installed it. If you or your Lync users haven’t done this already you might be in for an unpleasant surprise.
After the install was done I launched Lync and and hit the sign in button. I was greeted with the following error mesage.
After doing all the normal troubleshooting I still couldn’t find the reason for the error.
Thanks to Guy Bachar’s post I first of all realized that I wasn’t alone in having this issue. Turns our that for some reason; if your regional setting on iPhone doesn’t match your iPhone language you can’t sign in to Lync if you are on iOS 9.
This worked fine in iOS 8 and to me it’s really frustrating. I prefer to have my regional settings set to Swedish to get date, currency and all that in…
View original post 132 more words
“The odd call drops” of the Mediation ServerStandardI had a very annoying issue lately when an installation of a new gateway resolved in some calls (specifically to US numbers) dropped by the Skype for Business mediation server saying “A call to a PSTN number failed due to non availability of gateways.”The cause, according to the mediation server, was that “All gateways available for this call are marked as down“, and the resolution, surprisingly, was to “Verify that these gateways are up and can respond to calls.”It seemed funny, because all other calls were successful, I have not exhausted the available PRI channels I had, the gateway didn’t seem to lose connectivity for a split second and SIP options are accepted and replied to on both ends.Looking further at the Lync Monitoring Reports, I noticed the following:Reported by Client12000; reason=”Routes available for this request but no available gateway at this point”Reported by Server12000; reason=”Routes available for this request but no available gateway at this point”I went to the gateway (AudioCodes M1000B) for answers and the logs were showing something very weird;Every call starts with the same flow:Flow1The mediation server sends a SIP Invite that will normally be answered immediately by the gateway with a “100 Trying”. This, for me, will close the deal on the “Gateway no responding” – this is a great response if you ask me.The next phase would be the gateway immediately sending a “PSTN Place call” to the PSTN, hopefully receiving a “Proceeding” instantly from the PSTN, meaning so far we’re fully communicating. So for the time being I’m not really buying what the Lync mediation server is selling.Looking further at the logs, I see the following strange behaviour:As I’m still waiting for the PSTN to connect the call (this would normally be a “PSTN Call Alerting” message), I see that the mediation server decided to abandon ship!This is what I see in the logs:WrongWithin 10 seconds after initiating the call, the mediation server will send a “Cancel” request to the gateway and will terminate the call:19:25:49.640 [S=660986] [SID:1327438938] INVITE sip: firstname.lastname@example.org;user=phone SIP/2.0 19:25:49.729 [S=661027] [SID:1327438938] SIP/2.0 100 Trying 19:25:49.730 [S=661035] [SID:1327438938] ( lgr_psbrdif)( 656225) pstn send –> PlaceCall19:25:50.087 [S=661039] [SID:1327438479] ( lgr_psbrdex)( 656229) pstn recv PSTNDisconnectCallClearly, the gateway is available and responding, but the mediation server is somewhat impatient.Doing a bit of digging around, it appears there’s a setting for this.
The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.
Here’s an excerpt:
A San Francisco cable car holds 60 people. This blog was viewed about 1,700 times in 2015. If it were a cable car, it would take about 28 trips to carry that many people.
Source: Skype for Business VCFG Viewer