Deprecated: The recording API has been replaced by the new Noojee API.

The recording API will no longer be supported post the release of 4.0

Retrieving a Recording

Note: The API will only accept POST requests.

Retrieving a recording is a little more complex than the simple start and stop methods. There are two key issues that have to be dealt with when retrieving a recording.

Recordings with multiple legs
Decoding the audio

When Noojee Admin records a call it is automatically split into separate recordings referred to as 'Legs'. A call is split each time the call goes through a transition. For example when a call enters a queue a split (Leg) is created, when the call is answered a second Leg is created. If the call is then transferred to a third party the call is once again split.

In order to access the entire call recording you need to retrieve each individual leg. In order to identify what legs are available you need to first retrieve the recording's meta data via the 'retrieveMetaData' call. From the meta data you can then uniquely identify and retrieve each Leg of the call in turn. If you don't specify a Leg when retrieving a recording the system will just return the first Leg of the call (which is likely to be ringing and nothing else).

Browser not supported