| Title: | Digital Brouters Conference |
| Notice: | New common-code brouter family: RouteAbout, DECswitch 900 |
| Moderator: | MARVIN::HART LL |
| 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 |
Hi,
a custommer of us has some problems, connecting his departments by using
some RouteAboute Access EI. He is using PPP over ISDN-dial-up Lines (EDSS1)
at the built-in ISDN-interface of the RA.
The Router-Software is:
"RtAbt Acces EI/MP, Brouter: 1 Enet 1T1 1BRI,HW=1,RO=1,#1222,SW=V2.0-3"
It's no problem to dial in to that system, but it's not possible to dial out.
Has anybody ever seen this Cause-Codes?
GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
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
GW.026: Mnt nt 0 int Eth/0
GW.043: CML state CML_CONNECTING, event CML_XMT nt 3 int PPP/1
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x64) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x57) NLS Cause Indication on nt 2 in
t ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Init ev DiscInd -> Idle nt 2 int ISDN/0
Thank's for any hints
Johann
Here is the config:
===============================================================================
Config>list isdn
Address assigned name Network Address Network Subaddress
--------------------- --------------- ------------------
dec2 08990468210
dec2-in 8990468210
Config>net 3
Circuit configuration
Circuit Config>list all
Base net: 2
Destination name: dec2
Inbound dst name: dec2-in
Outbound calls allowed
Inbound calls allowed
Idle timer = 30 sec
SelfTest Delay Timer = 150 ms
Send/Rcv Line ID: NONE
Circuit Config>
Circuit Config>exit
Config>net 2
ISDN user configuration
ISDN Config>list all
ISDN Configuration
Local Network Address Name = hbf3
Local Network Address = 24278733
Local Network Subaddress =
Maximum frame size in bytes = 2048
Outbound call address Timeout = 180 Retries = 2
Switch Variant = ETSI NET3
DN0 (Directory Number 0) = 24278733
DN1 (Directory Number 1) =
TEI = Automatic
PS1 detect = Enabled
No circuit address accounting information being kept
ISDN Config>
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 898.1 | MARVIN::CLEVELAND | Wed May 14 1997 08:11 | 10 | ||
0x64 is "Invalid IE contents" !
0x57 is not in my list of cause codes.
My only guess would be that perhaps the local address setting is
incorrect, and the switch is noticing (it is used as the Calling Party
Address in the outgoing SETUP message). Any chance they could try
V2.0.2? I did make a change in this area for V2.0.3 and possibly they
are running into an unintended side effect.
Tim
| |||||
| 898.2 | Invalid IE contens ??? | MUNICH::WIESHEU | Thu May 15 1997 03:54 | 18 | |
Hi,
the local address setting is OK (I could dial in to this RA with the
ISDN-Address it has stored as local address).
I already asked the customer to downgrade to 2.0-2.
Could You please explain to me, what "Invalid IE contents" means?
By the way, I found some new behaveour in the 2.0-3 SW.
eg.
During setting up a virgin RA (SW < 2.0-3), I was used that the
DN0-address has been automatically set when inserting the "Local
Network Address Name"
Thanks for Your help
Johann
| |||||
| 898.3 | MARVIN::CLEVELAND | Thu May 15 1997 05:34 | 22 | ||
> Could You please explain to me, what "Invalid IE contents" means?
The switch didn't like something in a packet we sent it. (IE =
Information Element). Not good, we should only send valid IEs ;-(
> By the way, I found some new behaveour in the 2.0-3 SW.
> eg.
> During setting up a virgin RA (SW < 2.0-3), I was used that the
> DN0-address has been automatically set when inserting the "Local
> Network Address Name"
Yes, in 2.0.3, we disabled that. There is no need to set DN0 anymore
unless you need to share the S-BUS with other ISDN equipment. This
eliminates the most common setup problem by far (incorrect setting of
DN0 caused calls not to be answered).
If you want to set it, first confirm the actual DN0 from the switch by
looking at ELS message ISDN.041 when a call arrives.
Tim
| |||||
| 898.4 | MUNICH::WIESHEU | Thu May 15 1997 08:25 | 5 | ||
Nice to see what's going on,
Thanks
Johann
| |||||