At least one invalid authentication signature was detected. There were %2 messages with invalid signatures in the last %1 ...

At least one invalid authentication signature was detected.

There were %2 messages with invalid signatures in the last %1 minutes. The last one was this SIP message:

%3

Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.

At least one authentication challenge response could not be sent back to a client. There were %2 of these failures in the ... At least one Front End Server or pool must exist before the Mediation Server can be defined. Please define a Front End Server ... At least one Front End Server or pool must exist before the Trusted Applications Server can be defined. Please define a Front ... At least one Front End Server or pool must exist in the central site before a Survivable Branch Appliance can be defined. ... At least one invalid authentication signature was detected. There were %2 messages with invalid signatures in the last %1 ... At least one replayed message was detected. There were %2 replays in the last %1 minutes. The last one detected was this ... At the end of this wizard, information about your version 2007 or 2007 R2 topology will automatically be merged with your ... Attempt to create UserAgent or Server headers needed for sip messages failed. Check the version of the assembly to make sure ... Attempt to delete a stale address book file failed. Path: '%1' Exception: %2 Cause: Should not occur, as the Address Book ...