Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread qasimak...@gmail.com
Have you confirmed that table/DB name is correct? You can verify your
version table from config.h in your sources.

-Qasim

On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes zozo6...@gmail.com
 wrote:

 Hello,

 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog
 found, expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:init_mod:
 failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules

 The error is telling about invalid version of the dialog table however if
 I check the version table the dialog has the value 8 as it supposed to have
 it.

 Thanks
 Peter
 ___
 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] open sips 1.9 issue

2013-03-18 Thread Peter Zoltan Keresztes
Yes, the table/DB name is correct. the same as in config.h in the sources.
#define VERSION_TABLE version /*! Table holding versions of 
other opensips tables */
#define VERSION_COLUMNtable_version   /*! Column name for the 
version value in version table */
#define TABLENAME_COLUMN  table_name  /*! Column name of the table 
name column in the version table */

mysql describe version;
+---+--+--+-+-+---+
| Field | Type | Null | Key | Default | Extra |
+---+--+--+-+-+---+
| table_name| char(32) | NO   | PRI | NULL|   |
| table_version | int(10) unsigned | NO   | | 0   |   |
+---+--+--+-+-+---+
2 rows in set (0.00 sec)


On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com wrote:

 Have you confirmed that table/DB name is correct? You can verify your version 
 table from config.h in your sources.
 
 -Qasim
 
 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes zozo6...@gmail.com 
 wrote:
 Hello,
 
 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new 
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: 
 ERROR:core:db_check_table_version: invalid version 0 for table dialog found, 
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: 
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:dialog:mod_init: 
 failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:init_mod: 
 failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main: error 
 while initializing modules
 
 The error is telling about invalid version of the dialog table however if I 
 check the version table the dialog has the value 8 as it supposed to have it.
 
 Thanks
 Peter
 ___
 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

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread qasimak...@gmail.com
Also since you copied script from 1.8 you should consider going through
this document.

http://www.opensips.org/Resources/DocsMigration180to190

-Qasim

On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com
qasimak...@gmail.comwrote:

 Set debug level to 6 and then send the logs again.

 -Qasim


 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes 
 zozo6...@gmail.com wrote:

 Yes, the table/DB name is correct. the same as in config.h in the sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */

 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)


 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:

 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.

 -Qasim

 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes 
 zozo6...@gmail.com wrote:

 Hello,

 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog
 found, expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules

 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed to
 have it.

 Thanks
 Peter
 ___
 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



 ___
 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] open sips 1.9 issue

2013-03-18 Thread Peter Zoltan Keresztes
Seting the debug t 6 does not give more information about this error

Mar 18 02:38:59 freya /usr/local/sbin/opensips[16070]: 
ERROR:core:db_check_table_version: invalid version 0 for table dialog found, 
expected 8
Mar 18 02:38:59 freya /usr/local/sbin/opensips[16070]: 
ERROR:dialog:init_dlg_db: error during table version check.
Mar 18 02:38:59 freya /usr/local/sbin/opensips[16070]: ERROR:dialog:mod_init: 
failed to initialize the DB support
Mar 18 02:38:59 freya /usr/local/sbin/opensips[16070]: ERROR:core:init_mod: 
failed to initialize module dialog
Mar 18 02:38:59 freya /usr/local/sbin/opensips[16070]: ERROR:core:main: error 
while initializing modules

Peter

On 18 Mar 2013, at 11:34, qasimak...@gmail.com qasimak...@gmail.com wrote:

 Set debug level to 6 and then send the logs again.
 
 -Qasim
 
 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes zozo6...@gmail.com 
 wrote:
 Yes, the table/DB name is correct. the same as in config.h in the sources.
 #define VERSION_TABLE version /*! Table holding versions 
 of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the 
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the table 
 name column in the version table */
 
 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)
 
 
 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com wrote:
 
 Have you confirmed that table/DB name is correct? You can verify your 
 version table from config.h in your sources.
 
 -Qasim
 
 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes 
 zozo6...@gmail.com wrote:
 Hello,
 
 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new 
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: 
 ERROR:core:db_check_table_version: invalid version 0 for table dialog found, 
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: 
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:dialog:mod_init: 
 failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:init_mod: 
 failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main: error 
 while initializing modules
 
 The error is telling about invalid version of the dialog table however if I 
 check the version table the dialog has the value 8 as it supposed to have it.
 
 Thanks
 Peter
 ___
 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
 
 
 ___
 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

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread Laszlo
Also check the table schema of the dialog module, see
dialog-create.sql under /scripts/mysql
There are differences between 1.8 and 1.9.

dlg_id BIGINT(10) UNSIGNED PRIMARY KEY NOT NULL was removed

id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL
hash_entry INT(10) UNSIGNED NOT NULL
hash_id INT(10) UNSIGNED NOT NULL

was added.

plus there is a new index:
CREATE INDEX hash_idx ON dialog (hash_entry, hash_id);

And in the version table, the table_version is now 8.

-Laszlo


2013/3/18 qasimak...@gmail.com qasimak...@gmail.com:
 Also since you copied script from 1.8 you should consider going through this
 document.

 http://www.opensips.org/Resources/DocsMigration180to190

 -Qasim


 On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com qasimak...@gmail.com
 wrote:

 Set debug level to 6 and then send the logs again.

 -Qasim


 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:

 Yes, the table/DB name is correct. the same as in config.h in the
 sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */

 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)


 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:

 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.

 -Qasim

 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:

 Hello,

 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog 
 found,
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules

 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed to
 have it.

 Thanks
 Peter
 ___
 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



 ___
 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


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread Peter Zoltan Keresztes
Does it have anything to do with the dialog part of the configuration?

# dialog
modparam('dialog', 'db_url', 'mysql://root:sp110q@db/votosips_pp')
modparam('dialog', 'dlg_match_mode', 1)
modparam('dialog', 'db_mode', 2)

Regards,
Peter
On 18 Mar 2013, at 11:46, Laszlo las...@voipfreak.net wrote:

 Also check the table schema of the dialog module, see
 dialog-create.sql under /scripts/mysql
 There are differences between 1.8 and 1.9.
 
 dlg_id BIGINT(10) UNSIGNED PRIMARY KEY NOT NULL was removed
 
 id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL
 hash_entry INT(10) UNSIGNED NOT NULL
 hash_id INT(10) UNSIGNED NOT NULL
 
 was added.
 
 plus there is a new index:
 CREATE INDEX hash_idx ON dialog (hash_entry, hash_id);
 
 And in the version table, the table_version is now 8.
 
 -Laszlo
 
 
 2013/3/18 qasimak...@gmail.com qasimak...@gmail.com:
 Also since you copied script from 1.8 you should consider going through this
 document.
 
 http://www.opensips.org/Resources/DocsMigration180to190
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com qasimak...@gmail.com
 wrote:
 
 Set debug level to 6 and then send the logs again.
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Yes, the table/DB name is correct. the same as in config.h in the
 sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */
 
 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)
 
 
 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:
 
 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.
 
 -Qasim
 
 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Hello,
 
 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog 
 found,
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules
 
 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed to
 have it.
 
 Thanks
 Peter
 ___
 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
 
 
 
 ___
 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
 
 
 ___
 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] open sips 1.9 issue

2013-03-18 Thread Laszlo
No, as long as you using the new 1.9 database name in the db_url parameter.


2013/3/18 Peter Zoltan Keresztes zozo6...@gmail.com:
 Does it have anything to do with the dialog part of the configuration?

 # dialog
 modparam('dialog', 'db_url', 'mysql://root:sp110q@db/votosips_pp')
 modparam('dialog', 'dlg_match_mode', 1)
 modparam('dialog', 'db_mode', 2)

 Regards,
 Peter
 On 18 Mar 2013, at 11:46, Laszlo las...@voipfreak.net wrote:

 Also check the table schema of the dialog module, see
 dialog-create.sql under /scripts/mysql
 There are differences between 1.8 and 1.9.

 dlg_id BIGINT(10) UNSIGNED PRIMARY KEY NOT NULL was removed

 id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL
 hash_entry INT(10) UNSIGNED NOT NULL
 hash_id INT(10) UNSIGNED NOT NULL

 was added.

 plus there is a new index:
 CREATE INDEX hash_idx ON dialog (hash_entry, hash_id);

 And in the version table, the table_version is now 8.

 -Laszlo


 2013/3/18 qasimak...@gmail.com qasimak...@gmail.com:
 Also since you copied script from 1.8 you should consider going through this
 document.

 http://www.opensips.org/Resources/DocsMigration180to190

 -Qasim


 On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com qasimak...@gmail.com
 wrote:

 Set debug level to 6 and then send the logs again.

 -Qasim


 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:

 Yes, the table/DB name is correct. the same as in config.h in the
 sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */

 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)


 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:

 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.

 -Qasim

 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:

 Hello,

 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog 
 found,
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules

 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed to
 have it.

 Thanks
 Peter
 ___
 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



 ___
 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


 ___
 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

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread Peter Zoltan Keresztes
Yes I am using the new database. 
All the fields you were talking about in your previous posts are there the 
version in the version table is also correct but when I start the opensips the 
error is still there.

I am totally clueless and unless I will be able to make this work I will have 
to  uninstall this and install the 1.8 which is working fine for me.
Regards
Peter
On 18 Mar 2013, at 12:03, Laszlo las...@voipfreak.net wrote:

 No, as long as you using the new 1.9 database name in the db_url parameter.
 
 
 2013/3/18 Peter Zoltan Keresztes zozo6...@gmail.com:
 Does it have anything to do with the dialog part of the configuration?
 
 # dialog
 modparam('dialog', 'db_url', 'mysql://root:sp110q@db/votosips_pp')
 modparam('dialog', 'dlg_match_mode', 1)
 modparam('dialog', 'db_mode', 2)
 
 Regards,
 Peter
 On 18 Mar 2013, at 11:46, Laszlo las...@voipfreak.net wrote:
 
 Also check the table schema of the dialog module, see
 dialog-create.sql under /scripts/mysql
 There are differences between 1.8 and 1.9.
 
 dlg_id BIGINT(10) UNSIGNED PRIMARY KEY NOT NULL was removed
 
 id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL
 hash_entry INT(10) UNSIGNED NOT NULL
 hash_id INT(10) UNSIGNED NOT NULL
 
 was added.
 
 plus there is a new index:
 CREATE INDEX hash_idx ON dialog (hash_entry, hash_id);
 
 And in the version table, the table_version is now 8.
 
 -Laszlo
 
 
 2013/3/18 qasimak...@gmail.com qasimak...@gmail.com:
 Also since you copied script from 1.8 you should consider going through 
 this
 document.
 
 http://www.opensips.org/Resources/DocsMigration180to190
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com 
 qasimak...@gmail.com
 wrote:
 
 Set debug level to 6 and then send the logs again.
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Yes, the table/DB name is correct. the same as in config.h in the
 sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */
 
 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)
 
 
 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:
 
 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.
 
 -Qasim
 
 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Hello,
 
 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog 
 found,
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules
 
 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed 
 to
 have it.
 
 Thanks
 Peter
 ___
 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
 
 
 
 ___
 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
 
 
 ___
 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
 
 ___
 Users mailing list
 Users@lists.opensips.org
 

Re: [OpenSIPS-Users] two UACs behind the same nat

2013-03-18 Thread Nick
Hello

I modify my config.

route[nat_fixups] {
xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
# RTP Proxy handling ---#
if (is_method(BYE|CANCEL)) {
unforce_rtp_proxy();
} else if (is_method(INVITE)){
# Activates the RTP Proxy for the CALLEE ---#
rtpproxy_offer(c,61.67.128.46);
};
# catch and fix replies
t_on_reply(2);
}

onreply_route[2] {
#xlog(incoming reply\n);

# Handling of the SDP for the 200 or 183 reply #
# If behind nat (flags 5 or 6) start RTP Proxy #
#Activates the RTP Proxy for the CALLER#
if ( is_method(INVITE) 
(isflagset(5) || isbflagset(6)) 
has_body(application/sdp) ){
rtpproxy_answer(c,61.67.128.46);
}

# If the CALLEE is behind NAT, fix the CONTACT HF #
if (isbflagset(6)) {
fix_nated_contact();
search_append('Contact:.*sip:[^[:cntrl:]]*', ';nat=yes');
}
exit;
}

Then, I used ngrep get packet.

Connection Information still not Opensips SERVER of IP.
It's not change to my setting.

Do you have any suggestion??

Thanks
Nick



2013/3/15 Nick Khamis sym...@gmail.com

 Hello Nick,

 As Bogdan pointed out please look at the important parts of your SDP
 payload:

 sip:55688@61.67.128.46:5060
 Contact: sip:55688@211.75.166.164:5060
 c=IN IP4 211.75.166.164

 sip:@61.67.128.46
 Contact: sip:@192.168.4.197:5060
 c=IN IP4 192.168.4.197

 Kind Regards,

 Nick.

 On 3/15/13, Bogdan-Andrei Iancu bog...@opensips.org wrote:
  Hi Nick,
 
  But in the SDP-s received by the UACs, in the c line, you see the IP
  of the other UAC and not the IP of OpenSIPS, right ?
 
  Regards,
 
  Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
 
 
  On 03/15/2013 03:28 AM, Nick Chang wrote:
 
  Hello Bodgan
 
  2 UACs behind the same nat, I check my routing.
 
  UAC don't route to nat_fixups.
 
  But UACs checked My OpenSIPS private IP (10.10.12.111), Not Public IP.
 
  I don't know why? Do you have any suggestion??
 
  My Config
 
  route[generic_relay] {
 
  xlog(L_NOTICE,3 invite $si);
 
  # for INVITEs enable some additional helper routes
 
  # Helper route, if nat=yes in the R-URI  set flag 6 #
 
  #This is used to Process REINVITES  #
 
  if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){
 
  setbflag(6);
 
  };
 
  # If caller(flag 5) or callee(flag 6) are behind NAT  ---#
 
  # Call the route(6) to force the use of the RTP Proxy ---#
 
  if (isflagset(5) || isbflagset(6)) {
 
  route(nat_fixups);
 
  };
 
  if (!t_relay()) {
 
  sl_reply_error();
 
  };
 
  exit;
 
  }
 
  route[nat_fixups] {
 
  xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
 
  # RTP Proxy handling ---#
 
  if (is_method(BYE|CANCEL)) {
 
  unforce_rtp_proxy();
 
  } else if (is_method(INVITE)){
 
  # Activates the RTP Proxy for the CALLEE ---#
 
  rtpproxy_offer();
 
  };
 
  # catch and fix replies
 
  t_on_reply(2);
 
  }
 
  Thanks
 
  Nick
 
  *From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
  *Sent:* Friday, March 15, 2013 12:32 AM
  *To:* OpenSIPS users mailling list
  *Cc:* Nick Chang
  *Subject:* Re: [OpenSIPS-Users] two UACs behind the same nat
 
  Hi Nick,
 
  Assuming routing is possible between the 2 UACs, you need to double
  check that the IPs in SDP are not changed by proxy and points to the
  actual UACs.
 
  Regards,
 
  Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
 
 
  On 03/11/2013 11:40 AM, Nick Chang wrote:
 
  Hello
 
  I have two UACs behind the same nat.
 
  A call B is OK. But it's not voice.
 
  Can everyone give me a suggestion??
 
  Thanks
 
  Nick
 
 
 
  ___
  Users mailing list
  Users@lists.opensips.org  mailto: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

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] two UACs behind the same nat

2013-03-18 Thread Nick Khamis
It will change it if fired. Make sure that you get to
route[nat_fixups] for the call. And for testing, try removing the
flags (isflagset(5) || isbflagset(6)) etc... xlog(Why me god:
$ru\n) always seems to have mercy on our souls. ;)


Nick.

On 3/18/13, Nick nick.ch...@kland.com.tw wrote:
 Hello

 I modify my config.

 route[nat_fixups] {
 xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
 # RTP Proxy handling ---#
 if (is_method(BYE|CANCEL)) {
 unforce_rtp_proxy();
 } else if (is_method(INVITE)){
 # Activates the RTP Proxy for the CALLEE ---#
 rtpproxy_offer(c,61.67.128.46);
 };
 # catch and fix replies
 t_on_reply(2);
 }

 onreply_route[2] {
 #xlog(incoming reply\n);

 # Handling of the SDP for the 200 or 183 reply #
 # If behind nat (flags 5 or 6) start RTP Proxy #
 #Activates the RTP Proxy for the CALLER#
 if ( is_method(INVITE) 
 (isflagset(5) || isbflagset(6)) 
 has_body(application/sdp) ){
 rtpproxy_answer(c,61.67.128.46);
 }

 # If the CALLEE is behind NAT, fix the CONTACT HF #
 if (isbflagset(6)) {
 fix_nated_contact();
 search_append('Contact:.*sip:[^[:cntrl:]]*', ';nat=yes');
 }
 exit;
 }

 Then, I used ngrep get packet.

 Connection Information still not Opensips SERVER of IP.
 It's not change to my setting.

 Do you have any suggestion??

 Thanks
 Nick



 2013/3/15 Nick Khamis sym...@gmail.com

 Hello Nick,

 As Bogdan pointed out please look at the important parts of your SDP
 payload:

 sip:55688@61.67.128.46:5060
 Contact: sip:55688@211.75.166.164:5060
 c=IN IP4 211.75.166.164

 sip:@61.67.128.46
 Contact: sip:@192.168.4.197:5060
 c=IN IP4 192.168.4.197

 Kind Regards,

 Nick.

 On 3/15/13, Bogdan-Andrei Iancu bog...@opensips.org wrote:
  Hi Nick,
 
  But in the SDP-s received by the UACs, in the c line, you see the IP
  of the other UAC and not the IP of OpenSIPS, right ?
 
  Regards,
 
  Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
 
 
  On 03/15/2013 03:28 AM, Nick Chang wrote:
 
  Hello Bodgan
 
  2 UACs behind the same nat, I check my routing.
 
  UAC don't route to nat_fixups.
 
  But UACs checked My OpenSIPS private IP (10.10.12.111), Not Public IP.
 
  I don't know why? Do you have any suggestion??
 
  My Config
 
  route[generic_relay] {
 
  xlog(L_NOTICE,3 invite $si);
 
  # for INVITEs enable some additional helper routes
 
  # Helper route, if nat=yes in the R-URI  set flag 6 #
 
  #This is used to Process REINVITES  #
 
  if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){
 
  setbflag(6);
 
  };
 
  # If caller(flag 5) or callee(flag 6) are behind NAT  ---#
 
  # Call the route(6) to force the use of the RTP Proxy ---#
 
  if (isflagset(5) || isbflagset(6)) {
 
  route(nat_fixups);
 
  };
 
  if (!t_relay()) {
 
  sl_reply_error();
 
  };
 
  exit;
 
  }
 
  route[nat_fixups] {
 
  xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
 
  # RTP Proxy handling ---#
 
  if (is_method(BYE|CANCEL)) {
 
  unforce_rtp_proxy();
 
  } else if (is_method(INVITE)){
 
  # Activates the RTP Proxy for the CALLEE ---#
 
  rtpproxy_offer();
 
  };
 
  # catch and fix replies
 
  t_on_reply(2);
 
  }
 
  Thanks
 
  Nick
 
  *From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
  *Sent:* Friday, March 15, 2013 12:32 AM
  *To:* OpenSIPS users mailling list
  *Cc:* Nick Chang
  *Subject:* Re: [OpenSIPS-Users] two UACs behind the same nat
 
  Hi Nick,
 
  Assuming routing is possible between the 2 UACs, you need to double
  check that the IPs in SDP are not changed by proxy and points to the
  actual UACs.
 
  Regards,
 
  Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
 
 
  On 03/11/2013 11:40 AM, Nick Chang wrote:
 
  Hello
 
  I have two UACs behind the same nat.
 
  A call B is OK. But it's not voice.
 
  Can everyone give me a suggestion??
 
  Thanks
 
  Nick
 
 
 
  ___
  Users mailing list
  Users@lists.opensips.org  mailto: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



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] Configuration variables: shared variables

2013-03-18 Thread Răzvan Crainea

Hi, Stas!

Currently the pseudo variables are not allowed to be used in the 
modules' configuration. You can only use plain values.


Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 03/15/2013 03:22 PM, Stas Kobzar wrote:

Hello List,

Is there a way to use shared variables in modules' configuration?
For example:

modparam(cfgutils, shvset, DBURI=s:mysql//user:pass@host/accdb)
modparam(acc, db_url, $shv(DBURI))

does not work for me:
ERROR:core:db_check_api: module db_$shv(DBURI) does not export 
db_use_table function


Same error happens when I am trying to use varset:
ERROR:core:db_check_api: module db_$var(dburi) does not export 
db_use_table function


My version 1.8 rev: 9914

Thank you,
Stas





___
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] two UACs behind the same nat

2013-03-18 Thread Nick
Hello

I checked it. It don't to go to the route[nat_fixups].
But My UACs both behind the same NAT.

How to check why not go to the route[nat_fixups]??

Thanks
Nick


2013/3/18 Nick Khamis sym...@gmail.com

 It will change it if fired. Make sure that you get to
 route[nat_fixups] for the call. And for testing, try removing the
 flags (isflagset(5) || isbflagset(6)) etc... xlog(Why me god:
 $ru\n) always seems to have mercy on our souls. ;)


 Nick.

 On 3/18/13, Nick nick.ch...@kland.com.tw wrote:
  Hello
 
  I modify my config.
 
  route[nat_fixups] {
  xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
  # RTP Proxy handling ---#
  if (is_method(BYE|CANCEL)) {
  unforce_rtp_proxy();
  } else if (is_method(INVITE)){
  # Activates the RTP Proxy for the CALLEE ---#
  rtpproxy_offer(c,61.67.128.46);
  };
  # catch and fix replies
  t_on_reply(2);
  }
 
  onreply_route[2] {
  #xlog(incoming reply\n);
 
  # Handling of the SDP for the 200 or 183 reply #
  # If behind nat (flags 5 or 6) start RTP Proxy #
  #Activates the RTP Proxy for the CALLER#
  if ( is_method(INVITE) 
  (isflagset(5) || isbflagset(6)) 
  has_body(application/sdp) ){
  rtpproxy_answer(c,61.67.128.46);
  }
 
  # If the CALLEE is behind NAT, fix the CONTACT HF #
  if (isbflagset(6)) {
  fix_nated_contact();
  search_append('Contact:.*sip:[^[:cntrl:]]*',
 ';nat=yes');
  }
  exit;
  }
 
  Then, I used ngrep get packet.
 
  Connection Information still not Opensips SERVER of IP.
  It's not change to my setting.
 
  Do you have any suggestion??
 
  Thanks
  Nick
 
 
 
  2013/3/15 Nick Khamis sym...@gmail.com
 
  Hello Nick,
 
  As Bogdan pointed out please look at the important parts of your SDP
  payload:
 
  sip:55688@61.67.128.46:5060
  Contact: sip:55688@211.75.166.164:5060
  c=IN IP4 211.75.166.164
 
  sip:@61.67.128.46
  Contact: sip:@192.168.4.197:5060
  c=IN IP4 192.168.4.197
 
  Kind Regards,
 
  Nick.
 
  On 3/15/13, Bogdan-Andrei Iancu bog...@opensips.org wrote:
   Hi Nick,
  
   But in the SDP-s received by the UACs, in the c line, you see the IP
   of the other UAC and not the IP of OpenSIPS, right ?
  
   Regards,
  
   Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
  
  
   On 03/15/2013 03:28 AM, Nick Chang wrote:
  
   Hello Bodgan
  
   2 UACs behind the same nat, I check my routing.
  
   UAC don't route to nat_fixups.
  
   But UACs checked My OpenSIPS private IP (10.10.12.111), Not Public
 IP.
  
   I don't know why? Do you have any suggestion??
  
   My Config
  
   route[generic_relay] {
  
   xlog(L_NOTICE,3 invite $si);
  
   # for INVITEs enable some additional helper routes
  
   # Helper route, if nat=yes in the R-URI  set flag 6 #
  
   #This is used to Process REINVITES  #
  
   if (subst_uri('/((sip:.*)||(sip:.*:.*));nat=yes/\1/')){
  
   setbflag(6);
  
   };
  
   # If caller(flag 5) or callee(flag 6) are behind NAT
  ---#
  
   # Call the route(6) to force the use of the RTP Proxy
 ---#
  
   if (isflagset(5) || isbflagset(6)) {
  
   route(nat_fixups);
  
   };
  
   if (!t_relay()) {
  
   sl_reply_error();
  
   };
  
   exit;
  
   }
  
   route[nat_fixups] {
  
   xlog(L_NOTICE,4 NAT FIXED - $fu call $ru );
  
   # RTP Proxy handling ---#
  
   if (is_method(BYE|CANCEL)) {
  
   unforce_rtp_proxy();
  
   } else if (is_method(INVITE)){
  
   # Activates the RTP Proxy for the CALLEE ---#
  
   rtpproxy_offer();
  
   };
  
   # catch and fix replies
  
   t_on_reply(2);
  
   }
  
   Thanks
  
   Nick
  
   *From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
   *Sent:* Friday, March 15, 2013 12:32 AM
   *To:* OpenSIPS users mailling list
   *Cc:* Nick Chang
   *Subject:* Re: [OpenSIPS-Users] two UACs behind the same nat
  
   Hi Nick,
  
   Assuming routing is possible between the 2 UACs, you need to double
   check that the IPs in SDP are not changed by proxy and points to the
   actual UACs.
  
   Regards,
  
   Bogdan-Andrei Iancu
   OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
  
  
   On 03/11/2013 11:40 AM, Nick Chang wrote:
  
   Hello
  
   I have two UACs behind the same nat.
  
   A call B is OK. But it's not voice.
  
   Can everyone give me a suggestion??
  
   Thanks
  
   Nick
  
  
  
   ___
   Users mailing list
   Users@lists.opensips.org  mailto:Users@lists.opensips.org
   

