![axing MIP 16-00 Manual Download Page 88](http://html1.mh-extra.com/html/axing/mip-16-00/mip-16-00_manual_3036629088.webp)
Operation instructions | MIP 8-00 | MIP 16-00 | MIP 8-06 | MIP 16-06
Page 40 of 48
BA_MIP-8-16-0x.pdf | Technical improvements, changes in design, printing- and other errors reserved. | 2022-01-10
5.9.
SAP
5.9.1.
Session Announcement Protocol (SAP)
The MIP supports the Session Announcement Protocol (SAP). It is defined in RFC 2974. It uses multicast to announce streams
efficiently on a LAN: any computer on the network can receive announces from all others without any manual configuration.
SAP conveys SDP's to describe streams parameters. This can include an RTSP control URL to use for setting up the stream, or a
multicast group address to subscribe to. The SDP also includes port numbers and audio/video codecs parameters, and a stream
name, etc.
Slide the status switch to ON.
Configure an announcement interval in seconds.
5.10.
Logs
5.10.1.
Log entries
Under LOGS you can see the log entries of the headend.
•
The system log is written to the flash memory, so it is still available after rebooting the headend.
•
The status log is written to RAM and is empty after rebooting the headend.
Choose
Statuslog
.
The entries of the status log are displayed.
Choose
Systemlog
.
The entries of the system log are displayed.
Click SAVE LOG to save the respective log entries as a txt file.
Click on ERASE LOG to delete the respective log entries.
Tuner monitoring
Under TUNER TO MONITOR you select the tuners that are to write log entries.