Re: Getting a WRTp54G to take 3.1.17-NA... in Vonage

Re: Getting a WRTp54G to take 3.1.17-NA...

Sun, 23 Sep 2007 00:36:31 EDT

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.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 18 Sep 2007 22:07:29 EDT

mazilo :

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.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 17 Sep 2007 12:12:20 EDT

anon : 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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 05 Sep 2007 22:49:04 EDT

shmaks : Thank you so much wumarkus. I was just going to write a post asking where I can download a modded firmware.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 01 Sep 2007 23:16:41 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 12 Jul 2007 15:22:57 EDT

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 ?

Re: RTP300 firmware update RTP300-3-1-10.bin

Mon, 04 Jun 2007 12:36:28 EDT

skr1p7k1dd : i cant download it =[

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 22 May 2007 08:05:22 EDT

ptrowski : Thanks KillaB7. That is a bit above my abilities.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 21 May 2007 22:03:37 EDT

KillaB7 : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 21 May 2007 10:54:57 EDT

ptrowski :

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 12 May 2007 22:14:59 EDT

Kiwi : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 09 May 2007 12:44:49 EDT

celiomartins : 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!

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 09 May 2007 12:25:41 EDT

celiomartins : 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]

Re: Proper firmware shenanigans

Mon, 07 May 2007 16:07:08 EDT

larwilliams : Nevermind, you probably meant on a console in general. Not the router... just a pc with Perl installed.

Re: Proper firmware shenanigans

Mon, 07 May 2007 15:38:29 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 02 May 2007 10:02:04 EDT

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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 21 Apr 2007 19:55:19 EDT

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

WRTP54g DST rule

Tue, 20 Mar 2007 18:00:26 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 20 Mar 2007 15:43:54 EDT

kipa : 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!

User not enabled to login into the system - for RTP300

Sun, 18 Mar 2007 04:53:41 EDT

chinna24 : 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

Re: It will work someday ;)

Sun, 11 Mar 2007 10:45:06 EDT

jmontalvo1 : 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 !

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 06 Mar 2007 21:51:57 EDT

aquaregia : Check out my latest post.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 06 Mar 2007 21:50:47 EDT

aquaregia : Check out my new post, Boris.

Re: Proper firmware shenanigans

Tue, 06 Mar 2007 21:44:40 EDT

aquaregia : 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!

Re: Proper firmware shenanigans

Tue, 06 Mar 2007 21:36:57 EDT

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

Proper firmware shenanigans

Tue, 06 Mar 2007 20:49:21 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 01 Mar 2007 14:02:38 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 01 Mar 2007 13:51:44 EDT

neoalex4 : 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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 28 Feb 2007 17:02:50 EDT

KillaB7 : @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.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 28 Feb 2007 16:58:51 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 28 Feb 2007 14:37:28 EDT

KillaB7 : 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???

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 27 Feb 2007 14:33:07 EDT

mikev6 : 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?

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 21 Feb 2007 14:55:57 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 20 Feb 2007 01:59:49 EDT

mikev6 :

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!

Re: Getting a WRTp54G to take 3.1.17-NA...

Mon, 19 Feb 2007 03:50:24 EDT

carmatt59 :

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.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sun, 18 Feb 2007 00:41:53 EDT

KillaB7 : Any new features in 3.1.22?
I've been hoping for SRTP support (like in the Sipuras) for awhile now.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 17 Feb 2007 18:03:07 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 16 Feb 2007 23:44:07 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 16 Feb 2007 21:29:19 EDT

carmatt59 :

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.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thu, 15 Feb 2007 15:23:36 EDT

bombel321 : english here only ;P

zglos sie do mnie na gg:3220970

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thu, 15 Feb 2007 13:36:34 EDT

bolaudio : @bombel
Thanks for recalculate CRC

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thu, 15 Feb 2007 09:29:52 EDT

bombel321 : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 14 Feb 2007 14:20:34 EDT

trade : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 14 Feb 2007 11:09:09 EDT

rcilink : 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).

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 14 Feb 2007 10:26:51 EDT

trade : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 14 Feb 2007 10:09:24 EDT

trade : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 14 Feb 2007 00:07:03 EDT

bombel321 : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 13 Feb 2007 11:09:42 EDT

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 12 Feb 2007 16:34:36 EDT

bolaudio : 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 ?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Fri, 09 Feb 2007 17:25:15 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 09 Feb 2007 17:05:17 EDT

