Known Issues in Switchvox 6.3 - 6.4.1.1

----------------------------------------------------------------------------------

At this time, no issues are known to have been introduced in this build. Note that prior issues not identified as Resolved below are expected to persist in this version.

----------------------------------------------------------------------------------

Title: Switchboard may experience intermittent reloads affecting realtime data presented in Queue widgets

DEV Case ID: SWVX-11782

Issue Summary: Switchboard may experience intermittent issues where it loses connection and reloads. This may be accompanied by incorrect reporting of the day's totals for Queue Member Calls Taken and similar metrics as presented in the Switchboard or Queue Status reports. This issue does not affect long-term data, as reported in Queue Reports. When a reload occurs, other related presentation issues may be noticed in Switchboard, such as the calls currently displayed in Queue Calls Waiting widgets will no longer display their wait time. Note, however, that these queue calls will be served as expected. Further, calls which enter queue following the reload event will resume proper wait time display.

First Reported: 4/12/2017

Resolved in Version:  6.4.2 (86124) 

----------------------------------------------------------------------------------

Title: Outbound calling may stop in rare circumstances

DEV Case ID: SWVX-11771, SWVX-11746

Issue Summary: In rare circumstances, outbound calling may stop. Failure of discrete calls do not characterize this issue. Rather, all outbound calling will not resume until a software restart is performed.

First Reported: 3/28/2017

Resolved in Version:  6.7.1 

----------------------------------------------------------------------------------

Title: Call Log entries may show routing To "Unknown <?>" intermittently

DEV Case ID: SWVX-11697

Issue Summary: In rare circumstances, Call Log entries may show routing To "Unknown <?>" intermittently. The root cause for this issue is still being researched. No workaround or other guidance to mitigate is available at this time; however, reported incidences of this issue are very low.

First Reported: 3/22/2017

Resolved in Version:  Unresolved  

----------------------------------------------------------------------------------

Title: Logs may expand to exceed disk threshold in certain configurations

DEV Case ID: SWVX-11751

Issue Summary: If Switchvox is configured to force a user to change their password (or language) on the next login, and the Access Control rules are also setup such that the network the user is logging in from has User API turned off, then as soon as a user with these conditions attempts to login the system a recursive error condition causes the error logs to continue to expand until a configuration change is made to either no longer require the user password change or enable User API on their network. To prevent this issue, make sure users are logging in from an allowed network or re-enable the User API setting for all networks.

First Reported: 3/23/2017

Resolved in Version:  6.4.2 (86124) 

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

At this time, no issues are known to have been introduced in this build. Note that prior issues not identified as Resolved below are expected to persist in this version.

----------------------------------------------------------------------------------

At this time, no issues are known to have been introduced in this build. Note that prior issues not identified as Resolved below are expected to persist in this version.

----------------------------------------------------------------------------------

Title: Special Character appears prepended on Digium phones for outbound calls, and also in Current Calls admin page

DEV Case ID: SWVX-11227, SWVX-11421

Issue Summary: When dialing outbound from a Digium phone a special character may be added to the beginning of the called number on the phone screen. This character is not used in signaling, and will not affect ability to place calls. This issue may also manifest itself as an XML error on the Admin page for Current Calls.

First Reported: 12/13/2016

Resolved in Version:  6.4.2 (86124) 

----------------------------------------------------------------------------------

Title: Unable to add Rapid Dial List status indicator for Parking Lot

DEV Case ID: SWVX-11364

Issue Summary: When attempting to Add Status Indicator for a Parking Lot the Creating Status indicator will hang and never save.

First Reported: 1/4/2017

Resolved in Version:  6.3.5 (84192) 

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

Title: Certain types of transfers via My Calls widget result in an error causing call logs to be empty

DEV Case ID: SWVX-11143

Issue Summary: Specific transfer activities using My Calls widget result in an error that will cause subsequent calls to not be logged for any extensions on the PBX. The majority of transfer behaviors do not result in this issue. The only scenario consistently demonstrated to result in this issue involves the completion of the transfer via the My Calls widget on the Switchboard when the two calls were placed on hold prior to the initiation of transfer.

First Reported: 1/13/2017

Resolved in Version:  6.4 (85476) 

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

Title: Event Trigger variables on Event "Answered" do not contain all expected data

DEV Case ID: SWVX-11105

Issue Summary: Event Trigger variables CALLER_ID_NUMBER and CALLER_ID_NAME on Event "Answered" do not contain the data for the original Caller ID of the incoming call, but is now instead the extension number and extension name of the answering extension. Call Logs continue to show the correct, expected originall Caller ID and Name.

First Reported: 10/31/2016

Resolved in Version:  6.4.1 (85757) 

----------------------------------------------------------------------------------

Title: Queue calls incorrectly treated as internal calls for ring rules

DEV Case ID: SWVX-11219

Issue Summary: Queue calls are incorrectly treated as internal calls within extension ring rules.

First Reported: 11/22/2016

Resolved in Version:  6.4 (85476) 

----------------------------------------------------------------------------------

Title: Assisted transfer to external number from queue causes queue member to stay busy

DEV Case ID: SWVX-10957

Issue Summary: Queue members are unable to answer queue calls following a warm transfer to an external number. The queue call's transfer to an external numbers results in the queue member being labeled as busy until the transferred call is terminated. The queue member is still able to answer direct calls, but unable to receive calls from the queue.

First Reported: 9/21/2016

Resolved in Version:  6.3.3 (82427) 

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

----------------------------------------------------------------------------------

Title: Calls redirected out over PRI via personal call rule may be rejected by select providers

DEV Case ID: SWVX-11120

Issue Summary: Calls redirected out over PRI using a personal call rule (Ring-all or Cascade) may be rejected by select providers due to a "Redirecting Number - Unknown Number Plan" error. This is due to both legs of the hairpin redirect being external, select providers expecting to see a provider-assigned number on the request, and broader changes to the way send_to_external_num worked resulting in a behavior change with unintended consequences for this scenario. A temporary workaround for this issue is to use a Digium Phone's Forward feature. Please note that this relates to the bug detailed immediately above, but is resolved separately.

Note: Some aspects of this issue were resolved in version 6.3.3. However, some providers still continue to reject these calls and a complete resolution is expected in version 6.3.4

First Reported: 9/21/2016

Resolved in Version:  6.3.4 (83002) 

Title: New Global Variables cannot be correctly saved

DEV Case ID: SWVX-10913

Issue Summary: Global Variables created subsequent to the update to 6.3.1 are not saved in IVR actions and cannot be used at later points in the routine.

First Reported: 9/12/2016

Resolved in Version:  6.3.3 (82427)