85 - CM - Increase SIP transaction log size
closed
Sam Osheroff
In CM 8.1 the SIP transaction table holds 10K entries, each for 32 seconds after the dialog ends (before being removed). Since CM supports 30k SIP stations, the SIP transaction table size should be increased. This mostly comes into play when a large number of SIP stations register to SM and send SUBSCRIBE messages for avaya-cm-features and MWI. This might occur during the recovery from network outage, power outage or Session Manager outage/maintenance.
When the table size limit is reached, CM initiates a WARM 1 restart. If that doesn't resolve the issue, a second WARM 1, followed by an interchange occurs.
IAUG
closed
The IAUG volunteer committee has discussed this with Avaya at various times over the last few years. We recognize that the original problem submitted has been resolved, but there was still discussion of increasing the size of the SIP transaction tables.
In our discussions, Avaya articulated that the SIP transaction limit of 10K has been tuned in accordance with the other limits in Communication Manager architecture, such as Call-Ids. Changes to SIP transaction would require changes to Call-Ids and other core parameters, which is a major change. They are not considering this change for the CY2025 roadmap.
Avaya Responses
planned
Avaya Responses
This request will be considered for a future release.
S
Slade Besson
FR#85 - Submitted to Avaya 7/17/2020