Re: [OpenSIPS-Users] Virtual_DB issue with NDBClUSTER

[Duane Larson]

Thanks for the idea Jeff.

On Tue, Dec 14, 2010 at 6:27 PM, Jeff Pyle  wrote:

> I use Opensips with NDBCLUSTER, although not with db_virtual.  Seems to
> work okay with db_mysql.  To keep things simple, each of my Opensips
> machines (VMs, really) has a mysqld instance whose only role is to be a
> front-end to the cluster.  I've tried it with CentOS RPMs, Debian (stable)
> packages, and 7.1.x source from the MySQL site.  All okay.
>
> Sorry, no further information on the virtual portion.
>
>
> - Jeff
>
>
> On 12/14/10 12:35 PM, "osiris123d"  wrote:
>
> >
> >I am trying to get OpenSIPS Virtual_DB module to work with a MySQL Cluster
> >that I have set up.
> >
> >Instead of the database tables being the usual MyISAM I set them up to be
> >NDBCLUSTER.
> >
> >Within the OpenSIPS config I have
> >
> ># - db_virtual params -
> >modparam("db_virtual", "db_urls", "define set1 ROUND")
> >modparam("db_virtual", "db_urls",
> >"mysql://:***...@173.***.***.219/opensips")
> >modparam("db_virtual", "db_urls",
> >"mysql://:***...@173.***.***.218/opensips")
> >
> >
> >To test I shut down the database on the 173.***.***.218 server and
> >OpenSIPS
> >went down.  When I try to restart OpenSIPS I see the following in the
> >syslog
> >
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to
> >MySQL
> >server on '173.***.***.218' (111)
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:db_mysql:db_mysql_new_connection: initial connect failed
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:core:db_do_init: could not add connection to the pool
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:db_virtual:db_virtual_init: cant init db
> >mysql://:**...@173.***.***.218/opensips
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:db_mysql:db_mysql_submit_query: driver error: Got error 157 'Unknown
> >error code' from NDBCLUSTER
> >Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
> >ERROR:core:db_do_query: error while submitting query
> >Dec 14 11:17:20 Proxy01 kernel: [235305.342266] opensips[3843]: segfault
> >at
> >20 ip 004f4e03 sp 7fffb3965840 error 4 in
> >opensips[40+14d000]
> >
> >
> >
> >Looks like it dumped the core and the core says
> >
> >(gdb) backtrace
> >#0  0x004f4e03 in db_table_version (dbf=0x78d6e470,
> >connection=0x8175e0, table=0x7f3e124e9b40) at db/db.c:359
> >#1  0x004f51d1 in db_check_table_version (dbf=0x0, dbh=0x0,
> >table=0x7f3e124e9b40, version=7) at db/db.c:398
> >#2  0x7f3e122e585e in mod_init () at uri_mod.c:265
> >#3  0x00493514 in init_mod (m=0x798348) at sr_module.c:457
> >#4  0x004934ac in init_mod (m=0x798418) at sr_module.c:452
> >#5  0x004934ac in init_mod (m=0x7984e8) at sr_module.c:452
> >#6  0x004934ac in init_mod (m=0x7985b8) at sr_module.c:452
> >#7  0x004934ac in init_mod (m=0x798688) at sr_module.c:452
> >#8  0x004934ac in init_mod (m=0x798758) at sr_module.c:452
> >#9  0x004934ac in init_mod (m=0x798828) at sr_module.c:452
> >#10 0x004934ac in init_mod (m=0x7988f8) at sr_module.c:452
> >#11 0x004934ac in init_mod (m=0x7989c8) at sr_module.c:452
> >#12 0x004934ac in init_mod (m=0x798a98) at sr_module.c:452
> >#13 0x004934ac in init_mod (m=0x798b68) at sr_module.c:452
> >#14 0x004934ac in init_mod (m=0x798c38) at sr_module.c:452
> >#15 0x004934ac in init_mod (m=0x798d08) at sr_module.c:452
> >#16 0x004934ac in init_mod (m=0x798dd8) at sr_module.c:452
> >#17 0x004934ac in init_mod (m=0x798ea8) at sr_module.c:452
> >#18 0x004934ac in init_mod (m=0x798f78) at sr_module.c:452
> >#19 0x004934ac in init_mod (m=0x799048) at sr_module.c:452
> >#20 0x004934ac in init_mod (m=0x799118) at sr_module.c:452
> >#21 0x004934ac in init_mod (m=0x7991e8) at sr_module.c:452
> >#22 0x004934ac in init_mod (m=0x799528) at sr_module.c:452
> >#23 0x004934ac in init_mod (m=0x7996c8) at sr_module.c:452
> >#24 0x004934ac in init_mod (m=0x799798) at sr_module.c:452
> >#25 0x004934ac in init_mod (m=0x799868) at sr_module.c:452
> >#26 0x004934ac in init_mod (m=0x799a70) at sr_module.c:452
> >#27 0x004934ac in init_mod (m=0x799b40) at sr_module.c:452
> >#28 0x004934ac in init_mod (m=0x799c10) at sr_module.c:452
> >#29 0x004934ac in init_mod (m=0x799ce0) at sr_module.c:452
> >#30 0x004934ac in init_mod (m=0x799db0) at sr_module.c:452
> >#31 0x004934ac in init_mod (m=0x799e80) at sr_module.c:452
> >#32 0x004934ac in init_mod (m=0x799f50) at sr_module.c:452
> >#33 0x004934ac in init_mod (m=0x79a020) at sr_module.c:452
> >#34 0x0042c4f0 in main (argc=, argv= >optimized out>) at main.c:1351
> >
> >
> >Can you not use NDBCluster with OpenSIPS???
> >--
> >Vie

Re: [OpenSIPS-Users] Virtual_DB issue with NDBClUSTER

[Jeff Pyle]

I use Opensips with NDBCLUSTER, although not with db_virtual.  Seems to
work okay with db_mysql.  To keep things simple, each of my Opensips
machines (VMs, really) has a mysqld instance whose only role is to be a
front-end to the cluster.  I've tried it with CentOS RPMs, Debian (stable)
packages, and 7.1.x source from the MySQL site.  All okay.

Sorry, no further information on the virtual portion.


- Jeff


On 12/14/10 12:35 PM, "osiris123d"  wrote:

>
>I am trying to get OpenSIPS Virtual_DB module to work with a MySQL Cluster
>that I have set up.
>
>Instead of the database tables being the usual MyISAM I set them up to be
>NDBCLUSTER.
>
>Within the OpenSIPS config I have
>
># - db_virtual params -
>modparam("db_virtual", "db_urls", "define set1 ROUND")
>modparam("db_virtual", "db_urls",
>"mysql://:***...@173.***.***.219/opensips")
>modparam("db_virtual", "db_urls",
>"mysql://:***...@173.***.***.218/opensips")
>
>
>To test I shut down the database on the 173.***.***.218 server and
>OpenSIPS
>went down.  When I try to restart OpenSIPS I see the following in the
>syslog
>
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to
>MySQL
>server on '173.***.***.218' (111)
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:db_mysql:db_mysql_new_connection: initial connect failed
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:core:db_do_init: could not add connection to the pool
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:db_virtual:db_virtual_init: cant init db
>mysql://:**...@173.***.***.218/opensips
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:db_mysql:db_mysql_submit_query: driver error: Got error 157 'Unknown
>error code' from NDBCLUSTER
>Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
>ERROR:core:db_do_query: error while submitting query
>Dec 14 11:17:20 Proxy01 kernel: [235305.342266] opensips[3843]: segfault
>at
>20 ip 004f4e03 sp 7fffb3965840 error 4 in
>opensips[40+14d000]
>
>
>
>Looks like it dumped the core and the core says
>
>(gdb) backtrace
>#0  0x004f4e03 in db_table_version (dbf=0x78d6e470,
>connection=0x8175e0, table=0x7f3e124e9b40) at db/db.c:359
>#1  0x004f51d1 in db_check_table_version (dbf=0x0, dbh=0x0,
>table=0x7f3e124e9b40, version=7) at db/db.c:398
>#2  0x7f3e122e585e in mod_init () at uri_mod.c:265
>#3  0x00493514 in init_mod (m=0x798348) at sr_module.c:457
>#4  0x004934ac in init_mod (m=0x798418) at sr_module.c:452
>#5  0x004934ac in init_mod (m=0x7984e8) at sr_module.c:452
>#6  0x004934ac in init_mod (m=0x7985b8) at sr_module.c:452
>#7  0x004934ac in init_mod (m=0x798688) at sr_module.c:452
>#8  0x004934ac in init_mod (m=0x798758) at sr_module.c:452
>#9  0x004934ac in init_mod (m=0x798828) at sr_module.c:452
>#10 0x004934ac in init_mod (m=0x7988f8) at sr_module.c:452
>#11 0x004934ac in init_mod (m=0x7989c8) at sr_module.c:452
>#12 0x004934ac in init_mod (m=0x798a98) at sr_module.c:452
>#13 0x004934ac in init_mod (m=0x798b68) at sr_module.c:452
>#14 0x004934ac in init_mod (m=0x798c38) at sr_module.c:452
>#15 0x004934ac in init_mod (m=0x798d08) at sr_module.c:452
>#16 0x004934ac in init_mod (m=0x798dd8) at sr_module.c:452
>#17 0x004934ac in init_mod (m=0x798ea8) at sr_module.c:452
>#18 0x004934ac in init_mod (m=0x798f78) at sr_module.c:452
>#19 0x004934ac in init_mod (m=0x799048) at sr_module.c:452
>#20 0x004934ac in init_mod (m=0x799118) at sr_module.c:452
>#21 0x004934ac in init_mod (m=0x7991e8) at sr_module.c:452
>#22 0x004934ac in init_mod (m=0x799528) at sr_module.c:452
>#23 0x004934ac in init_mod (m=0x7996c8) at sr_module.c:452
>#24 0x004934ac in init_mod (m=0x799798) at sr_module.c:452
>#25 0x004934ac in init_mod (m=0x799868) at sr_module.c:452
>#26 0x004934ac in init_mod (m=0x799a70) at sr_module.c:452
>#27 0x004934ac in init_mod (m=0x799b40) at sr_module.c:452
>#28 0x004934ac in init_mod (m=0x799c10) at sr_module.c:452
>#29 0x004934ac in init_mod (m=0x799ce0) at sr_module.c:452
>#30 0x004934ac in init_mod (m=0x799db0) at sr_module.c:452
>#31 0x004934ac in init_mod (m=0x799e80) at sr_module.c:452
>#32 0x004934ac in init_mod (m=0x799f50) at sr_module.c:452
>#33 0x004934ac in init_mod (m=0x79a020) at sr_module.c:452
>#34 0x0042c4f0 in main (argc=, argv=optimized out>) at main.c:1351
>
>
>Can you not use NDBCluster with OpenSIPS???
>-- 
>View this message in context:
>http://opensips-open-sip-server.1449251.n2.nabble.com/Virtual-DB-issue-wit
>h-NDBClUSTER-tp5834548p5834548.html
>Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
>
>___
>Users mailing list
>Us

