[jitsi-dev] Unexpected Token : SIP


#1

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401 Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
聽聽at gov.nist.core.LexerCore.match(LexerCore.java:231)
聽聽at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
聽聽at gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
聽聽at gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
聽聽at gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
聽聽at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
聽聽at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
聽聽at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER

From: "Watson" <sip:watson@example.com>;tag=f439fe42

Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for this?

Regards,
Chris

路路路

To: "Watson" <sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8


#2

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

路路路

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401 Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
at gov.nist.core.LexerCore.match(LexerCore.java:231)
at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
at gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
at gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
at gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson" <sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for this?

Regards,
Chris


#3

Hey Chris,

Sounds like a jsip problem. Have you managed to pinpoint the symbol that
causes the problem? Do you think it is actually a valid symbol that
should be permitted by jsip?

Cheers,
Emil

袧邪 31.08.11 19:12, Chris Maciejewski 薪邪锌懈褋邪:

路路路

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401 Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
聽聽聽聽聽聽聽at gov.nist.core.LexerCore.match(LexerCore.java:231)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
聽聽聽聽聽聽聽at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
聽聽聽聽聽聽聽at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
聽聽聽聽聽聽聽at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson" <sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for this?

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#4

JSIP only understands English! :slight_smile: ( Not Turkish.) :slight_smile:

1. Are you using TCP as your transport ?

2. Can you reproduce the problem consistently and can you post a debug log?

Ranga

路路路

On 9/9/11, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

Sounds like a jsip problem. Have you managed to pinpoint the symbol that
causes the problem? Do you think it is actually a valid symbol that
should be permitted by jsip?

Cheers,
Emil

袧邪 31.08.11 19:12, Chris Maciejewski 薪邪锌懈褋邪:

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401 Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
聽聽聽聽聽聽聽at gov.nist.core.LexerCore.match(LexerCore.java:231)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
聽聽聽聽聽聽聽at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson"
<sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for
this?

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
M. Ranganathan


#5

More questions:

If you are using TCP, can you tell if the previous message was correctly framed?

If you are using TCP, there could be an issue with threading
(re-entrancy) where two threads are trying to read messages at the
same time. Is this the case?

路路路

On 9/9/11, M. Ranganathan <mranga@gmail.com> wrote:

JSIP only understands English! :slight_smile: ( Not Turkish.) :slight_smile:

1. Are you using TCP as your transport ?

2. Can you reproduce the problem consistently and can you post a debug log?

Ranga

On 9/9/11, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

Sounds like a jsip problem. Have you managed to pinpoint the symbol that
causes the problem? Do you think it is actually a valid symbol that
should be permitted by jsip?

Cheers,
Emil

袧邪 31.08.11 19:12, Chris Maciejewski 薪邪锌懈褋邪:

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401
Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
聽聽聽聽聽聽聽at gov.nist.core.LexerCore.match(LexerCore.java:231)
聽聽聽聽聽聽聽at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
聽聽聽聽聽聽聽at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
聽聽聽聽聽聽聽at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson"
<sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for
this?

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
M. Ranganathan

--
M. Ranganathan


#6

Hi, I don't use TCP. Plain normal UDP. There are no Turkish characters
in REGISTER packet.

I can consistently reproduce the problem which is:

A correctly formatted REGISTER packet (ASCII characters only) is sent
my Jitsi to SIP server via UDP port 5060.

If Jitsi language is set to Turkish an exception is logged as below
and registration fails.

When language is set to any other but Turkish everything works as expected.

Please let me know if you need any more information or log/trace files.

Regards
Chris

路路路

On 9 September 2011 13:25, M. Ranganathan <mranga@gmail.com> wrote:

More questions:

If you are using TCP, can you tell if the previous message was correctly framed?

If you are using TCP, there could be an issue with threading
(re-entrancy) where two threads are trying to read messages at the
same time. Is this the case?

On 9/9/11, M. Ranganathan <mranga@gmail.com> wrote:

JSIP only understands English! :slight_smile: ( Not Turkish.) :slight_smile:

1. Are you using TCP as your transport ?

2. Can you reproduce the problem consistently and can you post a debug log?

Ranga

On 9/9/11, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

Sounds like a jsip problem. Have you managed to pinpoint the symbol that
causes the problem? Do you think it is actually a valid symbol that
should be permitted by jsip?

