I want to confirm that it works fine.
Many, many thanks to every person involved
On 2021-10-26 15:20, Sean Bright wrote:
On 10/25/2021 1:19 PM, cio-al...@playerschool.edu wrote:
Yes, it's Asterisk 11 on Centos 8, not Centos 7.
Centos 7 cannot be used anymore because of some systemd
On 10/25/2021 1:19 PM, cio-al...@playerschool.edu wrote:
> Yes, it's Asterisk 11 on Centos 8, not Centos 7.
> Centos 7 cannot be used anymore because of some systemd incompatibility
> Can somebody be so nice as to provide a patch for the latest version of
> Asterisk 11?
Just add --without-libedit
Question:
Is there a developer or sangoma, who may write this patch for a fee?
My boss is putting pressure on me.
On 2021-10-25 11:19, cio-al...@playerschool.edu wrote:
Yes, it's Asterisk 11 on Centos 8, not Centos 7.
Centos 7 cannot be used anymore because of some systemd incompatibility
Can
Yes, it's Asterisk 11 on Centos 8, not Centos 7.
Centos 7 cannot be used anymore because of some systemd incompatibility
Can somebody be so nice as to provide a patch for the latest version of
Asterisk 11?
Asterisk 11 is not my choice, but it's the only version that works with
another software
On 10/24/2021 12:41 PM, cio-al...@playerschool.edu wrote:
> Really destroying SIP dialog
> '5af3bcf012ac9d574b17f2634e48de54@65.21.137.162:5060' Method: OPTIONS
> \U+26504\U+2650A\U+26565\U+26578\U+26569\U+26574\U+2650A\U+2650A
If this is still Asterisk 11 as you've mentioned in other threads,
On a new installation of Asteris, I connect to the command line and
after a few minutes I get the code below, and then I need to CTRL-C to
get out and come back in.
--- (10 headers 0 lines) ---
Really destroying SIP dialog
'7f9fc09410586a9e62c5fed905c398ba@208.78.161.2' Method: INVITE
Really
