My Oracle Support Banner

ApplicationRouter Routing And Sip.xml Request Based Filtering Not Working Together (Doc ID 1190593.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Communications Converged Application Server - Version 4.0.0 and later
Information in this document applies to any platform.

Goal

Trying to deploy two HTTP/SIP converged applications into Oracle Communications Converged Application Server (OCCAS) 4.0 server but having issues as both applications must be invoked by the incoming INVITE requests. The separating condition must be a unique request header user part (request.to.uri.user) which identifies the called number in our IVR system. Both numbers are routed to application server. Frankly, the last application deployed takes all the incoming requests giving nothing to other.



Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.