See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/232627204

The UCT IMS client

Article · January 2009

DOI: 10.1109/TRIDENTCOM.2009.4976254

CITATIONS READS
14 1,868

4 authors, including:

R. Good Richard Spiers

University of Cape Town University of Cape Town
18 PUBLICATIONS   141 CITATIONS    10 PUBLICATIONS   61 CITATIONS   

SEE PROFILE SEE PROFILE

Neco Ventura
University of Cape Town
207 PUBLICATIONS   689 CITATIONS   

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

UNIFI - UNIversities for Future Internet View project

Efficient Resource Utilization for Next generation Networks with Social Considerations View project

All content following this page was uploaded by Neco Ventura on 16 December 2014.

The user has requested enhancement of the downloaded file.

 The VCT IMS Client
David WaitingT, Richard Good8, Richard Spiers8 and Neco Ventura8
TTelkom SA Ltd, Pretoria, South Africa
Email: waitindc@telkom.co.za
8University of Cape Town, Rondebosch, South Africa
Email: {rgood.rspiers.neco}@crg.ee.uct.ac.za
Abstract-The VCT IMS Client is a free open source imple-
mentation of a 3GPP IMS Client. The project was started with the
goal of creating a flexible and extensible code base for researchers
and industry specialists to use the many communication services
offered by the IMS. Since its inception in 2006 the client has
grown, both in terms of its stability and its feature set, and is
used worldwide by IMS enthusiasts as a means to experiment
with IMS without any associated risks or costs.
This paper describes the history of the project, the software
architecture, the supported services and provides results of the
various interoperability tests that have been performed between
the VCT IMS Client and other freely available IMS Clients.
I. INTRODUCTION
The 3GPP first began standardisation of the IP Multimedia
Subsystem (IMS) in Release 5 of their specifications with the
goal to fill the need for an all-IP multimedia framework for
next generation mobile networks. Since then there has been
much activity in several standardisation bodies, including ETSI
TISPAN, 3GPP2 and Packet Cable, to incorporate the IMS
into their own specifications. However, despite the fact that
IMS was first proposed several years ago and that there has
been widespread interest in the technology worldwide, there
is relatively little IMS software available to the general public.
The Fraunhofer Institute FaKUS first identified the void
of IMS software in 2006 and consequently began developing
the Open IMS Core project [1]. This project encompassed
the core elements of an IMS network, the three Call Session
Control Functions (CSCFs) and the Home Subscriber Server
(HSS). The Open IMS Core software was released free to
the public in November of 2006, under the open source GNU
General Public License version 2 (GPLv2). By releasing this
software freely on the Internet Fraunhofer FOKUS instantly
made the new and powerful technology that is IMS available
to telcos, vendors, research institutions and the general public,
and opened the door for all these users to try the technology
without risk or cost. Unfortunately, one key piece of the IMS
puzzle was still not freely available: the IMS client. Although
Fraunhofer FOKUS also released a SIP-to-IMS gateway the
true power of the Open IMS Core could never be realised with
a vanilla SIP client.
Soon after the release of the Open IMS Core researchers
at the University of Cape Town (UCT) identified the need
for a pure IMS client for their own research. The UCT IMS
Client project was born as an open source initiative and was
released freely on the Internet under the GPLv2 in order to
encourage and drive innovative IMS research from the large
Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.
pool of potential developers and testers located around the
world [2]. The client, which originally offered only basic voice
calling capabilities quickly grew in robustness and scale, and
at the time of writing supports a multitude of features, includ-
ing video calling, presence, instant messaging, authentication,
XML Configuration Access Protocol (XCAP) and Real Time
Streaming Protocol (RTSP) for video on demand applications.
Reports from the dedicated UCT IMS Client mailing list
indicate that the client has a substantial following, particularly
in Europe and Asia. Fig. 1 shows the relative number of
visits to the UCT IMS Client website from cities around the
world as reported by Google Analytics. At the University of
Cape Town the client has been used extensively by under-
graduate and post-graduate students to develop new IMS
applications, including network-stored address books, IMS
multimedia servers and interactive games to name but a few.
This paper is dedicated to a in-depth overview of the
UCT IMS Client, including a look at its architecture, the
dynamically linked libraries, a detailed description of the
client's features and some examples of how it has enhanced
IMS research. We then describe a recommended IMS testbed
environment, similar to the one located at the University of
Cape Town, that allows the IMS enthusiast to fully utilise
the client's many features. Since the release of the UCT IMS
Client in 2006, other IMS clients have been released freely
on the Internet. We compare the features of these clients
to the UCT IMS Client and detail the results of various
interoperability tests.
II. CLIENT ARCHITECTURE
The goal of the UCT IMS Client project is to produce
software that is free, both in terms of cost and software
freedoms, that can be easily installed, operated and modified
by researchers looking to learn more about IMS. Therefore,
the use of Linux and its many freely available libraries was a
natural choice for the operating environment. An unfortunate
consequence of this choice, is that the client cannot easily be
run in the ubiquitous Windows environment, nor can it run
natively on current generation mobile devices, however, this
does not limit the client's primary purpose as a research and
testing tool.
An IMS client requires several IETF protocols in order
to perform its various functions, such as Session Initiation
Protocol (SIP) [3], Real-time Transport Protocol (RTP) [4],
XML Configuration Access Protocol (XCAP) [5], Message
 .
