Re: [General] The new PAP2 v2.0 in VOIP Tech Chat

Re: [General] The new PAP2 v2.0

Tue, 07 Apr 2009 22:17:40 EDT

said by squish102 :

I have a magicjack and really was hoping this firware would work. Do I have any other firmware versions that I could use for magicjack usage?

If you want to use your PAP2v2 with an MJ service behind a non-symmetrical NAT/Firewall router, then an original firmware and/or firmware released by Vonage for a PAP2v2 may not be suitable for you because it doesn't have a support for STUN options. In this case, you may have to resort to using the modded RTP300-NA firmware approach. Otherwise, the NAizer for CYT approach, developed by DogFace05, will be a much better solution mainly because it will un-customize a PAP2v2 unit.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Tue, 07 Apr 2009 22:02:36 EDT

squish102 : Great I finally got as far as the upload new firmware on my PAP2v2 after using CYT unlocking code. Next I figued out how to get pap2v2_fw_3.1.24_NA.img.web files created. Now I see that 3.1.24 is no good?

I have a magicjack and really was hoping this firware would work. Do I have any other firmware versions that I could use for magicjack usage?

Thanks

Re: [General] The new PAP2 v2.0

Sat, 28 Mar 2009 14:01:46 EDT

GrauerFuchs :

said by cyberma007 :

what i really need working right now is the Dailplan change, where can i change that?

The Dial Plan option can be set either by provisioning XML or by logging into the voice tab as the Admin and by enabling Advanced view.

Re: [General] The new PAP2 v2.0

Sat, 28 Mar 2009 13:59:23 EDT

GrauerFuchs :

said by studio1b :

help...

ok i flashed this pap2 v2 with the firmware patch now i go to
192.168.1.254 and i get this page that tells me 403 FORBIDDEN is there a way to fix this ?

This was caused by an error in compiling the new firmware. It normally means that either you tried to do the work on a filesystem that doesn't support the same permissions scheme, or you used a non caps-sensitive filesystem. ext2 or ext3 filesystems are preferred for doing this compile. FAT32, NTFS, and HFSPlus all exhibit potential problems when patching the firmware. When you've recompiled the firmware, you'll need to either log in by ssh and upload it by the command line, or by using the PAP2's onboard serial console.

Re: [General] The new PAP2 v2.0

Fri, 27 Mar 2009 21:42:42 EDT

anon : help...

ok i flashed this pap2 v2 with the firmware patch now i go to
192.168.1.254 and i get this page that tells me 403 FORBIDDEN is there a way to fix this ?
i clear my web and i tested firefox gives the same redish page with a 403 error

403 Forbidden
The requested URL '/' resolves to a file which is marked executable but is not a CGI file; retrieving it is forbidden.

^^ is there something i'm missing here

Re: [General] The new PAP2 v2.0

Thu, 19 Mar 2009 13:58:04 EDT

cyberma007 : All stuff is done
I have it working with MagicJack as well, but i need to change the DailPlan and i dont see an option to change it.
I did not say that the WebGui Does not work with admin\admin\, at leaset that is not what i ment.

There is a firmware page that you can click on to update that ask for password, that does not take any password.
and when i try to ssh to the device none of the admin passwords work,
put what i really need working right now is the Dailplan change, where can i change that?

Re: [General] The new PAP2 v2.0

Thu, 19 Mar 2009 13:52:36 EDT

mazilo :

said by cyberma007 :

Yes webgui Works just fine.

At least, this proved your PAP2v2 is still working. If you haven't done so, please perform a completely factory reset through the pinhole on the back of your PAP2v2. See if this will do a trick for you.

Re: [General] The new PAP2 v2.0

Thu, 19 Mar 2009 13:06:16 EDT

cyberma007 : Yes webgui Works just fine.

Re: [General] The new PAP2 v2.0

Thu, 19 Mar 2009 12:56:30 EDT

mazilo :

said by cyberma007 :

Also i cant login to SSH with Admin\Admin or admin\admin

Can you access its webGUI using a web browser?

Re: [General] The new PAP2 v2.0

Thu, 19 Mar 2009 12:38:25 EDT

cyberma007 : Hi all
I have the PAP2 V2 with the RTP 300 firmware patch.
I dont see an option for Dail Plan.
Also i cant login to SSH with Admin\Admin or admin\admin
can someone help me please.
Thanks

Re: [General] The new PAP2 v2.0

Tue, 10 Mar 2009 02:18:15 EDT

jboy_103 :

said by PX Eliezer :

[349]11

It permits dialing to 311, 411, and 911.

thanks!

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 20:19:56 EDT

PX Eliezer :

Look again.

[349]11

It permits dialing to 311, 411, and 911.

Sometimes the sequence is listed as [3469]11 which of course would also permit 611 dialing where applicable.

--------------------------------------

Everyone whose Voip provider provides 911 service should make sure that 911 dialing is in their dial plan.

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 20:05:05 EDT

jboy_103 : --removed--

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 20:03:28 EDT

jboy_103 :

said by toro :

The PAP2v1 (and PAP2T) dialplan syntax doesn't work on PAP2v2. For example it does not support pattern replacements like
Also, on PAP2v1, a variable number of digits can be set by just using a period (".") at the end of a pattern, while on PAP2v2, you must add a T as well.
In your case, since you use a Betamax service, all the numbers need to start with 00 (that's the prefix they use for all calls), and the numbers may be of variable length, so I suggest changing your dial plan to something like this:

00xxxxx.T

Thanks! Where can I find dial plan syntax instructions for the PAP2 v2, as well as the original v1?

Also, interestingly enough, the default dial plan on the doctored NA firmware (the one I mentioned earlier), worked for Betamax just as you would on other service, except 7-digits or 10-digits dialing does not work. In other words, 1-(area code)-(7 digits phone number) dialing works just fine for US domestic calls, and 011-(country code)-(international phone number with area code) works for international calls. I do not know how to explain this. ;)

