From: Fredrik Thulin <[EMAIL PROTECTED]>

   How is deactivating subscriptions as per RFC3265 supposed to
   actually be possible?

When the UACs send their new SUBSCRIBEs, how would it get to "the
other node in the server cluster"?

There seem to be two possibilities -- One is that one domain name has
multiple addresses, the addresses of the set of nodes.  In that case,
once a node has decided to go off-line, it should not respond to
requests that it receives, and not accept new TCP connections.  So any
agent that attempts to send a request to a node going off-line will
see the request time-out, and the agent will eventually retry with
another address for the same domain name.

A better method is to have some sort of forking proxy (either in a
proxy or the UAC), whereby the To address of the SUBSCRIBE sent by the
UAC is forked to the multiple nodes.  Then a node that is going
off-line can respond to all new requests with 503 (Service
Unavailable), and the forking proxy will try the other nodes.

Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to