[jitsi-dev] Manual installation init.d scripts and passing data from client to Jigasi


#1

Hi,

When installing Jitsi-Meet manually, is there a way to get the init.d scripts that you get when using quick install?

My second question is that is there a way to have multiple SIP accounts in Jigasi and control which one to use from the client side? The use case is that a Jitsi conference will be embedded in another web page. Now, depending on the network location of the web page, the dialed SIP number is different as well as the login credentials to SIP. Since I am starting the SIP call from Jicofo and not in the browser I need a way to pass information to Jicofo either from the client or from Nginx, which knows the network location. Do you have any suggestions how to do this?

Best regards,
Markus


#2

Hi,

Hi,

When installing Jitsi-Meet manually, is there a way to get the init.d
scripts that you get when using quick install?

Yes, all the sources are there:
https://github.com/jitsi/jitsi-videobridge/blob/master/resources/install/debian/init.d
https://github.com/jitsi/jicofo/blob/master/resources/install/debian/init.d

My second question is that is there a way to have multiple SIP accounts in
Jigasi and control which one to use from the client side?

This is currently not supported, jigasi instance makes one connection
to jicofo and there is no way of jicofo to select accounts, but there
can be multiple sip accounts in jigasi, it uses the jitsi-desktop
accounts loading.

The use case is
that a Jitsi conference will be embedded in another web page. Now, depending
on the network location of the web page, the dialed SIP number is different
as well as the login credentials to SIP. Since I am starting the SIP call
from Jicofo and not in the browser I need a way to pass information to
Jicofo either from the client or from Nginx, which knows the network
location. Do you have any suggestions how to do this?

