[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

790.0. "RouteAbout90EI, Cisco2503, ISDN, 2 TE's on same NT1" by IAMOSI::LEUNG () Sun Mar 09 1997 22:44

		NT1 -------+--------+
			  TE1      TE1
			  90EI	   Cisco

The ISDN line has been newly installed and each TE1 has been assigned a
different phone no using only one B channel each.
The phone nos. are xxxxxxxx30 and xxxxxxxx31.


                           Cisco 16.172.64.116
                      --------+--------------------
                              | 192.168.1.1
                              \
                              /
                              | 192.168.1.3
                      --------+-----------------
                            90EI 16.153.16.1


From the Cisco, ping to the 90EI (16.153.16.1) works fine. ISDN call is made.
But if the 90EI initiates the call (ping to 16.172.64.116), call fails.

ELS output on 90EI when 90EI initiates call :
Copyright 1995-1996 Digital Equipment Corp.

MOS Operator Control

*t 2
ISDN.032: Chn 0 ConnID 0x0 Cll Txcmp on nt 2 int ISDN/0
ISDN.015: Chn 0 FSM st Idle ev ConnReq -> Call_Init nt 2 int ISDN/0
ISDN.003: ConnID 0xE8 Status msg cause (0x3:0xB) Start call alerting on nt 2 int
 ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD
N/0
ISDN.023: ConnID 0x1 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Init ev ConnCnf -> DataXfer nt 2 int ISDN
/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/
0
ISDN.033: Chn 0 ConnID 0x1 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x10) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscInd -> Idle nt 2 int ISDN/0
ISDN.032: Chn 0 ConnID 0x0 Cll Txcmp on nt 2 int ISDN/0
ISDN.015: Chn 0 FSM st Idle ev ConnReq -> Call_Init nt 2 int ISDN/0
ISDN.003: ConnID 0xE8 Status msg cause (0x3:0xB) Start call alerting on nt 2 int
 ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD
N/0
ISDN.023: ConnID 0x1 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Init ev ConnCnf -> DataXfer nt 2 int ISDN
/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/
0
ISDN.033: Chn 0 ConnID 0x1 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x10) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscInd -> Idle nt 2 int ISDN/0

*logout

90EI configuration :
Config>list isdn

Address assigned name             Network Address  Network Subaddress
---------------------             ---------------  ------------------

CISCO                             xxxxxxxx31
ACCESS                            xxxxxxxx30
Config>net 2
ISDN user configuration
ISDN Config>list all

                                   ISDN Configuration

Local Network Address Name    = ACCESS
Local Network Address         = xxxxxxxx30
Local Network Subaddress      =

Maximum frame size in bytes   = 2048
Outbound call address Timeout =  180  Retries =   2
Switch Variant                = Australia TS013.1
DN0 (Directory Number 0)      = xxxxxxxx30
DN1 (Directory Number 1)      =
TEI                           = Automatic
PS1 detect                    = Enabled
Accounting information kept for the following network destinations:

Address assigned name             Network Address  Network Subaddress
---------------------             ---------------  ------------------
ISDN Config>exit
Config>net 3
Circuit configuration
Circuit Config>list all

Base net:       2
Destination name:    CISCO
Inbound dst name:    * ANY *
Outbound calls       allowed
Inbound calls        allowed
Idle timer           = 60 sec
SelfTest Delay Timer = 150 ms
Send Line ID:        NO

Config>p ip
Internet protocol user configuration
IP config>list all
Interface addresses
IP addresses for each interface:
   intf  0   16.153.16.1      255.255.255.0    Network broadcast,    fill 1
   intf  1                                     IP disabled on this interface
   intf  2                                     IP disabled on this interface
   intf  3   192.168.1.3      255.255.255.0    Network broadcast,    fill 1

Routing

route to 0.0.0.0,0.0.0.0 via 192.168.1.1, cost 1



Protocols
BOOTP forwarding: disabled
Directed broadcasts: enabled
ARP Subnet routing: disabled
RFC925 routing: disabled
OSPF: disabled
Per-packet-multipath: disabled
RIP: disabled
EGP: disabled


Partial Cisco config :

interface BRI0
 ip address 192.168.1.1 255.255.255.0
 no ip mroute-cache
 encapsulation ppp
 isdn answer1 xxxxxxxx31
 dialer map ip 192.168.1.3 xxxxxxxx30
 dialer-group 1


Tracing on Cisco :
Router#
BRI: write_sid: scp = 0, wrote = E

BRI: write_sid: scp = 0, wrote = E

BRI: write_sid: scp = 0, wrote = E

BRI: write_sid: scp = 0, wrote = E

ISDN BR0: received HOST_INCOMING_CALL
        Bearer Capability i = 0x080010
        -------------------
        Channel ID i = 0x0101
        Called Party Number i = 0x0401, 'xxxxxx31'
        IE out of order or end of 'private' IEs --
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Calling Party Number i = '!', 0x81, 'xxxxxxx30'
        Called Party Number i = 0xC1, 'xxxxxx31'
ISDN BR0: Event: Received a call from xxxxxxx30 on B1 at 64 Kb/s
ISDN BR0: Event: Accepting the call                     <<< Cisco accepts call
BRI: enable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to up
BRI: write_sid: scp = 0, wrote = E

BRI: write_sid: scp = 0, wrote = E

ISDN BR0: received HOST_DISCONNECT_ACK                  <<< ????
BRI: disable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to down
BRI: write_sid: scp = 0, wrote = E

%ISDN-6-CONNECT: Interface BRI0:1 is now connected to unknown
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: received HOST_INCOMING_CALL
        Bearer Capability i = 0x080010
        -------------------
        Channel ID i = 0x0101
        Called Party Number i = 0x0401, 'xxxxxx31'
        IE out of order or end of 'private' IEs --
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Calling Party Number i = '!', 0x81, 'xxxxxxx30'
        Called Party Number i = 0xC1, 'xxxxxx31'
ISDN BR0: Event: Received a call from xxxxxxx30 on B1 at 64 Kb/s
ISDN BR0: Event: Accepting the call
BRI: enable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to up
BRI: write_sid: scp = 0, wrote = E

BRI: write_sid: scp = 0, wrote = E

ISDN BR0: received HOST_DISCONNECT_ACK
BRI: disable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to down
BRI: write_sid: scp = 0, wrote = E

%ISDN-6-CONNECT: Interface BRI0:1 is now connected to unknown
BRI: write_sid: scp = 0, wrote = E
T.RTitleUserPersonal
Name		DateLines
790.1MARVIN::CLEVELANDMon Mar 10 1997 06:117
    Looks like a PPP problem possibly from the trace?  ISDN appears to be
    quite happy but the upper layer requests a disconnect.  I would enable
    PPP events and see if LCP negotiation is failing.  Do you possibly have
    PAP/CHAP configured for inbound calls on the cisco, but not set up on
    the routeabout?
    
    Tim
790.2IAMOSI::LEUNGMon Mar 10 1997 21:5488
Did PPP packet level tracing on Cisco box and no LCP packet at all. I think that 
it is not even getting to LCP negotiation yet. No PAP/CHAP authentication
configured on both routers.

I did more ISDN tracing when incoming call is received from RouteAbout to Cisco.
It seems that the RouteAbout is rejecting the Connect from the Cisco with an
error "Invalid Call Reference Value". The trace indicates the RouteAbout sends a
Release with that cause code and then the Cisco completes the Release.


Router#
ISDN BR0: TX ->  RRp sapi = 0  tei = 64 nr = 2 
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: RX <-  RRf sapi = 0  tei = 64  nr = 4
ISDN BR0: RX <-  RRp sapi = 0  tei = 65 nr = 14 
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 15
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 14  nr = 15  i = 0x0801810218018
A
    CALL_PROC pd = 8  callref = 0x81
        Channel ID i = 0x8A
ISDN BR0: RX <-  UI sapi = 0  tei = 127 i = 0x08014205040288901801896C0B21813239
393137373833307009C13939313737383331
    SETUP pd = 8  callref = 0x42
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Calling Party Number i = '!', 0x81, 'xxxxxxx30'
        Called Party Number i = 0xC1, 'xxxxxx31'
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 16
ISDN BR0: received HOST_INCOMING_CALL
        Bearer Capability i = 0x080010
        -------------------
        Channel ID i = 0x0101
        Called Party Number i = 0x0401, 'xxxxxx31'
        IE out of order or end of 'private' IEs --
        Bearer Capability i = 0x8890
        Channel ID i = 0x89
        Calling Party Number i = '!', 0x81, 'xxxxxxx30'
        Called Party Number i = 0xC1, 'xxxxxx31'
ISDN BR0: Event: Received a call from xxxxxxx30 on B1 at 64 Kb/s
ISDN BR0: Event: Accepting the call
BRI: enable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to up
ISDN BR0: TX ->  INFOc sapi = 0  tei = 64  ns = 4  nr = 2  i = 0x0801C207
    CONNECT pd = 8  callref = 0xC2
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 17
ISDN BR0: RX <-  RRr sapi = 0  tei = 64  nr = 5
ISDN BR0: RX <-  INFOc sapi = 0  tei = 64  ns = 2  nr = 5  i = 0x0801424D080282D
1
    RELEASE pd = 8  callref = 0x42                           <<<<<<<<<<<<<<<<<
        Cause i = 0x82D1 - Invalid call reference value      <<<<<<<<<<<<<<<<<
ISDN BR0: TX ->  RRr sapi = 0  tei = 64  nr = 3
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: received HOST_DISCONNECT_ACK
BRI: disable channel B1
%LINK-3-UPDOWN: Interface BRI0:1, changed state to down
ISDN BR0: TX ->  INFOc sapi = 0  tei = 64  ns = 5  nr = 3  i = 0x0801C25A
    RELEASE_COMP pd = 8  callref = 0xC2
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: RX <-  RRr sapi = 0  tei = 64  nr = 6
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 15  nr = 17  i = 0x08018101
    ALERTING pd = 8  callref = 0x81
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 16  nr = 17  i = 0x0801420F
    CONNECT_ACK pd = 8  callref = 0x42
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 17  nr = 17  i = 0x08018107
    CONNECT pd = 8  callref = 0x81
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 18
%ISDN-6-CONNECT: Interface BRI0:1 is now connected to unknown 
ISDN BR0: TX ->  RRp sapi = 0  tei = 64 nr = 3 
BRI: write_sid: scp = 0, wrote = E

ISDN BR0: RX <-  RRf sapi = 0  tei = 64  nr = 6
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 19
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 18  nr = 19  i = 0x0801424D
    RELEASE pd = 8  callref = 0x42
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 19  nr = 19  i = 0x0801814508028
090
    DISCONNECT pd = 8  callref = 0x81
        Cause i = 0x8090 - Normal call clearing 
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 20
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 21
ISDN BR0: RX <-  INFOc sapi = 0  tei = 65  ns = 20  nr = 21  i = 0x0801815A
    RELEASE_COMP pd = 8  callref = 0x81
ISDN BR0: RX <-  RRr sapi = 0  tei = 65  nr = 22
790.3MARVIN::CLEVELANDTue Mar 11 1997 06:1034
    
>I did more ISDN tracing when incoming call is received from RouteAbout to Cisco.
>It seems that the RouteAbout is rejecting the Connect from the Cisco with an
>error "Invalid Call Reference Value". The trace indicates the RouteAbout sends a
>Release with that cause code and then the Cisco completes the Release.
    
    I don't see that...your trace shows the cisco receiving a RELEASE from
    the switch, with that cause code.  But that doesn't mean that the
    Routeabout did the same thing.
    
    Your trace gets weirder after that.  Are those events shown actually
    happening at the same time?  I've distilled it down to the interesting
    packets:
    
RX    CALL_PROC pd = 8  callref = 0x81
RX    SETUP pd = 8  callref = 0x42
TX    CONNECT pd = 8  callref = 0xC2
RX    RELEASE pd = 8  callref = 0x42                           <<<<<<<<<<<<<<<<<
TX    RELEASE_COMP pd = 8  callref = 0xC2
RX    ALERTING pd = 8  callref = 0x81
RX    CONNECT_ACK pd = 8  callref = 0x42
RX    CONNECT pd = 8  callref = 0x81
RX    RELEASE pd = 8  callref = 0x42
RX    DISCONNECT pd = 8  callref = 0x81
RX    RELEASE_COMP pd = 8  callref = 0x81
    
    Is the cisco possibly dealing with two calls here?  Perhaps an inbound
    and an outbound at the same time?
    
    Still it appears to me that the RouteAbout is getting connected,
    receives a few packets, then disconnects.  If you enable PPP events
    we may be able to see the reason why.
    
    Tim
790.4IAMOSI::LEUNGTue Mar 11 1997 22:56138
>    Your trace gets weirder after that.  Are those events shown actually
>    happening at the same time?  I've distilled it down to the interesting
>    packets:
Yes, all the events are happening at the same time. Given that both the Cisco
and RouteAbout connect to the same NT1, the traces also show the packets coming
out of the Routeabout.

>    Is the cisco possibly dealing with two calls here?  Perhaps an inbound
>    and an outbound at the same time?
No, the RouteAbout initiaties the call and the Cisco should accept it. The
traces may be confusing given that both routers are on the same bus and the
traces show packets destined for the Routeabout as received by the Cisco.