Cheers,
Emil

袧邪 31.08.11 19:12, Chris Maciejewski 薪邪锌懈褋邪:

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401
Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
at gov.nist.core.LexerCore.match(LexerCore.java:231)
at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
at
gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
at
gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson"
<sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for
this?

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
M. Ranganathan

--
M. Ranganathan


#7

Hi,

we committed a fix for this issue. You can try and test with build
4018. Is it ok now?

Regards
damencho

路路路

On Fri, Sep 9, 2011 at 6:53 PM, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi, I don't use TCP. Plain normal UDP. There are no Turkish characters
in REGISTER packet.

I can consistently reproduce the problem which is:

A correctly formatted REGISTER packet (ASCII characters only) is sent
my Jitsi to SIP server via UDP port 5060.

If Jitsi language is set to Turkish an exception is logged as below
and registration fails.

When language is set to any other but Turkish everything works as expected.

Please let me know if you need any more information or log/trace files.

Regards
Chris

On 9 September 2011 13:25, M. Ranganathan <mranga@gmail.com> wrote:

More questions:

If you are using TCP, can you tell if the previous message was correctly framed?

If you are using TCP, there could be an issue with threading
(re-entrancy) where two threads are trying to read messages at the
same time. Is this the case?

On 9/9/11, M. Ranganathan <mranga@gmail.com> wrote:

JSIP only understands English! :slight_smile: ( Not Turkish.) :slight_smile:

1. Are you using TCP as your transport ?

2. Can you reproduce the problem consistently and can you post a debug log?

Ranga

On 9/9/11, Emil Ivov <emcho@jitsi.org> wrote:

Hey Chris,

Sounds like a jsip problem. Have you managed to pinpoint the symbol that
causes the problem? Do you think it is actually a valid symbol that
should be permitted by jsip?

Cheers,
Emil

袧邪 31.08.11 19:12, Chris Maciejewski 薪邪锌懈褋邪:

OK, it turns out the problem isn't related to a race condition, but to
a locale settings.

The error below happens when UI language is set to Turkish!!

Other locales (tested Arabic, Spanish, Polish) works fine, so it seems
only Turkish causes the problem.

Regard,
Chris

On 31 August 2011 16:31, Chris Maciejewski <chris@wima.co.uk> wrote:

Hi,

In some circumstances (I am not sure what yet - still investigating :frowning:
Jitsi is not accepting it would seem correctly formatted 401
Unauthorized
response to REGISTER message, logging error as below:

18:10:09.896 WARNING: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: [C@28c7a1
Unexpected Token : SIP
18:10:09.896 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: [C@28c7a1
Unexpected Token : SIP
at gov.nist.core.LexerCore.match(LexerCore.java:231)
at gov.nist.javax.sip.parser.Parser.sipVersion(Parser.java:58)
at
gov.nist.javax.sip.parser.StatusLineParser.parse(StatusLineParser.java:77)
at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:248)
at
gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:158)
at
gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
at
gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
at java.lang.Thread.run(Unknown Source)
18:10:09.896 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: BAD MESSAGE!
18:10:09.897 SEVERE: impl.protocol.sip.SipLogger.logError().112 Error
from the JAIN-SIP stack: SIP/2.0 401 Unauthorized
Call-ID: c9538f3ae2096b1c9fdc82848ef9718b@0:0:0:0:0:0:0:0
CSeq: 1 REGISTER
From: "Watson" <sip:watson@example.com>;tag=f439fe42
To: "Watson"
<sip:watson@example.com>;tag=e7f65b167981947c703f953b608a150e.cff8
Via: SIP/2.0/UDP
192.168.1.2:15511;branch=z9hG4bK-313836-5cee9473f1077cedd9683abd0b3ff5d1;rport=15511;received=10.10.10.200
WWW-Authenticate: Digest realm="example.com",
nonce="4e5e4ef0000102246ff175c1bf65c0ddcd7d9ce2afdb3f29"
Server: SIP Proxy 2
Content-Length: 0

After a quick search on Google some people say this is related to race
condition bug present in JAIN-SIP

Any pointers where should I be looking to pinpoint the exact reason for
this?

Regards,
Chris

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
M. Ranganathan

--
M. Ranganathan