Hi Kamal,
On Tue, Oct 11, 2011 at 4:09 PM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote:
Hello Carsten, Jason and Klaus,
Thank you for this nice discussion, it's good to know others motivations
:).
I am very new to this project, and am starting my master thesis
project that is too close to what you do, my project is about
interconnecting IMS users and H.248 users
'interconnecting' - what do you mean by this? I would imagine this is a
simple gateway function so I'm not quite sure to what extent you want to
interconnect? maybe you can elaborate?
, for the H.248 part am
working on SmallMGC "http://www.smallmgc.org/" and for the IMS side am
trying to use SIP Router, if I succeed to use SmallMGC as a module to
SIP Router I would be able to get SIP Router top act as an AGCF and
I don't think SR/Kamailio is the correct place to build a gateway. For a
University POC, maybe, but I would imagine it would be far better to build
it as a separate AGCF entity with an IMS stack (possibly something like
doubango - very good IMS stack IMO).
that is the main goal of my project.
I tried to install SIP Router from the IMS branch but
I got some bugs,
may be I should wait for the release of the 3.2 version?
3.2 won't make a diff for IMS extensions, however, we are now really close
to putting in another branch with the latest stuff we are doing with
kamailio and IMS. Just give us a few more days.
or can I have
access to the source of the version used in ng-voice -
http://www.ng-voice.com/our-solution/installation/ ??
Best regards
Kamal
On Tue, Apr 26, 2011 at 1:38 PM, Carsten Bock <carsten(a)ng-voice.com>
wrote:
Hi Klaus,
My Motivation for the IMS branch is, that i actually like the idea of
IMS.
Currently, at Telefonica/O2 in Germany (without
HanseNet, who will
follow later), we have about ~27% of our cusomters already using IMS
as a fixed-line replacement, in a "normal" VoIP-Provider scenario. The
number growing daily, we have scheduled to reach 100% at the end of
Q2. At the moment we have no mobile integration yet, that will follow
in Q3/Q4 2011 together with the LTE roll-out.
We also have several resellers on the Telefonica-IMS platform, using
similar scenarios. Probably somewhen we might even migrate our Class 4
infrastructure towards an IMS solution... At Telefonica we use the
Ericsson IMS platform, unfortunately no Kamailio and no Open-Source. I
believe, Kamailio and Open-Source IMS were too late for Telefonica.
There are no efforts made from my employer "Telefonica" to implement
IMS in Kamailio (except from donating my time working on it, when
there is nothing else to do).
"Status quo" for me: For me there is no commercial motivation for
making the move towards IMS (yet), except from propagating open-source
and bringing Kamailio forward.
Kind regards,
Carsten
2011/4/21 Klaus Darilion <klaus.mailinglists(a)pernau.at>at>:
Hi!
Carsten, Jason, I wonder what is the main motivation for you to have IMS
components?
Are you using Kamailio in an mobile operator environment and thus have
to support all the IMS interfaces, or do you plan to use those modules
also in "normal" VoIP provider scenarios (benefits?)
Thanks
Klaus
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Carsten Bock
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Schomburgstr. 80
22767 Hamburg
Germany
Mobile +49 179 2021244
Office +49 40 34927219
Fax +49 40 34927220
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev