WarmTransfer
cisco onprem uc · published

Unified CM network-based and built-in bridge recording

Verified 2026-09-25 · 58 sources · tier 2–4

Unified CM provides two mechanisms for capturing call audio: IP phone-based built-in bridge (BIB) recording and network-based recording (NBR) 36​34. In built-in bridge recording, the phone forks two media streams to the recording server, whereas network-based recording allows media to be sourced from either the phone or a gateway 36​34.

Recording Modes and Line Configuration

Unified CM supports three recording modes: automatic silent recording, selective silent recording, and selective user call recording 48. Automatic silent recording captures all calls on the configured line appearance without providing any indication on the phone 4. In selective silent recording, a supervisor or recording application initiates recording through CTI, and the recording status is not displayed on the agent phone 44. Selective user call recording allows the agent to decide which calls to record using a softkey, a line key, or a CTI application, with the recording status displayed directly on the phone 45. The Record feature can be placed on a phone button template using the Line dropdown or on a softkey template in the Connected call state, after which the phones must be reset or have their configuration applied 40.

On the agent line, the Recording Option field provides three settings: Call Recording Disabled, Automatic Call Recording Enabled, and Selective Call Recording Enabled 23. The line configuration also contains the Recording Profile and Recording Media Source settings 22. The Recording Media Source setting configures either the gateway or the phone as the preferred media origin 22. When the gateway is preferred and media is unsecure (RTP), Unified CM routes media through the gateway if one exists in the call path and falls back to the phone when no gateway is present 15.

Profiles and Trunks

A recording profile specifies a name, a Recording Destination Address, and a Recording Calling Search Space, which must contain the partition of the route pattern directing calls to the recorder 39. The Recording Destination Address contains the directory number or URL of the recording server, or the URL of the CUBE Media Proxy server 12. For network-based recording, the gateway must connect to Unified CM over a SIP trunk 33. On the SIP trunk, the Recording Information parameter provides three options: None (trunk not used for recording), this trunk connects to a recording-enabled gateway, and this trunk connects to other clusters with recording-enabled gateways 54.

When connecting a SIP trunk from Unified CM to CUBE Media Proxy, Early Offer support must be enabled 24. See also SIP early offer and delayed offer. Unified CM also allows an optional SIP profile for recording, in which the Deliver Conference Bridge Identifier setting delivers the conference bridge identifier to the recorder 11.

Built-In Bridge Device Settings

At the cluster level, the Builtin Bridge Enable service parameter for the Cisco CallManager service configures the default built-in bridge state to On or Off 8. Individual phone devices have a Built In Bridge setting that can be configured to On, Off, or Default 7. The Default setting relies on the cluster service parameter, whereas On or Off overrides the cluster parameter for that individual device 7. If Built-in Bridge is set to On while Media Termination Point Required is checked on the device, recording can fail 6.

Support for recording on a given phone model can be verified by running the Cisco Unified Reporting Unified CM Phone Feature List report with Record chosen as the feature 38. In the field, a third-party recorder vendor's list indicates that 7800 and 8800 series models support built-in bridge recording, while older models including the 7912, 7940, and 7960 do not 21.

Network-Based Recording and CUBE Configuration

When utilizing a gateway for recording, Unified Communications Gateway Services must be enabled by configuring Cisco IOS services on the device, configuring the Extended Media Forking (XMF) provider, and verifying the setup 17. For gateway-based recording, Unified CM transmits media-forking requests over HTTP to the Unified Communications Services API on CUBE via the XMF provider 10. Configuring the XMF provider requires enabling the IOS HTTP server using ip http server 56. Under uc wsapi, the administrator defines source-address, configures provider xmf with remote-url entries pointing to Unified CM, and issues no shutdown 55. CUBE Extended Media Forking is restricted to voice; video forking is not supported 58.

When a gateway serves as the recording media source, SIP proxy servers cannot be placed between Unified CM and the recording gateway 35. In environments where CUSP sits in the call path, Cisco TAC documentation specifies configuring dedicated dummy SIP trunks in Unified CM to each CUBE, setting destination addresses that match the CUBE XMF configuration 49.

Multi-fork recording through CUBE Media Proxy allows media to be forwarded to up to 5 recording servers simultaneously 30. This feature is listed as supported on Cisco 4000 Series ISR, ASR, and CSR1000V platforms running IOS XE Gibraltar 16.10.1 or later 31. Multi-fork recording does not support video recording, SRTP forking of non-secure calls, SRTP fallback, or midcall block 32. CUBE Media Proxy does not support server groups in recorder dial-peers 28. While CUBE Media Proxy supports both Unified CM network-based recording and SIPREC, these two recording mechanisms cannot be used simultaneously on the same call 27. See also SIPREC call recording interface.

Signaling, Tones, and Call Interactions

Unified CM establishes recording by transmitting a separate SIP INVITE to the recorder for each forked stream—one for near-end voice and one for far-end voice—meaning a basic call results in 2 recording sessions 20. To identify the streams, call legs, and participating parties, the From header of each recording INVITE contains the parameters x-nearend or x-farend, x-refci, x-nearenddevice, x-farendrefci, x-farenddevice, and x-farendaddr 14. When the far-end party initiates a transfer, Unified CM transmits UPDATE messages containing the updated x-farendaddr parameter to the recorder 13. If the agent (near end) initiates a transfer, the current recording sessions are terminated with BYE, and new recording sessions start for subsequent call segments, including the consultation call 2.

Recording sessions do not survive hold; they are torn down when an agent puts a call on hold and re-established when the call resumes 18. WarmTransfer's reading of the sources is that because hold tears down sessions and transfers restart them, a single interaction generates multiple recording segments that recorders must correlate, such as by matching x-refci 42. Each recording session adds 2 calls to the busy hour call completion (BHCC) rate 5.

Notification tones are managed by two Cisco CallManager service parameters: Play Recording Notification Tone to Observed Target (for the agent) and Play Recording Notification Tone To Observed Connected Parties (for the customer) 53. These tone parameters operate as cluster-wide service parameters rather than per-line or per-profile options 51. When a call is subject to both recording and monitoring simultaneously, recording tones take precedence over monitoring tones 52.

Applicability

Applies to: Cisco Unified Communications Manager, Cisco CUBE Media Proxy, Cisco CUBE, and Cisco IP phones. Deployments: on-premises. Sources checked 2026-09-25. The Unified CM 12.5(1) documentation includes Multi-Fork Recording, the Recording Media Source selection rules, the Builtin Bridge Enable parameter, the two notification tone service parameters, and the restriction that recording sessions do not survive agent hold 1.

What remains uncertain

BIB recording support and firmware baselines on desk phone models not listed in the claims are not covered by the sources below. Recording options and feature parity for Webex Calling Dedicated Instance regarding BIB and NBR are not covered by the sources below. The default values of the two cluster-wide recording notification tone service parameters are not covered by the sources below. Legal consent requirements for call recording tones, including one-party versus all-party consent rules, are not covered by the sources below. Secure SRTP recording to secure recorders and behavior regarding SRTP fallback on authenticated or encrypted phones are not covered by the sources below. CUBE Media Proxy licensing and session counting mechanisms are not covered by the sources below. Cisco-compatible recorder partner integrations and the end-of-life status of Cisco MediaSense are not covered by the sources below. Sizing guidelines from the Collaboration SRND and system-wide BHCC impact at scale are not covered by the sources below.

See also

Depends on

Related to

  • Cisco IP phone firmware management — Built-in bridge recording depends on phone model support; the Phone Feature List report with feature Record is the authoritative check
  • SIPREC call recording interface — CUBE Media Proxy serves both Unified CM network-based recording and SIPREC but the two cannot coexist on the same call (cisco-cube-xe-media-proxy-recording)

Sources

  1. 1
    The Unified CM 12.5(1) Recording chapter already documents Multi-Fork Recording, the media source selection table, the Builtin Bridge Enable parameter, the two notification tone parameters and the rule that recording does not survive agent hold.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Recording · Recording chapter: Multi-Fork Recording; Recording Media Source Selection; Enable Built in Bridge for Cluster; Configure Recording Notification Tones; Recording Calls Do Not Survive Agent Hold · Checked 2026-09-25
  2. 2
    When the agent (near end) transfers a call, the existing recording sessions end with BYE and new sessions start, including for the consultation call.
    Recording Use Cases for Cisco Unified Communications Manager · Transfer and Conference Handling > Near-End Party (Agent) Transfers · Checked 2026-09-25
  3. 3
    To record authenticated phones, the Authenticated Phone Recording service parameter must be set to Allow Recording; its default is Do Not Allow Recording.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Authenticated Phones · Checked 2026-09-25
  4. 4
    Automatic silent recording records all calls on the configured line appearance and gives no indication on the phone.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > recording modes · Checked 2026-09-25
  5. 5
    Each recording session adds two calls to the busy hour call completion (BHCC) rate.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Busy Hour Call Completion · Checked 2026-09-25
  6. 6
    Recording can fail when Built-in Bridge is On and Media Termination Point Required is checked for the device.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Enable Built in Bridge for a Phone, note · Checked 2026-09-25
  7. 7
    The per-phone Built In Bridge setting is On, Off or Default. Default uses the cluster service parameter; On or Off overrides it for that phone.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Enable Built in Bridge for a Phone · Checked 2026-09-25
  8. 8
    The Builtin Bridge Enable service parameter (Cisco CallManager service) sets the cluster-wide built-in bridge default to On or Off.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Enable Built in Bridge for Cluster · Checked 2026-09-25
  9. 9
    In the Cisco conference use case, the three-way portion is recorded from the phone's built-in bridge when media routes through a conference bridge, even though the initial 1x1 leg used the gateway.
    Recording Use Cases for Cisco Unified Communications Manager · Recording Streams per Call Type > Conference Calls · Checked 2026-09-25
  10. 10
    For gateway-based recording, Unified CM sends media-forking requests to CUBE over HTTP to the Unified Communications Services API through the Extended Media Forking (XMF) provider.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording · Network based Recording > overview · Checked 2026-09-25
  11. 11
    In the optional SIP profile for recording, the Deliver Conference Bridge Identifier setting sends the conference bridge identifier to the recorder.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure SIP Profile for Recording · Checked 2026-09-25
  12. 12
    The Recording Destination Address is the directory number or URL of the recording server, or the URL of the CUBE Media Proxy server.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Create a Recording Profile, Recording Destination Address field · Checked 2026-09-25
  13. 13
    When the far-end party transfers the call, Unified CM sends the recorder UPDATE messages carrying the new x-farendaddr.
    Recording Use Cases for Cisco Unified Communications Manager · Transfer and Conference Handling > Far-End Party Transfers · Checked 2026-09-25
  14. 14
    The From header of recording INVITEs carries parameters x-nearend or x-farend, x-refci, x-nearenddevice, x-farendrefci, x-farenddevice and x-farendaddr to identify the stream, the call leg and the parties.
    Recording Use Cases for Cisco Unified Communications Manager · SIP Header Enhancement for Recording Sessions, From header example · Checked 2026-09-25
  15. 15
    With gateway preferred and unsecure (RTP) media, Unified CM selects the gateway when one is in the call path and falls back to the phone when none is.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Recording Media Source Selection, Table 1 · Checked 2026-09-25
  16. 16
    With gateway preferred and secure (SRTP) media, the media source selection table lists the phone as the selected source whether or not a gateway is in the path.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Recording Media Source Selection, Table 1 · Checked 2026-09-25
  17. 17
    When a gateway is used for recording, Unified Communications Gateway Services must be enabled: configure Cisco IOS services on the device, then the XMF provider, then verify.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Enable Unified Communications Gateway Services · Checked 2026-09-25
  18. 18
    Recording sessions are torn down when the agent puts the call on hold and are re-established when the agent resumes the call.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Recording Calls Do Not Survive Agent Hold · Checked 2026-09-25
  19. 19
    For a call that enters on a Cluster 1 gateway and is answered on a Cluster 2 phone, the phone is chosen to fork media, and on hold Cluster 2 asks Cluster 1 to stop the recording session.
    Recording Use Cases for Cisco Unified Communications Manager · Inter-Cluster Recording · Checked 2026-09-25
  20. 20
    Unified CM sends the recorder a separate SIP INVITE for each forked stream, one for the near-end voice and one for the far-end voice, so a basic call produces two recording sessions.
    Recording Use Cases for Cisco Unified Communications Manager · SIP Header Enhancement for Recording Sessions · Checked 2026-09-25
  21. 21
    A third-party recorder vendor's list marks older Cisco models such as the 7940, 7960 and 7912 as not supporting built-in bridge recording, and 7800 and 8800 models as supporting it.field report
    Cisco Phones Supporting Built-in-Bridge Feature · Supported phones table · Checked 2026-09-25
  22. 22
    Recording Profile and Recording Media Source are also set on the agent line; Recording Media Source makes either the gateway or the phone the preferred source of recording media.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure Agent Phone Line · Checked 2026-09-25
  23. 23
    The agent line's Recording Option field has three values: Call Recording Disabled, Automatic Call Recording Enabled and Selective Call Recording Enabled.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure Agent Phone Line · Checked 2026-09-25
  24. 24
    The SIP trunk from Unified CM to CUBE Media Proxy must have Early Offer support enabled.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure SIP Trunks for Recording, note · Checked 2026-09-25
  25. 25
    With selective recording and MediaSense, the consult call during a transfer is not recorded unless the agent starts it with the Record softkey.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Selective Recording and MediaSense · Checked 2026-09-25
  26. 26
    CUBE Media Proxy recorders are defined with media profile recorder, media class and media-recording proxy (or media-recording proxy secure) that reference recorder dial-peers, and proxy policy mandatory marks a recorder as mandatory.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Media Proxy and Recording · Media Proxy and Recording > Configure · Checked 2026-09-25
  27. 27
    CUBE Media Proxy supports both Unified CM network-based recording and SIPREC, but the two cannot be used together on the same call.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Media Proxy and Recording · Media Proxy and Recording > Overview; Restrictions · Checked 2026-09-25
  28. 28
    CUBE Media Proxy does not support server groups in recorder dial-peers.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Media Proxy and Recording · Media Proxy and Recording > Restrictions · Checked 2026-09-25
  29. 29
    The CUBE Media Proxy guide lists supported platforms including Cisco 4000 Series, ASR, CSR, Catalyst 8000V, 8200/8200L and 8300 Series routers.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Media Proxy and Recording · Media Proxy and Recording > Supported Platforms · Checked 2026-09-25
  30. 30
    Multi-fork recording through CUBE Media Proxy forwards media to up to five recording servers at once.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Multi-Fork Recording · Checked 2026-09-25
  31. 31
    The Unified CM guide lists multi-fork recording as supported on Cisco 4000 Series ISR, ASR and CSR1000V running IOS XE Gibraltar 16.10.1 or later.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Multi-Fork Recording · Checked 2026-09-25
  32. 32
    Multi-fork recording does not support video recording, SRTP forking of non-secure calls, SRTP fallback or midcall block.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Multi-Fork Recording, restrictions · Checked 2026-09-25
  33. 33
    For network-based recording, the gateway must connect to Unified CM over a SIP trunk.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview · Checked 2026-09-25
  34. 34
    In Unified CM network-based recording, recording media can be sourced from either the phone or the gateway.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview · Checked 2026-09-25
  35. 35
    When the gateway is the recording media source, SIP proxy servers cannot sit between Unified CM and the recording gateway.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > SIP Proxy Servers · Checked 2026-09-25
  36. 36
    In IP phone-based (built-in bridge) recording, the phone forks two media streams to the recording server.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview · Checked 2026-09-25
  37. 37
    With phone preferred, the media source selection table lists the phone as the selected source for any media type; if the preferred source is unavailable, Unified CM tries the alternate source.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Recording Media Source Selection · Checked 2026-09-25
  38. 38
    To check whether a phone supports recording, run the Cisco Unified Reporting Unified CM Phone Feature List report with Record selected as the feature.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Prerequisites · Checked 2026-09-25
  39. 39
    A recording profile has a name, a Recording Calling Search Space, which must contain the partition of the route pattern to the recorder, and a Recording Destination Address.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Create a Recording Profile · Checked 2026-09-25
  40. 40
    The Record feature can go on a phone button template (Line dropdown) or a softkey template (Connected call state), and phones must be reset or have the configuration applied afterwards.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure Record Feature Button / Configure Recording Softkey · Checked 2026-09-25
  41. 41
    When a secure tone and a recording tone both apply, the secure tone plays first and the recording tone follows.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Secure Tones · Checked 2026-09-25
  42. 42
    Since recording sessions end on hold and restart after transfers, one customer interaction can produce several recording segments; recorders must correlate them, for example by x-refci.inferred
    Recording Use Cases for Cisco Unified Communications Manager · Call Hold Behavior; Transfer and Conference Handling; SIP Header Enhancement (derived) · Checked 2026-09-25
  43. 43
    With automatic recording enabled, an endpoint in a select-and-join conference advertises a single codec and payload.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Select and Join Conference · Checked 2026-09-25
  44. 44
    In selective silent recording a supervisor or recording application starts recording through CTI and the recording status is not shown on the agent phone.
    Recording Use Cases for Cisco Unified Communications Manager · Selective Call Recording > Silent Recording · Checked 2026-09-25
  45. 45
    In selective user call recording the agent chooses which calls to record, using a softkey, a line key or a CTI application, and the recording status appears on the phone display.
    Recording Use Cases for Cisco Unified Communications Manager · Selective Call Recording > User Recording · Checked 2026-09-25
  46. 46
    Because the selection table puts SRTP calls with gateway preferred on the phone, secure-media recording in practice depends on the agent phone supporting built-in bridge recording.inferred
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > Recording Media Source Selection, Table 1 (derived) · Checked 2026-09-25
  47. 47
    The Unified CM 15 recording task flow runs in this order: recording profile, SIP profile (optional), SIP trunk to recorder, route pattern, agent phone line, built-in bridge, Unified Communications Gateway Services, notification tones, then Record button or softkey.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow · Checked 2026-09-25
  48. 48
    Unified CM supports three recording modes: automatic silent recording, selective silent recording and selective user call recording.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Overview > recording modes · Checked 2026-09-25
  49. 49
    The Cisco TAC mobile-agent recording note says that when CUSP sits in the path, you create dedicated (dummy) SIP trunks in Unified CM to each CUBE, with destination addresses matching the CUBE XMF configuration.
    CUCM Network based Recording for Mobile Agents · Configure > CUCM configuration, dummy SIP trunks for CUSP · Checked 2026-09-25
  50. 50
    In that TAC note, CUBE SIP profiles add a Call-Info header with x-cisco-origIP so that Unified CM reclassifies the call onto the correct trunk.
    CUCM Network based Recording for Mobile Agents · Configure > CUBE configuration, SIP profiles · Checked 2026-09-25
  51. 51
    The recording notification tone parameters are cluster-wide service parameters, not per-line or per-profile settings.
    CUCM Network based Recording for Mobile Agents · Configure > Recording notification (cluster-wide service parameters) · Checked 2026-09-25
  52. 52
    When a call is both recorded and monitored, recording tones take precedence over monitoring tones.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Interactions and Restrictions > Monitoring and Recording Tones · Checked 2026-09-25
  53. 53
    Two Cisco CallManager service parameters control recording notification tones: Play Recording Notification Tone to Observed Target (agent) and Play Recording Notification Tone To Observed Connected Parties (customer).
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure Recording Notification Tones · Checked 2026-09-25
  54. 54
    The SIP trunk Recording Information setting has three options: None (trunk not used for recording), this trunk connects to a recording-enabled gateway, and this trunk connects to other clusters with recording-enabled gateways.
    Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording · Recording Configuration Task Flow > Configure SIP Trunks for Recording, Recording Information · Checked 2026-09-25
  55. 55
    On CUBE, the XMF provider is configured under uc wsapi with source-address, then provider xmf with remote-url entries pointing to Unified CM, then no shutdown.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording · Network based Recording > Configure XMF provider · Checked 2026-09-25
  56. 56
    The XMF provider requires the IOS HTTP server to be enabled with ip http server.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording · Network based Recording > Prerequisites · Checked 2026-09-25
  57. 57
    CUBE Extended Media Forking does not support media mixing, high availability, VRF, hairpinning or forking of TDM legs.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording · Network based Recording > Restrictions · Checked 2026-09-25
  58. 58
    CUBE Extended Media Forking supports voice only; video forking is not supported.
    Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording · Network based Recording > Restrictions · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Media Proxy and Recording

