Compression control protocol (ccp) – ZyXEL Communications omni.net Plus User Manual
Page 83

Technical Reference for ZyXEL omni.net series
7-3
in hashed form by CHAP. Sometimes CHAP can not be supported by the ISP. You may set
[
S87.2=1
] to use PAP only. If you do not want to do authentication at all, set [
S118.3=1
] to
disable the conversion.
CHAP is described in RFC1994 and PAP is described in RFC1334. The only hash method
supported by CHAP is MD5; MS-CHAP is not supported yet. Presently, authentication conversion
works for clients only.
NOTE: Disabling authentication may cause problems in Windows
95.
Authentication AT Commands
Description
ATS118.3 = 0
Enable authentication conversion.
Depends on [
S87.2
] (default).
ATS118.3 = 1
Disable authentication conversion.
ATS87.2 = 0
Accept CHAP/PAP/None (default).
ATS87.2 = 1
Accept PAP/None only.
Table 36. Authentication AT Commands
Compression Control Protocol (CCP)
The ISDN channel can be utilized more effectively when using compression. Compression Control
Protocol (CCP) is used by PPP to negotiate compression methods between peers.
CCP starts after the PPP reaches the network phase. Both ends must support the same compression
method to start packet compression. ZyXEL omni.net supports STAC/LZS. Right now STAC/LZS
is only supported with single history check mode 0 (none), 3 (sequence) and 4 (extended). Mode 1
(LCB) and mode 2 (CRC) are not supported due to patent limitations. CCP negotiation is described
in RFC1962. STAC/LZS is described in RFC1974.
The omni.net will monitor the DTE activity. If software compression has been negotiated, the
ISDN TA will automatically disable STAC/LZS compression.