On Wed, 2010-04-21 at 11:30 +1000, Graeme Allen wrote: > > Some further information: > > I got SipX to start, by changing /etc/init.d/sipxpbx
All that you did was disable the test that was designed to keep you from hitting the problems you're hitting now. As Josh said in another post, 4.2 has a way to load a certificate for use by the web interface, and that certificate can be a wildcard. Even when you do this, the system still uses its own fully qualified certificate for SIP (using a wildcard cert is not valid for SIP) and the secure messaging between services. I suggest that you revert to your original certificate, then upgrade to 4.2 and use the web ui to install the wildcard web cert. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
