Showing posts with label RTSP. Show all posts
Showing posts with label RTSP. Show all posts

Sunday, July 12, 2020

Exploring the Kanda QooCam 4K - pass1




I was hoping  to get live streaming off this camera, and it would appear if you have a 64 Bit android device their app can see a live video feed?

There is a Live option on the windows app that appears to do nothing.

 The USB doesn't show up as a video driver.


You can connect with the device over Wifi

To do this power on the device and wait for the power up tune to play.

one well timed (approx 1 second) power button push and it will beep and the blue wifi like will come on.

Scanning your wifi network SSID's, and you will see something like:

QOOCAM-06515

your camera id will vary based on the last 5 digits of the serial number.

password is : 12345678




From Linux, this command works but I was seeing many errors.
ffplay  rtsp:192.168.1.1:554/live


sokol@nuc2:~/Desktop/vr180$ ffplay  rtsp:192.168.1.1:554/live
ffplay version 2.8.15-0ubuntu0.16.04.1 Copyright (c) 2003-2018 the FFmpeg developers
  built with gcc 5.4.0 (Ubuntu 5.4.0-6ubuntu1~16.04.10) 20160609
  configuration: --prefix=/usr --extra-version=0ubuntu0.16.04.1 --build-suffix=-ffmpeg --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --cc=cc --cxx=g++ --enable-gpl --enable-shared --disable-stripping --disable-decoder=libopenjpeg --disable-decoder=libschroedinger --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp --enable-libschroedinger --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzvbi --enable-openal --enable-opengl --enable-x11grab --enable-libdc1394 --enable-libiec61883 --enable-libzmq --enable-frei0r --enable-libx264 --enable-libopencv
  libavutil      54. 31.100 / 54. 31.100
  libavcodec     56. 60.100 / 56. 60.100
  libavformat    56. 40.101 / 56. 40.101
  libavdevice    56.  4.100 / 56.  4.100
  libavfilter     5. 40.101 /  5. 40.101
  libavresample   2.  1.  0 /  2.  1.  0
  libswscale      3.  1.101 /  3.  1.101
  libswresample   1.  2.101 /  1.  2.101
  libpostproc    53.  3.100 / 53.  3.100
[h264 @ 0x7f95580008c0] RTP: missed 129 packetsKB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 37 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] left block unavailable for requested intra mode at 0 44
[h264 @ 0x7f95580008c0] error while decoding MB 0 44, bytestream 659
[h264 @ 0x7f95580008c0] concealing 1969 DC, 1969 AC, 1969 MV errors in P frame
[h264 @ 0x7f95580008c0] RTP: missed 28 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 41 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 31 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 27 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 121 packetsKB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 65 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 33 packets0KB sq=    0B f=0/0 
[h264 @ 0x7f95580008c0] RTP: missed 29 packets0KB sq=    0B f=0/0 
Input #0, rtsp, from 'rtsp:192.168.1.1:554/live': sq=    0B f=0/0 
  Metadata:
    title           : H.264 Video. Streamed by iCatchTek.
    comment         : H264
  Duration: N/A, start: 0.801333, bitrate: N/A
    Stream #0:0: Video: h264 (High), yuv420p, 1920x960, 15 fps, 14.99 tbr, 90k tbn, 30 tbc
[h264 @ 0x7f955812a200] left block unavailable for requested intra mode at 0 44
[h264 @ 0x7f955812a200] error while decoding MB 0 44, bytestream 659
[h264 @ 0x7f955812a200] concealing 1969 DC, 1969 AC, 1969 MV errors in P frame
[h264 @ 0x7f95580008c0] RTP: missed 41 packets9KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 65 packets1KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 25 packets2KB sq=    0B f=1/1 
[h264 @ 0x7f95580008c0] RTP: missed 41 packets
[h264 @ 0x7f95580008c0] RTP: missed 33 packets
    Last message repeated 1 times
[h264 @ 0x7f95580008c0] RTP: missed 161 packetsKB sq=    0B f=1/1 
 




$ nmap -v -sN 192.168.1.1
Starting Nmap 7.70 ( https://nmap.org ) at 2020-07-06 08:11 ric
Initiating ARP Ping Scan at 08:11
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 08:11, 2.16s elapsed (1 total hosts)
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-s
ervers
Initiating NULL Scan at 08:11
Scanning 192.168.1.1 [1000 ports]
Completed NULL Scan at 08:11, 6.23s elapsed (1000 total ports)
Nmap scan report for 192.168.1.1
Host is up (0.018s latency).
Not shown: 997 closed ports
PORT     STATE         SERVICE
21/tcp   open|filtered ftp
554/tcp  open|filtered rtsp
9200/tcp open|filtered wap-wsp
MAC Address: CC:4B:73:35:B4:2E (Ampak Technology)

Read data files from: C:\Program Files (x86)\Nmap
Nmap done: 1 IP address (1 host up) scanned in 15.72 seconds
           Raw packets sent: 1004 (40.148KB) | Rcvd: 998 (39.908KB)



$ nmap -v -A 192.168.1.1
Starting Nmap 7.70 ( https://nmap.org ) at 2020-07-06 08:12 ric
NSE: Loaded 148 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 08:12
Completed NSE at 08:12, 0.00s elapsed
Initiating NSE at 08:12
Completed NSE at 08:12, 0.00s elapsed
Initiating ARP Ping Scan at 08:12
Scanning 192.168.1.1 [1 port]
Completed ARP Ping Scan at 08:12, 2.46s elapsed (1 total hosts)
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-s
ervers
Initiating SYN Stealth Scan at 08:12
Scanning 192.168.1.1 [1000 ports]
Discovered open port 554/tcp on 192.168.1.1
Discovered open port 21/tcp on 192.168.1.1
Discovered open port 9200/tcp on 192.168.1.1
Completed SYN Stealth Scan at 08:12, 3.94s elapsed (1000 total ports)
Initiating Service scan at 08:12
Scanning 3 services on 192.168.1.1
Completed Service scan at 08:12, 6.01s elapsed (3 services on 1 host)
Initiating OS detection (try #1) against 192.168.1.1
Retrying OS detection (try #2) against 192.168.1.1
Retrying OS detection (try #3) against 192.168.1.1
Retrying OS detection (try #4) against 192.168.1.1
Retrying OS detection (try #5) against 192.168.1.1
NSE: Script scanning 192.168.1.1.
Initiating NSE at 08:13
Completed NSE at 08:13, 10.04s elapsed
Initiating NSE at 08:13
Completed NSE at 08:13, 0.00s elapsed
Nmap scan report for 192.168.1.1
Host is up (0.0042s latency).
Not shown: 997 closed ports
PORT     STATE SERVICE    VERSION
21/tcp   open  tcpwrapped
554/tcp  open  rtsp       DoorBird video doorbell rtspd
9200/tcp open  tcpwrapped
MAC Address: CC:4B:73:35:B4:2E (Ampak Technology)
No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).
TCP/IP fingerprint:
OS:SCAN(V=7.70%E=4%D=7/6%OT=554%CT=1%CU=34247%PV=Y%DS=1%DC=D%G=Y%M=CC4B73%T
OS:M=5F02CF11%P=i686-pc-windows-windows)SEQ(CI=I%II=RI)ECN(R=N)T1(R=Y%DF=N%
OS:T=FF%S=O%A=S+%F=AS%RD=0%Q=)T1(R=N)T2(R=N)T3(R=N)T4(R=Y%DF=N%T=FF%W=E420%
OS:S=A%A=S%F=AR%O=%RD=0%Q=)T5(R=Y%DF=N%T=FF%W=E420%S=A%A=S+%F=AR%O=%RD=0%Q=
OS:)T6(R=Y%DF=N%T=FF%W=E420%S=A%A=S%F=AR%O=%RD=0%Q=)T7(R=Y%DF=N%T=FF%W=E420
OS:%S=A%A=S+%F=AR%O=%RD=0%Q=)U1(R=Y%DF=N%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPC
OS:K=G%RUCK=G%RUD=G)IE(R=Y%DFI=S%T=FF%CD=S)

Network Distance: 1 hop
Service Info: Device: webcam

TRACEROUTE
HOP RTT     ADDRESS
1   4.20 ms 192.168.1.1

NSE: Script Post-scanning.
Initiating NSE at 08:13
Completed NSE at 08:13, 0.01s elapsed
Initiating NSE at 08:13
Completed NSE at 08:13, 0.01s elapsed
Read data files from: C:\Program Files (x86)\Nmap
OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 52.54 seconds
           Raw packets sent: 1241 (60.438KB) | Rcvd: 1047 (43.282KB)
$





Saturday, June 20, 2020

A history of video conferencing (VC) technology


Lifted from:
https://www.packetizer.com/ipmc/history-of-videoconferencing/

I started streaming audio in 1988 across the lan, and video across the Stanford IP Network in 1989. and was invited to work on video at Sun in 1992. 

So I have the original global internet video stream I did at Sun in December 1992.
13000 viewers using 384 rebroadcast servers.

Now posted at:
https://github.com/johnsokol/holiday_greeting_1992

  6/22/2020 With a little persuasion I convinced Ron Frederick to post this up on github. 
     https://github.com/ronf/nv

A history of video conferencing (VC) technology

"This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us." -- Western Union internal memo, 1876.
Picurephone, 1964
The Bell system Picturephone, 1964
  • 1956: AT&T builds the first Picturephone test system
  • 1964: AT&T introduces Picturephone at the World's Fair, New York
  • 1970: AT&T offers Picturephone for $160 per month
  • 1971: Ericsson demonstrates the first trans-atlantic video telephone (LME) call
  • 1973 Dec: ARPAnet packet voice experiments [1]
  • 1976 Mar: Network Voice Protocol (NVP), by Danny Cohen, USC/ISI
  • 1981 Jul: Packet Video Protocol (PVP), by Randy Cole, USC/ISI [2]
  • 1982: CCITT (forerunner of the ITU-T) standard H.120 (2 Mbit/s) video coding, by European COST 211 project
  • 1982: Compression Labs begins selling $250,000 VC system, $1,000 per hour lines
  • 1986: PictureTel's $80,000 VC system, $100 per hour lines
  • 1987: Mitsubishi sells $1,500 still-picture phone
  • 1989: Mitsubishi drops still-picture phone
  • 1990: TWBnet packet audio/video experiments, vt (audio) and pvp (video) from ISI/BBN [3]
  • 1990: CCITT standard H.261 (p x 64) video coding
  • 1990 Dec: CCITT standard H.320 for ISDN conferencing
  • 1991: PictureTel unveils $20,000 black-and-white VC system, $30 per hour lines
  • 1991: IBM and PictureTel demonstrate videophone on PC
  • 1991 Feb: DARTnet voice experiments, Voice Terminal (vt) program from USC/ISI [4]
  • 1991 Jun: DARTnet packet video test between ISI and BBN.
  • 1991 Aug: UCB/LBNL's audio tool vat releases for DARTnet use
  • 1991 Sep: First audio/video conference (H.261 hardware codec) at DARTnet
  • 1991 Dec: dvc (receive-only) program, by Paul Milazzo from BBN, IETF meeting, Santa Fe [5]
  • 1992: AT&T's $1,500 videophone for home market
  • 1992 Mar: World's first MBone audio cast (vat), 23rd IETF, San Diego
  • 1992 Jul: MBone audio/video casts (vat/dvc), 24th IETF, Boston [6]
  • 1992 Jul: INRIA Videoconferencing System (IVS), by Thierry Turletti from INRIA [7]
  • 1992 Sep: CU-SeeMe v0.19 for Macintosh (without audio), by Tim Dorcey from Cornell [8]
  • 1992 Nov: Network Video (nv) v1.0, by Ron Frederick from Xerox PARC, 25th IETF, Washington DC [9]

       The Code nv this is LOST, and no longer available.   6/22/2020 Correction, with a little persuasion I convinced Ron Frederick to post this up on github.
         https://github.com/ronf/nv

  • 1992 Dec: Real-time Transport Protocol (RTP) v1, by Henning Schulzrinne
  • 1992 Dec, First Global Video Stream, over Sun's private network. 13000 viewers.
    This becomes Sun's CellB.
  • 1993 Apr: CU-SeeMe v0.40 for Macintosh (with multipoint conferencing)
  • 1993 May: Network Video (nv) v3.2 (with color video)
  • 1993 Oct: vic initial alpha, by Steven McCanne and Van Jacobson from UCB/LBNL [10]

       Code for VIC at https://github.com/johnsokol/LBL-VIC
       The only Source Code for Sun's Cellb Video compression
  • 1993 Nov: VocalChat v1.0, an audio conferencing software for Novell IPX networks [11]
  • 1994 Feb: CU-SeeMe v0.70b1 for Macintosh (with audio) , audio code by Charley Kline's Maven [12]
  • 1994 Apr: CU-SeeMe v0.33b1 for Windows (without audio), by Steve Edgar from Cornell
  • 1994 Jun: John Sokol forms NetSys Inc and begins building first CDN for video Streaming of Livecam Motion Jpeg Streams. 
  • 1995 Feb: VocalTec Internet Phone v1.0 for Windows (without video)
  • 1995 Aug: CU-SeeMe v0.66b1 for Windows (with audio)
  • 1996 Jan: Real-time Transport Protocol (RTP) v2, by IETF avt-wg [13]
  • 1996 Mar: ITU-T standard H.263 (p x 8) video coding for low bit-rate communication
  • 1996 Mar: VocalTec Telephony Gateway
  • 1996 May: ITU-T standard H.324 for POTS conferencing
  • 1996 Jul: ITU-T standard T.120 for data conferencing
  • 1996 Aug: Microsoft NetMeeting v1.0 (without video)
  • 1996 Oct: ITU-T standard H.323 v1, by ITU-T SG 16 [14]
  • 1996 Nov: VocalTec Surf&Call, the first Web to phone plugin
  • 1996 Dec: Microsoft NetMeeting v2.0b2 (with video) [15]
  • 1996 Dec: VocalTec Internet Phone v4.0 for Windows (with video)
  • 1997 Jul: Virtual Room Videoconferencing System (VRVS), Caltech-CERN project
  • 1997 Sep: Resource ReSerVation Protocol (RSVP) v1, by IETF rsvp-wg
  • 1998 Jan: ITU-T standard H.323 v2
  • 1998 Jan: ITU-T standard H.263 v2 (H.263+) video coding
  • 1998 Apr: CU-SeeMe v1.0 for Windows and Macintosh (with color video), from Cornell
  • 1998 May: Cornell's CU-SeeMe development team has completed their work and has gone on to other projects
  • 1998 Oct: ISO/IEC standard MPEG-4 v1, by ISO/IEC JTC1/SC29/WG11 (MPEG)
  • 1999 Feb: Session Initiation Protocol (SIP) makes proposed standard, by IETF mmusic-wg [16]
  • 1999 Apr: Microsoft NetMeeting v3.0b (with gatekeeper)
  • 1999 Aug: ITU-T H.26L Test Model Long-term (TML) project , by ITU-T SG16/Q.6 (VCEG)
  • 1999 Sep: ITU-T standard H.323 v3
  • 1999 Oct: NAT compatible version of iVisit, v2.3b5 for Windows and Mac
  • 1999 Oct: Media Gateway Control Protocol (MGCP) v1, IETF
  • 1999 Dec: Microsoft NetMeeting v3.01 service pack 1 (4.4.3388)
  • 1999 Dec: ISO/IEC standard MPEG-4 v2
  • 2000 May: Columbia SIP user agent sipc v1.30
  • 2000 Oct: Samsung releases the first MPEG-4 streaming 3G (CDMA2000-1x) video cell phone
  • 2000 Nov: ITU-T standard H.323 v4
  • 2000 Nov: MEGACO/H.248 Protocol v1, by IETF megaco-wg
  • and ITU-T SG 16
  • 2000 Dec: Microsoft NetMeeting v3.01 service pack 2 (4.4.3396))
  • 2000 Dec: ISO/IEC Motion JPEG 2000 (JPEG 2000, Part 3) project, by ISO/IEC JTC1/SC29/WG1 (JPEG)
  • 2001 Jun: Windows XP Messenger supports the SIP
  • 2001 Sep: World's first trans-atlantic tele gallbladder surgery (operation Lindbergh)
  • 2001 Oct: NTT DoCoMo sells $570 3G (WCDMA) mobile videophone
  • 2001 Oct: TV reporters use $7,950 portable satellite videophone to broadcast live from Afghanistan
  • 2001 Oct: Microsoft NetMeeting v3.01 (4.4.3400) on XP
  • 2001 Dec: JVT video coding (H.26L and MPEG-4 Part 10) project, by ITU-T SG16/Q.6 (VCEG) and ISO/IEC JTC1/SC29/WG 11 (MPEG)
  • 2002 Jun: World's first 3G video cell phone roaming
  • 2002 Dec: JVT completes the technical work leading to ITU-T H.264
  • 2003 May: ITU-T recommendation H.264 advanced video coding
Sources : Wall Street Journal (27 February 1996), The MBone FAQ, rem-conf listserv, The MBone listserv, CU-SeeMe listserv, RTP: Historical Notes, and few PostScripts (*.ps).
Notes and References
[1] Danny Cohen, "Specifications for the Network Voice Protocol (NVP)", RFC 741, Internet Engineering Task Force, November 1977.
"The major objective of ARPA's Network Secure Communications (NSC) project is to develop and demonstrate the feasibility of secure, high-quality, low-bandwidth, real-time, full-duplex (two-way) digital voice communications over packet-switched computer communications networks. The Network Voice Protocol (NVP), implemented first in December 1973, and has been in use since then for local and transnet real-time voice communication over the ARPANET."
[2] Randy Cole, "PVP - A Packet Video Protocol", Internal Document, USC/ISI, July 1981.
"The Packet Video Protocol (PVP) is a set of extensions to the Network Voice Protocol (NVP-II) and consists mostly of a data protocol for transmission of video data. No specific changes to the NVP-II protocol are necessary for the PVP."
[3] Eve M. Schooler, "A Distributed Architecture for Multimedia Conference Control", ISI research report ISI/RR-91-289, November 1991.
"Voice Terminal (VT) program and Packet Video Program (PVP) were originally implemented on a BBN Butterfly multiprocessor. VT and PVP digitize and packetize data, using the Netowrk Voice Protocol (NVP) for audio and the Packet Video Protocol (PVP) for video. They transmit this data across the network using the experimental Stream Protocol (SP) and the Terrestrial Wideband Network (TWBnet)."
[4] DARTnet : A trans-continental IP network of about a dozen research sites connected by T1 trunks.
November 1988, small group (MIT, BBN, UDel, ISI, SLI, PARC, LBL) led by Bob Braden of USC/ISI proposes testbed net to DARPA. This becomes DARPA Research Testbed Net (DARTnet).
DARTnet has since evolved to CAIRN, which presently connects 27 institutions in the US and Britain.
[5] Tim Dorcey, "CU-SeeMe Desktop VideoConferencing Software", Connexions, Volume 9, No.3, March 1995.
"In fact, it was Paul Milazzo's demonstration of such a tool in 1991 that inspired development of CU-SeeMe."
[6] The video used for the July 1992 Internet Engineering Task Force (IETF) was the Desktop Video Conferencing (DVC) program from BBN, written by Paul Milazzo and Bob Clements.
They have made available a receive-only program, but they retain a proprietary interest in the version that is capable of sending.
This program has since become a product, called PictureWindow.
[7]INRIA Videoconferencing System (IVS) was used to broadcast part of the IETF 25 meeting held in Washington, DC during 16-20 November, 1992. The broadcast was sent over the Mbone. See Internet Monthly Report published in November 1992.
[8] "When development of CU-SeeMe began in July 1992, the only real-time videoconferencing software for the Internet required expensive hardware which severely limited the number of potential senders and receivers. Working with Richard Cogger in the summer of 1992, Tim Dorcey wrote the original version of CU-SeeMe."
URL: http://cu-seeme.cornell.edu
As the Macintosh did not have IP multicast support, CU-SeeMe took a more traditional approach and developed a multipoint server (Reflector) that CU-SeeMe clients could connect to.
[9] For the November 1992 IETF and several events since then, they have used two other programs.
The first is the Network Video (nv) program from Ron Frederick at Xerox PARC.
Also available from INRIA is the IVS program written by Thierry Turletti (as mentioned previously).
Van Jacobson, "Old timers might remember that the first, binary-only, release of nv happened 24 hours before the November 1992 IETF where it was first used."
[10] vic (vi/deo c/onfernece) was inspired by nv. Portions of vic (the ordered dither, the nv-format codec, and some of the video capture code) were derived from the nv source code.
An early version of vic was used by the Xunet research community to carry out distributed meetings in Fall 1993.
vic change history at http://www-nrg.ee.lbl.gov/vic/CHANGES.html
[11] In 1991, 5 high school friends established ClassX, a start-up software company, at Raanana, Israel.
2 years later, 4 members of them joined VocalTec and they have developed the VocalChat v1.0-2.5, and the Internet Phone.
Ofer Shem Tov, "VocalChat early version was introduced first time in PCEXPO end of June 1993 in New York. It did half duplex calls over Novell IPX networks. VocalChat v1.0 was released in Comdex Fall, November 1993, in Las Vegas, it was a finished version of the PCEXPO product. First long distance call was done on Bell South Novell network from Atlanta to Miami. VocalChat 2.02 LAN and WAN were released in June 1994 and included voice mail, address book, TCP/IP support and support of VocalTec Compression Card (VCC) for low bandwidth links.
VocalChat GTI (Gateway To the Internet) was released in October 1994. It was focused on the Internet and required the VCC card."
[12] Charley Kline, "I got annoyed at the Fall 1992 IETF when told that the only serious platform for multimedia conferencing was a hefty Unix workstation. I figured a Macintosh has better audio processing ability than a Sun (true!), so set about to write an audio conferencing tool for the Macintosh that would interoperate with the popular vat program for Unix."
URL: http://spiffy.ci.uiuc.edu/~kline/cvk-ido.html
[13] Henning Schulzrinne, "Real-time Transport Protocol (RTP) is the Internet-standard protocol for the transport of real-time data, including audio and video. It can be used for media-on-demand as well as interactive services such as Internet telephony. RTP consists of a data and a control part. The latter is called RTP Control Protocol (RTCP)."
RTP has its roots in the early work done using Network Voice Protocol 2 (NVP-II) with vat, vt and nevot in 1991, which in turn has its roots in the Network Voice Protocol (NVP) experiences in the early 1970s.
[14] H.323 : "Visual telephone systems and equipment for Local Area Networks which provide a non-guaranteed Quality of Service." (original title)
"Packet-based multimedia communications systems." (revised title in H.323 v2 drafts)
4 main H.323 network components; Terminals, Gateways, Gatekeepers, and Multipoint Control Units (MCUs).
H.320 (N-ISDN), H.321 (B-ISDN, ATM), H.322 (GQoS LAN), H.323 (H.320 over LAN), H.324 (SCN), H.324 M (Mobile).
[15] Toby Nixon, "Microsoft NetMeeting version 2.0 and below uses an alternative call setup procedure that is permitted for combined H.323/T.120 terminals. Because NetMeeting was originally a T.120-based product (without H.323 support), it sets up the T.120 (data conference) call first, and then the H.323 (audio and video conference) call."
Current versions of NetMeeting are not compliant with the H.323 standard as they do not attempt to register with a gatekeeper, a required function.
[16] SIP is a simple signaling protocol for Internet conferencing and telephony.
H.323 is an ITU-T standard, while SIP is the IETF approach.
The pioneering video conferencing tools :
  • CU-SeeMe [video]
    from Cornell University
    platform : Apple Macintosh
  • DVC [video]
    from BBN
    platform : Sun SPARC
  • IVS [video & audio]
    from INRIA
    platform : Sun SPARC, HP, SGI and DEC stations
  • NV [video]
    from Xerox PARC
    platform : Sun SPARC, SGI and DEC stations

      6/22/2020 With a little persuasion I convinced Ron Frederick to post this up on github.

         https://github.com/ronf/nv

     I am told it will build and run on modern machines and Ron was surprised on how well his codec performs against more modern ones.

Friday, November 25, 2016

LOW-COST VIDEO STREAMING WITH A WEBCAM AND RASPBERRY PI

http://hackaday.com/2016/11/25/low-cost-video-streaming-with-a-webcam-and-raspberry-pi/


http://videos.cctvcamerapros.com/raspberry-pi/ip-camera-raspberry-pi-youtube-live-video-streaming-server.html


Spoiler Alert, Basically they use the Raspberry Pi to connect to the CCTV IP camera over RTSP and then send a live stream up to youtube. Up, out though your firewall and NAT to youtube or any service that will accept RTMP.

Most of this is a good NOVICE GUIDE to setting up and configuring the Pi and buying a IP camera from them.

  1. You can download the source code for the BASH script here.

#!/bin/bash

SERVICE="ffmpeg"
RTSP_URL="rtsp://192.168.0.119:554/video.pro1"
YOUTUBE_URL="rtmp://a.rtmp.youtube.com/live2"
YOUTUBE_KEY="dn7v-5g6p-1d3w-c3da"

COMMAND="sudo ffmpeg -f lavfi -i anullsrc -rtsp_transport tcp -i ${RTSP_URL} -tune zerolatency -vcodec libx264 -t 12:00:00 -pix_fmt + -c:v copy -c:a aac -strict experimental -f flv ${YOUTUBE_URL}/${YOUTUBE_KEY}"

if sudo /usr/bin/pgrep $SERVICE > /dev/null
then
        echo "${SERVICE} is already running."
else
        echo "${SERVICE} is NOT running! Starting now..."
        $COMMAND
fi


They have a bunch of neat Pi Video projects on their web site.
http://videos.cctvcamerapros.com/raspberry-pi

Friday, August 19, 2011

LIVE555 Media Server

LIVE555 is an open source (LGPL) C++ library for multimedia streaming. It supports open standards such as RTP/RTCP, RTSP, SIP for streaming, and can also manage video and audio formats such as MPEG, H.263+ JPEG video. It is designed in such a way that it can be easily extended to support more formats.

It is used by VLC media player and MPlayer.


http://www.live555.com/

http://en.wikipedia.org/wiki/LIVE555


LIVE555 Media Server 

A complete RTSP server application.