cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
1,697 Views
Message 21 of 124

Re: IP camera


@Ironside wrote:

The company who are hosting the camera will give me some HTML code which I embed onto a page. This will then allow me to display the camera on a website.


What is the make and model of the camera?

0 Ratings
1,696 Views
Message 22 of 124

Re: IP camera

H264 HI3516EV200_85H30AI_S38

0 Ratings
1,692 Views
Message 23 of 124

Re: IP camera


@Ironside wrote:

H264 HI3516EV200_85H30AI_S38


This one http://www.golbong.com/download/Document/Manual/Manual-GOLBONG-Wireless-IP-Bird-Box-Camera-en.pdf

I assume that its actually turned on and connected at the moment?

Its very similar to the cameras I have outside.

0 Ratings
1,686 Views
Message 24 of 124

Re: IP camera

No, it's not that exact model, but it's basically the same as that one. All the settings are the same. And yes, it is switched on. In fact, I have **bleep** that has been sleeping in the box for the last week or so.2021.02.02 19-48-45.jpg

0 Ratings
1,679 Views
Message 25 of 124

Re: IP camera


@Ironside wrote:

No, it's not that exact model, but it's basically the same as that one. All the settings are the same. And yes, it is switched on. In fact, I have **bleep** that has been sleeping in the box for the last week or so.2021.02.02 19-48-45.jpg


Why I was asking, was because I use Blue Iris here, to monitor all of my camera feeds, and as an experiment, I tried to add the camera to the program, but it could not identify the location of the video stream.

I have a couple of ieGeek cameras which are H264, and have very similar interface, and these are the Blue Iris video settings.

Capture.JPG

Its the port information and video path bit that I think was missing, as this normally defines the stream. In my case, there are two streams, one HD and one SD.

As yours is a public viewable camera, I dis not enter any login details.

I was just interested to see if it was possible to view it remotely, otherwise its going to be difficult for you to do much.

The 8999 is only the discovery port. You need to forward the actual video feed port number, for it to be visible. I think that is where you are going wrong.

Look at the camera setting you use when you view the camera, which port are you displaying, as its that port that will also need to be forwarded to the Internet.

0 Ratings
1,672 Views
Message 26 of 124

Re: IP camera

I am sure its a simple problem to solve.

On your camera settings, the url would have to point to the actual video port, and not the auto discovery port of 8899, as that is only used by the viewer, to discover the connection type.

If you can access it via a web browser, then what port does the camera use? That is the port that you need to add to the port forwarding rules. The default would normally be port 80.

It should then be possible to view the camera on the web,

0 Ratings
1,662 Views
Message 27 of 124

Re: IP camera

Hopefully, all the settings I have given cam secure will allow them to get the camera live streaming online. It's worked for the last three years with no problems whatsoever. I just completely forgot how to set up the dynamic IP section and no IP.

0 Ratings
1,634 Views
Message 28 of 124

Re: IP camera

@Ironside 

Have you made any progress with this, as a doubt you will get it to work unless you forward the port which has the actual video stream on it.

All you have done is to open the automatic configuration stream on port 8899 which returns the configuration script to whatever display program is attempting to determine the camera properties.

What is missing, is the actual video stream. For example, the video stream on my ONVIF camera, is port 88. You need to determine what it is, as you must be able to view it on your computer, as you have shown a screen grab.

Once you know what port its on, then you need to add that to the port forwarding rules. That will enable a remote viewer to display that stream.

If I attempt to add your camera to Blue Iris, it can see the configuration port 8899, but it cannot find the port for the video.

At the moment, the only port that is open on your network, apart from the SDR, is port 8899. This is shown by Microsoft PortQuery.

Capture.JPG

 

0 Ratings
1,628 Views
Message 29 of 124

Re: IP camera

Yeah, I think I've got all the settings correct. I'm just waiting for Cam Secure to get the settings right on their side.

I can't post a link because this forum has obviously got some kind of system in place to stop rude words appearing. 

Anyway, you can probably work out what the word should be. It's a type of garden bird. t-i-t-s

http://brixham-blue-**bleep**.ddns.net:8899/

0 Ratings
1,616 Views
Message 30 of 124

Re: IP camera

I would be very surprised if that works, as you need more than one connection. If I cannot connect to it, then Cam Secure are not going to be able to. Its possible that the camera is opening other outgoing ports using UPnP, but that is not showing on your port forwarding screenshot.

All I can see on that website, is the configuration script.

That may work locally on your network, but it will not work from the Internet.

If you access that web address from another connection, like a mobile hotspot, all you will see is this script.

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2000/10/XMLSchema" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsa5="http://www.w3.org/2005/08/addressing" xmlns:xop="http://www.w3.org/2004/08/xop/include" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:tt="http://www.onvif.org/ver10/schema" xmlns:ns1="http://www.w3.org/2005/05/xmlmime" xmlns:wstop="http://docs.oasis-open.org/wsn/t-1" xmlns:ns7="http://docs.oasis-open.org/wsrf/r-2" xmlns:ns2="http://docs.oasis-open.org/wsrf/bf-2" xmlns:dndl="http://www.onvif.org/ver10/network/wsdl/DiscoveryLookupBinding" xmlns:dnrd="http://www.onvif.org/ver10/network/wsdl/RemoteDiscoveryBinding" xmlns:d="http://schemas.xmlsoap.org/ws/2005/04/discovery" xmlns:dn="http://www.onvif.org/ver10/network/wsdl" xmlns:ns10="http://www.onvif.org/ver10/replay/wsdl" xmlns:ns11="http://www.onvif.org/ver10/search/wsdl" xmlns:ns13="http://www.onvif.org/ver20/analytics/wsdl/RuleEngineBinding" xmlns:ns14="http://www.onvif.org/ver20/analytics/wsdl/AnalyticsEngineBinding" xmlns:tan="http://www.onvif.org/ver20/analytics/wsdl" xmlns:ns15="http://www.onvif.org/ver10/events/wsdl/PullPointSubscriptionBinding" xmlns:ns16="http://www.onvif.org/ver10/events/wsdl/EventBinding" xmlns:tev="http://www.onvif.org/ver10/events/wsdl" xmlns:ns17="http://www.onvif.org/ver10/events/wsdl/SubscriptionManagerBinding" xmlns:ns18="http://www.onvif.org/ver10/events/wsdl/NotificationProducerBinding" xmlns:ns19="http://www.onvif.org/ver10/events/wsdl/NotificationConsumerBinding" xmlns:ns20="http://www.onvif.org/ver10/events/wsdl/PullPointBinding" xmlns:ns21="http://www.onvif.org/ver10/events/wsdl/CreatePullPointBinding" xmlns:ns22="http://www.onvif.org/ver10/events/wsdl/PausableSubscriptionManagerBinding" xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2" xmlns:ns3="http://www.onvif.org/ver10/analyticsdevice/wsdl" xmlns:ns4="http://www.onvif.org/ver10/deviceIO/wsdl" xmlns:ns5="http://www.onvif.org/ver10/display/wsdl" xmlns:ns8="http://www.onvif.org/ver10/receiver/wsdl" xmlns:ns9="http://www.onvif.org/ver10/recording/wsdl" xmlns:tds="http://www.onvif.org/ver10/device/wsdl" xmlns:timg="http://www.onvif.org/ver20/imaging/wsdl" xmlns:tptz="http://www.onvif.org/ver20/ptz/wsdl" xmlns:trt="http://www.onvif.org/ver10/media/wsdl" xmlns:trt2="http://www.onvif.org/ver20/media/wsdl" xmlns:ter="http://www.onvif.org/ver10/error" xmlns:tns1="http://www.onvif.org/ver10/topics" xmlns:tnsn="http://www.eventextension.com/2011/event/topics">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>HTTP GET method not implemented</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Perhaps you could update this thread with progress. Thanks.

0 Ratings