Businessphone management suite 5.1 download

You can quickly access the Charms bar on any Windows 8 computer touch screen or non-touch screen by holding down the Windows key and pressing C. After PowerShell is running, you must change the execution policy to allow the running of remote scripts. PowerShell' is denied. This error message typically occurs if you are not running PowerShell under administrator credentials.

Close your session of PowerShell, and start a new session as an administrator. If you are not currently running Windows PowerShell 5. This is an installation package that includes Windows PowerShell 5. This installation package might be required if you, for example, are running Windows 7 SP1 and have not yet updated to Windows PowerShell 5.

Windows PowerShell 5. Make sure you have downloaded the correct version of the installation package. If you are running the bit version of Windows 7, download the file Win7-KBx This is performed by the PBX and can be configured.

This situation is actually unwanted, since the BCT Operator performs this action via their own terminal. ReCall from a party that is transferred but other party didnt answer within time-out.

The BCT operator can break-in into a busy party. The BCT operator can record a call. It should be possible to call all desired numbers from any iS in the network, e. Every iS network node requires its own cluster identity. Note that this cannot be the same as the first digit s of the DNRs in your system, e.

In node A, create: - Routing Points for all Queues internal, external, fallback, park , as described in section 4. Make sure that in this Park-Queue no prompts are played.

This extension will be used to handle unsuccessful calls DDI-Fail actions. Program the configuration of the above picture:. Figure Group Configuration shows an example of a configuration. Based on this example, this chapter explains how to setup the system. The following items are important: BCT takes care of the routing to the agents. BCT takes care of queuing. BCT plays announcements. Only the announcements of the BCT are used.

BCT uses normal extensions as agent extensions. These extensions are only placed in an ACD group when creating a fall back scenario. Agent status switching using Starter Line In case of a Logon Starter Line, the agents need to dial a special number for changing their status. When an agent needs to change the status, the agent dials a special DNR. If your system is a busy system, it can be useful to use a dedicated VMP line or a line on the Dialogic card.

This means that the line is no longer available for BCT access. You must remove that line from the IVR Group. In case of dialing a prefix the phone based agents use prefixes to logon and log off. Also entering call type information and switching not ready is possible via prefixes. Computer Based Agents use the application to change the agent status.

There is one exception. In case of Fallback, no Computer Based Agents are available any more. In that case the agents configured for the Fallback group s must login and switch themselves ready by entering status information. First you have to select for which Server the action is valid. The number of digits for the agent log on and ready is digits. The number of digits for agent not ready is 1 up to 6 digits. When no not ready reasons are required you can omit this value The number of digits used for entering transaction code is 0 up to 6 digits.

This prefix is used to enter call type information. The number of digits used for the not ready reason and the call type should match the number of digits that are used during the creation of these items. Per default after installation, a number of NRRs are available in the chosen system language. Project a DNR as Voicemail access number.

Note: In the following program example is assumed that a Fallback scenario is used as described in chapter 4. When no Fallback is required the IVR hunting groups is the entry starter number for the callers. If you assign this FCM to the lines, the system will not work. If you need more than one access number more than one service requested , create dummy DNRs no hardware associated with call forwarding not reachable to agent ACD group. Configuring IP Lines Execute the procedure described in 4.

Assign virtual SIP extension board. However, if the customer already uses G, and wants to keep it, you can use G. If for whatever reason BCT fails, all calls will be lost. Therefore it is strongly recommended to configure a Fall Back scenario. There are two types of Fall Back configurations possible. The agents are grouped in an ACD group. A call. In normal operation the agent group is switched to night. All calls are forwarded to the IVR hunting group.

From this moment on the calls will be distributed to the agents of the ACD Group. From that moment on, BCT is in normal operation. Configure call forwarding on night to the agent ACD group. In normal operation the calls are handled in the IVR group via the call forwarding on overflow. The moment the BCT is down, the grouting group will switch automatically to night and the calls will be sent to the agent ACD group via the call forwarding on night.

See section 4. The agent state is synchronized between the switch and BCT during the normal operation mode. The moment the fall back is activated, agents who are ready in BCT will also receive calls when the fall back mode is activated.

There is no Synchronization when the fall back mode is switched back to normal operation mode. This means that the moment the normal operation is active after a period of fall back agents may have an incorrect state. Switching the agent state via the BCT Supervisor or agent phone will synchronies the state again. The following note is very important and should be communicated clearly to the group supervisor and group agents:. The moment BCT is operational. Note: Do not create a group with a group property that allows any type of call pick-up.

Always create the ACD agent group with a supervisor, otherwise you cannot switch the group from day to night with a prefix.

The only possibility without a supervisor is via an OM terminal. The command asks for the following additional parameters: Unit:;Enter the unit number only applicable if this system is multi-unit. ACD group threshold priority:;. Choose 1, 2 or 3. Do not use 0. In that case the agent is not allowed to switch.

Rank is the unique number in the ACD group. Example: ,1,0; ,1,1; ,1,2; The group that you have created is automatically in Day and the members are automatically switched present in the group. This is the result of Switch Allowance 1 for the members. Note: Switch the agent ACD group to night. Night is the normal operation mode when BCT is running correctly. The prefixes for agent switching must be performed with ACD server dialed prefixes.

In that case the prefixes can also be used for phone based agents. This parameter defines the number of digits that must be entered for the above mentioned actions. When no not ready reasons are required you can omit this value. The number of digits used for entering transaction code is 1 up to 6 digits. Note: When the prefixes are only used in fall back mode and no phone based agents are used in the Contact Center, info-nbr-length value can be ignored.

Configure Automatic Fall Back Execute the following steps: 1. Configure an IVR hunting group as described in section 4. Create a routing group as described in section 4. For an automatic fall back it is important that the maximum Queue on the Routing Point is set to zero.

This will trigger the call forwarding on overflow to the IVR group in normal operation mode. Assign call forwarding on overflow to the IVR group. Assign call forwarding when night to the agent ACD group. The configured Routing Point will trigger the day and night status of the Routing Point. For every starter that is required in the Call Flow, create hardware less extensions or non member ACD groups group prop.

Configure call forwarding on not reachable to the routing group for the hardware less extensions or configure call forwarding on night to the routing group in. In that case the calls are queued in the PBX. The callers are queued on Routing Points until a free agent is found. In that case the number of available IVR lines is no longer the maximum number of caller that can be queued. Only the in- switch announcements can be used to inform the callers.

The in-switch announcements can only be used for a welcome message, night announcement, and Queue status information and not for Call Flow information attendant, confirmation prompts etc. Creating a routing group A routing group is a non member ACD group. The difference between a normal non member group and a routing group is that a routing group can be switched to day and therefore calls will be accepted in the Queue.

It is possible that more than one routing group is required multi- language Contact Center, VIP treatments etc. Create of one or more ACD routing groups. The following parameters should be entered.

Group property: Enter Group property 59 followed by a semicolon. The system will prompt for additional information. ACD group threshold priority: Accept the default, threshold priority can be arranged when more than one router is used. Full threshold: Maximum number of non-threshold and threshold priority calls that can be stored in the ACD Queue. Enter a value that starts with 99 followed by e.

Do not use a value higher than Also enter a fixed value, see Full threshold. For routing groups used by BCT, it is recommended to use the same value for the busy and full threshold. Note: Do not use a relative Queue for the busy and full threshold for a routing group. This results in a routing group where no calls can be queued. The number of available Queue places should be at least the same as the maximum Queue size that is configured in the Router and the number of callers that can be queued according the granted licenses.

Forced absent time: Accept the default, the forced not ready time is arranged on the router. After call work time: Accept the default, the after call work time is arranged on the router. Call in queue time: Calls will be diverted or dropped when the call in queue time has expired. Make sure that the selected call in queue time matches the call in queue time that is set in the router options. Pause tone: Defines the type of pause tone sent to the caller between announcements.

Note: Be aware that one Routing Point in combination to several starters one or more Non member groups forwarded to one routing group will result in incorrect announcements. The iS announcements will play announcements for the Routing Point Queue and not related to the Starter Line router relation. In case of more routers and correct iS announcements per router, more than one Routing Point must be created.

Queue priority of the group: Select the default value, priority can be arranged in the Call Flow. When no free agents are available the PBX must generate busy tone to the caller. Call forwarding The call forwarding destination may be another ACD group but it is also possible to forward to a normal extension or operator extension. The following parameters should be entered:.

Call forwarding type: number between 0 and 9. Call forwarding type for CFWA is 2. Call forwarding type for CFWE is 3. Call forwarding type for CFWO is 4.

Call forwarding type for CFWN is 5. Announcements There are three types of iS announcements: - Station call, first announcement that is given when a customer dials the ACD group extension.

The announcements can be recorded e. For information, please refer to the related documents. There are a number of Fall Back options possible. The routing groups are in Day status when the Contact Center is running in normal mode. Calls are accepted in the Queue and BCT routes the calls to agents. The moment BCT is not responding any more, the routing groups, automatically switched to night mode.

Via a call forwarding when night, the calls are routed to an ACD fall back group. This group should always be in day. When BCT switches over to the Fallback configuration the agents already have the correct status. This extension is used as destination for call forwarding when night during the fall back period. The value must be between 30 and Some examples: Group property Longest idle hunting, call pickup group and member allowed, empty group not allowed.

Group property Longest idle hunting, call pickup group and member allowed, empty group allowed. Enter the appropriate group property value. This is only applicable if a second ACD group is used as destination in a call forwarding.

The size of the threshold should be equal to the Queue size that is used in the router settings. Use the same duration as used in the router. If absolute is selected, DDM is related to the Queue position.

In the following example, three DDM messages are defined. Queue position Played announcement. In the following example the weighted method is used with three Dynamic Delay Messages and the full threshold of 2 per agent. Table Queue position - Announcement table - Queue priority of the group: Used to give one ACD group a higher priority than another group.

Select the default value, priority is only applicable when a next ACD group destination is configured. When the above mentioned information is entered, the system will ask for specific agent information. Initial state: logged in and present. Initial state: logged in and absent. Initial state: logged out and absent.

Option 0 will not be used in Contact Centers, agents are not able to switch status during the fall back period. The result will be that the moment the fall back is activated all agents are logged in and ready to answer calls. Be aware that is possible that a number of agents are not at their desk but the telephone is ready to receive calls. These calls will be rerouted after a forced not ready to agents that are available. This to avoid that callers are waiting a long time due to rerouting on forced not ready.

This is only a problem for screen based agents. When the Contact Center is using phone based agents, the status of the agent will not be changed the moment the fall back is activated. Enter for each agent that is working in the Contact Center an extension and a rank. The rank is a unique number within an ACD group.

When all agents are entered, end the command with return. At this moment the ACD group is created. Company Directory and Presence Information on Polycom terminals Polycom terminal users can access the Company or Central Directory to search for an entry, look at the presence information and set up a call.

To allow this, you must modify the sip. To allow an application to be run from the microbrowser: 1. Open the sip. Optional: change mb. For example: mb. Change mb. Keys description: - maximumDataInPage: maximum number of entries shown in one page. Default value: 4 - showPhoneState: show 'Phone State' icon for each entry. Default value: true - showDetails: show 'Details' icon for each entry. Default value: false. When showPhoneState is changed to true the DataAccess.

In iS the mobile extension is Mobility Access. With this functionality a remote extension e. Mobile phone can be reached under a local extension number and can use the same features as a local extension, like consultation call, transfer consultation and blind and conference.

To program the MA, execute the following procedure:. Configuration for Bria softphone support Bria is a softphone that can be used as telephone for BCT uses. In order to use the auto answer be- havior of the Bria phone in the BCT Desktop Client, the Bria softphone and extensions need to be configured. The Bria can get its configuration settings from a Login server.

This Login server is a PHP server that contains a login script, that the Bria phones retrieves during startup. After configuring the PHP server, a login script should be created to configure the Bria. This script can reside in the installation folder of PHP, e.

An example for the login. When the Bria softphone is started then Profile: manual enter login server should be selected and in the field Login server: the URL to the login. The terminal type of a Bria extension is initially synchronized as SIP, which lacks the enhanced func- tionalities in the Desktop client.

The main configuration issues concern access to the Active Directory and operator Queue. Without an extension assigned to the stations, the station cannot be called because it is simply not addressable. A station is reachable by its extension number. Changes can only be made in Active Di- rectory. Synchronization is done during installation of the BCT server.

This is described in section 8. Here are the basic steps you need to follow before you install BCT: 4. This account is, amongst others, used for presence monitoring, call control and Active Directory Synchronization of BCT users. In order to create this user you must be logged in on the domain controller with an account that has domain administrator rights. If you do not have an account with these rights yourself, then you should have this procedure being performed by an IT administrator.

How to create a CTI user account: Note: in this example the user "CTIuser" is created, you do not necessarily need to name this account this way, it is just an example which will be used throughout the manual.

Login on a domain controller of your domain, with an account that is part of the domain admins group. Right-click the Organizational Unit or AD container e. Fill in the last name and user logon name as CTIuser. Note that the domain unicorn. Click Next. Figure Create new CTI user, password 4. Create a strong password and clear the "User must change password at next logon" checkbox. Select the "User cannot change password" and "Password never expires" checkboxes and click Next.

Review your settings and press Finish. To do this: 1. Enter a name for the new group and add all users that Business ConneCT should monitor, click OK to create the new group 4. Next to that special user rights are needed:. Without line rights, the CTIuser cannot take control of individual stations. Multiple zones without trust relations are not supported by BCT.

Operator Barge in One special case of call control is the operator breakin facility. One important aspect of the configuration in UNIVERGE 3C is that stations that can be barged into as well as stations that will initiate the barge in have to be members of the same address group. Stations allowed to initiate a barge in session need to have supervision rights to this address group. Crucial is that also the CTIuser needs to be given these supervision rights to any address group configured for barge-monitor, otherwise the CTIuser is not allowed to start a barge in session operator breakin on behalf of a BCT operator client.

Do NOT assign a password for webservices. When you leave it blank the windows password of CTIuser as configured on the domain controller will be used. Make sure that the CTIuser is marked as user centric.

The CTIuser also needs a dummy exten- sion address. The address does not need to be preferred and no station needs to be assigned to the extension. Click on Zone, select the zone from the list and click OK. Now assign the CTIuser full privileges on the line default it only receives monitoring privilege af- ter adding rights to the zone and click OK.

See the following figure. Note: the zone name "UCS Lab zone" is just an example, your zone name will be different. Click on Address Group, select the barge-monitor address group from the list and click OK. Now assign the CTIuser supervise privilege on the address group s. Prepare a class of service profile for operator and agent stations Although BCT can handle multiple incoming calls per station for employee users, this has to be lim- ited to 1 incoming call maximum for any operator or agent station.

It is best to define a special ser- vice class profile for operators and agents which limits the maximum number of incoming calls to 1 and then assign this profile to the operator and agent stations. When the maximum number of incoming calls is not limited to 1 for operator stations, direct calls to operators one or more simultaneous will always take precedence over calls in one of the operator queues, thereby effectively blocking operator of taking calls from the queues as long as direct incom- ing calls are offered direct means calls directed to the operator stations extension number.

The contact center can also not handle more then one incoming call to agent stations. Expand the Organization Name, right click Class of Service Profiles and select add, now you can add a new class of service profile give it a clear recognizable name like Operator Stations and set the "Max Calls" to 1 Call and click OK. For this purpose it is recommended to define a special Class of Service profile which allows for 48 incoming calls per SIP line.

Now you can add a new class of service profile and give it a clear recognizable name like BCT Routing Points. The BCT Routing Points class of service profile need to be assigned to the stations which will act like queues routing points. Four of these Queues will to be created:. Procedure: 1. Then click start. See next screenshot:. Repeat the steps above, but now only create one SIP registration for the internal queue 9.

There are 0 results matching your filter criteria. Show Filter. Version All 6. MX8 applications processor series Zeus 1. MX8 applications processor series Sumo 1. Build MX8 applications processor series 1. More Downloads. Back to Webshop. MX8 applications processor series Zeus. Basler blaze Firmware. Just trying using a local server account and it should work. Was able to get past the "failed to set password change policy" issue by temporarily blocking inheritance on the OU our on-prem WMS server was in, so that the domain password policy wasn't applying, then re-running the install kudos to Drewsky25 there.

Browse Community. Wyse Management Suite. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Last reply by kraggzy Unsolved. Upgrade failed from WMS 3. Hello everyone, Trying to upgrade 3. This has happened on 2 production servers thus far, both being domain controllers.

Has anyone experienced this? Please advise. Thanks, Ted Tsoukas. All forum topics Previous Topic Next Topic.