On Sat, 16 Dec 2006 22:42:50 UTC, "Graham" <me@privacy.com> opined:[color=blue]
>
> "Stan" <SPAM_FOILER@some.domain> wrote in message
> news:uViCr8LlbtmJ-pn2-3KdgSqX3hvdV@poblano...[color=green]
> > On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:[color=darkred]
> >> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
> >>
> >> [Snip]
> >>
> >> > I had never filled in an administrative password for the device, but
> >> > had found that the string "password" was the default that enabled me
> >> > to bring up the PAP2T configuration screens. The reaction of the voice
> >> > to this was "Invalid password". I then tried the four-digit numerical
> >> > password that iConnect issued me. This produced a continuous tone in
> >> > the telephone handset, which never stopped until I hung up. After
> >> > that, even the "****" code doesn't work (no feedback tone in the
> >> > handset receiver), so that the device is totally dead in the water. My
> >> > fear, of course, is that the PAP2T is now a paperweight and nothing
> >> > more.
> >>
> >> [Another snip]
> >>
> >> > If somebody knows a way that I can actually reset the thing, or even
> >> > just to undo the most recent step, which would give me a little hope,
> >> > I would be most happy and grateful. Needless to say, I would then seek
> >> > another solution to the communication problem.
> >>
> >> I thought the Sipura 2000/PAP2 came unconfigured without any passwords
> >> and, in any case, resetting the unit with **** 73738# or **** 877778#
> >> didn't require one. Maybe things have changed since I got mine.
> >>
> >> Anyway, to give you something to try: disconnect the router from the
> >> internet and switch off the PAP2. Have a cup of decent coffee.
> >>
> >> Reconnect to the power supply but not to the internet. Try **** 110# to
> >> see what the ATA thinks its IP is. If there is a response contact the
> >> unit with http://<PAP2 IP>.
> >>
> >> Does any of that work? No. Have another cup of coffee.[/color]
> >
> > I still haven't done the coffee bit yet, but I have run through the
> > entire reset process once more. The situation is a little different
> > now.
> >
> > The two rightmost LEDs (Power and Ethernet) are now on steadily;
> > formerly, Power blinked once per second. I think this shows that the
> > device sees the 'Net. It also verifies the device's LAN settings.
> >
> > I am still unable to see the configuration screens with the browser --
> > http://<device's IP address> times out. Therefore I can't set such
> > details as DNS addresses, which would enable me to connect with a
> > service provider.[/color]
>
>
> Does ****110# confirm the IP address as being what you think it is?[/color]

Yes.