Are there opensource/commercial IMS in java ?

[Vicky]

Are there any plans of having the IMS framework using jain-slee(java)
technology Or it does not make appropriate choice when openims is
already there .
btw are there any opensource/commericial IMS frameworks in java ?

-Vicky

[Eduardo Martins]

In java 99% of Telco/IMS stuff is not open source (BEA, IBM, HP, etc.), Perhaps the whole 1% open source is the Mobicents platform...

[aayush bhatnagar]

The open ims core hss is in java..if i remember correctly.

[Vicky]

Yes HSS is in pure java/mysqldb but the core is in c .

On Aug 7, 7:16 pm, "aayush bhatnagar" <abhatnagar192...@gmail.com>
wrote:

> The open ims core hss is in java..if i remember correctly.
>

> On 8/7/08, Eduardo Martins <emmart...@gmail.com> wrote:
>
> > In java 99% of Telco/IMS stuff is not open source (BEA, IBM, HP, etc.),
> > Perhaps the whole 1% open source is the Mobicents platform...
>

[Vicky]

So guys then would it make sense to have opensource IMS framework in
pure java(jain-slee) .

-Vicky

[aayush bhatnagar]

I think its a good idea. However, that would put jslee in direct
competetion to ims vendors. An open source ims solution which can be
used commercially would also hurt the margins of ims vendors..bound to
make them cranky ;)

[aayush bhatnagar]

On the flip side..it might also be off focus for moving from the
services plane to the core network. Perhaps if more services can be
developed on top of the slee in addition to Presence...like Push to
Talk, Personal Network Management (release 8 ims), multimedia content
sharing aided by the mobicents media server, group and list management
aided by XDM and so on.
Just my 2 cents..
Aayush

[Jean Deruelle]

We are planning to add IMS interoperability and features to Mobicents
Sip Servlets.
See Issues http://code.google.com/p/mobicents/issues/detail?id=323 and
http://code.google.com/p/mobicents/issues/detail?id=324
If anyone is interested, has ideas, etc feel free to chime in and we
welcome and are eager for any contributions ; we will make our best to
help you in the process.

Thanks in advance
Best regards
Jean Deruelle

[Vicky Kak]

Where to start from ?

[Jean Deruelle]

I would say for Issue 323 try to identify what is needed and what is
currently missing from Mobicents Sip Servlets(MSS) to become an IMS
compliant SIP Application Server. What can be done is to try to use
MSS as a SIP AS along with Open IMS core (http://www.openimscore.org/)
and maybe document the process.

I guess for Issue 324, that would be implementing one or several sip
servlets applications that will acts as CSCFs. In this issue the HSS,
I-CSCF and S-CSCF node can only be implemented once we have Diameter
support which will come soon through Issue 119.

Vladimir may be able to comment more on this too.

Best regards
Jean

[aayush bhatnagar]

Hi Jean :)

With respect to issue #324:

 

What should be the preferred configuration for building the CSCFs? P / I / S co-located on a single machine? Or will the functional split be preserved as shown in the IMS architecture?

 

Regarding the development of the CSCF nodes, the following major use-cases can be present:

---------------------------------------------------------------------------------------------------------------------------------------

 

1) Security association management at the P-CSCF (Temporary SAs/Old SAs/New SAs)

 

2) Registrar functionality at the S-CSCF including implicit registrations (Some checks enforced at the P-CSCF for registration procedures)

 

3) Subscriptions and Notifications ( maintenance of context for the 'reg' event package at the S-CSCF) (Actors: UE/P-CSCF/SIP-AS)

 

4) Subscriptions and Notifications extension: Maintaining the implicit subscription of the REFER event package at the S-CSCF.

 

5) Initial Filter Criteria processing (originating and terminating) and SPT matching at the S-CSCF

 

6) User Profile management and updation (PPR) at the S-CSCF / other procedures towards HSS.

 

7) Topology hiding (THIG) at the I-CSCF (THIG shifted to I-BCF Rel-7 onwards)

 

8) Ma reference point routing due to preconfiguration of PSI sub-domains at the I-CSCF.

 

9) Session initiation / modification / indirection /termination procedures at all three nodes (INVITE/RE-INVITE/REFER/BYE) including the 3-way handshake for media negotiation ( SDP offer answer model)

 

10) Forking.

 

11) ENUM query support for breaking out to PSTN from IMS (BGCF function)

 

12) Selection of  the appropriate S-CSCF at the I-CSCF on the basis of the IMPU or PSI.

 

10) Optional third party registraton procedures at the S-CSCF (towards the SIP-AS)

 

11) Special handling for interactions between the S-CSCF and a B2BUA ( Original Dialog Identifier)

 

13) Media parameter checks at the P and S-CSCF to enforce local policy (SBLP)

 

14) P-CSCF and PCRF interaction.

 

15) Pager mode and Session based messaging through the IMS core (MSRP required)

 

16) Identification of inter-dependencies between the three major functional verticals of the CSCF: Registrar, Subs/Not and Session initiation. (Eg: Sending notifications upon user-initiated deregistration, dropping all active call sessions on network initiated deregistrations, information needed by the Charging Trigger Function (CTF) from all three logical verticals etc)

 

17) Charging (offline common to all).

 

18) Negative scenarios and error conditions.

 

19) Security mechanism support at the CSCF(depedency on the HSS): IMS-AKAv1MD5 algo and SIP Digest

 

20) GRUU management for registrations and Subs/Not at the S-CSCF.

 

                                                                                                      

 

Regards

 

Aayush                                                                                                  

[Jean Deruelle]

Hi Ayyush,

I would say that if the nodes are cleanly separated in different sip
servlets applications (one sar per P / I / S node), the functional
split can be preserved as shown in the IMS architecture.

That's a nice TODO list for sure :-)

[aayush bhatnagar]

I have also made some UML use cases for s-cscf..can i share them here only?

[Jean Deruelle]

What do you mean by share them here only ? do you mean in a private location ?
If you want to share them on mobicents-public google group (which is
public and available to anyone), just go there
http://groups.google.com/group/mobicents-public/files and upload your
files.

Jean

On Fri, Aug 29, 2008 at 3:22 PM, aayush bhatnagar

[aayush bhatnagar]

Actually..i was wanting to ask whether i should attach them in the
email as an attachment..or load it to a repository. I didnt know the
path to the repo..thanks for the link.

[Jean Deruelle]

You can use whatever you found most useful.
emailing as attachment has the benefit of not having to go to another
place to download them and people can search in gmail or their
favorite mail provider but that's just a personal opinion

On Fri, Aug 29, 2008 at 3:44 PM, aayush bhatnagar

[aayush bhatnagar]

okay :)

 

I am attaching 3 diagrams:

 

1) Registration use cases

2) Subscription and Notifications.

3) Call session initiations.

 

Also attaching a word doc, which will just clarify some use-cases that might not make sense just by looking at the diagram.

 

Thanks

Aayush

[Jean Deruelle]

Thanks for your contribution aayush.
Issue 324 has been updated to link to this thread.

On Fri, Aug 29, 2008 at 6:40 PM, aayush bhatnagar

[Jean Deruelle]

Thanks for the evangelization part and spreading the word :-)
We would gladly welcome any open source contributions to Mobicents Sip Servlets.
I guess since you're focusing more on applications this will have to
wait until we are done with implementing IMS nodes on top of MSS, but
we would definitely be interested in having applications contributed
by your group !

Thakns in advance :-)
Jean

On Sun, Sep 14, 2008 at 6:19 PM, narfice
<ihatefillin...@gmail.com> wrote:
>
> The Communications Research Group at the University of Cape Town has
> many members working on IMS related projects. Currently most of our
> focus is on applications, which are being developed in C, because the
> UCT IMS Client is written in C, and interacts with the open IMS core.
> There was a java UCT IMS Client, but I think that fell by the wayside.
> All of our work is open source and admittedly much more research-
> oriented than really good application and implementation-oriented (ie
> buggy, etc).
> I'm the only person at the moment using mobicents tomcat and sip
> servlets in the group, but creating a buzz around the water cooler, as
> it were. I reckon java and tomcat is the way to go, especially for
> applications. I'll make others in the group aware of this project (if
> it becomes one), there may be some interest. Tomcat makes a serious
> server much easier to create than starting pretty much in scratch from
> C, which is what most of our projects unfortunately are. Thanks for
> the awesome product!
> mike
> PS from our experience, splitting the entities between desktop pc's is
> beneficial, a single pc running all entities with applications really
> takes strain, even in simple research environments.
>
> I'm doing post-graduate IMS research at UCT (crg.ee.uct.ac.za), and
> the UCT IMS Client was I think the first open source IMS client to be
> released (we like to claim so) - it's unfortunately in C, and
> developed primarily on and for Ubuntu, but that's because the open
> source core is written for linux. Most of our MSc research is based on
> applications, but I'm keen to try convert people coming in to the
> group to using java and mobicents tomcat. Writing a server in C that
> matches tomcats' multithreading and everything else is just too much
> for a research project!

