SIP Terminals/Clients

The centralized NLOG feature is enabled for a SIP extension/SIP client(MiCollab)when its service profile is programmed to support the NLOG handling function. This is done by means of an I/O-command. This I/O-command needs parameters that state the extension directory number, and will turn off the local NLOG function in the terminal/client.

The same functionality is also available via the Service Node Manager. Centralized NLOG is supported for Mitel 6900 and Mitel 6800 SIP phones, of version 4.0.0 SP1 or later and SIP client (MiCollab, 9.5 and later versions).

The time before an unanswered call is registered can be defined in the system by means of I/O-command (AS).

For picking service, the centrally stored NLOG feature has the following options:

If the call is logged as outgoing or incoming for the picking extension (I/O command and generic extension service profile).
If the call is picked in alerting (or ringing) to log it as incoming-missed or incoming for the picked extension (I/O command and generic extension service profile).
If the picking number and name (if any) are included in the picked extension log (I/O command and generic extension service profile).
If the calling (or parked) number, name (if any), and dialed digits (or procedure) are included in the picking (or answering) extension log (I/O command and generic extension service profile).

For diversion service, the centrally stored NLOG feature has the following options:

If an unconditional diversion (direct diversion, follow-me, ECF, or message diversion) occurs for the diverted extension, it is logged as incoming-missed (I/O command, generic extension service profile).
If an unconditional diversion (direct diversion, follow-me) is executed, the dialed (diverted) number and name (if any) are included in the divert-to extension log (I/O command and generic extension service profile).
If diversion on no reply is executed, the dialed (diverted) number and name (if any) is included in the divert-to extension log (I/O command and generic extension service profile).
If diversion on no reply is executed for the diverted extension, the diverted-to number is included in the divert-to extension log (I/O command and generic extension service profile).
If diversion on busy is executed for the diverted extension, it is logged as incoming-missed (I/O command, generic extension service profile).
If diversion on busy is executed, the dialed (diverted) number and name (if any) is included in the divert-to extension log (I/O command and generic extension service profile).

↑