<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Run Your Own SIP Server, Today!</title>
	<link>http://www.jeremy-mcnamara.com/2007/07/21/run-your-own-sip-server-today/</link>
	<description>VoIP, Asterisk and OpenSER: News, Information and Tutorials</description>
	<pubDate>Fri, 21 Nov 2008 13:08:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: jj</title>
		<link>http://www.jeremy-mcnamara.com/2007/07/21/run-your-own-sip-server-today/#comment-1623</link>
		<dc:creator>jj</dc:creator>
		<pubDate>Fri, 14 Dec 2007 17:14:20 +0000</pubDate>
		<guid>http://www.jeremy-mcnamara.com/2007/07/21/run-your-own-sip-server-today/#comment-1623</guid>
		<description>Mike: I don't use the stock init script for openser.  I use my own init script that does more than just fire up openser.

What version of OpenSER are you running?  My configurations here are geared for v1.1.1 and most likely will NOT work with newer versions.

You can look in your syslog to find a cryptic, but generally helpful message detailing the error.  (most likely /var/log/syslog or /var/log/messages, depending on your distro) 

Another option is to set:

fork = no
log_stderror = yes

...and start openser manually in your bash shell.  You can control the verbosity using:

debug = 3  

...higher numbers will result in more spewage. 

HTH</description>
		<content:encoded><![CDATA[<p>Mike: I don&#8217;t use the stock init script for openser.  I use my own init script that does more than just fire up openser.</p>
<p>What version of OpenSER are you running?  My configurations here are geared for v1.1.1 and most likely will NOT work with newer versions.</p>
<p>You can look in your syslog to find a cryptic, but generally helpful message detailing the error.  (most likely /var/log/syslog or /var/log/messages, depending on your distro) </p>
<p>Another option is to set:</p>
<p>fork = no<br />
log_stderror = yes</p>
<p>&#8230;and start openser manually in your bash shell.  You can control the verbosity using:</p>
<p>debug = 3  </p>
<p>&#8230;higher numbers will result in more spewage. </p>
<p>HTH</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike_white</title>
		<link>http://www.jeremy-mcnamara.com/2007/07/21/run-your-own-sip-server-today/#comment-1603</link>
		<dc:creator>mike_white</dc:creator>
		<pubDate>Wed, 12 Dec 2007 16:49:35 +0000</pubDate>
		<guid>http://www.jeremy-mcnamara.com/2007/07/21/run-your-own-sip-server-today/#comment-1603</guid>
		<description>Hey - First off thanks for making such a great resource for openser. 

I've installed and set everything up per your cfg but I'm getting a bad config msg when trying to start ser with /etc/init.d/openser start 

originally, the error message showed 11 errors in the code - Which I've wittled down to three.  The username/pass for mysql dbs were wrong and I fixed them. 

Any ideas?</description>
		<content:encoded><![CDATA[<p>Hey - First off thanks for making such a great resource for openser. </p>
<p>I&#8217;ve installed and set everything up per your cfg but I&#8217;m getting a bad config msg when trying to start ser with /etc/init.d/openser start </p>
<p>originally, the error message showed 11 errors in the code - Which I&#8217;ve wittled down to three.  The username/pass for mysql dbs were wrong and I fixed them. </p>
<p>Any ideas?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
