deleted
Thanks, Keith. We will have to wait until tomorrow because I have to go now. But thank you very much for your help, it's very much appreciated
Correction.
Its port 554 not 123, that you need to forward.
@Ironside wrote:
Thanks, Keith. We will have to wait until tomorrow because I have to go now. But thank you very much for your help, it's very much appreciated
Yes I am off to bed now. But its the RTSP port 554 that needs to be forwarded. You also need to remove the login and password details from your YouTube video.
If you want the feed to be public, then you would have to remove the login details, and just leave the stream as open access.
If that is done, then you should be able to view the stream without having to add the login name and password to the url that you pass to media player.
I don't know how I would even manipulate the address or take out the password and username..
@Ironside wrote:
I don't know how I would even manipulate the address or take out the password and username..
Not sure. All I am sure of is that you would have to forward the RTSP stream on port 554.
At some point you must have entered some login details that are needed to access the stream, because it shows on your YouTube video very quickly.

That shows the stream url, which is very similar to the format that Blue Iris has for your camera.

This is why I think you need to forward port 554.
It could be that company that is going to display your stream, will need this login info.
What would be worth me trying, as an experiment, is to see if I can add your camera to Blue Iris, once you forward that port.
I already have RTSP cameras on my system, like this one.

If I can see the camera, then there is a good chance that your camera hosting service can see it.
Anyway, its something to try, perhaps over the weekend if you have time.
You can see the video within your own network at the moment, but if you want to stream it over the Internet, then the port needs to be forwarded. I cannot see it working any other way, as all you have forwarded at the moment, is the discovery port, which is only there to determine the camera capabilities, and may not actually be needed.
I have ten different cameras, four outside, and six monitoring other processes.
Hi Keith, yes, that would be great. Let me read what you've said and I will get back to you. Just wanted to let you know that I am still here eagerly hoping we can sort this issue out. Mind you, Camsecure are not being particularly helpful. It's getting to the point where I feel like I am being a nuisance by keep emailing them asking if they have tried the new settings. I'm the one who's paying them to host the camera 🙂 🙂
Take a look,
I will be around later on today,
Not sure why you need to use Camsecure, as you are serving the video from your own network. You really need to be in the position where I can see your camera on Blue Iris.
You would not have to pay anyone to host your camera.
In fact, if you have a PC which is running all of the time, then its a much better option to use Blue Iris, as you have full control over the connection stream, and it does the conversion from RTSP, to many different formats, and you can insert a link into a web page.
If I can get your stream onto Blue Iris, then I will give you a link back from its internal web server, so you can view the video. I am only on ADSL, so the bandwidth it s a bit limited.
The problem in inserting a RTSP link into a page, is that not all web browsers can display the video. I would imaging that Camsecure is doing something like Blue Iris does, but running it on a cloud application.