sr-users July 2007

sr-users@lists.kamailio.org

163 participants
261 discussions

by JF

Hi, I can't compile SER HEAD. I get the errors below. How can this be fixed? Thanks, JF bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_rr.c:39: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_param.c:42: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/shm_mem.c:43: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/mem.c:50: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from usr_avp.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tls_hooks.h:40, from tls_hooks.c:26: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from timer.c:59: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_read.c:59: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_main.c:111: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from select.c:49: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from pt.c:42: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from msg_translator.c:134: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from main.c:119: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from lock_ops.c:27: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from io_wait.h:93, from io_wait.c:54: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dst_blacklist.c:40: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from dprint.c:34: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dns_cache.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_rr.c:39: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from parser/../mem/../lock_ops.h:85, from parser/../mem/shm_mem.h:76, from parser/parse_param.c:42: parser/../mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/shm_mem.c:43: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from mem/mem.c:50: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from usr_avp.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tls_hooks.h:40, from tls_hooks.c:26: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from timer.c:59: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_read.c:59: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from tcp_conn.h:42, from tcp_main.c:111: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from select.c:49: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from pt.c:42: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from msg_translator.c:134: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from main.c:119: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from lock_ops.c:27: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from io_wait.h:93, from io_wait.c:54: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dst_blacklist.c:40: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from lock_ops.h:85, from locking.h:70, from pt.h:50, from dprint.c:34: futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from dns_cache.c:48: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c action.c -o action.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c atomic_ops.c -o atomic_ops.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c bit_scan.c -o bit_scan.o gcc -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -mtune=athlon -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev9-dns"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 3.4.3"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DUSE_FUTEX -DHAVE_SELECT -c core_cmd.c -o core_cmd.o In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h:48:25: linux/futex.h: No such file or directory In file included from mem/../lock_ops.h:85, from mem/shm_mem.h:76, from core_cmd.c:32: mem/../futexlock.h: In function `futex_get': mem/../futexlock.h:90: error: `FUTEX_WAIT' undeclared (first use in this function) mem/../futexlock.h:90: error: (Each undeclared identifier is reported only once mem/../futexlock.h:90: error: for each function it appears in.) mem/../futexlock.h: In function `futex_release': mem/../futexlock.h:118: error: `FUTEX_WAKE' undeclared (first use in this function) make: *** [core_cmd.o] Error 1

17 years, 1 month

[OpenSER-Users] Re: [Serusers] enum_query from failure route

by Jiri Kuthan

Not sure. I think it is possible to turn it on but possibly ENUM's processing latency may conflict with the failure_route located in the middle of transaction processing and lead to some blocknig conditions, current TM maintainer, Andrei, will certainly know better. -jiri At 16:41 11/07/2007, JF wrote: >Hi, > >Is there any particular reason why enum_query cannot be called from >FAILURE_ROUTE? > >Thanks, > >JF >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

17 years, 1 month

[OpenSER-Users] a c program behaves differently when called by openser than it does when called from the console.

by Bontron

Hello, I have this piece of code in my openser.cfg : exec_msg("/usr/local/etc/openser/uri-folder/record '$fu' $$SIP_USER '$ft' 'additionalinfo'"); The instruction 'record' is a c program. This is supposed to add a record in a mysql database - new incoming call, from caller , to called, date, and an additional info - and as the matter of fact it almost does except that 'record' is unable to append the date. It writes '0000-00-00'. The strange thing is that when the 'record' instruction is being called from the console, the set of instructions being manually written : record 'joe@....' etc ... it records everything including the right date and time. Did any one face a similar situation ? Thanks in advance. Olivier ________________________________________________ Message sent using UebiMiau 2.7.8

17 years, 1 month

[OpenSER-Users] Restricting calls between users

by Gerardo Gonzalez

Regards, I have a debian (etch - kernel 2.6.18) server with openser 1.1.0-9-etch1installed and Asterisk 1.4.6. To admin openser, I'm using openseradmin 0.3 and Asterisk-GUI (Rev. 1203) to admin Asterisk. Openser service works fine to make calls between users (Linksys phones, ATA phones, Sipura phones, etc.) and I installed Asterisk to use VoiceMail, Call Queues, Conferencing, Voice Menus, Calls redirections and PSTN GW functions. NOTE: I can hear only Asterisk VoiceMail, but I'm still working to openser-asterisk integration. For me, who I am a new Linux user, It's hard but not impossible. I want to configure call restrictions between openser VoIP groups at the same domain. For example: I have an IP Network with clients who has remote offices. I'm using openser to connect their offices. Now, I want to use groups to resctric calls between clients. I want to know what's the best solution to do calls restrictions between groups. I must use AVPops, Groups, Asterisk modules, etc ?????? Can anybody help me? PD: I'm sorry for my spanglish. Thanks

17 years, 1 month

Re: [OpenSER-Users] Performance metric

by Fredrik Lundmark

Have a look at these http://www.transnexus.com/White%20Papers/OpenSER-SER_Comparison.htm http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---Perfomance-Te… Should relief any concerns reg. capacity... ///Fredrik ----- Original Message ----- From: Pande, Piyush To: users(a)openser.org Sent: Wednesday, July 11, 2007 10:44 PM Subject: [OpenSER-Users] Performance metric Hi, Does anybody know what is the benchmark for calls/sec and number of simultaneous SIP calls that OpenSER can support? -------------------------------------------------------------------------------- _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

