Known Issues

Table 3-1 Services

Known Issue	Impact Statement and Mitigation
Potential Voice Service Overcharges	Impact Statement—Customers run the risk of being overcharged in their Voice Service SIP trunk configuration. Although toggling bursting multiple times in an hourly window can cause the overcharge sometimes, it is not known to be the only cause for overcharging. Mitigation—As a partial solution, Oracle recommends disabling bursting for all SIP trunk configurations until this risk is resolved in a subsequent release.
Required Format for Service Names	Impact Statement—Certain names for Services can cause the network diagram to misalign so that you cannot see the Services in the diagram. Mitigation—Use underscores instead of spaces when creating Service names. For example: Use ICON_Service_ABC instead of ICON Service ABC. Do not use words followed by a number. For example, use Testing_Sandbox_One instead of Testing Sandbox_1
Unique Username Required for Authentication with SIP Termination	Impact Statement—When adding a Service and selecting Authentication as the SIP Termination Method, the UI displays an additional configuration form. The form requires you to enter a username and password. If you enter a username that already exists in Oracle Intelligent Communication Orchestration Network, the Service automatically transitions to the inactive state. Mitigation—To ensure successful activation, you must provide a unique username that does not conflict with existing entries in the Oracle Intelligent Communication Orchestration Network.
Carrier Service Classless Inter-Domain Routing (CIDR) Requirement	Impact Statement—Services become inactive with improperly formatted Classless Inter-Domain Routing (CIDR) entries in the Access Control List. When you add an IP address in the ACL field while adding the Service, you must define the CIDR using the first IP address of the network. If you use any other IP within the sub net as the base for CIDR, Oracle Intelligent Communication Orchestration Network returns an error. Mitigation—Format the CIDR with an IP address followed by the number of network address prefix bits after the slash. For example: 192.168.1.0/32. Provide the IP address in CIDR format. Begin the CIDR with the network's first address. Example: Use `192.168.12.0/24` instead of `192.168.12.1/24` Do not use a CIDR such as 12.13.14/32, which does not contain four Octets.
Unexpected UI Behavior When Selecting a Voice Service Card	Impact Statement—When you select a Voice Service card, the UI should remove all the others and show only the selected card. Although the system highlights the selected card, all the other Service cards remain displayed, Mitigation—
Incorrect Hint in the SIP Termination Field Help	Impact Statement—The hint Help in the SIP Termination field incorrectly says to use "bcid" instead of "bcld". The issue applies only when you are manually entering the text. It is not an issue when you copy and paste the text. Mitigation—Use "bcld" instead of "bcid".
Carrier Service Connection Error Message	Impact statement—When you create a Carrier Service during the configuration of another Voice or SIP Service, the process may initially appear unsuccessful. Note that the Carrier Service might have been created in the background without your knowledge. After you see the error message, you might attempt to create the Carrier Service again resulting in duplicate Carrier Services. For example, two instances of the same Carrier Service. Mitigation—Check the Services page after you create the first Carrier Service to confirm the Service was added.
Cannot Group NICE CXone Mpower	Impact Statement— The group functionality for Services is currently not available for the NICE CXone Mpower Service. You cannot add or manage the NICE CXone Mpower within a Service group, which limits the ability to group and manage it with other Services in the platform. Mitigation—None, but you can still use the NICE CXone Mpower Service separately (not in a group) with no restriction on managing the Service.

Table 3-2 Numbers

Known Issue	Impact Statement and Mitigation
The System Erases the Outbound CLI Number	Impact Statement—When you save a Number block in Edit mode, the system erases the default Outbound CLI field. Mitigation—Reenter the Outbound CLI phone number.
Import Phone Numbers is Not Supported in 25.1.0	Impact Statement—Importing Phone Numbers from a CSV file is not supported in 25.1.0. When you attempt to import numbers from a CSV file, the system displays an internal server error. Mitigation—Enter phone numbers manually.
Number Block Size Defaults to 1	Impact Statement—When editing the Block Size field for mobile, the field defaults to 1 when you click Save, no matter which size block you select. Mitigation—None.
The Hosting Carrier You Want is Not Listed in the Drop-Down List	Impact Statement—In the Adding Numbers procedure, the Hosting Carrier you want might not be listed in the Hosting Carrier drop-down list. Mitigation—If the Hosting Carrier you want is not listed, contact Oracle Support about adding the carrier.
Cannot Add the Same Number to Another Country Code	Impact Statement—The system does not allow you to add the same number to more than one country code. For example, Suppose you already added +1 9822992276. Then you try to add +61 9822992276. The system does not allow you to add the +61 entry because it specifies the same number as the +1 entry. Mitigation—None.
SIP Calls Allowed on Paused Number Blocks	When a number block is in the Paused state in a Service, SIP calls are still allowed to and from that number block as long as the associated Service remains active. If suitable, remove the number block from the Service or Pause the Service.

Table 3-3 Sites

Known Issue	Impact Statement and Mitigation
Incorrect Automatic Address Population	Impact Statement—When you create a Site and enter a partial address in the Address field to search, the system may return multiple similar results. When you select one, the system sometimes chooses a different address than the one you selected and populates the Address fields with that address. For example, if you search for “12 Easthill” in the United States, the system displays ten results in different states. You select the result in New York State, but the system populates the Address fields with the address in Virginia. Mitigation—Manually enter the entire address.
Unsuccessful Results When Deleting a Site	Impact Statement—The system is designed so that you can delete a Site when no number blocks are assigned to the Site. In the scenario where you deleted a split number block, the system will not let you delete the Site. Deleting a sub-block corrupts the entire block. Mitigation—You must merge the number block back into its original size before deleting it. Deleting only a sub-block will corrupt the entire number block.
A New Site Is Not Displayed on the Sites Map	Impact Statement—After you add a Site, the location marker on the Sites map is not immediately visible on the map. Mitigation—Refresh the Sites page from the browser.
Incorrect Address Parsing for Non-English Addresses	Impact Statement— The required Street Type field does not recognize non-English street types. Mitigation—Enter the closest English approximation. The Street Type does not affect the map location.

Table 3-4 Accounts

Known Issue	Impact Statement and Mitigation
The Country You Want is Not Listed in the Accounts Configuration Drop-Down List	Impact Statement—In the Add Accounts procedure, the drop-down list for Country might not include the country you want. Mitigation—If the country you want is not listed, contact Oracle Support about adding the country.
Customer ID is Not Displayed in the Edit Account Details Drawer	Impact Statement—The Edit Account Details drawer displays Managed Service Partner's account ID, rather than the Enterprise's ID. Mitigation—On the Dashboard landing page, customer account details including customer id is visible, hence customer id information can be sourced from here.
Customer and Partner Account Names Must Be Unique	Impact Statement—The Customer Name field is defined as unique, meaning no two accounts can share the same name. When a Managed Service Provider licensee adds an account by way of the Accounts dashboard and the account name already exists in the system, the operation will not complete. When an Enterprise or Managed Service Provider licensee is onboarded through the Oracle Ordering System with a name that already exists in the system, the operation will not complete. Mitigation— Ensure that every account name is unique. Avoid using special characters or spaces in the account name. Use only alphabets (A–Z, a–z) and numbers (0–9).

Known Issue

Impact Statement and Mitigation

The Country You Want is Not Listed in the Accounts Configuration Drop-Down List

Impact Statement—In the Add Accounts procedure, the drop-down list for Country might not include the country you want.

Mitigation—If the country you want is not listed, contact Oracle Support about adding the country.

Customer ID is Not Displayed in the Edit Account Details Drawer

Impact Statement—The Edit Account Details drawer displays Managed Service Partner's account ID, rather than the Enterprise's ID.

Mitigation—On the Dashboard landing page, customer account details including customer id is visible, hence customer id information can be sourced from here.

Customer and Partner Account Names Must Be Unique

Impact Statement—The Customer Name field is defined as unique, meaning no two accounts can share the same name.

When a Managed Service Provider licensee adds an account by way of the Accounts dashboard and the account name already exists in the system, the operation will not complete.
When an Enterprise or Managed Service Provider licensee is onboarded through the Oracle Ordering System with a name that already exists in the system, the operation will not complete.

Mitigation—

Ensure that every account name is unique.
Avoid using special characters or spaces in the account name.
Use only alphabets (A–Z, a–z) and numbers (0–9).

3 Known Issues