Boghe - IMS/RCS Client for Windows

We are proud to announce the availability of the first alpha release of Boghe, our IMS/RCS client for Windows XP, Vista and 7.



For more information: http://code.google.com/p/boghe/

IMSDroid - SIP/IMS Client for Android (Beta)

We are proud to announce the availability of the first fully featured open source IMS Client for Android devices (1.5 and later).
The main purpose of the project (codename IMSDroid) is to exhibit doubango's features and to offer an IMS client to the open source community.

The current version of IMSDroid partially implements GSMA Rich Communication Suite release 3 and The One Voice profile V1.0.0 (LTE/4G, also known as GSMA VoLTE) specifications. Missing features will be implemented in the next releases. Stay tuned.
Highlights

• SIP(RFC 3261, 3GPP TS 24.229 Rel-9)
• Signaling Compression, SigComp (RFC 3320, 3485, 4077, 4464, 4465, 4896, 5049, 5112 and 1951)
• 
  
• Enhanced Address Book (XCAP storage, authorizations, presence, ...)
• Partial supports for GSMA Rich Communication Suite release 3
• Partial supports for One Voice Profile V1.0.0 (GSMA VoLTE)
• Partial supports for MMTel UNI (used by GSMA RCS and GSMA VoLTE)
• 
  
• IMS-AKA registration (both AKA-v1 and AKA-v2), Digest MD5, Basic
• 3GPP Early IMS Security (3GPP TS 33.978)
• Proxy-CSCF discovery using DNS NAPTR+SRV
• Private extension headers for 3GPP
• Service Route discovery
• Subscription to reg event package (Honoring network initiated (re/de/un)-registration events)
• 
  
• 3GPP SMS Over IP (3GPP TS 23.038, 24.040, 24.011, 24.341 and 24.451)
• Voice Call (AMR-NB, GSM, PCMA, PCMU, Speex-NB, iLBC)
• Video Call (H264, Theora, H.263, H.263-1998, H.261)
• DTMF (RFC 4733)
• QoS negotiation using Preconditions (RFC 3312, 4032 and 5027)
• SIP Session Timers (RFC 4028)
• Provisional Response Acknowledgments (PRACK)
• Communication Hold (3GPP TS 24.610)
• Message Waiting Indication (3GPP TS 24.606)
• Calling E.164 numbers by using ENUM protocol (RFC 3761)
• NAT Traversal using STUN2 (RFC 5389) with possibilities to automatically discover the server by using DNS SRV (TURN already implemented and ICE is under tests)

Many other features are supported by the underlying framework but not exposed to the user interface (in progress). For more information please refer to doubango website.
These features include: IPv6, OMA Large IM Message (MSRP), File Transfer (MSRP), Image Sharing (IR.79), Video Sharing (IR.74), TLS and IPSec Security Agreement (RFC 3329), Proxy-CSCF discovery using DHCPv4/v6, TURN, ...

For more information: http://code.google.com/p/imsdroid

libSigComp Beta 0.2

First beta version of libSigComp is now available for download.
To download source code:
- go to http://code.google.com/p/libsigcomp or
- use command line "svn checkout http://libsigcomp.googlecode.com/svn/trunk/ libsigcomp-read-only"

Released under LGPLv3

libSigComp: THE Open-Source SigComp framework

I’m writing today to announce the launch of libSigComp, an Open-Source SigComp Framework. This project is intended to develop a complete and compliant SigComp Framework to speed-up SigComp integration in Open-Source IMS projects.

As many operators have begun to commercially deploy IMS, the relevance of using SigComp to lower bandwidth usage will come quickly. In my own opinion I think that most operators (especially those using RCS) will question how to reduce SIP signaling (registration, billing, presence, messaging …) bandwidth usage (who will pay bits?).

These questions will especially concern using SIP (or all other text-based protocols) in wireless handsets as part of 2.5G and 3G cellular networks.

SigComp stands for Signaling Compression and has been defined in RFC 3320 by 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 a mandatory part of 3GPP IMS.

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.

The goal of this project is to provide a SigComp framework which:

- Could be used as an external API or Framework

- Highly portable (Coded in C/C++ without any external dependencies)

- Easily configurable (memory usage, priorities in static dictionaries, stateful/stateless modes, dynamic/static/shared compression types …)

- Easy to integrate with any existing SIP/IMS stack, Proxy-CSCF, PoC client …

- Allow to easily plug your own compressor (DEFLATE –RFC 1951- will be the default)

- Robust

- Efficiently run on mobile handsets (small footprint)

- Use small memory (UDVM decompression)

- Run fast without high CPU usage

COMPLIANCE:

RFC 3320: Signaling Compression (SigComp)

RFC 3321: Signaling Compression (SigComp) - Extended Operations

RFC 4464: Signaling Compression (SigComp) Users' Guide

RFC 4465: Signaling Compression (SigComp) Torture Tests

RFC 4077: A Negative Acknowledgement Mechanism for Signaling Compression

RFC 3485: The Session Initiation Protocol (SIP) and Session Description Protocol

(SDP) Static Dictionary for Signaling Compression (SigComp)

RFC 5112: The Presence-Specific Static Dictionary for Signaling Compression (Sigcomp)

RFC 1951: DEFLATE Compressed Data Format Specification version

3GPP TR23.979 Annex C: Required SigComp performance

Released under LGPLv3

MORE INFORMATION:

• To have feedbacks or if you are interested for IOTs don’t hesitate to contact me at diopmamadou{at yahoo}dot fr.
• libSigComp homepage: http://code.google.com/p/libsigcomp/