SIP Sorcery's Blog
Subscribe to feed
‹ Dial Plan Script Processing Problem (aka as: Long running dialplan script was terminated) • App Server Unresponsive ›
July 16, 2009 in source | 5 comments
I’ve just uploaded a v1.0 release of sipsorcery that’s designed for local installs. The release is available at sipsorcery v1.0.
Comments feed for this article
Trackback link: http://blog.sipsorcery.com/wp-trackback.php?p=33
destinycan on July 16, 2009 at 2:17 pm
Thank you thank you thank you.
destinycan on July 16, 2009 at 4:16 pm
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 System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
destinycan on July 16, 2009 at 4:55 pm
This is the error from log file:
2009-07-16 10:54:21,672  DEBUG sipsporcery-app [(null)] – pid=412.
2009-07-16 10:54:21,672  DEBUG sipsporcery-app [(null)] – os=Microsoft Windows NT 5.2.3790 Service Pack 2.
2009-07-16 10:54:21,672  DEBUG sipsporcery-app [(null)] – current directory=C:tempsipsorcery.
2009-07-16 10:54:21,719  DEBUG sipsorcery [(null)] – 3 SIPSorcery.SIP.App.SIPAccount assets loaded from XML record set.
2009-07-16 10:54:21,719  DEBUG sipsorcery [(null)] – Starting file watch on C:Tempsipsorceryxmlconfig and sipaccounts.xml.
2009-07-16 10:54:21,719  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.
sipsorcery on July 16, 2009 at 11:50 pm
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.
destinycan on July 16, 2009 at 8:30 pm
Using database (MySQL) works perfectttt!!!
Your email address will not be published. Required fields are marked *
Powered by WordPress and Tarski