Also, does someone know other such command that are unknown for the
majority of us?
Thank you all!
D. Germain
PS: I've been on this list for a little while now, and would like to say
"congratulation" to MZ. You seems to be very useful on this list but
sometimes our destiny is somewhere else.
At 22:43 20-01-98 -0700, you wrote:
>This is what I got back... looks normal...?
>
>pm9> dsct inband 0
> 1 2
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
>------------------------------------------------------
> A 0 0 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 0 0 0
> B 0 0 1 1 1 1 1 1 1 1 0 1 1 1 1 1 0 1 1 1 0 0 0 0
>FSM 1 1 4 4 4 4 4 4 4 4 1 4 4 4 4 4 1 4 4 4 1 1 1 1
>pm9> dsct inband 1
> 1 2
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
>------------------------------------------------------
> A 0 1 1 1 1 1 1 0 0 1 0 0 0 1 0 1 1 0 1 0 0 1 1 1
> B 0 1 1 1 1 1 1 0 0 1 0 0 0 1 0 1 1 0 1 0 0 1 1 1
>FSM 1 4 4 4 4 4 4 1 1 4 1 1 1 4 1 4 4 1 4 1 1 4 4 4
>
>
>The problem should be on 11 on line 1 and it shows good... right?
>
>Thanks,
>Allan
>
>Shawn wrote:
>>
>> I had this once.... Do a
>>
>> dsct inband 0
>>
>> and
>>
>> dsct inband 1
>>
>> In my case -
>>
>> pm3-saco-1> dsct inband 0
>> 1 2
>> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
>> ------------------------------------------------------
>> A 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>> B 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>> FSM 4 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
>> pm3-saco-1>
>>
>> Line "0" is in use, and the rest are idle... When I had my problem I saw
>> that the A & B were set to 1 and so was FSM... It turned out that one of
>> the DS0s were busied out - and the other was skipped.
>>
>> Let me know if this helps.
>>
>> At 12:26 AM 1/20/98 -0700, you wrote:
>> >I've got one port S34 one one of my PM3s that is not receiving calls.
>> >
>> >S34 64000 on Login/ IDLE 0 0
>> 0
>> >
>> >The hunt group goes completely full and this line doesn't get any use...
>> >
>> >These are running over channelized T1s. I have swapped line0 and line1
>> and the
>> >problem stays at port S34.
>> >
>> >Any Ideas?
>> >
>> >COMOS 3.7.2
>> >
>> >Thanks in advance,
>> >Allan
>> >-
>> >To unsubscribe, email 'majordomo@livingston.com' with
>> >'unsubscribe portmaster-users' in the body of the message.
>> >
>> >
>-
>To unsubscribe, email 'majordomo@livingston.com' with
>'unsubscribe portmaster-users' in the body of the message.
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.