Re: [OpenSIPS-Users] Stripping unwanted hex characters from headers

2013-03-18 Thread Răzvan Crainea

Hi, Jock

This doesn't seem to be an OpenSIPS issue, but rather a regular 
expression one :). The 'replace' and 'substr' functions in OpenSIPS use 
the POSIX regular expressions[1]. I am not an regexp master, and I don't 
know how they work in perl either, so I can't conclude if you can 
achieve this in OpenSIPS, but I think the link below is a good starting 
point.


[1] http://man7.org/linux/man-pages/man7/regex.7.html

Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 03/15/2013 03:23 PM, Jock McKechnie wrote:

Greetings;

I've got a bit of an oddity. We have a TDM media convertor putting a
$00 (NUL) at the end of the Remote-Party-ID header which is killing
one of our proprietary (and unfixable) SIP stacks. For the life of me
I can't figure out how to get OpenSIPS to strip this - it appears like
the textops features don't work with a hex character like it would in,
say, perl... but I might be using the tooling completely wrong.

I've tried the following without apparent success:
if (is_present_hf(Remote-Party-ID)) {
# Either:
substr('/\x00//g');

# Or:
replace(\x00, );
}

Am I using this completely incorrectly? Or does OpenSIPS not work
escape hex characters in this manner? Or not at all?

My thanks for your time!

  - Jock

___
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] OpenSIPs Database Maintenance

2013-03-18 Thread David Crow
I've got an opensips system that we've been running for about 3 years now.  
Recently I've noticed that the load average on the system has been creeping up 
slowly over time.

I've narrowed this down to the cdr generation script in the opensips-cp, which 
seems to be taking longer and longer to finish.

I was looking at the mysql database and it looks like both the acc and cdrs 
tables just continue to grow.  I know that I can remove stuff from the CDR 
table, but I'm not really sure about the ACC table.  Does anyone have scripts 
that regularly purge old stuff from these databases?  Also what do I do now 
with them as large as they are?

Thanks,

David Crow | Senior Systems Architect
1301 Gervais Street, Suite 1800 | Columbia, SC 29201
(d) 803.978.2727 | (f) 803.733.5888
david.c...@vc3.commailto:david.c...@vc3.com| www.VC3.comhttp://www.vc3.com/
Follow us: [Description: Description: Description: Description: Description: 
cid:image002.png@01CC30E6.8E093080] http://www.facebook.com/VC3Inc 
[Description: Description: Description: Description: Description: 
cid:image004.png@01CC30E6.8E093080] http://twitter.com/#!/VC3Inc

[cid:image003.jpg@01CE23C4.0EB5A2F0]   [cid:image006.jpg@01CE23C4.72A6CFA0]


inline: image001.pnginline: image002.pnginline: image003.jpginline: image006.jpg___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] ACK Timer

2013-03-18 Thread M.Khaled W Chehab
Dear Bogdan,

 

I set the timer as below and all my calls have now 3 sec duration ,please
advice 

 

if (has_totag()  (uri == myself)  is_method(INVITE|ACK|BYE|UPDATE)) {

  if(match_dialog()) {

 xlog(L_INFO,  in-dialog topology hiding request
- $DLG_dir  \n);

 if (check_route_param(nat=yes)) {

setflag(5);

setbflag(6);

 }

 

 if ( is_method(INVITE)) {

$avp(timeout2) = 3;

 

 } else if (is_method(ACK)) {

$avp(timeout2) = 3540;

 }

 

 route(1);

 exit;

  }

 

if (has_totag()) {

  if (is_method(ACK)) {

 $avp(timeout2) = 3540; 

  }

 

  # sequential request withing a dialog should

  # take the path determined by record-routing

 

  if (loose_route()) {

etc

 

} else {

 if ( is_method(ACK) ) {

if ( t_check_trans() ) {

   # non loose-route, but stateful ACK; must
be an ACK after 

   # a 487 or e.g. 404 from upstream server

   t_relay();

   exit;

} else {

   # ACK without matching transaction -

   # ignore and discard

   exit;

}

 }

 sl_send_reply(404,Not here);

  }

  exit;

  

   } else {

  if ( is_method(INVITE)) {

 $avp(timeout2) = 3;

  }

   }

 

Regards

 

 

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Thursday, March 14, 2013 6:59 PM
To: OpenSIPS users mailling list
Cc: M.Khaled W Chehab; 'Brito Nicolas'
Subject: Re: [OpenSIPS-Users] ACK Timer

 

Hi Khaled,

your mistake here is to set the timeout for INVITE under the has_totag()
branch - initial INVITEs do not have TO tags.

Try:


if (has_totag()) {
 if (is_method(ACK)) {
 $avp(timeout2) = 3540; 
  }
  . (loose_route)

} else {

if ( is_method(INVITE)) {
$avp(timeout2) = 3; 
}

...

}

Regards,
Bogdan

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] ACK Timer

2013-03-18 Thread Răzvan Crainea

Hi, Khaled!

The match_dialog() function also matched the dialog and updates the 
timer, therefore you should also set the pseudo variable for ACK before 
the match_dialog() call.


Best regards,

Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 03/18/2013 03:38 PM, M.Khaled W Chehab wrote:


Dear Bogdan,

I set the timer as below and all my calls have now 3 sec duration 
,please advice


