My earlier mail, bounced because of size limit.. sending again without the log file. (Please check below). I will send the attachment (37Kb) to you in second mail. Please take a look.
Thanks, Visu M ---------- Forwarded message ---------- From: Visu.M <[email protected]> Date: Thu, Feb 26, 2009 at 4:35 PM Subject: Re: [OpenSIPS-Users] Reg: help needed to get RLS module working To: Anca Vamanu <[email protected]> Cc: [email protected] Thanks Anca for looking into the problem. Here are the details you asked for. I earlier didn't include the fallback2db parameter. now included it. Now, the error changes to "ERROR:presence:get_database_info: No matching subscription dialog found in database" Here is my Config file: #--rls parameters -- modparam("rls","db_url", "mysql://opensips:opensip...@localhost/opensips") modparam("rls", "server_address", "sip:128.61.113.210:5060") modparam("rls", "xcap_root", "http://128.61.113.210/xcap-root:80";) modparam("rls|presence_xml", "integrated_xcap_server", 1) modparam("rls", "presence_server", "sip:128.61.113.210:5060") modparam("rls", "to_presence_code", 10) modparam("rls", "waitn_time", 10) # ----- presence params ----- /* uncomment the following lines if you want to enable presence */ modparam("presence|presence_xml", "db_url", "mysql://opensips:opensip...@localhost/opensips") modparam("presence_xml", "force_active", 0) modparam("presence", "server_address", "sip:128.61.113.210:5060") #-- mi_xmlrpc params -- /*set the same port in OpenXCAP configuration file*/ modparam("mi_xmlrpc","port", 8081) #--pua parameters -- modparam("pua","db_url","mysql://opensips:opensip...@localhost/opensips") ----------------------------------*-------------------------------------- Also, another thing, I noted. In watcher info of cnn which is buddy of 'alice', alice was listed when I first subscribe to the list. But subsequently from the next notify, 'alice' disappears from that list. ---- Received NOTIFY: ---- Active watchers: sip:[email protected] <sip%[email protected]> Terminated watchers: Pending watchers: Waiting watchers: ---- Received NOTIFY: ---- Active watchers: Terminated watchers: Pending watchers: Waiting watchers: ---- -----------------------------&;-------------------------- Log file is attached with the mail. It contains log from "DBG:core:parse_msg: method: <SUBSCRIBE>" with the first occurrence of the error. ------------------------------------------------*-------------------------------------------------- Log of sip trace for alice-buddies. (adding the last notify message. other notify's are similar in content) ---------------------------------------------------*------------------------------------------- SENDING: Packet 24, +0:24:35.137175 2009-02-26 16:31:21.812429: 128.61.113.210:59003 -(UDP)-> 128.61.113.210:5060 SIP/2.0 200 OK^M Via: SIP/2.0/UDP 128.61.113.210;received=128.61.113.210;branch=z9hG4bK0.2a071b83.0^M Call-ID: I3mLPr-0nQkBLFy6swEoAI3NxNQxGFHx^M From: <sip:[email protected] <sip%[email protected]> >;tag=10.19334.1235682406.1^M To: <sip:[email protected] <sip%[email protected]> >;tag=EtLEID3iRHnpXSPQXBwo.JW3UjEfawbp^M CSeq: 6 NOTIFY^M Contact: <sip:[email protected]:59003;transport=udp>^M Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, MESSAGE^M Supported: 100rel^M Content-Length: 0^M Please let me know, if I need to add any other details. Thanks, Visu On Thu, Feb 26, 2009 at 1:23 PM, Anca Vamanu <[email protected]> wrote: > Hi Visu, > > I have now tested RLS for 1.4.X branch and sipsimpleclient and did not saw > that error. Please give me more details. > What is the configuration that you use? Do you set the fallback2db > parameter? Best if you print here the parameters for presence and rls > modules. > Also can you please increase the debug level to 6 and the print here the > part of the log that contains the errors - for that process begining with > the processing of the message - you should search upwards for a line > containing DBG:core:parse_msg: method: <SUBSCRIBE>. > > regards, > Anca > > > Visu.M wrote: > >> Hi, >> >> Folks, I am using opensips with rls module integrated with openxcap >> server. Client is sipsimpleclient. >> I am playing around RLS and openXCAP to see the basic functionality of RLS >> module. >> >> I created a buddy list for 'alice' with two buddies. I am able to >> subscribe to the buddy list. >> But, when one of the buddy publishes it presence information, 'alice' is >> not receiving any notifications. >> >> On checking through the server logs, I am getting the following error >> message in the server. >> Here the info says that alice subscription has got expanded. >> subsequent message says that send notify request to alice on behalf of one >> of the buddy. But no notification is received in the client. >> Then the error message and notification cycle continues. >> >> I am using 1.4.4 version of Opensips. Can someone throw some light? >> Is the issue with config file (I dont think so) or is it some other error. >> Please let me know. >> >> Thanks, >> Visu M >> >> " >> Feb 26 11:54:22 [7906] INFO:rls:resource_subscriptions: Subscription from >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for resource >> list uri >> sip:[email protected]<sip%[email protected]><mailto: >> sip%[email protected] <sip%[email protected]>> >> expanded to 2 contacts >> Feb 26 11:54:22 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:54:22 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> Feb 26 11:54:22 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:54:22 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> Feb 26 11:54:22 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event presence >> Feb 26 11:54:22 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence" >> >> sometimes, I get this error as well, "Feb 26 12:44:03 [7918] >> ERROR:rls:rls_notify_callback: record not found in hash table". >> >> >> ------------------complete Log file------------------ >> Feb 26 11:40:12 [7906] WARNING:core:main: no fork mode >> Feb 26 11:40:12 [7906] INFO:core:init_tcp: using epoll_lt as the TCP io >> watch method (auto detected) >> Feb 26 11:40:12 [7906] NOTICE:core:main: version: opensips 1.4.4-notls >> (i386/linux) >> Feb 26 11:40:12 [7906] INFO:core:main: using 32 Mb shared memory >> Feb 26 11:40:12 [7906] INFO:core:main: using 1 Mb private memory per >> process >> Feb 26 11:40:12 [7906] INFO:sl:mod_init: Initializing StateLess engine >> Feb 26 11:40:12 [7906] INFO:tm:mod_init: TM - initializing... >> Feb 26 11:40:12 [7906] INFO:maxfwd:mod_init: initializing... >> Feb 26 11:40:12 [7906] INFO:usrloc:ul_init_locks: locks array size 512 >> Feb 26 11:40:12 [7906] INFO:registrar:mod_init: initializing... >> Feb 26 11:40:12 [7906] INFO:textops:mod_init: initializing... >> Feb 26 11:40:12 [7906] INFO:xlog:mod_init: initializing... >> Feb 26 11:40:12 [7906] INFO:acc:mod_init: initializing... >> Feb 26 11:40:12 [7906] NOTICE:presence:mod_init: initializing module ... >> Feb 26 11:40:13 [7906] INFO:core:probe_max_receive_buffer: using a UDP >> receive buffer of 255 kb >> Feb 26 11:40:13 [7918] NOTICE:presence:child_init: init_child [-1] pid >> [7918] >> Feb 26 11:40:13 [7919] INFO:mi_xmlrpc:xmlrpc_process: starting xmlrpc >> server >> Feb 26 11:40:13 [7906] NOTICE:presence:child_init: init_child [1] pid >> [7906] >> Feb 26 11:46:59 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:36252;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence >> Feb 26 11:49:27 [7906] INFO:rls:resource_subscriptions: Subscription from >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for resource >> list uri >> sip:[email protected]<sip%[email protected]><mailto: >> sip%[email protected] <sip%[email protected]>> >> expanded to 2 contacts >> Feb 26 11:49:27 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event presence >> Feb 26 11:49:27 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event presence >> Feb 26 11:50:31 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:36762;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence.winfo >> Feb 26 11:51:31 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:49318;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence.winfo >> Feb 26 11:53:33 [7918] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:36252;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence >> Feb 26 11:54:22 [7906] INFO:rls:resource_subscriptions: Subscription from >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for resource >> list uri >> sip:[email protected]<sip%[email protected]><mailto: >> sip%[email protected] <sip%[email protected]>> >> expanded to 2 contacts >> Feb 26 11:54:22 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:54:22 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> Feb 26 11:54:22 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:54:22 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> Feb 26 11:54:22 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event presence >> Feb 26 11:54:22 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via sip: >> 128.61.113.210:5060 <http://128.61.113.210:5060> on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event presence >> Feb 26 11:55:26 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:36762;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence.winfo >> Feb 26 11:56:26 [7906] INFO:presence:send_notify_request: NOTIFY >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> via >> sip:[email protected]:49318;transport=udp on behalf of >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for event >> presence.winfo >> Feb 26 11:59:17 [7906] INFO:rls:resource_subscriptions: Subscription from >> sip:[email protected] <sip%[email protected]> <mailto: >> sip%[email protected] <sip%[email protected]>> for resource >> list uri >> sip:[email protected]<sip%[email protected]><mailto: >> sip%[email protected] <sip%[email protected]>> >> expanded to 2 contacts >> Feb 26 11:59:17 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:59:17 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> Feb 26 11:59:17 [7906] ERROR:presence:get_stored_info: record not found in >> hash_table >> Feb 26 11:59:17 [7906] ERROR:presence:handle_subscribe: getting stored >> info >> >> ---------------------------*---------------------------------------------------------- >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [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
