Today I have a very appetizing mushroom. Perhaps you have had at anytime a problem with your Skype to Skype for Business integration.
I describe the problem:
Some users advise you that they can contact with Skype users, but Skype users can’t view presence and doesn’t have chat with Skype for business users, for example:
If you have tested your deployment, and you followed all steps from Technet guidance: https://technet.microsoft.com/en-us/library/dn705313.aspx
Also you checked your firewall and everything is allowed. Keep calm, you are not crazy. Your environment are correctly configured, but you have some users that are using Lync 2013 (With or without skype for business interface). Please, follow next steps to solve your issue.
Check if your users with those clients have next configuration:
If not, please apply it and try again.
Open your client options and go to ‘alerts’. On ‘contacts not using Skype for Business’ menu, check ‘allow anyone to contact me’. The problem will be resolved.
I hope this information will be useful for you.
When you restart your Audiocodes Gateway, your users change their status to “Limited features”?
Have you ever asked yourself why you lost connectivity with your SBA when you reboot your Audiocodes Gateway?
Here is the answer:
If you have an Audiocodes Mediant as SBA, you know that it is necessary to use the WebGui to configure it (This is Awful!). Deployment Wizard can’t be used, because Audiocodes SBAs doesn’t have bootstrapper.exe and Deployment Wizard doesn’t work.
As you know, Audiocodes Mediant have many modules. It have a Gateway module, an OSN module (for Operating System) and also it have a little switch module, this module is internal and it isn’t available to configure (as far as I know).
Well, known this. On WebGui for the SBA configuration. We will asked for IP Settings. In this moment, we can select one of the four network interfaces of the Audiocodes OSN Module: two internal interfaces and two external interfaces.
THIS IS VERY IMPORTANT! You can choose anyone, but if you choose one of the internal interfaces, you are choosing an interface that it is connected directly with the internal little switch. So if you need to restart the gateway module (for any reason), you also restart the little switch, so you will lose connectivity with your SBA and your users will enter on survival mode.
If you have two core network ports to connect both modules (Gateway and OSN), always choose external network interface, in this way you will have the two modules separated for modifies, troubleshooting or any other thing that you need.
If you have only the possibility of a core network port, and you need to use internal interface, you will remember that if you make changes on the gateway that requires restart, you will lose connectivity with your SBA and you users show the message and they will have limited features while the gateway is restarting.
I hope this information will be useful