Manager Portal

New Features

V44.1

• Added new time frame capabilities for recurring time frames and holiday observance.

V44.2

• Added a Call Time Limit setting to the Domain settings modal. This allows the configuration of a maximum duration for calls within the domain. When set, this will override the system parameter. In case of a cross-domain call, the smaller non-zero limit will be honored.

Improvements

v44.0

• SMS Numbers can support "+" character.
• Allowed all primary buttons to be color-branded.

V44.1

• Prevented users from setting the domain max user count to a value lower than that already present on the domain.
• Associated dial translations are now deleted from the database when deleting a domain.
• Improved use of custom statuses. Now, a custom status message will persist when going to online, offline, or single call mode but will be overwritten when going to any of the pre-defined custom statuses (i.e. Lunch, Web, Other)..
• Hid the "Auto Answer" button from the agent page when editing a queue using any of the Simultaneous ring options for hunting type as it's not compatible.
• Allowed Office Managers and above to see user addresses on the Emergency Address page.
• Dramatically decreased the size of PHP sessions to allow for replication of the sessions and improved performance.
• Improved portals local session caching speed by reducing disk access.

V44.1.3

• Solved bug related to cache cleanup causing CPU and IO load issues.
• Improved portals local session caching speed by reducing disk access. 

V44.1.4

• Hid “domain user” in Portal’s Time Frame list. Now only “Domain” will show, which configures domain-wide Time Frames. 

v44.2

• Now MFA functions properly when using SSO login.
• Shrunk down the clickable space on the voicemail page in the portal to avoid accidental clicks on touch screen devices.
• Now, if an SMS queue conversation is ended with a Termination Keyword, the agent will not be able to continue sending messages to the recipient.
• Ensured that, when adding a number to the SMS Inventory, the system checks the relevant extension before allowing users to save.
• Corrected an issue where the new user link on the main portal page was not working due to a validation issue.
• Fixed a 44.0 regression bug where, when a user’s answering rules were set for Do Not Disturb, the appropriate DND icon didn’t appear on the user’s Web Phone status.
• Now, the button that configures what columns appear within tables is labeled “Columns” on all Portal pages instead of “Table Settings.”
• Reduced timeframe load time by over 80%, eliminating lag time before timeframes appear in the portal.
• Resolved a tooltip bug in Time Frames that displayed inaccurate data when clicking the tooltip info buttons.
• Prevented a TOD route from being routed back to the same user. The change removes the number/user from the destination field’s autocomplete when configuring Time of Day Routing rules.
• Corrected an issue where selecting all and bulk editing on the Top-Level Inventory page could result in DID changes to the user’s domain instead of the selected DIDs.
• Corrected an issue where Resellers could modify system-wide UI configs with the Import Tool without appropriate permissions.
• Now, when an agent ends a session using the “End” button, a closing message is sent to the client informing them the session has ended.
• Corrected a 44.1 regression issue where favicons would only appear when the login screen was open. After logging in, they would no longer populate.
• Corrected a 44.2 bug during Early Access where Sentiment, Closing Sentiment, and Topics Column options were appearing in the Call History dropdown even when the features were not enabled for that domain via UI Config.
• Corrected an issue concerning Bulk Editing users’ Caller IDs where a blank dropdown was incorrectly added, preventing users from completing edits.
• Corrected a regression issue found in 44.2 Early Access where default columns for the Call History Table were erroneously changed.
• Corrected a bug concerning TOD tooltip displays of specific dates in Time Frames, where deleted dates would still appear when hovering over the Time Frame tooltip.
• Corrected a bug concerning Time Frame order when configuring Time of Day Routing. If a user added a Time Frame, immediately changed its order, and saved, the changes were not applied when the configuration was reopened.
• Corrected an issue that occurred during 44.2 Early Access where transcription and summary data were not populating in Call History for some builds.

Bug Fixes

v44.0

• Resolved a bug that prevented Shared Contacts from being displayed
• Now Resellers do not see address pop-ups outside of their own domain. This was incidentally fixed by a change in permissions logic in 43.4.
• Improved call count on inventory view by phone number from super user level.
• Ensured that Auto Attendant appears as a dropdown option when filtering Phone Numbers by Treatment.
• Corrected a bug where in some instances voicemail reminders would not save correctly.
• Fixed bug where half-hour and 45-minute timezones were not respected when applying time frames.
• Ensured that the Active Answering Rule section on the User homepage correctly represents the Answering Rule in effect.
• Fix for Allow/Block answering rules not working correctly when editing a different user's rules.
• Ensured that updating user status does not impact agent status.
• Ensured that Site Managers cannot edit another user's site.
• Ensured that Site Managers cannot modify or add higher scopes.
• Removed styling limit so longer contact names are not unnecessarily truncated.
• Fix to allow Office Managers to edit and delete Emergency Addresses.
• In the Portals bulk user edit page, increased the limit for number of addresses in the dropdown from 100 to 10,000.
• Corrected a bug allowing residential users to see other domain extensions via auto-complete dropdowns in answering rule settings. Now, the user will only be able to view their own devices in the auto complete.
• Fixed a bug where if a device does not have an inherited address, and an emergency caller ID was added without an emergency address, then the address would be left blank with only the country code.
• Corrected a permissions issue preventing call center supervisors from listening to recordings by agents in the domain.
• Fixed bug that, when masquerading as another user and leaving the page idle until the session times out, logs the browser into the previously masqueraded user.
• Corrected bug starting in 43.3.3 where editing treatments of Phone Numbers on the Domain-Level would not save properly.
• Fixed an issue where legacy emergency numbers weren't showing the correct information when editing.
• Corrected a bug identified in v44 Early Access. When editing MOH, the user would receive a Music on Hold Failed to Update message.
• Improved call center page to better handle supervisors adding or removing the agent from queues so that the buttons and actions reflect the current set of queues and don’t allow the agent to reenter themselves into queues accidentally.

V44.0.1

• Corrected a bug where, when a queue had no active calls, incorrect data was displayed in the Active Calls column and modal.

V44.0.2

• Improved cookie handling in Attendant Console by: 1) Preventing the setting of a cookie with a null value 2) Setting a timer to remove some cookies after 1 hour instead of adhering to the 1-day browser timeout setting.

V44.1

• Prevented users from editing the MAC from the phone's edit view. This prevents duplicate MACs from being added.
• Now, when a domain is deleted, associated 911 numbers will be deleted from the database.
• Allowed Basic Users and similar scopes to configure phones in SNAPbuilder for all devices owned by their user. Previously, if the phone extension did not match user extension exactly (for example, had appended letters), SNAPbuilder appeared as read only.
• Improved the extension to extension filter option in call history. Previously, this filter would still allow for inbound and outbound calls.
• Improved offnet agent support in call queues when using international numbers.
• Improved fax account creation when max fax accounts is set to 1.
• Fixed bug where portal was not showing some call recordings.
• Added a warning when attempting to add a call to you using an extension that already exists. This warning is now consistent across relevant scenarios.
• Fixed a bug where the save button was not functioning properly after attempting to save voicemail reminder settings without entering a reminder recipient.
• When a group chat list of participants exceeds the height of the modal, information becomes scrollable. Previously, list would spill over to other parts of the screen. 
• Corrected a bug where, if notes and call history had a line break, extra rows were created in call history export.
• If the window is off-screen, inbound group chat messages now cause a sound notification.
• Forced a line number selection when creating a new phone device directly for a user.
• Corrected a bug which occurred when importing numbers outside of your user's domain. In this case, changes in phone number settings using the import tool, appeared as added rather than updated.
• Corrected a bug concerning the directory tab when viewing a config file in the portal for Yealink phones. Previously, this directory was not visible until the phone synced. Now the directory is visible after saving.
• Corrected a bug that prevented the call center page from loading if a custom status contained an apostrophe.
• Fixed an issue with emergency notifications via phone message. Previously suggestions for notification destinations did not populate.
• Resolved issue with tracking agent availability status when using per-queue login / logout.
• Corrected a bug concerning editing phone numbers. When selecting a conference treatment, SNAP.HD meeting IDs unexpectedly appeared in the dropdown.
• Ensured that devices without domain assignments can be deleted.
• Corrected a bug for emergency address export. When exporting emergency addresses from the inventory page, the first emergency address was omitted.
• Corrected a bug preventing users from deleting old scheduled call history exports.
• Improved cookie handling in attendant console by: 1) preventing the setting of a cookie with a null value 2) setting a timer to remove some cookies after 1 hour instead of adhering to the 1 day browser timeout setting.
• Fixed an issue with call center reports. Now, users can view call center reports within the date range limit.
• Fixed a bug that occurred when recycling users. After recycling, the previous user's custom status was still visible.
• The portal now allows for the shared contacts import of fax numbers.
• corrected number formatting when importing contacts.
• Ensured that the Emergency Address map is accurate for addresses after validation.
• Ensured auto attendants and conference bridges correctly appeared in call forwarding auto-completes when configuring answering rules.
• Ensured that hide recordings in domain level-call history" setting is honored. Note: Setting does not affect Super User and Reseller view.
• Ensured uniform color of presence dot on Portal and WebPhone. Now, three colors will be available: -Green = Available to take calls -Grey = Offline/On Break/Lunch/Custom Status (before only grey for offline) -Red = Online but busy
• Corrected a bug where, when a queue had no active calls, incorrect data was displayed in the Active Calls column and modal.
• Corrected a bug concerning portal display of active time frames for a given user. The active tag was previously dictated by the viewing user's time zone. Now the time zone of the user who owns the time frame/answering rule will inform the active tag.
• Corrected an issue for email voicemail notifications. Email addresses containing "-" were not being saved in the portal.
• Improved call history and cradle to grave lookups in portal when Call-IDs contain a /.
• Now, when configuring Ring-All call queues, or any queue with multiple agent ringing, the option, log out agent on missed call", is hidden.
• Corrected an issue where favorites list in contacts was not updating.
• Improved the auto complete on voicemail forwards when using a basic user.
• Properly hid "call queue" from sms inventory add/edit pages when SMS queueing is disabled via system default.
• Ensured that users can change time frame type in 44.1: for example, changing a time frame from days of the week to specific dates.
• Added a fix for the Call History page filter time picker. It was not working correctly when using the 24-hour time format.
• Corrected a bug that caused a blank timezone drop-down within the user profile section of the Portal.
• Corrected a bug that prevented Preferred Server drop-down changes being saved. Preferred Servers changes now save as expected.

V44.1.3

• Back ported from 44.2 to 44.1 micro release: corrected a bug concerning TOD tooltip displays of specific dates Time Frames. If, in a given time frame, two specific dates were selected and saved, then one date was deleted, the deleted date would still be visible when hovering over the Time Frame tooltip when configuring Time of Day Routing. Although it is labeled OMP, this fix is supplied in an API package.

V44.1.4

• Corrected a bug concerning time frames covering days in two separate months. If the first month contained 31 days, the 31st was skipped within the time frame and the UI presented unexpected outputs.
• Corrected a v44.1 regression issue. If an answering rule was created and the corresponding time frame was subsequently modified, a Missing Timeframe notification would appear by the answering rule.
• Reduced time frame load time by over 80%, thus correcting an issue where new time frames were displaying as “expired” in the Portal.
• Corrected an issue with Specific Date timeframes that caused answering rules to apply incorrectly if a timeframe spanned multiple days in any configuration other than midnight-to-midnight.
• Fixed a bug where, if bulk editing phone numbers on the top level, the phone numbers would adopt the user’s domain by default. Now, the numbers' assigned domain persists after bulk edit (unless purposefully modified).

V44.2

• Made improvements to the load time of the contacts dock, specifically when containing a large number of off-net contacts.
• Improved the click-to-call from the popout contacts dock.
• Prevented voicemail message forwarding via the portal to users with voicemail disabled.
• Fixed a bug concerning SMS Queues; previously, if an agent began an SMS Queue session and changed pages, the SMS chat would not show the correct “From” number.
• Corrected an issue concerning SNAPbuilder templates sharing the same name, resulting in erasing a device’s settings when the template was applied.
• Corrected an issue within Call Center Reports where the selected date and time range would reset when switching report views.
• Corrected a bug where the “Add Fax Number” button was still clickable once the domain limit for fax numbers had been reached.
• Fixed an issue concerning answering rules pointing to off-net numbers with answer confirmation, leading to failures in call processing for non-US numbers.
• Corrected a bug affecting devices with an “@” in its username or password, where the config file preview via SNAPbuilder would not generate.
• Portal now prevents two Call Center Agents from picking up the same SMS Queue session; after one picks it up, others are blocked.
• Corrected an issue where creating answering rules with Simultaneous Ring would add multiple destinations for a single user due to autocomplete issues.
• Corrected an issue with modifying answering rules where existing dial rules would overwrite settings with custom tokens.
• Corrected an issue where SIP Trunks with the Trunk Type of Origination Only or Termination Only were not saved correctly.
• Corrected a bug where, if the list of sites in the attendant console was too long, not all sites were accessible.
• Corrected a bug where, in certain cases, SMS Queues failed to send replies stating no agents were available.
• Corrected a bug where saving an SMS number containing spaces resulted in improper saving in the database.
• Corrected a bug where a password containing % or & could not be changed via the portal.
• Corrected a bug where SMS_VOL and SMS_AHT Call Center Stats were not accurate.
• Corrected an issue where the new user link on the main portal page was not working due to a validation issue.
• Corrected a 44.1 regression issue where, when adding a config from the domain level, the domain dropdown did not populate.
• Corrected a 44 regression issue where DIDs assigned to Conferences via the Conference page were not visible in the Inventory Phone Numbers list at the domain level.
• Corrected an issue concerning Bulk Editing users’ Caller IDs, where a blank dropdown was incorrectly added.
• Corrected a regression issue found in 44.2 Early Access where default columns for the Call History Table were erroneously changed.
• Corrected a bug concerning Time Frame tooltip displays of specific dates in Time Frames where deleted dates would still appear.
• Corrected an issue concerning Time Frame order when configuring Time of Day Routing, where changes were not saved correctly.
• Corrected an issue where Custom Statuses added or edited from the Call Center Reports Page didn’t save.
• Corrected a bug where Resellers could modify system-wide UI configs with the Import Tool without proper permissions.
• Corrected a bug where the tooltip description for Call Volume in Call Center was missing details about Assisted Calls Handled (AST).
• Corrected a bug where a user’s favicon would only appear during the login screen and not afterward.

V44.2.1

• Corrected an issue where changes to the URL, when paginating voicemail, didn’t allow voicemail forwarding to function.

API

New Features

V44.0

• Added ability to reset subscriber passwords without existing password if request originates from designated IPs.
• A new column (dialrule_domain) was added to the database to significantly increase the speed of reading phone numbers.
• Added audit log entries for all successful logins and access token grants. Logs will include the user, ip and access type info such as password, sso options, jwt option and masquerade options.
• Changed the JWT implementation to allow access without the need for a cookie to provide part of the secret for validation. Also enabled revoking specific JWTs by ID (JTI or User ID) to void all JWTs created by that ID prior to the current date. 
• Added support for a stronger JWT token including the ability to validate using public key. New Configs are needed to set the location of the public and private keys. Public key may be shared but private key needs to be kept local and VERY secure. Ideally the same key is used on all servers in cluster to allow JWTs to be used on all servers. 

V44.1.1

• API v2 now supports full interaction with NetSapiens' new recurring and holiday timeframes as well as all existing timeframes. 

Improvements

V44.0 

• Now, when requesting information via the API that does not exist, the API returns a 404 instead of a 200.
• Enabled Broadcast Paging Groups creation via API.
• Added the ability to determine whether a subscriber has Caller ID blocking ("Privacy") enabled by changing API code to include "privacy" in the list of fields returned by a read of the subscriber object.
• Increased the number of lines that can be provisioned on a device via API from 8 to 24.
• Added audit log entries for reseller Create, Update, and Delete actions.

V44.0.6

• Reworked how Android Push messages are sent from the platform, including the adoption of the firebase v1 HTTP API and moving from server keys to service accounts for authentication. These changes meet the new Firebase requirements, starting on June 20, 2024.

V44.1

• Now, when an assigned reseller for a domain is changed, phones assigned to that domain will correctly change resellers.
• Prevent the creation of timeframes on Sites and Departments as they are not currently supported by the core switch due to a system limitation. Timeframes for Sites and Departments is functionality we will possibly add to the platform in a future version.
• Holidays in Time Frames are now properly localized to suit the language of the user.
• Reworked how Android Push messages are sent from the platform, including the adoption of the firebase v1 HTTP API and moving from server keys to service accounts for authentication. These changes meet the new Firebase requirements, starting on June 20, 2024.

V44.1.1

• Reworked how Android Push messages are sent from the platform, including the adoption of the firebase v1 HTTP API and moving from server keys to service accounts for authentication. These changes meet the new Firebase requirements, starting on June 20, 2024.
• Holidays in Time Frames are now properly localized to suit the language of the user.

V44.1.2

• Increased the batch size for the audit log channel to allow for a faster replication.

V44.2

• Corrected an issue where missed call notification emails didn’t include user ext and name in the email body.
• Disabled voicemail by default for system users.
• Fixed an issue where MMS payload was received as an array of data.
• Now, the API supports devices with 48 lines with full filtering abilities.
• When deleting UI Configs, the target User is now displayed in the Audit Log.

Bug Fixes

v44.0

• Improved a case when saving a domain broke implementation of IvrNotChangeFwd to block call forward setting in IVR.
• Added API config, SNAPhdSendEmail, to control the recipient limit of SNAP.HD's "recording complete" email.
• Added Audit Log items for adding, deleting, or updating DLR 911 addresses. This functionality still respects user privacy and does not directly reveal described address.
• Improved device create on Poly builds with mini sidecars; these sidecars are now recognized regardless of where you configure the device.
• Fixed issues receiving MMS using Inteliquent.
• Fixed issue where SNAP.HD recordings failed to generate for geo calls.
• Corrected issue allowing ATA Inbound Fax Handling to remain enabled after disabling ATA Method.
• Fixed an issue where the Call Flow displayed incorrect call legs if it encountered an event containing multiple SIP messages.
• Improved stats for callbacks. Previously, callbacks using 302 redirect (like STIR) were counted in domain-wide Dialed Number Stats, but were inaccurate when viewing per queue.
• Corrected a bug leading to an erroneous test subject for faxes sent via FaxBack.
• Ensured that changes made while masquerading are correctly represented in the Audit Log.
• Improved the ability to transition an agent from Online to One call status on WebPhone and API v2.
• Improved call center page to better handle supervisors adding or removing the agent from queues so that the buttons and actions reflect the current set of queues and don't allow the agent to re-enter themselves into queues accidentally.
• Fixed a bug where, if the content of the notes field under Portal>Inventory>Phone Numbers is deleted, the description field in the DID Table becomes NULL
• Corrected a bug causing incorrect PidfLo data when duplicating user addresses with Inteliquent.
• Corrected a bug where, if a Reseller had a space in their name, they were unable to edit a Reseller via API v2.

V44.0.2

• Corrected an issue with updating a phone number. Previously, the system gave an error about needing a Dial Rule ID.

V44.0.3

• Corrected a bug causing the Outbound Proxy value to be blank when accessing the phone settings page in the Portal. 
• Corrected a bug causing install issues for servers that did not previously have Redis. Now, IPv6 loopback binding is prevented by ensuring that Redis only binds to 127.0.0.1.

V44.0.4

• Fixed an issue where newly created Auto Attendant dial plans were not replicated to Geo cores.
• Improved the inbound status update flow for Pangea status due to an early exit when one user reached the disk space limit.

V44.0.5

• Improved the matching of email addresses when using SSO.

V44.1

• Improved audit log for answer rules edits and ensured information is properly replicated.
• All associated cdr schedules are now deleted when a user is deleted.
• Improved the API response in JSON format for reading back recordings when there is no valid converted files.
• Corrected a case sending duplicate new voicemail email notifications.
• Corrected several issues in Call Center reports with call details when preselected queue and department fields are used. Also corrected incorrect Total row values when certain filters were used.
• Improved audit log when answer rules are reordered. The list order will now update accordingly and continue to update with multiple audit log additions.
• Corrected bug where, in cases with non-standard Call IDs, recordings did not populate when filtering by caller number.
• Improved the speed of call history lookup with MOS scores by omitting user agent data, which requires a second database query and can result in extreme delay.
• Fix for SMS carrier not being assigned correctly, resulting in media attachment icon not showing.
• Corrected a bug that, when moving user settings from voicemail notification + move to trash to voicemail notification disabled, would save voicemail instead of leaving it new. For those upgrading to 44.1, resave affected users to correct setting.
• Corrected a bug causing the Outbound Proxy value to be blank when accessing the phone settings page in the Portal.
• Previously, when adding a second device to an existing user, some call processing defaults (such as ForceNotify) were ignored. Now these call processing defaults are honored.
• Improved lookup of v2 event subscriptions when using access token.
• Ensured that third-party access to call recordings follows expected behavior: now if an agent (recording disabled) calls another user who has recording enabled but has checked the hide recordings in domain level call history checkbox, call center supervisors will not have access to the recording. If that checkbox is not selected, supervisors will see the recording.
• Increased the ability for office managers to read message sessions for their domain using APIv2 and event subscriptions.
• Improved lookup of existing subscriptions in external domains when viewing as a Super User.
• Improved cleanup of .tiff files saved after faxing.
• Improved the use of "path" when using ftp and sftp for remote archive.
• Fixed an issue where newly created Auto Attendant dial plans were not replicated to geo cores.
• Corrected an issue where call center email reports were not being deleted.
• Corrected a case where, when reaching a fax limit, a batch of excess emails is triggered notifying of the full storage space.
• Improved API access to messaging options from higher level scopes. Office manager and resellers now can access messaging (SMS and chat) via the API.
• Corrected issues that would result in duplicate user appearance in SNAPanalytics.
• Improved phone number and dial rule addition/updating when using the new friendly responder names in v2. previously was not converting to the required real responder names.

V44.1.1

• Corrected a regression issue in 44.1. Previously, CDR exports would not successfully download.
• Ensured that logic from API-1631 is applied, reducing Call History Page load time containing MOS scores.

V44.1.2

• Corrected an issue where some specific dates time frames were not properly recognized by the system.
• Fixed transcription summary and topics table creation bug.

V44.1.3

• Back ported from 44.2 (API-1903) to 44.1 micro release: Corrected a 44 regression issue concerning Call Center Supervisors that are not assigned to any queues. In this case, Call Center Supervisors did not have access to call recordings for their calls.

V44.2

• Corrected an issue with Call Center where, when logging back in with the granular queue login button, the Agent Log was not updated.
• Fixed an issue with duplicate missed calls within Call Center Reports when setting the date range to begin and end in different months.
• Now, API v2 does not allow messagesessions with special characters.
• Emergency Endpoints with a blank or * domain specification are now marked as “unassigned”. The filter for unassigned Endpoints is also functional.
• Added a section on removing auto attendant prompts to API documentation.
• Corrected an issue where authentication can be bypassed using particular API calls to read UI Config data.
• Now, reject and accept rules can be removed via API v2.
• Corrected a 44 regression issue concerning Call Center Supervisors that are not assigned to any queues. In this case, Call Center Supervisors did not have access to call recordings for their calls.
• Added protection against an erroneous create agent request when adding a queue in a different domain.
• Corrected a bug that allowed the creation of an answering rule via API with another user’s time frame.
• Added dial-rule-description as a forced string variable in API v2.
• Corrected a bug where Resellers saw all SNAPbuilder templates within their territory instead of just a domain’s templates when using the tool within a given domain.
• Corrected a bug that disrupted Reseller access to recordings for interdomain calls when viewing domain Call History.
• Fixed an issue where queue calls ended during voicemail greetings were not tagged as Abandoned Calls.
• Changed Audit log to accept “null” and other values, along with ensuring accurate default values are set and in place so that audit log is error free and capturing changes throughout the system accurately.
• Fixed a 44.2 issue in Early Access where in some cases, API errors would appear during upgrade.
• Corrected a v44.1 regression. When agents used star codes to login and out of queues, agent status was not properly reflected in the Call Center Agent Status Report.
• Corrected a bug found during Early Access. PUSH/Create requests were not functioning without deprecated configs in the api_config.php file.
• Corrected an issue where read-only API keys were unable to complete count and list requests.

V44.2.1

• Improved retrieval and update speed for transcription and sentiment data.
• Improved replication by allowing batches for transcription updates.

V44.2.2

• Corrected a regression issue concerning Call Center Stats. API calls for data using the HH:M:SS format were receiving a 400 error.

Auto Attendants 

Bug Fixes

v44

• Added the option for Auto Attendants and Call Queues to not allow duplicate extensions upon create. If the configs are set to "no", then it will validate across all extensions and stop users from creating a duplicate extension if one is found. In that case, the Portal will display a warning that "this extension is already in use". 
• The Calls Waiting stat in the call queue subpage now accurately reflects activity.
• Ensured that Auto Attendant appears as a dropdown option when filtering Phone Numbers by Treatment.
• Corrected bug identified in Early Access for v44. In the top level Phone number filter, Auto Attendant was appearing twice under Treatment.
• Now, caller ID prefixes added by Auto Attendants appear correctly and caller names are appropriately truncated.
• Added the option for Auto Attendants and Call Queues to not allow duplicate extensions upon create

v44.0.2

• Improved cookie handling in Attendant Console by: 1) Preventing the setting of a cookie with a null value 2) Setting a timer to remove some cookies after 1 hour instead of adhering to the 1-day browser timeout setting.

v44.0.4

• Fixed an issue where newly created Auto Attendant dial plans were not replicated to Geo cores.

v44.1

• Properly hid "call queue" from sms inventory add/edit pages when SMS queueing is disabled via UI config.
• Ensured auto attendants and conference bridges correctly appeared in call forwarding auto-completes when configuring answering rules.

v44.1.2

• Tagged any call that were in the Talking state with the “Talked” tag, so upon entering Call Queue, it will be excused from STIR, even if the queued entity was from Offnet and had NOT been STIRred.

Call History

Improvements

v44

• Added servedCallId to raw CDR fields.

v44.1

• CDR exports will no longer include CDRs with No Orig Match and a 0 duration on full system exports.

v44.2

• Fixed an issue with FTPCDR Export data intermittently appearing as empty.
• Added two system parameters to allow conversion tools in the Recording Module to use processing powers to continue converting recordings, even if one recording is not yet fully converted.

Bug Fixes

v44

• Fixed a bug occurring in calls that failed over to a secondary connection. In these cases, the domain information was not present and Call History records were not available within the applicable domain of the Portal.
• Corrected issue with cross-domain site and department lists in Call History filter dialog when, as a Super User, masquerading as a user in another domain.
• Synchronized the numbers displayed on the call history and call details pages.
• Improved the domain tracking of calls inbound to fax servers through NetSapiens' integrations so they now will properly show in the CDR table linked to the domain.
• Improved a call pickup case preventing some issues from proper stat calculation.

v44.1

• Improved the extension to extension filter option in call history. Previously, this filter would still allow for inbound and outbound calls.
• Portal call history now displays the name of the callee when available.
• Corrected a bug where, if notes and call history had a line break, extra rows were created in call history export.
• Corrected a bug preventing users from deleting old scheduled call history exports.
• Ensured that “hide recordings in domain level-call history" setting is honored. Note: Setting does not affect Super User and Reseller view.
• Improved call history and cradle to crave lookups in portal when Call-IDs contain a “/”.
• Added a fix for the Call History page filter time picker. It was not working correctly when using the 24-hour time format.
• Improved the speed of call history lookup with MOS scores by omitting user agent data, which requires a second database query and can result in extreme delay. Added a new API config, NsLookupUserAgentsVoipmonitor, (defaults to false). Set this API config to true to include user agent data.
• Ensured that third-party access to call recordings follows expected behavior: now if an agent (recording disabled) calls another user who has recording enabled but has checked the “hide recordings in domain level call history” checkbox, call center supervisors will not have access to the recording. If that checkbox is not selected, supervisors will see the recording.
• All associated cdr schedules are now deleted when a user is deleted.
• Corrected a crash condition causing CDR error messages on syslogs after upgrading to v44.
• Properly tagged calls to ad-hoc conference bridges to ensure they don’t appear in outbound call stats.

v44.1.1

• Ensured that logic from API-1631 is applied, reducing Call History Page load time containing MOS scores.
• Corrected a regression issue in 44.1. Previously, CDR exports would not successfully download.

v44.2

• Corrected a bug for scheduled CDR exports. Previously, if a call ended just before a report was to be exported, the call would not be included in the CDR.
• Improved download of "custom" scheduled exports. Previously, issues concerning download could cause a 404 error.
• Improved error handling in failing ftp and sftp exports.
• Added fix to normalize UK numbers to one format for DNIS reports.
• Corrected issues with duplicate call counts. 

v44.2.1

• Resolved an issue where call history was showing different results between servers in the same cluster.

Call Queues, SNAPanalytics, & Call Center Reporting

New Features

v44

• Added a new feature to create custom ringtones for Call Parks upon ringback, leveraging the RngBckQueue token used for Call Parks that automatically ring back agents after a configured timeout. This can be configured per queue or system-wide. Per queue: To configure a unique ringtone for a call park, use RbAddHdr in the queue option on the Core Admin UI with the needed value. This will allow all ringback calls dispatched from the queue/call park to send the value as an additional header in the SIP Invite. 

V44.1

• Now, call blocking rules for the domain user will be applied to any user configured for allow/block. Currently, this only applies to "Users" and does not yet function for "applications" such as call queues. Application treatment will be implemented along with Portal UI in v44.2
• Previously, If an off-net call went into a queue via DID, the domain stir/shaken settings were, in some cases, ignored. Logic is now changed so those settings are reliably applied.
• Fixed an issue with call center reports. Now, users can view call center reports within the date range limit

Improvements

V44

• Disabled agent status menu when user is not in any call queues.
• Changed the System default to “yes”. If enabled when a call session is dispatched through a queue and the system sends a push to a device and does not get registration, the system will not attempt to dispatch the call to that device again. Once another call enters the queue, the device will be attempted again with the same rules applied.

v44.1

• Improved offnet agent support in call queues when using international numbers.
• Hid the "Auto Answer" button from the agent page when editing a queue using any of the Simultaneous ring options for hunting type as it's not compatible.

Bug Fixes

V44

• Added the option for Auto Attendants and Call Queues to not allow duplicate extensions upon create. 
• The Calls Waiting stat in the call queue subpage now accurately reflects activity.
• Corrected an invalid JSON object provided as a sample for the Custom Data Source chart type in SNAPanalytics.
• Fixed issues with localization in SNAPanalytics.
• Fixed a bug where, when a caller listened to MOH in a queue and was subsequently on hold by an agent, the system failed to resume playing queue MOH and instead played MOH assigned to the agent despite MohContinuous being enabled.
• Fixed a bug that caused calls to honor Call Park settings rather than Queue settings after timeout when a call was parked and subsequently transferred to a queue.
• Fixed a bug where, when a user as agent uses the ‘toggle availability’ key on a hard phone to change status, the change is not reflected on the toggle queue BLF.
• Fixed a bug in the following scenario: A caller chooses the call-back option after a queue time out. The call is then dispatched with the incorrect From-URI.
• Corrected the handling of recording for Devices/Users as Agents, Queue owners, and off-net agents.
• Corrected the stuck ACR issues caused by the fix for Queue's BLF status v43.4
• Added extra logic to check when a Destination User is changed, e.g. when a call is fowarded from one Queue to another, to remove the Session associated from the previous Destination User.

v44.1

• Properly hid "call queue" from sms inventory add/edit pages when SMS queueing is disabled via UI config.
• Now, when configuring Ring-All call queues, or any queue with multiple agent ringing, the option, “log out agent on missed call", is hidden.
• Corrected issues that would result in duplicate user appearance in SNAPanalytics.
• Corrected a bug that prevented the call center page from loading if a custom status contained an apostrophe.
• Fixed an issue with call center reports.
• Corrected several issues in Call Center reports with call details when preselected queue and department fields are used. Also corrected incorrect Total row values when certain filters were used.
• Prevented ghost Hunt group creation upon incorrect “queue login" star code.
• Prevented duplicate "P-Served-Queue" fields from appearing in invite headers.
• Fixed an issue in the Core Module, where session updates for calls waiting in the queue were not published, causing syncing problems between servers.

V44.1.2

• Tagged any call that were in the Talking state with the “Talked” tag, so upon entering Call Queue, it will be excused from STIR, even if the queued entity was from Offnet and had NOT been STIRred.

Conference

Improvements

v44.2

• Reduced Idle CPU usage for the Conferencing Module.

Bug Fixes

v44.1.3

• Corrected a bug where star codes used during a conference weren’t working. 

v44.2

• Now, conference max participant limits are properly enforced. Previously, limits sometimes affected conferences with participant counts below the max threshold.
• Changed the default for NCS’s System Parameter. Previous setting caused crashes for SMA and IOS applications calling into conferences.

Contacts & Chat/SMS

Bug Fixes

v44

• Resolved a bug that prevented ‘Shared Contacts’ from being displayed

v44.1

• The portal now allows for the shared contacts import of fax numbers.
• Corrected number formatting when importing contacts.
• Corrected an issue where favorites list in contacts was not updating.
• When a group chat list of participants exceeds the height of the modal, information becomes scrollable. Previously, list would spill over to other parts of the screen.  
• If the window is off-screen, inbound group chat messages now cause a sound notification.
• Properly hid "call queue" from sms inventory add/edit pages when SMS queueing is disabled via UI config.

E911

Bug Fixes

v44

• Added Audit Log items for adding, deleting, or updating DLR 911 addresses. This functionality still respects user privacy and does not directly reveal described address.

V44.1

• Corrected missing “--” at the end of the last multi-part boundary in the SIP Header. This resulted in carrier issues during 911 calls.
• Now, when a domain is deleted, associated 911 numbers will be deleted from the database.

Inventory

Bug Fixes

v44

• Fixed a bug where, if the content of the notes field under Portal>Inventory>Phone Numbers is deleted, the description field in the DID Table becomes 
• Improved call count on inventory view by phone number from super user level.

v44.1

• Corrected a bug for emergency address export. When exporting emergency addresses from the inventory page, the first emergency address was omitted.

Native Fax

Improvements

v44

• Improvement to verify the data limit is respected and the user will receive a warning email notifying that their storage is full.  Each time the user receives a new fax, a new email is sent to notify that the fax cannot be delivered and includes sender <caller ID>.  Users also are not able to send faxes when storage is full.

Bug Fixes

v44

• Corrected a bug leading to an erroneous ‘test’ subject for faxes sent.
• Corrected issue allowing ATA Inbound Fax Handling to remain enabled after disabling ATA Method.

v44.1.2

• Corrected a regression issue preventing inbound and outbound faxes from working in 44.

SNAPbuilder & NDP

New Features

v44

• Added Fanvil v67 Device support in SNAPbuilder.
• Added GRP 2650 to SNAPbuilder.
• Added platform support for SNOM 300, 360, D120, D717, D735, D785, M3, M100, M700, PA1. SNAPbuilder support for D713 and DC7.
• Added support in NDP for Algo paging devices 8301 and 8373.
• Added Yealink T31W and T34W to the platform.

v44.0.1

• The implementation of “NDP-652” Add Poly Rove B1 to the platform” introduced a regression issue: Polycom devices enabled for SNAPbuilder but never configured and saved with the tool failed to register. Issue is now corrected.

Improvements

v44

• Added support for a newer format of outbound proxy settings in Yealink firmware. Will use both old and new formats together, with the exception of older phones no longer sold and specific versions known by Yealink to not be supported with both settings.
• Added Poly Rove B1 to the Endpoint Module.
• Corrected issue where SNOM overrides in config file did not match the override added in the Portal/NDP.

v44.0.1

• The implementation of “NDP-652” Add Poly Rove B1 to the platform” introduced a regression issue: Polycom devices enabled for SNAPbuilder but never configured and saved with the tool failed to register. Issue is now corrected.

v44.2

• Analog Gateways can now be deployed with full per-device password support.
• Corrected an issue where the SNAPbuilder directory sort order was not respected on the first save.
• Removed the deprecated user option, “Domain”, in NDP.
• Replaced deprecated Canada/East-Saskatchewan timezone option with corrected America/Regina timezone.
• Corrected the # of phone lines for various Yealink devices to support expanded line capacity.
• Added NDP configs, ‘LineShowNameAsLabel' and ‘BLFShowNumberAsLabel' both default to “no”. When set to yes, the user’s name or extension will be displayed by default when provisioning devices. Separately configurable for line appearance and BLF keys. When not set, line and shared line appearances will use extensions and BLF keys will use full names.
• Added additional tokens that can now be used as device overrides for these brands:  Avaya, Linksys, Polycom, Obihai, Grandstream, Cisco, Snom, Htek, Fanvil, Crexendo, Algo, Yealink, Vtech, Panasonic, and ReadyNet: 
• Added page key support in SNAPbuilder for the following models: OneCloud OC923U, OneCloud OC924U, OneCloud OC926U
• Added full support for Yealink T44W and T44U models.
• Added 4 more SNOM D series models to the platform: D815, D812, D150, and D140.
• Added Flying Voice FIP15GPlus and P23GW SIP phones to the platform.
• Added Flying VoicePR08 ATA to the platform.

Bug Fixes

v44

• Ensured that SNAPbuilder appears enabled when viewing the Device List on the Endpoint Admin UI and when clicking and drilling down to a specific device. Previously, SNAPbuilder appeared as disabled once clicking on the specific device.
• Corrected an issue that caused DB connection failures and didn’t allow phones to upload log files.
• Corrected a bug where only 8 configurable lines were displayed in the NDP Admin UI within the Device Model # Page even if the device allowed for more lines.
• Applied a time-out that prevents endpoints from becoming available while transitioning between a ringing and answering state. Previously, this allowed subsequent calls to interrupt during this transition. Time-out is configured by , with a default of 2 (second), and can be disabled by changing the value to 0.0. This fix also corrected issues with the Portal pop-up not honoring agent wrap-up time.
• Applied a time-out that prevents endpoints from becoming available while transitioning between a ringing and answering state. Previously, this allowed subsequent calls to interrupt during this transition. Time-out is configured by , with a default of 2 (second), and can be disabled by changing the value to 0.0. This fix also corrected issues with the Portal pop-up not honoring agent wrap-up time.

v44.1

• Added Snom M500 SNAPbuilder and general support.
• This functionality has been implemented for all brands within SNAPbuilder. The change intends to enable customers using hotdesking to correctly display the logged-in user extension number, not the base extension.
• Allowed Basic Users and similar scopes to configure phones in SNAPbuilder for all devices owned by their user. Previously, if the phone extension did not match user extension exactly (for example, had appended letters), SNAPbuilder appeared as read only.
• Fixed the static sorting feature in SNAPbuilder.
• Support has been added for line key “custom label” variables [[first_name]] [[last_name]] [[extension]] for all the SNAPbuilder-enabled phone models.
• Fixed several issues that occurred with Poly Edge B devices configured in SNAPbuilder.

v44.1.1

• Corrected SQL inserts for SNOM M500 devices

v44.2

• Fixed provisioning issue with certain Aastra devices.
• Corrected an issue where spaces in Grandstream override values were removed in XML files.
• Corrected an issue where SNAPbuilder was adding invalid user extensions to unused lines in NDP.
• Corrected an issue where the SNAPbuilder directory sort order was not respected on the first save.
• Corrected an issue with sorting the SNAPbuilder directory by “Extension.”
• Device override functionality is enhanced to now allow the following character: '.
• Changed default SRTP setting for Snom D120 to off.
• Corrected an issue where Htek page keys were not correctly factored in when provisioning in SNAPbuilder.
• Corrected an issue where the line 2 user for analog gateways was not properly updated in NDP.
• Corrected the # of phone lines for various Yealink devices to support expanded line capacity.
• Corrected an issue where Line Appearances/SLA’s were incorrectly shown as an option on Yealink sidecars.
• Corrected a null value in proxy address field for certain Yealink devices when YealinkUseSRV is set to “no.”
• Corrected a 44.2 regression identified during Early Access. In some cases, customized label tokens in SNAPbuilder, such as [[Extension]], were not being honored.

SNAPmobile Web

Improvements

v44.0

• Disabled agent status menu when user is not in any call queues.
• WebPhone dial pad can now be permanently pinned to page.
• When SNAPMobile Web is open in a browser, if the same user tries to load another instance on a different tab or window then there will be a Duplicate Instance notice. This does not work in Incognito nor across different computers.
• Prevented ringing during an active call when user presses a play button on the keyboard.
• Added onboarding cards for setting up devices and permissions after logging in.

V44.1

• Improved browser caching on html files in WebPhone.
• Improved the fail-over logic to allow for additional time on reconnect attempt to the same server vs. failing down list immediately. This will improve cases like PC wake from sleep or brief interruption due to VPN reconnect for example. Ideally, this will keep connections on the preferred server if the reconnect was not a result of an actual server outage.

Bug Fixes

v44.0

• The Calls Waiting stat in the call queue subpage now accurately reflects activity.
• Ensured updated WebPhone properly supported chat and SMS, including a fix for message time stamps that failed to update.
• Corrected issue where SMS messages containing text that has been copy/pasted with new lines could read out as HTML text on receiving mobile.
• Synchronized the numbers displayed on the call history and call details pages.
• Corrected bug that allowed auto dialing of previously entered numbers after using the click to call feature.
• Updated call session contact information to correctly show data regarding transferred call.
• Fixed a bug that kept users from parking calls via WebPhone if the user already had another call on hold.
• Now, caller ID prefixes added by Auto Attendants appear correctly and caller names are appropriately truncated.
• Fixed a bug that caused an agent device to appear as offline after closing and reopening WebPhone.
• Ensured that instances of PWA more reliably fetch customizable settings.
• Previously, filters for Site/Department in the Call Park tab did not work, now the relevant Call Parks appear.
• Fixed an issue with repeating calls for click to call in PWA.
• Corrected issues concerning Call Park Statuses when monitoring the Park from a geo-remote node.
• Corrected issue that intermittently affected select users' WebPhone registration.
• Adopted HH:MM:SS time format for call stats in WebPhone; now matches Portal.
• Corrected a bug that stopped users from making outbound calls after using the Switch Phone feature.
• Added agent status option for "End Shift" Or Log Out functionality.
• Ensured scopes have the same access to shared contacts as in the Portal; now, only Call Center Supervisors, Office Managers, Resellers, and Super Users can edit/delete shared contacts in the Portal and WebPhone.
• WebPhone will now only setup PUSH support when opened in PWA mode. If opened in standalone (normal browser tab), it will attempt to delete any PUSH token and push support previously set up. This improves WebPhone availability accuracy, and prevents agents appearing available in their queues when the user is logged in but doesnt have an open and valid browser tab running WebPhone.
• Fixed a bug where, when retrieving a call park, api rung the user instead of the WebPhone device.
• Added functionality for Call Center Agents to view a Wrap-Up card when outbound calls are terminated.
• Fixed a bug for agents configured with wrap-up time; their status was changed after receiving a call and modifying window size. Now, status remains unaffected.
• Added functionality to send 486 Busy Here message when incoming queue call is 'ignored' by agent.
• WebPhone now properly accepts 183 Early Media and plays incoming RTP rather than Ring Back.
• Corrected google SSO issue due to change in library and handling of width value.
• Corrected an issue where SSO for WebPhone was redirecting to the login screen.
• Push registration will only happen when the user has the SNAPMobile Web client open as a PWA. Will unregister PUSH on logout.
• Allowed hiding WebPhone Call Center and Settings menu with two new UI Configs.
• Corrected voicemail badge behavior and confirmed badge count functionality without refresh upon receiving a voicemail, deleting, or when a voicemail is moved to a saved folder.
• Corrected a bug identified in v44 Early Access. Logout icon appeared as a lock instead of an exit.
• Corrected issue identified in v44 Early Access. Chevron was replaced by Hamburger as the expanding sidebar icon to ensure consistency between compact/non-compact views.
• Corrected a bug identified in v44 Early Access. In some cases, after canceling a call transfer, the user was unable to return to the active call.
• Corrected bug identified in v44 Early Access. The Call Center tab was displaying an incorrect count of online agents.
• Corrected a bug identified in v44 Early Access. The queue card grid was not updating offline status in real-time.
• Corrected a bug identified in v44 Early Access. When receiving a second call from off-net, the Caller ID was incorrect.
• Corrected a bug identified in v44 Early Access. In certain cases, when receiving a second call from off-net, the call would drop or WebPhone would crash.
• Corrected bug identified in v44 Early Access. When receiving a second, incoming call, user was unable to take the call in compact mode (and had to maximize screen to pick up).

V44.0.2

• Fixed a bug concerning PC Chrome browser notifications. Previously, when rejecting via Chrome notification, the call card would persist. Accepting the call after reject would lead to WebPhone crash.
• Fixed a crash that occurred when transferring call to a contact using the contact card.

V44.0.3

• WebPhone didnt allow users to scroll all the way through a Contacts List. The bug is now fixed and all contacts are accessible.
• Fixed an issue in the Answering Rules details subpage that caused a blank screen.

V44.0.4

• Fixed a Call Park issue where Webphone would not display calls parked from hard phone endpoint devices.

V44.1

• Corrected issues with call parks when both endpoints are soft phones registered to different cores.
• Fix for SMS conversations that start with a space within the offnet number.
• WebPhone now respects commas in URL dialing. Previously, commas in any link one clicks to call could result in call failure.
• WebPhone didnt allow users to scroll all the way through a Contacts List. The bug is now fixed and all contacts are accessible.
• Ensured that duplicate instances of Web Phone did not make repeated reconnection attempts, interrupting registration for the instance in use.
• Improved updating and synchronization of messages on outbound SMS sending
• Improve the update of outbound messages in webphone when sent from another method than webphone.
• Fixed a typo on the v44 dial pad. The #5 key had the letters JKL in the wrong order.

V44.1.1

• Corrected a bug in 44.1.0, where Web Phone was not properly failing over during registration to alternative Core Servers after receiving a 503.

V44.2

• Fixed bug causing one-way audio after long holds due to erroneous a=recvonly in the SDP.
• Previously, agents on Web Phone were unable to decipher if a conversation card is part of an SMS Queue. Now, the card will list the SMS Queue’s Name and extension over the destination’s off-net number.
• Now, if a user does not have an assigned SMS number, they will not see available SMS numbers. Previously, they still had the option, leading to unnecessary error notifications.
• Allowed the following symbol in contact numbers: *.
• Fixed a bug concerning inbound calls from anonymous callers. When a name was not present for the caller, the Web Phone Call History Page would show the number dialed instead of the originating number.
• Fixed a v44.0 regression issue concerning custom statuses on Web Phone. If three or more custom statuses were available, selecting a custom status could result in the application freezing until refreshed.
• Now, if a user makes a call from a non-Web Phone device, the call will be pushed into Web Phone Call History without the need to refresh.
• Ensured that the drawer_default.png setting is honored by the system when configured for a Reseller-Territory.
• Changed code so, by default, STUN is disabled for Web Phone user agents in an attempt to correct an issue with delays initiating calls in certain cases. 
• Corrected a v44.1 regression concerning call parks using WebPhone. During certain cases using simultaneous ring and ring all queues, WebPhone call parks would park the wrong calls.
• Corrected an issue where, if a 3-way call was formed and a participant hung up, the user would not be able to add a new participant.
• Fixed a regression resulting in a WebPhone crash after typing Enter or Delete on the dial pad during a call.

SNAP.HD

Bug Fixes

v44

• Fixed issue where SNAP.HD recordings failed to generate for geo calls.
• Ensured that SNAP.HD does not send an email notification when using Outlook plugin
• Added API config, “SNAPhdSendEmail”, to control the recipient limit of SNAP.HD's "recording complete" email.

v44.1

• Corrected a bug concerning editing phone numbers. When selecting a “conference” treatment, SNAP.HD meeting IDs unexpectedly appeared in the dropdown.

SBUS

Bug Fixes

v44.1.1

• Corrected a memory leak introduced in v44.1 which also triggered high memory alarms.

Voicemail

Bug Fixes

v44

• Fixed a bug where attended transfers to Voicemail using WebPhone did not connect.
• Corrected a bug where, if the call was started with a Call Back at an off-net number and the call was redirected to voicemail, then that number was incorrectly exposed.
• Ensured that Voicemail notification settings, “send with attachment” and “send with brief attachment”, result in different email attachments.
• Corrected a bug where in some instances voicemail reminders would not save correctly.

v44.1

• Corrected an issue for email voicemail notifications. Email addresses containing "-" were not being saved in the portal.
• Improved the auto complete on voicemail forwards when using a basic user.
• Corrected an SBus issue that resulted in duplicate voicemail email notifications.
• Corrected a bug that, when moving user settings from voicemail notification + move to trash to voicemail notification disabled, would save voicemail instead of leaving it new. For those upgrading to 44.1, resave affected users to correct setting.
• Ensured that the configurable voicemail reminder interval is honored for initial voicemail reminder.
• Fixed a bug where the save button was not functioning properly after attempting to save voicemail reminder settings without entering a reminder recipient.

Improvements

v44.1

• Made improvements to voicemail reminders feature to increase efficiency.

NMS

Improvements

v44

• Removed a deadlock condition that could cause System Status updates for NMS/NCSto stop or in rare instances crashes, by adding a timeout to SBus requests.
• Fixed an issue where the STIR/SHAKEN's 302 was not processed by the Core Module if the call was in the "Connecting" state.
• The NMS now accepts a=sendonly and a=inactive in the SDP before any m-line. Processing this sdp form allows Fanvil hold requests to function properly.
• Now, if a WSS/TLS/TCP connection fails momentarily, the NMS will attempt to adopt a new connection of the same protocol rather than fall back to UDP. This means that, during momentary connection failures, subsequent re-invites continue to function properly.
• Improved file replicator's (NFR) error handling for failed file sync attempts, enabling records and retries upon scp failures. 
• Now, whichever NMS is processing the session sends Push instead of using the device's last registered instance. If the device is not directly connected to said NMSinstance, the invite is sent across the geo-cluster.
• Now, the system will accept an un-register from an IP already registered without a response to a 407 challenge.
• Added aors to term and orig lines of call trace media summary for easier reading of Switch Logic. An example line might read: (1.1.1.1:27984) (IPV4) @<2.2.2.2:26910> 18292 (18292/0/18292) bytes 48.78Kbps
• Fixed an issue where an invalid SDP media line combined with the PcmuOnly token led to looping and audio quality issues.

v44.1

• If an agent receives a call and a prompt is played for call confirmation, a short No Answer T/O may disconnect the agent before the prompt finishes. To ensure this no longer happens, additional logic was added to the call dispatch, controlled by three additional system parameters, allowing the system to track on-hold/pending sessions dispatched to agents. 
• Previously, If an off-net call went into a queue via DID, the domain stir/shaken settings were, in some cases, ignored. Logic is now changed so those settings are reliably applied.
• Switched MySQL table engine to InnoDB for NFR host worker tables.
• Expanded logic RELEASED  from v44.0 to cover more scenarios with Grandstream devices and various gateways.
• Introduced the WebResponder verbs Echo and Say. Echo allows for real-time audio feedback, enabling immediate playback of user input to facilitate testing. The Wait verb can be used to insert configurable pauses within a call flow.
• Fixed an issue in the Core Module, where session updates for calls waiting in the queue were not published, causing syncing problems between servers.
• Made improvements to voicemail reminders feature to increase efficiency.
• Prevented users from setting the domain max user count to a value lower than that already present on the domain.

v44.1.4

• Corrected an issue concerning the Reason Header of the SIP CANCEL signal when going to Avaya devices through simrings. Previously, this could result in continuous ringing of the Avaya device. 

v44.2

• Enabled TCP/TLS session sharing to improve system efficiency.
• Added System Parameter to resend SIP messages even over Reliable Transport, i.e., TCP/TLS/WSS. This configuration is meant to solve cases with E911 Bandwidth where initial invites were not always processed by the carrier.
• Ensured that calls can be transferred even while ringing an agent or agents.
• Improved File Replicator transfer speed by batching SCP transfers.
• Improved the TCP/TLS session timeout handling by incorporating a timer within each session.
• Improved the Core Module’s TLS certificate auto-reload by checking that the certificate, private key, the configured CA, and intermediate certificates are valid before restarting the TLS server upon cert renewal.
• Ensured that, when a Phone Number is set to “Call Queue” Treatment, the user and domain call block rules are honored.
• Introduced Core Module system properties which control whether the Core Module will send TCP keep-alive signals for SIP connections
• Allowed for configuration of voicemail type by user instead of domain in the Admin UI within a User settings modal. 

Bug Fixes

v44

• Integrated crashpad for fast and reliable crash reporting.
• Allowed WebPhone to correctly process 183 Early Media by removing local ringback and instead receive the rtp stream.
• Corrected an issue where wrap-up time configuration was not honored when calls were answered via Portal pop-up. Fix is located in logic designed in “NMS-2783”.
• Fixed a bug where, when a caller listened to MOH in a queue and was subsequently on hold by an agent, the system failed to resume playing queue MOH and instead played MOH assigned to the agent despite MohContinuous being enabled.
• Fixed a bug that caused calls to honor Call Park settings rather than Queue settings after timeout when a call was parked and subsequently transferred to a queue.
• Created a new timeout in switch logic. 
• Fixed a bug that caused Admin UI domain modifications to change fax settings.
• Fixed a bug causing one-way audio when taking a call off hold.
• Fixed an issue where the Core Module would crash while closing media files.
• Improved stability by fixing a deadlock condition that could lead to a crash.
• Ensured that CID prefixes are properly applied when using STIR/SHAKEN.
• Corrected a bug allowing the Clear IP Identity header to be included in re-invites to the caller, resulting in large packet sizes, which, in some cases, can lead to call failure.Corrected bug where remote BLF observers did not see the BLF “early” status.
• Fixed an issue where an invalid SDP media line combined with the PcmuOnly token led to looping and audio quality issues.
• Ensured that calls to users with Forward Always to an offnet number have the appropriate From Header and can be correctly processed through STIR/SHAKEN.

v44.1

• If a Connection is assigned a domain, the domain’s stir/shaken settings will be checked and, if enabled, applied.
• Previously, if a call was forwarded off-net with STIR/SHAKEN and the first connection tried in a route is set to term=no (no outbound calls), the next connection in the route was not attempted. Bug has been corrected to try for Alternate Route. 
• Added the logic upon re-INVITE to check whether the 2 sides are in the same domain before updating the URI. This ensures that personal extensions are not shared across domains. 
• Corrected a bug in admin UI statistics that caused incorrect metrics in some cases when increasing resolution.
• Added two Dial Translation Tokens to enable playback to be skipped with DTMF to disable skipping playback with DTMF Their effect is valid until the next Dial Plan is applied.
• Corrected a caller ID issue. When forwarding a 302 off-net from a device, the caller's extension number was mistakenly included in the invite.
• Ensured that inbound calls with stir shaken follow the same code path (for consistent behavior) in both of the following cases: -calls using the feature because a connection contains the rule, STIR -calls routed to the service because a domain is configured with the feature
• Corrected call recording issue when dealing with callback calls over geo-remote servers.
• Upon startup, the system now checks for a valid license and, if invalid, a new license is requested.
• Prevented duplicate "P-Served-Queue" fields from appearing in invite headers.
• Adjusted system to better handle STIR/SHAKEN and UDP connections and endpoints. Now, all legs to on-net devices do not send identity headers, regardless of transport. However, for off-net destinations, the identity header will always be sent through tcp connections, but will not be supplied for udp connections if is set to yes.
• Also fixed an issue with counting calls over a given gateway. 
• Prevented a crash case concerning problematic .wav files.
• Ensured that  wake up calls added via API are replicated across geo-nodes.
• Corrected bug. Audit log now properly records failed login attempts to the Admin UI.
• Enhanced DNS resolution efficiency.
• Introduced the WebResponder verbs Echo and Say. Echo allows for real-time audio feedback, enabling immediate playback of user input to facilitate testing. The Wait verb can be used to insert configurable pauses within a call flow.
• Corrected missing “--” at the end of the last multi-part boundary in the SIP Header. This resulted in carrier issues during 911 calls.

v44.1.2

• Corrected a regression issue: in 44.0 and 44.1, calls with the “barge in” feature were not properly counted/monitored. Previously, if a user barged into a call and then hung up, an active session would continue until the call ended, this resulted in misleading BLF--showing the barger as busy even though they had finished the call. Now, the session for the barger is ended once they hang up.
• Fixed an issue where, if the Core, while running, attempts to restart TLS after a certificate change, TLS connections would cease to work.
• Tagged any call that were in the Talking state with the “Talked” tag, so upon entering Call Queue, it will be excused from STIR, even if the queued entity was from Offnet and had NOT been STIRred.
• Corrected a regression issue preventing inbound and outbound faxes from working in 44.1. 

v44.1.3

• Fixed a 44.1 regression issue concerning changes to DND not being communicated to devices. This resulted in incorrect DND status and dispatch failures.

v44.1.4

• Fixed a bug where the dispatch timeout was not triggered after ringing the second tier of agents. Due to this bug, agents after the second tier were not rung. 

v44.2

• Corrected an issue where calls using a dial translation with the application “To Conn for DNIS- Add Header” did not function properly. In these cases, the relevant domain was not always applied to the call, resulting in the domain call limit and status not being honored.
• Corrected an issue related to inbound calls diverted with a 302 from the endpoint. If a call used To Connection with Privacy, the call would fail.
• Corrected a bug where, if a voicemail exceeded the Pre-talk Timeout configuration, the voicemail would not be saved. Now, the recording is saved before the session is terminated.
• Corrected an issue concerning Call Park with calls across geo-nodes and endpoints in different domains. If the receiver parks the call, picks up the call, and then the caller attempts to park, the call park would fail.
• Corrected an issue where a call across geo-nodes to a WebPhone would cause issues when transferred. In this case, upon transfer, the WebPhone window hangs until the call is completed.
• Corrected a crash case concerning Watch Dog looping.
• Eliminated empty folders created by the Core Module in the root directory. This was a regression issue from 44.0.
• Corrected a 44.2 regression identified in Early Access. If a queue call reached an agent using a physical device and that agent blind transferred the call, the agent would still appear as on a call. 
• Fixed a bug concerning calls dispatched to off-net agents via ring-all queues. If the carrier replied with a 407 or 401 challenge, the system was unable to retrieve the correct call leg after sending authorization. Depending on the carrier, this can result in hanging or declined calls.
• Corrected Alert-info passthrough logic that was broken for Sim-Ring. This resulted in call failures with conferences configured with auto-answer.
• Fixed an issue where the Core Module would fail to play a file if the WebServer redirected the request.
• Corrected a regression issue from 44.1 where inbound calls with STIR/SHAKEN enabled would drop when transferred.
• Fixed an issue where the Core Module would fail to parse a Web Responder URL that omitted the forward slash but contained a query string.
• Corrected a v44.1 regression issue. After a user’s voicemail greeting was deleted, the “Phrase Unavailable” prompt wouldn’t play.
• Corrected a v44.1 regression issue. Previously, Caller ID prefixes were added twice when a DID was assigned to a queue and STIR/SHAKEN was applied.
• Corrected a v44.2 Early Access issue concerning Round Robin and Tiered Round Robin Queues. If an agent was using a PUSH device and PUSH received no response, the queue call would not continue to other agents in the queue.
• Corrected an issue concerning calls dispatched to User Agents for Ring-All and Linear Cascade queues. When the agent toggled their time frame, the new answering rule setting was not honored.
• Corrected an issue concerning emergency notification calls. Previously, notification calls would pick up the original call to the Emergency Safety Answering Point, and the original caller would be dropped.

New Features

v44

• Implements NEMO support for the Core Module. 
• Introduces NEMO (Netsapiens Media Offload) support for the File Replicator.
• Now, whichever NMS is processing the session sends Push instead of using the device's last registered instance. If the device is not directly connected to said NMSinstance, the invite is sent across the geo-cluster.
• Now, the system will accept an un-register from an IP already registered without a response to a 407 challenge.
• Added aors to term and orig lines of call trace media summary for easier reading of Switch Logic. An example line might read: (1.1.1.1:27984) (IPV4) @<2.2.2.2:26910> 18292 (18292/0/18292) bytes 48.78Kbps
• Added support in Admin UI to manage new API v2 API keys.

v44.1

• Increase stability of connection-oriented communication (TLS/TCP/WSS) by storing transport type directly within device information. This can now be seen directly by navigating to Connections > User Devices in the Core Admin UI and selecting "Show Contacts". Now, a Transport column will appear.
• WebResponders will now show as a call participant in call traces.
• WebResponders can now feature enhanced security through the verification of the X-NS-Signature-256 header, ensuring data integrity and authentication. Introduced the System Property, WebRespSecret (default unset), which defines a global secret key used for signing all WebResponder requests.