OK. That does make sense. Although with this support the BNF of RFC 3261 is a little out of date. Thanks Paul!
-------------------------------------------------- From: "Paul Kyzivat" <[EMAIL PROTECTED]> Sent: 2008年8月5日 9:36 PM To: "Bi Ran" <[EMAIL PROTECTED]> Cc: <[email protected]> Subject: Re: [Sip-implementors] query about 'npdi' 'rn' 'cpc' and 'cic' parameters > These are TEL URI parameters. They may appear in a sip uri when the sip > uri embeds a tel URI. In that case, all of these parameters appear > *before* the "@" sign. > > Thanks, > Paul > > Bi Ran wrote: >> [EMAIL PROTECTED]> >> Bcc: "garyjin" <[EMAIL PROTECTED]> >> References: <[EMAIL PROTECTED]> >> Subject: query about 'npdi' 'rn' 'cpc' and 'cic' parameters >> Date: Tue, 5 Aug 2008 10:39:06 +0800 >> MIME-Version: 1.0 >> X-Unsent: 1 >> Content-Type: text/plain; >> format=flowed; >> charset="iso-8859-1"; >> reply-type=original >> Content-Transfer-Encoding: 7bit >> X-Priority: 3 >> X-MSMail-Priority: Normal >> Importance: Normal >> X-Mailer: Microsoft Windows Live Mail 12.0.1606 >> X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 >> >> Hi all, >> >> Could 'npdi' 'rn' 'cpc' and 'cic' parameters be put into SIP-URI? Or they >> are only allowed in TEL-URI as defined by RFC 4694? >> This seems a conflict between standard and implementation. For PSTN to >> SIP (with SIP-URI) calls those parameters are defintely needed. >> >> If they could be added to SIP-URI, can we add them at the end of SIP-URI >> like 'user=phone'? Or we must put them before the '@'. >> >> Thanks, >> Bi Ran _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
