Hi Raghu,
are the two scenarios running directly against each other, or is there
your Application between them? I am a bit nervous about your use of
cseq, as you set it manually to 1 in case of INVITE and let SIPp choose
the value for the CANCEL; if SIPp automatically chooses any other value
than 1 for the CANCEL's CSeq, and if the A scenario does not talk
directly to B scenario, the SIP-compliant UAS of the A scenario is
unable to pair the CANCEL with the INVITE because the CSeq numeric part
differs while RFC3261 requires that it is the same (while the method
name must differ). This would explain why the UAS of the A scenario
would not send a 200 with CANCEL Cseq and 487 with INVITE CSeq in
response to the CANCEL, but a 408 with INVITE CSeq because it could not
respond the INVITE before timeout.
Pavel
Dne 6.1.2016 v 16:32 SREE RAGHURAM PATTABHI napsal(a):
Hi,
I am using SIPP scripts (attached) where I simulate a A party CANCEL
scenario.
On receiving CANCEL at B party side, 487 is sent back to application
where the application should send 487 back to A party. But, at the A
party 408 is received instead of 487.
However, I tested this scenario using PureTest and that worked as
expected.
Any help on this is much appreciated. Am I missing some tags or
message format is wrong?
Below is the SIPp screen data where the test case is executed:
*B party
---------------*
Messages Retrans Timeout
Unexpected-Msg
----------> INVITE 1 0 0 0
<---------- 100 1 0
<---------- 180 1 0
----------> CANCEL 1 0 0 0
<---------- 200 1 0
<---------- 487 1 0
----------> ACK 1 0 0 0
------------------------------ Test Terminated
--------------------------------
*A Party
------------*
Messages Retrans Timeout
Unexpected-Msg
INVITE ----------> 1 0
100 <---------- 1 0 0 0
180 <---------- 1 0 0 0
Pause [ 3000ms] 1 0
CANCEL ----------> 1 0
200 <---------- 1 0 0 0
487 <---------- 0 0 0 1
ACK ----------> 0 0
------------------------------ Test Terminated
--------------------------------
----------------------------- Statistics Screen ------- [1-9]: Change
Screen --
Start Time | 2016-01-06 20:53:04.858797 1452093784.858797
Last Reset Time | 2016-01-06 20:53:08.005545 1452093788.005545
Current Time | 2016-01-06 20:53:08.008142 1452093788.008142
-------------------------+---------------------------+--------------------------
Counter Name | Periodic value | Cumulative value
-------------------------+---------------------------+--------------------------
Elapsed Time | 00:00:00:002000 | 00:00:03:149000
Call Rate | 0.000 cps | 0.318 cps
-------------------------+---------------------------+--------------------------
Incoming call created | 0 | 0
OutGoing call created | 0 | 1
Total Call created | | 1
Current Call | 0 |
-------------------------+---------------------------+--------------------------
Successful call | 0 | 0
Failed call | 0 | 1
-------------------------+---------------------------+--------------------------
Call Length | 00:00:00:000000 | 00:00:03:037000
------------------------------ Test Terminated
--------------------------------
2016-01-06 20:53:08.000062 1452093788.000062: Aborting call on
unexpected message for Call-Id '[email protected]
<mailto:[email protected]>': while expecting '487' (index 6),
received 'SIP/2.0 408 Request Timeout
To: Callee02 <sip:[email protected]
<mailto:sip%[email protected]>>;tag=proxy408-58e10ce4
Via: SIP/2.0/TCP 10.184.46.83:25090;branch=z9hG4bK-11854-1-0
CSeq: 1 INVITE
Content-Length: 0
Call-ID: [email protected] <mailto:[email protected]>
From: Caller01 <sip:[email protected]
<mailto:sip%[email protected]>>;tag=1
--
Thanks,
Raghu,
09886828155 <tel:09886828155>
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
