Password with Special character

[Roy Reynolds]

Hi all,

I made the mistake of using a password that the service provider sent for their sip trunk.  It has special characters  of & included.  I removed the gateway after realizing that but now th siptrunk service, sipxbridge will not restart.  I  looked in the logs and it said Fatal error and caught an exception.  See the extract from the log:

"SipXbridge : Fatal error caught "
org.sipfoundry.sipxbridge.SipXbridgeException: Initialization exception
at org.sipfoundry.sipxbridge.ConfigurationParser.createAccountManager(ConfigurationParser.java:333)
at org.sipfoundry.sipxbridge.Gateway.parseConfigurationFile(Gateway.java:240)
at org.sipfoundry.sipxbridge.Gateway.main(Gateway.java:1247)
Caused by: org.xml.sax.SAXParseException; systemId: file:///etc/sipxpbx/sipxbridge.xml; lineNumber: 61; columnNumber: 24; The reference to entity "Q2" must end with the ';' delimiter.

I don't have the latest backup from the PBX and was wondering if editing the file and finding the incorrect password, removing it then restarting the services would bet me back up.

I appreciate any suggestions.

Best Regards,

[Roy Reynolds]

I figured out the issue.  the file that actually had the incorrect password was /etc/sipxpbx/sipxbridge.xml.cfsaved.  I edited and removed the special character and the sipxbridge service started up successfully.

I noticed that the sipxlogwatcher service failed and it stated that it was already running.  What log do I look in to find out why?

Best Regards,

[OnRelay Support]

Hello Roy,

See https://github.com/onrelay/sipxecs/issues/22.

Thank you.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/2f0da907-5017-4dd7-b01f-7e7259dc5fb3n%40googlegroups.com.

[Roy Reynolds]

Thank you for sharing the information. 

I clicked on the link and saw this in the report:  Fix error in startup script checking for sec instead of /usr/bin/sec process executable

What do I do to fix the problem? 

What startup script is it referring to and where do I find it?

Thanks in advance.

[Support]

Hello,

Here is the corresponding change: https://github.com/onrelay/sipxecs/commit/0f6ed619c4b18b8ef2fab251e5c1c897c2d2a56d

Would strongly recommend you upgrade to 24.01 since there were a lot of changes to sipXbridge as well.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/CALz8TxnZ%3D%2BfOB22aQpXCiFRPpduh3mbeg-E-gsWWe0n-b0CSLw%40mail.gmail.com.

[Roy Reynolds]

Thank you for your response.  I checked the file and made the edits and the service is running again.  I will schedule an  upgrade release 24.0.1 as you suggested.  Just to be sure, Can I backup the configuration and voicemail and import it once the upgrade is done?

Thanks.

[Support]

Hello Roy,

You can upgrade an existing  21.04 installation to 24.01 following these simple instructions: https://onrelay.github.io/sipxecs/upgrading.html