[jitsi-dev] Run into problem on setting-up Jigasi debug environment


#1

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the "jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added few line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39] impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173 Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException: javax.crypto.BadPaddingException: Given final block not properly padded

at net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not properly padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available" after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

···

Sent from Outlook<http://aka.ms/weboutlook>


#2

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

···

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at
net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at
net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at
net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at
gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at
gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at
gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#3

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted password"?

However, it sounds those logic should keep to be compatible with other version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at the moment.

Next, it requires to set below config properties (otherwise, it won't go thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and "PASSWORD" properties here?

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at
net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at
net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at
net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at
gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at
gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at
gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup without throwing exception.

However, when I make SIP call thur the website, it will throw exception as shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted password"?

However, it sounds those logic should keep to be compatible with other version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at the moment.

Next, it requires to set below config properties (otherwise, it won't go thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and "PASSWORD" properties here?

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at
net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at
net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at
net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at
net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at
net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at
net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at
gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at
gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at
gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at
gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at
net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#5

This is the connection to prosody 5222, the client xmpp connection jigasi uses.

···

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup without
throwing exception.

However, when I make SIP call thur the website, it will throw exception as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

···

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

This is the connection to prosody 5222, the client xmpp connection jigasi uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup without
throwing exception.

However, when I make SIP call thur the website, it will throw exception as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

···

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent) of net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP server)?

Thank you very much,

Sunny Mok

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#9

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

···

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#10

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()" function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#11

Is that anything to do with ICE? or the callee is not available?

Further error log:

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

Aug 05, 2016 6:11:46 PM org.ice4j.ice.Agent setState
INFO: ICE state changed from Waiting to Terminated
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger error
SEVERE: Did not received session invite within 30000 ms
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: 1565a2fa54b@callcontrol.192.168.3.73 is removing account Jabber:1565a2fa54b@192.168.3.73/1565a2fa54b
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key: service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key: service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Jingle : OFF
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Removed session for call 1565a2fa54b@callcontrol.192.168.3.73

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Friday, August 5, 2016 1:42 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()" function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing
RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at
net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at
net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]
impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at
gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#12

Hi,

Check in whether you have disco info enabled in prosody main config.
"disco"; -- Service discovery
How did you install it?
Normally if you install everything by default just using the debian
packages it should work out of the box and you should not touch
anything.

Regards
damencho

···

On Fri, Aug 5, 2016 at 5:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Is that anything to do with ICE? or the callee is not available?

Further error log:

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

Aug 05, 2016 6:11:46 PM org.ice4j.ice.Agent setState
INFO: ICE state changed from Waiting to Terminated
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger error
SEVERE: Did not received session invite within 30000 ms
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: 1565a2fa54b@callcontrol.192.168.3.73 is removing account
Jabber:1565a2fa54b@192.168.3.73/1565a2fa54b
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Jingle : OFF
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Removed session for call 1565a2fa54b@callcontrol.192.168.3.73

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Friday, August 5, 2016 1:42 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()"
function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing

RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi
at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine
in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]

impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at

gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not
available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a
while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#13

Hi damencho,

I see "disco" inside "modules_enabled" scope in "/etc/prosody/prosody.cfg.lua" as below.

···

-----

modules_enabled = {

    -- Generally required

    "roster"; -- Allow users to have a roster. Recommended :wink:

    "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.

    "tls"; -- Add support for secure TLS on c2s/s2s connections

    "dialback"; -- s2s dialback support

    "disco"; -- Service discovery

-----

I assume "prosody.cfg.lua" is the global config applying to any interface,

and "192.168.3.73.cfg.lua" applies to only 192.168.3.73.

Is that correct?

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Friday, August 5, 2016 5:15 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi,

Check in whether you have disco info enabled in prosody main config.
"disco"; -- Service discovery
How did you install it?
Normally if you install everything by default just using the debian
packages it should work out of the box and you should not touch
anything.

Regards
damencho

On Fri, Aug 5, 2016 at 5:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Is that anything to do with ICE? or the callee is not available?

Further error log:

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

Aug 05, 2016 6:11:46 PM org.ice4j.ice.Agent setState
INFO: ICE state changed from Waiting to Terminated
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger error
SEVERE: Did not received session invite within 30000 ms
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: 1565a2fa54b@callcontrol.192.168.3.73 is removing account
Jabber:1565a2fa54b@192.168.3.73/1565a2fa54b
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Jingle : OFF
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Removed session for call 1565a2fa54b@callcontrol.192.168.3.73

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Friday, August 5, 2016 1:42 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()"
function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing

RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi
at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine
in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]

impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at

gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not
available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a
while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#14

Hi damencho,

I set ALWAYS_TRUST_MODE_ENABLED to be true in Jigasi's config sip-communicator.properties as well:

net.java.sip.communicator.service.gui.ALWAYS_TRUST_MODE_ENABLED=true

Coz some exceptions were gone after this setting. Is that config a matter?

Thanks,

Sunny

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Sunday, August 7, 2016 6:36 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi damencho,

I see "disco" inside "modules_enabled" scope in "/etc/prosody/prosody.cfg.lua" as below.

-----

modules_enabled = {

    -- Generally required

    "roster"; -- Allow users to have a roster. Recommended :wink:

    "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.

    "tls"; -- Add support for secure TLS on c2s/s2s connections

    "dialback"; -- s2s dialback support

    "disco"; -- Service discovery

-----

I assume "prosody.cfg.lua" is the global config applying to any interface,

and "192.168.3.73.cfg.lua" applies to only 192.168.3.73.

Is that correct?

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Friday, August 5, 2016 5:15 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi,

Check in whether you have disco info enabled in prosody main config.
"disco"; -- Service discovery
How did you install it?
Normally if you install everything by default just using the debian
packages it should work out of the box and you should not touch
anything.

Regards
damencho

On Fri, Aug 5, 2016 at 5:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Is that anything to do with ICE? or the callee is not available?

Further error log:

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

Aug 05, 2016 6:11:46 PM org.ice4j.ice.Agent setState
INFO: ICE state changed from Waiting to Terminated
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger error
SEVERE: Did not received session invite within 30000 ms
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: 1565a2fa54b@callcontrol.192.168.3.73 is removing account
Jabber:1565a2fa54b@192.168.3.73/1565a2fa54b
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Jingle : OFF
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Removed session for call 1565a2fa54b@callcontrol.192.168.3.73

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Friday, August 5, 2016 1:42 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()"
function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing

RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi
at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine
in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]

impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at

gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not
available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a
while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#15

Hi damencho,

I come across this link about "disco" config:

https://prosody.im/doc/modules/mod_disco#configuration

Should I set the "disco_items" as well?

and what links/items are supposed to be in the list?

Thanks,

Sunny

···

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Sunday, August 7, 2016 6:46 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi damencho,

I set ALWAYS_TRUST_MODE_ENABLED to be true in Jigasi's config sip-communicator.properties as well:

net.java.sip.communicator.service.gui.ALWAYS_TRUST_MODE_ENABLED=true

Coz some exceptions were gone after this setting. Is that config a matter?

Thanks,

Sunny

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok <apollomok@hotmail.com>
Sent: Sunday, August 7, 2016 6:36 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi damencho,

I see "disco" inside "modules_enabled" scope in "/etc/prosody/prosody.cfg.lua" as below.

-----

modules_enabled = {

    -- Generally required

    "roster"; -- Allow users to have a roster. Recommended :wink:

    "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.

    "tls"; -- Add support for secure TLS on c2s/s2s connections

    "dialback"; -- s2s dialback support

    "disco"; -- Service discovery

-----

I assume "prosody.cfg.lua" is the global config applying to any interface,

and "192.168.3.73.cfg.lua" applies to only 192.168.3.73.

Is that correct?

Sent from Outlook<http://aka.ms/weboutlook>

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov <damencho@jitsi.org>
Sent: Friday, August 5, 2016 5:15 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug environment

Hi,

Check in whether you have disco info enabled in prosody main config.
"disco"; -- Service discovery
How did you install it?
Normally if you install everything by default just using the debian
packages it should work out of the box and you should not touch
anything.

Regards
damencho

On Fri, Aug 5, 2016 at 5:14 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Is that anything to do with ICE? or the callee is not available?

Further error log:

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

Aug 05, 2016 6:11:46 PM org.ice4j.ice.Agent setState
INFO: ICE state changed from Waiting to Terminated
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger error
SEVERE: Did not received session invite within 30000 ms
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: 1565a2fa54b@callcontrol.192.168.3.73 is removing account
Jabber:1565a2fa54b@192.168.3.73/1565a2fa54b
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger warn
WARNING: Missing resource for key:
service.gui.NOT_IN_CONTACT_LIST_GROUP_NAME
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Jingle : OFF
Aug 05, 2016 6:11:57 PM net.java.sip.communicator.util.Logger info
INFO: Removed session for call 1565a2fa54b@callcontrol.192.168.3.73

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Friday, August 5, 2016 1:42 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

Jigasi throws NullPointerException when it runs further.

INFO: Failed to process an incoming session initiate
java.lang.NullPointerException
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.setTransportManager(CallPeerMediaHandlerJabberImpl.java:2100)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.processOffer(CallPeerMediaHandlerJabberImpl.java:1753)
at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.processSessionInitiate(CallPeerJabberImpl.java:798)
at
net.java.sip.communicator.impl.protocol.jabber.CallJabberImpl.processSessionInitiate(CallJabberImpl.java:1001)
at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl$2.run(OperationSetBasicTelephonyJabberImpl.java:1024)

I stepped into the code,

and found a call "getDiscoveryManager()" was inside "setTransportManager()"
function in class "CallPeerMediaHandlerJabberImpl".

However, the discovery manager was a null pointer at that time.

Should I configure anything further in this case?

Thanks,

Sunny

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:44 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

You can ignore this exception. VCards requires it, but they are not
used by jigasi. Maybe at some point we can disable
OperationSetPersistentPresence at all.

On Fri, Aug 5, 2016 at 12:31 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

I explicitly set "anonymous" authentication for Jigasi as below in my
prosody cfg file (192.168.3.73.cfg.lua) :

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

    authentication = "anonymous"

Jigasi still throws below exception:

SEVERE: An error occurred while executing

RegistrationStateChangeListener#registrationStateChanged(RegistrationStateChangeEvent)
of

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener@498d104c
java.lang.IllegalArgumentException: Connection cannot be anonymous
at org.jivesoftware.smackx.packet.VCard.checkAuthenticated(VCard.java:571)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:511)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl.createAccountPhotoPresenceInterceptor(OperationSetPersistentPresenceJabberImpl.java:1898)
at

net.java.sip.communicator.impl.protocol.jabber.OperationSetPersistentPresenceJabberImpl$RegistrationStateListener.registrationStateChanged(OperationSetPersistentPresenceJabberImpl.java:1106)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:187)
at

net.java.sip.communicator.service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged(AbstractProtocolProviderService.java:141)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1314)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:944)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:755)
at

net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:468)
at org.jitsi.jigasi.RegisterThread.run(RegisterThread.java:58)

Is it complaining about anonymous login from Jigasi to the prosody (XMPP
server)?

Thank you very much,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 10:18 PM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

No,

Component is the xmpp component. You need xmpp account for jigasi only
if your prosody is configured to accept only authenticated users. If
anonymous is enabled you do not need that.

Regards
damencho

On Thu, Aug 4, 2016 at 9:19 PM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

In my prosody config file "192.168.3.73.cfg.lua", I can see:

------

Component "callcontrol.192.168.3.73"

    component_secret = "lEQ9HBhE"

------

In such case, should I set the Jigasi config on my desktop to be:

org.jitsi.jigasi.xmpp.acc.USER_ID = callcontrol.192.168.3.73

org.jitsi.jigasi.xmpp.acc.PASS = lEQ9HBhE

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Thursday, August 4, 2016 7:20 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

This is the connection to prosody 5222, the client xmpp connection jigasi
uses.

On Thu, Aug 4, 2016 at 2:28 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi damencho,

After I uncomment and fill in those properties, Jigasi could startup
without
throwing exception.

However, when I make SIP call thur the website, it will throw exception
as
shown:

Aug 04, 2016 3:24:19 PM org.jivesoftware.smack.PacketReader
notifyConnectionError
SEVERE: Closes the connection temporary
stream:error (text)
at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

does anyone have idea?

I looked into the PacketReader,

and saw it was parsing "stream" and "error" from a buffer,

but I couldn't figure out what it is parsing.

Thanks,

Sunny Mok

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Sunny Mok
<apollomok@hotmail.com>
Sent: Thursday, August 4, 2016 12:18 AM

To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi damencho,

I tried to encode my password with the same logic in Jigasi,

and it came out a different "encrypted password" from jitsi app.

Do you mean different java version would create different "encrypted
password"?

However, it sounds those logic should keep to be compatible with other
version as well, doesn't it?

