Actions

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

From Zenitel Wiki

 
Line 1: Line 1:
 +
= Display =
 +
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.
 +
[[File:CRM 5.PNG|left|500px|thumb]]
 +
<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.
 +
 +
If the CRM station is an IP Station, the CRM station type selection will also turn on the backlight constantly.
 +
 +
Stations not set as CRM will receive all mail messages in the two line display like this:
 +
[[File:CRM 6.PNG|left|500px|thumb|Standard display station without any configuration having received three mail messages]]
 +
<br style="clear:both;" />
 +
 +
In AlphaPro there is a flag that can be set to change the [[Users_%26_Stations_(AlphaPro)#Station_Type|display behaviour]] whenever there is an incoming mail for two line display stations:
 +
[[File:CRM 8.PNG|left|500px|thumb]]
 +
<br style="clear:both;" />
 +
 +
The display will then look like this when a mail message arrives:
 +
[[File:CRM 7.PNG|left|thumb|500px|Standard display station with configured display behavour having received three mail messages.]]
 +
<br style="clear:both;" />
 +
 +
= Queue Navigation =
 +
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 default navigation keys for a CRM 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 highlighted entry)
 +
 +
The navigation keys can be configured using AlphaPro:
 +
[[File:CRM 9.PNG|left|thumb|500px|Users & Stations &rarr; DAK: Queue operation codes]]
 +
<br style="clear:both;" />
 +
 +
The queue for two line display stations can be navigated with:
 +
* 0 = Delete entry
 +
* 2 = Step to top
 +
* 3 = Step to last
 +
* 7 = Step to next entry
 +
* 8 = Answer current mail
 +
* 9 = Step to previous entry
 +
 +
= LED Control =
 +
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]]
 +
<br style="clear:both;" />
 +
 +
The two LED's (red and green) can be controlled individually using the [[IND]] command in the [[Event Handler]].
 +
 +
Typical events to control LED's:
 +
 +
:'''Incoming mail (i.e. Call Request received):'''
 +
[[Image:CRM 1.PNG|left|500px|thumb]]
 +
<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]]
 +
<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''': || 08 - Conversation - Outgoing
 +
|-
 +
|'''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 outgoing call is made.
 +
----
 +
 +
: '''Incoming Conversation'''
 +
[[Image:CRM 3.PNG|left|500px|thumb]]
 +
<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.
 +
----
 +
 +
: '''Door Status'''
 +
[[Image:CRM 4.PNG|left|500px|thumb]]
 +
<br style="clear:both;" />
 +
{|
 +
|-
 +
|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.
 +
----
 +
 +
: '''Station Down'''
 +
[[Image:CRM 15.PNG|left|500px|thumb]]
 +
<br style="clear:both;" />
 +
{|
 +
|-
 +
|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.
 +
 +
''See also:''
 +
* ''[[CRM_IV:_Indicate_status_of_remote_stations_in_AlphaNet|CRM-IV: Indicate status of remote stations in AlphaNet]]''
 +
 +
= DAK Redirection =
 +
[[File:CRM 10.PNG|left|thumb|500px|DAK Layout]]
 +
<br style="clear:both;" />
 +
 +
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.
 +
[[File:CRM 11.PNG|left|thumb|500px|Redirecting DAK table to physical 501, 502 ... 510]]
 +
<br style="clear:both;" />
 +
 +
The DAK key configuration must be performed at the users DAK table to which the original CRM DAK table is pointing:
 +
[[File:CRM 12.PNG|thumb|left|500px]]
 +
<br style="clear:both;" />
 +
 +
[[File:CRM 13.PNG|left|thumb|500px|Here DAK 91-100 is shown configured from the DAK table at physical #510]]
 +
<br style="clear:both;" />
 +
 +
= Transfer =
 +
Manual:
 +
* 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:
 +
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).
 +
 +
DAK 1 is configured with an [[Event Trigger (Event Type)|event trigger]]:
 +
[[File:CRM 16.PNG|thumb|left|500px]]
 +
<br style="clear:both;" />
 +
 +
When a CRM station presses D1 an event trigger (9534) is dialled triggering an event:
 +
[[Image:CRM 17.PNG|left|500px|thumb]]
 +
<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 =
 +
==Autosearch==
 +
Calls and Call Requests can be forwarded automatically to a predefined receiver if unanswered :
 +
[[File:CRM 18.PNG|thumb|left|500px|Users & Stations &rarr; Automatic Search]]
 +
<br style="clear:both;" />
 +
 +
[[File:CRM 19.PNG|left|thumb|500px|Users & Stations &rarr; DAK]]
 +
<br style="clear:both;" />
 +
 +
==Audio Indication==
 +
Default Priority level    Arrival notification    Queue notification
 +
-----------------------------------------------------------------------
 +
  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]]:
 +
[[File:CRM 20.PNG|thumb|left|500px|Exchange & System &rarr; System &rarr; Calls and Options]]
 +
<br style="clear:both;" />
 +
 +
To change the default priority levels:
 +
[[File:CRM 21.PNG|thumb|left|500px|Exchange & System &rarr; System &rarr; Calls and Options]]
 +
<br style="clear:both;" />
 +
 +
''See also:''
 +
* ''[[Call_request#Call_Request_notification_when_Station_type_is_set_to_.22CRM.22|Call Request Notification when Station type is set to CRM]]''
 +
 +
= Related Articles =
 +
* [[Answer call requests by pressing M-key]]
 +
* [[Emergency group call with acknowledge]]
 +
* [[Anti-nuisance control (Event Handler)]]
 +
* [[Audio Monitoring - Scanning]]
 +
* [[Audio Monitoring - Simplex Conference]]
 +
* [[Call restriction from guard station to cell station (Event Handler)]]
 +
  
  
 
[[Category: Control Room Stations - CRM]]
 
[[Category: Control Room Stations - CRM]]

Revision as of 12:29, 22 May 2015

Display

By setting a station to Station Type: CRM in AlphaPro the display layout will change from the standard two line display to a four line display.

CRM 5.PNG


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.

If the CRM station is an IP Station, the CRM station type selection will also turn on the backlight constantly.

Stations not set as CRM will receive all mail messages in the two line display like this:

Standard display station without any configuration having received three mail messages


In AlphaPro there is a flag that can be set to change the display behaviour whenever there is an incoming mail for two line display stations:

CRM 8.PNG


The display will then look like this when a mail message arrives:

Standard display station with configured display behavour having received three mail messages.


Queue Navigation

Incoming mails (typically Call Requests) to a CRM station will form up a queue in the order they are coming in, where the last mail is at the bottom. All incoming mails have a 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 default navigation keys for a CRM 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 highlighted entry)

The navigation keys can be configured using AlphaPro:

Users & Stations → DAK: Queue operation codes


The queue for two line display stations can be navigated with:

  • 0 = Delete entry
  • 2 = Step to top
  • 3 = Step to last
  • 7 = Step to next entry
  • 8 = Answer current mail
  • 9 = Step to previous entry

LED Control

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.

CRM 14.PNG


The two LED's (red and green) can be controlled individually using the IND command in the Event Handler.

Typical events to control LED's:

Incoming mail (i.e. Call Request received):
CRM 1.PNG


Event Owner: 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 is received.

Outgoing Conversation:
CRM 2.PNG


Event Owner: The CRM-V station or a group of CRM-V stations Enter the physical station number or the UDP group number
Event type: 08 - Conversation - Outgoing
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 outgoing call is made.

Incoming Conversation
CRM 3.PNG


Event Owner: 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.

Door Status
CRM 4.PNG


Event Owner: 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 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
  OWN 105 Set the CRM directory number as owner of the event
  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.

Station Down
CRM 15.PNG


Event Owner: 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
  OWN 105 Set the CRM directory number as owner of the event
  IND %1.phy %1.dak(I%tmp(0)) 1 1
  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.

See also:

DAK Redirection

DAK Layout


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.

Redirecting DAK table to physical 501, 502 ... 510


The DAK key configuration must be performed at the users DAK table to which the original CRM DAK table is pointing:

CRM 12.PNG


Here DAK 91-100 is shown configured from the DAK table at physical #510


Transfer

Manual:

  • 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: 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).

DAK 1 is configured with an event trigger:

CRM 16.PNG


When a CRM station presses D1 an event trigger (9534) is dialled triggering an event:

CRM 17.PNG


Event Owner: 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
  $TRF L%1.dir "" Remove call transfer
  $SCRT L%1.dir Remove Call Request transfer
  IND %1.dir %1.dak(I%2.dir) 1 1 OFF Turn off red LED in D1
  LOG "Transfer deactivated from %1.dir %1.nam to Main Guard" Log the action
  WUDD %1.dir 0 Toggle function: set transfer status to off
  STOP
  ENDIF
  $TRF L%1.dir "I110" Set call transfer to Main Guard
  $SCRT L%1.dir L110 Set Call Request transfer to Main Guard
  IND %1.dir %1.dak(I%2.dir) 1 1 ON Turn on red LED in D1
  LOG "Transfer activated from %1.dir %1.nam to Main Guard" Log the action
  WUDD %1.dir 1 Toggle function: set transfer status to on

See also:

Additional Settings

Autosearch

Calls and Call Requests can be forwarded automatically to a predefined receiver if unanswered :

Users & Stations → Automatic Search


Users & Stations → DAK


Audio Indication

Default Priority level    Arrival notification    Queue notification
-----------------------------------------------------------------------
  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:

Exchange & System → System → Calls and Options


To change the default priority levels:

Exchange & System → System → Calls and Options


See also:

Related Articles

Retrieved from "https://wiki.zenitel.com/w/index.php?title=CRM_V_-_Control_Room_Master&oldid=133807"