Hi,

I am afraid I am not familiar with the configuration of those clients for presence.

What should happen is that the client should PUBLISH at around the same time as you REGISTER. When you change your presence information (online/offline/busy, or your status message, or your avatar) the client should send another PUBLISH updating your presentity.

When Kamailio receives the PUBLISH you should detect this and call handle_publish() (in the presence module). It is handle_publish() that populates the presentity table.

Regards,

Peter

On Thu, 2012-01-26 at 14:28 +0100, Vogt, Jonathan wrote:

Hello Peter,

the presentity table is empty. I have not seen any publish request. Neither using bravis or x-lite.

Is there something I can do to make the client send a publish request? Or is my configuration missing something?

I got

REGISTER 401 REGISTER 200 SUBSCRIBE 407 SUBSCRIBE 202 NOTIFY 200

see http://pastebin.ca/2106425 for details.

Thanks Jonathan

---

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Donnerstag, 26. Januar 2012 14:10 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Enable application/pidf+xml

Hello,

Are there any PUBLISH requests between your clients (particularly the client for sip:2002@sip.intern.domain) and Kamailio?

Does the presentity table in Kamailio contain anything?

The active state NOTIFY should contain the presentity information stored for the contact in the presentity table. This table is populated when the contact sends a PUBLISH.

If there is no record in the presentity table for the contact (sip:2002@sip.intern.domain) then this NOTIFY is correct.

Regards,

Peter

On Thu, 2012-01-26 at 14:03 +0100, Vogt, Jonathan wrote:

...

Hello all,

I'm trying to set up kamailio as a sip server with presence support for Bravis.

So far I got the call processing running on either openser-1.3.2-3build1 or 3.2.0+lucid1 running. Problem is the notification is not using Content-Type: application/pidf+xml

My openser config is at http://pastebin.ca/2106401

My kamailio config is pretty much a stock configuration. It is at http://pastebin.ca/2106404 I enabled mysql and presence.

I also tried using x-lite but there is no presence information either. modparam("presence_xml", "force_active", 1) did not seem to make a difference. (I cleaned my watchers table)

I can see the database has the information but the notify packets are just like this:

NOTIFY sip:2001@10.0.76.0:56239 SIP/2.0 Via: SIP/2.0/UDP 10.0.10.23;branch=z9hG4bKcb76.b2dab2d4.0 To: sip:2001@sip.intern.domain;tag=90cd05fe2b0619108127da16a6e721e1 From: sip:2002@sip.intern.domain;tag=10.785.1327490724.1 CSeq: 22 NOTIFY Call-ID: 90cd05fe-2b06-1910-9660-da16a6e721e1 Content-Length: 0 User-Agent: OpenSER (1.3.2-notls (i386/linux)) Max-Forwards: 70 Event: presence Contact: sip:10.0.10.23:5060 Subscription-State: active;expires=300

Where is my mistake. As I'm new to kamailio please bear with me, if I just didn't find the right switch.

Thanks Jonathan Vogt

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Peter Dunkley Technical Director Crocodile RCS Ltd

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hello,

I think that force_active affects the state of the SUBSCRIBE dialogs. So, a presentity does not have to explicitly authorise a watcher. This is not the same as automatically PUBLISH'ing presence state. I don't believe force_active will do what you want here as it has nothing to do with the body of the NOTIFY, just the Subscription-State: SIP header.

Also, I think the problem could be that X-Lite supports peer-to-peer presence (where the clients exchange SUBSCRIBEs and NOTIFYs) but does not support server presence (where the SUBSCRIBEs are from the client to the server, NOTIFYs are from the server to the client, and the client must PUBLISH to the server).

If you want the server to automatically PUBLISH for a client that does not support server presence (so online when you REGISTER and offline when you un-REGISTER) take a look a pua_usrloc.

Regards,

Peter

On Thu, 2012-01-26 at 15:27 +0100, Vogt, Jonathan wrote:

Hi,

but I've understood correctly. I only need kamailio and no other software if I use the force_active switch?

Thanks Jonathan

---

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Donnerstag, 26. Januar 2012 14:36 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Enable application/pidf+xml

Hi,

I am afraid I am not familiar with the configuration of those clients for presence.

