Mycalls And Virtual Loopback Reporting - NEC Univerge SV9100 Installation Manual

MyCalls and Virtual Loopback Reporting

MyCalls can report on calls that are passed through virtual loopback trunks on the SV9100. This is
because SMDR and P commands are output for loopback trunks just like they are for any other trunk
type. Loopbacks can often be configured on an SV9100 to give greater flexibility for call routing and
reporting.
Previously if a call arrived on a real trunk and was passed around a loopback trunk, there would be
two unrelated SMDR records output, these would both be displayed in the call records view and be
available in the MyCalls reports.
The example below shows a call that arrived on ISDN trunk 1 and was passed round virtual loopback
trunk 31. The call was then answered by extension 200. The two calls are listed next to each other
but there is no easy way to know that the two calls are associated. The big downside to the call
records being displayed like this is if you have call recording. This is because the recorded call is
associated with the real trunk and not the virtual trunk. If you were to filter the call records view to
show calls for ext 200, there would be no way to playback the associated recorded call.
There is an combined enhancement in SV9100 system software and MyCalls version 4 and above
that tags loopback calls to the trunk that the call originated on. The enhancement to the system
software marks the SMDR output to indicate the call has been passed around a loopback. This
feature is set by MyCalls when it does the configuration import and enables PRG 35-02-24, Virtual
Loop Marking. MyCalls version 4 will use the virtual loop marking feature to group loopback call to
real calls.
The screenshot below shows the same call as above – a call that arrives on real trunk 1, passes
round a loopback and is answered by extension 200. The call type now shows as an Incoming
Transfer call with the + icon shown on the far left of the call record.
17 | P a g e