I have seen several cases in both a larger 4.4.0 deployment and a small 4.4.0 lab deployment where the registrar fails. When it fails there is no alarm sent, and unless you look under services you will not see the indication it is not running (no jobs failed, but makes me think that an alarm indicator that you have to clear at login might be in order along with a server status traffic light for each server used in the sipdomain.
In any event, clicking details says no details are available. It seems to happen much more frequently in a larger environment. Weeks on a smaller one, days or hours on a larger one. I tried to push through some logs to see what the issue was (no internet or real sip connectivity, so sipvicious or external forces are not something to look at here), but saw nothing to follow. In trying to determine part of this issue, I tried to pull in the sipxrls/commserverlib/sipxconfig packages from the build repo. When I did that the registrar failed and STAYED failed (rest using a stable 4.4.0 repo). If RLS is "not" responsible for the registrar failing, what changes were made to sipxconfig or sipxcommserverlib that would? -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.326.5325 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Contract Customers: http://support.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
