Howto:Soft-migration (looping in a innovaphone gateway) and Voice Recording
Voice Recording is possible if an innovaphone Gateway is lopped in between a trunk and an existing PBX in a soft-migration scenario. Here is how.
Applies To
This information applies to
Tested with V11 innovaphone Recording Build 1072 or higher
More Information
In some scenario there is not a partial migration, but all users are in the “old” PBX; the innovaphone gateway is used as a “Recording Interface”.
This situation is described here, other setups follow the same or similar logics.
As shown in the picture you need an innovaphone Gateway, PBX, Reporting and a Compact Flash.
The reporting can run on the gateway if an application processor is there, but also on an LAP(Linux Application Platform).
The CF can work with the innovaphone PBX, the application processor or be an external Webdav device. In theory even the PBX can run on an IPVA and the gateway works just as gateway.
Prerequisites
- innovaphone hardware or virtual gateway
- innovaphone linux application platform based reporting
- innovaphone voice recording
- appropriate licenses
Remark: V13-recording application does not provide trunk recording
License
You need the following licenses for such a scenario:
• 2 PBX registration licenses (PBX-min20 are good enough)
• For each user that should be recorded you need a dedicated voice recording license bound to this user
• For each user in the legacy PBX you need a reporting license (less are required if in the routing calls for certain users are bypassed)
• On top you need two additional reporting licenses
• The relative hardware license (PRI/BRI and DSP).
Example:
There is an existing legacy PBX with 100 users where 10 dedicted users shall be recorded. An IP6010 is used as gateway. This is the list of the licenses required:
• 2 x PRI
• 60 x DSP (or less if necessary)
• 1 x Recording Lic Base (bound to a dedicated user)
• 9 x Recording Lic (bound to dedicated users)
• 12 x Reporting Lic (bound to dedicated users, the trunk and the GW-object)
• 2 x PBX Port-Lic
In the GW the inbound and outbound calls to the 10 user follow a separate route. If that is not possible you need the reporting license for 102 User (and you have to do a lot of setup in the PBX).
This aspect is not further discussed and we assume that all users have to be recorded.
Problem Details
All users of the legacy PBX must be reproduced in the innovaphone PBX - just as dummy user, without registration and thus no need for a PBX license.
All incoming calls will be routed to the innovaphone PBX where the DID will found a user. In the trunk object the target for invalid, incomplete and Loopback DID is forwarded to a dummy with the same number as the legacy PBXs' operator. All dummy user have a CFU to “0” followed by their own legacy extension. For example the user “39” has a CFU to “039” and therefore the call is forwarded to the trunk line pointing to the legacy PBX.
The incoming GW will record the call writing the PCAP file to the CF.
Outgoing calls has to be handled in a different mode, because the call is going from one GW to the other without passing the PBX. Therefore you have to switch on the reporting flag even on that interface, only in this way the reporting receives the complete call information. From a recording point of view the problem is that no internal user of the PBX is involved, and therefore the record would be deleted when release is detected. To avoid that, in the setup of the recorder must be switch on the flag “softmigration”.
As stated in many parts of the recorder descriptions it is not a good idea record a user that should not be recorded at all, causing traffic and senseless disk usage.
Therefore in soft-migration scenarios it is a good idea doing a little bit of routing and just route the user to record through the relative interfaces.
The following chapter shows a sample setup for further explanation.
Installation
In the PBX create one Trunk object and one Gateway object.
In Gateway->GK register two interfaces respectively to the Trunk and Gateway objects in the PBX.
On both interfaces configure the “record to (URL)” field with the appropriate URL and enable “Media Relay”.
In our example the physical interface “TEL2” point to the legacy PBX while the physical interface “TEL3” is connected to the PSTN.
In Gateway->Routes you must create the routing for incoming and outgoing calls.
OUTGOING CALLS FROM LEGACY PBX TO PSTN:
- one route from the legacy PBX(TEL2) to the GW13.
- one from GW13 to TEL3(PSTN).
INCOMING CALLS FROM PSTN TO LEGACY PBX:
- one route from TEL3(PSTN) to GW1
- one route from GW1 to TEL2(Legacy PBX)
The Trunk object in the PBX will have the “Reporting” flag enabled. Enter in the trunk tab the number of the operator in the fields “Loopback”, “Incomplete” and “Invalid”.
The Gateway Object in the will also have the “Reporting” flag enabled.
Create all User of the legacy PBX and enter a CFU to the access number of the “TRUNK VR” (typical “0”) followed by the number of the extension, mark the CDR flag on each user.
Assign the same not active group to each user that should be recorded and enter that group later in the recorder setup.
The example shows the user 33 in the innovaphone PBX diverted to 033 and in the recording group “qwer”:
Create a SOAP dummy user for interfacing the Recording.
Known Problems
Once the call is in the legacy PBX the innovaphone PBX is not able to detect anything else than the release. Therefore if a call is answered from another user in the legacy PBX because of a call pickup or a CFNR or CFB for the recording the call is still recorded to the initial DID. This is also valid for outgoing calls; if the user calls an external number and transfer that call the reporting cannot detect that and again the entire call is recorded on the original caller. Also the CDR tickets will not show the internal switching of the legacy PBX. If that is a problem the only solution is to proceed with a full migration to the innovaphone PBX.
In softmigration scenarios the status field will show “no Agent” even if an Agent is involved. This because just at call end the real caller will be detected using the reporting.