trade : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Fri, 09 Feb 2007 16:03:45 EDT

Oreb : 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!

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 08 Feb 2007 09:21:04 EDT

adamsge : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 20 Jan 2007 14:18:45 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 16 Jan 2007 11:07:34 EDT

IBEJohnson : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 16 Jan 2007 08:31:11 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 16 Jan 2007 02:39:23 EDT

IBEJohnson : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 11 Jan 2007 17:45:55 EDT

niel8 : 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?

Re: [Vonage] RTP300 Administration>firmware password after reset

Wed, 10 Jan 2007 09:51:10 EDT

anon : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Sun, 07 Jan 2007 23:20:03 EDT

niel8 : type 192.168.15.1/update.html

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sun, 07 Jan 2007 23:17:12 EDT

ii904 : 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!

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sun, 07 Jan 2007 20:12:22 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 06 Jan 2007 00:49:02 EDT

ii904 : could someone put rtp300 file here? it is same with wrtp54g fireware?

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 05 Jan 2007 21:12:12 EDT

niel8 : 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?

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 05 Jan 2007 12:49:43 EDT

rcilink :

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

Re: [Vonage] Getting the encryption key for RTP300 & WRTP54G

Fri, 05 Jan 2007 12:04:21 EDT

ayubsyz : Hi, this work but i am unable to download the required tiMAC.xml file as described. Can someone share...

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 02 Jan 2007 17:20:59 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Tue, 02 Jan 2007 07:49:27 EDT

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

Keeping Vonage settings

Fri, 29 Dec 2006 19:54:54 EDT

anon : 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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sun, 24 Dec 2006 04:26:07 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 15 Dec 2006 15:09:39 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thu, 14 Dec 2006 22:34:12 EDT

myvoip07 :

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.

Re: Getting a WRTp54G to take 3.1.17-NA...

Mon, 11 Dec 2006 15:27:51 EDT

radom11 : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Mon, 11 Dec 2006 13:17:43 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Mon, 11 Dec 2006 13:01:19 EDT

radom11 : 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:

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Sat, 09 Dec 2006 21:04:42 EDT

niel8 : 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?

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 08 Dec 2006 08:24:13 EDT

rcilink :

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 08 Dec 2006 08:06:39 EDT

anon : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 07 Dec 2006 15:40:37 EDT

anon : 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

Re: Getting a WRTp54G to take 3.1.17-NA...

Sat, 25 Nov 2006 20:53:11 EDT

anon : Hi,
I found the problem with img size, it was my download manager.

Re: Getting a WRTp54G to take 3.1.17-NA...

Fri, 24 Nov 2006 23:02:38 EDT

anon : 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 ?

Re: Getting a WRTp54G to take 3.1.17-NA...

Thu, 23 Nov 2006 19:01:08 EDT

anon : How do you upgrade the firmware on WRTP54G? There is not such an option under the Administration menu. HELP!

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Thu, 23 Nov 2006 17:05:48 EDT

niel8 : also is it possible to replace the firmware of this rtp 3oo with spa2102-NA?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 22 Nov 2006 14:58:26 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA...

Wed, 15 Nov 2006 02:27:35 EDT

anon : this works!

Re: New firmware version 3.1.18

Mon, 13 Nov 2006 20:21:55 EDT

mijoe : 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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 13 Nov 2006 19:32:28 EDT

ii904 : wherw are you got 3.1.17 fireware? could you link to download?thanks

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 13 Nov 2006 15:44:20 EDT

speed_spec : 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?

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 07 Nov 2006 00:36:26 EDT

anon :
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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 07 Nov 2006 00:15:22 EDT

anon : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Mon, 06 Nov 2006 04:53:31 EDT

anon : does all of this apply to wrtp54g-er (for earthlink) too ??

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 03 Nov 2006 15:04:46 EDT

campuschill : fixed it, had to remove nat=yes in the general sip.conf

Asterisk box behind a router...

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 21:29:34 EDT

campuschill : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 20:02:54 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 11:00:10 EDT

anon : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 10:24:24 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 08:30:10 EDT

zimmy6996 : »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.

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 08:27:25 EDT

zimmy6996 : 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?

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 00:32:28 EDT

anon : campuschill,

post your configs and also debug logs and i'll have a look

cheers

-p

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 00:31:14 EDT

