Yeah, still not working for me either, but I agree that this beta version is much better overall than the 2005 edition. As for the GTalk2VoIP service, it is awesome and couldn't come at a better time. I'd like to thank everyone on the GTalk2VoIP working so hard to make the service work on the 770.

Yeah, the service has crashed this night :-(. Looks like I have injured a bug while did modifications for N770 compatibility. Workig on it..

Regards,
Ruslan.

Is there a way to use the gtalk2voip service to call a packet8 number via SIP?
With FWD you just dial **898+1+number.
I tried "call **8981xxxyyyzzzz@packet8.net" and it just sat there trying to call but my packet8 number did not ring. Any ideas?

What you put to GTalk2VoIP is a SIP ID. If that SIP ID can be dialed on an ordinary SIP phone (SJPhone, etc..) so it will work with our gateway too. Try to figure it out how that FDW number is accessable from a SIP phone and let me know so I could check it.

As for your case, here is what we have got in our logs:

SIPConnetion::WritePDU writing raw data, time (usec) = 1150954257722440:
INVITE sip:**898171XXXXXXXX@packet8.net SIP/2.0^M
CSeq: 1 INVITE^M
Via: SIP/2.0/UDP 217.116.51.36;rport;branch=00000000001234560000000 000123456000000000012345^M
User-Agent: GTalk2VoIP V2 by RZ and UGIN^M
From: "gururise@gmail.com"<sip:gururise@gmail.com>;tag=1 73635150^M
Call-ID: SIPCALL-1359133527-1976348468@217.116.51.36^M
To: <sip:**898171XXXXXXXX@packet8.net>^M
Contact: <sip:217.116.51.36:5060;transport=udp>^M
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REFER, INFO, NOTIFY, MESSAGE^M
Content-Type: application/sdp^M
Content-Length: 298^M
Max-Forwards: 70^M

SIP/2.0 407 Proxy Authentication Required^M
CSeq: 1 INVITE^M
f: "gururise@gmail.com"<sip:gururise@gmail.com>;tag=1 73635150^M
Call-ID: SIPCALL-1359133527-1976348468@217.116.51.36^M
t: <sip:**898171XXXXXXXX@packet8.net>;tag=abKJDtJMads U^M
Record-Route: <sip:aZO4q64DYfqzfVDhUId@63.209.12.145:5111;lr>, <sip:aiz2kX7GdBfuPazPfFIAIaNcXGh@192.84.16.30:1506 2;lr>^M
v: SIP/2.0/UDP 217.116.51.36;rport=5060;branch=000000000012345600 00000000123456000000000012345;received=217.116.51. 36^M
Server: eSLEE/0.12.38.1^M
l: 0^M
Proxy-Authenticate: Digest realm="packet8.net", nonce="76f26146856b60e321d6819bcf486b3e"^M
^M

The remote side required some sort of Proxy Authentication. We cannot do it since we don't have any credentials from your SIP account on packet8 proxy.

Regards,
Ruslan.

The GTalk2VoIP development team.

The Gtalk2voip service was down yesterday as many you did notice too... This morning it was up and running and I did the test without my Vonage adapter connected in my network. The result was the same as above. I even tried to "borrow" neighbors WiFi :o for a second to test it with it, but no difference in behavior.

What's next? Ruslan, can you check some logs in your system to find out any clues? Let me know if you need my Gtalk accoung name and I can PM it to you.

The service is up again and I am able to use the call +1xxxxxxx feature through the chat bot with success. I noticed that if you hang up on the 770 the service continues to call the number resulting in the phone continuing to ring. Just thought that info might help somehow. Now we need an option to buy more credits through PayPal, and the phone number lease service. After that, everything else is gravy.

whats up with service@gtalk2voip
 

It was down all day yesterday, this morning it was up for one of my accounts but the other could not reach it, and now again neither can reach it. Whats the deal with the up and down :confused:

gtalk2voip is unreliable
 

its gone down again which is quite irritating. I have been monitoring before buyin any credits and find the client to be a bit unreliable

Has anyone heard of this company? I dont want 2 start giving credit card details to an unknown Russian or Eastern European outfit......

You don't give CC number to us, you give it to some Merchant which process the payment. The one we are using now is located in Amsterdam. But you don't have to trust it either, cause they smoke pots there ;-)))

Yes, the service became unstable, that is due to that goddamn fix for Nokia 770. If I won't find a solution on how to make it stable I'll just remove all modifications I made to support your Nokias.

Thank you Mara for expressing your desire to help. We are currently working on making that bloody patch a bit more stable (bot crashes each 5 mins due to some bug in the patch), after that I'll contact you to investigate your case.

Regards,
Ruslan.

The GTalk2VoIP development team.