URGENT: Call dropping/massive errors when so!

Joined
Dec 3, 2007
Messages
71
Points
0
Hi,
I have finnaly managed to get my TE110P to working with my E1/PRI line. Now, everything works great for a minute or so, but when the below error appears on console, all calls drop instantly!!! Any ideas why? here's the error message:

Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
Use of uninitialized value in concatenation (.) or string at /var/www/html/panel/op_server.pl line 1924.
 
Joined
May 12, 2010
Messages
1,663
Points
0
It might be helpful if you post your file /var/www/html/panel/op_server.pl line 1924.
I don't have any concatenation(.) in this line..
Did you previously edit this file?
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Pacini,

You need to give a little more info. The log you have provided, is for the Operator Panel, and the operator panel doesn't handle errors all that well, which is what you are seeing. This is just a secondary error, e.g. a result of a primary error somewhere else (usually on the telephony interface).

As an example, this type of error can pop up when a ISDN/E1 line has gone into Yellow/Red Alarm. So the primary error is actually the ISDN/E1 line in this particular case.

You need to troll through the /var/log/asterisk/full log and look at what is occurring at the time of the call. There should be some errors showing in the log. Post the relevant errors that you see and this will provide a little more info so we can assist.

Don't post the whole log, just any errors for 1 particular call.

Just to hazard a guess, the first thing I would be looking at, is the ISDN/E1 Synchronisation (Clocking) line in the Zaptel.conf. It is possible that your E1/ISDN vendor has specific clock/sync requirements. The line that you are looking for is similar to span=1,0,0,ccs,hdb3 (example only)
Post the line here and the E1 provider so that we can check that as well....

Hope this helps.....

Regards

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
ramoncio said:
It might be helpful if you post your file /var/www/html/panel/op_server.pl line 1924.
I don't have any concatenation(.) in this line..
Did you previously edit this file?
Sure... here we go:

log_debug( "$heading canal $canal sesion $sesion", 32 ) if DEBUG;

if ( defined($canal) && defined($sesion) ) {
$canal =~ tr/a-z/A-Z/;
$elemento = $canal . "\t" . $sesion;
}


Note, the 1st line is line 1924 ..
 
Joined
Dec 3, 2007
Messages
71
Points
0
Bob said:
Pacini,

You need to give a little more info. The log you have provided, is for the Operator Panel, and the operator panel doesn't handle errors all that well, which is what you are seeing. This is just a secondary error, e.g. a result of a primary error somewhere else (usually on the telephony interface).

As an example, this type of error can pop up when a ISDN/E1 line has gone into Yellow/Red Alarm. So the primary error is actually the ISDN/E1 line in this particular case.

You need to troll through the /var/log/asterisk/full log and look at what is occurring at the time of the call. There should be some errors showing in the log. Post the relevant errors that you see and this will provide a little more info so we can assist.

Don't post the whole log, just any errors for 1 particular call.

Just to hazard a guess, the first thing I would be looking at, is the ISDN/E1 Synchronisation (Clocking) line in the Zaptel.conf. It is possible that your E1/ISDN vendor has specific clock/sync requirements. The line that you are looking for is similar to span=1,0,0,ccs,hdb3 (example only)
Post the line here and the E1 provider so that we can check that as well....

Hope this helps.....

Regards

Bob
Hey Bob,
You're correct, I have been seeing yellow/green going back and forth on my TE110P E1 card, thought this is normal. Here's my zaptel.conf timing line:

span=1,1,0,ccs,hdb3,crc4

Thank you guys for the help, I appreciate it
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
You're correct, I have been seeing yellow/green going back and forth on my TE110P E1 card, thought this is normal. Here's my zaptel.conf timing line:

span=1,1,0,ccs,hdb3,crc4
Pacini,

We are now on the right path, the Yellow/Green LED should be lit permanently green. Yellow is normally an indiction of a protocol error/or issue on the remote end (e.g. Cable/Carrier equipment).

Thanks for the SPAN line, and now we are closer to the issue, can you provide

