I'm a bit confused by the examples used in this draft:

         Refer-To: sip:[EMAIL PROTECTED]?Accept-Contact=sip:bobsdesk.
                   biloxi.com&Call-ID=55432%40alicepc.atlanta.com

         Refer-To: sip:[EMAIL PROTECTED]?Replaces:12345%40192.168.118.3;
                   to-tag=12345;from-tag=5FFE-3994;


Is the 2nd example correct?

In RFC2543 bis-09 it says:
19.1.1 SIP and SIPS URI Components

        Headers: Header fields to be included in a request constructed
             from the URI.

             Headers fields in the SIP request can be specified with the
             "?" mechanism within a URI. The header names and values are
             encoded in ampersand separated hname = hvalue pairs. The
             special hname "body" indicates that the associated hvalue
             is the message-body of the SIP request.



So I would expect the 2nd example to be:
         Refer-To: sip:[EMAIL PROTECTED]?Replaces=12345%40192.168.118.3;
                   to-tag=12345;from-tag=5FFE-3994;
(note the "=" after the "Replaces")


Am I right?
Or have I misunderstood something?


Any help is greatly appreciated.

Regards,

Attila



Attila Sipos    
Software Engineer

<mailto:[EMAIL PROTECTED]> 
<http://www.vegastream.com>

____________________________________________________________________________
_______


VegaStream : A World of difference for your Integrated Communications
        
EMEA Office (UK)
Tel    + 44 - 1344 784900    Fax    ?+ 44 -  1344 784901
USA Office
Tel + 1 -   561-995-2300  Fax  + 1 -   561-995-2600

This e-mail and any attachments hereto are strictly confidential and
intended solely for the addressee.  If you are not the intended addressee
please notify the sender by return and delete the message.  You must not
disclose, forward or copy this e-mail or attachments to any third party
without the prior consent of the sender.
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to