In 3.1 this was resolved with SP5... Not sure which version you're experiencing this on, but the fix below could solve your issue.
From Avaya: The notify me failure of this week has been temporary resolved. The Engineer has identified the problem and it has been addressed in our latest Service Pack. The MAS server reverted the list of server names in the registry to not have the callme server listed first (which also handles notify).
Thanks,
98C
We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.