For this dial plan:
*xxT|*1xx|[349]11|1xxx[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T

I can pretty much guess what it means, except what this [349] means???

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 14:54:52 EDT

toro : Are you looking to use the VTA firmware on PAP2v2 or the PAP2v2 firmware on VTA ?
The PAP2v2 and D-Link VTA are very similar but not exactly the same. If you look close the processor is not the same.
And I found this the hard way: personally I hate the VTA firmware and the SIP setting pages don't work well. When I first got the PAP2v2 flashed with the RTP300 firmware patched by GrauerFuchs, I was so excited (I like the Spiura-like firmware) that I tried to load it on a VTA. The result: a few crackling noises, maybe a little smoke, and voila: that VTA's voice portion is now dead. The rest of it still works, boots up, I can access the web interface and console, but that's about it.
So beware...

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 13:08:18 EDT

Guiness : Since the PAP2 V2.0 has the same internals as the D-link VTA-?V (I've got the CV) can this firmware be used in it?

I've got my unit unlocked, but can't find much information on the fw I'm running, and would rather run the one described here!

Re: [General] The new PAP2 v2.0

Fri, 06 Mar 2009 09:14:22 EDT

toro : The PAP2v1 (and PAP2T) dialplan syntax doesn't work on PAP2v2. For example it does not support pattern replacements like
Also, on PAP2v1, a variable number of digits can be set by just using a period (".") at the end of a pattern, while on PAP2v2, you must add a T as well.
In your case, since you use a Betamax service, all the numbers need to start with 00 (that's the prefix they use for all calls), and the numbers may be of variable length, so I suggest changing your dial plan to something like this:

00xxxxx.T

Re: [General] The new PAP2 v2.0

Thu, 05 Mar 2009 21:14:54 EDT

PX Eliezer : If you have a PAP2T, go to:
»www.linksysbycisco.com/US/en/sup···download

Then:
---Select Version 1.0
---Go to Guides and Information
---Then go to User Guide (choose the second one they list!)
---Download (PDF)
---Go to dialplans, page 61.

----------------------------------

~~If a PAP2 Version 2.0, Linksys does not currently seem to have the manual posted. However, the Dialplan instructions in the above manual should still be relevant.~~

See next post...

Re: [General] The new PAP2 v2.0

Thu, 05 Mar 2009 20:21:25 EDT

jboy_103 : I am having trouble to use any dial plan other than the default one in the unlocked PAP2 V2 (PAP2v2-1.00.16-patch_NA-0.5b).

I am trying to use it with nonoh or voipbuster/pro. Seems the provider does not matter, as soon as I change the default dial plan (digit map), the line no longer register.

Anybody has the same problem?

BTW, I am a newbie to this dial plan/digit map thing. Can somebody point me to a place for a prime? I have read this tutorial at:

»www.netphonedirectory.com/pap2_dialplan.htm

However, it doe not explain a lot of the things in the default dial plan:

*xxT|*1xx|[349]11|1xxx[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T

Re: [General] The new PAP2 v2.0

Sat, 21 Feb 2009 11:47:53 EDT

meister_sd : Ok - I have a v2 with a socket on it so I can easily try some experiments. Somewhere along the line I burned up my serial console. I'm wondering if anyone knows what chip is providing serial access? I have a spare v2 for parts that I can use to swap chips.

Re: [General] The new PAP2 v2.0

Sat, 31 Jan 2009 07:53:23 EDT

SIPLiterate : Thanks for the feedback. I looked at past instructions but it looked like it would be very involved (such as compiling code using Linux). I do have a Linux partition that I hardly use so I could probably fight through this but it would take hours...

I managed to get it going again by doing a 30/30/30 reset as noted by mazilo at »[General] The new PAP2 v2.0 and then re-provisioning it.

I ordered a Mediatrix 2102 and hope that it will perform well.

Re: [General] The new PAP2 v2.0

Mon, 26 Jan 2009 15:29:27 EDT

GrauerFuchs :

said by SIPLiterate :

Is there any way to recover from this bug?

This is the bug that ended development of that firmware series on this device. It is built so deeply into the binary code that it would require reverse engineering and/or a major financial outlay and corporate backer to resolve. The only solution to this bug is to very carefully follow the instructions previously given in the thread for reversion to a previous firmware. The PAP2v2 3.1.24 firmware is a dead project, having been replaced by an attempt to produce a 100% open source firmware for it instead. Unfortunately, this new project is not likely to result in usable firmware any time soon.

Re: [General] The new PAP2 v2.0

Sat, 24 Jan 2009 15:58:22 EDT

SIPLiterate : I just got past one problem. I determined that its IP address is static 192.168.1.254 from »[General] The new PAP2 v2.0. So now I have it provisioned again with my SIP provider's information and my userid/password. However it is not registering based on its web interface. When I enabled SIP debug to a syslog server (my PC), I see that it is registering with a contact address of 192.168.15.1. This would explain why it is not registering. Is there any way to recover from this bug? As I just finished trying a factory reset, I assume that trying that again won't help.

Re: [General] The new PAP2 v2.0

Sat, 24 Jan 2009 14:48:46 EDT

SIPLiterate : I bought a Linksys PAP2 v2 unlocked from someone privately. It came with Vonage paperwork.

I successfully used it for the last 1.5 months with a SIP service provider. Its web interface showed revision 3.1.22 in one spot and 3.1.24 in another.

Today it stopped working after a call I was on abruptly dropped. I power cycled it, logged into its web interface, and saw that it would not register with my SIP provider. I was able to debug and see that it was trying to register as IP address 192.168.15.1. I researched online and found that this is a known bug (here on dslreports).

So I did a factory reset while it was connected to my network and could not since access it. I tried sniffing packets from it and it is not sending any packets (ie. not even DHCP) even though per its IVR it is configured for DHCP. It is not responding to 192.168.15.1 which its IVR reports as its IP address. The IVR option 170 (check web server port) is invalid. The IVR option to enable/disable DHCP (101) is also invalid. When I enter IVR option 7932 (enable/disable web server), it asks to enter a value. I entered 1 followed by #. It says to enter 1 to save value. However this does not appear to help.

Do I have a brick on my hands or is it possible to recover this PAP2 v2? If so are you able to point me to some instructions?

Re: [General] The new PAP2 v2.0

Wed, 14 Jan 2009 02:58:29 EDT

DogFace05 : Thanks for your interest. I've made substantial progress lately, but much work still remains, in particular in designing a GUI for the tool. Can't give any kind of ETA, given the amount of work still to be done, while also having to divide my time between it and other current projects. I can confirm however, after some preliminary testing, that the tool will definitely support the PAP2v2 (I designed it with the RTP300 in mind).

Re: [General] The new PAP2 v2.0

Tue, 13 Jan 2009 23:47:56 EDT

msiam : I'm on the edge of my seat waiting for that tool, Dogface..

Re: [General] The new PAP2 v2.0

Sat, 03 Jan 2009 08:47:04 EDT

mazilo :

said by fastcar23 :

hmmm.. I used »www.keyspan.com/products/usa19hs/

This is ONLY a Serial2USB cable. If you use this cable, you will still need to use either a Serial/USB to a serial-console cable to connect to your PAP2v2.

Re: [General] The new PAP2 v2.0

Sat, 03 Jan 2009 07:32:33 EDT

GrauerFuchs : The output from that adapter is RS-232. You probably fried the interface port of the PAP2. The only way to know if the damage is done or not is to build a proper adapter or buy one. I have yet to see a pre-made device on the market with a reasonable price tag. I suggest you look at building one based around the MAX3232 chip. This means soldering and putting together an interface out of components. That keyspan adapter of yours could then connect to this new adapter, and in combination, it would work.

Re: [General] The new PAP2 v2.0

Sat, 03 Jan 2009 00:30:57 EDT

fastcar23 : hmmm.. I used »www.keyspan.com/products/usa19hs/
This the wrong one? Do know if a website that has the correct one?
How do I know if the damage is already done?

If damaged, what should I do with the pap2v2? Make it it door stop?

Thanks!

Re: [General] The new PAP2 v2.0

Fri, 02 Jan 2009 22:36:21 EDT

GrauerFuchs : The serial adapter you need is to go from RS-232 (normal PC/modem serial) to CMOS Logic (3.3v) and vice versa. A standard USB to serial dongle will damage your PAP2 unless modified to put out the 3.3v/0v CMOS signals. RS-232 serial puts out -12v/+12v signals. If you didn't modify that adapter to put out the right levels, the damage is probably already done.

Re: [General] The new PAP2 v2.0

Thu, 01 Jan 2009 12:38:04 EDT

fastcar23 : okay, good news. I got a serial cable/usb connected to the pap2v2 fw 1.00.22. using, putty, I connected it the serial/usb making sure to line pins and got nothing. I swapped the pins and just got garbage. I was using a keyspan serial adapter and I checked that inferface out there was info, but the same think over and over.
I set up the connection like this: (someone else posted this)
LINKSYS PAP2 V2.0
pin 1 ... 3.3v (Pin 1 Marked)
115200 baud. (8,N,1-Hardware)

Any ideas???

Re: [General] The new PAP2 v2.0

Wed, 24 Dec 2008 20:16:14 EDT

mazilo :

said by fastcar23 :

Oh BTW, I tried the 30/30/30 rule and it didn't work. I unplugged it from the internet. I push the reset button for 30 sec, unplug it, still holding the reset button for 30 sec, then plugged it back in still holding the reset button for 30 sec. I think that was right.

That's exactly about 30/30/30 factory reset and sorry to hear it didn't help. :(

Your best option is to wait for DogFace05 to release his beta test software. Second to this is to use a serial-console cable to erase/flash a new firmware on to your unit.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Wed, 24 Dec 2008 20:05:43 EDT

fastcar23 : That sounds great about your software. I would really like to know when you get that up and running and even be a beta tester.

Question though..i downloaded a tftp client to download the fw downgrade to the pap2v2. The tftp port is not enabled, so how can i upload the bin file? Have to hack it first, right?

Oh BTW, I tried the 30/30/30 rule and it didn't work. I unplugged it from the internet. I push the reset button for 30 sec, unplug it, still holding the reset button for 30 sec, then plugged it back in still holding the reset button for 30 sec. I think that was right.

Thank you for all your ideas and comments.

Re: [General] The new PAP2 v2.0

Wed, 24 Dec 2008 19:12:30 EDT

DogFace05 : You're likely trying to do a web upgrade with the image made for a tftp upgrade. Upgrading through the web interface requires a version of the image with a special header prepended to it. I believe there are instructions somewhere in these forums detailing how to modify a tftp upgrade image such that it can be used to upgrade through the web.

Alternatively, if you're willing to wait a few weeks, I've developed a software-only solution for permanently doing away with Vonage from RTP300/WRTP54G adapters, which I expect will work with PAP2v2s as well. It currently consists of an assortment of separate command line tools, but I'm working on integrating it all into a single, user friendly GUI version that will make unlocking and NAizing these devices as easy as a mouse click. Like all my other NAizing solutions, it does not make any modifications whatsoever to the onboard firmware. I hope to be able to put it out for a limited beta test soon.

Re: [General] The new PAP2 v2.0

Wed, 24 Dec 2008 13:45:40 EDT

mazilo :

said by fastcar23 :

Any other ideas?

You may want to try to perform a 30/30/30 factory reset first. Do this while your PAP2v2 unit isn't connected to the Internet. Failing that, use a serial-console cable to flash the firmware. If this still fails, consider to donate your brick for the cause of hacking, instead of throwing it away to trash.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Wed, 24 Dec 2008 12:08:05 EDT

fastcar23 : Thank you for the input, I just tried to downgrade pt-11.4.0-r060426-1.00.13-r060426.bin and I got the same error. Not sure where to go now, except to use it as a door stop. lol. Any other ideas?

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 22:28:56 EDT

holiday :

said by fastcar23 :

...using this file:pt-11.4.0-r060426-1.00.13-r060426.bin ...

I've no idea what that error really means, but can you downgrade to pt-11.4.0-r060628-1.00.16-r060628.img? Then try to unlock it.
--
Holiday

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 21:54:16 EDT

mazilo :

said by DogFace05 :

said by mazilo :

If you connect your PAP2v2 serial port to your computer serial port (a +5V TTL), then chances are you are going to burn the serial port on your PAP2v2.

A standard computer serial port operates at ±12V, according to the RS-232C/V-24 standards, not 5V TTL levels. Some cell phones do sport a 5V TTL level serial interface, which require a level shifter (just like the 3.3V devices) to connect to a standard serial port.

DogFace05, many thanks for your clarifications above. Cheers.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 21:00:29 EDT

DogFace05 :

said by mazilo :

If you connect your PAP2v2 serial port to your computer serial port (a +5V TTL), then chances are you are going to burn the serial port on your PAP2v2.

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 19:56:31 EDT

mazilo :

said by fastcar23 :

I found that I have a serial to serial cable. Will that work?

AFAIK, the voltage on an embedded system, i.e. PAP2v2, etc., is on a +3.3V. If you connect your PAP2v2 serial port to your computer serial port (a +5V TTL), then chances are you are going to burn the serial port on your PAP2v2. You will need a 3.3V serial-console cable to connect your PAP2v2 to your computer.

I am guessing that I need to take the router apart and connect to the 5 pins that are on the board, Right

R we talking the same thing here? I thought you mentioned on your OP that you want to unlock your PAP2v2. AFAIK, a PAP2v2 is an ATA and NOT a router.

Do you have a step-by-step instructions to unlock the device this way.

I believe you will need to read posts on this thread to find out. I know it is a waste of time. Unless you want to learn something, chances are you won't like to read all posts on this thread. As such, just pay someone to do this dirty job for you.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 10:52:00 EDT

fastcar23 : Thank you so much for replying. I found that I have a serial to serial cable. Will that work?
I am guessing that I need to take the router apart and connect to the 5 pins that are on the board, Right

Do you have a step-by-step instructions to unlock the device this way.

Thanks!

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 08:42:09 EDT

mazilo :

said by fastcar23 :

I got it for $20, but I have been working on this for 2 days.

The best and easiest way to unlock this device is to hook it to your computer USB/serial port with a USB/serial-console cable.

Re: [General] The new PAP2 v2.0

Tue, 23 Dec 2008 03:53:02 EDT

fastcar23 : Maybe someone can help me out. I have a new pap2v2 with fw 1.00.22 on it. I tried to downgrade it to 1.00.13 and i get an error - "magic number config error" I am using this file:pt-11.4.0-r060426-1.00.13-r060426.bin and trying to unlock it using CYT 4.9. I am not a linux person to much, so if there is a windows solutions that would be great!!

I got it for $20, but I have been working on this for 2 days.

Any help would be great!!

Re: [General] The new PAP2 v2.0

Wed, 29 Oct 2008 10:37:48 EDT

GrauerFuchs : The post above will work for anyone that had the 3.1.24 firmware go bad on them. I posted it both for instruction to help any user that needs it, and to show exactly how difficult it is to roll back for anyone considering a haphazard try at the modded firmware. onlinefun and anyone else in a similar position could make use of the information in that post.

I do plan on producing a tool that will make the transition easy, but have not had time to do any work on it yet. This tool will be more in preparation for a new development firmware (in only the planning stages ATM) that would release the PAP2v2 from almost all of the proprietary code. I hope to eventually see an open source firmware produced, leaving only the kernel level hardware access code under the required proprietary license.

This final step will require the help of multiple users with high level experience in Linux development, cross-compiling configurations, mipsel hardware development, web development, Asterisk software, and more.

Re: [General] The new PAP2 v2.0

Tue, 28 Oct 2008 22:31:39 EDT

holiday : GrauerFuchs, does your post above, to onlinefun, reflect the final answer to the question of how to rollback the firmware on a pap2v2 that had the patched 3.1.24 firmware put in it?

Or are you still working on another way? I was hoping for a ... non-hardware way :)

Re: [General] The new PAP2 v2.0

Tue, 28 Oct 2008 17:02:59 EDT

onlinefun : Thanks GrauerFuchs for the reply.

I knew about the issues when I installed RTP300 patch and still went with it as I wanted to use MagicJack acount which has Alpha Numeric ID which I thought can only be solved on PAP2v2 with this patch. Anyway...the steps you have mentioned are too much for me so I will stick with the current one I have and may be try to fix the issue to NAT/STUN that you guys have mentioned to register with Asterisk.

I will be helping a friend with unlocking his PAP2v2 very soon. So, wondering if I can go with 1.00.16 - 0.5 patch now and then may be in future upgrade to RTP300 patch if needed (only for Alpha issue!). Will that be a safe thing to do (or) does that patch also has similar rework with partitions?

Just wondering what is the safe thing to do after CYT unlock on this device so that it wouldn't get locked to Fonage again? - Only options I understood from this thread is to go with 1.00.16 patch (or) RTP300 patch?

Thanks for all your help.

Re: [General] The new PAP2 v2.0

Tue, 28 Oct 2008 07:00:08 EDT

GrauerFuchs : You should have read the details on the patch before loading it. The SIP reported IP was a known issue at release that as of yet cannot be resolved. What's more, you can no longer run the original firmware.
The PAP2v2 was massively reconfigured (even in firmware partitions) when you loaded the RTP300 firmware on it, so downgrading will result in an extremely high risk of errors or problems. This does not mean that it isn't possible, however.
To downgrade safely, you will need to overwrite the environment space by JTAG, followed by all of the image and configuration space. The only thing that can remain on the unit is the 0xb0000000-0xb0010000 bootloader code. This means you have to use JTAG to erase all data from 0xb0010000-0xb8000000. Once this is done, you can reboot and upload (by bootloader prompt on the serial console) the patched 1.00.16 firmware. Use only the patched firmware here, or an older version of unpatched. The new firmware, if unpatched, WILL result in the box locking to the provider for whom the firmware was designed. In addition, the Admin password will be reset to the hardware default (unknown) password.

Re: [General] The new PAP2 v2.0

Mon, 27 Oct 2008 20:10:49 EDT

onlinefun :

said by mazilo :

said by onlinefun :

Now that I am trying to hook this up to my Asterisk on router (internal to my network), I got caught with subnet issue that we have on this (192.168.15.1).

Were you saying your PAP2v2 running on an RTP300 patched firmware won't allow you to change its IP Address to other subnet? If so, why not just change the router LAN subnet to reflect to the subnet used by your PAP2v2?

Sorry for confusion...I was talking about the SIP module stuck with 192.168.15.1 issue...Was suggested in this topic to have a static ip for this patched router (which I left at default for this - 192.168.1.254) instead of DHCP. But even with that static I am seeing 192.168.15.1 on my Asterisk logs and finally gets Unauthenticated (as others were getting with the same firmware)...so I was thinking to use 1.00.16 patched v0.5..so will that be an issue going back to that 1.00.16 and may be come back to 3.1.24 version
Simply...can the firmware be switched back and forth between these two versions or any limilations?

Re: [General] The new PAP2 v2.0

Mon, 27 Oct 2008 17:36:20 EDT

mazilo :

said by onlinefun :

Now that I am trying to hook this up to my Asterisk on router (internal to my network), I got caught with subnet issue that we have on this (192.168.15.1).

Re: [General] The new PAP2 v2.0

Mon, 27 Oct 2008 15:20:10 EDT

onlinefun : Hello Gurus...

I had my PAP2v2 patched with version made from RTP300 firmware for had been working good for some months.

Now that I am trying to hook this up to my Asterisk on router (internal to my network), I got caught with subnet issue that we have on this (192.168.15.1). So, wondering what are the risks with going with PAP2v2-1.00.16-patch_NA-0.5b? Should I just build and update it through web? (or) do I have to watch for any things?

Also, Once I do that and have patched 1.00.16 can I go back to RTP300 patched version? - probably for using it with Magicjack which has alphanumeric ID/PWD? - if I get in to any troubles with Asterisk (or) to help friends with different needs? (may have to work on 3 PAP2v2 boxes to remove Fonage dependency)

Thanks in Advance

Re: [General] The new PAP2 v2.0

Thu, 16 Oct 2008 00:17:16 EDT

western221 : i searched a bit but i didnt find/understand the answers that helped me so please indulge me since i am sure this has been asked a million times.

i got a new pap2 v2 locked to vonage, i think i was sucessfull in unlocking it and now it has Firmware Version: 1.00.13.

What settings do i enter on the adapter for it to work with ACANAC?
»xs232.xs.to/xs232/08422/line1460.png
»xs232.xs.to/xs232/08422/sip279.png
»xs232.xs.to/xs232/08422/commoncoding233.png

also is there a way to know for sure if my unlocking was sucessful?

the information provided to me by ACANAC

Proxy : 66.49.255.59
Outbound Proxy : 66.49.255.59 ***where do i enter this***
Register Expires : 60 ***where do i enter this***
Proxy FallBack Intvl: 60 ***where do i enter this***
Voice Mail Server : 66.49.255.59 ***where do i enter this***

Display Name : Yopr name
User ID : 647*********
Password: ******
Auth ID: 647******

also do i leave the remaining fields blank? like registar address

thx for the help in advance. and if someone is really generous and can spare a few minutes please email me at western221 (@) gmail.com

Re: [General] The new PAP2 v2.0

Sun, 12 Oct 2008 22:11:27 EDT

anon : Thanks to the great post, I followed the instructions in page 25-28, compiled the firmware in Ubuntu. When i installed in my PAP2 V2.0 adapter, i received "End of file error". Is there any other way to unlock PAP2 V2.0?
Here is what i did. Downgraded my PAP2 to 1.33 firmware,enabled SSH and using CYT overwrote the passwords.
Am I missing anything else? I am trying to unlock PAP2 to use with MagicJack. Appreciate your help. Thanks!

Re: [General] The new PAP2 v2.0

Sat, 11 Oct 2008 09:14:47 EDT

R3bel : I think I am going to leave the problem partially fixed like it is now. It is working outbound to most PBX with dial menu digits I tried. So it is good news since this is useful and mostly required when you need to use it.
For my VM voice, I temporarily disable Voicemail settings so message is recorded through the handset hardware VM. So with little work without too much stress, it is much better than before since I no longer need to use the other line to dial.
Thanks for all your help!

Re: [General] The new PAP2 v2.0

Fri, 10 Oct 2008 21:56:23 EDT

R3bel : Thx AndrewZ! I got it partially working through SSH. I can dial extension number through PBX with extension number recognized by the external system which before could not be done. However, the voice mail is still not working. I will try different setting. It is not perfect yet but it works. I will make more test to call bank system or tech support automated system to see if digits are correctly sent.

Re: [General] The new PAP2 v2.0

Fri, 10 Oct 2008 11:29:39 EDT

AndrewZ : As it was mentioned DTMF is broken, both rfc2833 and SIP INFO.
Some time ago the workaround for this was implemented on Asterisk upon my request (for rfc2833 only). Other SIP servers have the right to ignore the tones you're sending.

Regarding ssh - search this thread and one I mentioned earlier for dbgcmd.

Re: [General] The new PAP2 v2.0

Fri, 10 Oct 2008 10:11:59 EDT

R3bel : Forgot to ask, is there someway to SSH to talk to the device so some hidden command line can be sent to set the DTMF mode. If there is such possibility, which cmd syntax to submit and any instruction how to do that? Thx for all your help!

Re: [General] The new PAP2 v2.0

Fri, 10 Oct 2008 10:08:07 EDT

R3bel : Thx for your help. I saw that thread too! Tried all the values. Never get it to work. The default setting was 1. Out of luck trying out all the other values.
Still the VM did not understand the code, say it loops the voice menu no matter what digit I entered. Say press #1 for this, press #2 for that, entering the correct digit always get the same main voice menu message.

Re: [General] The new PAP2 v2.0

Fri, 10 Oct 2008 05:44:05 EDT

AndrewZ : R3bel,
Check this »Re: [General] DLink VTA-VR

Mine is configured with the value of "1" which works fine with rfc2833 on the opposite side. Please note the comment at the end of the message I'm referring to.

Re: [General] The new PAP2 v2.0

Thu, 09 Oct 2008 15:54:27 EDT

R3bel : Hope to find help in this thread and my thanks to all the members who contribute their sharing. I am currently have this problem but unable to find any information on how to fix it. That is what happens with unlocked device.

Though i like to opt for a firmware change but it seems not recommended with an average user group which I belong to. So I want to ask if there is something to try to fix the DTMF. I currrently have the new PAP2 V2.0 1.00.13 unlocked though in SIP, line1, line2 and common panel do not have any config field for DTMF which I need to set for rfc8833 to fix the access problem through voice mail or when dialing to a PBX system with extension numbers to input.

I looked but could not find if there is any hidden DTMF syntax I can write to the unencrypted config xml file so I can transfer back to the device forcing it to use the DTMF mode as RFC8833. The unlocked device is working with inbound and outbound calls with the current voip provider except this dtmf problem. I can read voice mail through wav file from email but it is starting getting annoying not able to do it from the phone.

Any help is greatly appreciated even if it can't be done so I know not to look anymore!

Re: [General] The new PAP2 v2.0

Wed, 24 Sep 2008 14:50:40 EDT

Randy_G :

said by Jmf421 :

said by blueyes :

hi all,

sorry for what may be a newbie question, but I have searched the web and was getting conflicting information.

I managed to grab 4 brand-new-in-box pap2 from Staples for $20 each. All 4 of them have the S/N of the following pattern:

Good deal!

is this deal still going on?

Jeremy Ferguson
Jferguson@bandwidth.com

FH900F14

My question is: are these v1 or v2? posts on dslreports.com seem to suggest that these are v1 and hence is to be unlocked with tftp trick. However, other forums seem to suggest that these are v2 and hence are to be unlocked with cyt.

any clarification is very much appreciated,

Jeremy, did you ( or BlueEyes ) read post ONE?

said by meister_sd :

I just bought a vonage pap2...
All four of mine are using a different serial number scheme than the last set of PAP2s I've bought. These serials are CH911F50xxxx whereas the others were FH900Exxxxxx or FH900Fxxxxxx.
These also say they are V2.0. ...
...box is just like the old unless you look at the white label where it says the model no. It will say "PAP2 v2.0" and the serial will be in this new series.

Re: [General] The new PAP2 v2.0

Mon, 22 Sep 2008 22:06:19 EDT

Jmf421 :

Re: PAP2 v2.0 - alternate (permanent) unlock success

Sun, 21 Sep 2008 07:34:48 EDT

GrauerFuchs :

said by mazilo :

One question. Once this is done, won't it be safer to revert and point cyt_private back to its previous address?

You won't need to do that. So long as you wait until the erase is finished, when you unplug the box and cold-boot it, it re-initializes the environment from what is stored in the bootloader. This means that all flash partitions will revert to the original settings they had on the 1.00.13 firmware. If you edited the bootloader before doing this, then all your new settings will also take effect from here on out. Goodbye provider locks!

Re: PAP2 v2.0 - alternate (permanent) unlock success

Sat, 20 Sep 2008 23:46:54 EDT

mazilo :

said by GrauerFuchs :

The trick there is to temporarily assign the cyt_private environment variable to the address range of the bootloader environment. Reboot the ATA, and next time you log in, you'll be able to use dd to overwrite the boot environment (labeled as cyt_private) using dd.

An excellent hack!

One question. Once this is done, won't it be safer to revert and point cyt_private back to its previous address?
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: PAP2 v2.0 - alternate (permanent) unlock success

Fri, 19 Sep 2008 14:56:05 EDT

toro :

I copied the bootloader into /var/tmp (RAM), loaded a new instance of thttpd capable of accessing that dir

Thanks very much for the info ! This is exactly the step where I got stuck: finding a means to transfer the image from the device to my PC.

Re: Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Fri, 19 Sep 2008 14:53:01 EDT

GrauerFuchs :

said by baizw :

Thanks.
Only the internet lights flashing after some hours later. But i am sure it is only happening after i setup Acanac VOIP service. If i remove the acanac voip service and setup any others, everything would be ok.

I'm afraid I'm unfamiliar with that service or its setup, but it is possible that something may be going wrong. Without a debug or log stream from the machine showing what happened before it stopped working, it's hard to narrow down the exact cause and how to resolve it.

Re: PAP2 v2.0 - alternate (permanent) unlock success

Fri, 19 Sep 2008 14:50:14 EDT

GrauerFuchs :

said by toro :

I've been thinking of another approach that would also work for other CYT based devices, such as the VTech IP8100 which doesn't have a JTAG interface (or at least I wasn't able to identify all the pins yet):
...
I wanted to try it on a device that has JTAG (and therefore could be recovered if something went wrong).

This idea is very similar to the success I had on the PAP2v2. By way of the serial console, I copied the bootloader into /var/tmp (RAM), loaded a new instance of thttpd capable of accessing that dir, offloaded the bootloader code to my devel Linux box, and edited out the environment variables. (on PAP2v2's pspboot, the environment info starts at byte 0xC350) I then turned on the devel http server, used the PAP2's wget command to upload the edited version to memory, and then used dd to block-write the edited one to flash. Unfortunately, the work doesn't end there. It won't directly let you overwrite or change the bootloader environment from the bootloader prompt, and it doesn't show up in the mtd partitions list.

The trick there is to temporarily assign the cyt_private environment variable to the address range of the bootloader environment. Reboot the ATA, and next time you log in, you'll be able to use dd to overwrite the boot environment (labeled as cyt_private) using dd.

My ultimate plan is to package a 100% GPL kernel, filesystem, and tools into a mini firmware image that will do all the above automatically (and retain the MAC address and necessary information) and then put in a more sane Admin factory default password, a known (to the user) crypto key, and a file path that won't be found on the V's servers. The firmware would then do one of two things: Burn itself out and leave a second copy of the previous firmware, or open up a web and tftp server for custom firmware uploads without any resistance. The second method will be used as a more or less mandatory step to loading the new development firmwares into place, as they'll need a clean environment to prevent user lock-out.

Re: Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Fri, 19 Sep 2008 14:10:21 EDT

baizw : Thanks.
Only the internet lights flashing after some hours later. But i am sure it is only happening after i setup Acanac VOIP service. If i remove the acanac voip service and setup any others, everything would be ok. I first found this problem in D-LINK ATA device with acanac service, also linksys pap2 v2 has the same problem, i guess they used the same firmware

Re: PAP2 v2.0 - alternate (permanent) unlock success

Fri, 19 Sep 2008 13:53:57 EDT

toro : I've been thinking of another approach that would also work for other CYT based devices, such as the VTech IP8100 which doesn't have a JTAG interface (or at least I wasn't able to identify all the pins yet):
- use the CYT unlocker to gain access to the device and enable SSH
- SSH into the device, copy the boot loader to a file (using the dd command), and FTP that file to your computer
- remove the HASH_DIR and CRYPT_KEY and change the ADMIN_PWD to a known hash
- use wget to download the boot loader as a file and dd it back to the bootloader partition
Of course, this is quite risky and could brick the ATA if something goes wrong.
I wanted to try it on a device that has JTAG (and therefore could be recovered if something went wrong). The problem I'm having is I'm not too good with toolchains and compiling stuff for a different platform (which is needed in order to compile a simple FTP program).

Re: Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Thu, 18 Sep 2008 21:54:14 EDT

GrauerFuchs : Are both your power -and- Internet lights flashing, or is only one flashing, or is it just one? If one, which one?

If it's only the power light, you may be dealing with a problem of bad or dirty power. These adapters don't handle poor power conditions well at all. The only way to rule that out as a possibility is to replace the power pack with a better, less problematic power adapter. Either get a regulated or switch-mode power adapter that has the same voltage rating and either the same or higher current rating.

If it's the Internet light that is constantly flashing, you have one of a few different issues. The first step here would be to check your Ethernet cable and your router to make sure the cable is undamaged and the router isn't disconnecting the PAP2 for some reason.

Re: Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Thu, 18 Sep 2008 17:13:17 EDT

baizw : Thanks for your quick reply.
Unplugging the power and then plugging resolved this issue.
I unlocked the pap2 v2 with cty39c and the firmware is still 1.0.13, upgraded to 1.0.16 still face the same problem.

PAP2 v2.0 - alternate (permanent) unlock success

Wed, 17 Sep 2008 20:49:38 EDT

GrauerFuchs : Okay, we may have a new tool released soon. I've had some recent success in tricking the PAP2v2 in zapping the formerly permanent environment settings without using JTAG. So far, it looks like the 1.00.16 V*-locked firmware can be broken quickly and easily once initially unlocked by CYT and this trick is applied. What this means:
The factory-default Admin password can be changed permanently to a known value, and if desired, the factory default RC4 key can also be changed!
This will allow a user to run a minimally modified firmware that should retain full function and not be subject to the persistent password/key/xml directory bug that the beta 0.6 firmware suffered. This would also allow (albeit against the V*'s ToS) a user to have their PAP2v2 still running on V*'s service, but able to be removed at any given time simply by factory reset and temporary disconnection from the internet.

A patch or set of instructions will follow this, but the plan is still preliminary. An open source 'neutering' firmware may shortly be provided to support the permanent clipping of this box.

Re: Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Wed, 17 Sep 2008 20:39:03 EDT

GrauerFuchs : We need more details to have any chance of answering this. You said a light was flashing. Are both the power and internet lights flashing? If so, did you try unplugging the power and then plugging it back in? Did that resolve the issue? Which unlock method did you use? CYT only, or a patched firmware? Which version, if you used a patched firmware?

Unlocked linksys pap2 v2 will disconnect after 8-9 hours!

Wed, 17 Sep 2008 17:19:14 EDT

baizw : i just unlocked this linksys pap2 v2 ata, and config line 1 to acana phone and line 2 to voipdiscount service. last nite it worked fine, this morning, i found this ata device disconnected, only power light and internet light flashing , line 1 and line 2 green lights are black.

do someone else solve this problem?

i installed in d-link vta before, it has the same problem;
but as for linksys spa1001, it is always working fine.

best regards,

Re: PAP2 v2.0 - 3.1.24 firmware development halted

Wed, 17 Sep 2008 08:10:07 EDT

GrauerFuchs :

said by Randy_G :

When you picked apart the .16 firmware, did you see anything in there for a valid digit mask?

Not yet. I haven't done much with breaking down the internals of the ggsip package in the .16 firmware, and that's where this issue would be.

Re: PAP2 v2.0 - 3.1.24 firmware development halted

Tue, 16 Sep 2008 23:39:25 EDT

Randy_G : for phone numbers in firmware .16, you can use abcd1234567890. Not e though. I need one e.

I went so far as:

So I give up, I don't know how to make it send an e. :(

When you picked apart the .16 firmware, did you see anything in there for a valid digit mask?

Re: PAP2 v2.0 - 3.1.24 firmware development halted

Tue, 16 Sep 2008 15:26:15 EDT

GrauerFuchs : The kernel / ggsip mismatch that causes the de-sync bug also produces the following problems:
* IVR does not function properly. No settings work, wrong information read back.
* SIP headers send 192.168.15.1 in all communications. This makes it impossible to use on a local SIP proxy or PBX.
Workaround: Place it behind a NAT router or use a local STUN server.
* IP address cannot be reliably set or retrieved. Therefore, DHCP addressing is extremely dangerous.
* MAC address cannot be properly read from the hardware, and will always result in a 1-off number from the hardware MAC.
* Ethernet connection detection does not work.
* Spurious and unexplainable reboots have been reported, but I have yet to run across this problem.

This is an incomplete list. If I do recall, there were more problems, but I can't remember them at the moment.

Re: PAP2 v2.0 - 3.1.24 firmware development halted

Tue, 16 Sep 2008 13:04:18 EDT

Randy_G :

said by GrauerFuchs :

Bad news on the 3.1.24 and 3.1.27-ETSI firmwares. The de-sync bug...critical issue.
...For those of you that tried the 3.1.24 firmware and ended up with an unusable ATA, I will also be working on a how-to (and possibly a firmware clean-up) which will allow reversion to the previous code line....

The glitch where Pap2V2 won't send letters in the caller-id number is in FW 1.0.0.16 as well. That makes it not work at all, for my setup.

The 3.1.24 de-sync bug, the only downside is the 192.168 IP? Does it affect the functioning of the device any other way? Any other show-stopper problems?

Re: [General] The new PAP2 v2.0

Mon, 15 Sep 2008 13:23:23 EDT

tigger66 : those are PAP2 version 1. Most likely with 3.1.9 firmware. They are difficult to unlock, but they can be unlocked for sure as long as they have never been connected to the Internet.

Re: [General] The new PAP2 v2.0

Mon, 15 Sep 2008 09:27:05 EDT

anon : hi all,

sorry for what may be a newbie question, but I have searched the web and was getting conflicting information.

I managed to grab 4 brand-new-in-box pap2 from Staples for $20 each. All 4 of them have the S/N of the following pattern:

FH900F14

My question is: are these v1 or v2? posts on dslreports.com seem to suggest that these are v1 and hence is to be unlocked with tftp trick. However, other forums seem to suggest that these are v2 and hence are to be unlocked with cyt.

any clarification is very much appreciated,

Re: [General] The new PAP2 v2.0

Fri, 12 Sep 2008 10:15:30 EDT

anon :

said by Randy_G :

Toro (in Scarborough, ON) should be able to get some though, unless they show different availability by postal code or something (I have no idea, I just assumed staples.ca showed the same items for everywhere in Canada) They still show In Stock for me today.

what's your postal code? I've tried a few and they were all OOS for me.

thanks,

PAP2 v2.0 - 3.1.24 firmware development halted

Wed, 10 Sep 2008 15:57:45 EDT

GrauerFuchs : Bad news on the 3.1.24 and 3.1.27-ETSI firmwares. The de-sync bug (that prevents the voice module and adapter from communicating) is locked deep in the proprietary code linking the kernel and the ggsip package. Since the flaw impacts basic operation, this is a critical issue.
The only remaining possibility of success lies in building a fresh kernel optimized for the PAP2v2 that is also capable of running the proprietary software. Unfortunately, since it requires proprietary modules to do so, this means there will likely be no more releases of this patch line.

For those of you that tried the 3.1.24 firmware and ended up with an unusable ATA, I will also be working on a how-to (and possibly a firmware clean-up) which will allow reversion to the previous code line.

Work will continue on the older firmware code, as even though it lacked features, it was fully functional.

For now, the hope for new capabilities lies in the eventual porting of a slim SIP-only Asterisk version and a purely open source firmware to replace the proprietary code on this ATA.

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 15:39:53 EDT

GrauerFuchs :

said by Randy_G :

They still show In Stock for me today.

Hey, there's always the thought of a group buy on them. :D
(In other words, people give you the money to buy them and ship them out)

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 14:50:52 EDT

Randy_G :

said by toro :

No worries mazi, there's no stock anywhere. And in Canada, we didn't have any of the PAP2 sales that ran in US for the past 2-3 years :(

Agreed, 99% of the time it's the great US deals you can't get in Canada ;-)

Toro (in Scarborough, ON) should be able to get some though, unless they show different availability by postal code or something (I have no idea, I just assumed staples.ca showed the same items for everywhere in Canada) They still show In Stock for me today.

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 14:24:46 EDT

GrauerFuchs :

said by Randy_G :

There's lots in stock, online ONLY though. Link is above

The link won't work unless you live in / ship to Canada. It requires a Canadian postal code, and won't give details without one.

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 13:49:48 EDT

Randy_G : There's lots in stock, online ONLY though. Link is above

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 11:56:20 EDT

mazilo :

said by toro :

I wished local Staples stores here in the US have this price. Cheers.

No worries mazi, there's no stock anywhere.

Thanks.

Re: [General] The new PAP2 v2.0

Wed, 10 Sep 2008 11:03:46 EDT

toro :

I wished local Staples stores here in the US have this price. Cheers.

No worries mazi, there's no stock anywhere. And in Canada, we didn't have any of the PAP2 sales that ran in US for the past 2-3 years :(

Re: [General] The new PAP2 v2.0

Tue, 09 Sep 2008 22:15:53 EDT

mazilo :

said by Randy_G :

sure... they are still on sale, $19.97. If you buy three, free shipping.

»www.staples.ca/ENG/Catalog/cat_s···d=591137

The three I got were consecutive serial numbers, 1.0.0.13 firmware.

I wished local Staples stores here in the US have this price. Cheers.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Tue, 09 Sep 2008 15:40:25 EDT

Randy_G : already posted this once, can't see it though after 10 min...
>>

sure... they are still on sale, $19.97. If you buy three, free shipping.

»www.staples.ca/ENG/Catalog/cat_s···d=591137

The three I got were consecutive serial numbers, 1.0.0.13 firmware.

Re: [General] The new PAP2 v2.0

Tue, 09 Sep 2008 14:12:28 EDT

toro :

I picked up three of them on sale for $20 ea

Do you mind if I ask where ?

Re: [General] The new PAP2 v2.0

Mon, 08 Sep 2008 21:14:32 EDT

GrauerFuchs :

said by Randy_G :

Is the VON@GE firmware still in the backup partition? Can it ever get back on the PAP2v2?
I am asking since the part where extracting the encrypted key etc from the VON@GE provisioning file took the majority of the time required, and I don't quite get why I actually need that with (nicely patched) firmware 1.00.16 on there.

Yes. It's still present on the second image. It is possible to remove the second image from the machine(or update that with the patched firmware), but it usually requires direct access to the PAP2's serial console.

What gets reset now on a hard reset? I am running now with the defaults that came up after the .16 update, (and it works fine). Is a hard reset required/recommended after the update? (coming from DD-WRT land where hard-resetting is mandatory after every update ;-) )

Everything is reset on a hard reset, but so long as it has the 'patched' firmware running, the big V's defaults will remain latent.

Is a 3.1.27 still "in the works" since this ATA looks discontinued now? I picked up three of them on sale for $20 ea, but thinking now maybe buying the NA models might have been smarter (for upgrades, like for STUN)

Possibly. If the new adjustments on the drawing board work on the 3.1.24 firmware, it'll be easy to patch the 3.1.27 to do the same. Although the box is discontinued, there are thousands out there. However, if the 3.1.24 bug squashing doesn't work, I may scrap this line of updates and fall back to something more stable (the 0.6) and work on that again.

Last question - I looked HARD for beta .6, can't find it. Any chance of posting/reposting that ?

It wasn't posted. Oops. It may be a bit of time, but as soon as I get the chance (and can retrieve the code to finalize and put together a working version of the patch), I'll post it here. Right now, I'm held back by time constraints and a lack of a PAP2v2 to work on and verify this line of patches.

Re: [General] The new PAP2 v2.0

Mon, 08 Sep 2008 19:31:01 EDT

anon : Sweet , updated PAP2v2 to beta 0.5, THANKS GrauerFuchs!!

I have some questions if you have time.
*
Is the VON@GE firmware still in the backup partition? Can it ever get back on the PAP2v2?
I am asking since the part where extracting the encrypted key etc from the VON@GE provisioning file took the majority of the time required, and I don't quite get why I actually need that with (nicely patched) firmware 1.00.16 on there.
*
What gets reset now on a hard reset? I am running now with the defaults that came up after the .16 update, (and it works fine). Is a hard reset required/recommended after the update? (coming from DD-WRT land where hard-resetting is mandatory after every update ;-) )
*
Is a 3.1.27 still "in the works" since this ATA looks discontinued now? I picked up three of them on sale for $20 ea, but thinking now maybe buying the NA models might have been smarter (for upgrades, like for STUN)
*
Last question - I looked HARD for beta .6, can't find it. Any chance of posting/reposting that ?
*
Sorry if that's too many questions ;-) Thanks!

Re: [General] The new PAP2 v2.0

Fri, 29 Aug 2008 19:32:57 EDT

GrauerFuchs :

said by KillaB7 :

GrauerFuchs, you mentioned awhile back about patching the 3.1.27-ETSI code. Are you still actively pursuing the patch and finding the subnet bug? I'd like to help if possible. Do you figure the problem is buried in the ggsip binary?

It's something that definitely needs to be done, but I haven't had the time to do any work on it at all. Making enough money to survive has taken precedent so far over all of the side projects I currently have on the bench. I have a few theories on how to get rid of the bug, but I haven't had a chance to test them yet. The subnet bug is buried in a combination of the kernel (built to run on similar hardware) and the ggsip package.

I'd like to help with the Asterisk port, but I'm not sure 16MB RAM on the PAP2v2 is enough. After enabling SSH on stock 1.0.13 firmware, I noticed it only had 522bytes free. And that was just sitting idle. What do you think? There's definitely enough Flash space if you where to combine the Primary and Secondary partitions.

It's already been done. Asterisk was running on the PAP2v2, but not quite fully usable. There are also a few questions about how viable it will be to bother with this port, considering the limited resources. Although it has the CPU power to handle 4 PCMA/PCMU channels, there is no license for the other codecs, and even with the g.711 streams, it doesn't have the processor power to spare to manage other boxes even if the RAM is sufficient. This being the case, is it even worth the effort?

Re: [General] The new PAP2 v2.0

Fri, 29 Aug 2008 15:59:46 EDT

KillaB7 : Finally got my hands on a PAPv2 and read through the entire thread again. Since I intend to use it with my local Asterisk server (also on OpenWrt) I just learned that I'll need to use the beta 0.6 patch due to the 192.168.15.1 subnet bug.

GrauerFuchs, you mentioned awhile back about patching the 3.1.27-ETSI code. Are you still actively pursuing the patch and finding the subnet bug? I'd like to help if possible. Do you figure the problem is buried in the ggsip binary?

I'd like to help with the Asterisk port, but I'm not sure 16MB RAM on the PAP2v2 is enough. After enabling SSH on stock 1.0.13 firmware, I noticed it only had 522bytes free. And that was just sitting idle. What do you think? There's definitely enough Flash space if you where to combine the Primary and Secondary partitions.

Re: [General] The new PAP2 v2.0

Fri, 29 Aug 2008 14:56:03 EDT

GrauerFuchs :

said by Nate_M :

Btw, can you please point/direct me to the older 0.6 beta patch you mentioned? (hopefully with instructions too, hehe).

»[General] The new PAP2 v2.0

This will take you to the beta 0.5 file. The only differences from 0.5 and 0.6 were cosmetic. All the information above it and the first bunch of posts below applies to this. The only issue you may have is in getting certain tools to compile on your system. Because of this, you will probably want to unzip the pap2v2-utils archive into your /usr/local/bin directory. Those tools should be compatible with the older patch. You'll need to unzip the utils archive 'unzip {name}', un-tar it 'tar xjf {name.tbz2}',
and then move the programs into the directory. 'mv {name} {name2} ... /usr/local/bin/'
With the beta 0.5 patch, unzip it much as you did the utils archive, and the readme file in there should guide you through the rest of the process.

Re: [General] The new PAP2 v2.0

Fri, 29 Aug 2008 10:10:39 EDT

anon : Thanks GrauerFuchs, I'll take up your advice and start my Linux learning process now...soon or later I'm gonna go the Linux way.... I will not touch the 3.1.24 until I'm more familiar with Linux.

Btw, can you please point/direct me to the older 0.6 beta patch you mentioned? (hopefully with instructions too, hehe).

Thanks for your reply and help, much appreciated.

Re: [General] The new PAP2 v2.0

Fri, 29 Aug 2008 08:05:57 EDT

GrauerFuchs :

said by Nate M :

P/s I'm using XP Pro and know nothing about Linux, lol.

If this is the case, I strongly suggest against trying to patch your PAP2 with the 3.1.24 code until you've had a chance to learn the basics of compiling software, managing, and running a Linux machine from the command line. The patched code works for some and fails for others, and a good, working knowledge of Linux and its commands is essential in recovering from problems. Many of the problems that occur cannot be resolved without extreme frustration in any way other than getting 'in the dirt' so to speak with the code and the underlying operating system and limited toolset.

If you want something reliable and free from the control of the big V, you may want to consider the older 0.6 beta patch. That code is far more stable, since it's little more than a web and back-end patch to remove the VoIP provider's data.

If, however, you still wish to take the risk, you should only need the contents of the patcherplus archive. Make sure the file is in a folder to which you have full access. To extract the files from the command line, you would give the command 'tar xjf pap2patcherplus.tar.bz2' and hit [enter]. There will be a README file in the archive which has all the instructions you need to take it from there. If an error occurs, don't try and load the firmware that it may or may not build. It means something went wrong, and it's probably not going to work.

Re: [General] The new PAP2 v2.0

Thu, 28 Aug 2008 17:17:59 EDT

anon : OK, I got the time now and ready to try/learn something new ;). I just got a new Linksys PAP2 v2.0 and already got it unlock using CTY's patch and tested fine with 2 Voip providers.

I understand that to update to 3.1.24, I will need Linux, so I downloaded slax-6.0.7.tar for USB and also downloaded 1)pap2v2-3.1.24patcher.zip 2)pap2patcherplus.tar.bz2 and 3)pap2v2-utils.tbz2.zip. I will appreciate it very much if any guru here who has got the time to please tell me in details (step by step) how to execute the above FW update or point me to a link with instructions..

Thanks in advance.

P/s I'm using XP Pro and know nothing about Linux, lol.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Mon, 25 Aug 2008 17:39:49 EDT

FireFire : never mind... It works.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Tue, 05 Aug 2008 10:22:32 EDT

GrauerFuchs : wolfboy & kmem: You'd better learn details on how the VTA works. The firmware will need serious changes to be compatible. If you load it the way it is, you'll probably brick your ATA. If you want to port the code over to it, be my guest! The purpose of the project is to free locked boxes for people who are stuck with paperweights anyway. :)

drewlsvern: Does it directly inform you on the flashing page that the flash has succeeded? If so, firmware corruption may be the issue. Make sure you're building the firmware on a writable ext2 or ext3 partition to rule out filesystem troubles. Also, the web flash doesn't always work for all machines for other reasons. If you happen to have one of these that refuses the web flash, try using the serial console flashing method and the tftp firmware.

Nalfa, your problem was answered in the very same post in which I attached the patcher tool you used. The IVR reports false information and does not work properly. The IP defaults to static 192.168.1.254.

Qingz: Sorry, you won't find it here. It is illegal to distribute the binary, even if it wasn't against the patch agreement.
If you are familiar with Linux but simply don't have a machine for it, try the Ubuntu distribution. You can run it directly from CD without installing it. Better yet, consider making a virtual machine on your computer with the free QEMU emulator. Linux is not optional if you do want to get involved with this patch.

To everyone else that wants to try the patch, be warned.

This is DEVELOPER'S code, and a complete hack. It is not and has never been considered a final working product. It is therefore unreliable by nature and damaging to the hardware at worst. You cannot simply flash it and be done. Loading it without understanding the software and hardware will result in you wasting your time and probably also everything you paid for the PAP2!

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Tue, 05 Aug 2008 10:16:32 EDT

mazilo :

said by qingz :

I do not have Linux system. If anybody have the patched binary, please PM me the link to download.

These days, you don't have such an excuse because you can run a Linux Live CD on your computer. I don't mind to make the patch firmware and make it available for certain people who will need it. However, I honestly won't do this for two reasons:

--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Tue, 05 Aug 2008 00:15:17 EDT

qingz : I do not have Linux system. If anybody have the patched binary, please PM me the link to download.
Thanks!

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Mon, 07 Jul 2008 15:25:57 EDT

Nalfa : Hello GrauerFuchs and all members,

I have successfully unlocked my PAP2-v.2 by using CYT. After that I tried to upgrade my PAPA2-v.2 firmware to a patched pap2v2_fw_3.1.24_NA.img by using GrauerFuchs patcher "pap2patcherplus.tar.bz2" and patched "rtp300_fw_3.1.24_US.img" under Linux (ubuntu).

After patching, I do have the 2 images with exact the size as mentioned.
3752085 pap2v2_fw_3.1.24_NA.img.flash
3752093 pap2v2_fw_3.1.24_NA.img.web
So far so good!!!
At this point, I was able to access to my PAP2-v.2 via 192.168.1.100 and login by the default admin/admin then »192.168.1.100/cgi-bin/webcm?getp···ate.html AND login again by Admin/Admin.

I was able to see the firmware update menu at this point and updated to the patched firmware mentioned above.

After it finished and reboot, now I am NO LONGER able to access to my PAP2-v.2, I DOES NOT even get an IP from my Router.
I did reset several times by holding the reset button for 30 seconds each time and nothing has changed. I now have 2 of the LED SOLID green lights (PWR + Internet LED)even WITHOUT connect to a computer or router or switch .

Without connecting to anything but just the Power to the PAP2-v.2 and a telephone plugged to phone 1 port, I did the following:

Pick up your phone and dial: ****
Then dial: 73738#
enter 1 to confirm press # Hang up

100# Check DHCP (enabled)

110# Check IP address ==> 192.168.15.1

130# Check Gateway ==> 192.168.15.1

150# Check Firmware Version ==> 3.1.22

732668# Manual Reboot of Unit

If I connect it to a Switch and manually set my computer to 192.168.15.80 with the gateway: 192.168.15.1 and open IE browser point to: »192.168.15.1/, I just got this ERROR (please see above screen shot):

403 Forbidden
The requested URL '/' resolves to a file which is marked executable but is not a CGI file; retrieving it is forbidden.

Thank you for your time to read this long post. I am just seeking help from you all and not blaming on anyone but just myself for the lack of knowledge but life is full of risk and I am always willing to take the risk to learn.
Thank you again...

Cheers,

PS. Which one of the two files here I should use and do I have to RENAME it like:
pap2v2_fw_3.1.24_NA.img.flash => pap2v2_fw_3.1.24_NA.img or==> pap2v2_fw_3.1.24_NA.img.web => pap2v2_fw_3.1.24_NA.img

Re: [General] The new PAP2 v2.0

Mon, 07 Jul 2008 08:16:36 EDT

anon : See Mzuri's post earlier. If the firmware is not loading it means the firmware is corrupt so although the PAP2 appears to be upgrading it returns to default firware state.

Try changing your Linux distro for patching.

Re: [General] The new PAP2 v2.0

Mon, 07 Jul 2008 05:23:40 EDT

anon : So I decided to try remaking the firmware and realized i'm getting an error when creating the modified files. It goes through the unpacking firmware part, then it says "tar: ./usr/www/versions.txt: Cannot hard link to './etc/versions': Operation not permitted. tar: error exit delayed from previous errors

Done

And then it still continues to make the firmware files.

Any thoughts?

Re: [General] The new PAP2 v2.0

Mon, 07 Jul 2008 05:15:26 EDT

anon : So I applied the (pap2v2_fw_3.1.24_NA.img.web) firmware...but it just reverts right back to the previous config(1.00.13)once it completes the flash. Any Ideas or help is appreciated. I used Ubuntu to create the modified firmware.

Thanks!

Re: [General] The new PAP2 v2.0

Sun, 06 Jul 2008 15:38:37 EDT

kmem : Wolfboy,

I'm in the same boat as you are, I would like to try this firmware on my VTA. There are some instructions on this forum on how to use the PAP2v2 firmware on a VTA. I plan on trying to go from VTA to PAP2v2 and the PAP2v2 to RTP300, but I would think you could bypass the VTA to PAP2v2 part if we had the right files.

Re: [General] The new PAP2 v2.0

Sun, 06 Jul 2008 06:05:50 EDT

anon : GrauerFuchs, thanks for this firmware !

Q : Has anyone applied this firmware (pap2v2_fw_3.1.24) to a DLINK-VTA VR? Both the DLINK and the new Linksys PAP2 seem very similar (in the unmodded firmware)..

there a DLINK VTA VR version of this firmware?

Thanks

Re: [General] The new PAP2 v2.0

Thu, 26 Jun 2008 13:55:08 EDT

notageek : Yeah, I set the secure call parameters to enabled.
I have verified that this works on my voip service provider with 2 spa2002 units.

Hoping for a miracle.

Re: [General] The new PAP2 v2.0

Thu, 26 Jun 2008 05:01:25 EDT

GrauerFuchs : I would assume you also set a vertical service code for secure all calls, secure one call, unsecure all calls, unsecure one call, and then ran the vertical service code for secure all calls on both? If I remember correctly, the internal config for the PAP2v2 on 3.1.24 had also removed the secure service codes, didn't enable SRTP, and didn't set the parameters. You probably need to supply the whole works in the provisioning file for it to have any effect.

It's also possible that it isn't enabled, and that the SRTP code isn't present in the firmware. As of yet, I haven't heard of anyone running the RTP300 with SRTP. The only details on this that I have are direct from the full Linksys ATA administration documentation.

Also, I've found (on other devices) that unless all secure parties are sharing the same CA and SIP server, and the SIP server supports the full pass-on of SIP INFO messages, SRTP connections will never be made.

Your WRTP54Gs are using the same SIP code as the RTP300 and PAP2v2 3.1.24 patch, so what works on one will likely work for the other.

Re: [General] The new PAP2 v2.0

Thu, 26 Jun 2008 02:48:29 EDT

notageek : I have 2 wrtp54g's with firmware version 3.1.24 and I tried to configure the mini certificate (and other related settings) via a provisioning .xml file and it took the file, but the feature did not work when calling between them.

I am under the assumption that this feature was removed from this version of the firmware but exists in the 1.x.x version.

Can anyone shed any light on this?

I am assuming the pap2v2 mod'd firmware is based on 1.x.x sourcecode. I was hoping that my wrtp54g's had this functionality :(

Re: [General] The new PAP2 v2.0

Wed, 25 Jun 2008 17:40:08 EDT

GrauerFuchs : SRTP would be implemented the same way as it is on the RTP300, since that is the code upon which the newest patch is built. As of right now, I don't know of a method to set up SRTP by the web interface. It can be enabled by way of a provisioning file, however. For this, you will need to use the "Mini Certificate" and "SRTP Private Key" XML tags. The mini certificate and key should be in the same format as used by the Sipura boxes.

Re: [General] The new PAP2 v2.0

Tue, 24 Jun 2008 15:13:14 EDT

anon : GrauerFuchs (and others),

Slightly offtopic question, but related to your firmware build...

How is SRTP implemented? I see an enable option and a box for a key, but no location for a MiniCertificate.

Does a MiniCert fill-in box appear after enabling the function or is the MiniCert stored elsewhere?

I don't have a v2 unit and am going off the screen-shots I've seen here of the line1 config page (in admin/advanced mode).

I'm not beyond custom compiling if required to do so.

I'd be very happy if I could implement SRTP on PAP2v2 units.
Thanks,
pap2fan

Re: OMG -still not loading

Sat, 21 Jun 2008 08:22:09 EDT

GrauerFuchs : Try downloading the firmware on the OpenWRT page for RTP300 and see if that makes a difference. Linksys may have bungled their firmware. That wouldn't be a surprise to me at all. Next, if you can, try running the patch on a Gentoo LiveCD or even LFS starter/install CD. My reference platform for compiling the tools was was Gentoo 2007.0.

EDIT:
Well, you beat me to the post. Congrats on getting it going! I know Knoppix works well for many things and for many users, but I've never found it adequate for what I do under Linux.

Sucess

Sat, 21 Jun 2008 08:22:00 EDT

Mzuri : Hi Grauerfuchs,

Success!! :D

You were absolutely right about the corruption. Knoppix involved setting permissions and executing the .sh but resulted in Cannot mkdir & Cannot open errors. So I loaded Ubuntu and ran the command through terminal with smooth execution. Upload was as before except IVR changing to 192.168.15.1. Login to 192.168.1.254 confirmed perfect upgrade.

What can I say? Avoid Knoppix for this project& use Ubuntu or Gentoo as per posting below. Thank you so much & looking forward to your next project. :)

Re: OMG -still not loading

Fri, 20 Jun 2008 16:01:55 EDT

Mzuri : GrauerFuchs. Man you are a great support.

I used knoppix 5 on disk with firmware from Linksys support for RTP 300 . I think the firmware was for RTP v.1 and was the only available firmware as v2 does not appear to have a firmware posted.

The only screen I get after the upgrade reaches 100% is the restart page as I have posted. Although both .flash & .web have the correct byte size, since i am the only person on the forum to have problems - logic would indicate a corruption as you suggest so I will try again. :huh:

Re: OMG -still not loading

Thu, 19 Jun 2008 07:07:39 EDT

GrauerFuchs :

said by can2000 :

Where can I find the 3.1.24 firmware for PAP2 V2.?

The instructions for patching the original firmware are in this thread.

Re: OMG -still not loading

Thu, 19 Jun 2008 07:06:12 EDT

GrauerFuchs : It looks like something went wrong. During the process of building the firmware, it may have been corrupted or refused. Does it give any sort of error after loading, or does it say that it has succeeded? If it came back with an error on the page, it has refused to take the firmware. If that is the case, you will probably have to install it by way of tftp (either in a provisioning file or by using the onboard serial console). If it indicates success and simply doesn't load, that means that it believes the firmware file is corrupt.

What OS/distribution/filesystem are you using when you ran the patch, and where did you obtain the un-patched original firmware?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Wed, 18 Jun 2008 20:01:36 EDT

can2000 : Any instruction to implement the upgrade?

Thanks!

Re: OMG -still not loading

Wed, 18 Jun 2008 19:01:57 EDT

can2000 : Where can I find the 3.1.24 firmware for PAP2 V2.?

thanks!

OMG -still not loading

Wed, 18 Jun 2008 18:40:24 EDT

Mzuri : Well 5 times each with IE,Feurfuchs and Opera, Still not updating. I lose the IVR after update and get it again after pulling the power /restart but still do not have RTP. i am assuming that reset will make no difference to the whole process. pictures below. Thanks :uhh:

Re: Cannot load RTP 3.1.24

Wed, 18 Jun 2008 17:52:40 EDT

Mzuri : Thanks. Your help is much appreciated.
I will try that again a few times then. Is it worthwhile trying the .img.flash trough the web loader or is there another method for that one? Danke.

Re: Cannot load RTP 3.1.24

Wed, 18 Jun 2008 09:03:45 EDT

GrauerFuchs : It sounds like the upload failed or became corrupt. The web interface doesn't always accept the files. On mine, I could only get it to load by web once. Since you still have a viable 1.00.13, try loading it to the device again and see if that works.

Re: Cannot load RTP 3.1.24

Tue, 17 Jun 2008 11:01:24 EDT

Mzuri : Hi Guys & Gurus,
Awesome post. I cannot upgrade to 3.1.24.

I have v 1.00.13 - Cyt unlocked. admin/admin for user & Admin/Admin for voice. pap2v2_fw_3.1.24_NA.img.web renamed to .img & flashed, However firmware does not upgrade to RTP 3.1.24 & after upgrade/restart I still have v 1.00.13 and default ip address that I started with :uhh:.

GrauerFuchs any ideas?

thanks

Re: [General] The new PAP2 v2.0

Tue, 17 Jun 2008 06:52:30 EDT

yahoo2003 : JTAG works for any firmware version,
»[Unlock] JTAG PAP2 V2?
"Ping hack" may work for some versions.

Re: [General] The new PAP2 v2.0

Mon, 16 Jun 2008 23:43:53 EDT

can2000 : I found the pap2V2.0 with firware 1.00.22 is hard to be unlocked. Would anyone please help? Any suggestions will be much appreaciated.

thanks!

Re: blinking power light with the patched rtp300 firmware

Wed, 28 May 2008 14:51:50 EDT

anon : Thanks for your clarification, GrauerFuchs.

said by GrauerFuchs :

An LED can be completely burned out, and it wouldn't pose any additional risk to the ATA.

Now I can give away all my fears! I actually wanted to know whether a burnt-out LED could affect operational behaviors.

said by GrauerFuchs :

Unlike light bulbs, an LED can flash without damage to it, up to its normal lifetime of 35,000 hours or more. This still means more than 4 years of continual light, or more time when flashing.

That means... my flashing LED is just better than a turned-on one. ;)

You gave me peace of mind, have a good day!

Re: blinking power light with the patched rtp300 firmware

Wed, 28 May 2008 13:59:16 EDT

GrauerFuchs : This is the first time I've heard of this happening. Until a solution or cause can be found, let me put your fears to rest. The LEDs don't affect operation of the device. They're just a visual indication of its status. An LED can be completely burned out, and it wouldn't pose any additional risk to the ATA.
What happened here? Nearest I can guess, your unit has simply forgotten to toggle the IO pin that causes the LED to stop blinking. This may be due to a change in configuration, a fluke, or a change in hardware design that isn't severe enough to affect normal operation.
Unlike light bulbs, an LED can flash without damage to it, up to its normal lifetime of 35,000 hours or more. This still means more than 4 years of continual light, or more time when flashing. If it becomes a nuisance, you can always put a piece of electrical tape over it so you can't see the flashing. Either way, it won't do you or your equipment any harm to let this go as it is for now.

Re: blinking power light with the patched rtp300 firmware

Tue, 27 May 2008 16:01:34 EDT

anon : Hi, I am very glad to test the GrauerFucks patch.
In my case, almost everything is perfect! on my PAP2v2 with rtp300 derived pap2v2_fw_3.1.24_NA.img.web, registering a self-managed Asterisk PBX. ;)

