I thought NW 5 shipped with NIAS 4.2, but either way....
You need to run TCP/IP on the LAN with addressing in the _private_ networks. Then you can enable TCP/IP routing in INETCFG. You also have to enable NAT and configure it for DYNAMIC translation. You're client PC's need to have your NW server as their default gateway and you NW server needs to have a default route specified within the TCP/IP option of INETCFG. Once you have the default route setup, you shouldn't have to use CALLMGR to establish that call. It should puch up the line when traffic is sent to the server destined for any Internet site. You'll probably want to adjust your connection timers in INETCFG as well to keep the line up during periods on inactivity.
I haven't done this with a dial-up connection in quite a while, but it will work.