[Vonage] SIP credentials, RTP300, GPP_K?
Links: home · search · speed test · login · more ·
 
Links: Reply New Topic
Forums » Voice Over IP - VOIP » Vonage » [Vonage] SIP credentials, RTP300, GPP_K?
page: 1 · 2 · 3 · 4 ...18 · 19 · 20
anon @ 7th Apr 09:45AM:
[Vonage] SIP credentials, RTP300, GPP_K?

I've heard that it's possible to extract Vonage SIP credentials from some RTP300s using methods discovered on another site (we wouldn't want Vonage to know who or where!), but the extracted config information I saw from an RTP300 didn't include any kind of GPP_K or other encryption key, as the PAP2s did. If I were to extract all this configuration info from my RTP300, is there any way I could find the encryption key so as to download my actual config file with VuckFonage and decrypt it?
reply
ptrowski @ 7th Apr 09:50AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The credentials were not there? I watched someone do it with the instructions I gave him and they were there...Hmmmm
--
Make a Difference-Join Team Helix!
reply
anon @ 7th Apr 10:03AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The SIP credentials were there. I just couldn't find any kind of key that would allow me to download config files and decrypt them.
reply
ptrowski @ 7th Apr 10:05AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Ahh, my misunderstanding.
reply
rcilink @ 7th Apr 10:54AM:
Re: [Vonage] Getting the encryption key for RTP300 & WRTP54G

Yes. Here's how to get the encryption key for your VOICE_XML file.

Experiment with this, and it will work out.

1. Disable javascript. If you dont, the page will redirect to a different page. Some have reported hitting ESC repeatedly to stop this from happening-- it is hard to time this one!

2. Hook your PC into the RTP300 or WRT54GP2 LAN port. Your pc will get an IP address of 192.168.15.100.

3. Open a web browser and point to »192.168.15.1

4. Login to the device. Default is admin for username and password.

5. Point your browser to: »192.168.15.1/cgi-bin/webcm?getpa···ion.html

6. If you did not turn off JAVA, you got redirected. The page you want to see is attached.. Keep trying. Load the page, hit escape key.. Eventually it will show up. I find this works well when using an old 400MHz PC..

7. Once the page is visable, it appears blank. Right-click on it and click view source.

8. Scroll down towards the bottom of the source.. Look for entries like this:
<!-- Provisioning -->
.
.(removed.. redundant info)
.
<!--new-->
<input type="hidden" name="provision:settings/intervalimg" value="3600" id="uiPostProvisionIntImg">
<input type="hidden" name="provision:status/profileurl" value="tftp://ti.tftp.vonage.net:69,21,2400" id="uiPostProvisionProfileDef" disabled>
<input type="hidden" name="provision:status/imageurl" value="tftp://ti.tftp.vonage.net:69,21,2400" id="uiPostProvisionImageDef" disabled>
 
<input type="hidden" name="provision:status/path" value="pexxxxxxx2" id="uiPostProvisionPathDef" disabled>
<input type="hidden" name="provision:status/key" value="6C04A7A8F44FC354435AAAAAAAAAAxxxxxxxxF1AC5A065F8EEE91CF7F23CD4DA" id="uiPostProvisionKeyDef" disabled>
<input type="hidden" name="provision:status/interval" value="1" id="uiPostProvisionIntDef" disabled>
<!--new-->
<input type="hidden" name="provision:status/intervalimg" value="60" id="uiPostProvisionIntImgDef" disabled>
 
<input type="hidden" name="provision:settings/dns1" value="4.4.4.4" id="uiPostProvisionDNS1">
<input type="hidden" name="provision:settings/dns2" value="4.4.4.5" id="uiPostProvisionDNS2">
 
<input type="hidden" name="provision:status/last" value="Not provisioned" id="uiPostProvisionStatus" disabled>
 
<input type="hidden" name="provision:settings/VOICE_XML/PORT_1_CONFIG/CID_NAME" value="LINE_1" id="uiPostProvisionCID">

Your Provision key is listed in there. The tftp address and folder location for your file is also listed there.

filename is ti00000000.xml (replace 0's with MAC addy)
Click for full size
reply
meister_sd @ 7th Apr 02:32PM:
Re: [Vonage] Getting the encryption key for RTP300 & WRTP54G

This is what I've been looking for! Thanks alot! I'll try this when I get home tonight.

Have you had any luck in getting a serial console working? I've seen some tutorials on openwrt, but I haven't heard from anyone here who actually did it. I have the settings on HyperTerm to 115000 8-N-1 and Control to "None".
reply
rcilink @ 7th Apr 04:25PM:
Re: [Vonage] Getting the encryption key for RTP300 & WRTP54G

The serial console is set to a 'login' prompt, so you cant get into it unless you have the password.

If you have the root password, why not just use ssh and connect that way?

Here's where I'm at with this device..
I have it registered and working with Asterisk... I have not gotten the provision portion working though. In addition, I would like to get the shell password, so I can get into the Linux filesystem.

I have the GPL source for 1.00.60 firmware for this device. (can be downloaded from Linksys).

In the firmware, under /usr/bin, look at the cm_ files.
# ls
 
[@           cm_logic*    cm_reset*  foxy*  passwd@       traceroute@  whoami@
cm_config*   cm_monitor*  cut@       free@  pppoe-relay*  tty@         yes@
cm_convert*  cm_msg*      dbgcmd@    id@    test@         upgrade*
cm_klogd*    cm_pc*       env@       nmm*   tftp@         wget*

The cm_config is one of interest. Since this device is not i386 based, it needs an emulator to run.
# file cm_config
 
cm_config:  ELF 32-bit LSB MIPS-I executable, MIPS, version 1 (SYSV), 
            dynamically linked (uses shared libs), stripped

So, if you have a MIPS version 1 emulator for linux, you can most likely run that config program and make a new XML to unlock your box completely, using the encrypt key it wants to see.

reply
meister_sd @ 8th Apr 08:49PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Well, I tried the above hack to get to the provisioning page. The first thing is you have to have v1.0.60. I had .37 and didn't work. The next thing is I was able to download my encrypted .xml file but when I tried to decrypt it using the method for the PAP2 I got a "bad magic number". When I looked at openssl it says there are other ways to encrypt/decrypt. Anyone decrypted their file?

openssl aes-256-cbc -d -in ti00xxxxxxxxxx.xml -out cleartext.xml -k AB82DD541xxxxxxxxxxAA622E9FC6F43EAE48FDF93D1F4E789DFA93005C2D8AA

I did see that there were two provisioning folders each with their own key and I've tried them both with the same error.

Now the first part of my encrypted pap2 file is:
Salted__Á[¯G€Šæt°>ìb"§¿ÞChaš>ÕéÝ;J!

Now this says "Salted" in the beginning, but on my rtp300 xml file this is what I get:
‡g f¹eœ_E4€ÔÒ±öÞuÞû

No salted...... Any ideas?
reply
meister_sd @ 8th Apr 10:18PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I just created a batch file to try to decrypt the file using all the commands in openssl, 52 of them. All came up with "bad magic number" or a syntax error. So maybe they are using their own encryption? I can give anyone the files I have if they want to check my work or try another path. Just PM me.
reply
rizzo2dial @ 8th Apr 10:30PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by meister_sd :

Now the first part of my encrypted pap2 file is:
Salted__Á[¯G€Šæt°>ìb"§¿ÞChaš>ÕéÝ;J!

Now this says "Salted" in the beginning, but on my rtp300 xml file this is what I get:
‡g f¹eœ_E4€ÔÒ±öÞuÞû

No salted...... Any ideas?
Peppered? :D

The "salted" config file simply means that in addition to encrypting the file using the "GPP_K equivalent" passphrase, a random SALT value is inserted into the encrypted file immediately after the "salted__" keyword. The GPP_K passphrase in conjunction w/ the random SALT value are then used to build the actual encryption/decryption KEY needed to encrypt/decrypt the file. This is how Vonage is able to encrypt the same plain-text XML over and over such that each produced ENCRYPTED file is unique (at least for the PAP2).

If the encrypted file isn't salted, and if it's encrypted with the same "GPP_K equivalent" passphrase, so long as no changes have been made to the plain-text file, the resulting encrypted file will be the same every time.

Rizzo
reply
meister_sd @ 8th Apr 11:21PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Excellent explination. Thanks.

Any ideas how it is encrypted and how to decrypt it? As shown above, I do have the passphrase. Everything rcilink I have been able to duplicate just as described. Now the decrypting of the XML file is all that is left.
reply
rizzo2dial @ 9th Apr 05:18AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Perhaps the file is encrypted using a different encryption scheme. When you execute the command:
quote:
openssl aes-256-cbc -d -in ti00xxxxxxxxxx.xml -out cleartext.xml -k AB82DD541xxxxxxxxxxAA622E9FC6F43EAE48FDF93D1F4E789DFA93005C2D8AA


"aes-256-cbc" is the encryption scheme you're instructing openssl to use. openssl supports numerous encryption schemes (google the openssl docs), so perhaps try some other schemes. Try writing a script / batch file to go through all possible schemes offered by openssl. ;)

Rizzo
reply
meister_sd @ 9th Apr 12:58PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rizzo2dial :

Try writing a script / batch file to go through all possible schemes offered by openssl. ;)

Rizzo
That is what I did in the post about 4 messages up. I got the same error. I'll try to attach the file.

One thing I did last night was to use the same hack from rcilink, look at my values, make changes in the screen and click save. It worked! After reloading my page, even unplugging the router and relogging back in, my chages were there. I then went to all the screens that are in the voice folder and used the same delay/esc trick to get copies of all the files in there so I can change the routers settings. The user screen, provisioning and everything can be changed. Just one screen voiceAuthenticate.html is a problem. This screen is where you can change the "Admin" (big admin). It will let me change but when I save it an error about being outside the html path occurs.

The good thing is I can make changes. I'm going to print the screens of all the voice pages and fill in what I need from my working PAP2 so I can insert all the correct info. We'll see if this will work.

One other thing I tried is in the Provision.html, I removed my encryption key, which worked, but then I tried to give it an unencrypted file. For some reason my tftp server would send but time out sending it. It seems the rtp300 will ask but not transfer it.

I also found this:
»www.profiber.dk/media/router_opdatering.pdf
This talks about an rtp300 with firmware 3.1.10 including screen shots of the voice screens. Anyone seen this? I tried to get the .bin file but no luck. The IP in the example and the IP of the host of the file come from the same place. That is as far as I got. Anyone have a rtp300-na? What is the firmware version for that model?
batch.zip 584 bytes
reply
anon @ 9th Apr 08:14PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I'm quite sure the algorithm is rc4 and it is a raw key. I'm not sure if the whole string is the key or if there is an initialization vector.
reply
anon @ 9th Apr 09:36PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Ok, openssl won't decrypt it but »www.uqtr.ca/~delisle/Crypto/codes/rc4/rc4.c does it nicely.
reply
anon @ 9th Apr 09:39PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Oh, I can't test it, but rc4 is a stream cypher so you can use the same program to reencrypt it with the same key, then you should be able to feed it to the router.
reply
meister_sd @ 10th Apr 03:16AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I didn't have any luck with the RC4.

I did try changing the values in user1 but my screen doesn't populate the saved values so I have to enter them all in again. If I don't, during the save it will enter nothing for the values - erasing the old ones.

So now my problem is that there is a timeout of about 10 minutes (??) so not everything was written. I am using IE6 with normal settings. I will try to open two IE screens, populate one and let the other screen re-register the timeout.

The other thing I see is even with these settings changed, a factory reset won't clear my changes and replace them with the old Vonage info!
reply
rcilink @ 10th Apr 10:43AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I did not have much luck with the RC4 either. It takes the key and xml file. The output is not plaintext, so I can not do much with it... Anyone get this working?

------------------
Some observations about changing data in the other Voice pages:

IF you want to setup a SIP service, use the ESC trick and look at voiceLine1.html (Link: »192.168.15.1/cgi-bin/webcm?getpa···ne1.html )

Before changing the info in there, make sure you 'view source' and pay attention to the values stored at the bottom of the page. Since it can't fill-in the fields (the javascript is not enabled, or it was stopped using ESC), you need to plug-in all fields, and set all settings prior to hitting the 'SAVE' button!

I found that an easier way to do this is to save the source to the voiceLine1.html and modify it locally to have the correct data in it. Then, when I run it locally, it can use java, and show the 'defaults' I pre-set on my page.

Two more steps to make the local page load and save correctly:

1. Find this:
function uiDoOnLoad(){
var user= "ROUTER";
if(user != "ADMIN"){
...and change it to:
function uiDoOnLoad(){
var user= "ADMIN";
if(user != "ADMIN"){

2. Find this:
<!-- Post Form -->
<form method="POST" action="webcm" target="_self" id="Line1PostForm"
 onsubmit="jslDoOnSubmit()">
...and change it to:
<!-- Post Form -->
<form method="POST" action="http://192.168.15.1/webcm" target="_self" 
id="Line1PostForm" onsubmit="jslDoOnSubmit()">

As for the provisioning stuff... Some observations:

1. If I set the "KEY" to blank (nothing in there), it complains in the syslog. (syslog link: »192.168.15.1/cgi-bin/webcm?getpa···_vo.html ) The device wants a key that is divisible by 2!

2. If you mess with putting a plain-text file, a modified config.xml from the source code, and feed it to the box, it will appear to be receiving the file, but it then goes to vonage and re-gets the XML file from vonage! Once this happens, it is a pain to undo the SIP settings. For example, Vonage puts 666 in the dialplan. Even if you change the dialplan, it keeps sending the 666! The solution: you must do this:
1. Let the box read the vonage .xml file
2. Go to this link: »192.168.15.1/cgi-bin/webcm?getpa···Def.html (This is where to restore factory defaults for voice)
3. Select 'restore voice defaults' (not router).
4. unplug your device from the Internet!
5. username = user password = tivonpw
6. Voice will reset- and the dialplan will be clean.
7. Change the TFTP settings in the Provision.html page to prevent it from going back to vonage settings.

Best of luck with the box!
reply
meister_sd @ 10th Apr 10:58AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rcilink :

I did not have much luck with the RC4 either. It takes the key and xml file. The output is not plaintext, so I can not do much with it... Anyone get this working?
I have my XML file and key from my Provision.html I can give you.

said by rcilink :

Two more steps to make the local page load and save correctly:
I will try this later today.

said by rcilink :

Best of luck with the box!
Thanks! And I think I have another bit of luck. I found the file I was looking for in the PDF from my post above rtp300-3.1.10.bin. Inside the file name is said to be rt-11.1.1-r060214-3.1.10-r060214.img. I tried to load it into my router and got an image error (forgot the exact message). Anyone want to try it? Maybe it is something along the lines of needing to create an spa-tools to make some changes like with the PAP2 and the Sipura software?!?!?!
reply
rcilink @ 10th Apr 11:08AM:
Made my own provision file

I decided to get creative and make a provision file to try..

I took a plaintext XML file that had all the params setup for line1 and line2 and used the RC4 tool to 'encrypt' with a 6-byte key.

I then placed this file on my server and spoon-fed it by changing the provision settings on the Provision.html page.

Outcome: it blew-away my settings, and resorted to vonage!! argh!

Here is a snip of the syslog code.. [sanitized]
Starting wget 'http://myserver.com/prov/ti0013abcdefaa.xml' 
'-nv' '--failover' '-O' '/var/tmp/provision.xml' 
Report 'start' 'prov_xml' '(null)'! 
Report 'all' 'prov_xml' '14:55:22 URL:http://myserver.com/prov/ti0013abcdefaa.xml 
[11192/11192] -} "/var/tmp/provision.xml" [1] '! 
provisioning xml: 14:55:22 URL:http://myserver.com/prov/ti0013abcdefaa.xml 
[11192/11192] -} "/var/tmp/provision.xml" [1] 
Report 'exit' 'prov_xml' '0'! 
*** Checksum of the file = EE3F3F65, previous = (null) 
*** Decrypting provision XML file! 
*** Parsing provision XML file! prov_state = 2, 
image_state = 0 
Error parsing XML provisioning file from directory 'prov',
 trying the default location
Starting wget 'tftp://ti.tftp.vonage.net:69,21,2400/xyzxyz/ti0013abcdefaa.xml'
 '-nv' '--failover' '-O' '/var/tmp/provision.xml'

reply
meister_sd @ 10th Apr 11:58AM:
Re: Made my own provision file

I'm bringing my box to work to try some stuff. But I'm still on a box right now that won't let me load any file into it until I do the reset you told me to try. But what I was thinking is (1) Are we sure the file is RC4 from Vonage, and (2) I am going to put my own key into Provision.html and use that same key to encrypt a file and let it get uploaded to my box since you said there was an error in syslog about NOT having a key. I'll make one up.

I'll put the .bin file on rapidshare.de later today.
reply
anon @ 10th Apr 01:00PM:
Re: Made my own provision file

Are you using the right key? I downloaded the provision file with the default (as opposed to current) path and decrypted it with the default key. The result was a plaintext XML file.
reply
rcilink @ 10th Apr 01:25PM:
Re: Provision XML decrypting is not working for me...

Please correct the following steps, as this is not working for me.

1. download the ti001300000.xml file from ti.tftp.vonage.net. (Using the 'default' subdirectory defined in the Provision.html)

2. download rc4.c and compile it (mine is compiled on linux)

3. extract key from Provision.html in source view.

4. decrypt .xml file as follows:
# rc4 ABCABC-BIG-LONG-KEY-ABCABC outfile.xml

When I do these steps, the 'outfile.xml' is the same size as the ti001300000.xml file. It is not readable and it is not the same as the ti00130.. file.

So, if you would be kind enough to share what step we are missing, I know I would appreciate it.

Thanks!
reply
meister_sd @ 10th Apr 01:36PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Here is the bin file:

»rapidshare.de/files/17661517/rtp···bin.html
reply
anon @ 10th Apr 02:31PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

$ tftp ti.tftp.vonage.net
tftp> bin
tftp> get /<default path>/ti<mac>.xml
Received 12152 bytes in 10.9 seconds
tftp> q
$ mv ti<mac>.xml ti<mac>.xml.crypt
$ ./rc4 <256bit default key> < ti<mac>.xml.crypt > ti<mac>.xml

The first few lines look like:
 
<provision version="2">
<options>
        <reconfig/>
</options>
<settings>
 
<firmware>+XXXXXXXXXXXX/rt-11.1.0-r021-1.00.62-r060327.img</firmware>
 
        <profileurl>tftp://ti.tftp.vonage.net:69,21,2400</profileurl>
        <imageurl>http://httpconfig.vonage.net</imageurl>
 
        <tftp>ti.tftp.vonage.net</tftp>
        <tftpimg>ti.tftp.vonage.net</tftpimg>
        <tftpports>69,21,2400</tftpports>

reply
mazilo @ 10th Apr 02:37PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by czyc :

+XXXXXXXXXXXX/rt-11.1.0-r021-1.00.62-r060327.img
Remember the above firmware version. This was the latest/current released by Vonage before this hacking begins. After the new firmwares are released, this hacking may and/or may no longer works!
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
meister_sd @ 10th Apr 02:54PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by czyc :

The first few lines look like:

Would you post your file here? Scrub it if you'd like by putting x's so we know what goes where.
reply
anon @ 10th Apr 02:55PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Crap, i left my mac above. Any moderator around who can possibly remove it?
reply
rcilink @ 10th Apr 03:14PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

OK, I am going to have to try the 'reset button' option, cuz this thing is not getting back to factory fresh or something.. ARGH.

I just tried again, and it lets me download a file, but it is different from the file you got. It is 6598 bytes. I tried using the key listed for the thing, and it won't open it up.

BTW, if you register here, you have the edit/delete option to fix your posting..
reply
meister_sd @ 10th Apr 03:21PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

That is what happend to me. After the factory voice reset, I got entirely new keys so I am sticking with the facreset file/keys and leaving it off the net until I can decrypt mine also.

Anyone look at getting the bin uploaded to their rtp?
reply
mazilo @ 10th Apr 03:22PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by czyc :

Crap, i left my mac above. Any moderator around who can possibly remove it?
Don't worry, this has been taken care by the mod.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
mazilo @ 10th Apr 03:25PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by meister_sd :

That is what happend to me. After the factory voice reset, I got entirely new keys so I am sticking with the facreset file/keys and leaving it off the net until I can decrypt mine also.
Remember, this is your device's factory default encryption key and be sure to keep a copy of it. Do do like some people who didn't bother to do so after unlocking their PAP2s.

Anyone look at getting the bin uploaded to their rtp?
I have an expired Rapid share account. When I clicked to the link you provided, I got a message to ask me to renew my account. Anyway, I wondered what is the .bin file you had uploaded to Rapid Share site? Is it an RTP300 firmware? If so, why the version is 3.1.10?
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
meister_sd @ 10th Apr 03:32PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by mazilo :

Anyway, I wondered what is the .bin file you had uploaded to Rapid Share site? Is it an RTP300 firmware? If so, why the version is 3.1.10?
This is what I was wondering. I found a reference on Google on provisioning your own rtp300 and the screen shots show a different firmware loaded. I'm thinking this is the true -na version. Here is where I got it.

»www.profiber.dk/media/router_opdatering.pdf

Take a look and you will see other screens that we don't have access to - that's why I think it's a true -na. Does anyone have a true -na to verify their version number?

If you want me to email it to you, it's just over 5 meg. PM me your email address and I'll send it.
reply
czyc @ 10th Apr 03:32PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mod: thank you

said by rcilink :

OK, I am going to have to try the 'reset button' option, cuz this thing is not getting back to factory fresh or something.. ARGH.

I just tried again, and it lets me download a file, but it is different from the file you got. It is 6598 bytes. I tried using the key listed for the thing, and it won't open it up.

BTW, if you register here, you have the edit/delete option to fix your posting..
Yeah, that'll teach me to be lazy.
reply
mazilo @ 10th Apr 03:42PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by meister_sd :

Take a look and you will see other screens that we don't have access to - that's why I think it's a true -na. Does anyone have a true -na to verify their version number?
I don't see much of differences between my unlocked WRTP54G and the pages you had shown through the link, except my WRTP54G will still show the nasty message when I clicked the Voice menu. I hope you will also find the WRTP54G-NA firmware.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
meister_sd @ 10th Apr 03:51PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

So, along with Line 1 and Line 2 you have User 1 and User 2, along with the basic view and advanced view?
reply
czyc @ 11th Apr 02:21AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by meister_sd :

said by czyc :

The first few lines look like:

Would you post your file here? Scrub it if you'd like by putting x's so we know what goes where.
I hope I censored everything that needed to be.
tigeneric.xml.gz 2,803 bytes
reply
rcilink @ 11th Apr 12:33AM:
I downloaded the firmware listed here and...

Found that it would not load on my device!

Not leaving it alone, I peaked inside to see the difference between my other firmwares..

I found the size was off, and the 'code' in the header did not allow my device to load this firmware. Then it was a matter of checksum fixing.

I guess I should have realized that this firmware was for the rtp300, not the wrtp54g! I figured it would work.. just not provide wireless capabilities. That is what it did.. It shut-off the wireless part.

Now I need to find this release for the WRTp54G and fix it up.. looks like a very nice release of firmware!

My wrtp54g is now running firmware version 3.1.10!
It still works like the router/firmware, but also looks like the PAP2 for the voice part!

So, I will patch the header of this firmware back to the rtp300 unit, and let others try it.. It completely unlocks the voice part.

Anyone have a rtp300 and want to try this?
Click for full size
reply
IPA @ 11th Apr 12:38AM:
Oops...

Nevermind :D
reply
rcilink @ 11th Apr 12:45AM:
RTP300 firmware update RTP300-3-1-10.bin

Here's the firmware update. It has the corrected filesize (padded with FF's) and re-checksum'd so it will work.

This firmware will load up your RTP300 unit with the latest in voice firmware (3.1.10) unlocked..

When you click on 'VOICE', you get the Voice menu, not a "contact your service provider"..

This one will only load on a RTP300 unit. I have tested it on a WRTP54G unit by modifying the hardware ID in the firmware, and it works!
reply
anon @ 11th Apr 01:25AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

I tried it on my rtp300 it won't take it :-(
reply
anon @ 11th Apr 01:33AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Sorry I forgot the tell what happend
It shows
FirmWare Upgrade failed due to the following reason:
Invalid Code Patttern
reply
rcilink @ 11th Apr 01:44AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Here's the fix. CYLL is in there.. try for RTP300 unit

It is version 3.1.10 firmware.
reply
anon @ 11th Apr 01:55AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

It shows CYLL@

Hope this help
reply
anon @ 11th Apr 02:00AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

I changed the CYLM to CYLL then it let me upload the firmware but after finished upload then shows Upload failed
Status Invalid CRC
reply
rcilink @ 11th Apr 02:02AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

yeah, use the one i posted- it has the fixed CRC with CYLL in it. Sorry about that.
reply
meister_sd @ 11th Apr 02:14AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

RCILINK!! You are the man! Mine has been upgraded! Our long day has finally paid off!!!!

Now my fear is how the prices will increase on ebay.
reply
anon @ 11th Apr 02:24AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

This works find to upgrade to 3.1.10 but the Voice and Provision Page all different then before, I think this still don't have dailplane like PAP2 has. I will put it on my main router to test.

Thanks rcilink
reply
meister_sd @ 11th Apr 02:42AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have replaced my router with the rtp300 and I'm writing from you now with it in place. It works great so far. One think to remember: TURN JAVASCRIPTING BACK ON! heheee

I also used my settings from the PAP2, including the dial plan, and made a test call and that worked too.

I'll keep doing some testing and let everyone know how it goes but so far so good.
reply
anon @ 11th Apr 03:58AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

rcilink Thanks again, I apologize about the dialplan, it works as PAP2

rcilink can you point me how to do CRC check on the firmware image?

Thank you a lot
reply
ptrowski @ 11th Apr 08:04AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Nice job rcilink, glad to see it all paid off. ;)
--
Make a Difference-Join Team Helix!
reply
rcilink @ 11th Apr 08:25AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

The trick with this device:

1. the firmware is GPL (source code is available for most of it)

2. the thing uses a TI ARM7 CPU

3. there are freely available TI ARM7 tools (toolchains, and other fun things to calculate checksums)

4. the firmware is actually a "squashfs" filesystem. This means it is possible to 'mount' the filesystem and modify as needed. Then re-build the squashfs filesystem and flash your device.

---

For this job, the existing firmware recently posted here needed some simple fixes. The router was complaining about the file type being incorrect, incorrect size, and the checksum being incorrect. After getting all these things fixed-up, it loaded up!

Too bad I don't have a RTP300! I have the WRTP54G. That is why I mentioned above that I tested the firmware.. my Wrtp54g will run this firmware, without wireless option.

Anyone find the wireless version? I would really appreciate it!

By the way, the version of this firmware is:
router 1.11.1
voice 3.1.10
They named it "rtp300.3.1.10.bin" and made it hard to see the router portion.. but that is what it is.

I had no problems going back to the older router/voice versions of firmware on my device.

When I have more time, I would like to mount the filesystem and take a look at their PAP2 implementation. Is it just HTML, or did they really upgrade the voice firmware that much?

One remaining part we did not accomplish here. The thing is running Linux and has a SSH login on it. I would like to log-in to the box.. Password is unknown for it.

In the new firmware, the "Admin" account has no password.

I looked around and nothing stood-out since i could use the 'voice' part already (since it is PAP2 style and unlocked).

I took a gamble and down-graded the unit to 1.00.60 to see if the 'Admin' would remain without a password. Sadly, it reset and now has a password.

Anyhow, this "no password" for Admin is important if you wish to downgrade and dont have your 'USER' account set to active. By default Vonage activates the user account and sets a standard pw. If you do a factory reset of voice, it gets disabled. Use the 'Admin' trick w/o password, and it will work for the /update.html page.

OK, unless someone stumbles across the WRTp54G version, I will step back and let you guys with RTP300 units test this and report back.
reply
meister_sd @ 11th Apr 11:01AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

I couldn't get SSH to work. It would crash Putty. Also the password for big admin (Admin) is blank - just hit enter.
reply
anon @ 11th Apr 10:28PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Anyone have a working Asterisk configuration (xml perhaps) they'd like to share?
reply
rcilink @ 11th Apr 10:45PM:
stupid voice tricks for rtp300-3-1-10.bin

Just in case you were missing the "Please contact your service provider for further information.", here is the link under the new firmware to see that page :)

»192.168.15.1/cgi-bin/webcm?getpa···ice.html

Don't worry, it's unlocked. Click "status" tab and then "voice" tab to get back in..

Curiously, they make a hint on the right margin about Vonage.. I guess this firmware may be what is next from vonage..
reply
rcilink @ 11th Apr 11:34PM:
RTP300-3-1-10.bin ... more tricks

I would love to get shell access on this new firmware..

It appears that the ssh daemon is dead, so possibly a serial cable or I will work on opening-up the firmware image (squash-fs style).

Here's why.. It is not yet clear if Linksys actually re-wrote the PAP2 MIPS code or if they are running an emulator on this device.

Some stuff is changed, for sure. Some is still the same.

The syslog_vo.html still works. They reference "SIPURA" in the log..
Link: http://192.168.15.1/cgi-bin/webcm?getpage=%2Fusr%2Fwww_safe%2Fhtml%2Fvoice%2Fsyslog_vo.html
(Note: login info is Admin with no password)

The PAP2 upgrade method works on this firmware. I haven't decided to try it or not for real, as I don't want to brick my box..
Link: "http://192.168.15.1/admin/upgrade?tftp://a.com/b.bin"

One last thing that is very informative: use the log feature (in Administration / Log).. Set it to debug to see lots, or info to see less msgs.. The IP address must be a machine with a syslog viewer..
reply
rizzo2dial @ 12th Apr 03:06AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by czyc :

Ok, openssl won't decrypt it but »www.uqtr.ca/~delisle/Crypto/codes/rc4/rc4.c does it nicely.
I've modified the code for the program to accept file names for the input & output files (instead of using STDIN/STDOUT redirection) and have compiled it under Visual Studio .NET 2003. I've also cleaned up the program a bit (and moved some logic out of the MAIN function).

Attached is a zip file containing the modified source code as well as a Windows (DOS/Command Prompt) executable. Since it's compiled under VS.NET 2003 (which is a development environment for the .NET 1.1 framework), the Microsoft .NET 1.1 framework will likely need to be installed for the program to run. (Microsoft provides it for free).

The syntax for this version is of rc4 is:
rc4 key inFile outFile

Rizzo
RC4.zip 22,381 bytes
rc4 Windows Executable + Source Code
reply
ydef @ 12th Apr 02:38PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by rcilink :

The trick with this device:

4. the firmware is actually a "squashfs" filesystem. This means it is possible to 'mount' the filesystem and modify as needed. Then re-build the squashfs filesystem and flash your device.

Rcilink:

Question. When rebuilding the squashfs firmware, which hex words do you manipulate in the footer to get the web interface upgrade to take it? I'm able to successfully manipulate the headers of my customized squashfs filesystem to take into account new filesize, zipped fs, and all that, then I reattach the firmware header and footer, apply the tichksum and it will take my new image all the way to the end before complaining of a truncated image, almost like i'm missing one last checksum in the footer. (and yes, i have included the tichksum)

In case you don't have the new firmware image for the wrtp54g yet:

»httpconfig.vonage.net/wrt-11.1.0···0327.img

Although I haven't checked it yet to see what changes are in it and whether it holds that the new firmware image does not come with an Admin pw as you say about the rtp300 image. This would seem weird to me. So when you say it doesn't come with an Admin pw, what do you mean by this? It doesn't seem plausible or likely that there is no password entry in /etc/passwd (with the shell in fact as /bin/false) since this would shutout vonage as well. What do you mean by this?

At least for me, it doesn't seem that vonage has pushed out this new firmware yet since my router doesn't have it on it.
reply
rcilink @ 12th Apr 03:18PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Some things to note:

The file size is important for the firmware. it must be 3866632 bytes long. If it is shorter than that, pad it with FF's towards the end and then re-checksum it.

As for the 'Admin pw'.. I was meaning to say that the Admin password is not set, (there is no password), so on that new firmware, you can use Admin with no password, and it works.

I also noticed that SSH wont work in the new firmware.. Possibly because we need to feed it a XML config to enable it. I am not sure how I am going to feed this thing at this point. (Is it the XML under the voice section that will work, or do I need to use the Provision.html page ? )

Either way, I hope to have the squashfs available for review soon, alongside the 1.00.62 package. This way, I can combine the better of the parts and make a WRTp54G version.. I want my wireless portion to work!
reply
meister_sd @ 12th Apr 03:19PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

ydef, we are in the process of trying to take the bin file we have used to unlock the rtp300 and modify it to work with the wrtp54g by basically taking the router portion out of the vonage image and placing it in the rtp300 voice image and combining them. I've seen the work you've done on this already and maybe you can help us. I think the same procedure used to modify the original rtp300 to upload into the vonage rtp300 can be applied to the rt31p2. If you could PM rcilink, we would like your help. One thing I'm really interested in is duplicating your serial port access and JTAG access. I haven't had any luck getting a serial port connection that you described in your wiki on openwrt.
reply
czyc @ 12th Apr 04:46PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

The config backup file hopefully is still zlib. In it there is a setting for the Admin password but it seems to be overridden by the provision file. Maybe the unlocked firmware will accept a password change. Also there is a setting for remote ssh in it.
reply
meister_sd @ 12th Apr 05:30PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by czyc :

Also there is a setting for remote ssh in it.
Yes, but the setting can be turned on but it crashes my ssh client. So we will work in it.
reply
ydef @ 12th Apr 11:31PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by meister_sd :

ydef, we are in the process of trying to take the bin file we have used to unlock the rtp300 and modify it to work with the wrtp54g by basically taking the router portion out of the vonage image and placing it in the rtp300 voice image and combining them.
Okay, but I'm a bit confused first as to where this RTP300-3-1-10.bin firmware originated from. I can't imagine that a provider would release a firmware where the root pw was blank.

said by meister_sd :

I've seen the work you've done on this already and maybe you can help us. I think the same procedure used to modify the original rtp300 to upload into the vonage rtp300 can be applied to the rt31p2. If you could PM rcilink, we would like your help. One thing I'm really interested in is duplicating your serial port access and JTAG access. I haven't had any luck getting a serial port connection that you described in your wiki on openwrt.
Serial port's easy. Just follow the diagram i put up on the openwrt wiki:

»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G

at the bottom of the page. Don't forget that you'll need a level converter. If you try to plug it straight into your pc (which runs at 12 volts) you'll fry your router, or your pc, or both. Using a max233a serial adapter does the trick, like the ones you can pick up at compsys1:

»www.compsys1.com/workbench/On_to···ter.html

Another thing I'm confused about, is why you guys are going through the trouble of modifying the RTP300-3-1-10 firmware and then working backwards to make it compatible with the wrtp54g when the vonage firmware can just be modded directly given that the 3866632 size of the firmware is what allows it to take? I suppose I can continue this discussion in PM with rcilink if he wants to PM me what the big picture here is. I need some time to play with feeding modded firmware with that size to confirm that that's what i was missing before. But given that rcilink was able to do this succesfully with the 3-1-10 firmware, what's stopping him from directly modding the 1.00.62?
reply
meister_sd @ 13th Apr 12:40AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by ydef :

Okay, but I'm a bit confused first as to where this RTP300-3-1-10.bin firmware originated from. I can't imagine that a provider would release a firmware where the root pw was blank.
I found it on a site in the Netherlands that is supporting it there. I've asked if they have any other firmware for Linksys Voice products and they didn't.

said by ydef :

Using a max233a serial adapter does the trick, like the ones you can pick up at compsys1:
I bought one from them, the same that is what you recommend but maybe I'm just not getting the settings right in HyperTerm. 115000, 8-N-1 and I've tried all three Xon/Xoff, Harware and None. Doesn't work for me.

said by ydef :

But given that rcilink was able to do this succesfully with the 3-1-10 firmware, what's stopping him from directly modding the 1.00.62?
The 3.1.10 has the whole voice package. It includes all of the voice options and screens as the PAP2. The 1.00.xx from Vonage doesn't have the granular control as the other - just what Vonage needs for it's network. It's a custom Vonage only build - At least as far as I have seen. I've fed my rtp300 with an XML file that gave me big admin (Admin) and the options just weren't there like the 3.1.10 software. It also doesn't have the radio options as the wrtp52g needs either because it's not included in the build or was turned off at compile. He (rcilink) put it on his wrtp52g and got everything but the radio to work.
reply
ydef @ 13th Apr 09:09PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by meister_sd :

I found it on a site in the Netherlands that is supporting it there. I've asked if they have any other firmware for Linksys Voice products and they didn't.
Too bad, they hadn't released the wireless wrtp54g? That's odd.

said by ydef :

I bought one from them, the same that is what you recommend but maybe I'm just not getting the settings right in HyperTerm. 115000, 8-N-1 and I've tried all three Xon/Xoff, Harware and None. Doesn't work for me.
Weird, have you verified that your adapter works independently?

said by ydef :

The 3.1.10 has the whole voice package. It includes all of the voice options and screens as the PAP2 ...
Cool. Too bad this norweigan company doesn't also support wrtp54g? Did you ask about the unit specifically?

Okay, so here's a prelim diff I did between 1.00.62 and the rtp 3.1.10:
»www.m-a-g.net/wrtp10062-rtp3110.diff

As you can see, the only things missing from 3.1.10 are:

Only in 62/etc: killp
Only in 62/lib/modules/2.4.17_mvl21-malta-mips_fp_le/kernel/drivers: net
Only in 62/usr/sbin: dropbear
Only in 62/usr/sbin: wlan
Only in 62/usr/www/html/defs/style5/images: .svn
Only in 62/usr/www_safe/html/status: HWLStatus.html
Only in 62/usr/www_safe/html/status: WirelessClient.html
Only in 62/usr/www_safe/html/status: WirelessInfo.html
Only in 62/usr/www_safe/html/voice: restartVoice.html
Only in 62/usr/www_safe/html: wireless

Being, all the wireless related parts and dropbear.

So that's simple enough ... unless anyone has better suggestions I'll put together a combined firmware that consists of 3.1.10 and the above missing parts from 1.00.62 and see if that will allow to create a generic NA firmware compatible functional on the wrtp. Anyone have any ideas why this might NOT work?
reply
mazilo @ 13th Apr 09:48PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by ydef :

So that's simple enough ... unless anyone has better suggestions I'll put together a combined firmware that consists of 3.1.10 and the above missing parts from 1.00.62 and see if that will allow to create a generic NA firmware compatible functional on the wrtp. Anyone have any ideas why this might NOT work?
Ydef,

If you have the ability to combine and put together the missing parts, why not just take apart the latest 1.00.62, edit the /etc/shadow to replace the Admin password hashed key with the known password, mod the Voice button so that it will point to the Voice_adminPage.html file, and repackage to redistribute the firmware?
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
meister_sd @ 13th Apr 10:09PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Mazi, Why not add the wrtp54g router portion to the v3 voice? It would seem easier. But since I don't have a wireless, maybe I'm speaking out of turn since I can't test. The voice part of the v3 is complete and looks just like a pap2.
reply
meister_sd @ 13th Apr 10:15PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by ydef :

Cool. Too bad this norweigan company doesn't also support wrtp54g? Did you ask about the unit specifically?
Yes I did. I asked about the wrtp54g, the rt31p2 and any other voice linksys router....

said by ydef :

As you can see, the only things missing from 3.1.10 are:
I may sound strange, but did you check the other way? I think the vonage stuff is missing much more than the 3.1.10 such as the advanced admin page and user 1 & 2 page. It may seem if you had a rtp300 AND the wrtp54g, you could try the firmware independently. I have a couple of rtp300's coming from ebay next week. If it isn't solved by then, I can send you one if you'd like.

said by ydef :

Anyone have any ideas why this might NOT work?
Nope. That is what I've been thinking too.
reply
mazilo @ 13th Apr 10:30PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by meister_sd :

Mazi, Why not add the wrtp54g router portion to the v3 voice? It would seem easier.
I believe you are right. Perhaps, Ydef is doing what you have said here.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
ydef @ 13th Apr 10:31PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by mazilo :

If you have the ability to combine and put together the missing parts, why not just take apart the latest 1.00.62, edit the /etc/shadow to replace the Admin password hashed key with the known password, mod the Voice button so that it will point to the Voice_adminPage.html file, and repackage to redistribute the firmware?
Because, from what I'm inferring from the discussion here about firmware version 3.1.10 for the rtp300 that meister_sd scored on a norweigan site, the web interface pages are far superior and allow user enhanced capabilities and features bereft from the stripped down vonage versions, and if you check out the diff I just posted you'll see significant differences in the html pages of the two firmware sources.
reply
ydef @ 13th Apr 10:39PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by meister_sd :

I may sound strange, but did you check the other way?
Other way? The diff file I posted says all. These are the files that are in one version but not the other:

Only in 62/etc: killp
Only in 62/lib/modules/2.4.17_mvl21-malta-mips_fp_le/kernel/drivers: net
Only in 62/usr/sbin: dropbear
Only in 62/usr/sbin: wlan
Only in 62/usr/www/html/defs/style5/images: .svn
Only in 62/usr/www_safe/html/status: HWLStatus.html
Only in 62/usr/www_safe/html/status: WirelessClient.html
Only in 62/usr/www_safe/html/status: WirelessInfo.html
Only in 62/usr/www_safe/html/voice: restartVoice.html
Only in 62/usr/www_safe/html: wireless
Only in rtp/bin: more
Only in rtp/etc: ca_crt.pem
Only in rtp/etc: fpar_check
Only in rtp/etc: lsca_crt.pem
Only in rtp/etc: rootca_crt.pem
Only in rtp/sbin: watchdog
Only in rtp/usr/bin: head
Only in rtp/usr/bin: od
Only in rtp/usr/bin: tail
Only in rtp/usr/www/html/defs/style5/images: UI_03.jpg
Only in rtp/usr/www/html/defs/style5/images: UI_Cisco1.gif
Only in rtp/usr/www_safe/html: index.html.orig

And as far as differences between html pages, all the explicit differences are in that diff file I posted. The diff file is the grand culmination of all the differences between the 1.00.62 and 3.1.10 firmware.

So yeah, all the html differences that you're referring to are references in that diff file.

So I think you're a bit confused as to what I suggested I'm going to do ... which is to construct a firmware based on the 3.1.10 and add the missing wireless stuff, plus dropbear from the vonage firmware. That way, this uber firmware i'm constructing will have all the benefits of the 3.1.10 firmware along with the wireless capabilities so its compatible with the wrtp54g, and also have dropbear running so its shell accessible like the vonage based firmwares.

Does this make sense? When I was pointing out what i was missing in my previous post, I was doing so as a means of pointing out what I was going to do to 'fill in' what was missing in order to create an improved firmware that's compatible with my unit and also includes a dropbear shell. I'm not sure you completely understood what I was illustrating ... you might want to re-read my original post.
What the vonage firmware is 'missing' is somewhat irrelevant in this case because the firmware i'm piecing together is based on the norweigan firmware.
reply
meister_sd @ 13th Apr 11:15PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

You are totally right. I skipped a part of your breakdown. It is very complete and my hat is off to you. Tomorrow I have off work and I'm going to fire up my linux box and try some of the utilities available and see what I can do with the rt31p2. Maybe we both can find a solution very soon. I'll PM you with my contact info if you want to talk online tomorrow.
reply
anon @ 15th Apr 04:22AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Hi rcilink,
I have two WRTP54Gs. I do like to try the rtp300-3-1-10 firmware you made. Can you upload here?

Thanks
reply
mazilo @ 15th Apr 06:36AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by machycd :

Hi rcilink,
I have two WRTP54Gs. I do like to try the rtp300-3-1-10 firmware you made. Can you upload here?
Please read all the posts here in this thread before you ask for a repost to upload for the file to waste the resources here just for you!
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
rcilink @ 15th Apr 01:21PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by machycd :

Hi rcilink,
I have two WRTP54Gs. I do like to try the rtp300-3-1-10 firmware you made. Can you upload here?

Thanks
The "rtp300-3-1-10" file posted in this thread is coded for the Linksys RTP300 device.

I used the WRTP54G to test the firmware (with a CODE change, to make it load), and confirmed it working. I did not post the modified 'RTP300' firmware (loadable on the WRTP54G) since the wireless portion is not usable at this point.

I believe it is safe to say that soon you will find a WRTP54G version of 3-1-10 here. So, your best bet is to hang in there and keep an eye on this message thread.

I hope this helps to answer your question.
reply
anon @ 16th Apr 12:26AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

rcilink thank for replying my question, I knew the firmware you tested on your WRTP54G won't be able to use the wireless, I was too excited so asked you to upload that firmware(sorry about what I did). I will keep eye on this thread and looking forward you the new firmware for wrtp54g from you.

Thanks again
reply
anon @ 16th Apr 01:53PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

I used the rtp300-3-1-10 firmware from here and made some change and did the check-sum for wrtp54g just like rcilink did and it works great just no wireless like rcilink said. Thanks meister_sd and rcilink

I checked both firmware on wrtp54g and rtp300, I found out end of the firmware before the check-sum both have "23 DE 53 C4".

Does " 23 DE 53 C4 " mean anything?

Thanks
reply
anon @ 20th Apr 03:54PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Hello everyone,

I have a RTP300 I got from vonage but no longer use their services. However, they told me to just keep the router so I've been reading about how to unlock it. I'd like to be able to access a shell.

I uploaded the RTP300-3-1-10.bin file to my RTP300 and everything seemed to go correctly. However, contrary to what I've read, I can't seem to login in as admin (or Admin).

Now I'm a little stuck since I can't get in to flash back to my original firmware. Any ideas?

Frosty
reply
rcilink @ 20th Apr 05:41PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

DISCLAIMER: If you are reading this and are actively using VONAGE with your device, you should NOT be doing any of these actions listed below. If you select to ignore this warning, you are on your own..

Hmm. Interesting.
You should still login as 'admin' (lowercase) with the password you had set prior to the upgrade.

Once you are in there, under the RTP300-3-1-10.bin firmware, try clicking on the 'VOICE' tab. Does it want a password, or are you in?

If you wanted to do a firmware upgrade, look under 'ADMINISTRATION' tab and select firmware upgrade. The service provider username / password may be one of these:

username=Admin
password=
or
username=user
password=tivonpw

---
One thing I noticed is that the firmware upload does not actually change some of the user info.. To truely do that, you must perform a factory reset after updating the firmware to RTP300-3-1-10.bin. I have done this on a former-vonage WRTP54G and it did not lock it down. In fact, it cleared the Admin password completely.

---

If you have no idea what the actual 'admin' (lowercase a) password is... do this:

1. grab your favorite sharp item (paper clip?)
2. push it in the 'reset' hole on the back of the unit.
3. remove the power from unit.
4. restore power to the unit.
5. continue to hold the reset button until about 60 seconds.

* This should have cleared all router settings, and you can then login with admin for username and admin for password.
reply
anon @ 21st Apr 12:39PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Hi, How do you upload the firmware RTP300-3-1-10.bin?

Thanks
reply
anon @ 21st Apr 03:52PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Thanks RCILINK. Actually, is the main admin password that won't be accepted. The update.html page no longer will work as well, but I assume that is because I can not authenticate as admin.

After the 3.1.10 upload, the 192.168.15.1 main page does not accept admin with no password, or my custom password prior to flashing. I'm not sure if the name itself is case sensitive, so I did try both Admin and admin.

I'll try a full factor reset by holding the reset button in for 60 seconds and see if that will reset the admin password back to blank.

I'll report back. Thanks again.

Frosty
reply
meister_sd @ 21st Apr 04:47PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by frossm :

I'll try a full factor reset by holding the reset button in for 60 seconds and see if that will reset the admin password back to blank.

I'll report back. Thanks again.

Frosty
The login password for the first login screen is:
admin/admin

After you are in and you are asked for a password to do firmware upgrades or other work in the voice section use:
Admin/[no password]
This password is blank, just hit enter. With the 3.1.10, you can change the big Admin and "user" in the voice section.
reply
anon @ 21st Apr 07:33PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Wow, do I feel a bit silly.....

Not to keep reading on obtaining ssh access.

Thanks all.

Frosty
reply
mazilo @ 21st Apr 07:57PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by frossm :

Wow, do I feel a bit silly.....

Not to keep reading on obtaining ssh access.
That's what happens when you don't read.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
xeryax @ 23rd Apr 11:47PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

So, heres my delema-
I have read this topic forwards and backwards (at least I think I did)
I have an rtp300, it doesnt seem to want to connect to update from vonage *good thing* i have grabbed my provisioning file and decrypted it, again a good thing, I have downloaded the rtp300-3-1-10.bin file, but i cannot seem for the life of me to be able to get that uploaded to my router... when I hit the hidden update page, i get an error saying, "upgrade not allowed for this login type." so i go back and try different usernames/passwords with the adminpwd in my provisioning file and nothing is seeming to work.... am i just heading in the wrong direction? i am absolutely clueless here...
Thanks!
reply
rcilink @ 24th Apr 12:13AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by xeryax :

when I hit the hidden update page, i get an error saying, "upgrade not allowed for this login type."
This happens when the config.xml does not have the user account enabled. Make sure enabled is set to 1 for the user account.

If it is missing from your .XML file, you might be able to add it. It should look something like this:
             <user id="3">
              <username>user</username>
              <password>rBCmSyBFEFvLU</password>
              <shadow>1</shadow>
              <idle_timeout>15</idle_timeout>
              <userlevel>USER</userlevel>
              <enabled>1</enabled>
             </user>
*NOTE: the above password hash for user is User (capital U).

re-encrypt the config.xml and feed it to your device.

If your device is completely not syncing to take/decrypt the file, you may need to hold-down the reset button and give it a complete factory reset to get it back in sync.

reply
xeryax @ 24th Apr 12:43AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Another Dumb question: (sorry again if I have overlooked this)

Do i feed the provisioning xml via faking the vonage tftp server? or is there a magical URL... I prefer the URL, but it is probably passwd protected too.
reply
rcilink @ 24th Apr 12:49AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Take a look at the Provision.html page.
Make sure you are quick with the ESC key.

It tells you the 'path' (subdirectory) you need to make.
it also tells you the provision server.
It usually will say "ti.tftp.vonage.net" or something like that.. Replace it with your server ip address.

Filename is ti00000000.xml (replace 0's with MAC address of device)

If you make changes on that web page, you must fill in all fields that can be filled-in, or they will get saved as blank (empty) values!!
reply
meister_sd @ 24th Apr 03:20AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Also remember to grab the second file rcilink put up as the first file in this thread was bad.
reply
xeryax @ 24th Apr 07:56PM:
It will work someday ;)

Alright,
I've been messing with the stuff you gave me last night, all day... still to no avail... The RTP300 pulls the xml file down, and when i hit the Provision.html page and view source: i see that provisioning was successful... My problem is that I still get user/pass errors when trying to login, i have tried Admin with the --adminpwd--xxxxxxx--/adminpwd-- (those are tags) as a password (obviously not the tags) both caps and no caps, i have tried user, making sure that it is all lowercase with the rBCmSyBFEFvLU that you posted above, again with all different types of cases, including all lower.... My xml file did not have a user section before, is it possible that i placed it in the wrong area??
My firmware version is 1.00.43 so i am playing with older than most people, maybe my rtp300 does not have some features.
One of the biggest things is that when I try the "user" account, it still says "User not enabled to log into the system" most other times it says Bad username/password, and when i type admin/admin, i obviously get user not allowed to login this user level.

Let me know what you think, I truly appreciate all your help!
-XeryaX
reply
rcilink @ 25th Apr 01:57AM:
Re: It will work someday ;)

Please note that rBCmSyBFEFvLU is the hashed-password, and you need to type the actual password.

For the user account login, type User for the password. (User is the unhashed password.)
reply
xeryax @ 25th Apr 03:17AM:
Re: It will work someday ;)

still get the bad username/password and user disabled messages.... hrmmm....
reply
xeryax @ 25th Apr 10:37AM:
Re: It will work someday ;)

Yeah, I'm not entirely sure the user got enabled, because if i type crap for a password, it will tell me that i have typed the wrong password, but if I type user/user it tells me user is disabled...
I have attached my xml from fonage.... obviously with some tweaks... Remember I get Provisioning Successfull messages, so it does take it when i re-encrypt it and feed it to the rtp300, I just need to know how to dump firmware on it.
rc, thanks for all your help so far
.
plaintext.zip 2,161 bytes
plaintext.xml
(plaintext.xml)
reply
rcilink @ 25th Apr 04:29PM:
SAMPLE provision xml for RTP300

Try this file.. I changed the Admin PW to be "Admin" and left the user pw as "tivonpw". Also, I assume your router to the net is at 192.168.100.1. I set DNS1 to that IP. Also, I put your TFTP and HTTP server IP to 192.168.100.53.

The way this is written, it will do this:
1. The RTP300 will TFTP from 192.168.100.53 the file: /rtp300/ti001310000.xml (replace 0's with actual MAC)

2. The RTP300 will HTTP get (using WGET) from 192.168.100.53 the file: /rtp300/rtp300-3-1-10.bin

3. Set appropriate provision info.

4. Set Admin password to Admin and enable Admin

5. Set user password to tivonpw and enable user

6. Set idle timeouts to: user:5 and Admin:15

<provision version="2">
<options>
<reconfig/>
</options>
<settings>
<firmware>rtp300-3-1-10.bin</firmware>
<profileurl>tftp://192.168.100.53:69</profileurl>
<imageurl>http://192.168.100.53</imageurl>
<key>43731b1f3e73581f53e3bc5456929138dfd0a980e9ab066f5b148a9a073b1e24</key>
<path>rtp300</path>
<interval>30</interval>
<intervalimg>120</intervalimg>
<dns1>192.168.100.1</dns1>
<dns2></dns2>
<voicelog>notice</voicelog>
<logdest></logdest>
<sntp>time.vonage.net</sntp>
<tikeypub></tikeypub>
        <timezone>STD5:0DST,M4.1.0,M10.5.0</timezone>
    <adminpwd>Admin</adminpwd>
    <userpwd>tivonpw</userpwd>
    <userstate>1</userstate>
    <useridle>5</useridle>
    <adminstate>1</adminstate>
    <adminidle>15</adminidle>
</settings></provision>

reply
xeryax @ 25th Apr 09:00PM:
Re: SAMPLE provision xml for RTP300

Worked like a charm!!! Gratzi!!!!

-XeryaX
reply
rcilink @ 26th Apr 02:48AM:
wrtp54g firmware version 3.1.10

If you are using your WRTP54G with Vonage for an active subscription, this firmware will _not_ work for you! Don't do it!

OK, I have been testing this version of firmware, and it appears to be stable.. As with anything these days, you assume full responsibility when loading firmware on your device.

It is for the WRTp54g router.

Some features:

- Wireless works!
- Serial console does not require login (press any key for shell prompt)
- ssh login (dropbear) added for remote admin
- Default 'Admin' password is "" (blank)
- This makes the WRTp54G work as a '-NA' (unlocked) device.
- VOICE section works the same as a Linksys PAP2 device.
- Configure additional features using config.xml files, as before

Limitations/Bugs:

:VOICE section identifys as "RTP300". No 'Wireless' tab while in voice..

Work-around: change to another screen (non-voice) to see Wireless tab.

---
If you are having trouble getting into your WRTP54g, review the first several posts on this thread. They will help you find your 'encryption key' and info to get going.

To get the most of this firmware, you should perform a 'factory reset' after loading this version. Do that with reset button (hold in for 50 secs or so) or the fact reset option in ADMIN tab. This will clear junk from flash ram and let you setup the device, starting from unlocked (-NA).

OK, well have fun with it!
reply
markwei @ 26th Apr 03:43AM:
Re: wrtp54g firmware version 3.1.10

Wow rcilink you are the man
I am going to test it now

Thanks a lot
reply
mazilo @ 26th Apr 09:03AM:
Re: wrtp54g firmware version 3.1.10

I wondered if this hacked firmware will have a support for STUN server options under its SIP tab. Can anyone confirm this?
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
anon @ 26th Apr 10:04AM:
Re: wrtp54g firmware version 3.1.10

Did the update, everything on the Router side works fine, but on the voice side it will not save any of my Settings when the router reboots all setting fields are blank. I did perform a Fact Reset on Voice and Router after doing the update and I am setting up the SIP settings over Wireless
reply
anon @ 26th Apr 11:33AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

When I fill out the SIP settings and click save, the router reboots but none of the data is saved all is gone on the reboot.

Voice seems to be broke, will not even save the time settings under regional
reply
anon @ 26th Apr 04:41PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I can not set any of the SIP settings when I make changes and save them they show up empty after reboot.?

I did a fact reset and still no go
reply
rcilink @ 26th Apr 07:56PM:
Re: wrtp54g firmware version 3.1.10

Now something definately is not right with the voice portion on that wrt3-1-10 firmware.

I took it down from here until we get the voice part fixed-up..

Sorry about getting people's hopes up!!

But, we are close..

So, I will load up the RTP300 and begin the painful task of comparing the file structures, etc..

Stay tuned!
reply
anon @ 26th Apr 10:06PM:
Re: wrtp54g firmware version 3.1.10

Does flashing it completely require setting any of the J1 jumpers? Curious noob, following with admiration and awe.
reply
rcilink @ 26th Apr 10:14PM:
OK, so what about the WRTp54G version... ?

OK, I think I figured it out..

It looks something like this:

The RTP300-3-1-10 firmware is unique in that they added a seriously modified SIP application. This SIP application appears to be an emulated PAP2-type interface, with most of the features of a regular Linksys PAP2 device.

The design of the SIP application includes memory locations to read/write the Sipura Profile (commonly known as 'factory defaults') and the Line1/Line2 settings.

Things seem to work OK with the RTP300, as the additional flash ram is not taken by wireless components, etc.

The WRTP54G uses more of this valuable memory, and when you go to 'save settings' in the VOICE module, it causes the thing to crash and reboot. The memory it is trying to write to could easily be in use for the wireless apps or another piece within the system.

So, time to begin working on a memory map of this beast and relocate the Sipura Profile and Configs. Setting the location is easy. It is done using environment variables (stored in /proc/ticfg/env )
reply
xeryax @ 26th Apr 10:15PM:
Re: wrtp54g firmware version 3.1.10

I think there is something messed up with the voice part of the RTP firmware too... the voice tab tries to redirect you to http.//IP ADDRESS/voice.html instead of the nested path that it used to be.
reply
syos19 @ 27th Apr 08:47AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Can someone help me to unlock RTP300? Thanks.
reply
meister_sd @ 27th Apr 01:26PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by syos19 :

Can someone help me to unlock RTP300? Thanks.
Everything you need to know is in this thread - read it!

If you are still having problems, be specific as to what you cannot do.
reply
rcilink @ 28th Apr 09:38PM:
WRTp54g unlocked 1.00.62-NA

Since it had been posted here in this thread, here is an update to this project...

Attached is wrtp54g 1.00.62-NA firmware. Yes, for the most part, it is unlocked!

For now, it is the old voice interface.

Give it a spin.
reply
markwei @ 29th Apr 03:18AM:
Re: WRTp54g unlocked 1.00.62-NA

I have tried this firmware and I found a problem with me when I tried to flash back to other firmware. When I click "Firmware Upgrade" enter my ID and password then can't show the upgrade page. I don't know if other people have same problem or just me.

But finally I got the old firmware back to my unit.
reply
rcilink @ 29th Apr 10:06AM:
Re: WRTp54g unlocked 1.00.62-NA

said by markwei :

I have tried this firmware and I found a problem with me when I tried to flash back to other firmware. When I click "Firmware Upgrade" enter my ID and password then can't show the upgrade page. I don't know if other people have same problem or just me.

But finally I got the old firmware back to my unit.
You are right.. The link it jumps back to is not correct-- that will have to be fixed.

Until then, after it gives you the html error, simply point to this link »192.168.15.1/update.html

You will be able to up or downgrade firmware from there.
reply
anon @ 29th Apr 08:06PM:
Re: WRTp54g unlocked 1.00.62-NA

What is the default Admin password on this new image?
I tried to SSH into my WRTP with Admin/blank, Admin/Admin and a few other variations but couldn't get in. Even after a factory reset with the reset button.

[Edit] - Strange...It seems to be retaining the Admin password I gave it in my xml. Not sure how after I performed a full factory default?

Good news is, I was able to TFTP it a modified and re-encrypted tigeneric.xml file and get it to provision to my Asterisk server....changing the Admin password in the process.

Keep up the good work rcilink!
Can't wait for the working wrt3-1-10 firmware.
reply
anon @ 30th Apr 02:32AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

It's great with asterisk and so far no problems Thanks for the FW
reply
xeryax @ 1st May 09:56PM:
rtp300

is anyone else having problems with the rtp300 firmware? mine is freezing every time i hit a voice page... i have to reboot it to make it work, i have re-downloaded the FW a few times, and it still does this,...

(thats using the 3.1.10 fw posted on page 3 of this thread)

Actually now that I am looking at it, i think it is because i gave it no voice provisioning info... No tftp server to look for for info, so it is trying as hard as it can to fill the voids in the html at the voice pages, and it is freezing.... any other ideas how to push an XML to one of these things so i can unbrick mine?
reply
rcilink @ 2nd May 01:44AM:
Re: rtp300

Hmm, I am curious what you mean 'freezing' upon hitting the voice page. Do you mean it displays the top of the page (blue tabs, etc) but never completes? ...or nothing, just a 'page not found' ?

Did you do the 'factory reset' after loading the rtp300-3-1-10.bin file? It is a good idea to reset it, so re-format the flash to handle the new voice module.

The 3.1.10 version for rtp300 is seriously beta. It is marked a "pre-release" in the firmware.

As for the provision information.. This has been interesting. In this firmware, there are two provision systems. The first is the old-style provision (rc4'd config.xml) that can set/change Admin password, user password, etc. The second provision system is the Sipura (new voice section) system.

The way Linksys made the SIP application was to map out some of the flash ram for the Sipura VOICE application. It appears in their efforts, they had to remove anything possible, to free-up extra flash memory for the profile and images.

(This is why the WRTp54g version is not working-- it does not have enough room to run the new voice module and wireless..)

Now, I have no idea on their timeline for this product. Will the RTP300 / WRTP54G be phased out? They put a lot of effort into porting the voice module to the RTP300 to scrap it completely.. So, maybe there is a new 'rtp300' coming out.. (just a guess).

Anyhow, to save you the pain, in the voice section, go into ADMIN and ADVANCED. Look for PROVISION tab. In there, set PROVISION ENABLE to NO. This will make it never try to get a voice provision file.

The rtp300 XML config (old-style provision) should still be up and running. You will know this if you did not change the info in there, you will get downgraded to 1.00.62, compliments of Vonage. Do your factory reset, and then go in there and change the provision info to point to a non-vonage server.
reply
xeryax @ 2nd May 02:18PM:
Re: rtp300

When i say freeze, I mean it will load the page (what appears to be completely) If you recall the provisioning stuff at the bottom of the Provision.html source, you will remember that has all the info that the unit is provisioned to, when I hit ANY voice page, the unit will load the full page (again appearances only) but stop responding to ANY http request when it gets to about there in the html source. therefore, i think it is trying to find provisioning information in its memory somewhere and never succeeds.
As you may recall, I had a problem child when i was trying to upgrade my firmware, and we fed it an xml file with just username info in it with no voice configuration. now the unit will not hit the tftp server for an xml, it has no provisioning, the voice tab goes to ipaddress/voice.html (thus i have to type in the pages manually */usr/www_safe....etc.etc*) and when i do hit one of those pages, the unit needs to be power cycled to get back into the web interface.

Again, any ideas are much appreciated.

-XeryaX
reply
rcilink @ 2nd May 07:38PM:
Re: rtp300

Please keep in mind that the rtp300-3-1-10.bin file contents are original, as found on the net. The only thing changed is the filesize/checksum, so the rtp300 hardware would take it.

--

Having the serial console hooked-up during some testing, I can tell you that the reason it is 'freezing' is because the javascript is trying to resolve variables that currently do not have values assigned to them.

Simply loading the Provision.html page will cause this result. The page loads, looks OK, but is blank. Slowly, it is trying to get the values for each variable. If you wait long enough, it will finish-- without freezing. (seriously, might be 2-4 minutes!)

This is probably a bug that Linksys will need to clean-up when/if they ever plan to release an official 3.1.10 version.

If you have not done so, try a factory reset. The firmware you are using has factory defaults for Provision.html (points to vonage)
reply
xeryax @ 2nd May 10:20PM:
Re: rtp300

I must be retarded--- I thought i did a factory reset before, but i guess I didnt, its all good now ;) If anyone ever wants to know if they did one or not, read my post from "everything works great" to now to see a list of symptoms.

Thanks rclink for your help, good effort!

-XeryaX
reply
tkprojects @ 4th May 04:16PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

said by ydef :

In case you don't have the new firmware image for the wrtp54g yet:

»httpconfig.vonage.net/wrt-11.1.0···0327.img
For the RTP300 just remove the initial 'w' in the filename. Thus:

»httpconfig.vonage.net/rt-11.1.0-···0327.img

Not suprisingly.
reply
vlan4 @ 5th May 06:46PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

After: 1) Select 'restore voice defaults'; 2) Confirm with user/tivonpw. The previous voice setting was cleaned. Now my RTP300 doesn't send tftp query to ti.tftp.vonage.net. No dial tone at line 1. I cannot use the above method to feed .xml back to the box. Anyone could shed a light on me? Thanks.
reply
rcilink @ 5th May 09:10PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

That is because you were not supposed to do this if you were using the box with an active Vonage account...

You can plug-in by hand the vonage tftp info in the Provision.html page, and it will turn it back into a vonage box..

If you want it to provision the dial-tone (SIP settings), it will downgrade you to 1.00.62 firmware also.

Another option you have... you can get the .XML file and decrypt it to read it. then put in the settings yourself. It should work. (if you do this, don't fill-in the provision stuff)
reply
vlan4 @ 6th May 12:09AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

No, it is not a vonage-activate box. Put a sniffer on its WAN interface. Only DHCP packets and NTP packets to time.vonage.net. No other packets including packets to ti.tftp.vonage.net or tftp.vonage.net. Its current firmware is 1.00.60. Anything else I can try? Thank you.
reply
rcilink @ 6th May 01:41AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

If the RTP300 is not used with Vonage, do this:

WARNING: this will erase SIP settings! If you are using the box with Vonage, don't do this!

1. put a pencil or small object in to hold the reset button for about 60seconds. (notice power light starts to blink)..

2. Let go of reset button.

3. Give the reset button one more 'quick' press (do not hold this time). Let go of button.

4. Sit back and wait. You should find your box with the factory default settings..

After the 'factory reset'...
On the RTP300 / WRTP54g box from Vonage, this means:
- The Admin account will be locked (set at factory in config)
- The user account will have tivonpw as password, but is not enabled.
- The voice/Provision.html page will have info pointing your box to ti.tftp.vonage.net to get a base .XML config and firmware. Note the encryption key and path are there also.
- ALL SIP Settings are gone. Junk (factory set) is placed in there.

------
You have a couple of options at this point.
1. Download the plain-text XML a couple pages back on this thread and feed it to your box.

2. Let the box get its first XML config from vonage. It will open up the user account, so you can up/downgrade firmwares..

3. Grab the XML file from the provider and decrypt it. Then you will know your Admin password..

-------
Worst case... if nothing works as described above, you can hand-feed the Provision.html page with the correct values, save, and reboot (power cycle).. it should go grab the vonage XML at that point.
reply
vlan4 @ 6th May 11:17AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I did a long press and a quick press as above. But no luck. My RTP300 just sent out DHCP packets to obtain its IP, then kept querying PTR 0.0.0.0.in-addr.arpa. When I used my DNS server to responded it with any name, such as vonage.net, PTR queries stopped. No other packets observed then. Can't use tftp or http to communicate with rtp300 at this point. Any tips? And how to "hand-feed the Provision.html page"? Could you tell me the detailed steps? Thanks you.
reply
anon @ 8th May 12:53PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The methods mentioned in this forum to unlock the rtp300, can they be used on the rt31p2? Has anyone tried them on the rt31p2? Thanks.
reply
meister_sd @ 8th May 06:03PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Each device uses it's own firmware even though they reuse alot of the same code. The RT31P2 is being worked on in the other forum.
reply
tkprojects @ 8th May 06:06PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

RT31P2 has different architecture and no linux.
reply
speed_spec @ 22nd May 12:25PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

This is a great thread.

I have the RTP300 and leaving Vonage.
I am satisfied with the router as is, but I would like to disable the VOIP portion of it so it does not use my bandwidth.

Any simple way of disabling the VOIP portion or making it not use my bandwidth?
reply
rcilink @ 22nd May 04:43PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hmm, Up to you. If you wanted, you could load the rtp300-3-1-10.bin firmware on your RTP300 unit. Then, go into the Voice tab and set Line1 and Line2 to "off".

That should disable the voice stuff pretty good.

Also, if you ever wanted to use the voice later-on, you could easily have access to it.

IF you 'do nothing' and leave it 1.00.62-vonage, it will continue to check Vonage for updated provision files. The SIP registration will stop, and it will not use bandwidth for voice unless you plug a phone in and take it off-hook. (When not on an active account, it will be programmed to remain 'unregistered' and place a call to 666 when phone goes off hook. This will play a msg to you telling you that this port is not active and you might need to try the other phone port). When the phone is unplugged or hung-up, no registration packets are sent, so the Voice packet traffic should be close to none.
reply
rcilink @ 23rd May 12:19AM:
Some observations using RTP300 with 3.1.10 firmware

I'm not convinced that this firmware is useful with the RTP300 device..

I recently picked-up one RTP300 device from ebay. It was a USED device, with one active line on Vonage. From the looks of things, they have a 'not so great' way of dealing with closed accounts (lines don't get shut-off immediately, etc.)..

GOAL: Can I have LINE1 set to a vonage account, and LINE2 to any other service, all using RTP300-3.1.10 firmware?

So, I saved-off the Vonage configuration for LINE1 to a text file, for this test. No problem..

Now, I loaded the RTP300-3.1.10 firmware, being careful to not let it talk to Vonage and re-provision or downgrade to 1.00.62 firmware. No problem..

After loading that firmware, I performed the factory reset to clear/reset the FLASH to map the Sipura area, etc.

Under the 3.1.10 firmware, it reboots the device each time i save any voice setting. This is quite annoying! At first, I thought that the firmware was bad, so I hooked up the serial console cable. Nope .. it actually wants to reboot. Once in a while it will sneak out a 'rebooting, wait 30 sec.' or something like that web page, but most of the time as soon as you hit SAVE, it is booting..

So, I got all the vonage settings into the LINE1 area. Took me a little while to map across some of them, but they're in there.. After a reboot, LINE1 comes up! I can make calls on it..

I decided to configure LINE2 to my Asterisk box.. This was not successful. I am unsure if it was not happy with me having each LINE set to a different SIP server, or what the problem was.. I was not able to get the second line to see/talk to my Asterisk box at all..

So, to conclude this test, I loaded 1.00.62 back on the RTP300. I re-configured LINE1 with vonage and LINE2 to my Asterisk box. Amazingly, both work!!

So, I guess what this tells me is that we may be stuck using a 1.00.62 firmware for these devices... :( So, time to load up a -NA version of 1.00.62 for RTP300 ..

---

Has anyone else tested the RTP300 - 3.1.10 firmware and had better results? I would be interested to hear your results using each line for different providers, etc.
reply
anon @ 23rd May 01:12PM:
Re: Some observations using RTP300 with 3.1.10 firmware

Exactly the same things I'm seeing.

Just an FYI...I stumbled across version 1.00.64 sitting on the Vonage servers. It doesn't look like Vonage are rolling it out just yet and I have no idea what's changed...so use at your own risk.

Any chance is dissecting this one and making an NA version from it?

RTP300: »httpconfig.vonage.net/rt-11.1.0-···0502.img
WRTP54G: »httpconfig.vonage.net/wrt-11.1.0···0502.img
reply
rcilink @ 23rd May 03:53PM:
NEW 1.00.64 firmware

How on earth did you find this on the vonage servers?
(I know part of the filename is static, but the version number and date-code.... ) You must be on the 'inside'.

Anyway... The major changes are the HTML and javascript.. Found some mistakes in there also! :)

It is highly possible that the cm_* files are changed. I will verify this tonight.

I have not loaded it on a device yet, so will try that tonight for the actual test.

The SIP application (ggsip) does not appear to have changed.
reply
ptrowski @ 23rd May 03:56PM:
Re: NEW 1.00.64 firmware

Rcilink,
Once my number is ported over to Viatalk, if I don't have to return my rtp300 you are more than welcome to it...
--
Make a Difference-Join Team Helix!
reply
rcilink @ 23rd May 11:26PM:
Results: Firmware 1.00.64 loaded up..

So-far it is working fine..

I have yet to find anything exciting about this one.. The web pages showed-up different when I compared the package to 1.00.62.

I will say that the method of setting the Admin password is still doable, so it seems to be ok to use.

I have line1 configured for a Vonage account and Line2 configured for a local Asterisk account.

Here's a bug in the way this thing works... (This bug has been in all the recent firmware releases too): If you try to configure a LINE2 on one of these devices that previously showed "666" as the dialplan, it will have problems. I find that even if I erase and re-write the dialplan, it does not care. The '666' gets prepended to the outgoing number being dialed on that line.

The only way I have found to get rid of this bug is to do the factory reset option. This will wipe out all voice settings and you get to start over.

EDIT:
I just noticed that the 1.00.64 firmware 'phoned home' to vonage and grabbed the 1.00.62 firmware.. argh. I had provisioning changed to my server, so this seems to be a new behaviour.
reply
KillaB7 @ 23rd May 11:55PM:
Re: Results: Firmware 1.00.64 loaded up..

quote:
The only way I have found to get rid of this bug is to do the factory reset option. This will wipe out all voice settings and you get to start over.


Another nice way is to modify the tigeneric.xml file posted by czyz, encrypt it with your default RC4 key and have your router point to your local TFTP server.
reply
rcilink @ 24th May 01:47AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

NOTE: This is not for people with active VONAGE accounts! It is for those who are stuck with an old RTP300, no longer used with vonage.

With respect to the GPL, here we find a 1.00.64-NA firmware for the rtp300 unit. I am testing it now, and it seems stable at this point.

Some things to note:
1. SIP (voice) is unlocked
2. Admin PW is changable (sample provision.xml included at: »192.168.15.1/provision.xml)
3. Serial console does not require login (drops to shell prompt)
reply
rcilink @ 24th May 09:23PM:
For now...stay away from 1.00.64

I am beginning to see the differences with this .64 version..

So-far, I don't like it! I don't like it enough to remove the .64-NA firmware from the above post.. If someone can post, telling us that they got it to work (registered to a SIP service), I won't erase it. Otherwise, it will be trashed.

Some more observations:
Using .64, the Vonage line no longer works.. I downgraded to .62 and it started working again.. (not sure what that's about..)

I cleared the firewall and that did not help.. hmmm.

I see this entry in the serial console:
cfgmgr(voice): Sending EVT_REPORT_PROV_VOICE_READY

Does this mean that this version actually tries to 'talk back' to vonage??? If unsuccessful, it does not enable voice. (This is only a guess).

FYI: another difference I found is the eth interfaces. They got rid of the bridging that was partially set-up in .62 and prior.

reply
Evildude @ 26th May 03:33PM:
Re: For now...stay away from 1.00.64

If you can post the 3.10 modified for wrtp54g i'd like to try it. I cant get .62 to register correctly, and i dont need the wireless.
reply
sunray73 @ 26th May 08:34PM:
Re: For now...stay away from 1.00.64

First off... Great posts guys!!! So I just had a couple of questions on RTP300 and configuring it for VoipStunt.com(Since it's now free for all outgoing U.S. calls) Here is what I did so far:

1) I logged into the RTP300 and upgraded the firmware rtp300-3-1-10(I didn't have to do any of the sugestions in the first couple of pages of this forum for whatever reason)

2) I did a software reset and logged into the router's Voice Section.

Question is... what do I need to change in the configuration pages to have phone port 1 configured to work with VoipStunt.com? I am just afraid that I will screw up some of the configuration pages and not have anything work. Any help is GREATLY appriciated!

Thanks again!

***UPDATE***
I was able to get logged in once and made my first call but after that nothing... tried tried and tried some more and still nothing. I attached my config for voice if anyone could help that would be great!!!
Voice.zip 17,974 bytes
VoiceSettings
(Voice.htm)
reply
meister_sd @ 27th May 11:23PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

First off, congradulations rcilink!

It loaded just fine on my box and I'm going to test SIP soon. But I did try to SSH into it and the usernames don't work (admin/admin, Admin/[blank], root/[blank])
reply
anon @ 28th May 06:35AM:
Re: For now...stay away from 1.00.64

After alot of messing around with the newer versions, yes, it looks like it does, even if I force a provision update, it still tries to call back to vonage (on stock, and modified firmware), it tries DNS lookups, as well as direct IP's... It will even try to re-provision (and upgrade) after getting GOOD information... its a pain in the ass to get around this... I have not found a way yet, but I would think its in the image (grep for vonage.net, as well as other IP's that you will see with a TCPDump)

Other then that, good job on the firmwares... I've been enthused about this...
reply
sunray73 @ 28th May 07:13PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

So I finally got everyuthing running great. I have VoipStunt for outgoing calls on Line 1 and StanaPhone for incoming calls on Line to 2. I am now trying to foward calls from line 2 to line 1 as per this forum »216.109.125.130/search/cache?p=p···.intl=us and when I add the fowarding in User2 config page(username@myexternalipaddress:line1port#) and reboot I just get a fax sound when calling my stanaphone from my cell??? Not sure why this is happening. I also tried configuring it with the internal IP address as well as a loopback address. Any help on this would be GREATLY appriciated as I don't want to go and spend another $150 on a 2 line cordless phone for this setup. THANKS!!!
reply
toro @ 30th May 10:59AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

OK, so I must be the most stupid user on this list :)
I have all the .bin files posted here. I grabbed my encryption keys as well, I was able to download and decrypt my provisioning .xml files from Vonage (there are 2 of them referenced so I downloaded and decrypted both).
But I still have no clue how to upload the new firmware. I am guessing that I have to change the provisioning on the device and point it to a local spoofed TFTP server, but I don't really know how.
reply
rcilink @ 30th May 02:29PM:
Unlocking and Upgrading firmware on RTP300 or WRTp54G

Hmm, there are several ways to do this.. here is one way:

* Note: this method assumes your device is a Vonage device, and that it has recently provisioned itself with Vonage (It does not matter if it is an active account or not.)

*THIS METHOD IS NOT FOR ACTIVE VONAGE SUBSCRIPTIONS!!*
Steps:
1. Download the firmware for your device that you wish to upgrade your device with.

2. Using a web browser, open a page at: »192.168.15.1

3. Login (username=admin password=admin)

4. Change URL to: »192.168.15.1/update.html

5. At this 'login' screen, enter:
username= user
password= tivonpw

6. Follow directions to upgrade firmware that show on screen.

-----
IMPORTANT!
-----
If you are loading one of the firmwares described in this thread that 'unlocks' your device, you MUST reset it when the upgrade is complete!

(make sure the upgrade is complete, and it has presented you a login page)

Here's how to restore factory defaults:

1. use your favorite sharp object and press-and-hold the reset button on the back of the unit.

2. Eventually, the lights will flash in some random pattern.

If, per chance, you are too slow or decided not to do the 'factory reset' method described above, you will find that your firmware may revert back to 1.00.62 (vonage current).. This is because you did not remove the vonage settings (they go away at factory reset time)..

Good luck!
reply
toro @ 30th May 08:48PM:
Re: Unlocking and Upgrading firmware on RTP300 or WRTp54G

OK, that was silly of me. I just couldn't find that firmware update page. Thanks again rcilink
reply
toro @ 31st May 12:13PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Will this 3.1.10 firmware take old style XML provisioning files ? (like the one I downloaded and decrypted from Vonage for my MAC address) ? Or will it take PAP2-like XML provisioning files ?
I tried to set the provisioning to an HTTP address through Voice menu/Provisioning (same way I do it for PAP2 adapters) and it hasn't even tried to download the file from the server.
reply
rcilink @ 31st May 01:08PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Did you find success in configuring line1 and/or line2 in the voice section of 3.1.10 firmware for rtp300?

I finally dumped the firmware and went to 1.00.62-NA.
reply
toro @ 31st May 08:55PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mine appears to work OK if connected to the Internet directly (if it has a routable IP address on the WAN interface).
If I put it behind a router, it fails to register even if I use a STUN server and change some NAT settings the same way I do for PAP2.
reply
toro @ 31st May 11:13PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Looks like there's a bug in the 3.1.10 firmware when it comes to the STUN server. It resolves the external IP address with the digits in the reversed order. For example if the external IP is 1.2.3.4, the Info page shows the external IP as 4.3.2.1
reply
SteveLV702 @ 3rd Jun 10:20PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

how do you extract the .bin file in order to check it.. As I have tried a few programs that dont work...
reply
rcilink @ 4th Jun 02:07AM:
looking inside the wrtp54g (rtp300) firmware using Linux

The 'bin' file for these devices is a squashfs filesystem, along with the Linux boot and base system.

The easiest way to 'mount' it for review is to use your modified Linux kernel to mount the bin file.

For example, the mount command might be:

mount -t squashfs ./wrt-11.1.0-r021-1.00.62-r060327.img /mnt/wrtp-62
 -o loop,offset=0x90000
The cool thing about this mount command is that it will mount the squashfs portion of the firmware, skipping the kernel portion. No need to strip off the non-squash stuff..

Of course, this most likely will not work under a standard linux package... You need to patch the squashfs to handle LZMA and rebuild your kernel..

If you wish to 'make' a new squashfs suitable for using on this Linksys hardware, you will need to patch an older version of mksquashfs to handle LZMA.

The best (easy) suggestion to check firmware to determine if it is a good download would be to checksum it. Then, either checksum the same firmware from a known good source, or have someone checksum the firmware for comparison. Keep in mind that the firmware has been checksum'd before being made available. TI released a Linux tool called tichksum to do this for you. It is acceptable to run this tool on an existing firmware, and it will verify the checksum and tell you if it is OK, or needs to be changed. I do not advise you change the checksum unless you are fully aware of the firmware changes in the package you are working with.. It is easy to brick your device!

reply
anon @ 10th Jun 06:23PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

hi everyone, I stand in awe.

I bought a wrtp54g cause it was the only wireless one around, however, vonage won't take my number and viatalk might in the near future, do I need unlock it for viatalk? and if so, is there a step by step guide for someone who never actually signed up for vonage?

thanks
reply
rcilink @ 12th Jun 09:41AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Yup, you will need access to the SIP settings (voice tab) to make the device work with Viatalk.. If you can, try upgrading the firmware (»192.168.15.1/update.htm use username=user password=tivonpw). Put in the unlocked firmware and then do the factory reset.

As for a complete, concise how-to guide, I dont think that has been done for this device (partial, not complete)..

I guess I will have to throw something together.

I will post something here, when I have something worth posting...
reply
Evildude @ 12th Jun 11:03PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

well, post something, since i cant get my wrtp54g to register properly to anyone.
reply
rcilink @ 13th Jun 12:40AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I am curious what your wrtp54g v1.00.62 is doing...

Here's a 'quick' guide to get things in place using wrtp-1.00.62-NA firmware:

1. download the wrtp-1.00.62-NA firmware

2. Update wrtp device: (login and then use this link: »192.168.15.1/update.htm )
* Username = user - and - Password = tivonpw

3. Update is complete when it is not blinky LED.. Be patient.

4. Login.. Look at status page to verify firmware version.

5. In 'ADMIN' tab, do a factory reset of ROUTER and VOICE.
* Username = user - and - Password = tivonpw

-------------------------------
Notes:

If you can not use 'user' and the password listed above (it says account is not enabled), you will need to enable the account. See notes about how to do that (look for the XML to change Admin and user passwords in this thread).

Once the above steps are complete (including the fact reset), you can begin setting-up your SIP settings. Use the Voice tab to quickly get the setup complete.

The Provision settings will be changed after a Fact reset to generic IP (192.168.1.76) to avoid accidential change. If you wish to use provisioning, simply change the address to your provision server IP address-- it will work. (yes, it is possible to put the 'vonage' address in there, and it will bring your box live... using this unlocked firmware).

Please report back here if you experience troubles with this firmware version and setting-up SIP services.

I had my wrtp setup to work with my Asterisk box without any problems on this firmware version. (a side note: I did find problems using 1.00.64 release firmware with Asterisk..)
reply
Evildude @ 13th Jun 08:07PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The box is unlocked, as i have mentioned a few times, I cant get it to register either on my local sip sever or elsewhere. I need a copy of some successful settings so i can emulate them.
reply
anon @ 15th Jun 10:43PM:
sip creds

Excellent thread!

My goal from the begining was simply to extract my SIP credentials from my wrtp54g so I could use my Cisco 7920 IP Phone. My question is: Does vonage start to ask questions if they see you registered but hear nothing from your wrtp54g for a while?

Anyone every try this?
reply
ii904 @ 22nd Jun 12:26AM:
Re: WRTp54g unlocked 1.00.62-NA

I have tried this firmware and I found a problem with me when I tried to flash back to other firmware. When I click "Firmware Upgrade" enter user/tivonpw then can't show the upgrade page.just show bad username and password I don't know how to get the old firmware back to my unit.anyone may help?
reply
ii904 @ 22nd Jun 09:25AM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

anyone try this firmware ?looks like wrtp54g-NA verison. WRTP54G-NA - firmware v.3.1.14:
»www.dspring.com/podpora/fw/WRT54···1.14.bin
reply
ii904 @ 23rd Jun 11:09AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

look for the XML to change Admin and user passwords

anybody know how to do it?
reply
rcilink @ 23rd Jun 12:00PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Please see the post here: »[Vonage] SIP credentials, RTP300, GPP_K?

It resets passwords.
reply
ii904 @ 24th Jun 12:38AM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

rcilink thanks for reply.
I follow your guide ,
1. download the wrtp-1.00.62-NA firmware

2. Update wrtp device: (login and then use this link: 192.168.15.1/update.htm )
* Username = user - and - Password = tivonpw

3. Update is complete when it is not blinky LED.. Be patient.

4. Login.. Look at status page to verify firmware version.

5. In 'ADMIN' tab, do a factory reset of ROUTER and VOICE.
* Username = user - and - Password = tivonpw

now my wrtp54g running 1.00.62-na firmware,but I want update the voice section to rtp300 3-1-10.bin because I don't know how to setup to work with Asterisk box .but I know how to setup a sip account like FWD ,sipphone.so i want to update to rtp300 3-1-10 version.also I want to try this firmware .looks like wrtp54g-NA version. WRTP54G-NA - firmware v.3.1.14: »www.dspring.com/podpora/fw/WRT54···1.14.bin

So I login (username=admin password=admin) then Change URL to : 192.168.15.1/update.html ,At this 'login' screen, enter:
username= user
password= tivonpw
but it show can't login ,show bad user name.then I follow this guide :

I changed the Admin PW to be "Admin" and left the user pw as "tivonpw". Also, I assume your router to the net is at 192.168.15.1 I set DNS1 to that IP. Also, I put my TFTP and HTTP server IP to 192.168.15.100

The way this is written, it will do this:
1. The RTP300 will TFTP from 192.168.15.100 the file: ti001310000.xml (replace 0's with actual MAC)
here-------I put my xml file in solarwinds tftp server boot folder

2. The RTP300 will HTTP get (using WGET) from 192.168.15.100the file: /rtp300/rtp300-3-1-10.bin
here-----I put rtp300-3-1-10.bin in solarwinds tftp server boot folder

3. Set appropriate provision info.

4. Set Admin password to Admin and enable Admin

5. Set user password to tivonpw and enable user

6. Set idle timeouts to: user:5 and Admin:15

<provision "2">   
<options>
<reconfig/>
</options>
<settings>
<firmware>rtp300-3-1-10.bin</firmware>
<profileurl>tftp://192.168.15.100:69</profileurl>
<imageurl>http://192.168.15.100</imageurl>
<key>43731b1f3e73581f53e3bc5456929138dfd0a980e9ab066f5b148a9a073b1e24</key> 
<path>rtp300</path>
<interval>30</interval>
<intervalimg>120</intervalimg>      
<dns1>192.168.15.1</dns1>
<dns2></dns2>
<voicelog>notice</voicelog>
<logdest></logdest>
<sntp>time.vonage.net</sntp>
<tikeypub></tikeypub>
<timezone>STD5:0DST,M4.1.0,M10.5.0</timezone>    <adminpwd>Admin</adminpwd>   
<userpwd>tivonpw</userpwd> 
<userstate>1</userstate>    
<useridle>5</useridle>  
<adminstate>1</adminstate>   
<adminidle>15</adminidle>
</settings></provision>

looks rtp54g can get xml file from 192.168.15.100 (tftp sever) but user/tivonpw still can't login, also no firmware update.

I just need to know how to dump firmware on it.
rc, thanks for all your help so far
reply
rcilink @ 24th Jun 01:03AM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

two things to try:

1. In your XML, clear the "key" tag above.. it should look like:
<key></key>

2. When you update your Provision.html page, make sure you
leave the 'encryption key' field blank. put in the other meaningful data.

Let me know if this works.

reply
ii904 @ 24th Jun 11:40AM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

thanks rcilink

follow your guide ,I final get user/tivonpw. when I try update my wrtp54g to rtp300 3-1-10 firmware or WRTP54G-NA - firmware v.3.1.14 show invalid code pattern. now my wrtp54g still using 1.0062-na version.in voice part,it's old voice interface . i don't know how to setup to fwd.I still looking wrtp54g 3.1.10 version,like pap2 support stun .

thanks for advance
Click for full size
Click for full size
reply
ii904 @ 24th Jun 11:44AM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

thanks rcilink

follow your guide ,I final get user/tivonpw. when I try update my wrtp54g to rtp300 3-1-10 firmware or WRTP54G-NA - firmware v.3.1.14 show invalid code pattern. now my wrtp54g still using 1.0062-na version.in voice part,it's old voice interface . i don't know how to setup to fwd.I still looking wrtp54g 3.1.10 version,like pap2 support stun .
how do you do this? " Now I need to find this release for the WRTp54G and fix it up.. looks like a very nice release of firmware!

My wrtp54g is now running firmware version 3.1.10!" how?

thanks for advance
reply
lj00 @ 24th Jun 12:31PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hello first time poster, I successfully used the 3.1.0 firmware on my RTP300, though did not get it to connect to anything. I read another post that said the RTP300 could be unlocked via decrypting, editing, then re-encrypting the provisioning config xml. I played around with it but could not get rc4 to re-encrypt it using the same key as given in the default provision.html, I was hoping anyone could shed some light on this? Was there anything very particular I should have edited/removed before trying to re-encrypt it?
The syntax I used was the same as decryption,
(./rc4 {key} {edited.xml} {encryptededited.xml}

Also has anyone been able to get the 3.1.0 firmware working with FWD? If so could you post some pictures of the extended settings.
reply
rcilink @ 24th Jun 09:00PM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

ii904, The reason you are having trouble is the error displayed in your screen shot "Invalid code pattern".

This means you are trying to load a firmware that is not for the device. For example, you can not simply load a RTP300 firmware on the WRTP54g device, unless you edit the firmware and re-checksum it.

From what someone posted, there is a firmware 3.1.14 (I think it was that version) for the WRTP54g on a link above.. If I remember right, it has the wrong code pattern also, and won't load on a stock wrtp54g firmware.

I will have to take a look at it and change the code pattern, so it will load on our WRTP54g versions..
reply
KillaB7 @ 25th Jun 01:55AM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

Hey rcilink,

Would you be able to package up an 1.00.62-NA for the RTP300? 3.1.10 is too buggy for my liking and you don't recommend 1.00.64-NA.

3.1.14 sounds interesting. Perhaps it's more stable than 3.1.10?
reply
samuelyw @ 25th Jun 11:12PM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

Can anyone tell me how to downgrade 1.00.64 firmware to 1.00.62? thank you!
reply
samuelyw @ 26th Jun 11:21PM:
Re: wrtp54g with wrt1.00.62-NAr6.bin

it downgraded to 1.00.62 already.
reply
rcilink @ 27th Jun 01:32AM:
RTP300 1.00.62 Firmware

Well, I felt that the 1.00.64-NA for RTP300 was a bum deal..

So, here is a 1.00.62-NA (unlocked) for RTP300.. it even works!

I have tested it with sipdiscount, and I can tell you it works nicely.

Same rules as before. If you are a customer and the RTP300 is in use with a VOIP company, you should not be messing with it!!

If you recently quit the provider, and they told you to toss the box, then load this up and see what you can do..
reply
samuelyw @ 28th Jun 12:27AM:
Re: RTP300 1.00.62 Firmware

Is this rtp300 1.00.62 firmware also works for wrtp54g?
reply
rcilink @ 28th Jun 01:19AM:
Re: RTP300 1.00.62 Firmware

said by samuelyw :

Is this rtp300 1.00.62 firmware also works for wrtp54g?
(unlocked firmware, based on traditional 1.00.62 release)

For the WRTP54G, use this firmware: »/r0/download/1···NAr6.zip

For the RTP300, use this firmware: »/r0/download/1···2-NA.zip
reply
wayneconnor @ 28th Jun 10:13PM:
Re: RTP300 1.00.62 Firmware

Is there another link to this where I can download it,
it is not letting me download it from here.

or can you email it?
I'm after the wrtp54g-na firmware.
Thanks,
Wayne
reply
niel8 @ 29th Jun 07:29PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

hey guys, i have RTP300 and i am looking for that 3.1.10bin, can somebody please provide me with it? plssss, ma email is niel.pancholi@yahoo.co.uk many many thnx.
reply
niel8 @ 29th Jun 07:36PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

hey man. can i have that 3.1.10 bin plsssssssss? i need that one to unlock mine. thank you.
reply
ii904 @ 30th Jun 12:06AM:
Re: RTP300 1.00.62 Firmware

nobody find a WRTP54G unlock version of 3-1-xx here?
reply
niel8 @ 30th Jun 01:11PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

hey guys, i have rtp 300, i dont see upgrade firmware option anywhere, any comments pls? i am trying to upgrade to 3.1.10 firmware. i got the file. how do i upgrade? can someone provide me with step by step information? i m a newbie,, learning how to deal with this router, thanks a lot.
reply
anon @ 30th Jun 09:22PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Update rtp300 device: (login and then use this link: »»192.168.15.1/update.htm )
* Username = user - and - Password = tivonpw
reply
niel8 @ 3rd Jul 02:59PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

i tried it, it says the requested url is not available on server :(
reply
anon @ 3rd Jul 11:30PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

if ".htm" doesn't work. try ".html",
try: »192.168.15.1/update.html
reply
darthschrade @ 8th Jul 12:54AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

This may be a stupid question, but how do I install the firmware update? I've read everything here and just can't figure that part out. Help please!
reply
darthschrade @ 8th Jul 04:33PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Ok, I had a heck of a time figuring this out, so here it is for all the not-so-tech folks out there who don't fluently speak this strange language here (no offense intended to all you guru's here, because the rest of us love you, we just don't always understand you!). Ready??!!
IMPORTANT, BEFORE DOING ANY OF THIS, MAKE SURE TO DOWNLOAD THE FIRMWARE VERSION FOUND IN THIS FORUM, UNZIP IT AND SAVE IT! RTP300-3-1-10.ZIP
1. Login to the RTP300 at »192.168.15.1 using admin for the user name and password
2. In internet explorer, go to tools, internet options, security, custom level, and scroll down to Active Scripting and click disable. Save and close.
3. Go to »192.168.15.1/upgrade.html
4. For username - user, for password - tivonpw.
5. Since you've already extracted the zip file with the firmware upgrade (you have already done this, right?), and saved it to a location you can find, just browse for the file and upgrade the firmware! Easy as pie!

Thanks to all the guru's out there who have gotten me and the rest of the tech wann-a-be's this far! You're awesome! Now if I can just get all the settings right to make this thing have a dial tone I'd throw a party! Let the real fun begin! Good luck to you all!
Get more voip info... voip@keepwhatyoumake.com
rtp300-3-1-10(2).zip 3,109,508 bytes
reply
rcilink @ 9th Jul 07:40PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Thanks for the upgrade steps.. I am sure people will appreciate your work.

I would suggest using 1.00.62-NA firmware. It is stable. The 3.1.x firmware seems to have unstable voice functionality..

The -NA firmwares can be found here.
reply
darthschrade @ 9th Jul 08:19PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Can you go from the 3.1.x to the 1.00.62-NA?

Thanks for the thanks...I've started selling voip now, and I've learned what a pain Vonage can be when you want to leave! Not only do they lock the ATA, but I was unaware that If I didn't stay for one year I pay an additional $40 cancellation! As far as I'm concerned, Vonage is not the way to go...too many better options out there, probably even some better than mine. At least we don't lock the ATA. So anything I can do to help ex vonage customers is my pleasure.
reply
niel8 @ 11th Jul 03:03AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

hey guys try this out, »www.dd-wrt.com/wiki/index.php/DD···%28EN%29
should work, i couldnt try since i dont have that wireless router, i unlocked rtp 300 tho with help of meister_sd and rcilink, lemme knw if it works or not, i wanna buy one of them if it does.
reply
anon @ 14th Jul 10:54PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have been using 1.00.62-NA on the RTP300 and am having some issues

1) I have to press # after dialing my number before it even tries my Asterisk server, this started after the upgrade from the old 3.1.10 firmware

2) It seems my Line 1 will not properly connect and stay connected, after a while it says "Proceeding" in the status page, even after it has previously connected....

This TA connects locally to my asterisk server, the config for line 1 and line 2 are the same, except user/pass/callerid...
reply
faskas @ 16th Jul 11:37AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Can you plz tell me step by step how to flash Linksys RTP300 with firmware 1.00.62. I will really appreciate your help. fahadshah@msn.com

Thanks
reply
damialok @ 19th Jul 12:10AM:
wrt 1.00.62 firmware Termination digit

I upgraded my wrtp54g with the 1.00.62-NA firmware provided in this thread. I then hooked up this with my asterisk server and I can make calls fine now. But all my calls require me to enter a termination digit '#'. Also I am not sure how to read the Digit Map. I would appreciate if someone can provide any insight into how to modify these so that I dont have to enter a termination digit. Here are my settings.

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

Termination Digit:#
Partial Digit Timer:16 secs
Critical Digit Timer:4 secs
Dial Timeout:30 secs

Also I see no Voice profiles. If that ok? I would like to use g729a as my codec but the Voice Coding Profile : PCMU
I am not sure if that 'PCMU' profile includes g729a.

Please help....
reply
tkprojects @ 19th Jul 02:05AM:
Re: wrt 1.00.62 firmware Termination digit

said by damialok :

I then hooked up this with my asterisk server and I can make calls fine now. But all my calls require me to enter a termination digit '#'.
I don't know what a T is, I suspect it is the termination digit. BTW, the default Linksys interdigit timers are typically 3 and 10, not 4 and 16. Have you actually waited 16 seconds after putting in the last digit to make sure that you really have to dial a # to complete the number?

If you don't care about the * codes and use a service provider using NANP, this dial plan will probably work for you:

1[2-9]xx[2-9]xxxxxx|011x.T

dialing the first 1 is kind of a waste in this plan, so unless you're used to dialing all the "domestic" numbers through 1 I would suggest to try:

[2-9]xx[2-9]xxxxxx|011x.T

In both instances you will need to dial a # to dial "international" calls. You may also want to try putting an S0 in front of the |. In other Linksys boxes that reduces the interdigit timer locally to 0 meaning that the call is placed immediately after dialing the last didit preceeding the S0. This will only affect dialing "domestic" numbers.

You can prepend the dial plan with:

*xxT|*1xx|

to enable using star codes like *12# or *123.
reply
niel8 @ 19th Jul 08:22AM:
Re: wrt 1.00.62 firmware Termination digit

have you guys found a way to make WRT54G work> with its wifi radio functionality? if not would anyone like to try this one? it has a firmware thats seems like NA and it shows how to flash wrt54g, »www.dd-wrt.com/wiki/index.php/DD···%28EN%29
reply
tkprojects @ 19th Jul 01:00PM:
Re: wrt 1.00.62 firmware Termination digit

said by niel8 :

have you guys found a way to make WRT54G work> with its wifi radio functionality? if not would anyone like to try this one? it has a firmware thats seems like NA and it shows how to flash wrt54g, »www.dd-wrt.com/wiki/index.php/DD···%28EN%29
The WRTP54G and the WRT54G are two different routers with substantially different although perhaps somewhat similar firmware, but substantially different functionality.
reply
damialok @ 19th Jul 01:50PM:
Re: wrt 1.00.62 firmware Termination digit

said by tkprojects :

BTW, the default Linksys interdigit timers are typically 3 and 10, not 4 and 16. Have you actually waited 16 seconds after putting in the last digit to make sure that you really have to dial a # to complete the number?

1[2-9]xx[2-9]xxxxxx|011x.T

[2-9]xx[2-9]xxxxxx|011x.T

You may also want to try putting an S0 in front of the |. In other Linksys boxes that reduces the interdigit timer locally to 0 meaning that the call is placed immediately after dialing the last didit preceeding the S0. This will only affect dialing "domestic" numbers.

You can prepend the dial plan with:

*xxT|*1xx|
Thanks very much for your input. I think I can change the Digit Map and see if that helps. Also I did wait for 16 secs and I get a slow busy signal and the call does not go through. So a Termination Digit is required for Long Distance.

Do you know if the PCMU profile includes the g729? If not what profile would I need to use to enable g729a. And if I need to create a new profile how do I do it?(I am assuming that not gonna be easy).
Thanks again for your help.
reply
tkprojects @ 19th Jul 03:34PM:
Re: wrt 1.00.62 firmware Termination digit

said by damialok :

Thanks very much for your input. I think I can change the Digit Map and see if that helps. Also I did wait for 16 secs and I get a slow busy signal and the call does not go through. So a Termination Digit is required for Long Distance.
I think I just used the standard Linksys dial plan on an RT300, but I was walking someone through the steps so I have no idea how the interface looks and I wasn't aware of the termination digit setting. A simple plan, if configured for use for NANP dialing would look like this:

([2-9]|*xx|[2-9]xx[2-9]xxxxxxS0|011[2-9]xxxxxxxxx.)

If you use FWD I think you need to rewrite the numbers add some asterisk madness. In general the numbering/renumbering schemes of many VoIP providers are a cluster f@(& that should be standardized ASAP.

As far as codecs, check the Line 1 and Line 2 tabs in advanced administrator mode to select which are available and which should be the default.
reply
mogulman @ 19th Jul 04:19PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Ok... so I had already installed 3.1.10 on my RTP300. Now I wanted to try the 1.0.0.62-NA firmware.

unfortunately user/tivonpw isn't working for the password for firmware upgrades. Anyone know what it gets changed to?

Doh.. it was Admin/..
reply
samuelyw @ 19th Jul 10:26PM:
Re: wrt 1.00.62 firmware Termination digit

I have the same setting as you, but I don't have this dialing problem.
I read some threads said that the "T" is waiting 4 seconds to send out the number you dial.

My problem is I need to dial US number with 1, if I don't dial 1, it can't go through.
I want to make a dialplan that can let me dial US number without dialing 1 or dial US local number without dialing 1 and area code,
like:
<:1>[2-9]xx[2-9]xxxxxx|<:1212>[2-9]xxxxxx

but it can't work for me.
Someone has any ideal for this?

For the dialplan that has "S0", it can't work at my wrtp54g.

reply
soufan5 @ 20th Jul 01:12PM:
Unlocking Linksys PAP v2 FW 1.00.13

Hi,

Im trying to unlock a Linksys Pap2 V2 adapter. Based on this thread, Im getting a feeling that it can be unlocked like the RTP300.

I downloaded the ti0000000.xml from ti.tftp.vonage.net.

I could not get the provision key based on the suggestion given(disabling java script...and going to the specified url). I did get the source for the html page as suggested. but it did not have the key.

Few of you did decrypt the ti000.xml without a rc4 key. You mentioned that you used a default key. Im not sure what default key should I use. The compiled rc4.c requires a key and Im not sure what to enter in that.

Any suggestions?
reply
rcilink @ 20th Jul 01:32PM:
Re: Unlocking Linksys PAP v2 FW 1.00.13

I posted a response in another thread that includes how to unlock the RTP300 and/or WRTP54g devices..

Take a look at: »[ViaTalk] RTP300 1.0.0.62-NA firmware with Viatalk

and look for my post.

Let us know if this does not make it easier..
reply
tkprojects @ 20th Jul 03:24PM:
Re: wrt 1.00.62 firmware Termination digit

said by samuelyw :

I want to make a dialplan that can let me dial US number without dialing 1 or dial US local number without dialing 1 and area code,
like:
<:1>[2-9]xx[2-9]xxxxxx|<:1212>[2-9]xxxxxx

but it can't work for me.
Someone has any ideal for this?
That doesn't work most likely because the match is ambiguous after the 7th digit, i.e. a shift/reduce conflict. Let me explain, you put in the first 7 digits where the 4th digit is 2-9 and then the parser finds a match, the dillema is whether to shift (i.e. wait for another digit or for expiration of the timer) or reduce (i.e. prepend the number with 1212). In theory the developers at Linksys/Sipura could have - probably should have based on the documentation for PAP2 and RT31P2 - handled it by a shift, but since it doesn't work for you it appears that they decided no to do so, but rather to return an error.

I thought I ran into this behavior in another context where I thought that e.g. 1900! barred the user from dialing a 900 number although it should have waited for additional digits to make that decision. If in fact it worked (I need to verify now), it is a somewhat useful bug because it shortens the length of the dial plan in some instances.

One way to "fix" it would be to determine whether your provider requires you to start long distance numbers with a 1. If not then you can input the 1 by yourself for long distance (afterall it is only 1 extra digit), but have the system prepend the area code when there is no 1 at the beginning, for the local area codes. Thus, the dial plan would be:

(1[2-9]xx[2-9]xxxxxx|[2-9]xxxxxx)

If you can post a reference to the meaning of "T" I will be grateful.

reply
samuelyw @ 20th Jul 09:42PM:
Re: wrt 1.00.62 firmware Termination digit

said by tkprojects :

If you can post a reference to the meaning of "T" I will be grateful.
»voxilla.com/index.php?name=PNphp···start=30
and »www.teledex.com/documents/ip250d···reva.pdf
reply
tkprojects @ 21st Jul 04:30PM:
Re: wrt 1.00.62 firmware Termination digit

said by samuelyw :

»voxilla.com/index.php?name=PNphp···start=30
Thanks!

The T means "wait 4 seconds to timeout"
Now, what does this mean? Does it mean it is a 4 second pause or is it some interdigit timer? Can someone test it experimentally? I don't have an RTP300 around me.

On the Sipura/Linksys a 'P' followed by a digit and a space is a pause AFAIR.
reply
emuman100 @ 30th Jul 10:19PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Holla234234,

The Cisco 7920 only uses SCCP, not SIP unfortunately. I wish they would release SIP firmware for the 7920, it's the best wifi phone currently out there, and i doubt any phone will beat it. I use the 7912 with Vonage that I got by unlocking my PAP2. Works beautifully!
reply
rmanaka @ 9th Aug 11:36PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Just an noob, but I think I got my WRTP54G unlocked...at least it indicates Firmware Version: 1.00.62-NA and I can get to the Voice pages OK.

Can't seem to get dial tone from Voice Pulse's Open Access Plan, however.

If I keep the Provisioning page to its default Provisioning Profile Base URL and Image Firmware Base URL, my Voice System Log says:

0001363065 - AUTH_USER_NAME
0001363065 - CID_NUMBER
0001363065 - CID_NAME
0001363065 - FCODE_CALL_RETURN
0001363065 - FCODE_DND
0001363065 - FCODE_ANON_UNBLOCK
0001363065 - FCODE_ANON_BLOCK
0001363065 - FCODE_CW_DISABLE
0001363065 - FCODE_CID_UNBLOCK
0001363065 - FCODE_CCFWD
0001363065 - FCODE_CFREACT
0001363065 - FCODE_CFN
0001363065 - FCODE_CFB
0001363065 - FCODE_CFU
0001363065 - SRTP_MASTER_KEY
0001363065 - PORT_1_CONFIG
0001363065 - FCODE_VMAIL
0001363065 - FCODE_CALL_RETURN
0001363065 - FCODE_DND
0001363066 - FCODE_ANON_UNBLOCK
0001363066 - FCODE_ANON_BLOCK
0001363066 - FCODE_CW_DISABLE
0001363066 - FCODE_CID_UNBLOCK
0001363066 - FCODE_CFREACT
0001363066 - FCODE_CCFWD
0001363066 - FCODE_CFN
0001363066 - FCODE_CFB
0001363066 - FCODE_CFU
0001363066 - SRTP_MASTER_KEY
0001363066 - NMM: XML file un-repairable
0001363066 - NMM: xml_parse_configure -VOICE_XML PARSE ERROR
0001363066 - NMM: voice_config: Other character expected (146):#60;:1>[2-9]xx[2-9]xxxxxx{/DIGIT_MA



If, however, I set the Provisioning Profile Base back to "tftp://ti.tftp.vonage.net:69,21,2400" and the Image Firmware Base to "http://httpconfig.vonage.net", the voice section seems to come alive but won't give me dialtone. The Voice System Log now says:


0000510001 - Content-Length: 0

0000510001 -
0000510008 - SSMU_RVREG 10159d1c, Srv=0, HostName=0, IpAddr=0
0000510008 - SSMU_RVREG 10159d1c, dest resolved IP=64.61.93.33
0000510013 - SSMU: 0 {--- Message Recd:
0000510013 - SIP/2.0 404 Not found
0000510013 - From: {sip:1@access1.voicepulse.com;transport=UDP};tag=87685144-2710-44daa8fa-f1ad0-454de667
0000510013 - To: {sip:1@access1.voicepulse.com;transport=UDP};tag=as040aaaaf
0000510013 - Call-ID: 87685144-2710-44daa51d-266-6d6f222a
0000510013 - CSeq: 99 REGISTER
0000510013 - Via: SIP/2.0/UDP 68.81.104.135:10000;received=68.81.104.135;branch=z9hG4bK-44daa8fa-f1ad0-1908ac14
0000510013 - User-Agent: VoicePulse SW
0000510013 - Max-Forwards: 70
0000510013 - Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY
0000510013 - Contact: {sip:1@64.61.93.33}
0000510014 - Content-Length: 0
0000510014 -
0000510014 - SSMU_RVREG Registration Failed, 10159c58
0000510025 - SSMU: 1 {--- Message Recd:
0000510025 - SIP/2.0 404 Not found
0000510025 - From: {sip:2@access1.voicepulse.com;transport=UDP};tag=87685144-2710-44daa8fa-f1af8-3e488203
0000510025 - To: {sip:2@access1.voicepulse.com;transport=UDP};tag=as040aaaaf
0000510025 - Call-ID: 87685144-2710-44daa51d-266-6d6f222a
0000510025 - CSeq: 100 REGISTER
0000510025 - Via: SIP/2.0/UDP 68.81.104.135:10000;received=68.81.104.135;branch=z9hG4bK-44daa8fa-f1af8-6dce7580
0000510025 - User-Agent: VoicePulse SW
0000510025 - Max-Forwards: 70
0000510025 - Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,SUBSCRIBE,NOTIFY
0000510025 - Contact: {sip:2@64.61.93.33}
0000510025 - Content-Length: 0
0000510025 -
0000510026 - SSMU_RVREG Registration Failed, 10159d1c


Any suggestions? Thanks!
reply
rcilink @ 9th Aug 11:57PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

that is telling you that the dial plan is invalid. here is a dial plan for this device:

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

Give that a try and put in the voicepulse proxy info.. it should work for ya. If not, post here.

reply
rmanaka @ 10th Aug 03:39PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The dial plan fixed the previous errors, but for the life of me I can't get line1 to register with Voicepulse.

Here's my current voiceSyslog:


0000009193 - Incorrect format for tone OFFHOOK_NOTICE
0000009193 - Incorrect format for tone OFFHOOK_ALERT
0000009193 - Incorrect format for tone CW1_TONE
0000009193 - Incorrect format for tone CW2_TONE
0000009194 - NMM: ACTIVATING VOICE_APP
0000009197 - NMM: 0, Switched CAS, FXS Loop Start
0000009197 - NMM: 0, Set Channel State UNCONFIGURED Done (SUCCESS)
0000009198 - NMM: 0, Channel Config Done (SUCCESS)
0000009214 - NMM: 0, Set Channel State NORMAL Done (SUCCESS)
0000009215 - NMM: 1, Switched CAS, FXS Loop Start
0000009215 - NMM: 1, Set Channel State UNCONFIGURED Done (SUCCESS)
0000009215 - NMM: 1, Channel Config Done (SUCCESS)
0000009216 - NMM: CID number absent for tcid 1. Not registered
0000009231 - NMM: 1, Set Channel State NORMAL Done (SUCCESS)
0000009232 - SSMU: created profile rtp maps #=11
0000009232 - SSMU Opening Firewall for RTP port 10050 - 10151
0000009260 - ============================================================
0000009260 - SSMU Inited RV SIP Stack Version 3.0.5.1 successfully!!
0000009260 - ============================================================
0000009271 - SSMU: created profile rtp maps #=11
0000009272 - NMM: 0, Set Channel State DOWN Done (SUCCESS)
0000009278 - NMM: 1, Set Channel State DOWN Done (SUCCESS)
0000009293 - SSMU_RVREG Registration Failed, 10195cec
0000009294 - NMM: unregister sip phone 2155253205 (tbl indx 1): FAILED
0000009328 - NMM: ATPM Update Database Granted OK
0000009329 - NMM: ATPM Update database done OK
0000009344 - NMM: 0, Set Channel State NORMAL Done (SUCCESS)
0000009365 - NMM: 1, Set Channel State NORMAL Done (SUCCESS)
0000009368 - SSMU_RVREG Registration Failed, 10195db0
0000009369 - NMM: register sip phone 2155253205 (tbl indx 1): FAILED
0000009370 - NMM: CID number absent for tcid 1. Not registered
0000009428 - NMM: voice_app activation DONE


According to Voicepulse support, I should only need three parameters:

Login: s123456789
Password: p1a2s3s4
Host: access1.voicepulse.com:5060

I've tried just about everything I can think of without success. I assume that I don't have to put the port number in the URL box for the registrar and/or proxy, but I've tried it anyway...I've also tried putting in the IP address of the host (64.61.93.33) just in case the Vonage DNS servers are blocking other VOIP servers. I've put in a comcast DNS server IP in the SIP page.

Any other thoughts?

I am also assuming that the INVALID tone formats aren't causing any fatal errors!

Thanks!
reply
DJ Vonage @ 10th Aug 10:33PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

heheh sorry but we are well aware of this allready ;)
reply
rmanaka @ 11th Aug 09:05AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Does that mean that even with the loaded 1.00.62-NA the router is still "locked" for registration purposes? Just want to confirm this before I purchase a new router/ap and a PAP2-NA!

Seems like a good reason NEVER to purchase a co-branded piece of equipment.
reply
rcilink @ 11th Aug 09:23AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rmanaka :

Does that mean that even with the loaded 1.00.62-NA the router is still "locked" for registration purposes?
No, the 1.00.62-NA simply means:

- the owner of the device will have full access to all menus, configurations, etc. (including VOICE)

- the firmware still can be setup to be provisioned, if desired. By default, it is disabled (with bogus destination info).

- the firmware can be reloaded to a non '-NA' version at any time (can't imagine why anyone would want to do this?!)

- the -NA firmware should be able to register with most any SIP provider.
reply
tkprojects @ 11th Aug 12:26PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Well, the problem may be that you're putting in 2155253205 for your login rather than the s123456789 that you told us is your login.
reply
tkprojects @ 11th Aug 12:29PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by DJ Vonage :

heheh sorry but we are well aware of this allready ;)
It only took 4 months. ;)
reply
rmanaka @ 13th Aug 04:08PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks for your reply!

I only put the 2155253205 in the Caller ID Number field, whereas the s123456789 is in the User Name field (actual username obviously). My password is in the Password field and both the Proxy Server and the Registrar Address fields have the host url, access1.voicepulse.com.

If I try to put the user name "s123456789" into the Caller ID Number field, the router will drop the leading "s" and will still fail to register the account.

In my SIP tab, I still have localhost in the Proxy Server field (127.0.0.1) but I have also tried access1.voicepulse.com to no avail. I have the voicepulse url in the Registrar address on this page.

Any other suggestions appreciated!
reply
rmanaka @ 13th Aug 06:53PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

That's great! Still trying. If I look at the firmware upgrade page, the password area no longer works, i.e. admin/admin, Admin/, user/tivonpw. I guess there's an .xml push that would fix this but it's a bit beyond me right now...

Thanks!
reply
tkprojects @ 14th Aug 12:05AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rmanaka :

If I try to put the user name "s123456789" into the Caller ID Number field, the router will drop the leading "s" and will still fail to register the account.

In my SIP tab, I still have localhost in the Proxy Server field (127.0.0.1) but I have also tried access1.voicepulse.com to no avail.
Skip the CID stuff for the time being.
The only thing you need is username, password, and the proxy which should be set to your VSPs host, not localhost. Also, set register to Yes.

Oh, and connect the ATA instead of the router if you can, to eliminate routing/NAT issues. Once you get it working this way put it behind the router and perhaps change the outbound proxy/use outbound proxy settings to accomodate the router, if necessary. All these settings refer to Line 1/Line 2 tab depending on which line you're configuring.

BTW, I'm going off a PAP2 because temporarily don't have access to an RT300, but the menus are extremely similar.
reply
rmanaka @ 14th Aug 12:36PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hmmm...we may be talking about two different beasts...the configuration pages look totally different between my WRTP54G (which I'm trying to get registered) and my Linksys SPA-2002 which is registered (albeit locked) to VoicePulse.

Here are the two main SIP pages on the router:

If I don't put entries is the Caller ID number and Caller ID Name fields on the Line 1 tab, the router won't even try to register the line!

Since the SIPs are internal to the WRTP54G, I can't move the "ATA" behind the router, although a SPA-2002 ATA is working just fine "behind" the WRTP54G.

The Voicepulse Open Access account is fine as I can register both an XTEN X-Lite 3.0 and a Nero SIPP softphone with this account.

Thanks.
Click for full size
Line 1 tab
Click for full size
SIP tab
reply
tkprojects @ 14th Aug 02:24PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rmanaka :

Hmmm...we may be talking about two different beasts...the configuration pages look totally different between my WRTP54G (which I'm trying to get registered) and my Linksys SPA-2002 which is registered (albeit locked) to VoicePulse.
Hmmm, the configuration pages seem to look different from the RTP300 I last configured, which is weird because I thought that they used similar firmware. Also, the screens you show seem to be a little light on options, e.g. they don't let you choose prefered codec. Did you log in as administrator into the box? If not, perhaps there is a setting in the Admin settings, e.g. Use Authenticate ID, which prevents you from successfully authenticating.

The procedure with which I am familiar is:

Login into the box as admin
username: admin
default password: admin

Click on "Voice"

Click on "Admin Login"

Click on "Line 1" or "Line 2"

Start configuring

---

As for moving the box in front of the router I meant moving the entire box in front of any other router you may have or may have had. It's not unusual for people to hook up a router/ATA combo device behind another router which does NAT and thus greatly complicates the setup.

P.S. If you're going to post screenshots, try to save them as jpegs or gifs which will reduce their size (not dimensions). The bmp was about 4MB in size.
reply
rmanaka @ 14th Aug 02:59PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks for the reply!

The WRTP54G is connected to the modem only through a Hawking HBB1 Packet Prioritizer so there isn't any other NAT translation/traversal involved.

I logged in as admin/admin, but there still might be an unenabled Admin login as the "Firmware Update" tab in Administration now generates a bad user response. If I click on Voice, however, there is no additional prompt for password or login.

There is a set of "Preferred CODEC" fields on the Line (1 & 2) tabs, but their entires are beyond me ! :-)

I guess the firmware is quite different from a SPA-2000/2002/PAP2 as the dial string which was provided by VoicePulse for a Linksys/Sipura device completely blew out the configuration (see my first post).

Sorry about the bmps...if I can edit the message I'll upload jpgs.

[added by Edit] sorry, looks like I can't kill the previous uploads, only add to them (won't burn anymore bits)...
reply
tkprojects @ 16th Aug 06:38PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rmanaka :

I logged in as admin/admin, but there still might be an unenabled Admin login as the "Firmware Update" tab in Administration now generates a bad user response. If I click on Voice, however, there is no additional prompt for password or login.
I'm sorry. I hate to give you any more directions for fear that I'll be just leading you astray. I don't have a WRTP54G and currently I don't even have access to an RTP300. I'm doing most of it from memory which is scant because once I configured the RTP300 it just worked. Once an RTP300 or a WRTP54G comes across my bench I'll try to give you some better pointers.
reply
rmanaka @ 16th Aug 07:46PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks, I appreciate your help!

So far it will only get to the point of registering, generating dial tone, busy, etc. but the registration will fail. It might be particular to VSPs such as Voicepulse that use a letter in their username and the Vonage WRTP54G's peculiarity.

I'm hoping that the Linksys release 3.1.17-NA firmware (now available on the Linksys website) will solve this issue, but so far I'm getting a BAD CRC error when trying to update. I don't have a CRC routine here to recalculate the CRC after patching the CYWM->CYWL product ID in the image!

So...until someone can calculate a valid CRC for this patched image, I think I'm stuck at the moment.
reply
tkprojects @ 16th Aug 09:11PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by rmanaka :

It might be particular to VSPs such as Voicepulse that use a letter in their username and the Vonage WRTP54G's peculiarity.
The RTP300 I spoke about is being used with an account that uses alphabetical characters. Though, it does not have any numeric characters. I'm not sure that that would be a problem.
reply
rcilink @ 16th Aug 09:57PM:
Getting a WRTp54G to take 3.1.17-NA...

If you have tried to load up the WRTp54G with version 3.1.17-NA firmware from Linksys support and it does not take (says wrong code pattern), have a look at this:

For this project, you will need:

- a copy of wrtp54g_fw_3.1.17_US.img (get it from www.linksys.com)
- a good HEX editor
- a Linksys WRTp54G device (no, this does NOT work on a WRT54Gp2!)
- the ability to access /update.html (you must know the password)

Here's what to do:

Open the wrtp54g_fw_3.1.17_US.img file using your favorite HEX editor.

1. Change HEX offset 23 from 4D to 4C.

2. Change the last four bytes to: AB 3A 49 5D

3. Save your new file.

4. Update the firmware on your WRTp54G (/update.html) to the new firmware.

Very Important!!! Let the firmware upgrade complete!!! Do not close the web browser session! Eventually (1-2 minutes) it will load the login screen of your WRTp54G device.
If you interrupt this, you may brick your device!

One last note, you may need to do a factory reset to rid yourself of any left-over params from the former use.. I did not have to do that, so the admin password was retained, along with the router settings. The voice section lost all of the settings, as it loads a different SIP engine (resembles the Linksys PAP2).

The new Admin password is blank (nothing in the password field). This is only needed for the /update.html page on firmware 3.1.17-NA.

Good luck!!
reply
KillaB7 @ 16th Aug 10:26PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Thanks rcilink as always!

Would you be able to post an MD5 for the modded file so people don't screw this one up (myself included).

I'm assuming this one acts like a Sipura/PAP2 vs. 1.00.62-NA?
reply
rcilink @ 17th Aug 12:25AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Sure, the MD5 for the firmware (after the above mods are done) should be: 611eb9063d2c9c8ff2e34826c1a376e2

It does have a PAP2 SIP module, unlike the 1.00.62 versions.

I was pleased to see it is more stable than the 3.1.3 and older versions we played with in the past...
reply
rmanaka @ 17th Aug 12:32AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

This is really, really great. Thank you rcilink!!! Version 3.1.17 is indeed running like a SPA-2002/PAP2 as I just reinitialized the router and then added a "Voicepulse" recommended dial plan for the SPA-2002:
(x#|xx#|*821[2-9]xx[2-9]xxxxxx|*82011x.|*xx|*1xx|[3469]11|0|00|1[2-9]xx[2-9]xxxxxx|011x.|[2-9]xx[2-9]xxxxxx)
This string blew the 1.00.62-NA firmware out of the water, but its working just fine in 3.1.17!

I think the Vonage WRTP54G is really open now! :D

reply
ii904 @ 17th Aug 01:03AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

hi rcilink, would you upload your modded file ?because I don't know how to do it.Thanks in advance!!
reply
ericolsendsl @ 18th Aug 04:55PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

hi rcilink:

How did you get your RTP 300 to work with sipdiscount.com? I upgraded my RTP300 firmware to 1.00.62-NA and tried their test account with no success.

Their test settings are below:

SIP settings:
User Name: test
Password: test
Domain/Realm: sipdiscount.com
SIP Proxy/registrar: sip1.sipdiscount.com
SIP Outbound Proxy (optional): sip1.sipdiscount.com
STUN server (optional): stun.sipdiscount.com

I hear a dial tone, however, dialing results in a 3 different sounding beeps... du-dU-dUU pause then it beeps again. I should have been able to make a 1 minute call.

Any tips would be greatly appreciated. Maybe my dialing plan is off?

Thanks in advance!

Eric
reply
rcilink @ 18th Aug 05:00PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hmm, I think if I were you, I would look into the cyt tool. It is referenced here: »[General] The new PAP2 v2.0

This will most likely resolve your problem by replacing the dial plan (digit map) and removing the PLAR (dial digits prepend 666 )..

then reconfig the SIP settings and then dial a number using: 001+areacode+number

*Note: check that default dial plan to make sure it will work with 001+AC+NMB
reply
ericolsendsl @ 18th Aug 06:16PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks for that advice. I'm making progress, as now I'm actually getting a fast busy tone. There dial plan works as follows:

Dialplan:
00 + {countrycode} + {areacode} + {subscriber}
For instance if you want to call to the USA dial 001987654321 calling to France would be 0033987654321

The digit map I'm using is as follows:

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

What do you suggest?
reply
KillaB7 @ 18th Aug 06:42PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks for the MD5 rcilink!

Could you kindly tell us what to modify in the RTP300 image (rtp300_fw_3.1.17_US.img)?

I think all you're calculating is the tichksum. Any chance this can be done in Windows?
reply
celiomartins @ 19th Aug 12:26AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

rcilink and other that can Help.

I've tried your instructions and the HEX offset 23 is not 4C... I am using WinHEX... anyway the MD5 was different, so I guess that's the reason whay it is not working? could you please upload it? thank you very much!
reply
KillaB7 @ 19th Aug 12:54AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

23 Decimal = 17 HEX

So when using a HEX editor, you'll be editing the byte in address 17h
reply
rcilink @ 19th Aug 01:46AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

KillaB7
Hey, I'm interested in that version of firmware, if you have it.. I have rtp300 v 3.1.10, not 3.1.17 ...
Thanks!

celiomartins
BTW, the offset I speak of is 23 decimal. In winHEX, you can move the cursor down to the 23rd byte (it shows in a status area in the bottom of your edit window.)

If you are using a different firmware than WRTP-3.1.17-NA.img (or whatever the name of it is), then yes, this will not work.

ericolsendsl
The dialplan in a wrtp54g or rtp300 that is/was running 1.00.62 (locked and unlocked) will not operate correctly if it had talked to vonage. Vonage pushes out a "hot line" config that trashes the dial plan (you can see "666" in there). There is another field not shown on the web page that also messes it up when trying to 'undo' and use for a real service.

The fix:

- do a factory reset of device (hold in reset button or from ADMIN tab, reset voice)

or

- use the cyt tool discussed in the other link. it will correctly remove the digits '666' from your dialing plan.
reply
KillaB7 @ 19th Aug 01:56AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

rcilink
Hey bud, it's on the Linksys site (just added on the 16th).
Just need to change from CYLM to CYLL and modify the checksum ;)
reply
rcilink @ 19th Aug 01:59AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks, got it. I guess I missed it (2 days old, nice.)
reply
meister_sd @ 19th Aug 03:28PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

OK, I've loaded this and it looks good! I didn't make any changes to the firmware other than to change the header and re-checksum it. If anyone wants to use it I've posted it.

**** REMEMBER!! If you are using any provider on this device, ALL THE SETTINGS WILL BE ERASED!!

**** If you are using Vonage - DON'T use this firmware. You will not be able to use Vonage again without loading their firmware back on.

1) Download the file to your desktop
2) Log into your router and then click Administration. Click on Firmware Update then the browse button and find the file you just downloaded. Then click the upgrade firmware button.
3) Wait for the upgrade to complete. You will be brought to the login screen automatically. This whole procedure can take upto 5 minutes.
4) After you've logged back in, click on the Administration tab again and then to Factory Defaults. Click BOTH the router and voice to be reset. It will ask for a username/password. The username is Admin (Big A) and leave the password blank. This factory reset will clear any garbage configs and give you a new file.
5) Log back in and then click the voice tab. You are done!

