Closed stemid closed 8 years ago
@sii feel free to chime in on this issue because I think you've seen it before. Fredrik B told me he has discussed it with you.
An untested workaround would be to delete the user from Siptrack and do another sync with the AD.
This workaround has been reported to work in the past but we did not try it this time.
Have a user with three previously connected sub keys but trying to connect any other key to that user now results in no errors and no connected keys.
Have also tried through the API so I believe this is a siptrackd issue.
Will assign to myself since I have access to the DB.