>
>
>
> On Sep 12, 2:57 pm, "Jean Deruelle" <jean.derue...@gmail.com> wrote:
>> Thanks for your contribution aayush.
>> Issue 324 has been updated to link to this thread.
>>
>> On Fri, Aug 29, 2008 at 6:40 PM, aayush bhatnagar
>>

>> <abhatnagar192...@gmail.com> wrote:
>> > okay :)
>>
>> > I am attaching 3 diagrams:
>>
>> > 1) Registration use cases
>> > 2) Subscription and Notifications.
>> > 3) Call session initiations.
>>
>> > Also attaching a word doc, which will just clarify some use-cases that might
>> > not make sense just by looking at the diagram.
>>
>> > Thanks
>> > Aayush
>>

>> > On Fri, Aug 29, 2008 at 7:17 PM, Jean Deruelle <jean.derue...@gmail.com>

>> > wrote:
>>
>> >> You can use whatever you found most useful.
>> >> emailing as attachment has the benefit of not having to go to another
>> >> place to download them and people can search in gmail or their
>> >> favorite mail provider but that's just a personal opinion
>>
>> >> On Fri, Aug 29, 2008 at 3:44 PM, aayush bhatnagar
>> >> <abhatnagar192...@gmail.com> wrote:
>>
>> >> > Actually..i was wanting to ask whether i should attach them in the
>> >> > email as an attachment..or load it to a repository. I didnt know the
>> >> > path to the repo..thanks for the link.
>>

>> >> > On 8/29/08, Jean Deruelle <jean.derue...@gmail.com> wrote:
>>
>> >> >> What do you mean by share them here only ? do you mean in a private
>> >> >> location
>> >> >> ?
>> >> >> If you want to share them on mobicents-public google group (which is
>> >> >> public and available to anyone), just go there

>> >> >>http://groups.google.com/group/mobicents-public/filesand upload your

>> >> >> files.
>>
>> >> >> Jean
>>
>> >> >> On Fri, Aug 29, 2008 at 3:22 PM, aayush bhatnagar
>> >> >> <abhatnagar192...@gmail.com> wrote:
>>
>> >> >>> I have also made some UML use cases for s-cscf..can i share them here
>> >> >>> only?
>>

>> >> >>>>> <jean.derue...@gmail.com>

>> >> >>>>> wrote:
>>
>> >> >>>>>> I would say for Issue 323 try to identify what is needed and what
>> >> >>>>>> is
>> >> >>>>>> currently missing from Mobicents Sip Servlets(MSS) to become an IMS
>> >> >>>>>> compliant SIP Application Server. What can be done is to try to use
>> >> >>>>>> MSS as a SIP AS along with Open IMS core
>> >> >>>>>> (http://www.openimscore.org/)
>> >> >>>>>> and maybe document the process.
>>
>> >> >>>>>> I guess for Issue 324, that would be implementing one or several
>> >> >>>>>> sip
>> >> >>>>>> servlets applications that will acts as CSCFs. In this issue the
>> >> >>>>>> HSS,
>> >> >>>>>> I-CSCF and S-CSCF node can only be implemented once we have
>> >> >>>>>> Diameter
>> >> >>>>>> support which will come soon through Issue 119.
>>
>> >> >>>>>> Vladimir may be able to comment more on this too.
>>
>> >> >>>>>> Best regards
>> >> >>>>>> Jean
>>

>> >> >>>>>> On Thu, Aug 21, 2008 at 11:29 AM, Vicky Kak <vicky....@gmail.com>

>> >> >>>>>> wrote:
>> >> >>>>>> > Where to start from ?
>>
>> >> >>>>>> > On Thu, Aug 21, 2008 at 2:50 PM, Jean Deruelle

>> >> >>>>>> > <jean.derue...@gmail.com>

>> >> >>>>>> > wrote:
>>
>> >> >>>>>> >> We are planning to add IMS interoperability and features to
>> >> >>>>>> >> Mobicents
>> >> >>>>>> >> Sip Servlets.
>> >> >>>>>> >> See Issues
>> >> >>>>>> >>http://code.google.com/p/mobicents/issues/detail?id=323
>> >> >>>>>> >> and
>> >> >>>>>> >>http://code.google.com/p/mobicents/issues/detail?id=324
>> >> >>>>>> >> If anyone is interested, has ideas, etc feel free to chime in
>> >> >>>>>> >> and we
>> >> >>>>>> >> welcome and are eager for any contributions ; we will make our
>> >> >>>>>> >> best
>> >> >>>>>> >> to
>> >> >>>>>> >> help you in the process.
>>
>> >> >>>>>> >> Thanks in advance
>> >> >>>>>> >> Best regards
>> >> >>>>>> >> Jean Deruelle
>>

>> >> >>>>>> >> On Fri, Aug 8, 2008 at 1:22 PM, Vicky <Vicky....@gmail.com>

[aayush bhatnagar]

Hi Jean,

An new open source IMS HSS initiative: http://code.google.com/p/hss

HSS modules breakup : http://www.3gdb.org/doc/

:) 

Aayush 

[Vicky Kak]

Well I looked at this earlier, it is erlang based HSS implementation.

Vicky

[aayush bhatnagar]

yep. 

Somehow the project owner has not been active on the mail hosting platform (google), but has shifted everything elsewhere. 

thats odd for an open source project. 

enjoy the weekend ! 

[Eduardo Martins]

Once Diameter Sh Server RA I'm thinking on an Mobicents HSS, and provide the possibility of integration with the XDM Server in same Mobicent JAIN SLEE Server, thus having all user data control logic in SLEE and sharing the same datasource, how does that sounds?

[aayush bhatnagar]

Hi ! 

Integrating the XDMS with the HSS ? I dont get the motivation for such an integration...maybe you can explain further :) 

Is it proposed to polarize data maintenance at just one location, or is there a special IMS service that has called for such an integration?

Best Regards

Aayush 

[Eduardo Martins]

The motivation would be to share same (high availability, fault tolerant, whatever) back-end data source, and keep the control logic in JAIN SLEE. This would also mean, that apps running on same JAIN SLEE container could skip sh client interface to get user profile data from HSS, the same for the SIP Presence Service servers, and all future enablers we may implement...

[aayush bhatnagar]

My understanding is, that if the HSS and XDM are co-located on the same SLEE node, then the SIP-AS need not store its metadata in the HSS. 

It can store it directly in the XDM by acting as a XCAP client. The XDM provides more flexibility as far as XML data storage, retrieval, updation and manipulation is concerned which justifies it as an IMS service enabler (the service being hosted at the SIP AS). 

The HSS would simply store the SIP AS related data as transparent repository data. This means, that it will store and return the entire XML document when needed.  

On the other hand, if we define our own app usage in the XDMS, then we get much more data manipulation flexibility than provided by the HSS. We can change/add/delete XML elements, attributes etc. 

Architecturally speaking, such a unified combo will be interesting from a deployment point of view. Usually HSS nodes are deployed as a mated pair solution, with their DBs synchronized. Maybe the same strategy can be followed with the XDM servers too. 

So, unified HSS+XDM node will need to have only 2 interfaces (Cx towards the CSCF) and XCAP/HTTP towards the SIP-AS. Sh will be masked. 

:) 

Aayush

[Eduardo Martins]

The idea is not to change specs, but to have a modular architecture where modules (servers) can be deployed in a single node or not, since not all networks will need to handle a million user base, consider for example, an enterprise environment where a IMS compliant network is deployed to serve 1000 users. All standard interfaces should remain to support: other (remote) SIP ASs in the network;  HSS independent deployment in one node.

[aayush bhatnagar]

Yes. The specs will / should not change. 

In case the HSS is deployed standalone, then the SIP AS has the choice of Sh interface, as well as the XCAP/HTTP interface towards a standalone XDMS for metadata storage.

In an integrated setup of HSS+XDMS, user data can be stored in the XDMS over XCAP, and other information such as a list of pulic identities of the user, registration state of the user, charging platform information, location information, S-CSCF name can be retrieved over the Sh interface. Sh interface provides provisions for getting such data. 

Otherwise, it is not mandatory for every SIP AS to implement Sh interface (as per the specs). It is implemented only if required by the business logic of the service.

[Vicky Kak]

I have been trying to install the opencoreims, the instructions are over here
http://www.openimscore.org/installation_guide

I am not able to make the ser_ims ie
calling this command fails
********************************************************************************************
-bash-3.2# pwd
/opt/OpenIMSCore/ser_ims
-bash-3.2# make install-libs all
Makefile.defs:268: Unknown compiler gcc\; supported compilers: gcc, sun cc, intel icc
Makefile.defs:598: You are using an old and unsupported gcc version  (unknown), compile at your own risk!
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
ccache: failed to create /root/.ccache (No such file or directory)
make -C lib -f Makefile.ser install
make[1]: Entering directory `/opt/OpenIMSCore/ser_ims/lib'
Making install in binrpc
make[2]: Entering directory `/opt/OpenIMSCore/ser_ims/lib/binrpc'
gcc    -DNAME='"ser"' -DVERSION='"2.1.0-dev1 OpenIMSCore"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"unknown"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DDBG_QM_MALLOC -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -ggdb  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -DSER -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -Wall -g0 -O9 -fPIC  -I/opt/OpenIMSCore/ser_ims/lib -I/opt/OpenIMSCore/ser_ims/lib/.. -c binrpc_api.c
ccache: failed to create /root/.ccache (No such file or directory)
make[2]: *** [binrpc_api.o] Error 1
make[2]: Leaving directory `/opt/OpenIMSCore/ser_ims/lib/binrpc'
make[1]: [binrpc] Error 2 (ignored)
Making install in cds
make[2]: Entering directory `/opt/OpenIMSCore/ser_ims/lib/cds'
gcc    -DNAME='"ser"' -DVERSION='"2.1.0-dev1 OpenIMSCore"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"unknown"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DDBG_QM_MALLOC -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -ggdb  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -DSER -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -Wall  -I/opt/OpenIMSCore/ser_ims/lib -I/opt/OpenIMSCore/ser_ims/lib/.. -c cds.c
ccache: failed to create /root/.ccache (No such file or directory)
make[2]: *** [cds.o] Error 1
make[2]: Leaving directory `/opt/OpenIMSCore/ser_ims/lib/cds'
make[1]: [cds] Error 2 (ignored)
Making install in xcap
make[2]: Entering directory `/opt/OpenIMSCore/ser_ims/lib/xcap'
gcc    -DNAME='"ser"' -DVERSION='"2.1.0-dev1 OpenIMSCore"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"unknown"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DDBG_QM_MALLOC -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -ggdb  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -DSER -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -Wall  -I/opt/OpenIMSCore/ser_ims/lib -I/opt/OpenIMSCore/ser_ims/lib/.. -I/usr/include/libxml2 -c common_policy.c
ccache: failed to create /root/.ccache (No such file or directory)
make[2]: *** [common_policy.o] Error 1
make[2]: Leaving directory `/opt/OpenIMSCore/ser_ims/lib/xcap'
make[1]: [xcap] Error 2 (ignored)
Making install in presence
make[2]: Entering directory `/opt/OpenIMSCore/ser_ims/lib/presence'
gcc    -DNAME='"ser"' -DVERSION='"2.1.0-dev1 OpenIMSCore"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"unknown"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DDBG_QM_MALLOC -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -ggdb  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -DSER -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -Wall -Wall  -I/opt/OpenIMSCore/ser_ims/lib -I/opt/OpenIMSCore/ser_ims/lib/.. -I/usr/include/libxml2 -c domain_maintainer.c
ccache: failed to create /root/.ccache (No such file or directory)
make[2]: *** [domain_maintainer.o] Error 1
make[2]: Leaving directory `/opt/OpenIMSCore/ser_ims/lib/presence'
make[1]: [presence] Error 2 (ignored)
make[1]: Leaving directory `/opt/OpenIMSCore/ser_ims/lib'
gcc -g -O9 -funroll-loops -Wcast-align -Wall     -DNAME='"ser"' -DVERSION='"2.1.0-dev1 OpenIMSCore"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"unknown"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM  -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DDBG_QM_MALLOC -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -ggdb  -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024  -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -c action.c -o action.o
ccache: failed to create /root/.ccache (No such file or directory)
make: *** [action.o] Error 1
-bash-3.2# pwd
/opt/OpenIMSCore/ser_ims
********************************************************************************************

Had anyone over here tried to build/run the p-i-s CSCF nodes successfully before ?

Vicky

[Jean Deruelle]

it seems your c compiler (gcc) is badly defined in your environment. See the error messages in your log

Makefile.defs:268: Unknown compiler gcc\; supported compilers: gcc, sun cc, intel icc
Makefile.defs:598: You are using an old and unsupported gcc version  (unknown), compile at your own risk!

[Vicky Kak]

Thanks Jean, I suspected the same but wanted to confirm it from people over here .
I hate this C stuff ;(

Vicky