"

. .'
':
,. • • __.~

..
'.
I"~

• ,:-_. __ ,~_ ~l:,'"

I
-:,'
..
•

:~I~._.>::-
.
.
..
::1. .-.1',-

" .... -/

" ,I "'\, I

r
.i.':/-·-~::~, ~,'

•
Figure 1. Visits to the UCT IMS Client website.

r' Signaling ------

r Media --------1 extensible and modular architecture provides a great deal
oSIP I eXosip I I

: gStreamer :
of flexibility to the program developer. gStreamer provides
I
I
1
1 modules to capture audio and video, encode the voice and
libCurl 1
libMSRP : video and packetise the resultant bit stream into RTP packets
I

IibVLC
~ J for transmission across the network.
D. libVLC
Figure 2. UCT IMS Client software architecture. The RTSP signalling functions that allow for the description,
setup and control of on-demand video streams are provided by
libVLC [13]. This library supports media trick functions such
Session Relay Protocol (MSRP) [6] and Real Time Streaming as play, pause, fast-forward and rewind.
Protocol (RTSP) [7]. The UCT IMS Client uses several
existing libraries that implement these protocols. All libraries, E. libMSRP
except for libMSRP, are dynamically linked at run-time and libMSRP provides a set of functions that allows the client to
therefore must exist on the host machine for the client to run transmit a series of related instant messages in the context of a
successfully. libMSRP is not currently available in popular session [14]. Message sessions are treated like any other IMS
Linux distributions and is therefore included as part of the session and the instant messaging data is transferred in the
client source code. data plane. Session-based instant messaging has a number of
A. oSIP and eXosip advantages over the traditional page-mode method, including
The oSIP library provides a low-level SIP stack useful for tighter integration with other media types, and brokered pri-
the creation of SIP proxies and end-points [8]. The eXosip vacy and security. libMSRP is a high-level API that provides
library on the other hand is a high-level API that abstracts simple methods to initiate, process and terminate session-based
much of the complexity of the oSIP library by providing instant messaging sessions.
methods to create SIP messages, responses and handle SIP III. CLIENT FEATURES
dialogs [9].
The first release of the UCT IMS Client supported only
B. libcurl and libxm12 basic voice calls using the j.,t-Iaw and A-law codecs. Apart
libCurl provides an HTTP stack for providing the GET and from the basic functionality of an IMS client, such as regis-
PUT commands that XCAP requires to download and upload tration with the core network, the client now also supports the
files to an XDMS respectively [10]. The XML content of following rich communications features.
the HTTP messages is created and parsed by the libXML2
A. Voice and Video Sessions
library [11].
The client can make voice and video calls with another suit-
C. gStreamer able IMS client once it has registered with its home network.
The gStreamer library provides a modular framework for The client extracts the service routes from the registration
handling many types of multimedia. Several gStreamer ele- process and routes calls to the home network S-CSCF from
ments can be linked together to form a pipeline [12]. This where they are routed to the terminating party.

Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.
 The client supports JL-Iaw, A-law, GSM and MP2 audio
codecs, and the H263 video codec. It is possible to vary the
video codec bit-rate between three different settings in case the
bandwidth of the host device is limited. It is possible during
an on-going session to re-negotiate the media components. In
this case the user simply selects different media components,
codecs or bit-rate, and re-INVITES the session.
B. Presence
The client supports SIP for Instant Messaging and Presence
Leveraging Extensions (SIMPLE) whereby the SIP subscrip-
tion mechanisms are utilised to subscribe to another user's
presence status. The client can subscribe to a users presence
event and will be notified whenever the status changes or the
user goes offline.
It is also possible to subscribe to a list of presence watchers
- the other parties that are currently subscribed to the user's
presence. The client subscribes to the watcher info event
(presence.winfo) and is notified whenever a new subscription
is made to their presence status. It is possible to authorise or
block these subscriptions if the presence server supports such
mechanisms.
C. Instant Messaging
The client supports the two types of instant messaging
currently prescribed in IMS networks, pager mode and session-
based. Pager mode messages are sent in the body of SIP
MESSAGE requests whereas session-based messages are sent
across the media plane, in a similar fashion that IMS separates
the signalling and media of voice and video sessions. The
client supports a form of typing notification to alert the
corresponding party of keyboard activity [15].
D. Streaming Video and Video on Demand
The client supports two modes of uni-directional video
viewing. The client can simply setup a session with a video
server in a similar manner that it would with another IMS
client by sending a SIP INVITE message and then negotiating
the codecs via SIP/SOP. Alternatively, the client can setup the
session using the RTSP protocol. This has the added benefits
of the previously mentioned trick-play functions that are more
suitable for video-on-demand applications, which allow the
user to manipulate the incoming video feed.
IV. RECOMMENDED COMPONENTS OF AN OPEN SOURCE
IMS TESTBED
The primary motivation for an open source IMS testbed is to
expose the complex concepts and components associated with
IMS technology and Service Delivery Platforms in general to a
wide set of developers. Such a testbed brings academia and in-
dustry together, and helps accelerate technology development
and acceptance. From the research point of view these testbeds
facilitate easy prototyping and experimentation with new ideas,
and provide a safe and controlled area where technologies,
protocols and applications can be analysed, separate from the
live environment and associated hazards. In this section the
Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.
basic components needed to create an open source IMS testbed
environment are described.
A. IMS Core Elements
Central to an IMS testbed are the service control layer
elements that perform IMS authorisation, signalling and ser-
vice invocation. IMS Core elements are numerous and include
gateway and media processing functions. However, for a basic
system that supports registration and IMS session setup, only
core Call Session Control Functions (CSCF) and a Home Sub-
scriber Server (HSS) are necessary. The core CSCFs include a
Proxy-CSCF (P-CSCF), an Interrogating-CSCF (I-CSCF) and
a Serving-CSCF (S-CSCF). The P-CSCF is the first point
of entry into the IMS network, and can be located in the
home or visited network. This element is involved with signal
compression, security and resource management. The I-CSCF
is a SIP proxy located at the edge of an administrative domain,
and can be used to encrypt sensitive information to hide
network topology. The S-CSCF is always located in the home
network, and carries out admission control and application
invocation functions. The FOKUS Open Source IMS Core
provides software implementations of the core CSCF and HSS
functional elements [1]. It is a 3GPP standards based software
package that provides a reliable and comprehensive testing
framework for IMS applications.
B. End User Equipment
To interact with the IMS core and perform key IMS proce-
dures like registration and session initiation, end user equip-
ment is necessary. IMS clients range in functionality from
basic emulators that support registration and voice calls, to
application specific clients that support a number of integrated
applications, e.g. an IMS IPtv client that specifically caters
for streaming videos. At the very least, end user equipment
deployed in an IMS testbed should support AKAvl/2-MD5
authentication, IMS SIP signalling including pre-conditions,
basic voice and video, instant messaging, presence and XCAP.
Freely available end user IMS emulators include the UCT IMS
Client [2], the FOKUS Open IC Lite, the IMS Communi-
cator [16] and the Mercuro IMS Client [17]; each is useful
for different scenarios. The UCT IMS Client is particularly
useful to Linux developers that require access to the lower
level architecture details in order to test and prototype new
applications.
C. Presence Support
Presence on the Internet is an application that allows a user
to publish their communication status, indicating their avail-
ability and willingness to communicate. In IMS, SIP-based
presence will be a key enabler for achieving the envisaged rich
multimedia experience. As a service enabler, presence infor-
mation can be incorporated into any number of services, e.g.
IPtv, a presence enabled address book, etc. In an IMS testbed
a presence server should allow end users, or "presentities" as
they are known, to publish their status as well as allowing them
to subscribe to other presentities, becoming watchers. The
 Table I
FEATURE SUMMARY OF UCT IMS CLIENT, FOKUS OPEN IC LITE, IMS COMMUNICATOR AND MERCURO IMS CLIENT.
VCT IMS Client FOKVS Open IC Lite IMS Communicator Mercuro IMS Client
Registration AKAvl/2-MD5; MD5 AKAvl/2-MD5; MD5 AKAvl-MD5; MD5 AKAvl/2-MD5; MD5
IMS signalling
PRACK support No PRACK support PRACK support PRACK support
Pre-condition support No pre-condition Support Pre-condition support Pre-condition support
Media Support Audio / Video Audio Audio / Video Audio
Presence Support
Presence support No presence support No presence support Presence support
Watcher authentication Watcher authentication
Instant Messaging Pager mode / Session-based Pager mode No support Pager mode / Session-based
XCAP Support XCAP support No XCAP support No XCAP support XCAP support
Platform Linux Windows / Linux Windows / Linux Windows
License GPLv3 Free, Closed Source LGLP Free, Closed Source

presence server should support watcher authentication based

on uploaded presence rules. OpenSIPS is a high performance
SIP server, and when associated presence modules are enabled
I H~
OpenXCAP

XDM Server Presence

I
Streaming
and configured, it can process SIP PUBLISH and SUBSCRIBE Server Media Server
messages to provide the essential presence functionality [18].

----.f~-
Application
D. XML Document Management Support
SIP

.a
XML Document Management (XDM) is an Open Mobile Diameter
BOPENSOURCEI
HTTP
Alliance enabler that is standardised and widely accepted as SQL
an IMS application that can be used for the storage and
retrieval of XML documents from a centralised server in the 6i·····;:··::~Bi
-=t* . #<:
J.aa II S<SCf
Service Control

IMS network. The specification uses the XML Configuration

Access Protocol (XCAP) to transmit policy documents. This Ut ~~8
protocol defines HTTP PUT, GET and DELETE methods to
____ J _
store, retrieve and delete documents. The information is carried
over a secure HTTP connection which utilises "out-of-band" 1 End User Equipment
signalling that is separate from IMS signalling. XCAP support
is another service enabler that can be integrated into any ::~~'·I
number of applications including policy storage for privacy
and resource management, a network stored address book,
·~~II ~
UCTIMS Fokus Open IMS Mercuro IMS
etc. An XDM Server and associated XCAP support at the Client IC Lite Communicator Client
end user device is an important element for application pro-
totyping and development in an IMS testbed. OpenXCAP is Figure 3. An IMS Testbed based on open source components.
a fully functional XCAP server that facilitates the storage
and retrieval of XML documents [19]. This can be used to
manage buddy lists and policy information. OpenXCAP works INVITE request; this is forwarded to an indirection server that
in co-ordination with the OpenSIPS presence server to perform maps the requests to a specific RTSP address and returns it to
watcher authorisation. the end user; using this RTSP address the end user establishes
a video session with an RTSP enabled media server.
E. Streaming Media Support Fig. 3 shows the basic components that comprise an Open
The provisioning of Multimedia on Demand Services, like Source IMS Testbed.
Video on Demand (VoD), offers significant revenue opportu-
nities for traditional telecommunications carriers. In several V. INTEROPERABILITY WITH OTHER IMS CLIENTS
cases IPtv and VoD are the driving motivation for IMS The purpose of interoperability testing is to prove that
adoption. There are a myriad of standardised IPtv architectures end-to-end functionality between at least two communicating
and in the practical environment this area is enjoying much devices is as required by the standards on which those systems
research attention. Essential to an IMS testbed is some form are based [20]. These tests generally refer to the semi-formal
of streaming media or VoD server that utilises the IMS tests carried out during multi-vendor events - often referred to
procedures to authenticate subscribers as well as streaming as "plug-fests", "interops" or "bake-offs". In this section basic
the requested media. The UCT Advanced IPTV Server is interoperability test are carried out between the UCT IMS
an IMS IPtv implementation based on TISPAN and IETF Client and three other freely available IMS Client platforms,
standards [2]. Using an XML-based Electronic Program Guide namely the FOKUS Open IC Lite, the IMS Communicator, and
an end users requests video content in the form of a SIP the Mercuro IMS Client. By using a structured suite of tests,

Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.
these results are easily repeatable. Note that as of December
2008 all of these clients are under active development. The
FOKUS Open IC Lite is a free version of the Open IC that
contains only a subset of the full Open IC client features.
Table I summarises the client features.
functionality, and can subscribe to another clients presentity.
The verdict for this test case is either SUCCESS or FAILURE.
Fig. 6 shows the test arrangement.

A. Testing Methodology
To evaluate basic interoperability, test cases are defined for
IMS session initiation, media support, presence support and
instant messaging support. To evaluate session initiation, the Subscribe

Ej
UCT IMS Client initiates an IMS audio session with each other to presentity

8
client, and signalling is analysed. The purpose of this test is to
verify whether the UCT IMS Clients can successfully establish
IMS sessions with other clients, whether pre-conditions are
supported, and whether sessions can be renegotiated. The System Under Qualified
Test Equipment
verdict for each of these test steps is either SUCCESS or
FAILURE. Figure 4 shows the test arrangement. Figure 6. Test arrangement for presence test case.

~e~
Instant Messaging (1M) support is an important character-
istic of an IMS client. This can be achieved using the SIP
MESSAGE methods known as Pager mode 1M, or using the

~ Message Session Relay Protocol known as Session-based 1M.

8
/ Session
To evaluate the clients ability to support instant messaging,
Client 1 Initiation
i£<
~;.,.:.:.'~,: ~.,.).,
( '.;•.:• . . Client
' .2
:. .\'.•;.'
.<'
the UCT IMS Client initiates a pager mode and session-
based (where applicable) 1M exchange with all other clients -
System Under Qualified and vice versa. The purpose of this test is to verify whether
Test Equipment each client can process pager mode and session-based instant
messages, and whether writing notification is supported. The
Figure 4. Test arrangement for session initiation test case.
verdict for each of these test steps is either SUCCESS or
FAILURE. Fig. 7 shows the test arrangement.

r
To evaluate media support, audio and video sessions are

E1\
established between the UCT IMS Client and all other client
implementations. The audio and video streams are analysed by

€:,
a human user. The purpose of the test is to verify whether each P
client can establish satisfactory media sessions with the other

8
clients. The verdict for this test case is either SUCCESS or
FAILURE, the quality of the video and audio is not examined.
Fig. 5 shows the test arrangement.
Session-
System Under based 1M Qualified

t:~
Test Equipment

Figure 7. Test arrangement for instant messaging test case.

8 .:--------.:. t:o:)
System Under
AudioNideo streams

Test
Figure 5. Test arrangement for media test case.
To determine whether each client sufficiently supports SIP-
based presence, the UCT IMS Client uploads presence infor-
mation, and all other clients become watchers and subscribe
to this presence information - and vice versa. The purpose
of this test is to verify whether the clients support presence
Qualified
B. Results
Table II summarises the results of the inter-operability
tests - each test case is evaluated to either SUCCESS or
Equipment FAILURE. As a benchmark the UCT IMS Client, when
tested against itself, was successful for all test cases. For
the session initiation test case, basic SIP signalling was
successful for all clients, however when enabling PRACK and
particularly pre-condition support, the clients exhibited poor
interoperability. Audio sessions were successfully established
between the UCT IMS Client and all other clients, though
between the UCT IMS Client and the FOKUS Open IC Lite
the sound quality was very poor and the audio stream was

Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.
 Table II
SUMMARY OF INTER-OPERABILITY TESTS BETWEEN UCT IMS CLIENT AND OTHER CLIENT IMPLEMENTATIONS.

FOKUS Open IC Lite IMS Communicator Mercuro IMS Client

Basic SIP signalling ./ Basic SIP signalling ./ Basic SIP signalling ./
PRACK support X PRACK support ./ PRACK support ./
Session initiation
Pre-condition support X Pre-condition support X Pre-condition support X
Session re-negotiation ./ Session re-negotiation ./ Session re-negotiation ./
Audio X Audio ./ Audio ./
Media support
Video X Video X Video X
Presence support Presence support X Presence support X Presence support ./
Pager mode ./ Pager mode X Pager mode ./
Instant messaging support Session-based X Session-based X Session-based X
Writing notification X Writing notification X Writing notification X

unidirectional. However, for video sessions, the limited range REFERENCES

of codecs supported became apparent, as video sessions were [1] P. Weik, D. Vingarzen, and T. Magedanz, "The FOKUS Open IMS
not successfully supported between the UCT IMS Client and Core - A Global Reference Implementation," IMS Handbook - Concepts,
any other implementation. Technologies and Services - Mohamed Ilyas and Syad Ahson, pp. 113-
132, November 2008.
SIP-based presence is a relatively simple application, and [2] University of Cape Town, "UCT IMS Client,"
while it was not supported by all the clients, basic pub- http://uctimsclient.berlios.de/.
[3] J. Rosenberg et. al., "RFC 3261 - SIP: Session Initiation Protocol," June
lishing of communication status, and subscribing to anoth- 2002.
ers presentity was successful when both clients supported [4] H. Schulzrinne et. al., "RFC 3550 - RTP: A Transport Protocol for Real-
presence. Instant messaging support exhibited mixed results. Time Applications," July 2003.
[5] J. Rosenberg, "RFC 4825 - The Extensible Markup Language Configu-
While the simple pager-mode 1M operated successfully across ration Access Protocol," May 2007.
most client implementations, the more complex session-based [6] B. Campbell et. al., "RFC 4975 - The Message Session Relay Protocol
1M demonstrated the different interpretations of the standard (MSRP)," September 2007.
[7] H. Schulzrinne et. al., "RFC 2326 - Real Time Streaming Protocol
adopted by the implementers. (RTSP)," April 1998.
[8] "oSIP," http://WWltv.gnu.org/software/osip/.
c. Discussion [9] A. Moizard, "eXoSIP," http://savannah.nongnu.org/projects/exosip/.
[10] "libCurl," http://curl.haxx.se/.
From the results it is clear that the IMS client implementa- [11] "Libxml2," http://xmlsoft.org/.
[12] "GStreamer Open Source Multimedia Framework,"
tions focus on different application domains. While the Mer- http://gstreamerfreedesktop. orgl.
curo IMS Client is the most comprehensive implementation [13] "LibVLC," http://wiki.videolan.org/Libvlc.
regarding features and standards compliance, the fact that it [14] L. Miniero, "libMSRP," http://sourceforge.net/projects/libmsrp/.
[15] H. Schulzrinne, "RFC 3994 - Indication of Message Composition for
is closed source means that it not very useful to developers Instant Messaging," January 2005.
wanting to extend the code to integrate and prototype new [16] P. Inovacao, "IMS Communicator," http://imscommunicator.berlios.de/.
services and scenarios. Simple application scenarios like basic [17] Inexbee, "Mercuro IMS Client," http://WWltv.mercuro.net/.
[18] "Open SIP Server," http://WWltv.opensips.org/.
session initiation and pager mode instant messaging are widely [19] M. Amarascu, "OpenXCAP," http://WWltv.openxcap.org/.
supported, however with more complex mechanisms like full [20] ETSI TISPAN, "EG 202 237 Generic approach to interoperability
IMS session negotiation including pre-conditions and session- testing," April 2007.
based 1M, standards can be interpreted differently by the
implementers. These results highlight the importance of open
technology initiative, to accelerate implementation interoper-
ability.

VI. CONCLUSIONS AND FUTURE WORK

The UCT IMS Client was developed as a flexible and

extensible tool for the furtherment of research into IMS
networks and services. Since its first release it has seen a great
deal of improvements and additional features. It has been used
extensively world-wide as a tool to understand the basics of
IMS as well as a code-base on which new IMS applications
are developed.
The project will continue into the foreseeable future with
the primary goals of increasing the robustness and readability
of the code, as well as improving the associated documentation
to further promote IMS knowledge transfer.

View publication stats Authorized licensed use limited to: TOKYO. Downloaded on June 30, 2009 at 02:19 from IEEE Xplore. Restrictions apply.