Check Point Blocking H323 Traffic (Part 2) - Explained

Hi all.  Today I wanted to go back to my first post that I put on this site:  http://www.shanekillen.com/2011/11/check-point-blocking-h323-traffic.html

I had stated a problem and solution, but I didn't really know why the solution was what it was.  Well, I happen to have a pretty good SE in my area now (one I actually have confidence in), and he explained to me why I had the problem that I had.  This below is what he wrote to me, and I thought Id put this out there for anyone interested.  Here is his explanation, which I happen to think is a very good one.  

Quote:

I can tell you why this worked. Most likely, the H.323 service was not defined as a "Match for Any" service. When you said you had a rule allowing "ANY" traffic, it's not really allowing *everything*. It's allowing a class of services that are allowed to "Match Any".

So if you go to the Service properties for H.323 in R75.20 you'll see that the Match for Any is selected. This means it will match the "Any" service designation. I'm betting in your case it wasn't selected.

There is a reason Check Point does this and it has to do with it's protocol inspection.
  End Quote.

Well, he was right on this.  I didnt have that service as a "Match Any".