NetaxisNetaxisNetaxisNetaxis
  • Home
  • Solutions
    • Cisco BroadWorks Provisioning
    • Smart Routing
    • Microsoft Teams
    • Number Portability
  • Products
    • APIO – API Orchestrator
    • SRE-Session Routing Engine
    • Nemo – Network Monitoring
    • Engo – Fraud Management System
    • SIGMA – Centralized Call Generator
  • Services
    • Support Services
    • Engineering Services
  • Partners
  • Blog
  • Netaxis Academy
    • SIP Essentials
    • Oracle SBC Essentials and Basic Configuration
    • SIGMA multi-purpose call simulator
    • SRE Session Routing Engine
    • Nemo network monitoring
  • About Us
  • Jobs
  • Contact

Why moving to Netaxis APIO can bring more value than just replacing Loki or UCEP portals

    Home Loki replacement Why moving to Netaxis APIO can bring more value than just replacing Loki or UCEP portals
    NextPrevious
    apio based UC architecture

    Why moving to Netaxis APIO can bring more value than just replacing Loki or UCEP portals

    By Tref Davies | Loki replacement | 0 comment | 21 April, 2020 | 0

    Build a workflow using APIO as a replacement for Loki provisioning portal in Cisco BroadWorks UC

    It’s been a busy time at Netaxis. Very busy with lovely customers wanting our help with their Cisco BroadWorks Unified Communications projects. BroadWorks is the swiss army knife of UC platforms: extremely powerful yet complex to operate and integrate. One of the major challenges our customers have is finding the right balance between automation  and offering enough flexibility to their customers. At Netaxis we strongly believe in customer empowerment. Giving your customers all capabilities to manage their own environment will allow you to limit your integration efforts while giving your customers a maximum in flexibility.

    However, a UC ecosystem is complex containing many elements – how do you integrate all those elements? And what is a Loki portal or replacement if it just touches one box of the entire solution?

    This problem is the main reason (see our first blogpost about LOKI replacement) why Netaxis decided to fully rebuild our legacy, monolithic portal application and move to an API first design. By moving all business logic into a flexible API driven backend, we dramatically simplify the task of integrating 3rd party systems that sit close to Broadworks. Examples of these are Session Border Controllers, IMS networks and call recording platforms or perhaps internal environments such as real-time or offline charging systems, data warehouses and other entities in a Service Provider network.

    For third party integrations APIO offers 2 different integration strategies:

    1) Webhooks: inform a third party application about any change that happens through APIO. Prefect for loose coupling of both environments.

    2) Our workflow engine: allows you to define new API endpoints and overwrite existing endpoints through our UI. The business logic can be created through our service creation environment. This solution is perfect when you need to do proper rollback management etc.

    Webhooks

    Webhooks are hot these days. Tools such as IFTT or Zapier fully employ webhooks. If your Slack channels are spammed with useless notification about updates in a  document on google drive that’s thanks to webhooks. You want to auto-deploy your application when new code is pushed to your main branch of your code? Think webhooks! Most probably webhooks allow you to automate almost anything, maybe except combing your hair, but for the unfortunate ones amongst us, this might be pointless anyway. 

    Webhooks are “user-defined HTTP callbacks”. They are usually triggered by some event, such as pushing code to a repository or a comment being posted to a blog. In the case of BroadWorks maybe your application wants to be notified about a user creation, deletion or update? Well, no problem.

    Let’s just define that event:

    webhooks create user

    Now just subscribe your webservice to the event:

    subscribe to webserviceYour webservice will get notified each time a user is created. If that’s not simple what is?

    selfcare_portal

    Workflow engine

    When simple is not good enough, you’re ready to take for the next step. Meet our workflow engine. Our workflow engine is a task engine able to orchestrate API calls across platforms. You can overwrite the business logic of existing API’s or just create entirely new APIs. 

    Where do we start? As an example take this simple “Hello World” response and build your first custom API.

    Build your first workflow

    Give your workflow a name

    new workflow

    Every workflow needs a name to be used as a reference in further operations.

    Be polite and say hello

    To make our workflow polite we want to make it return “Hello, world” in its body response.

    Add a task to set the response:new task

    The task is designed to return our message which needs to be a valid JSON body.say hello

    End the workflow

    Another cell is added to mark the end of the workflowend

    Organise the cells

    Now that you have created the tasks they can be dragged to wherever is visually convenient. Cells are then linked together to organise transitions from “start” to “end” by using a mouse drag & drop any output* to any input**

    * outputs are bullet on the right of the tasks
    ** inputs are bullets on the left of the tasks

    compose hello world

    Save your hard work

    save hello world

    Now we have a workflow but it’s not exposed or available to anyone to run it.

    Create an HTTP endpoint

    To configure the HTTP endpoints, go to the “Startup events” page

    startup events

    Then create a new custom route (1) which needs a path (2) and a HTTP method (3) – note the final path to help you share your future endpoint.

    Our workflow is expected to return its response in a synchronous manner therefore the tick box is checked (4) and the configuration saved (5).

    new route

    Bind your workflow

    The brand new workflow can now be associated with the new route just created.

    link hello route

    You are all set and all users authenticated on the platform can trigger your workflow

    Trigger your workflow

    The new endpoint can be triggered from any HTTP client and a example is provided here of a call from cURL:

    curl -H "Authorization: Bearer <user token>" \
        http://<host>/api/v01/custom/hello
    

    And the platform returns:

    {"message": "hello, world"}
    

    Follow your trace

    Calls can be retrieved in the “custom requests” menu (1) including call details and its execution going to the details page (2).

    custom requests

    Conclusion

    So that’s it. A taste of what you will find when working with Netaxis. Get in touch for a demo and access our brand new APIO lab when looking for an replacement for Loki in Cisco Broadworks. The drag and drop UI makes it a lot easier to generate new workflows and you will be up and running in double quick time.

    Read the rest of our blog posts on the use of APIO as a replacement for the Loki portal in Cisco Broadworks platforms. As usual my partner in crime Bart Coelmont and the Netaxis team have been instrumental in helping me with this blog post.

    APIO, Broadworks, Loki replacement
    Tref Davies

    Tref Davies

    More posts by Tref Davies

    Related Post

    • advised way of working with Broadworks

      APIO for Broadworks – integration made easy

      By Tref Davies | 0 comment

      APIO for Broadworks – integration made easy  How does APIO relate to Cisco Broadworks APIO is a mediation layer between network elements such as the Cisco Broadworks platform and Northbound resources that include a customerRead more

    • APIO Loki replacement shortlisted for ITSPA awards

      Netaxis APIO is finalist in 3 prestigious ITSPA Awards

      By Tref Davies | 0 comment

      Netaxis APIO is finalist in 3 prestigious ITSPA Awards Netaxis APIO has made it to the shortlist for 3 ITSPA Awards: Best Software, Best Infrastructure Solution and Best Innovation.  APIO is hot property right nowRead more

    • Using APIO as a Loki Replacement

      By Tref Davies | 0 comment

      Use of APIO as a Loki replacement This post discusses the use of Netaxis APIO as a replacement for the Cisco Broadwords Loki provisioning platform. Cisco Broadworks Cisco Broadworks is a SIP based voice andRead more

    • Tref is on the floor

      By Jean-Sébastien Decubber | 0 comment

      UK MD Trefor Davies discusses the Netaxis API Orchestrator with UC Today at the Cavell Cloud Comms Summit Great interview with Tref at Cloud Comms Summit 2020! He is talking about how our very ownRead more

    • pool party at Broadsoft Connections Miami

      Broadsoft Connections Miami wrapup

      By Tref Davies | 0 comment

      Broadsoft Connections Miami wrapup By Trefor Davies and Bart Coelmont Big vendor events such as Broadsoft Connections are truly worth attending. Not necessarily for the content – at American events everything is “awesome”, “great” orRead more

    NextPrevious

    Recent Posts

    • Netaxis ranked amongst fastest growing companies in Belgium
    • Netaxis Session Routing Engine – Simple Automation
    • Simplify Automate Accelerate
    • Netaxis Sponsor Cavell Cloud Comms Summit #CCSEurope21
    • Automated number portability extended to four countries

    Archives

    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • October 2020
    • July 2020
    • May 2020
    • April 2020
    • March 2020
    • October 2019
    • September 2019
    • May 2019
    • April 2019
    • March 2019
    • January 2019
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • October 2017
    • August 2017
    • July 2017

    Categories

    • Blog
    • Events
    • Loki replacement
    • News
    • Uncategorized

    Tag Cloud

    APIO Audiocodes Barcelona Broadworks Cavell cloud Comms Summit CCA Cisco CLI presentation Cloud Communications Alliance Direct Routing Engo Event Fraud IPRN ITSPA ITSPA Awards Loki replacement marketing Microsoft Microsoft Teams Mobile Nemo Number Portability Ofcom SBC self care portal Session Routing Engine Sigma SIP SIP call generator SRE STIR/SHAKEN Teams training

    Social Channels

    Keep updated through our social channels. We'll be covering various topics regarding the impact of Artificial Intelligence on our daily lives and in specific how we do business.

    Slider

    Netaxis HQ

    Netaxis Headquarters
    Rue du Trone 60
    1050 Brussels
    Belgium
    VAT : BE0828790071

    Email Address
    info@netaxis.be

    Recent Posts

    • Netaxis ranked amongst fastest growing companies in Belgium

      Netaxis listed as one of Belgium’s fastest growing companies for second year

      1 March, 2021
    • Netaxis Session Routing Engine – Simple Automation

      SIMPLICITY and AUTOMATION support FUSE2’s ACCELERATING business Fuse2 Communications are a long

      1 March, 2021

    Categories

    • Blog
    • Events
    • Loki replacement
    • News
    • Uncategorized
    • Home
    • Solutions
      • Cisco BroadWorks Provisioning
      • Smart Routing
      • Microsoft Teams
      • Number Portability
    • Products
      • APIO – API Orchestrator
      • SRE-Session Routing Engine
      • Nemo – Network Monitoring
      • Engo – Fraud Management System
      • SIGMA – Centralized Call Generator
    • Services
      • Support Services
      • Engineering Services
    • Partners
    • Blog
    • Netaxis Academy
      • SIP Essentials
      • Oracle SBC Essentials and Basic Configuration
      • SIGMA multi-purpose call simulator
      • SRE Session Routing Engine
      • Nemo network monitoring
    • About Us
    • Jobs
    • Contact
    Copyright 2017 Netaxis | All Rights Reserved
    • Home
    • Solutions
      • Cisco BroadWorks Provisioning
      • Smart Routing
      • Microsoft Teams
      • Number Portability
    • Products
      • APIO – API Orchestrator
      • SRE-Session Routing Engine
      • Nemo – Network Monitoring
      • Engo – Fraud Management System
      • SIGMA – Centralized Call Generator
    • Services
      • Support Services
      • Engineering Services
    • Partners
    • Blog
    • Netaxis Academy
      • SIP Essentials
      • Oracle SBC Essentials and Basic Configuration
      • SIGMA multi-purpose call simulator
      • SRE Session Routing Engine
      • Nemo network monitoring
    • About Us
    • Jobs
    • Contact
    Netaxis