A A ANEES-RJD876 wrote:
All
As part of implementing RFC 3959 (early session) I am trying to
understand what interactions this feature has with preconditions as
described in RFC 3312. RFC just mentions and provides a reference to RFC
3312 but does not provide any details.
I
I'm coming back to an old question as it appears to me RFCs says differently
about.
Quoting an old answers from Paul:
If user=phone is present, then the syntax of the user part must conform
with the TEL URI syntax as defined in RFC 3966.
That syntax says that the number must start
Andrea Rizzi wrote:
On the other hand, RFC3966, Section 12 says:
When the '+' sign is not present, but a telephone number is
represented by the user portion of the URI, the SIP URI SHOULD
contain the optional ';user=phone' parameter; e.g.,
To: sip:83...@sip.example.net;user=phone
Andrea Rizzi wrote:
Sorry, I reported the wrong RFC number, the right one is 3398 SIP-ISUP
mapping. I beg your pardon
OK. That is also old - it predates 3966 by a couple of years, but it was
incorrect even with respect to RFC 2806, which it referenced for the
definition of the tel URL
Hello,
o Dale Worley [01/20/09 21:50]:
(2) The SIP standards tend to define *mechanisms* that are utilized to
implement features -- E.g., a phone executes a blind transfer by
sending a REFER to the remote phone. So one UA will be the one that
you can find more about transfer mechanisms in