Anyway, I used that generated password to go on my debugging on Jigasi
at
the moment.

Next, it requires to set below config properties (otherwise, it won't go
thur):

- org.jitsi.jigasi.xmpp.acc.USER_ID

- org.jitsi.jigasi.xmpp.acc.PASS

- org.jitsi.jigasi.xmpp.acc.ANONYMOUS_AUTH
Should I type in the same user ID and password as "ACCOUNT_UID" and
"PASSWORD" properties here?

Sent from Outlook

________________________________
From: dev <dev-bounces@jitsi.org> on behalf of Damian Minkov
<damencho@jitsi.org>
Sent: Wednesday, August 3, 2016 7:58 AM
To: Jitsi Developers
Subject: Re: [jitsi-dev] Run into problem on setting-up Jigasi debug
environment

Hi,

not sure but this can be result of using different java version while
creating the password and while running.

Regards
damencho

On Wed, Aug 3, 2016 at 3:55 AM, Sunny Mok <apollomok@hotmail.com> wrote:

Hi everyone,

In short, I try to run Jigasi on my local machine in debug mode, but I
couldn't make it so far.

First, I have a debian server with Jitsi and Jigasi installed, and the
versions are:

Jitsi-meet = 1.0.1072-1

Jitsi-meet-prosody = 1.0.1072-1

jitsi-videobridge = 750-1

jigasi = 1.0-107

Jigasi could send an INVITE message, but the SIP proxy shows that
message
SDP with null values:

o=+85287654321-jitsi.org 0 0 IN null null

So, I downloaded Jigasi source code and I try to run on local machine
in
debug mode.

I did:

- it can run "ant make" successfully, and can build the jar package

- I copied the "sip-communicator.properties" file from server to the
"jigasi-home" folder under Jigasi project.

- In the lua file under "/etc/prosody/conf.avail/192.168.3.73", I added
few
line in global scope:

component_interface = "192.168.3.73"

component_ports = { 5347 }

Now:

1st) I run the code, and it gets below exception:

2016-08-03 16:44:18.560 SEVERE: [39]

impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword().173
Decryption with master password failed

net.java.sip.communicator.service.credentialsstorage.CryptoException:
javax.crypto.BadPaddingException: Given final block not properly padded

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:184)

at

net.java.sip.communicator.impl.credentialsstorage.CredentialsStorageServiceImpl.loadPassword(CredentialsStorageServiceImpl.java:169)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:953)

at

net.java.sip.communicator.service.protocol.ProtocolProviderFactory.loadPassword(ProtocolProviderFactory.java:922)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:227)

at

net.java.sip.communicator.impl.protocol.sip.security.SipSecurityManager.handleChallenge(SipSecurityManager.java:138)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processAuthenticationChallenge(SipRegistrarConnection.java:997)

at

net.java.sip.communicator.impl.protocol.sip.SipRegistrarConnection.processResponse(SipRegistrarConnection.java:937)

at

net.java.sip.communicator.impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse(ProtocolProviderServiceSipImpl.java:781)

at

net.java.sip.communicator.impl.protocol.sip.SipStackSharing.processResponse(SipStackSharing.java:762)

at

gov.nist.javax.sip.EventScanner.deliverResponseEvent(EventScanner.java:317)

at gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:148)

at

gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:185)

at
gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1514)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.nonInviteClientTransaction(SIPClientTransactionImpl.java:630)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:535)

at

gov.nist.javax.sip.stack.SIPClientTransactionImpl.processResponse(SIPClientTransactionImpl.java:1622)

at

gov.nist.javax.sip.stack.ConnectionOrientedMessageChannel.processMessage(ConnectionOrientedMessageChannel.java:530)

at

gov.nist.javax.sip.parser.PipelinedMsgParser.run(PipelinedMsgParser.java:541)

at java.lang.Thread.run(Thread.java:745)

Caused by: javax.crypto.BadPaddingException: Given final block not
properly
padded

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)

at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)

at com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:313)

at javax.crypto.Cipher.doFinal(Cipher.java:2087)

at

net.java.sip.communicator.impl.credentialsstorage.AESCrypto.decrypt(AESCrypto.java:179)

... 19 more

2nd) On the website, it keeps showing "focus.192.168.3.73 not
available"
after I create and join inside a video group chat.

I really appreciate any advice in advance. I have struggled for a
while.

Thanks,

Sunny Mok

Sent from Outlook

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev