UCM6xxx – Service Guide

  • Updated on October 31, 2024

The UCM6xxx series comes with a variety of services and features that facilitate communication between users and enhance call efficiency. This guide describes essential services such as voicemail, call waiting, ring group, and more.

CALLER ID

Description

Caller ID is a service that transmits caller information to the called party’s device, allowing the callee to know who is calling before deciding whether or not to answer a call.

Getting Started

The Caller ID feature is available by default on the UCM. To use it:

  1. Make sure that either the trunk, extension or the UCM itself has a CID configured in their corresponding configuration pages.
  2. UCM’s Outbound CID priority is as follows:

From User (Register Trunk Only) > CID from inbound call (Keep Original CID Enabled) > Trunk Username/CallerID > (Keep Trunk CID Enabled) > DOD > Extension CallerID Number > Trunk Username/CallerID (Keep Trunk CID Disabled) > Global Outbound CID.

Using the Service

Assuming the following:

  • A is an extension registered to UCM 1.
  • B is an extension registered to UCM 2.
  • A has CID number “1000” and CID name “John Bob”.
  • UCM 1 is peered with UCM 2.
  • UCM 1’s peered trunk has CID number “123” and CID name “GS”.
  • UCM 2’s peered trunk has Keep Original CID enabled.

The service can be used as such:

  1. A calls B.
  2. B’s endpoint rings and displays A’s CID number “123” and CID name “GS”.

Due to CID priority, UCM 1’s CID information overrides A’s CID information, because UCM 2 enabled Keep Original CID, UCM 1’s CID information was preserved and passed along to B.

Miscellaneous

Some countries may not include CID information in calls over analog lines, potentially resulting in call failures when the UCM tries to look for the information in incoming calls.

CALL HOLDING

Description

Call holding is a feature that allows a person to pause and resume an ongoing call without terminating the line.

Getting Started

The call-holding feature is available by default on the UCM. No additional configuration is necessary.

Using the Service

Assuming the following:

  • A and B are extensions registered to the UCM.

The service can be used as such:

  1. B calls A.
  2. A starts ringing and picks up the call.
  3. The call between A and B is established.
  4. A presses the hold button.
  5. B is now on hold. Music on Hold may or may not play depending on the system’s configuration. No audio from either party can be heard.
  6. A presses the hold button again to retrieve the call.
  7. A and B can hear each other again.

Miscellaneous

If no Music on Hold is heard, or if calls cannot be retrieved, navigate to PBX Settings → SIP Settings → Misc and check if the “Forward HOLD Requests” option is enabled. If so, disable the option and try again.

CALL FORWARDING

Description

Call forwarding is a feature that allows an endpoint to redirect calls to another phone number or extension, minimizing the chances of a call going unanswered.

Getting Started

There are two ways to configure the Call Forwarding feature, either from the UCM itself or by dialing the feature codes from the endpoints.

To enable call forwarding from the UCM63xx please follow the steps below:

  1. Navigate to Extension/Trunk → Edit Extension and navigate to the Features tab.
  2. Configure the Call Forward Always, Call Forward No Answer, and Call Forward Busy fields with the desired settings.

To configure call forwarding using feature codes please navigate to Basic Call Features → Feature Codes and click on the DND/Call Forward tab. This allows users to enable and disable specific call-forwarding settings by entering a code.

Advanced Call Forward:

If Advanced is selected under “Call Forward Setting Type”, users will be able to set call forwarding for all calls, internal calls and external calls by dialing one of the call forwarding feature codes followed by the code modifiers 0, 1, or 2 which correspond to:

  • 0 – All Calls
  • 1 – Internal Calls (calls within the UCM) 
  • 2 – External Calls (calls from outside the UCM) 

Using Call Forward Always

Call Forward Always redirects all calls immediately to the configured destination.

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A has Call Forward Always set up to redirect calls to B.

The service can be used as such:

  1. C calls A.
  2. A does not ring, and the call is redirected to B.
  3. B rings and picks up the call.
  4. The call between B and C is established.

Using Call Forward No Answer

Call Forward No Answer redirects calls upon ring timeout to the configured destination.

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A has a Ring Timeout of 10 seconds.
  • A has Call Forward No Answer set up to redirect calls to B.

The service can be used as such:

  1. C calls A.
  2. A rings for 10 seconds.
  3. A stops ringing, and the call is redirected to B.
  4. B starts ringing and picks up the call.
  5. Call between B and C is established.

Using Call Forward Busy

Call Forward Busy redirects calls to the configured destination if the called line is busy.

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • C and D are out-office POTS phones.
  • A has Call Forward Busy set up to redirect calls to B.

The service can be used as such:

  1. C calls A.
  2. A starts ringing and picks up the call.
  3. Call between A and C is established.
  4. D calls A, and the call is redirected to B. The call between A and C receives no interruptions.
  5. B starts ringing and picks up the call.
  6. Call between B and D is established.
Note:

Call Forward Busy will not work if the Call Waiting service is enabled.

CALL TRANSFER

Description

Call transfer is a function that allows users to manually redirect calls to another recipient. This allows for a call participant to talk to an appropriate party without having to make a new call.

Getting Started

Call Transferring is available by default on the UCM. To use it:

  1. Make sure the feature codes for Blind Transfer, Attended Transfer, and Seamless Transfer are configured in Basic Call Features → Feature Codes → Feature Maps and that they are not disabled.
  2. The following transfer types are available:
    1. Blind Transfer – After dialing the number to transfer to, the transferring party is immediately disconnected. During this transfer process, music on hold will play for the transferred party. The default feature code is #1.
    2. Attended Transfer – After dialing the number to transfer to, the transferring party places the current call on hold and rings the new recipient. Generally, the transferring party confirms that the recipient is available before completing the attended transfer. The default feature code is *2.
    3. Seamless Transfer – After dialing the number to transfer to, the existing call will continue until the transfer recipient picks up. The transferring party will be disconnected upon pickup. No music on hold will play during the transfer process, and the transferred party will receive no indication of being transferred. This gives the impression of the transferring party physically handing the phone over to another party. The default feature code is *44.

Making a Blind Transfer

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • The blind transfer feature code is set to “Allow Both”.
  • #1 is the configured feature code to initiate a blind transfer.

The service can be used as such:

  1. A dials B.
  2. B rings and answers the call.
  3. A and B can hear and talk to each other.
  4. A dials #1.
  5. B hears music on hold.
  6. A dials C.
  7. A is disconnected from the call.
  8. C rings and answers the call.
  9. B and C can hear and talk to each other.

Making an Attended Transfer

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • The attended transfer feature code is set to “Allow Both”.
  • *2 is the configured feature code to initiate an attended transfer.

The service can be used as such:

  1. A dials B.
  2. B rings and answers the call.
  3. A and B can hear and talk to each other.
  4. A dials *2.
  5. B hears music on hold.
  6. A dials C.
  7. C rings and answers the call.
  8. A and C can hear and talk to each other.
  9. A hangs up the call.
  10. B is connected with C.
  11. B and C can hear and talk to each other.

Making a Seamless Transfer

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • 1200 is C’s extension number.
  • The seamless transfer feature code is enabled.
  • *44 is the configured feature code to initiate a seamless transfer.

The service can be used as such:

  1. A dials B.
  2. B rings and answers the call.
  3. A and B can hear and talk to each other.
  4. A dials *441200.
  5. C rings.
  6. The call between A and B is still ongoing.
  7. C answers the call.
  8. A is disconnected from the call.
  9. B and C can hear and talk to each other.

VOICEMAIL

Description

Voicemail is a service that allows callers to leave behind a voice message for an unavailable user. These voice messages can then be managed by the user.

Getting Started

The Voicemail feature is available by default on the UCM. To use it:

  1. Navigate to Extension/Trunk Edit Extension Basic Settings.
  2. Check the Voicemail option and select “Enable Local Voicemail”.
  3. Navigate to the Features tab and configure at least one Call Forward destination with “Voicemail”.
  4. If using Call Forward No Answer to forward to voicemail, make sure that the Ring Timeout option on the same page has a value configured.
  5. Navigate to Basic Call Features Feature Codes Feature Codes and make sure that Voicemail Access Code and My Voicemail options are enabled and have values configured (*98 and *97 by default respectively).
  6. Voicemail count can be viewed from the Extensions page and is formatted as Urgent/Total/Read.
  7. (Optional) If a user wants to be able to access the voicemail management system via an external device, navigate to Basic Call Features Voicemail Voicemail and enable Voicemail Remote Access. This prompt will not play for internal calls.
Warning

Enabling this will replace the default “Leave a Message” voicemail prompt with one that will give the caller the option to access an extension’s voicemail management system. This poses potential security risks and is recommended to be disabled if unused.

Leaving a Voice Message

Assuming the following:

  • A and B are extensions registered to the UCM.
  • B has the following configuration:
    • Voicemail: Enable Local Voicemail
    • AvailableCall Forward No Answer set to Voicemail
    • Ring Timeout: 3

The service can be used as such:

  1. A calls B.
  2. B starts ringing.
  3. B stops ringing after 3 seconds.
  4. A hears B’s voicemail prompt.
  5. A leaves a voice message and hangs up.
  6. Extensions page will show B’s voicemail count as 0/1/0
  7. If supported, B’s endpoint will indicate one unread voicemail.

Managing Voicemail with Personal Extension

Assuming the following:

  • A is a SIP extension registered to the UCM.
  • My Voicemail feature code is *97.
  • A has 1 unread voicemail.

The service can be used as such:

  1. A dials *97.
  2. A hears the UCM voicemail management prompt asking for the voicemail password.
  3. A enters his voicemail password.
  4. A hears all the voicemail management options.
  5. A presses 1 to listen to new messages.
  6. A presses 7 to delete the message.
  7. A hangs up the call.
  8. The extensions page will show A’s voicemail count as 0/0/0.

Managing Voicemail with Wave

Note

Please note that this feature is available on the UCM63xx/A series only.

Upon receiving a voicemail, users can listen, download, or delete a voicemail.

To access your voicemail, please log in with your account credentials on Wave web or desktop client, and go to Calls → Voicemail.

Managing Voicemail from a Different Extension

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • The voicemail Access Code feature code is *98.
  • A has 1 unread voicemail.

The service can be used as such:

  1. B dials *98.
  2. B hears the UCM voicemail management prompt asking for an extension number.
  3. B enters A’s extension number.
  4. B hears the UCM voicemail management prompt asking for A’s voicemail password.
  5. B enters A’s voicemail password.
  6. B hears all the voicemail management options.
  7. B presses 1 to listen to A’s new messages.
  8. B presses 7 to delete A’s message.
  9. B hangs up the call.
  10. The extensions page will show A’s voicemail count as 0/0/0.

Managing Voicemail from an Outside Line

Assuming the following:

  • Voicemail Remote Access is enabled in the Basic Call Features Voicemail Voicemail page.
  • A is a SIP extension registered to the UCM.
  • A does not have any call forwarding to voicemail configured.
  • A has a ring timeout of 3.
  • A has 1 unread voicemail
  • C is an external POTS line.
  • UCM has an analog trunk configured to make and receive PSTN calls.
  • An IVR extension is configured to allow the direct dialing of extensions.
  • An inbound route is configured for calls to the analog trunk to be routed to IVR.

The service can be used as such:

  1. C dials UCM’s PSTN number.
  2. C hears the IVR’s welcome prompt.
  3. C dials A’s extension.
  4. A rings for 3 seconds.
  5. C hears a prompt to press 1 to leave a voicemail for A or 2 to enter voicemail management.
  6. C dials 2.
  7. C hears the UCM voicemail management prompt asking for an extension number.
  8. C dials A’s extension number.
  9. C hears the UCM voicemail management prompt asking for A’s voicemail password.
  10. C enters A’s voicemail password.
  11. C hears all the voicemail management options.
  12. C presses 1 to listen to A’s new messages.
  13. C presses 7 to delete A’s message.
  14. C hangs up the call.
  15. The extensions page will show A’s voicemail count as 0/0/0.

