[jitsi-dev] Numerours exceptions


#1

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport

From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8

To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---


#2

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

···

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---

--
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


#3

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and never had problems
(well, some standard problems with dtmf and the like ;-). I wanted to
give Jitsi
a try and replace Twinkle with it. But have numerous problems with it.

I will see to prepare the log files for you. What would be a valid SIP
request?
Would it be worth to make Jitsi more tolerant here?

Best regards,
Matt

···

Am 04.04.2012 14:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---


#4

Hey Matt,

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and never had problems
(well, some standard problems with dtmf and the like ;-). I wanted to
give Jitsi a try and replace Twinkle with it. But have numerous problems with it.

Jitsi is very widely used with Asterisk and I don't believe we have seen
similar behaviour so far. Can you tell us more on how you configured
your account in Jitsi? Did you enter the server address as part of your
user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser of the JSIP
stack that Jitsi uses, so we'd have to implement quite a lot of rule
breaking for this to work (provided we had a good reason to do this). We
have implemented such "hacks" previously and it did happen to be for
asterisk (and the way it handles message waiting indications) but this
is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with asterisk,
so I am more inclined to believe that this is a configuration error.

Cheers,
Emil

···

On 04.04.12 15:26, Buddy Butterfly wrote:

Best regards,
Matt

Am 04.04.2012 14:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---

--
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


#5

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy option.
Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

···

Am 04.04.2012 15:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and never had problems
(well, some standard problems with dtmf and the like ;-). I wanted to
give Jitsi a try and replace Twinkle with it. But have numerous problems with it.

Jitsi is very widely used with Asterisk and I don't believe we have seen
similar behaviour so far. Can you tell us more on how you configured
your account in Jitsi? Did you enter the server address as part of your
user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser of the JSIP
stack that Jitsi uses, so we'd have to implement quite a lot of rule
breaking for this to work (provided we had a good reason to do this). We
have implemented such "hacks" previously and it did happen to be for
asterisk (and the way it handles message waiting indications) but this
is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with asterisk,
so I am more inclined to believe that this is a configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---


#6

Hey Matt,

Account:
SIP-ID: The name without server is given.

This creates a ServerLess account (as shown on the example beneath).
Please create your account _with_ the @server part as shown on the
example underneath the field.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy option.
Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

ServerLess accounts become "online" without connecting to a server. They
just listen on your local machine.

Hope this helps,
Emil

···

On 04.04.12 16:11, Buddy Butterfly wrote:

Am 04.04.2012 15:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and never had problems
(well, some standard problems with dtmf and the like ;-). I wanted to
give Jitsi a try and replace Twinkle with it. But have numerous problems with it.

Jitsi is very widely used with Asterisk and I don't believe we have seen
similar behaviour so far. Can you tell us more on how you configured
your account in Jitsi? Did you enter the server address as part of your
user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser of the JSIP
stack that Jitsi uses, so we'd have to implement quite a lot of rule
breaking for this to work (provided we had a good reason to do this). We
have implemented such "hacks" previously and it did happen to be for
asterisk (and the way it handles message waiting indications) but this
is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with asterisk,
so I am more inclined to believe that this is a configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---

--
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


#7

Hey there,

I am following up this issue because I found some more time.
I attached the logs, though with changed data.

I still want to replace twinkle which is working perfectly for years now but
because it is old and not maintained anymore, has its drawbacks.

Any help is very welcome.

Best regards,
Matt

jitsi0.log.0.zip (77 KB)

···

Am 04.04.2012 16:11, schrieb Buddy Butterfly:

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy option.
Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Am 04.04.2012 15:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and never had problems
(well, some standard problems with dtmf and the like ;-). I wanted to
give Jitsi a try and replace Twinkle with it. But have numerous problems with it.

Jitsi is very widely used with Asterisk and I don't believe we have seen
similar behaviour so far. Can you tell us more on how you configured
your account in Jitsi? Did you enter the server address as part of your
user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser of the JSIP
stack that Jitsi uses, so we'd have to implement quite a lot of rule
breaking for this to work (provided we had a good reason to do this). We
have implemented such "hacks" previously and it did happen to be for
asterisk (and the way it handles message waiting indications) but this
is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with asterisk,
so I am more inclined to believe that this is a configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is not
surprising.

Can you tell us more about how you get here? Your complete logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip ---
14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine call
peer state!
14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
:GenericURI, Bad URI format
14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
JAIN-SIP exception stack trace is
java.text.ParseException: BYE 200 SIP/2.0
:GenericURI, Bad URI format
    at gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    at
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    at
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    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(Thread.java:679)
14:01:28.764 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BAD MESSAGE!
14:01:28.765 SCHWERWIEGEND: impl.protocol.sip.SipLogger.logError().112
Error from the JAIN-SIP stack: BYE 200 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1>;tag=as2b1b0ac8
To:
<sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
CSeq: 103 BYE
User-Agent: Asterisk PBX
Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx"
<sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

14:01:49.688 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null
java.lang.NullPointerException
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    at
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    at
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    at
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:02:02.274 SCHWERWIEGEND: util.UtilActivator.uncaughtException().88 An
uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to java.awt.Component
java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
java.awt.Component
    at
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    at
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    at
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    at
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96)
    at java.awt.EventQueue$1.run(EventQueue.java:608)
    at java.awt.EventQueue$1.run(EventQueue.java:606)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    at java.awt.EventQueue$2.run(EventQueue.java:622)
    at java.awt.EventQueue$2.run(EventQueue.java:620)
    at java.security.AccessController.doPrivileged(Native Method)
    at
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
14:03:00.579 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
--- snap ---


#8

Did you get my latest mail about serverless accounts? Did you try using a
server?

--sent from my mobile

···

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de> wrote:

Hey there,

I am following up this issue because I found some more time.
I attached the logs, though with changed data.

I still want to replace twinkle which is working perfectly for years now
but
because it is old and not maintained anymore, has its drawbacks.

Any help is very welcome.

Best regards,
Matt

Am 04.04.2012 16:11, schrieb Buddy Butterfly:
> Account:
> SIP-ID: The name without server is given.
>
> Connection:
> Rgistrar: Asterisk with hostname and port is given.
> Proxy: Same hostname and port is used as proxy option.
> Automatic configuration switched off.
>
> Jitsi reports proper registration and shows "online".
>
> Am 04.04.2012 15:35, schrieb Emil Ivov:
>> Hey Matt,
>> On 04.04.12 15:26, Buddy Butterfly wrote:
>>> Hi,
>>>
>>> this is Jitsi connecting to a asterisk 1.4.36.
>>> We use this as a telephone system for a long time now and never had
problems
>>> (well, some standard problems with dtmf and the like ;-). I wanted to
>>> give Jitsi a try and replace Twinkle with it. But have numerous
problems with it.
>> Jitsi is very widely used with Asterisk and I don't believe we have seen
>> similar behaviour so far. Can you tell us more on how you configured
>> your account in Jitsi? Did you enter the server address as part of your
>> user name?
>>
>>> I will see to prepare the log files for you.
>> Here's how you could do this with a few clicks:
>> http://jitsi.org/faq/logs
>>
>>> What would be a valid SIP request?
>> A valid request line would look something like:
>>
>> BYE sip:200@192.168.0.1 SIP/2.0
>>
>>> Would it be worth to make Jitsi more tolerant here?
>> This is a rather serious error that's detected by the parser of the JSIP
>> stack that Jitsi uses, so we'd have to implement quite a lot of rule
>> breaking for this to work (provided we had a good reason to do this). We
>> have implemented such "hacks" previously and it did happen to be for
>> asterisk (and the way it handles message waiting indications) but this
>> is something significantly lower layer.
>>
>> However, as I said, Jitsi is known to work quite reliably with asterisk,
>> so I am more inclined to believe that this is a configuration error.
>>
>> Cheers,
>> Emil
>>> Best regards,
>>> Matt
>>>
>>> Am 04.04.2012 14:46, schrieb Emil Ivov:
>>>> Well:
>>>>
>>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the failure is
not
>>>> surprising.
>>>>
>>>> Can you tell us more about how you get here? Your complete logs would
>>>> also help.
>>>>
>>>> Emil
>>>>
>>>>
>>>> On 04.04.12 14:18, Buddy Butterfly wrote:
>>>>> Hi all,
>>>>>
>>>>> I am not able to receive calls.
>>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
>>>>> See excerpt below.
>>>>>
>>>>>
>>>>> I am running Kubuntu 11.04 amd64.
>>>>> Java is:
>>>>>
>>>>> java version "1.6.0_22"
>>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6) (6b22-1.10.6-0ubuntu1)
>>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
>>>>>
>>>>> Ekiga and Twinkle are running without any problems.
>>>>>
>>>>> Best regards...
>>>>>
>>>>> IP and phone number has been replaced.
>>>>>
>>>>> --- snip ---
>>>>> 14:00:58.952 SCHWERWIEGEND:
>>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not determine
call
>>>>> peer state!
>>>>> 14:01:28.764 WARNUNG: impl.protocol.sip.SipLogger.logException().75
>>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
>>>>> :GenericURI, Bad URI format
>>>>> 14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
>>>>> JAIN-SIP exception stack trace is
>>>>> java.text.ParseException: BYE 200 SIP/2.0
>>>>> :GenericURI, Bad URI format
>>>>> at
gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
>>>>> at
gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
>>>>> at
>>>>>
gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
>>>>> at
>>>>>
gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
>>>>> 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(Thread.java:679)
>>>>> 14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112
>>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
>>>>> 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112
>>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
>>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
>>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
>;tag=as2b1b0ac8
>>>>> To:
>>>>> <sip:mwitkn-200@192.168.1.155:5060
;transport=udp;registering_acc=voip>;tag=cdd4f0a1
>>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
>>>>> CSeq: 103 BYE
>>>>> User-Agent: Asterisk PBX
>>>>> Max-Forwards: 70
>>>>> Remote-Party-ID: "+49xxxxxx"
>>>>> <sip:+49xxxxxxxxxxx@192.168.1.1>;privacy=off;screen=no
>>>>> X-Asterisk-HangupCause: Normal Clearing
>>>>> X-Asterisk-HangupCauseCode: 16
>>>>> Content-Length: 0
>>>>>
>>>>>
>>>>> 14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An
>>>>> uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
>>>>> and message was: null
>>>>> java.lang.NullPointerException
>>>>> at
>>>>>
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
>>>>> at
>>>>>
net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
>>>>> at
>>>>>
net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
>>>>> at
>>>>>
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
>>>>> at
>>>>>
net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
>>>>> at
java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
>>>>> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
>>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
>>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
>>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>> at
>>>>>
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
>>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
>>>>> at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
>>>>> at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
>>>>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
>>>>> 14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An
>>>>> uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
>>>>> and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component
>>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be cast to
>>>>> java.awt.Component
>>>>> at
>>>>>
javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
>>>>> at
>>>>>
javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
>>>>> at
>>>>>
java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
>>>>> at
>>>>>
java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
>>>>> at java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
>>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
>>>>> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
>>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
>>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
>>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>> at
>>>>>
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
>>>>> at
>>>>>
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
>>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
>>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
>>>>> at java.security.AccessController.doPrivileged(Native Method)
>>>>> at
>>>>>
java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
>>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
>>>>> at
>>>>>
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
>>>>> at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
>>>>> at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
>>>>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
>>>>> 14:03:00.579 INFO:
>>>>>
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
>>>>> setting the following popup handler as active : Jitsi Pop-Ups
>>>>> 14:03:00.583 INFO:
>>>>>
impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
>>>>> setting the following popup handler as active : Jitsi Pop-Ups
>>>>> 14:05:40.806 WARNUNG: impl.protocol.sip.SipLogger.logException().75
>>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
>>>>> --- snap ---
>>>>>
>>>>>
>>>>>


#9

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

···

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de > <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,

    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.

    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.

    Any help is very welcome.

    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:
    > Account:
    > SIP-ID: The name without server is given.
    >
    > Connection:
    > Rgistrar: Asterisk with hostname and port is given.
    > Proxy: Same hostname and port is used as proxy option.
    > Automatic configuration switched off.
    >
    > Jitsi reports proper registration and shows "online".
    >
    > Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:
    >> Hey Matt,
    >> On 04.04.12 15:26, Buddy Butterfly wrote:
    >>> Hi,
    >>>
    >>> this is Jitsi connecting to a asterisk 1.4.36.
    >>> We use this as a telephone system for a long time now and
    never had problems
    >>> (well, some standard problems with dtmf and the like ;-). I
    wanted to
    >>> give Jitsi a try and replace Twinkle with it. But have
    numerous problems with it.
    >> Jitsi is very widely used with Asterisk and I don't believe we
    have seen
    >> similar behaviour so far. Can you tell us more on how you
    configured
    >> your account in Jitsi? Did you enter the server address as part
    of your
    >> user name?
    >>
    >>> I will see to prepare the log files for you.
    >> Here's how you could do this with a few clicks:
    >> http://jitsi.org/faq/logs
    >>
    >>> What would be a valid SIP request?
    >> A valid request line would look something like:
    >>
    >> BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0
    >>
    >>> Would it be worth to make Jitsi more tolerant here?
    >> This is a rather serious error that's detected by the parser of
    the JSIP
    >> stack that Jitsi uses, so we'd have to implement quite a lot of
    rule
    >> breaking for this to work (provided we had a good reason to do
    this). We
    >> have implemented such "hacks" previously and it did happen to
    be for
    >> asterisk (and the way it handles message waiting indications)
    but this
    >> is something significantly lower layer.
    >>
    >> However, as I said, Jitsi is known to work quite reliably with
    asterisk,
    >> so I am more inclined to believe that this is a configuration
    error.
    >>
    >> Cheers,
    >> Emil
    >>> Best regards,
    >>> Matt
    >>>
    >>> Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:
    >>>> Well:
    >>>>
    >>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the
    failure is not
    >>>> surprising.
    >>>>
    >>>> Can you tell us more about how you get here? Your complete
    logs would
    >>>> also help.
    >>>>
    >>>> Emil
    >>>>
    >>>>
    >>>> On 04.04.12 14:18, Buddy Butterfly wrote:
    >>>>> Hi all,
    >>>>>
    >>>>> I am not able to receive calls.
    >>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
    >>>>> See excerpt below.
    >>>>>
    >>>>>
    >>>>> I am running Kubuntu 11.04 amd64.
    >>>>> Java is:
    >>>>>
    >>>>> java version "1.6.0_22"
    >>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6)
    (6b22-1.10.6-0ubuntu1)
    >>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
    >>>>>
    >>>>> Ekiga and Twinkle are running without any problems.
    >>>>>
    >>>>> Best regards...
    >>>>>
    >>>>> IP and phone number has been replaced.
    >>>>>
    >>>>> --- snip ---
    >>>>> 14:00:58.952 SCHWERWIEGEND:
    >>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
    determine call
    >>>>> peer state!
    >>>>> 14:01:28.764 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> 14:01:28.764 INFO: impl.protocol.sip.SipLogger.logException().77
    >>>>> JAIN-SIP exception stack trace is
    >>>>> java.text.ParseException: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> at
    gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    >>>>> at
    gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    >>>>> 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(Thread.java:679)
    >>>>> 14:01:28.764 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
    >>>>> 14:01:28.765 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
    >>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8
    >>>>> To:
    >>>>>
    <sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
    >>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
    <mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1>
    >>>>> CSeq: 103 BYE
    >>>>> User-Agent: Asterisk PBX
    >>>>> Max-Forwards: 70
    >>>>> Remote-Party-ID: "+49xxxxxx"
    >>>>> <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen=no
    >>>>> X-Asterisk-HangupCause: Normal Clearing
    >>>>> X-Asterisk-HangupCauseCode: 16
    >>>>> Content-Length: 0
    >>>>>
    >>>>>
    >>>>> 14:01:49.688 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: null
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    >>>>> at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:02:02.274 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: java.awt.TrayIcon cannot be cast to
    java.awt.Component
    >>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be
    cast to
    >>>>> java.awt.Component
    >>>>> at
    >>>>>
    javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    >>>>> at
    >>>>>
    javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    >>>>> at
    >>>>>
    java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    >>>>> at
    >>>>>
    java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    >>>>> at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    >>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:03:00.579 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:03:00.583 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:05:40.806 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
    >>>>> --- snap ---
    >>>>>
    >>>>>
    >>>>>


#10

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

