AltiGen comm MAXCS 80 New Features Guide
Have a look at the manual AltiGen comm MAXCS 80 New Features Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 29 AltiGen comm manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
MaxCS 8.0 New Features Guide Page 11 of 46 Polycom VVX Directory Dialing This feature was added in Release 8.0. Directory Dialing requires a MAXCS Polycom Advanced Features license, and is only supported on the following VVX model IP phones. VVX 300/310 VVX 400/410 VVX 500 VVX 600 Polycom users can now choose contact from a corporate directory to place calls, transfer calls, and perform other basic functions. A default Directory Profile, named System, is provided by default. It includes all extensions. You can configure addi- tional Directory Profiles as needed. To configure this feature, you will create corporate directories and then enable directory use for appropriate ex- tensions. Refer to the MAXCS Polycom Configuration Guide for full instructions. Polycom Client Call Control This feature was added in Release 8.0. The MaxCS Clients are now synchronized with Polycom phones; regardless whether you used the client or the Pol- ycom phone to place a call on hold, you can retrieve the call from either the client or the phone. Polycom-to-Polycom Video Call Support This feature was added in Release 8.0. MAXCS supports video calls on Polycom IP phones for Softswitch deployments. Video calls are not supported on Max1000 or Office systems. Supported devices include: • VVX500 and VVX600 (these models require a separate Polycom VVX USB camera) • VVX1500 (this model has a built-in camera) Considerations: Video conferences are not supported; only direct peer-to-peer calls are supported. Video calls are supported in Softswitch Deployments only. Refer to the MAXCS Polycom Configuration Guide for configuration instructions. Polycom Device Auto-Answer Changes In previous releases, agents with Polycom VVX phones could both enable the Auto-Answer feature as well as set the default voice path (speaker or handset) in a single setting the client’s Configuration > Extension page. Due to the specific way that Polycom handles voice paths, AltiGen has changed how users configure this feature. Configuration now requires two separate steps. To enable or disable the client Auto-Answer feature, users still open the MaxAgent Configuration page. The choic- es now are Enable and Disable. (The choice in earlier releases was Speaker or Headset).
MaxCS 8.0 New Features Guide Page 12 of 46 This feature requires an Advanced Features license. Refer to the MAXCS Polycom Configuration Guide for full instructions. Polycom #33 Do Not Disturb Feature Profile When you clear Call Management feature #33 – do not disturb (in System Configuration > Feature Profiles), both the DND button and the DND softkey will be disabled in Polycom phones that have been assigned to that profile. However, users will still see the disabled DND softkey until the phone is rebooted. Similarly, when you enable feature #33, some Polycom models will enable the DND button right away; other mod- els may need to be rebooted before the change will take effect. Polycom Miscellaneous Updates The Caller ID will now show correctly while the call is ringing; in the previous release, the Caller ID updated only after the call connected. Polycom Known Issues and Considerations For a list of known issues, refer to the Polycom Configuration Guide. Technology Enhancements in Release 8.0 This section describes new features included in this release. HMCP Load Balancing This feature was added in MaxCS 8.0. The HMCP system has been enhanced to perform load balancing on a multi-core system, in a round-robin method. This results in a more even distribution of work across all channels, resulting in performance that is more con- sistent. Security Enhancement This feature was added in MaxCS 8.0. A security enhancement has been added for the AltiGen Java Service Loader. Figure 1: AltiGen Java Services Manager Prior to Release 8.0, you could use AltiGen Java Service Manager to connect a remote machines Java Service Load- er with the default password, if the remote servers administrator had not changed the password. In MaxCS 8.0, however, the new Java Service Manager can connect only to the local system. In addition, earlier versions of the MAXCS AltiGen Java Service Manager will not be able to connect to the MaxCS 8.0 AltiGen Java Service loader.
MaxCS 8.0 New Features Guide Page 13 of 46 This change will prevent you from running Java Service Loader Manager from a LAN or WAN connection. The only way to access Java Service Loader Manager now will be from the server itself, via Remote Desktop. SIP Group Configuration This feature was added in MaxCS 8.0. In previous releases of MaxCS, SIP registration was configured by individual channels. This configuration approach had several disadvantages. For example, configuring multiple channels with the same authentication credentials was inefficient. Setting multiple channels to register to the same server and having to configure only one of them with a registration period required configuring that channel twice. Moreover, for some scenarios, such as configur- ing an AltiGen SIP Trunk fax server, one trunk had to be reserved for fax even if faxes were seldom sent or re- ceived. Some benefits of the new approach: The number of SIP trunk channels is now configurable, as opposed to the license-based model in earlier releases. SIP trunk configuration is accessed through single entry point “SIP Group Configuration” screen as op- posed through SIP Profile and multiple entry points in the previous release. This design improves usability for SIP trunk provisioning. Each SIP Trunk group may be configured with one or more SIP servers, and the server’s status is displayed. When at least one SIP server’s status is up, this SIP Trunk Group is considered active. The priority of the SIP server is from top to bottom. For example, when two SIP servers are configured in a group, MaxCS sets up SIP calls with the first SIP server if its status is up. Otherwise, if the second server is up then MaxCS will set up the calls with second SIP server instead. The configuration for SIP.US SIP trunk can now be achieved by configuring a single SIP Trunk Group with two servers, gw1.sip.us and gw2.sip.us where gw1 is used as primary server and gw2 as backup server. The Register tab in SIP Group Configuration displays SIP Registration parameters for the highlighted SIP Server entry. One SIP Registration session is established for each SIP server. This registration status de- fines the SIP server up/down status. When all the servers in a group are down, all the SIP trunk channels associated with this SIP trunk group are considered inactive. This design eliminates the problem in the previous release where when the SIP registration to a server failed, only those channels with SIP registration enabled are down but other channels connect to the same server are still active. Allows a SIP server in multiple SIP groups – In the case where the system connects to a SIP carrier through multiple SIP trunks, the administrator may configure this carrier’s SIP server in multiple SIP Groups, and each SIP Server entry has the same domain, IP address but different User Name. This configuration should be used for outbound call ONLY as Out Call Routing may select the trunk chan- nels associated with a particular SIP trunk group. Inbound calls, in this case, are routed in a first-available fashion to all of the SIP trunk channels of these SIP Groups that have this SIP server address configured. Settings and SIP OPTION parameters are re-organized and supported for each SIP Server entry. Best effort configuration conversion is performed when MAXCS is upgraded from a previous release. The administrator should verify the SIP Group and SIP Trunk channel assignment after upgrading. To streamline SIP registration, AltiGen has implemented SIP Group configuration. The following three panels in the earlier releases have been consolidated:
MaxCS 8.0 New Features Guide Page 14 of 46 The SIP Trunk Configuration dialog box The Trunk Group Configuration dialog box The SIP Trunk Profile dialog box In addition, the Trunk Configuration dialog box has been updated to show the SIP Trunk group, in the Type column. The SIP Signaling Channel Configuration dialog box is the main starting point for all SIP channel configuration. (Double-click a SIPSP board in Boards view and then click Board Configuration to reach this panel.) Figure 2: The new buttons on the updated SIP Signaling Channel Configuration panel Two of the buttons in the earlier releases have been replaced with two new buttons: SIP Group Configuration – This is where you now configure SIP Groups, adding SIP servers and configuring various options for each server. Channel Assignment – This is where you now enable and disable channels, and move channels from one SIP group to another. In the SIP Signaling Channel Configuration panel, you can do the following: Create new SIP groups Add servers to SIP groups (and remove servers from SIP groups) Change the relative priority of servers in a SIP group Configure various registration and SIP Options for a server
MaxCS 8.0 New Features Guide Page 15 of 46 Create a New SIP Group To create a new SIP Group, 1. Double-click a SIPSP board in Boards view and then click Board Configuration > SIP Group Configuration. 2. Below the Groups list, click Add. Figure 3: Click Add to creating a new SIP Group 3. Provide a name for the group and indicate whether this is an AltiGen SIP Trunk. Note: Release 8.0 includes license checking for AltiGen SIP trunks. Be aware that trunks will show as not registered if you start MAXCS Administrator before MAXCS is fully up, because license information will not be ready until then. However, after 30 to 90 seconds, the trunk should be show as ready. Figure 4: The parameters for the new SIP Group 4. If appropriate, select Enable fax trunk routing and provide the fax user name and fax password. These fields are for use only with AltiGen SIP Trunks. Add SIP Servers to a SIP Group You can add up to four servers to each SIP group. To add a SIP server to a SIP group, 1. Double-click a SIPSP board in Boards view and then click Board Configuration > SIP Group Configuration.
MaxCS 8.0 New Features Guide Page 16 of 46 2. Select the appropriate SIP group in the Groups list. 3. Below the SIP Servers list, click Add. Figure 5: Click Add to add SIP servers to a SIP Group 4. Enter the Domain name. 5. (Optional) If you want to copy the settings from another server, choose the group and the server from those two pulldown menus. Figure 6: The parameters for the SIP Server Note: Click Refresh to retrieve the latest registration status. To remove a server from a SIP group, 1. Double-click a SIPSP board in Boards view and then click Board Configuration. 2. Select the appropriate SIP group in the Groups list. 3. Select the server that you want to remove from the SIP group. 4. Click Del (Delete). Change the Order of SIP Servers in a SIP Group The order of the servers in the Servers list determines how the servers are accessed. The first server is always used; when that server is not available, the next server in the list is used, and so on. To change the priority order of servers within a group, 1. Double-click a SIPSP board in Boards view and then click Board Configuration. 2. Select the appropriate SIP group in the Groups list. 3. In the Servers list, select the server to move, and then click Up or Down as appropriate.
MaxCS 8.0 New Features Guide Page 17 of 46 Configure SIP Server Registration Parameters The Register tab contains all registration-related settings for a SIP server. All of the settings on the SIP Trunk Con- figuration dialog box from earlier releases of MaxCS are found on this tab. Figure 7: The SIP Server registration parameters The lone exception is the Enable Channel option, which is now handled in the Channel Assignment panel. Note: SIP Server registration status depends upon both the registration results and the SIP OPTIONS results. If either of those two processes fails, the server’s status will be set to DOWN. SIP Groups and member channels share the same registration status. As long as at least one SIP server is UP, all of the enabled member channels will show as status Idle. Configure General SIP Server Parameters The Settings tab contains the parameters from the SIP Trunk Profile tab in earlier releases of MaxCS.
MaxCS 8.0 New Features Guide Page 18 of 46 Figure 8: The SIP Server general parameters Configure Server SIP Options The SIP OPTIONS tab includes the SIP OPTIONS parameters from the previous release of MaxCS. The SIP Server Name parameter is essentially the new Domain field. Figure 9: The SIP Server SIP Options
MaxCS 8.0 New Features Guide Page 19 of 46 Enable or Disable Channels To view a list of channels and determine the SIP Group to which each channel belongs, 1. Double-click a SIPSP board in Boards view and then click Board Configuration. 2. Click Channel Assignment. Figure 10: Channel Assignment view A checkbox indicates whether a channel is currently enabled. To disable a channel, clear its checkbox. To enable a channel, check its checkbox. To enable or disable all channels, check or clear the checkbox in the column heading at the top of the list. If you discover that you need to add more channels, close this panel, click the Board Configuration, and set an ap- propriate value for the Change Number of SIP Trunk Channels to… option (see Figure 2). Then restart the system. Assign Channels to a SIP Group To assign a channel to a SIP Group, or reassign it to a different SIP Group, 1. Double-click a SIPSP board in Boards view and then click Board Configuration. 2. Click Channel Assignment. 3. Select one or more channels in the list. Use Ctrl-Click to select multiple channels.
MaxCS 8.0 New Features Guide Page 20 of 46 4. Click Assign Group. Figure 11: The list of available SIP Groups 5. Choose a SIP Group from the list and click OK. Considerations: A channel is not enabled if it is not assigned to any SIP group. If you assign a disabled channel to a SIP group, doing so does not automatically enable it – you must man- ually enable the channel (see the previous section). In order to assign channels to a SIP group, the SIP group must have at least one SIP Server assigned to it. If you remove all SIP Servers from a SIP Group, all channels previously assigned to that SIP group automat- ically will show as ‘Not Ready.’ Trunk View Enhancements As a result of adding SIP Groups to MaxCS, the Type column in Trunk view will now shows each SIP Trunk’s group name (if it is part of a group).