View Single Post

  #3 (permalink)  
Old 16-12-2006, 18:37
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:[color=blue]
> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
>
> [Snip]
>[color=green]
> > 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.[/color]
>
> [Another snip]
>[color=green]
> > 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.[/color]
>
> 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.[/color]

Unimportant. right now I can't access it with or without a password.
[color=blue]
> 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>.[/color]

Been there; done that.
[color=blue]
> Does any of that work? No. Have another cup of coffee.[/color]

Drat. I left out the steps with the coffee.
[color=blue]
> Brian.[/color]

Reply With Quote