Re: [OpenSIPS-Users] Need some help with NAT/rtpproxy

[James Lamanna]

Does anyone have a working example with fix_nated_register() that they
could post (or email me directly).
I'd really like to see how this is done properly.

Thanks.

-- James

On Mon, Dec 13, 2010 at 5:54 PM, James Lamanna  wrote:
> Some other weird stuff that happens if I remove the fix_nated_register call:
> Sometimes everything will work fine, audio is fine, etc..
> However, sometimes I'll call a phone, and the phone will immediately
> place a call back out to the number I'm dialing from!
> (very strange).
>
> -- James
>
> On Mon, Dec 13, 2010 at 5:28 PM, James Lamanna  wrote:
>> Hi,
>> I'm having some issues getting a correct NAT configuration going.
>> The problem I'm having is
>> I get a "479 We don't forward to private IP addresses" back when
>> receiving a call to a phone from Asterisk, presumably because the
>> location table has private IPs in it for some reason.
>>
>> This seems to be related to my failed attempt to use fix_nated_register().
>> Removing the call to fix_nated_register and just using
>> fix_nated_contact allows calls to go through, but then I get no audio
>> on either side...
>>
>> Config follows.
>>
>> Thanks.
>>
>> -- James
>>
>>
>> debug=3         # debug level (cmd line: -dd)
>> fork=yes
>> log_stderror=no # (cmd line: -E)
>> log_facility=LOG_LOCAL0
>> tos=0x60
>>
>> # Uncomment these lines to enter debugging mode
>> #fork=no
>> #log_stderror=yes
>> #debug=6
>>
>> check_via=no    # (cmd. line: -v)
>> dns=no           # (cmd. line: -r)
>> rev_dns=no      # (cmd. line: -R)
>> port=5060
>> children=4
>>
>> listen=udp:208.xxx.xxx.6:5060
>> listen=udp:208.xxx.xxx.6:5061
>> # -- module loading --
>>
>> #set module path
>> #mpath="/usr/local/lib/opensips/modules/"
>> mpath="/usr/local/lib64/opensips/modules/"
>>
>> # Uncomment this if you want to use SQL database
>> loadmodule "db_mysql.so"
>>
>> loadmodule "sl.so"
>> loadmodule "maxfwd.so"
>> loadmodule "textops.so"
>> loadmodule "avpops.so"
>> loadmodule "tm.so"
>> loadmodule "rr.so"
>> loadmodule "dialog.so"
>> loadmodule "signaling.so"
>> loadmodule "options.so"
>> loadmodule "localcache.so"
>>
>> loadmodule "usrloc.so"
>>
>> loadmodule "presence.so"
>> loadmodule "presence_xml.so"
>> loadmodule "presence_dialoginfo.so"
>> loadmodule "pua.so"
>> loadmodule "pua_dialoginfo.so"
>> #loadmodule "pua_bla.so"
>> loadmodule "pua_usrloc.so"
>>
>> loadmodule "registrar.so"
>> loadmodule "mi_fifo.so"
>> #loadmodule "xlog.so"
>>
>> # Uncomment this if you want digest authentication
>> # db_mysql.so must be loaded !
>> loadmodule "auth.so"
>> loadmodule "auth_db.so"
>>
>> # !! Nathelper
>> loadmodule "nathelper.so"
>>
>>
>> # - setting module-specific parameters ---
>>
>> # -- mi_fifo params --
>> modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo")
>>
>> modparam("usrloc", "db_mode", 2)
>> modparam("usrloc|dialog|dispatcher|presence|presence_xml|pua|avpops",
>>        "db_url", "mysql://opensips:xx...@localhost/opensips")
>>
>>
>> modparam("avpops","avp_table","usr_preferences")
>>
>> #modparam("dispatcher", "force_dst", 1)
>> # Only use username
>> #modparam("dispatcher", "flags", 1)
>>
>> # Store passwords for 1 hour in cache
>>
>> modparam("auth","username_spec","$avp(i:54)")
>> modparam("auth","password_spec","$avp(i:55)")
>> modparam("auth","calculate_ha1",1)
>>
>> modparam("auth_db", "db_url",
>>        "mysql://opensipsro:x...@localhost/opensips")
>> modparam("auth_db", "calculate_ha1", yes)
>> modparam("auth_db", "password_column", "password")
>> modparam("auth_db", "load_credentials", "$avp(i:55)=password")
>>
>> modparam("rr", "enable_full_lr", 1)
>>
>> modparam("dialog", "dlg_flag", 4)
>> modparam("dialog", "profiles_with_value", "caller")
>>
>> modparam("usrloc","nat_bflag",6)
>> modparam("nathelper","sipping_bflag",8)
>> #modparam("nathelper", "natping_interval", 30)
>> modparam("nathelper", "ping_nated_only", 1)   # Ping only clients behind NAT
>> #modparam("nathelper", "natping_interval", 30)
>> modparam("nathelper", "sipping_from", "sip:pin...@208.xxx.xxx.6")
>> modparam("nathelper", "rtpproxy_sock", 
>> "unix:/var/run/rtpproxy/rtpproxy.sock")
>> modparam("nathelper", "received_avp", "$avp(i:42)")
>> modparam("registrar", "received_avp", "$avp(i:42)")
>>
>> modparam("presence", "server_address", "sip:s...@208.xxx.xxx.6:5060")
>> modparam("presence", "expires_offset", 10)
>> modparam("presence", "mix_dialog_presence", 1)
>> #modparam("presence", "fallback2db", 1)
>> modparam("presence_xml", "force_active", 1)
>>
>> modparam("presence_dialoginfo", "force_single_dialog", 1)
>> modparam("pua_dialoginfo", "presence_server", "sip:s...@208.xxx.xxx.6:5060")
>> modparam("pua_dialoginfo", "include_callid", 1)
>> modparam("pua_dialoginfo", "include_tags", 1)
>> modparam("pua_dialoginfo", "caller_confirmed", 1)
>>
>> modparam("pua_usrloc", "default_domain",  "208.xxx.xxx.6")
>> modparam("pua_usrloc", "presence_server", "sip:s...@208.xxx.xxx

[OpenSIPS-Users] Opensips 1.6.3 stable version

[Antonio Anderson Souza]

Dear List,

I'm using Opensips 1.6.3 version from the branch 1.6 [1] in my development
environment, due a patch that it's not available in the stable download [2],
but I'll need to make some installations in production environments, and I'd
like to hear form you guys which is the better choice, use the stable
version[1] and apply only the patch that I need, or use the version in the
branch [2]?

[1] -
http://opensips.org/pub/opensips/1.6.3/src/opensips-1.6.3-notls_src.tar.gz
[2] - http://opensips.svn.sourceforge.net/viewvc/opensips/branches/1.6

Best Regards,


Antonio Anderson Souza

 


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

Re: [OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Stanislaw Pitucha]

- Original message -
> If there are things missing to this new release (code, patches, docs, 
> anything), please let me know.

Hi Bogdan,

I'm not sure if it is in pipeline for merging now or not, but there's a crasher 
with patches available at 
http://sourceforge.net/tracker/?func=detail&aid=3039943&group_id=232389&atid=1086410
 - which isn't in trunk yet. Any chance it will make 1.6.4?

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

[OpenSIPS-Users] Virtual_DB issue with NDBClUSTER

[osiris123d]

I am trying to get OpenSIPS Virtual_DB module to work with a MySQL Cluster
that I have set up.

Instead of the database tables being the usual MyISAM I set them up to be
NDBCLUSTER.

Within the OpenSIPS config I have

# - db_virtual params -
modparam("db_virtual", "db_urls", "define set1 ROUND") 
modparam("db_virtual", "db_urls",
"mysql://:***...@173.***.***.219/opensips")
modparam("db_virtual", "db_urls",
"mysql://:***...@173.***.***.218/opensips")


To test I shut down the database on the 173.***.***.218 server and OpenSIPS
went down.  When I try to restart OpenSIPS I see the following in the syslog

Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to MySQL
server on '173.***.***.218' (111)
Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:db_mysql:db_mysql_new_connection: initial connect failed
Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:core:db_do_init: could not add connection to the pool
Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:db_virtual:db_virtual_init: cant init db
mysql://:**...@173.***.***.218/opensips
Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:db_mysql:db_mysql_submit_query: driver error: Got error 157 'Unknown
error code' from NDBCLUSTER
Dec 14 11:17:20 Proxy01 /usr/local/sbin/opensips[3843]:
ERROR:core:db_do_query: error while submitting query
Dec 14 11:17:20 Proxy01 kernel: [235305.342266] opensips[3843]: segfault at
20 ip 004f4e03 sp 7fffb3965840 error 4 in
opensips[40+14d000]



Looks like it dumped the core and the core says

(gdb) backtrace
#0  0x004f4e03 in db_table_version (dbf=0x78d6e470,
connection=0x8175e0, table=0x7f3e124e9b40) at db/db.c:359
#1  0x004f51d1 in db_check_table_version (dbf=0x0, dbh=0x0,
table=0x7f3e124e9b40, version=7) at db/db.c:398
#2  0x7f3e122e585e in mod_init () at uri_mod.c:265
#3  0x00493514 in init_mod (m=0x798348) at sr_module.c:457
#4  0x004934ac in init_mod (m=0x798418) at sr_module.c:452
#5  0x004934ac in init_mod (m=0x7984e8) at sr_module.c:452
#6  0x004934ac in init_mod (m=0x7985b8) at sr_module.c:452
#7  0x004934ac in init_mod (m=0x798688) at sr_module.c:452
#8  0x004934ac in init_mod (m=0x798758) at sr_module.c:452
#9  0x004934ac in init_mod (m=0x798828) at sr_module.c:452
#10 0x004934ac in init_mod (m=0x7988f8) at sr_module.c:452
#11 0x004934ac in init_mod (m=0x7989c8) at sr_module.c:452
#12 0x004934ac in init_mod (m=0x798a98) at sr_module.c:452
#13 0x004934ac in init_mod (m=0x798b68) at sr_module.c:452
#14 0x004934ac in init_mod (m=0x798c38) at sr_module.c:452
#15 0x004934ac in init_mod (m=0x798d08) at sr_module.c:452
#16 0x004934ac in init_mod (m=0x798dd8) at sr_module.c:452
#17 0x004934ac in init_mod (m=0x798ea8) at sr_module.c:452
#18 0x004934ac in init_mod (m=0x798f78) at sr_module.c:452
#19 0x004934ac in init_mod (m=0x799048) at sr_module.c:452
#20 0x004934ac in init_mod (m=0x799118) at sr_module.c:452
#21 0x004934ac in init_mod (m=0x7991e8) at sr_module.c:452
#22 0x004934ac in init_mod (m=0x799528) at sr_module.c:452
#23 0x004934ac in init_mod (m=0x7996c8) at sr_module.c:452
#24 0x004934ac in init_mod (m=0x799798) at sr_module.c:452
#25 0x004934ac in init_mod (m=0x799868) at sr_module.c:452
#26 0x004934ac in init_mod (m=0x799a70) at sr_module.c:452
#27 0x004934ac in init_mod (m=0x799b40) at sr_module.c:452
#28 0x004934ac in init_mod (m=0x799c10) at sr_module.c:452
#29 0x004934ac in init_mod (m=0x799ce0) at sr_module.c:452
#30 0x004934ac in init_mod (m=0x799db0) at sr_module.c:452
#31 0x004934ac in init_mod (m=0x799e80) at sr_module.c:452
#32 0x004934ac in init_mod (m=0x799f50) at sr_module.c:452
#33 0x004934ac in init_mod (m=0x79a020) at sr_module.c:452
#34 0x0042c4f0 in main (argc=, argv=) at main.c:1351


Can you not use NDBCluster with OpenSIPS???
-- 
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Virtual-DB-issue-with-NDBClUSTER-tp5834548p5834548.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

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

Re: [OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Bogdan-Andrei Iancu]

Hi Ovidiu,

Thanks for the reminder - I will look into that!

Regards,
Bogdan

Ovidiu Sas wrote:

There are a few things that needs to be fixed before the release:
 - final replies for INVITE does not show up in the b2b_entities reply route;
 - sometimes there are retransmissions for PUBLISH requests (I will
provide you with logs for this one).

Regards,
Ovidiu Sas

On Tue, Dec 14, 2010 at 8:21 AM, Bogdan-Andrei Iancu
 wrote:
  

Hi everyone,

we are in full progress of fixing the last bugs, of doing all backports from
devel version, of uploading the last patches.and testing :) for the new
release.

In the next days I will compile a list of all changes and improvements of
this release - I will send you the link once ready.

From timeline point of view :

  - Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
  - testing and packaging update
  - *Monday 20 Dec - official release*.

If there are things missing to this new release (code, patches, docs,
anything), please let me know.


Best regards,
Bogdan

___
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

  



--
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
www.voice-system.ro


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

[OpenSIPS-Users] [EVENT] OpenSIPS Miami 2011 event - expo, conf, social, bootcamp