···

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,

    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.

    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.

    Any help is very welcome.

    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:
    > Account:
    > SIP-ID: The name without server is given.
    >
    > Connection:
    > Rgistrar: Asterisk with hostname and port is given.
    > Proxy: Same hostname and port is used as proxy option.
    > Automatic configuration switched off.
    >
    > Jitsi reports proper registration and shows "online".
    >
    > Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:
    >> Hey Matt,
    >> On 04.04.12 15:26, Buddy Butterfly wrote:
    >>> Hi,
    >>>
    >>> this is Jitsi connecting to a asterisk 1.4.36.
    >>> We use this as a telephone system for a long time now and
    never had problems
    >>> (well, some standard problems with dtmf and the like ;-). I
    wanted to
    >>> give Jitsi a try and replace Twinkle with it. But have
    numerous problems with it.
    >> Jitsi is very widely used with Asterisk and I don't believe we
    have seen
    >> similar behaviour so far. Can you tell us more on how you
    configured
    >> your account in Jitsi? Did you enter the server address as
    part of your
    >> user name?
    >>
    >>> I will see to prepare the log files for you.
    >> Here's how you could do this with a few clicks:
    >> http://jitsi.org/faq/logs
    >>
    >>> What would be a valid SIP request?
    >> A valid request line would look something like:
    >>
    >> BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0
    >>
    >>> Would it be worth to make Jitsi more tolerant here?
    >> This is a rather serious error that's detected by the parser
    of the JSIP
    >> stack that Jitsi uses, so we'd have to implement quite a lot
    of rule
    >> breaking for this to work (provided we had a good reason to do
    this). We
    >> have implemented such "hacks" previously and it did happen to
    be for
    >> asterisk (and the way it handles message waiting indications)
    but this
    >> is something significantly lower layer.
    >>
    >> However, as I said, Jitsi is known to work quite reliably with
    asterisk,
    >> so I am more inclined to believe that this is a configuration
    error.
    >>
    >> Cheers,
    >> Emil
    >>> Best regards,
    >>> Matt
    >>>
    >>> Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:
    >>>> Well:
    >>>>
    >>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the
    failure is not
    >>>> surprising.
    >>>>
    >>>> Can you tell us more about how you get here? Your complete
    logs would
    >>>> also help.
    >>>>
    >>>> Emil
    >>>>
    >>>>
    >>>> On 04.04.12 14:18, Buddy Butterfly wrote:
    >>>>> Hi all,
    >>>>>
    >>>>> I am not able to receive calls.
    >>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
    >>>>> See excerpt below.
    >>>>>
    >>>>>
    >>>>> I am running Kubuntu 11.04 amd64.
    >>>>> Java is:
    >>>>>
    >>>>> java version "1.6.0_22"
    >>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6)
    (6b22-1.10.6-0ubuntu1)
    >>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
    >>>>>
    >>>>> Ekiga and Twinkle are running without any problems.
    >>>>>
    >>>>> Best regards...
    >>>>>
    >>>>> IP and phone number has been replaced.
    >>>>>
    >>>>> --- snip ---
    >>>>> 14:00:58.952 SCHWERWIEGEND:
    >>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
    determine call
    >>>>> peer state!
    >>>>> 14:01:28.764 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> 14:01:28.764 INFO:
    impl.protocol.sip.SipLogger.logException().77
    >>>>> JAIN-SIP exception stack trace is
    >>>>> java.text.ParseException: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> at
    gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    >>>>> at
    gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    >>>>> 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(Thread.java:679)
    >>>>> 14:01:28.764 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
    >>>>> 14:01:28.765 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
    >>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8
    >>>>> To:
    >>>>>
    <sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
    >>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
    <mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1>
    >>>>> CSeq: 103 BYE
    >>>>> User-Agent: Asterisk PBX
    >>>>> Max-Forwards: 70
    >>>>> Remote-Party-ID: "+49xxxxxx"
    >>>>> <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen=no
    >>>>> X-Asterisk-HangupCause: Normal Clearing
    >>>>> X-Asterisk-HangupCauseCode: 16
    >>>>> Content-Length: 0
    >>>>>
    >>>>>
    >>>>> 14:01:49.688 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: null
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    >>>>> at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:02:02.274 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: java.awt.TrayIcon cannot be cast to
    java.awt.Component
    >>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be
    cast to
    >>>>> java.awt.Component
    >>>>> at
    >>>>>
    javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    >>>>> at
    >>>>>
    javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    >>>>> at
    >>>>>
    java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    >>>>> at
    >>>>>
    java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    >>>>> at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    >>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:03:00.579 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:03:00.583 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:05:40.806 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
    >>>>> --- snap ---
    >>>>>
    >>>>>
    >>>>>


#11

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

···

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,

    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.

    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.

    Any help is very welcome.

    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:
    > Account:
    > SIP-ID: The name without server is given.
    >
    > Connection:
    > Rgistrar: Asterisk with hostname and port is given.
    > Proxy: Same hostname and port is used as proxy option.
    > Automatic configuration switched off.
    >
    > Jitsi reports proper registration and shows "online".
    >
    > Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:
    >> Hey Matt,
    >> On 04.04.12 15:26, Buddy Butterfly wrote:
    >>> Hi,
    >>>
    >>> this is Jitsi connecting to a asterisk 1.4.36.
    >>> We use this as a telephone system for a long time now and
    never had problems
    >>> (well, some standard problems with dtmf and the like ;-). I
    wanted to
    >>> give Jitsi a try and replace Twinkle with it. But have
    numerous problems with it.
    >> Jitsi is very widely used with Asterisk and I don't believe we
    have seen
    >> similar behaviour so far. Can you tell us more on how you
    configured
    >> your account in Jitsi? Did you enter the server address as
    part of your
    >> user name?
    >>
    >>> I will see to prepare the log files for you.
    >> Here's how you could do this with a few clicks:
    >> http://jitsi.org/faq/logs
    >>
    >>> What would be a valid SIP request?
    >> A valid request line would look something like:
    >>
    >> BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0
    >>
    >>> Would it be worth to make Jitsi more tolerant here?
    >> This is a rather serious error that's detected by the parser
    of the JSIP
    >> stack that Jitsi uses, so we'd have to implement quite a lot
    of rule
    >> breaking for this to work (provided we had a good reason to do
    this). We
    >> have implemented such "hacks" previously and it did happen to
    be for
    >> asterisk (and the way it handles message waiting indications)
    but this
    >> is something significantly lower layer.
    >>
    >> However, as I said, Jitsi is known to work quite reliably with
    asterisk,
    >> so I am more inclined to believe that this is a configuration
    error.
    >>
    >> Cheers,
    >> Emil
    >>> Best regards,
    >>> Matt
    >>>
    >>> Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:
    >>>> Well:
    >>>>
    >>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the
    failure is not
    >>>> surprising.
    >>>>
    >>>> Can you tell us more about how you get here? Your complete
    logs would
    >>>> also help.
    >>>>
    >>>> Emil
    >>>>
    >>>>
    >>>> On 04.04.12 14:18, Buddy Butterfly wrote:
    >>>>> Hi all,
    >>>>>
    >>>>> I am not able to receive calls.
    >>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
    >>>>> See excerpt below.
    >>>>>
    >>>>>
    >>>>> I am running Kubuntu 11.04 amd64.
    >>>>> Java is:
    >>>>>
    >>>>> java version "1.6.0_22"
    >>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6)
    (6b22-1.10.6-0ubuntu1)
    >>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
    >>>>>
    >>>>> Ekiga and Twinkle are running without any problems.
    >>>>>
    >>>>> Best regards...
    >>>>>
    >>>>> IP and phone number has been replaced.
    >>>>>
    >>>>> --- snip ---
    >>>>> 14:00:58.952 SCHWERWIEGEND:
    >>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
    determine call
    >>>>> peer state!
    >>>>> 14:01:28.764 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> 14:01:28.764 INFO:
    impl.protocol.sip.SipLogger.logException().77
    >>>>> JAIN-SIP exception stack trace is
    >>>>> java.text.ParseException: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> at
    gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    >>>>> at
    gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    >>>>> 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(Thread.java:679)
    >>>>> 14:01:28.764 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
    >>>>> 14:01:28.765 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
    >>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8
    >>>>> To:
    >>>>>
    <sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
    >>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
    <mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1>
    >>>>> CSeq: 103 BYE
    >>>>> User-Agent: Asterisk PBX
    >>>>> Max-Forwards: 70
    >>>>> Remote-Party-ID: "+49xxxxxx"
    >>>>> <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen=no
    >>>>> X-Asterisk-HangupCause: Normal Clearing
    >>>>> X-Asterisk-HangupCauseCode: 16
    >>>>> Content-Length: 0
    >>>>>
    >>>>>
    >>>>> 14:01:49.688 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: null
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    >>>>> at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:02:02.274 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: java.awt.TrayIcon cannot be cast to
    java.awt.Component
    >>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be
    cast to
    >>>>> java.awt.Component
    >>>>> at
    >>>>>
    javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    >>>>> at
    >>>>>
    javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    >>>>> at
    >>>>>
    java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    >>>>> at
    >>>>>
    java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    >>>>> at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    >>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:03:00.579 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:03:00.583 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:05:40.806 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
    >>>>> --- snap ---
    >>>>>
    >>>>>
    >>>>>

