[jitsi-users] Using Lib Jitsi Meet Query


#1

Hi team,

I have setup jist-meet on a server which installed videoBridge, focus,
prosody and meet. It works fine and I am able to use it.

Now I want to use lib-jitsi-meet to make my own GUI. Basically I want to
have a video conference integrated into my pre-existing web. So I don't
want a separate tab for video conference but I want it to be handled inside
my current web as a component or a div worst case in an iframe.

I tried to run this example (
https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example) on apache
but it gives scope error:

Error:
XMLHttpRequest cannot load https://some-domain/http-bind.
Response to preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'https://localhost:9443' is therefore not allowed access.

It makes sense as VideoBridge is hosting 443 port and serving jitsi meet on
remote server, and I am trying to connect it from my local machine. How can
I host my own app using JitsiVideobridge back-end. Or how can I decouple it
to an external web app averaging lib-jitsi-meet.

Need some directions from community. Thanks in advance.

BR,
Jade


#2

Hi,

Reference to above, I found apache configs in jitsi-meet docs, does that
mean that we have to disable videoBridge running on 443 through
/etc/jitsi/videobridge/sip-communicator.properties ?

But the question of creating custom GUI using lib-jitsi-meet inside your
external website is still not clear. Can someone please clarify. Thanks

BR,
Jade

···

On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> wrote:

Hi team,

I have setup jist-meet on a server which installed videoBridge, focus,
prosody and meet. It works fine and I am able to use it.

Now I want to use lib-jitsi-meet to make my own GUI. Basically I want to
have a video conference integrated into my pre-existing web. So I don't
want a separate tab for video conference but I want it to be handled inside
my current web as a component or a div worst case in an iframe.

I tried to run this example (https://github.com/jitsi/lib-
jitsi-meet/tree/master/doc/example) on apache but it gives scope error:

Error:
XMLHttpRequest cannot load https://some-domain/http-bind.
Response to preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'https://localhost:9443' is therefore not allowed access.

It makes sense as VideoBridge is hosting 443 port and serving jitsi meet
on remote server, and I am trying to connect it from my local machine. How
can I host my own app using JitsiVideobridge back-end. Or how can I
decouple it to an external web app averaging lib-jitsi-meet.

Need some directions from community. Thanks in advance.

BR,
Jade


#3

Hi,

So by default if java8 is available, jitsi-meet is installed with jvb
configured to serve meet. This is done so by default if everything is
on one machine you can still use port 443 for jvb media (some
corporate networks disable any tcp than 80 and 443 and no udp, in this
case only media using 443 will work).
But when installing jitsi-meet there is a nginx or apache installed,
that web server is configured to serve meet (the docs you have found
are just templates for those configs). In that case if web server and
jvb are on same machine, jvb will use port 4443 for tcp media. This
can be changed by adding a second ip address to the machine and using
that for jvb, or by moving jvb to another machine.
For your case currently, you will need to use some web server cause
those headers cannot be currently set in jvb, but it is a reasonable
use case and I will make sure we include this change in our roadmap.
In order to move your deployment to another webserver, there are two
options, purge everything jitsi releated and install the webserver
nginx/apache and then install jitsi-meet. Or the second option is to
config the webserver yourself and remove the
sip-communicator.properties files of jvb (which will remove its config
to serve meet).
Generally all the logic in configuring one or another thing is here:
https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-web-config.postinst

Hope this helps.

Regards
damencho

···

On Mon, Jan 16, 2017 at 5:37 AM, Jade SZ <jitterbuffer@gmail.com> wrote:

Hi,

Reference to above, I found apache configs in jitsi-meet docs, does that
mean that we have to disable videoBridge running on 443 through
/etc/jitsi/videobridge/sip-communicator.properties ?

But the question of creating custom GUI using lib-jitsi-meet inside your
external website is still not clear. Can someone please clarify. Thanks

BR,
Jade

On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> wrote:

Hi team,

I have setup jist-meet on a server which installed videoBridge, focus,
prosody and meet. It works fine and I am able to use it.

Now I want to use lib-jitsi-meet to make my own GUI. Basically I want to
have a video conference integrated into my pre-existing web. So I don't want
a separate tab for video conference but I want it to be handled inside my
current web as a component or a div worst case in an iframe.

I tried to run this example
(https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example) on apache
but it gives scope error:

Error:
XMLHttpRequest cannot load https://some-domain/http-bind.
Response to preflight request doesn't pass access control check: No
'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'https://localhost:9443' is therefore not allowed access.

It makes sense as VideoBridge is hosting 443 port and serving jitsi meet
on remote server, and I am trying to connect it from my local machine. How
can I host my own app using JitsiVideobridge back-end. Or how can I decouple
it to an external web app averaging lib-jitsi-meet.

Need some directions from community. Thanks in advance.

BR,
Jade

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


#4

Hi Damencho,

Thanks for the detailed reply. I'll try with configuring web-server and
moving sip-communicator.properties. My other question regarding
lib-jitsi-meet is not clear though, forgive my ignorance.

So Lets say I have some website on server-2 and server-1 has
videoBridge/Jicofo/prosody installed. I want to use lib-jitsi-meet in
server-1 website, not jitsi-meet but lib-jitsi-meet to create and integrate
custom UI in some website. Also I do not want to open a new tab with
domain/conference-nam for each participant instead I want to have a GUI
which can be executed inside that web app. (correct me If I am not
explaining it well). Thanks

BR,
Jade

···

On Mon, Jan 16, 2017 at 6:53 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

So by default if java8 is available, jitsi-meet is installed with jvb
configured to serve meet. This is done so by default if everything is
on one machine you can still use port 443 for jvb media (some
corporate networks disable any tcp than 80 and 443 and no udp, in this
case only media using 443 will work).
But when installing jitsi-meet there is a nginx or apache installed,
that web server is configured to serve meet (the docs you have found
are just templates for those configs). In that case if web server and
jvb are on same machine, jvb will use port 4443 for tcp media. This
can be changed by adding a second ip address to the machine and using
that for jvb, or by moving jvb to another machine.
For your case currently, you will need to use some web server cause
those headers cannot be currently set in jvb, but it is a reasonable
use case and I will make sure we include this change in our roadmap.
In order to move your deployment to another webserver, there are two
options, purge everything jitsi releated and install the webserver
nginx/apache and then install jitsi-meet. Or the second option is to
config the webserver yourself and remove the
sip-communicator.properties files of jvb (which will remove its config
to serve meet).
Generally all the logic in configuring one or another thing is here:
https://github.com/jitsi/jitsi-meet/blob/master/debian/
jitsi-meet-web-config.postinst

Hope this helps.

Regards
damencho

On Mon, Jan 16, 2017 at 5:37 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi,
>
> Reference to above, I found apache configs in jitsi-meet docs, does that
> mean that we have to disable videoBridge running on 443 through
> /etc/jitsi/videobridge/sip-communicator.properties ?
>
> But the question of creating custom GUI using lib-jitsi-meet inside your
> external website is still not clear. Can someone please clarify. Thanks
>
>
>
> BR,
> Jade
>
>
> On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> wrote:
>>
>> Hi team,
>>
>> I have setup jist-meet on a server which installed videoBridge, focus,
>> prosody and meet. It works fine and I am able to use it.
>>
>> Now I want to use lib-jitsi-meet to make my own GUI. Basically I want to
>> have a video conference integrated into my pre-existing web. So I don't
want
>> a separate tab for video conference but I want it to be handled inside
my
>> current web as a component or a div worst case in an iframe.
>>
>> I tried to run this example
>> (https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example) on
apache
>> but it gives scope error:
>>
>> Error:
>> XMLHttpRequest cannot load https://some-domain/http-bind.
>> Response to preflight request doesn't pass access control check: No
>> 'Access-Control-Allow-Origin' header is present on the requested
resource.
>> Origin 'https://localhost:9443' is therefore not allowed access.
>>
>> It makes sense as VideoBridge is hosting 443 port and serving jitsi meet
>> on remote server, and I am trying to connect it from my local machine.
How
>> can I host my own app using JitsiVideobridge back-end. Or how can I
decouple
>> it to an external web app averaging lib-jitsi-meet.
>>
>> Need some directions from community. Thanks in advance.
>>
>>
>> BR,
>> Jade
>>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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


#5

Hi,

Hi Damencho,

Thanks for the detailed reply. I'll try with configuring web-server and
moving sip-communicator.properties. My other question regarding
lib-jitsi-meet is not clear though, forgive my ignorance.

So Lets say I have some website on server-2 and server-1 has
videoBridge/Jicofo/prosody installed. I want to use lib-jitsi-meet in
server-1 website, not jitsi-meet but lib-jitsi-meet to create and integrate
custom UI in some website. Also I do not want to open a new tab with
domain/conference-nam for each participant instead I want to have a GUI
which can be executed inside that web app. (correct me If I am not
explaining it well). Thanks

Yep, this is perfectly fine. Then in the website that is served from
server2 you will source the library pointed to server1. This way when
you update components they will also update the jitsi-meet and
corresponding lib-jitsi-meet.
Currently jitsi-meet is sourcing the library from different location
and using it:
<script src="https://…some-server…/libs/lib-jitsi-meet.min.js?v=1592"></script>
so you have a working example to build your own:)

Regards
damencho

···

On Mon, Jan 16, 2017 at 8:17 AM, Jade SZ <jitterbuffer@gmail.com> wrote:

BR,
Jade

On Mon, Jan 16, 2017 at 6:53 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

So by default if java8 is available, jitsi-meet is installed with jvb
configured to serve meet. This is done so by default if everything is
on one machine you can still use port 443 for jvb media (some
corporate networks disable any tcp than 80 and 443 and no udp, in this
case only media using 443 will work).
But when installing jitsi-meet there is a nginx or apache installed,
that web server is configured to serve meet (the docs you have found
are just templates for those configs). In that case if web server and
jvb are on same machine, jvb will use port 4443 for tcp media. This
can be changed by adding a second ip address to the machine and using
that for jvb, or by moving jvb to another machine.
For your case currently, you will need to use some web server cause
those headers cannot be currently set in jvb, but it is a reasonable
use case and I will make sure we include this change in our roadmap.
In order to move your deployment to another webserver, there are two
options, purge everything jitsi releated and install the webserver
nginx/apache and then install jitsi-meet. Or the second option is to
config the webserver yourself and remove the
sip-communicator.properties files of jvb (which will remove its config
to serve meet).
Generally all the logic in configuring one or another thing is here:

https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi-meet-web-config.postinst

Hope this helps.

Regards
damencho

On Mon, Jan 16, 2017 at 5:37 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi,
>
> Reference to above, I found apache configs in jitsi-meet docs, does that
> mean that we have to disable videoBridge running on 443 through
> /etc/jitsi/videobridge/sip-communicator.properties ?
>
> But the question of creating custom GUI using lib-jitsi-meet inside your
> external website is still not clear. Can someone please clarify. Thanks
>
>
>
> BR,
> Jade
>
>
> On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> wrote:
>>
>> Hi team,
>>
>> I have setup jist-meet on a server which installed videoBridge, focus,
>> prosody and meet. It works fine and I am able to use it.
>>
>> Now I want to use lib-jitsi-meet to make my own GUI. Basically I want
>> to
>> have a video conference integrated into my pre-existing web. So I don't
>> want
>> a separate tab for video conference but I want it to be handled inside
>> my
>> current web as a component or a div worst case in an iframe.
>>
>> I tried to run this example
>> (https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example) on
>> apache
>> but it gives scope error:
>>
>> Error:
>> XMLHttpRequest cannot load https://some-domain/http-bind.
>> Response to preflight request doesn't pass access control check: No
>> 'Access-Control-Allow-Origin' header is present on the requested
>> resource.
>> Origin 'https://localhost:9443' is therefore not allowed access.
>>
>> It makes sense as VideoBridge is hosting 443 port and serving jitsi
>> meet
>> on remote server, and I am trying to connect it from my local machine.
>> How
>> can I host my own app using JitsiVideobridge back-end. Or how can I
>> decouple
>> it to an external web app averaging lib-jitsi-meet.
>>
>> Need some directions from community. Thanks in advance.
>>
>>
>> BR,
>> Jade
>>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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

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


#6

Hi Damencho,

I purged the components and installed it with apache, had couple of issues
but jitsi-meet works now all in same server say *server1*.

Now I have *server2* totally unrelated having it's own apache sever, and
hosting lib-jitsi-meet-example (
https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example), it's
index.html file is sourcing lib-jitsi-meet from sever1 i.e.

    <script src="https://server1
-domain/libs/lib-jitsi-meet.min.js?v=1592"></script>

Also example.js on sever2 using options from server1 jitsi-meet config:

var options = {
    hosts: {
        domain: 'server1-domain',
        muc: 'conference.server1-domain', // FIXME: use XEP-0030
    },
    bosh: '//server1-domain/http-bind', // FIXME: use xep-0156 for that
    clientNode: 'http://jitsi.org/jitsimeet', // The name of client node
advertised in XEP-0115 'c' stanza
};

