Last updated on JULY 24, 2015
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
This article will aim to explain how Oracle Communications Network Charging and Control (NCC) E.164 Number Mapping (ENUM) handles failed servers.
It is observed that when multiple Domain Name System servers are configured in the enca.enumCallOut.servers section of the enca.conf file (in /IN/service_packages/etc), that ENUM requests are load-balanced across the configured servers. However if any server goes offline, requests are still being sent to it resulting in those calls not getting a valid ENUM responses.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms