sr-users May 2007

sr-users@lists.kamailio.org

164 participants
295 discussions

by Papadopoulos Georgios

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 >

16 years, 11 months

[Users] CDR capturing

by Tim

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

16 years, 11 months

[Users] BUG: qm_free ?

by Papadopoulos Georgios

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.

16 years, 11 months

[Users] Not able to add users

by kiran.bkumar＠wipro.com

Hi All, Even now I am still not able to add the users as I get this error when I am trying.. [root@mkd149633 sbin]# openserctl add wipro1 wipro1 wipro1(a)presence.mkd149633.wipro.com This command requires a database engine - none was loaded [root@mkd149633 sbin]# pwd /usr/local/sbin [root@mkd149633 sbin]# There seems to be some problem in opening the connection to the mysql database. I have done the changes in openserctlrc file which is under /usr/local/etc/openser directory. Please let me know what could be the problem. Is there any other workaround to add 1 0r 2 users for testing purpose. Thanks in advance. Regards, Kiran. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

16 years, 11 months

[Serusers] ser/serweb acl

by flavio

Hi to all, I have successfully installed serweb and I can manage acl users grants as admin. Should I configure my ser.cfg anyway?how to? Any references will be well accepted. Thanks, Flavio -- ******************************** * (o< ing. Patria Flavio * //\ phone 0823451358 * V_/_ mobile 3407873357 * ********************************

16 years, 11 months

[Serusers] Formal SIP message logging

by Sahria Hao

Hi All, I want to get ONLY formal SIP message (ex. INVITE, REGISTER and more) by SER, like Cisco AS5300 debug mode (ex. # debug ccsip message). How do I configure my ser.cfg? Now ser.cfg as follows: debug=3 fork=yes log_facility=LOG_LOCAL0 listen=MY.SER.IP.ADDRESS alias=MY.SER.FQDN.ADDRESS1 alias=MY.SER.FQDN.ADDRESS2 port=5060 children=4 dns=no rev_dns=no fifo="/tmp/ser_fifo" fifo_db_url="mysql://ser:heslo@localhost/ser" And /etc/syslog.conf as follows: # SIP Express Router log local0.* /var/log/ser.log Regards, Sahria

16 years, 11 months

[Serusers] TECHNICAL BOARD: Closed for new nominations

by Greger V. Teigre

New nominations for the iptel.org technical board are no longer accepted. The nominees not having confirmed their candidacy yet have received the below email privately just a few minutes ago. We will shortly proceed to voting, which according to the rules will be open 7 days from its start. g-) ------------------------ Hi, You have been nominated as a candidate for the iptel.org technical board, but has not yet indicated your willingness (or not) to participate as a candidate in the election. Your nominations have all been posted quite some time ago, and you should have had time to consider it, so in order to proceed with voting, we need to quickly confirm the candidates. Please reply to this email within 24 hours to confirm your candidacy. If I do not hear anything, I assume that you are not willing to be a candidate. Cheers, Greger

16 years, 11 months

[Serusers] Technical board: Secret vs. public voting, suggested amendment to the rules

by Greger V. Teigre

Several people have on the lists and privately indicated their concern about public voting and the risk that people may feel uncomfortable. I have had several discussions privately on the issue and suggest the following amendment to the rules for election of the technical board (http://www.iptel.org/technicalboard/rules): ------------------- - The parenthesis "(by posting to one of the lists)" is removed from item 6. New items: 9. Before nomination starts, a person and email address should be identified publicly as the coordinator of the election process. 10. Nominations are suggested either publicly on one of the lists identified in item 6 or privately to the coordinator. Each nominee must accept the nomination in order to be electable. 11. Voting is done according to item 8 either by posting who are voted for on one of the lists identified in item 6 or privately to the coordinator. 12. Nominations and votes shall be anonymously posted to an iptel.org webpage and kept updated regularly by the coordinator. The coordinator shall keep all posts and private emails with votes as an assurance that the result can be verified by a third party. 13. Voting shall be open for seven days. ------------------- I'm sorry this becomes elaborate, but I believe that by being very explicit and detailed on the technical board, we may avoid trouble later. Unless there are change suggestions, comments, or objections within the end of the nomination (end of day Monday), I will amend the technical board rules and proceed to the voting step. g-)

16 years, 11 months

[Users] LinuxTag - Hall 12, Stand 11

by Daniel-Constantin Mierla

Hello, those visiting LinuxTag in Berlin, May 30 - June 2, can find OpenSER at Stand 11 in the Hall 12, it will be like the VoIP area: http://www.linuxtag.org/2007/en/visitors/ausstellung/ausstellerliste.html We hope to meet many of you, discuss about the project and go for some German beer. Cheers, Daniel

16 years, 11 months

[Serusers] ser-to asterisk and asterisk to ser call

by Rjey Nomer

Hi, Good day to all, is anyone in the list successfully installed and configured on different machine an asterisk and ser server wherein ser sip user can call asterisk sip user and vice versa. Is it possible? Can you post configuration files for regarding this? Thank you in advanced! Regards, Rjey ____________________________________________________________________________________Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/

16 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
...
30
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 May 2007