URI vs. RFC 2806
"Kalman Lau" <[email protected]> Tue, 23 Oct 2007 18:06:08 -0700
| Newsgroups | gmane.comp.voip.nist-sip |
|---|---|
| Message-ID | <[email protected]> |
--===============8681491561728747231== Content-Type: multipart/alternative; boundary="----=_Part_4594_20901252.1193187968030" ------=_Part_4594_20901252.1193187968030 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline The javadoc for javax.sip.address.URI only suggests support for generic URIs from RFC 2396. The NIST SIP RI does not appear to support RFC 2806. Does anyone have suggestions for the pause "p" and wait "w" characters? Kalman ------=_Part_4594_20901252.1193187968030 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline The javadoc for javax.sip.address.URI only suggests support for generic URIs from RFC 2396. The NIST SIP RI does not appear to support RFC 2806. Does anyone have suggestions for the pause "p" and wait "w" characters? <br><br>Kalman<br> ------=_Part_4594_20901252.1193187968030-- --===============8681491561728747231== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nist-sip mailing list [email protected] http://www-x.antd.nist.gov/mailman/listinfo/nist-sip --===============8681491561728747231==--