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 flowi
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. Absolutely the same behavi
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 but
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 checking.
> I'll may
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 understand your last
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 sys
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?
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 pr
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 i
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 net
10 matches
Mail list logo