How to identify HTTPS-tunneled SDP traffic for F5 proxy'ing

How do I get an F5 server to recognize Dimensions CM Desktop client HTTPS traffic
so that the SDP contents tunneled inside of those HTTPS connections can be routed to the Dimensions CM Listener service?

My CM Desktop client
"Server:" connection field is like this:

My web server hosts Dimensions CM, Dimensions RM, and SBM products, so I can't simply route all HTTPS traffic to the Dimensions CM listener service.
I have to figure out how to distinguish between the CM Desktop Client (tunneled SDP) traffic and the rest of the HTTPS incoming traffic.

Surely there must be something unique about SDP protocol traffic that F5 can use to identify which 443 inbound traffic to route to the Dimensions CM Listener service.

-Joshua Trosclair