But...
The power light has been blinking day and night, and I become little bit worried about losing the device because of one tiny LED. :(
Is there any treat for this issue?

Thanks in advance.

Re: [General] The new PAP2 v2.0

Sat, 17 May 2008 10:32:16 EDT

cgigate : it is nice to use modified fw

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 22:46:39 EDT

GrauerFuchs : Getting the software aboard will be the easy part. The tough part will probably be getting it to interface with the Legerity chip without having to spend the 5-6 digit fee and sign the contracts with the company to get the datasheet and access to the API code, only to not be able to release anything due to licensing incompatibilities.

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 22:02:19 EDT

mazilo :

said by GrauerFuchs :

As you suspected, getting a distribution of the Perl code small enough to fit into the firmware will be its biggest problem. It would likely require a massive re-write of the code, flash partitioning, and operating environment to make this happen.

Try OpenWRT SVN trunk and configure/compile it with AR7 platform support.

I already have a plan in the works to release this device from most of the proprietary elements, as well as converting it to run a native version of Asterisk.

Same as above (OpenWRT SVN trunk). In this case, I believe you will need to downgrade its Linux kernel source to match the same version used on a PAP2v2 firmware.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 21:25:45 EDT

GrauerFuchs :

said by onlinefun :

Anyway, What should I do to run a perl script on PAP2v2 running patched RTP300-NA firmware (Ofcourse - trick is yours and Thank you so much for it - it works very good now) - not sure how to find the perl distribution that can fit and work on this box and once we can get it to work then how can I start a thing everytime PAP2 reboots or the process is killed....appreciate your input on this...even if we can't use for this purpose we can use for other tricks if we can run perl script on the BOX

Thanks for your consideration in looking in to this.

I do not have access to the forum, or a MagicJack device for that matter. That's one piece of hardware I've been avoiding due to the need to tether it to a computer.

As you suspected, getting a distribution of the Perl code small enough to fit into the firmware will be its biggest problem. It would likely require a massive re-write of the code, flash partitioning, and operating environment to make this happen. I already have a plan in the works to release this device from most of the proprietary elements, as well as converting it to run a native version of Asterisk. Unfortunately, I haven't had much time available to run the numbers or even any tests on the viability or demand for such a setup.

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 17:35:53 EDT

onlinefun :

said by GrauerFuchs :

said by mazilo :

Before you even think of doing this, you need to ask yourself this question: Does MJ inject all outgoing calls with its own MJ CID? If so (which I would think so; otherwise, I believe it is an FCC violation), then your effort to inject your own CID is useless.

Agreed. If I remember correctly, the RTP300 firmware (and PAP2v2 unmodded, etc.) validates and sends the CID information to the server as part of the registration process. Changing the information in the form to something completely different will cause it to fail on registration.
The only exception I have found so far is the following:

Using SipPhone as a provider, you can set the CID number to your purchased POTS dial-in number instead of the SIPPhone SIP number.

This, of course, doesn't violate any laws. It still provides a valid call-back ID.

We are not going to be changing all the SIP packets...if you look in to the perl script in my link it simply appends Asserted Identity tag (this is what I understood) seems to make the trick - may be a BUG on MJ side but it works now with a perl script on my computer (or an Windows app based on the same trick) - look at UDP packets on a port and change so that it won't cause issue...let me know if you want me to send the script from that forum (if you don't have access to it)

Anyway, What should I do to run a perl script on PAP2v2 running patched RTP300-NA firmware (Ofcourse - trick is yours and Thank you so much for it - it works very good now) - not sure how to find the perl distribution that can fit and work on this box and once we can get it to work then how can I start a thing everytime PAP2 reboots or the process is killed....appreciate your input on this...even if we can't use for this purpose we can use for other tricks if we can run perl script on the BOX

Thanks for your consideration in looking in to this.

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 16:19:54 EDT

mazilo :

said by toro :

You should try the 3.1.24/3.1.22 firmware patched by GrauerFuchs.

Ultimately, that will be my solution. At this point, I still like to play around with this old freaky firmware to learn more. :D

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 16:17:19 EDT

toro : You should try the 3.1.24/3.1.22 firmware patched by GrauerFuchs. I have 2 units connected to my Asterisk (over internet, my Asterisk is in a different location) running without problems for more than 3 and a half months. I even stopped using PAP2v1, I like the v2 better.

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 13:28:25 EDT

mazilo : Regarding this post where I said the key to make your PAP2v2 to work with two Lines running on a Vonage firmware v1.00.13 is to leave empty the Proxy Server and Registrar Address Proxy Server fields on the Default Proxy section under the SIP Menu, I would like to make some correction here that it was too premature for me to make such a statement that it NO longer holds true. After a few weeks running in this mode without a problem, last night I found my PAP2v2 started to behave erratically and it no longer wanted to register to my asterisk system. :( Well, at least I had some good weeks with my PAP2v2. ;)
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 13:09:39 EDT

GrauerFuchs :

Re: [General] The new PAP2 v2.0

Fri, 16 May 2008 08:18:16 EDT

mazilo :

said by onlinefun :

Why can't we do this on RTP300 itself thru some patch? - either on RTP's web package (similar to what windows app is doing) (or) may be fiddle with Voip package itself to modify SIP packets!

Before you even think of doing this, you need to ask yourself this question: Does MJ inject all outgoing calls with its own MJ CID? If so (which I would think so; otherwise, I believe it is an FCC violation), then your effort to inject your own CID is useless.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Thu, 15 May 2008 22:53:30 EDT

onlinefun :

said by onlinefun :

Hello GrauerFuchs and Team...

Thank you so much for the information in this thread...finally was able to finally put RTP's patched firmware on PAP2v2 - ofcourse, after reading the thread multiple times and carefully following instructions...

Now here's the challenge...I think you guys definetly would love to solve it!

I am planning to use this now with MagicJack a/c for outgoing calls and would like to continue to use Grand Central number for Outgoing Caller-ID. This is now possible thru an windows app or perl script (Thanks you Stewart / MagicHack). Here is the thread about how this is being done...
»unofficialmagicjack.forum2u.org/···t68.html

Why can't we do this on RTP300 itself thru some patch? - either on RTP's web package (similar to what windows app is doing) (or) may be fiddle with Voip package itself to modify SIP packets!

Hope to have this cool feature and totally free computer from my VoIP calls...

Thanks!

Hello GrauerFuchs... what do you think about this? Is it possible if somebody come up with an app doing the same thing as the Stewart's perl script?

==== my POST on other forum ===
»unofficialmagicjack.forum2u.org/···561.html
========
Hello Guys,

Anybody up for a spoofer app that can work on any linux system...

This is what I am dreaming!!! for:
I was able to patch PAP2v2 firmware from RTP300 using the beautiful instructions by GrauerFuchs from »Re: [General] The new PAP2 v2.0 - Firmware 3.1.24! (very good thread with good info about VoIP and firmware...)
Now...it looks like one could put any app we want and put in firmware and make it to start (I think some tweaking required) and let this app take care of Spoofing :wink: and not to have a computer on! may be app can read from a .txt file to read your info required (number etc.,) which we can put before creating firmware (or) someway to putting on PAP2v2 using SSH

Hope I am making sense here!
====

Re: [General] The new PAP2 v2.0

Thu, 15 May 2008 02:14:40 EDT

onlinefun : Hello GrauerFuchs and Team...

Thank you so much for the information in this thread...finally was able to finally put RTP's patched firmware on PAP2v2 - ofcourse, after reading the thread multiple times and carefully following instructions...

Now here's the challenge...I think you guys definetly would love to solve it!

I am planning to use this now with MagicJack a/c for outgoing calls and would like to continue to use Grand Central number for Outgoing Caller-ID. This is now possible thru an windows app or perl script (Thanks you Stewart / MagicHack). Here is the thread about how this is being done...
»unofficialmagicjack.forum2u.org/···t68.html

Why can't we do this on RTP300 itself thru some patch? - either on RTP's web package (similar to what windows app is doing) (or) may be fiddle with Voip package itself to modify SIP packets!

Hope to have this cool feature and totally free computer from my VoIP calls...

Thanks!

Re: [General] The new PAP2 v2.0

Tue, 06 May 2008 16:16:40 EDT

crapoid685 : I tried all suggested solutions and none of them solved my problem. GrauerFuchs, I tried your settings and I did not see any changes with the behavior of my unit. Mazilo, I tried your settings, and the only difference is that the person on the other end of the line has an echo. There is no difference in the length that my unit stays up. In my voice log, I have a SIP/2.0 401 Unauthorized entry. I think this is why my unit is not staying up, but I don't have any idea on how to troubleshoot this issue. I don't think that my username or password is wrong (all settings are available in my viatalk control panel).

I would like to know the best way to retrieve my provision.xml and config.xml files (on GrauerFuchs' 1.00.16 firmware) and put the edited versions back on my device, just in case I have to edit these files manually?

Re: [General] The new PAP2 v2.0

Mon, 05 May 2008 09:44:03 EDT

mazilo :

said by biggys :

Register Expires: set this lower so the connection is not timming out

I don't see this option on my PAP2v2, except a Reg Expire Timer. If this is the same option, you will notice it is set to 60,000ms (1 minute) on my PAP2v2 as shown on SIP Menu of my snapshot above or from my asterisk-1.4.19.1 CLI as follows:

BTW, is 1 minute low enough or can you be more specific in this matter? AFAIK, the only way to set this value beyond 99 seconds is through an XML provision file. IIRC, you should be able to search in this forum one (if not several) of my old posts where I had mentioned to my PAP2v2 and/or (Dlink) VTA-VR with 99 seconds (manually) or 30 minutes (through an XML provision file) and they didn't fail during my one week tests.

--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Mon, 05 May 2008 05:04:55 EDT

anon : Here is the problem you are having i bet

i have a pap2 aswell when i set it up year ago now works great i great free incomming and out :)

Register Expires: set this lower so the connection is not timming out

Re: [General] The new PAP2 v2.0

Fri, 02 May 2008 19:23:43 EDT

mazilo : Here is the update on my PAP2v2 unit. I has survived running continuously for more than 4 days without any interruptions. So, I decided to reboot and power cycle my PAP2v2. I noticed one problem here that it randomly takes a long time, i.e. from 1 minute to several hours, for my PAP2v2 to register the lines to my asterisk-1.4.19.1 system after a reboot and/or power cycle. Honestly, I have no idea why. However, once the lines are registered, they stay solid.

If you are interested in my configuration, see the above attached snapshots on the SIP and Line1 menu. The configuration on Line2 is the same as Line1, except it was on different extension number. AFAIK, the key to make your PAP2v2 to work with two Lines running on a Vonage firmware v1.00.13 is to leave empty the Proxy Server and Registrar Address Proxy Server fields on the Default Proxy section under the SIP Menu. I don't know if Vonage has fixed this problem with newer version firmware. If you have a CYT device, i.e. DLink VTA-VR, etc., and it is behaving erratically with random disconnections, perhaps this hack will do the trick to resolve the problem. Give it a try and post your feedback here.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

PAP2v2 -- SIP Menu
PAP2v2 -- Line1 Menu

Re: [General] The new PAP2 v2.0

Wed, 30 Apr 2008 12:41:36 EDT

GrauerFuchs :

said by crapoid685 :

I changed the Notify Interval from 0 to 3600. Unfortunately, this did not work. Should I keep adjusting this interval? Any other suggestions or further info that I can provide?

It might be time to re-check the port forwarding. Make sure you have the SIP TCP and UDP Listen ports forwarded respectively for TCP and UDP messages, and the RTP port range (your set range as per the PAP2 SIP configuration) forwarded for UDP.
Next, verify your Reg Expiry Timer is also set to 3600 or lower. Do not set this value too low. Extremely low values (under 600) may upset providers. In addition, set your Reg Fail Retry Timer to a lower value. I recommend 300-900 here.

Re: [General] The new PAP2 v2.0

Wed, 30 Apr 2008 12:18:36 EDT

mazilo :

said by crapoid685 :

I have 1.00.16 NA installed.

My PAP2v2 still runs on Linksys released v1.00.13 firmware stowed on some shelves. So, I just took it out and put to use to see if it will still run with no problems. Now, it is configured as extensions to my asterisk-1.4.19.1 running on my LaFonera WiFi router with OpenWRT SVN firmware. So far, both lines have been steadily registered for more than two hour. Let's see if it will pass one day without any problem.

I was just asking if I should upgrade to 3.1.24, if it would help to take care of my problem.

Linksys firmware v3.1.24 uses STUN/OutBound Proxy approach. Vonage v1.00.16 firmware uses Registrar Address Server approach.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Wed, 30 Apr 2008 10:44:44 EDT

crapoid685 :

said by mazilo :

I haven't used this modded firmware; however, I am not sure if you have confused me or something isn't right here. You had flashed your PAP2v2 with a modded v1.00.16 firmware and then upgraded to v3.1.24? if your PAP2v2 is running on a modded v3.1.24 firmware that has Sipura look, then use the STUN options.

I have 1.00.16 NA installed. I was just asking if I should upgrade to 3.1.24, if it would help to take care of my problem.

Re: [General] The new PAP2 v2.0

Wed, 30 Apr 2008 09:44:27 EDT

mazilo :

said by crapoid685 :

I unlocked my pap2 using CYT and then I used GrauerFuchs' 0.5b patch to load a NA 1.00.16 firmware on to my device...

... Do I need to use STUN options(upgrade to 3.1.24)?

I haven't used this modded firmware; however, I am not sure if you have confused me or something isn't right here. You had flashed your PAP2v2 with a modded v1.00.16 firmware and then upgraded to v3.1.24? if your PAP2v2 is running on a modded v3.1.24 firmware that has Sipura look, then use the STUN options.
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Wed, 30 Apr 2008 08:57:21 EDT

crapoid685 :

said by GrauerFuchs :

Check on your SIP settings page for the Notify Interval and set this to a figure of 3600 seconds. It sounds to me like your registration is timing out, and the viatalk is forgetting that you are connected. Adjusting/lowering the Notify Interval to an hour (assuming the PAP2v2 defaulted to a higher value) should resolve this.

I changed the Notify Interval from 0 to 3600. Unfortunately, this did not work. Should I keep adjusting this interval? Any other suggestions or further info that I can provide?

Re: [General] The new PAP2 v2.0

Mon, 28 Apr 2008 20:29:27 EDT

GrauerFuchs :

said by crapoid685 :

My problem is that my phone drops out every 4-8 hours and then I have to restart my PAP2 v2 for it to work again. During that 4-8 hours I can make and receive calls as usual.

If you consistently lose your connection after 4 to 8 hours, but it runs properly before this time, the ports shouldn't need changing. Check on your SIP settings page for the Notify Interval and set this to a figure of 3600 seconds. It sounds to me like your registration is timing out, and the viatalk is forgetting that you are connected. Adjusting/lowering the Notify Interval to an hour (assuming the PAP2v2 defaulted to a higher value) should resolve this.

Re: [General] The new PAP2 v2.0

Mon, 28 Apr 2008 16:56:44 EDT

crapoid685 : I previously had vonage and I switched to viatalk. I have a pap2 v2 that was previously provisioned to vonage. I unlocked my pap2 using CYT and then I used GrauerFuchs' 0.5b patch to load a NA 1.00.16 firmware on to my device. The first time I brought it up, there were vonage provisioning settings still visible, so I did a factory default and the vonage stuff was gone. So now I have a problem that I am trying to work through. Hopefully you guys can help.

My problem is that my phone drops out every 4-8 hours and then I have to restart my PAP2 v2 for it to work again. During that 4-8 hours I can make and receive calls as usual. I signed up for the BYOD plan on viatalk and they emailed me the settings I should use on an unlocked device(their default unit is the original PAP2). The settings were: proxy server, username(1 + my 10 digit phone number), and password. I can fill in that info only on line1 and my phone will work, or I can have those settings filled in on SIP and line1 and my phone will work, but no matter what, it will stop working after a while. I have the proper ports forwarded as previously stated in this thread, however the phone has the same problem whether I have the ports forwarded or not. I know that viatalk will provision an original PAP2 but I don't know if the v2 will take the same file/settings. I want to know how to send my unit a custom provision file(if possible/needed) and where I should begin on trying to troubleshoot this problem further. What other info do you guys need that would help(logs, etc.)? Do I need to use STUN options(upgrade to 3.1.24)?

I know that is a handful of questions but I have been following this thread for a while and would like to get my unit up for good. Hopefully this post can also help others. BTW Thank You GrauerFuchs, and everyone else who has a hand in the modded firmware and support.

Re: [General] The new PAP2 v2.0

Thu, 24 Apr 2008 09:52:44 EDT

mazilo :

said by GrauerFuchs :

Besides, if you're unable or unwilling to build the patched firmware, you really shouldn't be running it anyway.

I am glad to hear what you had to say above. I was going to reply to this post exactly like this, but thought it would be too harsh that the admin/system/mods on this forum will tend to remove my post. So, now that you had posted this, I just ditto it.

All the PAP2v2 patched firmwares have a high risk of problems, and you need to be able to work around the problems you find when they do come up. If you want something simple and easy, you should spend the extra $30-$40 more than you paid for your locked box and get an adapter that's already unlocked.

Or, get all PAP2v2 owners to write to Linksys and demand it to develop its firmware with Sipura interface. :D
--
Mazilo always prays for FREEBIES!
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Thu, 24 Apr 2008 09:18:59 EDT

GrauerFuchs :

said by ilhy :

Do you have the link to rapidshare? PM me if yes.

Simple answer: No.

Detailed answer: It would be in violation of the patch agreement and of US copyright law. Therefore, The Big V (provider) who is already in financial difficulty would be very happy to sue you if you did make available the binary code you don't have the rights to distribute.

You don't need to install Linux to make the patched firmware, either. You can run a Linux live cd, or even a micro distro like Damn Small Linux (DSL, 50MB) in a virtual machine. This way, no permanent changes are made to your computer. Besides, if you're unable or unwilling to build the patched firmware, you really shouldn't be running it anyway. All the PAP2v2 patched firmwares have a high risk of problems, and you need to be able to work around the problems you find when they do come up. If you want something simple and easy, you should spend the extra $30-$40 more than you paid for your locked box and get an adapter that's already unlocked.

Re: [General] The new PAP2 v2.0

Wed, 23 Apr 2008 23:36:26 EDT

ilhy : Do you have the link to rapidshare? PM me if yes.

Re: [General] The new PAP2 v2.0

Wed, 23 Apr 2008 14:23:53 EDT

anon : someone post a rapidshare link to the new test firmware... I need a firmware that will allow 20 or so password characters & supports alphanum letters in logins etc

Re: [General] The new PAP2 v2.0

Wed, 23 Apr 2008 13:13:09 EDT

mazilo :

said by Dave5512 :

I don't want to install linux just to compile 1 file.

What?!

Re: [General] The new PAP2 v2.0

Wed, 23 Apr 2008 12:13:27 EDT

anon : can anyone post a link to the binary files for the firmware... I don't want to install linux just to compile 1 file.

Re: [General] The new PAP2 v2.0

Mon, 21 Apr 2008 15:56:15 EDT

omcdr : Thanks it working ;)

Re: [General] The new PAP2 v2.0

Mon, 21 Apr 2008 11:42:39 EDT

toro : Ignore the IP you get through the IVR, it always says 192.168.15.1 no matter what the actual IP is.
- factory default your PAP2v2 (by holding the Reset button until the lights start flashing - approx 8 sec)
- now the IP address will be 192.168.1.254 (static)
- change your computer's IP to something like 192.168.1.10
- login to the PAP2's web interface at the address above and change it to whatever you like, or DHCP

Re: [General] The new PAP2 v2.0

Mon, 21 Apr 2008 09:56:29 EDT

omcdr : I have tried to upgrade my PAP2 v2, I used GrauerFuchs path and generate image pap2v2_fw_3.1.24_NA.img.web.
I used www upgrade form, upgrade went fine, but I can login to my PAP2 gateway. IVR config menu works, I can check IP address is: 192.168.15.1, firmware version is: 3.1.22. I can't ping PAP2, network don't working, I can't change IP manually, PAP2 don't send any packet or DHCP request.
Console working, but I can't log in with default: admin/admin or Admin/Admin, login is incorrect.

ESC at power up didn't work.

How to repair my PAP2 gateway ? What is wrong ? Only JTAG will help ?

This is my log from my console.

pap2-log.zip 10,174 bytes
console log

Re: [General] The new PAP2 v2.0

Sun, 06 Apr 2008 07:12:32 EDT

yahoo2003 :

said by GrauerFuchs :

The 3.1.24 firmware is not recommended for the average user. It is a development test version. This means that it still has some major flaws, especially since this device was never intended to run that code. You could easily end up with a box that will not work at all. Plus, once you upgrade to this test firmware, going back to the old code may not be possible.

I found it out the hard way. 3.1.24 for RTP300 has different ways to partition flash, it puts voice configuration ("SPA"? or "fpar") separately from CONFIG_A and CONFIG_B after the first boot. I had to clean all flash blocks except bootloader and env and then reload 1.00.16-NA using serial cable. It may be possible to load 1.00.16-NA from SSH but I have not tried it.
1.00.16-NA worked great compared with original PAP2V2.

Re: [General] The new PAP2 v2.0

Sun, 06 Apr 2008 06:40:43 EDT

GrauerFuchs : The 3.1.24 firmware is not recommended for the average user. It is a development test version. This means that it still has some major flaws, especially since this device was never intended to run that code. You could easily end up with a box that will not work at all. Plus, once you upgrade to this test firmware, going back to the old code may not be possible.

If you still wish to use the firmware, you need to go through the steps listed. We cannot provide a pre-made firmware due to legal restrictions and licensing agreements. You must acquire and build the binary yourself, according to the provided instructions.

Re: [General] The new PAP2 v2.0

Sun, 06 Apr 2008 05:14:25 EDT

anon : I have 1.0.0.16 firmware on unlocked PAP2V2.
Mazilo,
Can you or someone help me how to upgrade to the latest firmware 3.1.24.
Do I need to use all the steps or just update the firmware ??
please email me bellamkondagmaildotcom
or my yahoo ID : saravi_2000
Thanks
Sarath

Re: [General] The new PAP2 v2.0 with Acanac!

Fri, 04 Apr 2008 20:22:23 EDT

TJ_in_IL :

said by GrauerFuchs :

A few tips I've noted of value when dealing with config problems on the unmodified but unlocked PAP2v2:

Make sure your caller ID name matches your username.
Configure your router to forward ports 5060-5061 TCP and UDP to your PAP2.
Configure your router to forward ports 16384-16480 UDP to your PAP2.
Set your PAP2 to accept RTP on ports 16384-16480.
Manually set the external IP address on your PAP2.
Configure an outbound proxy server for your provider.

Don't forget username has to be a numeric value. Any alpha characters will not work. I had this happen to mine.
FWIW.... I do not have to forward any ports or put in DMZ for mine to operate. I use a static ip, not dhcp, just so I have a bookmark to access, and not have a swinging ip address.

TJ

Re: [General] The new PAP2 v2.0 with Acanac!

Fri, 04 Apr 2008 19:40:21 EDT

GrauerFuchs : A few tips I've noted of value when dealing with config problems on the unmodified but unlocked PAP2v2:

Make sure your caller ID name matches your username.
Configure your router to forward ports 5060-5061 TCP and UDP to your PAP2.
Configure your router to forward ports 16384-16480 UDP to your PAP2.
Set your PAP2 to accept RTP on ports 16384-16480.
Manually set the external IP address on your PAP2.
Configure an outbound proxy server for your provider.

Re: [General] The new PAP2 v2.0 with Acanac!

Fri, 04 Apr 2008 12:40:31 EDT

anon : Hello everyone,

I am just new here (so please easy on me if you would/could).

I have an UNLOCKED PAP2 v2.0 and try to setup for Acanac VoIP service but unsuccessful to do so. I have the user ID, password and registrar server address which Acanac provided to me and I first signed for their service.

I was ABLE to made for one of my PAP2 v1 working with Acanac but for the same info, I CAN NOT make my PAP2 v2.0 work as the PAP2 v1 (either behind or on front of a router), the PAP2 v2.0 simply is NOT able register with Acanac Voice server...

I have asked Acanac for help to setting up BUT they said the PAP2 v2.0 is NOT in their support ATAs list!!! :mad:
Acanac! YOU ARE NOT very helpful!!! :(

I have nowhere to turn to but hope that this community with lots of gurus who would help in my case, all help and opinions would be much appreciated.

Cheers.

Re: [General] The new PAP2 v2.0

Fri, 04 Apr 2008 08:22:59 EDT

GrauerFuchs : Unless I misread the details on STUN, it doesn't affect the client communication at all. All it does is accept a connection from your ATA and respond with the IP, port(s), and other parameters it received. This way, your ATA can auto-configure itself and properly identify itself to clients and servers. The ATA may be sending a SIP message to the server revealing the fact that it is using STUN, but that's about it.

Re: [General] The new PAP2 v2.0

Thu, 03 Apr 2008 08:24:39 EDT

drdr6 :

said by GrauerFuchs :

1) No, it looks like that's something the provider is enforcing for some reason.

2) Yes, you need to adjust the registry timeout. It's probably set at 3600 , so you'll need to drop it down to match the 600.

I had a word with the provider & they said they couldn't recommend using STUN, since their server spots the STUN server and gives out a default 600s timeout.

It seems that if they see a client behind a NAT, their server sends keep-alives from the WAN side, so port forwards shouldn't be necessary. However that probably doesn't work in a double NAT which is what I'm stuck with.

I apologise if I'm asking really dumb stuff here, but is it possible to use stun to get the WAN side IP address and do that translation only in the outbound SIP messages, rather than having the STUN server dynamically involved in calls ?

Re: [General] The new PAP2 v2.0

Thu, 03 Apr 2008 07:48:53 EDT

GrauerFuchs :

said by drdr6 :

The original 200 OK registration reply contains "Expires=600" which explains why it times out after 10 minutes.

Two questions:
1) Is it normal to get expires=600, or is this symptomatic of something else not working properly ? I see the provider's help guides advising 3600 in registration timeout settings

2) Shouldn't the PAP2 be trying to re-register after 600, since this is what it's been told by the provider ? I see SIP keepalives running every 15 seconds, but no attempt to re-register itself. Is this another setting that needs changing somewhere ?

1) No, it looks like that's something the provider is enforcing for some reason.

2) Yes, you need to adjust the registry timeout. It's probably set at 3600 , so you'll need to drop it down to match the 600.

Re: [General] The new PAP2 v2.0

Wed, 02 Apr 2008 19:13:19 EDT

drdr6 :

said by nitzan :

said by drdr6 :

Router
Forward 5060-5061 TCP
Forward 16384-16482 TCP+UDP

Shouldn't this be UDP for both? :)

Typo: meant TCP+UDP for both

Also - looks like I am not out of the woods yet.
Incoming calls work for 10 minutes only; after which the regsitration expires and the PAP2 does not renew.

The original 200 OK registration reply contains "Expires=600" which explains why it times out after 10 minutes.

Two questions:
1) Is it normal to get expires=600, or is this symptomatic of something else not working properly ? I see the provider's help guides advising 3600 in registration timeout settings

2) Shouldn't the PAP2 be trying to re-register after 600, since this is what it's been told by the provider ? I see SIP keepalives running every 15 seconds, but no attempt to re-register itself. Is this another setting that needs changing somewhere ?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Tue, 01 Apr 2008 00:33:28 EDT

nomadic :

said by GrauerFuchs :

quote:
I was wondering if there are any issues using 3-way calling with this patched firmware.

This is the first I've heard of it. I haven't tested 3-way calling on this firmware. Can anyone else confirm this?

Hmmm! looks like I'm the only lucky guy facing this issue.
BTW, in line 57 of usr/www_safe/html/admin/user.html there is a call to an undefined function RemoteWebChange().

Re: [General] The new PAP2 v2.0

Sat, 29 Mar 2008 23:04:29 EDT

nitzan : Wouldn't hurt anything to enable both I guess. :)

Just make sure UDP is also enabled.

Re: [General] The new PAP2 v2.0

Sat, 29 Mar 2008 10:39:15 EDT

GrauerFuchs : TCP+UDP might work better for the 5060-5061, you're right. I haven't run a packet trace on the protocol used by the PAP2v2, but I have heard reference to some devices sending SIP messages by TCP and others by UDP.
As far as the RTP port set, you're right. By specification, it should be only UDP. Unfortunately, I've run into situations where for whatever reason, cheap SoHo routers have gotten confused and erroneously handle IP traffic if the TCP is not forwarded while UDP is.

Re: [General] The new PAP2 v2.0

Fri, 28 Mar 2008 23:17:28 EDT

nitzan :

said by drdr6 :

Router
Forward 5060-5061 TCP
Forward 16384-16482 TCP+UDP

Shouldn't this be UDP for both? :)
--
Nitzan Kon, CEO
Future Nine Corporation

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 28 Mar 2008 21:53:30 EDT

GrauerFuchs :

quote:
I was wondering if there are any issues using 3-way calling with this patched firmware.

This is the first I've heard of it. I haven't tested 3-way calling on this firmware. Can anyone else confirm this?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 28 Mar 2008 17:56:02 EDT

nomadic : I was wondering if there are any issues using 3-way calling with this patched firmware.

I tried the following:
1. Called person A
2. Pressed the 'flash' key and dialed person B
3. Pressed the 'flash' key
4. I was able to talk to person A and B
5. Hung-up the call

The ATA lost dial-tone and wouldn't accept incoming call afterwards.
I recycled the power on the ATA and it was back to normal.
I repeated this test couple times with same result.

The ATA registers to an asterisk (v 1.2.26) box (don't know if that matters)

Re: [General] The new PAP2 v2.0

Fri, 28 Mar 2008 11:46:16 EDT

mazilo :

said by drdr6 :

outbound proxy: proxy.localphone.com
use outbound proxy: yes
use OB proxy in dialog: yes

Your device should be configured with a STUN server unless it is connected to a symmetrical NAT/Firewall router. With an outbound proxy server, all the RTP traffics will go through the outbound proxy server which will add some latencies.
--
Mazilo always prays for FREEBIES! :D
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Fri, 28 Mar 2008 08:03:56 EDT

GrauerFuchs : Excellent news! Glad to hear it's good to go for you. Please let me know if any new bugs creep up while it's in use.

Re: [General] The new PAP2 v2.0

Fri, 28 Mar 2008 06:33:03 EDT

drdr6 : Well, I have it working (calls in and out)

The final change required was to set
proxy: localphone.com
outbound proxy: proxy.localphone.com
use outbound proxy: yes
use OB proxy in dialog: yes

Consider it closed!
Brilliant patch - useable even with quite a tricky setup!

Many thanks

Re: [General] The new PAP2 v2.0

Fri, 28 Mar 2008 04:58:49 EDT

drdr6 : It does look that way. I'm pretty sure about the username and password because the SIP REGISTER request is succeeding and if I change either of them, register fails & the PAP doesn't give a dialtone.

I'm wondering if localphone doesn't normally operate this way with the proxy (their softphone doesn't use the proxy at least by default).

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 23:45:03 EDT

GrauerFuchs : Check your outbound proxy and SIP proxy server settings. Also, verify your username and password are correct.

If they are, set the caller ID display name to the same thing as your username and try connecting again. It looks like your provider is refusing you access.

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 19:32:40 EDT

drdr6 : So in brief:

On the failed outgoing call I see:

PAP2-> myproviderIP sip request INVITE SIP:myaddr@proxy.mysipprovider, with session description

proxy.myproviderIP -> PAP2 sip status 407 Proxy authentication required

PAP2-> proxy.myproviderIP sip Request ACK sip NumberIdialled@proxy.myprovider

PAP2-> myproviderIP sip request INVITE SIP:myaddr@proxy.mysipprovider, with session description

proxy.myproviderIP -> PAP2 sip status 403 Fake FROM - use From=id next time

PAP2-> proxy.myproviderIP sip Request ACK sip NumberIdialled@proxy.myprovider

all of the above happening on src=5060, dst=5060

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 18:38:27 EDT

drdr6 : Oops sorry for last posting

I changed to your settings (mine were only different in the RTP port range) and no joy

I'll get wireshark going again and see if I can figure out what's not getting through.

Thanks for your suggestions mazilo and GrauerFuchs

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 18:35:54 EDT

drdr6 : PAP2 -
Set RTP port min to 16384
Set RTP port max to 16482
Set SIP port to 5060 (or 5061 for line 2)

Router
Forward 5060-5061 TCP
Forward 16384-16482 TCP+UDP

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 13:13:27 EDT

GrauerFuchs : Manual port forwarding shouldn't be needed, but unfortunately, many peers are set to refuse VIA messages. This can cause problems when dealing with STUN-configured boxes (or at least it has on all of mine as well). I've manually configured my PAP2/SPA2001 to use a set of ports, and also ensured those are forwarded to the box on its statically allocated IP. For instance, here is what I have tested and still use:

PAP2 -
Set RTP port min to 16384
Set RTP port max to 16482
Set SIP port to 5060 (or 5061 for line 2)

Router
Forward 5060-5061 TCP
Forward 16384-16482 TCP+UDP

STUN does not need forwarding unless you intend to run a STUN server behind your router.

I've done similar for the PAP2v2 under test, and it works properly with the forwards in place but not without the forwarding in place. In addition, don't try to make a peering call from your computer (same subnet) to your PAP2v2 or vice versa. It won't work, and will drive you crazy trying to figure out why. Bounce the call off the SIP provider if you need to locally test it.

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 08:28:58 EDT

mazilo :

said by drdr6 :

I have ports 5060-5061 and 20000-21000 and 3478-3479 forwarded to the PAP2 - I don't suppose you have any ideas ?

If you have your PAP2v2 configured with STUN options, manual labors on ports forwarding are not needed. Make sure on each configured line, you have NAT traversal options enabled, too.

Re: [General] The new PAP2 v2.0

Thu, 27 Mar 2008 05:35:41 EDT

drdr6 : GrayerFuchs, that was excellent. I can now register with my SIP provider and I see SIP requests going out with the WAN address in place as it should be.

It took me a while to notice that the NAT settings weren't taking, because I had my PC aand the PAP2 on a hub behind the router so that I could snoop the packets. This was leading to packet loss & so the web pages weren't always completing properly before I was trying to send them back - hence no settings update.

I also had some issues with the service provider giving confusing messages about what the login ID was.

So I'm nearly there - I can receive incoming calls, but can't make outgoing ones. Down on the wire, the same set of RTP ports seem to be being used (20000-21000) but after ratcheting up through 4 or 5 of them the outgoing call gives up. Incoming uses ports in the same range & works - so I think my port tunnelling is working.. I have ports 5060-5061 and 20000-21000 and 3478-3479 forwarded to the PAP2 - I don't suppose you have any ideas ?

Thanks for you patience...

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 20:45:47 EDT

GrauerFuchs : The appearance of 192.168.15.1 is the very same bug that causes it to fail without NAT traversal. The voice module is currently incapable of reading or understanding the network settings.

STUN also needs a few more settings turned on for it to work properly. You have to enable NAT and STUN settings. I've included viable, tested screenshots with the configuration I use for reference. Both are logged in as admin with advanced view. The first is a segment of the SIP page, and the second is from the Line? page. The result of these settings enables full STUN support, and tells the device to understand the connection through the router.

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 20:04:20 EDT

drdr6 : Well, as usual I can't seem to duplicate results.
Yesterday, the device reset itself to 192.168.1.254 three times after printing the message

PAP2v2? is updating your configuration. Unit may reset.
You will be redirected to the configuration page in 30 seconds.
If not, you can click HERE to return to the configuration page.

Today, I've done it about a dozen times, and, as you say, the ip address is holding at 192.168.2.10.

However, I still can't get it to register.
I see 50 or more SIP messages sent, 0 received.
Looking at the wire with a PC running wireshark connected to a 10Mb hub, I see the SIP requests going out, but with the IP address 192.168.15.1 (as the ****110# reports).

Contact: 44122379xxxxx [sip:44122379xxxxx@192.168.15.1:5060];expires=3600

I've got STUN turned on - did exactly what I did yesterday, but today it takes it.

However I see no messages to the stun server, when entered as
stun.stunserver.com or
stun.stunserver.com:3478
stun enable is "yes", stun test enable is "no"
I tried setting ext IP to my external IP address, but that didn't alter the SIP messages - still contain 192.168.15.1

I see my provider being resolved correctly, so I assume it can resolve the stun server correctly

I've got a syslog server set up; monitoring through the voice/system/misc settings and the admin/log/ settings - different messages reported, but no obvious SIP messages.

It does report that some part of the system thinks it's running on 192.168.15.1:

2008-03-25 23:41:48 Local0.Info 192.168.2.10 System started: ip@192.168.15.1, reboot reason:W4

So I'm hoping you can throw some light on:

1) Why the split personality with http answering on 192.168.2.10 and voice trying to use 192.168.15.1 - though I'm guessing this is because of the way the voice is grafted in. Is this what you see in your system ?

2) Any ideas for kicking STUN into life ?

Thanks in advance ...

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 13:35:11 EDT

GrauerFuchs : Changing the IP address does work. I use a different subnet for testing as well. Here's what I've done, and it's been able to stick every time:

Log in at the original address and change your IP. Click save.
Browse to the new IP and enter the remaining changes on the network setup page. Click save.

From here on out, until you run a factory reset, I have yet for the PAP2v2 to fail in retaining the new IP, gateway, or DNS entries.

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 13:30:17 EDT

drdr6 :

said by GrauerFuchs :

Please keep in mind that as of right now, this patch is still in the experimental and temperamental stages of development. Some of the major bugs (you've already run across a couple of them) are proving very difficult to resolve without a large outlay of cash to acquire the appropriate sources and documentation for the Legerity chipset. Most of the remaining troubles are all linked together, and are caused by the work-arounds implemented to make this box function at all. Even without the source, I am hopeful that a solution will be discovered in the near future, and a new patch can be released that will correct the major issues.

Please don't get me wrong - I think this is an amazing piece of work, and I'm very happy to use whatever workarounds are necessary for the time being, understanding the difficulties you are working with. I'm just trying to understand what's going on - what's a limitation, what's a bug etc. e.g. for the time being it's probably easiest for me to change my network to be 192.168.1.x so that if I do lose the IP address, it'll still be there on the same subnet.

I'll come back on the other matters when I've had a bit more runtime on setting it up, if I may.

Many thanks GrauerFuchs, I hope your debugging continues with success.

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 13:20:19 EDT

GrauerFuchs : 1) Are you entering just the STUN DNS name or IP? You need to make sure the port is also correct for STUN to work.
Also, do check the DNS settings under the System tab. They may or may not be set. For some reason, not all of the established service defaults carry over from the initial configuration file in the firmware.

2) There is no longer a separate registrar address. That feature does not exist in this firmware.

3) This is a known bug in the horribly hacked firmware. You can change the IP, gateway, and DNS together. Once you click 'Save', you then need to manually change the IP in the address bar to the new IP of the PAP2. Do not remove the rest of the URL. The settings often require loading the page at the new URL for the changes to be saved and retained.

Please keep in mind that as of right now, this patch is still in the experimental and temperamental stages of development. Some of the major bugs (you've already run across a couple of them) are proving very difficult to resolve without a large outlay of cash to acquire the appropriate sources and documentation for the Legerity chipset. Most of the remaining troubles are all linked together, and are caused by the work-arounds implemented to make this box function at all. Even without the source, I am hopeful that a solution will be discovered in the near future, and a new patch can be released that will correct the major issues.

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 05:29:39 EDT

drdr6 : Hi, yes, I'm getting the message about having a SIP account etc. and do indeed have one. I'm a bit wary of launching in without debug because I have wasted dozens of hours on the PAP2 trying to get it to communicate with my SIP provider. I have recently found the reason for this to be with my ADSL2MUE which has improved significantly since fitting the Routertech firmware on Saturday. Nevertheless, although I can use a softphone from my PC, the PAP2 was unable to get registered - hence my trying this firmware hack. What drew me to this thread in particular was being able to turn stun on which does seem to be one reasonably foolproof way of solving NAT problems.

However I do still have some problems:
1) If I try to turn stun on, I enter a valid stun server (I've tested this with a stun client), but the firmware refuses to take this setting and highlights the stun entry with a red "no". What needs to be set in addition to stun "on" and a valid stun server (btw. does that need to be an IP address - do you know if the voice s/w can do DNS resolution ?)

2) Not being able to turn stun on, my alternative is a milkfish equipped DD-WRT router, but this needs the SIP client to register with the SIP provider and set the proxy to the SIP router address (there are no milkfish settings for SIP provider). The voice setup is now quite a bit different to before. In particular I don't see an entry for registrar address, only proxy. Where is the registrar address ? There are a lot of blank entries etc. is there a good guide to configuring the RTP300 you can point me to ?

3) My IP setup is currently based on 192.168.2.x; whenever I change a voice setting, the linksys goes back to 192.168.1.254, which means changing my PC's address to 192.168.1.x and then configuring it back. Weirdly so long as I don't touch the IP address, it's happy to retain the gateway and DNS entries, but if I change the PAP's IP address to 192.168.2.10, then it will clear the gateway and DNS entries. Any ideas ?

Thanks for your earlier reply..

Re: [General] The new PAP2 v2.0

Tue, 25 Mar 2008 02:24:46 EDT

GrauerFuchs : Until you enable a line and enter the information for your SIP server, you won't see a single SIP message or get a dial tone. As mentioned before, sign up for an account with a service such as sipphone.com or freeworlddialup.com, and enter the information for your user account on the Voice->(admin) Line* page.

If you are unwilling to use a SIP provider and wish only to use the peering (IP calling), you can enable this by setting the 'make calls without registration' and 'receive calls without registration' options to Yes. These options are on the same tab as you would enter server information. You also need to set the 'Enable IP Dialing' option to Yes.

Re: [General] The new PAP2 v2.0

Mon, 24 Mar 2008 20:20:10 EDT

drdr6 : Ok, picked up handset and did **** - now get lady config menu voice! I ** know ** I tried this 20 mins ago - seems like slowly the device is configuring itself.

On the log front, I have a log server set up with log level at debug but only see messages like:

03-25-2008 00:17:49 User.Debug 192.168.1.254 [0018F8B192C7] webcm: Querying module lan0 for key static:settings/netmask

- there's nothing SIP specific going on.

thanks for the tips..

Re: [General] The new PAP2 v2.0

Mon, 24 Mar 2008 20:10:32 EDT

myvoip07 :

said by drdr6 :

But after reset, both lines are "dead" - no dial tone.

Pickup the handset and dial **** and should get the lady voice saying linksys config menu. You may have to dial more then 4 *'s sometime to get it. Also u wan't get dial tone unless you configure a voip sip provider. If u don't have a sip voip then register to any free providers like FWD, freedigits and configure the PAP2v2 on 1 of the lines and u should then get a dial tone.
To setup log files got to Admin-> Log-> setup the ip where you r logserver is located.
Don't forget to click on the Advanced view link to get more option when in Admin/user login :)

Re: [General] The new PAP2 v2.0

Mon, 24 Mar 2008 19:59:26 EDT

drdr6 : So I loaded all the stuff from pap2patcherplus.tar.bz2 and after some fiddling about (the readme.txt doesn't mention that you need to have rtp300_fw_3.1.24_US.img there as well, and the update script doesn't error its not being there) I managed to get a new firmware file of the correct size.

After loading it and doing the reset, the device appears on 192.168.1.254 and I can configure it. But after reset, both lines are "dead" - no dial tone. The status page shows the phone as off hook if I pick it up, so the line is not completely dead...

Also, any idea how to debug setting a connection up ? There only seems to be a remote log page. Is there an internal log one can see over ssh ?

Screen shot voice page

Re: [General] The new PAP2 v2.0

Thu, 06 Mar 2008 01:01:50 EDT

anon :

said by GrauerFuchs :

This is a known bug.

It is working now. Thanks for the info, and all the hours you have put into this. Really appreciate it.

Re: [General] The new PAP2 v2.0

Tue, 04 Mar 2008 14:28:13 EDT

GrauerFuchs : This is a known bug. You can't trust any of the details given by the device IVR on the modded 3.1.24 firmware. The information is in error. Instead, hold the reset button again for 20 seconds, and then access it at the real default IP of 192.168.1.254.

Re: [General] The new PAP2 v2.0

Mon, 03 Mar 2008 12:05:21 EDT

anon : My pap2v2 is still stuck at the default 15.1 ip address even after pushing the reset button for 15 seconds. From the phone using **** option 150 says it is at 3.1.22 fw. Before upgrade it was on 1.00.16 fw. Also unable to disable the dhcp so that i can input the ip details manually. Noticed the lan port link is still green even if a ethernet cable is not plugged in. How can i fix this, need some assistance from the experts here :) Thanks for the wonderful people and the great supporting community..

Re: [General] The new PAP2 v2.0 - RTP300 module

Fri, 22 Feb 2008 14:05:03 EDT

mazilo :

said by toro :

Any luck with the 8100 (or is it discussed in another thread) ? I have a couple of those too. I was able to unlock them with the CYT unlocker, but I would love something a little more permanent.

If you want more hackers to do this thing, send them some of your IP8100 units to hack and before you know it, a permanent unlocking method will be here in no time. :D
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - RTP300 module

Fri, 22 Feb 2008 13:13:44 EDT

toro :

said by rcilink :

I am still working on the IP8100 at the moment

Any luck with the 8100 (or is it discussed in another thread) ? I have a couple of those too. I was able to unlock them with the CYT unlocker, but I would love something a little more permanent.

Re: [General] The new PAP2 v2.0

Fri, 22 Feb 2008 07:06:22 EDT

rcilink : modify your command a little.. it works in 1.00.13 also:

echo "setenv CONSOLE_STATE unlocked" > /proc/ticfg/env

Re: [General] The new PAP2 v2.0

Fri, 22 Feb 2008 06:52:33 EDT

vsnine : Yes, issuing: echo "CONSOLE_STATE unlocked" > /proc/tivcfg/env on the patched/modded 3.1.24 firmware worked for me. It did not however work under the 1.00.13 firmware. I had the 1.00.22 firmware at first (which did not allow much), was able to downgrade by going to »link-pap2/cgi-bin/firmwarecfg (thx slickms) and sending the 1.00.13 firmware, then using the CYT unlocker. This enabled SSH access, but i was unable to unlock the bootloader's prompt.

That's when I decided to try the patched 3.1.24 firmware, allowing me to unlock the bootloader. Of course, now that I have this firmware installed, I don't really need to access the bootloader ;)

Now I just need to get this thing to talk to Asterisk.

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 17:51:52 EDT

yahoo2003 :

said by vsnine :

I figured as much. Was able to unlock my bootloader with the modded firmware but still cannot send the ESC to get in.

Time for new parts...

I had to unlock my bootloader (changing "CONSOLE_STATE" from "locked" to "unlocked") using JTAG before I downgraded firmware, I wasn't aware bootloader can be unlocked with "the modded firmware".
So you saw "Hit [ESC} for PSLBoot...3..2..1" when you power up but you couldn't get in PSLBoot by hit [ESC]?
Then you have a hardware problem. Those MAX chips are very robust, I haven't seen a bad one. Even one of the transmitter is bad, you have another one on the same chip.

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 13:16:10 EDT

mazilo :

said by vsnine :

Was able to unlock my bootloader with the modded firmware but still cannot send the ESC to get in.

If you use telnet and ESC doesn't work, try to read this Telnet into RedBoot section (near the end about .telnetrc options).

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 12:29:00 EDT

vsnine : I figured as much. Was able to unlock my bootloader with the modded firmware but still cannot send the ESC to get in.

Time for new parts...

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 11:53:39 EDT

yahoo2003 :

said by vsnine :

Does the 3.1.24 firmware respond to the serial console? If it does then my level converter is shot.

Firmware has nothing to do with Serial console. Even you erase all IMAGEs and CONFIGs, the serial console should work as long as the bootloader is working.

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 10:03:09 EDT

vsnine : Excellent!

I should have tried Ping scanning 192.168.1.0/24 ;)
Did .15 and .0, boy I feel silly.

Does the 3.1.24 firmware respond to the serial console? If it does then my level converter is shot.

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 09:49:18 EDT

GrauerFuchs : You'll need to hold the reset button for 15 seconds or so, until it forcefully reloads everything from factory defaults. The configuration from the 1.x.x firmwares is incompatible with the 3.1.24 firmware. Once reset, it will default to the IP 192.168.1.254.

Re: [General] The new PAP2 v2.0

Thu, 21 Feb 2008 08:35:57 EDT

vsnine : I applied the modded firmware (pap2v2_fw_3.1.24_NA.img.web) to my PAP2v2, and it took the new firmware ok.

The problem i find myself with now is that it doesn't appear to start the network interface, and to make matters worse, my level converter doesn't seem to be sending my commands properly. Essentially, I'm getting read-only output from the serial console, ATM.

Is this modded firmware defaulting to 192.168.15.1? Or should it be getting an IP from DHCP? The serial console does not mention the IP of the device.

Re: [General] The new PAP2 v2.0

Wed, 20 Feb 2008 07:14:17 EDT

vsnine : I can confirm that this works. Successfully downgraded to 1.00.13, then was able to use the CYT unlocker to gain access to the box.

Was able to watch the update process via the serial terminal.

I'm going to try and load the hacked firmware later on, hopefully I can get it to work.

Thanks for all the support, everyone.

Re: [General] The new PAP2 v2.0

Mon, 11 Feb 2008 22:30:08 EDT

slickms : gotcha - so i thought - sharing issues.

thank you.

BTW nice work in putting it together. gonna try it tomorrow.

Re: [General] The new PAP2 v2.0

Mon, 11 Feb 2008 22:26:37 EDT

GrauerFuchs : The problem comes with the lack of any official NA firmware for this device. It was released presumably for only the one service provider. The only unlocked/untethered firmware is considered hacked code. While the altered code itself can be distributed here, it is against forum rules to provide full copies of hacked firmware. There are other issues involving IP law which makes it illegal to distribute complete, hacked firmware code as well. This is why you have to take extra steps to use this box with the altered firmware.

CYT does well in most cases, but it doesn't completely free your box. It only unlocks the current settings. A factory reset will return it to the service provider's control. A properly crafted SIP message may also make possible a return to the provider's control. The replaced firmware alters the default instructions, making a factory reset a safe operation. It isn't completely the same as running a factory unlocked box, but it is as close as one currently exists.

Re: [General] The new PAP2 v2.0

Mon, 11 Feb 2008 21:48:16 EDT

slickms : Well but i thought CYT unlocks the Pap2v2. All i should need to do is point to the new firmware file and upgrade it.

What am i missing?

Re: [General] The new PAP2 v2.0

Mon, 11 Feb 2008 21:44:35 EDT

mazilo :

said by slickms :

Would anyone be able to post the latest firmware here. Why does everyone need to install linux and generate one?

So that the PAP2v2 can run a custom firmware that will completely remove Vonage from it, i.e. a complete unlock (until you reflash it with a Vonage firmware).

Re: [General] The new PAP2 v2.0

Mon, 11 Feb 2008 21:17:57 EDT

slickms : Would anyone be able to post the latest firmware here. Why does everyone need to install linux and generate one? Probably I am missing something again.

Re: [General] The new PAP2 v2.0

Sun, 10 Feb 2008 21:06:01 EDT

mazilo :

said by slickms :

2 steps
1. - Download fw from »httpconfig.vonage.net/pt-11.4.0-···0426.img
2. - Navigate to »IP_ADDRESS/cgi-bin/firmwarecfg

Chose the fw downloaded in step 1 and upgrade.

Done. It will be downgraded to v 1.00.13.

Use CYT to unlock it.

Well done and thank you for sharing.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Sun, 10 Feb 2008 18:06:37 EDT

GrauerFuchs : Perfect. Thank you for the update on that. It's great to hear that the unlucky ones now have a chance to get away from a bad (for users) firmware.

Re: [General] The new PAP2 v2.0

Sun, 10 Feb 2008 16:25:01 EDT

slickms : it asks to login but admin/admin the usual one works. You don't need the admin/tivonpw or Admin/xxxxxxx passwords.

Re: [General] The new PAP2 v2.0

Sun, 10 Feb 2008 15:44:33 EDT

GrauerFuchs : Does it not ask you to log in when using this method? If so, that could be a problem for those unable to retrieve a user password. Other than that, it's an excellent way to get in and flash a locked box.

Re: [General] The new PAP2 v2.0

Sun, 10 Feb 2008 15:41:25 EDT

slickms : Here is the simplest way.

THIS WORKS on PAP2 V2 1.00.22. THANK YOU.

2 steps
1. - Download fw from »httpconfig.vonage.net/pt-11.4.0-···0426.img
2. - Navigate to »IP_ADDRESS/cgi-bin/firmwarecfg

Chose the fw downloaded in step 1 and upgrade.

Done. It will be downgraded to v 1.00.13.

Use CYT to unlock it.

No need of level convertor/JTAG or anything else.

Boom.

Re: [General] The new PAP2 v2.0

Wed, 06 Feb 2008 07:11:16 EDT

GrauerFuchs :

said by meister_sd :

said by TJ_in_IL :

Is there a more "user friendly" version of this hack

Basically, the reason an easier way isn't posted is that DSLReports forbids "hacked" firmware from being posted.

That said, maybe someone will post a link to rapidshare, or whatever, for a web upgradeable version.

Precisely. Between that and the current state of IP law, I can't provide a pre-built firmware.
If the original service provider goes out of business, however, that's a completely different matter. ;)

Re: [General] The new PAP2 v2.0

Wed, 06 Feb 2008 02:17:17 EDT

meister_sd :

said by TJ_in_IL :

Is there a more "user friendly" version of this hack

Re: [General] The new PAP2 v2.0

Tue, 05 Feb 2008 23:33:43 EDT

TJ_in_IL : Is there a more "user friendly" version of this hack (for lack of better term), that can be simply uploaded, similar to a firmware upgrade?
Or, am I missing something in the reading, and making it more difficult than it really is?
I really appreciate what you have been doing, and encourage more. I wish I had the knowledge. What you have done has helped to spark interest in this product again.
Thanks in advance.

TJ

Re: [General] The new PAP2 v2.0

Tue, 05 Feb 2008 16:09:45 EDT

odin1221 : @Ilhy:

Are you logging in first with the admin/admin combination?

Here is what I need to do:

Navigate to the adapter.
Login as admin/admin.
Manually navigate to the Provision.html page.
Login as Admin/Admin.

HTH

Re: [General] The new PAP2 v2.0

Mon, 04 Feb 2008 12:20:40 EDT

GrauerFuchs : It could be a number of reasons. Unfortunately, it's difficult to narrow down with such little information. Let's start from the beginning and most common issues, just to rule out all possibilities along the way. When you were trying to log in again after a few minutes, were you trying to log in as 'Admin' or as 'admin'?
Quick note to be sure:
* If it simply asks for username and password, use 'admin'.
* If it asks for the username/password from your service provider, use 'Admin'.

Re: [General] The new PAP2 v2.0

Sun, 03 Feb 2008 17:05:03 EDT

ilhy : I unlocked my PAP2 V2.0 using CYT last August. The firmware is 1.00.13. I tried to configurate it to use one provider. But I could not log in with the unlocked Admin/Admin password. I reset it and using CYT unlocked it again and logged in with Admin/Admin password and set it up with the provider. But one or two minutes later same thing happened. I couldn't log in again(never connect it to internet). It couldn't remember the admin password. But the voip setup still there. What's wrong with my adapter?

TIA

Ilhy

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Sat, 02 Feb 2008 14:23:45 EDT

elvisk : Thanks for the info.

I got it working with public stun and DDNS to my system. It's working well so far. Will keep you informed of stability.

Seems like the IP issues is the last major issue. If you can identify that it will be a very good box.

Thanks for your hard work and let me know if I can help testing the IP address problem.

Elvisk

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Sat, 02 Feb 2008 13:40:58 EDT

GrauerFuchs : This is probably the giant bug I mentioned when you first asked about the firmware. For unknown reasons, the voice module is unable to recognize the assigned IP address. This may be due to minor incompatibilities with the hardware. If you examine the Trixbox SIP logs, you will see the PAP2v2 identifying itself as '192.168.15.1' and not as the correct IP address. The IVR identifies as the same. As of yet, the reason or source of this bug remains unknown. This is why I suggested use of the beta 0.5 and not the 3.1.24 firmware. Beta 0.5 may not have as many features, but it is fully functional across local networks.

The only known workaround currently is to pass the SIP and RTP traffic from the PAP2v2 through a NAT firewall to an external server.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Sat, 02 Feb 2008 12:41:05 EDT

elvisk : rcilink or others,

I'm having a hard time registering to my trixbox. is there a special setting that is required? My info..

Network: 192.168.34.x

Trixbox (1.1.1) settings...

username=1998
type=friend
secret=xxxx
record_out=Adhoc
record_in=Adhoc
qualify=no
port=5060
nat=never
mailbox=1998@device
host=dynamic
dtmfmode=rfc2833
context=from-internal
canreinvite=no
callerid=1998

Pap2v2 with 3.1.24 settings

All default except...

Proxy - pointed to my trixbox
Display Name - 1998
User ID - 1998
Password - xxxx

These settings work for the pap2v1 so I'm not sure where the problem lies. Any help is appreciated.

Thanks.

Elivsk

Re: [General] The new PAP2 v2.0

Fri, 01 Feb 2008 00:16:17 EDT

GrauerFuchs : No problem. It's a giant change from the old provisioning method. Good luck!

Re: [General] The new PAP2 v2.0

Fri, 01 Feb 2008 00:14:38 EDT

elvisk : GrauerFuchs,

My bad. I've been using the xml files for so long that I forgot about the advanced view.

I will test tomorrow.

Thanks for your work.

Elvisk

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 22:59:38 EDT

GrauerFuchs : In the smaller tab bar, select 'advanced view'. STUN settings will be on the SIP tab, and your registration server and dial plans will be on the Line 1 / Line 2 tabs.

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 22:43:24 EDT

elvisk : I figure a picture is worth a 1000 words...

If the interface is suppose to be exactly the same as RTP300 firmware 3.1.24, I believe this modded version is missing many fields.

I would really appreciate you checking the code.

Thanks.

missing registration/dial plan fields

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 22:37:30 EDT

GrauerFuchs : Which version did you load? If you are using the beta 0.5, it does not support STUN. As soon as I know which version you're testing, I'll re-check the code for that version to ensure the fields are present.

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 22:33:59 EDT

elvisk : GrauerFuchs,

I just loaded the modded firmware and for some reason it seems to be missing several things...
- missing registration server field
- missing stun server field
- missing dial plan map

Can you confirm that these fields should be there?

I used your simplified patching method (I believe it was your last post with the patch).

Thanks.

Elvisk

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 19:37:00 EDT

GrauerFuchs : I've left the modified PAP2v2 with 3.1.24 software running for nearly a week now with no problems. Registration and service is maintained with 2 providers without incident.

A far as Asterisk is concerned, it will register, but I've seen and heard reports of problems if your Asterisk server is on the local network. If you're looking for something to reliably act as an Asterisk extension, I would recommend you stick with the beta 0.5 using PAP2 v1.00.16 firmware for now. If you want something to test, please feel free to try the 3.1.24 and let me know your results.

Re: [General] The new PAP2 v2.0

Thu, 31 Jan 2008 17:33:25 EDT

elvisk : Hello All,

I haven't had a chance to test drive the modified firmware. May I ask how it's been doing since several of you most likely had time to test. Also how well is it working with Asterisk? Any issues?

Thanks.

Re: PAP2 ver.2 fw 3.1.24! - Recommended dial plan addition

Sat, 26 Jan 2008 01:07:48 EDT

GrauerFuchs : A nice little addition I've been toying with, specifically for handling the issue with peering on ATA devices:

This string will tell the PAP2 (or other Sipura-based ATA) to use the SipBroker free peering service upon request for a SIP-SIP call. To use the feature, dial the SipBroker peering code followed by a *. Dial the user's number, and then hit # (much as you would SEND on a cellular) and it will transfer the call away from the default proxy and onto the SipBroker peering gateway.
Example: To call someone using FWD, you would dial *393*??????# where *393 is the SipBroker peer link to FWD and ?????? is the user's FWD number.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 20:16:00 EDT

yahoo2003 : Yes I have confirmed that the "dropbear" module was missing from RTP300-NA firmware, and the "ssh" was commented out in "user.html".

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 19:49:54 EDT

GrauerFuchs : No. If you apply the patched firmware to the RTP300, you'll end up with an unusable router. Instead, here's what you need to do:

1) Get a binary copy of the dropbear server for mipsel (you can use the one from the PAP2v2 1.00.16 firmware, that's the one included in my patch) and place it in /usr/sbin
2) Edit the /usr/www_safe/html/admin/user.html file and uncomment the ssh fields from 4 sections:
* Javascript function uiDoOnLoad()
* Javascript function uiDoSave()
* HTML section 'SSH Access'
* FORM section 'Post Form'
3) Recompress the filesystem and build your firmware.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 19:36:31 EDT

yahoo2003 :

said by GrauerFuchs :

Thank you for the update on that. I'm glad to hear it's working. The RTP300 root file system for the 3.1.24 firmware did not have an SSH server. The code to enable/disable from the web interface was also commented out.

So it's time to hack RTP300. :D
Will your binary patch work for RTP300?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 19:31:11 EDT

GrauerFuchs :

said by yahoo2003 :

I tested ssh on my PAP2V2 with new firmwre using "putty" and it worked.
However "putty" does not work with my RTP300 with the same version of RTP300-NA firmware. :( .
Putty crashed evertime with "server unexpectedly closed network connection".
Does anyone have same problem when using ssh on their RTP300?

Thank you for the update on that. I'm glad to hear it's working. The RTP300 root file system for the 3.1.24 firmware did not have an SSH server. The code to enable/disable from the web interface was also commented out.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 19:23:44 EDT

yahoo2003 :

said by GrauerFuchs :

Overall, the 'patch' is simply a hack of the existing firmware. The only real addition was the insertion of the dropbear ssh server, which remains untested as of the release of this patch.

I tested ssh on my PAP2V2 with new firmwre using "putty" and it worked.
However "putty" does not work with my RTP300 with the same version of RTP300-NA firmware. :( .
Putty crashed evertime with "server unexpectedly closed network connection".
Does anyone have same problem when using ssh on their RTP300?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 17:21:30 EDT

GrauerFuchs :

said by meister_sd :

All this new RTP voice module stuff is still based on the .16 firmware, correct?

No. The 3.1.24 patch is based entirely on RTP300 firmware 3.1.24, and does not require the PAP2v2 firmware file.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 17:19:20 EDT

meister_sd : All this new RTP voice module stuff is still based on the .16 firmware, correct?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 15:36:17 EDT

GrauerFuchs :

said by paplearner :

1. Although, the setup,status and administration pages shows Firmware Version: 3.1.24. Voice pages shows Firmware Version: 3.1.22 at the top of the page.

This is due to the firmware source. The voice firmware is version 3.1.22 (same as in the RTP300 and WRTP54G 3.1.24 releases)

2. I assigned a static IP of 10.1.2.10 and registered 'line1' to an asterisk box. asterisk peer info displays:
Reg. Contact : sip:1001@192.168.15.1:5060. Everything worked but there seems to be a hard coded 192.168.15.1 IP address somewhere.

This is a glitch I'm currently trying to track down. The voice module doesn't seem to be able to keep in sync with the OS. 192.168.15.1 was the IP address of the default LAN on the source firmware. When connecting to an external IP through a home router (as many of us do), it works fine. Internally, it gets twitchy.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 15:31:15 EDT

anon : Thanks! Great work. Worked like a charm. Couple comments:

1. Although, the setup,status and administration pages shows Firmware Version: 3.1.24. Voice pages shows Firmware Version: 3.1.22 at the top of the page.

2. I assigned a static IP of 10.1.2.10 and registered 'line1' to an asterisk box. asterisk peer info displays:
Reg. Contact : sip:1001@192.168.15.1:5060. Everything worked but there seems to be a hard coded 192.168.15.1 IP address somewhere.

Re: [General] The new PAP2 v2.0

Fri, 25 Jan 2008 15:25:55 EDT

meister_sd :

said by amanitajoy :

No high-speed Internet is available at my location in rural Mexico, south of San Diego.

I'm in San Diego, not far from you.

One thing I would check is your codec. I think you can log into your vonage account and change them. Play around a bit and make your outgoing tests. Also, see about getting an unlocked unit and another provider.

I would start a new thread on this as this isn't part of this subject. More people not monitoring this thread might see your's and offer help.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 15:21:45 EDT

mazilo :

said by toro :

I agree, but that is if you have access to the Admin password, or you have a version that can be unlocked with the CYT unlocker first. However, I was responding to slickms's question, who has a PAP2v2 locked to Vonage and using the firmware 1.0.22.

I agreed with what you said above; however, your remarks sounded like a serial-console cable is required to perform a firmware upgrade which is kind of a misleading information. The fact is you don't even need a serial-console cable to perform a firmware upgrade without knowing the Admin password (you just need to know how to do this). No one is willing to discuss this doesn't mean there is no such hack.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 15:09:43 EDT

toro : I agree, but that is if you have access to the Admin password, or you have a version that can be unlocked with the CYT unlocker first. However, I was responding to slickms's question, who has a PAP2v2 locked to Vonage and using the firmware 1.0.22.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 15:06:28 EDT

mazilo :

said by toro :

said by mazilo :

Are you sure about this? I thought a serial-console cable is ONLY needed if you want to flash your PAP2v2 with the web version modded firmware.

I may be wrong, but I thought the only way you could control the boot loader is through the serial console. Not only for PAP2v2, but for many other devices too (for example the VTA-VR).

Yes and you are right; however, a serial-console is not required to flash the modded firmware through a webGUI.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 14:56:53 EDT

toro :

said by mazilo :

Are you sure about this? I thought a serial-console cable is ONLY needed if you want to flash your PAP2v2 with the web version modded firmware.

I may be wrong, but I thought the only way you could control the boot loader is through the serial console. Not only for PAP2v2, but for many other devices too (for example the VTA-VR).

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 14:55:10 EDT

GrauerFuchs :

said by mazilo :

Are you sure about this? I thought a serial-console cable is ONLY needed if you want to flash your PAP2v2 with the web version modded firmware. Also, it is always good to have a serial-console cable handy so that one can access the device in its lowest level format; however, this is CERTAINLY NOT REQUIRED, except recommended for a good practice.

If you're dealing with a locked device on 1.0.22, I don't know of any other way to get access to it. CYT doesn't work, and without the encryption key, you can't feed it a tainted XML. Data in the binaries is hard-locked to The V, so you can't even expect anything you do manage to get through to stick around. From what little I've done on 1.0.22, your options are either serial console wipe, or JTAG. Either is just as risky, but serial console is easier and much faster. If you do know another way to get around 1.0.22, please say so.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 14:49:08 EDT

mazilo :

said by toro :

- a RS232 level-converting serial adapter, to connect between the computer's serial port and the 5 pin header inside the PAP2v2. This is required, in order to stop the booting process and send commands to the bootloader

Are you sure about this? I thought a serial-console cable is ONLY needed if you want to flash your PAP2v2 with the web version modded firmware. Also, it is always good to have a serial-console cable handy so that one can access the device in its lowest level format; however, this is CERTAINLY NOT REQUIRED, except recommended for a good practice.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 14:45:47 EDT

GrauerFuchs :

said by yahoo2003 :

Do you know which module controls the voice chip?

All of the kernel modules are requirements for the voice module to function, and each one of the modules links to the others. As far as binary applications involved, ggsip does all of the voice and voice/web processing, and the cm_logic handles the interface between it and the rest of the operating system.

Re: [General] The new PAP2 v2.0

Fri, 25 Jan 2008 14:37:37 EDT

mazilo :

said by amanitajoy :

My objective has been Voip via satellite.

You are better off signing up for a free new account and post this as a new post (starting with a new thread) instead of posting on an existing thread with different subject. Interjecting your post in an ongoing discussion on a different subject will get you nowhere, let alone helps. If you don't know how to post, please read the FAQ on how to post.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 14:16:34 EDT

yahoo2003 : Thanks for the insights. I'll try the magics on my VT2442. Do you know which module controls the voice chip?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 13:09:42 EDT

yahoo2003 : This link gives a lot of hardware/software information about CYT devices.
»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G
PAP2-V2 is similar to WRTP54G and RTP300, but it is not a router.
You can connect PAP2 to a PC directly or though a router.
If you connect PAP2 to a Windows PC, you need a DHCP server such as "tftp32d", or you have to set PAP2-V2 to a static IP through your phone.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 13:05:14 EDT

GrauerFuchs : The above post beat me to it. :)

The level converting adapter is usually a piece of home-built technology. If you're not good with a soldering iron and building devices from components, you may wish to ask for assistance in its construction. The one I use is a variation of the one listed everywhere for adding a serial console to the WRT-54G.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 13:01:16 EDT

toro :

quote:
I feel as if I am technically very weak now.

As GrauerFuchs suggested here probably your only choice for firmware 1.0.22 is to flash the adapter from the boot loader with a more friendly firmware. Either the pt-11.4.0-r060628-1.00.16-r060628.img (which can be unlocked then using the CYT unlocker) or the custom firmware that he built.
You will need a little bit of expertise and some tools to do this:
- a RS232 level-converting serial adapter, to connect between the computer's serial port and the 5 pin header inside the PAP2v2. This is required, in order to stop the booting process and send commands to the bootloader
- a network switch (or router NOT connected to the internet)
- a TFTP software loaded on the computer (for example SolarWinds)
Then, you need to configure the computer with an IP address in the 192.168.1.x range, for example 192.168.1.10, put the firmware on your TFTP server, boot the PAP2 and stop it during the boot loader initialization, then issue the commands listed by GrauerFuchs, where you have to replace {tftp server IP} and {firmware_file} with the appropriate values.
If all these steps seem too complicated, maybe you should ask someone local more technical to unlock your adapter.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 12:56:44 EDT

GrauerFuchs :

said by yahoo2003 :

Now even Caveman can do it ;).

Hey! I take offense to that. A caveman wrote this patch, thank you. :D

(1). You have appended many "htm" and other files to "usr" and "etc" directories. Is this because PAP2 and RTP have different web interfaces? Do you have to create some those files?
(2). You deleted some directories ("advanced" and "secuirities") and modules. Is this because RTP is a router and PAP is DHCP client?

The HTML files contained extra tabs for features the PAP2 does not have and cannot use. In addition, the PAP2 populates its hardware in a different manner, so the files had to be altered to reflect the new hardware and labeling. The deleted web directories contained materials the PAP2 cannot use. I opted to have them removed for reasons of space alone. The same goes for the deleted binaries.
Files changed in the /etc directory included the system configuration file and the versions file. The versions file was altered to indicate the new build, and the new hardware. The system configuration file removed any possibility of being locked back to the provider, and also to reflect the new device's hardware.

