[jitsi-dev] Jigasi + jitsi-videobridge known working versions


#1

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al


#2

Just adding the information that I use Ubuntu 14.04 LTS

···

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al


#3

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

···

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

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


#4

Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

···

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

···

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Do you think it could be useful to try the versions from unstable?

Thanks for the help! Really crazy is, that I got in a specific combination of versions (I think jitsi-meet bundle from testing and jigasi from stable) the first call was successful with audio. The following not… :(.

I will try the jitsi-desktop client and the sip settings and report back.

···

Am 16.07.2017 um 23:33 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

···

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

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

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

···

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

···

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

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

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

···

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Hi damencho,

I found this setting:

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN

Is this something that I have to configure to resolve the issue? This is
at the moment commented out.

Thanks.

Regards

Th3R3al

···

Am 17.07.2017 um 20:03 schrieb Damian Minkov:

Hi,

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

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

So jigasi by default connects to directly to port 5222 to communicate
with the xmpp server. This just enables this communication to be done
over bosh. So I doubt this will change something.
I was looking at the logs you send me and I cannot see something
suspicious that will result those kind of errors. I'm really out of
ideas, can you try updating everything to unstable and see do you see
any change, I know I told you the versions shouldn't be a problem, but
as I'm out of ideas.

Regards
damencho

···

On Tue, Jul 18, 2017 at 1:54 PM, Th3R3al <th3r3al@cloudreboot.de> wrote:

Hi damencho,

I found this setting:

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN

Is this something that I have to configure to resolve the issue? This is
at the moment commented out.

Thanks.

Regards

Th3R3al

Am 17.07.2017 um 20:03 schrieb Damian Minkov:

Hi,

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Its quite strange.. I am again at the point described earlier. If i
restart all the services (including prosody) jigasi works for 1 call -
the errors mentioned earlier are also occuring in the meeting, but seems
not to be the cause of the issue.

I update the setup now to the versions on unstable.

Regards

Th3R3al

···

Am 18.07.2017 um 21:00 schrieb Damian Minkov:

Hi,

So jigasi by default connects to directly to port 5222 to communicate
with the xmpp server. This just enables this communication to be done
over bosh. So I doubt this will change something.
I was looking at the logs you send me and I cannot see something
suspicious that will result those kind of errors. I'm really out of
ideas, can you try updating everything to unstable and see do you see
any change, I know I told you the versions shouldn't be a problem, but
as I'm out of ideas.

Regards
damencho

On Tue, Jul 18, 2017 at 1:54 PM, Th3R3al <th3r3al@cloudreboot.de> wrote:

Hi damencho,

I found this setting:

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN

Is this something that I have to configure to resolve the issue? This is
at the moment commented out.

Thanks.

Regards

Th3R3al

Am 17.07.2017 um 20:03 schrieb Damian Minkov:

Hi,

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

Same issue on unstable.

The first call is working after i restart all services. Maybe its caused
by the online pbx I am using? (But why?)

Regards

Th3R3al

···

Am 18.07.2017 um 21:07 schrieb Th3R3al:

Its quite strange.. I am again at the point described earlier. If i
restart all the services (including prosody) jigasi works for 1 call -
the errors mentioned earlier are also occuring in the meeting, but seems
not to be the cause of the issue.

I update the setup now to the versions on unstable.

Regards

Th3R3al

Am 18.07.2017 um 21:00 schrieb Damian Minkov:

Hi,

So jigasi by default connects to directly to port 5222 to communicate
with the xmpp server. This just enables this communication to be done
over bosh. So I doubt this will change something.
I was looking at the logs you send me and I cannot see something
suspicious that will result those kind of errors. I'm really out of
ideas, can you try updating everything to unstable and see do you see
any change, I know I told you the versions shouldn't be a problem, but
as I'm out of ideas.

Regards
damencho

On Tue, Jul 18, 2017 at 1:54 PM, Th3R3al <th3r3al@cloudreboot.de> wrote:

Hi damencho,

I found this setting:

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN

Is this something that I have to configure to resolve the issue? This is
at the moment commented out.

Thanks.

Regards

Th3R3al

Am 17.07.2017 um 20:03 schrieb Damian Minkov:

Hi,

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:

Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
    at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
    at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:

Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS

Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

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


#15

Hi,

i changed the online pbx now to sipgate. But got the same issue with jigasi. I will try to look in the pcap files jigasi is creating if I see some errors.

Help is much appreciated. :confused:

Thanks!
Th3R3al

Anfang der weitergeleiteten E‑Mail:

···

Von: Th3R3al <th3r3al@cloudreboot.de>
Datum: 18. Juli 2017 um 21:14:15 MESZ
An: dev@jitsi.org
Betreff: Re: [jitsi-dev] Jigasi + jitsi-videobridge known working versions
Antwort an: Jitsi Developers <dev@jitsi.org>

Same issue on unstable.

The first call is working after i restart all services. Maybe its caused
by the online pbx I am using? (But why?)

Regards

Th3R3al

Am 18.07.2017 um 21:07 schrieb Th3R3al:
Its quite strange.. I am again at the point described earlier. If i
restart all the services (including prosody) jigasi works for 1 call -
the errors mentioned earlier are also occuring in the meeting, but seems
not to be the cause of the issue.

I update the setup now to the versions on unstable.

Regards

Th3R3al

Am 18.07.2017 um 21:00 schrieb Damian Minkov:
Hi,

So jigasi by default connects to directly to port 5222 to communicate
with the xmpp server. This just enables this communication to be done
over bosh. So I doubt this will change something.
I was looking at the logs you send me and I cannot see something
suspicious that will result those kind of errors. I'm really out of
ideas, can you try updating everything to unstable and see do you see
any change, I know I told you the versions shouldn't be a problem, but
as I'm out of ideas.

Regards
damencho

On Tue, Jul 18, 2017 at 1:54 PM, Th3R3al <th3r3al@cloudreboot.de> wrote:
Hi damencho,

I found this setting:

org.jitsi.jigasi.xmpp.acc.BOSH_URL_PATTERN

Is this something that I have to configure to resolve the issue? This is
at the moment commented out.

Thanks.

Regards

Th3R3al

Am 17.07.2017 um 20:03 schrieb Damian Minkov:
Hi,

This is strange and needs looking at it. When this happens can you
execute in the console APP.conference.saveLogs() and send the file it
will contain all the xmpp messages that were exchanged. If you are
concerned about private data, you can send it directly to me in a
private message.

Regards
damencho

On Sun, Jul 16, 2017 at 5:14 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Hmm.

Ah, something other thing.. the member that is created from jigasi is always displayed as „having connectivity issues“. :confused:

And I see this on my google chrome console:

conference.js] <e.value>: CONFERENCE FAILED: conference.setup_failed Error: ICE fail
   at o.peerconnection.oniceconnectionstatechange (JingleSessionPC.js:398)
   at RTCPeerConnection.peerconnection.oniceconnectionstatechange (TraceablePeerConnection.js:246)

