AutoCLIP Operation

Step-by-Step Process:

1. Inbound Call Arrives:

Customer: Dials +1-555-SALES
Trunk: Receives call on DID +1-555-SALES
PBX: Notes which DID received the call

2. Call Routed to Extension:

Inbound Route: Directs call to extension 2001 (Sales Rep)
PBX: Associates extension 2001 with DID +1-555-SALES
Storage: Stores this association temporarily

3. Call Completes:

Conversation: Sales rep talks with customer
Call Ends: Customer hangs up
PBX: Maintains DID association for callback period

4. Return Call Made:

Sales Rep: Presses callback button or redials
PBX: Checks AutoCLIP cache
Finds: Last inbound call for ext 2001 was on DID +1-555-SALES
Action: Sets outbound caller ID to +1-555-SALES

5. Customer Sees Familiar Number:

Customer Phone: Displays "+1-555-SALES"
Customer: "Oh, that's the sales number I called!"
Result: Customer answers

Technical Implementation:

Database Table: autoclip_cache
Columns:
  - extension_number
  - last_inbound_did
  - timestamp
  - trunk_id
  - caller_number

Entry Example:
  Extension: 2001
  DID: +15555551234
  Time: 2024-11-21 14:30:15
  Trunk: Trunk-Main
  Caller: +15559876543

Detailed Call Flow Examples

Example 1: Direct Return Call

Time: 10:00 AM
Event: Customer calls +1-555-SALES
Action: Routed to extension 2001
AutoCLIP: Records DID +1-555-SALES for ext 2001

Time: 10:15 AM (15 minutes later)
Event: Extension 2001 dials customer back
AutoCLIP: Checks cache, finds +1-555-SALES
Outbound Caller ID: +1-555-SALES
Result: Customer sees same number they called

Example 2: Multiple DID Scenario

Time: 9:00 AM
Event: Customer A calls +1-555-SALES
Action: Routed to extension 2001
AutoCLIP: Records +1-555-SALES for ext 2001

Time: 11:00 AM  
Event: Customer B calls +1-555-SUPPORT
Action: Routed to extension 2001
AutoCLIP: Updates to +1-555-SUPPORT for ext 2001

Time: 11:30 AM
Event: Extension 2001 returns call to Customer B
AutoCLIP: Uses latest DID: +1-555-SUPPORT
Result: Customer B sees support number they called

Example 3: Multiple Extensions

Extension 2001:
  Last inbound: +1-555-SALES
  AutoCLIP: Uses +1-555-SALES for callbacks

Extension 2002:
  Last inbound: +1-555-SUPPORT  
  AutoCLIP: Uses +1-555-SUPPORT for callbacks

Extension 2003:
  No recent inbound calls
  AutoCLIP: Falls back to default trunk caller ID

Each extension maintains independent DID memory

Example 4: Queue Calls

Time: 10:00 AM
Event: Customer calls +1-555-SUPPORT
Action: Enters support queue
Queue: Waits 2 minutes

Time: 10:02 AM
Event: Extension 3001 answers from queue
AutoCLIP: Records +1-555-SUPPORT for ext 3001

Time: 10:20 AM
Event: Extension 3001 returns call
AutoCLIP: Uses +1-555-SUPPORT
Result: Customer recognizes support number

Example 5: Transfer Scenario

Time: 10:00 AM
Event: Customer calls +1-555-MAIN
Initial: Answered by reception (ext 1000)
AutoCLIP: Records +1-555-MAIN for ext 1000

Time: 10:02 AM
Event: Transferred to sales (ext 2001)
AutoCLIP: Now also records +1-555-MAIN for ext 2001

Time: 10:30 AM
Event: Extension 2001 returns call
AutoCLIP: Uses +1-555-MAIN (main number customer called)
Result: Recognizable number

How Long AutoCLIP Remembers

Cache Duration Settings:

Short Duration (1 hour):

Setting: 3600 seconds
Use Case: High-volume call centers, frequent different callers
Reason: Avoid old DID associations
Behavior: After 1 hour, cache expires, uses default

Medium Duration (8 hours / Business Day):

Setting: 28800 seconds
Use Case: Standard business operations
Reason: Callbacks typically within same day
Behavior: Lasts full business day

Long Duration (24 hours):

Setting: 86400 seconds
Use Case: Sales, account management
Reason: May return call next day
Behavior: Persists overnight

Extended Duration (7 days):

Setting: 604800 seconds
Use Case: Project-based work, ongoing cases
Reason: Callbacks may be days later
Behavior: Maintains association for week

Cache Expiration Behavior:

Within Cache Period:

Time: 10:00 AM - Inbound call on +1-555-SALES
Time: 2:00 PM - Return call (4 hours later)
Cache: Still valid (within 8-hour setting)
Result: AutoCLIP uses +1-555-SALES

After Cache Expiration:

Time: 10:00 AM - Inbound call on +1-555-SALES
Time: 7:00 PM - Return call (9 hours later)
Cache: Expired (exceeded 8-hour setting)
Result: AutoCLIP falls back to default trunk caller ID

Cache Refresh on New Call:

10:00 AM: Call on +1-555-SALES (cache until 6:00 PM)
2:00 PM: New call on +1-555-SUPPORT (cache until 10:00 PM)
3:00 PM: Return call
Result: Uses +1-555-SUPPORT (most recent, still cached)

Manual Cache Clear:

Action: Admin clears AutoCLIP cache
Effect: All stored DID associations deleted
Behavior: All extensions fall back to default
Use Case: System maintenance, troubleshooting

Per-Extension Cache:

Extension 2001:
  Last Call: 10:00 AM on +1-555-SALES
  Expires: 6:00 PM (8 hours)
  
Extension 2002:
  Last Call: 2:00 PM on +1-555-SUPPORT
  Expires: 10:00 PM (8 hours)

Independent timers per extension

When AutoCLIP Can't Be Used

Fallback Scenarios:

Scenario 1: No Recent Inbound Call

Situation: Extension makes outbound call, but has no recent inbound calls
AutoCLIP: No cached DID
Fallback: Use extension's default outbound caller ID
Or: Use trunk default caller ID

Scenario 2: Cache Expired

Situation: Last inbound call was 10 hours ago, cache is 8 hours
AutoCLIP: Cache entry expired and deleted
Fallback: Extension default or trunk default

Scenario 3: Cached DID No Longer Available

Situation: DID was ported away or removed from trunk
AutoCLIP: Has cached DID, but DID no longer valid
Validation: System checks DID still exists
Fallback: If invalid, use extension/trunk default

Scenario 4: Trunk Doesn't Support Cached DID

Situation: Cached DID is on Trunk A, but outbound uses Trunk B
AutoCLIP: DID not available on outbound trunk
Fallback: Use Trunk B's default caller ID

Scenario 5: Manual Override

Situation: User manually selects different caller ID
AutoCLIP: Bypassed by user preference
Result: Uses user-selected caller ID

Scenario 6: Inbound Call Was Anonymous

Situation: Inbound call had no DID (direct IP call, internal)
AutoCLIP: No DID to cache
Fallback: Extension/trunk default

Fallback Hierarchy:

Priority 1: AutoCLIP cached DID (if valid and available)
  ↓ (if not available)
Priority 2: Extension configured outbound caller ID
  ↓ (if not configured)
Priority 3: User role default caller ID
  ↓ (if not configured)
Priority 4: Trunk default caller ID
  ↓ (always has a value)
Priority 5: Emergency number (last resort)

Configuration Example:

Extension 2001 Settings:
  AutoCLIP: Enabled (priority 1)
  Extension Outbound CID: +1-555-1234 (priority 2)
  Trunk Default: +1-555-MAIN (priority 4)

Scenario A: Recent inbound on +1-555-SALES
  Result: Uses +1-555-SALES (AutoCLIP)

Scenario B: No recent inbound
  Result: Uses +1-555-1234 (Extension setting)

Scenario C: Extension setting empty
  Result: Uses +1-555-MAIN (Trunk default)

Enable AutoCLIP per Trunk

Enable AutoCLIP: Toggle ON
Apply To: All extensions (default)
Cache Duration: 8 hours (28800 seconds)
Fallback: Extension default caller ID

Setting: Enabled (recommended)
Behavior: All extensions on this trunk use AutoCLIP
Use Case: Organization-wide implementation

Setting: Whitelist specific extensions
Behavior: Only listed extensions use AutoCLIP
Use Case: Pilot program, specific departments

Setting: Blacklist specific extensions  
Behavior: All except listed use AutoCLIP
Use Case: Executives who prefer fixed caller ID

Expected: Outbound caller ID = Inbound DID
If Different: Check cache, trunk settings, DID availability
Logs: Review AutoCLIP logs for debugging

Configure Cache Duration

Setting Cache Duration:

Location: Settings > Trunks > [Trunk] > AutoCLIP > Cache Duration
Unit: Seconds
Range: 300 (5 min) to 604800 (7 days)
Default: 28800 (8 hours)

Duration Recommendations by Business Type:

High-Volume Call Center:

Duration: 3600 seconds (1 hour)
Reason:
  - Many different callers per day
  - Quick callback turnaround
  - Avoid stale associations
  - Frequent cache refresh

Sales Department:

Duration: 28800 seconds (8 hours / business day)
Reason:
  - Callbacks within same day
  - Follows up on morning calls in afternoon
  - Resets overnight
  - Balance between fresh and persistent

Account Management:

Duration: 86400 seconds (24 hours)
Reason:
  - May return call next day
  - Ongoing customer relationships
  - Persist overnight
  - Less frequent different callers

Technical Support:

Duration: 43200 seconds (12 hours)
Reason:
  - Tickets may take hours to resolve
  - Callback after investigation
  - Extend beyond business day
  - Still refresh regularly

Project-Based Work:

Duration: 604800 seconds (7 days)
Reason:
  - Long-term project relationships
  - Callbacks may be days apart
  - Persistent client associations
  - Weekly refresh adequate

Cache Management:

Automatic Cleanup:

Process: Background job runs hourly
Action: Deletes expired cache entries
Benefit: Keeps cache fresh, saves memory
Log: Records cleanup actions

Manual Cleanup:

Action: Admin can manually clear cache
When: System maintenance, troubleshooting
Effect: All extensions lose AutoCLIP until next inbound call
Use: Sparingly, as needed

Cache Size Monitoring:

Monitor: Number of cached entries
Alert: If cache grows unusually large (> 10,000 entries)
Action: May indicate cache not expiring properly
Investigation: Check cleanup job, duration settings

Per-Extension Duration Override:

Option: Set different duration for specific extensions
Example:
  - Sales team: 8 hours
  - Account managers: 24 hours
  - Support: 12 hours
Implementation: Extension-level setting overrides trunk default

Multiple Trunk Scenarios

Problem: Multiple Trunks

Scenario:
  Trunk A: US DIDs
  Trunk B: UK DIDs
  Trunk C: Emergency/backup

Question: Which trunk's AutoCLIP applies?

Solution: Trunk Priority

Configuration:

Outbound Route Rules:
1. Match outbound destination
2. Select appropriate trunk
3. Check AutoCLIP on selected trunk
4. If cached DID available on that trunk, use it
5. Else, fallback to trunk default

Example 1: Same-Trunk Return Call

Inbound:
  Customer calls +1-555-1234 (US number)
  Arrives on Trunk A (US trunk)
  AutoCLIP caches +1-555-1234 on Trunk A

Outbound:
  Extension returns call to US customer
  Outbound route selects Trunk A
  AutoCLIP finds +1-555-1234 cached for Trunk A
  Result: Uses +1-555-1234 ✓

Example 2: Cross-Trunk Scenario

Inbound:
  Customer calls +44-20-1234-5678 (UK number)
  Arrives on Trunk B (UK trunk)
  AutoCLIP caches +44-20-1234-5678 on Trunk B

Outbound:
  Extension returns call to US customer (different call)
  Outbound route selects Trunk A (US trunk)
  AutoCLIP checks Trunk A cache (empty for this extension)
  Result: Uses Trunk A default (no cached DID for this trunk)

Example 3: DID Available on Multiple Trunks

Setup:
  +1-555-MAIN is configured on both Trunk A and Trunk B

Inbound:
  Call comes in on +1-555-MAIN via Trunk A
  AutoCLIP caches with Trunk A association

