History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: SFT-32
Type: Bug Bug
Status: In Progress In Progress
Priority: Minor Minor
Assignee: Nils Ohlmeier
Reporter: Frank Shearar
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
SF Test Framework

case905 raises spurious warning

Created: 2005-01-05 20:01   Updated: 2005-01-10 10:16
Component/s: test case
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. Text File debug.log (18 kb)


 Description  « Hide
The test results tell me:

Case 905: [Warning]
  Description: Request merging
               [Passed] : one request accepted, the other rejected
               [Warning] : received 18[03] for allready rejected INVITE

but this is the call flow (it's a bit long):

(Note that both 180s have as their Via branch the branch of the first INVITE - the warning is wrong because the framework hasn't yet received a final response for the first request, only for the second request.)

<<<< 2005/01/05 14:18:53.386
INVITE sip:abc@80.168.137.82 SIP/2.0
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
Call-ID: 137049516-41dbf74d@81.86.64.25
Content-Length: 150
Max-Forwards: 70

To: sip:abc@80.168.137.82
Contact: sip:sc@81.86.64.25
CSeq: 1 INVITE
Supported:
Content-Type: application/sdp

v=0
o=sc 1104934733 1104934733 IN IP4 81.86.64.25
s=Dummy on hold SDP
c=IN IP4 0.0.0.0
m=audio 65534 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=recvonly

>>>> 2005/01/05 14:18:53.433
SIP/2.0 100 Trying
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake


>>>> 2005/01/05 14:18:53.605
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82;tag=003FE84B65C33C0E


<<<< 2005/01/05 14:18:53.761
INVITE sip:abc@80.168.137.82 SIP/2.0

Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-second-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy2.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy2-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
Call-ID: 137049516-41dbf74d@81.86.64.25
Content-Length: 150
Max-Forwards: 70
To: sip:abc@80.168.137.82
Contact: sip:sc@81.86.64.25
CSeq: 1 INVITE
Supported:
Content-Type: application/sdp

v=0
o=sc 1104934733 1104934733 IN IP4 81.86.64.25
s=Dummy on hold SDP
c=IN IP4 0.0.0.0
m=audio 65534 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=recvonly

>>>> 2005/01/05 14:18:53.808
SIP/2.0 100 Trying
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-second-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy2.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy2-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake


>>>> 2005/01/05 14:18:53.839
SIP/2.0 482 Loop Detected
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-second-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy2.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy2-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82;tag=A08E13719766B97C


<<<< 2005/01/05 14:18:54.089
ACK sip:abc@80.168.137.82 SIP/2.0
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
Call-ID: 137049516-41dbf74d@81.86.64.25
Content-Length: 0
Max-Forwards: 70
To: sip:abc@80.168.137.82;tag=A08E13719766B97C
Contact: sip:sc@81.86.64.25
CSeq: 1 ACK


>>>> 2005/01/05 14:18:54.230
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82;tag=003FE84B65C33C0E


<<<< 2005/01/05 14:18:54.245
CANCEL sip:abc@80.168.137.82 SIP/2.0
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
Call-ID: 137049516-41dbf74d@81.86.64.25
Content-Length: 0
Max-Forwards: 70
To: sip:abc@80.168.137.82
Contact: sip:sc@81.86.64.25
CSeq: 1 CANCEL


>>>> 2005/01/05 14:18:54.308
SIP/2.0 200 OK
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 CANCEL
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82


>>>> 2005/01/05 14:18:54.401
SIP/2.0 482 Loop Detected
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-second-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy2.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy2-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82;tag=A08E13719766B97C


>>>> 2005/01/05 14:18:54.433
SIP/2.0 487 Request Terminated
Via: SIP/2.0/UDP 81.86.64.25;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-first-request;rport=5060;received=81.86.64.25
Via: SIP/2.0/UDP proxy1.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-proxy1-request1-fake
Via: SIP/2.0/UDP ua.example.com;branch=z9hG4bK-SCb-0-1104934733.31-81.86.64.25-ua-request-fake
Call-ID: 137049516-41dbf74d@81.86.64.25
CSeq: 1 INVITE
From: sip:sc@81.86.64.25;tag=SCt-0-1104934733.32-81.86.64.25~case905
To: sip:abc@80.168.137.82;tag=003FE84B65C33C0E

 All   Comments   Work Log   Change History      Sort Order:
[ Permlink | « Hide ]
Nils Ohlmeier - 2005-01-10 00:32
I added some code to give the warning only when the original request was not canceled yet.
Can you please verify if it helps?


Powered by a free Atlassian JIRA non-profit license for Sip Foundry. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.10-#260) - Bug/feature request - Contact Administrators