Imagicle Call Recording provides an exclusive approach to play announcements for incoming/outgoing calls, both internal and external. It offers two unique methods for different recording technologies, leveraging CURRI protocol (Cisco UCM External Call Control – ECC) or TAPI-based Cisco Agent Greeting feature, without the need of any additional application.
In the following paragraphs, both methods are explained, with advices on correct usage depending on your Cisco/Imagicle environment.
This is the most recent recording announcement method for delivering announcements on any TAPI-enabled phone device. It offers the option to play an announcement for both incoming and outgoing calls, internal and external, and it is compatible with Media Forking, SIPREC and automated/manual Dial-In Conference recording methods.
Currently, Agent Greeting announcements method does not work on Jabber Desktop clients older than ver. 12.9. The announcement is actually played, but it is heard by local party only.
As soon as the call recording starts, if the recording phone is TAPI controlled, the application automatically triggers a call from the recording IP phone to a particular destination number, using the built-in bridge "agent greeting" feature.
Such destination number is composed by:
- a fixed prefix, that is the configured announcement pilot number (for instance 8600)
- further 4 digits randomly generated by the application.
The resulting number (for instance 86000113) must be routed by the CUCM to the Imagicle Call Recording SIP Trunk.
The call recorder answers such incoming call and plays the configured recording announcement, that is heard both by the recording party and the recorded party.
Please, notice that:
The following diagram describes such mechanism in the case of built-in bridge call recording.
You can enable this functionality from Imagicle web portal: Call Recording ⇒ Global Settings ⇒ Announcement
See a screenshot sample below:
Announcement pilot (prefix) field should be populated with an unused DN range (10,000 numbers), which corresponds to the pilot number involved to get the announcement prompt. Once entered, same web page shows below the relevant Route Pattern to be defined in CuCM to route calls to IAS through Call Recording SIP Trunk.
External incoming/outgoing calls fields allow to choose which voice prompt to be played when Call recording is triggered. Available options are:
In a high availability configuration involving mutiple Imagicle servers, the recording announcement should normally be provided by the same Imagicle node that records the call. Therefore, the annoucement call routing should follow the same node selection policy of the recording profile, that is, a route list with an active-standby selection.
However, if you deal with an Imagicle cluster and you need to balance the announcement calls among the available nodes, this is still possible. In order to do this, you need to:
1) create additional Route Patterns for the same Announcement Pilot pattern (for instance 8600XXXX), on different partitions. Each route pattern shuld point to a specific Ruote List, including one or more SIP Trunk(s) toward different recording nodes, ordered with chosen priority.
2) Create and assign different CSS to different phones in order to trigger different announcement route patterns.
See the below sample diagram:
This kind of phones partition allows to balance the overall load due to call recording announcements,
Enabling Call Recording announcement for internal calls is not a common case therefore it requires an advanced configuration on the Imagicle server.
Please, access to Imagicle server using Remote Desktop and edit this file:
C:\Program Files (x86)\StonevoiceAS\Apps\Recorder\Settings\Recorder.ini
Set the following parameter under the [Settings] section:
PlayAnnouncementForInternalCalls = 1
Then save the file.
This will play a default (built-in) announcement.
If you want to customize the voice message, open this folder:
C:\Program Files (x86)\StonevoiceAS\Apps\Recorder\Data\AudioFiles\User
and copy into such folder the announcement audio file for internal calls, that must have the following file format:
Once copied, please rename the wav file appending in front of the original filename the prefix "8049F0AA-B96C-45E3-8F29-CB9C014B4133_", so that the final filename is something like:
8049F0AA-B96C-45E3-8F29-CB9C014B4133_your file name.wav
ATTENTION:
In those special cases where it's not possible to discern internal/external call type or incoming/outgoing call direction, Imagicle Call Recording can still play a specific announcement. This is typical of below call scenarios:
To enable announcement in this particular scenario, you need to access Imagicle ApplicationSuite file system and amend a configuration file.
Please access to Imagicle server via RDP and edit this file:
C:\Program Files (x86)\StonevoiceAS\Apps\Recorder\Settings\Recorder.ini
Set the following parameter:
PlayAnnouncementForUnknownDirectionOrTypeCalls=1
This will play a default (built-in) announcement.
If you want to customize the voice message, open this folder:
C:\Program Files (x86)\StonevoiceAS\Apps\Recorder\Data\AudioFiles\User
Copy into such folder the announcement audio file for internal calls, that must have the following file format:
Once copied, please rename the wav file appending in front of the orignal filename the prefix "4C504392-CC9F-45BD-B0C4-22BC4C46E862_", so that the final filename is something like:
4C504392-CC9F-45BD-B0C4-22BC4C46E862_your file name.wav
ATTENTION:
This is the suggested recording announcement method for delivering announcements on Jabber clients prior to ver. 12.9, where other method is not supported. It offers the option to play an announcement for incoming calls only.
http://<Imagicle_IP>:80/fw/ecc.ashx?recordingPrompt=prompt_name
example
http://192.168.10.10:80/fw/ecc.ashx?recordingPrompt=Recording_Announcement
Available Trigger Points in CuCM are:
More information available in Cisco documentation here
Voicegateway needs to support SIP Early Media
In case of a SIP Voice Gateway
GLOBAL CONFIGURATION
voice service voip
sip
rel1xx require 100rel
OR at single dial peer:
DIAL-PEER CONFIGURATION
dial-peer voice 1000 voip
voice-class sip rel1xx require 100rel
In case of a H.323 Voice Gateway VG, No configuration needed.