SMGR 10 : SIP users migrated from the older version responding 403 Forbidden auth failure when login, while the newly created user works fine

Doc ID    SOLN386814
Version:    1.0
Status:    Published
Published date:    27 Jul 2026
Author:   
Parthiban Kalisamy
 

Details

403 Forbidden Authorization Failure - reported by the SIP users that are migrated from the R8 SMGR.
SMGR, SM are upgraded to R10.x
SMGR CA
 

Problem Clarification

SMGR/SM are upgraded from R8.1 to R10.x and post which the existing sip users report "403 Forbidden (Authorization Failed)" noted at the traceSM.
At the same time, if a SIP user are cloned from the same problem reported user - is able to login success at the same endpoint.
Also the newly created users at the R10 are all working fine.

│◄─────────────REGISTER─────────────│(111) <sip:[email protected]> Exp:3600
│───────────Unauthorized───────────►│(111) 401 Unauthorized
│◄─────────────REGISTER─────────────│ (111) <sip:[email protected]> Exp:3600
 │──Forbidden (Authorization Failed─►│ │ (111) 403 Forbidden (Authorization Failed)

User registration request contains the correct domain, station config are valid, Communication profile passwords are reset as well at the problem user.
At the csuser db table also, the user type exists as "local".

Cause

Its of known issue at the database that the csuser table need to updated for the parameter, "userupdatedatetime" to the current date/time to overcome this '403 Forbidden' logon failure if reset of the parameters like 'domain', station config, communication profile passwords are valid.

Solution

SMGR postgres DB update at csuser table to be performed as below - 

update csuser set userupdatedatetime =now() where loginname IS NOT NULL;
update csuser set updatedatetime =now() where loginname IS NOT NULL;
 

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy