SIP application router on Liberty
The Session Initiation Protocol (SIP) container uses the SIP application router to select the order in which applications are run within the container.
The SIP container can invoke multiple applications to deploy a complete service or function. This modular and compositional approach makes it easier for application developers to develop new applications. The modular applications can be more easily combined and managed, while individual application implementations remain independent.
The application router is responsible for selecting the correct applications in the correct order to service an incoming message. An application router is required for a container to function, but it is a separate logical entity from the container. The application router is based on the JSR 289 specification. See the specification for more details about the application router function.
The default application router (DAR) can be configured with a standard configuration file, which is supplied to the SIP container as defined in JSR 289.
- Configure a custom application router (CAR) by specifying the path of the Java™ archive (JAR) file that contains the application router implementation and provider to the library element and add the bell element to refer to this library in the server.xml file. A specific provider is defined on the carProvider attribute of the sipApplicationRouter element. For an exmaple see the documentation for Administering Session Initiation Protocol (SIP) on Liberty.
- Configure the DAR by providing its location on the sipDarConfiguration attribute of the sipApplicationRouter element in the server.xml file.