Bugs item #1749310, was opened at 2007-07-06 14:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=637564&aid=1749310&group_id=104305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Control
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alex Zhilyakov (azhilyakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Tag in From: is wrong on retransmissions

Initial Comment:
Hi,

I am using a sipp UAC scenario (with minor modifications). The following is 
From: header in BYE message from the scenario:

From: sipp <sip:[EMAIL PROTECTED]:[local_port]>;tag=[pid]SIPpTag00[call_number]

When sipp sends BYE, it sends it correctly:

From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=2944SIPpTag00114

However if BYE is lost and not responded to by server, sipp retransmits BYE 
incorrectly, i.e. "tag" is not correct:

From: sipp <sip:[EMAIL PROTECTED]:5060>;tag=114


So, tag second BYE is incorrect for two reasons: 1. it does not follow scenario 
rule; 2. it violates RFC 3261 section 12.2.1.1 which says that the From: must 
match dialog state.

I am using "SIPp v2.0.1-TLS-PCAP, version 20070521, built May 22 2007, 
12:49:03." for Windows (shame on me)


-Alex

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=637564&aid=1749310&group_id=104305

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to