It looks good, but what about ports 20480 and 82? Do the Nortel cards only do proprietary signaling, or is there some protocol like h.323 running as well? Just in case, below is an access list that catches a lot of the standard voip signaling protocol ports.
The af31 should catch a lot of the control traffic because you should be marking it on the gateways, who knows, maybe Nortel marks it that way too. But if there is something that was overlooked or somethings that cannot mark with dscp, then the rest of the list should suffice to catch everything else. Rule 2 is SCCP signalling for Cisco ip phones. Rules 3 and 4 are MGCP signaling. Rules 5 and 6 are h.323 signaling, I think.
You might want to be more specific with your access list, so that only traffic coming from a certain address and going to a certain address or network will be considered. That is what I have done in the access list here.
You probably need more bandwidth for signaling. Does anyone have a voip signaling bandwidth calculator? Or is there a good way to tell how much is needed? I don't know, I might allocate 32 k for signaling if you are doing 768k worth of voice traffic, but then, that depends on what codec you are using. Etc, etc.
Unless you have time-sensitve data traffic in your class-default, you should do wred on that class. I think you can implement the feature by typing "random" on the class-default.
access-list 101 permit ip 10.62.25.0 0.0.0.255 any dscp af31
access-list 101 permit tcp 10.62.25.0 0.0.0.255 any eq range 2000 2002
access-list 101 permit udp 10.62.25.0 0.0.0.255 any eq 2427
access-list 101 permit tcp 10.62.25.0 0.0.0.255 any eq 2428
access-list 101 permit tcp 10.62.25.0 0.0.0.255 any eq 1720
access-list 101 permit tcp 10.62.25.0 0.0.0.255 any eq range 11000 11999
