----------------------------------------------------------------------------------
Title: SIP Carriers' Varied Expectations for Route Header and Proxy Host Values
DEV Case ID: SWVX-9776, SWVX-9798
Issue Summary: Switchvox 6.1 makes use of new Asterisk 13 features, which includes enhanced pjsip functionality. Due to this change, additional headers are now communicated to SIP providers, which may require a configuration change, depending on your provider's requirements. Prior to version 6.1.1.1, certain configurations required by select SIP providers could not be accomplished through the UI.
First Reported: at release
Resolved in Version: 6.1.1.1 (78787)
----------------------------------------------------------------------------------
Title: PRI/BRI Debug Fails to Start
DEV Case ID: SWVX-9827
Issue Summary: Unable to initiate Advanced Debugging -> PRI/BRI Debug; however, Packet Capture and ACLI capture work as expected.
First Reported: 3/15/2016
Resolved in Version: 6.1.2 (79112)
----------------------------------------------------------------------------------
Title: Calls Transferred to VM Via Queue Do Not Go Straight to VM
DEV Case ID: SWVX-9693
Issue Summary: When a call is transferred to an extension's VM via Queue On Transfer or BLF, the call will ring and not reach the voicemail box.
First Reported: at release
Resolved in Version: 6.1.2 (79112)
----------------------------------------------------------------------------------
Title: Contacts and Tags Widget Does Not Sort by Last Name
DEV Case ID: SWVX-9769
Issue Summary: When creating or editing a widget for Contacts and Tags, you are unable to perform the expected sort by last name when selected.
First Reported: 3/4/2016
Resolved in Version: 6.2.1 (80665)
----------------------------------------------------------------------------------
Title: Queue Strategies Can Cause Calls to be Stuck in a Queue
DEV Case ID: SWVX-9488
Issue Summary: The ringing strategies Least Recently Answered and Fewest Answered are supposed to ring queue members in strategy order, not continue ringing the one queue member with the absolute least or absolute fewest.
First Reported: at release
Resolved in Version: 6.1.1 (78597)
----------------------------------------------------------------------------------
Title: Second Call to a Rapid Dial Contact Makes Status Incorrect