Re: Significance of port in maddr parameter.
aayush bhatnagar <[email protected]> Wed, 23 Dec 2009 08:25:02 +0030
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
Vineet, The maddr parameter can be present in the Via header and in the request URI. If present in the Via header, it signifies that the client is sending the request to a multicast receiver. Refer to section 18.1.1 of 3261 for this. It may be present in the Request URI...which means that the entry of the request uri is added as the only entry in the target set for the request. As for the port, it is not present in the maddr paramater. It is present in the sent-by parameter, or defaults to 5060 in case the sent-by parameter is absent. Hope this helps. For more info of maddr parameter usage, read sections 16.4, 16.5, 18.1.1, 18.1.2 and 19.1.1 of RFC 3261. On 23/12/2009, Sreerekha Shenoy (sresheno) <[email protected]> wrote: > Hi Vineet, > As per RFC 3261, I don't see a placeholder for port number in the > maddr-param. > The ABNF syntax for maddr goes as follows: > > maddr-param = "maddr=" host > host = hostname / IPv4address / IPv6reference > > please explain on what do you mean by 'port in maddr param' > > > > Thanks, > Best Regards, > Rekha > > ======================================================================== > ========= > > > Today's Topics: > > 1. Significance of port in maddr parameter. (Vineet Gupta) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 Dec 2009 17:27:40 +0530 > From: Vineet Gupta <[email protected]> > Subject: [Sip] Significance of port in maddr parameter. > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > Can someone let me know why exactly following statement is present in > RFC > 3261: > > *"The maddr parameter indicates the server address to be contacted for > this > user, overriding any address derived from the host field. When an maddr > parameter is present, the port and transport components of the URI apply > to > the address indicated in the maddr parameter value"* > > To be specific: > a) What exactly can go wrong on using the port in maddr parameter? > b) In what are situations where port present in Req-URI should be used > rather than port present in maddr parameter? > c) And in what situation port in maddr parameter should be used? > > Regards, > Vineet. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://www.ietf.org/mail-archive/web/sip/attachments/20091222/d7434e03/ > attachment.htm> > > ------------------------------ > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use [email protected] for questions on current sip > Use [email protected] for new developments on the application of sip > > End of Sip Digest, Vol 64, Issue 10 > *********************************** > -- aayush http://in.linkedin.com/in/abhatnagar19 ====== _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip