On Tue, 2009-08-25 at 10:51 +0530, Shobha wrote: > Hi All, > > This is regarding "Process failed configuration test" alarm type. > Right now Iam able to generate the above alarm type for only > 'SipXproxy' service. > > Steps followed to test: > 1.Navigate to System > Servers >earth.qantom.int > NAT. > 2.Changed the NAT Public port address, 5060 to some invalid port > number and restarted the services which asks for restart. > > Result: > 1. sipxproc shows, > "SIPXProxy"=>"ConfigurationTestFailed" > 2.Config UI also shows, > "SIP Proxy"=>"Configuration test failed" > 3.Alarm notification was generated for the alarm type. > > But Iam not able to generate the same alarm type for other services. > Please suggest me the steps to reproduce the "Process failed > configuration test" alarm type for at least 'SIP Registrar' and > 'SipXbridge' services.
Looking at the registrar test, it appears that if you configure an HA system and then remove the 'rr.*' records from the DNS, it should fail configtest for the registrar (I have not tried this). _______________________________________________ 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/
