Okay. I ordered a commercially made T1 crossover cable, connected all of the
cables and rebooted both computers.
I no longer get the 'Got S-frame while link down' or 'HDLC Bad FCS' errors.
However, I still receive the series of 'Detected alarm on channel NN: Red
Alarm' and 'Unable to disable echo
Brian Alexander wrote:
*snipped
The errors all seem to be about echo cancellation... What do I need to do to
force asterisk to never disable echo cancellation?
*snipped
there used to be this in ../zaptel/zconfig.h
#define NO_ECHOCAN_DISABLE
check if whatever version you are running has
At this point I do not think the problem is the wiring. What else should I
try?
___
Sign up now for AstriCon 2007! September 25-28th. http://www.astricon.net/
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users
Brian Alexander wrote:
At this point I do not think the problem is the wiring. What else
should I try?
Have you confirmed that the failing card is working correctly? Maybe
the card is at fault.
Doug
--
Ben Franklin quote:
Those who would give up Essential Liberty to purchase a little
On 9/24/07, Doug Lytle [EMAIL PROTECTED] wrote:
Have you confirmed that the failing card is working correctly? Maybe
the card is at fault.
All of the cards have been confirmed to work by themselves.
-Brian
___
Sign up now for AstriCon 2007!
Brian Alexander wrote:
On 9/24/07, *Doug Lytle* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Have you confirmed that the failing card is working correctly? Maybe
the card is at fault.
All of the cards have been confirmed to work by themselves.
The only other suggestion I
On 9/24/07, Doug Lytle [EMAIL PROTECTED] wrote:
The only other suggestion I have would have would be to use IAX instead
of PRI for inter-machine communications.
LOL Yeah, normally that is what I would use. Unfortunately it is not an
option for this...
Brian Alexander wrote:
On 9/24/07, *Doug Lytle* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
The only other suggestion I have would have would be to use IAX
instead
of PRI for inter-machine communications.
LOL Yeah, normally that is what I would use. Unfortunately it
On 9/24/07, Brian Alexander [EMAIL PROTECTED] wrote:
At this point I do not think the problem is the wiring. What else should I
try?
Is this the latest Zaptel? Is it 1.4 or 1.2? I may have missed it in a
previous message if you mentioned it.
I've got a setup where I have a 2 port PRI on
Brian Alexander wrote:
Have any of you connected two asterisk machines by t1 crossover using
pri_net/pri_cpe signaling? I am completely stumped and would love to
know that some had done this and what their
What does your cable pin in/out look like. I haven't connected two
Asterisk
On Fri, 2007-09-21 at 09:31 -0400, Brian Alexander wrote:
I tried two other cables this morning with the same results...
Hmmnn... what kind of cable are you using? You're using a T1-crossover
cable, correct? (Not an ethernet crossover, not a straight-through
ethernet cable.)
Check out the
Brian,
I hope this helps, it is slightly different from what you have
setup. Here is what I used to connect my asterisk server to our
Norstar Meridian. The Norstar T1 was setup as pri_cpe with the 24th
channel as D. Check out this webpage for making a T1 crossover cable :
Thanks for all of the feedback. I really appreciate the help! :)
My cable is
1--4
2--5
4--1
5--2
I got this from
http://www.voip-info.org/wiki/view/crossover+T1+cable
http://help.fonality.com/index.php/T1_crossover_HOWTO
On 9/20/07, Jared Smith [EMAIL PROTECTED] wrote:
I'd look at your wiring, as an HDLC error like that is usually an
indication of some type of a problem at the physical layer.
I tried two other cables this morning with the same results...
While I was swapping cables around I unloaded asterisk
On 9/21/07, Forrest Beck [EMAIL PROTECTED] wrote:
You should also try making/obtaining a T1 loopback adapter and test both
cards.
http://www.adtran.com/adtranpx/Doc/0/FMPI9MBKGJBH39S8038BE81ID8/CU-2abf1b83844b11d78ff20c045003.html
I have not tested with a loop back but I did verify that
Brian Alexander wrote:
Thanks for all of the feedback. I really appreciate the help! :)
My cable is
1--4
2--5
4--1
5--2
I believe you need to change your cabling.
Doug
--
Ben Franklin quote:
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve
On Friday 21 September 2007 10:08:06 Doug Lytle wrote:
Brian Alexander wrote:
Thanks for all of the feedback. I really appreciate the help! :)
My cable is
1--4
2--5
4--1
5--2
I believe you need to change your cabling.
Uh, why? That is the correct pinout for T1 crossover.
--
Tilghman Lesher wrote:
Uh, why? That is the correct pinout for T1 crossover.
Then why does mine work? Is it a straight though cable that is needed then?
Doug
--
Ben Franklin quote:
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither
On Friday 21 September 2007 12:01:56 Doug Lytle wrote:
Tilghman Lesher wrote:
Uh, why? That is the correct pinout for T1 crossover.
Then why does mine work? Is it a straight though cable that is needed
then?
A straight-through cable to used for connecting from a QuickJack to a T1
card,
Tilghman Lesher wrote:
A straight-through cable to used for connecting from a QuickJack to a T1
card, but a T1 crossover is needed for card-to-card (or card-to-channel bank,
for that matter).
I have a Sangoma 102u port 1 to port 2.
And, my Micoscanner is showing
1 -- 5
2 -- 4
4 --
In article [EMAIL PROTECTED],
Doug Lytle [EMAIL PROTECTED] wrote:
Tilghman Lesher wrote:
A straight-through cable to used for connecting from a QuickJack to a T1
card, but a T1 crossover is needed for card-to-card (or card-to-channel
bank,
for that matter).
I have a Sangoma 102u
I am trying to connect two machines to each other with an T1 crossover
cable. The first machine has two TE120P cards - one connecting to the telco
on an ISDN PRI. The second to a crossover T1 cable to a second machine which
has one TE120P card.
Telco -cA- Machine1 -cB- Machine2
Machine1: Two
On Thu, 2007-09-20 at 13:20 -0400, Brian Alexander wrote:
Machine 1 experiences almost the same behavior on its span. The only
differance I am noticing is that instead of the S-frame error I get
the following notice:
chan_zap.c:8457 pri_dchannel: PRI got event: HDLC Bad FCS (8) on
23 matches
Mail list logo
