Better make a new post an this time say that you need presence, include your ser.cfg file, include your traces (if you find it necessary) and include your /var/log/messages part also ;)
This mailing thread is too long already. New post will refresh your questions.

 
On 3/14/06, İlker Aktuna (Koç. net ) <ilkera@koc.net> wrote:
Hi,
 
Thanks for your reply. I am mostly interested in the presence server part. That's why I need to use the development version. I guess 0.9.6 does not include presence server, right ?
 
Isn't there anyone who may have come across the problem I get now ?
Any developer who may be reading this ?
 
Thanks,
ilker
 


From: serusers-bounces@iptel.org [mailto: serusers-bounces@iptel.org] On Behalf Of Andrey Kouprianov
Sent: Monday, March 13, 2006 6:23 PM

To: serusers@iptel.org
Subject: Re: [Serusers] mysql configuration and serctl

 
I am not entirely sure, but I think SER has a problem creating ser_fifo for some reason. Your directory settings are fine too.
 
I think you should not use CVS to install SER. Those sources are most probably under development and are being changed constantly. So, instead, download a stable SER version (I would suggest using 0.9.6, which is the latest) from iptel.org and install it right upon your existing version (read INSTALL file first on how to specify the installation directory). If you have a way to remove previous installation first, that would be even better.
 
Best of luck :)

On 3/13/06, İlker Aktuna (Koç. net ) <ilkera@koc.net > wrote:
Hi,
 
I downloaded the ser sources with cvs (following command):
cvs -d :pserver:anonymous@cvs.berlios.de:/cvsroot/ser checkout sip_router
 
I am not sure of the version. How can I check that ?
 
If I use the "serctl ul show" command , I get this response:
Error opening ser's FIFO /tmp/ser_fifo
Make sure you have line fifo=/tmp/ser_fifo in your config
 
My /tmp/ folder permissions:
# ls -adl /tmp/
drwxrwxrwt   14 root     root         4096 Mar 13 09:25 /tmp/
 
In messages file I get these:
Mar 13 08:24:02 asterisk1 /root/ser/sbin/ser[15292]: ERROR: receive_fd: EOF on 21
Mar 13 08:24:02 asterisk1 /root/ser/sbin/ser[15292]: ERROR: receive_fd: EOF on 22
Mar 13 08:45:46 asterisk1 ser: parse error (12,1-5): syntax error
Mar 13 08:45:46 asterisk1 ser: parse error (12,1-5): 
Mar 13 08:53:05 asterisk1 ser: parse error (12,1-5): syntax error
Mar 13 08:53:05 asterisk1 ser: parse error (12,1-5):
 
Mar 13 08:57:15 asterisk1 ser: parse error (12,1-5): syntax error
 
so what should I do ?


_____________________________________________________________________________________________________________________________________________
Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa,  icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz  ve  tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz.  Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez.
This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential  information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however,  sender  cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.
_____________________________________________________________________________________________________________________________________________