Greeting Injection & Announcements for Cisco CUCM
Call Telemetry injects audio greetings and announcements into active Cisco CUCM calls — compliance prompts, recording notifications, branding messages, or operational announcements. Greetings are bridged into the call so both parties hear the audio, and are controlled per-device through greeting policies.
Feature Comparison
Call Telemetry supports two injection methods. Choose based on your environment and requirements:
| JTAPI | CURRI | |
|---|---|---|
| Timing | On answer | Before call connects |
| Who hears the greeting | Both parties | Caller only |
| Media established during playback | Yes | No |
| Supported endpoints | Any — SIP, MGCP, PRI, analog | Phones, SIP trunks, and ICT trunks |
| Inbound / outbound matching | Yes, per device | Yes, via policy rules |
| DN exclusion | Yes — exclude internal transfers, help desk, conference numbers | Via policy rule patterns |
| Per-device greeting policies | Yes — via Greeting Policies assigned to devices | Yes — policy rules or per-device assignment |
| Audio managed in | Call Telemetry (upload, TTS, browser recording) | CUCM Announcements (uploaded to CallManager nodes) |
| DTMF skip key | Yes — OOB DTMF; requires conference mode for phone-to-phone calls | No |
| CUCM mechanism | Built-In Bridge / Agent Greeting | Early offer SIP media flow |
| Infrastructure | CTI Application User + CTI port pool | SIP trunk + CUCM annunciators + MRGL |
| License | Premium | Community |
Choose JTAPI when you need coverage on any endpoint type, want to manage audio centrally in Call Telemetry with TTS, or prefer to avoid SIP trunk early-offer and MRGL configuration changes.
Choose CURRI when you need the greeting to play before the call connects and you are comfortable uploading and managing media resources on the CallManager nodes directly.
Choose JTAPI over CURRI when you cannot establish compatible early offer, or need greetings for MGCP or PRI endpoints.
Learn more about CURRI policy greeting injection:
- CURRI Integration Setup — register Call Telemetry as an external call control profile in CUCM
- CURRI Greeting Injection — media resource planning, announcement configuration, and deployment
- Call Policy Design — routing patterns, inbound matching, and policy architecture
- CURRI Troubleshooting — MRGL configuration, annunciator allocation, and trace analysis
JTAPI Setup
JTAPI greeting injection uses CTI ports and an Application User to bridge audio into active calls. Audio is managed centrally in Call Telemetry — upload files, generate with TTS, or record from your browser. Requires a Premium license.
- Create a CUCM Application User with CTI permissions
- Add a JTAPI server in Call Telemetry (CUCM host + credentials)
- Provision a CTI Port Pool sized for expected concurrent injection volume
- Add Controlled Devices (which phones should be monitored)
- Create Greeting Policies and assign them to devices
See JTAPI Greeting Configuration for server setup, CTI port sizing, and CUCM audit.
CURRI Setup
CURRI plays a CUCM Announcement into the call before it connects — the caller hears the greeting while the phone is still ringing. Audio is managed directly on the CallManager nodes as CUCM Announcement resources, and injection is triggered through Call Telemetry policy rules. Included with the Community license (free).
Prerequisites
- CURRI integration configured and active — Call Telemetry must be registered as the external route plan for the target route patterns
- SIP Early Offer enabled on the trunk — CURRI greetings rely on early media, which requires the trunk to send SDP in the initial INVITE
- Annunciators in your MRGL — the Media Resource Group List assigned to the trunk or device pool must include an annunciator. Without one, CUCM cannot play the announcement
- Greeting audio uploaded as CUCM Announcements — upload
.wavfiles through CUCM Administration under Media Resources > Announcements and deploy to nodes in your cluster
Limitations
- SIP and ICT trunks only — analog and PRI trunks do not support early offer SIP signaling and cannot use CURRI greetings
- Pre-connect timing only — the greeting plays before the call connects
- Audio managed in CUCM — unlike JTAPI, you cannot use Call Telemetry's TTS engine or audio library. Files must be uploaded to each CallManager node
Setup Steps
- Configure CURRI integration in Call Telemetry
- Enable SIP Early Offer on your trunk in CUCM
- Verify annunciators are available in the MRGL for the trunk or device pool
- Upload greeting audio as CUCM Announcements
- Create a CURRI greeting rule in Call Telemetry policy
See CURRI Greetings for the full setup guide and CURRI Troubleshooting for MRGL and annunciator issues.
Call Flow Interaction Diagrams
These diagrams show how each injection method interacts with CUCM during a call. Use them to understand where in the call flow the greeting is played and which components are involved.
JTAPI Call Flow
CURRI Call Flow
Troubleshooting
- JTAPI Troubleshooting — connection failures, CTI pool issues, silent audio, Application User errors
- CURRI Troubleshooting — MRGL configuration, annunciator allocation, SDL trace analysis
Related
- JTAPI Greeting Configuration — server setup, CTI port sizing, CUCM audit
- Quick Start — end-to-end JTAPI setup walkthrough
- Audio Library — upload audio, generate TTS
- Greeting Policies — rules, DN exclusions, skip key
- CURRI Greetings — CUCM-side announcement setup
- CTI Application User — roles and device association