High queued data amounts during busy hours using SIP over TLS

Hi guys,

Last year we had several issues with a customer using SIP over TLS in an Access implementation of a HA NN4500 SBC node.

During busy hours the SBC node was showing very high queued data amounts (above 100K) and the TLS subscribers were loosing registration and service whenever such event was present.

We openned a ticket with TAC but, there were not any solution to the issue and from the TAC we just got an upgrade recommendation to its current version;

nnSCX620m12p7 and configuration to prevent DDoS for TLS.

The customer had to reduce the number of SIP subscriber and such thing was the work around by then and, this status remains the same until today.