--
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


#12

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.

   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

   Though, it would be nice if we could use angle brackets.

2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right low
edge of the screen with the
   number calling. But the call can not be answered as there is no
accept butten respectively no
   accept dialog being displayed (apart from key shortcuts).

   I have found that this is because I have no video device. Global
properties -> Video -> Devices
   does not list any device.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device), no accepting
   dialog will be displayed.

   On the other hand, if, for example, I select the first codec
H263-1998 even having no device then there
   will be an accepting dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

···

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,

    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.

    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.

    Any help is very welcome.

    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:
    > Account:
    > SIP-ID: The name without server is given.
    >
    > Connection:
    > Rgistrar: Asterisk with hostname and port is given.
    > Proxy: Same hostname and port is used as proxy option.
    > Automatic configuration switched off.
    >
    > Jitsi reports proper registration and shows "online".
    >
    > Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:
    >> Hey Matt,
    >> On 04.04.12 15:26, Buddy Butterfly wrote:
    >>> Hi,
    >>>
    >>> this is Jitsi connecting to a asterisk 1.4.36.
    >>> We use this as a telephone system for a long time now and
    never had problems
    >>> (well, some standard problems with dtmf and the like ;-). I
    wanted to
    >>> give Jitsi a try and replace Twinkle with it. But have
    numerous problems with it.
    >> Jitsi is very widely used with Asterisk and I don't believe we
    have seen
    >> similar behaviour so far. Can you tell us more on how you
    configured
    >> your account in Jitsi? Did you enter the server address as
    part of your
    >> user name?
    >>
    >>> I will see to prepare the log files for you.
    >> Here's how you could do this with a few clicks:
    >> http://jitsi.org/faq/logs
    >>
    >>> What would be a valid SIP request?
    >> A valid request line would look something like:
    >>
    >> BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0
    >>
    >>> Would it be worth to make Jitsi more tolerant here?
    >> This is a rather serious error that's detected by the parser
    of the JSIP
    >> stack that Jitsi uses, so we'd have to implement quite a lot
    of rule
    >> breaking for this to work (provided we had a good reason to do
    this). We
    >> have implemented such "hacks" previously and it did happen to
    be for
    >> asterisk (and the way it handles message waiting indications)
    but this
    >> is something significantly lower layer.
    >>
    >> However, as I said, Jitsi is known to work quite reliably with
    asterisk,
    >> so I am more inclined to believe that this is a configuration
    error.
    >>
    >> Cheers,
    >> Emil
    >>> Best regards,
    >>> Matt
    >>>
    >>> Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:
    >>>> Well:
    >>>>
    >>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the
    failure is not
    >>>> surprising.
    >>>>
    >>>> Can you tell us more about how you get here? Your complete
    logs would
    >>>> also help.
    >>>>
    >>>> Emil
    >>>>
    >>>>
    >>>> On 04.04.12 14:18, Buddy Butterfly wrote:
    >>>>> Hi all,
    >>>>>
    >>>>> I am not able to receive calls.
    >>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
    >>>>> See excerpt below.
    >>>>>
    >>>>>
    >>>>> I am running Kubuntu 11.04 amd64.
    >>>>> Java is:
    >>>>>
    >>>>> java version "1.6.0_22"
    >>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6)
    (6b22-1.10.6-0ubuntu1)
    >>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
    >>>>>
    >>>>> Ekiga and Twinkle are running without any problems.
    >>>>>
    >>>>> Best regards...
    >>>>>
    >>>>> IP and phone number has been replaced.
    >>>>>
    >>>>> --- snip ---
    >>>>> 14:00:58.952 SCHWERWIEGEND:
    >>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
    determine call
    >>>>> peer state!
    >>>>> 14:01:28.764 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> 14:01:28.764 INFO:
    impl.protocol.sip.SipLogger.logException().77
    >>>>> JAIN-SIP exception stack trace is
    >>>>> java.text.ParseException: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> at
    gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    >>>>> at
    gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    >>>>> 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(Thread.java:679)
    >>>>> 14:01:28.764 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
    >>>>> 14:01:28.765 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
    >>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8
    >>>>> To:
    >>>>>
    <sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
    >>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
    <mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1>
    >>>>> CSeq: 103 BYE
    >>>>> User-Agent: Asterisk PBX
    >>>>> Max-Forwards: 70
    >>>>> Remote-Party-ID: "+49xxxxxx"
    >>>>> <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen=no
    >>>>> X-Asterisk-HangupCause: Normal Clearing
    >>>>> X-Asterisk-HangupCauseCode: 16
    >>>>> Content-Length: 0
    >>>>>
    >>>>>
    >>>>> 14:01:49.688 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: null
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    >>>>> at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:02:02.274 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: java.awt.TrayIcon cannot be cast to
    java.awt.Component
    >>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be
    cast to
    >>>>> java.awt.Component
    >>>>> at
    >>>>>
    javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    >>>>> at
    >>>>>
    javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    >>>>> at
    >>>>>
    java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    >>>>> at
    >>>>>
    java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    >>>>> at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    >>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:03:00.579 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:03:00.583 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:05:40.806 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
    >>>>> --- snap ---
    >>>>>
    >>>>>
    >>>>>


#13

Hey Matt,

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.

   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the problem.

   Though, it would be nice if we could use angle brackets.

2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right low
edge of the screen with the
   number calling. But the call can not be answered as there is no
accept butten respectively no
   accept dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

   I have found that this is because I have no video device. Global
properties -> Video -> Devices
   does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
   dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

···

On 25.08.12, 14:16, Buddy Butterfly wrote:

   On the other hand, if, for example, I select the first codec
