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 functionalities into 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.
Key Product Characteristics
C++ SDK for SIP client devices, Implements all standard call and media services, Standards based; implements a wide range of standards, Integrates with different multimedia engines / chipsets, Highly portable, supports a number of operating systems and platforms, Full C++ source code access, Supports multi-user / multi-line, IPv6 ready and dual IPv4 / IPv6 support, Multiple network interfaces support, Highly flexible, allows building new services over it, Highly customizable, Highly interoperable, Low footprint.
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.
Simplifies Product Line Development
The portable M5T SIP Client Engine can be reused across different projects, minimizing the learning curve and further decreasing time to market. Moreover, this reuse across project ensures cross-product interoperability and enhanced stability due to bug fixes transiting from one project to another
Extensible Media5 built extensive mechanisms in the M5T SIP Client Engine to allow developers to modify incoming and outgoing SIP packets; headers can be added, removed or modified. Moreover, another extension mechanism allows programmers to send and receive SIP requests that are not directly handled by the SIP Client Engine, which permits the integration of value-added features at the signaling level.
Media5 Professional Services to Further Decrease Time to Market
Media5 is a leading software provider delivering the latest software technology for developing secure and feature-rich IP communication systems. Over the past few years, the M5T product line has been developed to address IP communications and security requirements in large and complex network architectures. This know-how allows Media5 to provide up-to-date, reliable and deployable solutions. Thus, as an important addition to any solution, Media5 offers professional services that are provided by experienced engineers. Media5’s engineers offer years of hands-on R&D and field experience in Internet and Internet Telephony technologies. They possess extensive knowledge of IETF and ITU protocols related to real-time communication over IP, such as: SIP, MGCP/NCS, H.323, SDP, SigComp, MIKEY, RTP, RTCP, SRTP, TLS, Kerberos, STUN, etc. In addition, the engineers’ expertise is present at all system levels: DSP, CPU, OS, BSP, compiler, embedded client applications, server applications, distributed management and security. This complete expertise combined together with an efficient management team allows M5T to complete feature-rich projects on time and further allows faster time to market for our customers
Partial Features Overview
General Features
Multi-user/profile support, Multi-network interface, IPv4, IPv6, dual host 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, ENUM resolution of “tel” URIs, SIP extensions for:(Privacy, Asserted Identity, UA Capabilities, Caller Preference, GRUU t
Call Features
Make / Receive Call, Forward Call, Transfer Cal, Reliable 1xx (PRACK), UPDATE, Forked call handling, Caller Preferences, Support for all Offer/Answer scenarios, Early media
Media Sessions Features
Offer/Answer Negotiation, Support Audio, Video & Fax, Hold Media Stream, Resume Media Stream, 3-way Conference, Early media, RTP/RTCP Control*, SRTP/SRTCP Control*, ICE Negotiation*, MIKEY*, Security Descriptions*
Registration Features
Automatic refresh, Registrar list configuration, Registration monitoring (reg-info), Obtaining a GRUU, Persistent Connection Mgmt, Service-Route discovery, Publishing UA capabilities
Presence Features
Publishes PIDF*, Refreshes publications*, Subscribes and reports watchers (presence.winfo)*, Subscribes to peer for presence state*, Parses and reports PIDF to the application*, Automatically refreshes subscriptions*
* denotes features available with the use of optional components
IPv4 and IPv6 Ready
The M5T SIP Client Engine supports a wide range of transport protocols, allowing communications over UDP, TCP and TLS. Moreover, it can communicate over both IPv4 and IPv6 networks, and it can be configured to support multiple network interfaces, including dual stack devices. Overall, the M5T SIP Client Engine allows a smooth transition to the new IPv6 standard by supporting both Ipv4 and IPv6 at the same time.
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.
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, such as: Android, eCos, iPhone/iOS, Linux; Symbian, VxWorks, Windows and WindowCE.
Please contact M5T for the latest list of supported Operating Systems or to know more about the support of your operating system.
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 offers higher level user agent APIs.
M5T UA-IMPP which is the User-Agent Instant Messaging and Presence Provider that also integrates M5T SIP-UA SAFE to offer high-level presence and IM APIs.
M5T Sigcomp which is used for compressing the SIP signaling on low bandwidth links.
MSP which is the Media Service Provider that offers high-level media APIs and integrates many media-related components.
M5T ICE, M5T STUN and M5T TURN that offer the functionality for sending media through NATs and Firewalls.
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
rfc3262 - Reliable 1xx Responses
rfc3263 - Locating SIP Servers
rfc3264 - SDP Offer-Answer Model
rfc3265 - SIP Specific Event Notification
rfc3266 - Support for IPv6 in SDP
rfc3267 - RTP Payload - AMR&AMR-WB*
rfc3311 - The SIP UPDATE Method
rfc3320 - Sigcomp* rfc3321 - Sigcomp Extended Op*
rfc3323 - A Privacy Mechanism for SIP
rfc3325 - Asserted Identity
rfc3389 - RTP Payload - Comfort Noise*
rfc3420 - message-sipfrag
rfc3428 - SIP Extension for IM*
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
rfc3608 - Service Route
rfc3611 - RTCP XR*
rfc3680 - Registration Event Package
rfc3711 - SRTP*
rfc3761 - Enum
rfc3764 - Enum registration for SIP AOR
rfc3824 - Using E.164 numbers with SIP
rfc3830 - MIKEY*
rfc3840 - UA Capabilities
rfc3841 - Caller Preferences
rfc3842 - MWI Event Package for SIP
rfc3856 - Presence Event Package*
rfc3857 - winfo Event Package*
rfc3858 - XML for Watcher Information*
rfc4566 - SDP
rfc3861 – im and pres Resolution*
rfc3862 - CPIM Message Format*
rfc3863 - PIDF*
rfc3891 - The SIP Replaces Header
rfc3903 - Publish*
rfc3952 - RTP Payload - iLBC*
rfc3959 - Early Session Disposition
rfc3960 - Early Media and Ringing Tone
rfc3966 - The TEL URI
rfc3984 - RTP Payload - H.264*
rfc4028 - SIP Session-Timers
rfc4091 - ANAT Semantics for SDP
rfc4092 - Use of ANAT in SIP
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-behave-turn*
draft-ietf-behave-turn-tcp*
draft-ietf-mmusic-ice*
draft-ietf-mmusic-ice-tcp*
draft-ietf-sipping-cc-transfer
draft-ietf-sip-gruu
draft-zimmermann-avt-zrtp*
* denotes RFCs that are supported through optional components.
Please select the documentation category that you are looking for: