CSipSimple + Sip2Sip + Obi202 + Google Voice
threehappypenguins:
Ahhh yes. Trev. He has been incredibly helpful while I was setting up my in-laws Obi. He blocked their long distance in the middle-of-the-road plan so I could get GV on and they get long distance for free. Trevor has gone above and beyond with help, and I have emailed him so many times that I cannot count! So I did not want to drive him crazy with another email... LOL!
Obion will not appear to work. I originally had my inlaws Obi110 on the Obitalk dashboard, and it was interfering with the AcroVoice provisioning. We tried working around it, but Trevor eventually had to have me completely disable it and delete it off of the dashboard. Then everything worked fine (well, except for some unrelated issues...). Now that I have my own Obi (Obi202), I have put it on the dashboard and attempted to simply use Google Voice with Obion. I do not understand how Obion works and why it will not work right. It doesnt matter what I dial, but it always calls the Obi, and not the number that I was dialing. So I gave up. And like I said, Obitalk interferes with AcroVoice provisioning, so I have no use for Obion anyway. I tried to play around with it to see if I could have on the dashboard, use Obion with Obitalk, and yet have the Obitalk disassociated with the provisioning via the Obi IP address, and I just could not see how it is possible. If any of that made any sense...
Thanks for trying Ianobi!!! ;D
I guess I will have to play around with this more... somehow. maybe read a nice 1000 page book on ports, forwarding, networking, telecommunications, etc. Anyone want to babysit for a week straight? ;)
threehappypenguins:
I started this thread http://www.obitalk.com/forum/index.php?topic=4726.0 because the outgoing call was only going intermittently (sometimes would go through, sometimes would time out), and I figured it was a port forwarding problem. I think that setting dmz on my router (not the Obi) solved the problem. I still have yet to test the calls on a different network. Right now my Android is on the same WiFi network so we will see when it is connected elsewhere outside my home network.
The last problem I was having was the Android ALWAYS called the Obi. I could dial any number I wanted, it didn't matter. It would just go to the Obi. It was not recognizing my sip2sip username as a trusted number and so it was always being sent to the Obi. ianobi, you are the best! He helped me via messaging on this forum.
OBiAdminGuide:
Quote
literals [in DigitMaps] - Any combination of 0-9,*,#,+,-,A-Z,a-z, except m, M, s, S, x, X which have special meaning in the digit map syntax.
http://www.obihai.com/OBiAdminGuide.htm
RonR:
Quote
The fact that you're reaching the PHONE Port means you're almost there.
The problem is likely that you don't have the username from your IP Phone in the cot User Defined DigitMap. Look at the OBi Call History and make sure you're using the correct username.
Also, if there are any reserved characters (m, M, s, S, x, X) in the username, they have to be surrounded by single quotes. For example, if the username is xlite, it would have to be entered in the cot User Defined DigitMap as : ('x'lite)
http://www.obitalk.com/forum/index.php?topic=2454.0
It turns out that the reason why my sip2sip account was not being recognized as a trusted caller by the Obi is because I had one of the reserved characters in my username. So in User Settings > User Defined DigitMaps > User Defined DigitMaps2 under DigitMap (if aaaaaaas is my sip2sip username) I had:
(aaaaaaas)
I changed it to:
(aaaaaaa's')
And it went through!!!!!!!!!
Navigation
[0] Message Index
[*] Previous page