I believe that EVAL might be able to help you here:
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Function_EVAL
Example:
Allphones=${EVAL(Kphones)}&${EVAL(Sphones)}
I'm not sure if in the globals it will let you, but in the dialplan for
sure it will.
On Tue, Jan 24, 2023 at 3:5
Have you tried adding “-n”?
Also, what version of asterisk are you using? newer versions only have
colorized output when your are connected to the console (-r) not for remote
commands (-rx)
On Wed, Aug 3, 2022 at 08:21 Carlos Chavez wrote:
> I usually like to have the colorized output wh
I would check if you don't have any channels in a hung/zombie state...
Have a look if "core show calls" matches "core show channels".
Either way, it seems wonky, so you might end up having to give that
asterisk a restart... :S
On Wed, Jul 27, 2022 at 6:21 PM David Cunningham
wrote:
> Hello,
>
Hi,
I wanted to add some comments to Sebastian's response:
1- When you have a lot of DIDs, you can't just "port" them over from
company1 to company2. Try to have 1M or so DIDs and ask if you can just
port them. No no, not that simple. There is a process that a lot of times
is not worth the cost/r
Well I skipped reading the part where you say “only for log files” :-(
On Thu, Jul 23, 2020 at 21:06 Joel Serrano wrote:
> Have you tried starting asterisk with the "-n" param?
>
>-n Disable console colorization
>
> On Thu, Jul 23, 2020 at 5:11 PM And
Have you tried starting asterisk with the "-n" param?
-n Disable console colorization
On Thu, Jul 23, 2020 at 5:11 PM Andrew Yager wrote:
> Hi,
>
> Is there a way to drop the ANSI colour strings from log files? In
> particular, I've got JSON logging throwing logs over to ES, but
angup()
>
> I added hints to see if that would make a difference and it hasn't.
>
> I also made a 'Anonymous' peer to see if that would help without any luck.
>
> On Thu, Jul 16, 2020 at 6:11 PM Joel Serrano wrote:
>
>> Hey John,
>>
>> In
Hey John,
In one installation I have, we use several monitoring tools (nagios based
and custom scripts based) and we have the following:
; Reply OK to SIP:OPTIONS
[public]
exten => s,1,Wait(1)
same => n,Hangup
: For Nagios
exten => nagios,1,Wait(1)
same => n,Hangup
NOTES:
1- We have context=pub
uniqueid plus the sequence, I can grab the fields from the
row that has them.
On Tue, Feb 25, 2020 at 4:01 PM Joel Serrano wrote:
> Hello,
>
> I have a setup with asterisk 16.8.0, I'm facing a problem where calls that
> fail (CONGESTION) don't have filled in some extr
Hello,
I have a setup with asterisk 16.8.0, I'm facing a problem where calls that
fail (CONGESTION) don't have filled in some extra fields we add to the CDRs
in the database.
We use cdr_adaptive_odbc with MySQL as backend.
To simplify the scenario:
[sub-hanguphandler]
exten => s,1,Set(CDR(foo)=
devices
registering via an intermediate proxy :)
Just wanted to update this in case it helps anyone else.
Cheers,
Joel.
My problem was caused by the *nat=* setting for the device.
I found
On Wed, Mar 20, 2019 at 11:37 AM Joel Serrano wrote:
> Hello,
>
> We have a couple asterisk1
Hello,
We have a couple asterisk11 servers behind a Kamailio4 proxy. We are in the
process of upgrading to asterisk16 and Kamailio5 and I'm testing out Path:
support with chan_sip (migration to PJSIP is not possible right now due to
integrations with other systems).
Functionality-wise things are
12 matches
Mail list logo
