Mitel and virtual extension and my recordings are being rej

[John Richard Procter]

There are only 3 reason why calls should be rejected:

1. not enough licenses
2. the physical extensions to be recorded (recorded device)
   is not configured under "Inclusive Rules".
3. the rejected devices is configured under "Exclusive Rules".

When using the Mitel and Virtual extensions, the following must
be in place:

• Standard Mitel SMDR data as per SSL,
  MITEL 3300 Certified format..
• Latest version of the Mitel plugin, version 2008.3.20.1 or newer.
• SMDRLink for Windows, version 1.1.3.7, sending direct to AMETHYST
  and not via SMDRLink for Linux.
• AMTACDMitel for Windows (released 2008) when using a card solution
  and 'Configure Virtual Extensions' with client side recording.
• The physical extensions to be recorded must be configured
  under "Inclusive Rules".

If a call is rejected, please check the date and time of the log
entry in the rejected log and compair it with the same date and
time in the AMTACDMitel log. If a virtual extension was provided
by the PABX for AMTACDMitel this will be used to map the physical
and virtual extension thereby not causing the recording to be
rejected. If no virtual extension is provided, it will use what
was previously sent off with the physical extension - the list
remains the same and is not updated.

AMTACDMitel:
2008-04-07 00:04:40.687 -> ACD|7015|6186|
2008-04-07 00:23:04.796 -> ACD|7015||
In this example 7015 is the physical extension and 6186 is the virtual.

With the Sweeper version up to 1.5.9.0, there was a problem, where
when no virtual extension was sent from the PABX, a blank extension
was updated, which will cause the recording to be rejected. This
will be fixed in a future release of the Sweeper.