|
Grex > Coop10 > #21: PLEDGE DRIVE: Buying Grex a Much Faster Internet Connection |  |
|
| Author |
Message |
| 25 new of 203 responses total. |
aruba
|
|
response 175 of 203:
| 
Oct 9 21:51 UTC 1997 |
Have you called Ken K. about this, STeve? And is there another item where
the ISDN status is being discussed?
|
valerie
|
|
response 176 of 203:
|
Oct 10 02:34 UTC 1997 |
This response has been erased.
|
aruba
|
|
response 177 of 203:
|
Oct 10 04:13 UTC 1997 |
Thanks.
|
steve
|
|
response 178 of 203:
|
Oct 11 16:56 UTC 1997 |
If it doesn't get resolved very soon (if it hasn't already) I'll
breath some fire on Ken's direction, but it really is a repair department
issue. Actually, its another one of our Ameritech-is-disfunctional
issues, of which we have many.
|
valerie
|
|
response 179 of 203:
|
Oct 11 22:27 UTC 1997 |
This response has been erased.
|
i
|
|
response 180 of 203:
|
Oct 11 22:49 UTC 1997 |
Griping to the Mich. Public Service Commission got my company a real,
working ISDN line very quickly after many weeks of hassles with Ameritech.
|
krj
|
|
response 181 of 203:
|
Oct 12 04:33 UTC 1997 |
Would anyone like to describe "it doesn't work" in any more detail?
|
valerie
|
|
response 182 of 203:
|
Oct 13 02:39 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 183 of 203:
|
Oct 13 02:39 UTC 1997 |
This response has been erased.
|
scg
|
|
response 184 of 203:
|
Oct 13 07:20 UTC 1997 |
re 181:
This is the first time I've been thinking about Grex's ISDN line while
I've had a P50 manual in front of me in a while. I checked the manual, and
the indicator it gives for line status translates to "The line is not active
at this time, but is physically connected."
This should ideally be a repair issue, so dealing with repair is the right
thing to do on this, assuming that route goes anywhere. Jared has been
dealing with Ameritech on it. The last mail I saw from him said that
Ameritech was working on the problem. From what I understand Jared is out
of the country until Wednesday, so I'm not sure how to get trouble ticket
numbers or status reports form him before then.
|
krj
|
|
response 185 of 203:
|
Oct 13 16:12 UTC 1997 |
I'm probably nagging needlessly, especially with jared unavailable.
Is the line status indicator you cite above a "cause code", or the
blinkie light on the front?
From either P50, have you been able to make a loopback call, where your
B1 number calls your B2 number? If the loopback fails, what is
cause code?
What software rev is in the P50s?
(Feel free to tell me to go away. I probably know just enough to be
dangerous here.)
|
steve
|
|
response 186 of 203:
|
Oct 13 18:58 UTC 1997 |
No Ken, stay here. That kind of suggestion is always helpful. Very helpful.
|
valerie
|
|
response 187 of 203:
|
Oct 14 16:17 UTC 1997 |
This response has been erased.
|
scg
|
|
response 188 of 203:
|
Oct 17 05:52 UTC 1997 |
It just says "Error: call failed". No cause code. The Ascends give cause
codes for a lot of things, but for a lot of things they just have status
indicators, and X or . is the indicator that something isn't working.
Maybe it's sending more out via syslog. I'll get it logging somewhere.
|
krj
|
|
response 189 of 203:
|
Oct 17 18:32 UTC 1997 |
Steve: to get the cause code or other ISDN diagnostics, go into Term Serv,
then use the command: show isdn
|
valerie
|
|
response 190 of 203:
|
Oct 18 05:07 UTC 1997 |
This response has been erased.
|
krj
|
|
response 191 of 203:
|
Oct 18 17:27 UTC 1997 |
No, but I'm certainly willing to pitch in on the ISDN installation,
since I've installed about a dozen P50s and a hundred other ISDN
connections. Let's set up a work session when we can have
Grex people with consoles at both ends of the connection.
|
krj
|
|
response 192 of 203:
|
Oct 18 17:45 UTC 1997 |
Rattling off a few other things about ISDN: The "cause codes"
I'm referring to above are the standard codes which the telco
switch is to return to the device on every call termination or
failure. Most of them are decoded in the router manuals.
If the P50 is not getting a cause code back, that usually goes in
tandem with an error message "TEI not assigned;" TEI not assigned
means that either there is a physical discontinuity between the router
and the switch, or else the telco forgot to build the phone number into
the switch. But scg said the P50 had an indicator reporting that
the physical link to the switch was OK.
How did we specify the ISDN line installation on the order?
Did we specify "Intel Blue"? I think that's what the manual says to
order. Also, did we order the switch type to be "National ISDN", and
is that what the switch type is set to in the router?
"National ISDN-1" or "NI-1" is a "virtual" switch type; so the user
isn't supposed to have to worry about if the equipment is connected
to an AT&T 5ESS switch or a DMS-100, or whatever else might be out there.
How are our lines orders, and our equipment set, with regards to
Circuit Switched Data and Circuit Switched Voice? (Any problems here
should be revealed with the cause codes.)
|
jared
|
|
response 193 of 203:
|
Oct 19 02:36 UTC 1997 |
Folks, ameritech fixed the line.
It appears to be up and running just fine
|
krj
|
|
response 194 of 203:
|
Oct 19 04:13 UTC 1997 |
Hah, all my responses were unnecessary; all we had to do was fix
a typo in the phone number.
|
senna
|
|
response 195 of 203:
|
Oct 19 05:42 UTC 1997 |
What you need is someone who is technically sound, like Ken, and has no life,
like me. That would be lethally effective at solving grex's problems.
|
scott
|
|
response 196 of 203:
|
Oct 19 14:03 UTC 1997 |
Yeah, unfortuneately all our gurus have lives these days.
|
valerie
|
|
response 197 of 203:
|
Oct 19 16:48 UTC 1997 |
This response has been erased.
|
orinoco
|
|
response 198 of 203:
|
Oct 19 20:14 UTC 1997 |
woohoo!
I may just have to start telnetting in again...
|
remmers
|
|
response 199 of 203:
|
Oct 19 23:47 UTC 1997 |
The speed is very refreshing indeed.
|