Skip to content
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

Public address or no incoming voice (media delivery issues) #20

Closed
Rysakov1986 opened this issue Nov 17, 2020 · 4 comments · Fixed by #21
Closed

Public address or no incoming voice (media delivery issues) #20

Rysakov1986 opened this issue Nov 17, 2020 · 4 comments · Fixed by #21
Labels
bug Something isn't working

Comments

@Rysakov1986
Copy link

Rysakov1986 commented Nov 17, 2020

Hello!
I was on vacation and now I have checked my incoming calls, everything works great!

But I have a problem with an incoming voice. (media delivery issues)

I use corp VPN, in microsip "Public address" I select ip corp VPN (172.20.239.15), then there is an incoming voice, if auto, then there is no voice.

In tinyphone, how can I select "Public address"?

I attach tinyphone logs.
17-11-2020-tinyphone.log

@Rysakov1986 Rysakov1986 changed the title Public address or no incoming voice Public address or no incoming voice (media delivery issues) Nov 17, 2020
@kingster
Copy link
Member

kingster commented Nov 18, 2020

Manually configuration of external IP address doesn't look a longterm solution as the vpn IP address would change everytime one reconnects. It seems that you are having misconfigured NAT issue. There are better ways to solve this using STUN/TURN, which the sip protocol supports.

Can you try turning on "stun" in your microsip configuration ( type in your corp stun endpoint similar to stun.l.google.com:19302 in the box) and in "Public address" leave it as auto, and try a call? If this works for you I can enable stun options on tinyphone.

@Rysakov1986
Copy link
Author

Rysakov1986 commented Nov 18, 2020

our company uses Jitsi (or Zoiper before) and it probably automatically uses the
SIP UDP Transport Started, **Published Address** 192.168.1.67:5060 // log tiny-softphone
which is used by VIA.
Via: SIP / 2.0 / UDP **172.20.239.15**:5060;rport;branch=z9hG4bKPja5b2c3303fec4d558bb21aae378aa8d0. // log tiny-softphone

Therefore, we don`t use STUN

@kingster
Copy link
Member

Okay,

I have made changes to use the IP discovered in the registration step to be used in SDP in #21

Can you please try with the latest build of this PR.

@Rysakov1986
Copy link
Author

Super! I checked it, it works great!

@kingster kingster linked a pull request Nov 18, 2020 that will close this issue
@kingster kingster added the bug Something isn't working label Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants