C2C still not working on WRTP54G with 1.00.43 firmware...

Posts: 38 · Vonage Forum Junior Joined: Jul 28, 2005 Posts: 38

Vonage pushed the .43 firmware to me tonight. My first test was to see if Click-2-Call had been fixed. Placed the call through the applet and my phone rang, this looked promising. When I picked the call up there was only silence. Tried it several other times with my cell phone and still nothing. So I tried to manually dial my cell phone and the call would go through. Attempted a C2C and this time it rang my cell phone when i picked up on the Vonage line but when I picked up the cell phone there was no audio going either way. Power cycled router with no effect. Anyone else having this problem?

Posts: 79 · Posted: Mon Aug 22, 2005 12:25 am Post subject:

I got my update to 1.00.43 on my WRTP54G on Friday and my C2C works just fine. When I tested it just now, it took 3-5 seconds for the call to setup and ring once I answered the inbound C2C call but it works without an issue.

- Mark

Posts: 192 · Posted: Mon Aug 22, 2005 7:17 pm Post subject:

I have the WRTP54G also. I tested C2C today by initiating a call to my work number. The phone rang in the house, my wife picked it up, the phone in my office rang, I picked it up and the connection was fine.

The firmware upgrade seemed to fix it for me.

Posts: 38 · Vonage Forum Junior Joined: Jul 28, 2005 Posts: 38

This all sounds promising, maybe it is just something in my config and will be resolved by Vonage tech support soon...

Posts: 40 · Full Forum Member Joined: Jul 03, 2005 Posts: 40

As another data point, C2C doesn't work for me either with 1.00.43 on my WRTP54G. Tonight is the first time I actually installed Vonage's program and tried it. It actually did work for the very first call--I made it from Outlook, using the COM adapter, and it all went fine--it even took no more than a second for my phone to ring for the first part of the dialing procedure. However, after that first call (a 1-minute message left on voicemail) a second call worked to be initiated, was dialing, and suddenly stopped. At some point I realized that my Motorla SB 4100 cable modem (to Comcast) wasn't showing a network connection, so i figured that was just what had happened--an oddly-timed interruption of service. It synced up though after power cycling it.

However at that point i noticed that I couldn't even ping the WRTP54G. A power cycle of that solved that problem, and I had LAN/WAN connectivity again. And still do, but now any C2C calls made, whether via Outlook or F6'ing a selected number, go through the computer almost instantly, cause my Vonage phone to start ringing almost instantly (and my Simulring cell phone soon thereafter), but lead to nothing but silence when I pick up the Vonage line. But at least each of these unsuccessful ones haven't been followed by a loss of Internet connectivity.

Here's the 4 lines the WRTP54G's logger produces with every C2C attempt.

Code:

2005-09-01 21:06:46 Kernel.Warning Router [xxxMAC addressxxx] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000
2005-09-01 21:06:46 Kernel.Warning Router [xxxMAC addressxxx] : VP880SetRelGain(gx=-6,gr=0)
2005-09-01 21:06:46 Kernel.Warning Router [xxxMAC addressxxx] : VP880SetRelGain(gx=0,gr=0)
2005-09-01 21:06:46 Kernel.Warning Router [xxxMAC addressxxx] : putting dsp in tight loop status=1

Posts: 38 · Vonage Forum Junior Joined: Jul 28, 2005 Posts: 38

YES!!! This sounds like the exact same problems I have been having. It will work for one call and the very next one, not. How do you generate that log? I will see if my router is producing the same entries.

E-Gads

Posts: 40 · Full Forum Member Joined: Jul 03, 2005 Posts: 40

I generated them via http://www.kiwisyslog.com/info_syslog.htm Kiwi, a logging daemon and browser that runs on Windows and that I saw mentioned by temproductions vonage-forum.com/ftopic7839.html" rel="nofollow" target="_blank" class="postlink">here. The way the WRTP54G logging works is that the router sends SNMP messages to the destination IP address, where something needs to be expecting them and recording them. This is different from my old Linksys 4-port switch, which also had the ability to just display recent activity logs via a web page.

Anyway, I installed Kiwi's logging daemon as a service on XP Pro on my desktop, set the WRTP54G to enable logging and send it to my desktop's IP address (desktop uses a fixed address, not DHCP), and then configured the Kiwi log viewer program (File->Setup->Inputs) to log SNMP messages (port 152). Lastly I had to both add/enable a UDP port 152 exception to Windows Firewall and and add "C:\Program Files\Syslogd\Syslogd_Service" as a program exception to the firewall as well.

Once set up you don't need the log-viewing client running as long as the logging service is started. The log-viewer only seems to show the most recent messages for me as well, but all messages are stored in the logging file (something like "C:\Program Files\Syslogd\Logs\SysCatchAll.txt" ... I'm not at home but it's both specified in the Kiwi setup and also in a Logs subdirectory under its Program Files location.

Posts: 38 · Vonage Forum Junior Joined: Jul 28, 2005 Posts: 38

Here is my syslog:

09-05-2005 21:40:38 Kernel.Warning 192.168.15.1 [xxxxxxxxxxxx] DSP mult: 10 Input clock: 12288000, final DSP speed: 122880000

09-05-2005 21:40:38 Kernel.Warning 192.168.15.1 [xxxxxxxxxxxx] : VP880SetRelGain(gx=-6,gr=0)

09-05-2005 21:40:39 Kernel.Warning 192.168.15.1 [xxxxxxxxxxxx] : VP880SetRelGain(gx=0,gr=0)

09-05-2005 21:40:39 Kernel.Warning 192.168.15.1 [xxxxxxxxxxxx] : putting dsp in tight loop status=1

Looks pretty much identical to yours. I got a Vonage CSR to reopen my original ticket on this issue so if I get any satisfaction I will let you know.

Posts: 40 · Full Forum Member Joined: Jul 03, 2005 Posts: 40

Yeah, I think those "warnings" are really just debug output every time a C2C is placed. I do have an update however--as of yesterday I placed 3 or 4 successful C2Cs with no failures at any time. It could be the 1.00.45 update that fixed it, or perhaps it's some other random transient bug that will resurface at a later date.