Hello,
I start using realtime queue and while all queue types perform great, I
find not usable the linear strategy. In the linear strategy, order of the
agents matters. The problem is due to the fact it is not possible (in a
clean way) to list the agents in the desired order. There is no field in
I think to have found an issue, but before reporting on issue.asterisk.org,
I'd like to get an advice here...
I am using realtime ODBC voicemail and all works great except I cannot set
the fromuser settings. It is ignored and the default one is used.
The problem seems laying in the definition of
I am back to try to fight with the problem highlighted few years ago
https://issues.asterisk.org/jira/browse/ASTERISK-18480
In short, when using realtime queue members, it is impossible to use
ordered ringing method because it is impossible to define the ordering of
agents and the alphabetical
Hello,
I just noticed some FAILED disposition entries in the cdr (using
cdr_adaptive_odbc). They are connected to the NO ANSWER entries. For each
NO ANSWER, there is a FAILED entry, so a call generated two entries. In
other words, every time a call got a NO ANSWER, two entries are generated
in the
Hello,
I have at least two asterisk boxes suffering from continuous lock and I'd
like to know if you are experiencing the same issues. I have a total of
around 200 asterisk servers around with versions ranging from 11.x to
latest 13.6, but this problems happens just on a couple.
In detail,
Hello,
is there anybody being affected by asteirsk bug 25468 who has maybe an idea
about a work around this unpleasant situation? Asterisk locks and stops
processing UDP packets, letting the UDP buffer to fills up.
Being forced to stick with asterisk 13.2.0 (one not affected, but not sure
this is
-07-21 17:18 GMT+02:00 Jonathan Rose <
jonathan.r...@motorolasolutions.com>:
>
>
> On Thu, Jul 21, 2016 at 10:16 AM, Jonathan Rose <
> jonathan.r...@motorolasolutions.com> wrote:
>
>>
>> On Thu, Jul 21, 2016 at 2:30 AM, Leandro Dardini <ldard...@gmail.com
Hello,
I am looking for an advice for having a bug fixed. I am talking about
ASTERISK-25468
https://issues.asterisk.org/jira/browse/ASTERISK-25468
I tried posting a bounty for this issue, but got no feedback.
Is chan_sip definitively abandoned and no fixes will be done?
Is the bounty too low?
I am interested in having the ticket below fixed.
https://issues.asterisk.org/jira/browse/ASTERISK-25468
The patch needs to be accepted by Asterisk development team and integrated
in mainstream asterisk.
Contact me directly for payment arrangement.
Leandro
--
I am interested in having the ticket below fixed.
https://issues.asterisk.org/jira/browse/ASTERISK-25468
The patch needs to be accepted by Asterisk development team and integrated
in mainstream asterisk.
Contact me directly for payment arrangement.
Leandro
--
Tichy" <asteri...@pi4tel.de> ha scritto:
> On Thu, Jul 21, 2016 at 11:06:50PM +0200, Leandro Dardini wrote:
> > About replicating the problem at will, it is not easy ... I have some
> > servers where the locking is quite immediate, others running for days
> > witho
Your analysis of the chan_sip/PJSIP is really great and I agree with you.
Being a grey haired tech, I can check what drives similar changes in the
latest 20 years. We moved from Netware networks to TCP/IP, we moved from
Windows 3.11 to Windows 95, we moved from IE to Chrome... in all these past
Hello,
I just found a problem while using queue realtime and assigning a value to
the "context" field.
The context field allows to specify a context to send the caller when a
DTMF key is pressed.
If I have a queue running with configuration stored in realtime database
and I set the "context"
While you work on the AMI events for PJSIP endpoints, don't forget the
issue with no AMI events issued when a PJSIP endpoint loses completely the
connectivity. If it de-registers, an event is fired, if you just pull the
plug, no events are generated.
Leandro
Il giorno mer 15 ago 2018 alle ore
Please check if you have any chan_sip extension with subscribemwi=yes and
turn it to "no" and restart asterisk.
Leandro
Il giorno ven 27 mar 2020 alle ore 11:45 Дмитрий Шлег EFSOL <
d.sh...@efsol.ru> ha scritto:
> Dear Friends, i have periodic frack on asterisk 13.30.0 on CentOS 7, need
> some
15 matches
Mail list logo
