Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to: 1) remove "fifo=/tmp/openser_fifo" from your config 2) load the mi_fifo module 3) configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Bogdan!
I have problems with the new fifo:
root@pb94:/usr/sbin# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments
although the user is registered: root@pb94:/usr/sbin# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3539 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 1 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951
Is it a bug or am I doing something wrong?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Klaus,
difficult to say as it works for me:
root@test:scripts$ openserctl ul show user3@192.168.2.7 Contact:: sip:user3@192.168.2.7:5062;transport=udp;q=1;expires=410;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2> Contact:: sip:user3@192.168.2.7:5062;transport=tcp;q=1;expires=375;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
try to update and see if you have any differences against the CVS head
BTW, this remained me to add the cflags (per branch flags) in the MI usrloc responses.
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I have problems with the new fifo:
root@pb94:/usr/sbin# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments
although the user is registered: root@pb94:/usr/sbin# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3539 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 1 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951
Is it a bug or am I doing something wrong?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Bogdan!
I just made a fresh checkout, made the debian packages (packaging/debian-sarge) and installed them. Still the same problem:
root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:enum-test@sip.nemox.net Q= Expires:: 1048 Callid:: 335426696@213.239.207.29 Cseq:: 1 User-agent:: sipsak 0.9.6 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: tcp:213.239.207.29:6060 Methods:: 0 Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3224 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 2 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951 root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments root@pb94:/home/darilion/software/openser-cvs-clean#
The logs are:
openser[15438]: DEBUG:mi_fifo:mi_fifo_server: entered consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: **** done consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
openser[15438]: DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val klaus@pernau.at openser[15438]: DEBUG:mi_fifo:mi_parse_tree: end of input tree openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
any hints where the problem can be?
regards klaus
Bogdan-Andrei Iancu wrote:
Klaus,
difficult to say as it works for me:
root@test:scripts$ openserctl ul show user3@192.168.2.7 Contact:: sip:user3@192.168.2.7:5062;transport=udp;q=1;expires=410;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
Contact:: sip:user3@192.168.2.7:5062;transport=tcp;q=1;expires=375;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
try to update and see if you have any differences against the CVS head
BTW, this remained me to add the cflags (per branch flags) in the MI usrloc responses.
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I have problems with the new fifo:
root@pb94:/usr/sbin# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments
although the user is registered: root@pb94:/usr/sbin# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3539 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 1 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951
Is it a bug or am I doing something wrong?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See: http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Klaus,
it looks like the openserctl is not sending both parameter for the MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location> 0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val user3@192.168.2.7 0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree 0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not wrong, the name of the location table is defined in the DB section of openserctl.....so you need to use a DB engine ....
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I just made a fresh checkout, made the debian packages (packaging/debian-sarge) and installed them. Still the same problem:
root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:enum-test@sip.nemox.net Q= Expires:: 1048 Callid:: 335426696@213.239.207.29 Cseq:: 1 User-agent:: sipsak 0.9.6 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: tcp:213.239.207.29:6060 Methods:: 0 Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3224 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 2 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951 root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments root@pb94:/home/darilion/software/openser-cvs-clean#
The logs are:
openser[15438]: DEBUG:mi_fifo:mi_fifo_server: entered consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: **** done consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
openser[15438]: DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val klaus@pernau.at openser[15438]: DEBUG:mi_fifo:mi_parse_tree: end of input tree openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
any hints where the problem can be?
regards klaus
Bogdan-Andrei Iancu wrote:
Klaus,
difficult to say as it works for me:
root@test:scripts$ openserctl ul show user3@192.168.2.7 Contact:: sip:user3@192.168.2.7:5062;transport=udp;q=1;expires=410;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
Contact:: sip:user3@192.168.2.7:5062;transport=tcp;q=1;expires=375;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
try to update and see if you have any differences against the CVS head
BTW, this remained me to add the cflags (per branch flags) in the MI usrloc responses.
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I have problems with the new fifo:
root@pb94:/usr/sbin# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments
although the user is registered: root@pb94:/usr/sbin# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3539 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 1 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951
Is it a bug or am I doing something wrong?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
Hi everybody,
the old fifo implementation (from core) was removed and replaced by the MI FIFO module. See http://www.openser.org/docs/modules/1.2.x/mi_fifo.html
why? See:
http://www.openser.org/pipermail/users/2006-December/008154.html
To maintain the previous FIFO behaviour, you just have to:
- remove "fifo=/tmp/openser_fifo" from your config
- load the mi_fifo module
- configure modparam("mi_fifo", "fifo_name",
"/tmp/openser_fifo")
that's all :)
for an working example, see the default openser.cfg which was already updated:
http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi...
regards, bogdan
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Bogdan-Andrei Iancu wrote:
Klaus,
it looks like the openserctl is not sending both parameter for the MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location> 0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val user3@192.168.2.7 0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree 0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not wrong, the name of the location table is defined in the DB section of openserctl.....so you need to use a DB engine ....
Although the communication between openserctl and openser is via FIFO I have to define the DBENGINE? Why? I would the dumping the location table should be done from cache thus not needing and DB operation.
regards klaus
regards klaus
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I just made a fresh checkout, made the debian packages (packaging/debian-sarge) and installed them. Still the same problem:
root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:enum-test@sip.nemox.net Q= Expires:: 1048 Callid:: 335426696@213.239.207.29 Cseq:: 1 User-agent:: sipsak 0.9.6 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: tcp:213.239.207.29:6060 Methods:: 0 Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3224 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 2 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Cflag:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951 root@pb94:/home/darilion/software/openser-cvs-clean# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments root@pb94:/home/darilion/software/openser-cvs-clean#
The logs are:
openser[15438]: DEBUG:mi_fifo:mi_fifo_server: entered consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: **** done consume openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
openser[15438]: DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val klaus@pernau.at openser[15438]: DEBUG:mi_fifo:mi_parse_tree: end of input tree openser[15438]: DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
any hints where the problem can be?
regards klaus
Bogdan-Andrei Iancu wrote:
Klaus,
difficult to say as it works for me:
root@test:scripts$ openserctl ul show user3@192.168.2.7 Contact:: sip:user3@192.168.2.7:5062;transport=udp;q=1;expires=410;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
Contact:: sip:user3@192.168.2.7:5062;transport=tcp;q=1;expires=375;flags=0x0;socket=udp:192.168.2.7:5060;methods=0x173F;user_agent=<kphone/4.2>
try to update and see if you have any differences against the CVS head
BTW, this remained me to add the cflags (per branch flags) in the MI usrloc responses.
regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I have problems with the new fifo:
root@pb94:/usr/sbin# openserctl ul show klaus@pernau.at WARNING: no database engine found - tried '' 400 Too few or too many arguments
although the user is registered: root@pb94:/usr/sbin# openserctl ul show WARNING: no database engine found - tried '' Dumping all contacts may take long: are you sure you want to proceed? [Y|N] y Domain:: location table=512 records=1 max_slot=1 AOR:: klaus@pernau.at Contact:: sip:klaus@83.136.33.3:61174;rinstance=b1f1648bbed1e0fb;transport=udp Q= Expires:: 3539 Callid:: N2VhN2I0OGI3NmU4N2I0ZTY1ZTE1YjY0MjY2OWRmN2U. Cseq:: 1 User-agent:: eyeBeam release 1008m stamp 36652 State:: CS_SYNC Flags:: 0 Socket:: udp:213.239.207.29:6060 Methods:: 5951
Is it a bug or am I doing something wrong?
regards klaus
Bogdan-Andrei Iancu wrote:
Hi Klaus,
yes, it make sense - I fixed the docs on cvs and web site.
thanks and regards, bogdan
Klaus Darilion wrote:
Hi Bogdan!
I suggest to use the default value "/tmp/openser_fifo" also in the example:
http://www.openser.org/docs/modules/1.2.x/mi_fifo.html#AEN80
regards klaus
Bogdan-Andrei Iancu wrote:
> Hi everybody, > > the old fifo implementation (from core) was removed and replaced > by the MI FIFO module. See > http://www.openser.org/docs/modules/1.2.x/mi_fifo.html > > why? See: > > http://www.openser.org/pipermail/users/2006-December/008154.html > > To maintain the previous FIFO behaviour, you just have to: > 1) remove "fifo=/tmp/openser_fifo" from your config > 2) load the mi_fifo module > 3) configure modparam("mi_fifo", "fifo_name", > "/tmp/openser_fifo") > > that's all :) > > for an working example, see the default openser.cfg which was > already updated: > > http://openser.cvs.sourceforge.net/openser/sip-server/etc/openser.cfg?revisi... > > > > regards, > bogdan > > _______________________________________________ > Devel mailing list > Devel@openser.org > http://openser.org/cgi-bin/mailman/listinfo/devel
well... :)....even if it is a operation bouncing to cache (with no DB implication), you need to know the name of location table, to be able to search through cache....Like: search in "location" array for the "xxx" AOR... and the name of the location table is defined in the SQL section of openserctl .....as it is related to DB...
in this case, it is not possible to do a strict separation between DB and cache as the cache follows the structure and naming of the DB...
regards, bogdan
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Klaus,
it looks like the openserctl is not sending both parameter for the MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location> 0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val user3@192.168.2.7 0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree 0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not wrong, the name of the location table is defined in the DB section of openserctl.....so you need to use a DB engine ....
Although the communication between openserctl and openser is via FIFO I have to define the DBENGINE? Why? I would the dumping the location table should be done from cache thus not needing and DB operation.
Thus, people which have not installed any DB module can use the lookup?
regards klaus
Bogdan-Andrei Iancu wrote:
well... :)....even if it is a operation bouncing to cache (with no DB implication), you need to know the name of location table, to be able to search through cache....Like: search in "location" array for the "xxx" AOR... and the name of the location table is defined in the SQL section of openserctl .....as it is related to DB...
in this case, it is not possible to do a strict separation between DB and cache as the cache follows the structure and naming of the DB...
regards, bogdan
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Klaus,
it looks like the openserctl is not sending both parameter for the MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location> 0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val user3@192.168.2.7 0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree 0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not wrong, the name of the location table is defined in the DB section of openserctl.....so you need to use a DB engine ....
Although the communication between openserctl and openser is via FIFO I have to define the DBENGINE? Why? I would the dumping the location table should be done from cache thus not needing and DB operation.
not at all - you just need (at the moment) to configure DB support in openserctl (just do DBENGINE="MYSQL"). This does not require any installation or what ever ...it just forces the inclusion of the file with DB definition.
probably moving the def of this table to a not-DB related location will be a good fix.
regards, bogdan
Klaus Darilion wrote:
Thus, people which have not installed any DB module can use the lookup?
regards klaus
Bogdan-Andrei Iancu wrote:
well... :)....even if it is a operation bouncing to cache (with no DB implication), you need to know the name of location table, to be able to search through cache....Like: search in "location" array for the "xxx" AOR... and the name of the location table is defined in the SQL section of openserctl .....as it is related to DB...
in this case, it is not possible to do a strict separation between DB and cache as the cache follows the structure and naming of the DB...
regards, bogdan
Klaus Darilion wrote:
Bogdan-Andrei Iancu wrote:
Klaus,
it looks like the openserctl is not sending both parameter for the MI call - the table name and the AOR. It should be like:
0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val <location> 0(5292) DEBUG:mi_fifo:mi_parse_tree: adding node <> ; val user3@192.168.2.7 0(5292) DEBUG:mi_fifo:mi_parse_tree: end of input tree 0(5292) DEBUG:mi_fifo:mi_fifo_server: done parsing the mi tree
export DBENGINE="MYSQL" before running openserctl....if I'm not wrong, the name of the location table is defined in the DB section of openserctl.....so you need to use a DB engine ....
Although the communication between openserctl and openser is via FIFO I have to define the DBENGINE? Why? I would the dumping the location table should be done from cache thus not needing and DB operation.
Klaus,
I made an update in openserctl to avoid including a DB engine just for using UL commands. Please update from CVS and see if works.
regards, bogdan
Bogdan-Andrei Iancu wrote:
not at all - you just need (at the moment) to configure DB support in openserctl (just do DBENGINE="MYSQL"). This does not require any installation or what ever ...it just forces the inclusion of the file with DB definition.
probably moving the def of this table to a not-DB related location will be a good fix.
regards, bogdan
Klaus Darilion wrote:
Thus, people which have not installed any DB module can use the lookup?
regards klaus
Bogdan-Andrei Iancu wrote:
well... :)....even if it is a operation bouncing to cache (with no DB implication), you need to know the name of location table, to be able to search through cache....Like: search in "location" array for the "xxx" AOR... and the name of the location table is defined in the SQL section of openserctl .....as it is related to DB...
in this case, it is not possible to do a strict separation between DB and cache as the cache follows the structure and naming of the DB...
regards, bogdan
-
Bogdan-Andrei Iancu -
Klaus Darilion