24 Feb
2010
24 Feb
'10
3:38 a.m.
Hi,
there could be other reasons to block subscriptions. Maybe the operator of
the service decides that Alice and Bob are on different realms, and are thus
not allowed to subscribe each others status. Explicitly blocking these
requests, eventually with a reason would be the right way to do this.
Marcus
On Fri, Feb 19, 2010 at 1:40 PM, Iñaki Baz Castillo <ibc(a)aliax.net> wrote:
El Viernes, 19 de Febrero de 2010, Klaus Darilion
escribió:
But then Alice will know (or can know) that you have rejected her!
Imagine you want to "captivate" Carol but don't want Alice to know that
you
are connected. You don't want to reject Alice, but just set "invisible"
for
her (you don't want to reject Alice because if you don't captivate Carol
you
would like to try with Alice later). :)
--
Iñaki Baz Castillo <ibc(a)aliax.net>
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Dipl.-Inf. (FH)
Marcus Hunger - hunger(a)sipgate.de
Telefon: +49 (0)211-63 55 55-61
Telefax: +49 (0)211-63 55 55-22
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106 / 5724 / 7147, Umsatzsteuer-ID: DE219349391
www.sipgate.de - www.sipgate.at - www.sipgate.co.uk
Am 19.02.2010 12:10, schrieb Iñaki Baz Castillo:
> But there is a problem with point 1 as it's not valid for the case in
> which you block a user who was allowed. This is, subscription status
> cannot transition from "active" to "pending", so the only way is
using
> case 3 in which the subscription status remains "active" but the
presence
server
sends a spoofed NOTIFY with "offline" status.
Why not terminate the subscription if Bob removes Alice from the allowed
buddies?
Then Alice will SUBSCRIBE again and receives status=pending.