Download ZIP (34.5 MB)

Testing and Issues

You can test this entry and submit issues during the testing period of the VoIP Contest, Round 1 contest.

Entries with serious issues will not be able to win the contest, but even minor issues might be important for overall results.


by rating


Fair Wombat Nov 14, 2019 at 11:09
The submitted tgvoiprate app got a score of 954 and took the 11th place in the scoring table, receiving 3⭐️.
The minor issue #issue9060 prevented us from using tgvoipcall in generating the rating dataset. -0.25⭐️
External dependency: PESQ (commercial license) -0.25⭐️
Final result is 2.5⭐️
Fair Wombat Nov 5, 2019 at 12:21
#issue9021 No, most of other submissions work fine with similar input. And in our environment I can't make it work even 1 out of 5 times
Debian GNU/Linux 10 (buster)
Groovy Cow Nov 5, 2019 at 15:55
Thanks for the report.
I just fixed this issue by adding sleep between Start and Connect.
My patch here:
Resulted tgvoipcall here
I believe that exist a better way, but it this is fast one
Fair Wombat Nov 4, 2019 at 13:21
Can't manage to make tgvoipcall work on Buster. Every time ends with

Error connection timeout

Same for callee. Tcpdump shows traffic both to and from reflector.
Just tried with completely fresh install, still doesn't work.
Debian GNU/Linux 10 (buster)
Groovy Cow Nov 4, 2019 at 21:44
Hi thanks for your testing )
I have the same issue. In my test environment I need 5 retries in average to succeed a call.
Checked other contest entries and all of them had the same behaviour.
Borik Bobrujskov Nov 5, 2019 at 00:24
Trying to do it manualy will ends with the same results. But in autotesting i wil make successfull cal. Do autotesting with simple python3 util.

You can run it with:
python3 ./ -k <api_key> -S <samples_dir> -O <output_dir>


Script dependencies:
# apt install -y python3 python3-pip
# pip3 install argparse requests uuid
Debian buster
Borik Bobrujskov Nov 5, 2019 at 00:49
With enabled debug I see this error:

W/tgvoip: Received packet has wrong key fingerprint
W/tgvoip: wrong decrypted length

Full log of such call you can see there:

Sorry, it is mixed output from caller and callee, but there all info you needed
Debian buster
Nobody added any issues yet...