Miscellaneous

The “Enable Remote Voicemail” option supports only Informatec’s remote voicemail system.

CALL WAITING

Description

Call waiting is a feature that allows a person to receive calls even while already in an existing call. The person will hear a notification tone signaling that another call is coming in.

Getting Started

The call-holding feature is available by default on the UCM. To use it:

  1. Navigate to Extension/Trunk Edit Extension and navigate to the Features tab.
  2. Check the Call Waiting option.

Using the Service

Assuming the following:

  • A, B, and C are extensions registered to the UCM.

The service can be used as such:

  1. B calls A.
  2. A starts ringing and picks up the call.
  3. Call between A and B is established.
  4. C calls A.
  5. A hears a notification tone.
  6. C will continue to hear a ringback tone.

Miscellaneous

Enabling the Call Waiting service will cause Call Forward No Answer rules to be ignored.

CALL PARKING

Description

Call parking is a feature that allows a person to place a call on hold with one device and resume it from a different device. When the call is placed on hold, the UCM temporarily moves the call to a special extension on the UCM (hence “parking” the call) that can be dialed for retrieval. The range of extensions that are dedicated to parked calls is called the “Parking Lot”.

Getting Started

The Call Parking feature is available by default on the UCM. To use it:

  1. Make sure that there is a feature code configured for it in Basic Call Features Feature Codes Feature Maps and that it is not disabled. The default feature code is #72.
  2. Create a Parking Lot and configure it with the desired settings. Use parklot as an extension may need to be checked for the service to work properly.

Using the Service

Assuming the following:

  • A and B are extensions registered to the UCM.
  • C is an out-of-office POTS phone
  • 700 is the created parking lot with 701-710 as the available extension range to park in

The service can be used as such:

  1. C calls A.
  2. A picks up, and the call is established.
  3. A dials #72 and enters 701 after the prompt.
  4. C is now parked on extension 701 and hears hold music.
  5. B dials 701 to retrieve C.
  6. Call between B and C is established.

If C is not retrieved after the configured timeout period, C can either be routed back to A (default behavior) or be forwarded to another destination (requires Failover Destination to be configured).

DO NOT DISTURB

Description

Do-Not-Disturb (DND) is an extension state that blocks all incoming calls to the extension. All call forwarding settings will be ignored while in this state.

Getting Started

Do-Not-Disturb is available by default on the UCM. To use it:

  1. Make sure the feature codes to enable and disable the state are configured in Basic Call Features Feature Codes DND/Call Forward and that they are not disabled. The default feature codes to activate and disable it are *77 and *78 respectively.
  2. (Optional) Configure a time condition for when DND is active on the Extension/Trunk Extensions Features page.

Using the Service

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • *77 is the feature code to enable DND.
  • *78 is the feature code to disable DND
  • All extensions do not have DND currently active.

The service can be used as such:

  1. A dials *77 to enable DND.
  2. B calls A.
  3. B hears a message saying that A is unavailable.
  4. A dials *78 to disable DND.
  5. B calls A again.
  6. A picks up.
  7. A and B can now hear and talk to each other.

Miscellaneous

Do-Not-Disturb state can also be toggled in the UCM web portal.

CALL PICKUP

Description

Call Pickup allows a user to pick up calls on behalf of other extensions via feature codes. Users can also be members of Pickup Groups to simplify the call pickup process.

Getting Started

The Call Pickup feature is available by default on the UCM. To use it:

  1. Navigate to the Basic Call Features → Feature Codes → Feature Codes page and make sure the Call Pickup on Ringing, Pickup In-call, and Pickup Extension feature codes are configured and enabled.
  2. (Optional) Navigate to the Basic Call Features → Pickup Groups page and make sure there is an available pickup group. If there are none, create a new one and add members to it.

Pickup a Call for an Extension

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • C is an out-of-office POTS extension.
  • Call Pickup on Ringing feature code is **

The service can be used as such:

  1. C dials A.
  2. A rings.
  3. B dials ** and A’s extension number to pick up the call.
  4. B and C can now hear and talk to each other.

Pickup In-Call

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • C is an out-of-office POTS extension.
  • Pickup In-Call feature code is *45
  • B is included in A’s Seamless transfer privilege control list.

The service can be used as such:

  1. A and C are in a call.
  2. B dials *45 and A’s extension.
  3. B and C can now hear each other.
  4. A is no longer part of the call.

Pickup Groups

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • C is an out-of-office POTS extension.
  • A and B are members of the same pickup group.
  • The pickup Extension feature code is *8.

The service can be used as such:

  1. C dials A.
  2. B dials *8 to pick up the call.
  3. B and C can now hear and talk to each other.

Meeting

Description

A Meeting call is a call that allows a user to talk to several people at the same time.

Maximum allowed participants across all Meetings:

Model

Maximum Number of Attendees

UCM6102

25

UCM6104

UCM6202

UCM6204

UCM6108

32

UCM6116

UCM6208

UCM6300A

50

UCM6510

64

UCM6301

75

UCM6302A

UCM6304A

120

UCM6302

150

UCM6308A

UCM6304

200

UCM6308

300

Getting Started

The Meeting feature is available by default on the UCM. To use it:

  1. Navigate to the Basic Call Features → Multimedia Meeting page (Meeting for UCM630xA — Conference/Video Conference for UCM620x and UCM6510) and make sure there is a Meeting room available. If there are none, create a new Meeting room. You can choose to create a random meeting room with specific participants or create a public meeting room that would be accessible to everyone. Or you can schedule a meeting.
  2. Dial the Meeting room extension. For scheduled Meetings, a host password can be configured. Enter the host password if it has been configured on the scheduled meeting. (Use the access password in the case of UCM62xx/6510, this is necessary regardless if the meeting was scheduled or not)
  3. Admins and users (if configured) can dial the following codes during the call to invite other members, merge conferences, and drop connections to other conference rooms:
    • Invites specified users to join the conference via voice prompt upon answering.
      1. Pressing 1 will cause the user to accept the invite and join the conference.
      2. Pressing 2 will cause the user to reject the invite.
    • Bring the specified users into the conference upon answering.
    • Bridges the current conference with the specified conference room. Rooms will continue to be bridged until disconnected.
    • Disconnects all existing bridges to other conference rooms.

Entering a Meeting Call

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A is the Meeting room admin.
  • B and C are Meeting participants.
  • 6300 is a Meeting room extension.

The service can be used as such:

  1. A dials 6300 and enters the host password.
  2. B and C dial 6300 and enter the Meeting room.
  3. A, B, and C can hear and talk to each other.

Inviting Participants

Assuming the following:

  • A, B, C, and D are SIP extensions registered to the UCM.
  • A is the conference room admin.
  • B, C, and D are conference participants.
  • 6300 is a conference room extension.
  • Enable User Invite is enabled in the conference room settings.

The service can be used as such:

  1. A dials 6300 and enters the conference room.
  2. B dials 6300 and enters the conference room.
  3. A and B can hear and talk to each other.
  4. A dials 0 to invite C.
  5. C answers the call and hears the voice prompt.
  6. C presses 1 to join the conference.
  7. A, B, and C can hear and talk to each other.
  8. B dials 1 to invite D.
  9. D answers the call and automatically joins the conference.
  10. A, B, C, and D can hear and talk to each other.

Bridging Conferences

Assuming the following:

  • A, B, C, and D are SIP extensions registered to the UCM.
  • 6300 and 6400 are conference room extensions.
  • A is the admin of conference room 6300.
  • C is the admin of conference room 6400.
  • B and D are conference participants.

