Remote virtual queueing with IP-NIQ is very flexible:
At the remote sites, you'll usually have (virtual) trunk group for incoming IPNIQ-calls.
For this trunk group you create DNIS-entries pointing to CCTs (business as usual).
Within the CCTs you'll use an "accept interqueue" step, followed by the usual "select agent" steps to queue the calls virtually at that site.
At the originating site
you setup the remote nodes and (if desired) "routes" which can contain multiple sites (even the local site)
In your CCTs for the physical calls you'll use a "IP Network Interqueue" step, specifying a single remote node or a route (containing multiple sites) and a virtual DNIS to be dialed. These DNIS digits will decide which CCTs is used at the remote site(s).
That way you can initiate simultanuous virtual queueing to multiple remote sites by specifying DNIS digits. How these requests are treated is defined by the DNIS-entries and the CCTs at the remote sites.
There you have all the possibilities offered by schedules, IF steps, calculations, ANI-routing and so on, completely independant from the originating site or members of the same route.
Hope this helps,
Chris