[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    RE: [Sip-implementors] Re: Sip-implementors Digest, Vol 12, Issue 27
From:       "Brett Tate" <brett () broadsoft ! com>
Date:       2004-03-31 19:40:27
Message-ID: 006101c41758$05fe76a0$2b01a8c0 () broadsoft ! com
[Download RAW message or body]

> Does inclusion of parameter user=phone 
> guarantee that the user part confirms 
> to rfc 2806 or is it that it may confirm.

There are never any guarantees.  The
user=phone does indicate that the
user part can be parsed into a 
telephone-subscriber defined within
rfc 2806 or the various bis versions.
Since the bis versions are not completely
backwards compatible with rfc 2806,
care should be taken when trying to apply
strict conformance rules associated with
things not backward compatible.

For instance, some products currently
add user=phone without conforming to the
new bis rule that the telephone-subscriber
MUST contain a phone-context if the
telephone-subscriber contains a local-number.
If you desire to interwork with these products,
you should be lenient in what you accept from
these products that implemented rfc2806 instead 
of rfc2806bis.


[prev in list] [next in list] [prev in thread] [next in thread]