1) your Telco vendor
2)What model of Telco termination device (the actual device installed by the Telco
3) Whether you are using a ISDN/E1 Xover cable
4) Distance from your Telco termination device to your Elastix Box...
5) A copy of your Zaptel.conf
6) A copy of your Zapata.conf
With the last two, just make sure no identifiable details remain visible e.g. phone numbers etc...

The SPAN line that you are using looks correct...

Just to give you something to try as well, can you confirm that you busydetect in zapata.conf is set to no in your ZAPATA.CONF.

Just one other thing. Sometimes after a bit of stuffing around, the Telco termination unit may require a quick switch off and on (only do this if the device is local to you, if it is a central Fiber optic device for the whole building, that is a different matter). Just a quick reset is enough.

Regards
Bob<br><br>Post edited by: Bob, at: 2007/12/22 00:23
 
Joined
Dec 3, 2007
Messages
71
Points
0
Bob said:
1) your Telco vendor
2)What model of Telco termination device (the actual device installed by the Telco
3) Whether you are using a ISDN/E1 Xover cable
4) Distance from your Telco termination device to your Elastix Box...
1) It's a local MCI partner called UCC here in Kuwait.
2) Paradyne modem thru SHDSL E1 line.
3) Yes. I'm using Xover cable, straight never got the line up, ie, always red led on the iface card.
4) 2 meters

5) A copy of your Zaptel.conf
Zaptel.conf:

#Global data

span=1,1,0,ccs,hdb3,crc4
bchan=1-15,17-31
dchan=16

loadzone = uk
defaultzone = uk

6) A copy of your Zapata.conf
Zapata.conf:

Zapata telephony interface
;
; Configuration file

[trunkgroups]

[channels]

language=en
context=from-zaptel
;signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes

switchtype=euroisdn
;If you connect to a hicom PBX set your ISDN Numbering Plan Identifier to unknown.
pridialplan=unknown
signalling=pri_cpe

busydetect=no
callprogress=no

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no

channel=>1-15,17-31

;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

;Include genzaptelconf configs
#include zapata-auto.conf

;Include AMP configs
#include zapata_additional.conf


Just to give you something to try as well, can you confirm that you busydetect in zapata.conf is set to no in your ZAPATA.CONF.
I actually have both busydetect and callprogress set to no in zapata.<br><br>Post edited by: pacini, at: 2007/12/22 00:49
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Just a quick question.....

Is the cable that you used, a standard Ethernet X-Over cable or an ISDN X-Over cable???? for the connection from the Paradyne modem to the TE110??

Regards

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
Yes bro,
I made a standard CAT5e Xover cable. looks like this:
End-A:

1 -> Orange-White
2 -> Orange
3 -> Green-White
4 -> Blue
5 -> Blue-White
6 -> Green
7 -> Brown-White
8 -> Brown.

End-B:

1 -> Green-White
2 -> Green
3 -> Orange-White
4 -> Blue
5 -> Blue-White
6 -> Orange
7 -> Brown-White
8 -> Brown

So you think it's the cable huh? are both zaptel & zapata files above look fine?
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Pacini,

More than likely the cable

An e1/isdn xover cable is not the same as a Ethernet x-over cable. Pinouts for the E1/ISDN Xover Cable is as follows:


RJ-45 ----- RJ-45
1 ----------- 4
2 ----------- 5
4 ----------- 1
5 ----------- 2


As it is not one you make regularly, I suggest using the scheme above, apply (write) colours to the numbers, as you can get confused. All other lines are not connected.

