@maria

Hi Maria,

I just tested this on an iPhone X over a cellular connection and was able to logon without any trouble. What type of phone and what web browser are you using? I’ll try to test it on something similar to yours.

Thanks, Robert

@bill

If the Alexa devices are on a different LAN than the IP cameras, then that could be a problem. The Alexa devices make local connections to the IP cameras. If you have sophisticated routing on your LAN where you can allow the Alexa devices to connect to the IP cameras on a different LAN/VLAN/subnet, then it should work. However, yes you will need to put the correct host/address information in the Monocle web portal so that we send the appropriate RTSP URL address down to the Alexa devices when they request a stream.

One alternative could be to use our Monocle Gateway service which could act as a camera gateway if its running on a multi-homed system where it can communicate with the cameras and host an incoming interface that the Alexa devices can connect to.

Thanks, Robert

@spahwa

Just an update to this thread … we have a number of cameras that include mode=AAC-hbr in the SDP with no issues at all.

Example:

a=fmtp:97 streamtype=5;profile-level-id=1;mode=AAC-hbr;sizelength=13;indexlength=3;indexdeltalength=3;config=1588

@mdame

The current release of Monocle Gateway is generically compiled for newer ARM architecture such as in the RPi3B/3B+. Please open a support ticket via the link below and reference this forum topic and we can provide you an “untested” version compiled specifically for the Raspberry Pi.

https://monoclecam.com/contact

Thanks, Robert

@mamer999 said in No Access to Wansview Q3S:

Hello and thank you. Disabling audio was the solution.

Glad to hear that worked for the Q3S. I posted a compatibility note here:
https://forum.monoclecam.com/topic/127/wansview-compatibility-readme

Thanks, Robert

@cmjanus

Typically @tunnel works fine on most Reolink cameras. However, you can try @proxy to see if it helps. @proxy along with @hangup would ensure clean sessions on each Alexa request. @hangup does not have any impact when using @tunnel.

@Monkeycam

The Monocle Gateway is the newer replacement for the previous proxy server. Glad to hear its working without needing that. My Hikvision cameras work without needing it as well.

(PS, the Monocle Gateway would be needed if you were using a FireTV 4K or newer.)

@cferguson

When i click on the camera settings in monocle though it doesn’t seem to have a stored password. it is a series of aterisks that aren’t real. just let setting up a new camera it “seems” blank. Would that possibly be the cause? no stored password?

This is just a security/obfuscation technique. You password is stored and used at runtime, but we don’t reveal any details about it when viewing it on subsequent visits to the camera page.

If you have not already done so, can you open a support ticket? I think the next step would be for us to try accessing your camera stream from here and determine if we can get it working.

Thanks, Robert

Good deal. I have been in IT for over 20 years and have never heard of this. Ive never experienced it in my career. If you ever need any help with the project let me know. I have extensive knowledge of AWS and programming in general. I would be happy to help.

brian

OK, minor update to this thread …

I purchased this exact model:

FMUSER FBE200
https://amzn.to/2IyVHKb

alt text

I was able to get it working but it did require using the Monocle Gateway with the @proxy tag.

ff84ffce-94a6-44b9-9611-d69c693e27b8-image.png

Here are the encoder settings I am using with the “Main” stream:

58af1011-b2ac-477f-89cb-740ad052c9c5-image.png

I went back and re-tested my previous encoder:

J-Tech Digital H.264 Encoder
http://amzn.to/2H3lPJF

alt text

I was also able to finally get it working, but it also required using the Monocle Gateway with the @proxy tag. It also required setting the audio stream to “NONE”

626d5675-f5e4-4de6-9254-f1ce799e14ca-image.png

And here are the encoder settings I’m using on the main stream:

ee75f546-56d9-40d4-af9d-2667c0b5bcc7-image.png

@kwh561

Let’s stick with a direct connection to the Amcrest camera for testing. Every Amcrest camera I have worked with in the past seems to work fairly well with Alexa. You might want to make sure the camera’s firmware is up to date.

Also, please try these tips if you have not already. Often times a short display of video indicates that the Alexa device started to stream but then failed after getting some stream data it did not expect. Many times this is related to the audio stream:
https://monoclecam.com/troubleshoot/tips

I don’t have your exact camera model, but I do have it working fine on other Amcrest IP2M models such as IP2M-848EB and IP2M-841B.

If it still refuses to work, please post the log data from the Monocle Gateway while attempting to connect to the camera stream.

Thanks, Robert

Sorry for delay.
I try in few day to transmit logs.
Thx