<div>Hi there...i got it...:) tnx for the assistance...I appreciate it.</div>
<div>Now i need to simulate some sip clients...:)</div>
<div> </div>
<div>cheers,</div>
<div> </div>
<div> </div>
<div>josel<br><br> </div>
<div><span class="gmail_quote">On 7/24/06, <b class="gmail_sendername">Andrey Kouprianov</b> <<a href="mailto:andrey.kouprianov@gmail.com">andrey.kouprianov@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Something like (50,13-14) means you have an error at line 50, at<br>character 13 to 14.<br><br>On 7/25/06, Josel Layno <
<a href="mailto:josel70ph@gmail.com">josel70ph@gmail.com</a>> wrote:<br>> Hi there again....I think i got fix some syntax error...typo errors...:)<br>><br>> But not this new error...:(<br>><br>> voip# ser start
<br>> 0(1684) ERROR: load_module: could not open module<br>> </usr/local/lib/ser/modules/nathelpher.so>: Cannot open<br>> "/usr/local/lib/ser/modules/nathelpher.so"<br>> 0(1684) parse error (50,13-14): failed to load module
<br>> 0(1684) set_mod_param_regex: No module matching nathelpher found<br>> | 0(1684) parse error (72,19-20): Can't set module parameter<br>> 0(1684) set_mod_param_regex: No module matching nathelpher found<br>
> | 0(1684) parse error (73,19-20): Can't set module parameter<br>> 0(1684) parse error (124,48-49): unknown command, missing loadmodule?<br>><br>> 0(1684) parse error (216,22-23): unknown command, missing loadmodule?
<br>><br>> 0(1684) parse error (242,21-22): unknown command, missing loadmodule?<br>><br>> ERROR: bad config file (6 errors)<br>><br>><br>> I have here my module directory...seems the nathelpher.so is
<br>> included...*thinking*<br>><br>> voip# pwd<br>> /usr/local/lib/ser/modules<br>> voip# ls -al<br>> total 1388<br>> drwxr-xr-x 2 root wheel 1024 Jul 24 13:30 .<br>> drwxr-xr-x 3 root wheel 512 Jul 24 13:30 ..
<br>> -r-xr-xr-x 1 root wheel 14584 Jul 24 13:30 acc.so<br>> -r-xr-xr-x 1 root wheel 23708 Jul 24 13:30 auth.so<br>> -r-xr-xr-x 1 root wheel 22512 Jul 24 13:30 auth_db.so<br>> -r-xr-xr-x 1 root wheel 37176 Jul 24 13:30 auth_diameter.so
<br>> -r-xr-xr-x 1 root wheel 18096 Jul 24 13:30 auth_radius.so<br>> -r-xr-xr-x 1 root wheel 9816 Jul 24 13:30 avp.so<br>> -r-xr-xr-x 1 root wheel 9860 Jul 24 13:30 avp_db.so<br>> -r-xr-xr-x 1 root wheel 11524 Jul 24 13:30 avp_radius.so
<br>> -r-xr-xr-x 1 root wheel 51700 Jul 24 13:30 avpops.so<br>> -r-xr-xr-x 1 root wheel 8228 Jul 24 13:30 check_ua.so<br>> -r-xr-xr-x 1 root wheel 48316 Jul 24 13:30 dbtext.so<br>> -r-xr-xr-x 1 root wheel 14188 Jul 24 13:30
dispatcher.so<br>> -r-xr-xr-x 1 root wheel 5824 Jul 24 13:30 diversion.so<br>> -r-xr-xr-x 1 root wheel 15832 Jul 24 13:30 domain.so<br>> -r-xr-xr-x 1 root wheel 14348 Jul 24 13:30 enum.so<br>> -r-xr-xr-x 1 root wheel 22292 Jul 24 13:30
exec.so<br>> -r-xr-xr-x 1 root wheel 13960 Jul 24 13:30 ext.so<br>> -r-xr-xr-x 1 root wheel 14184 Jul 24 13:30 flatstore.so<br>> -r-xr-xr-x 1 root wheel 7224 Jul 24 13:30 gflags.so<br>> -r-xr-xr-x 1 root wheel 10248 Jul 24 13:30
group.so<br>> -r-xr-xr-x 1 root wheel 11080 Jul 24 13:30 group_radius.so<br>> -r-xr-xr-x 1 root wheel 28012 Jul 24 13:30 mangler.so<br>> -r-xr-xr-x 1 root wheel 9748 Jul 24 13:30 maxfwd.so<br>> -r-xr-xr-x 1 root wheel 39844 Jul 24 13:30
mediaproxy.so<br>> -r-xr-xr-x 1 root wheel 30736 Jul 24 13:30 msilo.so<br>> -r-xr-xr-x 1 root wheel 33180 Jul 24 13:30 mysql.so<br>> -r-xr-xr-x 1 root wheel 72724 Jul 24 13:30 nathelper.so<br>> -r-xr-xr-x 1 root wheel 7508 Jul 24 13:30
options.so<br>> -r-xr-xr-x 1 root wheel 114452 Jul 24 13:30 pa.so<br>> -r-xr-xr-x 1 root wheel 21384 Jul 24 13:30 pdt.so<br>> -r-xr-xr-x 1 root wheel 43268 Jul 24 13:30 permissions.so<br>> -r-xr-xr-x 1 root wheel 22776 Jul 24 13:30
pike.so<br>> -r-xr-xr-x 1 root wheel 32520 Jul 24 13:30 postgres.so<br>> -r-xr-xr-x 1 root wheel 3960 Jul 24 13:30 print.so<br>> -r-xr-xr-x 1 root wheel 27688 Jul 24 13:30 registrar.so<br>> -r-xr-xr-x 1 root wheel 22980 Jul 24 13:30
rr.so<br>> -r-xr-xr-x 1 root wheel 15344 Jul 24 13:30 sl.so<br>> -r-xr-xr-x 1 root wheel 72068 Jul 24 13:30 sms.so<br>> -r-xr-xr-x 1 root wheel 9928 Jul 24 13:30 speeddial.so<br>> -r-xr-xr-x 1 root wheel 14076 Jul 24 13:30
textops.so<br>> -r-xr-xr-x 1 root wheel 213548 Jul 24 13:30 tm.so<br>> -r-xr-xr-x 1 root wheel 10784 Jul 24 13:30 uri.so<br>> -r-xr-xr-x 1 root wheel 12968 Jul 24 13:30 uri_db.so<br>> -r-xr-xr-x 1 root wheel 8648 Jul 24 13:30 uri_radius.so
<br>> -r-xr-xr-x 1 root wheel 69340 Jul 24 13:30 usrloc.so<br>> -r-xr-xr-x 1 root wheel 19976 Jul 24 13:30 xlog.so<br>><br>> Is there something to do with ownership/permission..etc? Mediaproxy is<br>> runnig on boot. Btw, i did install SER
0.9.6 using FreeBSD ports.<br>><br>> I hope u can help me with this. tia.<br>><br>> cheers,<br>><br>><br>> josel<br>><br>><br>> On 7/24/06, <a href="mailto:openser@comcast.net">openser@comcast.net
</a> < <a href="mailto:openser@comcast.net">openser@comcast.net</a>> wrote:<br>> ><br>> > Is mysqld started, if not the way to start it in Fedora 4 is /sbin/service<br>> mysqld start<br>> ><br>> >
<br>> > -------------- Original message ----------------------<br>> > From: "Josel Layno" <<a href="mailto:josel70ph@gmail.com">josel70ph@gmail.com</a>><br>> > > ><br>> > > >
<br>> > > ><br>> > ><br>> > > I got to install SER 0.9.6 with Mysql on FreeBSD. But i got some parse<br>> > > error.<br>> > > How can i trace to find the error on my config file?
<br>> > ><br>> > > voip# ser start<br>> > > 0(940) parse error (163,25-35): syntax error<br>> > > 0(940) parse error (163,101-102): bad arguments<br>> > > 0(940) parse error (174,10-11): syntax error
<br>> > > 0(940) parse error (174,10-11): invalid operator, == , != or =~<br>> expected<br>> > > ERROR: bad config file (4 errors)<br>> > ><br>> > > Sorry for my ignorance...what's the relevance of (163,25-35) in
ser.cfg?<br>> > ><br>> > ><br>> > > cheers,<br>> > ><br>> > > josel<br>> ><br>> ><br>> ><br>> ><br>> ><br>> ><br>><br>><br>> ---------- Forwarded message ----------
<br>> From: "Josel Layno" <<a href="mailto:josel70ph@gmail.com">josel70ph@gmail.com</a>><br>> To: <a href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>> Date: Mon, 24 Jul 2006 18:48:14 +0000
<br>> Subject: [Serusers] Problem starting SER 0.9.6 with MYSQL on FreeBSD<br>><br>> ><br>> ><br>><br>> I got to install SER 0.9.6 with Mysql on FreeBSD. But i got some parse<br>> error.<br>> How can i trace to find the error on my config file?
<br>><br>> voip# ser start<br>> 0(940) parse error (163,25-35): syntax error<br>> 0(940) parse error (163,101-102): bad arguments<br>> 0(940) parse error (174,10-11): syntax error<br>> 0(940) parse error (174,10-11): invalid operator, == , != or =~ expected
<br>> ERROR: bad config file (4 errors)<br>><br>> Sorry for my ignorance...what's the relevance of (163,25-35) in ser.cfg?<br>><br>><br>> cheers,<br>><br>> josel<br>><br>><br>> _______________________________________________
<br>> Serusers mailing list<br>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>> <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers
</a><br>><br>><br>><br>><br>> _______________________________________________<br>> Serusers mailing list<br>> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a><br>> <a href="http://lists.iptel.org/mailman/listinfo/serusers">
http://lists.iptel.org/mailman/listinfo/serusers</a><br>><br>><br>><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org
</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>