I am really grateful to all the experts on the mailing list who gave me
some very good advice on this problem which I experienced in China. I
think we have fixed the problem and the card is no longer reporting any
problems. We are able to dial out successfully and we will continue to
test.
Here
Excelent!!
but may be better if you send to the list the zaptel.conf and zapata.conf
Regards,
Luis Morales
On Thu, Aug 21, 2008 at 10:19 PM, Lee, John (Sydney)
[EMAIL PROTECTED] wrote:
I am really grateful to all the experts on the mailing list who gave me
some very good advice on this
On 7/31/08, Jay R. Ashworth [EMAIL PROTECTED] wrote:
On Thu, Jul 31, 2008 at 05:36:14PM +1000, Lee, John (Sydney) wrote:
Yes, I tried all sorts of cables and ended up getting the local contact
to complain to NETCOM. An engineer came and swapped the Fast Ethernet
to E1 converter.
Hmmm.
if after you tried both straight through crossover cables and
it still give you RED alarm. just tell them you can't get any
clocking signal. they'll probably send someone on site and test
the line.
Yes, I tried all sorts of cables and ended up getting the local contact
to complain to NETCOM.
On Thu, Jul 31, 2008 at 12:31 PM, Uros Djokic [EMAIL PROTECTED] wrote:
Hi,
Ensure that in file indications.conf you have
[general]
contry=cn ; not usa ! or if you are in Australia shortcut for Australia
Regards,
Uros
--
Use Free Software http://www.fsf.org/
Hi,
Ensure that in file indications.conf you have
[general]
contry=cn ; not usa !
Regards,
Uros
--
Use Free Software http://www.fsf.org/
---
Four essential software freedoms:
1) To study source code
2) To copy program
3) To modify source code
4) To
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Lee, John (Sydney)
Sent: Thursday, July 31, 2008 3:36 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Newbie in China: Red alaram in
Zaptel for E1
Sounds like you're making progress. I would try the above span
definition without the crc4. That might do the trick.
Thanks Brad.
I already tried it without crc4 but it makes no difference.
___
-- Bandwidth and Colocation Provided by
Ensure that in file indications.conf you have
[general]
country=cn ; not usa ! or if you are in Australia shortcut for Australia
Uros, that was a good reminder. However, I don't think it is related to this
problem.
___
-- Bandwidth and
Make experiment.Make loopback Rj-45. (wire 1 from pin 1 to pin 4 wire 2 from
pin 2 to pin 5). Then put it in card and if card is OK you should see green
led.You should also see dozens of ALARMS notices or warnings on asterisk
CLI.
Also check pinout http://www.goonda.org/archive/docs/pinout.html
On Thu, Jul 31, 2008 at 05:36:14PM +1000, Lee, John (Sydney) wrote:
Yes, I tried all sorts of cables and ended up getting the local contact
to complain to NETCOM. An engineer came and swapped the Fast Ethernet
to E1 converter.
Hmmm.
Whose side is Fast Ethernet, and whose side is E1?
Are you
Dan Austin wrote:
John wrote:
Thanks Steve for your suggestions.
In China you will generally get either MFC/R2 or EuroISDN. MFC/R2 is
much more common.
This is exactly my current problem.
NETCOM in Shanghai just told my local contact it is an E1 and that's it.
I
You don't need to install it. Just run kernel/xpp/utils/genzaptelconf
directly from the source directory.
Thanks Tzafrir.
My local contact is away today and so I could not get him to plug the
line to port 4. So, it is still in port 1.
Here is the output after running genzaptelconf.
#
emist wrote:
My best guess from looking at that is that its a driver bug. The last
thing that happens before the lockup seems to be an ioctl call to the
device.
That was a bug that should have been resolved by 1.4.11 (he subsequently
updated and it was resolved).
Matthew Fredrickson
Lee, John (Sydney) wrote:
The test for that is simple:
head -n 1 /proc/zaptel/*
Let's look at all four spans. Not just the first one.
Thanks Tzafrir.
# head -n 1 /proc/zaptel/*
== /proc/zaptel/1 ==
Span 1: TE4/0/1 T4XXP (PCI) Card 0 Span 1 (MASTER) HDB3/ RED
== /proc/zaptel/2
Lee, John (Sydney) wrote:
i've installed several Asterisk systems in Shanghai Beijing.
Thanks Edwin.
The remote site is in Shanghai and NETCOM is the telco.
Do you know if their E1 line is MFC/R2 or EuroISDN?
i'm not sure if they provide MFC/R2. but we always
ordered PRI from them. as far
I think it can't hurt to try a different release. Let me know how it
goes.
Thanks Igor.
I just upgraded zaptel to 1.4.11.
However, I am still seeing red in the alarm in zttool and the LED on
port 1 also shows red.
---
cat
Wow - that's nasty.
Almost like a broken card or MB. Ouch.
Should you call the supplier of the card and ask them about warranty?
PaulH
Thanks Paul.
The TE412P card is fine and the zaptel error in dmesg is fixed by
1.4.11.
However, the red alarms are still there.
Wow - that's nasty.
Almost like a broken card or MB. Ouch.
Should you call the supplier of the card and ask them about warranty?
PaulH
Lee, John (Sydney) wrote:
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has been installed and so I plug it into
On Tue, Jul 29, 2008 at 01:48:26PM +1000, Lee, John (Sydney) wrote:
On the box, first of all, I just installed Zaptel 1.4.10.1.
[..]
BUG: soft lockup - CPU#2 stuck for 16s! [ztcfg:4681]
Hi, just for (all of) you to know this is a known bug of zaptel
1.4.11, the
Hi, just for (all of) you to know this is a known bug of zaptel
1.4.11, the firmware upload procedure is taking some time, operating
like a freeze during the process, so this message appears.
But this isn't a real problem, as it doesn't have any consequences
appart from the message.
On Tue, Jul 29, 2008 at 12:04:43AM -0500, Tilghman Lesher wrote:
On Monday 28 July 2008 22:48:26 Lee, John (Sydney) wrote:
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has been installed and so I plug it into port
1 of a TE412P.
Are you sure
The test for that is simple:
head -n 1 /proc/zaptel/*
Let's look at all four spans. Not just the first one.
Thanks Tzafrir.
# head -n 1 /proc/zaptel/*
== /proc/zaptel/1 ==
Span 1: TE4/0/1 T4XXP (PCI) Card 0 Span 1 (MASTER) HDB3/ RED
== /proc/zaptel/2 ==
Span 2: TE4/0/2 T4XXP (PCI) Card
On Tue, Jul 29, 2008 at 05:55:05PM +1000, Lee, John (Sydney) wrote:
The test for that is simple:
head -n 1 /proc/zaptel/*
Let's look at all four spans. Not just the first one.
Thanks Tzafrir.
# head -n 1 /proc/zaptel/*
== /proc/zaptel/1 ==
Span 1: TE4/0/1 T4XXP (PCI) Card 0
Hi John,
Good to see a fellow Sydney-sider setting up Asterisk in China! Which
city are you in? Our setup is in Kunming, Yunnan province.
I've managed to get a working setup through China Netcom with a
two-port Sangoma card. I'd email you all the settings / versions I'm
using right now but
I tried the suggestion on
http://www.voip-info.org/wiki/view/Asterisk+MFC+R2
http://www.voip-info.org/wiki/view/Asterisk+MFC+R2 but the red alarm is
still on.
An output of 'head -n 1 /proc/zaptel/*' after the fact might help us help
you. Did you re-run ztcfg after editing zaptel.conf ?
On Tue, Jul 29, 2008 at 10:31:43PM +1000, Lee, John (Sydney) wrote:
I tried the suggestion on
http://www.voip-info.org/wiki/view/Asterisk+MFC+R2
http://www.voip-info.org/wiki/view/Asterisk+MFC+R2 but the red alarm is
still on.
An output of 'head -n 1 /proc/zaptel/*' after the fact
Hi John,
In China you will generally get either MFC/R2 or EuroISDN. MFC/R2 is
much more common.
The only oddity with EuroISDN is that it often provided without CRC4.
That doesn't make a lot of sense, but there it is. MFC/R2 seems to be
universally provided without CRC4 in China.
You said you
If you're interested, our working circuit in Chengdu with a China
Telecom PRI is configured as:
/etc/zaptel.conf:
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone = cn
defaultzone=cn
/etc/asterisk/zapata.conf (just including the pertinent lines):
switchtype=euroisdn
signalling=pri_cpe
On Tue, Jul 29, 2008 at 01:56:23PM +0300, Tzafrir Cohen wrote:
An output of 'head -n 1 /proc/zaptel/*' after the fact might help us help
you. Did you re-run ztcfg after editing zaptel.conf ?
On a sidebar, let me suggest head -1q; it's neater.
Cheers,
-- jra
--
Jay R. Ashworth
China for E1 as has been mentioned is a strange place. China is broken up
into two parts basically south of Shanghai and north of Shanghai. It is all
operated by China Telecom and CNC, but the technical aspects of the two
parts are not necessarily the same.
For technical assistance in China we
Lee, John (Sydney) wrote:
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has been installed and so I plug it into port
1 of a TE412P.
i've installed several Asterisk systems in Shanghai Beijing.
On the box, first of all, I just installed Zaptel
An output of 'head -n 1 /proc/zaptel/*' after the fact might help us
help
you. Did you re-run ztcfg after editing zaptel.conf ?
On a sidebar, let me suggest head -1q; it's neater.
Thanks Jay for your neater suggestion!
# head -n1 /proc/zaptel/*
== /proc/zaptel/1 ==
Span 1: TE4/0/1 T4XXP
Thanks Steve for your suggestions.
In China you will generally get either MFC/R2 or EuroISDN. MFC/R2 is
much more common.
This is exactly my current problem.
NETCOM in Shanghai just told my local contact it is an E1 and that's it.
I have no idea whether it is MFC/R2 or EuroISDN and so there
If you're interested, our working circuit in Chengdu with a China
Telecom PRI is configured as:
/etc/zaptel.conf:
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
loadzone = cn
defaultzone=cn
/etc/asterisk/zapata.conf (just including the pertinent lines):
switchtype=euroisdn
i've installed several Asterisk systems in Shanghai Beijing.
Thanks Edwin.
The remote site is in Shanghai and NETCOM is the telco.
Do you know if their E1 line is MFC/R2 or EuroISDN?
red alarm usually means there's no clocking signal.
check all your cables (crossover vs straight through)
Yes, to try port 4 again.
Thanks Tzafrir.
Why do I have to plug it into port 4?
Backup the existing zaptel.conf and run genzaptelconf (no need to
unload
/ reload any modules). What is the output of 'head -n 1
/proc/zaptel/*'
after that?
I could not find genzaptelconf probably because I
On Wed, Jul 30, 2008 at 01:38:11PM +1000, Lee, John (Sydney) wrote:
Yes, to try port 4 again.
Thanks Tzafrir.
Why do I have to plug it into port 4?
Backup the existing zaptel.conf and run genzaptelconf (no need to
unload
/ reload any modules). What is the output of 'head -n 1
You don't need to install it. Just run kernel/xpp/utils/genzaptelconf
directly from the source directory.
Yes mate - I was just 1 sec away from reinstalling zaptel.
Why do I have to plug it into port 4?
Do I have to plug the line into port 4 instead of port 1?
John wrote:
Thanks Steve for your suggestions.
In China you will generally get either MFC/R2 or EuroISDN. MFC/R2 is
much more common.
This is exactly my current problem.
NETCOM in Shanghai just told my local contact it is an E1 and that's it.
I have no idea whether it is MFC/R2 or
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has been installed and so I plug it into port
1 of a TE412P.
On the box, first of all, I just installed Zaptel 1.4.10.1.
# service zaptel restart
Unloading zaptel hardware drivers:ERROR: Module zaptel is in
My best guess from looking at that is that its a driver bug. The last
thing that happens before the lockup seems to be an ioctl call to the
device.
Hope it helps,
Igor H.
Lee, John (Sydney) wrote:
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has
My best guess from looking at that is that its a driver bug. The last
thing that happens before the lockup seems to be an ioctl call to the
device.
Hope it helps,
Igor H.
Thanks Igor.
Does it mean that I should install a later release of zaptel?
On Monday 28 July 2008 22:48:26 Lee, John (Sydney) wrote:
This time, I am trying to remotely install Asterisk in China.
I was told that an E1 line has been installed and so I plug it into port
1 of a TE412P.
Are you sure that they're plugged into port 1 and not port 4? It is a rather
common
Are you sure that they're plugged into port 1 and not port 4? It is a
rather
common mistake to believe that the port numbers start at the bottom of
the card and not at the top.
Thanks Tilghman.
I checked with the guys in the remote office and he is certain that he
has plugged the E1 line
I think it can't hurt to try a different release. Let me know how it goes.
Regards,
Igor H.
Lee, John (Sydney) wrote:
My best guess from looking at that is that its a driver bug. The last
thing that happens before the lockup seems to be an ioctl call to the
device.
Hope it helps,
Igor H.
46 matches
Mail list logo
