Just a few additional notes, on what Mark has posted.
Is your ISP providing you just one or multiple networks? If just one network, you would only need to use one VLAN for you hosts, and you would configure hosts ports without a voice VLAN and your uplink port wouldn't be a trunk.
If multiple networks, your VoIP phones would need to support using the voice VLAN. If not, you may need to configure some ports in just the data VLAN and some ports in just the voice VLAN.
Mark shows enabling portfast and bpduguard on host ports, which is typical (and often a good thing), but some Cisco switches allow setting these as global options (which reduces configuration clutter somewhat, and also avoids forgetting to set it on host ports).
For the uplink trunk port, you might want to define the encapsulation mode as dot1q.
Mark also mentions the Aruba might need their ports defined as trunks. This too assumes your ISP is providing/supporting multiple networks, but even if they do, some WAPs will tunnel back to their controller, and their edge port only needs to be configured as just another host port.
Lastly, your 3650 is a L3 switch. If you do have multiple LAN networks, and you expect to pass traffic between your local hosts, on different networks, the 3650 might be able route between your networks much, much faster than the ISP router. Using it that way, though, may require coordination with your ISP.
