Fwd: [OpenIMSCore-CSCF] About my "carstenbock/ims" branch on the sip-router.org GIT repository
Hi,
I will simply forward this question... I would suppose to put it somewhere at the Kamailio SVN for 1.5?
Carsten
---------- Forwarded message ---------- From: Jason Penton jason.penton@gmail.com Date: 2011/4/5 Subject: Re: [OpenIMSCore-CSCF] About my "carstenbock/ims" branch on the sip-router.org GIT repository To: Carsten Bock carsten@ng-voice.com Cc: openimscore-cscf@lists.berlios.de
Hey Carsten, Right now I am doing something similar, but rather with kamailio-1.5.5. I have not migrated to SR yet and dont intend to anytime soon. Right now I have ported CDP, CDP_AVP, and ICSCF and they are running. My reason is that I don't quite 'trust' sr2 just yet - and I'm not sure I like the mix and match of ser and kamailio modules - anyway a discussion probably already discussed and not for this thread. I'd be happy to put a 1.5.5 version up somewhere that everyone could use? what do you suggest? Cheers Jason
On Tue, Apr 5, 2011 at 12:30 PM, Carsten Bock carsten@ng-voice.com wrote:
Hi everyone,
i just wanted to notice, that i am actually working on re-integrating the OpenIMS-core into the sip-router.org/Kamailio project. It is not a fork of the official OpenIMSCore project, but more a merge of the OpenIMScore Project into the Kamailio/sip-router.org project.
As a first step, i've made all the CSCF modules compile and work with a current Kamailio source. In order to do this, only minor adaptions were required.
As a second step, i am working on a better integration into the existing structures of the Kamailio project; i want to achieve the following things:
- replace integrated dialog awareness of the CSCF modules with
Kamailio's dialog module
- replcae integrated registrar of the CSCF modules with Kamailio's
registrar module
- replace integrated nathelper support with the sip-router.org
nathelper/rtpproxy moduels
- replcae integrated RFC 3680 support with Kamailio's
Presence/Presence-User-Agent modules
- add documentation in accordance with the other sip-router.org modules
I've already changed quite a few things in the Kamailio core, in order to achieve this: K's dialog module is now able to store additional data to a dialog (works great), K's usrloc/registrar module is able to store additional information to an contact (still buggy) and i have already added support for RFC 3680 to Kamailio's presence/pua infrastructure (when you register, the system will "PUBLISH" the registration state; another system may already "SUBSCRIBE" to the status and "NOTIFY" requests are already parsed (but not stored yet)). So it is going on. I have also already modified some of the config to use generic append_hf() and remove_hf() functions instead of custom implemented functions...
The progress is slow but steady since i work on it apart from my regular work. I try to publish any new developments on this on my blog/homepage (www.ng-voice.com), where you may also find some more information about the installation and the components of the project (i provide a repository of the last step for easy installation).
I started implementing an own HSS some time ago (openhss.org), but the development on this currently stopped. First, i do not have enough time to work on both the Kamailio integration, regular work and the HSS; second the main developer on the HSS (Brian) just resigned due to health reasons.
Some of you may have noticed, that i am working for Telefonica in Germany as a regular work. I am working on the Class 4/5 infrastructure at Telefonica and we have already implemented an Ericsson IMS core. However, i wanted to mention, that neither Telefonica nor O2 is behind this project. The only support i get from Telefonica is, that i get a monthly salary and that i may use some time to work on the OpenIMS-project during normal office-hours (as time allows). If i do things, i do it by heart and not half-hearted... that probably explains a lot of the effort spent on the project.
Kind regards, Carsten
-- 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 _______________________________________________ OpenIMSCore-CSCF mailing list OpenIMSCore-CSCF@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openimscore-cscf
Hello,
On 4/5/11 1:35 PM, Carsten Bock wrote:
Hi,
I will simply forward this question... I would suppose to put it somewhere at the Kamailio SVN for 1.5?
1.5 is no longer maintained officially, just backports by developers that still use it -- which may happen down to 0.9 -- but no new features.
Personally I would prefer to go only with one IMS extensions integration, based on current development branch (git master). Besides the fact that joining forces will make things move forward faster, having two directions for same thing (one within very old branch) will confuse people a lot. Maybe Jason will consider trying 3.1.x and we can try removing his doubts about this version when he has specific questions about what he does not trust.
I strongly think this is the best at this moment, there is already confusion with duplicated modules coming from kamailio and ser, creating a new development branch based on 1.5 will confuse even more. We are working to remove duplicated, thus remove confusion, and we should go only in this direction if we want to finish it soon.
Now regarding the trust of 3.x, I can say that 3.1.x is far more better than 1.5. In 1.x one could barely use tcp or tls, the tm module had some potential races which couldn't be handled without a major refurbishment. That happened in 3.x - if one search the recent archive, there were crashes reported to 1.5 rather than to 3.1.
If one does not like the mix of kamailio and ser modules, then just ignore the modules_s/* for a while and you are set. Installing kamailio from packages take care of that and only kamailio modules are installed (modules/* and modules_k/*). AFAIK, the openimscore developers are working also with 3.x so future code from them will just work on latest version of our project.
Cheers, Daniel
Carsten
---------- Forwarded message ---------- From: Jason Pentonjason.penton@gmail.com Date: 2011/4/5 Subject: Re: [OpenIMSCore-CSCF] About my "carstenbock/ims" branch on the sip-router.org GIT repository To: Carsten Bockcarsten@ng-voice.com Cc: openimscore-cscf@lists.berlios.de
Hey Carsten, Right now I am doing something similar, but rather with kamailio-1.5.5. I have not migrated to SR yet and dont intend to anytime soon. Right now I have ported CDP, CDP_AVP, and ICSCF and they are running. My reason is that I don't quite 'trust' sr2 just yet - and I'm not sure I like the mix and match of ser and kamailio modules - anyway a discussion probably already discussed and not for this thread. I'd be happy to put a 1.5.5 version up somewhere that everyone could use? what do you suggest? Cheers Jason
On Tue, Apr 5, 2011 at 12:30 PM, Carsten Bockcarsten@ng-voice.com wrote:
Hi everyone,
i just wanted to notice, that i am actually working on re-integrating the OpenIMS-core into the sip-router.org/Kamailio project. It is not a fork of the official OpenIMSCore project, but more a merge of the OpenIMScore Project into the Kamailio/sip-router.org project.
As a first step, i've made all the CSCF modules compile and work with a current Kamailio source. In order to do this, only minor adaptions were required.
As a second step, i am working on a better integration into the existing structures of the Kamailio project; i want to achieve the following things:
- replace integrated dialog awareness of the CSCF modules with
Kamailio's dialog module
- replcae integrated registrar of the CSCF modules with Kamailio's
registrar module
- replace integrated nathelper support with the sip-router.org
nathelper/rtpproxy moduels
- replcae integrated RFC 3680 support with Kamailio's
Presence/Presence-User-Agent modules
- add documentation in accordance with the other sip-router.org modules
I've already changed quite a few things in the Kamailio core, in order to achieve this: K's dialog module is now able to store additional data to a dialog (works great), K's usrloc/registrar module is able to store additional information to an contact (still buggy) and i have already added support for RFC 3680 to Kamailio's presence/pua infrastructure (when you register, the system will "PUBLISH" the registration state; another system may already "SUBSCRIBE" to the status and "NOTIFY" requests are already parsed (but not stored yet)). So it is going on. I have also already modified some of the config to use generic append_hf() and remove_hf() functions instead of custom implemented functions...
The progress is slow but steady since i work on it apart from my regular work. I try to publish any new developments on this on my blog/homepage (www.ng-voice.com), where you may also find some more information about the installation and the components of the project (i provide a repository of the last step for easy installation).
I started implementing an own HSS some time ago (openhss.org), but the development on this currently stopped. First, i do not have enough time to work on both the Kamailio integration, regular work and the HSS; second the main developer on the HSS (Brian) just resigned due to health reasons.
Some of you may have noticed, that i am working for Telefonica in Germany as a regular work. I am working on the Class 4/5 infrastructure at Telefonica and we have already implemented an Ericsson IMS core. However, i wanted to mention, that neither Telefonica nor O2 is behind this project. The only support i get from Telefonica is, that i get a monthly salary and that i may use some time to work on the OpenIMS-project during normal office-hours (as time allows). If i do things, i do it by heart and not half-hearted... that probably explains a lot of the effort spent on the project.
Kind regards, Carsten
-- 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 _______________________________________________ OpenIMSCore-CSCF mailing list OpenIMSCore-CSCF@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openimscore-cscf
Hey,
On 05.04.2011 13:35, Carsten Bock wrote:
I will simply forward this question... I would suppose to put it somewhere at the Kamailio SVN for 1.5?
Glad there are more people interested in backporting your code to 1.5 -- we would certainly take part in that effort as we need it as well.
However, I'm not sure if the SVN repository is the right spot to be, at least not the trunk branch which is feature-closed. A separate branch might be more appropriate; then again, I hate SVN's merging capabilities and would much rather use git for that.
Feeling hard to make up my mind on this one. Let's hear what others have to say.
Cheers,
--Timo
---------- Forwarded message ---------- From: Jason Penton jason.penton@gmail.com Date: 2011/4/5 Subject: Re: [OpenIMSCore-CSCF] About my "carstenbock/ims" branch on the sip-router.org GIT repository To: Carsten Bock carsten@ng-voice.com Cc: openimscore-cscf@lists.berlios.de
Hey Carsten, Right now I am doing something similar, but rather with kamailio-1.5.5. I have not migrated to SR yet and dont intend to anytime soon. Right now I have ported CDP, CDP_AVP, and ICSCF and they are running. My reason is that I don't quite 'trust' sr2 just yet - and I'm not sure I like the mix and match of ser and kamailio modules - anyway a discussion probably already discussed and not for this thread. I'd be happy to put a 1.5.5 version up somewhere that everyone could use? what do you suggest? Cheers Jason
On Tue, Apr 5, 2011 at 12:30 PM, Carsten Bock carsten@ng-voice.com wrote:
Hi everyone,
i just wanted to notice, that i am actually working on re-integrating the OpenIMS-core into the sip-router.org/Kamailio project. It is not a fork of the official OpenIMSCore project, but more a merge of the OpenIMScore Project into the Kamailio/sip-router.org project.
As a first step, i've made all the CSCF modules compile and work with a current Kamailio source. In order to do this, only minor adaptions were required.
As a second step, i am working on a better integration into the existing structures of the Kamailio project; i want to achieve the following things:
- replace integrated dialog awareness of the CSCF modules with
Kamailio's dialog module
- replcae integrated registrar of the CSCF modules with Kamailio's
registrar module
- replace integrated nathelper support with the sip-router.org
nathelper/rtpproxy moduels
- replcae integrated RFC 3680 support with Kamailio's
Presence/Presence-User-Agent modules
- add documentation in accordance with the other sip-router.org modules
I've already changed quite a few things in the Kamailio core, in order to achieve this: K's dialog module is now able to store additional data to a dialog (works great), K's usrloc/registrar module is able to store additional information to an contact (still buggy) and i have already added support for RFC 3680 to Kamailio's presence/pua infrastructure (when you register, the system will "PUBLISH" the registration state; another system may already "SUBSCRIBE" to the status and "NOTIFY" requests are already parsed (but not stored yet)). So it is going on. I have also already modified some of the config to use generic append_hf() and remove_hf() functions instead of custom implemented functions...
The progress is slow but steady since i work on it apart from my regular work. I try to publish any new developments on this on my blog/homepage (www.ng-voice.com), where you may also find some more information about the installation and the components of the project (i provide a repository of the last step for easy installation).
I started implementing an own HSS some time ago (openhss.org), but the development on this currently stopped. First, i do not have enough time to work on both the Kamailio integration, regular work and the HSS; second the main developer on the HSS (Brian) just resigned due to health reasons.
Some of you may have noticed, that i am working for Telefonica in Germany as a regular work. I am working on the Class 4/5 infrastructure at Telefonica and we have already implemented an Ericsson IMS core. However, i wanted to mention, that neither Telefonica nor O2 is behind this project. The only support i get from Telefonica is, that i get a monthly salary and that i may use some time to work on the OpenIMS-project during normal office-hours (as time allows). If i do things, i do it by heart and not half-hearted... that probably explains a lot of the effort spent on the project.
Kind regards, Carsten
-
Carsten Bock -
Daniel-Constantin Mierla -
Juha Heinanen -
Timo Reimann