[Bogdan-Andrei Iancu]

Hi all,
I'm glad to present a major and mix OpenSIPS event that will open
the 2011 year : OpenSIPS Miami 2011 Event.
The OpenSIPS Miami 2011 event will
consist out of:


  ITExpo exhibiting - visit OpenSIPS booth #530
  
  ITExpo Open Source panel conference- presenting the
OpenSIPS project - where to head?
  
  OpenSIPS social event - an opportunity to meet face
to face people involved with the project or people who like it
  
  OpenSIPS bootcamp training
- a 5 days training for OpenSIPS




1.  ITExpo exhibiting 
OpenSIPS project will be present with booth
#530 at ITExpo Conference and Expo Event on February
2-4, 2011, Miami, US ( http://www.itexpo.com/
).

The main goal on the project side is to present the
capabilities provided by OpenSIPS as a multi-purpose
SIP server:


  What scenarios OpenSIPS is suitable for
  
  What are the OpenSIPS features and scalability
  
  How to use OpenSIPS project - getting support for community 
  How OpenSIPS fits in the VOIP industry
  
  OpenSIPS based solutions - production ready 


2.  Conference 
During the developers panel, Bogdan-Andrei Iancu will have a
presentation about OpenSIPS projects, about OpenSIPS vision and goals
in VoIP world, about the new upcoming OpenSIPS 2.0 - a radical and
cutting-edge design and implementation for a SIP server.


3.  Social Event 
During the weekend following ITExpo (exact date will follow), an OpenSIPS
social event will take place. The purpose of this event is to
allow people involved in the project to meet, discuss and have fun.

This is an do what ever you like
event where developers, community people, users, fans, etc will get
together, talk (even about project 
:-)  ), have fun, etc. It will be an
opportunity to get get together and meet the peoples behind the names
(on mailing list, trackers, forums, IRC, etc). Also, this event will be
the kick-off meeting for the "OpenSIPS Foundation" (I will come back
with more infos on this).

The event will take place at  Dave & Buster's ,
with food, drinks, billiards and others. 
To attend, you need to let us know, by registering
(Registration form will be short available, in the mean while send an
email to bo...@opensips.org or fla...@opensips.org )



4.  OpenSIPS Bootcamp
In the week following ITExpo, the OpenSIPS bootcamp training session
will take place. See more on the training official page.




Best regards and hope to see you in Miami!
Bogdan
-- 
Bogdan-Andrei Iancu
OpenSIPS Event - expo, conf, social, bootcamp
2 - 4 February 2011, ITExpo, Miami,  USA
www.voice-system.ro




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

Re: [OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Taisto Qvist (WM)]

What about the issues I had with serial forking that I wrote to you
about? Will they make it into 1.6.4?
You fixed the core functionality so that serial forking worked 
somewhat,

but to get my "dream scenario", I needed some tweaks for the
return-codes of of serialize_branches.

This is what I wrote:

A few notes though. It seems like I need the serialize_branches()
to return a useful returncode as well. Otherwise my script cannot
differentiate between when serialforking really is being done, or
when normal proxy or parallell fork is in progress. (In which case
I wanted normal timer C) Returning 1 in the end of serialize.c, ´
instead of 0 which is returned when nothing is performed by the call
to serialize_branches() took care of that.
This cause action.c do LOG_ERR though, so I changed that to only
log error if the return from serialize_branches was < 0.

Regards
Taisto Qvist



On Tue, 14 Dec 2010 15:21:46 +0200, Bogdan-Andrei Iancu 
 wrote:

Hi everyone,

we are in full progress of fixing the last bugs, of doing all
backports from devel version, of uploading the last patches.and
testing :) for the new release.

In the next days I will compile a list of all changes and
improvements of this release - I will send you the link once ready.

From timeline point of view :

   - Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
   - testing and packaging update
   - *Monday 20 Dec - official release*.

If there are things missing to this new release (code, patches, docs,
anything), please let me know.


Best regards,
Bogdan

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


--
Taisto Qvist, IP-Solutions
Mobile: +46-708-88 02 63
"We are Pentium of Borg. Division is futile, You will be approximated"

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

Re: [OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Erik Dekkers]

Bogdan,

Thnx for the update. 

Kind regards,

Erik

-Oorspronkelijk bericht-
Van: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] 
Namens Bogdan-Andrei Iancu
Verzonden: dinsdag 14 december 2010 14:22
Aan: users@lists.opensips.org; de...@lists.opensips.org; n...@lists.opensips.org
Onderwerp: [OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

Hi everyone,

we are in full progress of fixing the last bugs, of doing all backports from 
devel version, of uploading the last patches.and testing :) for the new 
release.

In the next days I will compile a list of all changes and improvements of this 
release - I will send you the link once ready.

 From timeline point of view :

- Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
- testing and packaging update
- *Monday 20 Dec - official release*.

If there are things missing to this new release (code, patches, docs, 
anything), please let me know.


Best regards,
Bogdan

___
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] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Ovidiu Sas]

There are a few things that needs to be fixed before the release:
 - final replies for INVITE does not show up in the b2b_entities reply route;
 - sometimes there are retransmissions for PUBLISH requests (I will
provide you with logs for this one).

Regards,
Ovidiu Sas

On Tue, Dec 14, 2010 at 8:21 AM, Bogdan-Andrei Iancu
 wrote:
> Hi everyone,
>
> we are in full progress of fixing the last bugs, of doing all backports from
> devel version, of uploading the last patches.and testing :) for the new
> release.
>
> In the next days I will compile a list of all changes and improvements of
> this release - I will send you the link once ready.
>
> From timeline point of view :
>
>   - Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
>   - testing and packaging update
>   - *Monday 20 Dec - official release*.
>
> If there are things missing to this new release (code, patches, docs,
> anything), please let me know.
>
>
> Best regards,
> Bogdan
>
> ___
> 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] Opensips SNMP

[Wesley Volcov]

Hey,

I use cacti and nagios to monitor my opensips server with snmp protocol.

What do you need?

On 14 December 2010 00:29, sergio  wrote:

> Hello list,
>
> Has anyone used MRTG with SNMP and CACTI to monitor OpenSIPS?
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
Wesley Volcov
Email: wesleyvol...@gmail.com
Messenger: vol...@live.com
Mobile: +55 11 9989-5348
Website: http://volcov.blogspot.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] drouting module 1.6.3 with b2b

[Anton Zagorskiy]

Yes, openSIPS crashed because of there are "INFO:core:sig_usr: signal 15
received" messages in a log file.
I've tested on new VM with CentOS 5.5 with sources from svn stable release

Please see bt and bt full results in the attach.


Code:

route
{
[skipped]

if (!do_routing())
{
xlog("*** !!! route[invite]: No rules found for do_routing().
STOP");
send_reply("503", "Error");
exit;
};
xlog("*** route[invite]: do_routing() passed");
xlog("*** route[invite]: dr_attrs: $avp(s:dr_attrs); ruri:
$avp(s:dr_ruri)");
route(main_route);

[skipped]
}



route[main_route]
{
xlog("*** +++ route[main_route] has started");

if (is_method("INVITE"))
{
t_on_branch("2");
t_on_reply("2");
t_on_failure("1");
};

if (!t_relay())
{
sl_reply_error();
};

xlog("*** --- route[main_route] has finished");
}





WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru


> -Original Message-
> From: users-boun...@lists.opensips.org [mailto:users-
> boun...@lists.opensips.org] On Behalf Of Bogdan-Andrei Iancu
> Sent: Tuesday, December 14, 2010 4:25 PM
> To: OpenSIPS users mailling list
> Subject: Re: [OpenSIPS-Users] drouting module 1.6.3 with b2b
> 
> Hi Anton,
> 
> Why do you say it crashes ? do you have a corefile ?
> 
> your logs do not show any t_relay() after do_routing()could you
> post
> the relevant snip of your cfg?
> 
> Regards,
> Bogdan
> 
> Anton Zagorskiy wrote:
> > Hi!
> >
> > I'm trying to use drouting module, but something says to me that I
> using it
> > wrong because openSIPS goes to crash.
> >
> > I've inserted following values in the DB:
> >
> > 1. dr_gateways:
> >
> > gwid(2)
> > type(1)
> > address(192.168.0.10)
> > strip(0)
> > pri_prefix(1000)
> > attrs("")
> > probe_mode(0)
> > description(Gateway1)
> >
> > 2. dr_groups:
> > id(1)
> > username(100)
> > domain(mydomain.com)
> > groupid(1)
> > description(All-Test)
> >
> > 3. dr_gw_lists:
> > id(2)
> > gwlist(2)
> > description(Test)
> >
> > 4. dr_rules:
> > ruleid(1)
> > groupid(1)
> > prefix(89112599077)
> > timerec("")
> > priority(1)
> > routeid("")
> > gwlist(#2)
> > description(Test)
> > attrs("")
> >
> >
> > So, I'm calling from 1...@mydomain.com to 89112599077.
> > I'm expecting that this will be routed to 192.168.0.10 with R-URI
> > 100089112599...@.. Right?
> >
> > But when I'm calling do_routing() the same INVITE is passed to the
> main
> > route block and I'm again calling do_routing (Nothing changed in the
> script
> > :)) and opensips is crashing...
> >
> > Log file hasn't helpful messages:
> >
> > [8031]: *** route[invite]: call do_routing()
> > [8031]: DBG:core:db_new_result: allocate 28 bytes for result set at
> > 0x81ddb78
> > [8031]: DBG:db_mysql:db_mysql_get_columns: 1 columns returned from
> the query
> > [8031]: DBG:core:db_allocate_columns: allocate 16 bytes for result
> columns
> > at 0x81ddba4
> > [8031]: DBG:db_mysql:db_mysql_get_columns:
> RES_NAMES(0x81ddba8)[0]=[groupid]
> > [8031]: DBG:db_mysql:db_mysql_get_columns: use DB_INT result type
> > [8031]: DBG:core:db_allocate_rows: allocate 28 bytes for result rows
> and
> > values at 0x81ddbd0
> > [8031]: DBG:db_mysql:db_mysql_str2val: converting INT [1]
> > [8031]: DBG:core:db_free_columns: freeing result columns at 0x81ddba4
> > [8031]: DBG:core:db_free_rows: freeing 1 rows
> > [8031]: DBG:core:db_free_row: freeing row values at 0x81ddbd8
> > [8031]: DBG:core:db_free_rows: freeing rows at 0x81ddbd0
> > [8031]: DBG:core:db_free_result: freeing result set at 0x81ddb78
> > [8031]: DBG:drouting:do_routing: using dr group 1
> > [8031]: DBG:drouting:internal_check_rt: found rgid 1 (rule list
> 0xb60c0d0c)
> > [8034]: DBG:tm:utimer_routine: timer routine:4,tl=0xb60c34b4
> next=(nil),
> > timeout=1190
> > [8034]: DBG:tm:retransmission_handler: retransmission_handler :
> request
> > resending (t=0xb60c3368, INVITE si ... )
> > [8034]: DBG:tm:set_timer: relative timeout is 200
> > [8034]: DBG:tm:insert_timer_unsafe: [5]: 0xb60c34b4 (1390)
> > [8034]: DBG:tm:retransmission_handler: retransmission_handler : done
> > [8032]: DBG:core:parse_msg: SIP Request:
> > [8032]: DBG:core:parse_msg:  method:   (# The same INVITE is
> > coming!)
> >
> > What I'm doing wrong?
> >
> >
> 
> 
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
bt:
#0  0x00503f9c in do_routing (msg=0x81ebec0, drg=, 
sort_order=0) at drouting.c:1005
#1  0x08054d4a in do_action (a=0x81e1648, msg=0x81ebec0) at action.c:1195
#2  0x08058ec9 in run_action_list (a=0x81e1648, msg=0x81ebec0) at action.c:140
#3  0x080b25f8 in eval_elem (e=0x81e16b4, msg=0x0, val=0x0) at route.c:1354
#4  0x080b51d8 in eval_expr (e=0x81e16b4, msg=0x81ebec0, val=0x0) at 
route.c:16

Re: [OpenSIPS-Users] drouting module 1.6.3 with b2b

[Bogdan-Andrei Iancu]

Hi Anton,

Why do you say it crashes ? do you have a corefile ?

your logs do not show any t_relay() after do_routing()could you post 
the relevant snip of your cfg?


Regards,
Bogdan

Anton Zagorskiy wrote:

Hi!

I'm trying to use drouting module, but something says to me that I using it
wrong because openSIPS goes to crash.

I've inserted following values in the DB:

1. dr_gateways:

gwid(2)
type(1)
address(192.168.0.10)
strip(0)
pri_prefix(1000)
attrs("")
probe_mode(0)
description(Gateway1)

2. dr_groups:
id(1)
username(100)
domain(mydomain.com)
groupid(1)
description(All-Test)

3. dr_gw_lists:
id(2)
gwlist(2)
description(Test)

4. dr_rules:
ruleid(1)
groupid(1)
prefix(89112599077)
timerec("")
priority(1)
routeid("")
gwlist(#2)
description(Test)
attrs("")


So, I'm calling from 1...@mydomain.com to 89112599077.
I'm expecting that this will be routed to 192.168.0.10 with R-URI
100089112599...@.. Right?

But when I'm calling do_routing() the same INVITE is passed to the main
route block and I'm again calling do_routing (Nothing changed in the script
:)) and opensips is crashing...

Log file hasn't helpful messages:

