Guest meiotic Report post Posted 03/03/2006 12:20 AM Enabled tracing of D channel using ktTelControl_TraceSelect.txt, tried two calls and got file attached. Please advise what the log is showing. isdn_trace_dtiB1_0303_161626.log Share this post Link to post
Guest Guest Report post Posted 03/03/2006 12:25 AM Another trace isdn_trace_dtiB1_0303_162322.log Share this post Link to post
Guest Guest Report post Posted 03/03/2006 12:36 AM Trace from ISDIAG isdiag_1.log Share this post Link to post
SupportTeam Report post Posted 03/03/2006 12:39 AM The ISDIAG trace shows all is OK, but no calls are arriving on the system. As the two VG traces were made at the same time as when ISDIAG was running they do not hold valid info. Here is a sample of the ISDIAG trace. It all looks pretty much like below: PROTOCOL TYPE : PRI NI2 TRACE START TIME (MM/DD/YYYY) : 3/4/2006, 11:34:40.46 Time Stamp : 3/4/2006, 11:34:41.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:34:41.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:34:51.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:34:51.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:1.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:1.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:11.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:11.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:21.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:21.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:31.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:31.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:41.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:41.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:51.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:35:51.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:36:1.846 RECEIVE Command=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Time Stamp : 3/4/2006, 11:36:1.846 TRANSMIT Response=1 SAPI=0x00 TEI=0x00 0x01 0x2f Receive Ready Share this post Link to post
Guest Guest Report post Posted 03/07/2006 06:13 AM Here is a trace from ISDIAG now showing an incoming call arriving on system. ISDIAG is unable to obtain ANI from the SETUP message, reporting that "message is either too big or too small" tr1.txt Share this post Link to post
Guest Guest Report post Posted 03/07/2006 06:18 AM And another trace tr2.txt Share this post Link to post
SupportTeam Report post Posted 03/07/2006 06:43 AM This NI2 line (and some other T1 ISDN lines) used slot 24 as an additional signaling slot. As such VoiceGuide needed to be configured to only open the first 23 channels. When only the first 23 channels were opened the calls arrived and were answered by VoiceGuide with no problems. VoiceGudie also extracted both the CallerID and DNIS (number dialed by caller) with no problems. ie. All is OK. If the 24th channel was opened as well the signaling line would not work and callers would be played an 'all circuits are busy' message by the telco. Share this post Link to post
