> -----Original Message----- > From: Laurentiu Ceausescu [mailto:[email protected]] > Sent: Monday, March 29, 2010 6:42 AM > > Beeton, Carolyn (Carolyn) wrote: > > It does look like a certificate problem. > > sipXconfig uses xmlrpc to do a lot of things via the > supervisor. Do these other things work on the secondary > server? (e.g. restart a service on the secondary box, > retrieve alarms from the secondary box, etc) > > > Yes ... I can restart any service on the secondary server, > except SIP Proxy which is in 'Configuration test failed' > state with the following error: > * SIP route to SIPXCHANGE_DOMAIN_NAME > 'toor.itcnetworks.ro' is not to my IP address: 11.126.12.16 > * See the installation guide on setting the DNS SRV > records and domain names > > Please note that in my configuration, the primary server is > 'toor.itcnetworks.ro' (11.126.12.10) and secondary server is > 'laurentiu.itcnetworks.ro' (11.126.12.16). > Also I can successfully use the Snapshot page (this page uses xmlrpc). > > > The secondary server should have the CA of the master > in /etc/sipxpbx/ssl/authorities. Does it (at the point that > reloadAlarms is called...)? > > Carolyn > > > I have this directory which contains master's certificate. > Thanks, > Laurentiu >
There is a command-line utility to reload alarms: sipx-alarm -h <remote server> --reloadAlarms Does this command (run from the config server) produce the same results? Run from the secondary server? Carolyn _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