[8031]: *** route[invite]: call do_routing()
[8031]: DBG:core:db_new_result: allocate 28 bytes for result set at
0x81ddb78
[8031]: DBG:db_mysql:db_mysql_get_columns: 1 columns returned from the query
[8031]: DBG:core:db_allocate_columns: allocate 16 bytes for result columns
at 0x81ddba4
[8031]: DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x81ddba8)[0]=[groupid]
[8031]: DBG:db_mysql:db_mysql_get_columns: use DB_INT result type
[8031]: DBG:core:db_allocate_rows: allocate 28 bytes for result rows and
values at 0x81ddbd0
[8031]: DBG:db_mysql:db_mysql_str2val: converting INT [1]
[8031]: DBG:core:db_free_columns: freeing result columns at 0x81ddba4
[8031]: DBG:core:db_free_rows: freeing 1 rows
[8031]: DBG:core:db_free_row: freeing row values at 0x81ddbd8
[8031]: DBG:core:db_free_rows: freeing rows at 0x81ddbd0
[8031]: DBG:core:db_free_result: freeing result set at 0x81ddb78
[8031]: DBG:drouting:do_routing: using dr group 1
[8031]: DBG:drouting:internal_check_rt: found rgid 1 (rule list 0xb60c0d0c)
[8034]: DBG:tm:utimer_routine: timer routine:4,tl=0xb60c34b4 next=(nil),
timeout=1190
[8034]: DBG:tm:retransmission_handler: retransmission_handler : request
resending (t=0xb60c3368, INVITE si ... )
[8034]: DBG:tm:set_timer: relative timeout is 200
[8034]: DBG:tm:insert_timer_unsafe: [5]: 0xb60c34b4 (1390)
[8034]: DBG:tm:retransmission_handler: retransmission_handler : done
[8032]: DBG:core:parse_msg: SIP Request:
[8032]: DBG:core:parse_msg:  method:   (# The same INVITE is
coming!)

What I'm doing wrong?

  



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

[OpenSIPS-Users] [UPDATE] OpenSIPS 1.6.4 release - timeline

[Bogdan-Andrei Iancu]

Hi everyone,

we are in full progress of fixing the last bugs, of doing all backports 
from devel version, of uploading the last patches.and testing :) for 
the new release.


In the next days I will compile a list of all changes and improvements 
of this release - I will send you the link once ready.


From timeline point of view :

   - Wednesday 15 Dec - hour 24:00 UTC - SVN freeze
   - testing and packaging update
   - *Monday 20 Dec - official release*.

If there are things missing to this new release (code, patches, docs, 
anything), please let me know.



Best regards,
Bogdan

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

[OpenSIPS-Users] drouting module 1.6.3 with b2b

[Anton Zagorskiy]

Hi!

I'm trying to use drouting module, but something says to me that I using it
wrong because openSIPS goes to crash.

I've inserted following values in the DB:

1. dr_gateways:

gwid(2)
type(1)
address(192.168.0.10)
strip(0)
pri_prefix(1000)
attrs("")
probe_mode(0)
description(Gateway1)

2. dr_groups:
id(1)
username(100)
domain(mydomain.com)
groupid(1)
description(All-Test)

3. dr_gw_lists:
id(2)
gwlist(2)
description(Test)

4. dr_rules:
ruleid(1)
groupid(1)
prefix(89112599077)
timerec("")
priority(1)
routeid("")
gwlist(#2)
description(Test)
attrs("")


So, I'm calling from 1...@mydomain.com to 89112599077.
I'm expecting that this will be routed to 192.168.0.10 with R-URI
100089112599...@.. Right?

But when I'm calling do_routing() the same INVITE is passed to the main
route block and I'm again calling do_routing (Nothing changed in the script
:)) and opensips is crashing...

Log file hasn't helpful messages:

[8031]: *** route[invite]: call do_routing()
[8031]: DBG:core:db_new_result: allocate 28 bytes for result set at
0x81ddb78
[8031]: DBG:db_mysql:db_mysql_get_columns: 1 columns returned from the query
[8031]: DBG:core:db_allocate_columns: allocate 16 bytes for result columns
at 0x81ddba4
[8031]: DBG:db_mysql:db_mysql_get_columns: RES_NAMES(0x81ddba8)[0]=[groupid]
[8031]: DBG:db_mysql:db_mysql_get_columns: use DB_INT result type
[8031]: DBG:core:db_allocate_rows: allocate 28 bytes for result rows and
values at 0x81ddbd0
[8031]: DBG:db_mysql:db_mysql_str2val: converting INT [1]
[8031]: DBG:core:db_free_columns: freeing result columns at 0x81ddba4
[8031]: DBG:core:db_free_rows: freeing 1 rows
[8031]: DBG:core:db_free_row: freeing row values at 0x81ddbd8
[8031]: DBG:core:db_free_rows: freeing rows at 0x81ddbd0
[8031]: DBG:core:db_free_result: freeing result set at 0x81ddb78
[8031]: DBG:drouting:do_routing: using dr group 1
[8031]: DBG:drouting:internal_check_rt: found rgid 1 (rule list 0xb60c0d0c)
[8034]: DBG:tm:utimer_routine: timer routine:4,tl=0xb60c34b4 next=(nil),
timeout=1190
[8034]: DBG:tm:retransmission_handler: retransmission_handler : request
resending (t=0xb60c3368, INVITE si ... )
[8034]: DBG:tm:set_timer: relative timeout is 200
[8034]: DBG:tm:insert_timer_unsafe: [5]: 0xb60c34b4 (1390)
[8034]: DBG:tm:retransmission_handler: retransmission_handler : done
[8032]: DBG:core:parse_msg: SIP Request:
[8032]: DBG:core:parse_msg:  method:   (# The same INVITE is
coming!)

What I'm doing wrong?




WBR, Anton Zagorskiy
VoIP Developer, Oyster Telecom
Phone.: +7 812 601-0666
Fax: +7 812 601-0593
a.zagors...@oyster-telecom.ru
www.oyster-telecom.ru





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