Hi Bogdan, No, I don't see any errors like that.
Below is the result of cat /var/log/messages after starting opensips and placing one call: Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: NOTICE:core:main: version: opensips 1.8.1-notls (i386/linux) Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:main: using 32 Mb shared memory Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:main: using 2 Mb private memory per process Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:maxfwd:mod_init: initializing... Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:sl:mod_init: Initializing StateLess engine Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:tm:mod_init: TM - initializing... Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: NOTICE:signaling:mod_init: initializing module ... Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:options:mod_init: initializing... Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:sipmsgops:mod_init: initializing... Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:probe_max_sock_buff: using rcv buffer of 512 kb Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:probe_max_sock_buff: using snd buffer of 255 kb Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket Sep 3 09:57:58 BARNEY opensips: INFO:core:daemonize: pre-daemon process exiting with 0 Sep 3 10:04:38 BARNEY /usr/local/sbin/opensips[11505]: INFO:core:probe_max_sock_buff: using snd buffer of 255 kb Sep 3 10:04:38 BARNEY /usr/local/sbin/opensips[11505]: INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket Sep 3 10:04:38 BARNEY /usr/local/sbin/opensips[11501]: ERROR:core:new_avp: invalid AVP name! Sep 3 10:04:38 BARNEY /usr/local/sbin/opensips[11501]: ERROR:core:add_avp: Failed to create new avp structure Thanks Diego On Mon, Sep 3, 2012 at 11:23 AM, Bogdan-Andrei Iancu <[email protected]>wrote: > ** > Diego, what about : do you see any error actually reported by the > dispatcher module (should look like "ERROR:dispatcher:......") . > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > > On 09/03/2012 05:07 PM, Diego Barberio wrote: > > Hi Bogdan, > > Thanks for your response. The errrors only pop up when doing > ds_select_dst() > > I'm able to reproduce this problem in my lab with only one destination and > using mysql as database. I left the "socket" field in (null) and "attrs" is > an empty string > It seems the startup is ok: > > Sep 3 09:57:58 BARNEY opensips: WARNING:core:fix_socket_list: could not > rev. resolve 192.168.2.154 > Sep 3 09:57:58 BARNEY opensips: WARNING:core:fix_socket_list: could not > rev. resolve 192.168.2.154 > Sep 3 09:57:58 BARNEY opensips: INFO:core:init_tcp: using epoll_lt as the > TCP io watch method (auto detected) > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: NOTICE:core:main: > version: opensips 1.8.1-notls (i386/linux) > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:main: > using 32 Mb shared memory > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:core:main: > using 2 Mb private memory per process > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:maxfwd:mod_init: initializing... > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:sl:mod_init: > Initializing StateLess engine > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: INFO:tm:mod_init: > TM - initializing... > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > NOTICE:signaling:mod_init: initializing module ... > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:options:mod_init: initializing... > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:sipmsgops:mod_init: initializing... > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:core:probe_max_sock_buff: using rcv buffer of 512 kb > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:core:probe_max_sock_buff: using snd buffer of 255 kb > Sep 3 09:57:58 BARNEY /usr/local/sbin/opensips[11491]: > INFO:core:init_sock_keepalive: -- TCP keepalive enabled on socket > Sep 3 09:57:58 BARNEY opensips: INFO:core:daemonize: pre-daemon process > exiting with 0 > > Also the destinations list seems to be ok: > > [root@BARNEY opensips]# opensipsctl fifo ds_list > SET_NO:: 1 > SET:: 1 > URI:: sip:192.168.2.154:5063 flag=A > > > Best Regards > Diego > > On Mon, Sep 3, 2012 at 6:47 AM, Bogdan-Andrei Iancu > <[email protected]>wrote: > >> Hi Diego, >> >> So, the opensips startup is ok (with no errors or so) ? Are the >> destinations loaded correctly (check with opensipsctl via fifo) >> >> The errors you mentioned pop up only when doing ds_select_dst() - do you >> see any error actually reported by the dispatcher module (should look like >> "ERROR:dispatcher:......") . >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com >> >> >> On 08/31/2012 09:02 AM, Diego Barberio wrote: >> >> Hello all, >> >> I'm trying to migrate from opensips 1.7.2 to 1.8.1. I only use opensips >> to redirect incomming INVITEs to 3 sets of media servers using dispatcher >> module. >> This is my current dispatcher file: >> >> 1 sip:10.180.12.5:5060 >> 1 sip:10.180.12.13:5060 >> 1 sip:10.180.12.14:5060 >> 1 sip:10.180.12.15:5060 >> 1 sip:10.180.12.16:5060 >> 1 sip:10.180.12.17:5060 >> 1 sip:10.180.12.18:5060 >> 1 sip:10.180.12.19:5060 >> >> 2 sip:10.180.12.21:5060 >> >> 3 sip:10.180.12.21:5061 >> >> >> I still want to use a file for the destinations so I've created the >> dbtext and completed the dispatcher table like this: >> >> id(int,auto) setid(int) destination(string) socket(string,null) >> flags(int) weight(int) attrs(string) description(string) >> 1:1:sip\:10.180.12.5\:5060::0:1:'':'' >> 2:1:sip\:10.180.12.13\:5060::0:1:'':'' >> 3:1:sip\:10.180.12.14\:5060::0:1:'':'' >> 4:1:sip\:10.180.12.15\:5060::0:1:'':'' >> 5:1:sip\:10.180.12.16\:5060::0:1:'':'' >> 6:1:sip\:10.180.12.17\:5060::0:1:'':'' >> 7:1:sip\:10.180.12.18\:5060::0:1:'':'' >> 8:1:sip\:10.180.12.19\:5060::0:1:'':'' >> 9:2:sip\:10.180.12.21\:5060::0:1:'':'' >> 10:3:sip\:10.180.12.21\:5061::0:1:'':'' >> >> However, opensips is returning error when calling to ds_select_dst and I >> see the following repeating errors in "messages" file: >> >> Aug 30 23:43:15 GT-RBT-SIP-1 /usr/local/sbin/opensips[27008]: >> ERROR:core:new_avp: invalid AVP name! >> Aug 30 23:43:15 GT-RBT-SIP-1 /usr/local/sbin/opensips[27006]: >> ERROR:core:add_avp: Failed to create new avp structure >> Aug 30 23:43:15 GT-RBT-SIP-1 /usr/local/sbin/opensips[27007]: >> ERROR:core:add_avp: Failed to create new avp structure >> Aug 30 23:43:15 GT-RBT-SIP-1 /usr/local/sbin/opensips[27009]: >> ERROR:core:new_avp: invalid AVP name! >> >> This is the part of my configuration script where I set up the dispatcher >> module: >> >> # ----------------- setting module-specific parameters --------------- >> >> modparam("db_text", "db_mode", 0) >> >> modparam("mi_fifo", "fifo_name", "/tmp/opensips_fifo") >> >> modparam("tm", "T1_timer", 200) >> >> # -- dispatcher params -- >> modparam("dispatcher", "db_url", "text:///usr/local/etc/opensips/dbtext") >> modparam("dispatcher", "ds_ping_from", "sip:[email protected]") >> modparam("dispatcher", "ds_ping_interval", 10) >> modparam("dispatcher", "ds_probing_mode", 1) >> modparam("dispatcher", "ds_probing_threshhold", 2) >> >> >> Please, could you let me know what am I doing wrong? >> >> Thanks Diego >> >> >> _______________________________________________ >> Users mailing >> [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