H263-1998 even having no device then there
   will be an accepting dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,

    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.

    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.

    Any help is very welcome.

    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:
    > Account:
    > SIP-ID: The name without server is given.
    >
    > Connection:
    > Rgistrar: Asterisk with hostname and port is given.
    > Proxy: Same hostname and port is used as proxy option.
    > Automatic configuration switched off.
    >
    > Jitsi reports proper registration and shows "online".
    >
    > Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:
    >> Hey Matt,
    >> On 04.04.12 15:26, Buddy Butterfly wrote:
    >>> Hi,
    >>>
    >>> this is Jitsi connecting to a asterisk 1.4.36.
    >>> We use this as a telephone system for a long time now and
    never had problems
    >>> (well, some standard problems with dtmf and the like ;-). I
    wanted to
    >>> give Jitsi a try and replace Twinkle with it. But have
    numerous problems with it.
    >> Jitsi is very widely used with Asterisk and I don't believe we
    have seen
    >> similar behaviour so far. Can you tell us more on how you
    configured
    >> your account in Jitsi? Did you enter the server address as
    part of your
    >> user name?
    >>
    >>> I will see to prepare the log files for you.
    >> Here's how you could do this with a few clicks:
    >> http://jitsi.org/faq/logs
    >>
    >>> What would be a valid SIP request?
    >> A valid request line would look something like:
    >>
    >> BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0
    >>
    >>> Would it be worth to make Jitsi more tolerant here?
    >> This is a rather serious error that's detected by the parser
    of the JSIP
    >> stack that Jitsi uses, so we'd have to implement quite a lot
    of rule
    >> breaking for this to work (provided we had a good reason to do
    this). We
    >> have implemented such "hacks" previously and it did happen to
    be for
    >> asterisk (and the way it handles message waiting indications)
    but this
    >> is something significantly lower layer.
    >>
    >> However, as I said, Jitsi is known to work quite reliably with
    asterisk,
    >> so I am more inclined to believe that this is a configuration
    error.
    >>
    >> Cheers,
    >> Emil
    >>> Best regards,
    >>> Matt
    >>>
    >>> Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:
    >>>> Well:
    >>>>
    >>>> "BYE 200 SIP/2.0" is not a valid SIP Request line so the
    failure is not
    >>>> surprising.
    >>>>
    >>>> Can you tell us more about how you get here? Your complete
    logs would
    >>>> also help.
    >>>>
    >>>> Emil
    >>>>
    >>>>
    >>>> On 04.04.12 14:18, Buddy Butterfly wrote:
    >>>>> Hi all,
    >>>>>
    >>>>> I am not able to receive calls.
    >>>>> I am getting NullPointer Exceptions, Bad URL exceptions, etc.
    >>>>> See excerpt below.
    >>>>>
    >>>>>
    >>>>> I am running Kubuntu 11.04 amd64.
    >>>>> Java is:
    >>>>>
    >>>>> java version "1.6.0_22"
    >>>>> OpenJDK Runtime Environment (IcedTea6 1.10.6)
    (6b22-1.10.6-0ubuntu1)
    >>>>> OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)
    >>>>>
    >>>>> Ekiga and Twinkle are running without any problems.
    >>>>>
    >>>>> Best regards...
    >>>>>
    >>>>> IP and phone number has been replaced.
    >>>>>
    >>>>> --- snip ---
    >>>>> 14:00:58.952 SCHWERWIEGEND:
    >>>>> impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
    determine call
    >>>>> peer state!
    >>>>> 14:01:28.764 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> 14:01:28.764 INFO:
    impl.protocol.sip.SipLogger.logException().77
    >>>>> JAIN-SIP exception stack trace is
    >>>>> java.text.ParseException: BYE 200 SIP/2.0
    >>>>> :GenericURI, Bad URI format
    >>>>> at
    gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)
    >>>>> at
    gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)
    >>>>> at
    >>>>>
    gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.java:230)
    >>>>> 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(Thread.java:679)
    >>>>> 14:01:28.764 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BAD MESSAGE!
    >>>>> 14:01:28.765 SCHWERWIEGEND:
    impl.protocol.sip.SipLogger.logError().112
    >>>>> Error from the JAIN-SIP stack: BYE 200 SIP/2.0
    >>>>> Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport
    >>>>> From: "+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8
    >>>>> To:
    >>>>>
    <sip:mwitkn-200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1
    >>>>> Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
    <mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1>
    >>>>> CSeq: 103 BYE
    >>>>> User-Agent: Asterisk PBX
    >>>>> Max-Forwards: 70
    >>>>> Remote-Party-ID: "+49xxxxxx"
    >>>>> <sip:+49xxxxxxxxxxx@192.168.1.1
    <mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen=no
    >>>>> X-Asterisk-HangupCause: Normal Clearing
    >>>>> X-Asterisk-HangupCauseCode: 16
    >>>>> Content-Length: 0
    >>>>>
    >>>>>
    >>>>> 14:01:49.688 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: null
    >>>>> java.lang.NullPointerException
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:156)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDialog.java:121)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(ReceivedCallDialog.java:50)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.incomingCallReceived(CallManager.java:88)
    >>>>> at
    >>>>>
    net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.run(CallManager.java:81)
    >>>>> at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:02:02.274 SCHWERWIEGEND:
    util.UtilActivator.uncaughtException().88 An
    >>>>> uncaught exception occurred in
    thread=Thread[AWT-EventQueue-0,6,main]
    >>>>> and message was: java.awt.TrayIcon cannot be cast to
    java.awt.Component
    >>>>> java.lang.ClassCastException: java.awt.TrayIcon cannot be
    cast to
    >>>>> java.awt.Component
    >>>>> at
    >>>>>
    javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java:220)
    >>>>> at
    >>>>>
    javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPopupMenuUI.java:860)
    >>>>> at
    >>>>>
    java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378)
    >>>>> at
    >>>>>
    java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)
    >>>>> at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    >>>>> at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725)
    >>>>> at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    >>>>> at java.awt.EventQueue.access$000(EventQueue.java:96)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:608)
    >>>>> at java.awt.EventQueue$1.run(EventQueue.java:606)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:116)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:622)
    >>>>> at java.awt.EventQueue$2.run(EventQueue.java:620)
    >>>>> at java.security.AccessController.doPrivileged(Native
    Method)
    >>>>> at
    >>>>>
    java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
    >>>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
    >>>>> at
    >>>>>
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
    >>>>> at
    java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
    >>>>> at
    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
    >>>>> 14:03:00.579 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:03:00.583 INFO:
    >>>>>
    impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().593
    >>>>> setting the following popup handler as active : Jitsi Pop-Ups
    >>>>> 14:05:40.806 WARNUNG:
    impl.protocol.sip.SipLogger.logException().75
    >>>>> Exception in the JAIN-SIP stack: ACK 200 SIP/2.0
    >>>>> --- snap ---
    >>>>>
    >>>>>
    >>>>>

--
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


#14

Emil,

Just in case you missed it, there is a mail from Buddy from Wed 22.8. with a
logs attachment (although without pcap-traces). I took a short look at it
and it indeed seems that the (non)-presence of a video-device or something
related is involved in the error (PreCallDialog.java:156).

Regards,
Ingo

From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Montag, 27. August 2012 09:23
To: buddy.butterfly@web.de
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Numerours exceptions
Hey Matt,

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.
   
   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the

problem.

   Though, it would be nice if we could use angle brackets.
2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right
   low edge of the screen with the number calling. But the call can
   not be answered as there is no accept butten respectively no accept
   dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

   I have found that this is because I have no video device. Global
   properties -> Video -> Devices does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
   dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

   On the other hand, if, for example, I select the first codec
   H263-1998 even having no device then there will be an accepting
   dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

    Hey there,
    
    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.
    
    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.
    
    Any help is very welcome.
    
    Best regards,
    Matt

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy

option.

Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Hey Matt,

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and

    never had problems (well, some standard problems with dtmf and
    the like ;-). I wanted to give Jitsi a try and replace Twinkle
    with it. But have numerous problems with it. Jitsi is very
    widely used with Asterisk and I don't believe we have seen
    similar behaviour so far. Can you tell us more on how you
    configured your account in Jitsi? Did you enter the server
    address as part of your

user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser

    of the JSIP stack that Jitsi uses, so we'd have to implement
    quite a lot of rule breaking for this to work (provided we had
    a good reason to do this). We have implemented such "hacks"
    previously and it did happen to be for asterisk (and the way it
    handles message waiting indications) but this

is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with

    asterisk, so I am more inclined to believe that this is a
    configuration error.

Cheers,
Emil

Best regards,
Matt

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the
failure is not
surprising.

Can you tell us more about how you get here? Your complete
logs would
also help.

Emil

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6
1.10.6) (6b22-1.10.6-0ubuntu1) OpenJDK 64-Bit Server VM (build
20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip --- 14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
determine call peer state! 14:01:28.764 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: BYE 200 SIP/2.0 :GenericURI, Bad URI format
14:01:28.764 INFO:
impl.protocol.sip.SipLogger.logException().77 JAIN-SIP
exception stack trace is java.text.ParseException: BYE 200
SIP/2.0 :GenericURI, Bad URI format
    at

gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)

    at

gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)

    at

gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)

    at

gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.j
a

va:230)

    at

gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.ja
v

a:158)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMess
a

geChannel.java:337)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)

    at java.lang.Thread.run(Thread.java:679)
14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BAD MESSAGE! 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BYE 200 SIP/2.0 Via: SIP/2.0/UDP
192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport From:
"+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8 To:

    <sip:mwitkn-

200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1

Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
<mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1> CSeq:
103 BYE User-Agent: Asterisk PBX Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen
=no X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16 Content-Length: 0

14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null java.lang.NullPointerException
    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:156)

    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:121)

    at

net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(Recei
v

edCallDialog.java:50)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.inc
o

mingCallReceived(CallManager.java:88)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.r
u

n(CallManager.java:81)

    at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.jav
    a:226) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component java.lang.ClassCastException:
java.awt.TrayIcon cannot be cast to java.awt.Component
    at

javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java
:

220)

    at

javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPo
p

upMenuUI.java:860)

    at

java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378
)

    at

java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)

    at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
     at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:116)

    at java.awt.EventQueue$2.run(EventQueue.java:622) at
    java.awt.EventQueue$2.run(EventQueue.java:620) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:03:00.579 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

···

-----Original Message-----
On 25.08.12, 14:16, Buddy Butterfly wrote:

Am 24.08.2012 20:14, schrieb Emil Ivov:

On 22.08.12, 15:02, Buddy Butterfly wrote:

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Am 22.08.2012 14:36, schrieb Emil Ivov:

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>>> <mailto:buddy.butterfly@web.de>> wrote:
    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy Butterfly:

Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:

On 04.04.12 15:26, Buddy Butterfly wrote:

Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:

On 04.04.12 14:18, Buddy Butterfly wrote:

93

setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: ACK 200 SIP/2.0 --- snap ---


#15

Hey Emil,

shouldn't the display name in full (everything that has been entered
into the field)
automatically be quoted? This should be the default behavior.

Thanks Ingo for elaborating the NullPointerException. I intentionally
removed the pcaps as
the sip packets are also in the log files in case of exceptions. I will
prepare test accounts
and a VM for future testing such that I can easily send all the logs.

Best regards,
Matt

···

Am 27.08.2012 20:04, schrieb Ingo Bauersachs:

Emil,

Just in case you missed it, there is a mail from Buddy from Wed 22.8. with a
logs attachment (although without pcap-traces). I took a short look at it
and it indeed seems that the (non)-presence of a video-device or something
related is involved in the error (PreCallDialog.java:156).

Regards,
Ingo

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Montag, 27. August 2012 09:23
To: buddy.butterfly@web.de
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Numerours exceptions
Hey Matt,

On 25.08.12, 14:16, Buddy Butterfly wrote:

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.
   
   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the

problem.

   Though, it would be nice if we could use angle brackets.
2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right
   low edge of the screen with the number calling. But the call can
   not be answered as there is no accept butten respectively no accept
   dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

   I have found that this is because I have no video device. Global
   properties -> Video -> Devices does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
   dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

   On the other hand, if, for example, I select the first codec
   H263-1998 even having no device then there will be an accepting
   dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>>>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,
    
    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.
    
    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.
    
    Any help is very welcome.
    
    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy > Butterfly:

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy

option.

Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and

    never had problems (well, some standard problems with dtmf and
    the like ;-). I wanted to give Jitsi a try and replace Twinkle
    with it. But have numerous problems with it. Jitsi is very
    widely used with Asterisk and I don't believe we have seen
    similar behaviour so far. Can you tell us more on how you
    configured your account in Jitsi? Did you enter the server
    address as part of your

user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser

    of the JSIP stack that Jitsi uses, so we'd have to implement
    quite a lot of rule breaking for this to work (provided we had
    a good reason to do this). We have implemented such "hacks"
    previously and it did happen to be for asterisk (and the way it
    handles message waiting indications) but this

is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with

    asterisk, so I am more inclined to believe that this is a
    configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the
failure is not
surprising.

Can you tell us more about how you get here? Your complete
logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6
1.10.6) (6b22-1.10.6-0ubuntu1) OpenJDK 64-Bit Server VM (build
20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip --- 14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
determine call peer state! 14:01:28.764 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: BYE 200 SIP/2.0 :GenericURI, Bad URI format
14:01:28.764 INFO:
impl.protocol.sip.SipLogger.logException().77 JAIN-SIP
exception stack trace is java.text.ParseException: BYE 200
SIP/2.0 :GenericURI, Bad URI format
    at

gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)

    at

gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)

    at

gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)

    at

gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.j
a

va:230)

    at

gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.ja
v

a:158)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMess
a

geChannel.java:337)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)

    at java.lang.Thread.run(Thread.java:679)
14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BAD MESSAGE! 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BYE 200 SIP/2.0 Via: SIP/2.0/UDP
192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport From:
"+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8 To:

    <sip:mwitkn-

200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1

Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
<mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1> CSeq:
103 BYE User-Agent: Asterisk PBX Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen
=no X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16 Content-Length: 0

14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null java.lang.NullPointerException
    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:156)

    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:121)

    at

net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(Recei
v

edCallDialog.java:50)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.inc
o

mingCallReceived(CallManager.java:88)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.r
u

n(CallManager.java:81)

    at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.jav
    a:226) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component java.lang.ClassCastException:
java.awt.TrayIcon cannot be cast to java.awt.Component
    at

javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java
:

220)

    at

javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPo
p

upMenuUI.java:860)

    at

java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378
)

    at

java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)

    at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
     at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:116)

    at java.awt.EventQueue$2.run(EventQueue.java:622) at
    java.awt.EventQueue$2.run(EventQueue.java:620) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:03:00.579 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: ACK 200 SIP/2.0 --- snap ---


#16

Emil,

Just in case you missed it, there is a mail from Buddy from Wed 22.8. with a
logs attachment (although without pcap-traces). I took a short look at it
and it indeed seems that the (non)-presence of a video-device or something
related is involved in the error (PreCallDialog.java:156).

It does seem that way indeed. Thanks for the nudge. We'll have a look.

Emil

···

On 27.08.12, 21:04, Ingo Bauersachs wrote:

Regards,
Ingo

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Montag, 27. August 2012 09:23
To: buddy.butterfly@web.de
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Numerours exceptions
Hey Matt,

On 25.08.12, 14:16, Buddy Butterfly wrote:

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.
   
   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the

problem.

   Though, it would be nice if we could use angle brackets.
2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right
   low edge of the screen with the number calling. But the call can
   not be answered as there is no accept butten respectively no accept
   dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

   I have found that this is because I have no video device. Global
   properties -> Video -> Devices does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
   dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

   On the other hand, if, for example, I select the first codec
   H263-1998 even having no device then there will be an accepting
   dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>>>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,
    
    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.
    
    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.
    
    Any help is very welcome.
    
    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy > Butterfly:

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy

option.

Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and

    never had problems (well, some standard problems with dtmf and
    the like ;-). I wanted to give Jitsi a try and replace Twinkle
    with it. But have numerous problems with it. Jitsi is very
    widely used with Asterisk and I don't believe we have seen
    similar behaviour so far. Can you tell us more on how you
    configured your account in Jitsi? Did you enter the server
    address as part of your

user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser

    of the JSIP stack that Jitsi uses, so we'd have to implement
    quite a lot of rule breaking for this to work (provided we had
    a good reason to do this). We have implemented such "hacks"
    previously and it did happen to be for asterisk (and the way it
    handles message waiting indications) but this

is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with

    asterisk, so I am more inclined to believe that this is a
    configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the
failure is not
surprising.

Can you tell us more about how you get here? Your complete
logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6
1.10.6) (6b22-1.10.6-0ubuntu1) OpenJDK 64-Bit Server VM (build
20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip --- 14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
determine call peer state! 14:01:28.764 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: BYE 200 SIP/2.0 :GenericURI, Bad URI format
14:01:28.764 INFO:
impl.protocol.sip.SipLogger.logException().77 JAIN-SIP
exception stack trace is java.text.ParseException: BYE 200
SIP/2.0 :GenericURI, Bad URI format
    at

gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)

    at

gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)

    at

gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)

    at

gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.j
a

va:230)

    at

gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.ja
v

a:158)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMess
a

geChannel.java:337)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)

    at java.lang.Thread.run(Thread.java:679)
14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BAD MESSAGE! 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BYE 200 SIP/2.0 Via: SIP/2.0/UDP
192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport From:
"+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8 To:

    <sip:mwitkn-

200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1

Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
<mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1> CSeq:
103 BYE User-Agent: Asterisk PBX Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen
=no X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16 Content-Length: 0

14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null java.lang.NullPointerException
    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:156)

    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:121)

    at

net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(Recei
v

edCallDialog.java:50)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.inc
o

mingCallReceived(CallManager.java:88)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.r
u

n(CallManager.java:81)

    at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.jav
    a:226) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component java.lang.ClassCastException:
java.awt.TrayIcon cannot be cast to java.awt.Component
    at

javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java
:

220)

    at

javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPo
p

upMenuUI.java:860)

    at

java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378
)

    at

java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)

    at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
     at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:116)

    at java.awt.EventQueue$2.run(EventQueue.java:622) at
    java.awt.EventQueue$2.run(EventQueue.java:620) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:03:00.579 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: ACK 200 SIP/2.0 --- snap ---

--
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


#17

Hey Matt,

Hey Emil,

shouldn't the display name in full (everything that has been entered
into the field)
automatically be quoted? This should be the default behavior.

According to 3261's grammar, not necessarily.

Thanks Ingo for elaborating the NullPointerException. I intentionally
removed the pcaps as
the sip packets are also in the log files in case of exceptions.

It's a lot easier for us to just get the full zip, so you don't have to
bother removing anything. If you have privacy concerns then simply send
them over to support@bluejimp.com

I will
prepare test accounts
and a VM for future testing such that I can easily send all the logs.

Thanks,
Emil

···

On 28.08.12, 13:04, Buddy Butterfly wrote:

Best regards,
Matt

Am 27.08.2012 20:04, schrieb Ingo Bauersachs:

Emil,

Just in case you missed it, there is a mail from Buddy from Wed 22.8. with a
logs attachment (although without pcap-traces). I took a short look at it
and it indeed seems that the (non)-presence of a video-device or something
related is involved in the error (PreCallDialog.java:156).

Regards,
Ingo

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Montag, 27. August 2012 09:23
To: buddy.butterfly@web.de
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Numerours exceptions
Hey Matt,

On 25.08.12, 14:16, Buddy Butterfly wrote:

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
   accepted call.
   
   In my situation the wrong display name was: "Buddy Butterfly <100>".
   Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the

problem.

   Though, it would be nice if we could use angle brackets.
2. No accept dialog displayed when call is coming in.
   When a call is received there is a message displayed in the right
   low edge of the screen with the number calling. But the call can
   not be answered as there is no accept butten respectively no accept
   dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

   I have found that this is because I have no video device. Global
   properties -> Video -> Devices does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

   Cause of the problem:
   When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
   dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

   On the other hand, if, for example, I select the first codec
   H263-1998 even having no device then there will be an accepting
   dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>>>>> <mailto:buddy.butterfly@web.de>> wrote:

    Hey there,
    
    I am following up this issue because I found some more time.
    I attached the logs, though with changed data.
    
    I still want to replace twinkle which is working perfectly for
    years now but
    because it is old and not maintained anymore, has its drawbacks.
    
    Any help is very welcome.
    
    Best regards,
    Matt

    Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy >> Butterfly:

Account:
SIP-ID: The name without server is given.

Connection:
    Rgistrar: Asterisk with hostname and port is given.
    Proxy: Same hostname and port is used as proxy

option.

Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and

    never had problems (well, some standard problems with dtmf and
    the like ;-). I wanted to give Jitsi a try and replace Twinkle
    with it. But have numerous problems with it. Jitsi is very
    widely used with Asterisk and I don't believe we have seen
    similar behaviour so far. Can you tell us more on how you
    configured your account in Jitsi? Did you enter the server
    address as part of your

user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
    http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser

    of the JSIP stack that Jitsi uses, so we'd have to implement
    quite a lot of rule breaking for this to work (provided we had
    a good reason to do this). We have implemented such "hacks"
    previously and it did happen to be for asterisk (and the way it
    handles message waiting indications) but this

is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with

    asterisk, so I am more inclined to believe that this is a
    configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the
failure is not
surprising.

Can you tell us more about how you get here? Your complete
logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6
1.10.6) (6b22-1.10.6-0ubuntu1) OpenJDK 64-Bit Server VM (build
20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip --- 14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
determine call peer state! 14:01:28.764 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: BYE 200 SIP/2.0 :GenericURI, Bad URI format
14:01:28.764 INFO:
impl.protocol.sip.SipLogger.logException().77 JAIN-SIP
exception stack trace is java.text.ParseException: BYE 200
SIP/2.0 :GenericURI, Bad URI format
    at

gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)

    at

gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)

    at

gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)

    at

gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.j
a

va:230)

    at

gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.ja
v

a:158)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMess
a

geChannel.java:337)

    at

gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)

    at java.lang.Thread.run(Thread.java:679)
14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BAD MESSAGE! 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BYE 200 SIP/2.0 Via: SIP/2.0/UDP
192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport From:
"+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8 To:

    <sip:mwitkn-

200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1

Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
<mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1> CSeq:
103 BYE User-Agent: Asterisk PBX Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen
=no X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16 Content-Length: 0

14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null java.lang.NullPointerException
    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:156)

    at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:121)

    at

net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(Recei
v

edCallDialog.java:50)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.inc
o

mingCallReceived(CallManager.java:88)

    at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.r
u

n(CallManager.java:81)

    at
    java.awt.event.InvocationEvent.dispatch(InvocationEvent.jav
    a:226) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component java.lang.ClassCastException:
java.awt.TrayIcon cannot be cast to java.awt.Component
    at

javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java
:

220)

    at

javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPo
p

upMenuUI.java:860)

    at

java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378
)

    at

java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)

    at
    java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
     at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725) at
    java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
    at java.awt.EventQueue.access$000(EventQueue.java:96) at
    java.awt.EventQueue$1.run(EventQueue.java:608) at
    java.awt.EventQueue$1.run(EventQueue.java:606) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:116)

    at java.awt.EventQueue$2.run(EventQueue.java:622) at
    java.awt.EventQueue$2.run(EventQueue.java:620) at
    java.security.AccessController.doPrivileged(Native Method)
    at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

    at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
    at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

    at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

    at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

    at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

    at

    java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:03:00.579 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: ACK 200 SIP/2.0 --- snap ---

--
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


#18

Hi,

Emil,

Just in case you missed it, there is a mail from Buddy from Wed 22.8. with a
logs attachment (although without pcap-traces). I took a short look at it
and it indeed seems that the (non)-presence of a video-device or something
related is involved in the error (PreCallDialog.java:156).

It does seem that way indeed. Thanks for the nudge. We'll have a look.

I believe I've committed a fix for this one (r9835, build 4194).

Cheers,
Yana

···

On Sep 8, 2012, at 7:27 PM, Emil Ivov wrote:

On 27.08.12, 21:04, Ingo Bauersachs wrote:

Emil

Regards,
Ingo

-----Original Message-----
From: Emil Ivov [mailto:emcho@jitsi.org]
Sent: Montag, 27. August 2012 09:23
To: buddy.butterfly@web.de
Cc: dev@jitsi.java.net
Subject: [jitsi-dev] Re: Numerours exceptions
Hey Matt,

On 25.08.12, 14:16, Buddy Butterfly wrote:

Hi Emil,

did some more testing, created account anew and found the cause of the
problems!

1. If the display name contains angle brackets jitsi seems to crash and
there is no sound in an
  accepted call.

  In my situation the wrong display name was: "Buddy Butterfly <100>".
  Giving "Buddy Butterfly", "Buddy Butterfly (200)" or "Buddy Butterfly
200" works!

As long as the display name is sent within quotes, display names can
contain diples (">" and "<") so the display name is valid.

We just tried this locally and it seemed to work for us.

I already mentioned that we'd need you logs if we are to track the

problem.

  Though, it would be nice if we could use angle brackets.
2. No accept dialog displayed when call is coming in.
  When a call is received there is a message displayed in the right
  low edge of the screen with the number calling. But the call can
  not be answered as there is no accept butten respectively no accept
  dialog being displayed (apart from key shortcuts).

Unfortunately (as I already mentioned in my previous mails), we can't
reproduce this one either.

  I have found that this is because I have no video device. Global
  properties -> Video -> Devices does not list any device.

I find it quite unlikely that lack of a video device would be the
reason. There's probably something else.

  Cause of the problem:
  When there is no video codec selected (which is the default if there
is no video device)

It is not. Lack of a video device acquisition device has no impact on
the codecs we advertise. One cans still receive and render video.

, no accepting
  dialog will be displayed.

Just tried that too. Having manually disabled my video codecs, doesn't
prevent me from taking incoming calls.

There must be another reason why it's happening with your installation.

Cheers,
Emil

  On the other hand, if, for example, I select the first codec
  H263-1998 even having no device then there will be an accepting
  dialog displayed for an incoming call!

So, for the moment I can live with enabling this option and continue
testing jitsi and maybe replace Twinkle
with it.

Thanks a lot and best regards,
Matt

Am 24.08.2012 20:14, schrieb Emil Ivov:

Thanks Matt,

Could you please send us the complete logs [0]? We'd also need to have a
look at that SIP messages.

Emil

P.S. https://jitsi.org/faq/logs

On 22.08.12, 15:02, Buddy Butterfly wrote:

Behavior is such that incoming call rings,
a message windows is displayed but I am not able to accept the call via
clicking because
there is nowhere a button for this. When I try to accept the call via
key shortcut nothing
happens. No sound on both sides, nothing. With some combination I was
able to get a dialog
where I could accept the call but then also nothing happened. Now it
does not work anymore
and I am not sure which config combination brought up the dialog (i
guess is has something to
do with configuring video or video codecs, but should not matter).

Tnx,
Matt

Am 22.08.2012 14:41, schrieb Buddy Butterfly:

Hi Emil,

yep, did it like this as I was able to connect AND dial out.
Incoming calls are broken, though.

Best regards,
Matt

Am 22.08.2012 14:36, schrieb Emil Ivov:

Did you get my latest mail about serverless accounts? Did you try
using a server?

