[sip-comm] Re: A bug in sip-communicator


#1

Hello Jen-Ruie,

There was a bug report by Fredrik Wickstrom, that was fixed yesterday.
You can check out [Issue 19]. I think it might very well be the problem
you describe so try checking out from CVS again or downloading the last
nightly build. Let me know if this doesn't work for you.

Cheers
Emil

Jen-Ruie Peng wrote:

···

Hi
I found a bug in sip-communicator, and I can't solve it.
First, I need to describe the scenario about this error.

            A B
         > >
         > INVITE F1 |
         >------------------>|
         > 200 OK F2 |
         ><------------------|
         > ACK F3 |
         >------------------>|
         > BYE F4 |
         >----------------- >|
         > >
'A' dial a call to 'B' and they are connected. Then, 'A' want to hang up
the call and press
the HangUp Button on Sip-Comuunicator. Thus A send a BYE message to B.
In this moment, 'B' can receive the BYE message, but can't handle this
request correctly.
So, 'B' will not send Response to 'A', and 'A' can't terminate the call
correctly.
(If the BYE message was sent by 'B', then the error will not happen.)

The problem is in the fuction "processRequest(RequestEvent
requestReceivedEvent)".
When B receive the RequestEvent(BYE), I found that the
"getNewServerTransaction(Request request)"
will return an Exception "Transaction not available". I can't figure out
why this happened and hope
you can help me. Thank you very much.

Jen-Ruie Peng

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#2

Hi Jen-Ruie,

(I'm CC-ing the list so that we keep that in the archives.)

I assume both A and B are running sip-communicator. Could you please
send us the stack log. (in the log directory of sip-communicator) as
well as the output that the sip-communicator dumps to the stdout?
It would be very handy if you could also provide us with a binary
ethereal/tcpdump capture of such a session

Thanks
Emil

Jen-Ruie Peng wrote:

···

Dear Emil,

Sorry, I download the last nightly build and execute it, but the same
problem happened. When 'A' establish the call to 'B' and 'A' hangup
the call , 'B' will not handle this BYE message (An exception:
"Transaction not available"). If 'A' establish the call to 'B' and 'B'
hangup the call, the problem will not happen.
It is so strange, and I can't solve it. Thank you for your help.

Jen-Ruie Peng

----- Original Message ----- From: "Emil Ivov" <emil_ivov@yahoo.com>
To: "Jen-Ruie Peng" <raypeng@exodus.cs.ccu.edu.tw>;
<users@sip-communicator.dev.java.net>
Sent: Wednesday, November 03, 2004 2:51 PM
Subject: Re: A bug in sip-communicator

Hello Jen-Ruie,

There was a bug report by Fredrik Wickstrom, that was fixed yesterday.
You can check out [Issue 19]. I think it might very well be the problem
you describe so try checking out from CVS again or downloading the last
nightly build. Let me know if this doesn't work for you.

Cheers
Emil

Jen-Ruie Peng wrote:

Hi
I found a bug in sip-communicator, and I can't solve it.
First, I need to describe the scenario about this error.

            A B
         > >
         > INVITE F1 |
         >------------------>|
         > 200 OK F2 |
         ><------------------|
         > ACK F3 |
         >------------------>|
         > BYE F4 |
         >----------------- >|
         > >
'A' dial a call to 'B' and they are connected. Then, 'A' want to hang up
the call and press
the HangUp Button on Sip-Comuunicator. Thus A send a BYE message to B.
In this moment, 'B' can receive the BYE message, but can't handle this
request correctly.
So, 'B' will not send Response to 'A', and 'A' can't terminate the call
correctly.
(If the BYE message was sent by 'B', then the error will not happen.)

The problem is in the fuction "processRequest(RequestEvent
requestReceivedEvent)".
When B receive the RequestEvent(BYE), I found that the
"getNewServerTransaction(Request request)"
will return an Exception "Transaction not available". I can't figure out
why this happened and hope
you can help me. Thank you very much.

Jen-Ruie Peng

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Jen-Ruie,

Thanks a lot for your input. We've found out the bug.

The thing is that once an Invite request is re-transmitted for
authorization it creates a new Dialog. Yet sip-communicator was using
the old one when sending the Bye request and as a result it was being
ignored by the remote party.

We've fixed the glitch and ignored your contribution.

Thanks!
Emil

Jen-Ruie Peng wrote:

···

Dear Emil
   sip:piggie@iptel.org login from 140.123.105.35
   sip:raypeng0315@iptel.org login from 140.123.105.20
   They both use sip-communicator and regist to iptel.org.
   The log files and ethereal capture files are in the added files.
   Thank you very much.
Jen-Ruie Peng

----- Original Message ----- From: "Emil Ivov" <emil_ivov@yahoo.com>
To: "Jen-Ruie Peng" <raypeng@exodus.cs.ccu.edu.tw>;
<dev@sip-communicator.dev.java.net>
Sent: Thursday, November 04, 2004 12:24 AM
Subject: Re: A bug in sip-communicator

Hi Jen-Ruie,

(I'm CC-ing the list so that we keep that in the archives.)

I assume both A and B are running sip-communicator. Could you please
send us the stack log. (in the log directory of sip-communicator) as
well as the output that the sip-communicator dumps to the stdout?
It would be very handy if you could also provide us with a binary
ethereal/tcpdump capture of such a session

Thanks
Emil

Jen-Ruie Peng wrote:

Dear Emil,

Sorry, I download the last nightly build and execute it, but the same
problem happened. When 'A' establish the call to 'B' and 'A' hangup
the call , 'B' will not handle this BYE message (An exception:
"Transaction not available"). If 'A' establish the call to 'B' and 'B'
hangup the call, the problem will not happen.
It is so strange, and I can't solve it. Thank you for your help.

Jen-Ruie Peng

----- Original Message ----- From: "Emil Ivov" <emil_ivov@yahoo.com>
To: "Jen-Ruie Peng" <raypeng@exodus.cs.ccu.edu.tw>;
<users@sip-communicator.dev.java.net>
Sent: Wednesday, November 03, 2004 2:51 PM
Subject: Re: A bug in sip-communicator

Hello Jen-Ruie,

There was a bug report by Fredrik Wickstrom, that was fixed yesterday.
You can check out [Issue 19]. I think it might very well be the problem
you describe so try checking out from CVS again or downloading the last
nightly build. Let me know if this doesn't work for you.

Cheers
Emil

Jen-Ruie Peng wrote:

Hi
I found a bug in sip-communicator, and I can't solve it.
First, I need to describe the scenario about this error.

            A B
         > >
         > INVITE F1 |
         >------------------>|
         > 200 OK F2 |
         ><------------------|
         > ACK F3 |
         >------------------>|
         > BYE F4 |
         >----------------- >|
         > >
'A' dial a call to 'B' and they are connected. Then, 'A' want to
hang up
the call and press
the HangUp Button on Sip-Comuunicator. Thus A send a BYE message to B.
In this moment, 'B' can receive the BYE message, but can't handle this
request correctly.
So, 'B' will not send Response to 'A', and 'A' can't terminate the
call
correctly.
(If the BYE message was sent by 'B', then the error will not happen.)

The problem is in the fuction "processRequest(RequestEvent
requestReceivedEvent)".
When B receive the RequestEvent(BYE), I found that the
"getNewServerTransaction(Request request)"
will return an Exception "Transaction not available". I can't
figure out
why this happened and hope
you can help me. Thank you very much.

Jen-Ruie Peng

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net