The service can be used as such:

  1. A dials 6300 and enters his configured admin password.
  2. B dials 6300 and enters the conference room.
  3. A and B can hear and talk to each other.
  4. C dials 6400 and enters his configured admin password.
  5. D dials 6400 and enters the conference room.
  6. C and D can hear and talk to each other.
  7. A dials 2 to establish a bridge to conference room 6400.
  8. A, B, C, and D can hear and talk to each other.
  9. C dials 3 to disconnect the bridge.
  10. A and B can no longer hear and talk to C and D.

RING SIMULTANEOUSLY

Description

Ring Simultaneously is a feature that allows the UCM to ring an external extension or number while ringing the local extension at the same time.

Getting Started

The call-holding feature is available by default on the UCM. To use it:

  1. Navigate to Extension/Trunk Edit Extension and navigate to the Features tab.
  2. Check the Ring Simultaneously option and configure External Number and Time Condition for Ring Simultaneously.
Note

The UCM’s local extensions cannot be configured as an external number

Using the Service

Assuming the following:

  • A and B are extensions registered to UCM 1.
  • C is an extension registered to UCM 2.
  • UCM 1 and UCM 2 are peered to each other.
  • A has C as its configured Ring Simultaneously number.

The service can be used as such:

  1. B calls A.
  2. A and C start ringing.
  3. C picks up.
  4. A stops ringing.
  5. B and C can hear and talk to each other.

Miscellaneous

If the External Number is configured with a landline or mobile phone number, the original extension will stop ringing after approximately 3 seconds, behaving similarly to a Call Forward No Answer with a ring timeout of 3 seconds.

RING GROUP

Description

Ring Group is a feature that allows several users to be associated with a single extension. By calling this extension, all users in it will ring.

Getting Started

The Ring Group feature is available by default on the UCM. To use it:

  1. Navigate to Basic Call Features Ring Groups and add a ring group.
  2. (Optional) To receive ring group voicemail and email notifications for them, tick the Enable Destination option when editing a ring group, select “Voicemail” and “Ring Group Extensions”, and configure the Password and Email Address fields.

Receiving Calls on a Ring Group

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A and B are part of Ring Group 6000.
  • Ring Group 6000 has “Ring Simultaneously” configured as the ring strategy.

The service can be used as such:

  1. C calls 6000.
  2. A and B start ringing.
  3. B answers the call.
  4. A stops ringing.
  5. B and C can hear and talk to each other.

Receiving Email Notifications and Listening to Ring Group Voicemail

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A and B are part of Ring Group 6000.
  • Ring Group 6000 has “Ring in Order” configured as the ring strategy.
  • Ring Group 6000 has Enable Destination toggled with “Voicemail” and “Ring Group Extensions” as Default Destination and has a configured Password and Email Address.
  • UCM has Voicemail Access Code enabled in the Basic Call Features 🡪 Feature Code s🡪 Feature Codes page.
  • *98 is the configured feature code for Voicemail Access Code.

The service can be used as such:

  1. C calls 6000.
  2. A starts ringing.
  3. A rejects the call.
  4. B starts ringing.
  5. B rejects the call.
  6. C hears the UCM’s voicemail system prompting to leave a voicemail.
  7. C leaves a voicemail and terminates the call.
  8. UCM’s Ring Group overview page shows 0/1/0 in 6000’s Message column.
  9. A and B receive email notifications indicating C’s voicemail to Ring Group 6000.
  10. A dials *98 to access the UCM’s voicemail system.
  11. A dials 6000 when prompted for the voicemail box.
  12. A dials 6000’s voicemail password when prompted for the password.
  13. A presses 1 to listen to C’s voicemail.
  14. A presses 7 to delete C’s voicemail.
  15. A hangs up the call.
  16. UCM’s Ring Group overview page shows 0/0/0 in 6000’s Message column.

FOLLOW ME

Description

Follow Me is a feature that reroutes timed-out calls to a different set of extensions or external numbers.

Getting Started

Follow Me is available by default on the UCM.

To use it:

  1. Navigate to Extension/Trunk → Extensions → Edit Extension Follow Me and tick the Enable checkbox.
  2. Add Follow Me numbers.

Using the Service

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • D is an external POTS line.
  • A configured C and D as its Follow Me numbers with C being the first number on the Follow Me list.
  • Follow Me is configured to dial Follow Me numbers one by one in order with 30-second timeouts each.

The service can be used as such:

  1. B calls A.
  2. A rings until timeout.
  3. B hears a message indicating that the call will be routed to the Follow Me numbers.
  4. C rings until timeout.
  5. B hears the Follow Me message again.
  6. D rings and answers the call.
  7. B and D can hear and talk to each other.

Miscellaneous

Follow Me is not limited to dialing a single number upon triggering. Users can configure a new Follow Me number to ring simultaneously with the previously added number on the list. This allows users to create sets of Follow Me numbers to minimize dropped calls.

CONCURRENT REGISTRATION

Description

Concurrent Registration is a feature that allows an extension to be registered to and used from multiple devices. Each device would use the same registration information to connect but can make separate individual calls regardless of the extension status on other associated devices.

Getting Started

Concurrent Registrations are available by default on the UCM. To use it:

Navigate to Extension/Trunk Extensions Edit Extension Basic Settings and enter in the desired concurrent registrations value.

Using the Service

Assuming the following:

  • A, B, and C are SIP extensions registered to the UCM.
  • A1 is a SIP endpoint registered to A.

The service can be used as such:

  1. B calls A.
  2. Both A and A1 ring.
  3. A answers the call.
  4. A1 stops ringing.
  5. A and B can hear and talk to each other.
  6. A1 calls C.
  7. C starts ringing.
  8. C answers the call.
  9. A1 and C can hear and talk to each other.
  10. A and B’s call is uninterrupted by A1’s call.

Miscellaneous

Concurrent Registrations can be set only to 1 if SCA is enabled.

SHARED CALL APPEARANCE

Description

Shared Call Appearance, or SCA for short, is a feature that allows a user to be associated with several devices in a fashion similar to the Concurrent Registration service. Unlike Concurrent Registrations, however, SCA extensions have the following functions available:

  • Monitoring the extension status via MPK/VPKs
  • Restricting simultaneous calls from associated devices
  • Barging into and picking up existing calls from an associated device.

Getting Started

Shared Call Appearance is available by default on the UCM. To use it:

  1. Navigate to Extension/Trunk → Extensions → Edit Extension → Basic Settings and tick the Enable SCA checkbox.
  2. Navigate to Advanced Call Features SCA SCA Number Group and add a private number to the desired extension. This private number will be used to register devices to be associated with the main extension. To register to a private number, the endpoint must have the following fields configured as such:
    1. SIP User ID: private number
    2. Auth ID: main extension’s Auth ID. If no Auth ID is configured, the main extension’s number will be used instead.
    3. Password: main extension’s SIP password
  3. (Optional) If a SCA extension and its associated private numbers want to be able to barge into each other’s calls, Allow Bridging between Locations in the Advanced Call Features SCA page must be enabled.

Using the Service

Assuming the following:

  • A and B are SIP extensions registered to the UCM.
  • A1 is a SIP endpoint registered to an SCA private number associated with A.
  • A1 has an MPK/VPK configured for SCA.
  • Advanced Call Features → SCA → Allow Call Retrieve from Another Location is enabled.

The service can be used as such:

  1. B calls A.
  2. Both A and A1 ring.
  3. A picks up the call.
  4. A1 stops ringing.
  5. A holds the call.
  6. A1 can see on the configured MPK/VPK that A has held a call.
  7. A1 presses the MPK/VPK to pick up the call.
  8. A’s call is terminated.
  9. B and A1 can hear and talk to each other.

Miscellaneous

To avoid conflicts, Follow Me cannot be enabled alongside SCA, and only one concurrent registration is allowed for the extension when using SCA.

WAKEUP SERVICE

Description

