Using monitor on a So8

[moslin]

Had a problem with a video conference unit that uses a so8 module. When I was trying to do some troubleshooting I could not find a way of tracing what the so8 unit was doing, is there an option in monitor to show this?

Rafael Moslin

PS. Fixed the problem by the time old method of a reboot but not very elegant as a fix reason!

 

[Escorthosis]

I used the monitor yesterday to investigate a problem with a customers Faxserver attached to a S0-8.
Use the tab 'ISDN' in monitor and tick all the layer 1,2,3 boxes.

 

[moslin]

Thank you for your reply but looking at the Sysmon manual it only reports on PRI/BRI interfaces however I'm ready to stand corrected!

 

[IPGuru]

The So8 is BRI device (bri-S as apposed to BRI-T)
I am reasonably sure that I have used monitor to diagnose problems on an So Module at least once.

give it a try & come back if it does not work

 

[moslin]

To be honest, If I had been asked the same question by someone else I would have replied that Monitor should do that with the ISDN filters turned on, what is more surprising is that this is the first time this requirement has arisen in 5+ years of installing and maintaining IPO's. You can certainly do a trace on the BRI breakout on an Index.

Gone through the saved logs again which had all of the ISDN tabs tags checked but there is nothing in the trace that relates to the So8 module at all. The information that is provided is purely for the PRI connection to the box.

As an example here is a section of a logging session, all information refers just to the PRI trunk:

99642mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 01 ....
99642mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 01 ....
99642mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 01 ....
99643mS ISDNL1Tx: v=5 peb=5
0000 02 01 01 01 ....
106627mS ISDNL1Rx: v=5 peb=5
0000 02 01 00 00 08 02 00 01 05 a1 04 02 88 90 18 03 ................
0010 a9 83 81 6c 0c 21 81 31 37 36 XX XX XX XX XX XX ...l.!.176xxxxxx
0020 35 70 07 81 38 36 38 34 33 35 7c 02 88 90 5p..868435|...
106627mS ISDNL2Rx: v=5 peb=5
0000 02 01 00 00 08 02 00 01 05 a1 04 02 88 90 18 03 ................
0010 a9 83 81 6c 0c 21 81 31 37 36 XX XX XX XX XX XX ...l.!.176xxxxxx
0020 35 70 07 81 38 36 38 34 33 35 7c 02 88 90 5p..868435|...
106627mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0001(Remote)
Message Type = Setup
InformationElement = Sending Complete
InformationElement = BearerCapability
0000 04 02 88 90 ....
InformationElement = CHI
0000 18 03 a9 83 81 .....
InformationElement = CallingPartyNumber
0000 6c 0c 21 81 31 37 36 37 XX XX XX XX XX XX l.!.176xxxxxx
InformationElement = CalledPartyNumber
0000 70 07 81 38 36 38 34 33 35 p..868435
InformationElement = LowerLayerCompat
0000 7c 02 88 90 |...
106628mS ISDNL3Evt: v=5 stacknum=5 State, new=Present, old=NullState id=1
106628mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 02 ....
106629mS ISDNL1Tx: v=5 peb=5
0000 02 01 01 02 ....
106630mS PRN: National Number in prefix 0

Maybe this is a question I'll need to pose to Avaya directly?