...
If WCS is launched on this server, the second parameter port number should be out of ranges used by WCS. The stream that will be available on this port, will be named as the stream in the dump file
If source port is set to 0
Code Block | ||||
---|---|---|---|---|
| ||||
java -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -cp /usr/local/FlashphonerWebCallServer/lib/wcs-core.jar:/usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.tools.rtsp.RtspPcapServer /usr/local/FlashphonerWebCallServer/pcaps 3554 0 true |
the utility will try to detect all RTSP streams in all the dumps found, and list them to the standard output (see below).
The utility prints all information to stdout. For example, if there is one file log.pcap in /usr/local/FlashphonerWebCallServer/pcaps directory, the following will be printed to console:
Code Block | ||||
---|---|---|---|---|
| ||||
04:35:20,721 INFO RtspPcapServer - Starting 04:35:22,244 INFO RtspPcapServer - Available sources: 04:35:22,245 INFO RtspPcapServer - Source{path=/usr/local/FlashphonerWebCallServer/pcaps/log.pcap, pcap=io.pkts.Pcap@5a39699c, stream=RTSPStream{config=8, data=22052, streamName='live1.sdp'}} 04:35:22,245 INFO RtspPcapServer - Starting PCAP RTSP server 04:35:22,407 INFO RtspPcapServer - Listening PCAP RTSP on address /0.0.0.0 port 5543554 |
The RTSP stream name exposed by utility will be set to RTSP stream name from the dump, or RTSP URI from the dump encoded as base64.
In this case, stream can be captured from address
Code Block | ||||
---|---|---|---|---|
| ||||
rtsp://hostname:3554/livelive1.sdp |
where hostname is server name with utility running.
If the directory contains a number of dump files, the stream names should not be the same, only one of such streams will be captured.
Setting a custom name for captured streams
Since build 5.2.1794 it ts possible to set a custom name prefix for RTSP streams captured from a dump file
Code Block | ||
---|---|---|
| ||
rtsp_pcap_server_custom_stream_name=source |
An index number starting from 0 will be added to the prefix. In this case all the RTSP streams captured from the dump file using the command
Code Block | ||||
---|---|---|---|---|
| ||||
java -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -cp /usr/local/FlashphonerWebCallServer/lib/wcs-core.jar:/usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.tools.rtsp.RtspPcapServer /usr/local/FlashphonerWebCallServer/pcaps 3554 0 true |
will be available by the following URLs
Code Block | ||||
---|---|---|---|---|
| ||||
rtsp://hostname:3554/source0
rtsp://hostname:3554/source1
... |
where hostname is a server name where the utility is running.
RTSP connection redirection testing
To test RTSP connection redirection using IP camera emulator, it is necessary to set the method in flashphoner.properties file, in response on which 302 Moved Temporarily should be returned, for example
...
Then, run RTSP dump file capture utility and connect to stream from dump file as described above. RTSP connection will be redirected to address defined.
RTSP authentication testing
Since build 5.2.1002 it is possible to test RTSP digest authentication. To do this, the additional parameter must be set when launching the utility:
Code Block | ||||
---|---|---|---|---|
| ||||
java -Dcom.flashphoner.fms.AppHome=/usr/local/FlashphonerWebCallServer -cp /usr/local/FlashphonerWebCallServer/lib/wcs-core.jar:/usr/local/FlashphonerWebCallServer/lib/* com.flashphoner.tools.rtsp.RtspPcapServer /usr/local/FlashphonerWebCallServer/pcaps 3554 0 true 'login:password:SHA-256,MD5' |
Wher
- login - user name to login
- password - passwird
- SHA-256,MD5 - authentication algorithms list
In this case, all the streams exposed by the utility must be played by URI like
Code Block | ||||
---|---|---|---|---|
| ||||
rtsp://login:password@hostname:3554/streamName |