As found on Voip-info.org, a list of bandwidth consumption per codec.
It's worth mentioning that the table also indicates the total consumption including IP overhead. When making assumptions about bandwidth requirements, it is useful to take this overhead into account.
|G.711||64 Kbps||87.2 Kbps|
|G.729||8 Kbps||31.2 Kbps|
|G.723.1||6.4 Kbps||21.9 Kbps|
|G.723.1||5.3 Kbps||20.8 Kbps|
|G.726||32 Kbps||55.2 Kbps|
|G.726||24 Kbps||47.2 Kbps|
|G.728||16 Kbps||31.5 Kbps|
|iLBC||15 Kbps||27.7 Kbps|
You can easily verify whether an ADFS implementation is working by using a browser and trying to log on:
Replace adfs.yourdomain.com accordingly.
Note that in 2016, this no longer works unless you re-enable this feature through Powershell:
Set-AdfsProperties -EnableIdpInitiatedSignonPage $true
The RLM module may become unresponsive and you may see the following messages in the Syslog:
You can resolve the issue by rebooting the RLM from the CLI.
Log on using the CLI (SSH or console), then reboot the RLM.
CLI: rlm reboot
Wait for a while and verify the RLM is back online:
CLI: rlm status
The output of the command should report: Status: Online
I got this through the contact form. It's a jargon-free guide to computer and internet security. It provides a detailed explanation on how to properly secure your computer and internet experience, and best of all, it uses simple and understandable language, lowering the bar for everyone to secure themselves against malware, ransomware and other malicious attacks.
Although unsupported, it is possible to install Microsoft Security Essentials on a Windows Server 2012.
To do this, set the compatibility of the downloaded file to Windows 7, then start that file with the parameter /disableoslimit.
The installation goes without a problem, and as far as I can tell, there are no compatibility issues.