EVC-IP-1,3-2MP. (Audio, Video Player Development Guide)

Transcription

1 EVC-IP-1,3-2MP (Audio, Video Player Development Guide)

2 Table of Contents 1. Document History 2. Using RTSP API 2.1. RTSP Signaling 2.2. RTSP Syntax Client Request Server Response Status-code and reason-phase 3. RTSP Methods 3.1. OPTION 3.2. DESCRIBE IP-CAM SDP 3.3. SETUP 3.4. PLAY 3.5. TEARDOWN 4. RTSP Authentication 5. RTP Extension Header 6. Tunneling RTSP and RTP over HTTP Appendix 1. Example EVC-IP-1,3-2MP 2

3 1. Document History Date Version Auther Notes a Hosung Yoon Reviewer: Conner Sun Add section 6. Tunneling RTSP and RTP over HTTP Add Example 5. on Appendix Draft Hosung Yoon Hosung Yoon Modify contents 2. Using RTSP API Reviewer: SungNam Bae, DongUk Park Reviewer: SungNam Bae, DongUk Park Draft Version EVC-IP-1,3-2MP 3

4 2. Using RTSP API This API provides version after IP-CAMERA System S/W a Applicable IP-CAMERA models are NCX series(2000, 1300, 0350), NCD series, NCDi series, and NCB series. System S/W version and System-relative information documents can be checked in document "ITX IP-CAM HTTP API"(3.6.5) For Audio and Video streming, ITX IP-CAMERA controls Audio and Video based on RTSP(Real Time Streaming Protocol:Control Plane), and transmit Audio, Video media based on RTP(Real Time Protocol:Data Plane) ITX IP-CAMERA complies with standard RTSP(RFC 2326) and standard RTP( RFC 3550, 5285, 3984, 2435, 5391) 2.1. RTSP Signaling <Control Plane: RTSP> <Data Plane: RTP> Client Server Client Server 1 TCP Connection 2 OPTION req OPTION res 3 DESCRIBE req DESCRIBE res 4 SETUP req SETUP res 5 PLAY req PLAY res RTP Data RTCP msg RTP Data RTP Data RTCP msg 6 7 TEARDOWN req TEARDOWN res RTP Data 8 TCP Disconnection 1: Client request TCP Connetion of Server 2: Client request "OPTION" of Server. Server response with useable RTSP Method List 3: Client request "DESCRIBE" of Server. Server transmits response message to Client after add SDP(RFC 4566) format, which is transformed from Server media, on response message. By analyzing SDP, Client can know which media is being supported from Server 4: Client request media, which is in their need, by "SETUP" at SDP base. Server send response message after preparing of media transmission requested by Client 5: Client request "PLAY" to get media transmission and Server transmit media after response 6: Server transmit media to Client at RTP base. Client should send RTCP(RFC 3550) message regularly (genarraly 5sec or max 15sec) to Server 7: Client request "TEARDOWN" to completion of media transmission. Server stops RTP media transmission and response request 8: Server disconnects TCP 2.2. RTSP Syntax Client request followings to control IP-CAMERA's Audio and Video by using RTSP on the basis of Syntax Client Request Syntax: <Method> rtsp://<device IP>/<media type>/<stream name> <request-header>: value0 <request-header>: value1 [message-body] Method device IP media type Refer to 3. RTSP Method List (ex. OPTION, SETUP, PLAY ) ip-camera's IP Address or URL "live" EVC-IP-1,3-2MP 4

5 stream name request-header valuex message-body CRLF "main" or "second" Refer to 3. RTSP Method List Refer to 3. RTSP Method List Refer to 3. RTSP Method List Carriage Return Line Feed (\r\n) Server Response Syntax: RTSP/1.0 <status-code> <reason-phrase> <response-header>: val2 <response-header>: val3 <message-body> status-code Show three digit about result of request (refer to ) reason-phrase Easy to read description of status-code (refer to ) response-header Refer to 3. RTSP Method List valuex Refer to 3. RTSP Method List message-body Refer to 3. RTSP Method List CRLF Carriage Return Line Feed (\r\n) Status-code and reason-phase This is status-code and reason-phase List for Server using status-code reason-phase 200 OK 401 Unauthorized 404 Not Found 405 Not Acceptable 451 Invalid Parameter 453 Not Enough Bandwidth 454 Session Not Found 461 Unsupported Transport 501 Not Implemented 502 Fatal error 3. RTSP Methods 3.1. OPTION Client can know Method List supported by Server through "OPTION" Operation is as same as RFC 2068(9.2). Client can always request Server but it does not affect Server status Example: OPTIONS rtsp:// /live/main RTSP/1.0 CSeq:10 User-Agent: ITX Security CSeq: 10 Public: DESCRIBE, SETUP, TEARDOWN, PLAY Cseq User-Agent Public Request/Response Sequence number. Request should correspond to Response Client Information Method List supported by Server 3.2. DESCRIBE Client can get base URL's media information in SDP format which is described in "DESCRIBE" request message through "DESCRIBE" request Example: DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 11 Accept: application/sdp EVC-IP-1,3-2MP 5

6 User-Agent: ITX Security CSeq: 11 Content-Base: rtsp:// /live/main/ Content-Type: application/sdp Content-Length: 355 <SDP> Accept Content-Base Content-Type Contents type ("application/sdp" only) supported by Client base URL related with SDP(Content) Type of contents Content-Length SDP length SDP Refer to IP-CAM SDP IP-CAM SDP Describe media(h.264, mjpeg compression video, g.711 format audio) supported by Server in SDP format. More detailed information about SDP, refer to RFC 4566(SDP: Session Description Protocol), RFC 2435(RTP Payload Format for JPEG-compressed Video), RFC 3984(RTP Payload Format for H.264 Video), RFC 5391(RTP Payload Format for ITU-T Recommendation G.711.1) Server Media can be set through HTTP API. Refer to document "ITX IP-CAM HTTP SDK" Example, H G.711) Common Part v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 Video Part m=video 0 RTP/AVP 96 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4d4028;sprop-parameter-sets=j01aki2nkaoat2atqebauaaapoaadq YGhgA+gAAEZQLvLjQwAfQAACMoF3lwXo8=,KO48gA== a=control:track0 Audio Part m=audio 0 RTP/AVP 0 a=control:track1 Example, MJPEG + G.711) Common Part v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 Video Part m=video 0 RTP/AVP 26 a=control:track0 Audio Part m=audio 0 RTP/AVP 0 a=control:track SETUP On the basis SDP, Client request Server to send media URI taken by "DESCRIBE" request URI shall be made out by mixture of base URL what Client knows and internal information of SDP(ex, a=control:track0) Client can select the ways of Transport when they ask for "SETUP". Server provide "RTP unicast", "RTP multicast" and "RTP over RTSP" Server makes out Client Session at the point of getting "SETUP" request, and should be ready to transmit media what Client request Server give Session ID to "SETUP" response message. Client should send Message in addition to Session ID from the next reqeust Example: (req) SETUP rtsp:// /live/main/track0 RTSP/1.0 CSeq: 12 Transport: RTP/AVP;unicast;client_port= User-Agent: ITX Security EVC-IP-1,3-2MP 6

7 (res) CSeq: 12 Transport: RTP/AVP;unicast;client_port= ;server_port= ;ssrc=A0623E7A Session: 5A22066EF6FBBFF3296F3CC42910DF Describe the ways of transmission what Client need. Clinent can select following options 1) RTP/AVP(/UDP);unicast;client_port=port0-port1 2) RTP/AVP(/UDP);multicast;client_port=port0-port1 3) RTP/AVP/TCP;unicast;interleaved=ID0-ID1 Transport(req) Transport(res) Session 1) means RTP over UDP unicast transmit 2) means RTP over UDP multicast transmit 1) 2) both are Client port. port0 is Client port to get RTP data and port1 is Client port for RTCP 3) means RTP over RTSP over TCP transmit. Transmit RTP and RTCP data through RTSP port by interleaving and distinct RTP and RTCP by ID. "ID0" means ID of RTP, "ID1" means ID of RTCP Describe response about transmission request of Client. Followings are response of each request. 1) RTP/AVP;unicast;client_port=port0-port1;server-port=port2-port3;ssrc=XXXXXXXX 2) RTP/AVP;multicast;destination=<D class IP>;ttl=<value>;port=port2-port3 3) RTP/AVP/TCP;unicast:interleaved=ID0-ID1 In 1) case, port2 is RTP server port and port3 is RTCP server port In 2) case, client request port is disregarded. Client should transmit or get data through port2 and port3. port2 is RTP server/client port, port3 is RTCP server/client port. Server put D class IP for multicast transmission into "destination" field client session ID PLAY To transmit the media, Client ask the "PLAY" Media transmission use the appointed Port and Transport between Server and Client from "SETUP" request. Example: PLAY rtsp:// /live/main/ RTSP/1.0 CSeq: 13 Session: 75AE33C798602D41F4D076AA39EB32 Range: npt= User-Agent: ITX Security CSeq: 13 Session: 75AE33C798602D41F4D076AA39EB32 Range Range value is disregarded since Play time circle and Server support Live only 3.5. TEARDOWN Client request "TEARDOWN" to complete media transmission Server finish media transmission when get "TEARDOWN" request, and arrange internal source. Example: TEARDOWN rtsp:// /live/main/ RTSP/1.0 CSeq: 14 Session: 75AE33C798602D41F4D076AA39EB32 User-Agent: ITX Security CSeq: 14 Session: 75AE33C798602D41F4D076AA39EB32 EVC-IP-1,3-2MP 7

8 4. RTSP Authentication The ways of RTSP Authentication of Server should comply with WWW Authentication scheme, and use Digest between Basic and Digest Refer to RFC 2617(HTTP Authentication: Basic and Digest Access Authentication) chapter 3 about WWW Authentication and Password encode When RTSP Authentication is requested by Server, it returns to state-code "401" and every Client request should following format except "OPTION" request Example: DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 26 Accept: application/sdp User-Agent: ITX Security RTSP/ Unauthorized CSeq: 26 WWW-Authenticate: Digest realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50f8e8df3dc69a " DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 27 Accept: application/sdp Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main", response=" b8f5a612ad1aebc091ae8a" User-Agent: ITX Security CSeq: 27 Content-Base: rtsp:// /live/main/ Content-Type: application/sdp Content-Length: 394 WWW- Authenticate Authorization Information and thechnical description of Authentication what Client should sufficient. "Digest": Diget Authentication Method "nonce": random number brought out of Server Client request Server about realm what Server provided, ID what noonce and Client knows, encode password by URI and add it into "response". Refer to RFC 2617 in regard to encoding password 5. RTP Extension Header When transmit media Data to Client, Server should add media time and event information after RTP header extension RTP Extension Header complies with RFC 5285(A General Mechanism for RTP Header Extensions), and useses "Two-Byte Header" Format EVC-IP-1,3-2MP 8

9 RTP Extension Format: /* * RTP HDR EXTENSION * * * * RTP_X_DEF_APP lenght=6 * * NTP_ID NTP_LEN ntp_timestamp * * ntp_timestamp * * ntp_timestamp MD_ID MD_LEN * * md_flags * * SN_ID SN_LEN sn_flags * * AL_ID AL_LEN al_flags * * */ Definition Def Value Size(Byte) Description RTP_X_DEF_APP[11-0]: Fixed value 0x100 RTP_X_DEF_APP 0x100F 2 RTP_X_DEF_APP[15-12]: 0xF, timestamp and Event Status indicator. RTP_X_LEN 6 2 Total ExTension Header size, unit: 32bit words. NTP_ID 0x10 1 Timestamp indicator. NTP_LEN 8 1 Timestamp size, 8 Bytes ntp_timestamp - 8 UTC Time, NTP Timestamp format MD_ID 0x11 1 Motion flags indicator. MD_LEN 4 1 Motion flags size, 4 Bytes md_flags - 4 md_flags[3-0]: motion flags of area, md_flags[31-4]: reserved SN_ID 0x12 1 Alarm In(Sensor) flags indicator. SN_LEN 2 1 Alarm In flag szie, 2 Byte sn_flags - 2 sn_flags[0]: Alarm In flag, sn_flags[15-1]: resverved AL_ID 0x13 1 Alarm Out flags indicator AL_LEN 2 1 Alarm Out flags size, 2 Byte al_flasgs - 2 al_flags[0]: Alarm Out flag, al_flags[15-1]: reserved *) Sever's Timezone and DST using can be checked in SDP information. SDP example is shown in Example: a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 x-timezone For Time offset, refer to document "ITX IP-CAM HTTP API" Table 5 dst "0": No use of DST(Daylight Saving Time) "1": Use DST 6. Tunneling RTSP and RTP over HTTP This IP CAMERA support "Tunneling RTSP and RTP over HTTP" and method follow the "APPLE" rule. Please refer the "Tunneling RTSP and RTP over HTTP (page 104)" of "QTSS: QuickTime Streaming Server Modules Programming Guide" that is APPLE Develop Document. The example of "Tunneling RTSP and RTP over HTTP" can be checked from Example.5 of Appendix1. EVC-IP-1,3-2MP 9

10 Appendix 1) The followings are exmple that Client ask media(audio/video) by using RTSP from Server under various circumstances (* omission) Example 1) condition: Media URL : rtsp:// /live/main Transport Scheme : RTP unicast (UDP) Compressed Video : h.264 Compressed Audio : none Authentication : none RTSP req/res: OPTIONS rtsp:// /live/main RTSP/1.0 CSeq: 11 CSeq: 11 Public: DESCRIBE, SETUP, TEARDOWN, PLAY DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 12 Accept: application/sdp CSeq: 12 Content-Base: rtsp:// /live/main/ Content-Type: application/sdp Content-Length: 359 v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 m=video 0 RTP/AVP 96 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4d0028;sprop-parameter-sets=j00aki2nkaoat2atqebauaaapoaadqyghgajx AAAK/ILvLjQwAE4gAAFfkF3lwXo8A==,KO48gA== a=control:track0 SETUP rtsp:// /live/main/track0 RTSP/1.0 CSeq: 13 Transport: RTP/AVP;unicast;client_port= CSeq: 13 Transport: RTP/AVP;unicast;client_port= ;server_port= ;ssrc=6F9A9DB7 Session: 52CD571D6E9D09C37A8AEDB4F700CF PLAY rtsp:// /live/main/ RTSP/1.0 CSeq: 14 Session: 52CD571D6E9D09C37A8AEDB4F700CF Range: npt= CSeq: 14 Session: 52CD571D6E9D09C37A8AEDB4F700CF [RTP unicast Video Streaming] TEARDOWN rtsp:// /live/main/ RTSP/1.0 EVC-IP-1,3-2MP Appendix 1. 10

11 CSeq: 15 Session: 52CD571D6E9D09C37A8AEDB4F700CF CSeq: 15 Session: 52CD571D6E9D09C37A8AEDB4F700CF Example 2) condition: Media URL : rtsp:// /live/second Transport Scheme : RTP multicast (UDP) Compressed Video : mjpeg Compressed Audio : g.711 Authentication : none RTSP req/res: OPTIONS rtsp:// /live/second RTSP/1.0 CSeq: 46 CSeq: 46 Public: DESCRIBE, SETUP, TEARDOWN, PLAY DESCRIBE rtsp:// /live/second RTSP/1.0 CSeq: 47 Accept: application/sdp CSeq: 47 Content-Base: rtsp:// /live/second/ Content-Type: application/sdp Content-Length: 219 v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 m=video 0 RTP/AVP 26 a=control:track0 m=audio 0 RTP/AVP 0 a=control:track1 SETUP rtsp:// /live/second/track0 RTSP/1.0 CSeq: 48 Transport: RTP/AVP;multicast;client_port= CSeq: 48 Transport: RTP/AVP;multicast;destination= ;ttl=5;port= Session: 35B B96B035D73011CE5B66 SETUP rtsp:// /live/second/track1 RTSP/1.0 CSeq: 49 Transport: RTP/AVP;multicast;client_port= Session: 35B B96B035D73011CE5B66 CSeq: 49 EVC-IP-1,3-2MP Appendix 1. 11

12 Transport: RTP/AVP;multicast;destination= ;ttl=5;port= Session: 35B B96B035D73011CE5B66 PLAY rtsp:// /live/second/ RTSP/1.0 CSeq: 50 Session: 35B B96B035D73011CE5B66 Range: npt= CSeq: 50 Session: 35B B96B035D73011CE5B66 [RTP multicast Audio/Video Streaming] TEARDOWN rtsp:// /live/second/ RTSP/1.0 CSeq: 51 Session: 35B B96B035D73011CE5B66 CSeq: 51 Session: 35B B96B035D73011CE5B66 Example 3) condition: Media URL : rtsp:// /live/main Transport Scheme : RTP over RTSP (TCP) Compressed Video : h.264 Compressed Audio : g.711 Authentication : none RTSP req/res: OPTIONS rtsp:// /live/main RTSP/1.0 CSeq: 19 CSeq: 19 Public: DESCRIBE, SETUP, TEARDOWN, PLAY DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 20 Accept: application/sdp CSeq: 20 Content-Base: rtsp:// /live/main/ Content-Type: application/sdp Content-Length: 394 v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 m=video 0 RTP/AVP 96 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4d0028;sprop-parameter-sets=j00aki2nkaoat2atqebauaaapoaadqyghacw AAFRgu8uNCAEsAAKjBd5cE+iwA==,KO48gA== a=control:track0 m=audio 0 RTP/AVP 0 a=control:track1 EVC-IP-1,3-2MP Appendix 1. 12

