maemo.org Bugzilla – Bug 5962
unable to complete calls out
Last modified: 2010-02-14 06:29:15 UTC
You need to
before you can comment on or make changes to this bug.
configured ok, but unable to complete calls out. App status says "Calling
##########" for a second or 2, vanishes, and other phone never rings
Someone else on the forum seemed to have the same issue at first, but the
callbacks are making it to Gizmo which suggests it isn't Dialcentral. Still
waiting on information to help debug this.
$ cp ~/.dialcentral/dialcentral.log ~/MyDocs/
Thanks Ed, maybe I can troubleshoot from there. Youc an close this as
WORKSFORME if you like.
And I'm not being stubborn about the log file-- just reluctant to reveal the
extent of my Linux ignorance....lol. I still don't know how to access the file
even with what you just posted... :o
I'll probably keep it open for now, just to see what pops up. Ignorance of
Linux is a good thing, it exposes these rough edges developers cut their users
with. The sad part is I'd go and make it nicer to get the log but I don't want
to lose what votes I have for getting into Extras.
1.0.8 has been promoted to Extras Testing. Bug 6133, so pressing Ctrl+l should
put the log in the copy buffer to paste where needed. Hopefully that'll help
in resolving this issue.
So many people are reporting calling issues now, I would consider this
confirmed. Sadly, I don't have this issue, again.
Some get it with Gizmo callback numbers, some get it for all callback numbers.
Several users reported they also had issues on google.com/voice/m.
Thanks to pygooglevoice I found a better way to dial, I hope that fixes this
With 1.0.9-1 release, now a different set of users is reporting issues. A
google error code of 20.
This should resolve the error code 20 which was limited almost exclusively to
My hope is it was a lack of "+" in numbers which is now fixed in GIT, should be
released in 1.1.0.
I suspect this because I added support for "+" in TOR and have had no
complaints from users on Gizmo.