Bug: Forwarding rule to "Same as External Calls"

Status
Not open for further replies.

giwm

Forum User
Joined
Sep 27, 2016
Messages
279
Reaction score
51
15.5 SP1

Under Forwarding Rules, when setting an exception with the rule, "Same as External Calls", you get the following error when trying to hit OK:

Code:
TCX.Configuration.Exceptions.ObjectSavingException: Commit failed on transaction Save Extension.276 - '1030'
   at TCX.Configuration.PhoneSystem.WBatchUpdater.Commit()
   at TCX.Configuration.Extension.DoSave(WBatchUpdater updater)
   at TCX.Configuration.DN.Save()
   at ConfigurationManagementModel.CfgExtensionEditor.Serialize_AfterSerialize(Object sender, SerializeEventArgs e)
   at ConfigurationManagementModel.PropertySerializer.Serialize(ICfgItemInternal cfgItem, SerializeParameters serializeParameters)
   at ConfigurationManagementModel.CfgItemBase.Save()
   at ManagementConsoleJS.Services.Editor.Save()
   at ManagementConsoleJS.Services.EditorService.SaveActiveObject(Int32 id)
   at ManagementConsoleJS.Controllers.EditController.Save(Int32 id)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at ManagementConsoleJS.Middleware.ExceptionWrapperMiddleware.d__3.MoveNext()
 
I see same issue on 15.5 SP1 with Windows OS.
 
Thank you for reporting this. We will investigate the issue and report back once we have an update.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,873
Messages
589,496
Members
164,719
Latest member
David Gharakhanian