New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With 2 SIP-Accounts caller don't here anything #461
Comments
Hi |
Hey @julonexus, |
You can send it with the application but don't forget to point to this issue. Empty mails without explanations are unread. |
Hey @julonexus,
with Topic:
=> For sure. Nevertheless :p), I can
and
|
Hi,
I like Linphone a lot.
Unfortunately there seams to be a problem in the Desktop App.
The system
I use
2 SIP-Accounts
First: SIP-Account with a Fritz!Box
works fine with TCP.
Second: With a SIP-Account direct from VOIP-Provider.
Both SIP-Account works fine.
The Problem
But if someone call me to the Fritz!Box SIP-Account linked phone-Number, I have to ensure to use select the «right» Fritz!Box SIP-Account. Than the caller will hear also my voice.
If I don't choose first the right SIP-Account (above left side in the Linphone-App) I can hear the caller, but he can't here my voice. The Micro-Level Meter from Linphone beats out. But the caller can't here me.
Also if I change the SIP-Account in the Linphone-App After accepting the call, the caller can't here me.
But the same caller, if he calls again - and I choose before call-acceptance the «right» SIP-Account - can here my voice loud and clear.
It seams like the App conducts porperly the callers signal regardless which SIP-Account I have choosen, but miss-conducts the signal from the called side (my side).
It would be much easier if a call can be accepted without having to think about «which» SIP account the caller is calling «trough». In the current situation, the changes of errors are quite big and take calls is somewhat stressful.
Would be great to get some help for the right settings or some hint what could cause this miss-connection.
Best regards
Martin
The text was updated successfully, but these errors were encountered: