v1.0 release

I’ve just uploaded a v1.0 release of sipsorcery that’s designed for local installs. The release is available at sipsorcery v1.0.

  1. destinycan’s avatar

    Thank you thank you thank you.

    Reply

  2. destinycan’s avatar

    Hi Aaron,

    First time it runs perfect, but when I restart the service, it gives this error:

    Unhandled Exception: System.Xml.XmlException: The ‘lastupdate’ start tag on line
    15 does not match the end tag of ‘lastudpate’. Line 15, position 47.
    at SIPSorcery.SIPAppServer.SIPAppServerDaemon.Start()
    at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
    ontextCallback callback, Object state)
    at System.Threading.ThreadHelper.ThreadStart()

    Please help

    Reply

    1. destinycan’s avatar

      This is the error from log file:
      2009-07-16 10:54:21,672 [5] DEBUG sipsporcery-app [(null)] – pid=412.
      2009-07-16 10:54:21,672 [5] DEBUG sipsporcery-app [(null)] – os=Microsoft Windows NT 5.2.3790 Service Pack 2.
      2009-07-16 10:54:21,672 [5] DEBUG sipsporcery-app [(null)] – current directory=C:tempsipsorcery.
      2009-07-16 10:54:21,719 [5] DEBUG sipsorcery [(null)] – 3 SIPSorcery.SIP.App.SIPAccount assets loaded from XML record set.
      2009-07-16 10:54:21,719 [5] DEBUG sipsorcery [(null)] – Starting file watch on C:Tempsipsorceryxmlconfig and sipaccounts.xml.
      2009-07-16 10:54:21,719 [5] ERROR sipsporcery-app [(null)] – Exception SIPAppServerDaemon Start. The ‘lastupdate’ start tag on line 15 does not match the end tag of ‘lastudpate’. Line 15, position 47.

      Reply

      1. sipsorcery’s avatar

        The benefit of using XML files is that they are great for testing as you can edit and add to them using a text editor like notepad. The downside is that it’s a file system solution for a database job. In your case it looks like you killed the process at the same time it was writing an update to sipaccounts.xml. If you open that file it should be apparent where the malformed XML is.

        Basically the story is if you want to get up and running quickly and try a few things out then the XML config is the way to go. If you need to cope with multiple users or higher volumes of calls or regsitrations you need to swith to MySQL or Postgresql instead.

        Reply

      2. destinycan’s avatar

        Using database (MySQL) works perfectttt!!!

        Reply

Reply

Your email address will not be published. Required fields are marked *