Actions

Difference between revisions of "CRM V - Control Room Master"

From Zenitel Wiki

(Audio Indication)
(Ringing Group call (or Call Request))
 
(305 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Image:IP Flush Master.jpg|thumb|200px|Control Room Master Module]]
+
{{AI}}
[[image:CRM Full.png|thumb|350px|CRM V with all optional modules]]
+
[[image:CRM Full.png|thumb|700px|CRM V with all optional modules]]
  
=Features=
+
The '''CRM-V''' Station is designed for control room applications. This article describes how to configure the CRM-V station when used with an '''AlphaCom''' server.
* Made for Critical Communication over IP - CCoIP in a control room environment
 
* Large high contrast display with white backlight for excellent readability
 
* Superb audio technology - gives loud-speaking hands free duplex communication from any location in the room
 
* White light behind all keys for excellent readability in dark environments
 
* Optional noise cancelling goose-neck microphone
 
* Optional handset unit
 
* Integrated Web server for easy configuration and monitoring
 
* Remote automatic software update
 
* Clean relay output contact for control of external equipment
 
  
=Portfolio=
+
The station consists of a main module ([[IP Flush Master -V2|IP Flush Master]]), which can be extended with up to two IP [[IP Flush Master DAK-48 Module|DAK-48]] Units and a [[IP Flush Master Handset|handset module]].
<gallery class ="left">
+
 
File:80971 RS.jpg|Handset
+
This article describes how to install and configure the  CRM-V station.
File:IP Flush Master.jpg|IP Flush Master
+
 
File:DAK48.jpg|DAK 48 Unit
+
==Available items==
File:80975 RS.jpg|Gooseneck Microphone
+
The following items are available:
File:Stand.png|Desktop Stand
+
<gallery widths="100px" heights="100px" perrow="7">
 +
File:IP Flush Master.jpg|[[IP Flush Master -V2|IP Flush Master]]
 +
File:DAK48.jpg|[[IP Flush Master DAK-48 Module|DAK 48 Unit]]
 +
File:80971 RS.jpg|[[IP Flush Master Handset|Handset]]
 +
File:80975 RS.jpg|[[IP Flush Master Gooseneck|Gooseneck Microphone]]
 +
File:2810020006.PNG|[[Single Desk Stand CRM-V]]
 +
File:2810020005.PNG|[[Dual Desk Stand CRM-V]]
 +
File:2810020004.PNG|[[Triple Desk Stand CRM-V]]
 
</gallery>
 
</gallery>
  
= Installation =
+
==CRM-V Installation==
For installation of the CRM V, and connecting additional modules please see the <u>[[IP Station Installation]]</u> article.
+
* [[IP Flush Master -V2|CRM-V Main Module]]
 +
* [[IP Flush Master Handset|Handset]]
 +
* [[IP Flush Master and Headset|Headset]]
 +
* [[IP Flush Master Gooseneck|Gooseneck Microphone]]
 +
* [[IP Flush Master DAK-48 Module|DAK-48 Module]]
  
= Station Type =
+
== AlphaPro Configuration ==
By setting a station to [[Users_%26_Stations_(AlphaPro)#General|'''Station Type''': ''CRM'']] in AlphaPro the display layout will change from the standard two line display to a four line display.
+
=== Station Type ===
[[File:CRM 5.PNG|left|500px|thumb]]
+
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.
 +
[[File:CRM 5.PNG|left|700px|thumb|Set "Station Type" = CRM]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
The display on the station will instead of showing the date, time and station number and name, only 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 labelling the navigation keys when there is an entry in the queue.
+
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.
  
The CRM station type selection will also turn on the backlight constantly.
+
When the station type is set as "CRM", the backlight in the display will be permanently on.
  
= Queue Navigation =
+
=== Queue Navigation buttons ===
Incoming mails (typically [[Call Request|Call Requests]]) to a CRM station will form up a [[Mail Queue Operation|queue]] in the order they are coming in, where the last mail is at the bottom. All incoming mails have a [[SEND_MAIL#Mail_priority|priority]] (0-255), and a mail with priority higher than the ones in the queue already will go straight to the top. The four navigation keys below the display can be used to navigate the queue, and will be visible only when there are any entries in the queue.
+
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.
  
The default navigation keys for a CRM are (from left to right):
+
Incoming [[Call Request|Call Requests]] (and mails) are queued [[Mail Queue Operation|queue]] in the chronological order, the last Call Request will be at the bottom. However, incoming Call Requests have a [[SEND_MAIL#Mail_priority|priority]] (0-255), and a Call Request with higher priority will be placed on top.
* 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 highlighted entry)
 
  
The navigation keys can be configured using AlphaPro:
+
When the "Station Type" is set to "CRM", the navigation buttons are automatically configured by AlphaPro.
[[File:CRM 9.PNG|left|thumb|500px|Users & Stations &rarr; DAK: Queue operation codes]]
+
The [[Mail_Queue_Operation|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''':  
 +
 
 +
[[File:CRM 9.PNG|left|thumb|700px|Users & Stations > DAK: Queue navigation codes]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
The queue for two line display stations can be navigated with:
+
* When the "Station type" = Master, the navigation buttons are reported as DAK 21-24.
* 0 = Delete entry
+
* When the "Station type" = CRM, the navigation buttons are reported as DAK 101-104 (from AMC 12.3.3.4).
* 2 = Step to top
 
* 3 = Step to last
 
* 7 = Step to next entry
 
* 8 = Answer current mail
 
* 9 = Step to previous entry
 
  
= LED Control =
+
=== Enable the DAK-48 unit ===
The IP Flush Master has four DAK keys. In addition the station can be fitted with up to two DAK-48 panels to make a total of 100 DAK keys. of which all have two LED's each.
+
 
[[File:CRM 14.PNG|left|thumb|500px]]
+
==== CRM-V DAK Expansion License ====
 +
A [[Licenses#CRM-V_DAK_expansion|CRM-V DAK Expansion License]] is required in order to enable the DAK-48 unit(s). The [[Licenses#Inserting_the_license_key|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.
 +
 
 +
[[File:CRM 10.PNG|left|thumb|500px|DAK key layout of the CRMV station]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
The two LED's (red and green) can be controlled individually using the [[IND]] command in the [[Event Handler]].
+
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.  
  
Typical events to control LED's:
+
[[File:DAK Redirect2.PNG|left|thumb|500px|DAK table of the CRMV: Redirecting to DAK tables of physical 501, 502 ... 510]]
 +
<br style="clear:both;" />
  
:'''Incoming mail (i.e. Call Request received):'''
+
The actual DAK key configuration must be entered in the DAK table of the station to which the CRM DAK table is pointing:
[[Image:CRM 1.PNG|left|500px|thumb]]
+
[[File:DAK Redirect.PNG|thumb|left|500px|DAK 1-10 are configured in the DAK table of physical #501]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|
 
|-
 
|width="100pt"|'''Event Owner''':
 
|width="300pt"| The CRM-V station or a group of CRM-V stations || ''Enter the physical station number or the UDP group number''
 
|-
 
|'''Event type''': || 10 - Received mail
 
|-
 
|'''Subevent''': || N/A
 
|-
 
|'''When change to''': || ON or OFF
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || [[IND]] %1.phy %1.dak(I%2.dir) 1 3 || ''Replace I%2.dir with I2%.dir* to make it work with DAK keys containing longer strings e.g. "I202 M"''
 
|-
 
|}
 
  
This will turn on the red led, flashing fast, in the assosiated DAK key when a [[Call Request|Call Request]] is received.
 
----
 
  
: '''Outgoing Conversation:'''
+
 
[[Image:CRM 2.PNG|left|500px|thumb]]
+
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 ====
 +
Upon reception of a new call request there is a notification tone (dut-dut-dut) played in the loudspeaker.
 +
 
 +
This notification tone is by default enabled in software 11.5.3.4 and newer.
 +
 
 +
In older software this tone is disabled when the Station Type is set to "CRM", but can be enabled by creating an event with the following parameters:
 +
 
 +
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.
 +
[[File:CallReqNotif.PNG|thumb|left|500px| Enable "Call Request notification" tone for physical number 49]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|  
+
{{Code2|
|-
+
[[SNV|$SNV]] Q%op(%gnv(5,8,xx,17),|,8192) W5 W8 Wxx W17
|width="100pt"|'''Event Owner''':
+
}}
|width="300pt"| The CRM-V station or a group of CRM-V stations || ''Enter the physical station number or the UDP group number''
+
Where xx must be replaced by the actual physical number of the Control Room station.
|-
+
 
|'''Event type''': || 08 - Conversation - Outgoing
+
This flag was introduced in AMC software 10.56.
|-
+
 
|'''Subevent''': || N/A
+
==== 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.
|'''When change to''': || ON or OFF
+
It is the priority of the Call Request which decides what option will be used.
|-
+
 
|'''When related to''': || All
+
The options are:
|-
+
* '''[[Feature reminder|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.
|'''Action''': || [[IND]] %1.phy %1.dak(I%2.dir) 2 1 || ''Replace I%2.dir with I2%.dir* to make it work with DAK keys containing longer strings e.g. "I202 M"''
+
* '''[[Urgent feature reminder|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.
|}
 
  
This will turn on the green led in the assosiated DAK key when an outgoing call is made.
+
The priority of the Call Request code can be changed in AlphaPro, Directory & Features:
----
 
  
: '''Incoming Conversation'''
+
[[File:CallReqPriority.PNG|thumb|500px|left|Modifying the priority of the Call Request code]]
[[Image:CRM 3.PNG|left|500px|thumb]]
 
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|
 
|-
 
|width="100pt"|'''Event Owner''':
 
|width="300pt"| The CRM-V station or a group of CRM-V stations || ''Enter the physical station number or the UDP group number''
 
|-
 
|'''Event type''': || 07 - Conversation - Incoming
 
|-
 
|'''Subevent''': || N/A
 
|-
 
|'''When change to''': || ON or OFF
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || [[IND]] %1.phy %1.dak(I%2.dir) 2 1 || ''Replace I%2.dir with I2%.dir* to make it work with DAK keys containing longer strings e.g. "I202 M"''
 
|-
 
|}
 
  
This will turn on the green led in the assosiated DAK key when an incoming call is received.
+
===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]].
 +
[[File:CRM 14.PNG|left|thumb|500px|Red and green LED on the DAK panel]]
 +
<br style="clear:both;" />
  
: '''Door Status'''
+
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.
[[Image:CRM 4.PNG|left|500px|thumb]]
+
 
 +
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.
 +
 
 +
<br>
 +
 
 +
====Ringing Group call (or Call Request) ====
 +
To turn on the red led, flashing fast, in the associated DAK key when a Ringing Group call or [[Call Request|Call Request]] is received, create this event:
 +
[[Image:CRMV CallReq.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|  
+
{{Code2|
|-
+
  IND %1.phy %1.dak(I%2.dir) 1 3
|width="100pt"|'''Event Owner''':
+
}}
|width="300pt"| The Door Station or a group of Door stations || ''Enter the physical station number or the UDP group number''
 
|-
 
|'''Event type''': || 30 - Station DAK key as RCI
 
|-
 
|'''Subevent''': || 3 || ''Equal to the IP station [[RCI#Configuration|input]] that is used''
 
|-
 
|'''When change to''': || ON or OFF
 
|-
 
|'''When related to''': || All
 
|-
 
|'''Action''': || tmp 0 "%1.dir" || ''Temporarily store the station directory number''
 
|-
 
| &nbsp; || OWN 105 || ''Set the CRM directory number as owner of the event''
 
|-
 
| &nbsp; || IND %1.phy %1.dak(I%tmp(0)) 1 1
 
|-
 
|}
 
  
This will turn on the red led in the assosiated DAK key as long as the door is open.
+
<br>
----
 
  
: '''Station Down'''
+
====Outgoing Conversation====
[[Image:CRM 15.PNG|left|500px|thumb]]
+
To turn on the green led in the associated DAK key when an outgoing call is made, create this event:
 +
[[Image:CRMV ConvOut.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|  
+
{{Code2|
|-
+
IND %1.phy %1.dak(I%2.dir) 2 1
|width="100pt"|'''Event Owner''':
+
}}
|width="300pt"| A group of stations || ''Use UDP group 8 for all stations''
 
|-
 
|'''Event type''': || 13 - Faulty station line
 
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || ON or OFF
 
|-
 
|'''When related to''': || N/A
 
|-
 
|'''Action''': || tmp 0 "%1.dir" || ''Temporarily store the station directory number''
 
|-
 
| &nbsp; || OWN 105 || ''Set the CRM directory number as owner of the event''
 
|-
 
| &nbsp; || IND %1.phy %1.dak(I%tmp(0)) 1 1
 
|-
 
| &nbsp; || IND %1.phy %1.dak(I%tmp(0)) 2 1
 
|-
 
|}
 
  
This will turn on the red and green led in the assosiated DAK key as long as the station is reported down.
+
<br>
  
= DAK Redirection =
+
====Incoming Conversation====
[[File:CRM 10.PNG|left|thumb|500px|DAK Layout]]
+
To turn on the green led in the associated DAK key when an incoming call is received, create this event:
 +
[[Image:CRMV ConvIn.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
IND %1.phy %1.dak(I%2.dir) 2 1
 +
}}
 +
 +
<br>
  
Unused DAK tables from other stations must be borrowed to extend the CRM DAK table. CRM's using the same DAK layout can redirect to the same tables.
+
====Station faults ====
[[File:CRM 11.PNG|left|thumb|500px|Redirecting DAK table to physical 501, 502 ... 510]]
+
To turn on the red and green led in the associated DAK key when a station is reported faulty, create this event:
 +
[[Image:CRMV StatErr.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
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
 +
 +
<br>
  
The DAK key configuration must be performed at the users DAK table to which the original CRM DAK table is pointing:
+
====Busy indication ====
[[File:CRM 12.PNG|thumb|left|500px]]
+
To turn on steady red LED in the associated DAK key when a station is reported busy, create this event:
 +
[[Image:Busy Indication CRM.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
OWN r 105
 +
IND %2.phy %2.dak(I%1.dir) 1 1
 +
}}
  
[[File:CRM 13.PNG|left|thumb|500px|Here DAK 91-100 is shown configured from the DAK table at physical #510]]
+
105 is the directory number of the CRM
 +
 
 +
<br>
 +
 
 +
====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: <br>
 +
To turn on the red led in the associated DAK key when input 3 of the IP substation 159 is activated, create this event:
 +
[[Image:CRMV DoorStat.PNG|left]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
 +
{{Code2|
 +
OWN r 105
 +
IND %2.phy %2.dak(I%1.dir) 1 1
 +
}}
 +
 +
105 is the directory number of the CRM
 +
 +
<br>
  
= Transfer =
+
==== Lamp Test ====
Manual:
+
To perform a test of all LEDs in CRMV station (including the DAK48 panel), dial the [[Output station lamp test feature|code 7874]]. The station must be a [[SuperUser]], or have the right privileges in the [[Class of service]] settings.
* Transfer calls is done by using the feature code 71 + destination directory number
 
* Call Requests must be transferred using the feature code 7870 + destination directory number
 
* To reset the transfer dial 70.  
 
  
Automatic:
+
Note that this feature requires software version 2.5.3.0 or later in the [[IP Flush Master - 1008031000|CRMV main module]].
A typical CRM application is to transfer calls and call requests from a local guard to a main guard. In the example below two scenarios are shown:
 
  
1: The local guard is leaving his station for a while and transfers all calls and call requests to the main guard (directory number 110) by pressing D1 (DAK 1).
+
=== Call Forwarding ===
 +
==== Manual Call Forwarding ====
 +
Call Requests are manually forwarded by dialing the [[Transfer Call Request feature|feature code 7870]] + destination directory number. To reset the call forwarding, dial 70.
  
DAK 1 is configured with an [[Event Trigger (Event Type)|event trigger]]:
+
The Forwarding feature can be assigned to a DAK key for simple operation:
[[File:CRM 16.PNG|thumb|left|500px]]
+
[[File:CR Forwarding.PNG|thumb|left|500px|DAK 1 activates forwarding of the call request to station number 110. DAK 2 resets the forwarding]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
When a CRM station presses D1 an event trigger (9534) is dialled triggering an event:
+
==== Call escalation ====
[[Image:CRM 17.PNG|left|500px|thumb]]
+
If the Call Request is not answered within a preset time, it can be automatically forwarded to a predefined destination:
 +
[[File:CallReqForwarding.PNG|thumb|left|500px|Enabling "Automatic Search" on Call Request timeout]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
{|
 
|-
 
|width="100pt"|'''Event Owner''':
 
|width="400pt"| The CRM-V station or a group of CRM-V stations || ''Enter the physical station number or the UDP group number''
 
|-
 
|'''Event type''': || 15 - Event Trigger Feature
 
|-
 
|'''Subevent''': || 0
 
|-
 
|'''When change to''': || ON
 
|-
 
|'''When related to''': || Directory Nnumber: 9534
 
|-
 
|'''Action''': || IF %udd(%1.dir) || ''Toggle function: checks transfer status''
 
|-
 
| &nbsp; || $TRF L%1.dir "" || ''Remove call transfer''
 
|-
 
| &nbsp; || $SCRT L%1.dir || ''Remove Call Request transfer''
 
|-
 
| &nbsp; || IND %1.dir %1.dak(I%2.dir) 1 1 OFF || ''Turn off red LED in D1''
 
|-
 
| &nbsp; || LOG "Transfer deactivated from %1.dir %1.nam to Main Guard" || ''Log the action''
 
|-
 
| &nbsp; || WUDD %1.dir 0 || ''Toggle function: set transfer status to off''
 
|-
 
| &nbsp; || STOP
 
|-
 
| &nbsp; || ENDIF
 
|-
 
| &nbsp; || $TRF L%1.dir "I110" || ''Set call transfer to Main Guard''
 
|-
 
| &nbsp; || $SCRT L%1.dir L110 || ''Set Call Request transfer to Main Guard''
 
|-
 
| &nbsp; || IND %1.dir %1.dak(I%2.dir) 1 1 ON || ''Turn on red LED in D1''
 
|-
 
| &nbsp; || LOG "Transfer activated from %1.dir %1.nam to Main Guard" || ''Log the action''
 
|-
 
| &nbsp; || WUDD %1.dir 1 || ''Toggle function: set transfer status to on''
 
|-
 
|}
 
  
''See also:''
 
* ''[[Forward unattended Call Request (Event Handler)]]''
 
* ''[[Forwarding of Call Request to external telephone]]''
 
  
= Additional Settings =
+
Predefined destinations:
==Autosearch==
+
*If the call should be forwarded as a regular call to station 110, enter '''I 110'''.
Calls and Call Requests can be forwarded automatically to a predefined receiver if unanswered :
+
*If the call should be forwarded as a Call Request to station 110, enter '''I 627 I 110'''.
[[File:CRM 18.PNG|thumb|left|500px|Users & Stations &rarr; Automatic Search]]
+
*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.
<br style="clear:both;" />
+
*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:
  
[[File:CRM 19.PNG|left|thumb|500px|Users & Stations &rarr; DAK]]
+
[[File:CR AutoSearchTime.PNG|left|thumb|500px|Set the time before the call request is forwarded]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
==Audio Indication==
 
See: ''[[Call_request#Call_Request_notification_when_Station_type_is_set_to_.22CRM.22|Call Request Notification when Station type is set to CRM]]''
 
  
Default Priority level    Arrival notification    Queue notification
+
See also: [[Automatic_Search#Forward_unattended_Call_Request]]
-----------------------------------------------------------------------
 
  0 –  59                No tone                Beep every minute
 
  60 – 119                Dut-dut-dut tone        Beep every minute
 
120 – 149                Dut-dut-dut tone        Urgent Feature Reminder (configurable)
 
150 – 255                No tone                Private ringing tone
 
  
To configure the [[Urgent feature reminder]]:
+
===Optional settings ===
[[File:CRM 20.PNG|thumb|left|500px|Exchange & System &rarr; System &rarr; Calls and Options]]
+
* [[Answer call requests by pressing M-key]]
<br style="clear:both;" />
+
* [[Answer call requests by lifting the Handset]]
 +
* [[:Category: Control Room Applications|Control Room Applications]]
  
To change the default priority levels:
+
== Software Requirements ==
[[File:CRM 21.PNG|thumb|left|500px|Exchange & System &rarr; System &rarr; Calls and Options]]
+
This station is fully supported as form AlphaCom version 10.50
<br style="clear:both;" />
 
  
=Applications=
 
See [[:Category: Control Room Applications]]
 
  
[[Category: Control Room Stations - CRM]]
+
[[Category: INCA Stations]]

Latest revision as of 14:12, 26 April 2024

AI.png
CRM V with all optional modules

The CRM-V Station is designed for control room applications. This article describes how to configure the CRM-V station when used with an AlphaCom server.

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:

CRM-V Installation

AlphaPro 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


  • When the "Station type" = Master, the navigation buttons are reported as DAK 21-24.
  • When the "Station type" = CRM, the navigation buttons are reported as DAK 101-104 (from AMC 12.3.3.4).

Enable the DAK-48 unit

CRM-V DAK Expansion License

A CRM-V DAK Expansion 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

Upon reception of a new call request there is a notification tone (dut-dut-dut) played in the loudspeaker.

This notification tone is by default enabled in software 11.5.3.4 and newer.

In older software this tone is disabled when the Station Type is set to "CRM", but can be enabled by creating an event with the following parameters:

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.

Enable "Call Request notification" tone for physical number 49


Action commands:

$SNV Q%op(%gnv(5,8,xx,17),


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.


Ringing Group call (or Call Request)

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

CRMV CallReq.PNG


Action commands:

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:

CRMV ConvOut.PNG


Action commands:

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:

CRMV ConvIn.PNG


Action commands:

IND %1.phy %1.dak(I%2.dir) 2 1



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 commands:

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


Busy indication

To turn on steady red LED in the associated DAK key when a station is reported busy, create this event:

Busy Indication CRM.PNG


Action commands:

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


105 is the directory number of the CRM


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 commands:

OWN r 105
IND %2.phy %2.dak(I%1.dir) 1 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 requires software version 2.5.3.0 or later in the CRMV main module.

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 destination:

Enabling "Automatic Search" on Call Request timeout



Predefined destinations:

  • If the call should be forwarded as a regular call to station 110, enter I 110.
  • If the call should be forwarded as a Call Request to station 110, enter I 627 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



See also: Automatic_Search#Forward_unattended_Call_Request

Optional settings

Software Requirements

This station is fully supported as form AlphaCom version 10.50