Currently, if sipXproxy cannot read forwardingrules.xml, it logs a message but continues processing. Unfortunately, the forwardingRules object that encapsulates the information in the file then contains a null pointer, so sipXproxy crashes the first time it would need the information in the file to forward a message.
My inclinationfor how to handle this situation is for sipXproxy to log a CRIT message and exit(1). Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
