Re: No audio Over VPN

Sergio Charrua via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <CALZWR5zaQp9jJydR3tLXAFc6G-2SAoSn_uqL_VStGOYix9AEUQ@mail.gmail.com>
Have you tried other softphones? Had a similar issue with MicroSIP over NAT
(not using docker) and when using Zoiper all worked fine.
I have always used MicroSIP, but sometimes, it can be tricky....

Atenciosamente / Kind Regards / Cordialement / Un saludo,


*Sérgio Charrua*



On Mon, Jul 28, 2025 at 6:22 PM Fernando Lopes via sr-users <
[email protected]> wrote:

> Hello everyone,
>
> I'm having some issues with SIP when the VPN is active.
> I'm running a Docker container inside WSL. My WSL IP is 172.31.217.74, and
> my machine's IP is 192.168.1.77. When I connect to the VPN, I get the IP
> 192.168.1.129.
>
> When I place a call, I see this log. I've tried disabling ICE, setting the
> public IP of the SIP server in MicroSIP, and manually specifying my local
> machine IP. This does change the c= and a= parameters in the SDP, but it
> still doesn't work.
>
> Everything works fine without the VPN. I need the VPN active to access
> certain endpoints, but SIP stops working once it's connected.
>
> INVITE sip:100@localhost;transport=tcp SIP/2.0
> Via: SIP/2.0/TCP 172.31.208.1:54367
> ;rport;branch=z9hG4bKPjb591721e91454d2bae56a9edfc645ebe;alias
> Max-Forwards: 70
> From: "6001" <sip:6001@localhost>;tag=daa078657d2949e68935f308beeb8b89
> To: <sip:100@localhost>
> Contact: "6001" <sip:[email protected]:54367;transport=TCP;ob>;+sip.ice
> Call-ID: 49c169a9e92d4b23ad70709636ccab4f
> CSeq: 13400 INVITE
> Route: <sip:172.31.217.74;transport=tcp;lr>
> Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY,
> REFER, MESSAGE, OPTIONS
> Supported: replaces, 100rel, timer, norefersub
> Session-Expires: 1800
> Min-SE: 90
> User-Agent: MicroSIP/3.21.6
> Content-Type: application/sdp
> Content-Length:  1345
>
> v=0
> o=- 3962710251 3962710251 IN IP4 192.168.1.129
> s=pjmedia
> b=AS:84
> t=0 0
> a=X-nat:0
> m=audio 4030 RTP/AVP 8 0 96 97 98 9 99 100 101 102 103
> c=IN IP4 192.168.1.129
> b=TIAS:64000
> a=rtcp:4001 IN IP4 192.168.1.129
> ...
> a=ice-ufrag:1d266809
> a=ice-pwd:2f7e2ef6047a47d832ed0f55
> a=candidate:Hc0a80181 1 UDP 2130706431 192.168.1.129 4030 typ host
> a=candidate:Hc0a8014d 1 UDP 2130706175 192.168.1.77 4030 typ host
> a=candidate:Hc0a83801 1 UDP 2130705919 192.168.56.1 4030 typ host
> a=candidate:Hac1fd001 1 UDP 2130705663 172.31.208.1 4030 typ host
> a=candidate:Hc0a80181 2 UDP 2130706430 192.168.1.129 4001 typ host
> a=candidate:Hc0a8014d 2 UDP 2130706174 192.168.1.77 4001 typ host
> a=candidate:Hc0a83801 2 UDP 2130705918 192.168.56.1 4001 typ host
> a=candidate:Hac1fd001 2 UDP 2130705662 172.31.208.1 4001 typ host
>
> Does anyone know where the problem may be?
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions --
> [email protected]
> To unsubscribe send an email to [email protected]
> Important: keep the mailing list in the recipients, do not reply only to
> the sender!
>

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.