Filter
Top Products
Device Management
Polycom, Inc. 92
Names/Aliases in a Mixed H.323 and SIP Environment
An endpoint that supports both H.323 and SIP can register with the Polycom RealPresence DMA system’s
gatekeeper and SIP registrar using the same name/alias. When the RealPresence DMA system receives a
call for that endpoint, it uses the protocol of the calling endpoint. This is logical and convenient, but it can
lead to failed calls under the following circumstances:
● The system is configured to allow calls to/from rogue (not actively registered) endpoints (see Call
Server Settings).
● An endpoint that was registered with both protocols (using the same name/alias) later has one of the
protocols disabled, and that registration expires (or otherwise becomes inactive).
The Polycom RealPresence DMA system doesn’t know if the endpoint no longer supports that protocol.
When another endpoint tries to call using the called endpoint’s disabled protocol, the system still tries to
reach it using that protocol, and the call fails.
To avoid this problem, you can do one of the following:
● Ensure that endpoints supporting both protocols use different names/aliases for each protocol.
● Don’t allow calls to/from rogue endpoints.
● If you know an endpoint has stopped supporting a protocol, manually delete its inactive registration
for that protocol.
Delete Removes the registration of the selected endpoint(s) with the Call Server and
deletes the endpoint(s) from the Polycom RealPresence DMA system. A dialog asks
you to confirm.
Unregistered endpoints are treated like rogue endpoints (see Call Server Settings).
The device can register again.
Associate User Opens the Associate User dialog for the selected endpoint, where you can
associate this device with a user.
Not available if the Polycom RealPresence DMA system is integrated with a
Polycom RealPresence Resource Manager system. In that case, it receives
user-to-device association information from that system.
Block Registrations Prevents the endpoint(s) from registering with the Call Server. A dialog asks you to
confirm. When blocked endpoints are selected, this becomes Unblock
Registrations.
If a blocked device is in a site managed by the system, its ability to make and
receive calls depends on the system's rogue call policy (see Call Server Settings). If
the device is not in a site managed by the system, it can’t make or receive calls.
Quarantine Prevents the endpoint(s) from making or receiving calls. A dialog asks you to
confirm. When quarantined endpoints are selected, this becomes Unquarantine.
Unlike a blocked endpoint, a quarantined endpoint is registered (or can register) with
the Call Server.
View Call History Takes you to Reports > Call History and displays the call history for the selected
endpoint.
View Registration History Takes you to Reports > Registration History and displays the registration history
for the selected endpoint.
Command Description