What should happen is that the client should PUBLISH at around the same time as you REGISTER. When you change your presence information (online/offline/busy, or your status message, or your avatar) the client should send another PUBLISH updating your presentity.

When Kamailio receives the PUBLISH you should detect this and call handle_publish() (in the presence module). It is handle_publish() that populates the presentity table.

Regards,

Peter

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi,

this is the wrong mailing list: This Mailinglist is about OpenSER (the original), Kamailio, SER and sip-router.org - not OpenSIPS. If you have problems with an OpenSIPS configuration or module, please post it to the OpenSIPS-list.

We can only provide help for our modules.

Thank you, Carsten

2012/1/27 Vogt, Jonathan J.Vogt@swp.de

** Hello,

could anyone kindly send me a working config which does support clients that not support server presence or send me a link to a working sample configuration. I seem unable to produce a working config myself.

1. I have take the source from opensips.org and compiled it.
2. Taken the conf from

http://www.opensips.org/Resources/PuaUsrlocConfig replaced sip domain and ip and enabled auth 3. Reset DB and created users 4. Replaced X-LITE in conf with BRAVIS useragent. 5. Tested and did not work... 6. undid step 4 and used X-LITE 4 for test... did not work either.

I'm lost here. Any help appreciated.

Thanks Jonathan

---

*Von:* sr-users-bounces@lists.sip-router.org [mailto: sr-users-bounces@lists.sip-router.org] *Im Auftrag von *Peter Dunkley *Gesendet:* Donnerstag, 26. Januar 2012 15:38 *An:* SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List *Betreff:* Re: [SR-Users] Enable application/pidf+xml

Hello,

I think that force_active affects the state of the SUBSCRIBE dialogs. So, a presentity does not have to explicitly authorise a watcher. This is not the same as automatically PUBLISH'ing presence state. I don't believe force_active will do what you want here as it has nothing to do with the body of the NOTIFY, just the Subscription-State: SIP header.

Also, I think the problem could be that X-Lite supports peer-to-peer presence (where the clients exchange SUBSCRIBEs and NOTIFYs) but does not support server presence (where the SUBSCRIBEs are from the client to the server, NOTIFYs are from the server to the client, and the client must PUBLISH to the server).

If you want the server to automatically PUBLISH for a client that does not support server presence (so online when you REGISTER and offline when you un-REGISTER) take a look a pua_usrloc.

Regards,

Peter

-- Peter Dunkley Technical Director Crocodile RCS Ltd

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

When I am using pua_usrloc...

Modify the standard config:

... loadmodule "usrloc.so" loadmodule "pua.so" loadmodule "pua_usrloc.so" ... modparam("pua", "db_url", DBURL) modparam("pua", "outbound_proxy", "sip:127.0.0.1") modparam("pua_usrloc", "default_domain", "<<< whatever the domain your system has >>>") modparam("pua_usrloc", "entity_prefix", "sip") ... route[REGISTRAR] {

if (is_method("REGISTER")) {

pua_set_publish(); ...

}

...

You need to make sure Kamailio is listening on the loopback (127.0.0.1) device on port 5060, or change the pua outbound_proxy modparam to contain a real IP address and port that Kamailio is using. Setting this outbound_proxy parameter makes sure Kamailio routes the PUBLISH generated by pua/pua_usrloc through itself (so that it can be picked up and handle_publish() is called) instead of using DNS to try and route the request.

Also make sure that the pua database table was created when you ran kamdbctl to set-up the database.

Regards,

Peter

On Fri, 2012-01-27 at 15:04 +0100, Vogt, Jonathan wrote:

Hi sorry,

I guess I just got mixed up with all the name, merges, forks and mailinglists...

As I started out with openser, tried kamailio and just compiled opensips, I would appreaciate a working sample for openser or kamailio aswell.

I just need a sip server with presence support for bravis... which for itself does not seem to support server side presence...

Thanks Jonathan

---

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Carsten Bock Gesendet: Freitag, 27. Januar 2012 14:55 An: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml

Hi,

this is the wrong mailing list: This Mailinglist is about OpenSER (the original), Kamailio, SER and sip-router.org - not OpenSIPS. If you have problems with an OpenSIPS configuration or module, please post it to the OpenSIPS-list.

We can only provide help for our modules.

Thank you, Carsten

2012/1/27 Vogt, Jonathan J.Vogt@swp.de

    Hello,

    could anyone kindly send me a working config which does
    support clients that not support server presence or send me a
    link to a working sample configuration. I seem unable to
    produce a working config myself.

            I have take the source from opensips.org and compiled
            it.
            Taken the conf from
            http://www.opensips.org/Resources/PuaUsrlocConfig replaced sip domain and ip and enabled auth
            Reset DB and created users
            Replaced X-LITE in conf with BRAVIS useragent.
            Tested and did not work...
            undid step 4 and used X-LITE 4 for test... did not
            work either.
    I'm lost here. Any help appreciated.

    Thanks
    Jonathan




    ______________________________________________________________
    Von: sr-users-bounces@lists.sip-router.org
    [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von
    Peter Dunkley
    Gesendet: Donnerstag, 26. Januar 2012 15:38
    An: SIP Router "- Kamailio (OpenSER) and SIP Express Router
    (SER) -Users Mailing "List
    Betreff: Re: [SR-Users] Enable application/pidf+xml




    Hello,

    I think that force_active affects the state of the SUBSCRIBE
    dialogs.  So, a presentity does not have to explicitly
    authorise a watcher.  This is not the same as automatically
    PUBLISH'ing presence state.  I don't believe force_active will
    do what you want here as it has nothing to do with the body of
    the NOTIFY, just the Subscription-State: SIP header.

    Also, I think the problem could be that X-Lite supports
    peer-to-peer presence (where the clients exchange SUBSCRIBEs
    and NOTIFYs) but does not support server presence (where the
    SUBSCRIBEs are from the client to the server, NOTIFYs are from
    the server to the client, and the client must PUBLISH to the
    server).

    If you want the server to automatically PUBLISH for a client
    that does not support server presence (so online when you
    REGISTER and offline when you un-REGISTER) take a look a
    pua_usrloc.

    Regards,

    Peter


    -- 
    Peter Dunkley
    Technical Director
    Crocodile RCS Ltd


    _______________________________________________
    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
    mailing list
    sr-users@lists.sip-router.org
    http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock CEO (Geschäftsführer)

ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany

http://www.ng-voice.com mailto:carsten@ng-voice.com

Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284

Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi,

If by auth you mean the WITH_AUTH #!define in the configuration file then it sounds like a configuration error. You should check that the pua_usrloc stuff you've added isn't excluded when WITH_AUTH is not set.

It is also worth remembering that, if you are using a client that does not support server presence, or you are using a client that does support server presence but doesn't support XCAP, then your configuration will only work when you set the force_active modparam in presence_xml to 1. This is because with force_active not set you need clients that can update the pres-rules documents in the resource list to add new contacts to the allow list before they will be authorised for presence.

Regards,

Peter

On Mon, 2012-01-30 at 17:17 +0100, Vogt, Jonathan wrote:

Hello,

great. I got presence... but only when I do not enable auth.

Is there something I have to look out for when enabling auth

I've take the stock config for 3.2.0 as packed in the ubuntu package from the website, implementet your changes and reinit the database.

Apart from your changes I defined WITH_USRLOCDB, WITH_PRESENCE, WITH_AUTH, WITH_MYSQL.

No presence with auth. Presence without auth. Cleared the db in between.

Any hints

Thanks Jonathan

---

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Freitag, 27. Januar 2012 18:07 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml

When I am using pua_usrloc...

Modify the standard config:

    ...
    loadmodule "usrloc.so"
    loadmodule "pua.so"
    loadmodule "pua_usrloc.so"
    ...
    modparam("pua", "db_url", DBURL)
    modparam("pua", "outbound_proxy", "sip:127.0.0.1")
    modparam("pua_usrloc", "default_domain", "<<< whatever the
    domain your system has >>>")
    modparam("pua_usrloc", "entity_prefix", "sip")
    ...
    route[REGISTRAR] {

            if (is_method("REGISTER"))
            {

                    pua_set_publish();
                    ...

            }

    ...

You need to make sure Kamailio is listening on the loopback (127.0.0.1) device on port 5060, or change the pua outbound_proxy modparam to contain a real IP address and port that Kamailio is using. Setting this outbound_proxy parameter makes sure Kamailio routes the PUBLISH generated by pua/pua_usrloc through itself (so that it can be picked up and handle_publish() is called) instead of using DNS to try and route the request.

Also make sure that the pua database table was created when you ran kamdbctl to set-up the database.

Regards,

Peter

On Fri, 2012-01-27 at 15:04 +0100, Vogt, Jonathan wrote:

...

Hi sorry, I guess I just got mixed up with all the name, merges, forks and mailinglists... As I started out with openser, tried kamailio and just compiled opensips, I would appreaciate a working sample for openser or kamailio aswell. I just need a sip server with presence support for bravis... which for itself does not seem to support server side presence... Thanks Jonathan

---

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Carsten Bock Gesendet: Freitag, 27. Januar 2012 14:55 An: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml

Hi,

this is the wrong mailing list: This Mailinglist is about OpenSER (the original), Kamailio, SER and sip-router.org - not OpenSIPS. If you have problems with an OpenSIPS configuration or module, please post it to the OpenSIPS-list.

We can only provide help for our modules.

Thank you, Carsten

2012/1/27 Vogt, Jonathan J.Vogt@swp.de

    Hello, 
    could anyone kindly send me a working config which does
    support clients that not support server presence or send me
    a link to a working sample configuration. I seem unable to
    produce a working config myself. 
            I have take the source from opensips.org and
            compiled it. 
            Taken the conf from
            http://www.opensips.org/Resources/PuaUsrlocConfig replaced sip domain and ip and enabled auth 
            Reset DB and created users 
            Replaced X-LITE in conf with BRAVIS useragent. 
            Tested and did not work... 
            undid step 4 and used X-LITE 4 for test... did not
            work either. 
    I'm lost here. Any help appreciated. 
    Thanks 
    Jonathan 


    ____________________________________________________________

    Von: sr-users-bounces@lists.sip-router.org
    [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag
    von Peter Dunkley
    Gesendet: Donnerstag, 26. Januar 2012 15:38
    An: SIP Router "- Kamailio (OpenSER) and SIP Express Router
    (SER) -Users Mailing "List
    Betreff: Re: [SR-Users] Enable application/pidf+xml



    Hello,

    I think that force_active affects the state of the SUBSCRIBE
    dialogs.  So, a presentity does not have to explicitly
    authorise a watcher.  This is not the same as automatically
    PUBLISH'ing presence state.  I don't believe force_active
    will do what you want here as it has nothing to do with the
    body of the NOTIFY, just the Subscription-State: SIP header.

    Also, I think the problem could be that X-Lite supports
    peer-to-peer presence (where the clients exchange SUBSCRIBEs
    and NOTIFYs) but does not support server presence (where the
    SUBSCRIBEs are from the client to the server, NOTIFYs are
    from the server to the client, and the client must PUBLISH
    to the server).

    If you want the server to automatically PUBLISH for a client
    that does not support server presence (so online when you
    REGISTER and offline when you un-REGISTER) take a look a
    pua_usrloc.

    Regards,

    Peter


    -- 
    Peter Dunkley
    Technical Director
    Crocodile RCS Ltd

    _______________________________________________
    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
    mailing list
    sr-users@lists.sip-router.org
    http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Carsten Bock CEO (Geschäftsführer)

ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany

http://www.ng-voice.com mailto:carsten@ng-voice.com

Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220

Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284

Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Peter Dunkley Technical Director Crocodile RCS Ltd

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi,

thanks, that was the missing link. It's working now.

Jonathan

________________________________

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Montag, 30. Januar 2012 17:44 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml

Hi,

If by auth you mean the WITH_AUTH #!define in the configuration file then it sounds like a configuration error. You should check that the pua_usrloc stuff you've added isn't excluded when WITH_AUTH is not set.

It is also worth remembering that, if you are using a client that does not support server presence, or you are using a client that does support server presence but doesn't support XCAP, then your configuration will only work when you set the force_active modparam in presence_xml to 1. This is because with force_active not set you need clients that can update the pres-rules documents in the resource list to add new contacts to the allow list before they will be authorised for presence.

Regards,

Peter

On Mon, 2012-01-30 at 17:17 +0100, Vogt, Jonathan wrote:

Hello,

great. I got presence... but only when I do not enable auth.

Is there something I have to look out for when enabling auth

I've take the stock config for 3.2.0 as packed in the ubuntu package from the website, implementet your changes and reinit the database.

Apart from your changes I defined WITH_USRLOCDB, WITH_PRESENCE, WITH_AUTH, WITH_MYSQL.

No presence with auth. Presence without auth. Cleared the db in between.

Any hints

Thanks

Jonathan

________________________________

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Freitag, 27. Januar 2012 18:07 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml

When I am using pua_usrloc... Modify the standard config:

... loadmodule "usrloc.so" loadmodule "pua.so" loadmodule "pua_usrloc.so" ... modparam("pua", "db_url", DBURL) modparam("pua", "outbound_proxy", "sip:127.0.0.1") modparam("pua_usrloc", "default_domain", "<<< whatever the domain your system has >>>") modparam("pua_usrloc", "entity_prefix", "sip") ... route[REGISTRAR] {

if (is_method("REGISTER")) {

pua_set_publish(); ...

}

...

You need to make sure Kamailio is listening on the loopback (127.0.0.1) device on port 5060, or change the pua outbound_proxy modparam to contain a real IP address and port that Kamailio is using. Setting this outbound_proxy parameter makes sure Kamailio routes the PUBLISH generated by pua/pua_usrloc through itself (so that it can be picked up and handle_publish() is called) instead of using DNS to try and route the request. Also make sure that the pua database table was created when you ran kamdbctl to set-up the database. Regards, Peter On Fri, 2012-01-27 at 15:04 +0100, Vogt, Jonathan wrote:

Hi sorry, I guess I just got mixed up with all the name, merges, forks and mailinglists... As I started out with openser, tried kamailio and just compiled opensips, I would appreaciate a working sample for openser or kamailio aswell. I just need a sip server with presence support for bravis... which for itself does not seem to support server side presence... Thanks Jonathan ________________________________

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Carsten Bock Gesendet: Freitag, 27. Januar 2012 14:55 An: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Betreff: Re: [SR-Users] Sample pua_usrloc Config Was: Enableapplication/pidf+xml Hi, this is the wrong mailing list: This Mailinglist is about OpenSER (the original), Kamailio, SER and sip-router.org - not OpenSIPS. If you have problems with an OpenSIPS configuration or module, please post it to the OpenSIPS-list. We can only provide help for our modules. Thank you, Carsten 2012/1/27 Vogt, Jonathan J.Vogt@swp.de

Hello, could anyone kindly send me a working config which does support clients that not support server presence or send me a link to a working sample configuration. I seem unable to produce a working config myself.

I have take the source from opensips.org and compiled it. Taken the conf from http://www.opensips.org/Resources/PuaUsrlocConfig replaced sip domain and ip and enabled auth Reset DB and created users Replaced X-LITE in conf with BRAVIS useragent. Tested and did not work... undid step 4 and used X-LITE 4 for test... did not work either.

I'm lost here. Any help appreciated. Thanks Jonathan ________________________________

Von: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Peter Dunkley Gesendet: Donnerstag, 26. Januar 2012 15:38 An: SIP Router "- Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing "List Betreff: Re: [SR-Users] Enable application/pidf+xml Hello, I think that force_active affects the state of the SUBSCRIBE dialogs. So, a presentity does not have to explicitly authorise a watcher. This is not the same as automatically PUBLISH'ing presence state. I don't believe force_active will do what you want here as it has nothing to do with the body of the NOTIFY, just the Subscription-State: SIP header. Also, I think the problem could be that X-Lite supports peer-to-peer presence (where the clients exchange SUBSCRIBEs and NOTIFYs) but does not support server presence (where the SUBSCRIBEs are from the client to the server, NOTIFYs are from the server to the client, and the client must PUBLISH to the server). If you want the server to automatically PUBLISH for a client that does not support server presence (so online when you REGISTER and offline when you un-REGISTER) take a look a pua_usrloc. Regards, Peter