Pepp77
chec out the help files for services (it is a much forgotten feature since broadband took over the world)
in its most basic it is simply a matter of filling in the blanks & setting up an IP route to use it.
you can get much more complicated as well for example channel bonding & Dialback (where the remote system calls you back to complete the connection).
I once used this to demonstrate to a customer that it was his data link that was killing SCN not the IPO
FTP://aware.servebeer.com/pub/IPOffice_1.cfg is the bare minimum needed to connect to a default IP office.
I have used 192.168.99.1 fro the Lan 1 IP address so there is no need to force IP address if the remote unit does not have DHCP enabled
I would also recommend increasing the default timeouts & switching off "Do Not Keep Link Up for Incoming Traffic" in the PPP tab if you don't want the connection to drop half way through downloading a large config or when running a trace.
(this may be the cause of Paulos' problem)
I have over 400 services in my IPO, one limitation I have found is it current firmware (in fact anything V1.4 and above!) does not like more than 98 IP routes - an old 403 running V1.2 firmware did not seem to have this limitation but a 412 is probably better as it has pace for a bigger cfg.
Do things on the cheap & it will cost you dear