[SIPForum-discussion] tel URI

aditya kumar adityaakumar at hotmail.com
Wed May 23 10:56:52 UTC 2007


Hi,
 
Thanks guys...your valuable comment is really help me and clear my doubt.
 
Could u plz tell me one more thing,In SIP INVITE req. can we send "pres,h.323,im" uris?
 
Example:-
1.INVITE pres:11989388389 at example.com SIP/2.0
2.INVITE h323:11989388389 at example.com SIP/2.0
3.INVITE im:11989388389 at example.com SIP/2.0
 
Thanks,
Adi
 
 


To: Richard.Stastny at oefeg.atCC: adityaakumar at hotmail.com; discussion at sipforum.org; discussion-bounces at sipforum.org; zxia at alcatel-lucent.comSubject: Re: [SIPForum-discussion] tel URIFrom: dipanjan.dutta at aricent.comDate: Wed, 23 May 2007 15:28:33 +0530Hello Richard, "user=" is a SIP parameter defined by SIP ABNF in RFC 3261. user=phone parameter signifies that the user part in a sip: URI is a telephone number. postd (post-dial parameter) is deprecated in 3966:         "12.  Changes Since RFC 2806         ...         Compared to RFC 2806, references to carrier selection, dial context,         fax and modem URIs, post-dial strings, and pause characters have been         removed."thanks, Dipanjan 



"Stastny Richard" <Richard.Stastny at oefeg.at> Sent by: discussion-bounces at sipforum.org 
05/23/2007 02:42 PM 





To
"Xia, Zeng Wu \(Jackey\)" <zxia at alcatel-lucent.com>, "aditya kumar" <adityaakumar at hotmail.com>, <discussion at sipforum.org> 


cc



Subject
Re: [SIPForum-discussion] tel URI




I wonder   1.        ;user= is a sip parameter 2.        :postd= I do not find in RFC3966   Richard   


From: Xia, Zeng Wu (Jackey) [mailto:zxia at alcatel-lucent.com] Sent: Wednesday, May 23, 2007 11:02 AMTo: Stastny Richard; aditya kumar; discussion at sipforum.orgSubject: RE: [SIPForum-discussion] tel URI   Richard,    The RFC3966 think the   INVITE tel:+358-555-1234567;postd=pp22 at foo.com;user=phone    is valid. Regards Jackey   


From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of Stastny RichardSent: Wednesday, May 23, 2007 4:27 PMTo: aditya kumar; discussion at sipforum.orgSubject: Re: [SIPForum-discussion] tel URI >INVITE tel:+358-555-1234567;postd=pp22 at foo.com;user=phone   This is an invalid format You may either use Sip:+358-555-1234567 at foo.com;user=phoneor Tel:+358-555-1234567 postd=pp22 is not allowed anymore in the tel URI   Richard   


From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of aditya kumarSent: Wednesday, May 23, 2007 8:48 AMTo: discussion at sipforum.orgSubject: [SIPForum-discussion] tel URI   Hi,Can we send tel URI in the  INVITE req.,if not why ?Example:-INVITE tel:+358-555-1234567;postd=pp22 at foo.com;user=phoneThanks,Aditya 


The idiot box is no longer passe; It's making news and how!_______________________________________________This is the SIP Forum discussion mailing listTO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussionPost to the list at discussion at sipforum.org***********************  Aricent-Private   *********************** 



"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."

_________________________________________________________________
Catch the cricket action with MSN!
http://content.msn.co.in/Sports/Cricket/Default.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20070523/5dbddb30/attachment-0002.html>


More information about the discussion mailing list