It seems I have a classic legend problem, as described below. Does anyone know the cause of this? My config is 5ess, esf, b8zs. Additionally, each of the b-channels except 23 come up as described. When the T is idling, supervisory frames transfer back and forth every few seconds. When I try to send a call to the legend, asterisk complains that it can't find a d-channel, the call fails and the PRI is reset.
John
The following is pasted from:
Everything in programming looks good , but still can’t call in or out. Provider may report
That they cannot see the ‘D’ channel.
*Verify with the vendor that the “Switch Type” is correct, and that the appropriate protocol is being used. The protocol for the DMS-100 and other Nortel switches is NTNAPRI. The protocol for 5ESS and other AT&T switches is AT&T Custom. Also for DMS 100 switches the L1 flag in the ‘Trunk Sub-group’ table is to be set for ‘Yes’.
After a reset of the 100DS1 card a cold start of the switch or a brief disconnection of cabling for loop back testing, the T1 appears to come back up but calls cannot be made in or out.
*When a PRI connection is lost (for whatever reason) the T1 will normally reset itself and rebuild the connection to the Magix. To do this, the “D” channel is established first and then the “B” channels are brought up either one at a time , or globally(all at once). This is particularly significant because the success of the restart is entirely switch dependent. If the Switch is a DMS-100, DMS-250, or DEX600E, it expects Nortel protocol. Whenever the switch is reset, this protocol specifies that the first Layer-3 “D” channel message must be a global RESTART message (bringing the “B” channels up all together) sent from the network switch to the Magix. If the switch is a 4ESS or 5ESS, it expects AT&T protocol. Whenever the switch is reset, the first Layer-3 “D” channel message sent from the Network switch to the Magix must be a “ B” channel SERVICE message (bringing the ‘B” channels up one at a time)
John
The following is pasted from:
Everything in programming looks good , but still can’t call in or out. Provider may report
That they cannot see the ‘D’ channel.
*Verify with the vendor that the “Switch Type” is correct, and that the appropriate protocol is being used. The protocol for the DMS-100 and other Nortel switches is NTNAPRI. The protocol for 5ESS and other AT&T switches is AT&T Custom. Also for DMS 100 switches the L1 flag in the ‘Trunk Sub-group’ table is to be set for ‘Yes’.
After a reset of the 100DS1 card a cold start of the switch or a brief disconnection of cabling for loop back testing, the T1 appears to come back up but calls cannot be made in or out.
*When a PRI connection is lost (for whatever reason) the T1 will normally reset itself and rebuild the connection to the Magix. To do this, the “D” channel is established first and then the “B” channels are brought up either one at a time , or globally(all at once). This is particularly significant because the success of the restart is entirely switch dependent. If the Switch is a DMS-100, DMS-250, or DEX600E, it expects Nortel protocol. Whenever the switch is reset, this protocol specifies that the first Layer-3 “D” channel message must be a global RESTART message (bringing the “B” channels up all together) sent from the network switch to the Magix. If the switch is a 4ESS or 5ESS, it expects AT&T protocol. Whenever the switch is reset, the first Layer-3 “D” channel message sent from the Network switch to the Magix must be a “ B” channel SERVICE message (bringing the ‘B” channels up one at a time)
