Hello Asterisk users,
This issue started after we updated all of our systems to Asterisk 13.7.2.
Details:
CentOS 5.11
DAHDI Version: 2.9.1.1
Asterisk updated from 13.1.0 to 13.7.2
Asterisk takes around 5 rings to answer the call (before it took 2)
Only seems to happen to our Asterisk systems
Asterisk Project Security Advisory - AST-2016-005
ProductAsterisk
SummaryTCP denial of service in PJProject
Nature of Advisory Crash/Denial of Service
Asterisk Project Security Advisory - AST-2016-004
ProductAsterisk
SummaryLong Contact URIs in REGISTER requests can crash
Asterisk
The Asterisk Development Team has announced security releases for Certified
Asterisk 13.1 and Asterisk 13. The available security releases are released
as
versions 13.1-cert5, and 13.8.1.
These releases are available for immediate download at
Darryl,
We had this with a large ISP in the US. They blamed it on a software bug. For
this reason we offer clients the option to use a non standard port. It's most
likely your ISP that is blocking the port for g-d knows what reason.
Regards,
Dovid
-Original Message-
From: Darryl
Hey all. This isn't directly an Asterisk question, but it is Asterisk
related because I am using SIP on asterisk.
The last couple of days I found that our asterisk box was having all
packets originating from port 5060 being blocked.
If I moved my SIP port to any other port I could register
On Wednesday 13 Apr 2016, Jeremy Kister wrote:
> On 4/13/16 11:57 AM, A J Stiles wrote:
> > You could try
> > *CLI> dialplan show
>
> Between my older backup and dialplan show, I guess that's my best shot.
>
> Thanks :D
I'll have a go this lunchtime at knocking up a Perl script {for that is my
Hello.
I developed a little project (a PoC) to "integrate" Asterisk IVRs with
"other softwares", allowing that data already entered in IVR can be used in
other stages of a customer service, for example.
The main goal is to provide more efficiency and interoperability between
different solutions
