|
The M5T SIP Client Engine is a complete SIP client implementation based on RFC 3261 and other IETF RFCs. It offers a suite of high-level C++ APIs that developers can use to easily integrate SIP client functionality in any type of device. The M5T SIP Client Engine takes care of all SIP signaling details and RTP media handling details; only the user/device interface and management functionality need to be added in order to have a fully functional and sellable SIP client. The M5T SIP Client Engine is also highly portable and already supports a large range of operating systems, allowing a single implementation to run across a complete product line, from cell phones and wifi phones to IP phones and video soft phones.
M5T SIP Client Engine Architcture Overview
Reduces Time to Market
The M5T SIP Client Engine implements all standard client functionality, from signalling to media handling. Product Managers responsible for a SIP client application development only have to plan the integration of the M5T SIP Client Engine along with the user and management interfaces. The net result is faster time-to-market with enhanced stability and interoperability gained from reusing the M5T SIP Client Engine...
|
Feature Rich
The M5T SIP Client Engine implements a wealth of features, including call establishment, call transfer, call forward, hold, resume, visual message waiting indication, registration management, etc. Moreover, optional components are available that provide advanced features such as Security and NAT/firewall traversal.
|
Build Secure SIP Devices
The M5T SIP Client Engine can be augmented with optional security components, enabling secured interoperability. The SIP signaling is encrypted using TLS with mutual or server authentication. The media flow is transported using Secured RTP (SRTP), which uses AES to encrypt the data. The SRTP keys can be exchanged through SDP using RFC 4568 (security description), using the Multimedia Internet Key Exchange protocol (MIKEY), which further encrypts the SRTP key, or even using ZRTP.
|
 Read more
|
Read more |
Read more |
- Reduces Time to Market
- Feature Rich
- Security
- Supported Standards
| Minimizes R&D Investment and Simplifies Product Line Development
The portable M5T SIP Client Engine can be reused across different projects, minimizing the learning curve and further decreasing the time-to-market. It provides a single application development API platform. Moreover, this reuse across projects ensures cross-product interoperability and enhanced stability due to bug fixes transiting from one project to another.
|
|
High-Level API Hides Protocol Details
The M5T SIP Client Engine provides high-level APIs that allow programmers to immediately get working on their applications without having to learn one or more protocols. Moreover, the provided abstraction level allows focusing on the application to add more value there than on a protocol that must always be implemented in the same way.
|
|
Any Hardware, Any Platform, Any OS
The SIP Client Engine is built over the M5T Framework, which offers a layer of abstraction for a wide range of supported platforms and operating systems. The M5T SIP Client Engine thus works on all platforms and operating systems supported by the M5T Framework, including Linux, VxWorks, WindowCE, Symbian, Windows and eCos. Please contact M5T for the latest list of supported Operating Systems or to know more about the support of your operating system.
|
Partial Features Overview
GENERAL FEATURES
Multi-user/profile support
SIP over UDP, TCP, TLS*
SIP Security*
Server TLS Authentication
Mutual TLS Authentication
Digest Authentication
Media Security*
AES Encryption*
Media Security Key Negotiation*
MIKEY*
Security Descriptions*
sip, sips, tel, pres and im URI schemes
|
SIP CALL FEATURES
Make / Receive Call
Forward Call
Transfer Call
Forked call handling
Registration Management with automatic refresh
MEDIA SESSION FEATURES
Offer/Answer Negotiation
Support Audio & Fax
Hold Media Stream
Resume Media Stream
3-way Conference
Early media
RTP/RTCP Control*
SRTP/SRTCP Control*
MIKEY*
Security Descriptions*
|
BUILT-IN TELEPHONY FEATURES**
Make / Receive Call
Call Waiting
2nd Call
Caller ID
Caller ID on Call Waiting
Message Waiting Indicator (WMI)
Call Forward on No Answer
Call Forward on Busy
Call Forward Unconditional
Attended Call Transfer
Unattended Call Transfer
3-Way Local Conferencing
FAX in clear channel mode
T.38 FAX*
Multiple Digit Maps Configuration
Inter-digits timer configuration
|
Multimedia Engine / Chipset Integration The M5T SIP Client Engine must interface with a Multimedia Engine in order to support audio and video. The M5T SIP Client Engine already supports a number of multimedia engines and chipsets. Contact M5T to know if the multimedia engine you are using is currently supported. M5T can easily add the support for your selected multimedia engine / chipset if the need arises.
Builds Secure SIP Devices
Integrates Key M5T Components
The M5T SIP Client Engine is built over and integrates key M5T components, such as:
- M5T SIP-UA SAFE for SIP signaling management.
- M5T Framework, for abstracting the operating system and platform.
- M5T SDP for parsing and generating the SDP that is used for media negotiation.
- M5T UA-SSP which is the User-Agent Signaling Service Provider that integrates M5T SIP-UA SAFE and manages SDP and the offer/answer model. It offers higher level user agent APIs.
- M5T Sigcomp which is used for compressing the SIP signaling on low bandwidth links.
- M5T STUN to ease NATs and Firewalls traversal of the media.
|
- FXS Call Manager which provides the telephony and phone state machines with comprehensive Digit Maps configurations.
- MTEI which is the Media & Telephony Engine Integration that offers high-level media APIs and integrates many media-related components such as M5T RTP.
- M5T RTP SAFE which is used for encapsulating the media and sending it on the network.
- M5T SRTP SAFE which is used for encrypting the sent media and decrypting the received media.
- M5T ZRTP SAFE which is used for negotiating the keys to use with SRTP.
- M5T MIKEY SAFE which is also used for negotiating the keys to use with SRTP.
|
Implemented and Supported Standards
rfc1950 - Deflate*
rfc2246 TLS*
rfc2429 - RTP Payload - H.263+*
rfc2617 - HTTP Digest Authentication
rfc2976 - The SIP INFO Method
rfc3261 - SIP
rfc3263 - Locating SIP Servers
rfc3264 - SDP Offer-Answer Model
rfc3265 - SIP Specific Event Notification
|
rfc3485 - Sigcomp Dictionary SIP/SDP*
rfc3489 - STUN*
rfc3515 - The SIP REFER Method rfc3550 - RTP/RTCP
rfc3551 - RTP Audio/Video Profile
rfc3581 - Symmetric Response Routing
rfc3605 - RTCP attribute in SDP
rfc3611 - RTCP XR
rfc3711 - SRTP*
rfc3830 - MIKEY*
|
rfc3952 - RTP Payload - iLBC
rfc3984 - RTP Payload - H.264
rfc4028 - SIP Session-Timers
rfc4567 - Key Mgmt ext for SDP*
rfc4568 - SDP security descriptions*
rfc4733 - RTP Payload for DTMF/Tones
rfc5049 - Sigcomp and SIP*
draft-ietf-behave-rfc3489bis*
draft-ietf-sipping-cc-transfer
draft-zimmermann-avt-zrtp*
|
|
|