I am trying to cope with the dreadful experience of configuring a CSS 11050 to load-balance H.323 RAS traffic (UDP on port 1719) on a Cisco IOS gatekeeper group.
CSS is configured with a single content rule matching on protocol characteristics. The problem comes out as there's only one centralized client on the "public" network, referring to CSS.
In a nutshell, under continuous traffic condition a flow is created (identified by the mentioned client, the VIP address and protocol type/socket) and RAS traffic ( note: any single UDP packet received by CSS refers to a different RAS session ) remains "stuck" on the first available service, as the flow has not enough time to expire.
In cases of low traffic (the flow can expire) load-balancing is correctly performed.
Is there a way to prevent CSS from creating a flow for custom traffic patterns, so that every single received packet be delivered to a different service using any load-balancing algorithm ?