Hi all,
I have written a B side script for a simple basic call. It looks like this:
----------> INVITE
<---------- 407
----------> ACK
----------> INVITE
<---------- 100
<---------- 180
<---------- 200
----------> ACK
----------> BYE
<---------- 200
However it seems that I get dead calls in some scenarios... When the script
receives an INVITE it sends 100, 180 and then 200 and then wait for an ACK. If
the responses was lost or does not reach UAC before the retransmit timer
triggers, UAC will resend the INVITE. The problem is that when this happens I
get a dead call since it was expecting an ACK. Could I have done something
wrong, shouldn't SIPp realize that this is a retransmit of a request that it
has already sent an final response to and just send the 200 OK again?
I did try to insert a pause between the 180 and 200 but I still get the same
error, in the statistics for the running scenario I can see "unexpected-msg"
for Pause. Looks like it's the INVITE again
("2009-02-24 12:42:09:946 1235475729.946690: Dead call
efc13232-711c-4161-985b-170299da9a23 (aborted at index 6), received 'INVITE
sip:[email protected] SIP/2.0")
----------> INVITE
<---------- 407
----------> ACK
----------> INVITE
<---------- 100
<---------- 180
[ 2000ms] Pause
<---------- 200
----------> ACK
----------> BYE
<---------- 200
Anyone have a clue on how I can force the script to continue to run instead of
getting dead call?
Regards,
// Andreas
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
