Voice Call is not working
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, docker
- Domain
- audio-video-rtc, backend, mobile-dev, networking
Research direction
No files, tests, or entry points are named. Start by reproducing the call failure across the mentioned Android devices, emulators, and network locations, while comparing the Docker server and reTurn container setup. Done means identifying the cause of the stuck connecting state and the reported 10–30 second delay, with a concrete fix or configuration change.
Written by the indexing model from the issue text.
Description
Good day!
Thank you for your contribution.
I deployed my own server and built the android app to connect my own server.
The server has been built in docker mode and I deployed retund on my another server as a docker container.
However, the voice call is not working well.
I am testing with several mobiles in different locations and emulator but in some cases, they are not working.
On receiver side, it rings and then accept but it keeps showing "connecting ...".
Some guys, it depends on the receiver or caller's NAT type.
Would you kindly guide me how I can debug this issue?
Also, the connection speed is very slow. It is taking 10 ~ 30 seconds in case they work. How can I improve this speed? Maybe are there any delay param on wire server or mobile app?
Kindly guide me please.
Thank you.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 332
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wireapp/wire-server
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
wireapp/wire-server#5632 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
wireapp/wire-server#5443 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wireapp/wire-server#5315 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4754 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4613 ·
Maintainers usually reply within 2 days
All issues in wireapp/wire-server
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
alunduil/siren-json.hs#264 ·
Maintainers usually reply within 1 day
-
console: no way to refresh row data in Browse Rows without a full page reloadPossibly taken @12fahed claimed this today. Openk/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hasura/graphql-engine#10895 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day