I make this cable every few weeks, so the above pinouts are correct (at least for Australian Telco E1's, which adhere to the EuroISDN standard).

Please note that the cable is required for equipment to equipment. If it is terminated on a patch panel, your telco may have crossed it over on the patch panel. However this is unlikely as you stated that a straight through cable does not work.

Please let us know how you go, either way, as your reply will let others on these forums resolve these issues.

I am in and out every hour or so (Christmas shopping), but I will look to see if you are up and running each time I pop in....

Regards

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
Hey Bob,
Did change the cable as described above, but then I get a red led which means a no-go. I guess I'll contact my Telco asking them for a cable + to look into this matter before I start thinking it's a software problem, ie, Elastix.

Merry Xmass ya'll :)
 
Joined
Dec 3, 2007
Messages
71
Points
0
UPDATE: did try an E1 cable from the telco, and it got even worse, the card is showing RED now :(

Is there any span settings that I can try?
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Pacini,

I have just got to go out and do a few last minute jobs for clients, but when I return (a few hours), I will try and help you through this, and delve a little further into the equipment that you have....

Can you confirm the pinouts of the cable supplied by the Telco, so we know where we stand...

Everything else you have given me is fine....

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
Hey Bob,
it's exactly how you mentioned in your previous post.

1
2
4
5

TO

4
5
1
2

the thing is when I hook back the Eth Cross cable, it works just fine but drops calls exactly after 2mins.
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Pacini,

We need to go back to basics.

First of all lets assume that the Ethernet cable that provides the green/yellow led is the correct cable and leave that plugged in.

Now make a call or two and we need the details from the /var/log/asterisk/full log file at the point that the call is dropped.

I am expecting to see the D channel has dropped, which is why the call is dropping.

Can you confirm this....

Regards

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
Hey Bob,
Check this out, looks interesting:

[Dec 24 23:57:00] VERBOSE[2554] logger.c: -- Requested transfer capability: 0x00 - SPEECH
[Dec 24 23:57:00] VERBOSE[2554] logger.c: -- Called 1/113
[Dec 24 23:57:00] DEBUG[2335] chan_zap.c: Queuing frame from PRI_EVENT_PROCEEDING on channel 0/1 span 1
[Dec 24 23:57:00] VERBOSE[2554] logger.c: -- Zap/1-1 is proceeding passing it to SIP/2250101-08436aa0
[Dec 24 23:57:00] DEBUG[2335] chan_zap.c: Queuing frame from PRI_EVENT_PROGRESS on channel 0/1 span 1
[Dec 24 23:57:00] VERBOSE[2554] logger.c: -- Zap/1-1 is making progress passing it to SIP/2250101-08436aa0
[Dec 24 23:57:00] VERBOSE[2554] logger.c: -- Zap/1-1 answered SIP/2250101-08436aa0
[Dec 24 23:57:14] NOTICE[2335] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 24 23:57:46] NOTICE[2335] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 24 23:57:54] NOTICE[2335] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 24 23:58:10] NOTICE[2335] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
Dec 24 23:58:26] NOTICE[2335] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 24 23:59:00] VERBOSE[2335] logger.c: -- Channel 0/1, span 1 got hangup request, cause 31
[Dec 24 23:59:00] DEBUG[2554] chan_zap.c: Set option AUDIO MODE, value: ON(1) on Zap/1-1
[Dec 24 23:59:00] DEBUG[2554] chan_zap.c: Not yet hungup... Calling hangup once with icause, and clearing call
[Dec 24 23:59:00] DEBUG[2554] chan_zap.c: Set option AUDIO MODE, value: OFF(0) on Zap/1-1
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Hungup 'Zap/1-1'
[Dec 24 23:59:00] VERBOSE[2554] logger.c: == Spawn extension (macro-dialout-trunk, s, 25) exited non-zero on 'SIP/2250101-08436aa0' in macro 'dialout-trunk'
[Dec 24 23:59:00] VERBOSE[2554] logger.c: == Spawn extension (macro-dialout-trunk, s, 25) exited non-zero on 'SIP/2250101-08436aa0'
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [h@macro-dialout-trunk:1] Macro("SIP/2250101-08436aa0", "hangupcall") in new stack
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:1] ResetCDR("SIP/2250101-08436aa0", "w") in new stack
[Dec 24 23:59:00] DEBUG[2554] app_macro.c: Executed application: ResetCDR
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:2] NoCDR("SIP/2250101-08436aa0", "") in new stack
[Dec 24 23:59:00] DEBUG[2554] app_macro.c: Executed application: NoCDR
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:3] GotoIf("SIP/2250101-08436aa0", "1?skiprg") in new stack
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Goto (macro-hangupcall,s,6)
[Dec 24 23:59:00] DEBUG[2554] app_macro.c: Executed application: GotoIf
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:6] GotoIf("SIP/2250101-08436aa0", "1?skipblkvm") in new stack
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Goto (macro-hangupcall,s,9)
[Dec 24 23:59:00] DEBUG[2554] app_macro.c: Executed application: GotoIf
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:9] GotoIf("SIP/2250101-08436aa0", "1?theend") in new stack
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Goto (macro-hangupcall,s,11)
[Dec 24 23:59:00] DEBUG[2554] app_macro.c: Executed application: GotoIf
[Dec 24 23:59:00] VERBOSE[2554] logger.c: -- Executing [s@macro-hangupcall:11] Hangup("SIP/2250101-08436aa0", "") in new stack
[Dec 24 23:59:00] VERBOSE[2554] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/2250101-08436aa0' in macro 'hangupcall'
[Dec 24 23:59:00] VERBOSE[2554] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/2250101-08436aa0'


