Local Cluster Configuration

Note: Understanding SIP Communications

The system only answers UDP calls if that transport is enabled. But for communications back to the endpoint, it uses the transport protocol that the endpoint requested (provided that the transport is enabled, and for TCP, that unencrypted connections are permitted).

For more information about this and other aspects of SIP, see RFC 3261.

dLeave the default port numbers (5060 for TCP/UDP, 5061 for TLS) unless you have a good reason for changing them.

eTo turn on SIP digest authentication for either the unencrypted or TLS port, select the corresponding Enable authentication check box.

Device authentication credentials must be added on the Inbound Authentication tab of the Device Authentication page. Click the Device authentication settings link to go directly there.

fTo enable mutual TLS (mTLS), select Require certificate validation for TLS.

4To enable the system to receive untrusted calls (see Untrusted SIP Call Handling Configuration on page 73) from SIP session border controllers (SBCs) configured to route such calls to special ports, do the following:

a Under Unauthorized ports, click Add.

The Add Guest Port dialog box opens.

bSpecify the port number, the transport, whether authentication is required, and for TLS, whether certificate validation is required (mTLS). Click OK.

The new entry is added to the Unauthorized ports list.

cRepeat for each additional port on which to receive “unauthorized” or “guest” calls.

5To enable the system to receive untrusted calls (see Untrusted SIP Call Handling Configuration on page 73) from SIP session border controllers (SBCs) configured to add a specific prefix in the Request-URI of the INVITE message for such calls, do the following:

a Under Unauthorized prefixes, click Add.

The Add Guest Prefix dialog box opens.

bSpecify the prefix number, whether it should be stripped, and whether authentication is required. Click OK.

The new entry is added to the Unauthorized prefixes list.

cRepeat for each additional prefix used for “unauthorized” or “guest” calls.

6Click Update.

A dialog box informs you that the configuration has been updated.

7Click OK.

The system processes the configuration. The Status field shows the current H.323 signaling state.

8If you enabled the system to receive “unauthorized” or “guest” calls, do the following:

a Go to Admin > Call Server > Dial Rules and click in the Dial rules for unauthorized calls list to give it focus.

bAdd one or more dial rules to be used for routing “unauthorized” or “guest” calls. See Dial Rules on page 239.

An unauthorized call rule can route calls to a conference room ID (virtual meeting room, or VMR), a virtual entry queue (VEQ), or a SIP peer.

Polycom, Inc.

84

Page 84
Image 84
Polycom 3725-76302-001O manual Under Unauthorized ports, click Add, Under Unauthorized prefixes, click Add