USER’S GUIDE462 CyberSWITCHe. If syslogd is running but does not receive any log messages, make sure CDR is configuredfor the UDP port that syslogd is using. The typical port is 514, but some versions of syslogdmay use a different port.f. Check that the priority value that you assigned in the CFGEDIT Call Detail Recordingmenu (default of 38) matches the priority setting on your syslog server (default ofauth.info).C OMPRESSION1. To verify compression is operational, make sure compression is enabled on a system-widebasis.2. Cause a call to be established with a device for which per-device compression is enabled.3. To verify that compression is in effect with the device, issue thecmp stats console command while the connection is in place. If compression is in effect, this commandwill display the current compression counters and ratios.4. If compression is not in effect, the command will return an indication that the device is a non-compressed connection. If compression is not in effect, try the following:a. Issue thecmp stats console command then issue thedr console command to check themessage report log. A message will inform you if the compression failed due to memoryconstraints.b. Verify that the CyberSWITCH has compression enabled. This is done through selecting“Compression Options” from CFGEDIT’s Systems Options menu.c. Verify that the device to which the connection is being established has compressionenabled. If the device is another CyberSWITCH, refer to the previous step for instructions.d. Use the trace console command to examine the CCP frames exchanged with the device.This is typically accomplished by issuing thetrace ppp on command, erasing the logcontents, establishing the call, and then examining the log again (by issuing thedr consolecommand) to view the frame trace.The following traces illustrate some common PPP start-up scenarios when compression isenabled. Only the CCP frames are excerpted for clarity.• Successful NegotiationAs a reference, the following trace illustrates a successful negotiation of CCP using the Staccompression protocol. The key feature of this sequence is that each side receives aCONFIG-ACK to its respective CONFIG-REQ.