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
<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(a)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