Windows 7 support

We had a lot of queries regarding the support of Windows 7 for the Mercuro IMS Client. Well, the first tests we have made are pretty encouraging. As far as we know, there is no issue in running Mercuro on Windows 7. Yes, that means that even the IPSec works, as long as you run Mercuro as an administrator. If you encounter an issue under Windows 7, please let us know.

Back from the 3rd ETSI IMS PlugTest

We spend a whole week at Lannion, France, participating to the 3rd ETSI IMS PlugTest. We met a lot a nice people and got a load of feedback. Even if the tests were dedicated towards NNI interoperability, the Mercuro IMS Client was widely used during testing !!!

Here are some nice pictures I took during the event:

From the ground.

From the above.

During our trip in the Briton islands.

Inexbee is participating at the 3rd ETSI IMS PlugTest with Mercuro IMS Client

Tomorrow (2009-10-16) will be the beginning of the 3rd ETSI IMS PlugTest at Lannion, France. Inexbee will participate to this event with its famous Mercuro IMS Client.

You can find all the information along with the test description document (ETSI TS 186 011) on the ETSI website.

We will also bring some surprise, if we can get them ready by then. Stay tuned !!!

New Release of Mercuro IMS Client (4.0.1508)

The latest release of Mercuro IMS Client (Version 4.0.1508) is available for download at http://www.mercuro.net/.

This release comes with fixes and improvements. Here is a non-exhaustive list:

[BRONZE, SILVER, GOLD]

- Fix a GDI crash when using Remote Desktop

- Fix a glitch on the last DMTF packet retransmission

- Fix minimum size of the window to ensure options visibility

- Fix crash on the contact list when changing authorization

- Fix minimum size of the window to ensure options visibility

- Fix crash on the contact list when changing authorization

- Fix crash when using SIP MESSAGE with tel URIs

- Fix UPDATE/INVITE for session modification to use UPDATE if supported

- Fix a parsing bug in MSRP header (case insensitive)

- Fix a UTF-8 encoding issue in messages

- Add Network Info headers in PRACK requests

[SILVER, GOLD]

- Add Security-* headers in PRACK request when used with IPSec

[GOLD]

- Add OMA Final Delivery Report for MMS messages

- Fix half-octet encoding for SMS SUBMIT payload

- Update features tags for RCS Phase 2

Your feedback is welcomed (http://feedback.mercuro.net/)

SMS over 3GPP IMS Network

SMS stands for Short Message Service or Silent Messaging Service and is a communication service standardized in the GSM mobile communication system, using standardized communications protocols allowing the interchange of short text messages between mobile telephone devices.

SMS technology has been specified by the ETSI in GSM 03.40 and 03.38 documents (3GPP TS 23.040 and 3GPP TS 23.038 respectively). These documents only describe how to use SMS over mobile networks (nothing for IP networks).
In real world there are two way to receive SMS messages over mobile networks: Binary (PDU) and Text mode.
In this post I will explain how to use SMS technology over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in 3GPP TS 24.229.
Note: In the coming chapters, « SMS over IMS Network » and « SMS over IP Network » have the same meaning.

Text mode

The message payload is transfered « as is ». This mode is out of scope.

Binary mode

Also know as PDU (Protocol Data Unit) mode, it is use to encode the payload of the SMS sent over IMS networks. In this case the payload only contains a sequence of hexa-decimal octets or decimal semi-octets strings. The overall PDU string contains some useful information (SMSC address, Service center time stamp, sender number, message reference ...) plus the actual message.

The message length can be up to 160 characters where each character represent 7bits [160/7bits], [140/8bits] or [70/16bits]. By default, each character represent 7bits encoded as per GSM 03.38.

For IMS Networks, SMS message shall be encapsulated in RPDUs (Relay Protocol Data Unit) data string as defined in 3GPP TS 24.011, subclause 7.3. The RPDU data is transfered from SM entity to SM entity using SIP MESSAGE requests. These SIP requests shall use the MIME type "application/vnd.3gpp.sms" for this purpose.

GSM 7 bit Default Alphabet

Each character represent 7bits. For more information see 3GPP TS 23.038 or ETSI GSM 03.38.

Figure 1: GSM 7bit alphabet

3GPP IMS Registration

On sending a REGISTER request, the IMS Client shall indicate its capability to receive traditional short messages over IMS network by including a "+g.3gpp.smsip" parameter into the Contact header according to RFC 3840.

Figure 2: SIP/IMS registration request

Mobile-Originated SMS (MO-SMS)

The IMS Client sender shall build and populate RP-DATA message (RPDU encapsulating TPDU data string), containing all the information that a mobile station submitting an SMS message according to 3GPP TS 24.011 would place, for successful delivery. The sender shall parse and interpret RP- DATA, RP-ACK and RP-ERROR messages, containing all the information that a mobile station receiving an SM according to 3GPP TS 24.011 would see, in a SM submission or status report.

Figure 3: Signaling flows demonstrating successful UE originated SM submit procedure over IP as per 3GPP TS 24.341

** [1,2,4] RP-DATA (SMS-SUBMIT)

Below is represented the first request (RP-DATA(SMS-SUBMIT)) sent from the IMS Client to the P-CSCF.

Figure 4: RP-DATA(SMS-SUBMIT) from Mercuro to the P-CSCF

The SIP MESSAGE (Figure 4) request sent from the IMS client to the P-SCSF carry the RP-DATA (Mobile station to IMS Network) message encoded as per 3GPP TS 24.011 chapter 7.3.1.2.

Figure 5: RP-DATA (Mobile Station to Network) as per 3GPP TS 24.011 subclause 7.3.1.2

The SIP MESSAGE content (Figure 4) can be dissected as following:

RP-MESSAGE: 000000069133010000F019069133010000F011000A9133163254760000AA05F330BB4E07
RPDU:000000069133010000F019

TPDU (SMS-SUBMIT):069133010000F011000A9133163254760000AA05F330BB4E07

The RP-MESSAGE can be dissected as follow (Figure 6):

Figure 6: RP-DATA (Mobile Station to Network) content dissection

** [9,10,11] RP-ACK(SMS-SUBMIT-REPORT)

The SIP MESSAGE payload includes the RP-ACK message. Its RP-User-Data information element includes a TPDU of type SMS-SUBMIT-REPORT.

Figure 7: RP-ACK as per 3GPP TS 24.011 subclause 7.3.3

RP-MESSAGE:020009069133163254760080

For more information, see 3GPP TS 24.011 subclause 7.3.3 for RPDU (RP-ACK) data and 3GPP TS 23.040 subclause 9.2.2.2a for TPDU (SMS-SUBMIT-REPORT) encoding. If error occurs when decoding the message, RP-ERROR (3GPP TS 24.011 subclause 7.3.4) message is sent instead of RP-ACK.

Mobile-Terminated SMS (MT-SMS)

Figure 8: UE originated SM deliver procedure over IP signaling as per 3GPP TS 24.341

** [2,3,4] RP-DATA(SMS-DELIVER)

This request sent from the IP-SM-GW includes a vnd.3gpp.sms payload that includes the short message and routing information for the S-CSCF to forward the short message.

The payload includes the RP-DATA message. Its RP-User-Data information element includes a TPDU of type SMS-DELIVER.

Figure 9: RP-DATA (Network to Mobile Station ) as per 3GPP TS 24.011 subclause 7.3.1.1

RP-MESSAGE: 0100069133010000F0001E069133010000F0040A91331632547600000000000000000005F330BB4E07

For more information, see 3GPP TS 24.011 subclause 7.3.1.1 for RPDU (RP-DATA) data and 3GPP TS 23.040 subclause 9.2.2.1 for TPDU (SMS-DELIVER) encoding.

** [8,9,11] RP-ACK(SMS-DELIVER-REPORT)

This request includes a vnd.3gpp.sms payload that includes the SMS-DELIVER-REPORT and routing information for the IP-SM-GW to forward the delivery report.
The payload includes an RP-ACK message. Its RP-User-Data information element includes a TPDU of type SMS-DELIVER-REPORT.

RP-MESSAGE:020109069133163254760080

For more information, see 3GPP TS 24.011 subclause 7.3.3 for RPDU (RP-ACK) data and 3GPP TS 23.040 subclause 9.2.2.1a for TPDU (SMS-DELIVER-REPORT) encoding.
If error occurs when decoding the message, RP-ERROR (3GPP TS 24.011 subclause 7.3.4) message is sent instead of RP-ACK.

References:

• http://en.wikipedia.org/wiki/SMS

• 3GPP TS 23.038 - Alphabets and language-specific information
• 3GPP TS 23.040 - Technical realization of Short Message Service (SMS)
• 3GPP TS 24.011 - Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface.
• 3GPP TS 24.341 - Support of SMS over IP networks; Stage 3
• 3GPP TS 24.451 - Support of SMS and MMS over NGN IMS subsystem; Stage 3 [Endorsement of 3GPP TS 24.341 Release 7]

New Release of Mercuro IMS Client (4.0.1489)

The latest release of Mercuro IMS Client(Version 4.0.1489) 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 support for UPDATE request in early state during an INVITE session

- Add support for Instant Message Disposition Notification (IMDN) as per RFC 5438

- Add ability to choose page mode type (SIP SIMPLE/MSRP Large Message Mode)

- Add ability to deactivate DirectSound API when sound is choppy

- Add ability to change protocol when SIP requests exceeds MTU or 1300 bytes

- Fix SDP rejection in in-dialog request during an INVITE session

- Fix a crash when using presence external document in NOTIFY

- Fix the early start of media during an outgoing INVITE session

- Update UI library to fix ToLogFont() crashes

[SILVER, GOLD]

- Add support for OMA emoticons

- Fix DNS resolving issues when a name returns both IPv4 and IPv6 records

- Fix DHCP issues when a domain returns both IPv4 and IPv6 records

[GOLD]

- Add support for 3GPP SMS(RP-DATA)

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

Swisscom delivers a Converged Messaging Experience with 724 Solutions & Inexbee

Here is the press release for the Swisscom's IMS trial. They are using a branded Mercuro IMS Client Gold Edition:

- http://wirelessfederation.com/news/17892-swisscom-delivers-a-converged-messaging-experience-with-724-solutions-inexbee/

- http://www.pressreleasepoint.com/swisscom-delivers-converged-messaging-experience-subscribers-724-solutions-and-inexbee

- http://finance.yahoo.com/news/Swisscom-Delivers-a-Converged-bw-2939310047.html?x=0&.v=1

- http://www.lightreading.com/document.asp?doc_id=180871

- http://www.businesswire.co.uk/portal/site/uk/permalink/?ndmViewId=news_view&newsId=20090825005253&newsLang=en

New Release of Mercuro IMS Client (4.0.1460)

The latest release of Mercuro IMS Client(Version 4.0.1460) 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]
- Enhance Audio Queue and Jitter Buffer

- Add support for XCAP-Diff

- Fix SDP negociation when dealing with new media

- Fix retransmission issue with OPTIONS requests

- Fix multipart-related handling in MSRP

- Fix illegal content-type when sending some types of content in MSRP

- Fix a crash when accessing mixer volume information

- Update Mercuro to use the latest VC++ Runtime

[SILVER, GOLD]

- Add support for SIP Dictionary in SigComp

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

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
  

Mercuro now includes H.264 codec

Inexbee has become an offical H.264/AVC licensee, in order to provide the H.264/AVC codec to owner of the Mercuro IMS Client Silver Edition.

Mercuro IMS Client is supporting the Base Profile (Level 1.0, 2.0 and 3.0), in CIF and QCIF video sizes.

If you own one or more license of Mercuro IMS Client Silver Edition, please upgrade to enjoy high-quality video calls with H.264/AVC codec.

New Release of Mercuro IMS Client (4.0.1381)

The latest release of Mercuro IMS Client(Version 4.0.1381) 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 User-Agent header in SIP Responses
- Add NAT traversal in MSRP (RFC 4145)
- Add support for partial publication (RFC 5262, RFC 5264)
- Add support for MSRP Delivery Reports
- Add support for content indirection in SIP NOTIFY
- Allow arbitrary URLs in Refer-To headers
- Add support for group of contacts
- Add support for free-text publication
- Add support for homepage publication
- Add support for status icon publication
- Add support for symmetric OMA presence authorization
- Simplify the authorization management (Pres Rules)
- Use the OMA naming conventions for XDMS (Resource Lists, RLS, Pres Rules)
- Fix "Sign-In" menu to connect

[SILVER, GOLD]
- Add supports for OMA Final Delivery Reports
- Add support for message composition indication for instant messaging (RFC 3994)
- Add support for H.264 codec

[GOLD]
- Add support for Conference Establishment using Request contained lists (RFC 5366)
- Add support for Event Package for Conference State (RFC 4575)
- Add support for Implicit Subscription using SIP REFER (RFC 4488)
- Add support for Session Timers in MSRP
- Add support for MSRP conference (one-to-many adhoc)
- Add support for extension from MSRP one-to-one chat to MSRP one-to-many adhoc
- Add support for message composition indication for instant messaging (RFC 3994)
- Add support for per-service publication

Your feedback is welcomed (http://feedback.mercuro.net/)

GSMA RCS Experience with Mercuro IMS Client

1. Presentation

RCS (Rich Communication Suite) was a join industry effort aiming to speed up the evolution of mobile phone communication towards rich communication. The RCS initiative includes network operators, network and device vendors (Orange, Telecom Italia, Telefonica, TeliaSonera, Ericsson, Nokia Siemens Networks, Nokia, SK Telecom, Sony Ericsson and Samsung).

The RCS is now managed by the GSM Association (GSMA). For more information about GSMA RCS program look at this dedicated website (http://www.gsmworld.com/rcs/programme.shtml)
The main goal of GSMA RCS is to provide a set of fully interoperable rich services to be used both in mobile and fixed network (Network/Access Convergence). These services will enrich call experience.
To be compliant with the GSMA RCS an IMS client MUST at least support these services:

- Enhanced Address Book (defined by the OMA –Open Mobile Alliance-)
- Enhanced Messaging (OMA)
- Content Sharing (GSMA)
- File Transfer (OMA)

An easy way to show how RCS work is to share with you RCS Experience using Mercuro IMS Client. Mercuro is one of the most complete and compliant IMS/RCS client used today.

Mercuro is developed by Inexbee.

2. Enhanced Address Book

This service (also called Enhanced Phonebook or EAB) is the main RCS Service and could be seen as an enriched buddy list with rich presence information. It should be possible to launch all other services (Image/Video Sharing, File transfer, SMS, MMS …) by selecting a contact from the phonebook.
The buddy list is expressed as XML documents and stored in various document repositories in the network where such documents can be located, accessed and manipulated (created, changed, deleted) by authorized principals.
Such documents are accessed and manipulated using IETF XML Configuration Access Protocol (XCAP).
Mercuro could be seen as a XDM Client (XDMC) and the server (XDMS) as a HTTP origin server.
Mercuro can automatically synchronize your EAB with your Terminal Address Book (TAB) to backup or restore your local buddies.
Synchronization between your TAB and the Network Address Book (NAB) must be done using a SyncML agent which will do translation from SyncML (OMA DS Synchronization) to OMA XDM.
Mercuro will support NAB synchronization in release 5.0.

Figure 1: Mercuro IMS Client EAB

2.1 XDM Storage

All contacts are remotely stored in the XDM server. Remote storage allows the user to get his buddy list everywhere and makes Convergence easier (Same contacts on your PC, PDA or mobile phone even if roaming). A contact is stored with some mandatory information (id and display-name) and extended with social information (e.g. nickname, e-mail, free text, dynamic avatar, birthday, labels, favorite link …). To keep XML documents compliant and interoperable, all Mercuro specific information are stored in separate documents.

Mercuro buddies are displayed with minimal information (nickname, msisdn …) and full profile is shown only when requested by the user. It is possible for the user to sort stored his contacts by nickname, e-mail, birthday …

2.2 History

All communications history is saved (for each contact) on behalf of the user. Retrieving a particular saved entry from the UI can be performed using dynamic filters.

Mercuro IMS Client allows the user to start new session (Voice/Video call, Image Sharing, Messaging …) from the history by selecting an entry. You can sort history by date, communication type...

2.3 Groups

Each contact could be part of one or many Groups (e.g. friends, family, biz …).

Mercuro buddies are displayed by Group. You can sort your buddies by group, name, sphere ….

2.4 Enhanced Address Book Presence

This feature is mainly based on OMA SIMPLE Presence 1.1 which partially uses IETF presence data model (RFC 4479).
Mercuro offers the possibility to publish your status (online, offline, out to lunch, on the phone …), dynamic avatar, favorite link, notes, availability, willingness, mood or per service/device capabilities at any time. Dynamic avatar publication (Based on OMA Presence Content) is an important element of EABP and gives Mercuro the look and feel of some well-known VoIP software (Skype or Windows Live Messenger).
It is possible to retrieve presence information for each contact in the phonebook using subscription mechanism (asynchronous). Presence could be retrieved one by one or per list.

All contacts are displayed with their presence information (all mentioned above). You have the possibility to sort your buddies by presence information (availability or willingness).
See below for capabilities indication.

2.5 Capabilities Enhanced Address Book

Mercuro can publish/store (persistent) end-user’s current communication capabilities and retrieve them later (new session). In the other side, capabilities information is retrieved for each contact using presence subscription. All contacts are displayed with their capabilities information. The list of capabilities to be shown to the user by Mercuro 4.x includes:

Video Call (3G CS video call)
Image Sharing (PRD IR.79 Image Share Interoperability Specification 1.0)
Video Sharing (PRD IR.74 Video Share Interoperability Specification, 1.0)
File Transfer (OMA SIMPLE IM 1.0)
Session Mode Messaging (OMA Instant Messaging using SIMPLE, 1.0)

Capabilities indication can be seen as “what type of communication I’m willing to accept”.

2.6 Presence authorization

Once your presence information is published you can choose with who you want to share it. At any time you can choose to accept, block, ignore or revoke an existing (or incoming request) authorization. Rules could be managed per lists (black-hat, white-hat …) or per buddy.

You can easily (UI) retrieve associated pres-rules (blocked, allowed …) for each contact.

2.7 Multimedia Element Integration

It is possible to integrate multimedia elements such as photos, portrait icon, free text …

3. Enhanced Messaging

Mercuro supports 1-to-1 and Ad-hoc mode messaging (Instant Messaging using SIMPLE v1.0 chapter 4.3.1). Peer-to-peer IM Session is also supported (chap. 4.3.2).
These services are supported as part of GSMA RCS Phase 1.

Mercuro also supports Pager mode (chap. 4.2.1) and Large Message Mode messaging (chap. 4.2.1).

Group Messages (chap. 4.2.2), Deferred Messages (chap. 4.2.3) and Predefined session mode messaging (chap. 4.3.1) will be supported in release 5.0.

Mercuro (PC version) uses Pager Mode and Large Message Mode messaging to simulate SMS/MMS services.
Mercuro uses OMA Final Delivery Reports (chap. 5.7) to simulate Negative/Positive Acknowledgement Mechanism for MMS messages.

For 1-to-1 mode the caller or callee can add new participants at any time. The exchanged message can contain both text and/or multimedia content (SMIL, images, videos ...).

End party activity (typing/composing) is indicated to all participants.

4. Content Sharing

4.1 Image Sharing

In 3GPP specifications Image sharing is defined as a service for sharing images between users during a mobile phone call (CS Call). These specifications were defined by the GSM Association for cellular network. For packet-only devices (e.g. Mercuro PC version) all these specifications do not apply. This mean that no CS voice call set up is required prior to sharing the images.
The Message Session Relay Protocol (MSRP), IETF RFC 4975, is mandatory for the Image Share Service. Image data information settings in SIP/SDP follow IETF File transfer RFC 5547 (previously [draft-ietf-mmusic-file-transfer-mech]).

To see how this feature is used in Mercuro IMS Client --> [http://imsclient.blogspot.com/2008/09/rcs-rich-communication-suite-image.html].

4.2 Video Sharing

This feature will be supported in release 5.0.

GSMA Video Sharing is vendor independent and a Peer-To-Peer service and doesn’t require special/dedicated server.
A compliant RCS Client shall be able to share live Video (by sharing the camera capture) and sharing pre-recorded Video is a handset implementation option.
Video codec H.263-2000 profile 0 level 45 is mandatory (QCIF). To have better Video quality MPEG4 Visual Simple Profile 0b and H.264/AVC Baseline Profile Level 1b could be optionally used.

5. File Transfer

Many technical references are common to GSMA Image Sharing but this service allows exchanging different types of content (text, documents, SMIL, videos …).
Both end clients (caller/callee) can start file transfer session during an ongoing session (CS/PS call) or without having an ongoing session.
Only 1-to-1 file transfer feature is supported in GSMA RCS phase 1 and only a single file can be transferred per session. Only sending/receiving files are supported and requesting files is not part of the GSMA RCS phase 1 use cases.

6. Main IETF/OMA specifications (3GPP omitted)

6.1 Enhanced address Book

[OMA-TS-XDM_Core-V1_1-20080627-A]
[OMA-WP-XDM_1_1_Implementation_Guidelines-20080627-C]
[OMA-TS-Presence-SIMPLE_Content_XDM-V1_0-20081223-C]
[OMA-TS-Presence_SIMPLE-V1_1-20080627-A]
[RFC 2387] + [RFC 3265] + [RFC 3857] + [RFC 3858] + [RFC 3863] + [RFC 3903] + [RFC 4662] + [RFC 4479] + [RFC 4480] + [RFC 4482] + [RFC 4483] + [RFC 4825] + [RFC 5025] + [RFC 5262] + [RFC 5264]

6.2 Enhanced Messaging (-minus those listed above)

[OMA-TS-SIMPLE_IM-V1_0-20080903-C]
[RFC 3862] + [RFC 3891] + [RFC 3994] + [RFC 4028] + [RFC 4145] + [RFC 4353] + [RFC 4488] + [RFC 4575] + [RFC 4579] + [RFC 4975] + [RFC 5366]

6.3 Image Sharing

[GSMA PRD IR.79 Image Share Interoperability Specification 1.0]
[RFC 4145] + [RFC 4575] + [RFC 4975] + [RFC 5547]

6.4 File Transfer

[OMA-TS-SIMPLE_IM-V1_0-20080903-C]
[RFC 4145] + [RFC 4575] + [RFC 4975] + [RFC 5547]

New Release of Mercuro IMS Client (4.0.1258)

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

[BRONZE, SILVER, GOLD]
- Fix crash when DNS request failed
- Fix crash when system time shifts during a session
- Add support for Early IMS authentication

[SILVER, GOLD]
- Fix Uri parsing when dealing with IPv6 domain
- Fix display of CPIM messages
- Add support for embedded images in MSRP
- Add support for QoS advertisement in 200OK OPTIONS

[GOLD]
- Fix protected source port for response with IPSec
- Fix re-registration temporary SA generation with IPSec

Your feedback is welcomed (http://feedback.mercuro.net/)

Inexbee joins the GSMA RCS program

Inexbee becomes an official participant of GSMA Rich Communications Suite (RCS) program. Inexbee restates its commitment to the standards for its Mercuro IMS Client. The Rich Communication Suite (RCS) Initiative is an effort of a group of like-minded industry players for the rapid adoption of mobile applications and services providing an interoperable, convergent, rich communication experience.



The RCS Initiative includes network operators, network and device vendors. More than 60 companies are collaborating in the RCS programme including Acision, Orange, Telecom Italia, Telefonica, Swisscom, Comverse, Nokia Siemens Networks, Nokia, Sony Ericsson and Samsung. Inexbee supports RCS in Mercuro IMS Client.

More information on the GSMA and Mercuro IMS Client websites.

P-Preferred-Identity : Selecting your preferred identity

Beginning with the release 4.0.1236 of Mercuro IMS Client, you now have the ability to select what will be the preferred identity when initiating sessions; this is reflected in the P-Preferred-Identity header.
To select the preferred identity, go to the Registration page, select the identity and click the button (see image below): the identity is now the preferred identity.


You must have a Silver or a Gold editions to have the button and note that by now, this selection is not persistent. Have fun !!!

New Release of Mercuro IMS Client (4.0.1236)

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

[BRONZE, SILVER, GOLD]
- Add feedback message when call failed to establish.
- Add support for PRACK for Bronze edition.
- Use P-Asserted-Identity header to identify remote party if present.
- Fix DMTF keyboard so it does not overlap the video.
- Fix the crash when Web Browser is too slow to respond.
- Fix the crash when used for a long time with Remote Desktop or Terminal Services.

[SILVER, GOLD]
- Add ability to select the preferred identity.
- Finalize the support for session timers.
- Fix the download notification not to show up before activation.
- Fix activation failure with some license codes.
- Fix TLS certificates update in options.
- Fix update download error for Silver edition.

[GOLD]
- Add visual feedback when security agreement is used.
- IPSec client ports are now distincts.
- Finalize support for QoS PreConditions (as per RFC 3312).
- Fix DHCP discovery, so multiple domains are correctly handled.

Your feedback is welcomed (http://feedback.mercuro.net/)

Mercuro Online Help

We have started to write an online help, which was a frequent wish from our users. You can visit it at http://www.mercuro.net/help/. Note that this is a work in progress, and that the content is getting bigger day after day.

The online will be available directly from the Mercuro IMS Client, starting with the next release.

IMS Client versus IMS Softphone

Q: What is the difference between an IMS Client and an IMS Softphone ?
A: Well, an IMS Client is basically an IMS Softphone that comes with a lot of additionnal features. While an IMS Softphone will be dedicated to telephony (audio/video) features, an IMS Client will handle things such as IM chat, file transfers, network based address book, presence, service activation, image/video sharing, etc. But, more and more, IMS Softphones are becoming IMS Clients. The ultimate goal is to provide an integrated and simple access to the various IMS services, now and in the future.

Inexbee joins the OpenIMSCore project

Inexbee is pleased to announce that one of the Mercuro's technical team member, Laurent Etiemble, has joined the OpenIMSCore project as a commiter. Most of the effort will be focused on the Gm and Ut interfaces (TLS, IPSec, etc.). Inexbee fully supports Open Source and is proud to allocate resources to such a successful project.

New Release of Mercuro IMS Client (4.0.1202)

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

[BRONZE, SILVER, GOLD]
- Improve SHA-1 computation for MSRP file transfer
- Allow MSRP file transfer with unknown size
- Allow MSRP chunk size with arbitrary size
- Improve memory usage of audio codecs (G.711, GSM, iLBC)
- Fix crash when using Remote Desktop or Terminal Services
- Fix the invalid transaction Id in MSRP Report responses
- Fix a wrong feedback for 407 errors
- Fix invalid order in SDP attributes
- Fix MSRP byte range parsing for edge cases
- Fix MSRP session negociation when accept-types don't match
- Fix Allow header in SIP OPTIONS
- Fix SDP handling, when offer is not done in INVITE (as per RFC 3261)

[SILVER, GOLD]
- Fix a wrong escaping of the GSMA option tags
- Improve capabilities query with in-dialog SIP OPTIONS
- Fix User-Agent to be compliant with OMA specifications

Your feedback is welcomed (http://feedback.mercuro.net/).

IMS Client for Windows Mobile

After the success of Mercuro IMS Client on Windows XP/Vista, Inexbee has launched Mercuro Pocket.

Mercuro Pocket is fully compliant with main 3GPP/IETF specifications and can be used to make voice calls over wireless connection (Both IPv4 and IPv6 networks are supported).

This IMS client includes OMA/IETF XDM features that make possible to store your buddy list on a remote server using XCAP protocol, and get the presence information.

Inexbee has incorporated a special mechanism that routes the audio streams for the SIP/IMS calls to the handset's earpiece instead of the handset's speaker. This results in high quality audio on all major handsets (HTC, BenQ, Samsung, HP, …).

GSMA Image Sharing and Video Sharing features are under development and will be released soon.

Mercuro Pocket can be used as a normal SIP /VoIP client and is now available for download at http://www.mercuro.net.

New Release of Mercuro IMS Client (4.0.1178)

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

[BRONZE, SILVER, GOLD]
- Fix the update check to report if the check was successfull
- Fix a crash with MSRP chunk overflow
- Improve MSRP transfer speed

[SILVER, GOLD]
- Fix the DNS NAPTR when used on a mixed IP stack (IPv4/Ipv6)
- Fix configuration import/export
- Fix crash when Auto-Answer is enabled
- Fix emoticons egdes
- Enhance call transfer dialog
- Add support for CPIM (Common Presence and Instant Messaging)
- Add ability to set the Operator Identifier and AMF values

[GOLD]
- Add ESP (Null, AES, CBC) support for IPSec for IPv4 and IPv6 on Windows XP and Vista.

Your feedback is welcomed (http://feedback.mercuro.net/).

Commercial version of Mercuro IMS Client is now available

	Inexbee’s Mercuro IMS Client is the result of more than four years of expertise in telecom and convergence software development. Today, the Mercuro IMS Client is the most complete and 3GPP/IMS/RCS compliant softphone available. After several months of live testing and thanks to the active contribution of many of you, the beta version is withdrawn to give birth to a Bronze, Silver and Gold edition on Windows and Windows Mobile.
	Mercuro Bronze Edition Inexbee is providing a free version of the Mercuro IMS Client. The Bronze edition is the entry level version that offers all of the most common features of IMS. It is perfect to begin IMS testing and deployment. The Mercuro Bronze edition is downloadable for free directly from our website: www.mercuro.net
	Mercuro Silver Edition + Mercuro Pocket (beta) The Mercuro IMS Client Silver edition is our most complete version of IMS Client. It includes all of the features of the Bronze edition. Additionaly, it is compliant with the latest security Networks and is carrying OMA XDMS support. It can be used in carrier-grade IMS environment. Be among the first to buy the Mercuro Silver Edition and get the beta Mercuro Pocket Silver edition (for Windows Mobile) for free. You can buy it directly from our website: www.mercuro.net
	Mercuro Gold Edition (On Request) Fully customizable, the Gold edition is available on request and is dedicated to large deployments and provides custom branding, QoS features and high quality codec. For further information please refer to: www.mercuro.net
	About Mercuro Inexbee is a worldwide leader in software development for multimedia convergence and interoperability. Mercuro team is part of a large community of companies and independent engineers setting up the standards of the next Rich Communication Suite and bringing to life the concept of Multimedia Convergence Service. For further information please refer to: www.mercuro.net
	Copyright 2008 © Inexbee - All Rights Reserved

Inexbee advances interoperability by participating in IMS PlugFest™ 6 event

Inexbee, the provider of Mercuro IMS Client, has participated to the 6th PlugFest event. The event was hold January 12-16, 2009, at the University of New Hampshire IMS Interoperability Lab (UNH-IOL) in Durham, N.H.

Plugfest 6 has addressed the User-to network ‘Gm interface', the vital link between end-users and service providers. In addition, Plugfest 6 has expanded the success from previous interoperability events to include robustness, reliability and certification of key IMS SIP and Diameter interfaces as well as local and visited network services.

Mercuro IMS Client, as a User End-Point, was able to integrate seamlessly with cores from different vendors, in local or visited situation.

In addition to participating in the IMS Forum's Plugfests, Inexbee is conducting SIP and IMS interoperability testing with partners (Core provider, AS providers, etc) in order to improve the Mercuro IMS Client.