Filter
Top Products
P-202H Plus v2 Support Notes
Cannot callback to a Dial-in User
The P-202H Plus v2 only supports Microsoft's proprietary CallBack Control
Protocol (CBCP). Thus, the P-202H Plus v2 will be able to do PPP callback to
only to those devices that also support CBCP. This means that if a dial-in user is
using a different package such as Trumpet which doesn't support CBCP, then
the P-202H Plus v2 will not callback to the user.
3. IP Routing
Related SMT screens and CI commands:
- SMT Menu 2
- ip route stat /* display ip route table and statistic counters */
- ip route errcnt disp /* display ip route error counters */
- ip route errcnt clear /* clear ip route error counters */
- sys filter disp /* display filter statistic counters */
- sys filter clear /* clear filter statistic counters */
IP Routing problem causes
An IP packet for the LAN destination should be routed to the LAN interface
( enif0 in P-202H Plus v2 ), and IP packet for a remote node destination should
be sent to the WAN interface if the connection is up, or else the packet will trigger
an outcall to that remote node ( if the remote node is not set for 'incoming' only in
Call Direction. ) If a packet cannot be routed or cannot trigger a call to remote
node, the reason may be due to:
• routing table problem
• the packet has been filtered
• cannot trigger the outcall or the outcall failed due to the reason stated in
previous chapter ( Incoming only remote node, Black List, Call Budget, or
PPP negotiation failed. )
Steps to verify IP routing problem
(1) check if there is any routing error ('ip route errcnt disp').
(2) check if the counter of the specified route increased ('ip route status').
(3) check if any filter counter increased ('sys filter disp').
(4) check if there is any LAN or WAN problem ( refer to sessions: LAN or WAN
connection)
All contents copyright © 2006 ZyXEL Communications Corporation.
401