I'm not sure if you mean they're not compatible or that Google Voice's services are going to trump the Peek's for SMS? Most likely not the latter, and it seems like the former is something that the Peek team can easily take care of in a software update or two.

Google Voice is VERY interesting to me. It seems like it could be great Peek 'teammate' in the game against cell phones. It would be sweet if the voicemail notification emails from gVoice could attach a simple sound file (like my trixbox at work) that the Peek could play.
{Sorry for the feature idea, I know that's taboo to just throw around here but hey Peek has to expect people to have their own ideas based on growing "Simply Email". All cool things get ripped off and progression is natural. Not that sound is an original idea I'm sure...}

Anyway I hope Google Voice gets opened to more people soon. I'm really trying to get myself and my gf off of contract cell phone plans and I think gVoice + Peek might be the way to go. Of course Skype has the same necessity features, but it's not totally free. It is quite cheap though and a promising option.

Anyone else have thoughts on GV and Peek?

I got a Google Voice account & tried to send a Peek text message to my Google Voice phone number today and got the following message (where 1112223333 is my Google Voice phone number:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
1112223333@cell.getpeek.net
retry timeout exceeded

===================================

Any idea if an update is in the works to make this go through?

Thanks Gabe,

I just tried it as an email to 1112223333 (where 1112223333 is my Google Voice phone number) and got the same result.

Frank, I was just looking into skype and the Voicemail to Spinvox option (translates voice to text). Skype implies Voicemail for any subscription, but Incoming costs extra. Are you automatically assigned a # direct to voicemail?

Oddly, they're getting my messages twice, so I'm having the opposite problem.

Okay here's something I don't understand.

Here's the work flow:

1. I send a text to someone's Google Voice phone number.
2. They reply
3. I hit 'reply' to reply to their reply.
4. Peek puts two email addresses in the 'to' box:

15038970729.14089059574.kKlxscKvPk@txt.voice.google.com,
15038970729.14089059574.kklxsckvpk@txt.voice.google.com

I can't delete one address from the 'To' box on the Peek without deleting the other.

So sending the message means my friend gets charged for two text messages because they get the same message twice.

Note that one of the addresses in the Peek's 'To' box is all lower case.

However, if I save the address as a contact it's added to the address in all lower case, and when I try to send a message using that contact it bounces because the address is in all lower case.

Here's what I don't understand:

If sending the message from my Contacts in all lower case doesn't work because of the case of the text, why does my friend get two text messages due to one address being in the 'To' box in lower case and one being in the correct case?

It seems like my only option for replying to a text message from Google Voice is to send them two copies or to send no copies.

Messages should still go through in all lower case, as we have confirmed testing with several accounts.

I agree with your "ideal" fix, but another possibility is to just fix the server-side duplication of To: field on replies where the field changes slightly (this is a fairly new bug and I think we'll see it fixed soon).

What you are seeing in the To: box is not 2 email addresses, but a name and an email address. Something like:

Bill <bill@email.com>

Except the full email address is getting tagged as the name. The second email is getting sent because it is stored in its partially capitalized version on the server.

Whoever you know who's paying 30¢ a message is really crazy.

This has been thoroughly discussed in another thread (the GV thread):

http://boards.getpeek.com/discussion/1487/the-peek-and-google-voice/