Select the software layer
Map SIP Client Engine, E-DVA and softDSP to the signaling, gateway and media functions required by the product.
Solutions
OEM & Embedded Voice
Integrate SIP signaling, gateway applications and media processing into customer-owned communications products.
Build voice into your product
For manufacturers and ODMs: scope signaling, the embedded voice application and media processing separately, then define the interfaces and integration responsibilities.
- SIP Client Engine: signaling and session control.
- E-DVA: embedded voice application. softDSP: voice and media processing.
- Share your OS, hardware platform, interfaces, target volumes and development schedule. Confirm platform support against the applicable documentation.
- Define evaluation deliverables, integration ownership, licensing, maintenance and support in the agreed scope.
SIP Client Engine
E-DVA
softDSP
OEM & EMBEDDED VOICE
What you can do with it
Integrate SIP signaling, gateway applications and software media processing into a customer-owned communications product using M5T software components and engineering support.
3M5T technology paths
OEMcustomer-owned product
Validatedtarget platform
CAPABILITIES
Capabilities that matter for your project
Validate the platform
Confirm CPU, memory, operating system, interfaces, codecs, concurrency and lifecycle requirements.
Plan commercial delivery
Define integration work, licensing, support, maintenance and product release ownership.
DEPLOYMENT FIT
Best suited for
- Communications devices
- Gateways and CPE
- Embedded applications
- Software media platforms
- Custom OEM products
KEY SPECIFICATIONS
Important selection data
ComponentsSIP Client Engine, E-DVA and softDSP
DeliveryCommercial SDK / software component
SupportM5T developer and engineering program
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
Products to compare
A starting point for your project. Review the model data sheet before ordering.
SOFTWARE
M5T SIP Client Engine SDK
Add SIP signaling to an OEM application or device.
- Selection criterion
- Operating system, APIs, security and integration responsibilities.
SOFTWARE
M5T E-DVA
Integrate an embedded voice application into an OEM platform.
- Selection criterion
- Target hardware, voice services, provisioning and integration scope.
SOFTWARE
M5T softDSP
Add software-based voice and media processing to your product.
- Selection criterion
- Processor budget, codecs, channel count and real-time performance.
SOLUTION BLUEPRINT
How OEM & Embedded Voice changes the voice path.
Define the software layer, platform interfaces and validation responsibilities for your product.
PRODUCT EXPERIENCESOFTWARE CONTROLPLATFORM FOUNDATION
Customer-owned product
The OEM defines the market, user experience, hardware and product lifecycle.
Application & APIs
Business logic calls the required signaling, gateway or media functions.
OEM BUILDING BLOCK
M5T software component
SIP Client Engine, E-DVA or softDSP supplies the selected voice capability.
Operating system
The integration is mapped to supported platform services and development tools.
Processor & interfaces
Compute, codecs, networking and telephony interfaces determine the validated design.
One integrated product
Each layer is validated against the layer below it; performance cannot be inferred from the SDK alone.
Product logicM5T APIsPlatform servicesHardware resources
READING THE DIAGRAM
OEM & Embedded Voice: M5T is embedded inside the OEM product
- Customer product
- The finished commercial device or application remains designed, branded and released by the OEM.
- M5T
- Licensed communications technology supplies a defined voice function inside that product.
- Integration scope
- Processor, operating system, APIs, codecs, concurrency and lifecycle are reviewed together before commitment.
Reference flow — carrier, platform, jurisdiction and field requirements determine the production design.
OEM INTEGRATION
Define an integration that your product team can validate.
Review the target platform, component interfaces and acceptance criteria before committing to an integration.
Confirm OS, processor, interfaces, concurrency, codecs and lifecycle against the selected component documentation.| Decision area | Integration risk | M5 architecture | Acceptance evidence |
|---|---|---|---|
| Interoperability | Assume systems will connect | Normalize signaling and media at a defined boundary | Documented end-to-end call tests |
| Security | Expose internal voice domains | Apply identity, topology and transport controls | Approved routes, certificates and logs |
| Continuity | Skip platform qualification | Define a supported integration scope | Platform and component acceptance tests |
| Operations | Treat go-live as the finish line | Assign monitoring, updates and escalation ownership | Runbook, backups and support entitlement |
FREQUENTLY ASKED
What to know before the next step.
Share your hardware, OS, required voice functions, interfaces, target volumes and engineering schedule.
Agree on deliverables, interfaces, responsibilities and acceptance tests before evaluating the selected component.
Normal and exceptional calls, encryption, routing, media, failover, monitoring and operational ownership should all pass documented tests.
READY FOR THE NEXT STEP?Request a free review
Build the right voice architecture.
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.