Shared Line handling
|
-
In a set up where you have a shared desk phone with a CMC RD and Spark RD associated , when a user calls from an enterprise
phone to a CMC Device DN, all the three - CMC RD, Spark RD and the Shared desk phone rings.
-
Answering from any of the remote destinations displays the message “Remote in Use” on the shared desk phone.
-
Answering from any of the shared desk phone disconnects both remote destination phones (CMC RD and Spark RD phones).
|
CMC Device to work in Call Manager Group (CMG) Setup
|
-
When a CMC device is associated with a Call Manager group, it always runs on primary server and runs on the next active secondary
server of the Call Manager Group only if the primary server is down.
-
If the primary server goes down mid call, then the ongoing call is still preserved and after the call ends, the CMC device
registers to secondary server.
Note
|
When the call is in preserved mode, media between the phones still remains active, but no other actions can be performed except
disconnecting the call.
|
-
If the Primary server was down initially and call was initiated while the CMC device was registered to Secondary server and
then the Primary server comes up during ongoing call, the call will go into preservation mode and after the call ends the
CMC device registers to Primary server.
|
Call Anchoring
|
All the basic incoming calls from the CMC device and Number to Remote Destination calls are anchored in the enterprise network.
When the CMC Remote Device is configured, users can place and receive calls from their mobile device with all calls being
anchored to the enterprise:
-
A user can dial directly to a CMC Remote destination from an Enterprise number.The call is anchored in the enterprise network.
In this scenario, the desk phone(shared line of CMC device) does not ring, but remains in Remote in Use state.
-
A user can dial from CMC Remote destination to any Enterprise number. The call is anchored. In this scenario, the desk phone
(shared line of CMC device) remains in Remote in Use state.
|
Single Number Reach
|
-
In the Remote Destination configuration page, if the Enable Single Number Reach checkbox is unchecked, the call do not get extended to the CMC RD and the call gets rejected.
-
The incoming calls from Remote Destination and the outbound Number to Remote Destination calls do not get affected irrespective of the Enable Single Number Reach checkbox selection.
-
If there is shared desk phone with the CMC device and if the Enable Single Number Reach checkbox is unchecked, then the call gets extended to the shared desk phone but not to the CMC RD.
Note
|
If the Single Number Reach Voicemail Policy is set to user control the mobility destination number will NOT be triggered in the event of a Blind transfer to the primary extension. Only the primary extension will be triggered.
User control setting supports consult transfers. Timer Control Voice mail avoidance policy supports both Consult and Blind transfer.
|
|
Call Routing based on Time of Day (ToD)
|
-
You can use the Time of Day configurations for the Remote Destination to set up a ring schedule (for example, you can configure
specific times such as Monday - Friday between 9 am and 5 pm). Calls will only be redirected to your Remote Destination at
those times.
Call from the Enterprise phone to CMC number gets routed based on the Ring Schedule fixed in the Remote Destination configuration
page. Ring Schedule can be specified as below:
-
All the Time – Call gets routed at any time. There is no restrictions.
-
Day(s) of the week – Calls get routed only on the selected specific day.
-
Specific time - Calls get routed only in the selected office hours. Make sure to select the Time Zone.
-
When receiving a call during the Ring schedule, call from the Enterprise phone to CMC number gets routed based on the call
number or pattern added in the Allowed access list or Blocked access list in the Remote Destination configuration page.
-
Allowed access list- Destination rings only if the caller number or pattern is in the Allowed access list.
-
Blocked access list- Destination do not ring if the caller number or pattern is in the Blocked access list.
Note
|
At any point of time, only Allowed access list or Blocked access list can be used.
|
|
User Locale settings
|
The CMC Virtual Device uses the locale settings that are configured in the Phone Configuration window to determine locale
for the phone display and phone announcements. This policy works for regular calls, and for calls to a Conference Now number.
For the announcement part, when calling (any enterprise phone) and called (CMC device) phone with same language selected in
User locale settings, the announcement on both calling and Remote Destination is based on the User Locale settings selected
in the Phone configuration page.
Note
|
For example, when calling from a Remote Destination which is associated with a CMC device, to a Conference Now number, the announcement is based on the User Locale settings selected in the Phone configuration page of the CMC device.
|
|
New Access code for HLogin and HLogout
|
This functionality helps the administrator to set the Hunt Group Login and Logout number for the CMC device using the added
service parameters:
When a user enters the Hlogin number from the RD associated to a CMC device, only then the calls will get redirected to the
RD on dialing the hunt pilot number associated with the CMC device.
When a user enters the Hlogout number from the RD associated to a CMC device, then the calls will not get redirected to the
RD on dialing the hunt pilot number associated with the CMC device.
By default the CMC device is Hloggedin. In either case, a direct call to the CMC device is not affected.
|
CMC Remote Destination call extention based on delay before ringer timer configured in Database
|
- If delay before ringing timer in DB is configured as 5000
-
-
When called from an Enterprise phone to CMC number, the shared line rings and the call reaches the Remote Destination after
five seconds.
-
When called from an Enterprise phone to CMC number, if the shared line answers the call before five seconds, the call do not
get extended to Remote Destination.
-
When called from Enterprise phone to CMC number, the shared line rings and if the calling party disconnects the call before
five seconds, the call do not get extended to Remote Destination.
- If delay before ringing timer in DB is configured as 0
-
Any call from Enterprise phone to CMC number will alert the Remote Destination and the shared line at the same time.
|
Bulk Administration Tool (BAT) Support
|
BAT support is provided for CMC device
|