[OpenSIPS-Devel] [ opensips-Bugs-2523454 ] Error in handling rls NOTIFY

SourceForge.net noreply at sourceforge.net
Tue Feb 24 13:55:11 CET 2009


Bugs item #2523454, was opened at 2009-01-20 13:55
Message generated for change (Comment added) made by anca_vamanu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2523454&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nathan (rmnathan)
Assigned to: Anca Vamanu (anca_vamanu)
Summary: Error in handling rls NOTIFY

Initial Comment:
Hi
The following error message are printed while handling rls notify.
Jan 20 06:45:44 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:45:44 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header
Jan 20 06:45:44 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:45:44 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header
Jan 20 06:45:44 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:45:44 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header
Jan 20 06:45:52 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:45:52 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header
Jan 20 06:45:52 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:45:52 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header
Jan 20 06:46:13 [7834] ERROR:core:db_do_insert: invalid parameter value
Jan 20 06:46:13 [7834] ERROR:pua:db_update: while inserting in db table pua
Jan 20 06:46:43 [7834] ERROR:core:parse_uri: uri too short: <> (0)
Jan 20 06:46:43 [7834] ERROR:tm:uri2proxy: bad_uri:
Jan 20 06:46:43 [7834] ERROR:tm:uri2su: failed create a dst proxy
Jan 20 06:46:43 [7834] ERROR:tm:t_uac: no socket found
Jan 20 06:46:43 [7834] ERROR:pua:update_pua: in t_request function
Jan 20 06:46:43 [7834] ERROR:pua:hashT_clean: while updating record
Jan 20 06:47:05 [7833] ERROR:rls:parse_subs_state: terminated state and no reason foundJan 20 06:47:05 [7833] ERROR:rls:rls_handle_notify: while parsing 'Subscription-State' header

Regards,
rmnathan


----------------------------------------------------------------------

>Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-02-24 14:55

Message:
Hi,

You can send me an e-mail at anca at opensips.org.

Anca

----------------------------------------------------------------------

Comment By: Nathan (rmnathan)
Date: 2009-02-24 14:12

Message:
Hi Anca,
can you please send me your mail id or IM id to discuss the issue? 
Regards
rmnathan

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-02-24 13:33

Message:
Hi Rmnathan,

What is the exact role of this scscf? Does is send Notifies with the state
of the clients? 
Please look in the trace that you sent and tell me who sends the Notify
number 119.

regards,
Anca

----------------------------------------------------------------------

Comment By: Nathan (rmnathan)
Date: 2009-02-24 06:31

Message:
Hi
This is also scscf only. it is multiple process running on 192.168.166.150
with different ports for each process (ie for each user).

Thanks
rmnathan

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-02-24 06:30

Message:
Hi
This is also scscf only. it is multiple process running on 192.168.166.150
with different ports for each process (ie for each user).

Thanks
rmnathan

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-02-20 14:09

Message:
Hi,

Can you tell me also what's running at 192.168.166.150:50607? 

thanks,
Anca

----------------------------------------------------------------------

Comment By: Nathan (rmnathan)
Date: 2009-02-20 12:28

Message:
Hi Anca,
You are correct . That is not presence or rls server. It is registrar
(scscf) running on 192.168.166.150:50606. 
Please let me know if you want any information.

Thanks lot
rmnathan

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-02-19 14:03

Message:
Hi Rmnathan,

I looked through your trace but something is confusing.
Can you please tell me what was running on 192.168.166.150 port 50606. I
see that the User-Agent header is OpenSIPS, but the behavior doesn't seem
like that of a presence or rls server.

regards,
Anca

----------------------------------------------------------------------

Comment By: Nathan (rmnathan)
Date: 2009-02-02 11:14

Message:
Hi Anca.
Yes, am using opensips as presence server and rls server. Please find the
logs and pcap file for call flow attached.

Regards,
rmnathan


----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-01-22 15:25

Message:
Hi rmnathan,

Thank you for this report also.
There is something wrong with that Notify that gives this error.
Can you please trace the trafic and catch a Notify that generates this
error and print it here?
This Notify is received from the presence server. Are you using also
OpenSIPS as the presence server? Can you please check is the source IP
address of the Notify message is that of the presence server?

regards,
Anca

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2523454&group_id=232389



More information about the Devel mailing list