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(a)pernau.at&gt; 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, 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 &lt;carsten(a)ng-voice.com&gt; wrote:

On Tue, Oct 11, 2011 at 4:49 PM, Jason Penton &lt;jason.penton(a)gmail.com&gt; 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