I've given a wrong answer here: viewtopic.php?f=327&t=16925&p=59704&hilit=2071#p59704
But this time my answer could match.
If the OXE creates many incidents 2071=Swap partition xx per cent full (~1 per hour) you should check the following:
-Check memory usage and identify the process consuming all the memory
-With the command 'free' or 'vmstat' the system shows you the memory and Swap usage.
-The used swap size should not too big. Just some MB. 200 MB and more are too much.
It could be that the sipmotor process is your problem.
Check with 'top -b -n1'-command...
If possible, you could try a sipmotor restart (killall sipmotor) but careful - SIP calls will be dropped...
If the sipmotor is really the bad guy, I suggest you to contact ALU Tech Support and tell them to assign your issue to the eSR 1-117422071 as duplicated one...