This will give you an unlocked RTP300 with the voice section looking like the PAP2. There isn't any SSH function in this firmware.
reply
kd4yal @ 19th Aug 04:30PM:
Router Backup

Can anyone tell me then I backup my setting from the web interface does this also save all the voice setting?

Thanks
reply
zuchmir @ 20th Aug 02:09PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have a rtp300 with firmware 1.00.43, I have the admin password, tried to go to the update.html page but the user is disabled. I tried getting to the xml file to enable the user but I'm not having any luck. I tried disableing the java scripts and going to the provisioning page, but it would not take any updates from there.

Anyone have the root password - or any password the will get me in with SSH, so that I can change the config.xml? or if someone knows another was to upload the hacked firmware, please let me know. I would greatlt apprecaite it. I read every post on the forum, but can't seem to get it going.

Thanks
reply
KillaB7 @ 20th Aug 02:21PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

@zuchmir

The answer is right here on this page. Look about 12 posts up. It's called CYT-Unlocker and works like magic.
reply
zuchmir @ 20th Aug 03:41PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks I million! You guys rock! that tool is great, now I will try to set it up to work with my asterisk box.

Zuchmir
reply
celiomartins @ 22nd Aug 04:50PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

To help I did a very easy walkthrough.
And also uploaded the Image file.
you can check here... »celiom.googlepages.com/linksys
reply
meister_sd @ 23rd Aug 12:48PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by celiomartins :

