Read the parts of RFC 3261 that describe the maddr.  

   A client that sends a request to a multicast address MUST add the
   "maddr" parameter to its Via header field value containing the
   destination multicast address, and for IPv4, SHOULD add the "ttl"
   parameter with a value of 1.  Usage of IPv6 multicast is not defined
   in this specification, and will be a subject of future
   standardization when the need arises.


> -----Original Message-----
> From: [email protected] [mailto:sip-
> [email protected]] On Behalf Of Shanbhag,
> Somesh (NSN - IN/Bangalore)
> Sent: Wednesday, March 23, 2011 2:07 AM
> To: ext malyabanta nayak; [email protected]
> Subject: Re: [Sip-implementors] sip request-uri
> 
> When maddr (machine address) is with the request-URI, it has the
> highest importance. The request shall be forwarded to the address
> received in maddr.
> 
> Best Regards,
> Somesh
> 
> -----Original Message-----
> From: [email protected] [mailto:sip-
> [email protected]] On Behalf Of ext malyabanta
> nayak
> Sent: Wednesday, March 23, 2011 12:26 PM
> To: [email protected]
> Subject: [Sip-implementors] sip request-uri
> 
> hello  all,
> 
> i am a beginner to sip rfc 3261.
> i have a doubt in request -uri
> 
> what  is the function of maddr parameter and how it works while
> stateful
> proxy forwards  a sip message towards destination?
> 
> can any body please help me regarding the question.
> 
> Thanks
> malyabanta nayak
> NET CLOUD SYSTEMS
> _______________________________________________
> 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

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to