Application Functions
Application Functions stands for engine instances that implement some specific service logic by consuming APIs published by AEFs through CAPIF-CF. Even though the creation of an application function using the slicce cloud communication engine foundation is rapid and easy, customers can also choose to build their own AFs using any other framework available on the market and using any preferred programming language. The APIs published to the CAPIF-CF do not force the AF developer to use slicce cloud communication engine foundation.
Single Endpoint Application Function
The Single Endpoint Application Function uses a single HTTP Request/Response to implement a service logic in a mid-call trigger. It is extremely easy to add a new service to this application function but the service capabilities are limited to a single mid-call trigger per session. Some examples of services that are pre-integrated in the application function:
Number translation service
Whitelist/blacklisting
Optimal call routing
These services are implemented using the mid-call triggers of the CAP-AEF, INAP-AEF or/and ISC-AEF so the AF can serve circuit switch or packet switch calls or messages on mobile or fixed line networks.
Multi Endpoint Application Function
The Multi Endpoint Application Function uses the one or more entire API set to implement a service. The AF will be triggered by the initial trigger point of the interface it is subscribed to, and it will be responsible for the entire continuity of the call flow until its end. Some examples of services that are pre-integrated in the application function:
Multi-ring
Caller ringback tone
Interactive call screening
Branded calling
These services are implemented using CAP-AEF, INAP-AEF or/and ISC-AEF so the AF can serve circuit switch or packet switch calls or messages on mobile or fixed line networks.