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.

  • Unique Username Required for Authentication with SIP Termination - 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 cloud service, 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 cloud service.
  • 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), but Oracle® 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.
  • Number Block Size Defaults to 1 - When configuring the Block Size for Mobile, the field defaults to 1 when you click Save, no matter which block size you selected.
  • Incorrect Address Parsing for Non-English Addresses - 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.
  • Customer ID is Not Displayed in the Edit Account Details Drawer - 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.
  • Sluggish UI Response - 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.
  • Private Interconnect Virtual Connection Stuck in “Processing” After Account Resume - After suspending and resuming an active sub-account with private interconnect enabled, one of the private interconnect virtual connections may remain in a processing state in the interconnect table, even though the account resume completes successfully.
  • SIPREC Metadata Format Not Applied - When configuring a generic SIP trunk service with a generic SIPREC integration, selecting Ribbon or AudioCodes as the metadata format does not take effect. The SIPREC signaling continues to use the RFC standard metadata format regardless of the selected option.
  • SIPREC X-Headers Dynamic Variables Not Supported - In the SIPREC integration configuration, the note in the "Custom SIP headers" screen indicates that X-Headers parameters can include dynamic variables derived from the call. However, dynamic variables in X-Headers are not currently supported, and the resulting SIPREC signaling does not reflect the expected substituted values.
  • Associated Interconnect Service field under Connection Route - The Associated Interconnect Service field under Connection Route for Carrier and Generic SIP Service is currently not supported; ignore this field until further notice.