Displaying 4 results from an estimated 4 matches for "2xe1".
Did you mean:
0xe1
2009 Apr 08
3
Multi Frequency Cycle Timeout - E1-R2 METROTEL COLOMBIA
Hi,
I have installed Elastix 1.5.2 (Barranquilla, Colombia (TELCO: METROTEL))
with a TE220P (2xE1) and TDM2400P (16FXS), openr2 is included in 1.5.2
version. The outcoming calls are ok, but with incoming call i have an error:
ERROR*[*14972*]* chan_dahdi.c: Chan 2 - Protocol error. Reason = Multi
Frequency Cycle Timeout, R2 State =
Seize ACK Transmitted, MF state = Category Request Transmitted,...
2003 Nov 21
3
PRI problems
I've got a couple of PRIs coming in from a SUMA 4 switch with some 800
numbers routed through it.
When the calls come in, I get the following message on the console and the
call never makes it through:
(800 number is fake)
Extension '8005551212' in context 'nonauthenticated' from '232102749585'
does not exist. Rejecting the call on span 4, channel 1.
I do have the
2015 Mar 05
0
DAHDI 2.10 on CentOS 5.11
I have just installed DAHDI 2.10.0.1 on a system running CentOS 5.11
(let's not get sidetracked into discussing the version of CentOS - there
are reasons for using it in this case).
The system has a TE220 card with 2xE1.
It has been working fine, but when booting, the udev startup gives out
warnings about ATTRS{hardware_id} and ATTRS{location} not being found.
After doing some research, I changed ATTRS to SYSFS in the file
/etc/udev/rules.d/dahdi.rules, and the warnings went away. Although I did
notice that afte...
2007 May 23
0
Deadlock problem with agents, queues and PRI (stop accepting incoming calls in PRI line)
Hi everyone,
We have a Asterisk-based call center deployment with around 40 SIP users,
attending incoming calls from two PRI lines (2xE1) using agents and queues.
The problem is that Asterisk stops accepting new incoming calls to the PRI
lines without reason, although there should be free channels to make room
for new incoming calls, but Asterisk thinks these channels are being used.
SIP calls can be placed without problemsbetween...