On 11 September 2026 Avaya published product support notice PSN006499u (severity: medium): in SBCE (Session Border Controller for Enterprise) 7.1.x and 8.x systems, the SSL/TLS certificate used by default for the PostgreSQL database expired on 7 September 2026.
1. What happened
The PostgreSQL database inside SBCE uses an SSL/TLS certificate to secure encrypted communications between components. It is the default certificate generated automatically at deployment, with a ten-year validity starting in September 2016, which brings it to expiry on 7 September 2026.
Once the certificate expires, TLS certificate validation fails. The system is still running and looks normal because existing connections have not yet re-triggered validation. Avaya explicitly warns that the following situations will set the problem off:
After a server or PostgreSQL service restart, the database may fail to start; database connections and daily operations on the EMS and SBCE are affected; and adding servers or nodes to an existing deployment fails because certificate validation fails.
In one sentence: being fine on the expiry day does not mean you are fine; the fuse is the next restart.
2. Who needs to act and who can relax
| Situation | Affected? | What to do |
|---|---|---|
| SBCE 7.1.x / 8.x that has never had its database certificate replaced | Affected | Contact your service provider as soon as possible |
| SBCE 7.1.x / 8.x already using a valid certificate issued by a third-party CA | Not affected | No action needed |
| Other SBCE releases, or deployments without SBCE | Outside the scope of this notice | Worth confirming certificate status while you are at it |
| Note that whether the default certificate is in use, and its exact expiry date, can only be confirmed by an engineer logging in to the system; it is not visible on the management interface. That is exactly why we recommend having your service provider check. |
|---|
3. How to fix it
Avaya provides a dedicated certificate update tool and the path is clear: the partner engineer logs in to the EMS and SBC devices, runs the official patch tool to replace the database certificate, restarts the services and confirms each process returns to normal. Avaya also documents how to verify the updated certificate.
Two reminders:
Take a system backup before starting (the official Patch Notes require it) and store it externally. The work itself is simple, a small piece of preventive surgery, but if it is left until a power cut takes the database down and a recovery becomes urgent, the troubleshooting detours and business interruption are on a completely different scale.
Closing note
The notice rates the risk only as medium and gives a handling window of when convenient. Note, though, that the trigger is precisely an inconvenient moment: an unplanned power cut or a failure restart. Replacing the certificate now, while the system is healthy, takes that medium risk to zero.
If you are not sure whether your SBCE uses the default certificate, please contact us to check.