13 SETUP rtsp:// /live/main/track0 RTSP/1.0 CSeq: 21 Transport: RTP/AVP/TCP;unicast;interleaved=0-1 CSeq: 21 Transport: RTP/AVP/TCP;unicast;interleaved=0-1 Session: 3283ED6C05F664086D4EE07F8E8CAB SETUP rtsp:// /live/main/track1 RTSP/1.0 CSeq: 22 Transport: RTP/AVP/TCP;unicast;interleaved=2-3 Session: 3283ED6C05F664086D4EE07F8E8CAB CSeq: 22 Transport: RTP/AVP/TCP;unicast;interleaved=2-3 Session: 3283ED6C05F664086D4EE07F8E8CAB PLAY rtsp:// /live/main/ RTSP/1.0 CSeq: 23 Session: 3283ED6C05F664086D4EE07F8E8CAB Range: npt= CSeq: 23 Session: 3283ED6C05F664086D4EE07F8E8CAB [RTP over RTSP Audio/Video streaming] TEARDOWN rtsp:// /live/main/ RTSP/1.0 CSeq: 24 Session: 3283ED6C05F664086D4EE07F8E8CAB CSeq: 24 Session: 3283ED6C05F664086D4EE07F8E8CAB Example 4) condition: Media URL : rtsp:// /live/main Transport Scheme : RTP over RTSP (TCP) Compressed Video : h.264 Compressed Audio : g.711 Authentication : Digest WWW Authentication (ID: ADMIN) RTSP req/res: OPTIONS rtsp:// /live/main RTSP/1.0 CSeq: 25 CSeq: 25 Public: DESCRIBE, SETUP, TEARDOWN, PLAY DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 26 Accept: application/sdp RTSP/ Unauthorized EVC-IP-1,3-2MP Appendix 1. 13

14 CSeq: 26 WWW-Authenticate: Digest realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50f8e8df3dc69a " DESCRIBE rtsp:// /live/main RTSP/1.0 CSeq: 27 Accept: application/sdp Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main", response=" b8f5a612ad1aebc091ae8a" CSeq: 27 Content-Base: rtsp:// /live/main/ Content-Type: application/sdp Content-Length: 394 v=0 o=- 1 1 IN IP s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 m=video 0 RTP/AVP 96 a=rtpmap:96 H264/90000 a=fmtp:96 packetization-mode=1;profile-level-id=4d0028;sprop-parameter-sets=j00aki2nkaoat2atqebauaaapoaadqyghac WAAFRgu8uNCAEsAAKjBd5cE+iwA==,KO48gA== a=control:track0 m=audio 0 RTP/AVP 0 a=control:track1 SETUP rtsp:// /live/main/track0 RTSP/1.0 CSeq: 28 Transport: RTP/AVP/TCP;unicast;interleaved=0-1 Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main/", response="93d314a c8a9b344c343704" CSeq: 28 Transport: RTP/AVP/TCP;unicast;interleaved=0-1 Session: FB3A5A037E365AD66C2273F3E9A47C SETUP rtsp:// /live/main/track1 RTSP/1.0 CSeq: 29 Transport: RTP/AVP/TCP;unicast;interleaved=2-3 Session: FB3A5A037E365AD66C2273F3E9A47C Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main/", response="93d314a c8a9b344c343704" CSeq: 29 Transport: RTP/AVP/TCP;unicast;interleaved=2-3 Session: FB3A5A037E365AD66C2273F3E9A47C PLAY rtsp:// /live/main/ RTSP/1.0 CSeq: 30 Session: FB3A5A037E365AD66C2273F3E9A47C Range: npt= Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main/", response="b07d70502e b943526b2b7b6" EVC-IP-1,3-2MP Appendix 1. 14

