My Oracle Support Banner

Defining Multiple SipScheme For AvpCodes Mapping In DCA Configuration (Doc ID 2997352.1)

Last updated on JANUARY 15, 2024

Applies to:

Oracle Communications Network Charging and Control - Version and later
Information in this document applies to any platform.


In Diameter Control Agent (DCA) eserv.config to read Attributes Value-Pair (AVP) 2035 with "tel" sipScheme (example value - tel:+40123456789) and map to inapField, it is working fine and DCA is correctly mapping value to profile tag.

Problem - In some scenarios AVP 2035 in Credit-Control Request (CCR) - request is received in "SIP" sipScheme format (example -, DCA unable to decode as the configuration defined for this AVP as tel format and value mapped is in encoded format, below is the CLI value received in ACS log.



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.