My Oracle Support Banner

IM-SSF CAP3 Ignore GenericNumber Not Generating SIP P-Asserted-Identity Headers In Anonymous Call (Doc ID 2663960.1)

Last updated on MAY 11, 2020

Applies to:

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


IM-SSF CAP3 ignores GenericNumber not generating SIP P-Asserted-Identity headers in anonymous call

User experienced an issue in a specific anonymous scenario call flow.

When OCCAS-SC receives an ingress SIP INVITE with:
 - Request-Line: INVITE tel:+NNNN SIP/2.0
 - From: "anonymous" <sip:anonymous@anonymous.invalid>;tag=a83904b9-3b8d-4908-996e-a00a751a1d7c
 - To: <>
 - no P-Asserted-Identity (PAI) header

in that case, the OCCAS-SC generates the following CAP invoke initialDP:
> calledPartyBCDNumber: NNNNNNNN ---> it matches with SIP 'To' header

and the CAP invoke Connect received contains:
> CalledPartyNumber: NNNNNNNN
> GenericNumber: NNNNNNNN

Finally, the egress SIP INVITE generated by OCCAS-SC contains:
- Request-Line: INVITE tel:+NNNNNNNN SIP/2.0
- From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=xxxxxx
- To: <tel:+NNNNNNNN>
- no PAI header

User expects the OCCAS-SC to generate a PAI header with the content of GenericNumber to identify the calling party. And this is not happening.

Is there any way to do it by OCCAS-SC configuration?


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

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