set isdn-switch ni-2
set line0 isdn
set line1 isdn
save all
I plugged the cable into the PRI wall jack and the portmaster seemed
happy. However the GTE guy in the CO said that the circuit was in
loopback. I did a "show line0" and "show line1" and did not see any
reference to loopback. I then tried
set line0 loopback off
set line1 loopback off
with no success. I ended up rebooting the PM-3 which brought
everything up properly and the GTE guy said that the circuit was no
longer in loopback.
I then tried
set line0 loopback on
set line0 loopback off
and he said that he didn't see any change in the circuit.
Rebooting the PM-3 clearly corrected the problem but I have two
questions.
How can I turn off loopback without rebooting the PM-3?
What does the "set loopback" command really do?
Issue #2
----------
I had 7 users online when I moved the cable from the channelized T1
wall jack to the the PRI wall jack. In the detail file, the
Acct-Termination-Cause for these users was User-Request. This is
clearly wrong. I would have expected Lost-Carrier, Lost-Service, or
Lost-Cable.
In the past when a customer says that they've been cut off and I see
the termination cause was User-Request, I figured that Windows95 did
something behind their back or the user made a mistake. Now I'm not
so sure.
Has anyone else noticed termination causes being incorrectly
classified as User-Request?
_____ ___ ___ ___
(_ _)( )( \/ ) Tim Moloney Think of something
) ( ) ( ) ( moloney@netsrq.com witty and imagine it
(___) (___)(__)\/(__) Sarasota, Florida was written here.
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>