On Mon, Oct 20, 2008 at 04:28:30PM +1300, CSB wrote:
> I installed Trixbox and a TDM400P with 2 FXO and 2 FXS ports and am having
> an annoying issue with the FXO ports. As soon as I plug either one into the
> phone line it's as though the line is disconnected i.e. get disconnected
> tone when trying to dial out, line is busy when dialling in.
Err... it should be exactly the other way around. You should have an
alarm when you disconnect.
What version of zaptel is it?
cat /sys/modules/zaptel/version
>
> The CLI shows the following:
> trixbox1*CLI> zap show channel 4
> Channel: 4
> File Descriptor: 18
> Span: 11*
> Extension:
> Dialing: no
> Context: from-pstn
> Caller ID:
> Calling TON: 0
> Caller ID name:
> Destroy: 0
> InAlarm: 1
> Signalling Type: FXS Kewlstart
> Radio: 0*
> Owner: <None>
> Real: <None>
> Callwait: <None>
> Threeway: <None>
> Confno: -1
> Propagated Conference: -1
> Real in conference: 0
> DSP: no1*
> Relax DTMF: no
> Dialing/CallwaitCAS: 0/0
> Default law: ulaw
> Fax Handled: no
> Pulse phone: no
> Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
> Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
> Onhook
>
> When plugged in:
> trixbox1*CLI> zap show channel 4
> Channel: 4
> File Descriptor: 18
> Span: 11*
> Extension:
> Dialing: noI
> Context: from-pstn
> Caller ID: I
> Calling TON: 0
> Caller ID name:
> Destroy: 0
> InAlarm: 0
It wasn't in alarm. Up until 1.4.22 there was no initial check for an
alarm on the channels at startup, hence the alarm status at startup
might be incorrect.
> Signalling Type: FXS Kewlstart
> Radio: 0*
> Owner: <None>
> Real: <None>
> Callwait: <None>
> Threeway: <None>
> Confno: -1
> Propagated Conference: -1
> Real in conference: 0
> DSP: no1*
> Relax DTMF: no
> Dialing/CallwaitCAS: 0/0
> Default law: ulaw
> Fax Handled: no
> Pulse phone: no
> Echo Cancellation: 128 taps unless TDM bridged, currently OFF Actual
> Confinfo: Num/0, Mode/0x0000 Actual Confmute: No Hookstate (FXS only):
> Offhook
>
Is this Zaptel 1.4.11?
> When cable plugged in:
> [Oct 20 09:02:56] DEBUG[2359] chan_zap.c: Monitor doohicky got event No more
> alarm on channel 4 [Oct 20 09:02:56] NOTICE[2359] chan_zap.c: Alarm cleared
> on channel 4
"alarm cleared" - no longer in alarm. This should not disconnect a call.
But it should have not been in a call in the first place (though see the
above comment about initial alarm status).
>
> When cable unplugged:
> [Oct 20 09:04:55] DEBUG[2359] chan_zap.c: Monitor doohicky got event Alarm
> on channel 4 [Oct 20 09:04:55] WARNING[2359] chan_zap.c: Detected alarm on
> channel 4: No Alarm [Oct 20 09:04:55] DEBUG[2359] chan_zap.c: disabled echo
> cancellation on channel 4
Again, exactly the reverse alarm than it should be.
To see the status of alarms:
cat /proc/zaptel/1
If there is 'RED' on a channel, it is in alarm.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
