Just for completeness, while Project Clearwater does not support the Rx interface to EPC, in our VoLTE Solution we replace the Bono P-CSCF with our proprietary Perimeta product (https://www.metaswitch.com/perimeta-session-border-controller-sbc) - it is this that provides the Rx interface in that solution.
Matt From: Clearwater [mailto:[email protected]] On Behalf Of Afriyie Abraham Kwabena Sent: 22 September 2017 10:52 To: [email protected] Subject: Re: [Project Clearwater] clearwater Installation using source code -- Help Matt, Thank you for this important information. Very good to know that Clearwater does not support Rx interface to EPC. BR Abraham Sent from my iPhone On 22 Sep 2017, at 12.31, Matt Williams <[email protected]<mailto:[email protected]>> wrote: Abraham, Just to check, I think you're looking to create a basic VoLTE deployment: · an IMS core consisting of P-CSCF, I-CSCF, S-CSCF and HSS (no IR.92 TAS, but that's probably OK) · an EPC · the IMS core communicating with o the UE (via the EPC) over the (SIP) Gm interface for call signaling o the EPC via the (Diameter) Rx interface for QoS control? Am I right in suggesting that you want to use Rx to control the EPC to set up the dedicated bearers? (That would be the standard way.) If so, unfortunately, Project Clearwater doesn't currently support the Rx interface to the EPC. I don't believe OpenIMSCore does, either. We'd be happy if you wanted to make this enhancement, but I suspect it's quite a big undertaking! Metaswitch, the company that developed Clearwater (and for which I work) does have a VoLTE Solution (https://www.metaswitch.com/voice-over-lte-volte-and-voice-over-wifi-vowifi-solution) that supports the Rx interface, but this uses proprietary components which aren't part of open-source Project Clearwater. I hope that helps! Matt From: Clearwater [mailto:[email protected]] On Behalf Of Jim Page Sent: 21 September 2017 14:51 To: [email protected]<mailto:[email protected]> Subject: Re: [Project Clearwater] clearwater Installation using source code -- Help Yes you have to have some DNS set up. Details are in the documentation. You need to have more than just A records to get this working properly … so yes really you need to have DNS set up. I have no idea what the parameters are though at a guess I would say that your home domain is everything to the right of the @ in your sip URIs, and the homestead cluster is the host name or IP address of the machine running homestead (dime, in my case). But that’s why I suggested actually running the binaries slightly differently; once you have installed the working system you can just create links from where the init scripts expect the production binaries to be to point to your built binaries. It’s quite an assignment. If I were you I would consider using openimscore instead of clearwater. It looks easier to build from source and I can see QOS is something that has been discussed on their forums. You might also want to look at this: http://ieeexplore.ieee.org/document/5532766/?reload=true The EPC I can’t help you with. Good luck! RedMatter Ltd Jim Page VP Mobile Services +44 (0)333 150 1666 +44 (0)7870 361412 [email protected]<mailto:[email protected]> On 21 Sep 2017, at 14:32, Afriyie Abraham Kwabena <[email protected]<mailto:[email protected]>> wrote: As part of my school special assignment, i have install an EPC and need to connect it to an IMS such that a dedicated bearer is created with a specific QoS for clearwater traffic or a call session. This is my task. However as you suggested, it would have been better to go the VM way but am not required to do that, am ask to install using the source code and also have to install the components on a single machine which is very hard. BTW, I have tried to build Sprout and bono, link: https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md but running the following command hang on my terminal, how to ./MIBS="" LD_LIBRARY_PATH=usr/lib:$LD_LIBRARY_PATH build/bin/sprout -t --domain=<Home Domain> --hss=<Homestead cluster> Also what would be the parameter for the - - hss=<Homestead cluster> ? Do i need to have a DNS installed to handle the domain name for all the components? BR Abraham On 21 Sep 2017, at 16:00, Jim Page <[email protected]<mailto:[email protected]>> wrote: If you have to run it on a single machine built from source, I guess your best option is to start here http://clearwater.readthedocs.io/en/stable/Manual_Install.html and just use a single host instead of 6. I guess it must be possible to some degree otherwise it wouldn’t be possible to create an all-in-one image. But you are making life hard for yourself by not going down the VM route. I would do the same thing however - install clearwater using production packages using apt-get, then once you have it working, selectively rebuild the component you want to change. I am not sure what you want to achieve by adding QOS to clearwater. I don’t see what relevance QOS has where the only service you have running is VOIP. QOS is only useful if you want to prioritise one type of traffic over another, and is only relevant where you have different types of traffic trying to get access to a limited resource such as an MPLS line or a broadband line, in which case you set the QOS up in the router that sends traffic down that line. What is it exactly that you are trying to do? RedMatter Ltd Jim Page VP Mobile Services +44 (0)333 150 1666 +44 (0)7870 361412 [email protected]<mailto:[email protected]> On 21 Sep 2017, at 13:47, Afriyie Abraham Kwabena <[email protected]<mailto:[email protected]>> wrote: Hi, My task is to install all the components of Clearwater on the same machine (ubuntu 14.04). In your explanation it means I need to have different hosts for each component but that is not my plan. Is it possible to install all components without using docker or any virtualization platform. Also for QoS, which component do you suggest I should modify. Sorry I may be asking basics, am newbie. BR Abraham Sent from my iPhone On 21 Sep 2017, at 15.17, Jim Page <[email protected]<mailto:[email protected]>> wrote: My recommendation (as a newbie) is to build a working release version of clearwater first, using these installation instructions: http://clearwater.readthedocs.io/en/stable/Installation_Instructions.html Once you have a basic working install, decide what component you want to rebuild, and build it on the host for that component. In my case I did this with sprout: 1. go to https://github.com/Metaswitch/sprout 2. Fork the repo: generic instructions here https://gist.github.com/Chaser324/ce0505fbed06b947d962 3. Carefully read README.md 4. go here for build instructions https://github.com/Metaswitch/sprout/blob/dev/docs/Development.md 5. Fork the repo and clone the forked repo on your local sprout host. Create a feature branch if you intend to push your changes back to clearwater. 6. Modify the sprout source as you see fit, and build sprout following the instructions in Development.md 7. When the build is complete, replace /usr/share/clearwater/bin/sprout and /sur/share/clearwater/sprout/plugins/*.so with links to your development builds in <your build dir>/sprout/build/bin. 8. ’sudo system sprout restart’ - now you are running a fully working clearwater setup with your own sprout build (assuming you have not broken sprout with your changes!). Hope this helps Cheers Jim RedMatter Ltd Jim Page VP Mobile Services +44 (0)333 150 1666 +44 (0)7870 361412 [email protected]<mailto:[email protected]> On 21 Sep 2017, at 11:59, Afriyie Abraham <[email protected]<mailto:[email protected]>> wrote: Hi, I have tried installing clearwater using the source code following the procedure in the documentation but not working. My main aim is to be able to have a device to device call session through my EPC connecting the IMS(clearwater). Also i would like to add some QoS parameters to for every call session. plan: UE ——————EPC ——————IMS Please can anyone help me with a working source code procedure to install clearwater on ubuntu 14.04. Thanks in advance. BR Abraham _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org _______________________________________________ Clearwater mailing list [email protected]<mailto:[email protected]> http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
