3 Known Issues

Known Issues contain descriptions of the issues and workarounds, when available. Check this document periodically to stay informed of updates and other new information.

The following Known Issues exist in this release.

Table 3-1 Services

Known Issue Impact Statement and Workaround
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 Communications Orchestration Network, the Service automatically transitions to the inactive state.

Workaround—To ensure successful activation, you must provide a unique username that does not conflict with existing entries in the Oracle Intelligent Communications 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 Communications Orchestration Network returns an error.

Workaround—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.
  • Only use a CIDR with four octets.
  • Example: Use
    192.168.12.0/24
    instead of
    192.168.12.1/24
Unable to Create A Service Group When You Select "Carriage Services"

Impact Statement—Currently, for users who have only the Voice Gateway SKU, Oracle Intelligent Communications Orchestration Network does not allow creating a service group when you select Carriage Services.

Workaround—None.

Zoom Phone Service and NICE CX Service Get Charged for Suspended Accounts

Impact Statement—The Zoom Phone Service and NICE CX Service continue to incur charges for suspended accounts, while other services are not charged, leading to inconsistent and incorrect billing behavior. This applies to Enterprise Customers and Managed Service Providers.

Workaround—None.

Voice Bot Goes to Paused State After Adding Number Blocks.

When you add a number block to an existing Voice Bot, the Voice Bot may intermittently transition to the Paused state with no apparent way to resume the Active state. Sometimes, the Voice Bot remains paused indefinitely. Until the Voice Bot becomes active again, avoid adding any more number blocks.

Workaround—Raise a Service Request when a Voice Bot remains in the Paused state.

Table 3-2 Numbers

Known Issue Impact Statement and Workaround
Number Block Size Defaults to 1

Impact Statement—When configuring the Block Size for Mobile, the field defaults to 1 when you click Save, no matter which block size you selected.

Workaround—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.

Workaround—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 block to a different dial code. For example, suppose you previously added +1 98222992276. 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. The same behavior occurs when uploading numbers by way of the .csv file.

Workaround—None.

Table 3-3 Sites

Known Issue Impact Statement and Workaround
The Country You Want is Not Listed in the Accounts Configuration Drop-Down List

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

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

Incorrect Address Parsing for Non-English Addresses

Impact Statement— The required Street Type field does not recognize non-English street types.

Workaround—Enter the closest English approximation. The Street Type does not affect the map location.

Table 3-4 Accounts

Known Issue Impact Statement and Workaround
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.

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

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.

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

Incorrect Address Parsing for Non-English Addresses

Impact Statement— The required Street Type field does not recognize non-English street types.

Workaround—Enter the closest English approximation. The Street Type does not affect the map location.

Billing Includes Suspended Period Usage After Account Reactivation

Impact Statement—After account reactivation suspension, billing includes usage from the suspended period, resulting in customers being charged inaccurately.

Workaround—None.

Table 3-5 User Interface

Known Issue Impact Statement and Workaround
Sluggish UI Response

Impact Statement—Some behaviors such as initially loading the landing page, displaying View Configuration, and reloading the landing page upon return may take longer than expected for large configurations.

Workaround—None.

The User Interface Does Not Show Concurrent Calls Accurately

Impact Statement—When the configured channel count is significantly higher than the actual number of concurrent calls (for example, 6000 configured channels versus 10 active calls), the User Interface does not accurately display concurrent call usage. In such a scenario, the system may determine that the small number of calls is insignificant and does not report the actual numbers.

Workaround—None.