Hi all,
I see in the wiki, IMS Module are included in developpement version ?
But, i couldn't find it, in GIT master branch ?
I know, we can find IMS Module in carstenbock/ims branch, but, we have an error during the build.
Alexis
******************************************************************************** IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus.
IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ********************************************************************************
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@orange.com wrote:
Hello all,
Alexis, in an other topic in the mailing list : subject "IMS branch", Jason said they'll release their last work in the few coming days, so we keep waiting.
me too had the same errors when trying to compile kamailio with ims modules, these are the errors : CC (gcc) [M Client_Ro.so] ccr.o CC (gcc) [M Client_Ro.so] diameter_ro.o CC (gcc) [M Client_Ro.so] ims_ro.o ims_ro.c: In function ‘send_ccr_interim’: ims_ro.c:594:42: error: ‘AVP_EPC_User_Equipment_Info_Type_MAC’ undeclared (first use in this function) ims_ro.c:594:42: note: each undeclared identifier is reported only once for each function it appears in ims_ro.c: In function ‘send_ccr_stop’: ims_ro.c:749:42: error: ‘AVP_EPC_User_Equipment_Info_Type_MAC’ undeclared (first use in this function) ims_ro.c: In function ‘Ro_Send_CCR’: ims_ro.c:831:17: error: ‘struct dlg_binds’ has no member named ‘get_dlg’ ims_ro.c:835:15: error: ‘struct dlg_binds’ has no member named ‘unref_dlg’ ims_ro.c:886:42: error: ‘AVP_EPC_User_Equipment_Info_Type_MAC’ undeclared (first use in this function) make[1]: *** [ims_ro.o] Error 1 make: *** [modules] Error 1
From now till getting the new release, I'll try to remove the parts
that generate such errors and see if i can compile it. If you have any other suggestion, it would help a lot.
Thank you guys. Kamal
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@gmail.comwrote:
Hi Jason,
Will the P-CSCF module and its config file be changed a lot from the actual one ? Can you tell us the main changes?
Thanks, With regards Kamal
On Fri, Oct 14, 2011 at 7:42 AM, Jason Penton jason.penton@gmail.com 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@gmail.comwrote:
Hi Jason,
Is it possible at this point to build a working P-CSCF using the source on your branche ?. If so you have a working config file for that, I would like to use it to access an I/S-CSCF in an existing IMS core. If the actual code could do that, it would help a lot.
Regards, Kamal
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@gmail.comwrote:
Hi, Great !!!, I'll wait for that, is the built P-CSCF will be of the new design or the old one, because I see no pcscf module in your branch?
Thanks a lot, Kamal
On Thu, Nov 3, 2011 at 10:54 AM, Jason Penton jason.penton@gmail.com 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@gmail.comwrote:
Hey Jason, Thanks for these valuable information, I've got the point, and it's indeed interesting. But I suppose that, in this case you'll need to provide users with documentations that shows what are the building blocks and how to configure them to get to a specific CSCF. For my case this is quite interesting and challenging at the same time. Interesting because am going to need to build some special IMS agents that interact directly with I-S-CSCF through the Mw interface, they act like a P-CSCF but they are not really P-CSCF. Challenging because I'll have to do that inside a module that I may call AGCF, so that I have to call some P-CSCF function from that module, and that won't be done through a config file. the IMS agents that are part of the AGCF module would do registration of H.248 users on behalf of the MGC. If I manage to do that, it would become possible to do PSTN/ISDN emulation, as describe in :
www.etsi.org/deliver/etsi_ts/182000.../ts_182012v020104p.pdf
page 11.
Chears, Kamal
On Thu, Nov 3, 2011 at 11:08 AM, Jason Penton jason.penton@gmail.com 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@gmail.comwrote:
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!
Hi Jason,
Thank you so much I will try that config file, and let you know about the out come as soon there'll be any.
Regards Kamal
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 kamal.koubaa@gmail.com wrote:
Hi Kamal.
I have just checked in some changes that should fix your probs. Apologies for that - I'm not quite sure how I missed those. Please let me know if you come right?
Cheers Jason
On Tue, Nov 8, 2011 at 1:41 PM, kamal koubaa kamal.koubaa@gmail.com 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 jason.penton@gmail.com wrote:
Hey Kamal,
which module is failing on the link for you? maybe send me a log file.
Cheers Jason
On Tue, Nov 8, 2011 at 2:26 PM, kamal koubaa kamal.koubaa@gmail.com 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)
-
alexis.marcou＠orange.com -
Daniel-Constantin Mierla -
Jason Penton -
kamal koubaa