On Tue, Feb 14, 2017 at 2:51 PM, George Joseph wrote:
>
>
> On Tue, Feb 14, 2017 at 10:21 AM, Olivier wrote:
>
>> Hello,
>>
>> I've got a 13.13.1 system using PJSIP stack on debian Jessie.
>> It runs from 50 to 100 simultaneous calls (so 100 to 200 PJSIP channels)
>> all day long.
>> From time
On Tue, Feb 14, 2017 at 10:21 AM, Olivier wrote:
> Hello,
>
> I've got a 13.13.1 system using PJSIP stack on debian Jessie.
> It runs from 50 to 100 simultaneous calls (so 100 to 200 PJSIP channels)
> all day long.
> From time to time, roughly meaning once a month, it segfaults with lines
> (fr
What an excellent response Richard!!! Thank you very much for that!!
Best regards!
Patrick
On Wed, Feb 15, 2017 at 5:23 AM, Richard Mudgett
wrote:
>
>
> On Tue, Feb 14, 2017 at 6:24 AM, Patrick Wakano wrote:
>
>> Hello Asterisk Users,
>>
>> Hope you all doing fine!
>> I am working with a quite
Hello Asterisk Users.
I have an issue with receiving fax on my Asterisk/SIP channel. I keep
getting timeout under T.38 negotiation - see http://pastebin.com/6eCe26YM
Any help would be greatly appreciated.
/Jacob
--
_
-- Bandw
On Tue, Feb 14, 2017 at 6:24 AM, Patrick Wakano wrote:
> Hello Asterisk Users,
>
> Hope you all doing fine!
> I am working with a quite complex dialplan, and I've come to some
> situations where it makes some nasty use of pre-bridge handlers.
> The pre-bridge handlers wiki (https://wiki.asterisk.
Hello,
I've got a 13.13.1 system using PJSIP stack on debian Jessie.
It runs from 50 to 100 simultaneous calls (so 100 to 200 PJSIP channels)
all day long.
>From time to time, roughly meaning once a month, it segfaults with lines
(from dmesg -T output) like this:
asterisk[1160]: segfault at 7eff
is back online now thanks!
On Feb 14, 2017, 11:18 -0300, Joshua Colp , wrote:
> On Tue, Feb 14, 2017, at 10:13 AM, Sebastian Gutierrez wrote:
> > The 13.14 tar gz doesn’t even exists on the current or in the old
> > releases folder.
> >
> > there seems to be an issue with the latest build not gene
On Tue, Feb 14, 2017, at 10:13 AM, Sebastian Gutierrez wrote:
> The 13.14 tar gz doesn’t even exists on the current or in the old
> releases folder.
>
> there seems to be an issue with the latest build not generating the
> artifacts?
It was temporarily removed during a synchronization but is now
The 13.14 tar gz doesn’t even exists on the current or in the old releases
folder.
there seems to be an issue with the latest build not generating the artifacts?
best regards
On Feb 14, 2017, 11:04 -0300, Marcelo Terres , wrote:
> Thanks Joshua.
> Marcelo H. Terres IM: mhter...@jabber.mundoo
Thanks Joshua.
Marcelo H. Terres
IM: mhter...@jabber.mundoopensource.com.br
https://www.mundoopensource.com.br
https://twitter.com/mhterres
https://linkedin.com/in/marceloterres
On 14 February 2017 at 14:01, Joshua Colp wrote:
> On Tue, Feb 14, 2017, at 09:57 AM, Marcelo Terres wrote:
>> Same p
On Tue, Feb 14, 2017, at 09:57 AM, Marcelo Terres wrote:
> Same problem with me.
>
> I downloaded the file in 2 different places and had the same error...
An issue was filed for tracking this[1] and it will be resolved later
today.
[1] https://issues.asterisk.org/jira/browse/ASTERISK-26791
--
Same problem with me.
I downloaded the file in 2 different places and had the same error...
Marcelo H. Terres
IM: mhter...@jabber.mundoopensource.com.br
https://www.mundoopensource.com.br
https://twitter.com/mhterres
https://linkedin.com/in/marceloterres
On 14 February 2017 at 08:42, Jonathan
Hello Asterisk Users,
Hope you all doing fine!
I am working with a quite complex dialplan, and I've come to some
situations where it makes some nasty use of pre-bridge handlers.
The pre-bridge handlers wiki (https://wiki.asterisk.org/
wiki/display/AST/Pre-Bridge+Handlers) doesn't have the big warn
Hi there;
2 linux boxes and Windows all report an error and the archive is not
extractable.
Wget reports the size as follows:
2017-02-14 08:36:21 (7.29 MB/s) - ‘asterisk-14-current.tar.gz’ saved
[40653605/40653605]
It starts un-tarring but then
asterisk-14.3.0/bridges/bridge_native_rtp.c
a
14 matches
Mail list logo