That's all - need to know if TA908e/924e supports NFAS
No. One D-channel per PRI. There are only two PRIs supported anyway, so with NFAS you'd only gain one talk path if it did. If NFAS were supported and you configured a primary and backup D-channel you would still have 46 voice paths so there would be no advantage.
What if I have a situation where a customer requests NFAS using only a single D-Channel?
ehuffman wrote:
What if I have a situation where a customer requests NFAS using only a single D-Channel?
Tell your customer that the TA-900e doesn't support it.
NFAS makes very little sense for a device that only supports only two PRIs delivered over individual T-1 interfaces. If it did support it and the PRI with the D-channel were to fail, it would render the other PRI unusable. Point this out to your customer as a valid reason not to use NFAS here. Using NFAS in this scenario would hurt reliability.
NFAS is really only useful in much larger deployments such as a T-3 interface with 672 channels spread over 28 T-1s. Here one would typically have two D-channels, one primary and one backup, and could gain 26 B-channel talk paths by doing so. As the TA900e only supports a maximum of two PRIs, and they're on separate physical interfaces, it doesn't scale.
Got it Jayh - thanks for the explanation.
Sent from my mobile