Open Source Sip: [OpenSIPStack] WatchRegistrationState ...

9 Replies Last post: Aug 19, 2008 2:44 PM by Guest

Guest

Apr 15, 2008 2:48 AM

[OpenSIPStack] WatchRegistrationState

Hi everyone,

how do I use WatchRegistrationState(const SIPURI & stateAgent, const
SIPURI & resourceURI, const PTimeInterval & expires, const OString &
authUser, const OString & authPassword). What do I have to process to
this call?

Regards,
M. Dreißig

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Guest

1. Apr 15, 2008 3:04 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Matthias Dreißig wrote:

Ouch! This method is an attempt to support RFC 3680 (
http://www.ietf.org/rfc/rfc3680.txt ). I did not get the chance to
revisit this work for a long time so it remains a work in progress at
this point. I am itching to get this supported in OpalOSS and OSBC
though (hint, hint, hint Ilian ;-)) .

Regards,
M. Dreißig

Guest

2. Apr 15, 2008 3:45 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

So there is no support for presence in opensipstack at this time?

Joegen E. Baclor schrieb:

Matthias Dreißig wrote:

Regards,
M. Dreißig

Guest

3. Apr 15, 2008 4:00 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Not at this point. Once upon a time, there were already classes for
parsing PIDF but due to the absence of dedicated manpower, it remained
dormant. I decided to removed them starting version 1.1.4 of OpenSBC.
It has support for messaging though, but not presence. However, it
should be "relatively" easy to create your own presence functionality
using the RFC3256 classes. Feel free to donate your code to the
project if you decide to give it a shot.

Matthias Dreißig wrote:

So there is no support for presence in opensipstack at this time?

Joegen E. Baclor schrieb:

Matthias Dreißig wrote:

Regards,
M. Dreißig

Guest

4. Apr 15, 2008 5:07 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

I'll try to work on this when time permits.

Ilian

Joegen E. Baclor wrote:

Matthias Dreißig wrote:

Regards,
M. Dreißig

Guest

5. Apr 15, 2008 6:36 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

That were nice.

Thanks so far for your answers.

Ilian Jeri C. Pinzon schrieb:

I'll try to work on this when time permits.

Ilian

Joegen E. Baclor wrote:

Matthias Dreißig wrote:

Regards,
M. Dreißig

Guest

6. Aug 19, 2008 10:51 AM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Hello Joegen,

I want to try to create the presence functionality and if it all works
fine I will donate the code to the project.

I have some questions.
Is it possible to get the classes for parsing the xml documents, perhaps
I could reuse it?
Where I could start?
Create SIPSessionManager.
Process events in OpalOSSUserAgent to this SessionManager if method
is SUBSCRIBE or NOTIFY and event is presence.
What I should use from RFC3265 code and what i do not need?
Are the RFC3680 implementations working, so I could see how it has to work?

PS: I found a little bug in RFC3265Client.h see attachment.

Thanks
Matthias

joegen@opensipstack.org schrieb:

So there is no support for presence in opensipstack at this time?

Joegen E. Baclor schrieb:

Matthias Dreißig wrote:

Regards,
M. Dreißig

Index: RFC3265Client.h
===================================================================
RCS file: /cvsroot/opensipstack/opensipstack/include/RFC3265Client.h,v
retrieving revision 1.5
diff -u -r1.5 RFC3265Client.h

RFC3265Client.h 14 Jul 2007 07:50:26 -0000 1.5

+ RFC3265Client.h 19 Aug 2008 14:42:46 -0000
@@ -57,7 +57,7 @@
*/

#ifndef RFC3265CLIENT_H
-#define RFC3265CLEINT_H
+#define RFC3265CLIENT_H

#include "RFC3265ClientManager.h"

This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Guest

7. Aug 19, 2008 12:32 PM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Matthias Dreißig wrote:

Hello Joegen,

I want to try to create the presence functionality and if it all works
fine I will donate the code to the project.

Thats great!

I have some questions.
Is it possible to get the classes for parsing the xml documents,
perhaps I could reuse it?

Of course. There are a lot of modules that demonstrates the use of the
expat wrapper. One good example is OSSAppConfig::CreatePage() where you
can find the code responsible for dynamically creating HTTP admin pages
from oss-application.conf.xml.

Where I could start?
Create SIPSessionManager.
Process events in OpalOSSUserAgent to this SessionManager if method
is SUBSCRIBE or NOTIFY and event is presence.

Before delving into the actual event package, I suggest that you come up
with the PIDF parser classes first and submit them so it can be
reviewed., just as a SIP Stack starts with the parser before delving
into the complexity of state machines

What I should use from RFC3265 code and what i do not need?

Yes. RFC3265 code is pretty much complete in opensipstack.

Are the RFC3680 implementations working, so I could see how it has to
work?

Partially. I won't say it's functional for reasons I have already
stated in this thread.

PS: I found a little bug in RFC3265Client.h see attachment.

Can you give a little explanation what the bug is all about?

Thanks
Matthias

joegen@opensipstack.org schrieb:

Not at this point. Once upon a time, there were already classes for
parsing PIDF but due to the absence of dedicated manpower, it
remained dormant. I decided to removed them starting version 1.1.4
of OpenSBC. It has support for messaging though, but not presence.
However, it should be "relatively" easy to create your own presence
functionality using the RFC3256 classes. Feel free to donate your
code to the project if you decide to give it a shot.

Matthias Dreißig wrote:

So there is no support for presence in opensipstack at this time?

Joegen E. Baclor schrieb:

Matthias Dreißig wrote:

Hi everyone,

how do I use WatchRegistrationState(const SIPURI & stateAgent,
const SIPURI & resourceURI, const PTimeInterval & expires, const
OString & authUser, const OString & authPassword). What do I have
to process to this call?

Ouch! This method is an attempt to support RFC 3680 (
http://www.ietf.org/rfc/rfc3680.txt ). I did not get the chance
to revisit this work for a long time so it remains a work in
progress at this point. I am itching to get this supported in
OpalOSS and OSBC though (hint, hint, hint Ilian ;-)) .

Regards,
M. Dreißig

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save
$100. Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database:
270.6.5/1619 - Release Date: 8/18/2008 5:39 PM

_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Guest

8. Aug 19, 2008 2:12 PM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Can you give a little explanation what the bug is all about?

The "#ifdef RFC3265_CLIENT_H_" and "#define RFC3265_CLEINT_H_" differ. CLIENT and CLEINT, its hard to see.

This means if two classes includes the RFC3265Client.h the RFC3265 class is declared twice.

GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196

Guest

9. Aug 19, 2008 2:44 PM

in response to: Guest

Re: [OpenSIPStack] WatchRegistrationState

Matthias Dreißig wrote:

Can you give a little explanation what the bug is all about?

The "#ifdef RFC3265_CLIENT_H_" and "#define RFC3265_CLEINT_H_" differ. CLIENT and CLEINT, its hard to see.

This means if two classes includes the RFC3265Client.h the RFC3265 class is declared twice.

Oops! It's now in CVS. Thanks for the patch!

Go to original post

Apr 15, 2008 2:48 AM

[OpenSIPStack] WatchRegistrationState

Actions

More Like This