NFAS Call handling problemWe used to carry nfas until I got tired of intermitent busy signals. My belief at the time was the telco didn't know what they were doing. I had read up on everything regarding the total control and nfas. It's been a while so excuse some of my ignorance. As far as the device id's....those are dictated by the telco supply the nfas group. Your settings MUST match what they have setup. (not necessarily what some service rep tells you, but how it is actually configured/setup at the telco's switch) As far as the busy signals go...my first thought is regarding the number of ports setup of each of the spans if you do a list chassis. If I remember correctly the primary and backup span should be listed as 23 ports and the rest of the pri should be setup as 24 ports b/c of the nfas. Todd ----- Original Message ----- From: Adam Barnhill To: usr-tc@mailman.xmission.com Sent: Tuesday, May 18, 2004 4:48 PM Subject: [USR-TC] NFAS Call handling problem Hi guys, I'm setting up a new location using an NFAS PRI configuration. The hardware consists of Multispans with an ARC II and NMC333. The code being run is TCS 4.5, specifically 3.5.109 Mdsp, 5.3.110 arc2, 8.7.3 nmc NFAS is setup as follows: Group 0 DeviceIDs 0-6 for a total of 7 spans. DeviceID 0 and 1 are my primary and secondary D Channels. Trunk Settings are B8ZS/ESF with a switch type of NI2. The D channels look good and everything appears normal, but the problem I am having is that calls made to the TC get dead air. From TCS I see the DNIS information and that a call is coming in, but the call never completes. A Q.931 trace is below for those that might find that helpful. Please note that by changing the config to fas PRI on both sides, the modems will take calls. It's only when in NFAS mode. The softswitch in case anybody cares is made by Metaswitch. I appreciate any and all responses, thank you. Does anybody have a working NFAS setup in the US? L1 : Physical : Span 0 : Network -> User L2 : Data Link : SAPI 0 : TEI 0 : C/R 1 : Frame I : Ns 11 : Nr 20 : P/F 0 L3 : Call Ref : 1280 Message : SETUP IE Name : Bearer capability Octet 3 : Capability - CCITT coding, Speech Octet 4 : Mode/rate - Circuit mode, 64 kbps Octet 5 : Layer 1 - G.711 u-law IE Name : Channel identification Octet 3 : Interface - Explicitly identified, primary rate : Selection - Preferred, B-channel, as follows Octet 3.1 : Identifier - 6 Octet 3.2 : Channels - CCITT coding, channel number, B-channel units Octet 3.3 : Number(s) - 24 IE Name : Progress indicator Octet 3 : Location - CCITT coding, remote public network (RLN) Octet 4 : Progress - Origination address is non ISDN IE Name : Calling party number Octet 3 : Type - National number : Plan - ISDN/telephony numbering plan (E.164) Octet 3a : Screening - Presentation restricted, network provided IE Name : Calling party number Octet 3 : Type - Unknown : Plan - Unknown Octet 3a : Screening - Number not available due to interworking, network provided IE Name : Called party number Octet 3 : Type - Subscriber number : Plan - ISDN/telephony numbering plan (E.164) Octet 4+ : Number - 7122900 Time 13:31:43.105 TX0: 02 01 01 18 : Total 4 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 1 : Frame RR : Nr 12 : P/F 0 Time 13:31:43.107 TX0: 00 01 28 18 08 02 85 00 02 18 04 E9 86 83 98 : Total 15 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame I : Ns 20 : Nr 12 : P/F 0 L3 : Call Ref : 1280 Message : CALL PROCEEDING IE Name : Channel identification Octet 3 : Interface - Explicitly identified, primary rate : Selection - Exclusive, B-channel, as follows Octet 3.1 : Identifier - 6 Octet 3.2 : Channels - CCITT coding, channel number, B-channel units Octet 3.3 : Number(s) - 24 Time 13:31:43.108 TX0: 00 01 2A 18 08 02 85 00 07 : Total 9 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame I : Ns 21 : Nr 12 : P/F 0 L3 : Call Ref : 1280 Message : CONNECT Time 13:31:43.109 TX0: 00 01 2C 18 08 02 85 00 45 08 02 80 90 : Total 13 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame I : Ns 22 : Nr 12 : P/F 0 L3 : Call Ref : 1280 Message : DISCONNECT IE Name : Cause code Octet 3 : Location - CCITT coding, user (U) Octet 4 : Cause 16 - Normal call clearing Time 13:31:43.110 RX0: 00 01 01 2A : Total 4 L1 : Physical : Span 0 : Network -> User L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame RR : Nr 21 : P/F 0 Time 13:31:43.111 RX0: 00 01 01 2C : Total 4 L1 : Physical : Span 0 : Network -> User L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame RR : Nr 22 : P/F 0 Time 13:31:43.112 RX0: 00 01 01 2E : Total 4 L1 : Physical : Span 0 : Network -> User L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame RR : Nr 23 : P/F 0 Time 13:31:43.118 RX0: 02 01 18 2E 08 02 05 00 4D : Total 9 L1 : Physical : Span 0 : Network -> User L2 : Data Link : SAPI 0 : TEI 0 : C/R 1 : Frame I : Ns 12 : Nr 23 : P/F 0 L3 : Call Ref : 1280 Message : RELEASE Time 13:31:43.118 TX0: 02 01 01 1A : Total 4 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 1 : Frame RR : Nr 13 : P/F 0 Time 13:31:43.118 TX0: 00 01 2E 1A 08 02 85 00 5A : Total 9 L1 : Physical : Span 0 : User -> Network L2 : Data Link : SAPI 0 : TEI 0 : C/R 0 : Frame I : Ns 23 : Nr 13 : P/F 0 L3 : Call Ref : 1280 Message : RELEASE COMPLETE -- Adam Barnhill Support Engineer, TotallyFabricated.com Information Technology Engineer, Poplar Bluff Internet, Inc. / Semo.net P.O. Box 190 | Poplar Bluff, MO 63902 | 573.686.9114, <http://www.semo.net/> Home of TotallyFabricated.com the creators of Total Scrutinizer ------------------------------------------------------------------------------ _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc