sr-users

sr-users@lists.kamailio.org

1 participants
37563 discussions

[Users] nat problem
by Kro Kamil 30 May '07

30 May '07

Hi, I have a registered Linksys, behind a USR 9108 modem. I can detect its nat, call Linksys and speak normally, but when I try to make a call from Linksys, call breaks down right after call setup. Linksys sends the via and contact ip's as 0.0.0.0 in invite messages and fix_nated_contact does not work. This is possibly because of the modem but, there are no extra configurations that can cause this in the modem. I will be glad if you can direct me with your experiences. thank you... _________________________________________________________________ Live.com'u deneyin: çevrimiçi dünyanýzý bir araya getirin; haberler, spor, hava durumu ve çok daha fazlasý. http://www.live.com/getstarted

6 8

[Users] AVP.pm
by Fero Vlkolinsky 30 May '07

30 May '07

Hi all, I just installed 1.2.1 on my test server and wanted to try out some of the new features. The perl module is exactly what I need. So I wrote a pl script to test avp manipulation. Now the problem is that there is no AVP.pm anywhere in the tarball. Can I get one somewhere? Thanks, Fero --- reklama ----------------------------------------------------- Si muž? A chceš porozumieť ženám? http://www.lesk.sk

3 2

[Serusers] SER rel 2_0_0 - Errors in msilo module
by tzieleniewski 30 May '07

30 May '07

Hi, When I try to store message in the database I get the following errors in the syslog (There are no messages stored in the database): May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found And here is ser.cfg: xlog("L_INFO", " route[INBOUND]: (m_store (0, )) \n"); if (m_store ("0", "")) { xlog("L_INFO", " route[INBOUND]: offline message stored \n"); xlog("L_INFO", " route[INBOUND]: (!t_reply(202,Accepted) \n"); if (!t_reply("202", "Accepted")) { xlog("L_INFO", " route[INBOUND]: sl_reply_error() \n"); sl_reply_error(); } } the error appears in the following place accordin to my logging: May 14 15:26:40 sen ser[5853]: route[INBOUND]: (m_store (0, )) May 14 15:26:40 sen ser[5853]: ERROR: parse_uri: uri too short: <> (0) May 14 15:26:40 sen ser[5853]: ERROR: uri2dst: bad_uri: May 14 15:26:40 sen ser[5853]: t_uac: no socket found May 14 15:26:40 sen ser[5853]: route[INBOUND]: offline message stored May 14 15:26:40 sen ser[5853]: route[INBOUND]: (!t_reply(202,Accepted) May 14 15:26:40 sen ser[5853]: route[INBOUND]: drop <MESSAGE> <sip:hulk@voip.rd.touk.pl> Below is the Message transaction sent through SER: U 2007/05/14 15:26:40.746835 192.168.0.165:7089 -> 192.168.0.165:5060 MESSAGE sip:hulk@voip.rd.touk.pl SIP/2.0. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. Content-Type: text/plain;charset=UTF-8. Content-Length: 12. Max-Forwards: 70. . test message # U 2007/05/14 15:26:40.790793 192.168.0.165:5060 -> 192.168.0.165:7089 SIP/2.0 202 Accepted. CSeq: 64 MESSAGE. Via: SIP/2.0/UDP 192.168.0.165:7089;branch=z9hG4bK24d4276b-8c00-dc11-982b-00148539376e;rport=7089. From: "Sen" <sip:sen@voip.rd.touk.pl>;tag=a0d0276b-8c00-dc11-982b-00148539376e. Call-ID: 32c6276b-8c00-dc11-982b-00148539376e@sen. To: "hulk@" <sip:hulk@voip.rd.touk.pl>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-fd05. Server: Sip EXpress router (2.0.0-rc1 (x86_64/linux)). Content-Length: 0. Warning: 392 192.168.0.165:5060 "Noisy feedback tells: pid=5853 req_src_ip=192.168.0.165 req_src_port=7089 in_uri=sip:hulk@voip.rd.touk.pl out_uri=sip:hulk@voip.rd.touk.pl via_cnt==1". . Thanks for any feedback! Cheers Tomasz

3 13

RE: [Users] BUG: qm_free ?
by Papadopoulos Georgios 30 May '07

30 May '07

I cannot find a core file anywhere. Where should it be? I can reproduce the problem very easily, so please give me more instructions on how to get the coredump+backtrace that you need. thank you George > -----Original Message----- > From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Sent: Tuesday, May 29, 2007 8:34 PM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] BUG: qm_free ? > > Maybe a bug? > > Can you provide a coredump+backtrace? I'm sure Bogdan or > Daniel will take a look at it. > > regards > klaus > > Papadopoulos Georgios wrote: > > Hi Klaus, > > > > It crashes immediately, I have no time to do anything. I > tried again > > and I increased the log level. So now it is process 692. > Here is part > > of the output. I can send you the whole output if that helps. > > > > thank you > > > > George > > > > > > 16(692) DEBUG: timer routine:5,tl=0xb61abdc4 next=0xb61adfd8, > > timeout=3000000 > > 16(692) DEBUG: retransmission_handler : request resending > > (t=0xb61abc78, REGISTER ... ) > > 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > > 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61abdc4 (6000000) > > 16(692) DEBUG: retransmission_handler : done > > 16(692) DEBUG: timer routine:5,tl=0xb61adfd8 next=(nil), > > timeout=3000000 > > 16(692) DEBUG: retransmission_handler : request resending > > (t=0xb61ade8c, REGISTER ... ) > > 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > > 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61adfd8 (6000000) > > 16(692) DEBUG: retransmission_handler : done > > 16(692) DEBUG: timer routine:0,tl=0xb6182810 next=0xb61845ac, > > timeout=3 > > 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > > (0xb61826a8) > > 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > > 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > > 16(692) DEBUG:tm:t_should_relay_response: dns-failover > test: branch=0, > > last_recv=408, flags=0 > > 16(692) DEBUG:tm:t_should_relay_response: trying DNS-based failover > > 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > > add_rule_to_list(377) > > 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb6278238 frag. > > 0xb6278220 (size=72) on 1 -th hit > > 16(692) DBG:add_list_to_head: adding to bl dns 0xb6278238,0xb6278238 > > 16(692) DEBUG:tm:local_reply: branch=0, save=0, winner=0 > > 16(692) DEBUG:tm:local_reply: local transaction completed > > 16(692) DEBUG: add_to_tail_of_timer[2]: 0xb61826f0 (8) > > 16(692) DEBUG: final_response_handler : done > > 16(692) DEBUG: timer routine:0,tl=0xb61845ac next=0xb6186c6c, > > timeout=3 > > 16(692) DEBUG: timer routine:0,tl=0xb6186c6c next=0xb6188d98, > > timeout=3 > > 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > > (0xb6186b04) > > 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > > 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > > 16(692) DEBUG:tm:t_should_relay_response: dns-failover > test: branch=0, > > last_recv=408, flags=0 > > 16(692) DEBUG:tm:t_should_relay_response: trying DNS-based failover > > 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > > add_rule_to_list(377) > > 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb62782b0 frag. > > 0xb6278298 (size=72) on 1 -th hit > > 16(692) DBG:add_list_to_head: adding to bl dns 0xb62782b0,0xb62782b0 > > 16(692) qm_free(0x8151c40, 0xb62782b0), called from blacklists.c: > > rm_dups(440) > > 16(692) BUG: qm_free: bad pointer 0xb62782b0 (out of memory > block!) - > > aborting > > > >> -----Original Message----- > >> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >> Sent: Tuesday, May 29, 2007 5:48 PM > >> To: Papadopoulos Georgios > >> Cc: users(a)openser.org > >> Subject: Re: [Users] BUG: qm_free ? > >> > >> The bug was in process 32133 > >> > >> There are no log statements from this process. What what this > >> process? > >> (use "openserctl ps" to see the PIDs of the processes) > >> > >> regards > >> klaus > >> > >> Papadopoulos Georgios wrote: > >>> Hello all, > >>> > >>> I am having some trouble geting Openser 1.2 to work. It > >> crashes pretty > >>> much immediately. I have tried it successfully on a test > >> system but as > >>> soon as I start it in the production environment, it > >> crashes. Any ideas? > >>> > >>> Thank you for any help. > >>> > >>> George > >>> > >>> > >>> 0(0) INFO: statistics manager successfully initialized > >>> 0(0) StateLess module - initializing > >>> 0(0) TM - initializing... > >>> 0(0) Maxfwd module- initializing > >>> 0(0) INFO:ul_init_locks: locks array size 512 > >>> 0(0) TextOPS - initializing > >>> 0(0) AVPops - initializing > >>> 0(0) permissions - initializing > >>> 0(0) WARNING: File not found: > >> /root/openser/config/permissions.allow > >>> 0(0) Default allow file > >> (/root/openser/config/permissions.allow) not > >>> found => empty rule set > >>> 0(0) WARNING: File not found: > /root/openser/config/permissions.deny > >>> 0(0) Default deny file > (/root/openser/config/permissions.deny) not > >>> found => empty rule set > >>> 0(0) AUTH module - initializing > >>> 0(0) AUTH_DB module - initializing > >>> 0(0) ACC - initializing > >>> 0(0) INFO:xl_parse_name: using hdr type (4) instead of <From> > >>> 0(0) INFO:xl_parse_name: using hdr type (3) instead of <To> > >>> 0(0) INFO:textops:hname_fixup: using hdr type name <Nat-flag> > >>> 0(0) INFO:textops:hname_fixup: using hdr type (31) instead of > >>> <Remote-Party-ID> > >>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>> 1(32087) INFO:mi_fifo:mi_child_init(1): extra fifo > >> listener processes > >>> created > >>> 2(32093) pre_auth(): Credentials received are not filled properly > >>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >> header in > >>> state 22 > >>> 1(32087) ERROR: get_hdr_field: bad to header > >>> 1(32087) ERROR: bad header field > >>> 1(32087) ERROR:maxfwd:is_maxfwd_present : parsing > >> MAX_FORWARD header > >>> failed! > >>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >> header in > >>> state 22 > >>> 1(32087) ERROR: get_hdr_field: bad to header > >>> 1(32087) ERROR: bad header field > >>> 1(32087) find_first_route: Error while parsing headers > >>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >> header in > >>> state 22 > >>> 1(32087) ERROR: get_hdr_field: bad to header > >>> 1(32087) ERROR: bad header field > >>> 1(32087) find_credentials(): Error while parsing headers > >>> 1(32087) pre_auth(): Error while looking for credentials > >>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >> header in > >>> state 22 > >>> 1(32087) ERROR: get_hdr_field: bad to header > >>> 1(32087) ERROR: bad header field > >>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >> header in > >>> state 22 > >>> 1(32087) ERROR: get_hdr_field: bad to header > >>> 1(32087) ERROR: bad header field > >>> 1(32087) ERROR: build_res_buf_from_sip_req: alas, parse_headers > >>> failed > >>> 1(32087) pre_auth(): Error while sending 400 reply > >>> INFO: started (pid: 32073) > >>> [root@ser1 sbin]# 1(32087) pre_auth(): Credentials > >> received are not > >>> filled properly > >>> 16(32133) BUG: qm_free: bad pointer 0xb648f38c (out of > >> memory block!) > >>> - aborting > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 3(32096) ERROR: parse_via: invalid char <=> in state 201 > >>> 3(32096) error: parse_via_param > >>> 3(32096) ERROR: parse_via on: <SIP/2.0/UDP > >>> 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>> To: <sip:gdt@sip.i-call.gr> > >>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>> <mailto:1b7dabcf26487db47f520b5c7195958e@gdt.ath.cx> > >>> CSeq: 4471 REGISTER > >>> User-Agent: Asterisk PBX > >>> Max-Forwards: 70 > >>> Expires: 120 > >>> Contact: <sip:s@87.202.97.60:59945> > >>> Event: registration > >>> Content-Length: 0 > >>> > >>> 3(32096) ERROR: parse_via parse error, parsed so > far:<SIP/2.0/UDP > >>> 87.202.97.60:59945;branc=> > >>> 3(32096) ERROR: get_hdr_field: bad via > >>> 3(32096) ERROR: bad header field > >>> 3(32096) ERROR: parse_msg: message=<REGISTER sip:sip.i-call.gr > >>> SIP/2.0 > >>> Via: SIP/2.0/UDP 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>> To: <sip:gdt@sip.i-call.gr> > >>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>> CSeq: 4471 REGISTER > >>> User-Agent: Asterisk PBX > >>> Max-Forwards: 70 > >>> Expires: 120 > >>> Contact: <sip:s@87.202.97.60:59945> > >>> Event: registration > >>> Content-Length: 0 > >>> > >>> 3(32096) ERROR: receive_msg: parse_msg failed > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 3(32096) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 1(32087) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 2(32093) WARNING: script writer didn't release transaction > >>> 0(32073) child process 32133 exited by a signal 6 > >>> 0(32073) core was generated > >>> 0(32073) INFO: terminating due to SIGCHLD > >>> 1(32087) INFO: signal 15 received > >>> 2(32093) INFO: signal 15 received > >>> 3(32096) INFO: signal 15 received > >>> 5(32102) INFO: signal 15 received > >>> 6(32103) INFO: signal 15 received > >>> 13(32123) INFO: signal 15 received > >>> 14(32127) INFO: signal 15 received > >>> 15(32130) INFO: signal 15 received > >>> 1(32087) 4(32099) 7(32104) INFO: signal 15 received > >>> 8(32109) INFO: signal 15 received > >>> 9(32112) INFO: signal 15 received > >>> 10(32115) INFO: signal 15 received > >>> 11(32118) INFO: signal 15 received > >>> 12(32121) INFO: signal 15 received > >>> INFO: signal 15 received > >>> INFO: signal 15 received > >>> 0(32073) INFO:mi_fifo:mi_destroy: seems that fifo child > is already > >>> dead! > >>> > >>> > >>> > >>> Disclaimer > >>> The information in this e-mail and any attachments is > >> confidential. It is intended solely for the attention and > use of the > >> named addressee(s). If you are not the intended recipient, > or person > >> responsible for delivering this information to the intended > >> recipient, please notify the sender immediately. Unless > you are the > >> intended recipient or his/her representative you are not > authorized > >> to, and must not, read, copy, distribute, use or retain > this message > >> or any part of it. E-mail transmission cannot be guaranteed to be > >> secure or error-free as information could be intercepted, > corrupted, > >> lost, destroyed, arrive late or incomplete, or contain viruses. > >>> > >>> > >>> > >>> > >> > --------------------------------------------------------------------- > >> - > >>> -- > >>> > >>> _______________________________________________ > >>> Users mailing list > >>> Users(a)openser.org > >>> http://openser.org/cgi-bin/mailman/listinfo/users >

