JFYI - https://issues.asterisk.org/jira/browse/ASTERISK-26922
чт, 20 апр. 2017 г. в 11:38, Kseniya Blashchuk :
> Hi!
> The issue did not reproduce with pjsip. As for ppa - somebody recommended
> me ppa:sapian/asterisk. Does anybody use it maybe?
>
>
> вт, 18 апр. 2017 г. в
Hi!
The issue did not reproduce with pjsip. As for ppa - somebody recommended
me ppa:sapian/asterisk. Does anybody use it maybe?
вт, 18 апр. 2017 г. в 2:24, Ludovic Gasc :
> Hi,
>
> I recommend you to install from sources, especially because the latest
> Asterisk 13 has
Hi,
I recommend you to install from sources, especially because the latest
Asterisk 13 has several bugfixes for pjsip.
To my knowledge, nobody proposes ppa or Debian backports for Asterisk.
Wazo has Debian packages, but it's only for Debian Jessie and with extra
patches for Wazo.
--
Ludovic
Hi!
Unfortunately pjsip is broken in Ubuntu Asterisk installed from repo. Yes I
also thought to try with pjsip, just to know if it's also affected. I'll
try to make a test next days.
On Sun, Apr 16, 2017, 8:18 PM Ludovic Gasc wrote:
> Hi Kseniya,
>
> You might test with
Hi Kseniya,
You might test with chan_pjsip: We have less production experience with
chan_pjsip than chan_sip, however, for now, we are more and more confident
in this new stack while we're digging in documentation and we're testing on
production.
However, I've no idea if you'll have the same
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.
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
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
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
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
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
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
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
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
On Sat, Mar 11, 2017, at 11:50 AM, Kseniya Blashchuk wrote:
> Hey guys, any thoughts on that? Probably a bug or is it a default
> behavior?
I'd suggest providing the configuration to make sure it is correct.
--
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW -
Hey guys, any thoughts on that? Probably a bug or is it a default behavior?
On Thu, Mar 9, 2017, 2:05 PM Kseniya Blashchuk wrote:
> Hi all!
> I am running asterisk 13.1.0 on Ubuntu server 16.04. There are two IP
> addresses from the same subnet set on one interface, and
Hi all!
I am running asterisk 13.1.0 on Ubuntu server 16.04. There are two IP
addresses from the same subnet set on one interface, and bindaddr is set to
the second on them in sip.conf and in iax.conf.
Incoming connections work as expected. However, for outgoing connections it
seems that asterisk
18 matches
Mail list logo