Matrix ETERNITY NE System Manual 1025
• As RCOC is a “Class of Service (CoS)” dependent feature, extensions that are not allowed this feature
in their CoS cannot have their calls returned; even if this feature is enabled on the Trunk they used to
make the call.
• In case of Call Transfer, RCOC will be set for the extension on which the call is transfered.
Feature Interaction: RCOC and DISA CLI Authentication
• When DISA CLI Authentication (Multiple Calls or One Call) is enabled on a trunk, whenever there is an
incoming call on the trunk, the system will first check the DISA CLI Authentication Table.
• If a matching entry is found in the DISA CLI Authentication table, the system will give dial tone to the caller.
• The caller can now invoke RCOC feature by dialing ** (pressing Star key twice).
OR
• The caller can make calls to an extension or an external number or use a feature as required.
• If the caller invokes RCOC feature by dialing ** (pressing Star key twice), the system will check the RCOC
Table.
• If a matching record entry is found, the system routes the call to the original caller and clears the record
entry from the RCOC Table.
How to configure
For this feature to work, it must be enabled on the Trunk and in the Class of Service of the extensions. See
“Enabling RCOC on Trunk” and “Enabling RCOC in Class of Service” below for instructions.
If desired, the related Timers, the RCOC Record Delete Timer and the Ring Back Tone Timer may also be changed.
See “System Timers and Counts” for instructions.
If you want SARVAM UCS to match the Trunk Port type and Trunk Port number of the incoming call with the Trunk
Parameters of the entry stored in the RCOC table, then you must enable Apply RCOC only if the caller calls
back on the same trunk from which the call was made check box in the System Parameters. See “System
Parameters” for instructions.
Enabling RCOC on Trunk
• Login as System Engineer.
• Click the trunk type on which you want to enable this feature. For example: Mobile.
To Next Page