Currently, there is a deployment info that is sent from the client to
jicofo. I need to verify this. You can always get the client ip in
nginx and add the ip to the deployment info (in config.js, this will
be generated on every fetch of it, you can see this is already done on
https://meet.jit.si/config.js). Than when you receive the information
in jicofo, you can use it to call number A or Number B on the jigasi
that is found. And You will need modifications in jigasi to choose an
account based on the number you receive.
To have multiple accounts you just need to have the appropriate
account settings, currently by default you have:
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.XXXXX,
you just need to add multiple of those like:
net.java.sip.communicator.impl.protocol.sip.acc1.XXXXX
net.java.sip.communicator.impl.protocol.sip.acc2.XXXXX

Regards
damencho

···

On Thu, Jan 11, 2018 at 1:44 AM, <markus.kullberg@teliacompany.com> wrote:

Best regards,

Markus

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


#3

Hello,

Thanks for your reply. I can see that the options in Jicofo are here: https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/JitsiMeetConfig.java . Are all options in config.js automatically passed here? And since deploymentInfo in config.js is a dictionary how is it parsed in Java? The constructor gets a Map<String, String> as a parameter so I'm guessing that the key, value pairs are taken directly from the dictionary, is this right? Is there a prefix or something to avoid duplicate keys?

And just to reiterate to make sure that I understood your proposed approach: I keep different config.js files on the web server with different deploymentInfo values, and depending the client IP-address I serve the right one?

Best regards,
Markus

···

-----Original Message-----
From: dev [mailto:dev-bounces@jitsi.org] On Behalf Of Damian Minkov
Sent: 11. tammikuuta 2018 16:37
To: Jitsi Developers <dev@jitsi.org>
Subject: Re: [jitsi-dev] Manual installation init.d scripts and passing data from client to Jigasi

Hi,

On Thu, Jan 11, 2018 at 1:44 AM, <markus.kullberg@teliacompany.com> wrote:

Hi,

When installing Jitsi-Meet manually, is there a way to get the init.d
scripts that you get when using quick install?

Yes, all the sources are there:
https://github.com/jitsi/jitsi-videobridge/blob/master/resources/install/debian/init.d
https://github.com/jitsi/jicofo/blob/master/resources/install/debian/init.d

My second question is that is there a way to have multiple SIP
accounts in Jigasi and control which one to use from the client side?

This is currently not supported, jigasi instance makes one connection to jicofo and there is no way of jicofo to select accounts, but there can be multiple sip accounts in jigasi, it uses the jitsi-desktop accounts loading.

The use case is
that a Jitsi conference will be embedded in another web page. Now,
depending on the network location of the web page, the dialed SIP
number is different as well as the login credentials to SIP. Since I
am starting the SIP call from Jicofo and not in the browser I need a
way to pass information to Jicofo either from the client or from
Nginx, which knows the network location. Do you have any suggestions how to do this?

Currently, there is a deployment info that is sent from the client to jicofo. I need to verify this. You can always get the client ip in nginx and add the ip to the deployment info (in config.js, this will be generated on every fetch of it, you can see this is already done on https://meet.jit.si/config.js). Than when you receive the information in jicofo, you can use it to call number A or Number B on the jigasi that is found. And You will need modifications in jigasi to choose an account based on the number you receive.
To have multiple accounts you just need to have the appropriate account settings, currently by default you have:
net.java.sip.communicator.impl.protocol.sip.acc1403273890647.XXXXX,
you just need to add multiple of those like:
net.java.sip.communicator.impl.protocol.sip.acc1.XXXXX
net.java.sip.communicator.impl.protocol.sip.acc2.XXXXX

Regards
damencho

Best regards,

Markus

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

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


#4

No, only config.deploymentInfo.userRegion is passed to jicofo as a "region" element.

Boris

···

On 15/01/2018 07:50, markus.kullberg@teliacompany.com wrote:

Hello,

Thanks for your reply. I can see that the options in Jicofo are here: https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/JitsiMeetConfig.java . Are all options in config.js automatically passed here?


#5

Sorry Markus, I thought all of that goes back to jicofo ...

···

On Mon, Jan 15, 2018 at 8:12 PM, Boris Grozev <boris@jitsi.org> wrote:

On 15/01/2018 07:50, markus.kullberg@teliacompany.com wrote:

Hello,

Thanks for your reply. I can see that the options in Jicofo are here:
https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/JitsiMeetConfig.java
. Are all options in config.js automatically passed here?

No, only config.deploymentInfo.userRegion is passed to jicofo as a "region"
element.

Boris

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


#6

What I was thinking that nginx has information about the ip address of
the client(public one) and can pre-fill it in config.js (some how ...
) and the client can re-send it to jicofo so you can have it there
make your logic ...

···

On Mon, Jan 15, 2018 at 9:14 PM, Damian Minkov <damencho@jitsi.org> wrote:

Sorry Markus, I thought all of that goes back to jicofo ...

On Mon, Jan 15, 2018 at 8:12 PM, Boris Grozev <boris@jitsi.org> wrote:

On 15/01/2018 07:50, markus.kullberg@teliacompany.com wrote:

Hello,

Thanks for your reply. I can see that the options in Jicofo are here:
https://github.com/jitsi/jicofo/blob/master/src/main/java/org/jitsi/jicofo/JitsiMeetConfig.java
. Are all options in config.js automatically passed here?

No, only config.deploymentInfo.userRegion is passed to jicofo as a "region"
element.

Boris

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


#7

That's exactly what we do (with Server Side Includes).

Boris

···

On 15/01/2018 21:16, Damian Minkov wrote:

What I was thinking that nginx has information about the ip address of
the client(public one) and can pre-fill it in config.js (some how ...
) and the client can re-send it to jicofo so you can have it there
make your logic ...


#8

Oops, my bad. I thought I was replying to Markus...

···

On 15/01/2018 21:32, Boris Grozev wrote:

On 15/01/2018 21:16, Damian Minkov wrote:

What I was thinking that nginx has information about the ip address of
the client(public one) and can pre-fill it in config.js (some how ...
) and the client can re-send it to jicofo so you can have it there
make your logic ...

That's exactly what we do (with Server Side Includes).