Difference between revisions of "Parallel Ringing feature"
From Zenitel Wiki
m (Hyperlink UDP) |
m |
||
| Line 14: | Line 14: | ||
L111 is the example Directory number of the additional station to include in ringing. Change that to the actual number to include. | L111 is the example Directory number of the additional station to include in ringing. Change that to the actual number to include. | ||
| − | Up to 10 parallel ringing stations can be added for a call. Which can be done either by a list of $PAR_RING statements in the event action text, or by a $PAR_RING with a station group reference. A $PAR_RING which includes own station is silently ignored, so it is possible to create a single rule for several stations using [[UDP_group]]. | + | Up to 10 parallel ringing stations can be added for a call. Which can be done either by a list of $PAR_RING statements in the event action text, or by a $PAR_RING with a [[Groups|station group]] reference. A $PAR_RING which includes own station is silently ignored, so it is possible to create a single rule for several stations using [[UDP_group]]. |
Once the $PAR_RING action is triggered, the AlphaCom takes care of the rest: Allow accept of call from either station with M/OFF-HOOK, and disconnect stations when appropriate. | Once the $PAR_RING action is triggered, the AlphaCom takes care of the rest: Allow accept of call from either station with M/OFF-HOOK, and disconnect stations when appropriate. | ||
If the primary called stations is busy, parallel ringing is not started. (Because the Private Ringing Event is not triggered.) If the primary station is free, and call is private ringing mode, parallel ringing is activated on the other stations which are free. $PAR_RING has no effect on stations which are busy. | If the primary called stations is busy, parallel ringing is not started. (Because the Private Ringing Event is not triggered.) If the primary station is free, and call is private ringing mode, parallel ringing is activated on the other stations which are free. $PAR_RING has no effect on stations which are busy. | ||
Revision as of 09:16, 17 July 2007
Parallel Ringing is an extension to normal call with private ringing.
It is an application used on ships. Captains suite has a living room and a bedroom. One station in each. When somebody calls either of the stations, both stations rings. Captain can accept call on either of the stations with M-key or lifting handset. The bridge can use private override, and get conversation to the primary called station.
Previously the VA114D parallel connection board was used for this purpose.
In first version of the AlphaCom SW support for this feature (AMCX10.22), the function has to be programmed using the EventHandler, using one event rule:
- Owner: Captains station (either single station, or UDP group)
- Event type: Private_Ringing_mode_(Event_Type)
- When change to: On
- Action: $PAR_RING %1.ref L111
L111 is the example Directory number of the additional station to include in ringing. Change that to the actual number to include.
Up to 10 parallel ringing stations can be added for a call. Which can be done either by a list of $PAR_RING statements in the event action text, or by a $PAR_RING with a station group reference. A $PAR_RING which includes own station is silently ignored, so it is possible to create a single rule for several stations using UDP_group.
Once the $PAR_RING action is triggered, the AlphaCom takes care of the rest: Allow accept of call from either station with M/OFF-HOOK, and disconnect stations when appropriate.
If the primary called stations is busy, parallel ringing is not started. (Because the Private Ringing Event is not triggered.) If the primary station is free, and call is private ringing mode, parallel ringing is activated on the other stations which are free. $PAR_RING has no effect on stations which are busy.