Outbound:
  Extension returns call
  Outbound route selects Trunk B (load balancing)
  AutoCLIP: Cached DID is +1-555-MAIN
  Validation: +1-555-MAIN available on Trunk B? Yes
  Result: Uses +1-555-MAIN on Trunk B ✓

Cross-Trunk AutoCLIP Configuration:

Option 1: Trunk-Specific (default)
  Each trunk maintains separate AutoCLIP cache
  Most predictable behavior
  Recommended for most deployments

Option 2: Shared AutoCLIP Cache
  Single cache across all trunks
  AutoCLIP checks if DID available on outbound trunk
  More flexible but complex
  Use for advanced multi-trunk scenarios

Trunk Failover:

Primary Trunk: Trunk A with AutoCLIP enabled
Backup Trunk: Trunk B with AutoCLIP enabled

Scenario:
  Inbound: Arrived on Trunk A, cached +1-555-1234
  Outbound: Trunk A down, fails over to Trunk B
  AutoCLIP: Checks if +1-555-1234 available on Trunk B
  If Yes: Uses +1-555-1234 on Trunk B
  If No: Uses Trunk B default caller ID

Extension-Level AutoCLIP Control

Per-Extension Settings:

Enable/Disable AutoCLIP:

Location: Settings > Extensions > [Extension] > Outbound Caller ID > AutoCLIP
Options:
  - Use Trunk Setting (default)
  - Force Enable
  - Force Disable

Use Cases:
  Force Enable: Extension always uses AutoCLIP regardless of trunk
  Force Disable: Extension never uses AutoCLIP (fixed caller ID preferred)

Cache Duration Override:

Setting: Extension-specific cache duration
Example:
  Extension 2001 (Sales): 8 hours
  Extension 3001 (Account Manager): 24 hours
  Extension 4001 (CEO): Disabled (always uses +1-555-CEO-DIRECT)

Fallback Caller ID:

Setting: Extension outbound caller ID when AutoCLIP not available
Priority:
  1. AutoCLIP cached DID (if available)
  2. This extension fallback setting
  3. Trunk default

Example:
  Extension 2001 fallback: +1-555-SALES
  No AutoCLIP cache → Uses +1-555-SALES

Manual Override Option:

Feature: Allow user to manually select caller ID
Options:
  - AutoCLIP (automatic)
  - Extension default
  - Custom select from available DIDs

Interface:
  Phone menu: Press *67 before dialing to select caller ID
  Softphone: Dropdown to select caller ID per call
  Web portal: Configure preferred override

Extension Groups:

Group: Sales Team
Members: Extensions 2001-2009
AutoCLIP: Enabled, 8-hour cache
Fallback: +1-555-SALES

Group: Support Team  
Members: Extensions 3001-3009
AutoCLIP: Enabled, 12-hour cache
Fallback: +1-555-SUPPORT

Group: Executives
Members: Extensions 9001-9005
AutoCLIP: Disabled
Fixed Caller ID: Individual executive DIDs

User Portal Control:

Allow users to:
  - View AutoCLIP status (current cached DID)
  - See cache expiration time
  - Manually clear their AutoCLIP cache
  - Set fallback caller ID preference
  - Enable/disable AutoCLIP (if permitted)

Benefits:
  - User empowerment
  - Troubleshooting aid
  - Flexibility

Call History Integration:

Call History Display:
  Shows which caller ID was used for each call
  Indicates if AutoCLIP was used
  Shows original inbound DID that triggered AutoCLIP

Example:
  10:00 AM - Inbound on +1-555-SALES from +1-555-9999
  10:30 AM - Outbound to +1-555-9999 using +1-555-SALES (AutoCLIP)

Tracking Marketing Channel Effectiveness

Scenario: Multiple Marketing Campaigns

Campaign A: Google Ads
  DID: +1-555-100-0001
  Landing Page: Shows this number
  
Campaign B: Facebook Ads
  DID: +1-555-100-0002
  Landing Page: Shows this number

Campaign C: Direct Mail
  DID: +1-555-100-0003
  Printed on mailer

Campaign D: Billboards
  DID: +1-555-100-0004
  Displayed on outdoor ads

