[SIP Beyond VoIP] Conference Screen Sharing/Video - 488 Not Acceptable Here
mail at jsteel.org
Mon Jul 17 22:24:50 CEST 2017
OK thanks for the info. I assumed because the same option "Share screen"
(or similar) was available in Blink when connected to a conference that it
should work just the same as it does with p2p.
I'm not really interested in video, it was mainly the screen sharing I was
hoping to find a solution for for Linux and Windows users. If there is
something else worth trying to accomplish screen sharing with multiple
people at once, I'd be interested to hear your suggestions.
Otherwise, thanks for the clarification.
On Mon 17 Jul 2017 at 17:43, Adrian Georgescu wrote:
> > On 17 Jul 2017, at 16:02, Jonathan Steel <mail at jsteel.org> wrote:
> > Thanks for your reply. Sure, a point in the right direction or to
> > learn more about how this all works is great. I wasn't expecting this
> > to be a simple answer/fix!
> > 1. I believe I needed to run MSRP to get screen sharing working. If I
> > stop MSRP I'm no longer able to do IM/text OR screen sharing.
> For p2p screensharing Blink uses MSRP. But SylkServer conference has no such support. There is no multi-party VNC sharing feature in either
> > 2. I believe the screen sharing is using VNC, not WebRTC. At least I'm
> > using Blink for the client software, not a web browser. If I uninstall
> > x11vnc it breaks the screen sharing; confirmation that it is VNC-based.
> > 4. I'm running this for clients internally, so I don't believe I need
> > a public IP address.
> Maybe it works.
> > Does that answer your points sufficiently? Does it shed any light on
> > my issue?
> Still not sure what do you want to accomplish. I can guess but I may be wrong:
> Multi party screensharing works with Blink for Mac only and is using streaming jpegs over Http. Client can be Blink or a web browser
> Videconference is possible using WebRTC tech either a web browser or SylkClient
> > Thanks,
> > --
> > Jonathan
> >> On 2017-07-17 14:42, Adrian Georgescu wrote:
> >> Hard to make a single answer for your compkex question. I will give
> >> you some clues to improve navigating the software.
> >> 1. MSRP is used for a text chat room
> >> 2. Video room uses WebRTC (no SIP or MSRP protocols involved)
> >> 3. The two above are disjunct worlds
> >> 4. SylkServer must use a public IP
> >> 5. You don't need an MSRP relay in combination with SylkServer as long
> >> as you stick with point 4
> >> Adrian
> >>> On 17 Jul 2017, at 14:37, Jonathan Steel <mail at jsteel.org> wrote:
> >>> I've just set up a basic install of OpenSIPS and SylkServer and everything
> >>> is working apart from screen sharing and video in a conference. It works OK
> >>> one to one (via OpenSIPS not through SylkServer). To confirm, audio and IM
> >>> work fine in a conference through SylkServer.
> >>> Here's an error from the SylkServer that I think is relevant:
> >>> https://bpaste.net/show/fdd1233513d9
> >>> (488 Not Acceptable Here)
> >>> My setup is as follows:
> >>> OpenSIPS + MSRPRelay:
> >>> sip.dev.lan
> >>> 10.74.6.250
> >>> SylkServer:
> >>> meet.sip.dev.lan
> >>> 10.74.6.251
> >>> Client:
> >>> Blink
> >>> 10.74.11.137
> >>> Does SylkServer run its own MSRPRelay and does it need to be configured
> >>> to use the one on the OpenSIPS server instead? Otherwise what do you
> >>> think I'm missing?
> >>> Thanks,
> >>> --
> >>> Jonathan
More information about the SIPBeyondVoIP