Hello, the IMS modules will not be packaged in the 3.2.0, they stay for the moment in a separate branch. The developers working on them didn't finish the development to all those modules to be ready for complete release. I guess they will make it to 3.3.0. However, if you get some errors during compilation, you can paste them here and some developers may be able to assist you or fix the problems themselves if it is the case. Cheers, Daniel On 10/13/11 6:54 PM, alexis.marcou(a)orange.com wrote: -- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda

Hi guys, To fix the std IMS extenstions, simply remove the Client_Ro module from Carsten's. This is a module we wrote which we gave to Carsten a while back. It requires some internals of the dialog module to be exposed via the API, like get_dlg, un/ref, etc. We are busy re-writing the Ro module based on a new dialog module that we have written. We are planning to start pushing all of our changes to a separate branch early next week. However, in the meantime, it would probably be best to simply remove Client_Ro from Carsten's branch and use his branch. Our branch will be *very* different from the std. openimscore code. We set out to re-use existing functionality of the Kamailio platform, for example, dialog, usrloc, registrar, etc. So effectively, our branch will not be what you are used to, but would welcome testers and developers alike to jump into the branch once we push it, and hopefully we can get everything in before 3.3.0 :D I don't think there will be much use for people to use our Client_Ro just yet anyway as you will need an OCS (online charging server), which is not part of the openimscore, so removing it from Carsten's branch to compile wont cost you any openimscore-specific functionality. Hope this helps Cheers Jason On Thu, Oct 13, 2011 at 11:54 PM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote:

Hi Kamal, Yes there are changes. For example, there is no such module called pcscf anymore ;). We have effectively broken IMS functionality into smaller building blocks, like: diameter_rx (this is the PCRF Policy control interface to the PCC) - used to be in pcscf.so diameter_cxdx (module which would be used by an I/SCSCF - for talking to HSS) - used to be in pcscf.so/scscf.so/icscf.so diameter_rx (online charging module for realtime billing) These modules can then be loaded and used from withing the config file, so based on your config you can make your kamailio into a P/S/I CSCF depending on what you want to do. The old pcscf stores dialog, contacts, registrar, pcc sessions, etc. These are now instead using existing functionality in std kamailio modules like registrar, usrloc, dialog, etc So to answer you question, yes it will look very different! We hope that this will help us better integrate IMS extensions into standard kamailio without duplicating functionality already there. Cheers Jason On Fri, Oct 14, 2011 at 10:13 AM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote:

Hi Kamal, Yes it should work. I am just busy with something else at the moment, but I will attach a pcscf example cfg file before the end of the day (GMT+2) ;) It will be great to get your feedback on your testing! ;) Cheers Jason On Thu, Nov 3, 2011 at 11:37 AM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote:

Hey Kamal, The idea behind the new design is that there will not be 1 module for PCSCF, 1 for SCSF, 1 for ICSCF, etc. Instead the individual logical components that make up functionality of a PCSCF is released as a module. So effectively, you can build a P/S/I CSCF based purely on config file and the appropriate functions/modules you require. For example, if you want a PCSCF to do PCC, you will load the diameter_rx module and call Rx_AAR before you setup a call (on_reply route block getting RTP). The diameter_rx module we have released will apply for QoS from PCRF and monitor the dialog (using dialog2) and tear it down should QoS disappear, etc, etc. This will allow us to re-use functionality where necessary across the modules, as opposed to the way it is now where functionality is replicated in all 3 modules. It also makes it a heck of a lot easier to manage the bite-size chunks of functionality in their individual modules. Hope that makes sense. p.s. this will most likely be quite a long task and we are def. still in alpha stage so don't expect thing to be rock solid just yet. maybe another few iterations on the code released so far, but with help from you and others we could progress quite quickly Cheers Jason On Thu, Nov 3, 2011 at 11:59 AM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote:

Hi Pamal, I have put an sample pcscf.cfg in examples directory for you. comments inline: On Thu, Nov 3, 2011 at 12:57 PM, kamal koubaa <kamal.koubaa(a)gmail.com>wrote;wrote: This is perfect in this case. I would envisage Mw interface module that you could use in any configuration, not necessarily a PCSCF type configuration. There is no reason why the Mw interface module can't have an API for that exact reason. wow - great!!! Please let us know how it goes and if we can help in any way!

Hello Jason, I've got some problems while trying to use your pcscf.cfg config. 1st : There was ims.h file included in some diameter related modules : "cxdx, rx", I commented to includes of ims.h, because it doesn't exist. 2nd: the compilation goes will, but when starting kamailio, like this $./kamailio -f pcscf.cfg start //after adapting pcscf.cfg I get 9 errors in the config file, and they come from loading cdp module loading modules under /usr/local/kamailio-ims/lib64/kamailio/modules:/usr/local/kamailio-ims/lib64/kamailio/modules_k:/usr/local/kamailio-ims/lib64/kamailio/modules_s 0(29262) ERROR: <core> [sr_module.c:565]: ERROR: load_module: could not open module </usr/local/kamailio-ims/lib64/kamailio/modules/cdp.so>: /usr/local/kamailio-ims/lib64/kamailio/modules/cdp.so: undefined symbol: memlog 0(29262) : <core> [cfg.y:3501]: parse error in config file /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg, line 51, column 12-19: failed to load module. looks like there is no reference to memlog. I commented to parts where memlog is used then I got the same error, this time for sem_post function from semaphore.h. Do you have any idea what could be the problem ?? Thanks Kamal On Fri, Nov 4, 2011 at 6:27 PM, kamal koubaa &lt;kamal.koubaa(a)gmail.com&gt; wrote:

Hi Jason, Now am trying to run to pcscf without diameter, I don't need it for the moment anyway, but still don't know why sem_post is not linked properly. Cheers, kamal On Tue, Nov 8, 2011 at 1:04 PM, Jason Penton &lt;jason.penton(a)gmail.com&gt; wrote:

Hey Jason, It fails to load the cdp module, and says : "undefined symbol: memlog" and when I remove parts related to momlog variable, an other errors rises : "undefined symbol: sem_post" I tested sem_post function from semaphore.h, it works fine, but not recognized in the CDP module. These are the Errors I get : bash-4.1$ sudo ./kamailio -f /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg restart loading modules under /usr/local/kamailio-ims/lib64/kamailio/modules:/usr/local/kamailio-ims/lib64/kamailio/modules_k:/usr/local/kamailio-ims/lib64/kamailio/modules_s 0(10918) ERROR: <core> [sr_module.c:565]: ERROR: load_module: could not open module </usr/local/kamailio-ims/lib64/kamailio/modules/cdp.so>: /usr/local/kamailio-ims/lib64/kamailio/modules/cdp.so: undefined symbol: memlog 0(10918) : <core> [cfg.y:3501]: parse error in config file /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg, line 51, column 12-19: failed to load module 0(10918) ERROR: <core> [sr_module.c:565]: ERROR: load_module: could not open module </usr/local/kamailio-ims/lib64/kamailio/modules/cdp_avp.so>: /usr/local/kamailio-ims/lib64/kamailio/modules/cdp_avp.so: undefined symbol: cdp 0(10918) : <core> [cfg.y:3501]: parse error in config file /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg, line 52, column 12-23: failed to load module 0(10918) ERROR: <core> [sr_module.c:565]: ERROR: load_module: could not open module </usr/local/kamailio-ims/lib64/kamailio/modules/diameter_rx.so>: /usr/local/kamailio-ims/lib64/kamailio/modules/diameter_rx.so: undefined symbol: load_cdp_avp_api 0(10918) : <core> [cfg.y:3501]: parse error in config file /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg, line 55, column 12-27: failed to load module 0(10918) ERROR: <core> [modparam.c:162]: set_mod_param_regex: No module matching <diameter_rx> found 0(10918) : <core> [cfg.y:3504]: parse error in config file /usr/local/kamailio-ims/etc/kamailio/pcscf.cfg, line 84, column 53: Can't set module parameter ERROR: bad config file (4 errors)