Hi Pamal,<div><br></div><div>I have put an sample pcscf.cfg in examples directory for you.</div><div><br></div><div>comments inline:<br><br><div class="gmail_quote">On Thu, Nov 3, 2011 at 12:57 PM, kamal koubaa <span dir="ltr"><<a href="mailto:kamal.koubaa@gmail.com">kamal.koubaa@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hey Jason,<br>
Thanks for these valuable information, I've got the point, and it's<br>
indeed interesting. But I suppose that, in this case you'll need to<br>
provide users with documentations that shows what are the building<br>
blocks and how to configure them to get to a specific CSCF. For my<br>
case this is quite interesting and challenging at the same time.<br>
Interesting because am going to need to build some special IMS agents<br>
that interact directly with I-S-CSCF through the Mw interface, they<br>
act like a P-CSCF but they are not really P-CSCF.<br></blockquote><div><br></div><div>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.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Challenging because I'll have to do that inside a module that I may<br>
call AGCF, so that I have to call some P-CSCF function from that<br>
module, and that won't be done through a config file. </blockquote><div><br></div><div>There is no reason why the Mw interface module can't have an API for that exact reason.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
the IMS agents<br>
that are part of the AGCF module would do registration of H.248 users<br>
on behalf of the MGC. If I manage to do that, it would become possible<br>
to do PSTN/ISDN emulation, as describe in :<br>
<br>
<a href="http://www.etsi.org/deliver/etsi_ts/182000.../ts_182012v020104p.pdf" target="_blank">www.etsi.org/deliver/etsi_ts/182000.../ts_182012v020104p.pdf</a></blockquote><div><br></div><div>wow - great!!! Please let us know how it goes and if we can help in any way!</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
page 11.<br>
<br>
<br>
Chears,<br>
<span class="HOEnZb"><font color="#888888">Kamal<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Thu, Nov 3, 2011 at 11:08 AM, Jason Penton <<a href="mailto:jason.penton@gmail.com">jason.penton@gmail.com</a>> wrote:<br>
> Hey Kamal,<br>
> The idea behind the new design is that there will not be 1 module for PCSCF,<br>
> 1 for SCSF, 1 for ICSCF, etc. Instead the individual logical components that<br>
> make up functionality of a PCSCF is released as a module. So effectively,<br>
> you can build a P/S/I CSCF based purely on config file and the appropriate<br>
> functions/modules you require. For example, if you want a PCSCF to do PCC,<br>
> you will load the diameter_rx module and call Rx_AAR before you setup a call<br>
> (on_reply route block getting RTP). The diameter_rx module we have released<br>
> will apply for QoS from PCRF and monitor the dialog (using dialog2) and tear<br>
> it down should QoS disappear, etc, etc.<br>
> This will allow us to re-use functionality where necessary across the<br>
> modules, as opposed to the way it is now where functionality is replicated<br>
> in all 3 modules. It also makes it a heck of a lot easier to manage the<br>
> bite-size chunks of functionality in their individual modules.<br>
> Hope that makes sense.<br>
> p.s. this will most likely be quite a long task and we are def. still in<br>
> alpha stage so don't expect thing to be rock solid just yet. maybe another<br>
> few iterations on the code released so far, but with help from you and<br>
> others we could progress quite quickly<br>
> Cheers<br>
> Jason<br>
><br>
><br>
> On Thu, Nov 3, 2011 at 11:59 AM, kamal koubaa <<a href="mailto:kamal.koubaa@gmail.com">kamal.koubaa@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hi,<br>
>> Great !!!, I'll wait for that, is the built P-CSCF will be of the new<br>
>> design or the old one, because I see no pcscf module in your branch?<br>
>><br>
>> Thanks a lot,<br>
>> Kamal<br>
>><br>
>> On Thu, Nov 3, 2011 at 10:54 AM, Jason Penton <<a href="mailto:jason.penton@gmail.com">jason.penton@gmail.com</a>><br>
>> wrote:<br>
>> > Hi Kamal,<br>
>> > Yes it should work. I am just busy with something else at the moment,<br>
>> > but I<br>
>> > will attach a pcscf example cfg file before the end of the day (GMT+2)<br>
>> > ;)<br>
>> > It will be great to get your feedback on your testing! ;)<br>
>> > Cheers<br>
>> > Jason<br>
>> > On Thu, Nov 3, 2011 at 11:37 AM, kamal koubaa <<a href="mailto:kamal.koubaa@gmail.com">kamal.koubaa@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi Jason,<br>
>> >><br>
>> >> Is it possible at this point to build a working P-CSCF using the<br>
>> >> source on your branche ?.<br>
>> >> If so you have a working config file for that, I would like to use it<br>
>> >> to access an I/S-CSCF in an existing IMS core. If the actual code<br>
>> >> could do that, it would help a lot.<br>
>> >><br>
>> >> Regards,<br>
>> >> Kamal<br>
>> >><br>
>> >> _______________________________________________<br>
>> >> sr-dev mailing list<br>
>> >> <a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
>> >> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > sr-dev mailing list<br>
>> > <a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
>> > <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> sr-dev mailing list<br>
>> <a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
>> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> sr-dev mailing list<br>
> <a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
> <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev</a><br>
</div></div></blockquote></div><br></div>