if (has_totag()  (uri == myself)  
is_method(INVITE|ACK|BYE|UPDATE)) {


  if(match_dialog()) {

 xlog(L_INFO,  in-dialog topology hiding 
request - $DLG_dir  \n);


 if (check_route_param(nat=yes)) {

setflag(5);

setbflag(6);

 }

 if ( is_method(INVITE)) {

$avp(timeout2) = 3;

 } else if (is_method(ACK)) {

$avp(timeout2) = 3540;

 }

 route(1);

 exit;

  }

if (has_totag()) {

  if (is_method(ACK)) {

 $avp(timeout2) = 3540;

  }

  # sequential request withing a dialog should

  # take the path determined by record-routing

  if (loose_route()) {

etc……..

} else {

 if ( is_method(ACK) ) {

if ( t_check_trans() ) {

# non loose-route, but stateful ACK; must be an ACK after

# a 487 or e.g. 404 from upstream server

t_relay();

exit;

} else {

# ACK without matching transaction -

# ignore and discard

exit;

}

 }

sl_send_reply(404,Not here);

  }

  exit;

   } else {

  if ( is_method(INVITE)) {

 $avp(timeout2) = 3;

  }

   }

Regards

*From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
*Sent:* Thursday, March 14, 2013 6:59 PM
*To:* OpenSIPS users mailling list
*Cc:* M.Khaled W Chehab; 'Brito Nicolas'
*Subject:* Re: [OpenSIPS-Users] ACK Timer

Hi Khaled,

your mistake here is to set the timeout for INVITE under the 
has_totag() branch - initial INVITEs do not have TO tags.


Try:


if (has_totag()) {
if (is_method(ACK)) {
$avp(timeout2) = 3540;
}
  . (loose_route)

} else {

if ( is_method(INVITE)) {
$avp(timeout2) = 3;
}

...

}

Regards,
Bogdan

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.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] RTPProxy Support - Not prefilling callees address

2013-03-18 Thread Nick Khamis
I am not sure if this is the correct place to post OpenSIPS+RTPProxy
questions however, I tried to subscribing to the RTP proxy mailing
list and never heard from them since. If it is ok to post RTP proxy
related questions here I am trying to test OpenSIPS with RTP proxy
with everything behind the same NAT box (i.e., 2 UAs, OpenSIPS,
RTPPoxy) just for testing.

The code I am using is:

route {
 force_rport();
}
route[1] {
if (is_method(INVITE)) {
t_on_branch(1);
t_on_reply(1);
t_on_failure(1);

if (has_body(application/sdp))  rtpproxy_offer();
}
else if (is_method(BYE|CANCEL)) {
unforce_rtp_proxy();
}

if (!t_relay()) {
sl_reply_error();
};
exit;
}
onreply_route[1] {
 if (has_body(application/sdp)) rtpproxy_answer();
}


There is no way audio using RTP proxy, but audio is fine between the
UA without including the RTP proxy related script. Looking at the log
I found that RTP is prefilling the callers address twice, but not the
callees address.


INFO:main: rtpproxy started, pid 7287
INFO:handle_command: new session
ae450168-538e-e211-8550-001b7700a65b@oakville, tag
d23f0168-538e-e211-8550-001b7700a65b;1 requested, type strong
INFO:handle_command: new session on a port 35010 created, tag
d23f0168-538e-e211-8550-001b7700a65b;1
INFO:handle_command: pre-filling caller's address with 192.168.2.101:5062
INFO:handle_command: new session
ae450168-538e-e211-8550-001b7700a65b@oakville, tag
d23f0168-538e-e211-8550-001b7700a65b;2 requested, type strong
INFO:handle_command: new session on a port 22982 created, tag
d23f0168-538e-e211-8550-001b7700a65b;2
INFO:handle_command: pre-filling caller's address with 192.168.2.101:5064
INFO:handle_delete: forcefully deleting session 1 on ports 35010/0
INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: session on ports 35010/0 is cleaned up
INFO:handle_delete: forcefully deleting session 2 on ports 22982/0
INFO:remove_session: RTP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: RTCP stats: 0 in from callee, 0 in from caller, 0
relayed, 0 dropped
INFO:remove_session: session on ports 22982/0 is cleaned up

Is it possible to test RTP relaying with everything on the same network?

Thanks in Advance,

Nick.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] ACK Loop when changing contact on_reply: Please Help!!!

2013-03-18 Thread Nick Khamis
Hello Everyone,

We are changing the Contact header in the on_reply to a public ip
address using:

onreply_route[1] {
xlog(incoming reply\n);
if (has_body(application/sdp)) {
remove_hf(Contact);
append_hf(Contact:
sip:1001@75.15.201.2\r\n);
append_hf(P-hint: Onreply-route -
fixcontact \r\n);

}
}

When doing so, ACK is going into a loop:

U 2013/03/18 13:42:11.021017 75.15.201.2:5060 - 192.168.2.5:5060
ACK sip:75.15.201.2;lr;did=b03.4af9f8f3 SIP/2.0.
Call-ID: VQUK2UGSQBCPHEW27UN5NBJIQM@81.201.86.45.
CSeq: 102 ACK.
From: 15178334003 sip:15178334...@voip.ms;tag=91641.
To: sip:1...@toronto.symack.com;tag=2643FD58-346926A7.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 75.15.201.2;branch=z9hG4bKcd1e.d68abdc.2.
Via: SIP/2.0/UDP 7


Your help is greatly appreciated,

Nick.

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] Load Balancer module for REGISTER as well as INVITE?

2013-03-18 Thread Tuomas Kaikkonen
Can the Load Balancer module be configured to balance REGISTERs as well as the 
INVITES so that the above mentioned setup would work? OR is the Load Balancer 
module just useful for balancing RTP Proxy / media server resources for INVITEs?

I'm new to the Load Balancer module of OpenSIPs. I am running OpenSIPs stable 
branch 1.7 - just by looking examples from the documentation it looks like 
INVITE load balancing is supported.

Tuomas Kaikkonen

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] open sips 1.9 issue

2013-03-18 Thread Peter Zoltan Keresztes
Hello,

One of the nodes of the mysql cluster was out of sync and this issue was 
because of it. 
Thanks for all your helps.
Peter
On 18 Mar 2013, at 12:08, Peter Zoltan Keresztes zozo6...@gmail.com wrote:

 Yes I am using the new database. 
 All the fields you were talking about in your previous posts are there the 
 version in the version table is also correct but when I start the opensips 
 the error is still there.
 
 I am totally clueless and unless I will be able to make this work I will have 
 to  uninstall this and install the 1.8 which is working fine for me.
 Regards
 Peter
 On 18 Mar 2013, at 12:03, Laszlo las...@voipfreak.net wrote:
 
 No, as long as you using the new 1.9 database name in the db_url parameter.
 
 
 2013/3/18 Peter Zoltan Keresztes zozo6...@gmail.com:
 Does it have anything to do with the dialog part of the configuration?
 
 # dialog
 modparam('dialog', 'db_url', 'mysql://root:sp110q@db/votosips_pp')
 modparam('dialog', 'dlg_match_mode', 1)
 modparam('dialog', 'db_mode', 2)
 
 Regards,
 Peter
 On 18 Mar 2013, at 11:46, Laszlo las...@voipfreak.net wrote:
 
 Also check the table schema of the dialog module, see
 dialog-create.sql under /scripts/mysql
 There are differences between 1.8 and 1.9.
 
 dlg_id BIGINT(10) UNSIGNED PRIMARY KEY NOT NULL was removed
 
 id INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL
 hash_entry INT(10) UNSIGNED NOT NULL
 hash_id INT(10) UNSIGNED NOT NULL
 
 was added.
 
 plus there is a new index:
 CREATE INDEX hash_idx ON dialog (hash_entry, hash_id);
 
 And in the version table, the table_version is now 8.
 
 -Laszlo
 
 
 2013/3/18 qasimak...@gmail.com qasimak...@gmail.com:
 Also since you copied script from 1.8 you should consider going through 
 this
 document.
 
 http://www.opensips.org/Resources/DocsMigration180to190
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:34 PM, qasimak...@gmail.com 
 qasimak...@gmail.com
 wrote:
 
 Set debug level to 6 and then send the logs again.
 
 -Qasim
 
 
 On Mon, Mar 18, 2013 at 2:14 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Yes, the table/DB name is correct. the same as in config.h in the
 sources.
 #define VERSION_TABLE version /*! Table holding
 versions of other opensips tables */
 #define VERSION_COLUMNtable_version   /*! Column name for the
 version value in version table */
 #define TABLENAME_COLUMN  table_name  /*! Column name of the
 table name column in the version table */
 
 mysql describe version;
 +---+--+--+-+-+---+
 | Field | Type | Null | Key | Default | Extra |
 +---+--+--+-+-+---+
 | table_name| char(32) | NO   | PRI | NULL|   |
 | table_version | int(10) unsigned | NO   | | 0   |   |
 +---+--+--+-+-+---+
 2 rows in set (0.00 sec)
 
 
 On 18 Mar 2013, at 08:08, qasimak...@gmail.com qasimak...@gmail.com
 wrote:
 
 Have you confirmed that table/DB name is correct? You can verify your
 version table from config.h in your sources.
 
 -Qasim
 
 On Sun, Mar 17, 2013 at 10:32 PM, Peter Zoltan Keresztes
 zozo6...@gmail.com wrote:
 
 Hello,
 
 I have installed an opensips 1.9
 I have the configuration copied from an 1.8 setup created a brand new
 database  when I start it I am getting the following errors:
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:db_check_table_version: invalid version 0 for table dialog 
 found,
 expected 8
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:init_dlg_db: error during table version check.
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:dialog:mod_init: failed to initialize the DB support
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]:
 ERROR:core:init_mod: failed to initialize module dialog
 Mar 17 09:56:35 freya /usr/local/sbin/opensips[434]: ERROR:core:main:
 error while initializing modules
 
 The error is telling about invalid version of the dialog table however
 if I check the version table the dialog has the value 8 as it supposed 
 to
 have it.
 
 Thanks
 Peter
 ___
 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
 
 
 
 ___
 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
 
 
 ___
 Users mailing list
 Users@lists.opensips.org
 http://lists.opensips.org/cgi-bin/mailman/listinfo/users
 
 
 

[OpenSIPS-Users] Opensips RTP issue

2013-03-18 Thread Jagadish Thoutam
Can any one  help Me on this

i configured Opensips i can able to receive the call on Asterisk server whn
i dial my did

###
External DID Provider ---  Opensips(NAT with Public
IP)(192.168.1.62)-Asterisk (192.168.1.222)
###
My Opensips is on NAT with Public Ip

But i cant able to hear anything on call  (No audio)


Here i my opensips.cfg file

XX.XX.XX.XX  = My Public Ip

##
## Core Parameters
##
# chroot=
# group=opensips
# user=opensips
# dbversion_table=
disable_core_dump=no
max_while_loops=100
maxbuffer=262144
memdump=3
memlog=2
# open_files_limit=2048
server_signature=no
server_header=Server: OpenSIPS
user_agent_header=User-Agent: OpenSIPS

##
## Core Fork Parameters
##
fork=yes
children=8
tcp_children=8

##
## Core Logging Parameters
##
debug=3
sip_warning=0
log_stderror=no
log_facility=LOG_LOCAL0
log_name=opensips

##
## Aliases
##
auto_aliases=yes
#alias=localhost
#alias=localhost.localdomain

##
## Connectivity
##
#listen=udp:eth0:5060
#listen=udp:eth0:5060
#listen=tcp:eth0:5060
#listen=udp:eth0:7000
#listen=tcp:eth0:7000
#listen=udp:eth0:7000
#listen=tcp:eth0:7000
# listen=udp:eth1:5060
#tos=IPTOS_LOWDELAY
# advertised_address=174.129.131.38
# advertised_port=5060
mcast_loopback=no
mcast_ttl=1
mhomed=0
# tcp_accept_aliases
tcp_connect_timeout=3
tcp_connection_lifetime=120
tcp_max_connections=2048
# tcp_poll_method=select

##
## DNS
##
dns=no
dns_retr_time=1
dns_retr_no=3
# dns_servers_no=2
dns_try_ipv6=no
disable_dns_blacklist=yes
disable_dns_failover=no
dns_use_search_list=no
rev_dns=no

##
## SIP
##
check_via=0
#! disable_503_translation=no
disable_stateless_fwd=no
disable_tcp=no
# disable_tls=no
#! reply_to_via=1

##
## TLS
##
# disable_tls=no
# listen=tls:your_IP:5061
# tls_verify_server=1
# tls_verify_client=1
# tls_require_client_certificate=0
# tls_method=TLSv1
# tls_certificate=/usr/local/etc/opensips/tls/user/user-cert.pem
# tls_private_key=/usr/local/etc/opensips/tls/user/user-privkey.pem
# tls_ca_list=/usr/local/etc/opensips/tls/user/user-calist.pem

##
## Destination Blacklist
##
# dst_blacklist=gw:{( tcp , 192.168.2.100 , 5060 ,  ),( any ,
192.168.2.101 , 0 ,  )}
# dst_blacklist=net_filter2:{ !( any , 192.168.30.0/255.255.255.0 , 0 , 
)}

##
## Attribute Value Pairs
##
# avp_aliases=uuid=I:660;email=s:email_addr;fwd=i:753

##
## Module Loading
##
mpath=/usr/local/lib64/opensips/modules/

loadmodule db_mysql.so
loadmodule localcache.so
loadmodule signaling.so
loadmodule sl.so
loadmodule tm.so
loadmodule dialog.so
loadmodule maxfwd.so
loadmodule rr.so
loadmodule path.so
loadmodule uri.so
loadmodule textops.so
loadmodule usrloc.so
loadmodule nathelper.so
loadmodule nat_traversal.so
loadmodule uac_redirect.so
loadmodule dispatcher.so
loadmodule mi_fifo.so
# loadmodule mi_datagram.so

##
## Localcache Module Parameters
##
modparam(localcache, cache_table_size, 10)
modparam(localcache, cache_clean_period, 120)

##
## Stateless UA Module Parameters
##
modparam(sl, enable_stats, 1)

##

Re: [OpenSIPS-Users] ACK Timer

2013-03-18 Thread M.Khaled W Chehab
Hi, Razvan .

 

You mean to add $avp(timeout2) = 3540; before  match dialog with no if 
close 

 

if (has_totag()  (uri == myself)  is_method(INVITE|ACK|BYE|UPDATE)) {

 

$avp(timeout2) = 3540;

 

  if(match_dialog()) {

 xlog(L_INFO,  in-dialog topology hiding request - 
$DLG_dir  \n);

 if (check_route_param(nat=yes)) {

setflag(5);

setbflag(6);

 }

 

 if ( is_method(INVITE)) {

$avp(timeout2) = 3;

 

 } else if (is_method(ACK)) {

$avp(timeout2) = 3540;

 }

 

 route(1);

 

Regards



 

 

 

 

From: users-boun...@lists.opensips.org 
[mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan Crainea
Sent: Monday, March 18, 2013 4:53 PM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] ACK Timer

 

Hi, Khaled!

The match_dialog() function also matched the dialog and updates the timer, 
therefore you should also set the pseudo variable for ACK before the 
match_dialog() call.

Best regards,




Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 03/18/2013 03:38 PM, M.Khaled W Chehab wrote:

Dear Bogdan,

 

I set the timer as below and all my calls have now 3 sec duration ,please 
advice 

 

if (has_totag()  (uri == myself)  is_method(INVITE|ACK|BYE|UPDATE)) {

  if(match_dialog()) {

 xlog(L_INFO,  in-dialog topology hiding request - 
$DLG_dir  \n);

 if (check_route_param(nat=yes)) {

setflag(5);

setbflag(6);

 }

 

 if ( is_method(INVITE)) {

$avp(timeout2) = 3;

 

 } else if (is_method(ACK)) {

$avp(timeout2) = 3540;

 }

 

 route(1);

 exit;

  }

 

if (has_totag()) {

  if (is_method(ACK)) {

 $avp(timeout2) = 3540; 

  }

 

  # sequential request withing a dialog should

  # take the path determined by record-routing

 

  if (loose_route()) {

etc……..

 

} else {

 if ( is_method(ACK) ) {

if ( t_check_trans() ) {

   # non loose-route, but stateful ACK; must be 
an ACK after 

   # a 487 or e.g. 404 from upstream server

   t_relay();

   exit;

} else {

   # ACK without matching transaction -

   # ignore and discard

   exit;

}

 }

 sl_send_reply(404,Not here);

  }

  exit;

  

   } else {

  if ( is_method(INVITE)) {

 $avp(timeout2) = 3;

  }

   }

 

Regards

 

 

 

From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] 
Sent: Thursday, March 14, 2013 6:59 PM
To: OpenSIPS users mailling list
Cc: M.Khaled W Chehab; 'Brito Nicolas'
Subject: Re: [OpenSIPS-Users] ACK Timer

 

Hi Khaled,

your mistake here is to set the timeout for INVITE under the has_totag() branch 
- initial INVITEs do not have TO tags.

Try:


if (has_totag()) {
 if (is_method(ACK)) {
 $avp(timeout2) = 3540; 
  }
  . (loose_route)

} else {

if ( is_method(INVITE)) {
$avp(timeout2) = 3; 
}

...

}

Regards,
Bogdan

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.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


Re: [OpenSIPS-Users] Fixing c=IN for OpenSIPS server

2013-03-18 Thread Nick Khamis
What parts of the SDP payload are most important when manipulating
Far End NAT traversal. How/where do we manipulate the Contact header
as such that it does not effect preceding loose routes.

A lot of examples cover an OpenSIPS+RTPProxy on a public IP that must
handle UA behind NAT. The problem we are having is that even our
OpenSIPS+RTPProxy server is behind a NAT, and getting dead ear when
using RTP proxy, and one way (outbound) audio when not using RTP proxy
implementation. Please help

Nick.

On 3/15/13, Ovidiu Sas o...@voipembedded.com wrote:
 Contact is just a SIP header that you can manipulate via
 transformations and sipmsgops functions.
 You can even remove the received header and build/append a new one.

 Regards,
 Ovidiu Sas

 On Wed, Mar 13, 2013 at 1:13 PM, Nick Khamis sym...@gmail.com wrote:
 Hello Ovidiu,

 Thank you so much for your response. I got blind sided when we took on
 this new DID service provider. What is strange is that the same
 configuration works fine with three other providers.. Anyhow, c and o
 are squared away however, I would also like to fix the contact using
 fix_contact(). Is there any way I can pass the public IP to the
 function? Almost there I hope :)

 Nicholas.

 On 3/13/13, Ovidiu Sas o...@voipembedded.com wrote:
 When calling rtpproxy_*, use flag 'c' along with the external IP as a
 second parameter:
 http://www.opensips.org/html/docs/modules/devel/rtpproxy#id292744

 Regards,
 Ovidiu Sas

 --
 VoIP Embedded, Inc.
 http://www.voipembedded.com

 On Tue, Mar 12, 2013 at 11:38 PM, Nick Khamis sym...@gmail.com wrote:
 Hello Everyone,

 We recently took on a new DID provider that is complaining about the
 c=IN IP4 192.168.2.5. advertised by our opensips server. They are
 telling us that is the reason we are not receiving any audio. For some
 reason this was not an issue with other service providers.
 Moving forward, is it possible to change the c=in of the opensips
 server before sending it to our service provider?

 I have seen how nat has been fixed for UA but no example for OpenSIPS
 herself. As I mentioned OpenSIPS and RTPProxy is behind the NAT box.

 Thanks in Advance,

 Nick.

 ___
 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