Vijay S Kamath wrote:
>
> Inline.
>
> Well, I suppose so, that the multicast socket would be closed at
> system shut down. but I still dont understand why you would want
> to close it just after sending a message?
> I do not want to close it immediately. I only want to close it when it
> is no longer needed for the UA. For ex: A user wishes to join a
> conference, and gives an address to the transport, which is a multicast
> address. So the transport layer creates a multicast socket joins the
> group & sends the message. The user is now part of the group. After
> sometime the user wishes to come out of the conference, so initiates a
> BYE. This is when I should be closing the socket. But I don't know how
> to implement this, since in every other case, the sockets are closed
> either immediately or after the expiration of a timer.
You are confusing a bunch of things here. A multicast conference would
use multicast sockets, but these have nothing to do with SIP. You'd join
the multicast group on sending/receivnig the INVITE, and leave it on
BYE.
Now, in the case of multicast SIP, it depends on what you are doing. If
you have a client (UAC or proxy) that wants to send a specific request
to a multicast group, it would join the group to receive the response,
but once it gets the response, it leaves the group. If you have a server
(UAS or proxy) that wishes to receive multicast requests (like the one
sent by the client in the previous example), it would probably join that
multicast group and remain in it indefinitely so that it can receive
requests at any time.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.jdrosen.net PH: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
