Which of the following will a SIP endpoint use as the SIP alias when the endpoint registers with a Cisco VCS?
A.
the endpoint’s IP address
B.
the AOR
C.
the H.323 alias
D.
the registrar address
Explanation:
A Session Initiation Protocol (SIP) endpoint will use the Address of Record (AOR) as the SIP alias when the
endpoint registers with a Cisco TelePresence Video Communication Server (VCS). The AOR should be in theform of a Uniform Resource Identifier (URI). When registering, the SIP endpoint will also give its IP address to
the VCS; however, the IP address is not used as the SIP alias.
The Cisco VCS acts as the SIP server and as a SIP registrar. The SIP registrar accepts registrations only for
the domain or domains for which it is authoritative. It can also proxy registration requests to another SIP
registrar if it is configured to do so.
The SIP endpoint needs to be able to discover the SIP registrar. If the endpoint is set for automatic SIP server
discovery, the endpoint will send a REGISTER message to the SIP server that is authoritative for the endpoint’s
domain. If the endpoint is set for manual SIP server discovery, the endpoint must be configured with the IP
address or the fully qualified domain name (FQDN) of the SIP registrar. Although a SIP endpoint might use the
SIP registrar address to register, it will not use the SIP registrar address as the SIP alias.
A SIP endpoint will not use an H.323 alias as the SIP alias when the endpoint registers with a Cisco VCS.
When an H.323 endpoint registers with Cisco VCS, the endpoint sends one or more of the following aliases to
the VCS:
One or more H.323 IDs
One or more E.164 aliases
One or more Uniform Resource Identifiers (URIs)Cisco: Cisco TelePresence Video Communication Server, Administrator Guide, Software version: X8.1:
Registering aliases (PDF)
Cisco: Cisco TelePresence Video Communication Server, Administrator Guide, Software version: X8.1: About
SIP (PDF)
Cisco: Cisco TelePresence Video Communication Server, Administrator Guide, Software version: X8.1:
Configuring SIP (PDF)