[OpenSIPS-Devel] SF.net SVN: opensips:[5840] trunk
Revision: 5840 http://opensips.svn.sourceforge.net/opensips/?rev=5840view=rev Author: bogdan_iancu Date: 2009-07-07 07:25:33 + (Tue, 07 Jul 2009) Log Message: --- - updated DB schema for Load-Balancer module (one more column added and version increased) Modified Paths: -- trunk/db/schema/load_balancer.xml trunk/scripts/db_berkeley/opensips/load_balancer trunk/scripts/db_berkeley/opensips/version trunk/scripts/dbtext/opensips/load_balancer trunk/scripts/dbtext/opensips/version trunk/scripts/mysql/load_balancer-create.sql trunk/scripts/oracle/load_balancer-create.sql trunk/scripts/postgres/load_balancer-create.sql This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[5842] branches/1.5/modules/db_mysql
Revision: 5842 http://opensips.svn.sourceforge.net/opensips/?rev=5842view=rev Author: bogdan_iancu Date: 2009-07-07 09:42:49 + (Tue, 07 Jul 2009) Log Message: --- backport from trunk (rev #5787 - #5797): - reworked the entire re-connect mechanism in mysql - as the mysql lib is not relaible in delivering the re-connect events to application (when using both prepared statements and text queries), the auto-reconnect for client lib was disabled and all the re-connect work is done manually at application (db_mysql module) level. Revision Links: -- http://opensips.svn.sourceforge.net/opensips/?rev=5787view=rev Modified Paths: -- branches/1.5/modules/db_mysql/README branches/1.5/modules/db_mysql/db_mysql.c branches/1.5/modules/db_mysql/db_mysql.h branches/1.5/modules/db_mysql/dbase.c branches/1.5/modules/db_mysql/doc/db_mysql_admin.xml branches/1.5/modules/db_mysql/my_con.c branches/1.5/modules/db_mysql/my_con.h This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2817434 ] Incorrect key file for table './opensips/active_watchers.MYI
Bugs item #2817434, was opened at 2009-07-06 16:06 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Iñaki Baz Castillo (ibc_sf) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: Incorrect key file for table './opensips/active_watchers.MYI Initial Comment: Using OpenSIPS trunk rev 5738 as presence server. After restarting MySQL server I get the following errors in the log: Jul 6 12:43:08 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30434]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:17 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:44:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:46:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:48:18 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:49:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:51:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it [...] - Note that I restarted MySQL at 12:43. -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 12:47 Message: Hi Inaki, I just backported to 1.5 the fixes from db_mysql (reconnect part) from trunk - maybe you can give it a try, even if i do not think is related to this report - I guess something wrong happened with the tables during restart - the queries done by OpenSIPS cannot bring the table into such state. Regards, Bogdan -- Comment By: Iñaki Baz Castillo (ibc_sf) Date: 2009-07-06 16:58 Message: Reparing the table is not enough, it remains occuring (but now
[OpenSIPS-Devel] [ opensips-Bugs-2815413 ] osipconsole broken for Postgres support
Bugs item #2815413, was opened at 2009-07-01 23:16
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2815413group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: tools
Group: 1.5.x
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Gordon Ross (gordonross)
Assigned to: Iulia Bublea (iulia_bublea)
Summary: osipconsole broken for Postgres support
Initial Comment:
osipconsole uses the wrong quote character in it's SQL statements. osipconsole
uses double quotes to enclose parameters. However, Postgres needs string
parameters to be enclosed in single quotes. Double quotes, to postgres,
indicate a colum name.
A simple add subscriber in osipconsole:
OpenSIPS$:add 1...@blah 1234
Used database is PostgreSQL
1234 blah
Entry could not be retrieved from tableERROR: column 1234 does not exist
Query results:
Retrieving user 1...@blah from dbaliases failedERROR: column 1234 does not
exist
Query results:
Alias 1...@blah does not exist!
Introducing the new user 1...@blah to subscriber table failedERROR: column
1234 does not exist
This problem does not exist in opensipctl.That uses single quotes and works
fine with Postgres.
# /usr/local/sbin/opensipsctl add 2...@blah 1234
pgsql_query: /usr/bin/psql -A -q -t -P fieldsep=' ' -h localhost -U
opensips opensips -c 'insert into subscriber (username,
domain,ha1,ha1b,password) values
('2345','blah','6bc52aec50b4af97f338b0d406234afa','5cb004acd453ef4e8548dfb19ab23ae4','1234');'
new user '2...@blah' added
--
Comment By: Iulia Bublea (iulia_bublea)
Date: 2009-07-02 13:05
Message:
Hi,
I have fixed this a couple of days ago, when another error was reported.
It has been fixed on 1.5 and also on trunk. Please check if it works for
you now.
Regards,
Iulia
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=1086410aid=2815413group_id=232389
___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] SF.net SVN: opensips:[5843] trunk/modules/load_balancer/lb_data.c
Revision: 5843 http://opensips.svn.sourceforge.net/opensips/?rev=5843view=rev Author: bogdan_iancu Date: 2009-07-07 09:53:08 + (Tue, 07 Jul 2009) Log Message: --- - fixed bug introduced with the last enhancements Modified Paths: -- trunk/modules/load_balancer/lb_data.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2808416 ] Load_balancer dst_uri always uses 5060 as port
Bugs item #2808416, was opened at 2009-06-18 17:24 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2808416group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: trunk Status: Open Resolution: Invalid Priority: 1 Private: No Submitted By: Josip Djuricic (jdjurici) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: Load_balancer dst_uri always uses 5060 as port Initial Comment: I've noticed this strange behavior on trunk and 1.5.0 versions (didn't tried any other version though), when I input dst_uri with port specified in it (i.e. sip: xxx.xxx.xxx.xxx:3) it always sends sip messages to port 5060 instead of 3. Because of this I get loops if I'm using same IP for b2bua and sips. So is this behavior normal or is it a bug? Best regards, Josip -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 12:56 Message: Hi Josip, running some tests: ++--++++-+ | id | group_id | dst_uri| resources | probe_mode | description | ++--++++-+ | 1 |1 | sip:127.0.0.1:5100 | pstn=3;tr=5;fff=5 | 0 | | | 2 |1 | sip:127.0.0.1:5200 | pstn=6;tr=57;fff=5 | 0 | | ++--++++-+ and I get (via xlog($du)) : AFTER LB -- DU=sip:127.0.0.1:5200 and the trace shows: U 127.0.0.1:5060 - 127.0.0.1:5200 INVITE sip:serv...@127.0.0.1:5100 SIP/2.0 Regards, Bogdan -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-06-20 02:23 Message: Let's sort out on the mailing list if indeed it's a bug or not. Regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2808416group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2797896 ] sql connection timeout w/ media dispatcher
Bugs item #2797896, was opened at 2009-05-28 15:58 Message generated for change (Settings changed) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2797896group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: tools Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Richard Revels (rrevels) Assigned to: Dan (dan_pascu) Summary: sql connection timeout w/ media dispatcher Initial Comment: Having a problem with the media dispatcher from media proxy 2.3.2 (which is an Excellent tool!) if calls don't hit the platform for several hours. The connection to the mysql server times out and the application does not attempt to reconnect. An error is logged and the record is dropped. Restarting dispatcher solves problem but if a reconnect attempt could be made before giving up it would be helpful. error message: media-dispatcher[7194]: error: failed to insert record into database: MySQL server has gone away -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2797896group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2779502 ] ERROR in re_init_statement: failed while mysql_stmt_prepare.
Bugs item #2779502, was opened at 2009-04-23 16:27 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2779502group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: ERROR in re_init_statement: failed while mysql_stmt_prepare. Initial Comment: When it happens, every registration gets rejected with 500 server internal error. Apr 23 04:04:07 /usr/local/sbin/opensips[9042]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (1243) Unknown prepared statement handler (4) given to mysql_stmt_close Apr 23 04:04:07 /usr/local/sbin/opensips[9042]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Apr 23 04:04:07 /usr/local/sbin/opensips[9042]: ERROR:usrloc:db_update_ucontact: updating database failed Apr 23 04:04:07 /usr/local/sbin/opensips[9042]: ERROR:usrloc:wb_timer: updating contact in db failed Apr 23 04:04:13 /usr/local/sbin/opensips[9042]: ERROR:db_mysql:get_new_stmt_ctx: failed while mysql_stmt_prepare: (2013) Lost connection to MySQL ser ver during query [...] Apr 23 04:07:08 /usr/local/sbin/opensips[9002]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (1243) Unknown prepared statement handler (1) given to mysql_stmt_close Apr 23 04:07:08 /usr/local/sbin/opensips[9002]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Apr 23 04:07:08 /usr/local/sbin/opensips[9002]: ERROR:siptrace:sip_trace: error storing trace Apr 23 04:07:09 /usr/local/sbin/opensips[9005]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_bind_param() failed: Using unsupported buffer type: 858928432 (parameter: 2) the later ones seems to be mysql errors, but triggered from the first one. Restarting opensips (1.5.1) solves the problem for a few days. Thanks a lot! -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 12:58 Message: This should be fixed with the latest backport from trunk (indeed there were some issues with the mysql librarym in particular with the way it reports the reconnect events). Regards, Bogdan -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-06-30 19:55 Message: In the last weeks there were couple of fixes that should also address this bug. Please use the trunk version of db_mysql module and confirm the fixing. Thanks and regards, Bogdan -- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-23 16:42 Message: sorry for the duplicate, my mistake! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2779502group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2817434 ] Incorrect key file for table './opensips/active_watchers.MYI
Bugs item #2817434, was opened at 2009-07-06 15:06 Message generated for change (Comment added) made by ibc_sf You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: Iñaki Baz Castillo (ibc_sf) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: Incorrect key file for table './opensips/active_watchers.MYI Initial Comment: Using OpenSIPS trunk rev 5738 as presence server. After restarting MySQL server I get the following errors in the log: Jul 6 12:43:08 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30434]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:17 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:44:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:46:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:48:18 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:49:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:51:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it [...] - Note that I restarted MySQL at 12:43. -- Comment By: Iñaki Baz Castillo (ibc_sf) Date: 2009-07-07 12:05 Message: Bogdan, it must be a problem in MyISAM indexes. After dumping the whole table and regenerating it from the dump file, the error never happens. Also, in the MySQL bug report I pointed in my first comment, more people got the same solution (regenerating the table, or using InnoDB). -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 11:47 Message: Hi Inaki, I just backported to 1.5 the fixes from db_mysql (reconnect part) from trunk - maybe you can give it a
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
Hi Anca! Nice feature, missing since long time :-) If I understand the code, this triggers PUBLISH with trying even if the dialog is not created (e.g. script error after dialoginfo_set()). In this case, it will stay in trying state for default lifetime. Wouldn't it be better to send trying also from a callback. regards klaus Anca Vamanu schrieb: Revision: 5835 http://opensips.svn.sourceforge.net/opensips/?rev=5835view=rev Author: anca_vamanu Date: 2009-07-06 16:06:57 + (Mon, 06 Jul 2009) Log Message: --- - changed the was dialoginfo publications are triggered. Now for triggering dialoginfo publications it is needed to call a function - dialoginfo_set for each INVITE which starts a dialog for which you want to have state published. This is better than the old way when the dialog publications were done for each dialog for which dialog_create function from dialog module was called. Modified Paths: -- trunk/modules/pua_dialoginfo/README trunk/modules/pua_dialoginfo/doc/pua_dialoginfo_admin.xml trunk/modules/pua_dialoginfo/pua_dialoginfo.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at: Hi Anca! Nice feature, missing since long time :-) If I understand the code, this triggers PUBLISH with trying even if the dialog is not created (e.g. script error after dialoginfo_set()). In this case, it will stay in trying state for default lifetime. Wouldn't it be better to send trying also from a callback. PUBLISH dialog with trying state is in fact a NOOP and it's not useful at all from the watcher's perspective. I suggest never to publish it. Also, the proceeding state means that a 1xx with no To tag (this is, a 100) has been received. This is also not useful, so I wouldn't publish it. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
Iñaki Baz Castillo schrieb: 2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at: Hi Anca! Nice feature, missing since long time :-) If I understand the code, this triggers PUBLISH with trying even if the dialog is not created (e.g. script error after dialoginfo_set()). In this case, it will stay in trying state for default lifetime. Wouldn't it be better to send trying also from a callback. PUBLISH dialog with trying state is in fact a NOOP and it's not useful at all from the watcher's perspective. I suggest never to publish it. Also, the proceeding state means that a 1xx with no To tag (this is, a 100) has been received. This is also not useful, so I wouldn't publish it. IMO it is useful - eg. A calls PSTN and the call setup takes long - e.g. 10 seconds until ringing. In this time intervall, A is already busy on the phone, thus other probably will get notified that A is currently on the phone and the will try to reach him later. regards klaus ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] Access rules for dialog state?
I have a question about the policy for subscriptions to dialog state. How should this be done? Would a new pres-rules document make sense for this. Like dialog-rules, same schema. I could not find any normative specification, did someone find something related to this? Regards, Adrian ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
2009/7/7 Klaus Darilion klaus.mailingli...@pernau.at: PUBLISH dialog with trying state is in fact a NOOP and it's not useful at all from the watcher's perspective. I suggest never to publish it. Also, the proceeding state means that a 1xx with no To tag (this is, a 100) has been received. This is also not useful, so I wouldn't publish it. IMO it is useful - eg. A calls PSTN and the call setup takes long - e.g. 10 seconds until ringing. In this time intervall, A is already busy on the phone, thus other probably will get notified that A is currently on the phone and the will try to reach him later. Othe example: - A is subscribed to dialog presence of C. - B calls C. - The proxy generates a dialog trying PUBLISH (C is called) and sends it to A. - A sees in his phone that C is begin called by B. - However, due to some network error (or C crashed) C doesn't reply to the INVITE (neither 100 or 1XX). In this case, why is useful the NOTIFY A has received? Or perhaps the trying and preceeding NOTIFY would only be received by A in case C is the caller? -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Access rules for dialog state?
For the lack of other pragmatic methods I would implement the following: A. Suport in OpenXCAP server a new auid, document name dialog-rules with the clear purpose of providing an authorization policy for dialog Event B. Setup the OpenSIPS PA module that handles the dialog event to read it in order to apply a policy, the same as presence_xml does with pres- rules Does anyone see a problem with this approach? Adrian On Jul 7, 2009, at 3:37 PM, Iñaki Baz Castillo wrote: 2009/7/7 Iñaki Baz Castillo i...@aliax.net: 2009/7/7 Adrian Georgescu a...@ag-projects.com: I have a question about the policy for subscriptions to dialog state. How should this be done? Would a new pres-rules document make sense for this. Like dialog-rules, same schema. I could not find any normative specification, did someone find something related to this? Hi Adrian, recently I've read all the XCAP related RFC's and documents and found no info at all about RFC 4235. It seems that XCAP is just defined for SIMPLE presence (events presence, presence.watcher and so). In section 6 of RFC 5025 (pres-rules) there is an example of XML document in which there is no keyword presence at all, so I assume it is intended just for presence event :( http://tools.ietf.org/html/rfc5025#section-6 However, would opensips presence module ask for such authorization rules to the XCAP server if the SUBSCRIBE event is different than presence? Adrian, since I'm also interested in this exotic topic, I've started a thread in sip-implementors: https://lists.cs.columbia.edu/pipermail/sip-implementors/2009-July/023106.html Feel free to join it :) -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Access rules for dialog state?
2009/7/7 Adrian Georgescu a...@ag-projects.com: For the lack of other pragmatic methods I would implement the following: A. Suport in OpenXCAP server a new auid, document name dialog-rules with the clear purpose of providing an authorization policy for dialog Event B. Setup the OpenSIPS PA module that handles the dialog event to read it in order to apply a policy, the same as presence_xml does with pres-rules Does anyone see a problem with this approach? I think that is the expected approach :) However, I would like to receive replies in sip-implementors. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Access rules for dialog state?
On Jul 7, 2009, at 4:54 PM, Iñaki Baz Castillo wrote: 2009/7/7 Adrian Georgescu a...@ag-projects.com: For the lack of other pragmatic methods I would implement the following: A. Suport in OpenXCAP server a new auid, document name dialog-rules with the clear purpose of providing an authorization policy for dialog Event B. Setup the OpenSIPS PA module that handles the dialog event to read it in order to apply a policy, the same as presence_xml does with pres- rules Does anyone see a problem with this approach? I think that is the expected approach :) However, I would like to receive replies in sip-implementors. I thought we are the SIP implementors ;-) Adrian ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Access rules for dialog state?
2009/7/7 Adrian Georgescu a...@ag-projects.com: I think that is the expected approach :) However, I would like to receive replies in sip-implementors. I thought we are the SIP implementors ;-) 100% agree :) -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Access rules for dialog state?
On Tue, Jul 7, 2009 at 4:17 PM, Adrian Georgescua...@ag-projects.com wrote: For the lack of other pragmatic methods I would implement the following: A. Suport in OpenXCAP server a new auid, document name dialog-rules with the clear purpose of providing an authorization policy for dialog Event B. Setup the OpenSIPS PA module that handles the dialog event to read it in order to apply a policy, the same as presence_xml does with pres- rules Does anyone see a problem with this approach? It makes sense. -- Victor Pascual Ávila ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2817434 ] Incorrect key file for table './opensips/active_watchers.MYI
Bugs item #2817434, was opened at 2009-07-06 16:06 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2817434group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Iñaki Baz Castillo (ibc_sf) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: Incorrect key file for table './opensips/active_watchers.MYI Initial Comment: Using OpenSIPS trunk rev 5738 as presence server. After restarting MySQL server I get the following errors in the log: Jul 6 12:43:08 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30434]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:08 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Jul 6 12:43:17 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30436]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (1210) Incorrect arguments to mysql_stmt_execute Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:43:40 myserver /usr/sbin/opensips[30437]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:re_init_statement: failed while mysql_stmt_prepare: (2002) Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) Jul 6 12:43:40 myserver /usr/sbin/opensips[30433]: ERROR:db_mysql:db_mysql_do_prepared_query: failed to re-init statement! Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:44:15 myserver /usr/sbin/opensips[30438]: ERROR:presence:insert_subs_db: unsuccessful sql insert Jul 6 12:44:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:46:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:48:18 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:49:58 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it Jul 6 12:51:38 myserver /usr/sbin/opensips[30440]: ERROR:db_mysql:db_mysql_do_prepared_query: mysql_stmt_execute() failed(2): (126) Incorrect key file for table './opensips/active_watchers.MYI'; try to repair it [...] - Note that I restarted MySQL at 12:43. -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 18:37 Message: yes, that was my impression also while googling for this kind of error. Maybe changing the default table type to InnoDB will be something smarter ;). I will close this report - if something new comes up, please re-open it or open a new one. Thanks and regards, Bogdan -- Comment By: Iñaki Baz Castillo (ibc_sf) Date: 2009-07-07 13:05 Message: Bogdan, it must be a problem in MyISAM indexes. After dumping the whole table and regenerating it from the dump
[OpenSIPS-Devel] SF.net SVN: opensips:[5844] trunk/modules/db_postgres
Revision: 5844 http://opensips.svn.sourceforge.net/opensips/?rev=5844view=rev Author: bogdan_iancu Date: 2009-07-07 17:38:14 + (Tue, 07 Jul 2009) Log Message: --- - fixed how the NULL values are handled - use Postgres dedicated fucntions for this. Based on a patch sent by Ruslan Bukin. Closes patch #2817560. Modified Paths: -- trunk/modules/db_postgres/res.c trunk/modules/db_postgres/val.c This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Patches-2817560 ] all method flag and db_postgres
Patches item #2817560, was opened at 2009-07-06 20:53 Message generated for change (Comment added) made by bogdan_iancu You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2817560group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: 1.5.x Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Ruslan Bukin (bukinr) Assigned to: Bogdan-Andrei Iancu (bogdan_iancu) Summary: all method flag and db_postgres Initial Comment: lookup(location) always return -2 if opensips restarted, because opensips cant represent correctly all method flag (only with db_postgres) based on same patch for kamailio http://lists.kamailio.org/pipermail/users/2008-November/thread.html#20549 -- Comment By: Bogdan-Andrei Iancu (bogdan_iancu) Date: 2009-07-07 20:40 Message: Hi, Thanks for the patch - I applied it in slightly modified version as I tried to avoid the burn (memory fragmentation) of allocating 1 byte string for the empty strings. The commit is done on trunk and if you could test it and confirm the fixing (including my changes) before doing a backport to 1.5, will be really great. Regards, Bogdan -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086412aid=2817560group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
El Martes, 7 de Julio de 2009, Adrian Georgescu escribió: Inaki, Should the dialog timeout in this case? Sorry, what do you mean? I couldn't understand. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
El Martes, 7 de Julio de 2009, Adrian Georgescu escribió: When a dialog times out, other actions can be triggered like updating the state for event dialog. Same as we can send BYE messages. Ok, but in case C crashed, why is useful A receiving a NOTIFY trying telling that C is receiving a call? (even if the notification would be terminated when the dialog or INVITE transactions times out). -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] SF.net SVN: opensips:[5835] trunk/modules/pua_dialoginfo
Even if it did crash, the purpose of the module is to notify an interested party when someone will likely be engaged in a phone call. If the end-point of the monitored party crashed just before an INVITE will be sent to it this does not affect anything related to the purpose of the dialog Event. I do not see a conflict here, do you? Adrian On Jul 7, 2009, at 10:34 PM, Iñaki Baz Castillo wrote: El Martes, 7 de Julio de 2009, Adrian Georgescu escribió: When a dialog times out, other actions can be triggered like updating the state for event dialog. Same as we can send BYE messages. Ok, but in case C crashed, why is useful A receiving a NOTIFY trying telling that C is receiving a call? (even if the notification would be terminated when the dialog or INVITE transactions times out). -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [ opensips-Bugs-2818243 ] make deb but opensipsdbctl looks in /usr/local/
Bugs item #2818243, was opened at 2009-07-07 23:54 Message generated for change (Tracker Item Submitted) made by ibc_sf You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2818243group_id=232389 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: core Group: trunk Status: Open Resolution: None Priority: 5 Private: No Submitted By: Iñaki Baz Castillo (ibc_sf) Assigned to: Nobody/Anonymous (nobody) Summary: make deb but opensipsdbctl looks in /usr/local/ Initial Comment: I install OpenSIPS trunk by make deb, but when running opensipsdbctl I get this error: - ERROR: could not load the script in /usr/local/lib64/opensips/opensipsctl/opensipsdbctl.mysql for database engine MYSQL ERROR: database engine not loaded - tried 'MYSQL' - Of course, the correct path in which that file is is the following: /usr/lib64/opensips/opensipsctl/ -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1086410aid=2818243group_id=232389 ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
