Hi,
I recently noticed some problems in SIPp handling retransmissions.
SIPp (rev 121) seems to ignore the CSeq for identifying retransmission
responses, at least for the 407 response.
It should be easy to reproduce by just setting the retransmission
timeout to a low value.
I'm using the following scenario:
(1) <sent>
INVITE
CSeq: 1 INVITE
(2) <sent>
INVITE (retransmission)
CSeq: 1 INVITE
(3) <received>
407
CSeq: 1 INVITE
(4) <sent>
ACK
CSeq: 1 ACK
(5) <sent>
INVITE (with WWW-Authentication header)
CSeq: 2 INVITE
(6) <received>
407 (answer for retransmission)
CSeq: 1 INVITE
--> while expecting '100' response, received 'SIP/2.0 407'
Could anybody reproduce this?
regards,
Enrico
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users