And this…

modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate
r @ Logger.js:125
Logger.js:125 [modules/xmpp/JingleSessionPC.js] <>: addIceCandidate failed! DOMException: Error processing ICE candidate

Maybe this help debugging this?

Am 16.07.2017 um 23:57 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

Now as I said earlier versions doesn't matter. I would just suggest
trying jigasi from unstable there were some bug fixes recently which
you maybe hitting, as you said it worked once...

So if you had it working once, this is really strange, and maybe the
part with jitsi desktop is not relevant, cause if something in the sip
settings was wrong no successful call will be made at all.

Thanks Ingo for the update, I will try adding this to the readme of jigasi.

Regards
damencho

On Sun, Jul 16, 2017 at 4:53 PM, Ingo Bauersachs <ingo@jitsi.org> wrote:
Create .usepropfileconfig where the properties-file would reside.

Freundliche Grüsse,
Ingo Bauersachs

-- Sent from my tablet

On 16.07.2017, at 23:36, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

This kind of problems are hard to debug. You need to make sure where
does the audio stops. You can use tcpdump on jigasi machine to see
whether something is going to the sip server or coming from it.
You can also check webrtc-internals whether something from that
participant is reaching your browser.
Normally we suggest to install jitsi desktop client and configure your
sip account there and make sure calling with it works and the use
those settings in jigasi (directly copying them from the config file
sip-communicator.properties).

Hey @Ingo, how one can force using properties file instead of the
embedded database for configuration in jitsi desktop, thanks?

Regards
damencho

On Sun, Jul 16, 2017 at 4:04 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Thanks for your fast answer.

Issue Description: I can call a number and the phone is ringing - I can also take the call on my telephone. But there is no audio in the conference and on the telephone (both directions).

I use the last versions from stable. (Jigasi, jitsi-meet bundle)

This are (maybe) some interesting log lines from the jigasi.log:

2017-07-16 22:53:34.055 WARNING: [332] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2017-07-16 22:53:34.057 INFO: [332] org.jitsi.jigasi.GatewaySession.onConferenceCallStarted().468 Created outgoing call to phonenumber Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:34.058 INFO: [332] org.jitsi.jigasi.JvbConference.peerStateChanged().874 15d4d2d7fb9@callcontrol.jitsi.mydomain.com JVB peer state: net.java.sip.communicat
or.service.protocol.CallPeerState:Connected
2017-07-16 22:53:34.059 INFO: [332] org.jitsi.jigasi.JvbConference.advertisePeerSSRCs().220 Peer net.java.sip.communicator.service.protocol.CallPeerState:Connected SSRCs audio: 2741
43348 video: null
2017-07-16 22:53:34.090 INFO: [4842] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.091 INFO: [4842] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting
2017-07-16 22:53:34.091 INFO: [4843] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.095 INFO: [4843] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:34.128 INFO: [4844] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().191 Auto discovered harvester is null
2017-07-16 22:53:34.138 INFO: [4845] impl.protocol.jabber.IceUdpTransportManager.createIceAgent().283 End gathering harvester within 1 ms
2017-07-16 22:53:34.150 INFO: [4577] impl.protocol.jabber.JingleNodesHarvester.harvest().91 harvest Jingle Nodes
2017-07-16 22:53:34.651 INFO: [4845] impl.protocol.jabber.CallPeerMediaHandlerJabberImpl.harvestCandidates().1192 End candidate harvest within 511 ms
2017-07-16 22:53:34.652 INFO: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().829 Got invite from 24348725
2017-07-16 22:53:34.653 WARNING: [4845] org.jitsi.jigasi.JvbConference.incomingCallReceived().834 Calls not initiated from focus are not allowed
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: audio - ignored candidates.
2017-07-16 22:53:34.665 WARNING: [4540] impl.protocol.jabber.IceUdpTransportManager.startConnectivityEstablishment().968 No ICE media stream for media: video - ignored candidates.
2017-07-16 22:53:36.545 INFO: [4921] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1001 Dynamic PT map: 96=rtpmap:-1 opus/48000/2 fmtp:usedtx=1; 98=rtpmap:-1 iLBC/8000; 101=rtpmap:-1 telephone-event/8000; 97=rtpmap:-1 AMR-WB/16000;
2017-07-16 22:53:36.549 INFO: [4921] service.protocol.media.MediaHandler.registerDynamicPTsWithStream().1018 PT overrides []
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().761 Sip call IN_PROGRESS: Call: id=1500238414042885475203 peers=1
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.handleCallState().769 SIP call format used: rtpmap:8 PCMA/8000
2017-07-16 22:53:36.550 INFO: [4921] org.jitsi.jigasi.GatewaySession.peerStateChanged().836 15d4d2d7fb9@callcontrol.jitsi.mydomain.com SIP peer state: Connecting*
2017-07-16 22:53:36.550 INFO: [4921] service.protocol.media.CallPeerMediaHandler.start().1962 Starting
2017-07-16 22:53:36.577 INFO: [4921] service.protocol.media.TransportManager.sendHolePunchPacket().534 Send NAT hole punch packets
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Unable to handle format: LINEAR, 48000.0 Hz, 16-bit, Mono, LittleEndian, Signed
2017-07-16 22:53:36.604 SEVERE: [4964] net.sf.fmj.media.Log.error() Failed to prefetch: net.sf.fmj.media.ProcessEngine@1ffc29fe
2017-07-16 22:53:36.604 SEVERE: [4963] net.sf.fmj.media.Log.error() Error: Unable to prefetch net.sf.fmj.media.ProcessEngine@1ffc29fe

2017-07-16 22:53:37.506 INFO: [52] impl.protocol.sip.ProxyRouter.getNextHop().167 Outbound proxy mode, using proxy 81.20.137.99:5060/UDP as hop instead of an address resolved by the SIP router
2017-07-16 22:53:37.539 INFO: [4973] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060
2017-07-16 22:53:39.822 INFO: [4974] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /81.20.137.99:5060

I use prosody internal authentication in my setup this seems to be working fine. (Got some extra credentials for jigasi and configured the creds in the config).

Thanks!

Regards
Th3R3al

Am 16.07.2017 um 22:47 schrieb Damian Minkov <damencho@jitsi.org>:

Hi,

The versions between jitsi-meet and its components and jigasi don't
matter. On meet.jit.si we are using latest jigasi and latest
jitsi-meet, by latest I mean those from unstable.

You can add your jigasi logs and describe the problems you have.

Regards
damencho

On Sun, Jul 16, 2017 at 3:43 PM, thereal33c3 <th3r3al@cloudreboot.de> wrote:
Just adding the information that I use Ubuntu 14.04 LTS
Am 16.07.2017 um 22:41 schrieb thereal33c3 <th3r3al@cloudreboot.de>:

Hi,

Is there a known version where jitsi-meet (including jicofo, jitsi-videobridge and so on..) is working with jigasi?

I got some hiccups with the stable versions from the repository. The best constellation was to have 1 working call in a meeting, after this jigasi is not working anymore since I restart all related services.

Thanks in advance.

Th3R3al

_______________________________________________
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

_______________________________________________
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