diff options
| author | Kevin P. Fleming <kpfleming@digium.com> | 2009-01-19 18:59:38 +0000 |
|---|---|---|
| committer | Kevin P. Fleming <kpfleming@digium.com> | 2009-01-19 18:59:38 +0000 |
| commit | c8eab5cc37b923e84da493d54314df836d0c30a2 (patch) | |
| tree | 0a3d5eefb4382a941c774e1468131a9b25736700 /README | |
| parent | 165680e91300531d30deb3319ec9376d372b5d4a (diff) | |
correct missing words and other typographical errors, and change wording to make sense in this file instead of a mailing list post
git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@5749 a0bf4364-ded3-4de4-8d8a-66a801d63aff
Diffstat (limited to 'README')
| -rw-r--r-- | README | 44 |
1 files changed, 23 insertions, 21 deletions
@@ -451,31 +451,33 @@ Alarm Types An alarm indicates that a port is not available for some reason. Thus it is probably not a good idea to try to call out through it. + Red Alarm ^^^^^^^^^ -Your T1/E1 port will go into red alarm when it maintain synchronization -with the remote switch. A red alarm typically indicates either a -physical wiring problem, loss of connectivity, or a framing and/or -line-coding mismatch with the remote switch. When your T1/E1 port loses -sync, it will transmit a yellow alarm to the remote switch to indicate -that it's having a problem receiving signal from the remore switch. +Your T1/E1 port will go into red alarm when it cannot maintain +synchronization with the remote switch. A red alarm typically +indicates either a physical wiring problem, loss of connectivity, or a +framing and/or line-coding mismatch with the remote switch. When your +T1/E1 port loses sync, it will transmit a yellow alarm to the remote +switch to indicate that it's having a problem receiving signal from +the remote switch. The easy way to remember this is that the R in red stands for "right -here" and "receive"... indicating that we're having a problem right here -receiving the signal from the remote switch. +here" and "receive"... indicating that we're having a problem right +here receiving the signal from the remote switch. Yellow Alarm ^^^^^^^^^^^^ (RAI -- Remote Alarm Indication) -Your T1/E1 port will go into yellow alarm when it receives a signal from -the remote switch that the port on that remote switch is in red alarm. -This essentially means that the remote switch is not able to maintain -sync with you, or is not receiving your transmission. +Your T1/E1 port will go into yellow alarm when it receives a signal +from the remote switch that the port on that remote switch is in red +alarm. This essentially means that the remote switch is not able to +maintain sync with you, or is not receiving your transmission. -The easy way to remember this is that the Y in yellow stands for -"yonder"... indicating that the remote switch (over yonder) isn't able +The easy way to remember this is that the Y in yellow stands for +"yonder"... indicating that the remote switch (over yonder) isn't able to see what you're sending. @@ -483,13 +485,13 @@ Blue Alarm ^^^^^^^^^^ (AIS -- Alarm Indication Signal) -Your T1/E1 port will go into blue alarm when it receives all unframed 1s -on all timeslots from the remote switch. This is a special signal to -indicate that the remote switch is having problems with it's upstream -connection. As far as I know, dahdi_tool/zttool and Asterisk don't -correctly indicate a blue alarm (at least I've never seen them indicate -one). The easy way to remember this is that streams are blue, so a blue -alarm indicates a problem upstream from the switch you're connected to. +Your T1/E1 port will go into blue alarm when it receives all unframed +1s on all timeslots from the remote switch. This is a special signal +to indicate that the remote switch is having problems with its +upstream connection. dahdi_tool and Asterisk don't correctly indicate +a blue alarm at this time. The easy way to remember this is that +streams are blue, so a blue alarm indicates a problem upstream from +the switch you're connected to. Recovering from Alarm |