Free Service W/O MagicJack

patyork99 · Post by **patyork99** » Fri Oct 29, 2010 4:50 pm

Using a Linksys pap2 device and Whistlephone service: http://www.krunk4ever.com/blog/tag/linksys-pap2/

patyork99 · Post by **patyork99** » Fri Oct 29, 2010 10:29 pm

So, has anyone else used or had this setup?It was quite simple to do. and I am not particularly tech savvy.The ATA can be had on ebay for about $30.With some outgoing calls,you do have to listen to a 15 second ad,but it is hit or miss, it doesn't happen on every call and the quality is clear on both ends.I really was getting irritated with my MJ the last couple of months and this option was free.

bgfrmnyc · Post by **bgfrmnyc** » Sat Oct 30, 2010 10:26 am

I set it up and it works perfectly! No problems! Your phone number that is assigned is your username and the password you pick is your password, lol. Proxy is proxy.whistlephone.com. Took all of 2 minutes to enter the info into my pap2t ATA and all is fine. Incoming/outgoing working. Every 3rd or 4th outgoing call you will have to listen to a 15 second add which is no biggie IMHO. Free is free and actually some of the ads are interesting. Also has free 411 built in like magicjack.

yazyazoo · Post by **yazyazoo** » Sat Oct 30, 2010 10:59 am

Anyone try faxing with this on a call that doesnt have an ad?

Is there a way to use Google Voice number with this so if this company goes down we still have the GV number?

adam3914 · Post by **adam3914** » Sat Oct 30, 2010 4:28 pm

I just joined as well using a sunrocket ata with no problems.

N7AS · Post by **N7AS** » Sat Oct 30, 2010 5:21 pm

I have whistlephone working on my PAP2T-NA, but with incoming calls, the caller gets the "can't connect the call" message about 95% of the time.
Anybody else having this problem?

sabresfan · Post by **sabresfan** » Sat Oct 30, 2010 6:41 pm

N7AS wrote:I have whistlephone working on my PAP2T-NA, but with incoming calls, the caller gets the "can't connect the call" message about 95% of the time.
Anybody else having this problem?

Yes it's about half the time. I called verizon to see if it was a problem from my cell and they said no. It was just a little odd after I got off the phone with them all was working well.

RobbyG · Post by **RobbyG** » Sat Oct 30, 2010 9:25 pm

Even though Whistle doesn't officially support the use of an ATA, the incoming call problem also exists on the Windows client. I have a thread open in the Whistle forum, the latest is that they are blaming the problem on my router.

Can you guys do a test with the Windows client running? Call your Whistle number several times over a 5 minute period and see how many go through and how many get the "I'm sorry but I cannot complete your call". For me it's about 50/50, if you can post to my thread at least they will know it's not just me having the problem. Don't mention the use of the ATA since if you do they will just say "Sorry, we don't support it".

The last post by someone named Yuri said something about the fact that they have 4 servers and that it seems the problem is that incoming calls could come from any of the 4 servers even though my client program is only registered to one. Sounds like that person is on to something.

http://support.whistlephone.com/help/di ... ming-calls

msiam · Post by **msiam** » Mon Dec 06, 2010 2:05 pm

If you are worried about missing calls on the Whistlephone, as long as you have a number you can enter into the "Follow Me" then your problem is solved, it is a 50/50 chance that the Whistlephone will not ring, but the calls do go thru to the next number immediately to the next number, even GV. I'm hoping that they fix the problem and it all smooths out, Whistle gets some very clean calls, I have experienced choppy calls from my TK6000 a lot more often. Whistle is a very good service and I recommend it highly. Easy ATA use, but, you do lose some of the great features that the Soft Phone gives you, like the call conference , but it seems that the use of the ata and the SPhone at the same time isnt a problem, actually you can be on 2 calls on the S phone and still make another separate call from the ATA

cool..

stav · Post by **stav** » Mon Jan 31, 2011 2:10 pm

RobbyG wrote:Even though Whistle doesn't officially support the use of an ATA, the incoming call problem also exists on the Windows client. I have a thread open in the Whistle forum, the latest is that they are blaming the problem on my router.

Can you guys do a test with the Windows client running? Call your Whistle number several times over a 5 minute period and see how many go through and how many get the "I'm sorry but I cannot complete your call". For me it's about 50/50, if you can post to my thread at least they will know it's not just me having the problem. Don't mention the use of the ATA since if you do they will just say "Sorry, we don't support it".

The last post by someone named Yuri said something about the fact that they have 4 servers and that it seems the problem is that incoming calls could come from any of the 4 servers even though my client program is only registered to one. Sounds like that person is on to something.

http://support.whistlephone.com/help/di ... ming-calls

Anyone found a solution to the infamous "I'm sorry but I cannot connect your call" with WP on ATA? I have an open ticket with them, but have no big hopes. It would seem that people have kind of resolved the issue using asterisk but I'm not ready to go that path due to the learning curve.

stav · Post by **stav** » Mon Jan 31, 2011 2:11 pm

RobbyG wrote:Even though Whistle doesn't officially support the use of an ATA, the incoming call problem also exists on the Windows client. I have a thread open in the Whistle forum, the latest is that they are blaming the problem on my router.

Can you guys do a test with the Windows client running? Call your Whistle number several times over a 5 minute period and see how many go through and how many get the "I'm sorry but I cannot complete your call". For me it's about 50/50, if you can post to my thread at least they will know it's not just me having the problem. Don't mention the use of the ATA since if you do they will just say "Sorry, we don't support it".

The last post by someone named Yuri said something about the fact that they have 4 servers and that it seems the problem is that incoming calls could come from any of the 4 servers even though my client program is only registered to one. Sounds like that person is on to something.

http://support.whistlephone.com/help/di ... ming-calls

Anyone found a solution to the infamous "I'm sorry but I cannot connect your call" with WP on ATA? I have an open ticket with them, but have no big hopes. It would seem that people have kind of resolved the issue using asterisk but I'm not ready to go that path due to the learning curve.

stav · Post by **stav** » Mon Jan 31, 2011 2:11 pm

RobbyG wrote:Even though Whistle doesn't officially support the use of an ATA, the incoming call problem also exists on the Windows client. I have a thread open in the Whistle forum, the latest is that they are blaming the problem on my router.

Can you guys do a test with the Windows client running? Call your Whistle number several times over a 5 minute period and see how many go through and how many get the "I'm sorry but I cannot complete your call". For me it's about 50/50, if you can post to my thread at least they will know it's not just me having the problem. Don't mention the use of the ATA since if you do they will just say "Sorry, we don't support it".

The last post by someone named Yuri said something about the fact that they have 4 servers and that it seems the problem is that incoming calls could come from any of the 4 servers even though my client program is only registered to one. Sounds like that person is on to something.

http://support.whistlephone.com/help/di ... ming-calls

Anyone found a solution to the infamous "I'm sorry but I cannot connect your call" with WP on ATA? I have an open ticket with them, but have no big hopes. It would seem that people have kind of resolved the issue using asterisk but I'm not ready to go that path due to the learning curve.

stav · Post by **stav** » Mon Jan 31, 2011 2:12 pm

Anyone found a solution to the infamous "I'm sorry but I cannot connect your call" with WP on ATA? I have an open ticket with them, but have no big hopes. It would seem that people have kind of resolved the issue using asterisk but I'm not ready to go that path due to the learning curve.

N7AS · Post by **N7AS** » Mon Jan 31, 2011 2:56 pm

Just program your ATA with another provider such as sipgate and add that number as a FollowMe to Whistlephone.

nostrodamus · Post by **nostrodamus** » Sat Feb 19, 2011 4:39 pm

Whistle is fine for outgoing calls, but there's no way to get incoming calls. Better go with Sipgate for that. And if you were going to pay money to avoid the ads, might as well skip Whistle altogether. Sipgate even has E911 available for like $1 a month, which I don't believe Whistle offers at all, so Sipgate can be a fully functional psuedo-landline for fairly cheap. More than MagicJack, but certainly less than Vonage and infinitely less than the scam that cable companies like Comca$t are selling.

Of course the MagicJack Plus or NetTalk Duo would still work out to be better deals (once the MJ Plus is available, of course) but if having full control over your own equipment is an important factor, I'd recommend the ATA/Sipgate combo.

jshg46 · Post by **jshg46** » Sat Feb 19, 2011 6:51 pm

I cant even get the soft phone to work for me from whistle lol. I get a dail tone but thats it.

stav · Post by **stav** » Mon Mar 07, 2011 6:19 pm

anyone was successfull with the asterisk solution with whistlephone? Seems it works just great but I havnt figure yet out how to configure the darn thing. Tried the incredible PBX (freePBX) and the FusionPBX (freeswitch). Both register with all 4 servers but incoming calls give the infamous "...I'm sorry but I cannot complete your call."