echarts.org - Re:unexpected retx timer expire??

Main Menu

Login Form

Home

Forums

	ECharts	Forum Threaded View

Welcome, Guest

ECharts

KitCAT

Re:unexpected retx timer expire?? (0 viewing)

Favoured: 0

TOPIC: Re:unexpected retx timer expire??

Forum Tools

#468

Russell Roy (User)

Junior Boarder

Posts: 39

unexpected retx timer expire?? 2 Months ago

The attached basic alice-calls-bob test passes all assertions but I'm just noticing now that there's an extra and unexpected 200 OK retransmission just 5ms after the first 200 OK in response to INVITE. The logger INFO message is labeled "Timer-0" suggesting to me that a timer expiration triggered the retransmit.

I tried playing around w/ the pause time (2000 ms) to no avail. This behavior is repeatable and consistent but for a small variation in the time between the first (expected) 200 and the second unexpected (4-10ms)

Is the kitcat app or the jain-sip stack in charge of this retransmission? A config err or a bug?

(I'm using rev 1660 echart and test built from source)

the test body...

Code: :


             setImplicitPause(2000);
                        logger.info("Basic call test.");
            logger.info(Alice+" is calling "+Bob);
            alice.call(bob);
            assertThat(alice, has(recvdResponse(100)));
            assertThat(bob, is(invited()));
            logger.info(Bob+" sends 180.");
            bob.sendResponse(180);
            logger.info(Bob+" answers.");
            bob.answer();
            assertThat(alice, is(connected()));
            assertThat(bob, is(connected()));

            processSIPAndCheckMedia(alice, bob);
            
            logger.info(Alice+" and "+Bob+" hang up.");
            alice.end();
            assertThat(alice, is(disconnected()));
            assertThat(bob, is(disconnected()));
            
            logger.info("Test passed!!");

And the run log...

Code: :


 
13639 [main] INFO  KitCAT.Tester  - Basic call test.
13640 [main] INFO  KitCAT.Tester  - EIT-Hammer-01 is calling EIT-Hammer-02
13641 [main] INFO  KitCAT.Tester  - EIT-Hammer-01 sends INVITE to EIT-Hammer-02
13677 [main] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717412999"
isSender="true" 
transactionId="z9hg4bka0dc3e52b25714ed67536cb3b2612c4e373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="INVITE sip:
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 :5060 SIP/2.0" 
>
<![CDATA[INVITE sip:EIT-Hammer-02@192.168.32.153:5060 SIP/2.0

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

CSeq: 1 INVITE

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

To: <sip:EIT-Hammer-02@192.168.32.153:5060>

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bKa0dc3e52b25714ed67536cb3b2612c4e373636

Max-Forwards: 70

Contact: <sip:EIT-Hammer-01@192.168.32.153:5060>

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-01 Fri Jul 09 19:16:40 EDT 2010

Allow: INVITE,BYE,CANCEL,ACK,PRACK,INFO

Content-Type: application/sdp

Route: <sip:scscf@172.16.40.23:6060;lr;role=orig>

Supported: 100rel,replaces

Content-Length: 182



v=0

o=user1 9 2 IN IP4 192.168.32.153

s=media session

c=IN IP4 192.168.32.153

t=0 0

m=audio 46932 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

]]>
</message>

13688 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717413010"
isSender="false" 
transactionId="z9hg4bka0dc3e52b25714ed67536cb3b2612c4e373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="SIP/2.0 100 Trying" 
>
<![CDATA[SIP/2.0 100 Trying

To: <sip:EIT-Hammer-02@192.168.32.153:5060>

CSeq: 1 INVITE

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bKa0dc3e52b25714ed67536cb3b2612c4e373636

Server: Glassfish_SIP_2.0.0

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

Content-Length: 0



]]>
</message>

13839 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717413147"
isSender="false" 
transactionId="z9hg4bkdaac9d1bdad014854591be9477a3483f6b32" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="INVITE sip:
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 :5060 SIP/2.0" 
>
<![CDATA[INVITE sip:EIT-Hammer-02@192.168.32.153:5060 SIP/2.0

Record-Route: <sip:172.16.40.23:5060;fid=server_2;lr>,<sip:172.16.40.23:6060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>

Contact: <sip:EIT-Hammer-01@172.16.40.133:5060;fid=server_1>

CSeq: 1 INVITE

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-01 Fri Jul 09 19:16:40 EDT 2010

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

Server: SafariTas

Max-Forwards: 65

Allow: INVITE,CANCEL,ACK,BYE,SUBSCRIBE,NOTIFY,OPTIONS

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac9d1bdad014854591be9477a3483f6b32,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaaccb2cc3604c514450852601858941e361,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac99542eea8cef45b7ab25694444ef7065

P-Charging-Vector: icid-value=CPC-PZXCFG455EREQDETMKLIT689IJKUF;icid-generated-at=172.16.40.23;orig-ioi=45678

Content-Type: application/sdp

Accept: application/sdp

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Content-Length: 182



v=0

o=user1 9 2 IN IP4 192.168.32.153

s=media session

c=IN IP4 192.168.32.153

t=0 0

m=audio 46932 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

]]>
</message>

13868 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717413190"
isSender="true" 
transactionId="z9hg4bkdaac9d1bdad014854591be9477a3483f6b32" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="SIP/2.0 100 Trying" 
>
<![CDATA[SIP/2.0 100 Trying

To: <sip:EIT-Hammer-02@192.168.32.153:5060>

CSeq: 1 INVITE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac9d1bdad014854591be9477a3483f6b32,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaaccb2cc3604c514450852601858941e361,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac99542eea8cef45b7ab25694444ef7065

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Content-Length: 0



]]>
</message>

15687 [main] INFO  KitCAT.Tester  - EIT-Hammer-02 sends 180.
15699 [main] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717415020"
isSender="true" 
transactionId="z9hg4bkdaac9d1bdad014854591be9477a3483f6b32" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="SIP/2.0 180 Ringing" 
>
<![CDATA[SIP/2.0 180 Ringing

Record-Route: <sip:172.16.40.23:5060;fid=server_2;lr>,<sip:172.16.40.23:6060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 1 INVITE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac9d1bdad014854591be9477a3483f6b32,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaaccb2cc3604c514450852601858941e361,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac99542eea8cef45b7ab25694444ef7065

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Contact: <sip:192.168.32.153:5060>

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-02 Fri Jul 09 19:16:44 EDT 2010

Supported: 100rel,replaces

Content-Length: 0



]]>
</message>

15719 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717415041"
isSender="false" 
transactionId="z9hg4bka0dc3e52b25714ed67536cb3b2612c4e373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="SIP/2.0 180 Ringing" 
>
<![CDATA[SIP/2.0 180 Ringing

Record-Route: <sip:172.16.40.23:6060;fid=server_2;lr>,<sip:172.16.40.23:5060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=gbfnc02y-40

Contact: <sip:172.16.40.133:5060;fid=server_1>

CSeq: 1 INVITE

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bKa0dc3e52b25714ed67536cb3b2612c4e373636

P-Charging-Vector: icid-value=CPC-PZXCFG455EREQDETMKLIT689IJKUF;icid-generated-at=172.16.40.23;orig-ioi=45678

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

Server: Glassfish_SIP_2.0.0

Content-Length: 0



]]>
</message>

17706 [main] INFO  KitCAT.Tester  - EIT-Hammer-02 answers.
17707 [main] INFO  KitCAT.Tester  - EIT-Hammer-02 sends 200 response to INVITE
17713 [main] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717417035"
isSender="true" 
transactionId="z9hg4bkdaac9d1bdad014854591be9477a3483f6b32" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="SIP/2.0 200 OK" 
>
<![CDATA[SIP/2.0 200 OK

Record-Route: <sip:172.16.40.23:5060;fid=server_2;lr>,<sip:172.16.40.23:6060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 1 INVITE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac9d1bdad014854591be9477a3483f6b32,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaaccb2cc3604c514450852601858941e361,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac99542eea8cef45b7ab25694444ef7065

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Contact: <sip:192.168.32.153:5060>

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-02 Fri Jul 09 19:16:44 EDT 2010

Content-Type: application/sdp

Supported: 100rel,replaces

Content-Length: 182



v=0

o=user1 9 2 IN IP4 192.168.32.153

s=media session

c=IN IP4 192.168.32.153

t=0 0

m=audio 41548 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

]]>
</message>

17718 [Timer-0] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717417040"
isSender="true" 
transactionId="z9hg4bkdaac9d1bdad014854591be9477a3483f6b32" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="SIP/2.0 200 OK" 
>
<![CDATA[SIP/2.0 200 OK

Record-Route: <sip:172.16.40.23:5060;fid=server_2;lr>,<sip:172.16.40.23:6060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 1 INVITE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac9d1bdad014854591be9477a3483f6b32,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaaccb2cc3604c514450852601858941e361,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac99542eea8cef45b7ab25694444ef7065

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Contact: <sip:192.168.32.153:5060>

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-02 Fri Jul 09 19:16:44 EDT 2010

Content-Type: application/sdp

Supported: 100rel,replaces

Content-Length: 182



v=0

o=user1 9 2 IN IP4 192.168.32.153

s=media session

c=IN IP4 192.168.32.153

t=0 0

m=audio 41548 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

]]>
</message>

17726 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717417046"
isSender="false" 
transactionId="z9hg4bkdaac0d8531ddd87343ee9fdf08e091a708b6" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="ACK sip:192.168.32.153:5060 SIP/2.0" 
>
<![CDATA[ACK sip:192.168.32.153:5060 SIP/2.0

Max-Forwards: 65

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 1 ACK

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac0d8531ddd87343ee9fdf08e091a708b6,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaac6f595c77b8f34e8484ed9f2e50d364c6,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaace1bd77c66fb74b9f9ab2cb132ee5cd6d

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Content-Length: 0



]]>
</message>

17895 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717417216"
isSender="false" 
transactionId="z9hg4bkdaac187a16031f444bc7b7e066fbdb89bd0f" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="ACK sip:192.168.32.153:5060 SIP/2.0" 
>
<![CDATA[ACK sip:192.168.32.153:5060 SIP/2.0

Max-Forwards: 65

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 1 ACK

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac187a16031f444bc7b7e066fbdb89bd0f,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaac40c027e308784ecc8f9da94e0dfd7daf,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaaca6f4101f472d487cb5e4c9061cd7fbb1

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Content-Length: 0



]]>
</message>

17906 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717417229"
isSender="false" 
transactionId="z9hg4bka0dc3e52b25714ed67536cb3b2612c4e373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="SIP/2.0 200 OK" 
>
<![CDATA[SIP/2.0 200 OK

Record-Route: <sip:172.16.40.23:6060;fid=server_2;lr>,<sip:172.16.40.23:5060;fid=server_1;lr>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=gbfnc02y-40

Contact: <sip:172.16.40.133:5060;fid=server_1>

CSeq: 1 INVITE

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bKa0dc3e52b25714ed67536cb3b2612c4e373636

P-Charging-Vector: icid-value=CPC-PZXCFG455EREQDETMKLIT689IJKUF;icid-generated-at=172.16.40.23;orig-ioi=45678

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

Content-Type: application/sdp

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

Server: Glassfish_SIP_2.0.0

Content-Length: 182



v=0

o=user1 9 2 IN IP4 192.168.32.153

s=media session

c=IN IP4 192.168.32.153

t=0 0

m=audio 41548 RTP/AVP 0 101

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

]]>
</message>

17917 [UDPMessageChannelThread] INFO  KitCAT.Tester  - sending ack to 200 ok to INVITE
17923 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:6060" 
time="1278717417245"
isSender="true" 
transactionId="z9hg4bkb7f3d952eb217d790ab1bfa5b09da33f373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="ACK sip:172.16.40.133:5060;fid=server_1 SIP/2.0" 
>
<![CDATA[ACK sip:172.16.40.133:5060;fid=server_1 SIP/2.0

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

CSeq: 1 ACK

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bKb7f3d952eb217d790ab1bfa5b09da33f373636

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=gbfnc02y-40

Max-Forwards: 70

Route: <sip:scscf@172.16.40.23:6060;lr;role=orig>

Supported: 100rel,replaces

Content-Length: 0



]]>
</message>

19717 [main] INFO  KitCAT.Tester  - checking media connectivity between EIT-Hammer-01 and EIT-Hammer-02
23731 [main] INFO  KitCAT.Tester  - EIT-Hammer-01 and EIT-Hammer-02 hang up.
23759 [main] INFO  KitCAT.Tester  - EIT-Hammer-01 sends BYE 
23788 [main] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717423108"
isSender="true" 
transactionId="z9hg4bk31b032e1342140f11bedeb197eeab0a9373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="BYE sip:172.16.40.133:5060;fid=server_1 SIP/2.0" 
>
<![CDATA[BYE sip:172.16.40.133:5060;fid=server_1 SIP/2.0

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bK31b032e1342140f11bedeb197eeab0a9373636

CSeq: 2 BYE

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=gbfnc02y-40

P-Charging-Vector: icid-value=CPC-PZXCFG455EREQDETMKLIT689IJKUF;icid-generated-at=172.16.40.23;orig-ioi=45678

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

Max-Forwards: 70

Route: <sip:scscf@172.16.40.23:6060;lr;role=orig>

Supported: 100rel,replaces

Content-Length: 0



]]>
</message>

23797 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717423119"
isSender="false" 
transactionId="z9hg4bk31b032e1342140f11bedeb197eeab0a9373636" 
callId="
 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 " 
firstLine="SIP/2.0 200 OK" 
>
<![CDATA[SIP/2.0 200 OK

P-Asserted-Identity: <sip:EIT-Hammer-01@imscore.net>

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=gbfnc02y-40

CSeq: 2 BYE

Via: SIP/2.0/UDP 192.168.32.153:5060;branch=z9hG4bK31b032e1342140f11bedeb197eeab0a9373636

P-Charging-Vector: icid-value=CPC-PZXCFG455EREQDETMKLIT689IJKUF;icid-generated-at=172.16.40.23;orig-ioi=45678

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=EIT-Hammer-01SipPort11278717400735

Call-ID: 0451362f05436de7422cd875aba3e5a2@192.168.32.153

Server: Glassfish_SIP_2.0.0

Content-Length: 0



]]>
</message>

23816 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="172.16.40.23:5060" 
to="192.168.32.153:5060" 
time="1278717423136"
isSender="false" 
transactionId="z9hg4bkdaac23a8b982cb7e42369406b05ab8dd3a1a" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="BYE sip:192.168.32.153:5060 SIP/2.0" 
>
<![CDATA[BYE sip:192.168.32.153:5060 SIP/2.0

Max-Forwards: 65

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

Contact: <sip:172.16.40.133:5060;fid=server_1>

CSeq: 2 BYE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac23a8b982cb7e42369406b05ab8dd3a1a,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaac6559400a8bea46608e4d1b92afe9164e,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac642d5af497ed471f87793eba95fdb1c5

P-Called-Party-ID: <sip:EIT-Hammer-02@192.168.32.153:5060>

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

Content-Length: 0



]]>
</message>

23831 [UDPMessageChannelThread] INFO  KitCAT.SipStack  - <message
from="192.168.32.153:5060" 
to="172.16.40.23:5060" 
time="1278717423152"
isSender="true" 
transactionId="z9hg4bkdaac23a8b982cb7e42369406b05ab8dd3a1a" 
callId="172.16.40.133_70_251460836088477844" 
firstLine="SIP/2.0 200 OK" 
>
<![CDATA[SIP/2.0 200 OK

To: <sip:EIT-Hammer-02@192.168.32.153:5060>;tag=EIT-Hammer-02SipPort11278717404866

CSeq: 2 BYE

Via: SIP/2.0/UDP 172.16.40.23:5060;branch=z9hG4bKdaac23a8b982cb7e42369406b05ab8dd3a1a,SIP/2.0/UDP 172.16.40.23:6060;branch=z9hG4bKdaac6559400a8bea46608e4d1b92afe9164e,SIP/2.0/UDP 172.16.40.133:5060;branch=z9hG4bKdaac642d5af497ed471f87793eba95fdb1c5

From: "EIT-Hammer-01" <sip:EIT-Hammer-01@192.168.32.153>;tag=gbfnbylm-3y

Call-ID: 172.16.40.133_70_251460836088477844

User-Agent: system.Regression.runBeforeEachTest.EIT-Hammer-02 Fri Jul 09 19:16:44 EDT 2010

Supported: 100rel,replaces

Content-Length: 0



]]>
</message>

25792 [main] INFO  KitCAT.Tester  - Test passed!!
25795 [main] INFO  KitCAT.Tester  - running test cleanup
39915 [main] INFO  KitCAT.Tester  - ====================

Report to moderator Logged

Logged

Last Edit: 2010/07/10 12:31 By rroy.

The administrator has disabled public write access.

#469

Gregory W. Bond (User)

Expert Boarder

Posts: 81

Re:unexpected retx timer expire?? 1 Month, 3 Weeks ago
hi russell - i just noticed your Q here - i didn't get it in my RSS feed, probably because of the website glitch last week - i'm not sure what's going on here - i'll confer with eric and tom and get back to you greg

Report to moderator Logged

Logged

The administrator has disabled public write access.

#470

Gregory W. Bond (User)

Expert Boarder

Posts: 81

Re:unexpected retx timer expire?? 1 Month, 3 Weeks ago
russell just looking at your test and log - this is as about a basic test as they get - as a data point, it's the jain sip stack underlying kitcat that's responsible for retransmissions - however, 5ms is too short a delay for retransmission (normally it's 0.5 sec) - a packet trace would be helpful - can you send one directly to me? greg

Report to moderator Logged

Logged

The administrator has disabled public write access.

#471

Russell Roy (User)

Junior Boarder

Posts: 39

Re:unexpected retx timer expire?? 1 Month, 3 Weeks ago

Ok, I rolled back the jain-sip to 1.2.86 and the problem seems to have gone away (limited testing).

So...I think I'm good for now. I don't know if the problem is carried forward to the latest and greatest jain-sip release version or if it was something that was specific to in or around the 1.2.118 release. I'll file a bug report w/ the stack maintainers should I need to or want to upgrade and find that the problem is still present.

Thanks for looking into this.

Report to moderator Logged

Logged

The administrator has disabled public write access.

Forum List

ECharts

KitCAT