Go Back   Wireless and Wifi Forums > News > Newsgroups > uk.telecom.voip
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 12-16-2006, 10:55 AM
Stan
Guest
 
Posts: n/a
Default A PAP2T disaster with Delta3/iConnect

After this forum gave me a great deal of help in setting up my PAP2T
for VOIPcheap, I was able to use it with that service, but found that
payment options were rather limited (I was not able to simply use my
credit card), and so decided to give Delta3 (iConnect) a try. The only
possibilities for using one's own ATA with iConnect are the PC2Phone
plans, and I took the cheapest of these ($5.95 for 400 min/month) as
an experiment. The experiment has ended in disaster, though I am able
to make calls from a PC.

Delta3 did not give me instructions for setting up the PAP2T, but I
found their page at
<http://corp.deltathree.com/productsa...pap2_instructi
ons.html>, which were simple enough to follow.

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.

The Power LED of the ATA now blinks at a rate of 1/sec; the Ethernet
LED is on steady, but flickers with LAN traffic. Telephone access to
the Linksys Configuration Menu worked, and I checked those settings
which are accessible through that menu -- they are as they should be.
I tried to reset the device using the codes "****" + "73738#"; that
brings up a login dialog with the recorded voice, asking for my
password.

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.

I sent this tale of woe to iConnect's "Customer Care" address, and
received a long boilerplate message suitable for any and all
occasions, but totally irrelevant to my query (its first advice is to
register and pay them some money). Evidently "care" consists of not
actually reading customer questions.

I think that covers everything I know about the state of the ATA and
how it got
to it.

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.

--
Stan Goodman


Reply With Quote
  #2 (permalink)  
Old 12-16-2006, 12:16 PM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

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.

Brian.

Reply With Quote
  #3 (permalink)  
Old 12-16-2006, 04:37 PM
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:
> 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.


Unimportant. right now I can't access it with or without a password.

> 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>.


Been there; done that.

> Does any of that work? No. Have another cup of coffee.


Drat. I left out the steps with the coffee.

> Brian.



Reply With Quote
  #4 (permalink)  
Old 12-16-2006, 05:35 PM
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:
> 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.


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.



Reply With Quote
  #5 (permalink)  
Old 12-16-2006, 09:42 PM
Graham
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect


"Stan" <SPAM_FOILER@some.domain> wrote in message
news:uViCr8LlbtmJ-pn2-3KdgSqX3hvdV@poblano...
> On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:
>> 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.

>
> 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.



Does ****110# confirm the IP address as being what you think it is?
--

Graham.
%Profound_observation%




Reply With Quote
  #6 (permalink)  
Old 12-16-2006, 11:53 PM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:

> 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.


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
  #7 (permalink)  
Old 12-16-2006, 11:59 PM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:

> On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:
>> 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>.

>
> Been there; done that.


Change the phone and connecting cable? Yes, I know it has worked
previously but......

Brian.

Reply With Quote
  #8 (permalink)  
Old 12-17-2006, 06:52 AM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 00:59:44 UTC, Brian <bandj@o2.co.uk> opined:
> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
>
> > On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:
> >> 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>.

> >
> > Been there; done that.

>
> Change the phone and connecting cable? Yes, I know it has worked
> previously but......


The cable is good: the Ethernet LED flickers with LAN traffic.
The phone is good: I can check and set the settings of the device.

> Brian.



Reply With Quote
  #9 (permalink)  
Old 12-17-2006, 06:52 AM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sat, 16 Dec 2006 22:42:50 UTC, "Graham" <me@privacy.com> opined:
>
> "Stan" <SPAM_FOILER@some.domain> wrote in message
> news:uViCr8LlbtmJ-pn2-3KdgSqX3hvdV@poblano...
> > On Sat, 16 Dec 2006 13:16:51 UTC, Brian <bandj@o2.co.uk> opined:
> >> 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.

> >
> > 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.

>
>
> Does ****110# confirm the IP address as being what you think it is?


Yes.


Reply With Quote
  #10 (permalink)  
Old 12-17-2006, 06:52 AM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 00:53:35 UTC, Brian <bandj@o2.co.uk> opined:
> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
>
> > 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.

>
> 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.


That's exactly what I am afraid of. See my original description above.
The experience with the provisioning site was also the point at which
it became impossible to view the configuration screens, or to
otherwise communicate with the device.

Reply With Quote
  #11 (permalink)  
Old 12-17-2006, 11:17 AM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:

> On Sun, 17 Dec 2006 00:53:35 UTC, Brian <bandj@o2.co.uk> opined:
>> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
>>
>> > 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.

>>
>> 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.

>
> That's exactly what I am afraid of. See my original description above.
> The experience with the provisioning site was also the point at which
> it became impossible to view the configuration screens, or to
> otherwise communicate with the device.


You could go through the whole process again in an attempt to get the
PAP2 recognised by iConnect. If it is the cause of your problems you
have little to lose.

Brian.

Reply With Quote
  #12 (permalink)  
Old 12-17-2006, 11:35 AM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:

> On Sun, 17 Dec 2006 00:59:44 UTC, Brian <bandj@o2.co.uk> opined:
>> Change the phone and connecting cable? Yes, I know it has worked
>> previously but......

>
> The cable is good: the Ethernet LED flickers with LAN traffic.
> The phone is good: I can check and set the settings of the device.


The PAP2 responds to **** codes. You can get IP address, netmask, dhcp
status etc but cannot alter them through the IVR because it asks for a
password. Is that correct? The ATA is functional but not in the way you
want it to be. If you manage to access it with a browser the password
problem will presumably arise again.

The ATA, computer and router are all on the same subnet but web pages on
the ATA won't display. Could be the web server is disabled. I think I'm
running short on ideas here.

Brian.

Reply With Quote
  #13 (permalink)  
Old 12-17-2006, 12:41 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 12:35:37 UTC, Brian <bandj@o2.co.uk> opined:
> On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:
>
> > On Sun, 17 Dec 2006 00:59:44 UTC, Brian <bandj@o2.co.uk> opined:
> >> Change the phone and connecting cable? Yes, I know it has worked
> >> previously but......

> >
> > The cable is good: the Ethernet LED flickers with LAN traffic.
> > The phone is good: I can check and set the settings of the device.

>
> The PAP2 responds to **** codes. You can get IP address, netmask, dhcp
> status etc but cannot alter them through the IVR because it asks for a
> password. Is that correct? The ATA is functional but not in the way you
> want it to be. If you manage to access it with a browser the password
> problem will presumably arise again.


I am snowed by the terminology: if IVR is the disemboded voice from
the PAP2T, that is NOT correct. I CAN set the IP address, DHCP state,
Gateway address, and subnet mask through the telephone set and the
**** codes. I cannot access the PAP2T's configuration screens through
the browser with URL <http://192.168.1.150>, because it times out.
There is no request for a password.
>
> The ATA, computer and router are all on the same subnet but web pages on
> the ATA won't display. Could be the web server is disabled. I think I'm
> running short on ideas here.


The web server is in the PAP2T; I know of no way to enable it or
disable it.

> Brian.



Reply With Quote
  #14 (permalink)  
Old 12-17-2006, 12:41 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 12:15:45 UTC, M.Dexter@blueyonder.co.uk opined:
> On 17 Dec 2006 07:52:59 GMT, "Stan" <SPAM_FOILER@some.domain> wrote:
>
>
> >That's exactly what I am afraid of. See my original description above.
> >The experience with the provisioning site was also the point at which
> >it became impossible to view the configuration screens, or to
> >otherwise communicate with the device.

>
> Have you thought of calling Linksys support or contacting them by
> email I am sure they could tell you if your pap is totally nackered or
> not and if it can be fixed how to do it .


I have an open request for help on the Linksys support line, and the
conversation has had several iterations since the middle of last week.
They are pondering at the moment, and I will probably hear more
tomorrow.

I have also laid out the problem with iConnect support (called
"Customer Care"), which has a slower iteration cycle than Linksys.
Their first reply was a very long message consisting entirely of
boilerplate and beginning with the assumption that I am not a paying
customer (I have in fact registered, paid, and can make calls from my
notebook machine, which I told them in my initial query); that made me
furious. My response to it seems to have energized them a bit, and
they are now volunteering to provision the device with no help from
me. I don't think they can do that, and the attempt will lead to a
correspondence which will explain the problem to them much better than
I could have done without that attempt.


Reply With Quote
  #15 (permalink)  
Old 12-17-2006, 01:28 PM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:

> On Sun, 17 Dec 2006 12:35:37 UTC, Brian <bandj@o2.co.uk> opined:
>> The PAP2 responds to **** codes. You can get IP address, netmask, dhcp
>> status etc but cannot alter them through the IVR because it asks for a
>> password. Is that correct? The ATA is functional but not in the way you
>> want it to be. If you manage to access it with a browser the password
>> problem will presumably arise again.

>
> I am snowed by the terminology: if IVR is the disemboded voice from
> the PAP2T, that is NOT correct. I CAN set the IP address, DHCP state,
> Gateway address, and subnet mask through the telephone set and the
> **** codes. I cannot access the PAP2T's configuration screens through
> the browser with URL <http://192.168.1.150>, because it times out.
> There is no request for a password.


I was working on what you said in your first post:

> I tried to reset the device using the codes "****" + "73738#"; that
> brings up a login dialog with the recorded voice, asking for my
> password.


and

> 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.


>> The ATA, computer and router are all on the same subnet but web pages on
>> the ATA won't display. Could be the web server is disabled. I think I'm
>> running short on ideas here.

>
> The web server is in the PAP2T; I know of no way to enable it or
> disable it.


****7932#

Brian.

Reply With Quote
  #16 (permalink)  
Old 12-17-2006, 03:00 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 14:28:14 UTC, Brian <bandj@o2.co.uk> opined:
> On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:
>
> > On Sun, 17 Dec 2006 12:35:37 UTC, Brian <bandj@o2.co.uk> opined:
> >> The PAP2 responds to **** codes. You can get IP address, netmask, dhcp
> >> status etc but cannot alter them through the IVR because it asks for a
> >> password. Is that correct? The ATA is functional but not in the way you
> >> want it to be. If you manage to access it with a browser the password
> >> problem will presumably arise again.

> >
> > I am snowed by the terminology: if IVR is the disemboded voice from
> > the PAP2T, that is NOT correct. I CAN set the IP address, DHCP state,
> > Gateway address, and subnet mask through the telephone set and the
> > **** codes. I cannot access the PAP2T's configuration screens through
> > the browser with URL <http://192.168.1.150>, because it times out.
> > There is no request for a password.

>
> I was working on what you said in your first post:
>
> > I tried to reset the device using the codes "****" + "73738#"; that
> > brings up a login dialog with the recorded voice, asking for my
> > password.


Yes. I know this is getting confusing. To clarify: The attempt to
access the configuration screens does not get a request for password;
"****" + "73738" did ask for password (and the device was not happy
with any password I gave it), but the device appears nevertheless to
have been reset, since after the reset operation, DHCP, subnet mask,
and the IP addresses were all returned to their default conditions.

> and
>
> > 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.


That was true with the telephone that I was using (it wouldn't dial
the device, and even asterisks didn't generate audible feedback). A
different telephone did dial, and did make it possible to enter the
voice-response conversation with the homunculus inside the device.

> >> The ATA, computer and router are all on the same subnet but web pages on
> >> the ATA won't display. Could be the web server is disabled. I think I'm
> >> running short on ideas here.

> >
> > The web server is in the PAP2T; I know of no way to enable it or
> > disable it.

>
> ****7932#


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)/

> Brian.


--
Stan


Reply With Quote
  #17 (permalink)  
Old 12-17-2006, 03:24 PM
Brian
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

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#

>
> 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.

Reply With Quote
  #18 (permalink)  
Old 12-17-2006, 04:16 PM
Ivor Jones
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

"Stan" <SPAM_FOILER@some.domain> wrote in message
news:uViCr8LlbtmJ-pn2-ESFB5Gi6PdUi@poblano
> On Sat, 16 Dec 2006 22:42:50 UTC, "Graham"
> <me@privacy.com> opined:


[snip]

> > > 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.

> >
> >
> > Does ****110# confirm the IP address as being what you
> > think it is?

>
> Yes.


Is the web server on port 80..? I changed my SPA-2000 to another port for
security reasons. Try http://<ipaddress>:81 or whatever to see if it's on
that port.

Ivor



Reply With Quote
  #19 (permalink)  
Old 12-17-2006, 04:37 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

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#

> >
> > 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.


What is it with you and coffee? I thought Brits were turned on only by
tea (with cream, not sugar -- shaken not stirred), served from real
sterling silver service, and presented with funny cookies.

> The ATA User Guide at http://www.sipura.com/support/index.htm.


I've d/l it. I'll look at it tomorrow; perhaps there's even a code
there for sensing the existing state of the web server.
>
> Brian.



Reply With Quote
  #20 (permalink)  
Old 12-17-2006, 04:50 PM
Ian Smith
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

Stan wrote:

>
> What is it with you and coffee? I thought Brits were turned on only by
> tea (with cream, not sugar -- shaken not stirred), served from real
> sterling silver service, and presented with funny cookies.


Brits don't do cookies. Biscuits, maybe - and dunked.

regards, Ian

Reply With Quote
  #21 (permalink)  
Old 12-17-2006, 04:51 PM
{{{{{Welcome}}}}}
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

Thus spaketh Stan:
> 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#
>>>
>>> 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.

>
> What is it with you and coffee? I thought Brits were turned on only by
> tea (with cream, not sugar -- shaken not stirred), served from real
> sterling silver service, and presented with funny cookies.
>


I don't drink coffee, can't even stand the smell - YUK.

Now tea, I drink litres of the stuff every day, with a dash of milk and
sugar.

Rarely eat biscuits, though they are very nice.

Not often use a tea-pot, usually make the tea in the cup.

>> The ATA User Guide at http://www.sipura.com/support/index.htm.

>
> I've d/l it. I'll look at it tomorrow; perhaps there's even a code
> there for sensing the existing state of the web server.
>>
>> Brian.



--
60 day free DVD rental: www.southeastbirmingham.co.uk/dvd
Mobile Offers: www.southeastbirmingham.co.uk/payg
Items for sale: www.dodgy-dealer.co.uk


Reply With Quote
  #22 (permalink)  
Old 12-17-2006, 05:28 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 17:50:14 UTC, Ian Smith
<news2006REMOVETHIS@orrery.e4ward.com> opined:
> Stan wrote:
>
> >
> > What is it with you and coffee? I thought Brits were turned on only by
> > tea (with cream, not sugar -- shaken not stirred), served from real
> > sterling silver service, and presented with funny cookies.

>
> Brits don't do cookies. Biscuits, maybe - and dunked.


That's good to know. Thank you...

--
Stan



Reply With Quote
  #23 (permalink)  
Old 12-17-2006, 07:38 PM
Ivor Jones
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect



"Ian Smith" <news2006REMOVETHIS@orrery.e4ward.com> wrote in
message
news:45858357$0$8745$ed2619ec@ptn-nntp-reader02.plus.net
> Stan wrote:
>
> >
> > What is it with you and coffee? I thought Brits were
> > turned on only by tea (with cream, not sugar -- shaken
> > not stirred), served from real sterling silver service,
> > and presented with funny cookies.

>
> Brits don't do cookies. Biscuits, maybe - and dunked.
>
> regards, Ian


On the subject of coffee, it should be freshly ground, none of this
instant stuff..!

Oh, and strong enough to stand your spoon up in..!

Ivor

PS I'm not "a Brit", I'm British - there's a difference..!



Reply With Quote
  #24 (permalink)  
Old 12-17-2006, 07:40 PM
Ivor Jones
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

"{{{{{Welcome}}}}}" <bhx___spam@trapped___hotmail.co.uk>
wrote in message
news:Tsfhh.17880$k74.1557@text.news.blueyonder.co. uk

[snip]

> I don't drink coffee, can't even stand the smell - YUK.


Ah, you are missing out on one of life's greatest pleasures, even greater
than that of baiting Dexter ;-)

> Now tea, I drink litres of the stuff every day, with a
> dash of milk and sugar.


Litres..? Are they those funny foreign measurements..?

Ivor



Reply With Quote
  #25 (permalink)  
Old 12-17-2006, 08:26 PM
{{{{{Welcome}}}}}
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

Thus spaketh Ivor Jones:
> "{{{{{Welcome}}}}}" <bhx___spam@trapped___hotmail.co.uk>
> wrote in message
> news:Tsfhh.17880$k74.1557@text.news.blueyonder.co. uk
>
> [snip]
>
>> I don't drink coffee, can't even stand the smell - YUK.

>
> Ah, you are missing out on one of life's greatest pleasures, even
> greater than that of baiting Dexter ;-)
>
>> Now tea, I drink litres of the stuff every day, with a
>> dash of milk and sugar.

>
> Litres..? Are they those funny foreign measurements..?
>
> Ivor



Just as funny as the foreign measurements this country had been using
for a while before? Though don't let Dexter know!
The old 'imperial' system came from France and Italy!

Sorry, was brought up on metric and was only taught metric. :-)


--
60 day free DVD rental: www.southeastbirmingham.co.uk/dvd
Mobile Offers: www.southeastbirmingham.co.uk/payg
Items for sale: www.dodgy-dealer.co.uk


Reply With Quote
  #26 (permalink)  
Old 12-17-2006, 09:02 PM
Dave Higton
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

In message <BCihh.18062$k74.8072@text.news.blueyonder.co.uk >
"{{{{{Welcome}}}}}" <bhx___spam@trapped___hotmail.co.uk> wrote:

> Sorry, was brought up on metric and was only taught metric. :-)


I was brought up on the Imperial system. Then, in my teens, I
discovered how much easier the metric system makes life.

I've spent these last 40-ish years using the metric system, and
I wouldn't like to go back to Imperial!

Dave

Reply With Quote
  #27 (permalink)  
Old 12-17-2006, 09:03 PM
Stan
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

On Sun, 17 Dec 2006 20:40:16 UTC, "Ivor Jones"
<ivor@despammed.invalid> opined:
> "{{{{{Welcome}}}}}" <bhx___spam@trapped___hotmail.co.uk>
> wrote in message
> news:Tsfhh.17880$k74.1557@text.news.blueyonder.co. uk
>
> [snip]
>
> > I don't drink coffee, can't even stand the smell - YUK.

>
> Ah, you are missing out on one of life's greatest pleasures, even greater
> than that of baiting Dexter ;-)


A REAL man makes his tea from Turkish coffee.

> > Now tea, I drink litres of the stuff every day, with a
> > dash of milk and sugar.

>
> Litres..? Are they those funny foreign measurements..?


Worse than funny. To use them, you have to know how to multiply and
divide by ten. They are insidious -- the integrity of the British
currency would be threatened if just anybody could figure out what the
Hell a Guinea is. Much better that one's weight is described as e.g.
twelve stone and 37 pebbles.

--
Stan


Reply With Quote
  #28 (permalink)  
Old 12-17-2006, 09:13 PM
Ivor Jones
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect



<M.Dexter@blueyonder.co.uk> wrote in message
news:66fbo2ddlfbieepts826uslmkbd4983oek@4ax.com
> On Sun, 17 Dec 2006 20:40:16 -0000, "Ivor Jones"
> <ivor@despammed.invalid> wrote:
>
>
> >
> > Ivor
> >

> No they are a unit of measurement what all Europeans use
> oh do forgive me you aren't a European are you Ivor .


At last he sees the light..! There is hope for you yet Ron.

Ivor



Reply With Quote
  #29 (permalink)  
Old 12-17-2006, 09:47 PM
{{{{{Welcome}}}}}
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect

Thus spaketh M.Dexter@blueyonder.co.uk:
> On Sun, 17 Dec 2006 21:26:57 GMT, "{{{{{Welcome}}}}}"
> <bhx___spam@trapped___hotmail.co.uk> wrote:
>
>
>> Sorry, was brought up on metric and was only taught metric. :-)

>
> In that case you should have attended school in the days when teachers
> taught children instead of sitting around watching children playing on
> computers all day long and collecting a massive salary for doing it .



It was only in the last 3 years of my schooling that computers were
brought in, and for the first year it we could only use them during
lunch time and after-school activities.

There were a ZX81, Tandy TRS80, BBC B and Commodore PET.

The last two years we had two lessons that required the use of the
computers.

My first actual computer which I spent some of my money that was left to
me when my Dad passed away was a Commodore 64.

It was through my C64 that go me into computers and this is what I have
been working in ever since.

In my first job the company had just upgraded their PCs to 8MHz ones.

I enjoy cooking too, and can remember the book we used throughout the
two years for our exams was metric only and the book was printed in
1968.

That's not to say I don't know the imperial system, but out of the two,
metric wins easily.

Times change, we move on.

Now if only I had bothered with English at school, I hated it, but it
does let me down from time to time, maths, the various sciences,
technology and cooking I was very good at, and pretty good at most of
the others, except Art, which I'm even more dreadful at than English.


--
60 day free DVD rental: www.southeastbirmingham.co.uk/dvd
Mobile Offers: www.southeastbirmingham.co.uk/payg
Items for sale: www.dodgy-dealer.co.uk


Reply With Quote
  #30 (permalink)  
Old 12-18-2006, 06:31 AM
speckled hen
Guest
 
Posts: n/a
Default Re: A PAP2T disaster with Delta3/iConnect


Brian wrote:

> On 2006-12-17, Stan <SPAM_FOILER@some.domain> wrote:
>
> > On Sun, 17 Dec 2006 00:53:35 UTC, Brian <bandj@o2.co.uk> opined:
> >> On 2006-12-16, Stan <SPAM_FOILER@some.domain> wrote:
> >>
> >> > 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.
> >>
> >> 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.

> >
> > That's exactly what I am afraid of. See my original description above.
> > The experience with the provisioning site was also the point at which
> > it became impossible to view the configuration screens, or to
> > otherwise communicate with the device.

>
> You could go through the whole process again in an attempt to get the
> PAP2 recognised by iConnect. If it is the cause of your problems you
> have little to lose.
>
> Brian.


Just looked at my spa2102 user guide, using IVR.

"user factory reset" > 877778 "The adaptor will request confirmation,
enter 1 to confirm
the adaptor will reboot and all user configurable settings will be reset


Reply With Quote
Sponsored Links
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments