Actions

CRM V - Control Room Master

From Zenitel Wiki

Revision as of 13:29, 28 October 2016 by Roarl (talk) (Available items)
CRM V with all optional modules

The CRM-V Station is designed for control room applications.

The station consists of a main module (IP Flush Master), which can be extended with up to two IP DAK-48 Units and a handset module.

This article describes how to install and configure the CRM-V station.

Available items

The following items are available:

Installation

Main Module - IP Flush Master

The IP Flush Master supports Power over Ethernet (PoE, IEEE 802.3 a-f).

If PoE is not available, the IP Station can be connected to a 24 VDC local power supply. See IP Station Installation on how to connect 24VDC.

There are two RJ45 ethernet ports on the IP Flush Master station.

  • LAN port: for connecting to the network and the AlphaCom XE Audio Server.
  • AUX port: for connecting to auxiliary equipment such as a PC or IP Camera.
IP Flush Master - Rear view


Handset module

Insert the RJ11 plug of the handset into the lower port of the dual RJ11 ports on the lower left of the station.

Handset connection



Related article:

DAK-48 Expansion module

The IP DAK-48 unit expands the IP Flush Master station with an additional 48 Direct Access Keys. Up to two DAK-48 units can be connected to one station. To interconnect the DAK-48 unit to the main unit, use the cable which is coming with the DAK-48 unit. The DAK-48 unit receive its power and data via this cable.
WARNING: A standard patch cable (1:1) must not be used. It might damage the unit!

Installing the IP DAK-48 Unit:

  • Power off the IP Flush Master station by disconnecting the ethernet cable in the LAN port
  • Plug one end of the cable coming with the DAK-48 unit into the RJ45 port on the right hand side of the IP Flush Master station (when the station is viewed from the front).
  • Plug the other end of the cable into the left RJ45 port on the DAK-48 unit (when the unit is viewed from the front).
  • Power up the IP Flush Master station by connecting the ethernet cable to the LAN port
Installing the IP DAK-48 Unit


Headset connection

The IP Flush Master station is fit with an RJ11 connector for headset connection. Insert the RJ11 plug of the headset into the upper port of the dual RJ11 ports on the lower left of the station. A regular PC style headset can be used. If the headset is not equipped with an RJ11 connector, an adapter must be made locally.

The headset will automatically be detected when connected, and a headset icon will appear in the top right corner of the display. The microphone and loudspeaker on the IP Flush Master panel will be disabled, and the audio routed to the headset.

Headset connection to IP Flush Master


For more details and options, see: IP Flush Master and Headset

Gooseneck

Instead of using the built-in electret microphone in the IP Flush Master module, it is possible to add a gooseneck microphone.

  • Remove the cover plug from the opening for the microphone on the front panel.
  • Thread the microphone cable through the opening, the lock washer and nut.
  • Tighten the nut on the microphone’s threaded stud.
  • Insert the microphone’s IDC socket into the upper two pins of the 3-pin header (J7) located at the lower left side of the station. The signal wire (white) should be on the top pin while the ground wire (green) should be on the bottom pin.
  • Slide the S1 switch (bottom back of station) to EXT to activate the external microphone, and disable the built-in microphone.
Installing the Gooseneck Microphone


Configuration

Station Type

In AlphaPro, Users & Stations the "Station Type" should be set to CRM. This will change the display layout from the standard two line display to a four line display, which is more suitable for call queuing operations.

Set "Station Type" = CRM


The display will show the date and time in the top line. Line 2 and 3 are used for the queue navigation, and line 4 is used for labeling the Navigation Keys when there is an entry in the queue.

When the station type is set as "CRM", the backlight in the display will be permanently on.

Queue Navigation buttons

The four navigation keys below the display can be used to navigate the queue. A label will be visible in the lowest line of the display when there are calls in the queue.

Incoming Call Requests (and mails) are queued queue in the chronological order, the last Call Request will be at the bottom. However, incoming Call Requests have a priority (0-255), and a Call Request with higher priority will be placed on top.

When the "Station Type" is set to "CRM", the navigation buttons are automatically configured by AlphaPro. The default configuration of the navigation keys are (from left to right):

  • 7638 = Answer (Answer the highlighted mail by calling back to it)
  • 7639 = Next (Go to the next mail in the queue)
  • 7632 = Top (Go to the first mail in the queue)
  • 7630 = Delete (Delete the selected entry)

The navigation keys can be manually configured. In AlphaPro, Users & Stations, select the CRM-V station from the list box, and press the button DAK. Select the tab Navig. Keys:

Users & Stations > DAK: Queue navigation codes


Enable the DAK-48 unit

CRM V license

A CRM V license is required in order to enable the DAK-48 unit(s). The license is installed in the AlphaCom server.

Redirection of DAK keys

In general every user in AlphaCom has DAK tables for 20 DAK keys. Because the CRMV uses up to 100 DAK keys, one have to "borrow" DAK tables from other, unused stations.

DAK key layout of the CRMV station


DAK tables are "borrowed" by pointing to the other users in the DAK table of the CRMV. This is done by using the symbol ">", followed by the physical number of the station from where we want to use the DAK table. Any free physical number in the range 1 to 552 can be used. However, it is recommended to use higher numbers to avoid conflicts if the system is expanded in the future.

DAK table of the CRMV: Redirecting to DAK tables of physical 501, 502 ... 510


The actual DAK key configuration must be entered in the DAK table of the station to which the CRM DAK table is pointing:

DAK 1-10 are configured in the DAK table of physical #501



Several CRMV stations may redirect to the same DAK tables if they should use the same DAK layout.

Audio alert

When a Call Request is received, this can be notified to the user by a "dut-dut-dut"-tone, called Notification tone. Then a Feature Reminder tone will continue to alert the user that there are calls in the queue.

Notification tone

By default there is no notification tone upon reception of the call request when the Station Type is set to "CRM". Notification tone can be enabled by creating an event with the following parameters:

Enable "Call Request notification" tone for physical number 49


Event 27, subevent 65 is triggered when the AlphaCom starts up. The action command will set a flag which enables the Notification tone for the user specified in the action parameters.

Action Command:

$SNV Q%op(%gnv(5,8,xx,17),|,8192) W5 W8 Wxx W17

Where xx must be replaced by the actual physical number of the Control Room station.


This flag was introduced in AMC software 10.56.

Feature Reminder tone

There are multiple options on how the presence of call requests in the queue should be notified in the CRM-V station. It is the priority of the Call Request which decides what option will be used.

The options are:

  • Feature Reminder: A short reminder tone (bleep) every minute. By default used when priority is 60 - 119. Used by the Call Request code 623, which has priority 100.
  • Urgent Feature Reminder: 3 times dut-dut-dut-dut tones, repeated every 20 second (programmable from AlphaPro). Used when priority is 120 - 149. By default used by the Call Request code 622, which has priority 140.
  • Private ringing tone. Used when priority is 150 - 255.

The priority of the Call Request code can be changed in AlphaPro, Directory & Features:

Modifying the priority of the Call Request code


LED Indication

The DAK keys on the IP Flush Master and on the DAK-48 panels have two LED's each. The two LED's (red and green) are controlled using the IND command in the Event Handler.

Red and green LED on the DAK panel


If there are several CRM-V stations which should have identical LED behavior, one can put all CRM-V's in a UDP group, and define the UDP group as the event owner instead of the single CRM-V station.

To create an event, go to Users & Stations window, select the CRM-V from the list box, and press the button Events. Press Insert to create a new event.

In the following, station 105 is used as example.


Call Request

To turn on the red led, flashing fast, in the associated DAK key when a Call Request is received, create this event:

Action Command: IND %1.phy %1.dak(I%2.dir) 1 3


Outgoing Conversation

To turn on the green led in the associated DAK key when an outgoing call is made, create this event:

Action Command: IND %1.phy %1.dak(I%2.dir) 2 1


Incoming Conversation

To turn on the green led in the associated DAK key when an incoming call is received, create this event:

Action Command: IND %1.phy %1.dak(I%2.dir) 2 1


Door Status

An input of the IP substation can be connected to a door magnet, providing indication on the DAK panel, showing if the door is open or closed.

Example:
To turn on the red led in the associated DAK key when input 3 of the IP substation 159 is activated, create this event:

CRMV DoorStat.PNG


Action Command:
OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1

105 is the directory number of the CRM

Station faults

To turn on the red and green led in the associated DAK key when a station is reported faulty, create this event:

CRMV StatErr.PNG


Action Command:
OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 1
IND %2.phy %2.dak(I%1.dir) 2 1

105 is the directory number of the CRM


Lamp Test

To perform a test of all LEDs in CRMV station (including the DAK48 panel), dial the code 7874. The station must be a SuperUser, or have the right privileges in the Class of service settings.

Note that this feature require software version 2.5.3.0 or later in the CRMV.

Call Forwarding

Manual Call Forwarding

Call Requests are manually forwarded by dialing the feature code 7870 + destination directory number. To reset the call forwarding, dial 70.

The Forwarding feature can be assigned to a DAK key for simple operation:

DAK 1 activates forwarding of the call request to station number 110. DAK 2 resets the forwarding


Call escalation

If the Call Request is not answered within a preset time, it can be automatically forwarded to a predefined target:

Enabling "Automatic Search" on Call Request timeout


The predefined target is entered in the "Search strings" table of the CRMV station:

Define the receiving station in Users & Stations > DAK > Search strings


  • If the call should be forwarded as a Call Request to station 110, enter I 623 I 110.
  • If the call should be forwarded to external phone number 987654321, enter I 0 P 987654321. "0" is the access code to the phone line.
  • See also: Forwarding of Call Request to external telephone

The time before forwarding is set in Exchange & System > System > Timers. The default time is 20.0 seconds:

Set the time before the call request is forwarded


Optional settings

Answer Call Request by M-key

A call request is normally answered by pressing a dedicated DAK key programmed to dial the answer code 7638. However, it is also possible to answer call requests by pressing the M-key, in the same way as for direct calls in private ringing mode.

In Users & Stations, select the CRMV station from the list box, and press the button Events. Insert a new event with the following properties:

Answer call request by pressing M-key


Action string: $MAILQ NAVIG L%1.dir 8

Answer Call Request when the lifting handset

It is possible to automatically answer the first call request in queue when lifting the handset.

In Users & Stations, select the CRMV station from the list box, and press the button Events. Insert a new event with the following properties:

Answer call request by lifting the handset


Action string: $MAILQ_NAVIG L%1.dir 8

Applications

See Category: Control Room Applications