How to get a backup from a remote system
How to get a backup from a remote system
(OP)
Hi all,
I have *zero* knowledge of Sopho's, but have the POMView app.
I know how to get details out of many, many other PABX's, but have never encountered a Sopho before.
Can someone (in simple steps) explain how I can;
1. Remotely access an iS3000
1a. What software I need (if any) and where I can download it.
2. How to get a 'project' file out of the Sopho back to my machine remotely
and
3. Will the POM view show me what's in there - I'm interested in Phones, Groups, Trunks and Route plans (mainly)
Alternatively, is it easier to just connect over a modem and run lots of scripts (as I have in the past for Nortels, Avaya's, BTeX's etc.)
Cheers,
Paul
I have *zero* knowledge of Sopho's, but have the POMView app.
I know how to get details out of many, many other PABX's, but have never encountered a Sopho before.
Can someone (in simple steps) explain how I can;
1. Remotely access an iS3000
1a. What software I need (if any) and where I can download it.
2. How to get a 'project' file out of the Sopho back to my machine remotely
and
3. Will the POM view show me what's in there - I'm interested in Phones, Groups, Trunks and Route plans (mainly)
Alternatively, is it easier to just connect over a modem and run lots of scripts (as I have in the past for Nortels, Avaya's, BTeX's etc.)
Cheers,
Paul
Talk To Other Members
RE: How to get a backup from a remote system
RE: How to get a backup from a remote system
SSW 810 (CPU3000)
(remote) access via telnet for management (if activated)
OR/PR.pom files are present inside the CPU disk accessible via FTP (user/password request)
SSW805 (CPU-MT) only via V24
but if you are not familiar with Sopho ...................
PS: Pomview APP it is only used to display data reading file .pom
RE: How to get a backup from a remote system
DIDNRC:000&&9999; [assuming you don't even know if extension numbers are 3 or 4 digit, takes some time...]
DIGRPA:000&&9999; [same principle, will give you the groups]
DIBNDL:0;
and
DIBNDL:1;
etc until you don't find any more info - will show the trunks if it's a small system with trunks assigned "from bottom"
"Route plans" (for any meaning of that) is more difficult, but you should see route numbers in the DIBNDL printouts and may issue DIROUTE-commands accordingly. This way you will not see what access code leads to which trunk, though.