ZyXEL Communications P-202H Plus v2, Support Notes

Page: 393 / 434

P-202H Plus v2 Support Notes
CHAP send response
CHAP login to remote OK!
IPCP negotiation started
BACP stopped
IPCP up
LCP down
IPCP down
LCP stopped
The call connected, IPCP was up, but still the call dropped. The call could have
been dropped by the far-end for some unknown reason. You need to verify the
problem with your ISP. Sometimes if the far-end is using Ascend Pipeline for
your connection, they will let IPCP up and check the IP address, if IP address is
not the same as what's configured in their 'Connection Profile', they would drop
the call and give no log about it!
- Other unknown reason
For any other unknown reason, you have to look at the packet trace to decide
what went wrong. To collect the trace,
•
Go to Menu 11, and mark down which remote number # is for Internet
access.
•
Go to CI (Menu 24.8)
•
Turn on the screen capture/log capability
•
sys trcl cl ( to clear the trace )
•
sys trcl sw on ( to turn on the trace log )
•
sys trcp sw on ( to turn on the packet trace )
•
dev dial #
•
After the call failed
•
sys trcl disp
Summary:
Failure reasons Actions
Dial failed - check disconnect cause
- go to SMT memu 24.1 to verify that channel status is
not DOWN. If DOWN, it might be ISDN Init failure.
- Do ISDN loopback test
Authentication failed - check name and password
All contents copyright © 2006 ZyXEL Communications Corporation.
393