See below for PPP and ISDN trace on RouteAbout when isdn call is initiated from
RouteAbout to Cisco.

I will try to use to seperate ISDN lines for doing the tests and see if it makes
a difference.


*t 2
  GW.001: Copyright 1995-1996 Digital Equipment Corporation
  GW.002: [not configured], RtAbt Acces EI/MP,  Brouter: 1 Enet 1T1 1BRI,HW=1,RO
=1,
          #7188,SW=V2.0-1 Started
  GW.005: Bffrs: 400 avail 400 idle   fair 103 low 80
ISDN.032: Chn 0 ConnID 0x0 Cll Txcmp on nt 2 int ISDN/0
ISDN.015: Chn 0 FSM st Idle ev ConnReq -> Call_Init nt 2 int ISDN/0
ISDN.003: ConnID 0x20 Status msg cause (0x3:0xB) Start call alerting on nt 2 int
 ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD
N/0
ISDN.023: ConnID 0x1 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Init ev ConnCnf -> DataXfer nt 2 int ISDN
/0
 PPP.014: LCP/Listen fsm_down nt 3 int PPP/1
 PPP.002: Srl prt up, nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_start nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_starting nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_reset nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_reset nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_reset nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x001A80E5
 PPP.016: LCP/Listen snd Configure Request, id 20 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
 PPP.014: LCP/Req Sent fsm_timeout nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x001A80E5
 PPP.016: LCP/Req Sent snd Configure Request, id 21 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
 PPP.014: LCP/Req Sent fsm_timeout nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x001A80E5
 PPP.016: LCP/Req Sent snd Configure Request, id 22 len 14, nt 3 int PPP/1
 PPP.038: mk mag 0x001A80E5
 PPP.016: LCP/Req Sent snd Configure Request, id 22 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
 PPP.014: LCP/Req Sent fsm_timeout nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x001A80E5
 PPP.016: LCP/Req Sent snd Configure Request, id 23 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/
0
ISDN.033: Chn 0 ConnID 0x1 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x10) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscInd -> Idle nt 2 int ISDN/0
ISDN.032: Chn 0 ConnID 0x0 Cll Txcmp on nt 2 int ISDN/0
ISDN.015: Chn 0 FSM st Idle ev ConnReq -> Call_Init nt 2 int ISDN/0
ISDN.003: ConnID 0x94 Status msg cause (0x3:0xB) Start call alerting on nt 2 int
 ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.003: ConnID 0x94 Status msg cause (0x3:0xB) Start call alerting on nt 2 int
 ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD
N/0
ISDN.023: ConnID 0x1 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Init ev ConnCnf -> DataXfer nt 2 int ISDN
/0
 PPP.014: LCP/Req Sent fsm_down nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_reset nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_reset nt 3 int PPP/1
 PPP.002: Srl prt up, nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_start nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_starting nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_reset nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_reset nt 3 int PPP/1
 PPP.014: LCP/Listen fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Listen lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x00352600
 PPP.016: LCP/Listen snd Configure Request, id 24 len 14, nt 3 int PPP/1
 PPP.038: mk mag 0x00352600
 PPP.016: LCP/Listen snd Configure Request, id 24 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
 PPP.014: LCP/Req Sent fsm_timeout nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x00352600
 PPP.016: LCP/Req Sent snd Configure Request, id 25 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
 PPP.014: LCP/Req Sent fsm_timeout nt 3 int PPP/1
 PPP.014: LCP/Req Sent fsm_timer nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makereq nt 3 int PPP/1
 PPP.019: LCP/Req Sent lcp_makeoptions nt 3 int PPP/1
 PPP.035: mk mru 2042
 PPP.038: mk mag 0x00352600
 PPP.016: LCP/Req Sent snd Configure Request, id 26 len 14, nt 3 int PPP/1
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x1 RxD Pkt ln 18 nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x1 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/
0
ISDN.033: Chn 0 ConnID 0x1 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x10) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscInd -> Idle nt 2 int ISDN/0
790.5MARVIN::CLEVELANDWed Mar 12 1997 03:108
    Yes please, try seperate lines to see if that resolves the problems!
    
    The trace shows the RouteAbout sending LCP config requests, but getting
    no response.  It also shows a received packet 'arriving' at the same
    time; this could well be it seeing the packet it transmitted, I guess? 
    But whatever it is, it gets ignored by the RouteAbout.
    
    Tim