Hi Peter,

do you get this error all the time? have you tried on a different machine? I guess the error is not related to SEMS specifically, as it is generated by "writev" in openser.

any additional info will be helpful.

regards,
bogdan

Peter Lemenkov wrote:

Hello, All!
I'm trying to use openser as SIP-router and SEMS as
voicemail/conference/etc. But then I tried it the following error
occured then openSER tried to contact SEMS:

0(31580) ERROR: tsend_datagram_ev: failed to send: (12) Cannot allocate memory 0(31580) ERROR:tm:write_to_unixsock: writev failed: Cannot allocate memory
0(31580) ERROR:tm:t_write_unix: write_to_unixsock failed

I pointed right SEMS socked in OpenSER config, but looks like no one
single byte wasn't written in in.

omega1 ~ # openser -V
version: openser 1.2.0-dev18-notls (x86_64/linux)
flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST,
SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
@(#) $Id: main.c,v 1.27 2007/01/11 10:58:47 bogdan_iancu Exp $
main.c compiled on 15:27:13 Jan 15 2007 with gcc 3.4.6
omega1 ~ #

I'm using latest SEMS from SVN (rev. 192), but stable release don't work also.

Here is my openser.cfg:

========================================

                if (!t_newtran()){
sl_send_reply("500","could not create transaction");
                       return;
               };
               if (method=="INVITE"){
#                       avp_db_load("$ru", "$avp(email)");
                       if(!t_write_unix("/tmp/sems_sock","conference")) {
                               t_reply("500","error contacting sems");
                       };
               }
               return;

========================================

What I'm dong wrong?



_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users

Reply via email to