Displaying 3 results from an estimated 3 matches for "ring_trip_tr".
Did you mean:
ring_trip_tres
2007 Jan 27
1
FXS - Init Indirect Registers UNSUCCESSFULLY.
...(just FXS modules) that does not see this
problem when I place it in the same slot.
Here is what dmesg shows for the TDM22B when the system boots, or when I
issues modprobe wctdm:
Freshmaker version: 73
Freshmaker passed register test
!!!!!!! LOOP_CLOSE_TRES iREG 1C = 1 should be 1000
!!!!!!! RING_TRIP_TRES iREG 1D = 8000 should be 3600
!!!!!!! COMMON_MIN_TRES iREG 1E = 0 should be 1000
!!!!!!! COMMON_MAX_TRES iREG 1F = 0 should be 200
!!!!!!! PWR_ALARM_Q1Q2 iREG 20 = 1480 should be 7C0
!!!!!!! PWR_ALARM_Q3Q4 iREG 21 = 37C0 should be 2600
!!!!!!! PWR_ALARM_Q5Q6 iREG 22 = 3D70 should be 1B80
!!!!!!!...
2011 Feb 21
3
Problem installing FXS module in old digium 4 channel tdm card
...installed an FXS module onto a 4 channel tdm thats about 5
years old and it wont work. Running dmesg I can see the following
error:
Zapata Telephony Interface Registered on major 196
Freshmaker version: 71
Freshmaker passed register test
!!!!!!! LOOP_CLOSE_TRES iREG 1C = 1 should be 1000
!!!!!!! RING_TRIP_TRES iREG 1D = 8000 should be 3600
!!!!!!! COMMON_MIN_TRES iREG 1E = 0 should be 1000
!!!!!!! COMMON_MAX_TRES iREG 1F = 0 should be 200
!!!!!!! PWR_ALARM_Q1Q2 iREG 20 = 1480 should be 7C0
!!!!!!! PWR_ALARM_Q3Q4 iREG 21 = 37C0 should be 2600
!!!!!!! PWR_ALARM_Q5Q6 iREG 22 = 3D70 should be 1...
2007 Feb 09
0
TDM2400: some FXS module fail
.... They are both connected to power.
Unfortunately some of the FXS module fail to initialize and I find
following messages in the logs (the rest of the FXS modules work
well). Could someone give me some advice?
!!!!!!! LOOP_CLOSE_TRES iREG 1C = 1 should be 1000
Feb 9 18:09:45 [kernel] !!!!!!! RING_TRIP_TRES iREG 1D = 8000 should be 3600
Feb 9 18:09:45 [kernel] !!!!!!! COMMON_MIN_TRES iREG 1E = 0 should be 1000
Feb 9 18:09:45 [kernel] !!!!!!! COMMON_MAX_TRES iREG 1F = 0 should be 200
Feb 9 18:09:45 [kernel] !!!!!!! PWR_ALARM_Q1Q2 iREG 20 = 1480 should be 7C0
Feb 9 18:09:45 [kernel] !!!!!!...