MMS using Mercuro IMS Client

Support for MMS (Multimedia Messaging Service) messaging has been added in the last release of Mercuro IMS Client.
MMS messages are sent over the network using MSRP/SMIL to one or multiple contacts (using conference factory).

New Release of Mercuro IMS Client (4.0.1448)

The latest release of Mercuro IMS Client(Version 4.0.1448) is now available for download at http://www.mercuro.net/.
This release comes with a lot of fixes and improvements. Here is a non-exhaustive list:

[BRONZE, SILVER, GOLD]
- Add missing "c" attribute in OPTIONS/SDP
- Message-Summry subscription does not depend on the presence anymore
- Fix SDP media addition
- Fix MSRP overflow when dealing with very large file (> 2Gb)
- Fix H.263 payloading, to optimize blob splitting
- Fix a potential deadlock when dealing with subscriptions
- Fix MAC/XMAC mistmatch handling in AKAv1 and AKAv2
- Fix context menu for watcher info screen.
- Fix potential buffer overrun during AKA computation

[SILVER, GOLD]
- Add support for SigComp compression
- Add support for IPSec/AKA
- Fix potential SPI value overflow for IPSec/AKA
- Fix session timers triggering after a BYE
- Fix IPv6 handling when IPv6 addresses have a zone ID

[GOLD]
- Add for MMS/SMIL composition
- Add for MMS/SMIL rendering
- Fix Qos Pre-Conditions failure when session timers are used
- Fix mode-set negociation for AMR and AMR-WB

Your feedback is welcomed (http://feedback.mercuro.net/)
Mecuro DataSheet: http://www.mercuro.net/downloads/DataSheet_Mercuro.pdf

SigComp (Signaling Compression)

SigComp (Signaling Compression) is now available starting with the Silver edition.
SigComp stands for Signaling Compression and has been defined in RFC 3320 by the Internet Engineering Task Force (IETF) ROHC working group.

Many application protocols used for multimedia communications are text-based and engineered for bandwidth rich links. As a result the messages have not been optimized in terms of size. For example, typical IMS/SIP messages range from a few hundred bytes up to two thousand bytes or more. For this reason, SigComp is mandatory for 3GPP IMS netwoks and PoC systems.

SigComp could also be useful for RCS (Rich Communication Suite) networks because of the size of the SIP packets (more than three thousand bytes for presence publication). Using SigComp in IMS/RCS context will reduce the round-trip over slow radio links.

Our SigComp implementation has been tested against 3GPP IMS and 3GPP2 MMD networks using [3GPP TS 24.229] and [3GPP2 X.S0013-004-A] compression procedures.

Mercuro IMS Client implements:

• RFC 3320 - Signaling Compression (SigComp)
• RFC 3485 - The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)
• RFC 3486 - Compressing the Session Initiation Protocol (SIP)
• RFC 4077 - A Negative Acknowledgement Mechanism for Signaling Compression
• RFC 4464 - Signaling Compression (SigComp) Users' Guide
• RFC 4465 - Signaling Compression (SigComp) Torture Tests
• RFC 4896 - Signaling Compression (SigComp) Corrections and Clarifications
• RFC 5049 - Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)
• RFC 5112 - The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)
• 3GPP TR23.979 Annex C - Required SigComp performance
• [3GPP TS 24.229] and [3GPP2 X.S0013-004-A] compression procedures