Aymeric Moizard wrote:
> hi,
>
> My question is about "section 11" (Requirement) and
> specifically about "REQ 4":
>
> REQ 4: It MUST be possible for a UA to obtain a multiplicity of GRUUs
> that each route to that UA instance. For example, this is needed
> to support ad-hoc conferencing where a UA instance needs a
> different URI for each conference it is hosting.
Note that this requirement was satisfied in the design by the grid
parameter. You get one gruu URI back from the registrar, and then can
use it with any grid parameter you want to form an infinite number of
gruus that are all routed the same way.
> I need to send a new GRUU in a re-INVITE (for example to setup a conference).
*need*? or *want?
I can imagine how you might want to, but not why you would need to.
> The initial GRUU used in first INVITE will probably be one
> given by the proxy.
If you want to distinguish incoming requests are are in some way derived
from the gruu in this call, then you should put a unique grid value in
the contact used for the initial invite.
> I want the second GRUU in the re-INVITE to use a different username.
> (like "bob-mixer" instead of bob).
You don't have control over the username part of the gruu. You ask the
registrar for a gruu that binds an AOR to an instance ID, and it comes
back with some user name. There is no way for you to get one that binds
the same AOR and instance ID and has a different user name.
If your AOR was <sip:[EMAIL PROTECTED]> then the gruu you got back *might*
be <sip:[EMAIL PROTECTED];opaque="xyzzy">. You then could have used
<sip:[EMAIL PROTECTED];opaque="xyzzy";grid="1"> in your initial invite. And
in your reinvite you could use
<sip:[EMAIL PROTECTED];opaque="xyzzy";grid="mixer1">.
> Should I just register it as a second
> Contact header?
That won't help. If you register a different contact but use the same
AOR and instance ID you will get the same gruu. You can get a different
gruu by using a different instance id, but that is the wrong thing to do.
> Questions:
>
> It seems such new modified GRUU/Contact will not be forwareded/accepted by
> the server that generated the GRUU?
If you do as I suggest above, using grid, then calls to the gruu will
arrive at your UA with the R-URI being the contact you registered, but
with a grid parameter equal to the grid in the gruu.
> It seems removing "opaque" value from GRUU should always give the AOR. Thus,
> bob-mixer must/(should?) be at least an existing alias for me on my server?
forget about bob-mixer.
Paul
> Is it possible to send such REGISTER to my proxy:
>
> REGISTER
> From: <sip:[EMAIL PROTECTED]>
> Contact:
> <sip:[EMAIL
> PROTECTED]>;+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
> Contact:
> <sip:[EMAIL
> PROTECTED]>;+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
>
>
> Thanks
> Aymeric
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
