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]> 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 > <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 >>> <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 >>> <https://github.com/Metaswitch/sprout> >>> 2. Fork the repo: generic instructions here >>> https://gist.github.com/Chaser324/ce0505fbed06b947d962 >>> <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 >>> <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 >>>> >>>> <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 >>> >>> <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
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
