Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant M&A/D Migration Expert Lead)

This should be just used as basic approach on how you can support busy on busy. First you can check if the new APPLICATION was installed correctly: The newly created appliance will be loaded during the Frontend server startup procedure and you will be able seeing a not in Event 30253 , indicating the application was included in the loading process. Next important, not to say most important tool ist LOGGING TOOL : Here you will find a pre-defined set towards busy on busy. Generally busy on busy messages look like this example below: Content-Length: 0 Via: SIP/2.0/TLS 192.168.0.13:49887;received=103.12.145.113;ms-received-port=41538;ms-received-cid=9F6B100 From: "User1"<sip:user1@westconlab.com>;tag=8ea09bf2e6;epid=2983f4c267 To: <sip:user2@westconlab.com>;tag=C643D58961F545B Call-ID: 734ea4e359617902c2098433b CSeq: 1 INVITE Server: BusyOptions/6.0.0.0 ms-diagnostics:    1034;reason="Previous hop federated peer did not re...

The free eBook is about troubleshooting Skype for Business and Lync. A complex solution in unified communication marking people's life more simpler, connecting to óther at any point of time, staying in contact with fellow friends and family members. Developing a set of skills, supporting and analyzing issues in this environment is an advanced task. I describe the troubleshooting work flow from general understanding of Skype for Business and Lync Server and Services. In the Troublehsooting Guide the following areas are covered: - General Approach to troubleshooting - Logging, Tracing and CLS - TCP and SIP Protocol - SIP Session Establishment - Lync/ Skype for Business Call Setup (entire process) - Troubleshooting IM - Troubleshooting Call with A/V - Diagnostic Headers - Monitoring - Troubleshooting Voice - Troubleshooting Conferencing - Troubleshooting Web Services - Troubleshooting Edge (external/ remote) - Health Monitoing - Troubleshooting Exchange Intergation ...