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.
|
| 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. |
| Unsuccessful Zoom Calls | Attempting to establish Zoom calls secured with Secure Real-Time Transport Protocol (SRTP), results in unsuccessful calls. The carrier sends SIP SDP with RTP-SAVP (SRTP), butOracle® Intelligent Communications Orchestration Network cloud service responds with SDP containing RTP-AVP (unencrypted RTP). The mismatch in media encryption negotiation prevents successful SRTP call setup.
Workaround—None. |
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. |
| Service Remains in "Processing" State |
Impact Statement—After removing a number block, the service remains in “Processing” even though the block is successfully removed. Customers should open a Service Request (SR) if this occurs, to change the service status to "Active". Workaround—None. |
| Inventory Option Not Available |
Impact Statement— The Inventory option is not available when moving a number block from non-inventory site.Workaround—You can create a site to act as inventory, where you can store all the numbers not in use. |
| Cannot Perform Number Block Operations |
Impact Statement—After removing a number block from a Service, no further number block operations can be performed on existing blocks. Options such as Pause, Split, Merge, and Remove from Service are disabled under More Actions, leaving only Move to Service enabled. 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. |
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. |