17 years, 1 month

[OpenSER-Users] OpenSER development meeting 17-07-2007 13:00 GMT

by Henning Westerholt

Hello all, the next IRC OpenSER development meeting will take place at next tuesday, the 17-07-2007 at 13:00 UTC (15:00 CEST) at the #openser channel on irc.freenode.net. The purpose of this meeting is to discuss the latest developments in and around the OpenSER project. Topics so far: - release planning (minor, major, schedules) - roadmap trimming (priorization, distribution of tasks) - technical topics (async processing, db interface, script reloading..) - review/ resume of some topics from last meeting For information about the IRC meetings read: http://openser.org/dokuwiki/doku.php/development:irc-meetings For details about this meeting read: http://openser.org/dokuwiki/doku.php/development:irc-meeting-agenda-17-07-2… Please join us! -- Henning Westerholt - Unix system development 1&1 Internet AG, Brauerstraße 48, 76135 Karlsruhe, Germany

17 years, 1 month

[OpenSER-Users] OpeSER Aministrator Training Course at VoN Itally, Rome

by Bogdan-Andrei Iancu

Hi everybody, Following the survey form the last 2 weeks regarding the interest in an OpeSER Aministrator Training Course, I'm very pleased to announce that first edition of this event will take place in Rome, during Von Fall Europe. I want to thanks to everybody who sent me or to the project feedback email regarding the event - they were very useful in taking the final decision. So, the event will take place in Rome, on 26 of September, at Marriott Park Hotel. It will a full day training, from 9:30 to 18:00, with lunch included. Once we settle all the details with pulvermedia, I will come back to you with information about the registration process and the detailed schedule of the course. Thanks and regards, Bogdan

17 years, 1 month

[OpenSER-Users] Good how-to openser + radius authentification

by Marc LEURENT

Good morning everybody, I would be very grateful if you had a great tutorial for configuring openser with radius authentification! I had some trouble with the deb packages, some radius functions are not recognized so I'm compiling it. Thanks

17 years, 1 month

[OpenSER-Users] Accessing openser mibs by name does not work.

by Sergio Gutierrez

Hello everybody. I am trying to access the mibs of openser by using its symbolic names, and I am having and error, but, if use the numerical oids, the values are returned well. # snmpget -v 2c -c public localhost openserSIPProtocolVersion.0 openserSIPProtocolVersion.0: Unknown Object Identifier (Sub-id not found: (top) -> openserSIPProtocolVersion) .1.1.1.1.1.0 # snmpget -v 2c -c public localhost .1.3.6.1.4.1.27483.1.1.1.1.1.0 SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1.0 = STRING: "SIP/2.0" Besides, at sometimes, the subagent seems to disconnect, and I have this error: # snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.27483 | more SNMPv2-SMI::enterprises.27483 = No Such Object available on this agent at this OID Is there something I can check? Thanks in advance for your attention. Sergio Gutiérrez EPM Telecomunicaciones Medellín, Colombia

17 years, 1 month

[OpenSER-Users] Re: [Serusers] enum_query from failure route

by Jiri Kuthan

At 12:08 12/07/2007, JF wrote: >So, if I want to perform some less simple (e.g. enum_query) processing >on failed requests, I should loop the request through SER again and do >it in request route? > >Not a very nice way to solve it. Well sometimes a big-hammer approach features design simplicity which is good (simple to understand, audit, maintain, ....) and can be used to solve problems on serial basis. I personally find this quite a good solution. > One more Record-Route, bigger >message... parsing the whole thing again. parsing yes, you don't have to record-route each pass. -jiri >Andrei, what exactly is the problem regarding long processing in >failure route, and what could be done to fix it? > >Thanks, >JF > >On 7/11/07, Jiri Kuthan <jiri(a)iptel.org> wrote: >>At 21:22 11/07/2007, Martin Hoffmann wrote: >>>Jiri Kuthan wrote: >>>> At 16:41 11/07/2007, JF wrote: >>>> > >>>> >Is there any particular reason why enum_query cannot be called from >>>> >FAILURE_ROUTE? >>>> >>>> Not sure. I think it is possible to turn it on but possibly ENUM's processing >>>> latency may conflict with the failure_route located in the middle of >>>> transaction >>>> processing and lead to some blocknig conditions, current TM >>>> maintainer, Andrei, will >>>> certainly know better. >>> >>>In short: There may be dragons there. >>> >>>Anyways, I am not sure what you want to do, but you can usually skip the >>>problem by fixing the Request-URI and sprialing the call to yourself. >>> >>>For instance, if call forwarding is what you're after, instead of >>>re-setting the target and just running processing again, you can just >>>stuff the URI you want to forward to in the Request-URI and call >>>t_relay() (don't forget the append_branch() if in a failure_route). >>> >>>As a rule, keep failure and onreply routes simple. Actually, as a rule, >>>keep your config simple (Though simple does not necessarly mean short). >> >>Indeed: KISS applies to ser.cfg very well. >> >>-jiri >> >> >> >> >>-- >>Jiri Kuthan http://iptel.org/~jiri/ >> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers > > > >-- >Jiri Kuthan http://iptel.org/~jiri/

17 years, 1 month

← Newer
1
...
12
13
14
15
16
17
18
...
27
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2007