|JIRA ID||JIRA name||RN Content||Enhancement/Fix/Known Issue|
|UC-3532||Allow mp3 upload for Auto Attendant from WebUI||An enhancement request was completed to allow Auto Attendant recordings that are in MP3 format to be uploaded as Auto Attendant greetings.||Enhancement|
|SIPX-123||Add help text to create SIP Trunk page||A note was added to the SIP Trunk page that stated the use of a Session Border Controller for SIP Trunks was highly recommended.||Enhancement|
|SIPX-121||LDAP - New User Group||An enhancement was completed so that during LDAP imports, when a new user that has not been seen previously by openUC is imported that user is placed into a group. This group should be able to be customized by the Administrator but should default to New_LDAP_Users. |
The user will not be placed into that group again, this is a one time only operation so that Administrators can identify newly created users from LDAP. This is for administrative place holding. This allows administrators to quickly identify brand new users which were imported via LDAP and take action on those users such as group placement or standardize permissions, etc.
This behavior is different from the ldap_imports group where users are always placed into that group when an LDAP import takes place.
|SIPX-124||A page refresh is needed after editing a chat room||An issue was fixed that caused newly created to be displayed incorectly in the list of chat rooms. A page refresh was required to display the new room.||Fix|
|SIPX-122||Wrong label under unmanaged services for DHCP||In DHCP Service configuration the check box for 'Unmanaged' read 'Unmanaged DNS'. Corrected to read 'Unmanged DHCP'.||Fix|
|SIPX-170||Restore of userProfile collection does not work properly when restoring on the same machine||Fixed an issue with Restore where the restore to the same machine, after a user change, did not properly overwrite the newer settings with the settings from the restore. Still important to send server profiles after restore.||Fix|
|SIPX-174||MongoDB crashed upon logrotate||Fixed an issue with MongoDB when used on a regional node. Related to MongoDB Bugs https://jira.mongodb.org/browse/SERVER-15643 and https://jira.mobgodb.org/browse/SERVER-11087||Fix|
|UC-3535||Investigate call_direction in CDR / sipXcallresolver||Customer noticed that data was not being recorded to the call_direction field of SIPXCDR. Engineering requested a JIRA to investigate sipXcallresolver configuration in this area.|
In the code (the cdr scripts) the call_direction field is never populated.
In the cdr scripts it is declared like this: "# call_direction char(1) Plugin feature see below ", but is never mentioned again.
In the sipXcom wiki only info on this field is : 11. call_direction Direction of the call
Two interesting discussions were found about call_direction are here:
Updated the following Wiki Pages: