Re: [asterisk-users] WebRTC - Transport Issues. - Solved

Josh Thank you for the confirmation on this. The captures do confirm that I am using the wss. What was throwing me was I have only udp and wss in the transports and then the Primary once connected was showing the ws. At first I thought I was doing something wrong and the traffic was

Re: [asterisk-users] tcpbind and source IP address

Ok, thank you for the assistance! пн, 13 мар. 2017 г. в 16:38, Joshua Colp : > On Mon, Mar 13, 2017, at 10:32 AM, Kseniya Blashchuk wrote: > > Tested with latest Asterisk 14.3.0 on Ubuntu 16 kernel 4.4.0-66-generic > > and > > Centos 7 kernel 3.10.0-514.10.2.el7.x86_64.

Re: [asterisk-users] tcpbind and source IP address

On Mon, Mar 13, 2017, at 10:32 AM, Kseniya Blashchuk wrote: > Tested with latest Asterisk 14.3.0 on Ubuntu 16 kernel 4.4.0-66-generic > and > Centos 7 kernel 3.10.0-514.10.2.el7.x86_64. Absolutely the same behavior. > Joshua, maybe you can advice what can be done further? You can file an issue

Re: [asterisk-users] tcpbind and source IP address

Tested with latest Asterisk 14.3.0 on Ubuntu 16 kernel 4.4.0-66-generic and Centos 7 kernel 3.10.0-514.10.2.el7.x86_64. Absolutely the same behavior. Joshua, maybe you can advice what can be done further? пн, 13 мар. 2017 г. в 14:52, Kseniya Blashchuk : > Ah ok, thank you for

Re: [asterisk-users] tcpbind and source IP address

Ah ok, thank you for checking. I'll maybe also try with the latest asterisk and/or other distro and see if this behavior is reproduced. пн, 13 мар. 2017 г. в 14:46, Joshua Colp : > On Mon, Mar 13, 2017, at 08:43 AM, Kseniya Blashchuk wrote: > > Mmh sorry I'm afraid I did not

Re: [asterisk-users] tcpbind and source IP address

On Mon, Mar 13, 2017, at 08:43 AM, Kseniya Blashchuk wrote: > Mmh sorry I'm afraid I did not understand your last message. Yes the code > does that but only with UDP, for TCP the source address is 192.168.0.172 > though it's bound to 192.168.0.177: > IP 192.168.0.172.47596 > .5061 > If it was a

Re: [asterisk-users] tcpbind and source IP address

Mmh sorry I'm afraid I did not understand your last message. Yes the code does that but only with UDP, for TCP the source address is 192.168.0.172 though it's bound to 192.168.0.177: IP 192.168.0.172.47596 > .5061 If it was a system/kernel issue, then why is the behavior different for TCP and UDP?

Re: [asterisk-users] tcpbind and source IP address

On Mon, Mar 13, 2017, at 08:31 AM, Kseniya Blashchuk wrote: > Yes, look: > netstat -nlp | egrep '506[01]' > tcp0 0 192.168.0.177:5061 0.0.0.0:* > LISTEN > 13255/asterisk > udp0 0 192.168.0.177:5060 0.0.0.0:* > 13255/asterisk > Still, the

Re: [asterisk-users] tcpbind and source IP address

Yes, look: netstat -nlp | egrep '506[01]' tcp0 0 192.168.0.177:5061 0.0.0.0:* LISTEN 13255/asterisk udp0 0 192.168.0.177:5060 0.0.0.0:* 13255/asterisk Still, the problem is with *outgoing* *TCP* packets originated from asterisk. Source IP

Re: [asterisk-users] tcpbind and source IP address

On Mon, Mar 13, 2017, at 03:52 AM, Kseniya Blashchuk wrote: > Hi! > Attached sip.conf and interface config as well. In this case we use only > TLS, but I have checked with TCP - same situation, 192.168.0.172 is used > as > a source. For UDP 192.168.0.177 is used as expected. Does the output of

Re: [asterisk-users] double NAT - one way audio

Hi Glenn, unfortunately there is no bridge mode or any comparable mode available. I am using the same router (but another type) on my private homenetwork with another router at the back (=> same architecture as in this failing scenario), but everything works fine. There are only two differences:

Re: [asterisk-users] tcpbind and source IP address

Hi! Attached sip.conf and interface config as well. In this case we use only TLS, but I have checked with TCP - same situation, 192.168.0.172 is used as a source. For UDP 192.168.0.177 is used as expected. пн, 13 мар. 2017 г. в 2:37, Joshua Colp : > On Sat, Mar 11, 2017, at