[Index]

Model: view/RS_SetupReg_VIEW

Using PBR Setup feature to configure a CUCM

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Related Topics

Using PBR Setup to configure a Cisco Unified CM

The PBR Setup feature automates the configuration of Unified CM for AutoRegistration and Phone Based Registration.

In VOSS Automate, browse to Services > Phone Based Registration > PBR Setup. The following input is required:

VOSS recommends that initial configuration of the Unified CM is performed using the PBR Setup workflow described above. In cases where there is existing auto registration config on the Unified CM, it may be required to do this manually.

Important

The Services Provisioning value under Enterprise Parameters Configuration - Parameter Name on the associated Unified CM must be set to Both.

Configuration on Cisco Unified CM

VOSS Automate Phone Based Registration (PBR) requires the following functionality to be configured on Cisco Unified CMs that manage phones which may be registered by this feature:

  1. Configure the Unified CM to allow AutoRegistration of new phones. This is standard auto registration config for Unified CM. The PBR Setup in VOSS Automate carries out this configuration.
  2. When a phone Auto Registers the phonereg phone service should be configured for the phone. This is achieved by specifying a Universal Device Template for Auto Reg that subscribes to the phonereg phone service.

Screenshots of the relevant configuration on Unified CM are provided to assist with understanding how the service is implemented and as background for a Cisco expert that may need to fine tune the Unified CM config.

  1. Setup the phonereg Phone Service:

    Browse to Device > Device Settings > Phone Services.

    172.30.11.126

    Service URL:

    Depending on whether HTTPS or HTTP is used the service URL may be different:

    Note

    The port must always be specified explicitly.

  2. Configure phonereg Universal Device Template:

    1. Browse to User Management > User/Phone Add > Universal Device Template.
    2. Note the subscription to the phonereg Phone Service.

  3. Unified CM for Auto Registration:

    1. Browse to System > Cisco Unified CM.
    2. Note the phonereg Universal device template.

PBR Setup - Configure CUCM for PBR

Full HTML Help

This section describes phone-based registration (PBR) setup.

Related Topics

The flowchart provides the steps for this task:

To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html

Using PBR Setup to Configure a CUCM

Use the PBR Setup menu to automates the configuration of Cisco Unified Communications Manager (CUCM) for AutoRegistration and Phone Based Registration.

  1. In the VOSS Automate Admin portal, go to (default menus) Services > Phone Based Registration > PBR Setup.
  2. Configure the following:
Setting Description
CUCM IP Address IP Address of the publisher for the CUCM cluster.
Call Manager Group for Auto Reg Name of CUCM group for AutoReg.
Call Manager for Auto Reg Name of the Call Manager for AutoReg (as specified under Services > Phone Based Registration > CUCM Call Managers).
First and Last Directory Number for Autoreg A valid range of DNs to be used for Auto Registration.
PBR Portal Address The IP Address of VOSS cluster UN1 .
PBR Portal Port 8412

VOSS recommends that initial configuration of the CUCM is performed using the PBR Setup workflow described above. In cases where there is existing auto-registration config on the CUCM, it may be required to do this manually.

Important

Set the Services Provisioning value (under Enterprise Parameters Configuration - Parameter Name on the associated CUCM) to Both.

Configuration on CUCM

VOSS Automate Phone Based Registration (PBR) requires the following functionality to be configured on CUCMs that manage phones which may be registered by this feature:

  1. Configure the CUCM to allow AutoRegistration of new phones.

    This is standard auto registration config for CUCM. The PBR Setup in VOSS Automate carries out this configuration.

  2. When a phone Auto Registers the phonereg phone service should be configured for the phone. This is achieved by specifying a Universal Device Template for Auto Reg that subscribes to the phonereg phone service.

Screenshots of the relevant configuration on CUCM are provided to assist with understanding how the service is implemented and as background for a Cisco expert that may need to fine tune the Unified CM config.

  1. Setup the phonereg Phone Service:

    Browse to Device > Device Settings > Phone Services.

    172.30.11.126

    Service URL:

    Depending on whether HTTPS or HTTP is used the service URL may be different:

    Note

    The port must always be specified explicitly.

  2. Configure phonereg Universal Device Template:

    1. Browse to User Management > User/Phone Add > Universal Device Template.
    2. Note the subscription to the phonereg Phone Service.

  3. CUCM for Auto Registration:

    1. Browse to System > Cisco Unified CM.
    2. Note the phonereg Universal device template.

Set up phone based registration

Model Details: view/RS_SetupReg_VIEW

Title Description Details
CUCM IP Address * This is the IP of the Call Manager Publisher
  • Field Name: cucm_address
  • Type: String
Call Manager Group for Auto Reg * The Call Manager group to use for Auto Reg
  • Field Name: cm_group
  • Type: String
Call Manager for Auto Reg * This is the name of the Call Manager Node to be used for AutoReg
  • Field Name: cm
  • Type: String
First Directory Number for auto registration * First Directory Number for auto registration
  • Field Name: start_dn
  • Type: String
  • MaxLength: 8
Last Directory Number for auto registration * Last Directory Number for auto registration
  • Field Name: end_dn
  • Type: String
  • MaxLength: 8
Phone Registration Portal Address * Phone Registration Portal Address
  • Field Name: portal_address
  • Type: String
  • Format: ip-address
Phone Registration Portal Port * Phone Registration Portal Port
  • Field Name: portal_port
  • Type: String