This log was taken from a 2 minutes "Sharp" dropped call...<br><br>Post edited by: pacini, at: 2007/12/25 00:22
 
Joined
Dec 3, 2007
Messages
71
Points
0
Some more logging:


Dec 25 00:14:39] NOTICE[3043] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 25 00:14:39] NOTICE[3043] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1
[Dec 25 00:14:39] WARNING[3043] chan_zap.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 1: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 1
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 2: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 2
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 3: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 3
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 4: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 4
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 5: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 5
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 6: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 6
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 7: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 7
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 8: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 8
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 9: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 9
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 10: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 10
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 11: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 11
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 12: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 12
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 13: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 13
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 14: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 14
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 15: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 15
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 17: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 17
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 18: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 18
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 19: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 19
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 20: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 20
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 21: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 21
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 22: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 22
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 23: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 23
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 24: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 24
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 25: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 25
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 26: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 26
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 27: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 27
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 28: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 28
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 29: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 29
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 30: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 30
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Detected alarm on channel 31: Yellow Alarm
[Dec 25 00:14:39] WARNING[3044] chan_zap.c: Unable to disable echo cancellation on channel 31
[Dec 25 00:14:40] NOTICE[3043] chan_zap.c: PRI got event: No more alarm (5) on Primary D-channel of span 1
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 1
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 2
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 3
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 4
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 5
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 6
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 7
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 8
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 9
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 10
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 11
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 12
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 13
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 14
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 15
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 17
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 18
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 19
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 20
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 21
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 22
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 23
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 24
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 25
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 26
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 27
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 28
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 29
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 30
[Dec 25 00:14:40] NOTICE[3044] chan_zap.c: Alarm cleared on channel 31
[Dec 25 00:14:40] VERBOSE[3043] logger.c: == Primary D-Channel on span 1 up
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/1 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/2 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/3 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/4 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/5 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/6 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/7 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/8 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/9 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/10 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/11 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/12 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/13 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/14 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/15 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/17 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/18 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/19 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/20 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/21 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/22 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/23 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/24 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/25 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/26 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/27 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/28 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/29 successfully restarted on span 1
[Dec 25 00:14:51] VERBOSE[3043] logger.c: -- B-channel 0/30 successfully restarted on span 1
[Dec 25 00:14:52] VERBOSE[3043] logger.c: -- B-channel 0/31 successfully restarted on span 1
[Dec 25 00:14:55] NOTICE[3043] chan_zap.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1
[Dec 25 00:14:55] NOTICE[3043] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1
[Dec 25 00:14:55] WARNING[3043] chan_zap.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Dec 25 00:14:55] WARNING[3044] chan_zap.c: Detected alarm on channel 1: Yellow Alarm<br><br>Post edited by: pacini, at: 2007/12/25 01:26
 
Joined
Dec 3, 2007
Messages
71
Points
0
and this is when changed 1st line on Zaptel.conf
From:
span=1,1,1,ccs,hdb3

To:
span=1,1,0,ccs,hdb3,crc4


