Troubleshooting SIPREC recording failures

See also

Sources

1. 1
   For a new call, if the active SRS gives no response or a reject, the AudioCodes SBC routes the recording to the standby SRS.

   Sending SIPREC to Multiple SRSs - Mediant Software SBC User's Manual Version 7.6 · Sending SIPREC to Multiple SRSs · Checked 2026-10-02
2. 2
   AudioCodes licenses SIPREC sessions to active SRSs (SIPREC Streams) separately from sessions to standby SRSs (SIPREC Redundancy Streams); a redundant pair needs both.

   Sending SIPREC to Multiple SRSs - Mediant Software SBC User's Manual Version 7.6 · Sending SIPREC to Multiple SRSs (licensing) · Checked 2026-10-02
3. 3
   AudioCodes Mediant SBC can send recordings to up to six active SRSs, each optionally paired with a standby SRS in 1+1 redundancy.

   Sending SIPREC to Multiple SRSs - Mediant Software SBC User's Manual Version 7.6 · Sending SIPREC to Multiple SRSs · Checked 2026-10-02
4. 4
   AudioCodes SBC can record an SRTP call and send it to the SRS as RTP, or the reverse, controlled by the SBC Media Security Mode in the IP Profile of the SRS IP Group.

   SIPREC for SRTP Calls - Mediant Software SBC User's Manual Version 7.6 · SIPREC for SRTP Calls · Checked 2026-10-02
5. 5
   If the active SRS goes offline during a recorded call, the AudioCodes standby SRS must send a re-INVITE to the SBC, after which the SBC sends recorded RTP to the standby.

   Sending SIPREC to Multiple SRSs - Mediant Software SBC User's Manual Version 7.6 · Sending SIPREC to Multiple SRSs · Checked 2026-10-02
6. 6
   In AudioCodes SRS active-standby redundancy, SIP signalling goes to both active and standby SRSs but recorded RTP goes only to the active SRS.

   Sending SIPREC to Multiple SRSs - Mediant Software SBC User's Manual Version 7.6 · Sending SIPREC to Multiple SRSs · Checked 2026-10-02
7. 7
   Amazon Connect has a service quota on maximum active recording sessions from external voice systems per instance, which must be raised before the integration appears in the console.

   Integrate Connect Customer conversational analytics with external voice systems · Set up steps, Request service quota increases · Checked 2026-10-02
8. 8
   If credentials were created for an Amazon Connect conversational analytics connector, the external SIPREC source system must use the same credentials.

   Configure your external voice system for integration with conversational analytics · Step 3, Note · Checked 2026-10-02
9. 9
   For Amazon Chime SDK Voice Connector SIPREC, the service relies on SIPREC metadata and in most cases treats the stream label with the lowest lexicographic value as the AGENT channel.

   Call analytics processor and output destinations for the Amazon Chime SDK · Amazon Transcribe Call Analytics processor destinations, Note · Checked 2026-10-02
10. 10
    Amazon Connect streams at most 3 hours 45 minutes of SIPREC replica audio per call from an external voice system; audio past that is neither streamed nor analysed.

    Integrate Connect Customer conversational analytics with external voice systems · Requirements · Checked 2026-10-02
11. 11
    In Amazon Connect conversational analytics integration with an external voice system, if no agent is identified for a call the replica call terminates and no recording or analytics are produced.

    Integrate Connect Customer conversational analytics with external voice systems · Set up steps, Note under Add agents · Checked 2026-10-02
12. 12
    From IOS XE 17.18.2, when a recorder answers with inactive SDP, CUBE stops sending media packets to that recorder.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Feature Information for SIPREC, 17.18.2 row · Checked 2026-10-02
13. 13
    When the recorder answers CUBE's recording INVITE with 503 or 500, Cisco advises adding debug ip tcp transactions to check whether TCP connections to the recorder are being set up.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Troubleshooting > Nonworking Scenarios · Checked 2026-10-02
14. 14
    CUBE SIPREC fails when the recorder dial-peer's destination-pattern is a regular expression instead of a simple number (for example 1… instead of 1234).

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Troubleshooting > Nonworking Scenarios · Checked 2026-10-02
15. 15
    CUBE cannot fork the same call using both dial-peer-based recording and SIPREC recording.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
16. 16
    If SIPREC is not explicitly configured, CUBE falls back to its older Network-Based Recording (non-SIPREC) forking.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Prerequisites for SIPREC · Checked 2026-10-02
17. 17
    The CUBE media-recording command accepts at most five recorder dial-peer tags.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Configuring SIPREC, media-recording step · Checked 2026-10-02
18. 18
    CUBE does not record flow-around calls, SDP pass-through calls, RTP loopback or non-SIP calls with SIPREC.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
19. 19
    The command show voip recmsp session detail forked call-id, which shows forked and anchor-leg information together, was introduced in IOS XE 17.18.1a.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Feature Information for SIPREC, 17.18.1a row · Checked 2026-10-02
20. 20
    On hold and resume, CUBE sends the recorder a re-INVITE that reflects the new sendonly, recvonly or inactive direction and updates participant-stream associations in the metadata.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · SIPREC call flows / metadata examples (hold) · Checked 2026-10-02
21. 21
    Cisco lists an incorrect inbound dial-peer match, where the selected inbound dial-peer has no media-class, as a reason CUBE SIPREC recording does not start.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Troubleshooting > Nonworking Scenarios · Checked 2026-10-02
22. 22
    CUBE SIPREC does not record IPv6-to-IPv6 or IPv6-to-IPv4 calls.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
23. 23
    CUBE builds SIPREC metadata to draft-ietf-siprec-metadata-17, and the recorder must accept at least the version 17 metadata format.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Prerequisites for SIPREC · Checked 2026-10-02
24. 24
    CUBE does not support media parameter changes that the recording server requests through re-INVITE or UPDATE.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
25. 25
    CUBE does not support mid-call renegotiation or supplementary services on the recorder leg.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
26. 26
    Because the inactive-SDP behaviour is listed as a 17.18.2 feature, CUBE releases before 17.18.2 probably keep sending forked media to a recorder that answered inactive.inferred

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Feature Information for SIPREC, 17.18.2 row · Checked 2026-10-02
27. 27
    An incorrect recording-server IP address, or a recorder hostname that does not resolve, is a listed cause of CUBE SIPREC failure.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Troubleshooting > Nonworking Scenarios · Checked 2026-10-02
28. 28
    show voip recmsp session lists CUBE's active SIPREC recording sessions, and show voip recmsp session detail call-id gives per-stream state for one call.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Verifying SIPREC / Troubleshooting · Checked 2026-10-02
29. 29
    CUBE supports only the siprec option tag and the src feature tag from the SIPREC protocol; the RFC 7866 SDP extensions are not supported.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Prerequisites for SIPREC · Checked 2026-10-02
30. 30
    CUBE cannot SIPREC-record SRTP passthrough calls.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
31. 31
    On SRTP-to-RTP calls, CUBE forks media only from the RTP leg; forking on the SRTP leg is not supported.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC · Checked 2026-10-02
32. 32
    On a transfer, CUBE sends the recorder a re-INVITE whose metadata associates the new participant and disassociates the old one, keeping the same recording session.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · SIPREC call flows / metadata examples (transfer) · Checked 2026-10-02
33. 33
    When a call has several video m-lines, CUBE forks only the first video stream to the recorder, and does not fork application media streams.

    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards: SIP Forking · Restrictions for SIPREC (video) · Checked 2026-10-02
34. 34
    Across the SRCs reviewed, a failed recording leg does not by default drop the customer call; only an explicit setting such as Oracle's session-recording-required makes recording a call-admission condition.inferred

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-required parameter; compare HA Support · Checked 2026-10-02
35. 35
    On an Oracle SBC HA failover, calls in progress are preserved but recording dialogs in progress do not survive.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · High Availability (HA) Support · Checked 2026-10-02
36. 36
    With the hunt strategy, Oracle SBC tries the next SRS in the group after a SIP response above 399, a timeout or a TCP setup failure, trying each SRS once before treating recording as failed.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · Load Balancing > Hunt · Checked 2026-10-02
37. 37
    With simultaneous-recording-servers above 1, Oracle SBC treats recording as established once at least one SRS dialog succeeds, so one recorder can silently miss a call that another recorded.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-group > simultaneous-recording-servers note · Checked 2026-10-02
38. 38
    Oracle SBC supports only selective recording mode on a session-recording-server; persistent recording mode is not supported.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-server attribute > recording-mode · Checked 2026-10-02
39. 39
    Oracle recommends leaving session-recording-required disabled.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-required parameter · Checked 2026-10-02
40. 40
    On Oracle SBC each communication session recorded to one SRS counts as two calls, with two extra flows to the SRS per call, which matters for session capacity sizing.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · High Availability (HA) Support · Checked 2026-10-02
41. 41
    On Oracle SBC, session-recording-required is disabled by default, so calls proceed when no recording server is available; when enabled, calls are not set up without a recorder.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-required parameter · Checked 2026-10-02
42. 42
    With the default round-robin strategy, Oracle SBC adds only one SRS from the recording group, and if that SRS is unavailable the recording fails even though other SRSs in the group are up.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · Load Balancing > Round-robin · Checked 2026-10-02
43. 43
    Oracle SBC simultaneous-recording-servers sets how many SRS dialogs are opened per call, from 1 to 10 with a default of 1.

    Configuring SIPREC - Session Border Controller Call Monitoring Guide · session-recording-group > simultaneous-recording-servers · Checked 2026-10-02
44. 44
    In Oracle's documented REFER transfer flows, the SBC keeps the existing recording session and sends the SRS a re-INVITE with new SDP and metadata that adds the transfer target and stops the transferor.

    SIPREC Call Flows - Session Border Controller · Call transfer (REFER) call flows · Checked 2026-10-02
45. 45
    A UA that does not support the Session Recording Protocol extensions rejects the recording INVITE with 420 (Bad Extension), so a 420 from a recorder means it does not support the siprec option tag.

    RFC 7866: Session Recording Protocol · Section 6.1.1 Initiating a Recording Session · Checked 2026-10-02
46. 46
    A SIPREC metadata document can declare itself a complete snapshot or a partial update, so an SRS that only handles complete documents may mis-handle partial updates sent after hold or transfer.inferred

    RFC 7865: Session Initiation Protocol (SIP) Recording Metadata · dataMode element (summariser placed it in Section 5.1.2) · Checked 2026-10-02
47. 47
    When a communication-session media stream changes to or from inactive (for example on hold), RFC 7866 leaves the effect on the matching recording-session stream to SRC policy.

    RFC 7866: Session Recording Protocol · Section 7.1.1.1 · Checked 2026-10-02
48. 48
    SIPREC recording metadata is carried as an XML document of media type application/rs-metadata+xml, usually alongside the SDP in a multipart/mixed body.

    RFC 7865: Session Initiation Protocol (SIP) Recording Metadata · Section 5 Recording Metadata Format · Checked 2026-10-02
49. 49
    In SIPREC metadata a participant can have several associate and disassociate times within one communication session, which is how joins, leaves and transfers are represented.

    RFC 7865: Session Initiation Protocol (SIP) Recording Metadata · Participant/session association section (summariser placed it in Section 6.6.1) · Checked 2026-10-02
50. 50
    In the SIPREC architecture the SRC must have access to the media; a SIP proxy that does not handle media cannot act as an SRC, while a B2BUA or SBC in the media path can.

    RFC 7245: An Architecture for Media Recording Using the Session Initiation Protocol · Section 3.1 Location of the Session Recording Client · Checked 2026-10-02
51. 51
    RFC 7866 defines an SDP a=record attribute (on, off, paused) that indicates recording state to recording-aware UAs, and an a=recordpref attribute by which a UA states its recording preference.

    RFC 7866: Session Recording Protocol · Sections 7.1.2 and 7.1.3 · Checked 2026-10-02
52. 52
    RFC 7866 requires the SRC to put the +sip.src feature tag in the Contact URI and the siprec option tag in the Require header of the INVITE that starts a recording session.

    RFC 7866: Session Recording Protocol · Section 6.1.1 Initiating a Recording Session · Checked 2026-10-02
53. 53
    An SRS that is not ready to receive a recorded stream sets that stream to a=inactive, and offers a=recvonly in a later SDP offer once it is ready; an SRS normally answers each stream with a=recvonly.

    RFC 7866: Session Recording Protocol · Section 7.2 Procedures at the SRS · Checked 2026-10-02
54. 54
    An SRS may explicitly ask the SRC for a full metadata snapshot, which is the protocol remedy when the SRS's metadata view is incomplete.

    RFC 7866: Session Recording Protocol · Section 9.2 Metadata Snapshot Request · Checked 2026-10-02
55. 55
    If SRTP is used on both the communication session and the recording session with different keys, the SRC has to decrypt and re-encrypt the media for the recording session.

    RFC 7866: Session Recording Protocol · Section 8.2.1.1 · Checked 2026-10-02
56. 56
    Each stream element in SIPREC metadata refers to the SDP a=label of an m-line; if labels in the metadata do not match the SDP, the recorder cannot tie the audio to a participant.

    RFC 7865: Session Initiation Protocol (SIP) Recording Metadata · Section 5 and Section 6.7.1 (stream label) · Checked 2026-10-02
57. 57
    Twilio reports problems streaming SIPREC media to the partner recorder in the Twilio Debugger, and connectorName must match the SIPREC connector installed from the Marketplace.

    TwiML Voice: <Siprec> · <Siprec> overview and Attributes > connectorName · Checked 2026-10-02
58. 58
    The Twilio <Siprec> track attribute defaults to inbound_track; both_tracks must be set to send both sides of the call to the recorder.

    TwiML Voice: <Siprec> · Attributes > track · Checked 2026-10-02
59. 59
    Twilio allows at most four forked streams per call.

    TwiML Voice: <Siprec> · <Siprec> page, limits note · Checked 2026-10-02
60. 60
    Twilio's <Siprec> statusCallback reports SiprecEvent values siprec-started, siprec-stopped and siprec-error, with SiprecError and SiprecErrorCode giving error detail.

    TwiML Voice: <Siprec> · Attributes > statusCallback parameters · Checked 2026-10-02

Documents

Cite this page

WarmTransfer. (2026, October 2). Troubleshooting SIPREC recording failures. WarmTransfer. https://warmtransfer.net/knowledge/siprec-recording-failures

@misc{warmtransfer-siprec-recording-failures,
  title  = {Troubleshooting SIPREC recording failures},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/siprec-recording-failures},
  note   = {Verified 2026-10-02}
}