Re: [OpenSIPS-Users] Call Recording with mediaproxy
Try oreka or orecx On 1/12/10, Indiver nehru.i...@gmail.com wrote: Hi Every one, I'm running opensips with mediaproxy. I want to record particular calls running thru my server. In rtpproxy call recording feature is inbuilt. Is there any option for call recording using mediaproxy. I tried to use orex call recording tool but it has no debian 64 bit package. Is there any opensource tool with opensips to record call or any method using mediaproxy. Thanks in advance -- View this message in context: http://n2.nabble.com/Call-Recording-with-mediaproxy-tp4290908p4290908.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Is RPID being cached?
Using OpenSIPs 1.6.1 and have noticed a peculiar issue. If a subscriber has a value in the RPID column, then that value is changed to NULL it seems that OpenSIPs still retains the previous number. For example: If RPID column is NULL (initially) --- if ($avp(s:rpid))) returns FALSE If RPID column is changed to eg. 1234567890 --- if ($avp(s:rpid)) returns TRUE and is 1234567890 If RPID column is then changed back to NULL --- if ($avp(s:rpid)) returns TRUE and is 1234567890 Is this a bug or a feature? In either case, is there a way to get OpenSIPs to only use the current DB value? Thanks! ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Is RPID being cached?
Depends on your db_mode for the registrar. On 01/14/2010 03:07 PM, Alan Frisch wrote: Using OpenSIPs 1.6.1 and have noticed a peculiar issue. If a subscriber has a value in the RPID column, then that value is changed to NULL it seems that OpenSIPs still retains the previous number. For example: If RPID column is NULL (initially) --- if ($avp(s:rpid))) returns FALSE If RPID column is changed to eg. 1234567890 --- if ($avp(s:rpid)) returns TRUE and is 1234567890 If RPID column is then changed back to NULL --- if ($avp(s:rpid)) returns TRUE and is 1234567890 Is this a bug or a feature? In either case, is there a way to get OpenSIPs to only use the current DB value? Thanks! ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] TLS errors
hi, i am using opensips/TLS, i get the following error Jan 14 22:53:54 [19740] ERROR:core:_tls_read: SYSCALL error - (0) Success Jan 14 22:53:54 [19740] ERROR:core:_tls_read: something wrong in SSL: 5 Jan 14 22:53:54 [19740] ERROR:core:tcp_read_req: failed to read Jan 14 22:54:46 [19740] ERROR:core:tls_accept: some error in SSL (ret=0, err=1, errno=0/Success): Jan 14 22:54:46 [19740] ERROR:core:tls_print_errstack: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca any hinst about these? actually the client works but error in encryption process is not good, i think thanks ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Is RPID being cached?
I was using memory only for usrloc. I played around with the different modes, then switched back to memory only. Noticed that the RPID would cache when I was testing in non-forked mode, but works as expected when forked mode. Thanks for the help. On Thu, Jan 14, 2010 at 3:13 PM, Alex Balashov abalas...@evaristesys.com wrote: Depends on your db_mode for the registrar. On 01/14/2010 03:07 PM, Alan Frisch wrote: Using OpenSIPs 1.6.1 and have noticed a peculiar issue. If a subscriber has a value in the RPID column, then that value is changed to NULL it seems that OpenSIPs still retains the previous number. For example: If RPID column is NULL (initially) --- if ($avp(s:rpid))) returns FALSE If RPID column is changed to eg. 1234567890 --- if ($avp(s:rpid)) returns TRUE and is 1234567890 If RPID column is then changed back to NULL --- if ($avp(s:rpid)) returns TRUE and is 1234567890 Is this a bug or a feature? In either case, is there a way to get OpenSIPs to only use the current DB value? Thanks! ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Need Help on integrating opensips with mysql on remote machine
have you set this option in the config *mysql*://user:db_passw...@remote_db_ip_address/opensips On Mon, Jan 11, 2010 at 12:15 PM, Alok Kushwaha alok.c...@gmail.com wrote: Hi! All, I am using opensips 1.5 and installed using source. my DB server (mysql) is running on a remote machine. I have enabled the remote access and granted the proper privileges. I started the opensips with service opensips start but it stopped in 2 minutes. and follwing error message is logged - (in /var/log/message) Jan 11 07:01:15 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.11 Jan 11 07:01:35 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.12 Jan 11 07:01:55 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.13 Jan 11 07:02:15 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.14 Jan 11 07:02:35 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.15 Jan 11 07:02:56 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.11 Jan 11 07:03:16 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.12 Jan 11 07:03:36 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.13 Jan 11 07:03:56 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.14 Jan 11 07:04:16 localhost opensips: WARNING:core:fix_socket_list: could not rev. resolve 200.200.100.15 Jan 11 07:04:16 localhost opensips: INFO:core:init_tcp: using epoll_lt as the TCP io watch method (auto detected) Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: NOTICE:core:main: version: opensips 1.5.0-notls (i386/linux) Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:core:main: using 32 Mb shared memory Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:core:main: using 1 Mb private memory per process Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: NOTICE:signaling:mod_init: initializing module ... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:sl:mod_init: Initializing StateLess engine Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:tm:mod_init: TM - initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:maxfwd:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:usrloc:ul_init_locks: locks array size 512 Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:registrar:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:textops:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:xlog:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:acc:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:auth:mod_init: initializing... Jan 11 07:04:16 localhost /usr/local/sbin/opensips[4645]: INFO:auth_db:mod_init: initializing... Jan 11 07:04:36 localhost /usr/local/sbin/opensips[4645]: INFO:core:probe_max_receive_buffer: using a UDP receive buffer of 255 kb Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4645]:last message repeated 5 times Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]: ERROR:db_mysql:db_mysql_new_connection: driver error(2003): Can't connect to MySQL server on '200.200.100.22' (4) Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]: ERROR:core:db_do_init: could not add connection to the pool Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]: ERROR:auth_db:child_init: unable to connect to the database Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]: ERROR:core:init_mod_child: failed to initializing module auth_db, rank 17 Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4663]: ERROR:core:main_loop: init_child failed for UDP listener Jan 11 07:06:36 localhost /usr/local/sbin/opensips[4665]: ERROR:db_mysql:db_mysql_new_connection: driver error(2003): Can't connect to MySQL server on '200.200.100.22' (4) for me it's look like some problem in core module. but i don't where to find it. please tell me why it's stopped. any help is appreciated. thanks in advance. -- Regards, Alok Kushwaha always be the reason of someones happiness. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] About STUN server configuration
Dear all, After configuring the following related to stun in opensips.cfg for my opensips1.6.0, start-up of the opensips failed. What else should I configure to work STUN server? [opensips.cfg] ### Modules Section loadmodule stun.so # - stun params - modparam(stun, primary_ip, 192.168.100.1) modparam(stun, primary_port, 5060) modparam(stun, alternate_ip, 192.168.1.1) modparam(stun, alternate_port, 3479) Regards, Yagishita ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
