![]() |
2009-09-06
, 00:48
|
Posts: 1,213 |
Thanked: 356 times |
Joined on Jan 2008
@ California and Virginia
|
#2
|
![]() |
2009-09-06
, 00:58
|
|
Posts: 109 |
Thanked: 37 times |
Joined on Oct 2008
@ NYC, NY
|
#3
|
![]() |
2009-09-06
, 01:04
|
Posts: 16 |
Thanked: 1 time |
Joined on Feb 2009
|
#4
|
![]() |
2009-09-06
, 04:15
|
Posts: 11 |
Thanked: 20 times |
Joined on Sep 2009
|
#5
|
![]() |
2009-09-06
, 04:22
|
Posts: 16 |
Thanked: 1 time |
Joined on Feb 2009
|
#6
|
![]() |
2009-09-06
, 04:53
|
Posts: 1,213 |
Thanked: 356 times |
Joined on Jan 2008
@ California and Virginia
|
#7
|
![]() |
2009-09-06
, 04:58
|
Posts: 16 |
Thanked: 1 time |
Joined on Feb 2009
|
#8
|
![]() |
2009-09-06
, 05:17
|
Posts: 11 |
Thanked: 20 times |
Joined on Sep 2009
|
#9
|
1) Will there be a way to reliably make voip calling work, using my t-mobile # for both inbound and outbound calling over wifi with the native dialer?
2) Can i use a SIP provider with the stock dialer? If so I could then spoof my # for outbound calls (to the t-mobile #), but that's going to add additional cost that i would rather not incur. Also if I have to pay monthly for a DID, and have my t-mobile # forward to that when I’m at home, if i remember correctly there is going to be an additional charge for each call because it is being forwarded?
3) I'm assuming reliable text messaging is going to be out of the question?
Thanks for any help, I really hope this is going to be achievable at a reasonable monthly expense!