2 2

RE: [Users] BUG: qm_free ?
by Papadopoulos Georgios 30 May '07

30 May '07

Hi Bogdan, I found /core.692. Strangely "core was generated" is not in the output. Do you want me to send the core file? thank you, George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, May 30, 2007 2:03 PM > To: Papadopoulos Georgios > Cc: Klaus Darilion; users(a)openser.org > Subject: Re: [Users] BUG: qm_free ? > > HI George, > > first check if the you get the message "core was generated" - > if yes, you should find the core file in the working > directory of openser; if non provided from CLI, check in the > root (/) directory. > > regards, > bogdan > > Papadopoulos Georgios wrote: > > I cannot find a core file anywhere. Where should it be? I can > > reproduce the problem very easily, so please give me more > instructions > > on how to get the coredump+backtrace that you need. > > > > thank you > > > > George > > > > > > > >> -----Original Message----- > >> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >> Sent: Tuesday, May 29, 2007 8:34 PM > >> To: Papadopoulos Georgios > >> Cc: users(a)openser.org > >> Subject: Re: [Users] BUG: qm_free ? > >> > >> Maybe a bug? > >> > >> Can you provide a coredump+backtrace? I'm sure Bogdan or > Daniel will > >> take a look at it. > >> > >> regards > >> klaus > >> > >> Papadopoulos Georgios wrote: > >> > >>> Hi Klaus, > >>> > >>> It crashes immediately, I have no time to do anything. I > >>> > >> tried again > >> > >>> and I increased the log level. So now it is process 692. > >>> > >> Here is part > >> > >>> of the output. I can send you the whole output if that helps. > >>> > >>> thank you > >>> > >>> George > >>> > >>> > >>> 16(692) DEBUG: timer routine:5,tl=0xb61abdc4 next=0xb61adfd8, > >>> timeout=3000000 > >>> 16(692) DEBUG: retransmission_handler : request resending > >>> (t=0xb61abc78, REGISTER ... ) > >>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61abdc4 (6000000) > >>> 16(692) DEBUG: retransmission_handler : done > >>> 16(692) DEBUG: timer routine:5,tl=0xb61adfd8 next=(nil), > >>> timeout=3000000 > >>> 16(692) DEBUG: retransmission_handler : request resending > >>> (t=0xb61ade8c, REGISTER ... ) > >>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61adfd8 (6000000) > >>> 16(692) DEBUG: retransmission_handler : done > >>> 16(692) DEBUG: timer routine:0,tl=0xb6182810 next=0xb61845ac, > >>> timeout=3 > >>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>> (0xb61826a8) > >>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>> > >> test: branch=0, > >> > >>> last_recv=408, flags=0 > >>> 16(692) DEBUG:tm:t_should_relay_response: trying > DNS-based failover > >>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>> add_rule_to_list(377) > >>> 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb6278238 frag. > >>> 0xb6278220 (size=72) on 1 -th hit > >>> 16(692) DBG:add_list_to_head: adding to bl dns > 0xb6278238,0xb6278238 > >>> 16(692) DEBUG:tm:local_reply: branch=0, save=0, winner=0 > >>> 16(692) DEBUG:tm:local_reply: local transaction completed > >>> 16(692) DEBUG: add_to_tail_of_timer[2]: 0xb61826f0 (8) > >>> 16(692) DEBUG: final_response_handler : done > >>> 16(692) DEBUG: timer routine:0,tl=0xb61845ac next=0xb6186c6c, > >>> timeout=3 > >>> 16(692) DEBUG: timer routine:0,tl=0xb6186c6c next=0xb6188d98, > >>> timeout=3 > >>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>> (0xb6186b04) > >>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>> > >> test: branch=0, > >> > >>> last_recv=408, flags=0 > >>> 16(692) DEBUG:tm:t_should_relay_response: trying > DNS-based failover > >>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>> add_rule_to_list(377) > >>> 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb62782b0 frag. > >>> 0xb6278298 (size=72) on 1 -th hit > >>> 16(692) DBG:add_list_to_head: adding to bl dns > 0xb62782b0,0xb62782b0 > >>> 16(692) qm_free(0x8151c40, 0xb62782b0), called from blacklists.c: > >>> rm_dups(440) > >>> 16(692) BUG: qm_free: bad pointer 0xb62782b0 (out of memory > >>> > >> block!) - > >> > >>> aborting > >>> > >>> > >>>> -----Original Message----- > >>>> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >>>> Sent: Tuesday, May 29, 2007 5:48 PM > >>>> To: Papadopoulos Georgios > >>>> Cc: users(a)openser.org > >>>> Subject: Re: [Users] BUG: qm_free ? > >>>> > >>>> The bug was in process 32133 > >>>> > >>>> There are no log statements from this process. What what this > >>>> process? > >>>> (use "openserctl ps" to see the PIDs of the processes) > >>>> > >>>> regards > >>>> klaus > >>>> > >>>> Papadopoulos Georgios wrote: > >>>> > >>>>> Hello all, > >>>>> > >>>>> I am having some trouble geting Openser 1.2 to work. It > >>>>> > >>>> crashes pretty > >>>> > >>>>> much immediately. I have tried it successfully on a test > >>>>> > >>>> system but as > >>>> > >>>>> soon as I start it in the production environment, it > >>>>> > >>>> crashes. Any ideas? > >>>> > >>>>> > >>>>> Thank you for any help. > >>>>> > >>>>> George > >>>>> > >>>>> > >>>>> 0(0) INFO: statistics manager successfully initialized > >>>>> 0(0) StateLess module - initializing > >>>>> 0(0) TM - initializing... > >>>>> 0(0) Maxfwd module- initializing > >>>>> 0(0) INFO:ul_init_locks: locks array size 512 > >>>>> 0(0) TextOPS - initializing > >>>>> 0(0) AVPops - initializing > >>>>> 0(0) permissions - initializing > >>>>> 0(0) WARNING: File not found: > >>>>> > >>>> /root/openser/config/permissions.allow > >>>> > >>>>> 0(0) Default allow file > >>>>> > >>>> (/root/openser/config/permissions.allow) not > >>>> > >>>>> found => empty rule set > >>>>> 0(0) WARNING: File not found: > >>>>> > >> /root/openser/config/permissions.deny > >> > >>>>> 0(0) Default deny file > >>>>> > >> (/root/openser/config/permissions.deny) not > >> > >>>>> found => empty rule set > >>>>> 0(0) AUTH module - initializing > >>>>> 0(0) AUTH_DB module - initializing > >>>>> 0(0) ACC - initializing > >>>>> 0(0) INFO:xl_parse_name: using hdr type (4) instead of <From> > >>>>> 0(0) INFO:xl_parse_name: using hdr type (3) instead of <To> > >>>>> 0(0) INFO:textops:hname_fixup: using hdr type name <Nat-flag> > >>>>> 0(0) INFO:textops:hname_fixup: using hdr type (31) instead of > >>>>> <Remote-Party-ID> > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 1(32087) INFO:mi_fifo:mi_child_init(1): extra fifo > >>>>> > >>>> listener processes > >>>> > >>>>> created > >>>>> 2(32093) pre_auth(): Credentials received are not > filled properly > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR:maxfwd:is_maxfwd_present : parsing > >>>>> > >>>> MAX_FORWARD header > >>>> > >>>>> failed! > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) find_first_route: Error while parsing headers > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) find_credentials(): Error while parsing headers > >>>>> 1(32087) pre_auth(): Error while looking for credentials > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR: build_res_buf_from_sip_req: alas, > parse_headers > >>>>> failed > >>>>> 1(32087) pre_auth(): Error while sending 400 reply > >>>>> INFO: started (pid: 32073) > >>>>> [root@ser1 sbin]# 1(32087) pre_auth(): Credentials > >>>>> > >>>> received are not > >>>> > >>>>> filled properly > >>>>> 16(32133) BUG: qm_free: bad pointer 0xb648f38c (out of > >>>>> > >>>> memory block!) > >>>> > >>>>> - aborting > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) ERROR: parse_via: invalid char <=> in state 201 > >>>>> 3(32096) error: parse_via_param > >>>>> 3(32096) ERROR: parse_via on: <SIP/2.0/UDP > >>>>> 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>> To: <sip:gdt@sip.i-call.gr> > >>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>> <mailto:1b7dabcf26487db47f520b5c7195958e@gdt.ath.cx> > >>>>> CSeq: 4471 REGISTER > >>>>> User-Agent: Asterisk PBX > >>>>> Max-Forwards: 70 > >>>>> Expires: 120 > >>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>> Event: registration > >>>>> Content-Length: 0 > >>>>> > >>>>> 3(32096) ERROR: parse_via parse error, parsed so > >>>>> > >> far:<SIP/2.0/UDP > >> > >>>>> 87.202.97.60:59945;branc=> > >>>>> 3(32096) ERROR: get_hdr_field: bad via > >>>>> 3(32096) ERROR: bad header field > >>>>> 3(32096) ERROR: parse_msg: message=<REGISTER sip:sip.i-call.gr > >>>>> SIP/2.0 > >>>>> Via: SIP/2.0/UDP 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>> To: <sip:gdt@sip.i-call.gr> > >>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>> CSeq: 4471 REGISTER > >>>>> User-Agent: Asterisk PBX > >>>>> Max-Forwards: 70 > >>>>> Expires: 120 > >>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>> Event: registration > >>>>> Content-Length: 0 > >>>>> > >>>>> 3(32096) ERROR: receive_msg: parse_msg failed > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 0(32073) child process 32133 exited by a signal 6 > >>>>> 0(32073) core was generated > >>>>> 0(32073) INFO: terminating due to SIGCHLD > >>>>> 1(32087) INFO: signal 15 received > >>>>> 2(32093) INFO: signal 15 received > >>>>> 3(32096) INFO: signal 15 received > >>>>> 5(32102) INFO: signal 15 received > >>>>> 6(32103) INFO: signal 15 received > >>>>> 13(32123) INFO: signal 15 received > >>>>> 14(32127) INFO: signal 15 received > >>>>> 15(32130) INFO: signal 15 received > >>>>> 1(32087) 4(32099) 7(32104) INFO: signal 15 received > >>>>> 8(32109) INFO: signal 15 received > >>>>> 9(32112) INFO: signal 15 received > >>>>> 10(32115) INFO: signal 15 received > >>>>> 11(32118) INFO: signal 15 received > >>>>> 12(32121) INFO: signal 15 received > >>>>> INFO: signal 15 received > >>>>> INFO: signal 15 received > >>>>> 0(32073) INFO:mi_fifo:mi_destroy: seems that fifo child > >>>>> > >> is already > >> > >>>>> dead! > >>>>> > >>>>> > >>>>> > >>>>> Disclaimer > >>>>> The information in this e-mail and any attachments is > >>>>> > >>>> confidential. It is intended solely for the attention and > >>>> > >> use of the > >> > >>>> named addressee(s). If you are not the intended recipient, > >>>> > >> or person > >> > >>>> responsible for delivering this information to the intended > >>>> recipient, please notify the sender immediately. Unless > >>>> > >> you are the > >> > >>>> intended recipient or his/her representative you are not > >>>> > >> authorized > >> > >>>> to, and must not, read, copy, distribute, use or retain > >>>> > >> this message > >> > >>>> or any part of it. E-mail transmission cannot be > guaranteed to be > >>>> secure or error-free as information could be intercepted, > >>>> > >> corrupted, > >> > >>>> lost, destroyed, arrive late or incomplete, or contain viruses. > >>>> > >>>>> > >>>>> > >>>>> > >> > --------------------------------------------------------------------- > >> > >>>> - > >>>> > >>>>> -- > >>>>> > >>>>> _______________________________________________ > >>>>> Users mailing list > >>>>> Users(a)openser.org > >>>>> http://openser.org/cgi-bin/mailman/listinfo/users > >>>>> > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > >

1 0

[Users] CPL module out of date?
by caco.vera＠unete.cl 30 May '07

30 May '07

Hi' All I'm have installed Openser 1.2.1 and CPL module. I'm having problems to set some parameters for CPL module: The following parameters can be loaded: loadmodule "cpl-c.so" modparam("cpl-c","db_url","mysql://openser:openserrw@localhost/openser") modparam("cpl-c","cpl_table","cpl") modparam("cpl-c","cpl_dtd_file","/usr/local/etc/openser/cpl-06.dtd") modparam("cpl-c","log_dir","/var/log/openser/cpl") modparam("cpl-c","proxy_recurse",2) modparam("cpl-c","proxy_route",0) modparam("cpl-c","lookup_domain","location") These parameters are showing an error "No module matching cpl_c found" #modparam("cpl_c","username_column","username") #modparam("cpl_c","domain_column","domain") #modparam("cpl_c","cpl_xml_column","cpl_xml") #modparam("cpl_c","cpl_bin_column","cpl_bin") #modparam("cpl_c","case_sensitive",0) #modparam("cpl_c","lookup_append_branches",1) #modparam("cpl_c","use_domain",0) LOG MESSAGES: 0(4660) loading module /usr/local/lib/openser/modules/cpl-c.so 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <db_url> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <cpl_table> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <cpl_dtd_file> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <log_dir> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <proxy_recurse> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <proxy_route> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: cpl-c matches module cpl-c 0(4660) set_mod_param_regex: found <lookup_domain> in module cpl-c [/usr/local/lib/openser/modules/] 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (105,18-19): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (106,18-19): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (107,18-19): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (108,18-19): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (109,17-18): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (110,17-18): Can't set module parameter 0(4660) set_mod_param_regex: No module matching cpl_c found | 0(4660) parse error (111,17-18): Can't set module parameter Is CPL module out of dated? somebody has an example of openser configuration file in order ti work with CPL Module? Thanks in advance for your help. Caco.

3 3

[Serusers] First steps understanding ser.cfg
by J. Alberto 30 May '07

30 May '07

Hello, I installed SER a few days ago and I am following the document "SER - Getting Started" to familiarize with SER and understand how it works. I've managed to run the first "hello world" application as well as including authentication through mysql. However, understanding ser.cfg has become more difficult than I thought. To help understand the main route script, I have inserted into the ser.cfg script several calls to xlog function to display information. Although the information displayed is very useful, I don't understand the result of the following sentence: if (uri!=myself) { ..... } I mean, uri is the request uri, for intance, sip:1001@192.168.1.10, and 'myself' is, according to the document, the sip proxy itself, so it can't be the same as uri. However, when the main route processes an INVITE message, the 'if' statement seems to return false because it doesn't execute the instrucion inside the 'if' block. And that would mean that uri is equal to 'myself'. I am sure that I don't undertand what the value of 'myself' is...... Thanks in advance

2 1

[Users] how to make IPv6-to-PSTN work?
by Lee Jacky 30 May '07

30 May '07

how to make IPv6-to-PSTN work? now I am using openser1.1 and rtpproxy. the IPV4 to IPV4/IPV6 works fine. But when I use IPV6 client call PSTN phone,I cann't hear from the PSTN phone. what is wrong? did any one ever meet this problem? thank you for any advice. ___________________________________________________________ 雅虎免费邮箱-3.5G容量，20M附件 http://cn.mail.yahoo.com/

1 0

RE: [Users] BUG: qm_free ?
by Papadopoulos Georgios 29 May '07

29 May '07

Hi Klaus, It crashes immediately, I have no time to do anything. I tried again and I increased the log level. So now it is process 692. Here is part of the output. I can send you the whole output if that helps. thank you George 16(692) DEBUG: timer routine:5,tl=0xb61abdc4 next=0xb61adfd8, timeout=3000000 16(692) DEBUG: retransmission_handler : request resending (t=0xb61abc78, REGISTER ... ) 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61abdc4 (6000000) 16(692) DEBUG: retransmission_handler : done 16(692) DEBUG: timer routine:5,tl=0xb61adfd8 next=(nil), timeout=3000000 16(692) DEBUG: retransmission_handler : request resending (t=0xb61ade8c, REGISTER ... ) 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61adfd8 (6000000) 16(692) DEBUG: retransmission_handler : done 16(692) DEBUG: timer routine:0,tl=0xb6182810 next=0xb61845ac, timeout=3 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL (0xb61826a8) 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 16(692) DEBUG:tm:t_should_relay_response: dns-failover test: branch=0, last_recv=408, flags=0 16(692) DEBUG:tm:t_should_relay_response: trying DNS-based failover 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: add_rule_to_list(377) 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb6278238 frag. 0xb6278220 (size=72) on 1 -th hit 16(692) DBG:add_list_to_head: adding to bl dns 0xb6278238,0xb6278238 16(692) DEBUG:tm:local_reply: branch=0, save=0, winner=0 16(692) DEBUG:tm:local_reply: local transaction completed 16(692) DEBUG: add_to_tail_of_timer[2]: 0xb61826f0 (8) 16(692) DEBUG: final_response_handler : done 16(692) DEBUG: timer routine:0,tl=0xb61845ac next=0xb6186c6c, timeout=3 16(692) DEBUG: timer routine:0,tl=0xb6186c6c next=0xb6188d98, timeout=3 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL (0xb6186b04) 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 16(692) DEBUG:tm:t_should_relay_response: dns-failover test: branch=0, last_recv=408, flags=0 16(692) DEBUG:tm:t_should_relay_response: trying DNS-based failover 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: add_rule_to_list(377) 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb62782b0 frag. 0xb6278298 (size=72) on 1 -th hit 16(692) DBG:add_list_to_head: adding to bl dns 0xb62782b0,0xb62782b0 16(692) qm_free(0x8151c40, 0xb62782b0), called from blacklists.c: rm_dups(440) 16(692) BUG: qm_free: bad pointer 0xb62782b0 (out of memory block!) - aborting > -----Original Message----- > From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Sent: Tuesday, May 29, 2007 5:48 PM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] BUG: qm_free ? > > The bug was in process 32133 > > There are no log statements from this process. What what this > process? > (use "openserctl ps" to see the PIDs of the processes) > > regards > klaus > > Papadopoulos Georgios wrote: > > Hello all, > > > > I am having some trouble geting Openser 1.2 to work. It > crashes pretty > > much immediately. I have tried it successfully on a test > system but as > > soon as I start it in the production environment, it > crashes. Any ideas? > > > > Thank you for any help. > > > > George > > > > > > 0(0) INFO: statistics manager successfully initialized > > 0(0) StateLess module - initializing > > 0(0) TM - initializing... > > 0(0) Maxfwd module- initializing > > 0(0) INFO:ul_init_locks: locks array size 512 > > 0(0) TextOPS - initializing > > 0(0) AVPops - initializing > > 0(0) permissions - initializing > > 0(0) WARNING: File not found: > /root/openser/config/permissions.allow > > 0(0) Default allow file > (/root/openser/config/permissions.allow) not > > found => empty rule set > > 0(0) WARNING: File not found: /root/openser/config/permissions.deny > > 0(0) Default deny file (/root/openser/config/permissions.deny) not > > found => empty rule set > > 0(0) AUTH module - initializing > > 0(0) AUTH_DB module - initializing > > 0(0) ACC - initializing > > 0(0) INFO:xl_parse_name: using hdr type (4) instead of <From> > > 0(0) INFO:xl_parse_name: using hdr type (3) instead of <To> > > 0(0) INFO:textops:hname_fixup: using hdr type name <Nat-flag> > > 0(0) INFO:textops:hname_fixup: using hdr type (31) instead of > > <Remote-Party-ID> > > 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > > 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > > 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > > 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > > 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > > 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > > 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > > 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > > 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > > 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > > 1(32087) INFO:mi_fifo:mi_child_init(1): extra fifo > listener processes > > created > > 2(32093) pre_auth(): Credentials received are not filled properly > > 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > > 1(32087) ERROR: parse_to: invalid To - unexpected end of > header in > > state 22 > > 1(32087) ERROR: get_hdr_field: bad to header > > 1(32087) ERROR: bad header field > > 1(32087) ERROR:maxfwd:is_maxfwd_present : parsing > MAX_FORWARD header > > failed! > > 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > > 1(32087) ERROR: parse_to: invalid To - unexpected end of > header in > > state 22 > > 1(32087) ERROR: get_hdr_field: bad to header > > 1(32087) ERROR: bad header field > > 1(32087) find_first_route: Error while parsing headers > > 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > > 1(32087) ERROR: parse_to: invalid To - unexpected end of > header in > > state 22 > > 1(32087) ERROR: get_hdr_field: bad to header > > 1(32087) ERROR: bad header field > > 1(32087) find_credentials(): Error while parsing headers > > 1(32087) pre_auth(): Error while looking for credentials > > 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > > 1(32087) ERROR: parse_to: invalid To - unexpected end of > header in > > state 22 > > 1(32087) ERROR: get_hdr_field: bad to header > > 1(32087) ERROR: bad header field > > 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > > 1(32087) ERROR: parse_to: invalid To - unexpected end of > header in > > state 22 > > 1(32087) ERROR: get_hdr_field: bad to header > > 1(32087) ERROR: bad header field > > 1(32087) ERROR: build_res_buf_from_sip_req: alas, parse_headers > > failed > > 1(32087) pre_auth(): Error while sending 400 reply > > INFO: started (pid: 32073) > > [root@ser1 sbin]# 1(32087) pre_auth(): Credentials > received are not > > filled properly > > 16(32133) BUG: qm_free: bad pointer 0xb648f38c (out of > memory block!) > > - aborting > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 3(32096) ERROR: parse_via: invalid char <=> in state 201 > > 3(32096) error: parse_via_param > > 3(32096) ERROR: parse_via on: <SIP/2.0/UDP > > 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > > From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > > To: <sip:gdt@sip.i-call.gr> > > Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > > <mailto:1b7dabcf26487db47f520b5c7195958e@gdt.ath.cx> > > CSeq: 4471 REGISTER > > User-Agent: Asterisk PBX > > Max-Forwards: 70 > > Expires: 120 > > Contact: <sip:s@87.202.97.60:59945> > > Event: registration > > Content-Length: 0 > > > > 3(32096) ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP > > 87.202.97.60:59945;branc=> > > 3(32096) ERROR: get_hdr_field: bad via > > 3(32096) ERROR: bad header field > > 3(32096) ERROR: parse_msg: message=<REGISTER sip:sip.i-call.gr > > SIP/2.0 > > Via: SIP/2.0/UDP 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > > From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > > To: <sip:gdt@sip.i-call.gr> > > Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > > CSeq: 4471 REGISTER > > User-Agent: Asterisk PBX > > Max-Forwards: 70 > > Expires: 120 > > Contact: <sip:s@87.202.97.60:59945> > > Event: registration > > Content-Length: 0 > > > > 3(32096) ERROR: receive_msg: parse_msg failed > > 3(32096) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 3(32096) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 1(32087) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 2(32093) WARNING: script writer didn't release transaction > > 0(32073) child process 32133 exited by a signal 6 > > 0(32073) core was generated > > 0(32073) INFO: terminating due to SIGCHLD > > 1(32087) INFO: signal 15 received > > 2(32093) INFO: signal 15 received > > 3(32096) INFO: signal 15 received > > 5(32102) INFO: signal 15 received > > 6(32103) INFO: signal 15 received > > 13(32123) INFO: signal 15 received > > 14(32127) INFO: signal 15 received > > 15(32130) INFO: signal 15 received > > 1(32087) 4(32099) 7(32104) INFO: signal 15 received > > 8(32109) INFO: signal 15 received > > 9(32112) INFO: signal 15 received > > 10(32115) INFO: signal 15 received > > 11(32118) INFO: signal 15 received > > 12(32121) INFO: signal 15 received > > INFO: signal 15 received > > INFO: signal 15 received > > 0(32073) INFO:mi_fifo:mi_destroy: seems that fifo child is already > > dead! > > > > > > > > Disclaimer > > The information in this e-mail and any attachments is > confidential. It is intended solely for the attention and use > of the named addressee(s). If you are not the intended > recipient, or person responsible for delivering this > information to the intended recipient, please notify the > sender immediately. Unless you are the intended recipient or > his/her representative you are not authorized to, and must > not, read, copy, distribute, use or retain this message or > any part of it. E-mail transmission cannot be guaranteed to > be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or > contain viruses. > > > > > > > > > > > ---------------------------------------------------------------------- > > -- > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users >

2 1

[Users] CDR capturing
by Tim 29 May '07

29 May '07

Hello, I was wondering if users out there would be willing to share what mechanism they have found success with in regards to capturing cdrs at a high rate. We recently ran into some problems writing CDRs to a postgres database. Openser threads seemed to block which led to incoming messages not being processed in a timely manner. Flatstore solved the problem but created others, primarily how to stream the data off box for real time processing. We are considering Mysql but first wanted to ask the community to weigh in on what is considered 'best practice' for cdr/transaction record capturing. Our goal is to handle 500 CPS without lost records or process blocking. Thanks. Tim

2 1

Jump to page:

2025

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