On Sun, 17 Dec 2006 16:24:55 UTC, Brian <bandj@o2.co.uk> opined:
> On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:
>
> > On Sun, 17 Dec 2006 14:28:14 UTC, Brian <bandj@o2.co.uk> opined:
> >> ****7932#
Now that the discussions of beverages and of the virtues of a system
of weights and measures based on the anatomy of long-dead kings are
over, and I have had the opportunity to read some of the Sipura User
Guide (which I never saw before -- the "improved" Linksys version is
much inferior, and I had not read it throughly, to tell the truth), I
think
I can present the current state of affairs in a more organized way:
I have tried to apply the above code (which is, by the way, not a
toggle: it enables or disables explicitly, according to 1 or 0
confirmation, which is much more logical). It doesn't work, because it
requires a password. The IVR asks for one, and I don't know what it
is.
So I began again, and reset the device with "73738". According to the
list in the User Guide, this is a total factory reset, so I expected
everything to be erased. In fact, the DHCP had been returned to its
default "enabled" state, and I had to disable it. After that, I found
that the pre-existing values for static IP address, gateway address,
subnet mask, and primary DNS are all intact, which surprised me.
After hanging up the handset, I tried again to use 7932 (to ensure
that the web server is enabled), and was asked for a password. I don't
know a password, never having set one, put tried "password"
(=72779673), which IVR declared invalid. I discovered that even the
code 111 requires a password now, which it never did before.
I can hang up, check the IP address, and repeat this cycle any number
of times, and always find the IP has survived. But if I use code 111
to try to change it, and then hang up, code 111 tells me that the IP
address is 0.0.0.0. After this, of course, there is no request for
password, and the attempt to access the configuration screens simply
times out. This goes a long way toward explaining why I have sometimes
reported the request for password from the browser attempt and
sometimes not. It is also incomprehensible as a way for the device to
react to an unauthorized action.
After I wrote all of the above, I chanced upon a list of common
factory passwords that one can expect to find on PAP2 ATAs, to wit:
78196365
50274537
7756112
8995523
5465866
I haven't time to check these out right now, but I will do so at the
first opportunity.
> >
> > Would you please elaborate on what this code does? Enable, disable, or
> > toggle? Where is there a listing of such codes? The only ones I know
> > about are the three-digit ones for setting up the IP addresses, etc.
> > (I got 73738 from Linksys support)/
>
> Toggle. It also drip feeds strong espresso to the homunculus. Try it. No
> harm can be done. Not the ATA anyway.
>
> The ATA User Guide at http://www.sipura.com/support/index.htm.
>
> Brian. 
Re: A PAP2T disaster with Delta3/iConnect 
Linear Mode
