Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: RTSP SERVER (Abhisek Techie)
   2. Re: RTSP SERVER (naza mantin)


----------------------------------------------------------------------

Message: 1
Date: Fri, 2 Aug 2019 22:08:10 +0530
From: Abhisek Techie <abhisek.study2...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] RTSP SERVER
Message-ID:
        <calvpzyulg8ehcqoemgmpyebzkvrr925zvmnridz1cr4nvnr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Naza,
Try configuring nginx webserver it supports rtsp and your clients can
connect to nginx  web server to get the feeds.

Regards

On Fri, 2 Aug 2019, 20:37 naza mantin, <naza.man...@gmail.com> wrote:

> Yes... absolutely sure on the push from the encoder.
>
> So, I am not a programmer and my knowledge on web socket is very limited.
> Can anybody help me and please tell me the Fees involve.
>
> My whatsapp > +962781327851
>
> On Fri, Aug 2, 2019 at 3:35 PM Ruslan Matveev <matveev.rus...@gmail.com>
> wrote:
>
>> If you're absolutely sure that your hardware can push rtsp stream, then
>> all you need is simple socket server which will be able from one side
>> accept rtsp stream from your cameras, and on the other side accept connects
>> from motion and forward all traffic from one side to another.
>>
>> ??, 2 ???. 2019 ?., 17:31 naza mantin <naza.man...@gmail.com>:
>>
>>> Dear Ruslan,
>>> Thanks for your reply. Sorry I don't quite understand>>> no access to
>>> them from outside the local network?
>>>
>>> What I mean is that the server can not "PULL" from the encoder.
>>> But the encoder can "PUSH" to the server.
>>>
>>> Thus, the server needs to have some kind of support and can accept RTMP
>>> "PUSH" from the encoder.
>>>
>>> I do hope the above is in order and look forward to your reply
>>> Regards,
>>> Naza
>>>
>>>
>>>
>>>
>>> On Fri, Aug 2, 2019 at 2:57 PM Ruslan Matveev <matveev.rus...@gmail.com>
>>> wrote:
>>>
>>>> Hi Naza,
>>>>
>>>> do you mean that your cameras is basically behind the firewall and
>>>> there is no access to them from outside the local network (i.e. from the
>>>> rest of the world?).
>>>> If so, you'll need to modify or write custom firmware for your ip -
>>>> cameras, such that it will take local RTSP stream from the camera and send
>>>> it to intermediate server. Then you can use motion to connect to that
>>>> intermediate server. In other words you need to make reverse proxy, or
>>>> tunnel to some machine located outside of your local network and accessible
>>>> to motion.
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Aug 2, 2019 at 4:28 PM naza mantin <naza.man...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>> Greetings to you all. I am interested in Motion and have some
>>>>> inquiries.
>>>>>
>>>>> I have 4 units of both, cameras + 4G encoders on sim cards, thus
>>>>> provided with local IP. But the encoders can "PUSH" to a server with RTSP
>>>>> format using the H.265 codec. The encoders are in a remote area and only 
>>>>> 4G
>>>>> service are available.
>>>>>
>>>>> So the situation is:
>>>>> 1. Camera+encoder on 4G using a sim card support push over RTSP.
>>>>> 2. The server needs to support RTSP push into the server.
>>>>> 3. The server can have a Static IP. As such, we can input the URL in
>>>>> the encoders.
>>>>> 4. The codec to use H.265/HEVC
>>>>>
>>>>> Can Motion support the above? The above system is intended for users
>>>>> in Malaysia and please provide a quotation for all the needed facilities 
>>>>> to
>>>>> be bought.
>>>>>
>>>>> Your reply is very much appreciated
>>>>>
>>>>> Best regards,
>>>>> Naza
>>>>> _______________________________________________
>>>>> Motion-user mailing list
>>>>> Motion-user@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>> https://motion-project.github.io/
>>>>>
>>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>>
>>>> _______________________________________________
>>>> Motion-user mailing list
>>>> Motion-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>> https://motion-project.github.io/
>>>>
>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Fri, 2 Aug 2019 21:46:24 +0100
From: naza mantin <naza.man...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] RTSP SERVER
Message-ID:
        <calyxdikko5dg+hgoupytbpops0zakwt1m-ne-nwdkce8d9d...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Abhisek,
Perhaps Nginx can support RTSP but what about using H265? Is there any
source code module for support of H265?
Because I am able to do RTMP with H264 only so far and if there is a way, I
will definitely try it. Any thoughts?
Regards,
Naza

On Fri, Aug 2, 2019 at 5:39 PM Abhisek Techie <abhisek.study2...@gmail.com>
wrote:

> Hi Naza,
> Try configuring nginx webserver it supports rtsp and your clients can
> connect to nginx  web server to get the feeds.
>
> Regards
>
> On Fri, 2 Aug 2019, 20:37 naza mantin, <naza.man...@gmail.com> wrote:
>
>> Yes... absolutely sure on the push from the encoder.
>>
>> So, I am not a programmer and my knowledge on web socket is very limited.
>> Can anybody help me and please tell me the Fees involve.
>>
>> My whatsapp > +962781327851
>>
>> On Fri, Aug 2, 2019 at 3:35 PM Ruslan Matveev <matveev.rus...@gmail.com>
>> wrote:
>>
>>> If you're absolutely sure that your hardware can push rtsp stream, then
>>> all you need is simple socket server which will be able from one side
>>> accept rtsp stream from your cameras, and on the other side accept connects
>>> from motion and forward all traffic from one side to another.
>>>
>>> ??, 2 ???. 2019 ?., 17:31 naza mantin <naza.man...@gmail.com>:
>>>
>>>> Dear Ruslan,
>>>> Thanks for your reply. Sorry I don't quite understand>>> no access to
>>>> them from outside the local network?
>>>>
>>>> What I mean is that the server can not "PULL" from the encoder.
>>>> But the encoder can "PUSH" to the server.
>>>>
>>>> Thus, the server needs to have some kind of support and can accept RTMP
>>>> "PUSH" from the encoder.
>>>>
>>>> I do hope the above is in order and look forward to your reply
>>>> Regards,
>>>> Naza
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Aug 2, 2019 at 2:57 PM Ruslan Matveev <matveev.rus...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Naza,
>>>>>
>>>>> do you mean that your cameras is basically behind the firewall and
>>>>> there is no access to them from outside the local network (i.e. from the
>>>>> rest of the world?).
>>>>> If so, you'll need to modify or write custom firmware for your ip -
>>>>> cameras, such that it will take local RTSP stream from the camera and send
>>>>> it to intermediate server. Then you can use motion to connect to that
>>>>> intermediate server. In other words you need to make reverse proxy, or
>>>>> tunnel to some machine located outside of your local network and 
>>>>> accessible
>>>>> to motion.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Aug 2, 2019 at 4:28 PM naza mantin <naza.man...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>> Greetings to you all. I am interested in Motion and have some
>>>>>> inquiries.
>>>>>>
>>>>>> I have 4 units of both, cameras + 4G encoders on sim cards, thus
>>>>>> provided with local IP. But the encoders can "PUSH" to a server with RTSP
>>>>>> format using the H.265 codec. The encoders are in a remote area and only 
>>>>>> 4G
>>>>>> service are available.
>>>>>>
>>>>>> So the situation is:
>>>>>> 1. Camera+encoder on 4G using a sim card support push over RTSP.
>>>>>> 2. The server needs to support RTSP push into the server.
>>>>>> 3. The server can have a Static IP. As such, we can input the URL in
>>>>>> the encoders.
>>>>>> 4. The codec to use H.265/HEVC
>>>>>>
>>>>>> Can Motion support the above? The above system is intended for users
>>>>>> in Malaysia and please provide a quotation for all the needed facilities 
>>>>>> to
>>>>>> be bought.
>>>>>>
>>>>>> Your reply is very much appreciated
>>>>>>
>>>>>> Best regards,
>>>>>> Naza
>>>>>> _______________________________________________
>>>>>> Motion-user mailing list
>>>>>> Motion-user@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>> https://motion-project.github.io/
>>>>>>
>>>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>>>
>>>>> _______________________________________________
>>>>> Motion-user mailing list
>>>>> Motion-user@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>> https://motion-project.github.io/
>>>>>
>>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>>
>>>> _______________________________________________
>>>> Motion-user mailing list
>>>> Motion-user@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>> https://motion-project.github.io/
>>>>
>>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>>
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 158, Issue 5
*******************************************

Reply via email to