(3). You binary patched "ggsip" module. How does the patch work? Do you have to write and compile some code to generate the patch?

This patch was put in place only to visually reflect the new hardware device. It should not alter performance or operation in any way other than to remove unused web tabs and indicate that the running device is a PAP2v2 and not an RTP300.

Overall, the 'patch' is simply a hack of the existing firmware. The only real addition was the insertion of the dropbear ssh server, which remains untested as of the release of this patch.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 12:26:33 EDT

slickms : I feel as if I am technically very weak now.

Can someone tell me if the Pap2v2 needs to be connected via the normal Ethernet cable or something else for this to work?

If its the Ethernet cable then what should be the IP of the computer. If not, then please show me a picture/link of the wire/adapter that is needed to connect.

Thanks.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 11:09:19 EDT

yahoo2003 :

said by GrauerFuchs :

Let's make it one step easier. This version of the patcher has the static binaries integrated already. No need to edit the files inside unless you really want to do so.

It's indeed getting easier for each new release. Now even Caveman can do it ;).
I did go through each releases and learned a lot of Linux.
I was able to generate the "web" and "flash" versions, load and test them using tftp and web interface.
I'm trying to understand the magic, here is what I observations and questions:
(1). You have appended many "htm" and other files to "usr" and "etc" directories. Is this because PAP2 and RTP have different web interfaces? Do you have to create some those files?
(2). You deleted some directories ("advanced" and "secuirities") and modules. Is this because RTP is a router and PAP is DHCP client?
(3). You binary patched "ggsip" module. How does the patch work? Do you have to write and compile some code to generate the patch?

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 08:55:22 EDT

toro : Great work !

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 01:09:11 EDT

GrauerFuchs :

said by rcilink :

Now someone needs to test the STUN server support.

Success here, to 2 different STUN servers. Tested SipPhone and FWD STUN with complete success.
Note: Enable STUN server and STUN testing from SIP page, and enable NAT mapping on each line page for it to have any effect.

Amanitajoy: I'd wager a guess that the transmit latency of the satellite is part of the problem. First, send a long series of pings and packets to test servers to make sure you're not dealing with excessive errors or packet retries. If your connection is good, you'll need to get Vonage to alter the settings on your PAP2. There are ways, but if it's locked to them, you won't be able to make permanent changes.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Fri, 25 Jan 2008 00:27:01 EDT

rcilink : Great news-- this Sipura Voice patch fixes the SIP registration limitation of the account name being numeric (0-9 and a,b,c,d,e).

I was able to register a SIP extension with username test to my test asterisk box using this 3.1.24 firmware.

Now someone needs to test the STUN server support.

Re: [General] The new PAP2 v2.0

Fri, 25 Jan 2008 00:26:03 EDT

anon : Good morning gentlemen. My objective has been Voip via satellite. No high-speed Internet is available at my location in rural Mexico, south of San Diego.

I am using the Wild Blue satellite premium package at $80 per month successfully, which provides 2 MB per second down & 156 kilobytes per second up.

Prior to acquiring While Blue, I had spent time reading Vonage & Hughes chat room commentaries. As of a year ago, Hughes could no longer successfully transmit Voip. At another chat room, Hotel owner Tom Messner in Canada reported complete success: "Vonage works w/ Xplornet"., Tom suggested I try While Blue. I am using my old PAP2.

Calls initiated to me, from the U.S., on my Vonage line, work well- (except for the annoying latency-but that is tolerable). Calls which I initiate are garbled and useless. Surprisingly, I can also place and receive calls to/from Mexico with reasonably good quality-calls which are usable.

Shall I now give up, or is there someone out there who knows of further strategy. I thought it significant that I can successfully initiate a usable satellite call via Vonage / PAP2 through my Texas area code, back to a phone near me here in Mexico. That transmission works OK. (Perhaps that is a piece of information of interest to someone.) Without "dial-out" capability to the U.S., I'm afraid my efforts have all been a waste.

Hopefully a knowledgeable expert will read this and provide a definitive comment on the current status, and perhaps a fix.

Thank you.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Thu, 24 Jan 2008 18:11:53 EDT

GrauerFuchs : Let's make it one step easier. This version of the patcher has the static binaries integrated already. No need to edit the files inside unless you really want to do so.

Edit:

A few notes on this patch:
Because the data produced by the compression utility can differ, you will not be able to verify good firmware by use of a CRC or MD5 sum. Instead, we have to resort to a simpler, less reliable check. The valid file lengths are as follows:

3752085 Jan 24 15:38 pap2v2_fw_3.1.24_NA.img.flash
3752093 Jan 24 15:38 pap2v2_fw_3.1.24_NA.img.web

I will look into modifying the patch to run on 3.1.27-ETSI firmware as well, since the US firmware does not have all the settings, defaults, and features needed for everyone.

pap2patcherp···.tar.bz2 811,556 bytes

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Thu, 24 Jan 2008 17:51:05 EDT

rcilink : Thanks for the great work and dedication.

Some notes of the run-through I experienced:

(the following notes are based on a Linux experience) For those windows users, I would image Knoppix with a USB flash drive would do the trick, but have not tested it that way myself.

1. Unpack the pap2v2-3.1.24patcher.zip into a new directory, slong with the pap2v2utils and the actual rtp300-3.1.24 image (not the ZIP or RTP300 directory, but the actual file)

2. If you don't have the current directory ( ./ ) in your path, you need to modify the patch-apply.sh to include the path to the appropriate util or directory. I also had to add the path to source/splitfw.sh

3. The two 'patched' firmwares are produced. one ends with 'flash' and the other 'web'. I had to manually run tichksum on the '.web' firmware.

Once I get home I will reset the pap2v2 and attempt to load the patched firmware into the unit.

Thanks again for the great work!

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Thu, 24 Jan 2008 16:08:43 EDT

GrauerFuchs : Specifically because the squashfs-tools patched is a pain in the rear to fix and compile, those and the other less common tools are now included in a separate package above. They are static binaries in ELF format for Linux/i386.

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Thu, 24 Jan 2008 09:51:28 EDT

mazilo :

said by GrauerFuchs :

squashfs-tools lzma patched (»wiki.openwrt.org/OpenWrtDocs/Har···.tar.bz2)
bspatch binary patch utility (»www.daemonology.net/bsdiff/bsdiff-4.3.tar.gz)

You may want to include these two in your program distribution.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - Firmware 3.1.24!

Thu, 24 Jan 2008 08:57:47 EDT

GrauerFuchs : Okay, the next stage in patch evolution is complete. This is a complete re-do, starting on firmware 3.1.24 for the RTP300. Since it is a complete hack-job patch, there may be unknown bugs lurking around the corner. This patch is considered beta code, and may render your adapter unbootable. Use at your own risk.

Here's what you'll need to apply this patch:

A Linux, BSD, or similarly based OS
This patcher utility
GNU dd utility
GNU tar utility
squashfs-tools lzma patched (»wiki.openwrt.org/OpenWrtDocs/Har···.tar.bz2)
bspatch binary patch utility (»www.daemonology.net/bsdiff/bsdiff-4.3.tar.gz)
a copy of the rtp300_fw_3.1.24_US.img firmware file for Linksys RTP-300

Some people have had trouble acquiring and compiling the tools needed to patch the firmware. In hopes of making this easier, the second attachment contains static versions of the patched squashfs-tools, bspatch, and tichksum for the i386 platform.
With these tools in your binary path, unzip this patcher alongside the RTP-300 firmware and run the patch-apply.sh script. If all goes well, you'll have 2 firmware files produced and ready to load onto the PAP2v2.

Defaults to know:
Router/adapter login: admin/admin
Super-user password not set.
* Note: If you set the Admin password in the voice module, the login name for the voice side is 'admin' with small 'a'. Firmware updates and shell access use 'Admin' with big 'A'.
Default IP: 192.168.1.254
* Note: See the bug list below for a reason on this.

Known bugs:
Cannot configure adapter by telephone IVR.
IVR reads wrong IP and MAC address. Use the MAC address on the Status page if you need it.
MAC address digit group 6 is one number lower than the address written on the label.
Switching from static IP to DHCP and back sometimes requires a re-connect to the web UI to validate and save.

pap2v2-3.1.2···cher.zip 111,181 bytes

pap2v2-utils···tbz2.zip 677,406 bytes
Binary utilities for Linux

Re: [General] The new PAP2 v2.0

Wed, 23 Jan 2008 19:58:10 EDT

GrauerFuchs : Sorry for the delays. I was hoping someone with more experience with that particular rev firmware would pop in to offer advice. My only familiarity with 1.00.22 is that it's a nightmare of a firmware, and has Vonage's data hard-coded into some of the binary applications.

My suggestion is to open the case, use a level-converting serial adapter on the 5-pin header present, and issue the bootloader commands to replace this unruly firmware with something more manageable. Here's the header pinout:

1* - 3.3v
2 - TxD
3 - RxD
4 - NC
5 - GND
*: Pin 1 is labeled.

You'll need a level converter that is self-powered or capable of running on 3.3v. A standard MAX232 chip will not run with this low source voltage. It will, however, accept the serial signals from the box if you power it separately.

Computer requirements: A Linux machine with all the necessary software to build the PAP2v2-NA beta 5 firmware listed in this thread, and a tftp server for loading the firmware onto the box.

Instructions:

Build the patched firmware and place the flash version in the root directory of your tftp server.
Open the PAP2v2 and connect your serial level converter to the header.
Prepare your terminal software, and set to 115200,8,N,1.

When you power on the PAP2, you should see the following message:

Hit [esc] and it will drop you into a (psbl) prompt.

Warning: The below commands should not be issued unless you are willing to risk the loss of your device! Once it has been formatted, it will not boot until you load a good firmware.

From here, issue the following commands:

From here, it will boot into the new firmware and initialize itself. Your previous settings will be lost, but the box will be unlocked.
Passwords to know:

admin/admin (router/basic level access)
Admin/Admin (Voice module access)

Re: [General] The new PAP2 v2.0 - The Sweet Sight of Success

Wed, 23 Jan 2008 18:51:36 EDT

slickms : Hi,

It looks like no one cares about novice people like me. Can someone spare a few mins and list the steps we can use to unlock?

Thanks a lot.

Re: [General] The new PAP2 v2.0 - The Sweet Sight of Success

Wed, 23 Jan 2008 10:39:32 EDT

elvisk : Great job! I've been using the Pap2v2 even with it's problems. This will greatly facilitate things. Going to get the RTP firmware now.

Elvisk

Re: [General] The new PAP2 v2.0 - The Sweet Sight of Success

Wed, 23 Jan 2008 09:29:00 EDT

ogdensburg : Good job!!!

Re: [General] The new PAP2 v2.0 - The Sweet Sight of Success

Wed, 23 Jan 2008 05:45:17 EDT

GrauerFuchs : After an extraordinary amount of tweaking for performance, ability, and stripping down the load, I have managed to get the RTP300 voice module running on the PAP2v2. I've managed to trace back and eliminate the RTP errors, which were caused by a combination of firmware twitchiness and firewall glitching. There's still a fair bit of work to go before I can release the new patch, but you may want to pick up your copy of the RTP300 3.1.24 firmware now!

Yes. Before you ask, the voice pages on this version are completely rendered by the SIP engine, just like they are on the RTP300.

Re: [General] The new PAP2 v2.0

Tue, 22 Jan 2008 20:45:49 EDT

anon : Can someone give me steps on how to provision this xml file on Pap2 v2 1.00.22 firmware?

What should be the computer's IP address?

Re: [General] The new PAP2 v2.0

Tue, 22 Jan 2008 17:56:08 EDT

GrauerFuchs : Possible. I've been attempting similar with trying to get the RTP300 voice module running on the PAP2. Almost all the same hardware, but there are tweaks and specific requirements that the other kernel can't handle. If it uses different chips, you may or may not be able to swap out the proprietary modules. The ggsip program relies on specific versions of the kernel modules and kernel options, so it may not be viable with such a major change. The only way to know for sure is to try.

Re: [General] The new PAP2 v2.0

Tue, 22 Jan 2008 17:48:24 EDT

yahoo2003 : I know they used different voice chips, if the drivers for the voice chips are separated from the ggip module, may be it's possible to keep the driver for voice chip while replace other modules?

Re: [General] The new PAP2 v2.0

Tue, 22 Jan 2008 17:33:17 EDT

GrauerFuchs : It's possible, if they use the same interface. Feel free to experiment around. Unfortunately, I don't have access to all of the boxes, or even the time to test them all even if I did have them. Maybe others have more information on some of these CYT devices.

Re: [General] The new PAP2 v2.0

Tue, 22 Jan 2008 17:28:21 EDT

yahoo2003 : Is there any changce your work can be applied to other Vonage CYT devices such as VT2442? Some of the CYT devices made for Vonage do not have voice web page at all.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 21:11:30 EDT

GrauerFuchs : The provisioning file will work on patched and unpatched firmwares, so long as you have the RC4 encoding app and the proper encryption key.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 20:57:32 EDT

ricekin : Grauerfuchs: Just for clarification: The main application of this provisioning file is for firmwares that have NOT been patched, correct? Or for those settings that cannot be accessed through the web configurator (which you are expanding, I assume).

At any rate: Excellent work, once again.

Re: [General] The new PAP2 v2.0 - beta0.5 bugs

Mon, 21 Jan 2008 19:39:10 EDT

GrauerFuchs : Okay, a few bugs noted that definitely need to be addressed:

Critical:
None found (yet).

Severe:
Admin (superuser) and user (Voice) password changes will not survive a reboot.

Major:
Provision encryption key will not remain set.
Returning to Setup tab from Voice tab results in settings not loading in Setup tab.

Minor:
Units on SIP timers inaccurate. Should be msec, not sec.
Random visual glitches in non-redesigned web pages.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 17:33:04 EDT

GrauerFuchs : I see what you mean. It's not a compiler problem or a bug, but more an awkward use of syntax. Breaking it up would definitely be of value overall.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 17:22:10 EDT

yahoo2003 :

said by GrauerFuchs :

You shouldn't be required to edit the code at all. These files are already pre-patched and tested on the squashfs-lzma filesystems. Just in case there was a bug, exactly what changes did you make?

One more thing to check: The URL for the package I provided came with some pre-built executables present. Those worked for me on multiple systems. Did you try with those?

I'm not sure if this is a "bug" or compiler problem, line 433
inodep = (squashfs_reg_inode_header *) inode = get_inode(sizeof(*reg) +
offset * sizeof(unsigned short));
must be broken up into two lines:
inode = get_inode(sizeof(*reg) + offset * sizeof(unsigned short));
inodep = (squashfs_reg_inode_header *) inode;

in order for my ubuntu gcc to compile. I noticed that the newest version of mkquashfs-tools has the lines broken up.
I don't know why the lines have to be broken up, it seems to me they are equivalent.
I'll try to find the executables.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 17:17:36 EDT

GrauerFuchs : Here's another little toy for those with a desire to play with their PAP2v2s. This provisioning xml has been sanitized of all the carrier's information, and should be suitable for use on most services after appropriate modifications are completed.

pap2v2-prov-base.zip 2,353 bytes

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 12:26:13 EDT

mazilo :

said by ricekin :

@mazilo: Sure. I have come to the conclusion that it must be the FAT file system, in which most USB sticks are formatted. The lzma-squashfs on the AR7 platform needs UID/GID of 5000/5001 as correct owners in order to correctly mount/parse the filesystem. The FAT filesystem does not retain these, thus the FS can't be loaded. That said, it was a stupid error that took me about a day to figure out.

LOL ..., every-now-and-then, this also happens to me, too! :D
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - RTP300 module

Mon, 21 Jan 2008 01:36:23 EDT

GrauerFuchs :

said by rcilink :

One thought: is the firmware using iptables? if so, perhaps the RTP port range is not opened? I know when I was experimenting with the RTP300 firmware loaded on the pap2 v2, i had to put holes into the iptables firewall to let the web interface work, etc. (I did not do as nice as you have done-- so the furthest I got was to get the web working, but no activity).

In the test build, iptables was removed from the filesystem altogether. The web interface was functional with no work at all. SIP packets also passed in and out without a problem. The only thing that failed was RTP. Even pings succeeded in and out of the box.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 01:31:29 EDT

ricekin :

said by rcilink :

Sort of off-topic,

Sorry, yes, I didn't even realize. Maybe this can nonetheless help people.

said by rcilink :

- the 11.4.1 firmware has intentional breakage in the webcm (web config manager), making it impossible to use the web interface to set the SIP username and password.

Thanks. That explains a lot. I will make my own combination of firmware now, with the older version.

said by rcilink :

For example, I have had no trouble making firmware packages that can load via the IP8100 web interface (tested on 11.1.0, 11.4.0, and 11.4.1). I made no effort to make a signature. I used the tichksum to add the last 8 bytes to the firmware as usual and it worked.

I was surprised too, especially because I think I remember I downgraded over the web interface at some point. I think it might have been a Firefox issue. I will investigate.

Re: [General] The new PAP2 v2.0 - RTP300 module

Mon, 21 Jan 2008 01:29:30 EDT

rcilink : I am still working on the IP8100 at the moment and have not loaded your works yet-- but sure like what I am reading!

One thought: is the firmware using iptables? if so, perhaps the RTP port range is not opened? I know when I was experimenting with the RTP300 firmware loaded on the pap2 v2, i had to put holes into the iptables firewall to let the web interface work, etc. (I did not do as nice as you have done-- so the furthest I got was to get the web working, but no activity).

I hope that helps. You should be able to issue iptables commands to poke a hole for RTP packets from the shell prompt on the device to test this theory.

Re: [General] The new PAP2 v2.0 - RTP300 module

Mon, 21 Jan 2008 01:17:47 EDT

GrauerFuchs : Well, the module half works. It comes up and is capable of making calls, but I can't seem to resolve the 100% loss of RTP packets coming in. This appears to be due to the differences in hardware, but I can't be entirely sure. Without access to the source code of the proprietary software or even the source to a kernel including the Legerity patchset, I'm at a loss. Here are a few notes if others want to give it a try:

*Ethernet on PAP2 registers as eth1.
*Voice services attempt to run from eth0.
> Limited switching of voice services can be done to start up on eth1, but it seems very buggy in whether or not it accepts the alteration.
* The RTP300 kernel is compiled with different parameters which are required for the newer voice driver to operate.
* Voice module will not accept on-the-fly changes to configuration. It does not properly recognize the current IP address on the IVR.
* IVR cannot set parameters.
* Outgoing calls can send audio. Incoming calls will not connect.

Re: [General] The new PAP2 v2.0

Mon, 21 Jan 2008 01:01:24 EDT

rcilink : Sort of off-topic, but here's the answer to the IP8100 problems you are finding:

- the 11.4.1 firmware has intentional breakage in the webcm (web config manager), making it impossible to use the web interface to set the SIP username and password.

I have also found this on the D-link VTA device on the newer firmware. It looks like they did this to deter folks from trying to re-use the unit after it is provisioned via XML method (standard method for most providers).

My suggestion: use 11.4.0 firmware to make your mods on. It works (web interface works fine for SIP configs).

You should register for an account here, so i can send you some more detailed information about this.

For example, I have had no trouble making firmware packages that can load via the IP8100 web interface (tested on 11.1.0, 11.4.0, and 11.4.1). I made no effort to make a signature. I used the tichksum to add the last 8 bytes to the firmware as usual and it worked.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 23:56:27 EDT

GrauerFuchs : I think I'm going to defer to rcilink and Mazilo on the specifics for setup of the IP8100. I have no experience with this particular box. From general knowledge of the setup and design of similar boxes, it seems to me, however, that this machine uses a different key in its user configuration. If this is the case, you will need to alter /etc/config.xml and the /usr/www_safe/html/voice/voiceLine?.html files there and in the advanced directory to suit the new key it uses for storage of those settings. Most likely, you will also need to alter the signature stored in the last 149 bytes of the file (just before the magic number and CRC).
If this box is like the PAP2, it will report 'provisioned' if it isn't seeking provisioning details. I believe it's simply a check to see if it's in the process of attempting to retrieve its data.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 23:33:48 EDT

anon : @mazilo: Sure. I have come to the conclusion that it must be the FAT file system, in which most USB sticks are formatted. The lzma-squashfs on the AR7 platform needs UID/GID of 5000/5001 as correct owners in order to correctly mount/parse the filesystem. The FAT filesystem does not retain these, thus the FS can't be loaded. That said, it was a stupid error that took me about a day to figure out.

@all, Grauerfuchs. First of all, thanks for all the input. My plan was to come out with this kind of a surprise, but now I am stuck with no further ideas. I plan a port to the IP8100 by Vtech. Thus the different locations and so on. There is no CYT_PRIVATE partition, the others are in slightly different locations, but that is not really important.

Some other key perceptions:
In the newest firmware, the bootloader environment cannot be unlocked through SSH. A downgrade is necessary, after which PSPBoot can be and will (to my surprise) stay unlocked.
Also, this firmware conducts a "digital signature" check that goes above and beyond the CRC check. At first, I thought this only meant the partition CRCs in the firmware header were also being checked, but after calculating those the firmware would still not load them. I confirmed my calculations by tichksum'ming the CRCs inside the original firmware file, so this cannot be the problem either. The newest firmware will not even re-flash itself or an older version! My guess is that it expects a higher version number inside the firmware file, possibly in one of the "unknown" dwords in the header.

All no big problems, since we can always flash via SSH/PSPBoot. However, the provisioning subsystem (namely those close sourced cfgmgr and lightbox routines) causes troubles that I cannot circumvent. I hope one of the wizards here will be able to help me.
What I did is I adapted the config.xml file. All fine, passwords set and so forth. Some of the XML keys I do not understand, but put them in there as well. All but some settings can be set and will be retained, but two. Here is an excerpt of the output the serial console produces.

(LAN is being plugged in:)                                                                                                         Sep  8 12:00:34 [MAC] cfgmgr(provision): Startup delay elapsed, do first poll, state 1                                                                             Sep  8 12:00:34 [MAC] cfgmgr(provision): provision_poll: wan_state 0                                                                                               Sep  8 12:01:03 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:01:03 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:01:03 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Sep  8 12:01:03 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Sep  8 12:01:31 [MAC] cfgmgr(provision): provision_apply: voice_config 1                                                                                           Sep  8 12:01:31 [MAC] cfgmgr(logic): Saving on Apply                                                                                                               Sep  8 12:01:35 [MAC] voice: N2V_XML_CONFIG_UPDATE                                                                                                                  ep  8 12:01:35 [MAC] voice: Config for coding                                                                                                                     Sep  8 12:01:36 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:01:36 [MAC] cfgmgr(fwan-106): fw_action: 1. -I INPUT -i eth0 -p udp --dport 10050:10151 -j ACCEPT                                                        Sep  8 12:01:36 [MAC] cfgmgr(fwan-106): fw_action: 2. -t nat -I PREROUTING -i eth0 -p udp -d  --dport 10050:10151 -j DNAT --to                                     Sep  8 12:01:36 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:01:36 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:01:36 [MAC] cfgmgr(provision): VOICE_CONFIG_SAVE received, Saving the profile                                                                            Sep  8 12:01:40 [MAC] voice: V2N_CONFIG_SAVE                                                                                                                       Sep  8 12:01:40 [MAC] lightbox: Received PROV_DONE                                                                                                                 Sep  8 12:01:41 [MAC] cfgmgr(provision): Voice app is configured                                                                                                   Sep  8 12:01:41 [MAC] cfgmgr(provision): EVT_REPORT_PROV_VOICE_READY received during a wrong state 1!                                                              Sep  8 12:02:14 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:02:14 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:02:14 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Sep  8 12:02:14 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Sep  8 12:03:00 [MAC] cfgmgr(logic): Saving on Apply                                                                                                               Sep  8 12:03:33 [MAC] cfgmgr(provision): provision_apply: voice_config 1                                                                                           Sep  8 12:03:33 [MAC] cfgmgr(logic): Saving on Apply                                                                                                               Sep  8 12:03:55 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:03:55 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Sep  8 12:03:55 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Sep  8 12:03:55 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      (WAN is being plugged in:)Sep  8 12:04:58 [MAC] cfgmgr(provision): provision_event: IFACE_CONFIGURED event received, setting want_state to 1: dhcpc-105                                      Sep  8 12:04:58 [MAC] cfgmgr(provision): provision_poll: wan_state 1                                                                                               Sep  8 12:04:58 [MAC] cfgmgr(provision): Starting wget '0.0.0.0/tiMAC.xml' '0.0.0.0/tiMAC.xml' '-nv' '--failover' '--tries=2' '-O' '/var/tmp/pro Sep  8 12:04:58 [MAC] cfgmgr(provision): Firmware version: vtech-11.4.1-r070125-4.019.1-r000015.img                                                                Sep  8 12:04:59 [MAC] cfgmgr(voice): Sending IP address[5]: 192.168.2.187                                                                                          Sep  8 12:04:59 [MAC] cfgmgr(sntp): start: sendProgramStart                                                                                                        Sep  8 12:04:59 [MAC] cfgmgr(upnp): EvtRepIfaceConf calling upnp_load                                                                                              Sep  8 12:04:59 [MAC] cfgmgr(provision): Provision: acquired Voice-AP Lock                                                                                         Sep  8 12:04:59 [MAC] cfgmgr(logic): Logic EVT_REPORT_VOICE_IPADDR received, calling logdest resolve                                                               Sep  8 12:04:59 [MAC] cfgmgr(manager): manager_find_defaults - !mod                                                                                                Sep  8 12:04:59 [MAC] cfgmgr(manager): manager_get_defaults - !config                                                                                              Sep  8 12:04:59 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:05:00 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:05:00 [MAC] cfgmgr(fwan-106): FWAN:fwan_evt_rep_fw_action                                                                                                Sep  8 12:05:00 [MAC] lightbox: Received PROV_START                                                                                                                Sep  8 12:05:00 [MAC] voice: V2N_IP_SET                                                                                                                             ep  8 12:05:00 [MAC] voice: TCID 0: tls_proxy: :5061                                                                                                               ep  8 12:05:00 [MAC] voice: TCID 1: tls_proxy: :0                                                                                                                 Sep  8 12:05:00 [MAC] lightbox: Received VOICE_LINE_PROVISIONED                                                                                                     ep  8 12:05:00 [MAC] voice: TCID 2: tls_proxy: :0                                                                                                                  ep  8 12:05:00 [MAC] voice: TCID 3: tls_proxy: :0                                                                                                                 Sep  8 12:05:00 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                         Sep  8 12:05:01 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                         Sep  8 12:05:01 [MAC] cfgmgr(upnp): UPNP started.                                                                                                                   ep  8 12:05:01 [MAC] voice: register sip phone 5555555 (LINE 1): FAILED                                                                                            ep  8 12:05:01 [MAC] voice: TCID 0 DNS resolution Successful on (REMOVED).com, ip = 87.106.181.52, TTL = 60                                                       Sep  8 12:05:01 [MAC] lightbox: Received VOICE_TELEPHONY_SRVC_UNAVAIL, port = 0                                                                                    Sep  8 12:05:01 [MAC] cfgmgr(SysEvents): Received VOICE_TELEPHONY_SRVC_UNAVAIL event from VoiceApp                                                                 Sep  8 12:05:01 [MAC]   weightmap: 100 100 60 40                                                                                                                   Sep  8 12:05:01 [MAC]   qlenmap: 15 20 39 26                                                                                                                       Sep  8 12:05:01 [MAC]   sch_table: 2 2 2 3 3 2 2 2 3 3                                                                                                             Sep  8 12:05:01 [MAC]   gap: 0                                                                                                                                     ConfigManTimer: 9 timer(s) changed by 169400638 sec                                                                                                                         (SNTP works from here on:)Jan 21 03:48:55 [MAC] cfgmgr(provision): provision_parse: File /var/tmp/provision.xml is empty                                                                     Jan 21 03:48:55 [MAC] cfgmgr(provision): Active image is secondary                                                                                                 Jan 21 03:48:55 [MAC] cfgmgr(provision): Delaying image download for 32767 minutes                                                                                 Jan 21 03:48:55 [MAC] lightbox: Received PROV_DONE                                                                                                                 Jan 21 03:49:12 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                         Jan 21 03:49:12 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                          an 21 03:49:12 [MAC] voice: TCID 0 DNS resolution Successful on (REMOVED).com, ip = 87.106.181.52, TTL = 60                                                       Jan 21 03:49:32 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                         Jan 21 03:49:32 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                          an 21 03:49:32 [MAC] voice: TCID 0 DNS resolution Successful on (REMOVED).com, ip = 87.106.181.52, TTL = 60                                                       Jan 21 03:49:35 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Jan 21 03:49:35 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_NAME' in 'provision':                                        Jan 21 03:49:35 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Jan 21 03:49:35 [MAC] webcm: set error: message= :Bad key 'settings/VOICE_XML/PORT_1_CONFIG/AUTH_USER_PASSWD' in 'provision':                                      Jan 21 03:49:52 [MAC] lightbox: Received VOICE_DNS_SUCCESS                                                                                                         Jan 21 03:49:53 [MAC] lightbox: Received VOICE_DNS_SUCCESS

Where does it look for the keys? Why are they bad? When I crate a /var/tmp/provision.xml (either empty or a regular provisioning file, that messes things REALLY up. A routine keeps restarting and producing a lot of console garbage. My guess is that these two settings AUTH_USER somehow rely on the provisioning. It does not seem to be possible to entirely configure INSTEAD of provisioning.

I also tried turning provisioning off, to no avail. Funny enough, when I "restore provisioning settings", the Web frontent will report the box is provisioned. I am not entirely sure when this occurs, but it might have something to do with WAN being plugged in as well.

I'm all out of ideas. You guys have experience with so many AR7 devices and successfully created so many unlocks, maybe you can help.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 21:12:55 EDT

GrauerFuchs : The propagated info was indeed replaced in the config.xml. The two DNS servers are the addresses to the OpenDNS service, and the NTP servers are all from the public pool with a fallback to the main pool round-robin server. Yes, the lines defaulted to 'off' so it wouldn't attempt to register to nothing. I may amend Line 1 so it doesn't register, but will accept calls on the IP regardless.

As far as the Upgrade tab, that was left unattached intentionally. Right now, there is no 'official' firmware for the box, so any re-loading would completely bork the NA-ized abilities. You might also try logging in to the Voice tab and then dropping back out to the Administration tab. The update tab appeared for me when I was a superuser.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 21:07:00 EDT

meister_sd : OK - I finally got my pap2v2 backed up via JTAG and tried a couple of things....

First, I went in at 0x0000c350 and removed my ADMIN_PWD, CRYPT_KEY and HASH_DIR. Then I loaded b5 of GrauerFuchs firmware and checked it out.

First thing I noticed is the firmware doesn't remove any pre-set information. My box was provisioned from vonage and I knew the admin password (box has been hacked for a long time). I was able to get into the voice section with my vonage password and all vonage info was retained. I thought this was nice. Then I did a factory reset of both router and voice and all vonage info is gone - I think. Logging back into the voice section, my credentials are Admin/Admin, which is what I expected since I wiped my info from the bootloader via JTAG. What surprised me was the info propagated. My DNS server 1 is 208.67.222.222, DNS server 2: 208.67.220.220, NTP server 1: 64.202.112.65, NTP server 2: 75.144.70.35 and NTP server 3: pool.ntp.org. I know for a fact none of this info is coming from my router. Also, by default, Line 1 and Line 2 Enable is set to OFF. I think this is programmed by the default config.xml file in /etc. I'll take a look at this.

What I REALLY like about this interface is when you are in Voice, the other tabs are on top - Setup, Administration, Status, Voice. This makes it very easy to move between the two. Even real Linksys firmware isn't doing this, ie. RTP300-NA. The voice screens have been totally re-written and the layout is slightly changed from default but easier to read and a little more intuitive.

My hats off to GrauerFuchs, he has spent a LOT of time on this.... I can't wait to try the new version with the RTP voice code that is integrated.

Edit: I noticed that the Update tab under Administration isn't there - still has to be manually typed in. (for firmware updates via the web interface)

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 20:21:46 EDT

GrauerFuchs : You shouldn't be required to edit the code at all. These files are already pre-patched and tested on the squashfs-lzma filesystems. Just in case there was a bug, exactly what changes did you make?

One more thing to check: The URL for the package I provided came with some pre-built executables present. Those worked for me on multiple systems. Did you try with those?

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 19:07:52 EDT

yahoo2003 :

said by GrauerFuchs :

All you need is the separate tools package. You don't need to patch your kernel to mount the filesystem. Here's the URL for the tools I use:
»wiki.openwrt.org/OpenWrtDocs/Har···.tar.bz2
As for these tools, simply extract them into a directory and 'make'.

After install ubuntu, I found I need to install "build-essential" and "zlib1g-dev" and edit lines 433 and 489 of "mksquashfs.c".
Then I found I need "lib" from lzma427. I downloaded, patched and built "lzma427" from this link
»www.beyondlogic.org/nb5/squashfs_lzma.htm
After built "squashfs-tools" and ran
../squashfs-tools/unsquashfs-lzma sqfs.img
I got
"zlib::uncompress failed, unknown error -3
FATAL ERROR aborting: uncompress_inode_table: failed to read block
zlib::uncompress failed, unknown error -3
*** glibc detected *** ../squashfs-tools/unsquashfs-lzma: double free or corruption (top): 0x0810a898 ***
......."
The file "sqfs.img" is the "sqfs_root segment" with offset 507904 and length 2678784 (with header "hsqs").

Re: [General] The new PAP2^H^H^H^HRTP300?

Sun, 20 Jan 2008 16:47:58 EDT

GrauerFuchs :

said by Velund :

Really nice work! Does it have STUN support now?

With that firmware in place, yes. I still have yet to work out full function, but when I do, I'll post the details.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 16:47:02 EDT

GrauerFuchs :

said by toro :

Does anyone know which mtd block holds the factory settings (and what is the address range) ? I was wondering if it's possible to erase them completely after one gained access to the SSH shell.

Unfortunately, that trick won't work on a Von@ge device. The firmware contains information specific to the carrier, so even if you do wipe out all of the configuration settings, it will re-load them from the firmware image.

Re: [General] The new PAP2 v2.0

Sun, 20 Jan 2008 13:38:28 EDT

toro : Does anyone know which mtd block holds the factory settings (and what is the address range) ? I was wondering if it's possible to erase them completely after one gained access to the SSH shell. Something similar to steps 6-7 in this wrtp54g-er unlocking method.

Re: [General] The new PAP2^H^H^H^HRTP300?

Sun, 20 Jan 2008 07:53:19 EDT

Velund : Really nice work! Does it have STUN support now?

Re: [General] The new PAP2^H^H^H^HRTP300?

Sat, 19 Jan 2008 22:00:49 EDT

mazilo :

said by GrauerFuchs :

I currently have an RTP300 Sipura voice driver and server installed and running on the PAP2v2!

Excellent job!!! Hopefully, you will be able to make it works completely. I wondered if this RTP300 firmware supports T.38 CoDec. Hopefully, this mod will also allow a PAP2v2 handle two concurrent G729 CoDec calls.

Re: [General] The new PAP2^H^H^H^HRTP300?

Sat, 19 Jan 2008 20:25:21 EDT

GrauerFuchs : Surprise, surprise! I just had a pleasant success with the second fork of firmware devel I was testing. I currently have an RTP300 Sipura voice driver and server installed and running on the PAP2v2! The firmware is responding correctly so far with only a few minor query errors being reported from the webcm interface. The module itself is up and running with no reported errors, and can be configured from the web. I have yet to test the viability of the voice features, but if this works, I will focus on releasing the details and procedure for implementing this alternative. I do have to warn potential experimenters. This firmware alters the mtd allocations. Because of this, it makes it difficult to reverse the changes and revert to the previously announced firmware patches.

Edit + addendum:
Initial testing is promising. IVR works, it recognizes the telephone connection, and will make and receive calls. Outgoing audio is fine, incoming RTP doesn't seem to make it to the box. This is likely due to the limited patching done for a first-run test, and can likely be corrected without much difficulty.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 19:57:45 EDT

yahoo2003 : This is very helpful. Thanks! :)

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 19:56:00 EDT

GrauerFuchs : All you need is the separate tools package. You don't need to patch your kernel to mount the filesystem. Here's the URL for the tools I use:

»wiki.openwrt.org/OpenWrtDocs/Har···.tar.bz2

I didn't bother with the kernel mod, though I probably should build the module just for S&G.

As for these tools, simply extract them into a directory and 'make'.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 19:41:44 EDT

yahoo2003 :

said by GrauerFuchs :

You may want to consider Debian, Slackware, Ubuntu, or even a RH Fedora release. If your machine is powerful enough and has a good amount of memory, you may even be able to do all your work from either a LiveCD or from a virtual machine, which would leave your current setup untouched and unaltered.

Thanks for the suggestions.
My gcc version is 3.2.3, it's too old to build kernel 2.6.23.
I like Ubuntu LiveCD, from there I can install squashfs, but I'm not sure how to install lzma patch from LiveCD.
I have decided to replace RH with Ubuntu. I may need your help to install lzma.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 18:43:17 EDT

anon : Hello Everyone.

I have been reading here and it looks like the gurus have made it possible to unlock 1.00.22 version of Pap2v2.

Can someone list the steps involved for novice folks like me.

Do you need any extra hardware for unlocking this?

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 18:29:15 EDT

GrauerFuchs : Compiling the squashfs-lzma tools manually should do well on GCC3.3+ or GCC4. If you're still running a 2.4 kernel, are you also running GCC2? (gcc -v to check) If so, you may need to upgrade your distribution to easily work on this. The Linux distro I use is Gentoo, but it requires much more in-depth knowledge of the operating system to run it at all. You may want to consider Debian, Slackware, Ubuntu, or even a RH Fedora release. If your machine is powerful enough and has a good amount of memory, you may even be able to do all your work from either a LiveCD or from a virtual machine, which would leave your current setup untouched and unaltered. If compiling it is still a problem, let me know which binutils, glibc, gcc, and your machine type, and I'll see if I can compile a version that will run under your setup. If you don't know where to find those details, look under the RedHat Package Manager (rpm) database. They'll be listed there.

Failing that, I could also have a go at compiling it with the results of 'gcc -v' and 'ls /lib/*libc-*' from your system.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 11:57:10 EDT

yahoo2003 :

said by GrauerFuchs :

It relies on the following pre-compiled tools, all in the system path:
dd, mksquashfs-lzma, unsquashfs-lzma, tichksum

I'd like to try your patch, I have Redhat Linux with kernel 2.4.21-4.EL and had hard time to install sqsfs-lzma tools. What Linux distribution do you recommend? I'm not a Linux expert.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 08:03:41 EDT

mazilo :

said by ricekin :

My advice to everybody who wants to apply this patch: Never use a USB stick as your working environment... It messes up the permissions. :)

Can you provide additional advice about this USB stick and how it messed up the permissions? :D

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 04:56:14 EDT

GrauerFuchs : Possibly so, or check your device for the other faults. Since it's using unusual locations for its storage, that may give it trouble with some storage. I ran into that problem on mine with a test firmware that altered the partitioning structure. My solution was to boot into the psbl prompt, format CONFIG_A, IMAGE_B, CONFIG_B, cyt_private, and then unset those params from the environment. Yes, it complained upon its next boot, but it reinstated the default scheme upon use of the physical reset button after that. From then on, it was perfectly stable and capable. If you don't mind, I would still like to see your partitioning table. Even if it's only for reference, it would be of aid to others with the same troubles you are facing now.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 04:47:26 EDT

anon : Thank you Grauerfuchs. It was the $§%" permissions. I have it running now. My advice to everybody who wants to apply this patch: Never use a USB stick as your working environment... It messes up the permissions. :)

It is working now, but the SIP configuration is not saving yet. That possibly has to do with my changes I made to config.xml.

Anybody experienced the same? Have I been too radical? Must the device show it has been provisioned in order to keep the settings?

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 02:00:10 EDT

GrauerFuchs : Possible, but I'm still seeing odd things from the logs you posted.

After re-checking the saved permissions in the patch data, I found a few discrepancies. To eliminate this as a possibility, I've re-uploaded the patch file with the corrected permissions.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 01:44:45 EDT

anon : I am at the point where I think it might be a permissions problem within the filesystem. Is that possible?

The squashfs-version issue was resolved: It is a squashfs1-filesystem.

Thanks for all your input.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 01:22:19 EDT

GrauerFuchs : My biggest concern is the information regarding where it's getting the data. That doesn't coincide with what I've seen of the general platform and layout. Most of the output is normal booting, but I'm wondering if your box has an odd or broken image layout for some reason. That's why I asked for the output from the bootloader's printenv command.

On the config file, I have yet to find a way to enable/disable provisioning from the web interface. Because of this, leaving it enabled but directed to itself allows for the use of later provisioning tools. There are a few of us that have more than one box, or make unusual config changes from time to time, and we benefit from having provisioning services enabled. In addition, certain providers will offer to provision the box without locking it. This makes it easier on the users, because they don't have to manually enter configs for the service.

Re: [General] The new PAP2 v2.0

Sat, 19 Jan 2008 01:14:45 EDT

anon : Thank you Grauerfuchs. It took me about a day to figure out that the above output is perfectly normal and occurs when booting a regular firmware, too.

The problem is in the last line "No init found, kernel panic". This causes a continuous reboot.

Hence, something must be wrong with my squashfs-lzma partition. I read somewhere that there are different versions of squashfs in use. I find it unlikely that if unsquashfs unpacks, but makesquashfs-lzma produces a broken partition. I will retry using the command line parameters you have specified in your latest file. Any suggestions?

Excellent work, by the way. Slick, slim, small code.

One question to your config-file: Why do you not simply turn provisioning off entirely?

Re: [General] The new PAP2 v2.0

Fri, 18 Jan 2008 05:01:08 EDT

GrauerFuchs : Okay, here we go. New revision of the NA patch. This version adds new features to the Voice tab, and provides both basic and advanced modes. New options are also present on some of the pages.

A new auto-patcher tool is included in this version. Please note the patching tool is ALPHA software, and therefore, not yet able to properly handle errors or all scenarios. This patching tool will only run under Linux, BSD, and similar. It relies on the following pre-compiled tools, all in the system path:
dd, mksquashfs-lzma, unsquashfs-lzma, tichksum

Manual processing of the patch can still be completed in case of error or unsupported OS.

As always, please pass along any bugs found.

Edit: Re-posted patch due to an error in permissions inside the patched filesystem

PAP2v2-1.00.···0.5b.zip 34,121 bytes

Re: [General] The new PAP2 v2.0

Fri, 18 Jan 2008 02:45:47 EDT

GrauerFuchs : The top block says to me that the flash chip failed to write. This may indicate a problem with the device.

The second indicates unusual placement of the storage partitions. Could you restart the box and stop in the bootloader, and from the (psbl) prompt, give me a printout of the following variables:

HWRevision
bootloaderVersion
IMAGE_A
CONFIG_A
IMAGE_B
CONFIG_B
BOOTLOADER
boot_env
cyt_private

You can do this by use of the printenv command.

Re: [General] The new PAP2 v2.0

Fri, 18 Jan 2008 02:33:56 EDT

anon : Hey! I am having trouble re-flashing the prepped image. Here is what I did:

Took an original firmware file.
1. Extracted und unsquashed the filesystem into a directory
2. Manipulated the config.xml-file (by, for example, turning provisioning off.
3. Makesquashed by giving the directory in the command line.
4. Re-inserted in the position of the old squashfs ("hsq...")
5. The squashfs-lzma file had a couple of 00h at the end. From their end on, i filled everything with FFh until the magic number.
6. Let the device calculate the checksum and wrote it in the firmware file.

Here is where I am stuck. The device takes the image, decompresses it but something goes wrong. I am parsing the serial console output here:

Sep  8 12:20:18 [...] lightbox: Received UPGRADE_DOWNLOAD_DONESep  8 12:20:21 [...] pc: Active configuration copied Sep  8 12:20:21 [...] pc: Making current image inactive Sep  8 12:20:21 [...] : Attempting to use a write to change a flash bit from 0 to 1 (addr 0x44000A, read 0x17FF, write 0xBFFF).Sep  8 12:20:21 [...] : Flash write/erase exceeded time limit! addr 0x44000A, last two reads = 0xFF64 0xFF24.Sep  8 12:20:21 [...] : do_write_buffer failed (try 1 of 3).Sep  8 12:20:21 [...] : Attempting to use a write to change a flash bit from 0 to 1 (addr 0x44000A, read 0x17FF, write 0xBFFF).Sep  8 12:20:21 [...] : Flash write/erase exceeded time limit! addr 0x44000A, last two reads = 0xFF64 0xFF24.Sep  8 12:20:21 [...] : do_write_buffer failed (try 2 of 3).Sep  8 12:20:21 [...] : Attempting to use a write to change a flash bit from 0 to 1 (addr 0x44000A, read 0x17FF, write 0xBFFF).Sep  8 12:20:21 [...] : Flash write/erase exceeded time limit! addr 0x44000A, last two reads = 0xFF64 0xFF24.Sep  8 12:20:21 [...] : do_write_buffer failed (try 3 of 3).Sep  8 12:20:21 [...] voice: N2V_PREP_RESTARTSep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 1. -D INPUT -i eth0 -p udp --dport 10050:10151 -j ACCEPTSep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 2. -t nat -D PREROUTING -i eth0 -p udp -d 192.168.3.11 --dport 10050:10151 -j DNAT --to 192.168.3.11Sep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 1. -D INPUT -i eth0 -p udp --dport 10000:10000 -j ACCEPTSep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 2. -t nat -D PREROUTING -i eth0 -p udp -d 192.168.3.11 --dport 10000:10000 -j DNAT --to 192.168.3.11Sep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 1. -D INPUT -i eth0 -p tcp --dport 10000:10000 -j ACCEPTSep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 2. -t nat -D PREROUTING -i eth0 -p tcp -d 192.168.3.11 --dport 10000:10000 -j DNAT --to 192.168.3.11Sep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 1. -D INPUT -i eth0 -p udp --dport 10050:10151 -j ACCEPTSep  8 12:20:25 [...] cfgmgr(fwan-106): fw_action: 2. -t nat -D PREROUTING -i eth0 -p udp -d 192.168.3.11 --dport 10050:10151 -j DNAT --to 192.168.3.11Sep  8 12:20:25 [...] cfgmgr(logic): Voice is ready, rebootingRestarting system.

I have two guesses:
a) The device wants to fetch some sort of information from the WAN. Or do you know what else the cfgmgr wants on those ports (10050...)?
b) I did something wrong when making the squash image. When I use the command line do I just give the name of the squashfs-root folder and then it puts all the folders in the root of the squash image? Or do I need a special option so that it does that? Anyways, here is some more output:

avalanche flash device: 0x800000 at 0x10000000.cfi_cmdset_0002 (swapper). Amd/Fujitsu Extended Query Table v1.3 at 0x0040cfi_amdstd_setup (swapper).number of CFI chips: 1Releasing semaphore (swapper).Avalanche: Adding a root image (0xbc000), with size (0x320000).Creating 1 MTD partitions on "Physically mapped flash:0":0x000bc000-0x003dc000 : "root"mtd: partition "root" doesn't start on an erase block boundary -- force read-onlyAvalanche:      linking partition root: root -> ../../mtdblock/0Avalanche: Adding a RESERVED_PRIMARY_KERNEL image (0x44000), with size (0x78000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00044000-0x000bc000 : "RESERVED_PRIMARY_KERNEL"mtd: partition "RESERVED_PRIMARY_KERNEL" doesn't start on an erase block boundary -- force read-onlyAvalanche:      linking partition RESERVED_PRIMARY_KERNEL: kernel -> ../../mtdblock/1Avalanche: Adding a RESERVED_PRIMARY_ROOT_FS image (0xbc000), with size (0x320000).Creating 1 MTD partitions on "Physically mapped flash:0":0x000bc000-0x003dc000 : "RESERVED_PRIMARY_ROOT_FS"mtd: partition "RESERVED_PRIMARY_ROOT_FS" doesn't start on an erase block boundary -- force read-onlyAvalanche:      linking partition RESERVED_PRIMARY_ROOT_FS: root -> ../../mtdblock/2devfs: devfs_do_symlink(root): could not append to parent, err: -17Avalanche: Adding a RESERVED_PRIMARY_IMAGE image (0x40000), with size (0x3c0000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00040000-0x00400000 : "RESERVED_PRIMARY_IMAGE"Avalanche:      linking partition RESERVED_PRIMARY_IMAGE: active_image -> ../../mtdblock/3Avalanche: Adding a RESERVED_SECONDARY_IMAGE image (0x440000), with size (0x3c0000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00440000-0x00800000 : "RESERVED_SECONDARY_IMAGE"Avalanche:      linking partition RESERVED_SECONDARY_IMAGE: inactive_image -> ../../mtdblock/4Avalanche:      linking partition RESERVED_SECONDARY_IMAGE: inactive_image_char -> ../../mtd/4Avalanche: Adding a RESERVED_PRIMARY_XML_CONFIG image (0x400000), with size (0x20000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00400000-0x00420000 : "RESERVED_PRIMARY_XML_CONFIG"Avalanche:      linking partition RESERVED_PRIMARY_XML_CONFIG: active_config -> ../../mtdblock/5Avalanche:      linking partition RESERVED_PRIMARY_XML_CONFIG: active_config_char -> ../../mtd/5Avalanche: Adding a RESERVED_SECONDARY_XML_CONFIG image (0x420000), with size (0x20000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00420000-0x00440000 : "RESERVED_SECONDARY_XML_CONFIG"Avalanche:      linking partition RESERVED_SECONDARY_XML_CONFIG: inactive_config -> ../../mtdblock/6Avalanche:      linking partition RESERVED_SECONDARY_XML_CONFIG: inactive_config_char -> ../../mtd/6Avalanche: Adding a RESERVED_BOOTLOADER image (0x0), with size (0x20000).Creating 1 MTD partitions on "Physically mapped flash:0":0x00000000-0x00020000 : "RESERVED_BOOTLOADER"Avalanche:      linking partition RESERVED_BOOTLOADER: bootloader -> ../../mtdblock/7Initializing Cryptographic APINET4: Linux TCP/IP 1.0 for NET4.0IP Protocols: ICMP, UDP, TCP, IGMPIP: routing cache hash table of 512 buckets, 4KbytesTCP: Hash tables configured (established 1024 bind 1024)Linux IP multicast router 0.06 plus PIM-SMip_conntrack version 2.0 (128 buckets, 1024 max) - 380 bytes per conntrackDEBUG: Registering protocol 6 in the conntrack 0x943a4f40DEBUG: Registering protocol 17 in the conntrack 0x943a4c98DEBUG: Registering protocol 1 in the conntrack 0x943a4facDEBUG: Registering protocol 50 in the conntrack 0x943a5178Error: NAT Protocol 50 already registered...ip_tables: (c)2000 Netfilter core teamDEBUG: Registering protocol 6 in the NAT 0x943a5b04DEBUG: Registering protocol 17 in the NAT 0x943a5ad4DEBUG: Registering protocol 1 in the NAT 0x943a5b34netfilter PSD loaded - (c) astaro AGNET4: Unix domain sockets 1.0/SMP for Linux NET4.0.VFS: Mounted root (squashfs filesystem) readonly.Mounted devfs on /devFreeing unused kernel memory: 60k freedKernel panic: No init found.

Can any of the wizards help me? Maybe someone could parse some of the output it SHOULD create. Thank you all for your support! I really wanna try this new FW!

Re: [General] The new PAP2 v2.0

Fri, 18 Jan 2008 02:26:59 EDT

GrauerFuchs : Give me a few minutes, I'm preparing a new patch pack that will make that task far easier. :)

As far as your PAP2, which version of the firmware is it running right now? The web install gets twitchy if the running firmware is already 1.00.16.

Re: [General] The new PAP2 v2.0

Fri, 18 Jan 2008 01:52:23 EDT

anon : I would like to follow GrauerFuchs's new findings, but I am having trouble understanding the process.
I use Linux, but just never worked on anything like this.

So I downloaded pt-11.4.0-r060628-1.00.16-r060628.img from that Fonage site. (is this right?)
How exactly do I split this?

Re: [General] The new PAP2 v2.0

Sun, 13 Jan 2008 21:40:09 EDT

GrauerFuchs :

said by johnny65 :

Can I downgrade my firmware to 1.00.16 using jtag and then unlock it with CYT?

Probably so, but you would need a copy of the 1.00.16 firmware set up for it. It's far easier and faster to do this by using the bootloader console, on the already populated serial port. All you need is a tftp server on a computer, a serial port to connect to the console, and a level converter to adapt the TTL serial levels on the PAP2 to RS-232 for your PC.

Should I use a buffered or unbuffered jtag. What are the differences in the time it takes to flash with each one?

If you need to use JTAG, the buffered cable is far more reliable. That's the main difference. Buffered vs unbuffered will flash in approximately the same amount of time, but the buffered cable is far less prone to errors.

Re: [General] The new PAP2 v2 NA firmware patch 0.1b

Sun, 13 Jan 2008 21:34:31 EDT

GrauerFuchs : Okay, time for the real fun to begin! The attached patch is a gzipped tar archive intended to be unzipped in the root directory. This patch will update the voice web pages for a mostly uniform appearance, and it will also modify the default configuration parameters for NA (unlocked) operation. This is beta code, and may still be buggy.

Required software:
squashfs-lzma tools
tichksum program (if you plan on installing from the Web interface)
dd or an equivalent program to split files
A hex editor (if you plan on installing from the bootloader console)
tar or an equivalent decompression program with tar+gz support
Firmware image: pt-11.4.0-r060628-1.00.16-r060628.img
This Patch.

All the appropriate instructions and legal terms are in the README.txt file.
Have fun, and please let me know of any bugs!

BTW, the default passwords are admin:admin and Admin:Admin.

Addendum: This version of the patch does not replace the entire web GUI. The changes only affect the voice module's operation and configuration.

pap2v2-1.00.···0.1b.zip 42,235 bytes
PAP2 Ver.2 NA Patch 0.1beta

Re: [General] The new PAP2 v2.0

Sun, 13 Jan 2008 12:21:05 EDT

GrauerFuchs : Yes and no. The web_safe folder is active for all tabs except Voice in both NA and Von@ge WRTP54Gs, RTP300s, and PAP2v2s. In the Von@ge units, the ggsip package has stripped down the pages because they aren't required for remote provisioning. I've already attempted an NA-version ggsip transplant, but something dies in the linking to resources. I will be attempting it again later with some additional debugging materials prepared in hopes of tracking down the issues.

Re: [General] The new PAP2 v2.0

Sun, 13 Jan 2008 09:56:24 EDT

mazilo :

said by GrauerFuchs :

The problem with the non-uniform web system comes from the fact that Linksys has embedded the Voice module pages in the ggsip program itself. You never see a physical web page for them, because the HTML is generated by the program itself. The voice pages in the web_safe folder are stagnant, relics of the old CyberTAN initial development for the unit. Although they're functional enough for Von@ge's needs, they are not actively maintained, and so they don't match the interface beyond the Beta coding.

If what you said above is true, then the web_safe folder/directory is really a waste of space. BTW, is this also done on a WRTP54G-NA firmware? If so, then Linksys should consider to replace the web_safe folder with a dropbear for an SSH. :D
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - 'NA' firmware status

Sun, 13 Jan 2008 05:56:17 EDT

GrauerFuchs : Well, here we go. Since I can no longer edit the status posted on the previous page, I'm updating here. The beta 1 web interface/NA firmware patch is all too close to completion. Tests will still need to be done to ensure it updates properly when settings are changed, but those issues should be easy to correct.

Known bugs:
- Setup page does not load information
- Restore Defaults not functioning properly

Here's a new pair of screenshots of the redesigned web structure. Yes, it intentionally looks very much like the original.

pap2v2-na-be···reen.zip 134,356 bytes

Re: [General] The new PAP2 v2.0

Sun, 13 Jan 2008 02:44:18 EDT

anon : Been reading this thread and I have some questions.

Can I downgrade my firmware to 1.00.16 using jtag and then unlock it with CYT?

I want to use my pap2 v2(vonage) with via talk. Any info on that?

Should I use a buffered or unbuffered jtag. What are the differences in the time it takes to flash with each one?

Thanks in advance.

Re: [General] The new PAP2 v2.0

Sun, 13 Jan 2008 01:35:13 EDT

Velund :

said by meister_sd :

The two strings, one for the admin password and the other for the encryption key - those themselves are encrypted in the bootloader area.

Yes, key in bootloader is somewhat encrypted. I returned back original variables for hash dir and admin pwd (one by one) and got valid key for "initial" xml only with all three in place. So, looks like pwd and dir vars used as a hash for bootloader key.

Got admin pwd, then allowed Von@ge to provision my unit again and update to 1.0.22... Login with their admin password, but was unable to save parameters on line 1 and line 2 pages. Only parameters from sip configuration page was saved. Also found that .22 does not display the key on provision page.

Tired to play with it. Hooked serial cable, in pspboot unset all three variables, defragmented env., formatted cyt_private, CONFIG_A and CONFIG_B, loaded .16 image back to active image partition. Everything started, but oops... It doesn't accept plaintext xml anymore.

Set everything in web interface, looks like it works just as before (except plaintext xml provisioning).

Re: [General] The new PAP2 v2.0

Sat, 12 Jan 2008 17:09:11 EDT

GrauerFuchs : The problem with the non-uniform web system comes from the fact that Linksys has embedded the Voice module pages in the ggsip program itself. You never see a physical web page for them, because the HTML is generated by the program itself. The voice pages in the web_safe folder are stagnant, relics of the old CyberTAN initial development for the unit. Although they're functional enough for Von@ge's needs, they are not actively maintained, and so they don't match the interface beyond the Beta coding.

Re: [General] The new PAP2 v2.0

Sat, 12 Jan 2008 15:40:41 EDT

meister_sd :

said by Velund :

BTW: Got encrypted xml for my unit and tried to decrypt it using rc4 executable that was found in this forum and key that was found in bootloader. Not successful. Maybe I missed something...

The two strings, one for the admin password and the other for the encryption key - those themselves are encrypted in the bootloader area.

After you get into the box via SSH, look in the env:

cat /proc/ticfg/env

You will see the Admin PW and encrypt key. It's been a long time, but I think those are different from what you see in the bootloader via JTAG.

Following rcilink's suggestion of stripping and tichksum will get a FW you can load via the web interface.

I did some work making an -NA version also with rcilink's help. The voice and provisioning screens were developed independently so the coding wasn't uniform making it very hard to create a central voice screen. Seems GrauerFuchs made that happen. Good job!

I have a pap2v2 that has a socket mounted and JTAG pins on the board, which also has serial access. I also have a ROM dump of my chip. My FW version is 1.00.22 currently and I have my Admin password from my decoded vonage file. I was able to delete settings in my Provision.html page and they saved... (or seemed to)

BTW - all Admin and encryption keys are unique in the bootloader.

Re: [General] The new PAP2 v2.0

Sat, 12 Jan 2008 03:40:56 EDT

GrauerFuchs : Thanks for the warning. I'll check the code for that one and see if they borked it.

Re: [General] The new PAP2 v2.0

Sat, 12 Jan 2008 03:26:58 EDT

Velund : Looks like there is one more "broken" thing in 1.00.16. Syslog to a remote machine can be set only through provision xml, changes in the web config doesn't change anything during my tests.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 12 Jan 2008 02:41:54 EDT

GrauerFuchs :

said by toro :

Isn't there some sort of checksum over the boot environment block, that needs to be done after the environment variables have been altered ?

Possibly so, but the edits done are in the bootloader block itself, not the boot environment block. There are no checks on the bootloader block.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Fri, 11 Jan 2008 23:51:42 EDT

toro :

said by DerGrauerFuchs :

You also want to edit the bootloader hard-coded environment variables starting at address C31A.

Isn't there some sort of checksum over the boot environment block, that needs to be done after the environment variables have been altered ?

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Fri, 11 Jan 2008 23:51:14 EDT

Velund :

said by GrauerFuchs :

I found the same thing running 1.00.16. Apparently, the dropbear SSH server from that point on will not accept an empty password. 1.00.13 did allow a blank password. Which firmware are you running now?

Currently it is 1.00.16. But once I set everything (including Admin and user passwords) by provisioning, dropbear become available.

I compiled xml with everything I found in web interface (tags there are the same as in provisioning xml) and feed it (unencrypted) from local tftp server.

By the way, does anyone succeed in decrypting provisiuoning xml since release of 1.00.22? I tried to return key and path to unit with 1.00.16 and make a try to re-provision it from Von@ge. Unit downloads encrypted xml, but unable to decrypt it. rc4 also produces garbage. So, I suspect that there is another encryption method in 1.00.22 or maybe I simply missed something.

And another question. Maybe someone seen somewhere a set of compatible voice prompts without Von@ge mentioned? ;)

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Fri, 11 Jan 2008 14:06:40 EDT

GrauerFuchs :

said by Velund :

SSH can be turned on, but unable to login. Maybe my SSH client does not allow to send empty passwords, not sure.

I found the same thing running 1.00.16. Apparently, the dropbear SSH server from that point on will not accept an empty password. 1.00.13 did allow a blank password. Which firmware are you running now?

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Tue, 08 Jan 2008 22:50:57 EDT

Velund :

said by GrauerFuchs Mine is also a 1.01.04, so the hard-coded bootloader info can indeed vary.

No doubt, Linksys writes MAC as a env. variable to bootloader, unique to each unit, so no problem to write a couple of other custom things there at once.

Most likely, admin password is a function of MAC or SN, but I think it will be very hard to find how to generate it, if possible at all.

BTW: Save/restore does not save voice config, just tried to save config, do full factory reset and then restore config from file. Voice configuration was empty.
SSH can be turned on, but unable to login. Maybe my SSH client does not allow to send empty passwords, not sure.

My PAP2v2 (formerly 1.0.22) works fine for almost 2 weeks on sipnet.ru. Make factory reset twice, no attempts to relock. cyt_private partition was not erased, so I doubt it is necessary to clear it.

Re: [General] The new PAP2 v2.0 - 'NA' firmware status

Tue, 08 Jan 2008 21:42:59 EDT

mazilo :

said by GrauerFuchs :

That said, if you can acquire a copy of the pt-11.4.0-r060628-1.00.16-r060628.img firmware, this is the one on which I'm basing the modifications.

Congratulation on your recent achievement to NAize a PAP2v2.

Re: [General] The new PAP2 v2.0 - 'NA' firmware status

Tue, 08 Jan 2008 20:39:30 EDT

GrauerFuchs : Excellent! Welcome aboard. I wish I could provide you a direct link to (or simply provide) the source files or firmware, we do need to be cautious of the copyright law. Since this machine seems to have been designed specifically for 'the big V', we need to be sure we don't cross the violation lines. With a company so far in debt, I'm sure they'd leap at any chance for litigation. That said, if you can acquire a copy of the pt-11.4.0-r060628-1.00.16-r060628.img firmware, this is the one on which I'm basing the modifications.

At a minimum, you'll need a copy of the squashfs-lzma tools (check the OpenWRT site for WRTP54G), the firmware, and a program for splitting files.
In this firmware, the squashfs-lzma root filesystem is 2678784 bytes long, and can be found after the 507904 byte header/kernel.

The files that are in need of work are in the /usr/www_safe/html/voice directory. Specifically, voiceSip.html, voiceCoding.html, voiceLine1.html, and voiceLine2.html need a major re-write to fit the UI design. The rest could probably do with minor work, since Linksys obviously didn't intend end users to have access to the device at all.

Re: [General] The new PAP2 v2.0 - 'NA' firmware status

Tue, 08 Jan 2008 19:45:10 EDT

dsswanson : GrauerFuchs - I would like to help. My PAP2v2 has the dreaded 1.0.22 firmware, but I'm handy with HTML and am happy to help.

Re: [General] The new PAP2 v2.0 - 'NA' firmware status

Mon, 07 Jan 2008 19:27:13 EDT

GrauerFuchs : Okay, status update (with a screenshot):

Note: I'll keep this entry updated with the status.

+ New firmware is loading, and NA / unlocked operation is confirmed even after factory reset.
+ Existing web interface is being overhauled due to inconsistencies, difficulty of editing, and copyright issues.
> + New CSS completed. Only tweaks remain.
> + Setup, Status, and Voice tabs replaced with new code.
> + Currently testing and debugging completed work. New screenshot soon to come, with the PAP2 running on its new web interface!
- Firmware RSA signatures are still acting funky when loading by web interface. Looking to replace firmware upgrade code.
- Firmware relies on closed-source, proprietary, and copyrighted code.

Screenshot updated as of 23:00EST on Jan 7.

Current status: debugging replacement web pages

Development timeline:

PAP2v2-NA v.1.0:
* Rebuild the UI for uniformity and ease of development, using CSS2 standard.
* NA-ize and sanitize the configuration XML files.

The beta of this stage should be done shortly, and will be released as an overlay to the current firmware.

PAP2v2-NA v.1.1:
* Advance the Voice UI to a level similar to that of the RTP300.
* Re-code some of the pages for efficiency of storage, reducing redundancy
* Adapt common features in the UI into scripts for automatic page rendering

PAP2v2-NA v2.0:
* Remove reliance on closed-source or copyrighted material
* Release an entirely open source firmware for the device
* Far future planning; More tasks to come.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Mon, 07 Jan 2008 17:43:22 EDT

GrauerFuchs :

said by Velund :

Hardware revision is 1.01.04...

Mine is also a 1.01.04, so the hard-coded bootloader info can indeed vary.
Overall, it's only a point for information. The difference will not affect operation once the unit is unlocked. A firmware, properly coded, can be made to ignore those variables in the bootloader altogether. I'm in the process of testing this with a custom-crafted 1.00.16 firmware. If this works, I'll build up a set of patch files for others to mod their own firmware for NA operation. Unfortunately, I can't provide a pre-made firmware due to copyright issues and the current litigious nature of companies in the USA.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Mon, 07 Jan 2008 04:08:50 EDT

GrauerFuchs : Success! Okay, it's not a perfect scenario yet, but I was able to get the box to accept the hacked firmware by direct flash method only. I was unable to get around the bad ssh-rsa signature even with the reconfigured checksum following it.

Instead, I stripped out the last 8 bytes and uploaded via bootloader console tftp. The machine happily accepted the altered firmware when done this way. Next task:

rebuilding the web interface to allow easier editing of voice variables, and hopefully also to allow changing of superuser (Admin) password by web

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Mon, 07 Jan 2008 02:23:16 EDT

Velund :

said by GrauerFuchs :

Shall I assume this one is also a Vonage unit? The hash from the password on mine was AB784LJImQx4E

Yes. At least it contains voice prompts like "This telephone line cannot register to Von@ge network"...

Hardware revision is 1.01.04...

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 23:05:26 EDT

GrauerFuchs : One odd thing of note is that it seems Linksys had Vonage in mind from the start. I analyzed the /etc/config.xml from an RTP300 and WRTP54G NA unit as well, and both contain Vonage defaults! Anyone else want to confirm their true NA also has this hidden data?

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 22:56:08 EDT

mazilo :

said by GrauerFuchs :

Shall I assume this one is also a Vonage unit? The hash from the password on mine was AB784LJImQx4E

If so, then it confirms there are differences in the hard-coded Admin passwords in some units. Anyone else willing to put forward the hash they've been able to retrieve?

Not yet until you both confirm if both PAP2v2 units have the same hardware version. Even if you are right, the idea here is to change the Admin and not admin password to a known one since it is this Admin password that is needed to access the VM of a PAP2v2. The password from admin is useless in this matter.

In addition, has anyone managed to acquire a PAP2v2-NA? I'm sure they exist somewhere, but I have yet to see one listed for sale anywhere.

I, too, hope so; however, I believe Linksys specifically produced this PAP2v2 for Vonage used only. Thus, no PAP2v2-NA. Unlocking this device will be much simpler if there is a PAP2v2-NA with a PAP2v2-NA firmware. :D
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 22:24:15 EDT

rcilink : in response to the signature / crc of the firmware:

In my test firmware, I did an exact copy of the rsa junk on the end of the firmware. Then, strip the last 8 bytes. (so the actual file is 8 bytes short) and run tichksum to calculate the proper checksum and have it append it to the file for you.

This has worked for me. I have made them loadable from the web interface and also from the psp bootloader via tftp. A byte has to be changed (after checksum) to make it load from psp bootloader method.

I have not had a pressing need to jtag any of the devices at this time, but I would imagine that the modded firmware would load that way also.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 20:16:29 EDT

GrauerFuchs : Good information. The problem with the PAP2 is the RSA firmware file signature at the end of its firmware file. If the signature doesn't match, it refuses to accept the firmware. Unfortunately, the signature contains some form of CRC or verification, so the valid signature from the original firmware won't match or validate a modified file. The D-link thread says absolutely nothing about the signature or the modifications performed inside the hacked firmware.

edit: So far, I haven't been able to decode the ssh-rsa signature on this, let alone find or determine what it uses as a checksum. This leaves me with 2 issues:

1) Find and forge the ssh-rsa signature so it recognizes the firmware as having been provided by a valid entity
2) update the encoded CRC/checksum so it can be validated.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 20:04:05 EDT

rcilink : Here is the link detailing the process..

»D-Link firmware 1.00.08 ... how to unlock it...

It involved a modded firmware that you load using web interface.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 20:01:39 EDT

GrauerFuchs : Excellent work. How did you manage to get around the firmware signature when you wrote it back to the PAP2?

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 19:59:15 EDT

rcilink : I've done some testing by changing "config.xml" to not look at CRYPT_KEY and ADMIN_PWD. It works, in my test, you can set the values yourself. A factory reset won't remove your assinged values..

Now, keep in mind that the orig ADMIN_PWD and other values remain... they are ignored with this modified firmware.

To see a similar project on a Dlink VTA, search the DSLR forums.. you will see details on the process.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 18:58:56 EDT

GrauerFuchs : Thank you, Velund. Unfortunately for us, not everyone on the forum has access to a JTAG kit or a machine capable of operating it. If we all did, I'm sure a complete solution would have been found by now. :)

Shall I assume this one is also a Vonage unit? The hash from the password on mine was AB784LJImQx4E

If so, then it confirms there are differences in the hard-coded Admin passwords in some units. Anyone else willing to put forward the hash they've been able to retrieve?

In addition, has anyone managed to acquire a PAP2v2-NA? I'm sure they exist somewhere, but I have yet to see one listed for sale anywhere.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 16:20:40 EDT

Velund :

said by GrauerFuchs :

Last information I had been given indicated that it, just like the factory encryption code, was different for each unit. Unfortunately, I do not have a bunch of PAP2v2s lying around to verify either way.

Hm. This forum have LOTS of such beasties... So just ask...

Mine have following hash in BL: ABteXK6Meukfw

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 14:03:07 EDT

GrauerFuchs :

said by mazilo :

If you use a JTAG to dump the whole Flash, doesn't bootloader area also get dumped?

Yes, the bootloader would be dumped if I backed up the whole flash memory.

IIRC, the factory default Admin password for a Linksys PAP2v2 is the same for each version of PAP2v2.

This is the first I've heard of it. Last information I had been given indicated that it, just like the factory encryption code, was different for each unit. Unfortunately, I do not have a bunch of PAP2v2s lying around to verify either way. Assuming that is the case, it makes that part of the job far easier. I still do prefer the thought of removing the HASH_KEY (path) and removing or changing the encryption key. That way, an accident won't result in a company getting their hands on the device by way of their usual provisioning.

So far, I've had no luck in getting around the firmware signature. Do we have any crypto gurus here that might be able to lend some advice?

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sun, 06 Jan 2008 08:42:34 EDT

mazilo :

said by GrauerFuchs :

I didn't include the Admin password because that is (1) in the bootloader code,

If you use a JTAG to dump the whole Flash, doesn't bootloader area also get dumped?

...and (2) different for each PAP2v2.

IIRC, the factory default Admin password for a Linksys PAP2v2 is the same for each version of PAP2v2.

The point I made on changing the factory default Admin, instead of admin, password is because it is the Admin password that is the key into its VM. A PAP2v2 whose VM isn't accessible is similar to a nicely designed brick. OTOH, there is no need to waste time to mess around with the factory default admin password because it is given/known.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 21:53:54 EDT

GrauerFuchs : I didn't include the Admin password because that is (1) in the bootloader code, and (2) different for each PAP2v2. ;) Of course, it is possible to update this by provisioning file, and removing this password entirely from the bootloader will cause it to accept blank passwords.

As far as the firmware is concerned, it is protected by an ssh-rsa signature in the last 149 bytes. Although the root filesystem is easy enough to edit, it will be a bit more difficult to get the machine to accept a hacked firmware.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 21:06:39 EDT

mazilo :

said by GrauerFuchs :

A few tidbits:
'admin' password: AB2ChJScbtR5I
'user' password: ABsFuZ3PufkXY
These may be encrypted.

They are not encrypted, but just some plain hashed keys, IIRC. Look for the Admin password hashed key instead of the above admin. Replace it with either this AB/PLgjMdnCMg (an empty hashed key password) or this ABW9wzpK6VV4Q (an Admin hashed key password -- yes, Admin is the password). Flash back this JTAG dump back to your PAP2v2 and you can access its VM with either a blank password or Admin as its password. Be sure to do this while your PAP2v2 isn't connected to a live Internet feed. Once you have done logging into your PAP2v2 with Admin account, go to the Provisioning menu to disable Provisioning enable option and then your PAP2v2 can be safely connected to a live Internet feed.
--
Mazilo
US Phone: +1-678-601-0907
UK Phone: +44-703-194-2574

Re: [General] The new PAP2 v2.0

Sat, 05 Jan 2008 21:00:29 EDT

Velund : Hm. I done something similar with my PAP2v2 just after Christmas (but not using EJTAG, just desoldered flash chip, put it on ARM-based prototype board with suitable pinout for flash and backed up/reprogrammed with J-Link there, then put it back). Seems a bit crazy, but I don't have any computers with parallel port handy, until I'll be back home. ;) Device programmer also far away from me now. Done only one such attempt, because PAP2v2 PCB doesn't seem too rugged.

Does not tried to erase cyt_private, just cleared environment vars, config areas and hardcoded variables in bootloader (except HWA). Then performed a factory reset.

Really, it does not relock anymore. It tries to get provision file, but cannot find it. Passwords reset to well known defaults.

The following problems was observed:

1. Serial console now is without password at all. Don't have SSH client installed right now to check what about dropbear. PAP does not allow to change higher level passwords, and if there is unchangeable Admin/Admin, forever..... I'd better turn it off.

2. 1.00.22 does not save any voice settings. Update page was accessible so I downgraded to .16 at once. It works somewhat better.

3. Problems with dialplan. Probably correct dialplan for sipnet.ru (with direct dial of numbers in Moscow) is silently rejected (simply not saved).
(sorry, tried to quote it here but forum scripts screw it up, replacing some chars)...

Some modifications of this string is accepted by PAP2v2 but cause crash of voice subsystem, so it continuously restart voice application. Put enough xxx to a dial plan field for a while. ;-) It's real XXX... ;-)

Not tested it very thorougly, maybe there is some more quirks... Don't know is it due to such brutal unlock or because Linksys simply not debugged and tested anything except remote provisioning on this model.

BTW: Got encrypted xml for my unit and tried to decrypt it using rc4 executable that was found in this forum and key that was found in bootloader. Not successful. Maybe I missed something...

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 20:27:17 EDT

GrauerFuchs : Okay, here we go. The common wrtp tools will not work on a PAP2 firmware, thanks to a different layout and size. Here are some of the important details:

Firmware analyzed: Vonage pt-11.4.0-r060426-1.00.13-r060426.img

squashfs-lzma filesystem begins at 0x0007C000 and ends 0x00328000.

If you're going to use dd to extract the root filesystem, use arguments skip=64 bs=8k count=342

The remaining Vonage details in /etc/config.xml can be easily altered once the filesystem is unpacked. You'll notice the provisioning server, a default user set, and more.
A few tidbits:
'admin' password: AB2ChJScbtR5I
'user' password: ABsFuZ3PufkXY
These may be encrypted. I haven't tested them yet.

This leaves only the broken voice tab in the web interface to correct.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 14:26:18 EDT

meister_sd :

said by DerGrauerFuchs :

Time to dig a little deeper...

Some stuff is hard coded in the firmware. Remember, this is Linux - so if you recompile your kernel with SquashFS w/LZMA support, you can mount the firmware, make changes and then load it back on your device. The SquashFS must me v1.3r3

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 08:45:10 EDT

mazilo :

said by DerGrauerFuchs :

Time to dig a little deeper...

And, don't forget to open a FREE account here. BTW, great job.

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 03:59:20 EDT

anon : This just in, a new report to fill the file of Egg on the Face.

This particular Vonage firmware has some of the provisioning details hard-coded into the default firmware image. This includes the DNS name of the Vonage provisioning server and Vonage DNS servers. A full reset of the machine, even after editing and/or CYT hack, will revert to Vonage details for the provisioning server. On a brighter note, removing the encryption key and the hash directory will still reduce chances of Vonage accessing your machine and making permanent alterations. It will not, however, prevent it from 'calling home' and trying to provision itself.

Time to dig a little deeper...

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 03:42:04 EDT

anon : It seems Vonage may have pulled a new one with the PAP2v2. Although the edit succeeded in permanently removing the password and all provider provisioning details, the page linked by the web interface still refers to 'contact your provider'. This must have been hard-coded into the software image itself. This means you either need to manually refer to pap2v2/Voice_adminPage.html to get access, or a patch will need to be produced for the firmware image to enable it by default. I may have a new project on my hands here, but at least it gives me something to do. ;)

Re: [General] The new PAP2 v2.0 - JTAG full unlock solution

Sat, 05 Jan 2008 01:46:56 EDT

anon : Okay, I just got to analyzing the software on a Vonage PAP2 v2.0 and was pleasantly surprised.

Data layout:
BOOTLDR B0000000-B0010000
BOOTENV B0010000-B0020000
IMAGE_A B0020000-B03F0000
CONFIG_A B03F0000-B0400000
IMAGE_B B0400000-B07D0000
CONFIG_B B07D0000-B07E0000
*??? B07E0000-B07F0000
CYT_PRIV B07F0000-B0800000

*: This segment contained no partition or data in my PAP2V2 (firmware 1.00.13)
To those that have toyed with a WRTP54G or an RTP300, you'll notice it's more or less the same layout. This means:

After backing up everything, erase the segments from B07E0000-B0800000, the configs, and the boot environment. You also want to edit the bootloader hard-coded environment variables starting at address C31A.
Most specifically, the HASH_DIR, CRYPT_KEY, and ADMIN_PWD variables are the troublesome ones. You'll need to move the HWA_0 and HWA_1 variables up to the top and fill the rest of that segment with FF if you do this.
Note: If you choose to add or edit any variables, they must end with a hex 00 for them to be recognized and valid.

With the segments erased and the modified bootloader code written back to flash, the box will no longer be locked and can no longer be re-locked by the provider.

JTAG software suggestion: Use the TJTAG software (derivative of wrt54g by HDM) version 4.8.2 or newer. The CPU and Spansion memory chips found in this device are supported in this software revision.
Although this software revision is not official as of this date, version 4.8.1 and the updated files can be found at the DD-WRT forums under the following thread.
»www.dd-wrt.com/phpBB2/viewtopic.php?t=22655
Update to tjtag.c is on page 6.

Re: PAP2 2.0 GPL code released

Fri, 04 Jan 2008 16:53:53 EDT

mazilo :

said by ogdensburg :

Maybe someone can hack it and port the PAP2 V1.0 firmware to PAP2 V2.0?

First of all, that GPLed code only contains the router module, i.e. no voice module code. Secondly, a PAP2v1 is based on an ESS chipset while its cousin PAP2v2 is based on a TI AR7 chipset. So, it probably will take a lot of efforts trying to port this code to a PAP2v1 although there may be some other code that has been ported to other ESS chipset.

PAP2 2.0 GPL code released

Fri, 04 Jan 2008 16:34:08 EDT

ogdensburg : Maybe it's a late news but I just found Linksys release PAP2 V2.0 GPL code. Maybe someone can hack it and port the PAP2 V1.0 firmware to PAP2 V2.0?

f t p://f t p .linksys.com/opensourcecode/pap2v2/1.00.13/pap2_v1.00.13.zip

Re: [General] The new PAP2 v2.0

Fri, 04 Jan 2008 11:45:29 EDT

yahoo2003 : Want to trade one of your ATAs with my JTAG cable? :)
WAnt to trade one of your ATAs with my serial cable? ;)

Re: [General] The new PAP2 v2.0

Fri, 04 Jan 2008 11:14:39 EDT

yahoo2003 :

said by floriantet :

said by yahoo2003 :

I dumped 8M flash

Did you use a Eprom programmer (which ? what adapter ?) or jtag (what program ?) ?
Please give a few details

Ha, you're the one bid on every ATAs I was looking at. :D
I used the simplest 14 pin passive JTAG shown in "wiki.openwrt.org" and this forum. Let me know if you can't find it. I like JTAGs, no programmers are needed.
BTW, I think I have enough ATAs for me now and I won't bid against you. ;)

Re: [General] The new PAP2 v2.0

Fri, 04 Jan 2008 10:43:21 EDT

floriantet :

said by yahoo2003 :

I dumped 8M flash

Did you use a Eprom programmer (which ? what adapter ?) or jtag (what program ?) ?
Please give a few details

Re: [General] The new PAP2 v2.0

Fri, 28 Dec 2007 10:48:00 EDT

yahoo2003 :

said by Velund :

Does anyone tried to make a physical dump of flash chip (using JTAG of device programmer)? What is contained in that secured data block?

I dumped 8M flash but I don't believe PAP2-V2's use the first 256 byte for ESN or password, they are store at higher locations. The first 64KB are used for boot loader.

said by Velund :

Does anyone succeeded in downgrading firmware without known user level password?

You can do it use JTAG.

Re: [General] The new PAP2 v2.0

Thu, 27 Dec 2007 21:32:26 EDT

anon : Hi mazilo,

Thanks a lot for your reply. I have not connected my pap2t to the internet till now and i can access the admin page so far.
So i guess my pap2t has no factory default lock and it is safe to plug and connect to the internet and use with any provider?

just wanna make sure there is no issue connecting it to internet before it's too late :)

thanks again!

Re: [General] The new PAP2 v2.0

Thu, 27 Dec 2007 15:51:21 EDT

mazilo :

said by indocan :

How would i know if my pap2t is unlocked version.

One way to find out if your PAP2T-NA is un/locked is as follows:

Customization

Open

admin

Re: [General] The new PAP2 v2.0

Thu, 27 Dec 2007 14:03:51 EDT

anon : Hi,

Just a quick question. How would i know if my pap2t is unlocked version. From what i read on forum is if it says pap2t-na it was sold is north america and if label says pap2t-as means it's sold in asia, 8-eu europe .....
before i plug my adapter to the internet i just wanna make sure it won't get locked and i can use with any provider.

Thanks a lot!

Re: [General] The new PAP2 v2.0

Thu, 27 Dec 2007 11:12:40 EDT

Velund : Just got PAP2v2 that was used with \/onage and already have 1.0.22 firmware. CYT does not work, not surprisingly.

Tried to dig deeper and looked into Spansion flash chip datasheet. Figured out that there is 256 byte permanently lockable area that can be used as a storage for ESN or other similar data.

Does anyone tried to make a physical dump of flash chip (using JTAG of device programmer)? What is contained in that secured data block?

Does anyone succeeded in downgrading firmware without known user level password?

Re: Password for PAP2T-NA???

Sat, 20 Oct 2007 14:02:31 EDT

DaveTap : can you plug in a phone and dial **** to get the configuration menu? I only know PAP2 and PAP2v2

Password for PAP2T-NA???

Fri, 12 Oct 2007 19:12:55 EDT

minimax : I was wondering if any of you experts can help me out with this issue:

I recently received a supposedly new PAP2T-NA. Unfortunately, I cannot get past the logon screen through the browser interface. The unit is password protected. I have tried all sorts of different combinations of admin and user passwords I found during my Google searches. I also came across posts how to reflash or reset the adapter, but they all were based on the premise that one was able to at least log in through the web browser as a regular user, which I cannot.

The unit may be pre-configured by yor.net (the packaging has a yor.net sticker on it). However their Tech Support was not able to find this unit (MAC address in their database). Contacting Linksys Tech support was not much help either…
Any idea how to reset or unlock this unit?

TIA!

Re: [General] The new PAP2 v2.0

Fri, 12 Oct 2007 16:59:37 EDT

floriantet :

said by meister_sd :

This seems for the PAP2, not the PAPV2

Ok I have asked him and he said it is about version 2 and he did not heard of CYT

he can't spell so I wouldn't trust his manual

:D I would have said that maybe his manual is with pictures, but you see he put the wrong picture (of PAP2 version 1 instead of PAP2 version 2)... Or is he confusing versions ? Or he does not understand questions ? Anyway if someone finds what it is about please let me know.

Re: [General] The new PAP2 v2.0

Fri, 12 Oct 2007 11:42:24 EDT

meister_sd :

said by floriantet :

with latest 1.00.22 firmware.

This seems for the PAP2, not the PAPV2.

Besides, he can't spell so I wouldn't trust his manual.
Would U trust him with ur money?

Re: [General] The new PAP2 v2.0

Fri, 12 Oct 2007 10:57:54 EDT

floriantet : I am wondering if this guy
»cgi.ebay.com/ws/eBayISAPI.dll?Vi···73150961
is using a method different than the one found in this tread and if it really works with latest 1.00.22 firmware.
Anyone who used his services to inform us ?

Re: [General] The new PAP2 v2.0

Mon, 10 Sep 2007 08:37:35 EDT

mazilo :

said by PAP2 v2 :

I am not able to do any anything. Any idea ?

Can you perform a factory reset through the pinhole on the back of your PAP2v2? Remember, to unplug your device off from the Internet unless you want it to phone home to get provisioned by Vonage. If the factory reset can cure this problem, then you can try to use CYT to unlock it again provided your PAP2v2 still runs on an older firmware supprted by CYT.

Once you get your PAP2v2 re-unlocked, perhaps you can try this approach (for Linksys WRTP54G) by sn9 to completely remove Vonage off your PAP2v2.

Re: [General] The new PAP2 v2.0

Mon, 10 Sep 2007 05:30:51 EDT

anon : Power keeps resetting and so as a result my Network keeps disconnected and keeps acquiring IP address. I am not able to do any anything. Any idea ?

Re: [General] The new PAP2 v2.0

Fri, 31 Aug 2007 20:22:23 EDT