[Dec 25 01:06:33] NOTICE[3636] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 1
[Dec 25 01:06:33] ERROR[3703] chan_zap.c: Write to 40 failed: Unknown error 500
[Dec 25 01:06:33] ERROR[3703] chan_zap.c: Short write: 0/15 (Unknown error 500)
[Dec 25 01:06:33] WARNING[3703] chan_zap.c: Detected alarm on channel 1: Yellow Alarm
[Dec 25 01:06:33] DEBUG[3703] chan_zap.c: Set option AUDIO MODE, value: ON(1) on Zap/1-1
[Dec 25 01:06:33] DEBUG[3703] chan_zap.c: Set option AUDIO MODE, value: OFF(0) on Zap/1-1
[Dec 25 01:06:33] VERBOSE[3703] logger.c: -- Hungup 'Zap/1-1'
[Dec 25 01:06:33] VERBOSE[3703] logger.c: == Spawn extension (macro-dialout-trunk, s, 25) exited non-zero on 'SIP/2250101-08c020e8' in macro 'dialout-trunk'
[Dec 25 01:06:33] VERBOSE[3703] logger.c: == Spawn extension (macro-dialout-trunk, s, 25) exited non-zero on 'SIP/2250101-08c020e8'
[Dec 25 01:06:33] VERBOSE[3703] logger.c: -- Executing [h@macro-dialout-trunk:1] Macro("SIP/2250101-08c020e8", "hangupcall") in new stack
[Dec 25 01:06:33] VERBOSE[3703] logger.c: -- Executing [s@macro-hangupcall:1] ResetCDR("SIP/2250101-08c020e8", "w") in new stack
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 2: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 2
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 3: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 3
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 4: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 4
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 5: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 5
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 6: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 6
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 7: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 7
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 8: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 8
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 9: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 9
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 10: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 10
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 11: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 11
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 12: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 12
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 13: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 13
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 14: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 14
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 15: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 15
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 17: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 17
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 18: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 18
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 19: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 19
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 20: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 20
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 21: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 21
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 22: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 22
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 23: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 23
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 24: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 24
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 25: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 25
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 26: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 26
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 27: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 27
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 28: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 28
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 29: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 29
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 30: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 30
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Detected alarm on channel 31: Yellow Alarm
[Dec 25 01:06:33] WARNING[3637] chan_zap.c: Unable to disable echo cancellation on channel 31
[Dec 25 01:06:33] NOTICE[3636] chan_zap.c: PRI got event: Alarm (4) on Primary D-channel of span 1
[Dec 25 01:06:33] WARNING[3636] chan_zap.c: No D-channels available! Using Primary channel 16 as D-channel anyway!
[Dec 25 01:06:33] DEBUG[3703] app_macro.c: Executed application: ResetCDR
 

Bob

Joined
Nov 4, 2007
Messages
2,400
Points
36
Pacini,

A couple of possible scenarios.....

1) incorrect framing type e.g. CCS is not correct. The only ones that can answer this is your Telco

2) Badly compiled Zaptel - I know there was one recent release that had an issue, but can't remember which one it was.

3) Interrupt issue, causing you to miss frames but very unusual for it to be spot on two minutes each time.

Can I confirm what version of Elastix you are upto...e.g. since the original install, have you performed a
yum -y update
to bring up all the versions, including Asterisk and Zaptel upto the latest versions?? If you haven't I receommend proceeding with this straight away.

As for the interrupt issue, if there are any devices that are not needed or not being used on your system e.g. Sata interface not being used (e.g. you are using IDE), or USB is not being used, or other BIOS Settings that can change the configuration of your basic system.

Regards

Bob
 
Joined
Dec 3, 2007
Messages
71
Points
0
Hey Bob,
Thanks for the help. Yes, the 1st thing I did was to update the box thru 'yum'. I'm giving up on this card, I guess I'll go with fonebridge and save myself all this headache. Would you recommend that? If not, what's best support E1 card out there to be used with Asterisk?
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,987
Messages
131,100
Members
17,716
Latest member
Orbit114
Top