*Issue:*

When open the https://server2-domain/example, i get the following COR error:

*Error:*

*XMLHttpRequest cannot load https://server1-domain/http-bind
<https://server1-domain/http-bind>. Request header field Content-Type is
not allowed by Access-Control-Allow-Headers in preflight response.*

Now reading on how prosody/apache uses proxy for http-bind and allowing all:

  <Location /http-bind>
      Order allow,deny
      Allow from all
   </Location>
   RewriteEngine On
   RewriteRule ^/http-bind$ http://example.com:5280/http-bind [P,L]

I tried above as well as what we get in default apache template but,
Server2 is unable to run lib-jitsi-meet example.

Need some pointers, should current lib-jitis-meet-EXAMPLE work?

BR,
Jade

···

On Mon, Jan 16, 2017 at 8:32 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Mon, Jan 16, 2017 at 8:17 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi Damencho,
>
> Thanks for the detailed reply. I'll try with configuring web-server and
> moving sip-communicator.properties. My other question regarding
> lib-jitsi-meet is not clear though, forgive my ignorance.
>
> So Lets say I have some website on server-2 and server-1 has
> videoBridge/Jicofo/prosody installed. I want to use lib-jitsi-meet in
> server-1 website, not jitsi-meet but lib-jitsi-meet to create and
integrate
> custom UI in some website. Also I do not want to open a new tab with
> domain/conference-nam for each participant instead I want to have a GUI
> which can be executed inside that web app. (correct me If I am not
> explaining it well). Thanks

Yep, this is perfectly fine. Then in the website that is served from
server2 you will source the library pointed to server1. This way when
you update components they will also update the jitsi-meet and
corresponding lib-jitsi-meet.
Currently jitsi-meet is sourcing the library from different location
and using it:
<script src="https://…some-server…/libs/lib-jitsi-meet.min.js?v=
1592"></script>
so you have a working example to build your own:)

Regards
damencho

>
>
> BR,
> Jade
>
>
> On Mon, Jan 16, 2017 at 6:53 PM, Damian Minkov <damencho@jitsi.org> > wrote:
>>
>> Hi,
>>
>> So by default if java8 is available, jitsi-meet is installed with jvb
>> configured to serve meet. This is done so by default if everything is
>> on one machine you can still use port 443 for jvb media (some
>> corporate networks disable any tcp than 80 and 443 and no udp, in this
>> case only media using 443 will work).
>> But when installing jitsi-meet there is a nginx or apache installed,
>> that web server is configured to serve meet (the docs you have found
>> are just templates for those configs). In that case if web server and
>> jvb are on same machine, jvb will use port 4443 for tcp media. This
>> can be changed by adding a second ip address to the machine and using
>> that for jvb, or by moving jvb to another machine.
>> For your case currently, you will need to use some web server cause
>> those headers cannot be currently set in jvb, but it is a reasonable
>> use case and I will make sure we include this change in our roadmap.
>> In order to move your deployment to another webserver, there are two
>> options, purge everything jitsi releated and install the webserver
>> nginx/apache and then install jitsi-meet. Or the second option is to
>> config the webserver yourself and remove the
>> sip-communicator.properties files of jvb (which will remove its config
>> to serve meet).
>> Generally all the logic in configuring one or another thing is here:
>>
>> https://github.com/jitsi/jitsi-meet/blob/master/debian/
jitsi-meet-web-config.postinst
>>
>> Hope this helps.
>>
>> Regards
>> damencho
>>
>>
>> On Mon, Jan 16, 2017 at 5:37 AM, Jade SZ <jitterbuffer@gmail.com> > wrote:
>> > Hi,
>> >
>> > Reference to above, I found apache configs in jitsi-meet docs, does
that
>> > mean that we have to disable videoBridge running on 443 through
>> > /etc/jitsi/videobridge/sip-communicator.properties ?
>> >
>> > But the question of creating custom GUI using lib-jitsi-meet inside
your
>> > external website is still not clear. Can someone please clarify.
Thanks
>> >
>> >
>> >
>> > BR,
>> > Jade
>> >
>> >
>> > On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> > wrote:
>> >>
>> >> Hi team,
>> >>
>> >> I have setup jist-meet on a server which installed videoBridge,
focus,
>> >> prosody and meet. It works fine and I am able to use it.
>> >>
>> >> Now I want to use lib-jitsi-meet to make my own GUI. Basically I want
>> >> to
>> >> have a video conference integrated into my pre-existing web. So I
don't
>> >> want
>> >> a separate tab for video conference but I want it to be handled
inside
>> >> my
>> >> current web as a component or a div worst case in an iframe.
>> >>
>> >> I tried to run this example
>> >> (https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example) on
>> >> apache
>> >> but it gives scope error:
>> >>
>> >> Error:
>> >> XMLHttpRequest cannot load https://some-domain/http-bind.
>> >> Response to preflight request doesn't pass access control check: No
>> >> 'Access-Control-Allow-Origin' header is present on the requested
>> >> resource.
>> >> Origin 'https://localhost:9443' is therefore not allowed access.
>> >>
>> >> It makes sense as VideoBridge is hosting 443 port and serving jitsi
>> >> meet
>> >> on remote server, and I am trying to connect it from my local
machine.
>> >> How
>> >> can I host my own app using JitsiVideobridge back-end. Or how can I
>> >> decouple
>> >> it to an external web app averaging lib-jitsi-meet.
>> >>
>> >> Need some directions from community. Thanks in advance.
>> >>
>> >>
>> >> BR,
>> >> Jade
>> >>
>> >
>> >
>> > _______________________________________________
>> > users mailing list
>> > users@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/users
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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


