Markus,
Thanks for the clarification, I have come up with the following.
The target of the Request-URI and the TO field are normally the same but do not need to be. It should be possible to have the well known SIP Server Multicast address in the Request-URI and a [EMAIL PROTECTED] address in the TO field. The proxy should process the call and if not known locally forward the Invite on to the next hop with the new applicable Request-URI.
Someone has obviously come up with this as a valid test for this proxy but I am unsure of using this method for a real implementation - presumeably the multicast address would be provisioned as the outbound proxy of a UA meaning every initial Invite will go to all local SIP Servers who will respond with any number of final responses (3xx, 4xx. etc.) the UAC can continue dialog with the most favourable one chosen which should included a unicast IP address in the contact header for further dialog within the session.
Wayne Davies
| "Markus Hofmann" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 19/05/2004 12:45 AM
|
To: [EMAIL PROTECTED] cc: Subject: Re: [Sip-implementors] Newbie: maddr parameter |
Hi Wayne,
yes I can.
I'm implementing a test key of the ETSI. The test key is described:
Ensure that the IUT (Implementation under test: here a proxy) on receipt of an INVITE request with the Request-URI with a maddr parameter indicating a value the proxy is responsible for and the request was received using the port and transport indicating, removes the maddr and any non default port or transport parameter from the request and forwards the message.
I read the same like you. The test key has a reference to 16.4 but I don't know what I have to do and the reason is I don't understand what a maddr parameter is doing.
I would be very thankful for help.
Markus
[EMAIL PROTECTED] schrieb am 18.05.04 00:39:12:
Markus,
Can you detail a little more the purpose of using the maddr parameter in the SIP addressing ?. Section 18.1.1 of RFC3261 touches on the use of maddr in the VIA header of a request. An example purpose of this would be to send a REGISTER request to the 'all SIP servers' multicast address 224.0.1.75 - which is also why the RFC recommends including a TTL of 1 so that the request doesn't propagate outside the local network.
Conferencing or placing someone on Music on Hold to a a multicast stream is typically seen with directed IPv4 unicast addressing or DNS entries in the SIP address header fields and a maddr address in the SDP.
Regards,
Wayne Davies
Hello everybody,
I have questions about the maddr parameter. I have to write a program which should have an maddr in the Request-URI. I read the RFC 3261 but it seems that I don't have an understanding for this.
What is the maddr parameter? Multi-home address or Multicast address? When is a proxy responsible for a request with a maddr parameter and when not? How looks a RequestURI with a maddr parameter?
Thank you very much.
Greeting
Markus
Zeigen Sie Emotionen mit der WEB.DE Bild-SMS! Das Bild ist gratis,
Sie bezahlen n! ur den Versand. http://freemail.web.de/?mc=021196
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
******************************************************************************
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately.
Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.
******************************************************************************
-----------------------------------------------------------------
_______________________________________________Sip-implementors mailing [EMAIL PROTECTED]://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_____________________________________________________________________
Endlich SMS mit Bildern versenden! Das Bild selbst ist dabei gratis,
Sie bezahlen lediglich den Versand. http://freemail.web.de/?mc=021195
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