The Wakeup Service is a feature that sends out scheduled calls to specified destinations and is typically used to send out reminders.

Getting Started

Wakeup service is available by default on the UCM. Users can manage wakeup calls through the admin portal, user portal, and feature code as long as they have the proper permissions.

To use it via feature code:

  1. Navigate to Basic Call Features Feature Codes Feature Codes Misc and confirm that the Scheduled Call feature code is enabled and configured. The default Scheduled Call feature code is *36.
  2. Navigate to Basic Call Features Feature Codes Feature Codes PMS and users can enable the PMS Wakeup Service feature code. The default Wakeup Service feature code is *35.
  3. (Only for UCM630x/UCM630xA) Navigate to Basic Call Features Feature Codes Feature Codes PMS and users can enable the PMS Remote Wakeup Service feature code. The default Wakeup Service feature code is *37.
Note:

Permission needs to be given under the Extension → Features → PMS Remote Wakeup Whitelist.

  1. Navigate to Maintenance User Management and confirm permissions for custom privileges. The default privilege levels Super Administrator, Administrator, and Consumer already have Wakeup Service permissions.

Using the Service

Assuming the following:

  • A is a SIP extension registered to the UCM.
  • *36 is the configured Scheduled Call feature code.

The service can be used as such:

  1. A dials *36.
  2. A hears the Wakeup Service management portal prompt.
  3. A presses 1 and follows the voice prompts to create and enable a new wakeup call.
  4. The wakeup service will ring A at the configured date and time.
  5. A answers the scheduled call.
  6. A hears the default wakeup service voice message.
  7. The call is automatically terminated once the voice message is complete.

Miscellaneous

To configure a scheduled/wakeup call to repeat on specific weekdays and to use a custom voice message upon picking up the scheduled/wakeup call, users must use the admin portal and user portal.

Feature Codes Nesting

Description

This feature is exclusive to the UCM6300 series and UCM630 Audio series and it consists of limiting certain codes from being used to avoid confusion and code conflict.

The codes that can’t be nested will be marked with this icon on the Web UI under Basic Call Features 🡪 Feature Codes. This feature is important because there are a few codes that can be used in conjunction with a series of digits.

Example:

  • Users can dial *72 (Call Forward Always Enable) followed by 1000 (*721000) to set the forwarding destination as extension 1000.
  • This may become an issue if there’s another configured feature code that starts with *72.
  • For this example, we will assume that *7210 is the configured feature code for enabling DND.
  • If a user dials *7210, the UCM will not be able to determine whether the user wants to activate DND mode or enable Call Forward Always with extension 10 as the destination.
Notes:

When attempting to configure a feature code that is already taken, users will receive the following error “Feature code conflict with …”. On the other hand, if a user tries to configure a code that can’t be nested, this error message will appear “Unsupported nesting with feature code …”.

Supported Feature Codes

Feature Codes

Nesting

Blind Transfer

Attended Transfer

Seamless Transfer

Disconnect

Call Park

Start/Stop Call Recording

Do Not Disturb (DND) Activate

Call Forward Busy Enable

Call Forward No Answer Enable

Call Forward Always Enable

Do Not Disturb (DND) Deactivate

Call Forward Busy Disable

Call Forward No Answer Disable

Call Forward Always Disable

Voicemail Access Code

Voicemail Group Access Code

My Voicemail

Direct Dial Voicemail Prefix

Agent Pause

Dynamic Agent Logout

Agent Unpause

Pickup on Ringing Prefix

Pickup Extension

Pickup In-call Prefix

Barge Spy

Listen Spy

Whisper Spy

PMS Wakeup Service

Update PMS Room Status

PMS Remote Wakeup Service

Paging Prefix

Blocklist Add

Blocklist Remove

Call Completion Request

Presence Status

Scheduled Call

Remote Extension Privilege Update

 Intercom Prefix

Blocklist Last Caller

Direct Dial Mobile Phone Prefix

Call Completion Cancel

Call Flip

Priority Call


Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Comment