Cisco Systems · 2026-04-25 · accessed 2026-09-25

tier 2 current vendor documentation

Cisco Unified Border Element Configuration Guide - Cisco IOS XE 17.6 Onwards - Network based Recording

Cisco Systems · 2026-04-25 · accessed 2026-09-25

tier 2 current vendor documentation

CUCM Network based Recording for Mobile Agents

Cisco Systems (TAC) · 2017-06-23 · accessed 2026-09-25

tier 2 current vendor documentation

Feature Configuration Guide for Cisco Unified Communications Manager, Release 12.5(1) - Recording

Cisco Systems · 2025-03-13 · accessed 2026-09-25

tier 2 current vendor documentation

Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Recording

Cisco Systems · 2026-09-16 · accessed 2026-09-25

tier 2 current vendor documentation

Recording Use Cases for Cisco Unified Communications Manager

Cisco Systems · 2025-12-05 · accessed 2026-09-25

tier 4 archived vendor documentation

Cisco Phones Supporting Built-in-Bridge Feature

MiaRec · accessed 2026-09-25

Cite this page

APA

WarmTransfer. (2026, September 25). Unified CM network-based and built-in bridge recording. WarmTransfer. https://warmtransfer.net/knowledge/cucm-built-in-bridge-recording

BibTeX

@misc{warmtransfer-cucm-built-in-bridge-recording,
  title  = {Unified CM network-based and built-in bridge recording},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/cucm-built-in-bridge-recording},
  note   = {Verified 2026-09-25}
}