Thomas.Poett@TEAMS (MVP Teams and Cross-Tenant Migration Specialist)

There is an issue cause confusion with the Lync Mobile Client behavior.   Let me give you a scenario: Assume a user is located in Munich: +49    Country Code Germany 89     Area Code Munich 314253 (main number) 554    (extension) Full number : +4989314253544   Munich Lync phone number: tel:.+4989314253544;ext=1544 (the 1 stands for Munich) New York Lync phone number: tel:.+16312455554;ext=2544 (the 2 stands for New York)   This number belongs to an internal Lync user and you have the normalization rules for this Munich location profile set as: normalizing to 3-digit ->       +4989314253$1 normalizing to 4-digit ->       cut 1 - +4989314253$1 normalizing to 4-digit ->       cut 2 - +16312455$1 normalizing to 9-digit ->       +4989$1 normalizing to 0+11-digit ...

There are three possible reasons why you can't send IM from Outlook Web Apps (OWA). I assume first, the integration was done according to the recommendations given. Meaning you have also tested that internal IM from OWA was possible to send and receive. If you encounter the following behavior: - Presence can be queried, but I’M cannot be initiated. - If you receive an external IM, you are able to answer the external contact. - You cannot receive or send external IM from OWA   While you are using the OCSLogger on the Lync Edge Server, you might see the following SIP 403 Forbidden message:   Text : SUBSCRIBE request for get rich presence was rejected by the Access Edge Server Result-Code : 0xc3e93d80 SIPPROXY_E_EPROUTING_MSG_INT_GET_RICH_PRESENCE_FILTERED You also see the internal Exchange Server with ipconfig -displaydns as: _sipfederationtls._tcp.sip-domain.com Solution: 1. Your external policy do not allow access to federated partner or public ...

Monitoring, a component in Lync which is most important. Not only collecting information about the servers and their services. Since here are users directly involved with their end devices, like phones, headset or computers. In between of those components sits the network and routing devices. Not enough here, mostly Lync or Skype for Business work in an environment where other voice solutions, e.g. PBX's or SIP Systems are running in parallel. During a migration for example, if you move users towards Enterprise Voice, the PBX and e.g. SIP Trunk Providers are in the loop for quite some time. This makes monitoring of the entire Voice solution essential. Lets see hat Lync and Skype for Business offers: Microsoft has introduced a two databases, the CDR and QoE database. Those are databases where Call Details are recorded and the entire environment quality data, like Server and service health, as well as the quality relevant information about call, either a P2P or Enterprise Voice...

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 ...