--sent from my mobile

On Aug 22, 2012 1:33 PM, "Buddy Butterfly" <buddy.butterfly@web.de >>>>>>>> <mailto:buddy.butterfly@web.de>> wrote:

   Hey there,

   I am following up this issue because I found some more time.
   I attached the logs, though with changed data.

   I still want to replace twinkle which is working perfectly for
   years now but
   because it is old and not maintained anymore, has its drawbacks.

   Any help is very welcome.

   Best regards,
   Matt

   Am 04.04.2012 16 <tel:04.04.2012%2016>:11, schrieb Buddy >> Butterfly:

Account:
SIP-ID: The name without server is given.

Connection:
   Rgistrar: Asterisk with hostname and port is given.
   Proxy: Same hostname and port is used as proxy

option.

Automatic configuration switched off.

Jitsi reports proper registration and shows "online".

Am 04.04.2012 15 <tel:04.04.2012%2015>:35, schrieb Emil Ivov:

Hey Matt,
On 04.04.12 15:26, Buddy Butterfly wrote:

Hi,

this is Jitsi connecting to a asterisk 1.4.36.
We use this as a telephone system for a long time now and

   never had problems (well, some standard problems with dtmf and
   the like ;-). I wanted to give Jitsi a try and replace Twinkle
   with it. But have numerous problems with it. Jitsi is very
   widely used with Asterisk and I don't believe we have seen
   similar behaviour so far. Can you tell us more on how you
   configured your account in Jitsi? Did you enter the server
   address as part of your

user name?

I will see to prepare the log files for you.

Here's how you could do this with a few clicks:
   http://jitsi.org/faq/logs

What would be a valid SIP request?

A valid request line would look something like:

BYE sip:200@192.168.0.1 <mailto:sip%3A200@192.168.0.1> SIP/2.0

Would it be worth to make Jitsi more tolerant here?

This is a rather serious error that's detected by the parser

   of the JSIP stack that Jitsi uses, so we'd have to implement
   quite a lot of rule breaking for this to work (provided we had
   a good reason to do this). We have implemented such "hacks"
   previously and it did happen to be for asterisk (and the way it
   handles message waiting indications) but this

is something significantly lower layer.

However, as I said, Jitsi is known to work quite reliably with

   asterisk, so I am more inclined to believe that this is a
   configuration error.

Cheers,
Emil

Best regards,
Matt

Am 04.04.2012 14 <tel:04.04.2012%2014>:46, schrieb Emil Ivov:

Well:

"BYE 200 SIP/2.0" is not a valid SIP Request line so the
failure is not
surprising.

Can you tell us more about how you get here? Your complete
logs would
also help.

Emil

On 04.04.12 14:18, Buddy Butterfly wrote:

Hi all,

I am not able to receive calls.
I am getting NullPointer Exceptions, Bad URL exceptions, etc.
See excerpt below.

I am running Kubuntu 11.04 amd64.
Java is:

java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6
1.10.6) (6b22-1.10.6-0ubuntu1) OpenJDK 64-Bit Server VM (build
20.0-b11, mixed mode)

Ekiga and Twinkle are running without any problems.

Best regards...

IP and phone number has been replaced.

--- snip --- 14:00:58.952 SCHWERWIEGEND:
impl.protocol.sip.CallPeerSipImpl.hangup().1042 Could not
determine call peer state! 14:01:28.764 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: BYE 200 SIP/2.0 :GenericURI, Bad URI format
14:01:28.764 INFO:
impl.protocol.sip.SipLogger.logException().77 JAIN-SIP
exception stack trace is java.text.ParseException: BYE 200
SIP/2.0 :GenericURI, Bad URI format
   at

gov.nist.javax.sip.parser.Parser.createParseException(Parser.java:45)

   at

gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:360)

   at

gov.nist.javax.sip.parser.RequestLineParser.parse(RequestLineParser.java:60)

   at

gov.nist.javax.sip.parser.StringMsgParser.processFirstLine(StringMsgParser.j
a

va:230)

   at

gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.ja
v

a:158)

   at

gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMess
a

geChannel.java:337)

   at

gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)

   at java.lang.Thread.run(Thread.java:679)
14:01:28.764 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BAD MESSAGE! 14:01:28.765 SCHWERWIEGEND:
impl.protocol.sip.SipLogger.logError().112 Error from the
JAIN-SIP stack: BYE 200 SIP/2.0 Via: SIP/2.0/UDP
192.168.1.1:5060;branch=z9hG4bK1ebf14e1;rport From:
"+49xxxxxxxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;tag=as2b1b0ac8 To:

   <sip:mwitkn-

200@192.168.1.155:5060;transport=udp;registering_acc=voip>;tag=cdd4f0a1

Call-ID: 5c92fb9035411a073f8c1483543d974d@192.168.1.1
<mailto:5c92fb9035411a073f8c1483543d974d@192.168.1.1> CSeq:
103 BYE User-Agent: Asterisk PBX Max-Forwards: 70
Remote-Party-ID: "+49xxxxxx" <sip:+49xxxxxxxxxxx@192.168.1.1
<mailto:sip%3A%2B49xxxxxxxxxxx@192.168.1.1>>;privacy=off;screen
=no X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16 Content-Length: 0

14:01:49.688 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: null java.lang.NullPointerException
   at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:156)

   at

net.java.sip.communicator.impl.gui.main.call.PreCallDialog.<init>(PreCallDia
l

og.java:121)

   at

net.java.sip.communicator.impl.gui.main.call.ReceivedCallDialog.<init>(Recei
v

edCallDialog.java:50)

   at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener.inc
o

mingCallReceived(CallManager.java:88)

   at

net.java.sip.communicator.impl.gui.main.call.CallManager$GuiCallListener$1.r
u

n(CallManager.java:81)

   at
   java.awt.event.InvocationEvent.dispatch(InvocationEvent.jav
   a:226) at
   java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
   at java.awt.EventQueue.access$000(EventQueue.java:96) at
   java.awt.EventQueue$1.run(EventQueue.java:608) at
   java.awt.EventQueue$1.run(EventQueue.java:606) at
   java.security.AccessController.doPrivileged(Native Method)
   at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

   at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
   at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

   at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

   at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

   at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

   at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

   at

   java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:02:02.274 SCHWERWIEGEND:
util.UtilActivator.uncaughtException().88 An uncaught
exception occurred in thread=Thread[AWT-EventQueue-0,6,main]
and message was: java.awt.TrayIcon cannot be cast to
java.awt.Component java.lang.ClassCastException:
java.awt.TrayIcon cannot be cast to java.awt.Component
   at

javax.swing.MenuSelectionManager.processMouseEvent(MenuSelectionManager.java
:

220)

   at

javax.swing.plaf.basic.BasicPopupMenuUI$MouseGrabber.eventDispatched(BasicPo
p

upMenuUI.java:860)

   at

java.awt.Toolkit$SelectiveAWTEventListener.eventDispatched(Toolkit.java:2378
)

   at

java.awt.Toolkit$ToolkitEventMulticaster.eventDispatched(Toolkit.java:2270)

   at
   java.awt.Toolkit.notifyAWTEventListeners(Toolkit.java:2228)
    at java.awt.TrayIcon.dispatchEvent(TrayIcon.java:725) at
   java.awt.EventQueue.dispatchEventImpl(EventQueue.java:654)
   at java.awt.EventQueue.access$000(EventQueue.java:96) at
   java.awt.EventQueue$1.run(EventQueue.java:608) at
   java.awt.EventQueue$1.run(EventQueue.java:606) at
   java.security.AccessController.doPrivileged(Native Method)
   at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

   at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:116)

   at java.awt.EventQueue$2.run(EventQueue.java:622) at
   java.awt.EventQueue$2.run(EventQueue.java:620) at
   java.security.AccessController.doPrivileged(Native Method)
   at

java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlCo
n

text.java:105)

   at java.awt.EventQueue.dispatchEvent(EventQueue.java:619)
   at

java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java
:

275)

   at

java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:20
0

)

   at

java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java
:

190)

   at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)

   at

java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)

   at

   java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

14:03:00.579 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:03:00.583 INFO:

impl.osdependent.jdic.SystrayServiceJdicImpl.setActivePopupMessageHandler().
5

93

setting the following popup handler as active : Jitsi Pop-Ups
14:05:40.806 WARNUNG:
impl.protocol.sip.SipLogger.logException().75 Exception in the
JAIN-SIP stack: ACK 200 SIP/2.0 --- snap ---

--
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