> >> 3. Regarding Tag. Can multiple instances of a user (with same
> >> SIP URL) be present on the same end-point (host), each
> >> instance having different session capabilities? These
> >> instances could be differentiated using tag. However,
> >> registration would be only done once.
>
> >No. How would you know, based on an incoming initial >INVITE,
> for which one
> >the request was targeted? Use separate URLs on the same >host.
>
> The incoming INVITE would be duplicated (I don't want to use
> 'forked')at the endpoint to both users.
I don't grok this -- either the request is forked, or it
is not forked. You should probably note, however, that a
reasonable proxy is unlikely to fork to the same location
(i.e., Request-URI, physical-address tuple) twice (or more).
> As they have different
> capabilities, only one would respond with a 200. Also, the user's
> software would add a tag to differntiate the responses.
> The benifit of this is that a user can subscribe to differnt
> services at the same endpoint with the same permanent sip id.
> Each service is independently handled by the software assigned by
> the user.
If these "instances" have the exact same SIP URL, then from
SIP's point-of-view, they are one entity. You may choose to
separate them somehow logically, but this is outside the
scope of SIP.
HTH,
- Jo.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
