Looks like my SIPp script sets the wrong branch when I get a 407 response
and tries to send an ACK on this final response, is this a know problem?
The scenario is:
* send invite
* rec optional 100, 500, 503
* rec 407
* send ACK
* send INVITE with digest info
In the send ACK I have the following
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: <sip:[EMAIL PROTECTED]>;tag=[call_number]
To: <sip:[EMAIL PROTECTED]>[peer_tag_param]
but the ACK that is sent dont have the same branch as the first INVITE sent.
This causes the receveing end to retransmit the 407.
I did read in the forum that some time ago someone had a similar problem and
he got the tip that he should remove the receiving of a 407 since branch
would work ok for a ACK on an unexpected message. When doing this, sipp
complains that I cant have optional responses only between the first and the
second Invite
Im using SIPp v2.0.1-TLS-PCAP, version 20070516, built May 16 2007, 11:06:11
Regards,
// Andreas
_______________________________
Andreas Byström
Software Engineer
Teligent AB
Konsul Jonssons väg 17
P.O. Box 213
SE 14923 Nynäshamn
mail: [EMAIL PROTECTED]
web: www.teligent.se <http://www.teligent.se/>
phone: +46 (0)8 4101 7221
mobile: +46 (0)733 1172 21
fax: +46 (0)8 520 193 36
_______________________________
-------------------------------------------------------------------------
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
