D and B channels will not stay up on PRI

[adminman3]

We have wrestled this one for two months and through two vendor meets. We can't get the PRI to come up and stay up.

G350 with S8300 LSP. CM52. PRI locally provisioned as B8ZS/ESF, and protocol 'b'.

During the V-meet, we changed protocol versions on both ends, we swapped the DS1 module, we verified the clocking on the gateway to synch with the DS1, ...all to no avail. As soon as we pass the PRI to the Gateway, the D-channel will be in-service for about 3 minutes, then down it goes.

Has anyone seen this before? Can this Gateway be messed up?

 

[AvayaTier3]

mm710a or mm710b and what firmware is on the board and what firmware is on your g350?

 GW      TN Circuit Pack                       Latest     Last          CM
MM/TN    Gateway / Media Module     Hardware   Firmware   Update Date   Software
-----    -------------------------  ---------  --------   -----------   --------
G350   - Gateway                               30.17.3  - 02/28/11      5.2.1
MM710  - T1/E1 ISDN PRI MM710 T1/E1  04 >      FW021    - 10/06/08
MM710B - T1/E1 ISDN PRI MM710 T1/E1  11 >      FW049    - 12/06/10

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[adminman3]

Board is MM710BP HW11 / FW47.
GAteway is FW 28.17.0 and HW is 3

 

[AvayaTier3]

You should use the suggested FW upgrades before replacing the gateway.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting

http://bshtele.com

 

[Mugsiensedgwick]

To eliminate the possibility of trouble on the PRI, you can put in a loopback facing the central office and have the provider run from the CO to the loopback. Probably not the issue but at least you can eliminate that as a problem. Make sure they send bit errors to themselves and see them coming back. There should be no errors and no slips except for the ones they generate to verify they are looking at the correct loopback plug.
Good luck.

 

[adminman3]

thanks to both of you. WE will work on the FW and the loop!

 

[telm59]

I see you have 2 ds1 boards. Are you using nfas? If not it sounds like telco is.

 

[adminman3]

The question of facility signaling came up and was verified during the vendor meet, but then, we can't see the translations that the carrier sees so that we can verify.

Keep the good thoughts coming!