How To Provisioning Endpoints With Sip Server Settings

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

ARTICLE ID: 000054594 LAST MODIFIED DATE: 12/09/2021 ACCESS LEVEL: INTERNAL PUBLIC PARTNERS

HOW TO PROVISIONING ENDPOINTS WITH SIP SERVER SETTINGS


The RealPresence Resource Manager system supports the integration with various SIP servers by provisioning endpoints SIP settings they need.

After you provision endpoints with SIP settings, all endpoints receive directory information from one of those servers. You are no longer using the
enterprise directory or the other directory functions in the RealPresence Resource Manager system.

The RealPresence Resource Manager system supports SIP to establish conference connections. If you want to use SIP, you must enable it and
configure SIP settings. You must also ensure that users have SIP URIs.

Create Authentication Information for SIP Endpoints

To have the RealPresence Resource Manager system dynamically provision a Polycom endpoint for SIP integration, the endpoint must use the same
credentials (username and password) to access both the SIP server and the RealPresence Resource Manager system. Only then can the RealPresence
Resource Manager system provision SIP settings.

If the SIP server uses a third-party database for authentication that the RealPresence Resource Manager system is not aware of, you need to import
both the user information and SIP URI information from the SIP server.

1 Create a RealPresence Resource Manager system local user account for the endpoint that matches the username and password.

2 Import SIP URI data for those users.

Import SIP URI Data

After you enable and configure SIP, you must import your endpoint SIP URI information from your SIP server. The SIP URI is used as the endpoint’s
address.

If you are using Microsoft as your SIP server, you do not need to import SIP URI data. The
RealPresence Resource Manager system can retrieve the SIP URI from the enterprise directory.

To import SIP URI data:

1 Create a CSV file in the format described here. The import requires a CSV file in the following format:

domain,username,deviceType,SIPURI,devicename

where:

Ø domain—Specifies the domain the user uses to log in to the RealPresence Resource Manager system.

Ø username—Specifies the RealPresenceRealPresence Resource Manager system user name.

Ø deviceType—Specifies the device type (valid values are HDX, VVX, CMADesktop, RPMobile, RPDesktop, GroupSeries or All_Types).

Ø SIP URI—Specifies the SIP URI for this user.

For example, this import reserves the SIP URI [email protected] for all device types for the John Doe user:

local,johndoe,All_Types,[email protected]

2 From the RealPresence Resource Manager system, go to User > Users.

a Go to More > Import User Aliases.

b Navigate to the CSV file, select it, and click Open.

Editing SIP URI Data

Whenever you add new users or rooms or need change a SIP URI, you must provide SIP URI data. For the methods available for editing the SIP URI

You can edit SIP URI data in either of the following ways:

¿ Upload a CSV file that has changes or new data. Data in the CSV file is added to any existing data.

¿ Edit individual users or rooms. For each RealPresence Resource Manager system user or room, you can add or edit the SIP URI in the Dial String
Reservations section of the Edit User or Edit Room dialog.

Provision SIP Settings for SIP Server Integration

SIP settings are dynamically provisioned with a network provisioning profile. This procedure describes how to change existing network provisioning
settings so that they provision integration with a SIP server.

Be sure to enable SIP and configure the servers, protocol, and credentials needed for your SIP sever.
To provision SIP for integration with a SIP server:

1 Go to Endpoint > Dynamic Management > Provisioning Profiles.

2 Select the Network Provisioning Profile you want to edit and click .

3 In the Edit Profile dialog, click SIP Settings and select these options.

Fields Description

Enable SIP Specify whether to enable SIP calls.

Automatically The RealPresence Resource Manager system will issue a DNS


Discover SIP query to locate the SIP server and provision that information
Servers to endpoints.

Specify the IP address or DNS name of the SIP proxy server for
Proxy Server
the network.

Backup Proxy Specify the IP address or DNS name of a backup proxy server
Server for the network.

Specify the IP address or DNS name of the SIP registrar server


for the network.

• In an Microsoft Office Communications Server 2007 or


Microsoft Skype For Business Server 2010 environment,
Registrar specify the IP address or DNS name of the Office
Server Communications Server or Skype For Business Server server.

• If registering a remote HDX system with an Office


Communications Server Edge Server or Skype For Business
Server Edge Server, use the fully qualified domain name of the
access edge server role.

Backup
Specify the IP address or DNS name of a backup SIP registrar
Registrar
server for the network.
Server

Indicates the protocol the system uses for SIP signaling. The
SIP network infrastructure determines which protocol is
required.

• Auto enables an automatic negotiation of protocols in the


following order: TLS, TCP, UDP. This is the recommended
setting for most environments.
Transport
Protocol • TCP provides reliable transport via TCP for SIP signaling.

• UDP provides best-effort transport via UDP for SIP signaling.

• TLS provides secure communication of the SIP signaling. TLS


is available only when the system is registered with a SIP
server that supports TLS. When you choose this setting, the
system ignores TCP/UDP port 5060.

Specify the SIP server type.

• Standard:

• Polycom:

• Avaya:

• BroadSoft:
Server Type
• Cisco:

• Microsoft: If you are integrating with a Microsoft Server, you


must also provision a group for the endpoint, see Provision
Group for Microsoft Skype For Business or Microsoft Office
Communications Server Integration.

• Siemens:
Verify Enable this option when the endpoint system’s certificate
Certificate should be verified by the certificate authority.

Use Endpoint Enable this option when the endpoint system should use the
Provisioning credentials the user entered at the endpoint to use for
Credentials authenticate when registering with a SIP registrar server.

Specify the name to use for authentication when registering


Common SIP with a SIP registrar server, for
User Name example, [email protected]. If the SIP proxy requires
authentication, this field and the password cannot be blank.

Use
Enable this option with the endpoint should use the SIP URI of
Enterprise
the enterprise user (domain user).
URI

Common SIP Specify the password that authenticates the system to the
Password registrar server.

4 Click OK.

5 You need to ensure that you have created a provisioning rule that applies this network provisioning profile to the intended site and endpoints.

You might also like