-----Original Message----- From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Pavol Segeč Sent: Tuesday, August 02, 2005 9:47 AM To: serusers(a)lists.iptel.org; 'Stefan Sayer' Subject: RE: [Serusers] SER <==> SEMS fifo permisions problem Hi, I had configuration as you wrote, it's described in the install manual, but I cheched it again. No results. I'm sending you my advance. I setted up cfg files as you wrote, after that in /tmp folder is created am_fifo file by root user with 644 permissions. There is not /tmp/ser_fifo file. Call on the sip:100 is terminated immediatelly, with error log inside syslog, no write permissions. There is still not created /tmp/ser_fifo file. I changed /tmp/am_fifo permissions on 666 manually, I've added to ser.cfg cmd: sock_mode=0666, restart ser process and made call on sip:100 (call looks like success, UA report connected, but no announcement, no voice), ser created /tmp/ser_fifo file with 666 permissions now, but there is also a new file created by root user, /tmp/00007A9854930305 with 644 permissions and in my syslog there is an error log Aug 2 09:01:55 mail /usr/sbin/ser[31229]: ERROR: open_reply_pipe: open error (/tmp/00007A9854930305): Permission denied Aug 2 09:01:55 mail /usr/sbin/ser[31229]: ERROR: fifo_reply: no reply pipe /tmp/00007A9854930305 Following your instructions: permission to They are started as root root user on the file They have. ---------------------- I do not understand, why reply pipes are cretaed with 644 permissions? And if did, why there is a write permission error problem? I've also tried to setup socket communication, there have been also some write error problems, which looks also like problems with permissions. But I didn't research it so carefully. Aug 2 08:33:07 mail Sems[30875]: Error: (SerClient.cpp)(write_to_socket)(335): while sending request to /tmp/ser_socket: Connection refused Aug 2 08:33:07 mail Sems[30875]: Error: (SerClient.cpp)(write_to_socket)(335): while sending request to /tmp/ser_socket: Connection refused Aug 2 08:40:23 mail Sems[30936]: Error: (SerClient.cpp)(write_to_socket)(335): while sending request to /tmp/ser_socket: Connection refused Aug 2 08:40:23 mail Sems[30936]: Error: (SerClient.cpp)(write_to_socket)(335): while sending request to /tmp/ser_socket: Connection refused Aug 2 08:42:24 mail /usr/sbin/ser[30775]: WARNING: destroy_fifo: cannot delete fifo (/tmp/ser_socket): Operation not permitted My OS is debian, SER version is 0.9.3 installed as deb package, SEMS is downloaded through CVS and compiled and installed Thanks palo > -----Original Message----- > From: serusers-bounces(a)lists.iptel.org > [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Stefan Sayer > Sent: Monday, August 01, 2005 3:12 PM > To: Pavol Segeč > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] SER <==> SEMS fifo permisions problem > > Hello, > > probably you are starting sems as another user than ser? > > please make sure that you set in sems.conf: > > send_method=fifo > fifo_name=/tmp/am_fifo > ser_fifo_name=/tmp/ser_fifo > > and put # before socket_name and ser_socket_name. > > in ser.cfg: > fifo="/tmp/ser_fifo" > permission to > files created by the user that starts ser (e.g. > start them both as the same user) and 2) both users have write > permission in /tmp and there is a little space left on the file > hth > Stefan > > > Pavol Segeč wrote: > > Hi All ! > > > > I'm implementing SER, SEMS server, I've configured fifo as > > communication method between them (folowing install manual). In > > ser.cfg I've enabled conference part in INVITE message > route handling as follows : > > > > if (uri=~"sip:100.*@") { > > if (!t_newtran()){ > > sl_send_reply("500","Could not create transaction"); > > break; > > }; > > t_reply("100","Trying - just wait a minute !"); > > > > # assumes that Sems configuration parameter 'socket_name=' > > # has been set to /tmp/am_sock > > > > if(!t_write_req("/tmp/am_fifo","conference")) { > > t_reply("500","error contacting sems - in uri > check 100"); > > }; > > break; > > }; > > > > I can make a call on sip:100.*, but I don't have received any > > announcement and in /var/log/syslog I see following > problems with SEMS > > and more oftenly with fifo permisions: > > > > Aug 1 14:30:09 mail Sems[25848]: Error: > > (SerClient.cpp)(read_from_fifo)(286): no more retries! > > Aug 1 14:30:09 mail Sems[25848]: Error: > > (SerClient.cpp)(read_from_fifo)(287): last error: Success Aug 1 > > 14:30:09 mail Sems[25848]: Error: (SerClient.cpp)(send)(137): while (SerClient.cpp)(send)(137): while _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers