That's correct. When you update the kernel package youhave also to
recompile dahdi package.
Am 12.05.2014 07:05, schrieb Lee, John (Sydney):
Hi,
I have noticed it for a while but I just thought about confirming this
with the Asterisk community.
As the compilation of DAHDI will need to
I am unable to get re-invite to work on a new system. Also, unwanted
transcoding is occurring on PSTN calls.
The new system (FreePBX 2.11.0.37, Asterisk 11.9.0, CentOS 6.5) will
eventually replace an old system (FreePBX 2.8.1, Asterisk 1.8.7.2,
CentOS 5.8) currently in production. Both
On 12-05-14 09:30, Thorsten Göllner wrote:
That's correct. When you update the kernel package youhave also to
recompile dahdi package.
AFAIK that's not true for RHEL6/CentOS6 as the EL6 kernels are ABI
compatible so you don't need to recompile DAHDI when there's a new EL6
kernel. When
Hello,
We are using Asterisk 1.4 as call distribution system with simple queues
for SIP calls.
With high load (4000 calls/hour) some calls remain in queue forever (until
queue's max wait time) in spite of being hung up already by the caller. It
seems that when a BYE is lost, Asterisk has no
On May 12, 2014, at 5:02 AM, Jan Gaida jan.ga...@grupoamper.com wrote:
We are using Asterisk 1.4 as call distribution system with simple queues for
SIP calls.
With high load (4000 calls/hour) some calls remain in queue forever (until
queue's max wait time) in spite of being hung up
Thank you.
Yes, that should work. But if I understand it correctly, only if there's no
silence detection activated. Otherwise, when silence is detected no RTP
would be send, so that rtptimeout would hang up a still active call.
I there no option to use RTCP? Not even in Asterisk 11?
Regards
On
Hello All, Looking for a little guidance on Real Time Pattern Matching.
We are attempting to block outbound 411 via when someone dials
NXX-555-, The must common being NXX-555-1212. However, We have some
outbound providers that consider any call to NXX-555- a directory
assistance
On Mon, May 12, 2014 at 12:25 PM, Nick Olsen n...@flhsi.com wrote:
Hello All, Looking for a little guidance on Real Time Pattern Matching.
We are attempting to block outbound 411 via when someone dials
NXX-555-, The must common being NXX-555-1212. However, We have some
outbound providers
On Mon, May 12, 2014 at 1:25 PM, Nick Olsen n...@flhsi.com wrote:
Hello All, Looking for a little guidance on Real Time Pattern Matching.
We are attempting to block outbound 411 via when someone dials
NXX-555-, The must common being NXX-555-1212. However, We have some
outbound providers
Thanks for the info everyone.
With our particular dial plan. We break out _321 _305 _407.. Local area
codes, And handle them differently. Where is _NXX555 works for numbers
not specifically broken out. The fix for this was adding more specific
_321555 for those handful of
Hello,
recently I have seen spike in attacks on my asterisk server, this is what I
get on the LCD of my phone: 201@76.220.5.205
or calls from 1000 sip1000@76.2230.5.205,
have any idea on how to stop this calls?
Thanks,
--
_
--
I would simply drop all traffic from the IP at the firewall.
William Hetherington
w - www.willwh.com
t - @wmwh
On Mon, May 12, 2014 at 2:43 PM, motty cruz motty.c...@gmail.com wrote:
Hello,
recently I have seen spike in attacks on my asterisk server, this is what
I get on the LCD of my
Hello, I am trying to get a Wildcard TE110P to work in a relatively
modern HP Proliant DL385p Gen8 server. Being a potent 12 core Opteron
server I expected no problems.
Much to my dismay the dahdi_test results are constantly terrible:
# dahdi_test
Opened pseudo dahdi interface, measuring
On Mon, May 12, 2014 at 4:57 PM, Mike Leddy m...@loop.com.br wrote:
[ 39.223031] wcopenpci: Module loaded
[ 39.751770] wcte1xxp: Setting yellow alarm
# dahdi_hardware
pci::06:00.0 wcte11xp+e159:0001 Digium Wildcard TE110P T1/E1
Board
Mike,
This stuff predates my time on
If the attacks are direct (rather than through Asterisk) and you have a Polycom
phone, check around page 522 of the firmware 4.0 admin guide.
If the attacks are directed at your Asterisk then you should use fail2ban to
dynamically block attackers.
If the attacks are coming to your phone via
15 matches
Mail list logo
