[Index]

Model: relation/CallPickupGroups

Add a Call Pickup Group

Use this procedure to add a call pickup group in VOSS-4-UC.

  1. Log in as provider, reseller, customer, or site administrator.

  2. Set the hierarchy to the Customer or Site level.

  3. Choose the Network Device List only if you have set the hierarchy to Customer level. For Site level this step is not required.

  4. Choose Subscriber Management > Call Pickup Groups.

  5. Click Add on the button bar to open the Call Pickup Groups input form.

  6. On the Call Pickup Group tab, enter the Name and a Description.

  7. From the Call Pickup Group Number drop-down, choose the pickup group pilot number.

  8. From the Route Partition Name drop-down, choose the required route partition.

  9. From the Pickup Notification drop-down, choose the method (No Alert, Audio Alert, Visual Alert or Audio and Visual Alert, and then enter the required Pickup Notification Timer period (in seconds).

  10. If the Call Pickup Group is associated with other pickup groups, click the + next to Call Pickup Groups to expose the Pickup Group Name. This allows users to pick up incoming calls in a group that is associated with their own group.

    Note that the first member is automatically added, so there is no need to specify the first member as itself in an Add request.

    1. For included Pickup Group Names, ensure that the Priority always starts at 1. When more than one included group exists, the group with Priority 1 has the highest the priority of answering calls for the associated group. Integer values are added in order of priority.
    2. The associated Directory Name and Partition is automatically selected, based on the Call Pickup Group Name.
    3. Set any required Pickup Notification settings.

  11. On the Member Lines tab, click the + (Add) button next to Line to expose the Line section.

  12. Choose a Directory Number from the drop-down. The Route Partition Name is automatically selected, choose a different Route Partition if necessary. Call Pickup Group members will only be successfully added if their directory number exists in a valid route partition. Directory numbers in a 'null' route partition, appear as selectable members, but saving them results in an error.

  13. Repeat steps 11 and 12 to add more members to the Call Pickup Group.

  14. Click Save on the button bar when complete to save the Call Pickup Group.

Note

If you are using partitions with the call pickup numbers, ensure that the directory numbers that are assigned to the call pickup group have a Calling Search Space that includes the appropriate partitions. We recommend using CU{macro}-PreISR-PT partition for the call pickup groups added at the customer hierarchy.

The selected Call Pickup Groups drop-down lists the call pickup groups created at the customer and the site level. Select the required call pickup group from both the customer and the site level.

Adding a Call Pickup Group at customer level with members across child sites, succeeds without error, and the configuration is pushed to the associated Unified CM. However, when viewing the Call Pickup Group configuration after it was added, the added members will not be seen. Added members are only seen if the Call Pickup Group and its members are at the same hierarchy level.

Verify the individual Member Line association with the Call Pickup Groups by navigating to Subscriber Management > Lines. The Call Pickup Group under Lines displays associated Call Pickup Group.

Delete a Call Pickup Group

Use this procedure to delete a call pickup group in VOSS-4-UC.

  1. Log in as provider, reseller, customer, or site administrator.
  2. Set the hierarchy to the Customer or Site level.
  3. Choose Subscriber Management > Call Pickup Groups.
  4. Choose the call pickup group, and then click Delete.

Call Pickup Group related to Lines.

Model Details: relation/CallPickupGroups

Title Description Details
Call Pickup Group Group Assigned by FDP
  • Field Name: Call Pickup Group
  • Type: Object
Name *
  • Field Name: Call Pickup Group.name
  • Type: String
  • Cardinality: [1..1]
Description
  • Field Name: Call Pickup Group.description
  • Type: String
  • Cardinality: [0..1]
Call Pickup Group Number *
  • Field Name: Call Pickup Group.pattern
  • Type: String
  • Cardinality: [1..1]
Route Partition Name
  • Field Name: Call Pickup Group.routePartitionName
  • Type: ["String", "Null"]
  • Target: device/cucm/RoutePartition
  • Target attr: name
  • Cardinality: [0..1]
  • Format: uri
Pickup Notification Default: No Alert
  • Field Name: Call Pickup Group.pickupNotification
  • Type: String
  • Cardinality: [0..1]
  • Default: No Alert
  • Choices: ["No Alert", "Audio Alert", "Visual Alert", "Audio and Visual Alert"]
Pickup Notification Timer Default: 6
  • Field Name: Call Pickup Group.pickupNotificationTimer
  • Type: Integer
  • Cardinality: [0..1]
  • Default: 6
Call Info For Pickup Notification This tag is applicable when Pickup Notification Policy is "Visual Alert" or "Visual or Audio Alert".
  • Field Name: callInfoForPickupNotification
  • Type: ["Object", "Null"]
  • Cardinality: [0..1]
Calling Party Info
  • Field Name: Call Pickup Group.callInfoForPickupNotification.callingPartyInfo
  • Type: Boolean
  • Cardinality: [0..1]
Called Party Info
  • Field Name: Call Pickup Group.callInfoForPickupNotification.calledPartyInfo
  • Type: Boolean
  • Cardinality: [0..1]
Included Call Pickup Groups On Addition always the first member added is itself. Do not specify the first member as itself in an Add request . Also make sure that the priority always starts with 1. It will internally be taken care of during Addition and Updation.
  • Field Name: members
  • Type: ["Object", "Null"]
  • Cardinality: [0..1]
Call Pickup Group
  • Field Name: member.[n]
  • Type: Array
Pickup Group Name
  • Field Name: Call Pickup Group.members.member.[n].pickupGroupName
  • Type: ["String", "Null"]
  • Target: device/cucm/CallPickupGroup
  • Target attr: name
  • Cardinality: [0..1]
  • Format: uri
Priority *
  • Field Name: Call Pickup Group.members.member.[n].priority
  • Type: Integer
  • Cardinality: [1..1]
Member Lines Group Assigned by FDP
  • Field Name: Member Lines
  • Type: Object
Line
  • Field Name: Line.[n]
  • Type: Array
Directory Number * Enter a dialable phone number. Values can include route pattern wildcards and numeric characters (0 through 9). Special characters such as a question mark (?), exclamation mark (!), backslash (\), brackets ([ ]), plus sign (+), dash (-), asterisk (*), caret (^), pound sign (#), and an X are also allowable. Special characters that are not allowed are a period (.), at sign (@), dollar sign ($), and percent sign (%). At the beginning of the pattern, enter \+ if you want to use the international escape character +. For this field, \+ does not represent a wildcard; instead, entering \+ represents a dialable digit. Note    When a pattern is used as a directory number, the display on the phone and the caller ID that displays on the dialed phone will both contain characters other than digits. To avoid this, Cisco recommends that you provide a value for Display (Internal Caller ID), Line text label, and External phone number mask. The directory number that you enter can appear in more than one partition. If you configure this field under Call Routing > Directory Number, you can enter insert directory numbers in bulk by entering a range (that is, by entering the beginning directory number in the first field and by entering the ending directory number in the second field); by using this method, you can create up to 500 directory numbers at a time.
  • Field Name: Member Lines.Line.[n].pattern
  • Type: String
  • Cardinality: [1..1]
Route Partition Choose the partition to which the directory number belongs. Make sure that the directory number that you enter in the Directory Number field is unique within the partition that you choose. If you do not want to restrict access to the directory number, choose <None> for the partition. You can configure the number of partitions that display in this drop-down list box by using the Max List Box Items enterprise parameter. If more partitions exist than the Max List Box Items enterprise parameter specifies, the Find button displays next to the drop-down list box. Click the Find button to display the Find and List Partitions window, then find and choose a partition name. Note    To set the maximum list box items, choose System > Enterprise Parameters and choose CCMAdmin Parameters.
  • Field Name: Member Lines.Line.[n].routePartitionName
  • Type: ["String", "Null"]
  • Target: device/cucm/RoutePartition
  • Target attr: name
  • Cardinality: [0..1]
  • Format: uri