It's not as easy as classifying it by a simple job title. Some software developers might travel whereas most won't. Some networking people will travel, but again, most won't. An experienced IT consultant will travel quite frequently in most cases, and that could be in software, networking, systems/business analysts, etc.
Traveling is required mostly for non-trivial project work. They usually encompass an entire enterprise, and as such you often need to liaise with people well outside of your normal scope. I worked on a $50M project at a Big 4 firm, and a dozen of us or more were sent literally everywhere in the world to collaborate with domain experts. A more trivial project, a project that might take less than 6 months with a small team usually is very local in its impact and thus has most of the resources it needs.
So, if you're wanting to travel I would concentrate on what is necessary to be a good consultant. This means not choosing one specialty and not isolating yourself to technical minutiae; interact with the business and sharpen your soft skills, market them and prepare to wear as many hats as possible.