[MordyT]

Originally Posted by Grandmast

I'm not sure how many people have read my posts regarding this seemingly excellent option, which for the most part is true, so big thanks to Mordy for reminding me about the wonderfully configurable Magicall. But having said that, I also wanted to add a few things that I've found to be true about the quirks I've been coming across. Actually, due to an in-line epiphany, I have deleted the bullet list I had and what follows is just a short scenario list after seeing some successful Incoming/Outgoing calls in ensemble.

Interestingly enough, I do seem to occasionally receive 'Incoming Calls' flagged with my google voice number, which in turn attach to my Mobile2Home bank instead of Anytime. This could be caused by one of two variables that seem to have changed. Recently, I ticked the "Display caller's number" radio button instead of "Display my Google Voice #" because I figured it wasn't doing any good for free Incoming GV. The other is the fact that a bunch of those incoming google voice calls might have been flagged as unavailable, because I was roaming.

So we have a couple scenarios if anyone has bothered to read this far. I'll try to test them tonight or perhaps tomorrow when I have caught up on some sleep. Any input on this issue is much appreciated.

Correct Caller ID on Sprint Network
Spoofed GV CID on Sprint Network
Correct Caller ID Digital Roam
Spoofed GV CID Digital Roam

If I had to guess, "Display caller's number" in addition to "Carrier Only" would be the ideal situation for pick3 incoming.

I'm not quite sure what you are saying. Are u saying that you are getting charged for your GV minutes by sprint? If so, please remeber that changing your pick 3 requires a new bill cycle to go in effect (i think). If not can you please clarify. Thanks for your input.

Originally Posted by Biker1

I have noticed that on Outgoing calls using GV and Magicall, sometimes the "String" is not completed and the outgoing number is not called. Instead, my GV # is called only and a partial string is completed which results in an endless recorded Loop.
I then disconnect the call, then dial the call again and it goes thru.
In the String, I did delete some commas (,) in error and reinsert them.
Would the following # of (,) 's be correct >>
I have the "String" in the new rule as:
Google Voice #,,,pin code,2,{phone}#
I have also used 2 (,) 's after my GV# and the outgoing issue still occurs intermittently.
It may just be a matter of timing of how the String dials outbound calls and is connecting to the Sprint network, which is why the issue occurs sporadically.

The (,)'s indicate pause. If you feel the program is moving faster then GV - go ahead add more comma's. The combination set in the rules is what i have found to be the best for me. Results may vary. Even somtimes with me (1 out of 50) i find that the program moves faster then google. However i have alos found this to much better battery/resouces/usabilty wise then any other program.