PRI packets - is there handshaking like this? 1

[jomaha]

If anyone is familiar with PRI packets and can steer me in the right direction please help. I have a 100D that I have yet to have up. At one point I had outgoing calls going through (after a long delay when dialing - but one would expect this is another issue).

Is this endless chatter normal for a 5ess switchtype? These messages get transmitted back and forth about every second - when the circuit is idle. It looks like both * and the merlin are calling for SABME and neither one is
listening...

The network end of this circuit is on a linux PC running asterisk (this produced the following ouput). The circuit is b8zs,esf and both ends are configured as 5ess (although I've also tried the other mutually availible switchtype dms-100)

John

> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended

> [ 02 01 7f ]

> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended

> [ 02 01 7f ]

> Unnumbered frame:
> SAPI: 00 C/R: 1 EA: 0
> TEI: 000 EA: 1
> M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
> 0 bytes of data

< [ 00 0b 7f ]

< Unnumbered frame:
< SAPI: 00 C/R: 0 EA: 0
< TEI: 005 EA: 1
< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]
< 0 bytes of data
Sending Set Asynchronous Balanced Mode Extended

 

[merlinman]

John,

What cards are in your switch?

What is the version of the 100D? 517___WHAT???

Do you have any 016 Modules of any type?

 

[jomaha]

100d-U 517M15
Hardware Vintage: 0A
Firmware Vintage: 91
Application Vintage: 18

Other card count (and plugged in in this order):
Processor
the 100d
1 - 408 GS/LD-MLX
4 - 008
3 - 012

 

[jgideon]

There is a known problem with PRI's in the first slot after the processor. Some releases don't like having the first trunk be a PRI trunk. Have you tried moving it later in the carrier?

 

[ttech]

I had A problem with the PRI in the first slot years ago. Have the Dial Tone Provider BUSY-OUT the first channel at their end until you can move the boards around and it will keep your system working.

 

[merlinman]

THere is also a kown problem with the M15 IF you have any 016 type modules AND are using COMMON CHANNEL SIGNALLING as with PRI.

It should work ok without the 016 cards though.

I would move it to slot 4 and start over with my line assignments.

 

[jomaha]

Looks like you guys are steering me in the right direction... Just started reconfiguring the whole system - but just supervisory frames in pri output now. I'll do a writeup on how to get legend running with asterisk when I'm done.

John

 

[tdaugirdas]

It might be one of the other T1 modules. I suspect that at least one of them is the following board:

100d-U 517M15
Hardware Vintage: 0A
Firmware Vintage: 91
Application Vintage: 18

This is the board with known interaction problems if any 016 boards are in the system when configured as PRI.


Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[merlinman]

I learned the hard way one day that the 517M15, with a mix of 016's and used with any common channel (AS IN PRI) will fail big time.

An easy fix is to use a 517E15.