15 CSeq: 30 Session: FB3A5A037E365AD66C2273F3E9A47C [RTP over RTSP Audio/Video streaming] TEARDOWN rtsp:// /live/main/ RTSP/1.0 CSeq: 31 Session: FB3A5A037E365AD66C2273F3E9A47C Authorization: Digest username="admin", realm="ncx-00115ff00300", nonce="4b0f5c2dc79d87c73188ef4fda0ea7daf5f715d50 f8e8df3dc69a ", uri="rtsp:// /live/main/", response="3c53587a6fe0ce83ae1c16a8a6e644f0" CSeq: 31 Session: FB3A5A037E365AD66C2273F3E9A47C Example 5) condition: Media URL : rtsp:// /live/second Transport Scheme : HTTP Tunneling (Tunneling RTSP and RTP over HTTP, TCP) Compressed Video : mjpeg Compressed Audio : none Authentication : none RTSP req/res: GET /live/second HTTP/1.0 (SC Port) User-Agent: OnvifStreamerControl x-sessioncookie: r7azsfuyu0s/tvuunrbggq== Accept: application/x-rtsp-tunnelled Pragma: no-cache Cache-Control: no-cache Connection: Keep-Alive *SC Port: Server to Clint direction Port, CS Port Clint to Server direction Port. (SC Port) (CS Port) (CS Port) HTTP/ OK Connection: close Cache-Control: no-cache Pragma: no-cache Content-Type: application/x-rtsp-tunnelled POST /live/second HTTP/1.0 User-Agent: OnvifStreamerControl x-sessioncookie: r7azsfuyu0s/tvuunrbggq== Content-Type: application/x-rtsp-tunnelled Pragma: no-cache Cache-Control: no-cache Content-Length: Expires: Tue, 20 Apr :31:35 GMT (Orignal Data) REVTQ1JJQkUgaHR0cDovLzE5Mi4xNjguMTAuMzQvbGl2ZS9zZWNvbmQgUlRTUC8xLjAKQ1NlcTogMQpVc2VyLUFnZW50Oi BPbnZpZlN0cmVhbWVyQ29udHJvbAoK (Base64 Decoded Data) DESCRIBE RTSP/1.0 CSeq: 1 User-Agent: OnvifStreamerControl (SC Port) CSeq: 1 Content-Base: rtsp:// /live/second/ Content-Type: application/sdp Content-Length: 180 v=0 o=- 1 1 IN IP EVC-IP-1,3-2MP Appendix 1. 15

16 s=media Server a=type:broadcast t=0 0 c=in IP a=x-timezone=gmt+09:00 Asia/Seoul;index=29;dst=0 m=video 0 RTP/AVP 26 a=control:track0 (CS Port) (Original Data) U0VUVVAgaHR0cDovLzE5Mi4xNjguMTAuMzQvbGl2ZS9zZWNvbmQvdHJhY2swIFJUU1AvMS4wCkNTZXE6IDIKVXNlci1BZ2V uddogt252awztdhjlyw1lcknvbnryb2wkvhjhbnnwb3j0oibsvfavqvzql1rdudtpbnrlcmxlyxzlzd0wltekcg== (Base64 Decoded Data) SETUP RTSP/1.0 CSeq: 2 User-Agent: OnvifStreamerControl Transport: RTP/AVP/TCP;interleaved=0-1 (SC Port) CSeq: 2 Transport: RTP/AVP/TCP;unicast;interleaved=0-1 Session: 20BE2B81D1252B06EEB0600A859056;timeout=20 (CS Port) (Original Data) UExBWSBodHRwOi8vMTkyLjE2OC4xMC4zNC9saXZlL3NlY29uZC90cmFjazAgUlRTUC8xLjAKQ1NlcTogMwpVc2VyLUFnZW5 0OiBPbnZpZlN0cmVhbWVyQ29udHJvbApSYW5nZTogbnB0PW5vdy0KU2Vzc2lvbjogMjBCRTJCODFEMTI1MkIwNkVFQjA2MD BBODU5MDU2Cgo= (Base64 Decoded Data) PLAY RTSP/1.0 CSeq: 3 User-Agent: OnvifStreamerControl Range: npt=now- Session: 20BE2B81D1252B06EEB0600A (SC Port) CSeq: 3 Session: 20BE2B81D1252B06EEB0600A (SC Port) (CS Port) [[ Streaming using RTP over RTSP method]] (Original Data) VEVBUkRPV04gaHR0cDovLzE5Mi4xNjguMTAuMzQvbGl2ZS9zZWNvbmQvdHJhY2swIFJUU1AvMS4wCkNTZXE6IDQKVXNlci1 BZ2VudDogT252aWZTdHJlYW1lckNvbnRyb2wKU2Vzc2lvbjogMjBCRTJCODFEMTI1MkIwNkVFQjA2MDBBODU5MDU2Cgo= (Base64 Decoded Data) TEARDOWN RTSP/1.0 CSeq: 4 User-Agent: OnvifStreamerControl Session: 20BE2B81D1252B06EEB0600A (SC Port) CSeq: 4 Session: 20BE2B81D1252B06EEB0600A EVC-IP-1,3-2MP Appendix 1. 16