#7

Got it resolved, it was my apache config issue.

Thanks

···

On Sun, Jan 22, 2017 at 4:41 PM, Jade SZ <jitterbuffer@gmail.com> wrote:

Hi Damencho,

I purged the components and installed it with apache, had couple of issues
but jitsi-meet works now all in same server say *server1*.

Now I have *server2* totally unrelated having it's own apache sever, and
hosting lib-jitsi-meet-example (https://github.com/jitsi/lib-
jitsi-meet/tree/master/doc/example), it's index.html file is sourcing
lib-jitsi-meet from sever1 i.e.

    <script src="https://server1-domain/libs/lib-jitsi-meet.min.js?v=
1592"></script>

Also example.js on sever2 using options from server1 jitsi-meet config:

var options = {
    hosts: {
        domain: 'server1-domain',
        muc: 'conference.server1-domain', // FIXME: use XEP-0030
    },
    bosh: '//server1-domain/http-bind', // FIXME: use xep-0156 for that
    clientNode: 'http://jitsi.org/jitsimeet', // The name of client node
advertised in XEP-0115 'c' stanza
};

*Issue:*

When open the https://server2-domain/example, i get the following COR
error:

*Error:*

*XMLHttpRequest cannot load https://server1-domain/http-bind
<https://server1-domain/http-bind>. Request header field Content-Type is
not allowed by Access-Control-Allow-Headers in preflight response.*

Now reading on how prosody/apache uses proxy for http-bind and allowing
all:

  <Location /http-bind>
      Order allow,deny
      Allow from all
   </Location>
   RewriteEngine On
   RewriteRule ^/http-bind$ http://example.com:5280/http-bind [P,L]

I tried above as well as what we get in default apache template but,
Server2 is unable to run lib-jitsi-meet example.

Need some pointers, should current lib-jitis-meet-EXAMPLE work?

BR,
Jade

On Mon, Jan 16, 2017 at 8:32 PM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

On Mon, Jan 16, 2017 at 8:17 AM, Jade SZ <jitterbuffer@gmail.com> wrote:
> Hi Damencho,
>
> Thanks for the detailed reply. I'll try with configuring web-server and
> moving sip-communicator.properties. My other question regarding
> lib-jitsi-meet is not clear though, forgive my ignorance.
>
> So Lets say I have some website on server-2 and server-1 has
> videoBridge/Jicofo/prosody installed. I want to use lib-jitsi-meet in
> server-1 website, not jitsi-meet but lib-jitsi-meet to create and
integrate
> custom UI in some website. Also I do not want to open a new tab with
> domain/conference-nam for each participant instead I want to have a GUI
> which can be executed inside that web app. (correct me If I am not
> explaining it well). Thanks

Yep, this is perfectly fine. Then in the website that is served from
server2 you will source the library pointed to server1. This way when
you update components they will also update the jitsi-meet and
corresponding lib-jitsi-meet.
Currently jitsi-meet is sourcing the library from different location
and using it:
<script src="https://…some-server…/libs/lib-jitsi-meet.min.js?v=1
592"></script>
so you have a working example to build your own:)

