Asked by:
Skype 2015 pstn hybrid voice with O365. voice problem since last maintenance (KB3061064 + reboot)

Question
-
Hello,
i have a strange error.
since last update and reboot, i cannot complete call (mobile to O365 client only, the O365 to outside world work well)
the infrastructure is onprem skype 2015 with hybrid voice. all worked before.
when user are homed in O365 user can't hang on (establishing call), and the caller (the mobile) continue to ring (waiting for call)
when user are homed in onprem server, all is working.
all trace say the same think, there is a sip protocol problem.
the sip provider said that this probleme is a Skype problem
red trace is mobile to O365
green trace is mobile to onprem
could you help me to brainstorm with this case ? the cancel is a manualy cancel
- Edited by Olivier Chantraine Wednesday, April 18, 2018 2:49 PM
Wednesday, April 18, 2018 10:53 AM
All replies
-
O365 user receive call :
stuck in connecting call
Wednesday, April 18, 2018 12:57 PM -
Hi Olivier.be,
Based on your description, I understand that the users homed on Office 365 can’t make PSTN calls to others, right?
All users in Office 365 had the issue or specific user had the issue?
The issue is appeared after you install the KB 3061064?
Which product did you use for reverse proxy?
For this, please make sure you have correct configure for Lync PSTN hybrid, for details, please refer to the link below
https://docs.microsoft.com/en-us/skypeforbusiness/skype-for-business-hybrid-solutions/plan-your-phone-system-cloud-pbx-solution/plan-phone-system-with-on-premises-pstn-connectivityMoreover, you can collect logs on SFB edge server, check if there are any clues.
Best Regards,
Alice Wang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.Thursday, April 19, 2018 8:30 AM -
Hello,
all o365 users cant receive pstn call. but can make pstn call.
all my 3 tests users have this problem
the issue is appaered just after the KB installation. before, calls were functionnal
for reverse proxy, i use iis ARR.
perhaps the configuration lost something when the maintenance was done. but before, it was working.
then i fell the configuration is correct. (i followed the docs.miscrosoft as guide to do)
i will gather more log
thanks already
Olivier.
- Edited by Olivier Chantraine Thursday, April 19, 2018 12:13 PM
Thursday, April 19, 2018 12:13 PM -
Hi Olivier.be,
I notice this issue seems occur after you did an update. I suggest you could first check the Skype for Business CMS replication status to see if all is True. You could run this command: “Get-CsManagementStoreReplicationStatus” on Management Shell.
According your description, only incoming call to Online user has this issue, please check the Event Log on Edge and FE server side to see if there is any related information about the failed call.
You could also refer to the sip flow according the following article:
https://gallery.technet.microsoft.com/office/Skype-for-Business-SIP-4d16a292
Best Regards,
Alice Wang
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.- Proposed as answer by Alice-Wang Wednesday, April 25, 2018 8:58 AM
Tuesday, April 24, 2018 7:01 AM -
Hello,
all is fine with replication
the only one error i found is this one :
TL_INFO(TF_PROTOCOL) [srv\srv]33E8.266C::04/25/2018-09:50:44.037.000128ED (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [1072932342] Trace-Correlation-Id: 1072932342 Instance-Id: DA59 Direction: incoming Peer: srv.contoso.eu:5061 Message-Type: response Start-Line: SIP/2.0 481 Call Leg Does Not Exist From: "+3349999999"<sip:+3349999999@contoso.eu;user=phone>;epid=52BE9110F6;tag=7511f1bec9 To: <sip:++324999999@contoso.eu;user=phone>;tag=4ED186F84B168B5298C04B74445AF3F0 Call-ID: 357b564b-7d30-4cc1-81b1-13775725cc72 CSeq: 9613 CANCEL Via: SIP/2.0/TLS 10.10.0.3:57483;branch=z9hG4bK47E05143.68EA75559FD23BBC;branched=FALSE;ms-received-port=57483;ms-received-cid=A4B00 Content-Length: 0 ms-diagnostics: 2;reason="See response code and reason phrase";HRESULT="0xC3E93C09(PE_E_TRANSACTION_DOES_NOT_EXIST)";source="sipfed2E.online.lync.com";source-server="AM42E00EDG05.infra.lync.com" ms-split-domain-info: ms-traffic-type=SplitIntra;ms-remote-fqdn=sipfed.online.lync.com ms-telemetry-id: 035CDA59-8DE3-5403-941F-75CB96E9FE0E Server: RTC/7.0
Friday, April 27, 2018 9:57 AM -
(only if i call from mobile to O365 hybrid psnt, o365 homed user)
I uninstalled the KB, and rolled back server before kb installation.
and i still have the problem
this is strange, if i check de client, i saw the 200 Ok of the hank on:
in my mediation server, when i trace, i dont have this "200 ok" as this picture show it
no ok after 183 session progress.
if i call from my mobile to this o365 homed user, and when this user aren't loggued -> voice mail , and i receive 200 OK
- Edited by Olivier Chantraine Wednesday, May 2, 2018 8:35 AM
Wednesday, May 2, 2018 8:32 AM