holiday : For those with the Admin password from the unencrypted provisioning file and firmware 1.00.22 (such as memorito has), you should be able to login with Admin/*your_encrypted_Password* at h**p://yourpap2v2ip/Provisioning.html. Case is important there. Once you successfully login you can then surf to h**p://yourPap2v2ip/Update.html and downgrade your firmware, or get to the other config pages like h**p://yourpap2v2ip/Voice_adminPage.html, and so on.

I found that once I have the settings I like I can re-upgrade the firmware, but once at the 1.00.22 level the web gui is not fully usable for provisioning anymore. For example the gui will not seem save the passwords (for line one or line two) if I change them, as evidenced by turning debug mode on and watching the pap2v2 log information into the remote syslog. Also Neither cyt46, nor cyt39c work when the pap2v2 gets upped to version 1.00.22 firmware.

--
Holiday

Re: [General] The new PAP2 v2.0

Sun, 26 Aug 2007 14:44:31 EDT

marksmith888 : I have the same problem. It just gets stuck on "Simple XML provision server is waiting for your device..." Also, I cannot login with the user account to downgrade firmware. Any suggestions?

Re: [General] The new PAP2 v2.0

Mon, 20 Aug 2007 00:11:54 EDT

anon : hello! i just got a pap2v2 that came with the newest firmware: 1.00.22. i cannot get it to unlock. i use the cyt programs cersion 4.6 and 3.5 without luck.

i did a factory reset, have the windows (vista) firewall off and only the pap2 hooked up to the network adapter.

PLEASE anybody, can you help me?

also: does anybody know the new user password so i could enable ssh access and maybe try it from there? THANK YOU

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 14:04:30 EDT

anon : I should have clarified, but I want the area code automatically prepended when I dial 10 digits on the handset. The dial plan above has a 10 digit sequence, but is only good if the provider prepends it. I used to be able to put [2-9]xxxxxxS0 and I could dial local numbers without putting "1919" before all the numbers.

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 14:01:50 EDT

TJ_in_IL : Not sure I follow, Instigator

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 13:59:56 EDT

mazilo :

said by InstigatorX :

Anyone got a 10 digit dialing plan working with the *NEW* PAP2?

This is what the dialplan of my Uniden UIP1869V looks like:

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 13:41:59 EDT

anon : Got the new PAP2 working with SIPPhone, but the more traditional dial plans don't work. Adding "S0" or cause the whole unit to not work. "()" at the beginning/end also cause the unit to not function correctly (e.g. register, ring, etc). Here's what I *know* works...

*xxT|*1xx|[349]11|1xxx[2-9]xxxxxx|[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T

Anyone got a 10 digit dialing plan working with the *NEW* PAP2?

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 11:20:33 EDT

TJ_in_IL : My first suggestion would be to go back on this thread and read the posts. There is a good deal of information available, and the specifics depend on your setup and firmware version.

TJ
--
TeleBlend- Your Local Broadband Phone Company????

Re: [General] The new PAP2 v2.0

Fri, 17 Aug 2007 04:13:09 EDT

anon : I just got a PAP2 v2 1.00.22. I logged in to the web interface as admin/admin, ran the CYT 4.6, It just sits there doing nothing... :(

Re: [General] The new PAP2 v2.0

Sun, 05 Aug 2007 14:43:10 EDT

toro : Thanks again. That worked.

Re: [General] The new PAP2 v2.0

Sun, 05 Aug 2007 13:56:23 EDT

TJ_in_IL :

said by toro :

Thanks, I was able to unlock it with the version 3.5.
Also is there a way to save the initial path and decryption key for the Fonage config ? On the VTA-VR (which uses a very similar configuration) it used to show the values on the web interface. I noticed the PAP2 v2 doesn't.

From what I have read:
goto the web interface and login.
then goto {ATA IP}/Provision.html.
(Use the IP address of the ATA. Make sure you use a capitol P, otherwise it won't work).
Right click on a blank white part of the screen, and click on 'View Source'. This will open a notepad page.
Save the notepad page. Towards the bottom should be the key.

Also, from what I have read, as long as the SIP Provision address is set for 127.0.0.1 it will not connect to Fonage for update. As long as you do not do a Factory Reset. Even then, the CYT program still will be able to unlock and change admin passwords.

TJ

Re: [General] The new PAP2 v2.0

Sun, 05 Aug 2007 13:21:11 EDT

toro : Thanks, I was able to unlock it with the version 3.5.
Also is there a way to save the initial path and decryption key for the Fonage config ? On the VTA-VR (which uses a very similar configuration) it used to show the values on the web interface. I noticed the PAP2 v2 doesn't.

Re: [General] The new PAP2 v2.0

Sun, 05 Aug 2007 07:13:33 EDT

TJ_in_IL :

said by toro :

I just got a PAP2 v2.0 with firmware 1.00.16. I logged in to the web interface as admin/admin, ran the CYT unocker, pointed it to the right IP (option 3) and then ran option 1 to unlock. It just sits there doing nothing. I tried CYT 3.9 and 4.6.
Does it work only for firmware version 1.00.13 ?

Should work with 16. If you read the previous pages, I believe some may have had problems with 22, and had to run CYT3.5.
I originaly had 1.00.13 and pushed the upgrade to 1.00.16 thinking it would solve my problems (incoming calls). I was able to use CYT4.6 no problem with 16.
It does take a while to run the reset. Power cycle the ATA, confirm your IP address, and run again.
You do need to be logged into the Web Portal on the ATA, and make sure to shut down any firewall program.

TJ

Re: [General] The new PAP2 v2.0

Sat, 04 Aug 2007 20:48:56 EDT

toro : I just got a PAP2 v2.0 with firmware 1.00.16. I logged in to the web interface as admin/admin, ran the CYT unocker, pointed it to the right IP (option 3) and then ran option 1 to unlock. It just sits there doing nothing. I tried CYT 3.9 and 4.6.
Does it work only for firmware version 1.00.13 ?

Re: [General] The new PAP2 v2.0

Thu, 02 Aug 2007 15:19:48 EDT

TJ_in_IL : Is this thread or any work on the PAP2v2 pretty much dead?
Judging by the last post date, there has not been any intrest in the pap2.

Am I better off finding another device then?

TJ

Re: [General] The new PAP2 v2.0

Sun, 24 Jun 2007 11:33:31 EDT

qingz : Upgraded to 1.0.22. Did a factory reset. Now I can not use cyt_39c to unlock it. cyt_39c does not work on fw1.0.22.

CIA home phone on this version

Mon, 18 Jun 2007 12:31:19 EDT

anon : I've been trying to get CIA home phone to work on this without and sucess. Can anyone offer suggestions? This is what I can for the status:

Registration Status : 8076240344 8076240344 Proceeding

After upgrading to firmware .22 I get no detailed information in the provision voice system log:

2002:9:8:12:4
2002:9:8:12:4
2002:9:8:12:4
2002:9:8:12:4
2002:9:8:12:4
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:5
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:6
2002:9:8:12:7
2002:9:8:12:7
2002:9:8:12:7
2002:9:8:12:7
2002:9:8:12:7
2002:9:8:12:7
2002:9:8:12:8
2002:9:8:12:8
2002:9:8:12:8
2002:9:8:12:8
2002:9:8:12:8

Re: [General] The new PAP2 v2.0

Mon, 11 Jun 2007 10:36:44 EDT

memorito :

said by mazilo You will first need to unlock your PAP2v2 to access its voice module. [/BQUOTE :

Oh boy...
I have done all of this. But the provisioning gets Parsing errors. I have unlocked my pap2v2. Several times actually.

Hearing people say that they "never let the box connect to the internet" confuses me. CYT doesn't work on the new firmware and when the box is factory reset the passwords we get from decrypting the XML files don't work. So it either has to be provisioned be Vonage in order to enter the voice section or I have to find the "Master" password from Linksys which I never heard of anyone having...

This whole problem is because I upgraded to 1.00.22 firmware by letting vonage provision it. But, I want to find a way to make it work, because I guarantee the voice quality has improved.

So, any ideas? I am willing to experiment as the box is now useless really.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 11 Jun 2007 07:08:09 EDT

mazilo :

said by memorito :

And how can you use the box if it has
never connected to vonage?

You will first need to unlock your PAP2v2 to access its voice module.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Mon, 11 Jun 2007 02:09:35 EDT

memorito : Ok are you all using the .22 firmware?
And how can you use the box if it has
never connected to vonage?

Don't you need that so you can figure
out the passwords?

I am getting more confused as time passes.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Fri, 01 Jun 2007 01:22:47 EDT

memorito : Ok. Soooo. This thing repeatedly downloads
the xml file and then does nothing with it.
How can I spoof the original dns thing?
I searched for the info but couldn't figure
it out. I tried SimpleDNS; it is anything but.
Couldn't make heads or tails of it.

Would it be better to just download the old
13 firmware from linksys and downgrade to that?
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 28 May 2007 10:49:34 EDT

dthompso99 : perhaps your encryption key is wrong? im not excatly sure what the error is when the key isnt right, as i've never let mine connect to vonage.

Re: [General] The new PAP2 v2.0

Thu, 24 May 2007 13:52:36 EDT

AndrewZ : Try another tftp server. I use tftpd32.
Try to make the file smaller, just remove all the information (or sections) except the very beginning of the file and line1/2 auth. details.

Re: [General] The new PAP2 v2.0

Thu, 24 May 2007 11:27:36 EDT

memorito : Andrew,

Thank you for the file. I made the changes
and it did not take. So, I went ahead and
uploaded it exactly as you sent it.
Got the parsing error again...
I really don't understand what is wrong
with this thing. It does it Perfectly
from the vonage server. Is it perhaps
being transferred in the wrong format?
The TFTP Desktop program says Octet, Send.
Does that sound correct?
What else can I try...
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Wed, 23 May 2007 05:08:31 EDT

memorito : I sent it through the email thingy.
When I tried it in the IM it got
all deformed.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Wed, 23 May 2007 04:59:34 EDT

AndrewZ : As I sad before - just send me a file, I'll check.

Re: [General] The new PAP2 v2.0

Wed, 23 May 2007 03:18:30 EDT

memorito :

said by AndrewZ :

said by memorito :

OK, everyone left me behind. Heheheh.
What I did was use the original xml
file and just plugged in my values.

This is exactly what I did.
I'm using UltraEdit. Are you using Notepad? Try wordpad for example and don't save in MS-DOS format.

Ok. I tried doing the whole thing over again.
Even downloaded the UltraEdit program to make sure...
Still the same error. Could it be one of the entries I
changed cannot be changed due to some hardwired thing and
it is causing a conflict?
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Wed, 23 May 2007 02:52:13 EDT

AndrewZ :

said by memorito :

OK, everyone left me behind. Heheheh.
What I did was use the original xml
file and just plugged in my values.

This is exactly what I did.
I'm using UltraEdit. Are you using Notepad? Try wordpad for example and don't save in MS-DOS format.

Re: [General] The new PAP2 v2.0

Wed, 23 May 2007 01:49:33 EDT

memorito : OK, everyone left me behind. Heheheh.
What I did was use the original xml
file and just plugged in my values.
Now every time I send it to the box
it says Error Parsing the file.
But, I only changed the entries in there...
I didn't write up a new one like you guys can.
What could be causing this?
I am thinking maybe the format of the file is
being corrupted somewhere along the way...
Like when I edit it... Maybe my text editor
is changing something... Or do I have to
recrypt the file? I dunno. Not sure what
I am doing wrong. :o/
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 21 May 2007 17:27:24 EDT

JayMan : That same thing works with the DLINK VTA. As soon as I left one with the IP and the other line with a domain name Line 2 doesn't disconnect anymore.
--
COME ON OVER TO THE NEW »TekSavvy FORUM

Re: [General] The new PAP2 v2.0

Mon, 21 May 2007 17:22:49 EDT

dthompso99 : Now for my new kick.... Has anyone had any luck figureing out the filesystem of the firmware, and managed to mount it... love to make a few modifications ;-)

I'd think about just loading openwrt on it, however... the tai drivers i think may be a huge issue =P

Re: [General] The new PAP2 v2.0

Mon, 21 May 2007 10:06:44 EDT

AndrewZ : Probably you put something wrong into the file ;)
You may PM it to me (w/o passwords), I can check.

Re: [General] The new PAP2 v2.0

Mon, 21 May 2007 09:13:37 EDT

memorito : OK, so I finally got the file to the box.
Now the status page tells me

Provisioning Status : Provisioned:Error parsing provision file

Anyone have a clue why?
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Sun, 20 May 2007 21:10:10 EDT

dthompso99 :

No tricks on PAP2. Just added insecure = invite in Asterisk.

Bingo, that was it... that and nat=route, and itw working like a champ.

fyi, for anyone else setting these up for asterisk, this is what i came up with in sip.conf:

[91]
context=default
host=dynamic
type=friend
mailbox=99
callerid="House Line 1" <91>
username=91
secret=1234
rfc2833compensate = yes
nat=route
dtmfmode=rfc2833
insecure=port,invite

As far as sending the xml to the device. you'll need to start up a tftp server, and point the settings in Provision.html to your server. There are several in depth walkthoughs in these forums on how to accomplish that part. (i think also in the cty tutorial)

I didnt need to use CTY on version 22 of firmware, as it was allready unlocked from version 13.

Re: [General] The new PAP2 v2.0

Sun, 20 May 2007 05:46:05 EDT

memorito : Ok. I am completely lost.
I don't know how to send the xml
file to my box. And did the cyt
work for you guys?
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Fri, 18 May 2007 15:37:27 EDT

AndrewZ :

said by dthompso99 :

I'll have to take that back... inbound ringing is not working =/ back to the drawing board....

Now I have both lines working in both directions.

No tricks on PAP2. Just added insecure = invite in Asterisk.

It will be interesting to see how it's done in Vonage.
Can anybody post the setting from the provisioned device?
I would like to see CID_NAME, CID_NUMBER and AUTH_USER_NAME for both ports. If you want to hide anything please do it the same way on both ports.

Re: [General] The new PAP2 v2.0

Thu, 17 May 2007 12:04:58 EDT

dthompso99 : Yea, that is only complete for the voice_config, which is the bulk of things. I havent found a similar source for the system settings such as time zone, ip address, provision settings, etc..

Re: [General] The new PAP2 v2.0

Thu, 17 May 2007 08:28:00 EDT

AndrewZ : Thanks a lot. There are some parameters in that file which I missed before. At the same time it's not complete - for example timezone is missing.

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 20:51:28 EDT

dthompso99 : I'll have to take that back... inbound ringing is not working =/ back to the drawing board....

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 19:56:53 EDT

dthompso99 : ok, attached is the "almost" full provision file. Most of these settings are default, as i did a full reset to get things working.

everything inside the voice_xml tags is taken from:

/var/tmp/voice_config

Ploping it inside of the provision tags seems to work, so i belive those are all valid settings for the device.

full provision.zip 21,226 bytes
pap2v2 1.00.22 provision
(full provision.xml)

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 19:47:31 EDT

dthompso99 : one sec, and i'll get you all the paramaters... and where i found them at...

the line 1 line 2 problem... i had a similar problem. the fix that actually worked for me was to use a dns address pointed at the same machine, which is cake if your running your own dns server... a little more complicated if not.

Why that worked... i couldnt really tell you, since asterisk still translates it to the same address.

Now... one sec while i dig out those provisoning settings...

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 17:15:17 EDT

AndrewZ : I'm looking for either .xml provisioning file parameter or CLI command to change Preferred CODEC located in WEB interface, LineX, Voice Coding Profile.

This field cannot be changed through the WEB interface, at least with the current software version.

There are 2 small glitches - FXS Ren and Impedance fields are empty and cannot be saved through the WEB as well. It will be good to know how to change and save (!) those settings.

Does anybody have the complete list of parameters available for provisioning ?

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 16:57:03 EDT

AndrewZ : dthompso99, thank you!

This is the current status of my research.

The problem I described persists until Line2 is disabled.

That was the case for me, as soon as I used only Line1 before. So if you want to use just a single line then it should be Line2.
Having both lines enabled/provisioned/registered is looking good, until you're trying to call (at least with Asterisk). The problem that SIP source port is configurable on a per-box level, not per-line, so then I have 2 extensions registered with the same IP:port my Asterisk gets confused and no calls are possible.

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 16:38:40 EDT

dthompso99 :

Provisioning Status :  Provisioned      
GR909 Status #1: PASS    
GR909 Status #2: PASS
 
Registration Status :  91 91 Done      
Call1 Status : idle    
Call2 Status : idle
 
Registration Status :  92 92 Done      
Call1 Status : idle    
Call2 Status : idle

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 13:16:15 EDT

AndrewZ : Could you please post the relevant part of your Status screen

Provisioning Status : Provisioned 
GR909 Status #1: PASS 
GR909 Status #2: PASS

My problem with the absence of dialtone has no relation to RTP at all, as soon as it's generated locally.

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 10:29:22 EDT

dthompso99 : Hasnt been an issue yet (only been running one day so far).. I did have to do a factory reset, then appy the provision file above to make it behave properly with ringing and all.

If your getting ring, cid, etc... port 5060 is working fine, but i would double check that your rtp ports match that of your asterisk server (I did need to change mine). All of the voice stuff runs over those ports.

I "think" i've noticed a slight improvement in voice quality with this firmware... its a little soon to tell tho, i havent had a good ip-ip conversation yet.

Re: [General] The new PAP2 v2.0

Wed, 16 May 2007 06:08:56 EDT

AndrewZ :

said by dthompso99 :

I've got mine up and running smooth on the 1.0.22 firmware to my asterisk server...

That's really interesting. Do you have any problems with GR909 stuff ? I've been unable to use the new firmware with my Asterisk server as I mentioned on the previous page.

Re: [General] The new PAP2 v2.0

Tue, 15 May 2007 22:40:51 EDT

dthompso99 : oops... and the versions someone was looking for

# cat /etc/versions
VERSION=11.4.1
BUILD=070309
ODMVERSION=1.00.22
ODMBUILD=070309
BOARD=CYT_PAP2
FSSTAMP=20070309174532
model_name=PAP2 Ver.2
fw_version=1.00.22
patch_desc=Release DEV_GGMRGW_11_04_01_010.PATCH_07 RGW Telogy Software

Re: [General] The new PAP2 v2.0

Tue, 15 May 2007 22:32:42 EDT

dthompso99 : I've got mine up and running smooth on the 1.0.22 firmware to my asterisk server... the gui config is fubar, so you'll need to configure it via provisioning.

Had some difficulty getting it to link up with both channels at once (authorization errors). What wound up actually working was using a different dns address (to the same host) for line1 and 2.

# cat /proc/ticfg/env
BUILD_OPS       0x441
bootloaderVersion       1.3.8.1602.3.8
HWRevision      1.01.04
max_try 4
IMAGE_A 0x90020000,0x903f0000
CONFIG_A        0x903f0000,0x90400000
IMAGE_B 0x90400000,0x907d0000
CONFIG_B        0x907d0000,0x907e0000
BOOTCFG_A       m:f:"IMAGE_A"
BOOTCFG_B       m:f:"IMAGE_B"
HW_COMPANDING   linear
FSX_FSR 16
TELE_IF INTERNAL
BOOTLOADER      0x90000000,0x90010000
save_voice_config       yes
DSP_CLK 12288000:10
boot_env        0xb0010000,0xb0020000
cyt_private     0xb07f0000,0xb0800000
TELE_ID VE882XX:AUTO
WIFI_LED_GPIO   13
WIFI_LED_RATE   50
IPA_GATEWAY     192.168.1.254
SUBNET_MASK     255.255.255.0
MAC_PORT        0
MEMSZ   0x01000000
FLASHSZ 0x00800000
MODETTY0        115200,n,8,1,hw
CPUFREQ 162500000
SYSFREQ 125000000
PROMPT  (psbl)
IPA     192.168.15.1
RESET_CAUSE     0
ProductID       CYPL
CONSOLE_STATE   locked
SerialNumber    CH911xxxxx
HASH_DIR        4rsdWxxxxx
CRYPT_KEY       EA36D833C94D06403F3B4C982672FA72960BF4F7C56918106Axxxxxxxxx
ADMIN_PWD       xxxxxxxxxxxx
HWA_0   00:18:39:6C:xx:xx
HWA_1   00:18:39:6C:xx:xx
BOOTCFG m:f:"IMAGE_A"

and my provisioning file, if its any help to anyone... digit map needs a little work, but other than that good.


        
                
        
        
                pt-11.4.1-r070309-1.00.22-r070309.img
                tftp://192.168.0.200:69,21,2400
                tftp://192.168.0.200:69,21,2400
                
                pap2v2
                1
                120
                time.windows.com
                192.168.0.1
                
                notice
                
                
                Admin
                admin
                1
                5
                1
                35
                
                        
                                1
                                House Line 1
                                91
                                91
                                1234
                                dev.xxxx.com
                                5060
                                dev.xxxx.com
                                5060
                                *xxT|*1xx|[349]11|1xxx[2-9]xxxxxx|[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T
                        
                        
                                1
                                Cordless
                                92
                                92
                                1234
                                xxxx.com
                                5060
                                xxxx.com
                                5060
                                *xxT|*1xx|[349]11|1xxx[2-9]xxxxxx|[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T
                        
                        
                        
                        
                                
                                
                                
                                
                                0
                                5060
                                5060
                                8000
                                8800

Also, in the question a few posts up regarding the phone ringing, but no voice... pay special attention to the RTP_PORT_START stuff.

Re: [General] The new PAP2 v2.0

Fri, 11 May 2007 07:17:05 EDT

mazilo : The Diagnostics folder should be located under the Administrator menu. In this folder, there should be a ping and traceroute options. Select the ping option and a window will pop-up where you can enter an IP address to ping. Since ping is a Un*x command that usually runs on a shell, it is possible to execute several command(s) concurrently in one line on the same shell by appending && in between two commands. Thus, the ping hack is all about. For instance, under the ping popped up window, you can replace an IP Address with 0.0.0.0 && cat /proc/ticfg/env to let these two commands to be executed concurrently. The popped up window will eventually be filled with the information returned by the cat /proc/ticfg/env if the system supports for a full ping command. From this, you can find out a lot of information (including the encryption key) on your PAP2v2 that some of them can be modified through this ping hack, too. I am not sure if the listed encryption key is the factory default one or not.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Thu, 10 May 2007 23:50:50 EDT

memorito :

said by mazilo :

...Diagnostics menu where you can try the infamous ping hack, i.e. 0.0.0.0 && cat /proc/ticfg/env (on the ping pop-up menu), and see what if it will return the factory default encryption key.

No clue what that means.
Where can I get a clue? heheheh
I looked up ping hack but I couldn't
understand most of what google returned.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Thu, 10 May 2007 08:19:36 EDT

mazilo :

said by memorito :

Is there some way I can browse the internals of this thing?

IIRC, the older version firmware has a GUI looks like a WRTP54G. If so, then there must be a Diagnostics menu where you can try the infamous ping hack, i.e. 0.0.0.0 && cat /proc/ticfg/env (on the ping pop-up menu), and see what if it will return the factory default encryption key.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Thu, 10 May 2007 03:44:13 EDT

memorito : Is there some way I can browse the internals of this thing?
The encryption key no longer works on the tiMAC.xml file, btw.
Dunno where to investigate more.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Wed, 09 May 2007 07:52:32 EDT

rcilink :

said by memorito :

rcilink, I haven't been able to find the version.txt page.
Could you tell me what the full link would be? While your at it could you list out the pages available in the adapter?

the version.txt is (was) found as a link to a file in /etc on the device (named 'versions')

This file details information about the actual firmware, including build timestamps, revision number and more.

It appears that the security has been changed to dis-allow access (error: outside directory tree), so it wont work now.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 23:20:50 EDT

memorito : Well, I logged in to the Admin with the "Default" password that was there previously.

Everything looks the same...

Andrew, sorry that it didn't work. Are the lines on different providers? Did you try changing the actual phone cords? It is line quality testing after all...

rcilink, I haven't been able to find the version.txt page.
Could you tell me what the full link would be? While your at it could you list out the pages available in the adapter?
Thanks.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 15:00:21 EDT

AndrewZ : No Vonage, just home Asterisk server. Everything was OK (with 36 days uptime) before the upgrade.
Just did a factory reset, will see.

Does not help. Will have to downgrade.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 14:48:57 EDT

memorito : Are you with Vonage?
Then call them up.
See what th problem is.
When you get to customer service don't try
to easily explain what is wrong. Just tell
them the very complicated version so they
send you to Advanced technical support as in
non-script readers... Their whole outsourced
thing is atrocious. They don't train them
very well.
Were you having any line problems before the upgrade?
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 12:28:55 EDT

AndrewZ : upgraded to 1.0.22

GR909 Status #1: PASS
GR909 Status #2: NA2 -- is it a problem?

But this is a real problem for me - it cannot detect off-hook condition anymore :(
When I'm trying to make a call - there is no dialtone.
When I'm receiving a call - phone is ringing, caller id is working, but there is no audio and I still hear ringing tones from the handset.
Registration, provisioning, etc are still fine.

Any idea?

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 01:43:41 EDT

memorito :

said by rcilink :

The GR909 stuff is talked about here: »www.legerity.com/press_room_detail.php?56

Line quality testing. Sweet.
I can honestly say that this
firmware upgrade made the audio
quality on my vonage line a LOT
better. I might even try to send
a fax now that I don't have constant
clicking on the calls...
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 01:29:59 EDT

rcilink :

said by memorito :

This is new...

Provisioning Status : Provisioned
GR909 Status #1: PASS
GR909 Status #2: PASS

The GR909 stuff is talked about here: »www.legerity.com/press_room_detail.php?56

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 01:13:35 EDT

memorito :

said by rcilink :

firmware filename is: pt-11.4.1-r070309-1.00.22-r070309.img

If you know where to look, you can download it for further study.

My 'firmware' development and testing box is currently offline (has a power supply problem). It will be back online soon.. Anyone else test this version?

Anything you would like me to try?
Don't know much about all this though.
Just what I read here.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Tue, 08 May 2007 01:04:28 EDT

rcilink : firmware filename is: pt-11.4.1-r070309-1.00.22-r070309.img

If you know where to look, you can download it for further study.

My 'firmware' development and testing box is currently offline (has a power supply problem). It will be back online soon.. Anyone else test this version?

Re: [General] The new PAP2 v2.0

Mon, 07 May 2007 16:21:25 EDT

memorito : This is new...

Provisioning Status : Provisioned
GR909 Status #1: PASS
GR909 Status #2: PASS

And it looks like CYT ain't werkin on it.

Sadness.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 07 May 2007 16:12:43 EDT

memorito : Ok!

Call Vonage and they will send you the 1.00.22 FW.
I am gonna do all the prelim testing...
Updates later.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 07 May 2007 15:04:53 EDT

memorito : I can't actually access that.
The box is not local and I don't have
the passwords.
--
T.N.S.L.P.P.T.S.O.

Re: [General] The new PAP2 v2.0

Mon, 07 May 2007 07:53:48 EDT

rcilink : can you load (from the web browser):

http://[ip of your pap2v2]/version.txt ?

it should tell you the new firmware filename.

please post the name here.. thanks!

Re: [General] The new PAP2 v2.0

Mon, 07 May 2007 05:47:57 EDT

memorito : Ok. So I am trying to get this thing working...
I thought you all might be interested in something
I found on the web...

New Firmware

At least I think it is. You tell me.
Look at the top right corner with the
tiny letters... hmmm...

Memo
--
T.N.S.L.P.P.T.S.O.

FW 1.00.22?

Re: [General] The new PAP2 v2.0

Tue, 01 May 2007 13:36:06 EDT

DogFace05 : Hardwarewise, the PAP2T is essentially identical to a PAP2v1, albeit with twice the amount of flash memory. In fact, it is to the PAP2v1 what the SPA2002 is to the SPA2000, and conversely to the SPA2002 what the PAP2v1 is to the SPA2000. These (PAP2v1/PAP2T/SPA200x) are all based on the ESS ES3890 (Visba3) chipset. The PAP2v2, on the other hand is based on the TI AR7 chipset, as stated by Mazilo, and is totally incompatible with the T model. Not only is the hardware totally different, their processors (ARM vs MIPS-X) and instruction sets are completely different and incompatible as well.

Re: [General] The new PAP2 v2.0

Tue, 01 May 2007 09:25:18 EDT

toro :

said by mazilo :

AFAIK, a PAP2v2 is based on a TI AR7 chipset. IIRC, a PAP2T is based on an ESS chipset (the same one used on a PAP2v1?)

Well, I ordered a PAP2T for the sake of finding out what hardware it is based on and how well it works. Will let you know once I receive it.

Re: [General] The new PAP2 v2.0

Tue, 01 May 2007 09:21:00 EDT

mazilo :

said by toro :

Arenn't they the same hardware ?

AFAIK, a PAP2v2 is based on a TI AR7 chipset. IIRC, a PAP2T is based on an ESS chipset (the same one used on a PAP2v1?). Thus, a PAP2T is not hardware compatible with a PAP2v1 and/or PAP2T.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Tue, 01 May 2007 07:50:06 EDT

toro :

said by DogFace05 :

No, there are several reasons why this isn't possible.

Actually I was referring whether the firmware available on the Linksys web site for PAP2T can be loaded on what is being referred as PAP2 v2 from fonage. Arenn't they the same hardware ?

Re: [General] The new PAP2 v2.0

Tue, 01 May 2007 01:06:01 EDT

DogFace05 : No, there are several reasons why this isn't possible. For one, the PAP2v1 and PAP2T firmwares use different incompatible image formats. The PAP2v1 won't recognize the latter's firmware and simply won't accept upgrading to it. There's no TFTP server on the PAP2s in either the main code or the boot loader (in fact, the boot loader has no communications capabilities whatsoever), so that's not an option for trying to trick it into taking the PAP2T's firmware. But most importantly, the PAP2T uses 2MB of flash vs the 1MB of the PAP2v1 and expects the full 2MB to be present. It won't run with just 1MB.

Re: [General] The new PAP2 v2.0

Mon, 30 Apr 2007 20:21:18 EDT

toro :

said by DogFace05 :

Yes, it has the same interface.

Can the firmware be loaded on a Fonage adapter (maybe with TFTP from the bootloader if the web interface doesn't allow it) ?

Re: [General] The new PAP2 v2.0

Mon, 30 Apr 2007 10:50:08 EDT

DogFace05 : Yes, it has the same interface.

Re: [General] The new PAP2 v2.0

Mon, 30 Apr 2007 09:05:22 EDT

toro : Looks like the Linksys web page has a version 5.1.3-LS for the PAP2T adapter.
This version numbering seems very different from the Vonage's firmware. Anybody knows whether this one has the PAP2 v1 interface (with STUN and all the good stuff) ?

Re: Unlocking the new PAP2 v2.0

Sat, 31 Mar 2007 18:37:21 EDT

anon : I would like to know if the PAP2 v.2 has a 100Mb fullduplex port. I have an old Linksys BEFSR41 V2. with the full and 10/100 lights. My current PAP2 v.1 shows up as only running at 10Mb and half duplex. If the PAP2 v.2 is 10/100Mb and full duplex then I may consider upgrading. I mostly want the full duplex version as I already know a phone call doesn;t even use anywhere near 10Mb. Can someone who owns a version 2.0 let me know what speed and duplex it operates at?

Re: [General] The new PAP2 v2.0

Wed, 21 Mar 2007 00:30:37 EDT

mazilo :

said by trafael1 :

Both my pap2v2 units are now locked and cannot be reset (reset pins in the back quit working). Also, CYT just sits there and doesn;t reset the boxes anymore. I had them working well with broadvoice and voipstunt but they would autodestruct once a week.
I would advise against purchasing those cursed units unless you enjoy hours of aggravation and useless tinkering.

Sorry to hear your bad experience on your PAP2v2. I am aware of this problem. Current firmware releases are pretty buggies and don't support STUN options. So, I have decided long ago to stow away my PAP2v2 until Linksys has released new firmware that supports STUN options
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Tue, 20 Mar 2007 23:28:11 EDT

trafael1 : Gave up on the POS. Both my pap2v2 units are now locked and cannot be reset (reset pins in the back quit working). Also, CYT just sits there and doesn;t reset the boxes anymore.
I had them working well with broadvoice and voipstunt but they would autodestruct once a week.
I would advise against purchasing those cursed units unless you enjoy hours of aggravation and useless tinkering.

Re: [General] The new PAP2 v2.0

Sun, 18 Mar 2007 22:15:20 EDT

sarathb8 : hey I downloaded the same...
any specific instructions on how to updateto 1.00.16?

Re: [General] The new PAP2 v2.0

Sun, 18 Mar 2007 22:08:45 EDT

sarathb8 : reply to VOIP234
hey can u share the instructions on how to update firware to v16 for pap2 v2 and from where I can download the same.. Any tricks...
Thanks
sarath

Re: [General] The new PAP2 v2.0

Sun, 18 Mar 2007 22:02:33 EDT

trafael1 : I am just about to give up on the pap2V2. About once a week it loses the capability to dial out (I get a fast busy signal after I dial the first digit) and I have to struggle for hours to reset it, sometimes successfully :) Interestingly at that point if I don't do anything the phone is still registering with the VOIP and i am able to receive incoming calls, but not dial out. Eventually that capability also disappears.

This unit is a major PITA. Is this the experience of everyone here? Is there any way to make this unit more stable and avoid those lockups?

Re: [General] The new PAP2 v2.0

Mon, 19 Feb 2007 19:49:31 EDT

anon : Hey - can you share which instructions you used to upgrade to firmware version 16?

Any major changes in version 16?

Thanks

Matt

Re: [General] The new PAP2 v2.0

Sun, 18 Feb 2007 13:27:48 EDT

indyqq0 : PAP2 V2 Setting for voipstunt/stanaphone, Line 2 ring on line 1.

1. Unlock: »www.bargainshare.com/index.php?s···ic=87504

2. Connect PAP2V2 to Router. Connect a phone to Line 1 and power on. Dial****, 110#, get IP (xxx.xxx.x.xxx).

3. »xxx.xxx.x.xxx (admin/admin). If you want to updata, go to:
»xxx.xxx.x.xxx/update.html (user/user)
»xxx.xxx.x.xxx/Provision.html (Admin/Admin)

4. »xxx.xxx.x.xxx/Voice_adminPage.html (Admin/Admin) and you will see the Voic Page.

5. Setup for Voipstunt (»www.voipstunt.com) (Line 1):

Caller ID Number: Put Line 2 Caller ID Number in here (When line 2 receive a call, it will ring on line 1).
Digit Map(Dial Plan): 1xxx[2-9]xxxxxx|00x.T

6. Setup for Stanaphone (»www.stanaphone.com) (Line 2):
Digit Map (Dial Plan): 08xxxxxx|1xxx[2-9]xxxxxx|00x.T

7. Make call:
US & Canada Call: 1+area code + number
International Call: 00+country code + area code + number

Re: [General] The new PAP2 v2.0

Wed, 14 Feb 2007 11:51:12 EDT

anon : Thank you for both answers. They were very helpful.
Yes, beginning the dial with 00 and ending with # worked for international numbers.

Best,

Giovanni

Re: [General] The new PAP2 v2.0

Wed, 14 Feb 2007 11:29:31 EDT

sumdum :

said by Giovanni :

My question is why my PAP2 v.2 does not give automatic IP to my PC. I have to configure manually my IP and the gateway (192.168.15.254). Otherwise I get a Limited Connection.

your pap2 v.2 is a phone adapter only device, it does not have built-in router functions like the wrtp54g/rtp300.

Re: [General] The new PAP2 v2.0

Wed, 14 Feb 2007 10:10:59 EDT

pram : there is also /Provision.html, for the international dialing, try hitting # after your last digit. For non US numbers, dialing should start with 00+countrycode+number+#

Re: [General] The new PAP2 v2.0

Wed, 14 Feb 2007 08:49:38 EDT

anon : After running Cyt39c, I could get the Voice configuration page typing »192.168.15.254/Voice_adminPage.html (Admin/Admin).
Is there any other config page that I can reach manually, like that one?
At this moment I am using VoipDiscount and I can make call to US and some other countries but I get a busy signal for most of the countries (including mine, Brazil).
My question is why my PAP2 v.2 does not give automatic IP to my PC. I have to configure manually my IP and the gateway (192.168.15.254). Otherwise I get a Limited Connection.
I would appreciate any help.

Re: [General] The new PAP2 v2.0

Sat, 10 Feb 2007 15:52:45 EDT

anon : I managed to unlock PAP2 V2 and update to latest firmware 16 with the help of this forum. However I still can not do the following:

Configure Speed dials
do ip dialing e.g 123@xxx.xxx.xxx.xx

Also after unlocking the web interface is messed up and the only way to access some pages is through putting web address (no way to do that through the menu).

any answers to the above is appreciated.

Sherif

Re: [General] The new PAP2 v2.0

Sat, 10 Feb 2007 15:06:56 EDT

trafael1 : My pap2V2 Firmware 1.00.16 was unlocked using CYT and it generally works fine.
Every few days though it gets messed up and i cannot dial out anymore
(incoming calls are fine): there is a normal dial tone, but when attempting to dial
I get a fast busy signal. I have to go then through resetting the entire
device (just using CYT again doesnt help)- it is a major pain.

in the voice logs I see the following :
[att=1]
Anyone has any idea how to fix this for good?

log.txt 3,534 bytes

Re: [General] The new PAP2 v2.0

Wed, 07 Feb 2007 12:37:35 EDT

floriantet : Has anyone discovered how to dial another user of the same provider if the username starts with/contains letters ? For example if I set voipsunt on my PAP2 v2 how do I call another voipstunt user ?
In case of old PAP2 version1 set with voipsunt I can put in dial plan (between >) 777:dan1009 and when I dial 777 the old PAP2 version1 calls dan1009@sip.voipsunt.com
For PAP2 v2 it does not work like that. Does anyone have a solution for dialing a known username containing letters ?

Re: [General] The new PAP2 v2.0

Tue, 30 Jan 2007 18:18:46 EDT

AndrewZ : It seems that PAP2v2 has strange rfc2833 implementation :mad:

See my post »Re: [Equipment] PAP2v2 (CYT Unlocked) With Asterisk PBX Talk

Re: [General] The new PAP2 v2.0

Mon, 29 Jan 2007 17:31:41 EDT

AndrewZ : Hello all
I've unlocked PAP2v2 and configured it to work with my home Asterisk server. But there is a problem...
Asterisk VoiceMail cannot recognize DTMF tones sent from PAP2, same problem with VTech ip8100.
At the same time Asterisk correctly passing tones from this PAP2 to external VM system through SIP trunk.

Any ideas?
Thanks!

Re: [General] The new PAP2 v2.0

Thu, 25 Jan 2007 02:13:20 EDT

trafael1 : I finally succeeded in locking myself out of hte device :)

First it got stuck into that idle state with no possibility of registering. Tried the reset button on the back and power cycle... no change.
tried to reset to default factory status on the web interface... no change... same old settings remained.

went to the restore voice default settings and since then it remained locked up. I tried using CYT to unlock but no go. reset button, power cycle.. nothing!

at some point it appears to have updated to v. 1.00.16.
I guess if noone comes up with some method of resetting it, back it goes to BB... what a major PITA!

EDIT: I was able to unlock it, not sure how... went through powercycling, button and web interface resetting and CYT about 100 times... it is finally unlocked again :)

Re: Beware!!! Vonage can screw up unlocked PAP2 V2

Tue, 23 Jan 2007 22:28:59 EDT

trafael1 :

said by bubamarkus :

I noticed another thing about PAP2 V2. If the device is power cycled after working for some time, it no longer connects to the SIP providers. The status page shows IDLE for both lines, but PAP is not connected to providers, and LEDs are no longer green. The device has to be reset and re-unlocked again.
Have anybody seen this?

It just happened to me too... did anyone find a more permanent solution to this nuissance?

said by mazilo :

Yup. Every now-and-then my PAP2v2 will go into an oblivion state. Power cycling my PAP2v2 solves the problem. No need to factory reset the PAP2v2.

Power cycling (I assume you mean cutting power supply off) doesn't work for my device.

Re: [General] The new PAP2 v2.0

Mon, 22 Jan 2007 14:51:29 EDT

cunyalen : Have you tried 1.00.16? How is it? Any better?

Re: [General] The new PAP2 v2.0

Mon, 22 Jan 2007 03:27:28 EDT

trafael1 : anyone set up Broadvoice with an unlocked V2.0 yet? I am still struggling with reading up on the different parameters.

i will most probably also have to call broadvoice since they have to register my new device I assume.

Re: [General] The new PAP2 v2.0

Sun, 14 Jan 2007 02:13:33 EDT

anon : Hi,

I have unlocked PAP2 ver 2, and i cannot configure FWD on this.

Can someone provide the settings for FWD on PAP2 ver 2?

Thanks in advance.

Cheers!!!!

Sanjay

Re: [General] The new PAP2 v2.0

Sat, 13 Jan 2007 20:21:54 EDT

cunyalen : What are the pages in www_safe?
Like bridge.html etc.

I still can't get it work with FWD. My pap2 is after a route. I have forwarded port 5060-5061 10000-20000 to the pap2. Here is the syslog:

SSMU: ---} Message Sent: Sent to Addr=69.90.155.70:5060, UDP
REGISTER sip:fwd.pulver.com;transport=UDP SIP/2.0
From: {sip:773271@fwd.pulver.com;transport=UDP};tag=101b4950-1000a8c0-2710-3d7b3c76-7033fe5-3d7b3c76
To: {sip:773271@fwd.pulver.com;transport=UDP}
Call-ID: 101bd4e0-1000a8c0-2710-3d7b3bd0-a73d6aa-3d7b3bd0
CSeq: 438 REGISTER
Via: SIP/2.0/UDP 192.168.0.16:10000;branch=z9hG4bK-3d7b3c76-29642ee3-4bbe610a
Max-Forwards: 70
Supported: replaces,timer,100rel
User-Agent: PAP2 Ver.2001839C7ED8E11.4.0-r060426-1.00.13-20060426185307 CYT
Contact: {sip:773271@192.168.0.16:10000;transport=UDP}
Expires: 60
Content-Length: 0

I have a dial tone, but cannot receive or make any calls.

Re: [General] The new PAP2 v2.0

Tue, 09 Jan 2007 14:59:58 EDT

jagiboy : Can someone please post settings to configure PAP2 V2 for vbuzzer? Also has anyone tried the new .16 firmware?.

Re: [General] The new PAP2 v2.0

Sun, 07 Jan 2007 09:55:34 EDT

bubamarkus : The firmaware is at HTTPCONFIG dot Vonage dot NET

Re: [General] The new PAP2 v2.0

Sat, 06 Jan 2007 23:15:08 EDT

mazilo :

said by rockzd :

However, it cannot work in my school's LAN although it has a IP address, and I can access the adminstration (line setup) page.

What kind of IP address does your school LAN assign to your PAP2? How is your PAP2 configured, i.e. NAT?
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Sat, 06 Jan 2007 19:47:34 EDT

rockzd : Help please!

I can set up my pap2 to work (using internetcalls or voipstunt) behind a router at home. However, it cannot work in my school's LAN although it has a IP address, and I can access the adminstration (line setup) page.

Any suggestions?

Re: [General] The new PAP2 v2.0

Fri, 05 Jan 2007 13:56:06 EDT

mazilo :

said by vjfromgt :

whooo-hoo whooo-hoo-hoo whooo--hoo-hoo is that Verizon? lol

Yup. When those commercials are online, I just LOL when observing my roomates looking at their PAP2 units running with FWD, VoIPUser, StanaPhone, SIPGate, SIPPhone, etc... and sing along with the following lyrics to enjoy the free ride with free PAP2 units:

quote:
;) whooo-hoo whooo-hoo-hoo ... Fonage Vucks Link sys ... We get free PAP2 ... ;) ;) whooo-hoo whooo-hoo-hoo ... Fonage Vucks Link sys ... We get free PAP2 ... ;) ;) whooo-hoo whooo-hoo-hoo ... Fonage Vucks Link sys ... We get free PAP2 ... ;)

BTW, if you want to be creative, you can mod the above lyrics to rhyme as follows:

quote:
;) whooo-hoo whooo-hoo-hoo ... With Rizzo's VuckFonage ... We get free PAP2 ;)
;) whooo-hoo whooo-hoo-hoo ... With Rizzo's VuckFonage ... We get free PAP2 ;)
;) whooo-hoo whooo-hoo-hoo ... With Rizzo's VuckFonage ... We get free PAP2 ;)

--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Fri, 05 Jan 2007 12:52:53 EDT

vjfromgt : whooo-hoo whooo-hoo-hoo whooo--hoo-hoo is that Verizon? lol

Re: [General] The new PAP2 v2.0

Fri, 05 Jan 2007 08:48:44 EDT

soufan5 : Has anybody tried the new firmware. Interested in knowing whether the bug related to "no support for alphanumeric characters in the user name field" is fixed in this version.

Is the GUI interface still the same or has made some improvements.

Re: [General] The new PAP2 v2.0

Fri, 05 Jan 2007 00:26:23 EDT

rcilink :

said by skypeuser :

I googled buy was unable to find the firmware.

We're not supposed to post direct links to firmware, so I did not post the link to it.

I can tell you this (and you can get it yourself):

•The firmware is on a site that the other PAP2v2 (1.00.13) firmware is on
•the company sells phone service for $24 or so
•whooo-hoo whooo-hoo-hoo whooo--hoo-hoo (something like that)

Re: [General] The new PAP2 v2.0

Thu, 04 Jan 2007 23:00:50 EDT

skypeuser : I googled buy was unable to find the firmware.
I will keep an eye on this thread hoping to find
this firmware. Thanks for your information that it
is available.
pt-11.4.0-r060628-1.00.16-r060628.img,
:D

Re: [General] The new PAP2 v2.0

Thu, 04 Jan 2007 22:09:37 EDT
rcilink : New firmware found!

PAP2 v2 was 1.00.13

now they push out: 1.00.16

filename is: pt-11.4.0-r060628-1.00.16-r060628.img

Re: [General] The new PAP2 v2.0

Sun, 31 Dec 2006 23:40:20 EDT
xeonox : i was wondering how to do this too? all i see is the type in box, but i dunno what to type in or how to use it.

Re: [General] The new PAP2 v2.0

Sun, 31 Dec 2006 11:43:27 EDT
indyqq0 : The new PAP2 V2.0 do not have Speed Dial Table (User 1/2). Who know where to set speed dial?

Re: [General] The new PAP2 v2.0

Thu, 21 Dec 2006 20:05:55 EDT
anon : How do you select codecs on the PAP2 v2.0? I need to change it to G729a to get it to work with voxee again.

Re: [General] The new PAP2 v2.0

Wed, 20 Dec 2006 21:30:21 EDT
cunyalen : With FWD, what about the proxy server and registry server? I tried it with CID number as FWD number but I didn't succeed.

What's your dial plan? I think if dial plan is no good, we cannot make calls, but we can receive calls. right? I can't receive calls.

Re: [General] The new PAP2 v2.0

Fri, 15 Dec 2006 01:19:35 EDT
xeonox : thanks ill just change anything that say vonage to "http://127.0.0.1"

thanks for the reply, i leanred some things.

Re: [General] The new PAP2 v2.0

Fri, 15 Dec 2006 00:04:50 EDT
rcilink :
said by xeonox :

Yes the provisioning page says something about "tftp.vonage.blah.blah.blah". Is that bad?

Hopefully, you see:
http://127.0.0.1

just above the line where you saw tftp.vonage.blah.blah..

Bad? well, if the device is showing vonage and not 127.0.0.1, then it is being told to connect to vonage and download provision info to replace the settings you put in.

IVR (on the provision page) can be set to on or off. If set to on, you can plug in a phone and dial certain numbers to use voice menus to set some of the options of the device (IP address, etc.)

Re: [General] The new PAP2 v2.0

Thu, 14 Dec 2006 23:46:54 EDT
xeonox : well i dont know, its not getting provisioning but it seems to work fine, i can still make outgoing calls, i havent tried incoming only cuz i dont know my number yet, lol.

Yes the provisioning page says something about "tftp.vonage.blah.blah.blah". Is that bad?

And what does "IVR" mean on the provisioning page?

Re: [General] The new PAP2 v2.0

Thu, 14 Dec 2006 22:43:20 EDT
rcilink : Yes, it should work with Voipbuster. As for the provision being reset, what is your device pointed to in "provision server"?

Also, CYT46 is out. Link: »CYT Device: Unlocking Information

You might experiment with the Customize XML option (after setting IP of device (option 3 on menu)..

Voipstunt, voipbuster, sipdiscount... all the same config.

FYI: D-link released a new firmware (stamped 11-27-06) that breaks the current CYT versions. Perhaps Linksys will have a firmware release that does the same? If this is the case, you can always block *.vonage.net at your firewall..

Re: [General] The new PAP2 v2.0

Thu, 14 Dec 2006 14:47:12 EDT
xeonox : running cyt_3.9c has anyone gotten the Pap2 ver2 to work with VOIPBUSTER? i keep loosning provisioning.

Re: [General] The new PAP2 v2.0

Wed, 15 Nov 2006 17:33:21 EDT
thaychuari : I am in the same situation. Please help.

Re: [General] The new PAP2 v2.0

Wed, 15 Nov 2006 14:12:29 EDT
MACD : Here is my situation. I have unlocked my PAP2 V2 device using the CYT utility, i also have the provision xml file decrypted. Now can anyone outline the steps to successfully configure FWD with PAP2 V2, as we all know it does not have STUN and proxy support, so what is the workaround. Someone had mentioned that he was successful by tweaking the provision file, can you tell me what changes are required to make it work. Thanks in advance.

Re: [General] The new PAP2 v2.0

Thu, 02 Nov 2006 17:26:20 EDT
DogFace05 : I can't foretell what improvements may be made in future versions of the PAP2v2 firmware, nor progresses with its unlocking. But currently the best bet for a device to use with other services than V*nage is the v1, as the v2 is difficult to configure reliably and apparently has a knack for relocking unexpectedly. The PAP2v1 on the other hand can be unlocked completely and even -NAized, and fairly easily be set up with most providers who support BYOD service. However, if you plan to use a v1 with V*nage, make sure that you buy a brand new one, and not one that has been previously used, as V*nage do not reactivate ATAs that have already been tied to previous owners's accounts.

Re: [General] The new PAP2 v2.0

Thu, 02 Nov 2006 08:55:21 EDT
mazilo :
said by hdlz :

... so any suggestions on which one I should use for Vonage service, v1 or v2?
There has been some talks here about completely removing Vonage from a PAP2v1/RT31P2 for a fee, I reckon it will be to your best interest to use a PAP2v1.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Wed, 01 Nov 2006 22:52:19 EDT
hdlz : I have an unlocked PAP2 v1 and just picked up a PAP2 v2, will try to unlock it as well.

My question is I plan to use Vonage, so after saving the factory fresh GPP_K, I will choose one of them to connect to Vonage. I want the option that I can re-unlock the PAP2 later if I ever decide to dump Vonage's service. I plan to use one pap2 for Vonage, one remains unlocked and use other VoIP service, so any suggestions on which one I should use for Vonage service, v1 or v2? Considering that I want the option to be able to later unlock Vonage veteran and I have Original GPP_K value saved?

DTMF

Fri, 06 Oct 2006 22:47:01 EDT
anon : I can't get DTMF to work on my device, any suggestions? I am with viatalk

PAP2 v2.0

Re: unexpected (again!) but nice, call to line 2 rings on line1

Fri, 06 Oct 2006 21:29:25 EDT
pram : phew, no spooky stuff here
found the magic.., follow the links to the vta-vr thread in the above post.

unexpected (again!) but nice, call to line 2 rings on line1

Fri, 06 Oct 2006 11:15:21 EDT
pram : check for background details here.. »[General] DLink VTA-VR

provisioned my pap2 v2 with the same xml, hey, same results.., calls to freedigits(line2) lands on line1 but cant dial out of line2. (use at your own risk)
something must be spooky with the xml that I got..

Re: [General] The new PAP2 v2.0

Thu, 28 Sep 2006 01:44:00 EDT
hoolahoous : mazilo... thanks !!! you got the exact cause .. and I was thinking the problem was on pap2 side.. now it is working like one legged champ.. (didn't dare to use second line, no big loss since the remote location won't be using second line anyways)
you really know your voip... :)

Re: [General] The new PAP2 v2.0

Tue, 26 Sep 2006 23:40:37 EDT
mazilo :
said by hoolahoous :

I have been trying very hard to make my pap2 v2 connect to my asterisk. it works fine inside the same network, however when I take it out side firewall and behind another fireless(and use dyndns name) it doesn't register.
Let me guess: Both your asterisk and PAP2 are connected behind a NAT/Firewall router and are on the same private LAN, right? When you configured your PAP2 for asterisk on the same (private) LAN, it is like configuring a PAP2 with a public IP address to register to an asterisk on a public LAN, i.e. you will need to comment the line NAT = yes on the extension used to register your PAP2. When you moved your PAP2 from a private LAN to a public LAN and/or another private LAN, the configuration on your asterisk (extension used to register your PAP2) has to be changed. I'm not an asterisk expert; however, in this case, I believe you will need to include NAT = yes for the extension used by your PAP2 because your PAP2 is no longer connected to the same private LAN with the asterisk.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)

Re: [General] The new PAP2 v2.0

Tue, 26 Sep 2006 11:15:41 EDT
hoolahoous : I have been trying very hard to make my pap2 v2 connect to my asterisk. it works fine inside the same network, however when I take it out side firewall and behind another fireless(and use dyndns name) it doesn't register.
i tried playing with proxy server/registrar server in both line1 tab and sip tab. Anyone got it working ? I was wondering since it can register to other voip providers, why not asterisk ? does it send registration info in some format which asterisk doe not understand but other voip providers do ?

Re: [General] The new PAP2 v2.0

Sun, 24 Sep 2006 14:19:43 EDT
meister_sd :
said by ctylor :

If you guys have figured out how to unlock I might pick one up if the deal ever improves, but I do have one main problem: if the device lacks STUN and STUN/NAT compensating settings, how is this going to be useful to us with routers?

Unless you get a great deal like the one Best Buy was giving - it still is a better idea to buy a -NA model of any type of ATA. I suspect though it's just a matter of time before an update comes out that offers the STUN support.