View Single Post

  #6 (permalink)  
Old 17-12-2006, 01:53
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
[color=blue]
> I was very careful to be precise in key-entry, and reviewed the
> settings twice afterward, before saving them. The settings for my LAN
> (IPaddress, subnet mask, gateway address etc. are unchanged and
> undisturbed, of course, from their content with VOIPcheap.
>
> I then, according to Paragraph IV of the instructions, logged on to
><http://www.icallhere.com>, using my iConnect ID and password. What
> stopped me cold was the next step, which is "Click 'Go to my
> devices'", because the menu on that page contained no such item. I
> attempted then to return to the PAP2 configuration screens, and found
> that I was no longer able to communicate with it at all.[/color]

Part of the setting up process includes allowing remote provisioning of
the ATA. I've no detailed insight into what happens but the rl-init.cfg
would seem to configure some of the PAP2's parameters to suit the
iconnecthere service. But IP addresses etc are not touched. Name servers
are altered but that shouldn't matter. A change to the firmware is a
possibility.

I cannot see the provisioning being other than benign but have read that
interupting the process by, for example, disconnecting the ATA from the
power supply, can leave the ATA in an unusable state. Also, unlocked
units tend to be locked again. Nothing like that applies here, does it?

Brian.
Reply With Quote