To help I did a very easy walkthrough.
Wow, that page looks very nice! Did you create it or is it a template?
reply
celiomartins @ 23rd Aug 05:38PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Does Anybody knows a free service that you can use as a SIP server, but you configure it login into multiple accounts and have them all to ring on the same "SIP address", also that you can create rules to use each account depending on the call?

Note that I don't want to install Asterisk an mantain a PC working here for this.

Thankssss!
reply
anon @ 24th Aug 10:50AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Folks, I really loved this topic, but i just have 2 concerns before go on it:
1) I had downloaded the img file from the site provided by celiomartins but the MD5 of that file does not match with the one provided before from rcilink as follows:
celiomartins's MD5: 611eb9063d2c9c8ff2e34826c1a376e2
rcilink's MD5 (provided above): e3470bc9b640d73d3330cafcc62d2bc9
Does someone already tried with the celio's file?

2) I couldn't find the wrtp54g_fw_3.1.17_US.img file to download from the linksys support site ... at the WRTP54G page there was no firmware to download, but I found the WRTP54G-NA_fw_3.1.17_US.zip at the WRTP54G-NA page ... will it works with the NA image? If no, from where can I get the original file?

tkx in advance for any help on this
reply
retro2783 @ 25th Aug 03:23PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Can this also be applied to the RTP300-NA_fw_3.1.17_US firmware from the Linksys site? I have the RTP300 with the 1.0.0.62-NA firmware installed. Used the CYT-Unlocker to get the logon/password.

retro2783
reply
mazilo @ 25th Aug 11:02PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by renatoz :

celiomartins's MD5: 611eb9063d2c9c8ff2e34826c1a376e2
rcilink's MD5 (provided above): e3470bc9b640d73d3330cafcc62d2bc9
Does someone already tried with the celio's file?
Please compare what you wrote here with rcilink's original post here.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
mazilo @ 26th Aug 11:35AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by celiomartins :

Note that I don't want to install Asterisk an mantain a PC working here for this.
You can also grab the asterisk source code, cross compile for AR7 platform, and upload to your RTP300/WRTP54G VoIP router to do exactly what you had said here. This way, you don't need an extra computer to maintain, but just one single router with asterisk to maintain. I must say it will be easier to have a trixbox configured and use the .conf files generated by trixbox for your asterisk on your router.
--
Mazi (UK Non-Geo Phone: +44-703-194-2574)
reply
ii904 @ 28th Aug 11:18PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

after upgrade to 3.17 ,wrtp54g keep reboot.don't know why.
reply
rajulkabir @ 28th Aug 11:59PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I unlocked a brand-new WRTP54G according to these instructions, and now I can get to the voice configuration screen.

However, no matter what I do, the voice business doesn't actually function. On the voice status page, everything in "Line 1 status" and "Line 2 status" is completely blank. There is no dial tone on either port, even if I set one of the lines up to allow placing calls without registration.

I am pretty used to configuring the Sipura SPA devices so I don't think I'm doing anything terribly wrong. This thing will not even try to register, will not do anything at all. DNS server is configured. I have tried factory reset, voice factory reset, etc.

Any ideas or is it useless?
reply
rajulkabir @ 29th Aug 12:02AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

