Terminating Requests - Registered User
When the Oracle Communications Core Session Manager receives an Initial request, it is validated as a terminating request towards a registered user when the following conditions are met:
- When the
ignore-psu-sesscase option is not set:
- The request is a dialog creating request or a standalone request.
- There is no "orig" parameter in the top route of the request.
- There is no "odi" parameter in the top route of the request.
- The regstate and sescase parameters of the P-served-user indicate for this to be treated as terminating request for a registered user OR the request is finished with originating services if applicable and the request is destined to a user who is currently registered with the Oracle Communications Core Session Manager.
- If the Request-URI changes when visiting an application server, the Oracle Communications Core Session Manager terminates the checking of filter criteria and routes the request based on the changed value of the Request-URI, per 3GPP Specification TS 23.218.
- When the
ignore-psu-sesscase option is set:
- The request is a dialog creating request or a standalone request.
- There is no "odi" parameter in the top route of the request.
- There is no "orig" parameter in the top route of the request.
- The served user is registered