AW: [sip-comm-dev] Exception after receiving 200/OK


#1

Hello Emil,

I got me the source code archive "nist-sip-1.2.src.zip"
from http://snad.ncsl.nist.gov/proj/iptel/nist-sip-downloads.html.

In jain-sip/src/gov/nist/javax/sip/stack/DialogImpl.java at line 1120
you'll find the javax.sip.Dialog.createRequest() implementation with
its comment header stating that it is not to be used to create ACK msg.

Is this the right version of source code I've looked at?

Best regards,
Thomas

···

-----Ursprüngliche Nachricht-----
Von: Emil Ivov [mailto:emil_ivov@yahoo.com]
Gesendet: Sonntag, 30. Mai 2004 18:53
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Exception after receiving 200/OK

Hello Thomas,

This seems to be a transaction problem of some sort. A tcpdump/ethereal
trace would help.

> According to the functions comment header this function is not to be
> used to create the ACK request! messageFactory.createRequest() is to
> be used instead!

Hm. Sounds strange. Where exactly did u read that?

Cheers
Emil

Thomas Ackermann wrote:

Hi all,

I found the sip-communicator receiving calls with no problems.
But when making calls I always get an Exception after receiving
the 200/OK response for INVITE.
After checking the source code of sip-communicator and jain-sip
stack I probably found the reason for that.

Function CallProcessing.processInviteOK() tries to create
the ACK request by calling the dialog (!) function:

    Request ack = (Request) clientTransaction.getDialog().createRequest(Request.ACK);

And here the Exception occurs because the dialog's state is null:

    "Dialog ... not yet established or terminated null"

According to the functions comment header this function is not to be
used to create the ACK request! messageFactory.createRequest() is to
be used instead!

Any comments from your side?

Best regads,
Thomas

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

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

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


#2

Hello Ranga,

It seems there's a small discrepancy in the method comment of

DialogImpl.createRequest(String method)

Lines 1109 through 1111 go as follows

* This
* method should not be used for Ack, that is the application should
* create the Ack from the MessageFactory.

Don't think this is relevant. Or is it?

The report came from Thomas Ackermann.

Tom, back to ur original problem. Could I please c a tcpdump/ethereal trace and sip-comm logs if possible?

Cheers
Emil

Thomas Ackermann wrote:

···

Hello Emil,

I got me the source code archive "nist-sip-1.2.src.zip"
from http://snad.ncsl.nist.gov/proj/iptel/nist-sip-downloads.html.

In jain-sip/src/gov/nist/javax/sip/stack/DialogImpl.java at line 1120
you'll find the javax.sip.Dialog.createRequest() implementation with
its comment header stating that it is not to be used to create ACK msg.

Is this the right version of source code I've looked at?

Best regards,
Thomas

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emil_ivov@yahoo.com]
Gesendet: Sonntag, 30. Mai 2004 18:53
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Exception after receiving 200/OK

Hello Thomas,

This seems to be a transaction problem of some sort. A tcpdump/ethereal trace would help.

> According to the functions comment header this function is not to be
> used to create the ACK request! messageFactory.createRequest() is to
> be used instead!

Hm. Sounds strange. Where exactly did u read that?

Cheers
Emil

Thomas Ackermann wrote:

Hi all,

I found the sip-communicator receiving calls with no problems.
But when making calls I always get an Exception after receiving
the 200/OK response for INVITE.
After checking the source code of sip-communicator and jain-sip
stack I probably found the reason for that.

Function CallProcessing.processInviteOK() tries to create
the ACK request by calling the dialog (!) function:

   Request ack = (Request) clientTransaction.getDialog().createRequest(Request.ACK);

And here the Exception occurs because the dialog's state is null:

   "Dialog ... not yet established or terminated null"

According to the functions comment header this function is not to be
used to create the ACK request! messageFactory.createRequest() is to
be used instead!

Any comments from your side?

Best regads,
Thomas

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

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

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

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


#3

Emil,
It does not look relevant to me (I'll fix the text none the less) but I would be curious to know why the Dialog has a null state. Did the dialog get terminated with a BYE or CANCEL on the INVITE before you could send the ACK. You may want to get the latest stack. I did some extensive performance hacking over the last few days and more performance tuning is on the way from another user. I'd like to test against it if I could .

Regards,

Ranga.

Emil Ivov wrote:

···

Hello Ranga,

It seems there's a small discrepancy in the method comment of

DialogImpl.createRequest(String method)

Lines 1109 through 1111 go as follows

* This
* method should not be used for Ack, that is the application should
* create the Ack from the MessageFactory.

Don't think this is relevant. Or is it?

The report came from Thomas Ackermann.

Tom, back to ur original problem. Could I please c a tcpdump/ethereal trace and sip-comm logs if possible?

Cheers
Emil

Thomas Ackermann wrote:

Hello Emil,

I got me the source code archive "nist-sip-1.2.src.zip"
from http://snad.ncsl.nist.gov/proj/iptel/nist-sip-downloads.html.

In jain-sip/src/gov/nist/javax/sip/stack/DialogImpl.java at line 1120
you'll find the javax.sip.Dialog.createRequest() implementation with
its comment header stating that it is not to be used to create ACK msg.

Is this the right version of source code I've looked at?

Best regards,
Thomas

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emil_ivov@yahoo.com]
Gesendet: Sonntag, 30. Mai 2004 18:53
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Exception after receiving 200/OK

Hello Thomas,

This seems to be a transaction problem of some sort. A tcpdump/ethereal trace would help.

> According to the functions comment header this function is not to be
> used to create the ACK request! messageFactory.createRequest() is to
> be used instead!

Hm. Sounds strange. Where exactly did u read that?

Cheers
Emil

Thomas Ackermann wrote:

Hi all,

I found the sip-communicator receiving calls with no problems.
But when making calls I always get an Exception after receiving
the 200/OK response for INVITE.
After checking the source code of sip-communicator and jain-sip
stack I probably found the reason for that.

Function CallProcessing.processInviteOK() tries to create
the ACK request by calling the dialog (!) function:

   Request ack = (Request) clientTransaction.getDialog().createRequest(Request.ACK);

And here the Exception occurs because the dialog's state is null:

   "Dialog ... not yet established or terminated null"

According to the functions comment header this function is not to be
used to create the ACK request! messageFactory.createRequest() is to
be used instead!

Any comments from your side?

Best regads,
Thomas

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

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

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

--
M. Ranganathan

Advanced Networking Technologies Divsion,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!


#4

Emil,

Now that I think of it, I believe this is the same problem sombeody else had reported in interacting with an asterix server (you were in on that email exchange). I think this has to do with the server not assigning tags. I have fixed this in the stack some time ago. You may want to update to the latest stack and see if the problem happens again.

Regards

Ranga

Emil Ivov wrote:

···

Hello Ranga,

It seems there's a small discrepancy in the method comment of

DialogImpl.createRequest(String method)

Lines 1109 through 1111 go as follows

* This
* method should not be used for Ack, that is the application should
* create the Ack from the MessageFactory.

Don't think this is relevant. Or is it?

The report came from Thomas Ackermann.

Tom, back to ur original problem. Could I please c a tcpdump/ethereal trace and sip-comm logs if possible?

Cheers
Emil

Thomas Ackermann wrote:

Hello Emil,

I got me the source code archive "nist-sip-1.2.src.zip"
from http://snad.ncsl.nist.gov/proj/iptel/nist-sip-downloads.html.

In jain-sip/src/gov/nist/javax/sip/stack/DialogImpl.java at line 1120
you'll find the javax.sip.Dialog.createRequest() implementation with
its comment header stating that it is not to be used to create ACK msg.

Is this the right version of source code I've looked at?

Best regards,
Thomas

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emil_ivov@yahoo.com]
Gesendet: Sonntag, 30. Mai 2004 18:53
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Exception after receiving 200/OK

Hello Thomas,

This seems to be a transaction problem of some sort. A tcpdump/ethereal trace would help.

> According to the functions comment header this function is not to be
> used to create the ACK request! messageFactory.createRequest() is to
> be used instead!

Hm. Sounds strange. Where exactly did u read that?

Cheers
Emil

Thomas Ackermann wrote:

Hi all,

I found the sip-communicator receiving calls with no problems.
But when making calls I always get an Exception after receiving
the 200/OK response for INVITE.
After checking the source code of sip-communicator and jain-sip
stack I probably found the reason for that.

Function CallProcessing.processInviteOK() tries to create
the ACK request by calling the dialog (!) function:

   Request ack = (Request) clientTransaction.getDialog().createRequest(Request.ACK);

And here the Exception occurs because the dialog's state is null:

   "Dialog ... not yet established or terminated null"

According to the functions comment header this function is not to be
used to create the ACK request! messageFactory.createRequest() is to
be used instead!

Any comments from your side?

Best regads,
Thomas

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

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

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

--
M. Ranganathan

Advanced Networking Technologies Divsion,
National Institute of Standards and Technology (NIST),
100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. tel:301 975 3664 , fax:301 590 0932 http://w3.antd.nist.gov/
Advanced Networking Technologies For the People!


#5

Hello, Ranga, Thomas

I have always tried to keep the stack as fresh as possible in the sip-communicator repository. And this is still the case (last commit was this morning).

So, Thomas you may wish to redownload and see whether this fixes ur problem.

Cheers
Emil

M. Ranganathan wrote:

···

Emil,

Now that I think of it, I believe this is the same problem sombeody else had reported in interacting with an asterix server (you were in on that email exchange). I think this has to do with the server not assigning tags. I have fixed this in the stack some time ago. You may want to update to the latest stack and see if the problem happens again.

Regards

Ranga

Emil Ivov wrote:

Hello Ranga,

It seems there's a small discrepancy in the method comment of

DialogImpl.createRequest(String method)

Lines 1109 through 1111 go as follows

* This
* method should not be used for Ack, that is the application should
* create the Ack from the MessageFactory.

Don't think this is relevant. Or is it?

The report came from Thomas Ackermann.

Tom, back to ur original problem. Could I please c a tcpdump/ethereal trace and sip-comm logs if possible?

Cheers
Emil

Thomas Ackermann wrote:

Hello Emil,

I got me the source code archive "nist-sip-1.2.src.zip"
from http://snad.ncsl.nist.gov/proj/iptel/nist-sip-downloads.html.

In jain-sip/src/gov/nist/javax/sip/stack/DialogImpl.java at line 1120
you'll find the javax.sip.Dialog.createRequest() implementation with
its comment header stating that it is not to be used to create ACK msg.

Is this the right version of source code I've looked at?

Best regards,
Thomas

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emil_ivov@yahoo.com]
Gesendet: Sonntag, 30. Mai 2004 18:53
An: dev@sip-communicator.dev.java.net
Betreff: Re: [sip-comm-dev] Exception after receiving 200/OK

Hello Thomas,

This seems to be a transaction problem of some sort. A tcpdump/ethereal trace would help.

> According to the functions comment header this function is not to be
> used to create the ACK request! messageFactory.createRequest() is to
> be used instead!

Hm. Sounds strange. Where exactly did u read that?

Cheers
Emil

Thomas Ackermann wrote:

Hi all,

I found the sip-communicator receiving calls with no problems.
But when making calls I always get an Exception after receiving
the 200/OK response for INVITE.
After checking the source code of sip-communicator and jain-sip
stack I probably found the reason for that.

Function CallProcessing.processInviteOK() tries to create
the ACK request by calling the dialog (!) function:

   Request ack = (Request) clientTransaction.getDialog().createRequest(Request.ACK);

And here the Exception occurs because the dialog's state is null:

   "Dialog ... not yet established or terminated null"

According to the functions comment header this function is not to be
used to create the ACK request! messageFactory.createRequest() is to
be used instead!

Any comments from your side?

Best regads,
Thomas

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

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

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

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