Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
As the other posters have noted, if source and destination attributes are the same, for Etherchannel, the same link will be used. As Daniel noted, some (often the higher end models) switches, within their hashing algorithm choices, also support L4 ports, but unless ports differ between flows, again the same link will be used.
If your hosts can be multi-homed, i.e. multiple IPs, that could allow different flows to use a different Etherchannel link.
Something to also keep in mind, Etherchannel doesn't do dynamic load balancing. Even if you have different attributes, multiple flows can be sent to the same link. For example, first flow saturates one link. Second flow, is "sent" to the same, already saturated, link, while second link is unused.
When possible, "faster" link is often the better solution (this is one reason why often uplinks ports have higher bandwidths).
If you're using routers, rather than switches, something like OER/PfR can dynamically load balance across your links.