anon : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Fri, 27 Oct 2006 00:06:10 EDT

zimmy6996 : 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?

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Thu, 26 Oct 2006 23:43:57 EDT

zimmy6996 : 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?

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Thu, 26 Oct 2006 18:51:06 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Tue, 24 Oct 2006 23:58:43 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Tue, 24 Oct 2006 11:21:09 EDT

anon : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Tue, 24 Oct 2006 10:45:48 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Sat, 21 Oct 2006 00:36:05 EDT

anon : 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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Wed, 18 Oct 2006 22:28:50 EDT

niel8 : 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

WRTP54G Unlocked ---- Thank you guys !!

Tue, 17 Oct 2006 00:08:23 EDT

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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Mon, 16 Oct 2006 16:44:52 EDT

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

Re: Getting a WRTp54G to take 3.1.17-NA... [ Still locked }

Sun, 15 Oct 2006 12:09:46 EDT

netmitra : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 11 Oct 2006 19:55:28 EDT

campuschill : Did you get incoming working, if yes can you post config. thanks

Re: RTP300 firmware update RTP300-3-1-10.bin

Wed, 11 Oct 2006 02:57:04 EDT

ScarEye : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 04 Oct 2006 16:37:49 EDT

anon : Oh -- forgot one more thing.

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

register=$username:$password@216.115.20.78:10000

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 04 Oct 2006 16:36:48 EDT

anon : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 04 Oct 2006 15:58:07 EDT

anon : 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

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 04 Oct 2006 15:04:40 EDT

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

Thanks all!

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Wed, 04 Oct 2006 14:59:13 EDT

meister_sd :

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.

Re: Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Tue, 03 Oct 2006 23:24:57 EDT

KillaB7 :

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.

Extracting SIP credentials from WRTP54G w/ v1.00.62 firmware

Tue, 03 Oct 2006 17:54:45 EDT

anon : 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!

Re: New firmware version 3.1.18

Mon, 02 Oct 2006 10:40:53 EDT

rcilink :

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.

Re: New firmware version 3.1.18

Mon, 02 Oct 2006 04:01:56 EDT

campuschill : Tried loading this firmware, i get a invalid code pattern error.

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Fri, 29 Sep 2006 12:45:33 EDT

daodao19 : :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:

Re: RTP300 firmware update RTP300-3-1-10.bin

Thu, 28 Sep 2006 12:42:13 EDT

darthschrade : You need to be logged in to download the file.

1.00.62 vs 3.1.17 For unlocking the RTP300?

Fri, 22 Sep 2006 11:12:46 EDT

Stroker : 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!!!

Re: New firmware version 3.1.18

Tue, 19 Sep 2006 00:05:33 EDT

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

Re: [Vonage] SIP credentials, RTP300, GPP_K?

Tue, 12 Sep 2006 11:32:39 EDT

daodao19 : 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?

Re: Getting a WRTp54G to take 3.1.17-NA...

Sat, 09 Sep 2006 00:29:14 EDT

sgonzalez : Can this be applid to the RTP300 router?

Re: RTP300 firmware update RTP300-3-1-10.bin

Fri, 08 Sep 2006 10:29:16 EDT

daodao19 : Hi,

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

Thanks,
Dario

New firmware version 3.1.18

Fri, 08 Sep 2006 09:38:43 EDT

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

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Thu, 07 Sep 2006 19:58:17 EDT

hollando : Thanks, rcilink. Just download a 1.00.60 GPL firmware from linksys. Hopefully this one don't give me much trouble in compiling.

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Thu, 07 Sep 2006 18:28:01 EDT

rcilink :

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.

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Thu, 07 Sep 2006 17:43:36 EDT

hollando :

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.

Re: wrt 1.00.62 firmware Termination digit

Thu, 07 Sep 2006 14:29:03 EDT

hollando :

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.

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Thu, 07 Sep 2006 08:36:31 EDT

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

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Wed, 06 Sep 2006 19:42:48 EDT

hollando : 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!

Re: wrt 1.00.62 firmware Termination digit

Wed, 06 Sep 2006 10:58:32 EDT

tkprojects :

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

Re: wrt 1.00.62 firmware Termination digit

Wed, 06 Sep 2006 02:55:14 EDT

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

Re: looking inside the wrtp54g (rtp300) firmware using Linux

Wed, 06 Sep 2006 01:59:53 EDT

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