Hi,
 
No, user=phone should not be added. Only the To tag for the dialog,
which you get in responses, should be added to the ACK (and all other
in-dialog requests).
 
Regards,
 
Christer


________________________________

        From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
        Sent: 10. joulukuuta 2008 13:10
        To: [email protected]
        Subject: [Sip] ACK not matching
        
        

        Hi,

         

        Is it correct to have "user=phone" added only in ACK's To header
while it is missing in initial INVITE, even though both the messages use
Tel-URI.

         

        Please refer to the trace below:

         

        Request-Line: INVITE sip:[EMAIL PROTECTED] SIP/2.0

            Message Header

                Via: SIP/2.0/UDP
X.X.X.X:5060;branch=z9hG4bKf0m63e30306gvdocj180.1

                To: <sip:[EMAIL PROTECTED];transport=UDP>

                From: <sip:[EMAIL PROTECTED];user=phone>;tag=t570lgsc

                Call-ID: 10.6.0.13450701228437693202

                CSeq: 2 INVITE

                Max-Forwards: 66

                Content-Length: 211

                Contact: <sip:[EMAIL PROTECTED]:5060;transport=udp>

                Content-Type: application/sdp

                Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, PRACK

                Accept: application/sdp

                

            Status-Line: SIP/2.0 100 Trying

            Message Header

                Via: SIP/2.0/UDP
X.X.X.X:5060;branch=z9hG4bKf0m63e30306gvdocj180.1

                f:<sip:[EMAIL PROTECTED];user=phone>;tag=t570lgsc

                t:<sip:[EMAIL PROTECTED];transport=UDP>

                i:10.6.0.13450701228437693202

                CSeq:2 INVITE

                l:0

         

            Status-Line: SIP/2.0 180 Ringing

            Message Header

                Via: SIP/2.0/UDP
X.X.X.X:5060;branch=z9hG4bKf0m63e30306gvdocj180.1

                f:<sip:[EMAIL PROTECTED];user=phone>;tag=t570lgsc

        
t:<sip:[EMAIL PROTECTED];transport=UDP>;tag=000000009EC7356300000
00000

                i:10.6.0.13450701228437693202

                CSeq:2 INVITE

                l:0

         

            Status-Line: SIP/2.0 200 OK

            Message Header

                Via: SIP/2.0/UDP
X.X.X.X:5060;branch=z9hG4bKf0m63e30306gvdocj180.1

                f:<sip:[EMAIL PROTECTED];user=phone>;tag=t570lgsc

        
t:<sip:[EMAIL PROTECTED];transport=UDP>;tag=000000009EC7356300000
00000

                i:10.6.0.13450701228437693202

                CSeq:2 INVITE

                c:application/sdp

                m:<sip:172.20.192.109:5060>

                l:203

            

            Request-Line: ACK sip:172.20.192.109:5060 SIP/2.0

            Message Header

                Via: SIP/2.0/UDP
X.X.X.X:5060;branch=z9hG4bKf0m63e30306gvdocj180.1

                To:
<sip:[EMAIL PROTECTED];transport=UDP;user=phone>;tag=000000009EC7
35630000000000

                From: <sip:[EMAIL PROTECTED];user=phone>;tag=t570lgsc

                Call-ID: 10.6.0.13450701228437693202

                CSeq: 2 ACK

                Max-Forwards: 68

                Content-Length: 0

         

         

        Regards,

        Sunil

_______________________________________________
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

Reply via email to