Implementation with AutoCLIP:

Setup:
  All DIDs route to sales queue
  Sales reps answer from queue
  AutoCLIP caches which DID customer called

When sales rep returns call:
  AutoCLIP automatically uses original DID
  Customer sees familiar number
  Higher callback answer rate

Tracking:
  CDR shows which DID was used
  Attribute sale to correct marketing campaign
  Calculate ROI per channel

Benefits:

1. Higher Answer Rates: Customer recognizes number from ad
2. Accurate Attribution: Know which ad drove call
3. ROI Calculation: Cost per acquisition per channel
4. Campaign Optimization: Double down on effective channels
5. Consistent Brand: Customer always sees same number

Reporting:

Campaign Performance Report:
  
Campaign A (Google Ads):
  Inbound Calls: 150
  Callbacks: 75
  Answer Rate: 85% (AutoCLIP recognition)
  Conversions: 30
  ROI: 250%

Campaign B (Facebook Ads):
  Inbound Calls: 200
  Callbacks: 100
  Answer Rate: 82%
  Conversions: 35
  ROI: 180%

Campaign C (Direct Mail):
  Inbound Calls: 50
  Callbacks: 30
  Answer Rate: 90% (highest - printed number saved)
  Conversions: 15
  ROI: 120%

Department-Specific Caller ID

Scenario: Multiple Departments, Shared Team

Company: Growing startup
Team: Small team wears multiple hats
DIDs:
  +1-555-SALES → Sales inquiries
  +1-555-SUPPORT → Technical support
  +1-555-BILLING → Billing questions
  +1-555-MAIN → General inquiries

All DIDs route to same team members (cross-trained)

Without AutoCLIP:

Customer calls +1-555-SUPPORT (support inquiry)
  ↓
Rep helps customer, creates ticket
  ↓
Rep calls back with update
  ↓
Customer sees +1-555-MAIN (company main number)
  ↓
Customer: "Who's this? I don't recognize this number."
  ↓
Confusion, lower answer rate

With AutoCLIP:

Customer calls +1-555-SUPPORT
  ↓
Rep helps customer
  ↓
AutoCLIP caches +1-555-SUPPORT
  ↓
Rep calls back
  ↓
Customer sees +1-555-SUPPORT
  ↓
Customer: "Oh, that's the support number I called! They're following up."
  ↓
Customer answers, smooth experience

Multi-Department Routing:

Morning:
  Customer A calls +1-555-SALES (sales inquiry)
  Answered by Extension 2001
  AutoCLIP: Caches +1-555-SALES for Ext 2001

Afternoon:
  Customer B calls +1-555-SUPPORT (support issue)
  Answered by Extension 2001 (same rep, different hat)
  AutoCLIP: Updates to +1-555-SUPPORT for Ext 2001

Later:
  Extension 2001 returns call to Customer B
  AutoCLIP: Uses +1-555-SUPPORT (most recent)
  Customer B recognizes support number

Next Day:
  Extension 2001 calls Customer A (sales follow-up)
  AutoCLIP: Cache expired, uses default +1-555-SALES
  Or manually select caller ID

Benefits:

• Context Preservation: Customer knows which department is calling
• Professional Image: Appears as larger company with dedicated departments
• Flexible Staffing: Small team can handle multiple functions
• Clear Communication: Customer expectations set by number they see

Advanced Call Tracking and Analytics

Scenario: Dynamic Number Insertion (DNI)

Setup:
  Website dynamically shows different phone numbers based on visitor source
  Google: +1-555-001
  Bing: +1-555-002  
  Organic: +1-555-003
  Direct: +1-555-004
  
All numbers route to same sales team
AutoCLIP ensures callbacks use same number

Full Customer Journey:

Step 1: Customer Acquisition
  Customer searches Google for "cloud PBX"
  Clicks your ad
  Website shows +1-555-001 (Google tracking number)
  
Step 2: Initial Contact
  Customer calls +1-555-001
  Sales rep answers
  AutoCLIP caches +1-555-001
  
Step 3: Follow-Up
  Sales rep sends proposal, schedules callback
  Calls customer next day
  AutoCLIP uses +1-555-001
  Customer recognizes number, answers
  
Step 4: Closing
  Multiple callback conversations
  Always displays +1-555-001
  Customer saves this number in phone
  
Step 5: Post-Sale
  Customer calls +1-555-001 for support
  AutoCLIP maintains consistency
  
Attribution: Entire customer journey traced to original Google ad

Integration with CRM:

When call comes in on +1-555-001:
  1. AutoCLIP caches DID
  2. Webhook to CRM with DID + caller number
  3. CRM tags contact with source: "Google Ads"
  4. Sales rep sees attribution in CRM
  5. Manager reports on channel performance

When rep returns call:
  1. CRM click-to-call
  2. AutoCLIP ensures +1-555-001 used
  3. CRM logs call with correct campaign attribution
  4. Complete customer journey documented

Analytics Dashboard:

Metrics per Tracking Number:
  
+1-555-001 (Google Ads):
  - Inbound Calls: 500
  - Unique Callers: 320
  - Callbacks Made: 180
  - Callback Answer Rate: 88%
  - Closed Deals: 45
  - Revenue: $225,000
  - Cost per Acquisition: $350
  - ROI: 320%

+1-555-002 (Bing Ads):
  - Inbound Calls: 150
  - Unique Callers: 100
  - Callbacks Made: 60
  - Callback Answer Rate: 85%
  - Closed Deals: 12
  - Revenue: $60,000
  - Cost per Acquisition: $400
  - ROI: 200%

Insight: Google Ads outperforming Bing 3:1
Action: Increase Google budget, optimize Bing

A/B Testing with AutoCLIP:

Test: Does showing local number vs toll-free affect conversion?

Group A: Show local numbers (+1-555-123-XXXX)
Group B: Show toll-free (+1-800-555-XXXX)

AutoCLIP: Ensures callbacks use same number customer saw
Measure: Answer rate, conversion rate per group
Result: Data-driven decision on number strategy

Improving Customer Experience Through Familiarity

Psychology of Number Recognition:

Unknown Number:
  Customer thinks: "Spam call? Scam? Who's this?"
  Action: Ignore, send to voicemail
  Answer Rate: ~30-40%

Recognized Number:
  Customer thinks: "Oh, that's [Company] calling back!"
  Action: Answer immediately
  Answer Rate: ~80-90%

Difference: 2-3x higher answer rate with recognition

Customer Scenario 1: Sales Follow-Up

Without AutoCLIP:
  Day 1: Customer calls sales, discusses product
  Day 2: Sales rep follows up, customer sees random number
  Customer: Ignores unknown number
  Result: Missed connection, sale delayed

With AutoCLIP:
  Day 1: Customer calls +1-555-SALES
  Day 2: Sales rep follows up using +1-555-SALES (AutoCLIP)
  Customer: "Oh, the sales team is calling back!"
  Result: Customer answers, sale progresses

Customer Scenario 2: Support Callback

Without AutoCLIP:
  Customer submits support ticket, provides number
  Support calls back from random internal number
  Customer doesn't answer (thinks it's spam)
  Support leaves voicemail, customer calls back
  Phone tag continues, frustration builds

With AutoCLIP:
  Customer called +1-555-SUPPORT to open ticket
  Support calls back using +1-555-SUPPORT (AutoCLIP)
  Customer recognizes number, answers
  Issue resolved in one call

Customer Scenario 3: Account Management

Ongoing relationship:
  Customer has account manager's direct number saved
  But sometimes calls main support line
  
Without AutoCLIP:
  Account manager returns call from direct line
  Customer may not recognize if they called main line
  
With AutoCLIP:
  If customer called main line, account manager uses main line for callback
  If customer called direct line, account manager uses direct line
  Flexibility ensures recognition

Customer Journey Consistency:

Touchpoint 1: Website shows +1-555-SALES
Touchpoint 2: Customer calls +1-555-SALES
Touchpoint 3: Callback displays +1-555-SALES (AutoCLIP)
Touchpoint 4: Follow-up emails from [email protected]
Touchpoint 5: Another callback shows +1-555-SALES
Touchpoint 6: Customer saves +1-555-SALES in contacts

Result: Single, consistent number throughout customer journey
Benefits:
  - Easy for customer to remember
  - Professional, cohesive brand experience
  - Higher engagement at every touchpoint
  - Customer knows exactly who's calling

Voicemail Impact:

Without AutoCLIP (unknown number):
  "You have a new voicemail from 555-1234..."
  Customer: "Who's that? Spam? I'll delete it."
  
With AutoCLIP (recognized number):
  "You have a new voicemail from 555-SALES..."
  Customer: "Oh, the sales team! Let me check this."
  Higher voicemail listen rate, callback rate

AutoCLIP Not Working - Using Default Instead

Problem: Extension makes callback, but default caller ID used instead of cached DID

Diagnostic Steps:

1. Verify AutoCLIP Enabled:

Check: Settings > Trunks > [Trunk] > AutoCLIP > Enabled
Status: Should be ON
If OFF: Enable and test again

2. Check Cache Existence:

Query: AutoCLIP cache for extension
Command: Check if extension has cached entry
Result: Should show DID and timestamp

If empty: No recent inbound call, or cache expired
Action: Make test inbound call, try again

3. Verify Cache Not Expired:

Cache timestamp: 10:00 AM
Current time: 7:00 PM
Cache duration: 8 hours (expires 6:00 PM)
Result: Expired - explains why default used

Solution: Increase cache duration or call sooner

4. Check DID Still Valid:

Cached DID: +1-555-1234
Current DIDs: Check if +1-555-1234 still configured
Status: If DID removed/ported, AutoCLIP can't use it

Solution: Re-add DID or update configuration

5. Verify Trunk Compatibility:

Inbound trunk: Trunk A
Outbound trunk: Trunk B  
Cached DID: Only on Trunk A
Problem: Trunk B doesn't have cached DID

Solution: Add DID to both trunks or use same trunk

6. Check Extension Override:

Extension settings: AutoCLIP disabled
Result: Extension-level setting overrides trunk
Status: Even if trunk enabled, extension can disable

Solution: Remove extension override or enable at extension level

7. Review Call Logs:

Log: Last outbound call from extension
Caller ID used: +1-555-MAIN (default)
AutoCLIP status: "Not used - no cached DID"
Reason: Helps identify exact cause

Action: Fix identified issue

AutoCLIP Using Incorrect DID

Problem: AutoCLIP active, but uses wrong DID for callback

Scenario 1: Multiple Recent Calls

10:00 AM: Inbound from Customer A on +1-555-SALES
11:00 AM: Inbound from Customer B on +1-555-SUPPORT
11:30 AM: Return call to Customer A

Problem: AutoCLIP uses +1-555-SUPPORT (most recent)
Customer A: Confused, called sales not support

Reason: AutoCLIP uses most recent cached DID
Solution: Manual caller ID selection for specific customer
Or: Check call history before calling back

Scenario 2: Wrong Extension

Extension 2001: Answered call from Customer on +1-555-SALES
Extension 2002: Trying to return call to same customer

Problem: Extension 2002 has different cached DID
Result: Wrong caller ID used

Reason: Each extension has independent cache
Solution: Extension 2001 should make callback
Or: Extension 2002 manually select +1-555-SALES

Scenario 3: Transferred Call

Original call: Came in on +1-555-MAIN to reception
Transferred to: Extension 2001 (sales)
Reception cache: +1-555-MAIN
Sales cache: Also +1-555-MAIN (inherited from transfer)

Problem: Sales wants to use +1-555-SALES not +1-555-MAIN
Customer called main, but now working with sales

Solution: Manual override to +1-555-SALES
Or: Transfer configuration to use destination dept DID

Scenario 4: Long-Ago Call

Last week: Customer called +1-555-SALES
Today: Customer called +1-555-SUPPORT  
Cache expired: Last week's call (duration 7 days)
Current cache: +1-555-SUPPORT only

Callback to: Old sales inquiry
AutoCLIP uses: +1-555-SUPPORT (only cached DID)
Customer: Confused

Solution: Shorten cache duration (8 hours) for fresher data
Or: Manual selection based on call purpose

Manual Caller ID Selection:

When AutoCLIP isn't appropriate:
  1. Press *67 before dialing (feature code)
  2. Select caller ID from list
  3. Dial destination number
  4. Call uses selected ID, not AutoCLIP

Alternative: Softphone interface with caller ID dropdown

Cache Not Recording Inbound Calls

Problem: Making inbound calls, but AutoCLIP cache not populating

Diagnostic Steps:

1. Verify AutoCLIP Enabled on Inbound Trunk:

Check: Trunk receiving inbound calls
Settings: AutoCLIP enabled?
If disabled: Enable to start caching

2. Check Extension Eligibility:

Extension: Is it in AutoCLIP whitelist/not blacklisted?
Setting: Extension AutoCLIP enabled?
If excluded: Add to whitelist or remove from blacklist

3. Verify Call Was Answered:

Requirement: Call must be answered to cache
Unanswered: No cache entry created
Ring-no-answer: No cache
Voicemail: No cache (not answered by extension)

Solution: Cache only created on actual answer

4. Check DID Association:

Problem: Call came in without DID association
Example: Internal transfer, direct IP call
Result: No DID to cache

Solution: Only external DID-based calls cache

5. Test with Simple Call:

Test:
  1. Clear cache (if possible)
  2. Make inbound call to specific DID
  3. Answer on specific extension
  4. Hang up
  5. Immediately check cache

Expected: Cache entry for extension with DID
If missing: Configuration issue, check logs

6. Review System Logs:

Enable: AutoCLIP debug logging
Make: Test inbound call
Review: Logs should show:
  - "Inbound call on DID +1-555-1234"
  - "Answered by extension 2001"
  - "Caching DID +1-555-1234 for ext 2001"

If missing: Identify which step failed

7. Database Check:

Admin: Direct database query (advanced)
Table: autoclip_cache
Query: SELECT * FROM autoclip_cache WHERE extension = '2001'
Result: Should show recent entries

If empty: Cache write failure, check permissions

Fallback Caller ID Problems

Problem 1: No Fallback Set

Scenario:
  AutoCLIP: No cached DID
  Extension: No default caller ID configured
  Trunk: No default caller ID (misconfigured)

Result: Outbound call fails or uses emergency number
Error: "No valid caller ID available"

Solution:
  1. Set trunk default caller ID (required)
  2. Set extension default (recommended)
  3. Test fallback path

Problem 2: Fallback Not Appropriate

Scenario:
  Extension 2001: Sales rep
  Extension fallback: +1-555-SUPPORT
  AutoCLIP: No cache
  Outbound call: To sales prospect

Result: Customer sees support number, confused

Solution:
  1. Set extension fallback to +1-555-SALES
  2. Align fallback with extension role
  3. Different fallbacks per department

Problem 3: Trunk Default Too Generic

Scenario:
  Trunk default: +1-555-0000 (generic number)
  Customer: Calls back to +1-555-0000
  Result: Wrong department, call routing confusion

Solution:
  1. Use main company number as trunk default
  2. Or most common department number
  3. Ensure default routes appropriately

Problem 4: Fallback Not Working

Scenario:
  Extension fallback: Set to +1-555-1234
  No AutoCLIP cache (expected fallback)
  Actual: Uses trunk default instead

Reason: Extension fallback overridden or not properly saved
Check: Extension configuration saved correctly
Solution: Re-save extension settings, test

Fallback Hierarchy Verification:

Test procedure:
  1. Clear AutoCLIP cache for extension
  2. Make outbound call
  3. Verify caller ID used

Expected order:
  1. AutoCLIP cached DID (none in this test)
  2. Extension default outbound caller ID (should be used)
  3. Trunk default (only if extension not set)

If wrong ID used: Check configuration priority

Best Practice Fallback Configuration:

Trunk: Main-Trunk
  Default: +1-555-MAIN (company main number)

Extension 2001 (Sales):
  Fallback: +1-555-SALES
  AutoCLIP: Enabled

Extension 3001 (Support):
  Fallback: +1-555-SUPPORT
  AutoCLIP: Enabled

Extension 9001 (CEO):
  Fixed: +1-555-CEO-DIRECT
  AutoCLIP: Disabled (always use fixed number)

Result: Appropriate fallback at each level