Embed instead of rebuild
Use a dedicated SIP engine as a software component inside a customer-owned product architecture.
Products
M5T SIP Client Engine SDK
A commercial embedded SIP software development kit for product teams adding real-time communications to customer-owned applications and devices.
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.
Embedded SIP SDK
OEM integration
Developer support path
EMBEDDED SIP CLIENT SDK
What you can do with it
M5T SIP Client Engine is an embeddable software development kit for product teams adding SIP signaling and real-time communications to customer-owned applications and devices.
SDKembedded integration model
SIPcommunications engine
OEMproduct-team deployment
CAPABILITIES
Capabilities that matter for your project
Architecture-led integration
Target operating system, hardware, media requirements, interfaces and lifecycle must be validated before scope is confirmed.
Developer support path
Technical documentation and packages are delivered through the authenticated M5T developer support environment.
DEPLOYMENT FIT
Best suited for
- Communications applications
- Connected devices
- Enterprise and carrier products
- OEM platforms
- Custom real-time communications
KEY SPECIFICATIONS
Important selection data
DeliveryCommercial SDK and support package
IntegrationCustomer-owned application or device
ScopeDefined from platform, feature and lifecycle requirements
DocumentationAuthenticated M5T developer portal
DOWNLOADS
Brochures and technical documents
Download the PDF files directly. Use the documentation portal for configuration guides, installation procedures and release-specific information.
REFERENCE ARCHITECTURE
See M5T SIP Client Engine SDK in the complete voice path.
A product decision is only correct when both sides of the interface, the security boundary and the operating model are considered together.
PRODUCT EXPERIENCESOFTWARE CONTROLPLATFORM FOUNDATION
Customer application
The OEM owns the user experience, business logic and release.
COMMERCIAL SDK
M5T SIP Client Engine
Adds embedded SIP signaling and real-time communications capabilities.
Operating system & APIs
The integration is mapped to the customer-selected software environment.
Target processor / device
Performance and supported platforms are validated for the actual product hardware.
One integrated product
Each layer is validated against the layer below it; performance cannot be inferred from the SDK alone.
Application callsM5 componentPlatform resources
READING THE DIAGRAM
Embedded software becomes one layer of the customer product
- OEM application
- The customer owns the complete product, interface and business logic around the licensed M5T component.
- M5T component
- A commercial software building block—not a finished phone, gateway or cloud service.
- Target platform
- The processor, operating system, APIs, codec mix and lifecycle must be reviewed before integration.
Conceptual architecture — final topology, capacity and interface configuration require validation.
SOFTWARE PORTFOLIO
Choose the layer you need to control.
DGW operates M5 voice platforms. M5T components are integrated into a customer-owned product and require a separate OEM engineering path.
Target operating system, processor, concurrency, codec and lifecycle requirements must be reviewed before an OEM scope is confirmed.| Technology | DGW Software | SIP Client Engine | E-DVA | softDSP |
|---|---|---|---|---|
| Primary function | Operate SBCs and gateways | Embed SIP signaling | Embed gateway applications | Embed media processing |
| Delivered for | Supported M5 platforms | OEM applications and devices | OEM gateways and CPE | OEM media platforms |
| Key decision | Release and license eligibility | API and platform fit | Interfaces and gateway scope | Codec mix and concurrency |
| Commercial path | License / maintenance | Commercial SDK | OEM program | OEM program |
FREQUENTLY ASKED
What to know before the next step.
Confirm deployment model, concurrent sessions, registered users, interfaces, codecs, carriers, resilience and operational ownership before choosing the final model or SKU.
Validate the exact hardware or virtual configuration, DGW release, license, power, interface modules, interoperability and support coverage.
Use the linked M5 data sheet for selection and the Media5 documentation portal for configuration, installation and release-specific guidance.
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.