By the way, the router functions fine (except that the throughput is horrible - with the Netgear RP614 that it replaced, we were getting 4500Mbps, with the WRTP54G the most we get is 2300Mbps.

Maybe I am answering my own question: it is a piece of crap.
reply
rcilink @ 29th Aug 01:52AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Just a possibility...
Make sure you fill-in the Line1 CID Number field (just under Line Enabled).

If this is blank, it will not try to register the line.
reply
KillaB7 @ 29th Aug 11:43PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

After unlocking, did you turn on remote administration (port 8080 by default) and then connect the Internet (WAN) port to the rest of your LAN?

AFAIK the unit will only attempt to register on the WAN port.
reply
mogulman @ 30th Aug 12:11PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Anyone know how the voice part of these routers compares with a pap2t?

Just wondering if there is any advantage either way?
reply
hollando @ 6th Sep 01:25AM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

Hi, if I want to create an image. I have the squashfs rootfs image and kernel image. Also, I'll add PSPBoot header and make total file size the same. Can I use it as a image for firmware update in web interface? Is there any check sum or somethin' else I need to include? Anybody can analysis me the structure of the img file? Thanks!
reply
rcilink @ 6th Sep 01:59AM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

yes the firmware is checksum'd with a TI checksum. the prog to do that is called 'tichksum'.

Source is GPL'd, so it can be built on your machine.
reply
hollando @ 6th Sep 02:55AM:
Re: wrt 1.00.62 firmware Termination digit

tkprojects, some times we do need to insert something for local call, for example, for some SIP provider we need this for US area code "aaa"
[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|xx.T
This works fine in PAPv1 dial plan, but not acceptable by PAPv2 xml digit map configuration. I looked into rfc2705 digit-map. They don't mention any autonumber rules. So can we figure out how to solve this problem? Maybe by other parameter. I don't want to dial area code for local call.
reply
tkprojects @ 6th Sep 10:58AM:
Re: wrt 1.00.62 firmware Termination digit

said by hollando :

[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|xx.T
This works fine in PAPv1 dial plan, but not acceptable by PAPv2 xml digit map configuration.
I'm not sure whether PAP2v1 ascribes any meaning to a "T". AFAIR the proper syntax for a timer in PAP2v1 is "S0". In PAP2v1 you can use substitution in the form <:1234>[2-9]xxxxxx to add the 1 + area code - here the area code is 234. I haven't looked at the PAP2v2 yet. Sorry.

I looked into rfc2705 digit-map. They don't mention any autonumber rules. So can we figure out how to solve this problem? Maybe by other parameter. I don't want to dial area code for local call.
Thanks for the hint, I haven't looked at the RFC, but it does clear up some questions I had about the meaning of "T". I'll have to read it detail to see if it sheds some light on the configuration of the TI based ATAs.
reply
hollando @ 6th Sep 07:42PM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

I tried to build this one (»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G) from openwrt. But seems like it missing something,
hollando@embeded:~/rtp300_cyt_1_00_60_060223_gpl $ make
Makefile:617: /home/hollando/rtp300_cyt_1_00_60_060223_gpl/
TI_Build.make: No such file or directory
make: *** No rule to make target 
`/home/hollando/rtp300_cyt_1_00_60_060223_gpl/TI_Build.make
'.  Stop.

Can you tell me how to get the missing part. Or give me url for some other SDK. Thanks!
reply
rcilink @ 7th Sep 08:36AM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

the GPL source that Linksys provided for the WRTP54G and RTP300 will not build.

There are several versions on their GPL site. Each has interesting things to look at/install.

The 1.00.37 one has most of a TI MIPS-I toolchain for Redhat Linux.

As far as I know, none of these GPL packages have the cfgmgr (cm_logic, cm_*, webcm, cm_* files) source. It is missing. The other critical piece missing is 'ggsip'. That is the actual program that runs the 2 phone ports on the device.

So, sadly, it will not be easy to build firmware from source code-- at least not to use the SIP features of the device.

Perhaps someone with money can talk (sue?) Linksys to comply with GPL.. They are supposed to release code that can be built.
reply
hollando @ 7th Sep 02:29PM:
Re: wrt 1.00.62 firmware Termination digit

I'm not sure whether PAP2v1 ascribes any meaning to a "T". AFAIR the proper syntax for a timer in PAP2v1 is "S0". In PAP2v1 you can use substitution in the form <:1234>[2-9]xxxxxx to add the 1 + area code - here the area code is 234. I haven't looked at the PAP2v2 yet. Sorry.
Hi, tkprojects. Just FYI, "S0" is from CCITT.NO1 (MFC signalling) that means "end-of-pulsing" while the caller number sending phase has finished. "T" is a digit map meaning 4 seconds interdigit timer.
reply
hollando @ 7th Sep 05:43PM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

said by rcilink :

There are several versions on their GPL site. Each has interesting things to look at/install.

The 1.00.37 one has most of a TI MIPS-I toolchain for Redhat Linux.
rcilink, can you give me URL for this TI GPL site please?

said by rcilink :

As far as I know, none of these GPL packages have the cfgmgr (cm_logic, cm_*, webcm, cm_* files) source. It is missing. The other critical piece missing is 'ggsip'. That is the actual program that runs the 2 phone ports on the device.
The "cm" programs are from Monta Vista, I think. Ggsip is their work, so they protect it, and we have to use open source SIP program like asterisk for replacement.
reply
rcilink @ 7th Sep 06:28PM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

said by hollando :

rcilink, can you give me URL for this TI GPL site please?
Sorry if I misled you.. I dont know of a "TI" GPL site. I know that the Linksys GPL site (can be found by looking for firmware for Linksys WRTP54G at linksys.com.. then click on GPL)..

The thing to look at is 1.00.37 GPL firmware on there. It has the TI Toolchain (most of it?) .. this does not mean it will compile, but it will give some clues about other stuff.
reply
hollando @ 7th Sep 07:58PM:
Re: looking inside the wrtp54g (rtp300) firmware using Linux

Thanks, rcilink. Just download a 1.00.60 GPL firmware from linksys. Hopefully this one don't give me much trouble in compiling.
reply
KillaB7 @ 8th Sep 09:38AM:
New firmware version 3.1.18

Did some obscure Googling and found a 3.1.18 firmware for both the WRTP and RTP.

»www.ippt.dk/voip_center_plus.asp···firmware

I would assume that for those of us with 3.1.17, 3.1.18 will load without modification since the product code already matches on our units.

***Use at your own risk, I have not tested this yet. Also, there is no change log with the download.
reply
daodao19 @ 8th Sep 10:29AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Hi,

I can't download ANYWHERE the zip file RTP300-3-1-10
Can you help me?
Even your link is "empty".

Thanks,
Dario
reply
sgonzalez @ 9th Sep 12:29AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Can this be applid to the RTP300 router?
reply
daodao19 @ 12th Sep 11:32AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

rcilink... HELP!
My eyes are burning after reading so many hundreds of posts...
I understood you are the "one" to ask:
WHY I cannot download ANY of the modified firmware for RTP300?

And, which one we should try: 1.00.62 or 3.1.17?
reply
KillaB7 @ 19th Sep 12:05AM:
Re: New firmware version 3.1.18

Still haven't loaded this on an RTP of my own since I don't have a spare to play with.

Found another link with the same files: »www.redspot.dk/page.aspx?ID=15BD···38018D6F

Noticed in the bin file the acronym ETSI, so I would have to assume this to be a Euro only firmware. The product ID's match so there's no reason to assume it won't load ok. I have no idea what's different since I've never been able to mount squashfs successfully so it's probably not a good idea until we know for sure.
reply
Stroker @ 22nd Sep 11:12AM:
1.00.62 vs 3.1.17 For unlocking the RTP300?

Any comments on unlocking the RTP300 with rcilink's :

rtp300-1.00.62-NA.zip

versus meister_sd's :

rtp300_fw_3.1.17_US.von.zip

Does the later work? Is one better?

Thanks for all the great work everyone!!!
reply
darthschrade @ 28th Sep 12:42PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

You need to be logged in to download the file.
reply
daodao19 @ 29th Sep 12:45PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

:D
Thanks a lot, Darthschrade!
:D
Even if it was just in front of my eyes, I couldn't understand why!!!!!
;)
I have now my rtp300 working with VoipCheap (to call) and Skypho (to receive).
i am working on having the skypho incoming calls "transferred" over the Voipcheap cordless phone...
Whish me good luck! :uhh:
reply
campuschill @ 2nd Oct 04:01AM:
Re: New firmware version 3.1.18

Tried loading this firmware, i get a invalid code pattern error.
reply
rcilink @ 2nd Oct 10:40AM:
Re: New firmware version 3.1.18

said by campuschill :

Tried loading this firmware, i get a invalid code pattern error.
Take a look at this post: Loading -NA firmare on a WRTP54G

It will give you some info about how to mod the firmware (3.1.17) to get it to load on your WRTP54G device.

Once that is loaded, you can upgrade to the 3.1.18 release.
reply
anon @ 3rd Oct 05:54PM:
Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Hello,

I'm not a noob and I've read this entire thread -- but I still don't see how to extract the Vonage SIP credentials from the WRTP54G (w/ 1.00.62 firmware).

The method of disabling javascript and heading to the provisioning pages doesn't work -- view source for the page just shows a frame header.

I just want to get the sip creds so I can setup Vonage as a SIP trunk from my asterisk box (have two less DA conversions in the process).

Is this possible with v1.00.62 or am I dreaming?

Thanks!
reply
KillaB7 @ 3rd Oct 11:24PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

said by pariax :

I just want to get the sip creds so I can setup Vonage as a SIP trunk from my asterisk box (have two less DA conversions in the process).

Is this possible with v1.00.62 or am I dreaming?
Totally possible. Go back and try to view the source of your Provision page again (you have to scroll to the very bottom)...use Firefox if you can't get things to work in IE.

Then download the RC4 win32 executable (page 3 of this thread) and grab your tiMAC.xml file from one of the Vonage servers and away you go.
reply
meister_sd @ 4th Oct 02:59PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

said by pariax :

The method of disabling javascript and heading to the provisioning pages doesn't work -- view source for the page just shows a frame header.

Remember, the ESC trick is one of timing. Keep trying and viewing the page source. Eventually you will get it. It can be very frustrating though.
reply
anon @ 4th Oct 03:04PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

OMFG! I am a muppet! It was there all along, I just wasn't scrolling down far enough in the source!

Thanks all!
reply
anon @ 4th Oct 03:58PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

OK so using my newly acquired mad skillz to actually scroll down past the header of the provisioning page to get my provisioning key, then tftp'ing my xml file from vonage, and decrypting it, I now have my vonage SIP creds. Woohoo!

I'm in the process now of configuring a SIP trunk from asterisk to voange (so I can skip the wrtp54g ata altogether) and a few things have come up:

1) My "user-agent" is no longer going to be User-Agent: W
RTP54G0014BF082B and so on... i.e. Vonage is going to know I've binned their ata. ;-)

2) What is my "register-string" for the asterisk SIP trunk?
For vonage softphone customers it appears to be in the format:

register=Phone_Number:Password@sphone.vopr.vonage.net:5061

Has anybody pulled this off yet? I'm not trying to fuck vonage over at all -- just don't need an extra digital-->analog-->digital conversion in my VOIP setup. If you've got this working pls post the required asterisk config..

Cheers,

-p
reply
anon @ 4th Oct 04:36PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Hey -- answering my own questions here! Fun!

I got outbound working as follows:

(from /etc/asterisk/sip.conf)
[VON-SIP]
username=$vonagephonenum
#type=peer
type=friend
secret=$vonagesippw
port=10000
host=216.115.20.78
nat=yes
insecure=very
fromuser=$vonagephonenum
dtmfmode=rfc2833
disallow=all
defaultexpirey=120
canreinvite=no
auth=md5
allow=G723.1
allow=g729
allow=ulaw
allow=alaw
allow=gsm

No joy on inbound tho... I'll keep hacking. If anybody already has it working pls drop a note aye?

Peace

- p
reply
anon @ 4th Oct 04:37PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Oh -- forgot one more thing.

At the top of /etc/asterisk/sip_additional.conf:

register=$username:$password@216.115.20.78:10000
reply
ScarEye @ 11th Oct 02:57AM:
Re: RTP300 firmware update RTP300-3-1-10.bin

Guys I have a RTP300 firmware version 1.01.07 I am trying to unlock it I have looked high and low but I don't see any information on this matter. Can anyone point me in the right direction ?

Thanks in advance
ScarEye
reply
campuschill @ 11th Oct 07:55PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Did you get incoming working, if yes can you post config. thanks
reply
netmitra @ 15th Oct 12:09PM:
Re: Getting a WRTp54G to take 3.1.17-NA... [ Still locked }

Rmaneka;

Unfortunately my WRTP54G is still locked by Vonage and running 1.00.20. I can't unlock it so no access to update.html

Please help
reply
anon @ 16th Oct 04:44PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Hey Campuschill--

Yes -- I got it working, but there is something strange going on w/ my Asterisk config which is devnulling the call immediately after answering it.

I believe that it has something to do w/ some whacky filtering I'm doing to inbound calls (i.e. screen if no CID, record name, drop call to holding line, ring extension, play name, user can connect call by ringing holding extension).

Config was as I posted. I haven't had time to test further yet but I think if I were running a stock-standard asterisk setup the config would be complete.
reply
netmitra @ 17th Oct 12:08AM:
WRTP54G Unlocked ---- Thank you guys !!

After 1 week of attempts - Success now.

I was successfully able to unlock my Vonage WRTP54G using the firmware upgrade procedure. The cyt software failed to do so. I used the following link and it worked like charm !

I was getting "Invalid Code Pattern" error with 3.1.17-NA firmware from Linksys support. Then I used celiom.googlepages.com/linksys code which got me onto 3.1.17, but No NA.

My router wasn't accepting any user:tivonpw password and I was stuck. Then I did a factory reset using the poke-in button at the back. After that I was able to access update.html and then upgraded the firmware. Now I am on 3.1.17 and life feels good. Configuring VIatalk was a cakewalk.

Next Project is to install astersik on this. ANy easy-2-go guide will be appreciated.
reply
niel8 @ 18th Oct 10:28PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

everything went fine i reset both router and voice, now it dont let me login, do u knw wuts username and password i would have to enter now? btw TWO THUMBS UP for gettin me to this step
reply
anon @ 21st Oct 12:36AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Campuschill,

My incoming and outbound configs are now working.

The problem was the fax detection in trixbox was enabled, and was making inbound calls hang. I disabled fax detection and now all is well.

Cheers

-p
reply
campuschill @ 24th Oct 10:45AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

pariax, i could not get it to work both incoming and outgoing, i used FreePBX. I copied the SIP.conf file in the incoming settings in FreePBX and also did enter register string. But when I look at the ASTERISK info page, it does not register at all, all i see is a request sent message.
reply
anon @ 24th Oct 11:21AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Campuschill,

I definitely got it working (in both directions) with Trixbox-NV 1.1.2 (w/ FreePBX). I'm on the road today but will be back online tonight and will post my complete configs and debug dumps.

I've been trying to connect Asterisk to Vonage via SIP for nearly a year now so I understand how frustrating it can be!

More soon!

-p
reply
anon @ 24th Oct 11:58PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

OK... Here it is.

This *definitely* works for me in both directions.

Environment:
Linux asterisk1.local 2.6.9-34.0.2.EL #1 Fri Jul 7 19:24:57 CDT 2006 i686 i686 i386 GNU/Linux

asterisk1*CLI> show version
Asterisk 1.2.12.1 built by root @ asterisk1.local on a i686 running Linux on 2006-09-28 14:30:48 UTC

Network:
Asterisk box is on private IP behind NAT, no port forwarding, stun, or anything going on yet (may do for production environment)

Configs:

[root@asterisk1 asterisk]# cat sip.conf
; Note: If your SIP devices are behind a NAT and your Asterisk
; server isn't, try adding "nat=1" to each peer definition to
; solve translation problems.

[general]

port = 5060 ; Port to bind to (SIP is 5060)
bindaddr = 0.0.0.0 ; Address to bind to (all addresses on machine)
disallow=all
allow=ulaw
allow=alaw
; If you need to answer unauthenticated calls, you should change this
; next line to 'from-trunk', rather than 'from-sip-external'.
; You'll know this is happening if when you call in you get a message
; saying "The number you have dialed is not in service. Please check the
; number and try again."
context = from-sip-external ; Send unknown SIP callers to this context
;context = from-pstn ; Send unknown SIP callers to this context
callerid = Unknown
tos=0x68

; #, in this configuration file, is NOT A COMMENT. This is exactly
; how it should be.
#include sip_nat.conf
#include sip_custom.conf
#include sip_additional.conf

[root@asterisk1 asterisk]# cat sip_additional.conf
register=$acn:$sippw@216.115.20.78:10000
(use whatever vonage host you like there -- sniff your ata to see who it prefers -- let me know if you have a better dns name -- i blew my router away before having a good look :)

(acn = area code+number, i.e. 18005551212)
sip pw = your vonage sip pw

; vonage outbound settings
[vonage]
username=$acn
type=friend
secret=$sippw
port=10000
nat=yes
insecure=very
host=216.115.20.78
fromuser=$acn
dtmfmode=rfc2833
disallow=all
defaultexpirey=120
canreinvite=no
auth=md5
allow=G723.1
allow=ulaw
allow=alaw
allow=gsm

; vonage outbound settings
[vonin]
username=$acn
type=friend
secret=$sippw
port=5060
nat=yes
insecure=very
host=216.115.20.78
fromuser=$acn
dtmfmode=rfc2833
disallow=all
context=from-pstn
canreinvite=no
auth=md5
allow=G723.1
allow=ulaw
allow=alaw
allow=gsm

also remember in trixbox inbound call config, to disable fax detect -- that threw me for awhile.

good luck!!! let me know if it works.
reply
campuschill @ 26th Oct 06:51PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Thanks for your reply..

Did not succeed to get it working, my decrypted text file says

216.115.24.230
216.115.31.140

I tried both, the proxy is

k.voncp.com:10000

this also does not work,,any thoughts...
reply
zimmy6996 @ 26th Oct 11:43PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Okay, so I have been able to grab that update page with that info. How do I go about grabbing the XML file now via TFTP, and then decrypting it so I can get the username/password SIP credentials?
reply
zimmy6996 @ 27th Oct 12:06AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Okay, I did a complete read of the thread. I figured out how to TFTP my ti000000000000.xml file from the site. I then used the RC4 program with the key from the provision page to decrypt the file. I am left with a file that when I open it starts with ...







+xxxxxxxxxxxx/rt-11.1.0-r021-1.00.62-r060327.img

tftp://ti.tftp.vonage.net:69,21,2400
»httpconfig.vonage.netti.tftp.vonage.net
ti.tftp.vonage.net

Then it is all binary after this .... Does this mean that I have done something wrong?

Armed with this information, where can I go from here? Am I close to being able to come up with the coveted SIP credentials I am looking for?
reply
anon @ 27th Oct 12:31AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Zimmy,

it looks like you grabbed a firmware via tftp, rather than your provisioning file

make sure when you tftp in you grab the $pathti$macaddr.xml file

it sounds to me like you're grabbing a firmware image via tftp rather than your provisioning file.

for $path use the 'default' path that you obtained from the router's provisioning page
reply
anon @ 27th Oct 12:32AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

campuschill,

post your configs and also debug logs and i'll have a look

cheers

-p
reply
zimmy6996 @ 27th Oct 08:27AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Okay, from my RTP300 upgrade page, here is the info ... Maybe I am looking at the wrong page, however, based on this info, I did the following command to pull the file down ...

tftp ti.tftp.vonage.net GET /Fxxxxxxxxv/ti000000000000.xml

then I did the RC4 command with the key that is listed.

Am I pulling the wrong file down?




























reply
zimmy6996 @ 27th Oct 08:30AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

»192.168.15.1/cgi-bin/webcm?getpa···ion.html

I am going to this page to get the file.

On that page at the botttom, there is a "Provisioning" header, and 2 "new" headers. If I try to pull based on the path under provisioning, the file doesn't exist. If I pull based on the path under the first "new" header, I am able to pull the file, however, like I said, you see the results I am getting when I run RC4 to decrypt it.
reply
zimmy6996 @ 27th Oct 10:24AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Im retarded ... Had to do a binary download from the TFTP site. All is well. I am able to make SIP calls now without that silly RTP300!

I did notice that I am unable to have 2 SIP devices connected at the same time. If I do, one or the other fails. So Vonage must have a limit of 1 SIP device connected at 1 time. This is different than the softphone, which allows you to have as many as you want connected at 1 time.

What are you guys doing with Asterisk in term of the user agent. Did you change your user agent so that it "appears" as if you are calling from your RTP300.
reply
anon @ 27th Oct 11:00AM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

jimmy,

i tested my setup w/ max channels set to 2, and it worked fine. (that's two conns from the same asterisk pbx). i haven't tested it w/ say my pbx and a direct sip conn from a softphone.

re: user-agent i didn't mess with it. i realize that i'm violating vonage's TOS but it's only because i get shitty performance when going digital-->analog-->digital (which is the case w/ their ATA and my tdm400p).

by going straight SIP i get better quality. and i'm not on an unlimited plan so it's not like i can use more minutes by virtue of having multiple sip channels active

so rather than change the user-agent i'm just being honest and if they terminate my acct that's their loss :)

there are 10 other providers i can choose from, most of which have open sip creds or support iax2
reply
zimmy6996 @ 27th Oct 08:02PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Yeah, I can tell you that if you try to fire up 2 SIP devices, it will knock 1 offline. I have tried to connect 2 different SIP devices to my account at the same time, and it fails. That is different from the Vonage softphone however, which allows several SIP devices on the same account at the same time.

I really could care less about having several SIP devices connecting to Vonage, because if I can connect Asterisk to Vonage and make 2 channels outbound, you are getting the same thing. I am not looking to abuse vonage, just make it more practical for my requirements.
reply
campuschill @ 27th Oct 09:29PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Freepbx Trunk
Outgoing Settings

Trunk Name:vonage
username=von#
type=friend
secret=vonpasswd
port=10000
nat=yes
insecure=very
host=216.115.31.140
fromuser=von#
dtmfmode=rfc2833
disallow=all
defaultexpirey=120
canreinvite=no
auth=md5
allow=G723.1
allow=ulaw
allow=alaw
allow=gsm

incoming settings
User Context:vonin
username=von#
type=friend
secret=vonpasswd
port=5060
nat=yes
insecure=very
host=216.115.31.140
fromuser=von#
dtmfmode=rfc2833
disallow=all
canreinvite=no
auth=md5
allow=G723.1
allow=ulaw
allow=alaw
allow=gsm

register=von#:vonpasswd@216.115.31.140:10000

Below is last 300 lines of the asterisk log

Oct 27 21:17:50 DEBUG[2493] config.c: Parsing /etc/asterisk/sip_notify.conf
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 216.115.31.140 with 192.168.15.0
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Challenge'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Login'
Oct 27 21:17:50 DEBUG[31333] config.c: Parsing /etc/asterisk/manager.conf
Oct 27 21:17:50 DEBUG[31333] config.c: Parsing /etc/asterisk/manager_custom.conf
Oct 27 21:17:50 WARNING[31333] config.c: Unknown directive 'permit=192.168.1.0/255.255.255.0' at line 18 of manager_custom.conf
Oct 27 21:17:50 DEBUG[31333] acl.c: 0.0.0.0/0.0.0.0/0.0.0.0 appended to acl for peer
Oct 27 21:17:50 DEBUG[31333] acl.c: 127.0.0.1/255.255.255.0/255.255.255.0 appended to acl for peer
Oct 27 21:17:50 DEBUG[31333] acl.c: ##### Testing 127.0.0.1 with 0.0.0.0
Oct 27 21:17:50 DEBUG[31333] acl.c: ##### Testing 127.0.0.1 with 127.0.0.0
Oct 27 21:17:50 VERBOSE[31333] logger.c: == Manager 'admin' logged on from 127.0.0.1
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 216.115.31.140 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 216.115.31.140 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 216.115.31.140 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 80.239.235.201 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 80.239.235.201 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 204.147.183.18 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 204.147.183.18 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 192.168.0.57 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 192.168.0.57 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 204.147.183.18 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 204.147.183.18 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - OPTIONS (No RTP)
Oct 27 21:17:50 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Stopping retransmission on '409665da40e1d67e1582f826041a3523@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Stopping retransmission on '24581ad9587071d142bb52ce71701a62@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Stopping retransmission on '4dd3056a451d12847884a3e80e6e079b@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Stopping retransmission on '6bff785f2dedf50e780025780b08dcee@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/vonin' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/5000' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/199' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/from-pstn' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/299' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/pstn' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/stanaratnastd' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'IAX2/iaxfwd' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits_kavi' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/7000' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits_ratna' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/3195220963' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/8000' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/voipbuster' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/vonage' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'IAX2/fwd' in family 'cfb'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/vonin' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/5000' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/199' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/from-pstn' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/299' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/pstn' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/stanaratnastd' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'IAX2/iaxfwd' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits_kavi' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/7000' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits_ratna' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/3195220963' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/8000' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/voipbuster' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/freedigits' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'SIP/vonage' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] db.c: Unable to find key 'IAX2/fwd' in family 'dnd'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'QueueStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Status'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'ZapShowChannels'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'MailboxStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'MailboxStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'MailboxStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'MailboxStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'MailboxStatus'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:50 DEBUG[2493] chan_sip.c: Stopping retransmission on '7e360baf2ddea4b414681ed2742e271a@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Stopping retransmission on '4a16b3215921318e0a8cb55766085576@71.56.56.84' of Request 102: Match Found
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 4db695972ca5daff223316e72dab4190@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:51 DEBUG[2493] acl.c: ##### Testing 216.115.31.140 with 192.168.15.0
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Target address 216.115.31.140 is not local, substituting externip
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for 216.115.31.140 id #1208457
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 73b39e2703e18c0f5909fb207af957bf@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:51 DEBUG[2493] acl.c: ##### Testing 204.147.183.18 with 192.168.15.0
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Target address 204.147.183.18 is not local, substituting externip
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for sip.stanaphone.com id #1208459
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 130763512dea59cb501b89cf6d45ba49@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:51 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for freedigits.net id #1208461
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Stopping retransmission on '130763512dea59cb501b89cf6d45ba49@127.0.0.1' of Request 102: Match Found
Oct 27 21:17:51 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 3d1cb7b86174d29239e544637ca09731@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:52 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:52 DEBUG[31333] manager.c: Manager received command 'Command'
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for freedigits.net id #1208464
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 73094eca2e8376671939ebfd0481cb9e@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 194.120.0.203 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 194.120.0.203 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for sip.voipbuster.com id #1208466
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 693f1c3b77ad23d6434dd9112da80874@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for freedigits.net id #1208468
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 352e834a3b25a63227251e91551313a0@127.0.0.1 - REGISTER (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Scheduled a registration timeout for ratna.selfip.com id #1208470
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 DEBUG[2493] sched.c: Request to schedule in the past?!?!
Oct 27 21:17:56 NOTICE[2493] chan_sip.c: Peer 'Ratna PSTN' is now UNREACHABLE! Last qualify: 379
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '130763512dea59cb501b89cf6d45ba49@127.0.0.1' of Request 103: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Registration successful
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Cancelling timeout 1208461
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for d1093498-d6cfc823@192.168.0.2 - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for d1093498-d6cfc823@192.168.0.2 - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for d1093498-d6cfc823@192.168.0.2 - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for (No Call-ID) - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 203.101.32.246 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 203.101.32.246 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for d1093498-d6cfc823@192.168.0.2 - NOTIFY (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '3d1cb7b86174d29239e544637ca09731@127.0.0.1' of Request 102: Match Found
Oct 27 21:17:56 DEBUG[31336] app_queue.c: Device 'SIP/vonin' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
Oct 27 21:17:56 DEBUG[31337] app_queue.c: Device 'SIP/vonage' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
Oct 27 21:17:56 DEBUG[31338] app_queue.c: Device 'SIP/Ratna PSTN' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
Oct 27 21:17:56 DEBUG[31339] app_queue.c: Device 'SIP/pstn' changed to state '1' (Not in use) but we don't care because they're not a member of any queue.
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '693f1c3b77ad23d6434dd9112da80874@127.0.0.1' of Request 102: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '73b39e2703e18c0f5909fb207af957bf@127.0.0.1' of Request 102: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '73094eca2e8376671939ebfd0481cb9e@127.0.0.1' of Request 102: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '130763512dea59cb501b89cf6d45ba49@127.0.0.1' of Request 103: Match Not Found
Oct 27 21:17:56 WARNING[2493] chan_sip.c: Got 200 OK on REGISTER that isn't a register
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '73b39e2703e18c0f5909fb207af957bf@127.0.0.1' of Request 102: Match Not Found
Oct 27 21:17:56 DEBUG[2493] acl.c: ##### Testing 67.55.159.160 with 192.168.15.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Target address 67.55.159.160 is not local, substituting externip
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Allocating new SIP dialog for 130763512dea59cb501b89cf6d45ba49@127.0.0.1 - SIP/2.0 (No RTP)
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: That's odd... Got a response on a call we dont know about. Cseq 103 Cmd SIP/2.0
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '73b39e2703e18c0f5909fb207af957bf@127.0.0.1' of Request 103: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Registration successful
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Cancelling timeout 1208459
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Stopping retransmission on '693f1c3b77ad23d6434dd9112da80874@127.0.0.1' of Request 103: Match Found
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Registration successful
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Cancelling timeout 1208468
Oct 27 21:17:56 DEBUG[2493] chan_sip.c: Cancelling timeout 1208468
reply
campuschill @ 3rd Nov 03:04PM:
Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

fixed it, had to remove nat=yes in the general sip.conf

Asterisk box behind a router...
reply
anon @ 6th Nov 04:53AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

does all of this apply to wrtp54g-er (for earthlink) too ??
reply
anon @ 7th Nov 12:15AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

The: rc4 key inFile outFile, and question is what is the "infile" and what is the "outfile" is supposed to be called?

I just want to unlock my rtp300 so I can firmware upgrade, cause these bastards locked it all up.

So can you explain a bit more?

Steve Masten
reply
anon @ 7th Nov 12:36AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?


I hope you will, or someone will reply.

Uuummm... My friend just told me you guys might not answer cause vonage put you all in jail?

If you want me to slap my friend sebastian again, I will be glad too... No offense, I am curious.

SM
reply
speed_spec @ 13th Nov 03:44PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have 3.1.17 loaded and working on my RTP300.
Big thanks to all and particularly to rcilink and meister_sd.

Now I have to get the RTP300 to work with SR. :)

Anyone has an easy guide for that?
reply
ii904 @ 13th Nov 07:32PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

wherw are you got 3.1.17 fireware? could you link to download?thanks
reply
mijoe @ 13th Nov 08:21PM:
Re: New firmware version 3.1.18

Hello all, I have a wrtp54G that I have been able to unlock to firmware 3.1.17, thanks to your unfailing toils. (thanks everyone) :)

However, After registering to my trixbox, I get no sound on calls from a remote location. It worked fine on my LAN, which naturally leads to an issue with ports. I did change the RTP ports to 10000-20000, as Trixbox dictates, and the ports chosen during calls fall within that range. The SIP extension in Trixbox is nat=yes. The ports on the side of the trixbox are forwarded to the correct IP, etc. Call control works flawlessly (I can watch at the CLI, CDR shows calls, etc.)

Has anyone else seen this and can he/she share experience with me to I can get this thing all up and running?
reply
anon @ 15th Nov 02:27AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

this works!
reply
niel8 @ 22nd Nov 02:58PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

well, i finally too unlocked my rtp 300 and loaded 3.1.17, i am sorry because this question seems inappropriate to this forum, but has anyone tried successfully voip.brujula.net settings? just for information it gives free US phone no. so u can have free incoming, but i coudnt apply them successfully, on support site www.fonosip.com it shows how to config pap2, dis one is similar to it, or can anyone point me to another services? thanks a lot.
reply
niel8 @ 23rd Nov 05:05PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

also is it possible to replace the firmware of this rtp 3oo with spa2102-NA?
reply
anon @ 23rd Nov 07:01PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

How do you upgrade the firmware on WRTP54G? There is not such an option under the Administration menu. HELP!
reply
anon @ 24th Nov 11:02PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Hi,
the image file from celiomartins (wrtp54g_fw_3.1.17_USmod.img) only has 2.746.234 bytes and the image (wrtp54g_fw_3.1.17_US.img) from linksys has 3.866.632 bytes, why they are not equal in size if only 5 bytes (offset 23 + checksum) were changed ?
reply
anon @ 25th Nov 08:53PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Hi,
I found the problem with img size, it was my download manager.


reply
anon @ 7th Dec 03:40PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

hi!
i'm using WRTP54G for Vonage
i've tried to upgrade celiomartins' img file and got message:
unexpected end of file
at the end of upgrade/upload of firmware

any idea what's wrong?

i would try upload with original linksys img file modified by myself but it's not available at linksys page anymore
reply
anon @ 8th Dec 08:06AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

part 2

celiomartins' file didn't work but i've tried the one from »blog.adonias.cl/leer.php?id=81 metodo 2a and this one worked

thakns a lot 4 all participants

maciek
reply
rcilink @ 8th Dec 08:24AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by macpas :

part 2

celiomartins' file didn't work but i've tried the one from »blog.adonias.cl/leer.php?id=81 metodo 2a and this one worked

thakns a lot 4 all participants

maciek
Thanks for that blog link.. on there one can find WRTP54G 3.1.19 firmware. I have not loaded it yet, but maybe it fixes the line1 / line2 usage issue...


EDIT: I guess I should check the linksys site more! On the site, under SUPPORT/downloads, select WRTP54G for Vonage. You can download 3.1.20 firmware!

Here is a link to a WRTP54G 3.1.20 Linksys page. From there, you can download the firmware:

»www.linksys.com/servlet/Satellit···rWrapper
reply
niel8 @ 9th Dec 09:04PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

well, sorr for dat dumb que, but if someone else has got the same que, it is admin/admin, also i got one more question,
Does this firmware support STUN/Outbound Proxy features? is there an option for outbound proxy?
reply
radom11 @ 11th Dec 01:01PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Rclink, :)
Please forgive but I am new to all of this and it looks like you are the most knowledgeable individual that helps many
We have 3 units of the WRTP which we are trying to get working for a charity group to who now need to change from "V" (no more money) and use a free Asterisk 2.7 pbx switch that we have built for them and works well in local lan location.
Spent hours reading the messages I then downloaded the wrtp54g_fw_3.1.17_US.img from celiomartins web site and got the image to load into the wrtp54g using the “stock” user/tivonpw unit, All of that was GOOD info and the unit now shows 3.1.17, I did a 60 second reload and router is working and voice section now shows SIP and other setting headers and most fields are blank.
When I downloaded the wrtp54g_fw_3.1.17_US.img from celiomartins web site it was my impression from reading the messages that the hex code changes where done to that image , Yes/No?
Anyway the box is running 3.1.17 but the user/tivonpw password no longer works in trying to do a factory reset or and when I attempt to reload any image , am I hosed?
Any material that we can read that will explain the settings in the wrtp as the booklet that was in the box only talks about “V” system and we need to talk to Asterisk or SIP.
We have wrt1.00.62-NAr6,wrtp54g-3.1.20,image availabel Please help!
Any information is much appreciated, any one knows of a easy step “guide” as this will help many

Many Thanks
Radom11 :huh:
reply
rcilink @ 11th Dec 01:17PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

loading the 3.1.17 (-NA) version on an old vonage box is an excellent choice, as it will remain unlocked..

when you click the "voice" tab, you should now be taken to a new voice section, with menus that look/feel identical to the Linksys PAP2 unit.

Look to the right of the web page, near top and find admin login and click that. Now you can configure Line 1 to your asterisk box and the other line if needed.

I do not suggest changing firmware again, as it is not needed.

Using 3.1.17, the new "Admin" account password is blank (just put username Admin with no password).

If you need help configuring SIP to your asterisk, look for help on Linksys pap2 and asterisk.
reply
radom11 @ 11th Dec 03:27PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Rcilink,
Thank you for the fast reply.
The unit is displaying only version 3.1.17 it is not indicating NA should it be indicating NA?
I did not do the Hex changes as messages from celiomartins indicated that he did the changes and then put out the image, is that correct?
I located the Ast recipe page that talks about connecting the Linksys PAP2 I will attempt to do so when we have no more users on the pbx later this evening as they are using the Asterisk and I do not want to blow anything, in your reply you indicated that the code was like and feel of a PAP2 will it program the same way?
We will use line one for asterisk pbx to provide the remote animal shelters with home office pbx functionality to the small key systems that they no have in place at the remote locations, can you suggest a free voip incoming service that we can program into line 2 and a config for it?
What is the story with the 3.1.20 that I see is now out?

Your courtesy and help is greatly appreciated.

Many Thanks.
Radom11
reply
myvoip07 @ 14th Dec 10:34PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by meister_sd :

This will give you an unlocked RTP300 with the voice section looking like the PAP2.
I upgraded my used rtp300 i bought to 3.1.17. A big thank you specially to meister_sd, rcilink and others it is now completely unlocked. Configured fwd and voipcheap and it is working fine. One observation after reboot when i click on Voice tab it gives a msg saying "Voice Module is not ready yet, please wait..." but after less then 1 min it displays the voice menu fine. Also noticed in the log for the voice module the following message. System started:ip@ip, reboot reason:W4
The rtp300 is connected to port 3 of WRT54GL. I haven't tried connecting the rtp300 to my broadband modem directly yet to see if the same problem exists.
Has anyone noticed/seen this problem.
reply
anon @ 15th Dec 03:09PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

radom11, try this one...www.sipnumber.com

Don't know anything about them but they offer what your looking for, I think.

I've been lurking and have my box up and at about the same place you are...good luck.
reply
qqura1 @ 24th Dec 04:26AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hi,
I followed the process to unlock my RTP300.
After I logged into my RTP, I went to voice tab to enter my proxy details.
When I tried pexes.org, it said status as 'Failed'. Then I entered 217.195.32.11 or pbxes.com in proxy details and entered user id & pwd. Now it shows status as 'Registered' rather than 'Online'. Now my line1 LED in ON but I'm not getting either dial tone or not able make/receive call.
Also I noticed during unlock process that both Admin/blank pw & user/tivonpw did not work for me. Always admin/admin worked.
Anybody can help on this? Am I doing anything wrong here?

Thanks.
reply
anon @ 29th Dec 07:54PM:
Keeping Vonage settings

OK, searched a little, but could not find an answer.
I know doing this will erase all my vonage setting, but is there a way to get them back so I can continue to use vonage but have full contorl of my router?
reply
neoalex4 @ 2nd Jan 07:49AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Is it possible to backup the voice settings as you would the rest of the router settings?
If yes how?
By the way, thanks for this post, works beautifully with my asterisk.
reply
niel8 @ 2nd Jan 05:20PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

hey rcilink, well i tried to edit file using hex editor, but i couldnt understand "Change HEX offset 23 from 4D to 4C." its like first binary file and hex editor i am trying my hand on, can you please have a look at the file i attatched and fix that for me? i did last four though.
reply
ayubsyz @ 5th Jan 12:04PM:
Re: [Vonage] Getting the encryption key for RTP300 & WRTP54G

Hi, this work but i am unable to download the required tiMAC.xml file as described. Can someone share...
reply
rcilink @ 5th Jan 12:49PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by niel8 :

...but i couldnt understand "Change HEX offset 23 from 4D to 4C." ...
Using your hex editor, count 23 bytes from the first byte of the file.
When you get to the 23rd byte position, you should see 4D.
Change it to 4C.

Hope that helps..
reply
niel8 @ 5th Jan 09:12PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

well everything just went right, unit is unlocked and up and running for stanaphone, well a question though, y is it still at 192.168.15.1 with admin user name pass user/tivonpw? i thought i will b at 192.168.0.1 with admin username and pass Admin/- , NO complaints tho, thanks a lot for all this help, also the firmware reads 3.1.17 not 3.1.17-NA, is there any other firmware you have modded the WRTP54G-NA_fw_3.1.17_US available on linksys website?
reply
ii904 @ 6th Jan 12:49AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

could someone put rtp300 file here? it is same with wrtp54g fireware?
reply
niel8 @ 7th Jan 08:12PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

check this out, this is where i downloaded files and unlocked my rtp-300,
" »[Vonage] SIP credentials, RTP300, GPP_K?
"
follow rcilink's instructions on bottom of this page
"
»[Vonage] SIP credentials, RTP300, GPP_K?
"
you might wanna consider to go thru whole forum, it really helps.
reply
ii904 @ 7th Jan 11:17PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

hi all,
now my rtp300 is unlock and runing 3.1.10 mod firmware, but i want upgrade to 3.1.17,please help me to get the right firmware file,please help!
reply
niel8 @ 7th Jan 11:20PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

type 192.168.15.1/update.html
reply
anon @ 10th Jan 09:51AM:
Re: [Vonage] RTP300 Administration>firmware password after reset

I unlocked an RTP300 using CYT 3.9 and loaded 3.1.7 firmware provided by meister_sd. Thanks !

Once this was done noticed the username / password for the router was “admin” / “admin” and for the Administration > firmware tab was “Admin” / (blank). I was not asked for a password when configuring the Voice tab.

I factory reset the unit (both router and voice part) after the firmware "upgrade". I changed the password for the router (admin / new-password) and set user and admin password for the Voice tab. I however cannot access the Administration > firmware tab with username / password “Admin” / (blank). I cannot access it using the router or the voice tab user names (s) and password(s) either. Not sure what changed and why I cannot access it after a factory reset. Any help would be appreciated.

Thanks
reply
niel8 @ 11th Jan 05:45PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

the port forward for APPLICATIONS AND GAMING is not working, i flashed unit with the locked one and then the 3.1.17_modded one again, still having the same problem, it anyone else has the problem? is that the firmware?
i need it for playing Age of Empires online, any one familiar with loopback? i think it allows to recognise the public ip, can someone explain how to do that?
reply
IBEJohnson @ 16th Jan 02:39AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hello everyone,

I noticed one other person posted a question about the WRTp54G-ER, but everyone ignored him/her. Hopefully this doesn't happen to me. :)

This is the same device, but pre-configured for Earthlink. $39.99 at Fry's so its a no-brainer if I can figure out how to get it unlocked. Problem is, I can't access the Firmware Upgrade part of the Admin section. It requires a username/password that I don't have.

I attempted to use CYT 3.9 to no avail. I'm stuck and I.m hoping someone can help. Please Help!!!

IBEJohnson
reply
rcilink @ 16th Jan 08:31AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

We're working on the WRTP54G-ER unit at this time.

It is a lttle different firmware than the Vonage version. Because of this, the traditional unlocking methods will not work.

Stay tuned.
reply
IBEJohnson @ 16th Jan 11:07AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hey thanks for the quick response rcilink. You've been a great help on these boards!

I'll be curious to see when a solution exists for the Earthlink version. Hopefully soon, I was hoping to have my ViaTalk service go smoothly. Ha ha! Maybe I'll have to breakdown and have them send me the PAP2-NA. I really hate activation fees. :) :)

Keep us posted.

IBEJohnson
reply
qqura1 @ 20th Jan 02:18PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Hi,
Can I use this "rtp300_fw_3.···.von.zip" file to unlock RTP 300 NA or RTP 300 NR?
I'm not sure what is this NA or NR stands for but I ordered this for cheap price.
Thanks.
reply
adamsge @ 8th Feb 09:21AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

I used the Link here to the moded img and all went fine my wrtp54g is now running on 3.1.17-NA Thanks Also will it now be able to take firmware updates now from Linksys or will the files still need to be moded. Thanks again Jerry
reply
Oreb @ 9th Feb 04:03PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Worked through this forum last night and was able to successfully unlock my Linksys RTP300, load in the rtp300_fw_3.1.17_us.von.img and configure it to use the free incoming DID from stanaphone. Inbound calls are working great.

I had two questions:

1) I see that there is a tab for QoS under the Applications & Gaming tab but it doesn't appear to indicate a way to boost voip traffice over other traffic and if I'm uploading files my voice breaks up. I found a post in the vonage forums that the RTP300 doesn't really do QoS but wasn't sure if that applied to this firmware or not. Is there a way to protect voice traffic?

2) I notice that the time and date on the Voice info tab are from 2003. I was able to set the corect day and month and hours and minutes on the Regional tab but don't see a way to set the year. I'm not sure that the date and time matters but was curious. I didn't see anyway to point to a NNTP server or anything either. Any ideas?

Thanks!
reply
trade @ 9th Feb 05:05PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Is it possible to backup the voice settings as you would the rest of the router settings?
If yes how?
Somebody can explain me if the 3.1.17 version can works with Vonage.
TRADE
reply
Oreb @ 9th Feb 05:25PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I got the date and time to take successfully, mm/dd/yy and hh/mm. I don't see anything for nntp. I had set the time before and then it somehow reset to 1/1/2003 but I was able to just set it and it seems to be "holding".

Still wondering about the nntp and the QoS, or a way to reduce voice breakup when uploading a lot of data.
reply
bolaudio @ 12th Feb 04:34PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Latest firmware is »cfg.ipfon.pl/firmware/wrt-11.1.1···1201.img how to change crc ( CYWM to CYWL ) and load this to router ?
reply
anon @ 13th Feb 11:09AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Rcilink,

Thanks for the greate help. Do you recommend 3.1.17 firmware or the 10.00.62?
What is the right digit map for a WRTP54G? is it the following: *xxT|*1xx|[349]11|1xxx[2-9]xxxxxx|[2-9]xxxxxxT|[2-9]xxxxxxxxx|011x.T

Appreciate your help!

Wiss
skydive36@hotmail.com
reply
bombel321 @ 14th Feb 12:07AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

I have newest firmware for us.

3.1.22.ETSI . Version for ex-Vonage WRTP54G (CYWM changed to CYWL and recalculated checksum).

All passwords as in 3.1.17 (upgrading firmware does not reset configuration of router and voice).

Some bugs fixed (e.g. Ping and Traceroute).
Works ok.

Size: 3 866 632 Bytes
MD5: 7316e897b644a421385fa2aac1d8aee6

edit:
Great idea from PAP2 is now in ours WRTP54G! dial: ****
Example, for get know yourr IP dial: ****110#

You can also enable/disable web configuration or restart router remotely.

Complete list of codes is on page 8 of PAP2T user manual from www.linksys.com
reply
trade @ 14th Feb 10:09AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

I have a problem with the CYWL firmware on my Vonage router, actual version 3.1.17 try your file and pass throug but the firmware version still is the same, some way to detect if the new firmware is in my router now or need use some trick to install it.
Thanks

TRADE
reply
trade @ 14th Feb 10:26AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

What is the best firmware for the Vonage users?
I red all the thread and the most of the questions are how use this Vonage router with other providers. But few indications how use the 3.1.XX with Vonage.

Really I think tha Vonage don't care about give the user control over their routers, I prefer use 3.1.XX version but I don't know how setup the voice part yet.

Some indications says install the Vonage firmware, provision it and extract the Vonage XML config, but not indicate how implement on the router later when you upgrade to 3.1.XX Maybe I need a TFTP server on my PC.

So maybe RCLINK or somebody else could help give some indications about how use the 3.1.xx firmware with Vonage.

Thanks
TRADE
reply
rcilink @ 14th Feb 11:09AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

It sounds like you are trying to load 3.1.17-NA on a device you indend to use with Vonage.

I encourage you to review the terms of service for your Vonage service, as you will find that any modification/tampering (etc) with the telephone adapter gives them the opportunity to cancel your account.

Indeed, Vonage cares and will not give you access to the voice area of the router. There has been exceptions with the old Cisco ATA (they used to let you pay a small fee to get full access.. no idea if this is still a possibility).

With respect to the Vonage terms, CYT will not preserve any of your user account settings. The purpose of CYT was to allow you to "re-use" the device after you have discontinued your Vonage phone service. An effort to lower the number of units being tossed in the landfill..

Now, a more technical answer:

The Vonage WRTP54G most often will be found with 1.00.62 firmware. They are experimenting with some new versions (1.01.07 and 3.1.x versions have been spotted).

The 1.00.62 firmware uses a SIP (voice) interface that closely matches the RADVision SIP toolkit (it uses the SIP toolkit behind the scenes).

The 3.1.xx versions offer a different user interface for the SIP (voice) pages. Although it is still using some of the RADVision SIP toolkit, the 'look and feel' very closely resembles the Linksys PAP2 configuration menus.

A big difference between these versions is the provision system. The 1.00.62 handles provisioning in the router section of the device. The provision file can change settings in the router and the voice areas. This config file is encrypted with a RC4 key. The "factory" key appears to be a hash with the unique Admin password and the seed key stored in flash at factory burn-in. The 3.1.xx versions use a provision system similar to the Linksys PAP2 (based on SIPURA technology). This is very different and is not RC4 encrypted as previously done in the 1.00.62 version.

So, as you may imagine, the vonage provision server is not going to know that your device wants the new format provision file, and your device will never auto-provision itself.

For them to roll-out this upgrade, some "behind-the-scenes" stuff is done in the WRTP54G device. For example, a new partition is created in flash memory called "fpar". This is the partition that stores the SIPURA config. Previously, it was stored in the standard provision areas (CONFIG_A and CONFIG_B).

I am sorry I can not assist you in getting this firmware update working with Vonage. I am not saying it is impossible. It is just outside their TOS, so I am not going there. The choices you make are made by you, and by making such choices, you assume full liability for your actions.

To answer your original question: The best firmware for the Vonage users is the firmware they push to your device. Some have had success calling into the support line and asking them to downgrade (or upgrade) the firmware -- to try to fix problems (look at the vonage forums site for more info on them).
reply
trade @ 14th Feb 02:20PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

RCILINK:
Thank you for your extensive answer, I get a better idea what path take with Vonage service and my router. Could you refer where get new version firmware that Vonage is experimenting. I get one 1.00.64 but I red that Vonage downgrade to the 1.00.62 when connects.

Thanks
TRADE
reply
bombel321 @ 15th Feb 09:29AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have done the same to RTP300 firmware. CYLM changed to CYLL and checksum recalculated.

The newest firmware. Version 3.1.22
For ex-Vonage users, who have access to upgrade page.

Size: 3 866 632 bytes
MD5: 36431751bfa0975e553c081af29f23c3
reply
bolaudio @ 15th Feb 01:36PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

@bombel
Thanks for recalculate CRC
reply
bombel321 @ 15th Feb 03:23PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

english here only ;P

zglos sie do mnie na gg:3220970
reply
carmatt59 @ 16th Feb 09:29PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by rcilink :

1. Change HEX offset 23 from 4D to 4C.

2. Change the last four bytes to: AB 3A 49 5D
Hey RC.
I have a question.
Do you suppose to include the very first byte when you do your math thing?
You might think it's weird that I ask, but look in the attachments, please.
Actually 4d byte is number 24, if you start counting from the very first one (43)...
Are the four bytes colored-circled in my attachment the last four you are talking about?

Thanks much.
Click for full size
Click for full size
reply
rcilink @ 16th Feb 11:44PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

That HEXedit software you are using wants to display (at the bottom) the current 'position', not the 'offset' value. The HEXedit software I use will tell me the offset at the bottom of the screen view.

The offset is supposed to be the number of bytes from the first byte. So, 23 bytes from the first byte is the "4D" in that firmware that gets changed to "4C".

Hope this helps you out.
reply
Oreb @ 17th Feb 06:03PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I tried the rt-11.1.1-r061201-3.1.22-r061201.img in my ex-Vonage RTP300 but couldn't connect out to the internet even after rebooting my cable modem. Any attempts to ping out resulted in time outs. I fell back to the rtp300_fw_3.1.17_US.von.img and was immediately connected back to the internet. Not sure if I did something wrong but I think I'll wait to upgrade until I hear from more folks who try 3.1.22.
reply
KillaB7 @ 18th Feb 12:41AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Any new features in 3.1.22?
I've been hoping for SRTP support (like in the Sipuras) for awhile now.
reply
carmatt59 @ 19th Feb 03:50AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by rcilink :

The offset is supposed to be the number of bytes from the first byte. Hope this helps you out.
That makes sense, of course.
Tks.
reply
mikev6 @ 20th Feb 01:59AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by bombel321 :

I have newest firmware for us.

3.1.22.ETSI . Version for ex-Vonage WRTP54G (CYWM changed to CYWL and recalculated checksum).
Is there an original version of the 3.1.22 firmware? While an already-modified version of the file is certainly much easier to work with, I prefer to do all the modifications myself... yanno, it never hurts to be safe when working with this kind of stuff. :)

A link to the Linksys site would be required for me to believe it trustworthy.

Thanks!
reply
bombel321 @ 21st Feb 02:55PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

There won't be link to for-usa-customers-only linksys site, because wifi channels 12-14 are in usa banned, so linksys can't release it for you.

The firmware i uploaded is European version, but WRTP54G , WRTP54G-NA and WRTP54G-EU have all the same hardware.
reply
mikev6 @ 27th Feb 02:33PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Linksys updated their site, and no longer has the WRTP54G-NA listed as a model on their site. Will the RTP300 firmware work just as well (after the modifications of course), or will that firmware disable the wireless capability since the RTP300 doesn't have WiFi?
reply
KillaB7 @ 28th Feb 02:37PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

I know it's easy to modify NA firmware images to load onto our routers but has anyone tried changing the ProductID under PSPBoot?

I've enabled console access on my WRTP, but don't want to attempt any changes just yet.
»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G

It might be as easy as simply changing the environment variable then rebooting. Or you may need to TFTP an NA image (matching ProductID) before rebooting???
reply
borivanov @ 28th Feb 04:58PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Dear meister_sd and all respected forum members,

Is any solution that allows fully unlock RTP300-VD to RTP300-NA? So locked RTP300-VD will become fully unlocked RTP300-NA (original firmware 3.1.17 from linksys.com WITH FULL functionality can be loaded to unlocked RTP300-VD)

Thanks.

Kind regards,
Boris.
reply
KillaB7 @ 28th Feb 05:02PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

@borivanov

That's what I'm trying to do in my last post.
I'll try it on an RTP300 tomorrow, just don't want to risk a WRTP.
reply
neoalex4 @ 1st Mar 01:51PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Thank you so much for the new firmware bombel. Works great, I will know more after I test it for a few weeks, to see how it holds. But thank you. There's one thing I don't understand, on the first page, when it asks me for my user name and password I see the word "age" in the top left corner, why is that?
reply
KillaB7 @ 1st Mar 02:02PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Well, I tried but it looks like ProductID is in protected memory.
Tried within BusyBox and PSPBoot.

#echo "ProductID CYLM" >/proc/ticfg/env
Sep  8 12:00:29 [0014xxxxxxxx] : adam2_env_set_variable(ProductID,CYLM) 1
Sep  8 12:00:29 [0014xxxxxxxx] Env: ProductID is read-only.
Sep  8 12:00:29 [0014xxxxxxxx] : Defragmenting environment variable region.
Sep  8 12:00:29 [0014xxxxxxxx] : adam2_env_set_variable(ProductID,CYLM) 1
Sep  8 12:00:29 [0014xxxxxxxx] Env: ProductID is read-only.
Sep  8 12:00:29 [0014xxxxxxxx] : Failed to write ProductID to environment variable region.

reply
aquaregia @ 6th Mar 08:49PM:
Proper firmware shenanigans

You guys are scaring me with md5's and what not, so I'll show you how to properly put a foreign firmware on a locked router (well, it's not really locked, but whatever)

Step one: Download a *virgin* firmware from linksys for whatever router you wish to have. For example:

RTP300-NA: CYLM
RTP300 from Vonage: CYLL
WRTP54G-NA: CYWM
WRTP54G from Vonage: CYWL

Pick a router that you want, and remember your original Product ID.

Step two: RTFM. Seriously. If your router bricks, catches on fire, and/or rises up and slays you, I'm not responsible.

»wiki.openwrt.org/OpenWrtDocs/Har···/WRTP54G

Step 3: Now that you know more about the WRTP54G than you might care to.

Issue the following commands. Yeah, on your own console. If you don't know what perl is, just stop and give up. The scripts can be found on the previous page, as well as the product codes above (Use your original product code.)

# perl set_ProductID firmware.img CYxx
# perl set_ti_checksum firmware.img

That's it. Go to the upgrade page, use the new firmware, and your RTP or WRTP is now NA (Non-Affiliated). While more complex, this works for any version of firmware.

UPDATE 060307: Some new Product ID's out there. I'll let you know.

For the very brave, the OpenWrt Wiki has a funky 3.1.17-NA firmware image with ssh and dropbear enabled. Be warned, it is enabled from outside the WAN with no password and no way to disable it.

Enjoy.
reply
aquaregia @ 6th Mar 09:36PM:
Re: Proper firmware shenanigans

Also, while I don't have one, I don't see why this won't work for any other flavor AR7 RTP. Ala Earthlink, VD (Vodafone?), et al.
If you know of other Product ID's, please let me know.
reply
aquaregia @ 6th Mar 09:44PM:
Re: Proper firmware shenanigans

In addition, for security reasons, downloading firmwares for a full Linux box from untrusted sources is a very, very bad idea. Feel free to peruse the OpenWrt Wiki, and the perl scripts, at your leisure. Do it yourself!
reply
aquaregia @ 6th Mar 09:50PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Check out my new post, Boris.
reply
aquaregia @ 6th Mar 09:51PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Check out my latest post.
reply
jmontalvo1 @ 11th Mar 10:45AM:
Re: It will work someday ;)

This is what I need to make my rtp300 work, but i'm very newbbie to do it. Plz some dummie's guide to do this procedure.
Thks !
reply
chinna24 @ 18th Mar 04:53AM:
User not enabled to login into the system - for RTP300

I am getting " User not enabled to login into the system" messsage when I try to login at update.html using user as userid. Is there is a way enable this account? Any help is appreciated.

Thanks in advance
reply
kipa @ 20th Mar 03:43PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Very nice site. I have my Vonage router unlocked!
Wov!

Does anyone know whether it works also for EARTHLINK ?


My friend asked me for advice - he has Earthlink dedicated WRTp54G router.

Thanks in advance for reply and again for HEX edit codes!
reply
neoalex4 @ 20th Mar 06:00PM:
WRTP54g DST rule

WRTP54g DST rule

Does anyone know what I should write in the DST rule in my Regional Settings on my WRTP54G. The rule should be:
* begins at 2:00 a.m. on the second Sunday of March and
* ends at 2:00 a.m. on the first Sunday of November

Please help thanks.
reply
alphamale @ 21st Apr 07:55PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I tried to upgrade my RTP300 1.00.62 firmware to 3.1.10 via the "TFTP 192.168.15.100 get rtp300-3-1-10.bin test.bin" DOS command on my laptop but I always get a timeout error.

What could I be doing wrong? Any help would be greatly appreciated.
reply
KillaB7 @ 2nd May 10:02AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

3.1.24-NA is out (3.1.22 Voice)
I've loaded it on my WRTP54G after modifying the usual header and checksum.

Still no SecureRTP like in the Sipura/PAP2's. What gives Linksys?
reply
larwilliams @ 7th May 03:38PM:
Re: Proper firmware shenanigans

Hi,

How can I access the RTP300 via SSH? I had the modded 3.1.10 firmware installed, with Secure Shell enabled. I tried Putty SSH to 192.168.15.1 (the confirmed IP of the adapter), but the connection is immediately refused.

The rest of your instructions make sense (I am a full-time programmer, including Perl et shell), but i cannot get to the console to execute any of the commands.
reply
larwilliams @ 7th May 04:07PM:
Re: Proper firmware shenanigans

Nevermind, you probably meant on a console in general. Not the router... just a pc with Perl installed.
reply
celiomartins @ 9th May 12:25PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Does Anyone has tryed the new 3.1.23.ETSI??
I haven't!

But i have the IMG here....
would it be the same procedure to make it cmwl?

[mod note: firmware removed, not allowed according to forum rules]
reply
celiomartins @ 9th May 12:44PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I just noticed another thing...
After updating the firmware to 3.1.22.ETSI (not .23) when I try to enter the page to upload a new one....
Update.html the:

user:tivonpw doesn't work anymore...

What is the new user/pass???

Thanks!
reply
Kiwi @ 12th May 10:14PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I'm bumping this to keep it 'ALive' For those that can appreciate the efforts made. I had this on my 'Watch' list. Very informative thread.

Cheers
reply
ptrowski @ 21st May 10:54AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by KillaB7 :

3.1.24-NA is out (3.1.22 Voice)
I've loaded it on my WRTP54G after modifying the usual header and checksum.

Still no SecureRTP like in the Sipura/PAP2's. What gives Linksys?
My RTP300 is running 1.00.62-NA and I tried the FW upgrade to 3.1.24 but got invalid code pattern. Any ideas why?
--
"A religious war is like children fighting over who has the strongest imaginary friend."

Have you been touched by his noodly appendage? »www.venganza.org
reply
KillaB7 @ 21st May 10:03PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

For a Vonage RTP300 you need to find and change CYLM to CYLL (4D to 4C at position 17h).
Also, the calculated checksum at the end of the firmware needs to be changed from "85 DA 20 BB" to "3B A5 4D DA".

For a Vonage WRTP54G you need to change CYWM to CYWL (4D to 4C at position 17h).
Also, the calculated checksum at the end of the firmware needs to be changed from "71 FB 16 5F" to "CF 84 7B 3E".

If you want to know how to do this yourself for future firmware releases I suggest you download a GPL source tarball and learn how to compile tichksum using something like Cygwin.
I would also recommend MinGW but for some reason it calculates wrong checksums for me.
»www.seattlewireless.net/DlinkDsl···db35ab37
reply
ptrowski @ 22nd May 08:05AM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thanks KillaB7. That is a bit above my abilities.
reply
skr1p7k1dd @ 4th Jun 12:36PM:
Re: RTP300 firmware update RTP300-3-1-10.bin

i cant download it =[
reply
boonkang @ 12th Jul 03:22PM:
Re: Getting a WRTp54G to take 3.1.17-NA...

Hello, Rcilink.

I have a VTech IP8100, like WRTP54G and RTP300, it runs a TI AR7 platform.
Does this mean that IP8a00 can also take the advantage of firmware like 1.00.62-NA and 3.1.17-NA ?
reply
wumarkus @ 1st Sep 11:16PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

thanks for the info - I edited the firmware on 3.1.24 and it worked great. I'm attaching it for anybody who's afraid of hex editing. It's for former Vonage RTP300's.
reply
shmaks @ 5th Sep 10:49PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thank you so much wumarkus. I was just going to write a post asking where I can download a modded firmware.
reply
anon @ 17th Sep 12:12PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

I have been reading page after page of this post and I am truly impressed with you guys and what you have done to allow us to freely use the RTP300, but, I am also very confused trying to follow the steps to free up the unit.
Could someone point me to a location where I could obtain the latest "NA" firmware and step by step instructions on how to apply it to a Vonage RTP300?
reply
mazilo @ 18th Sep 10:07PM:
Re: [Vonage] SIP credentials, RTP300, GPP_K?

said by Bill_S :

Could someone point me to a location where I could obtain the latest "NA" firmware and step by step instructions on how to apply it to a Vonage RTP300?
AFAIC, you should not do this on your RTP300 which is still served by Vonage. Doing so will cause your service to an earlier termination by Vonage. If your RTP300 device is no longer used with a Vonage service, then follow the links in this post to find out how to achieve what you want. Good luck.
reply
meister_sd @ 23rd Sep 12:36AM:
Re: Getting a WRTp54G to take 3.1.17-NA...

said by boonkang :

Hello, Rcilink.

I have a VTech IP8100, like WRTP54G and RTP300, it runs a TI AR7 platform.
Does this mean that IP8a00 can also take the advantage of firmware like 1.00.62-NA and 3.1.17-NA ?
No. It doesn't work this way. But you can still use CYT to unlock it.
reply

Thank you for using lo-fi dslreports.com - report bugs
© 99-2009 silver matrix LLC