Alex,
On 11/4/16 12:31 AM, Alex Balashov wrote:
Hi,
As far as I can tell from the RFC 3261 ABNF, it is permitted to put SEMI
and EQUAL in the username of a URI, but it has no semantic validity.
Why do you say this has no semantic validity? The owner of the domain
determines the semantics of
Alex Balashov writes:
> As far as I can tell from the RFC 3261 ABNF, it is permitted to put SEMI
> and EQUAL in the username of a URI, but it has no semantic validity.
> That is to say, this is permitted:
>
>
True, though you probably meant
> but doesn't mean anything. 'myval=abc;u
iginal Message-
> From: sa...@allegro-1.evaristesys.com [mailto:sasha@allegro-
> 1.evaristesys.com] On Behalf Of Alex Balashov
> Sent: Friday, November 04, 2016 9:57 AM
> To: Brett Tate; sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Semantics of parameter
Brett,
Thank you for your answer, but it is still rather clear—likely to my
feeble intellect—how to apply this to my question about use of Diversion
to pass state.
On 11/04/2016 07:04 AM, Brett Tate wrote:
As far as I can tell from the RFC 3261 ABNF, it is
permitted to put SEMI and EQUAL in
> As far as I can tell from the RFC 3261 ABNF, it is
> permitted to put SEMI and EQUAL in the username of
> a URI, but it has no semantic validity.
The user-parameter can help. However, be aware that some vendors add
"user=phone" when user portion is absent or otherwise cannot be decoded as
telep
Hi,
As far as I can tell from the RFC 3261 ABNF, it is permitted to put SEMI
and EQUAL in the username of a URI, but it has no semantic validity.
That is to say, this is permitted:
but doesn't mean anything. 'myval=abc;user' is just one big long username:
SIP-URI = "sip:" [ us
