Troubleshooting a Virtual Studio Device (VSD)

[JS]

One of the VSDs we sent out to remote locations is having trouble getting a connection to our server. With all the correct cables hooked up, as verified via video call, status and ethernet lights are all lit up as expected. However, neither http://jacktrip.local on a PC in the same local network yield anything, nor is the device showing up on http://app.jacktrip.org.

I shall be doing some troubleshooting over the internet soon via remote controlling one of the PCs on the same network. What are the steps or points to troubleshoot? I can think of:

1. If I'm in touch, manage to log into site's network switch / router
2. Check the router's port forwarding or restrictions (but what to look for?)
   
3. Try finding the IP of the VSD on the router's DHCP client list
4. SSH into the VSD via the IP
5. Then what?

Any pointers would be much appreciated. Thanks.

[Synthia Cynthia Payne]

recently supported a few similar issues:
one was just a bad ethernet cable,
one was a dead port on the router.

to see if the VS is getting on the network you can use a bonjour browser
on windows, aka 'discovery' for mac, from
http://hobbyistsoftware.com/bonjourbrowser

regarding port forwarding - you wouldn't just check, you would need to
set it up. Do an online search for "port forwarding instructions" +brand
and model of your router. Also check "port forwarding instructions" +ISP.

just for starters. hope it helps.

synthia

On 5/31/2021 9:34 AM, JS wrote:
> One of the VSDs we sent out to remote locations is having trouble
> getting a connection to our server. With all the correct cables hooked
> up, as verified via video call, status and ethernet lights are all lit
> up as expected. However, neither http://jacktrip.local on a PC in the
> same local network yield anything, nor is the device showing up on
> http://app.jacktrip.org.
>
> I shall be doing some troubleshooting over the internet soon via remote
> controlling one of the PCs on the same network. What are the steps or
> points to troubleshoot? I can think of:
>

> 1. If I'm in touch, manage to log into site's network switch / router
> 2. Check the router's port forwarding or restrictions (but what to look
> for?)
> 3. Try finding the IP of the VSD on the router's DHCP client list
> 4. SSH into the VSD via the IP
> 5. Then what?

>
> Any pointers would be much appreciated. Thanks.
>

> --
> You received this message because you are subscribed to the Google
> Groups "jacktrip-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jacktrip-user...@googlegroups.com
> <mailto:jacktrip-user...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com
> <https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Dave Adams]

One slight expansion on Synthia's excellent pointer on MDNS (aka Bonjour  or whatever): ASSUMING you can find the VSD IP address on the switch/router, http to THAT.  I had one user on an old enough Windows that MDNS was just NOT going to work.  This got us going.

If you  don't see the VSD ip address in the switch/router admin screens, it could be something like a port mis-match.  For instance, I have chased problems and ended up finding that the user plugged into the WAN port instead of a LAN port.  Likewise, a user got too clever for our own good and did some port sharing and sub-netting.  Never had EITHER of these with my JackTrip friends.  I think I only have one JacTripper who knows how to do that kind of thing, and he very much does not want to.  Says he retired from all that :)

I suspect MDNS, like Synthia. Using http direct to the VSD IP address is likely you best work around.  If MDNS is forbidden inside the LAN on the switch/router, you probably don't want to mess with the users firewall rules.  If the MDNS is missing from the user's version of Windows, it might be more pain than it's worth to try to retrofit it.

Good luck!

[Synthia Cynthia Payne]

On Bonjour or Discovery, it will say "Jacktrip Agent" I will send a
screenshot later.
synth

> > http://app.jacktrip.org <http://app.jacktrip.org>.

> >
> > I shall be doing some troubleshooting over the internet soon via
> remote
> > controlling one of the PCs on the same network. What are the
> steps or
> > points to troubleshoot? I can think of:
> >
> > 1. If I'm in touch, manage to log into site's network switch /
> router
> > 2. Check the router's port forwarding or restrictions (but what
> to look
> > for?)
> > 3. Try finding the IP of the VSD on the router's DHCP client list
> > 4. SSH into the VSD via the IP
> > 5. Then what?
> >
> > Any pointers would be much appreciated. Thanks.
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "jacktrip-users" group.
> > To unsubscribe from this group and stop receiving emails from it,
> send
> > an email to jacktrip-user...@googlegroups.com
> > <mailto:jacktrip-user...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com
> <https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com>
>
> >

> <https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com?utm_medium=email&utm_source=footer
> <https://groups.google.com/d/msgid/jacktrip-users/033a30f0-3471-4648-9c88-836529e0141fn%40googlegroups.com?utm_medium=email&utm_source=footer>>.

>
>
> --
> You received this message because you are subscribed to the Google
> Groups "jacktrip-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jacktrip-user...@googlegroups.com
> <mailto:jacktrip-user...@googlegroups.com>.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jacktrip-users/d7bfa0e5-112b-466e-b585-ae31cf138c4an%40googlegroups.com
> <https://groups.google.com/d/msgid/jacktrip-users/d7bfa0e5-112b-466e-b585-ae31cf138c4an%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Sandy Goldfless]

On connecting for registration:  I see that my router has indeed given an IP address to my RPi4 (with jacktrip image purchased on Amazon this week), but I still can't connect to register it, neither with direct http from another wired device on same router nor with bluetooth  using Bluefaro, as suggested on jacktrip.org's "Troubleshooting Device Registration" page: Bluefaro does not see any Physical Web beacons from the RPi4.  (In fact. I've tried every one of the 10 suggestions on that page, no luck.)

Could it be that a sound card has to be connected before mDNS or bluetooth beaconing or any connectivity is allowed?

Is it necessary to find the version id of my jacktrip image before proceeding any further?  If so, how does one do that?

BTW, I've been using jacktrip on an RPi4 from NetworkSound and with MTA's cloud-based server for six months now; it's been a great experience. Just eager now to try a VS server.

[Robert Holland]

Hi Sandy,

Yes - a compatible sound card must be connected and detected by the firmware before you can connect and register. Make sure you're using the current image file (14th Feb 2021) which supports a much wider range of audio interfaces....

https://help.jacktrip.org/hc/en-us/articles/360055205313-Virtual-Studio-Image-for-Raspberry-Pi

HTH

To unsubscribe from this group and stop receiving emails from it, send an email to jacktrip-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacktrip-users/9a6746cf-dd90-4c5f-9329-c3251dc75916n%40googlegroups.com.

--

Robert E B Holland

[Sandy Goldfless]

Excellent. Thank you, Robert.

[JS]

Thank you so much for all the help. As it turns out, the internet service provider supplies a router that is more locked down than I have ever come across in my life. You can't even ping it, let alone connecting to it to configure it's NAT etc. So, we gave up and just asked him to connect from another location which worked immediately.

Nevertheless, this has been a huge learning experience and I am very grateful for all your help!