Defining an IP Network Service
Conferencing with H.323 and SIP endpoints requires the presence of various
components in the IP environment. Several components are common to both
H.323 and SIP connections and others are unique to H.323 or SIP.
The following table lists the components required for conferencing using IP
endpoints, indicating their relevancy to H.323 and SIP:
Table 3-13: IP Network List of Components and Logical Entities
Name
MCU with IP card(s)
Subnet Mask
DHCP
DNS
Host Name
Default Router
Static Routes
NAT Traversal
Gateway
Gatekeepers
H.323 endpoints
SIP endpoints (User
Agents)
SIP Servers—general
Registrar
The MCU's IP cards can be used to connect both H.323 and SIP participants
to conferences. Therefore, you can define one IP Network Service that
includes both H.323 and SIP entities (including the MCU's IP cards) that
H.323
Required
Required
Optional
Optional
Required
Required
Optional
Optional
Optional
Optional
(recommended)
Required
N/A
N/A
N/A
MGC Administrator's Guide
SIP
Required
Required
Optional
Optional
Required
Required
Optional
Optional
Optional
N/A
N/A
Required
Optional
Optional
(recommended)
3-55
Need help?
Do you have a question about the MGC Administrator and is the answer not in the manual?
Questions and answers