> I have the lines currently set as ISCN_NFAS 0 and 1. If I change the > first PRI to just ISDN is shows a D channel where it should but > then loses the lines a few seconds later; the flashing question marks thingy. > As far as I can tell the lines seem to be working okay but it > bothers me that it doesnt "look" the same as our other hunt group spans. Are the PRI supposed to be configured for NFAS (Non Facilities Associated Signalling)? If they are, then you definately need the PRI set up as NFAS on the MAX, if they aren't then you need to switch to the normal ISDN signalling. > Is there a better way to ask the MAX what it thinks it is seeing with the > PRI's? > > |10-100 1234567890 | |10-200 1234567890 | > | L1/LA ****-**-** | | L2/LA *--*------ | > | 12345678901234 | | 12345678901234 | > | *********-*--. | | -------------. | This is probably related to the NFAS issue. If the PRI are NFAS then you need to find out if you have a primary and secondary D channel or just a primary. In any case, on at least one span you should see the last trunk with a character indicating the D channel ("s" for primary and "b" for backup). Your diagram above shows a "." which is bad news. In fact, I'm amazed that you are landing calls on it at all without a D channel. Check your settings on Line Config and see how your 24th channel is configured on each span. Here is how our PRI (from GTE HawTel) look for both FAS and NFAS (with primary and secondary): FAS |10-100 1234567890 | |10-200 1234567890 | | L1/LA ********** | | L2/LA -*-------- | | 12345678901234 | | 12345678901234 | | ***----------s | | -------------s | NFAS |10-100 1234567890 | |10-200 1234567890 | | L1/LA ********** | | L2/LA ********** | | 12345678901234 | | 12345678901234 | | *************s | | ****-********b | After experience with both, I would stick with FAS. If you only have 2 spans and you use a primary and a secondary then you don't gain anything other than complexity (except on the rare chance that you lose your D channel but not the rest of the span). If you decide to live dangerously and go without the backup D channel to actually gain a trunk you lose reliability because if you loose the span with the primary then you lose both spans. Also on 5.0Ap16 with an DMS100 switch when the backup and primary switch roles the MAX drops all calls! So much for enhanced reliability. ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <STRONG>Follow-Ups</STRONG>: <UL> <LI><STRONG><A HREF="msg11401.html">Re: (ASCEND) how is this PRI setup???</A></STRONG></LI> <UL> <LI><EM>From</EM>: Systems Admin <sysadmin@maui.net></LI> </UL> </UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg11401.html">Re: (ASCEND) how is this PRI setup???</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg11384.html">(ASCEND) Proxy-state attribute</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg11397.html">(ASCEND) how is this PRI setup???</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg11401.html">Re: (ASCEND) how is this PRI setup???</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#11399"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd265.html#11399"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>