Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Note:
Each event will have a severity indicator as follows:
■
0 - Emergency: system is unusable (unused by the MCU)
■
1 - Alert: action must be taken immediately (unused by the MCU)
■
2 - Critical: critical conditions (unused by the MCU)
■
3 - Error: error conditions (used by MCU error events)
■
4 - Warning: warning conditions (used by MCU warning events)
■
5 - Notice: normal but significant condition (used by MCU info events)
■
6 - Informational: informational messages (used by MCU trace events)
■
7 - Debug: debug-level messages (used by MCU detailed trace events)
Related Topics
■
SIP: Advanced
SIP Implementation
The MCU implements SIP as defined in RFC 3261. Any product wanting to establish SIP calls with the MCU should
implement INVITE, ACK, BYE, and CANCEL messages along with responses from 1xx to 6xx. The MCU acts as a client
and does not return 5xx and 6xx responses itself; however, proxies and other intermediaries may do so.
implement INVITE, ACK, BYE, and CANCEL messages along with responses from 1xx to 6xx. The MCU acts as a client
and does not return 5xx and 6xx responses itself; however, proxies and other intermediaries may do so.
To use a SIP registrar in conjunction with the MCU, you must register an ID for the MCU with the SIP registrar. The
MCU can register itself, and individual conferences and auto attendants with a SIP registrar.
MCU can register itself, and individual conferences and auto attendants with a SIP registrar.
For video Fast Update Requests, the MCU uses a type that involves sending an INFO message with an XML body. This
only applies to video endpoints, but these endpoints should be able to correctly reply to INFO requests whether or not
they understand them as Fast Update Requests.
only applies to video endpoints, but these endpoints should be able to correctly reply to INFO requests whether or not
they understand them as Fast Update Requests.
Authentication Details
The username and password that you provide on the Settings > SIP page are the authentication details for all SIP
authentication from the MCU. That is, for the SIP registrar and any SIP proxy. If you have individual conferences
registered with the SIP registrar, the username will be the numeric identifier of the conference and the password will
be the one entered on the Settings > SIP page.
authentication from the MCU. That is, for the SIP registrar and any SIP proxy. If you have individual conferences
registered with the SIP registrar, the username will be the numeric identifier of the conference and the password will
be the one entered on the Settings > SIP page.
Related Topics
■
Working with Call Detail Records
The MCU can display up to 20 pages of Call Detail Records. However, the MCU is not intended to provide long-term
storage of Call Detail Records. If you intend to use the CDR log for purposes such as billing or reporting, you should
download the Call Detail Records and store them independently of the MCU.
storage of Call Detail Records. If you intend to use the CDR log for purposes such as billing or reporting, you should
download the Call Detail Records and store them independently of the MCU.
CDRs are logged to the MCU's dynamic memory unless you enable permanent storage. The memory will hold a
comparatively small number of records, the oldest of which are deleted as new ones are stored.
comparatively small number of records, the oldest of which are deleted as new ones are stored.
If you enable permanent storage the logs are written to the MCU's permanent storage, which can hold a much greater
number of records. However, when the allocated CDR log storage is full, the oldest logs are deleted as new ones are
stored.
number of records. However, when the allocated CDR log storage is full, the oldest logs are deleted as new ones are
stored.
212
Cisco TelePresence MCU Series Online Printable Help