Question: Why does Microsoft Office Communicator not work after an upgrade to ArubaOS 3.4?  Nothing else has been changed, and traffic is allowed in the role.
Product and Software: This article applies to all Aruba controllers and ArubaOS 3.4.x.
Microsoft Office Communicator uses SIP. Communicator seems to overload the SIP protocol with short messages. When many people are using Communicator, the STM voip_mgr crashes and causes the SIP traffic to be dropped. The workaround would consider SIP as other protocols without a special ALG.
Why was Communicator working before the upgrade?
In ArubaOS 3.3.2.x, if we issue this command:
Disable stateful SIP processing. Default option is disabled.
In ArubaOS 3.4.x, if we issue this command:
Disable stateful SIP processing. Default is enabled.
To overcome this problem, issue this command:
conf term firewall disable-stateful-sip-processing
Note: This command causes the Aruba controller to treat SIP as any other UDP/TCP traffic.