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
Hi Klaus,
I work for a company called Smile Communications based in Johannesburg, South Africa (although legally registered in Mauritius) and we are a startup mobile comms company focussing on providing low cost voice and messaging services to underserved (bottom of the pyramid) customers across Africa. We have spectrum and operator licenses in Uganda, Tanzania, Nigeria & DRC thus far and are trying to acquire more as we go along. We launched in Uganda 18 months ago by rolling out our own Wimax network and fixed-wireless wimax/voip phones. We are now looking at rolling out in our other licensed countries. We built an entire voice/messaging stack integrating over 40 different open source projects using an SOA methodology.
We have now decided that with the slow uptake of Wimax voice handsets (in fact, no uptake :( ) we will now roll out LTE in our spectrum instead. This necessitates us to move our architecture from something slightly proprietary (although it is all based on SIP) to obey the IMS/VoLTE specifications.
Following our previous approach, we want to build the end to end IMS/OSS/BSS architecture in as cost effective manner as possible. We live by the motto that our customers make a decision to either eat lunch or make a phone call with the money they have at any given time - we want to make our calls as affordable as possible and hence keep our Capex and Opex costs as low as possible. We also want to have great flexibility and be able to make changes quickly without needing to call on product vendors.
At the same time our motto is provide back to the community - hence us publishing all the stuff we are going to do SR ;)
Cheers Jason
On Thu, Apr 21, 2011 at 4:41 PM, Klaus Darilion < klaus.mailinglists@pernau.at> 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@pernau.at:
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, 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 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? 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@ng-voice.com wrote:
Hi Kamal,
On Tue, Oct 11, 2011 at 4:09 PM, kamal koubaa kamal.koubaa@gmail.comwrote:
'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?
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.
On Tue, Oct 11, 2011 at 4:49 PM, Jason Penton jason.penton@gmail.com wrote:
I mean, interconnecting signaling messages, basically take h.248 message parse and get information needed to build sip messages and the other way around
I don't have to touch anything in the gateways development, it's just about signaling between h.248 and ims user, gateway comtrollers and ims core.
AGCF works much like MGCF, while MGCF take PSTN/ISDN signaling the sip/ims world, AGCF do that for h.248/megaco. No gateway will be built. I attached a schema of the AGCF architecture.
alright I'm waiting for it. Thanks for the answer and the great work you are doing,
Regards kamal
Hi Carsten, sorry my attached file exceeded the size limit. On Tue, Oct 11, 2011 at 6:02 PM, kamal koubaa kamal.koubaa@gmail.com wrote:
I mean, interconnecting signaling messages, basically take h.248 message parse and get information needed to build sip messages and the other way around
I don't have to touch anything in the gateways development, it's just about signaling between h.248 and ims user, gateway comtrollers and ims core.
AGCF works much like MGCF, while MGCF take PSTN/ISDN signaling the sip/ims world, AGCF do that for h.248/megaco. No gateway will be built. I attached a schema of the AGCF architecture.
alright I'm waiting for it. Thanks for the answer and the great work you are doing,
Regards kamal
-
Carsten Bock -
Jason Penton -
kamal koubaa -
Klaus Darilion