Support for more than 32 IPs/SIP SAPs

We came across a limitation (around mid 2020) since earlier versions that still persists, that is the limit of how many SIP SAPs are supported.

SipAddIpInterface: Failed to allocate IP interface context


Even being able to create more than 32 IP interfaces, when activating the configuration only the first 32 really come up and respond/bind to the SIP stack, with the others showing the error above.

This became a major problem for using ProSBC to SIP Interconnects that use routes defined by IP pairs requiring use of several different IP addresses.

So our demand is to increase the quantity of IPs supported to something arround 1024 or as high as possible. Anything above 128 should help right now.