On Tue, Nov 30, 2004 at 12:16:53PM +0530, Chowdhury, Sayan (Sayan) wrote:
> maddr is listed as an optional parameter to contact , but i am not sure
> about the scenarios wherein an UAC might like to be contacted at a multicast
> address , and what implementation issues may arise out of it.
> Would be interested if some body can throw some light on it :)
I too was falsely led into believing this was for a multicast address, but
it is not (as it is in the Via header).
In the case of the Contact header, the maddr parameter of the uri
specifies the location for further contact (RFC 3261 19.1.1):
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. [4] describes the
proper interpretation of the transport, maddr, and hostport in
order to obtain the destination address, port, and transport
for sending a request.
i.e. if you receive a message that has a Contact header like this all
further contact regarding the transaction/call are to be directed there.
David
>
> Cheers ,
> Sayan
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of shivam
> Sent: Monday, November 29, 2004 4:01 PM
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] maddr parameter
>
>
> Hi all,
> I would like to know what does "maddr" parameter signifies ? When used in
> the Contact header ,what does it signify?
> Thanx in advance.
>
> Warm Regards
> Shivam
--
[EMAIL PROTECTED] | phone: 902-832-2649 fax: 902-832-1015
"Complex problems have simple, easy to understand wrong solutions" - anon
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
