EXECUTIVE SUMMARY:

Vapi's current platform architecture presents two fundamental barriers preventing

production use with Brazilian SIP carriers: (1) inflexible SBC codec management

and (2) unacceptable latency profiles for real-time voice applications in Brazil.

ORG ID: f6c41da6-9df8-429c-bbae-18f0e815ca54

CREDENTIAL ID: 7ae953f8-158b-47b0-a071-4f8fa40365ce

TARGET CARRIER: DirectCall (189.84.133.111) - Representative of Brazilian market

================================================================================

PROBLEM 1: SBC CODEC INFLEXIBILITY - PLATFORM DESIGN GAP

================================================================================

CURRENT STATE:

• No API-exposed codec filtering for BYO SIP trunks

• SBC layer enforces hardcoded SDP offers including Opus/G722

• Requires manual engineering intervention per trunk

WHY THIS BREAKS IN BRAZIL:

• Brazilian carriers (DirectCall, Algar, Vivo, Claro, Oi) DO NOT implement

RFC-compliant codec negotiation

• Market standard: Hard reject (SIP 603) on any unsupported codec in SDP

• Result: 100% call failure rate with zero fallback mechanism

ARCHITECTURAL GAP:

US/EU Approach: Offer multiple codecs → Carrier selects → Negotiation succeeds

Brazil Reality: Offer wrong codec → Immediate reject → Call fails

PLATFORM IMPACT:

Vapi's "unified global API" promise fails in Brazil. Each carrier requires

manual SBC configuration, making the platform non-viable for:

• Multi-carrier deployments

• Rapid carrier switching

• Self-service trunk management

================================================================================

PROBLEM 2: LATENCY - REAL-TIME VOICE QUALITY COMPROMISED

================================================================================

OBSERVED METRICS:

[Insira aqui suas medições específicas, ex:]

• Vapi SBC → DirectCall: ~180-220ms RTT

• Media path sub-optimal routing through US/EU POPs

• Jitter buffer underruns during peak hours

REQUIREMENT BREACH:

• ITU-T G.114 recommends <150ms one-way for toll-quality voice

• Brazilian regulatory framework (Anatel) emphasizes local infrastructure

• Customer experience degradation: perceptible delay, talk-over issues

ROOT CAUSE:

Absence of Brazil-based SBC/media POPs forces hairpinning through

North American or European infrastructure before reaching local carriers.

================================================================================

BUSINESS IMPACT ASSESSMENT

================================================================================

CURRENT STATE: Platform UNUSABLE for Brazilian production workloads

BLOCKING FACTORS:

□ Cannot complete basic SIP registration with major carriers without

manual engineering escalation

□ No self-service path to resolve codec mismatches

□ Voice quality below acceptable thresholds for B2B/B2C applications

□ No timeline provided for Brazil-local infrastructure

COMPETITIVE DISADVANTAGE:

Local providers (TotalVoice, DirectCall, Nvoip) and regional cloud

communications platforms (Twilio with local POPs) offer:

• Native G711/G729-only SDP handling

• <50ms latency to local carriers

• Anatel-compliant infrastructure

================================================================================

REQUIRED SOLUTIONS

================================================================================

IMMEDIATE (30 days):

STRATEGIC (90 days):

================================================================================

ALTERNATIVE RECOMMENDATION

================================================================================

If above timeline not feasible, we request:

• Formal acknowledgment of Brazil market limitations

• Roadmap disclosure for LATAM infrastructure

• Early access program for local POP beta testing

Without concrete commitment to Brazil-specific architecture investments,

we will be forced to migrate to alternative platforms with local presence.

================================================================================

CONTACT: netoxp70@gmail.com

AVAILABILITY: Available for technical architecture discussion with

Product/Engineering leadership.

ATTACHMENTS: [PCAP files, latency logs, carrier rejection logs]