Regards
damencho

>
>
> BR,
> Jade
>
>
> On Mon, Jan 16, 2017 at 6:53 PM, Damian Minkov <damencho@jitsi.org> >> wrote:
>>
>> Hi,
>>
>> So by default if java8 is available, jitsi-meet is installed with jvb
>> configured to serve meet. This is done so by default if everything is
>> on one machine you can still use port 443 for jvb media (some
>> corporate networks disable any tcp than 80 and 443 and no udp, in this
>> case only media using 443 will work).
>> But when installing jitsi-meet there is a nginx or apache installed,
>> that web server is configured to serve meet (the docs you have found
>> are just templates for those configs). In that case if web server and
>> jvb are on same machine, jvb will use port 4443 for tcp media. This
>> can be changed by adding a second ip address to the machine and using
>> that for jvb, or by moving jvb to another machine.
>> For your case currently, you will need to use some web server cause
>> those headers cannot be currently set in jvb, but it is a reasonable
>> use case and I will make sure we include this change in our roadmap.
>> In order to move your deployment to another webserver, there are two
>> options, purge everything jitsi releated and install the webserver
>> nginx/apache and then install jitsi-meet. Or the second option is to
>> config the webserver yourself and remove the
>> sip-communicator.properties files of jvb (which will remove its config
>> to serve meet).
>> Generally all the logic in configuring one or another thing is here:
>>
>> https://github.com/jitsi/jitsi-meet/blob/master/debian/jitsi
-meet-web-config.postinst
>>
>> Hope this helps.
>>
>> Regards
>> damencho
>>
>>
>> On Mon, Jan 16, 2017 at 5:37 AM, Jade SZ <jitterbuffer@gmail.com> >> wrote:
>> > Hi,
>> >
>> > Reference to above, I found apache configs in jitsi-meet docs, does
that
>> > mean that we have to disable videoBridge running on 443 through
>> > /etc/jitsi/videobridge/sip-communicator.properties ?
>> >
>> > But the question of creating custom GUI using lib-jitsi-meet inside
your
>> > external website is still not clear. Can someone please clarify.
Thanks
>> >
>> >
>> >
>> > BR,
>> > Jade
>> >
>> >
>> > On Mon, Jan 16, 2017 at 2:50 PM, Jade SZ <jitterbuffer@gmail.com> >> wrote:
>> >>
>> >> Hi team,
>> >>
>> >> I have setup jist-meet on a server which installed videoBridge,
focus,
>> >> prosody and meet. It works fine and I am able to use it.
>> >>
>> >> Now I want to use lib-jitsi-meet to make my own GUI. Basically I
want
>> >> to
>> >> have a video conference integrated into my pre-existing web. So I
don't
>> >> want
>> >> a separate tab for video conference but I want it to be handled
inside
>> >> my
>> >> current web as a component or a div worst case in an iframe.
>> >>
>> >> I tried to run this example
>> >> (https://github.com/jitsi/lib-jitsi-meet/tree/master/doc/example)
on
>> >> apache
>> >> but it gives scope error:
>> >>
>> >> Error:
>> >> XMLHttpRequest cannot load https://some-domain/http-bind.
>> >> Response to preflight request doesn't pass access control check: No
>> >> 'Access-Control-Allow-Origin' header is present on the requested
>> >> resource.
>> >> Origin 'https://localhost:9443' is therefore not allowed access.
>> >>
>> >> It makes sense as VideoBridge is hosting 443 port and serving jitsi
>> >> meet
>> >> on remote server, and I am trying to connect it from my local
machine.
>> >> How
>> >> can I host my own app using JitsiVideobridge back-end. Or how can I
>> >> decouple
>> >> it to an external web app averaging lib-jitsi-meet.
>> >>
>> >> Need some directions from community. Thanks in advance.
>> >>
>> >>
>> >> BR,
>> >> Jade
>> >>
>> >
>> >
>> > _______________________________________________
>> > users mailing list
>> > users@jitsi.org
>> > Unsubscribe instructions and other list options:
>> > http://lists.jitsi.org/mailman/listinfo/users
>>
>> _______________________________________________
>> users mailing list
>> users@jitsi.org
>> Unsubscribe instructions and other list options:
>> http://lists.jitsi.org/mailman/listinfo/users
>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

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