Abilis CPX tutorial, release 7.

4
Draft Draft

Abilis CPX tutorial, release 7.4

Draft Draft

Table of Contents
What's new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
I. Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1. About Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Abilis CPX structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Abilis hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1. Abilis hardware structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Abilis Base-K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3. Abilis Base-J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4. Abilis VMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5. Compact Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6. Micro Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.2. Number of pluggable usb devices to the same USB 1.1 OHCI/UHCI controller . . . . . . . . . . . . . . . 13
2.6.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7. Nano Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.2. Number of pluggable usb devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.8. MFIDE module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.1. Watchdog Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.2. Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.3. Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9. Abilis PCI boards and extension boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9.1. ESB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.9.2. CTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.9.3. QPRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.9.4. QPRI2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.9.5. PB44X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9.6. PB44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.9.7. BRI-HFC4 / BRI-HFC8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.9.8. BRIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.9.9. POTS 4/8/16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9.10. POTS protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.9.11. VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.9.12. ETH100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.10. USB devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.2. UMTS-BOX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.10.3. GSM Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.10.4. UMTS-Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.5. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.6. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.10.7. RJ Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3. Physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.1. Numbering of the physical ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2. ISDN Basic Rate Interface (BRI) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.2.1. Emergency connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.3. Importance of the impedance matching adapters (ISDN Adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.4. Connecting pots cards to patch panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.5. ADSL modem connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.6. POTS protection connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.7. UMTS-BOX connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.8. Citobox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

iii
Draft Abilis CPX tutorial, release 7.4 Draft

3.8.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

3.9. Simbox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.10. RJS connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.10.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.10.2. Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4. Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1. Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.1. Firmware versioning numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.2. Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.3. Compatibility of drivers.cfg files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5. Command language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.2. Command Line Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.3. Help online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.4. System accessing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.1. LOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.2. LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.3. CLOSE / EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.5. Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.1. D DEV (Display Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.2. A DEV (Add Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.5.3. S DEV (Set Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.5.4. C DEV (Clear Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6. Resources or Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.1. D P (Display Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.2. A RES (Add Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.6.3. S P (Set Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.6.4. C RES (Clear Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.7. Initialization/activation/deactivation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.1. INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.2. D ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.3. S ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.4. D INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.5. S INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.7.6. D RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.7.7. D TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.7.8. ALARM VIEW and ALARM RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.7.9. CALL RES and DISC RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8. General and system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.1. D G (Display General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.2. D I (Display Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.8.3. D VER (Display Versions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.8.4. CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.8.5. Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.8.6. D DESCR (Display Descriptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.8.7. D PSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.9. Users Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
5.9.1. D USER (Display User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.9.2. A USER (Add User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.3. C USER (Clear User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.4. S USER (Set User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10. Address book management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.1. CONTACT EXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.2. CONTACT IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.10.3. CONTACT RELOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11. Lists management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11.1. LIST CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11.2. LIST DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.3. LIST RENAME / LIST DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.4. D LIST (Display List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.5. A LIST (Add List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.11.6. C LIST (Clear List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

iv
Draft Abilis CPX tutorial, release 7.4 Draft

5.11.7. D ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

5.11.8. Type of lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.12. Configuration validating and saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.12.1. VALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.12.2. SAVE CONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.13. System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.1. CONFLOG BACKUP and CONF BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.2. CONFLOG RESTORE / CONF RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.3. FILE COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.4. FILE DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.5. FILE GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.6. FILE PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.13.7. SYS COMPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.8. SYS COMPACTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.9. SYS DELETE PACKAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.10. SYS DELETE VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.11. SYS UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5.13.12. SYS DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.13.13. SYS DISK INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.14. SYS DISK CHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.15. SYS DISK FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.16. SYS DISK LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.17. SYS DISK MBR DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.18. SYS DISK PARTITION INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.19. SYS DISK PARTITION ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.20. SYS DISK PARTITION RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.21. SYS SET BOOT VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.22. SYS DISPLAY BOOT LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.13.23. WARM START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.14. Diagnostics and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.1. Diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.2. Statistics Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5.15. Test functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.1. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.2. Tracert / Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.3. Pingstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.15.4. DSPs test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.16. Trace functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.16.1. Trace act . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.16.2. Trace start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.3. Trace stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.4. Trace get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.17. DEBUG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.1. DEBUG RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.2. DEBUG SIMULATE EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6. Licencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.1. ABILIS ID and the class of product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.2. Managing licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7. Logging functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.1. System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.2. Debug Log (Events Log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.2.1. Displaying Log Debug saved on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.2.2. Displaying ERR codes (D CODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.3. Exceptions Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
7.4. LOG parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
8. Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.1. Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2. Example of an off-line configuration creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.3. Console configurator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.1. Example of an off-line input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.2. Example of an off-line output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

v
Draft Abilis CPX tutorial, release 7.4 Draft

II. Hardware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

9. Voip card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.1. Voip card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.2. POTS-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.3. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
9.3.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.2. ADSL-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.3. ADSL-X resource diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.1. ADLS-X resource diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.2. ADSL-X resource statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11. GSM-UMTS BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1. GSM-BOX and UMTS-BOX devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.1. UG device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.2. CELLBOX fake device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.1.3. CELL device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.1.4. CODEC device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.1.5. SIMEMU device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.2. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.2.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.3. LCS - Last Calling number Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
11.3.1. LCSG - Last Calling number Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
11.3.2. LCST - Last Calling number Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.4. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.5. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.6. CTI GSM/UMTS ports diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.1. Diagnostics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.2. Statistics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.7. How to update UMTSBOX-2 firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
12. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.1. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.2. Simbox device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.3. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
12.4. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
12.5. How to update Simbox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
13. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.1. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.2. Citobox and GPIO devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.3. CTI port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
13.4. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
13.4.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
13.5. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.1. Citobox diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.2. Citobox Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.6. How to update Citobox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
14. RJS - RJ Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.1. RJS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.2. RJS device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.3. How to update RJS firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
15. UMTS Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
15.1. UMTS Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
III. Software resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
16. CP - Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1. CP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.1. Access levels to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.2. CP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2. CP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.1. CP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.2. CP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
16.2.3. CP sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3. Connecting to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

vi
Draft Abilis CPX tutorial, release 7.4 Draft

16.3.1. Connecting through a TCP/IP network using TELNET/SSH protocols . . . . . . . . . . . . . . . . . . . . . 263

16.3.2. Connecting through the serials-asynchronous ports of the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
17. TELNET - TELecommunication NETwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.1. TELNET resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.1.1. TELNET resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.2. TELNET diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.1. TELNET diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.2. TELNET statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.3. TELNET session status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
17.3. TELNET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
17.3.1. TELNET from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
18. SSH - Secure SHell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1. SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.1. Activating the SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.2. SSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.2. SSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.1. SSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.2. SSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.3. SSH sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
18.3. SSH commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
18.3.1. SSH from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
19. IPRTR - IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
19.1. IPRTR resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
19.1.1. IPRTR resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2. IP Routings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2.1. D IPR (Display IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
19.2.2. A IPR (Add IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
19.2.3. C IPR (Clear IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.4. S IPR (Set IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.5. IP Source Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
19.3. IP Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.1. D P IP (Display Parameter IP resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.2. A RES:IP (Add IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
19.3.3. C RES:IP (Clear IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
19.3.4. S P IP (Set Parameter IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
19.3.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
19.4. Administrative Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.1. D IPAD (Display IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.2. A IPAD (Add IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.3. C IPAD (Clear IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
19.4.4. S IPAD (Set IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5. IP Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.1. D IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.2. A IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.3. C IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
19.5.4. S IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6. IPRTR diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.1. IPRTR diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.2. IPRTR statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
19.7. IPFLOW Tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
19.7.1. List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
19.7.2. Activating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
19.7.3. Deactivating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.4. Starting the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.5. Stopping the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.6. Display of IPFLOW parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.7. Setting IP packet filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
19.7.8. IPFLOW trace display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
20. NAT - Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1. NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.1. Frequently used expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.2. Activating the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

vii
Draft Abilis CPX tutorial, release 7.4 Draft

20.1.3. NAT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

20.2. NAT Aliases table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.1. D NAT (Display NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.2. A NAT (Add NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
20.2.3. C NAT (C NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
20.2.4. S NAT (Set NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
20.2.5. M NAT (Move NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
20.2.6. INIT RES:NAT and INIT NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
20.3. NAT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.1. NAT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.2. NAT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.3. Debug of the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
20.4. Examples of NAT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.1. Suggest an access from inside workstations to outside networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.2. Suggest an access from outside networks to internal servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
20.4.3. Configuring a DMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
21. IPSH - IP Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.1. IPSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.1.1. IPSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.2. IP Flow table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.1. D IPSH FLOW (Display IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.2. A IPSH FLOW (Add IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.3. C IPSH FLOW (Clear IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.4. S IPSH FLOW (Set IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3. IP Rule table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3.1. D IPSH RULE (Display IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
21.3.2. A IPSH RULE (Add IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.3. C IPSH RULE (Clear IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.4. S IPSH RULE (Set IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4. IP User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4.1. D IPSH USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.5. IPSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.1. IPSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.2. IPSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
22. IPACL - IP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
22.1. IP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
22.1.1. TOS (Type Of Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.1.2. Activating IPACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.2. IPACL management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
22.2.1. D IPACL (Display IP Access Control List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
22.2.2. A IPACL (Add IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
22.2.3. C IPACL (Clear IP Acces Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
22.2.4. S IPACL (Set IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
22.2.5. M IPACL (Move IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
22.2.6. F IPACL (Find IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
22.3. Examples of IPACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.1. IP packets blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.2. Giving High Priority to VoIP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
23. RIP - Routing Information Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1. RIP Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1.1. Activating the RIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1.2. RIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
23.2. RIP External Routes filter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
23.2.1. D RIP EXTERNAL (Display RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.2. A RIP EXTERNAL (Add RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.3. C RIP EXTERNAL (Clear RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.4. S RIP EXTERNAL (Set RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3. RIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.1. RIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.2. RIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4. Examples of RIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4.1. Activation of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

viii
Draft Abilis CPX tutorial, release 7.4 Draft

23.4.2. Configuration of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

23.4.3. Configuration of IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
23.4.4. Configuration of IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
23.4.5. Display IP routing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
24. VRRP - Virtual Router Redundancy Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1. VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.1. Activating the VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.2. VRRP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.2. VRRP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.3. VRRP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.1. VRRP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.2. VRRP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.4. Examples of VRRP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.1. One-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.2. Load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
24.4.3. Multiple Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
24.4.4. Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
24.4.5. Virtual Routers Without Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
24.4.6. One Backup Protecting Two Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
24.4.7. Virtual Routers With Multiple IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
24.4.8. Two-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
25. DHCP - Dynamic Host Configuration Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1. DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.1. Activating DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.2. DHCP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
25.2. DHCP Relay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3. DHCP Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3.1. DHCP Server tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
25.3.2. Example of configuration of DHCP in Server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
25.3.3. DHCP bindings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
25.4. DHCP diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.1. DHCP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.2. DHCP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
25.4.3. DHCP debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5. DHCPC resource (DHCP Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.1. Activating DHCPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.2. DHCPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
25.5.3. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
26. DNS - Domain Name System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1. DNS Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.1. Activating the DNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.2. DNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
26.2. DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3. DNS Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3.1. Appendix - How DNS relay works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4. DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.1. DNS Resource as Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.2. DNS Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
26.4.3. DNS Resolver Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
26.5. DNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
26.5.1. DNS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
26.5.2. DNS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
27. DDNS - Dynamic DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1. Dynamic DNS (DDNS) resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.1. Activating the DDNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.2. DDNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
27.1.3. DDNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
28. SMTP - Simple Mail Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1. SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.1. Activating the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.2. SMTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.2. Example of configuration of the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

ix
Draft Abilis CPX tutorial, release 7.4 Draft

28.3. SMTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

28.3.1. SMTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
28.3.2. SMTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
29. SNTP - Simple Network Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1. SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.1. Activating the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.2. SNTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
29.2. Examples of SNTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.1. SNTP client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.2. SNTP server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.3. SNTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.1. SNTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.2. SNTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
30. ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1. ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.1. Activating the ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.2. ALARM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.3. The ALARM table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
30.1.4. ALARM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
31. UPNP - Universal Plug and Play . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.1. UPNPS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.2. UPNPS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.3. UPNPS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
31.4. How to configure UPNP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
32. FTP - File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1. FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.1. Activating the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.2. FTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
32.2. FTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.2. FTP Virtual Root Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.2.3. FTP Virtual Paths Access Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.3. FTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.1. FTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.2. FTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.4. Example of FTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.1. Configuring the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.2. Activating the user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.3. Creating the virtual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.4. Giving access rights to user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
32.4.5. Connecting to Abilis FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
32.4.6. Access to the system version directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
33. TFTP - Trivial File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1. TFTP - Trivial File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.1. Activating the TFTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.2. TFTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
33.2. TFTP diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.1. TFTP diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.2. TFTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
34. HTTP - HyperText Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1. HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1.1. Activating the HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1.2. HTTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
34.2. HTTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.2. HTTP Virtual Root Paths Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.2.3. HTTP Virtual Paths Access Rights Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.3. HTTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.1. HTTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.2. HTTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.4. HTTPS (HTTP over SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
34.4.1. Activating the SSL resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

x
Draft Abilis CPX tutorial, release 7.4 Draft

34.4.2. HTTP resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465

34.4.3. Connecting to Abilis using HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
34.5. Appendix - HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
35. SYSLOG - The syslog protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.1. SYSLOG resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.2. SYSLOG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.3. SYSLOG diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
35.4. SYSLOG messages codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5. Win2k SYSLOG server implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.1. Kiwi SYSLOG Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.2. KLog win2k SYSLOG server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
35.6. Rsyslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
35.6.1. Rsyslog configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.2. Syslog resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.3. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7.1. SYSLOG architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
36. Tunneling proprietary protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
36.1. Tunneling proprietary protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
36.1.1. Link check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
36.2. Configuring Packet Voice tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.1. Packet Voice over IP- Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.2. IP Packet Voice - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
36.2.3. IP-BCK Packet Voice - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
36.2.4. IP Packet Voice - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
36.3. Configuring Abilis Ip Tunnels (AIPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
36.3.1. Abilis IP Tunnel over IP – Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
36.3.2. Abilis IP Tunnel over IP - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . 500
36.3.3. Abilis IP Tunnel over IP - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
36.3.4. Abilis IP Tunnel over IP - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
36.4. Tunneling diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.1. Tunneling diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.2. Tunneling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
36.5. Appendix - LN2 parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
37. IPSEC - Internet Protocol SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.1. IPSEC - Internet Protocol SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.2. IPSEC Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.1. Activating the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.2. IPSEC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.3. IPSEC tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
37.3. IKE Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.1. Activating the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.2. IKE resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
37.3.3. IKE tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
37.4. IPSEC and IKE diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.1. IPSEC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.2. Statistics of the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.3. IKE diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.4.4. Statistics of the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.5. Example of IPSEC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
37.5.1. Activating IPSEC parameter on the desired IP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
37.5.2. Configuration of the Host connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
37.5.3. Configuration of the Client connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
37.5.4. Configuration of the Pre-shard Key table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
37.5.5. Outgoing IP resource for IPSEC packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
37.6. Appendix - IPSEC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
38. POEAC - PPP Over Ethernet Access Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1. PoEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.1. Activating the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.2. POEAC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.2. PPP Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.3. POEAC diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

xi
Draft Abilis CPX tutorial, release 7.4 Draft

38.3.1. POEAC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

38.3.2. POEAC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
38.4. Example of POEAC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
38.4.1. Configuring the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.2. Configuring the IPRTR resource for DNS distribution to the clients . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.3. Activating and configuring the IP over PPP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
38.4.4. Activating and configuring the PPP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
38.5. Appendix - Point to Point protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
39. SNMP - Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1. SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.1. Activating the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.2. SNMP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
39.2. Example of configuration of the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3. SNMP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.1. SNMP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.2. SNMP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
39.4. SNMP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
39.5. Appendix - SNMP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
40. TRFA - Traffic Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1. TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.1. Activating the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.2. TRFA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.1.3. Activating the TRFA inside IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.2. TRFA diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.1. TRFA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.2. TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.3. TRFA debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3. Example of TRFA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.1. Configuring TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.2. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
40.3.3. Using HTTP for showing TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
41. LDAP - Lightweight Directory Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
41.1. LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
41.1.1. Activating the LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.1.2. LDAP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.2. LDAP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.1. User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.2. Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
41.3. LDAP use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.1. Publishing local VoIP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.2. Identifying the caller in a VoIP phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
41.3.3. Mail composing and LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
41.4. Handling contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.1. Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.2. LDAP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
41.5. LDAP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.1. LDAP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.2. LDAP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
IV. CTI System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
42. CTI System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
42.1. CTI System module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.2. CTI Ports configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.3. CTI Ports Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
42.3.1. POTS and CTI Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
42.4. CTI Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
42.4.1. Internal clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
42.4.2. CPO - Call path optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
42.5. CTI Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.5.1. CTI Link Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.6. CTI Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
42.6.1. Display CTI Routing Table (D CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
42.6.2. Add CTI Routing Table (A CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

xii
Draft Abilis CPX tutorial, release 7.4 Draft

42.6.3. Clear CTI Routing Table (C CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

42.6.4. Set CTI Routing Table (S CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
42.6.5. Move CTI Routing Table (M CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
42.6.6. Macro functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
42.7. CTI routing for POTS devices (“PBX Group”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
42.8. CTI System Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
42.9. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.1. CTI Ports diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.2. CTI Ports statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
42.9.3. CTI Cluster diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
42.9.4. CTI Link diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.5. CTI connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.6. DSP and Audio Coders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
42.10. Examples of CTI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.1. Configuration of a VPN to transport voice and data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.2. Configuration of a VPN to transport only voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
42.11. Soft-PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.1. Supplemetary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.2. User call logs and mails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
42.11.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
42.11.4. Administrative pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
42.11.5. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
42.12. FAX Relay with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.1. Fax over packet networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.2. Fax Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.3. Abilis configurations for best results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
42.12.4. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
42.12.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
43. The web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
43.1. The web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
43.2. Section 1 - User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.2. Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
43.2.4. Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
43.2.5. CTI incoming/outgoing calls log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
43.2.6. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
43.3. Section 2 - Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.1. IP Traffic Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.2. Operator Panel Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
43.3.3. SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
43.3.4. Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
43.4. Section 3 - Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.1. Configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.2. Users administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
43.4.3. Groups administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
43.4.4. Lists administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
43.4.5. Disa administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
43.4.6. CTI administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
43.4.7. Voice Mail administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
44. OPC - Operator Panel Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1. OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.1. Activating the OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.2. OPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
44.2. OPC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.3. OPC Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
44.3.1. The panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
44.3.2. The table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
44.3.3. Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
44.3.4. Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
45. IAX - Inter-Asterisk eXchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

xiii
Draft Abilis CPX tutorial, release 7.4 Draft

45.1. CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771

45.1.1. Activating the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1.2. CTIIAX resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
45.2. CTIIAX tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.2. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
45.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
45.4. Example of IAX configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
45.4.1. Configuration of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.3. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
45.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
45.5. Connecting Abilis and Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.1. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.2. Activation of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.3. Example 1: Abilis and Asterisk have static IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.4. Example 2: Abilis has a static address and Asterisk has a dynamic address . . . . . . . . . . . . . . . . . 797
45.5.5. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
45.6. CTIIAX diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.1. CTIIAX diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.2. CTIIAX statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
45.6.3. Debug of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
45.7. Appendix - IAX protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
46. SIP - Session Initiation Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1. CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.1. Activating the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.2. CTISIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
46.2. CTISIP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.2. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
46.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
46.4. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
46.4.1. Activation and configuration of the CtiSip resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.3. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
46.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
46.5. Connecting Abilis and a SIP proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.1. Activation of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.2. Example: Abilis and a proxy registered in Abilis domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.3. Example: Proxy and Abilis registered in Proxy remote domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
46.5.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
46.6. Busy Lamp Field (BLF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.1. Dialog an presence monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.2. BLF in Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
46.7. CTISIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
46.7.1. CTISIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
46.7.2. CTISIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
46.7.3. Debug of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
46.8. Appendix - SIP protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.1. SIP and NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.2. Solution to SIP NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
46.8.3. SIP NAT Trasversal problem with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
47. DISA - Direct Inward System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
47.1. CTIDISA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.1. User identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.2. Post-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
47.1.3. Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
47.1.4. Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.1.5. Data Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2. CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.1. Activating the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.2. CTIDISA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

xiv
Draft Abilis CPX tutorial, release 7.4 Draft

47.3. CTIDISA tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848

47.3.1. CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
47.3.2. CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
47.4. Example of Post Selection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
47.4.4. Configuring the CTI Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
47.5. Example of Automatic Call Distribution configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.5.4. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.6. Example of Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
47.6.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.6.4. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.7. Example of Data Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.3. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8. Message files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.1. File audio format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.2. Commands to manage audio files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.8.3. Example of insertion of WAV files and creation of CPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.9. CTIDISA diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.1. CTIDISA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.2. CTIDISA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
47.9.3. Advanced Debug of the CtiDisa resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
47.10. DISA administration through web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.1. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.2. DISA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
48. CTIAS - CTI Advanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1. CTIAS - CTI Advanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.1. Activating the CTIAS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.2. CTIAS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2. CTIVM - CTI Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.1. Activating the CTIVM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.2. CTIVM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
48.2.3. CTIVM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
48.2.4. CTIVM configuration through CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
48.2.5. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
49. CTISMS - CTI SMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1. CTISMS - CTI SMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1.1. Activating the CTISMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1.2. CTISMS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2. CTISMS Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.1. CTISMS IN routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.2. CTISMS OUT routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
49.3. CTISMS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.1. CTISMS diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.2. CTISMS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
50. ACNT - Accounting resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1. ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.1. Activating the ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.2. ACNT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2. ACNT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.1. ACNT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.2. ACNT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
50.3. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
V. HowTo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896

xv
Draft Abilis CPX tutorial, release 7.4 Draft

51. HowTo - Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900

51.1. How to enter into the Abilis control-program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
51.1.1. How to enter into the Abilis control-program through the TELNET protocol . . . . . . . . . . . . . . . 901
51.1.2. How to enter into the Abilis control-program through the serial-asynchronous port of
the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
51.1.3. How to enter into the Abilis control-program through the SSH protocol . . . . . . . . . . . . . . . . . . . . 902
51.1.4. How to enter into the Abilis control-program through an ISDN connection . . . . . . . . . . . . . . . . . 902
51.2. How to prepare an Abilis Compact-Flash using a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
51.3. How to use the Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
51.3.1. How to create a new configuration file DRIVERS.CFG with the Console configurator. . . . . 906
51.3.2. How to modify an existing configuration file DRIVERS.CFG with the Console
Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
51.4. How to remotely upgrade the Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
51.5. How to remotely transfer files using a terminal emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.1. How to download configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.2. How to upload configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
51.6. How to restart the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.7. How to upgrade configuration files to newer firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.8. How to copy files using a removable drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
51.8.1. How to copy configuration and log files on an USB disk through the command-line
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
51.8.2. How to copy configuration and log files on an USB disk using the MFIDE front panel. . . . . 915
51.8.3. How to copy configuration files from an USB disk to the Abilis HD/CF through the
command-line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
51.8.4. How to copy configuration files from an USB disk to the Abilis HD/CF using the
MFIDE front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
51.9. How to know which kind of hardware is mounted on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.9.1. How to recognize PCI cards model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.10. How to automatically reassign the USBPORTID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
51.11. How to manage licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.12. How to view boot log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13. How to change the login passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.1. How to change the TELNET password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.2. How to change the SSH password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.3. How to change the users' passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.14. How to activate the Abilis SSH server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.15. How to open a TELNET connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.16. How to open a SSH connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
51.17. How to create a list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
51.17.1. How to create a list of ISDN numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.2. How to create a list of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.3. How to create a list of IP addresses ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.18. How to configure Abilis as a SYSLOG client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.19. How to trace the internal events for debugging purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
51.19.1. How to convert Abilis CPX traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
52. HowTo - Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
52.1. How to configure LAN settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.2. How to activate a new ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.3. How to assign several IP addresses to the same LAN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4. How to configure ADSL connections using USB modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4.1. How to configure a RFC 1483 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
52.4.2. How to configure a PPPoA (RFC 2364) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.4.3. How to configure a PPPoE connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.5. How to configure HDSL/SHDSL connections using V.35/G.703 synchronous ports . . . . . . . . . . . . . . . . . 934
52.6. How to configure the default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.1. How to configure the default IP route in case Abilis is connected to an ADSL USB or
V.35/G.703 modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.2. How to configure the default IP route in case Abilis is connected to an ethernet ADSL
router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
52.6.3. How to configure an alternative default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
52.7. How to configure the Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
52.8. How to share a single Internet connection among multiple computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938

xvi
Draft Abilis CPX tutorial, release 7.4 Draft

52.9. How to access IP hosts and services which are behind a NAT manager (port forwarding) . . . . . . . . . . . . 938
52.10. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.1. How to setup DDNS service using dyndns.org . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.2. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
52.11. How to configure a Remote Access Server (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.1. How to configure a RAS using IPSEC VPN server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.2. How to configure a RAS using IPSEC VPN server with iPHONE . . . . . . . . . . . . . . . . . . . . . . . . . 950
52.11.3. How to configure a RAS using PPPoE connections with an Ethernet/WiFi network . . . . . . . 952
52.11.4. How to configure a RAS using ISDN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
52.12. How to configure an ISDN PPP Dial-UP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13. How to configure a VPN tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13.1. How to configure a VPN tunnel where both Abilis have a static public IP address . . . . . . . . 955
52.13.2. How to configure a VPN tunnel where one Abilis has a dynamic public IP address or
is placed behind a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
52.13.3. How to configure a VPN tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . . 957
52.13.4. How to configure a VPN tunnel with the “double path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
52.14. How to configure a voice tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
52.14.1. How to configure a voice tunnel where both Abilis have a static public IP address . . . . . . . . 962
52.14.2. How to configure a voice tunnel where one Abilis has a dynamic public IP address or
is placed behind a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
52.14.3. How to configure a voice tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . 964
52.14.4. How to configure a voice tunnel with the “double-path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
52.15. How to activate the DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
52.15.1. How to activate the DHCP in relay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
52.15.2. How to activate the DHCP in server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
52.15.3. How to activate the DHCP in client mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
52.16. How to activate the FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17. How to activate the HTTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17.1. How to activate the HTTP over SSL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
52.18. How to activate the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
52.19. How to use state detection of IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20. How to activate the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.1. How to activate the SNTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.2. How to activate the SNTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
52.21. How to activate the SNMP agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
52.22. How to publish the users on the Abilis LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
53. HowTo - CTI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
53.1. How to configure ISDN ports to connect PBX or ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
53.2. How to configure FXS (POTS) ports for analog telephones or fax machines . . . . . . . . . . . . . . . . . . . . . . . . . 979
53.3. How to program a group of telephone lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
53.4. How to configure fax modem relay parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
53.5. How to create a VoIP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
53.6. How to register an IAX telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
53.7. How to register a SIP telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
53.7.1. How to register a SIP telephone onto Abilis when the telephone is behind a NAT . . . . . . . . . . 985
53.8. How to register Abilis as a client of Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
53.9. How to register Abilis as a client of a SIP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.10. How to configure the speedlimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.11. How to configure opc to collect call information from a remote abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.12. How to activate the Accounting service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.13. How to enable pickup service for a POTS/ISDN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.14. How to enable pickup service for a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.15. How to configure CTIDISA to implement a responder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.1. Implementing a responder using MODE:INTRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.2. Implementing a responder using MODE:DISA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.3. Getting a call on phones while the responder is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
53.16. How to configure Last Calling Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
53.17. How to configure DATA CALL BACK using an UMTS Key, calling an ISDN number . . . . . . . . . . . . 994
53.18. How to configure CTISMS to send sms using the web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19. How to configure CTISMS to send sms via emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19.1. Instructions to send emails through sms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
53.19.2. Instructions to send sms through emails using a client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997

xvii
Draft Abilis CPX tutorial, release 7.4 Draft

54. FAQ - Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002

54.1. ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.1. How can I verify if an ISDN line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.2. Back up over ISDN doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.3. How can I manage the backup over ISDN autoconnection? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.4. Is it possible to connect ISDN phones to BRI/BRI-HFC cards? . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.5. Why (and how to) enable/disable analog ports on a NT1 Plus device? . . . . . . . . . . . . . . . . . . . . 1004
54.2. POTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.2.1. The connection to a PBX using pots ports doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.3. ADSL/HDSL lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.1. How can I verify if an ADSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.2. How can I verify if a HDSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.3. Why the xDSL line is slow? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
54.3.4. Why can't I reach any website? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4. CTI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.1. How can I manage alternative CTI routings? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.2. How does Round Robin scanning method work in CTI Port Group? . . . . . . . . . . . . . . . . . . . . . . 1009
54.4.3. How can I change the POTS number length? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
54.4.4. How can I activate the Caller Identification Presentation (CLIP) on POTS ports? . . . . . . . . . 1010
54.4.5. How can I manage the Calling Line Identification (CLI) for outcoming calls? . . . . . . . . . . . . 1010
54.4.6. Why during a call do I hear a fax handshaking? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
54.4.7. How can I view the maximum number of simultaneous calls supported by Abilis? . . . . . . . . 1011
54.4.8. How can I view the available coders supported by the cards installed in Abilis? . . . . . . . . . . . 1012
54.4.9. How can I change the volume of a compressed call? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
54.4.10. How many VoIP channels are used, depending on the call's source and destination? . . . . . 1013
54.4.11. What happens if a call fails with the “CAUSE:FF B4 (CPX,Loop)”? . . . . . . . . . . . . . . . . . . . . 1013
54.4.12. How can i configure sip multialerting? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5. IP router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.1. How can I query the IP routing table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.2. How does ACLBYPASS parameter work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.3. How can I view the Abilis ARP table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.4. How can I filter the NAT sessions? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
54.6. Abilis system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.1. How can I view the current RAM usage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.2. How can I view the current HD/CF space occupation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
54.6.3. How can I view the current CPU load? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.4. How can I view if the BRI card has the H.100 bus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.5. Is it possible to extract clock synchronization from BRIO cards? . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.6. How can I view if the Abilis USB ports are enabled? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.7. Why do I get the error “RESOURCE NOT PRESENT OR NOT RUNNING” when I
initialize a resource? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.6.8. How can I change the Abilis prompt name? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7. Tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7.1. How can i have information about the use of ISDN backup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.8. IPSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
54.8.1. Why the outgoing traffic from CPX toward an IPSEC vpn is blocked after updating
from 6.5.x to 7.0.x? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
54.9. CTISMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.1. Can SMS to Email be sent an SMTP server different from the Abilis one? . . . . . . . . . . . . . . . . 1024
54.9.2. Can SMS also send CC: and BCC:? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.3. Can SMS to Email or Email to SMS be more than 160 characters? . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.4. Are attachments supported for email to SMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.5. Can SMS be send thru a dialing plan to take advantage of cheaper or marketing promo
when sending SMS within the same Telco? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10. UMTS Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.1. How can I improve the quality of the calls with UMTS Box? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.2. How does Abilis manage the PIN code of a SIM card? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
VI. Separate software tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027
55. CPX accounting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1. CPX accounting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.1. Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.2. Extractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037

xviii
Draft Abilis CPX tutorial, release 7.4 Draft

55.2. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

56. IPSEC clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1. TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.1. Installing TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.2. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.3. Configuring The Greenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
57. PPPoE clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1. RASPPPoE driver for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.1. Installing RASPPPOE drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.2. Creating PPPoE Dial-Up connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.2. Routers with PPPoE support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
58. Softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1. Zoiper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.1. Zoiper installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.2. Creating an IAX account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
58.1.3. Creating a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
VII. References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1060
59. List of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
59.1. Complete list of On-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
59.2. Complete list of Off-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
60. Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
60.1. System Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
61. Disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1. ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.1. ISDN disconnection codes recommended by ITU (formerly CCITT) . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.2. Abilis CPX private ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
61.2. X.25 disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.1. ITU (formerly CCITT) X.25 codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.2. Abilis CPX internal codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084
A. Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086

xix
Draft Draft

What's new
New features of the release 7.1:

• Alarm resource;

• Tftp server;

• CTI advanced services (CTIAS): the voice mail plugin;

• d ipre command;

• DEBUG SIMULATE EVENT:WDGRESET command;

• HELP SYSLOG command;

• filter on list type using d list command.

xx
Draft Draft

About this book

Abilis CPX is a device which integrates many data-exchange and telephone services. The main built-in components are:

• TCP/IP router with firewall;

• CTI (Computer Telephony Integration) system containing: VoIP gateway, ISDN switch, Soft-PBX, POTS adapter, GSM/
UMTS Gateway;

• E-mail, FTP, HTTP, DHCP, DNS, RAS servers.

See www.abilis.net1 for details.

This book is an introduction to Abilis CPX installation, programming and usage. How to get diagnostic information and how
to solve problems, too, are described but all details are not provided (this book is not a “technical reference”).

Expected readers
This book is intended for people who want to train themselves as Abilis systems planners and integrators. The underlying
requisite is a general knowledge of telecommunication networks and protocols, especially IP and ISDN.

Book structure
This book is composed of five parts.

• Part I, “Abilis CPX” provides basic introduction to Abilis CPX system.

• Part III, “Software resources” explains ways to configure basic Abilis services.

• Part IV, “CTI System” describres how to configure CTI System and related resources.

• Part II, “Hardware configuration” provides information about the configuration of Abilis hardware.

• Part VI, “Separate software tools” documents additional programs related to Abilis CPX.

• Part V, “HowTo” contains short descriptions of how to accomplish a particular task or make use of a particular feature of
Abilis CPX.

• Part VII, “References” contains references like Log Messages or Disconnection codes.

Typographic conventions
Communication with Abilis CPX is illustrated in this way:

[18:06:39] ABILIS_CPX: d t
Current Local Time : Saturday 11/08/2007 18:06:41 (GMT+2.00)
Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague...
Currently Observing : Daylight Savings Time (DST)

The communication starts with a prompt, issued by the Abilis, in the above example called “ABILIS_CPX”. User commands
follow on the same line (d t is a command to display date and time information). The text after the d t command is
information output by the “ABILIS_CPX”.

If commands are present in normal text, they look like this: d d telnet. Names of configuration paremeters, diagnostic fields
or statistic counters look like this: KEEPALIVE (uppercase configuration parameters can be modified in run time, that is,
while ABILIS is running, while lowercase parameters require a reboot). Named values for configuration parameters look like
this: YES.

A Sidebar

Additional information, which is not directly related to the main text, is provided in sidebars.

1
http://www.abilis.net/

xxi
Draft About this book Draft

Additional information can be marked as a “Note”:

Note
Reasonable typographic conventions facilitate reading.

Good practices or easy-ways to results are marked as a “Tip”:

Tip
Reading the Abilis tutorial is the most reliable way to learn the Abilis features.

Actions which may produce unwished effects are marked with “Caution”:

Caution
Before entering IPACL instructions, double check not to make yourself filtered out!

Information about actions that can potentially lead to data loss or hardware damage are marked as “Warning”:

Warning
Don't pour water into Abilis CPX, its behaviour cannot be guaranteed in this case.

Contributors
This tutorial is the result of a collaborative effort of the following contributors (in alphabetical order):

• Luigi Demuro

• Tomáš Klinkovský

• Leo Mantovani

• Angelo Pignoli

• Marco Bellesia

• Nicola Trevisani

Any suggestions or comments can be sent to Abilis technical support (<[email protected]>).

xxii
Draft Draft

Part I. Abilis CPX

Draft Draft

Table of Contents
1. About Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1. General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Abilis CPX structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Abilis hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1. Abilis hardware structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Abilis Base-K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3. Abilis Base-J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4. Abilis VMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5. Compact Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6. Micro Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.2. Number of pluggable usb devices to the same USB 1.1 OHCI/UHCI controller . . . . . . . . . . . . . . . . . . . . . . 13
2.6.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7. Nano Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.2. Number of pluggable usb devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.8. MFIDE module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.1. Watchdog Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.2. Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.3. Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9. Abilis PCI boards and extension boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9.1. ESB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.9.2. CTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.9.3. QPRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.9.4. QPRI2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.9.5. PB44X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9.6. PB44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.9.7. BRI-HFC4 / BRI-HFC8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.9.8. BRIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.9.9. POTS 4/8/16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9.10. POTS protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.9.11. VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.9.12. ETH100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.10. USB devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.2. UMTS-BOX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.10.3. GSM Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.10.4. UMTS-Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.5. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.6. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.10.7. RJ Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3. Physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.1. Numbering of the physical ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2. ISDN Basic Rate Interface (BRI) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.2.1. Emergency connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.3. Importance of the impedance matching adapters (ISDN Adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.4. Connecting pots cards to patch panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.5. ADSL modem connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.6. POTS protection connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.7. UMTS-BOX connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.8. Citobox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.8.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.9. Simbox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.10. RJS connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

2
Draft Abilis CPX Draft

3.10.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

3.10.2. Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4. Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1. Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.1. Firmware versioning numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.2. Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.3. Compatibility of drivers.cfg files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5. Command language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.2. Command Line Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.3. Help online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.4. System accessing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.1. LOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.2. LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.3. CLOSE / EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.5. Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.1. D DEV (Display Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.2. A DEV (Add Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.5.3. S DEV (Set Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.5.4. C DEV (Clear Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6. Resources or Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.1. D P (Display Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.2. A RES (Add Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.6.3. S P (Set Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.6.4. C RES (Clear Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.7. Initialization/activation/deactivation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.1. INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.2. D ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.3. S ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.4. D INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.5. S INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.7.6. D RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.7.7. D TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.7.8. ALARM VIEW and ALARM RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.7.9. CALL RES and DISC RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8. General and system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.1. D G (Display General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.2. D I (Display Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.8.3. D VER (Display Versions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.8.4. CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.8.5. Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.8.6. D DESCR (Display Descriptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.8.7. D PSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.9. Users Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
5.9.1. D USER (Display User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.9.2. A USER (Add User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.3. C USER (Clear User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.4. S USER (Set User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10. Address book management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.1. CONTACT EXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.2. CONTACT IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.10.3. CONTACT RELOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11. Lists management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11.1. LIST CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11.2. LIST DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.3. LIST RENAME / LIST DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.4. D LIST (Display List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.5. A LIST (Add List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.11.6. C LIST (Clear List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.11.7. D ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.11.8. Type of lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.12. Configuration validating and saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

3
Draft Abilis CPX Draft

5.12.1. VALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

5.12.2. SAVE CONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.13. System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.1. CONFLOG BACKUP and CONF BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.2. CONFLOG RESTORE / CONF RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.3. FILE COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.4. FILE DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.5. FILE GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.6. FILE PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.13.7. SYS COMPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.8. SYS COMPACTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.9. SYS DELETE PACKAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.10. SYS DELETE VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.11. SYS UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5.13.12. SYS DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.13.13. SYS DISK INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.14. SYS DISK CHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.15. SYS DISK FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.16. SYS DISK LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.17. SYS DISK MBR DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.18. SYS DISK PARTITION INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.19. SYS DISK PARTITION ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.20. SYS DISK PARTITION RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.21. SYS SET BOOT VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.22. SYS DISPLAY BOOT LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.13.23. WARM START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.14. Diagnostics and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.1. Diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.2. Statistics Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5.15. Test functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.1. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.2. Tracert / Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.3. Pingstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.15.4. DSPs test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.16. Trace functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.16.1. Trace act . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.16.2. Trace start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.3. Trace stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.4. Trace get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.17. DEBUG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.1. DEBUG RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.2. DEBUG SIMULATE EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6. Licencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.1. ABILIS ID and the class of product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.2. Managing licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7. Logging functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.1. System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.2. Debug Log (Events Log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.2.1. Displaying Log Debug saved on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.2.2. Displaying ERR codes (D CODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.3. Exceptions Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
7.4. LOG parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
8. Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.1. Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2. Example of an off-line configuration creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.3. Console configurator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.1. Example of an off-line input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.2. Example of an off-line output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

4
Draft Draft

Chapter 1. About Abilis CPX

Nicola Trevisani
Tomáš Klinkovský
Marco Bellesia
Luigi Demuro

Table of Contents
1.1. General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Abilis CPX structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1. General description

Figure 1.1. Abilis CPX

• Abilis is a PC based product featuring high modularity, flexibility and scalability. It can be the only telecom appliance in
the branch offices, as well at the headquarters.

• Abilis has been planned to optimize corporations' networks (telephone-data integration), reducing costs and improving
services.

• Abilis is the ideal product for multi-site entities. Thanks to Abilis systems they can use VPN (Virtual Private Network),
transfer secret data (coded connections) and make VolP calls (for free!), reducing drastically the cost of inter-company
calls.

• Abilis can support any protocol and can be installed between the customer systems (IP net and switchboard) and the
telecommunication lines (PSTN, ISDN, GSM, ADSL, xDSL, X25, Internet FrameRelay, radio link, …) in a completely
transparent way, without the need to change existing equipment.

1.2. Abilis CPX structure

The internal structure of Abilis CPX is represented in the following scheme.

5
Draft About Abilis CPX Draft

Figure 1.2. Top level scheme

Hardware is composed by devices which provide an interface to different kinds of network (Internet, ISDN, GSM,...).

The storage device is used to keep the operating system, the configuration and log files; generally it is a Compact Flash, or
optionally a Hard Disk.

A Watchdog is dedicated to the control of the normal operational cycle.

The software is made up of different modules (or resources) providing a full scale of services.

There are three ways to configure Abilis:

• using the Control Port that allows configuration and supervising functions;

• using the Web Interface which allows to do many but not all operations;

• using the config.exe utility program which is a console mode Windows application which precisely reproduces the same
Control Port interface and command language available on a working Abilis CPX.

Note
Simplest operations, like software installation or recovery, can also be done using the front panel of MFIDE
module.

It is also possible to configure Abilis CPX without connecting to the Control Port, using the config.exe utility program.

6
Draft Draft

Chapter 2. Abilis hardware

Nicola Trevisani
Marco Bellesia

Table of Contents
2.1. Abilis hardware structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2. Abilis Base-K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3. Abilis Base-J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4. Abilis VMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.4.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5. Compact Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.5.1. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6. Micro Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.2. Number of pluggable usb devices to the same USB 1.1 OHCI/UHCI controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.6.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7. Nano Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.7.1. Led indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.2. Number of pluggable usb devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.7.3. Physical and electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.8. MFIDE module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.1. Watchdog Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.2. Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.8.3. Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9. Abilis PCI boards and extension boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.9.1. ESB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.9.2. CTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.9.3. QPRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.9.4. QPRI2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.9.5. PB44X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.9.6. PB44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.9.7. BRI-HFC4 / BRI-HFC8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.9.8. BRIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.9.9. POTS 4/8/16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.9.10. POTS protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.9.11. VoIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.9.12. ETH100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.10. USB devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.10.2. UMTS-BOX2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.10.3. GSM Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.10.4. UMTS-Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.5. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.10.6. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.10.7. RJ Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2.1. Abilis hardware structure

Abilis hardware:

• Base unit: PC platform with 4 PCI-slots for interface adapters, 2 RS-232 ports, 4 USB ports, 1 ethernet;

7
Draft Abilis hardware Draft

• CPU: Intel x86 (ranging from Celeron 430 to E7500);

• RAM: 512-2048 MB;

• MFIDE module with Watchdog microprocessor, 5 control buttons and 2x20 characters LCD;

• Mass Memory:

• 64-128 MB Compact Flash;

• Optional Hard Drives with SATA interface.

Figure 2.1. Abilis base unit

2.2. Abilis Base-K

Figure 2.2. Abilis Base-K

Abilis Base-K is an expandable device. Below there are the hardware characteristics of the base unit:

• Intel E7500 CPU

• 1024 MB RAM

• Dual 128MB Compact-Flash modules for boot

• PC platform with 4 PCI-slots, 4 USB ports (optionally expandable up to 8) for expansion modules and 1 ethernet

• 2 RS-232 ports

• Hardware Watchdog processor

These are the expansions:

• up to 8 ISDN-2 ports (up to 16 simultaneous calls to the ISDN public network). Refer to the following chapters:
Section 2.9.3, “QPRIX”, Section 2.9.5, “PB44X”, Section 2.9.7, “BRI-HFC4 / BRI-HFC8”,Section 2.9.8, “BRIO”

• up to 48 analogue extensions (for “internal” telephones or fax). Refer to the following chapter:Section 2.9.9, “POTS
4/8/16”

• up to 128 VoIP telephones (SIP or IAX2 protocol). Refer to the following chapter:Section 2.9.11, “VoIP”

8
Draft Abilis hardware Draft

• up to 8 xDSL concurrent connections to the Internet. Refer to the following chapter:Section 2.10.1, “ADSL modem”

• up to 8 GSM/UMTS gateways (up to 16 simultaneous calls between the fixed and the mobile network). Refer to the
following chapter:Section 2.10.2, “UMTS-BOX2”

• up to two 5” 5200 RPM SATA Hard-Drives

Abilis Base-K includes all licences but VMX and Data Comp ones, because it's a class 6 device. Refer to Section 6.1.1,
“ABILIS ID and the class of product” to know more about licencing.

2.2.1. Physical and electrical specifications

Dimensions[mm]: 440x355x138;

Weight:7,5 Kg;

Power supply:110-230VAC, 150W.

2.3. Abilis Base-J

Figure 2.3. Abilis Base-J

Abilis Base-J is an expandable device. Below there are the hardware characteristics of the base unit:

• Intel Celeron 430

• 512 MB RAM

• Dual 128MB Compact-Flash modules for boot

• PC platform with 4 PCI-slots and 4 USB (optionally expandable up to 8) ports for expansion modules and 1 ethernet

• 2 RS-232 ports

• Hardware Watchdog processor

These are the expansions:

• up to 8 ISDN-2 ports (up to 16 simultaneous calls to the ISDN public network). Refer to the following chapters:
Section 2.9.3, “QPRIX”, Section 2.9.5, “PB44X”, Section 2.9.7, “BRI-HFC4 / BRI-HFC8”,Section 2.9.8, “BRIO”

• up to 48 analogue extensions (for “internal” telephones or fax). Refer to the following chapter:Section 2.9.9, “POTS
4/8/16”

• up to 128 VoIP telephones (SIP or IAX2 protocol). Refer to the following chapter:Section 2.9.11, “VoIP”

• up to 8 xDSL concurrent connections to the Internet. Refer to the following chapter:Section 2.10.1, “ADSL modem”

• up to 8 GSM/UMTS gateways (up to 16 simultaneous calls between the fixed and the mobile network). Refer to the
following chapter:Section 2.10.2, “UMTS-BOX2”

• up to two 5” 5200 RPM SATA Hard-Drives

Abilis Base-j doesn't includes all licences, because it's a class 3 device. Refer to Section 6.1.1, “ABILIS ID and the class of
product” to know more about licencing.

9
Draft Abilis hardware Draft

2.3.1. Physical and electrical specifications

Dimensions[mm]: 440x355x138;

Weight:7,5 Kg;

Power supply:110-230VAC, 150W.

2.4. Abilis VMX

Figure 2.4. Abilis VMX

Abilis VMX supports multi-core CPUs: one core is dedicated to Abilis and the remaining to virtual machines managed
by a modified version of XEN1.There's no perfomance degradation because both router and Hypervisor can access to not
simulated hardware resources.

Abilis VMX is an expandable device. Below there are the hardware characteristics of the base unit:

• Intel E7500 CPU

• 2048 MB RAM

• Dual 128MB Compact-Flash modules for boot

• PC platform with 4 PCI-slots and 8 USB ports for expansion modules

• 2 RS-232 ports

• Hardware Watchdog processor

These are the expansions:

• up to 8 ISDN-2 ports (up to 16 simultaneous calls to the ISDN public network). Refer to the following chapters:
Section 2.9.3, “QPRIX”, Section 2.9.5, “PB44X”, Section 2.9.7, “BRI-HFC4 / BRI-HFC8”,Section 2.9.8, “BRIO”

• up to 48 analogue extensions (for “internal” telephones or fax). Refer to the following chapter:Section 2.9.9, “POTS
4/8/16”

• up to 128 VoIP telephones (SIP or IAX2 protocol). Refer to the following chapter:Section 2.9.11, “VoIP”

• up to 8 xDSL concurrent connections to the Internet. Refer to the following chapter:Section 2.10.1, “ADSL modem”

• up to 8 GSM/UMTS gateways (up to 16 simultaneous calls between the fixed and the mobile network). Refer to the
following chapter:Section 2.10.2, “UMTS-BOX2”

• up to two 5” 5200 RPM SATA Hard-Drives

Hypervisor can run both Linux OS and Windows OS virtual machines.

2.4.1. Physical and electrical specifications

Dimensions[mm]: 440x355x138;

1
http://en.wikipedia.org/wiki/Xen

10
Draft Abilis hardware Draft

Weight:7,5 Kg;

Power supply:110-230VAC, 150W.

2.5. Compact Abilis

Figure 2.5. Compact Abilis

Compact Abilis is a non-expandable device equipped with:

• 1 Gigabit ethernet

• 3 Ethernet 10/100

• 4 ISDN BRI

• 8 POTS

• 1, 2 or 4 DSPs supporting 4 channels each. Standard production is with 2 DSPs, 8 channels

• 1 ATOM 330 dual core , 1.66 GHz

• 8 USB ports

• MFPCI watchdog

• Optional 1 or 2 SATA hard disks

The device equipped with 4 BRI + 8 POTS has to be configured as BS48 device. Add it using the command A DEV:BS48-1.

This two core device dedicates one core to Abilis CPX and the other to the Hypervisor. The Hypervisor can run only Linux
OS virtual machines.

2.5.1. Physical and electrical specifications

Dimensions[mm]: 360x210x100;

Weight:3,5 Kg;

Power supply:+12 VDC, 50W.

2.6. Micro Abilis

Figure 2.6. Micro Abilis - Front view

11
Draft Abilis hardware Draft

Figure 2.7. Micro Abilis - Rear view

Micro Abilis is a non-expandable device equipped with:

• CPU: 500 MHz AMD Geode LX800

• RAM: 256 MB DDR

• BOOT DISK: CompactFlash 128MB

All Microabilis have three ethernet ports, two USB ports, 4 BRI, one COM port and a power out connector useful to supply
UMTS BOX2.

There are thwo versions of microabilis:

• equipped with 2 USB ports;

• equipped with 4 USB ports ().

Micro Abilis is a device available in two versions:

• 4 BRI + 4 POTS

• 4 BRI only

Warning
the version with only 4BRI still mounts 4 POTS ports. These ports ARE NOT connected so they are NOT
working!

Between the BRI ports and the POTS ports there are four integrated impedance matching adapters, so there's no more need to
use ISDN adapters. Each BRI port has two correspondig switches: one for output twisted pair and one for input twisted pair.
The default position is “ON” with the ISDN impedance activated (see figure below).

Note
All BRI ports are TE and not NT, so:

• a cross cable is needed to connect a PBX to Microabilis

• a straight cable is needed to connect an ISDN line to Microabilis

2.6.1. Led indications

Led Meaning State
LIVE Abilis Status LIVE and AUX leds flashing: startup

AUX Not used LIVE led flashing (1s ON - 1s OFF):

Abilis status is ok

12
Draft Abilis hardware Draft

Led Meaning State

AUX led: not used

2.6.2. Number of pluggable usb devices to the same USB 1.1 OHCI/
UHCI controller
This table shows the number of starmodems and UMTS/GSM boxes which can be connected to a Micro Abilis, depending on
adsl lines download bandwitdth.

The limit is caused by the isochronous mode. The condition to satisfy is (n. of lines) x (line download bandwidth) + (n. of
UMTS BOXes)< 9.6Mb.

Table 2.1. Table of the number of usb devices related to adsl lines download bandwidth

Devices* 1Mb/s 2Mb/s 4Mb/s 8Mb/s

N. of usb modem 1/8 1/7 1/5 1/1
Aethra/N. of
UMTSBOX
N. of usb modem 2/7 2/5 2/1 -
Aethra/N. of
UMTSBOX
N. of usb modem 3/6 3/3 - -
Aethra/N. of
UMTSBOX
N. of usb modem 4/5 4/1 - -
Aethra/N. of
UMTSBOX
N. of usb modem 5/4 - - -
Aethra/N. of
UMTSBOX
N. of usb modem 6/3 - - -
Aethra/N. of
UMTSBOX
N. of usb modem 7/2 - - -
Aethra/N. of
UMTSBOX
N. of usb modem 8/1 - - -
Aethra/N. of
UMTSBOX
N. of usb modem 9/0 - - -
Aethra/N. of
UMTSBOX

* Supposing to connect an USB hub.

Tip
Type the following command to know which devices are connected to a certain USB controller:

[09:14:40] ABILIS_CPX:d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 UHCI Virtual Root Hub 0.00 0
2 13FE 1D00 USB DISK 2.0 1.10 0.1

13
Draft Abilis hardware Draft

In the previous example, the usb DISK 2.0 is connected to the UCHI controller because the first number of
the UsbPortId is 0 (the same of UHCI controller).

2.6.3. Physical and electrical specifications

Dimensions[mm]: 234x163x66;

Weight:1.5 Kg;

Power supply:

2.7. Nano Abilis

Figure 2.8. Nano Abilis - Front view

Figure 2.9. Nano Abilis - Rear view

Nano Abilis is a non-expandable device equipped with:

• CPU: 500 MHz AMD Geode LX800

• RAM: 256 MB DDR

• BOOT DISK: CompactFlash 128MB

All Nano abilis have three ethernet ports, two USB ports, one COM port and a power out connector useful to supply UMTS
BOX2.

Nano Abilis is a device available in two versions:

• with one BRI port (with ISDN backup)

• without a BRI port (without ISDN backup)

The version with one BRI is equipped with an integrated impedance matching adapter (on the right side of the BRI port) so
there's no more need to use ISDN adapters. The BRI port has two correspondig switches: one for output twisted pair and one
for input twisted pair. The default position is “ON” with the ISDN impedance activated (see figure below).

14
Draft Abilis hardware Draft

Note
The BRI port is TE and not NT, so:

• a straight cable is needed to connect an ISDN line to Nanoabilis

Note
Nano abilis has no DSPs so transcoding is not allowed (there's no Packet Voice bandwidth optimization)

2.7.1. Led indications

Led Meaning State
LIVE Abilis Status LIVE and AUX leds flashing: startup

AUX Not Used LIVE led flashing (1s ON - 1s OFF):

Abilis status is ok

AUX led: not used

2.7.2. Number of pluggable usb devices

Refer to Section 2.6.2, “Number of pluggable usb devices to the same USB 1.1 OHCI/UHCI controller”.

2.7.3. Physical and electrical specifications

Dimensions[mm]: 234x163x45;

Weight: 1.20Kg;

Power supply:

15
Draft Abilis hardware Draft

2.8. MFIDE module

Figure 2.10. MFIDE module

The MFIDE module includes:

• Watchdog Processor;

• Status LED;

• 5 buttons: allow to administrate/diagnose the system (Compact-Flash formatting, up/downloading software, saving/
restoring configuration…);

• LCD display shows information about Abilis menu and the system status;

• Compact-Flash with 32/64/128/256 MB: contains the abilis object machine, the configuration and backup files, the
system's logs.

2.8.1. Watchdog Processor

The Watchdog is an independent microprocessor which is connected to the Abilis motherboard by IDE interface. It verifies
the constant presence of the so called “LIVE signal” generated by Abilis during its main operating cycle.

• When the cycle is regular, the LIVE signal is reset every second and the Watchdog sends every second a flashing signal on
the green LED (on the right end).

• If the cycle is not regular, the Watchdog issues a cold-reset of the motherboard, hence restarting the Abilis. The event text
I: WDL1 or I: WDL2 is added in the system log.

During the startup process (“boot”), the Watchdog stands by for one minute to permit loading the operating system and
initializing all the software modules.

2.8.2. Status LED

Figure 2.11. MFIDE LED

The MFIDE uses 4 state LEDs (RED, RED, GREEN,GREEN), controlled by the Watchdog.

16
Draft Abilis hardware Draft

Table 2.2. MFIDE status LEDs

LED Abilis state

All the LEDs are flashing in a right-left succession (Round Software loading
Robin)
All the LEDs are flashing at the same time Reset procedure
Only the GREEN LED #4 is flashing (1 flash per second) Abilis regularly operating
Any other combination Hardware failure

2.8.3. Buttons
Figure 2.12. MFIDE buttons

MFIDE includes 5 push buttons: “OK”, “Up”, “Down”, “Right”, “Left”. Their use is explained in the following table.

Table 2.3. MFIDE buttons

Button Action
OK Pressing the “OK” button it is possible to access information
about the menu currently showed on the LCD display. For
menus that require a confirmation, an affirmative answer will
be given to the request showed on the LCD display.
Up Every time the “Up” button is pressed, the display will show
the previous menu. By pressing it a lot of times, all the
menus will be shown in a cyclic way.
Down Every time the “Down” button is pressed, the display will
show the next menu. By pressing it a lot of times, all the
menus will be shown in a cyclic way.
Right Every time the “Right” button is pressed, the display will
show the sub-menu.
Left Every time the “Left” button is pressed, the display will go
back to the menu.

2.9. Abilis PCI boards and extension boards

Abilis can be supplied with several PCI cards, as many as the mother board can host (up to 4 PCI slots). Here are the
available cards:

17
Draft Abilis hardware Draft

Table 2.4. Abilis PCI boards and extension boards

Card name Function Notes

ESB2 4 Serial Synchronous Ports, HDLC Holds up to 4 modules (V24, V35, V11,
X21, E1/G.703)
CTI Voice-compression and H.100 engine To be supplied with QPRI o BRIx
modules, or connected to other cards
through H.100 bus
- QPRI Module 4 ports Primary Rate ISDN Needs CTI card
- BRI4 Module 4 ports Basic Rate ISDN Needs CTI card
- BRI8 Module 8 ports Basic Rate ISDN Needs CTI card
QPRIX - QPRI2 4 ports Primary Rate ISDN Stand-alone card
PB44X - PB44 4 ports Primary Rate ISDN 4 ports Stand-alone card+ extension
Basic Rate ISDN
BRI-HFC4 4 ports Basic Rate ISDN Stand-alone card
BRI-HFC8 8 ports Basic Rate ISDN Stand-alone card
BRIO 1 port Basic Rate ISDN Can only be supplied with Data Service
(backup, …)
POTS 4/8/16 From 4 to 16 FXS analog channels Can be supplied with CTI or BRI-HFC
card
VoIP 1/2 FXS analog channel + 1/2 DSP Stand-alone card
ETH100 IP router, Ethernet bridge -

2.9.1. ESB2
ESB2 card supplies Abilis with 4 synchronous ports you can configure up to 2,5 Mbps. They are generally used for CDN or
HDSL connections.

Figure 2.13. ESB2 card

As shown on the picture, the ESB2 card can hold up to 4 modules:

• RS232/V24

18
Draft Abilis hardware Draft

Figure 2.14. V24 module

• V35

Figure 2.15. V35 module

• V11

• X21

• E1/G.703

Figure 2.16. G703 module

The modules are plug-to-plug compatible and can be hold in any arrangement. The external devices are connected to
an “octopus” cable connected to the ESB2 card. This cable has 4 DB15 female connectors numbered from 0 to 3 which

19
Draft Abilis hardware Draft

correspond to the 1 to 4 modules and a HDB-62 female connector to connect the card. These connectors will be connected to
the corresponding adaptation cables V24/V35/X21/E1.

Each DB15 connector has 15 pins. The HDB-62 connector has 62 pins.

Figure 2.17. “Octopus” cable

The adapter cable is made by 7 twisted pairs. The cable is shielded.

Pin ESB2 Connector ESB2 Connector ESB2 Connector ESB2 Connector

pin - Port 0 pin - Port 1 pin - Port 2 pin - Port 3
1 1 6 11 16
2 22 22 32 37
3 23 28 33 38
4 24 29 34 39
5 25 30 35 40
6 26 31 36 41
7 2 7 12 17
8 4 9 14 19
9 43 48 53 58
10 44 59 54 59
11 45 50 55 60
12 46 51 56 61
13 47 52 57 62
14 3 8 13 18
15 5 10 15 20

Note
Pins 21 and 42 are not connected and can be used for the insertion key.

The port pins will have different meaning in fuction of the interface modules installed as shows in the following table:

20
Draft Abilis hardware Draft

Table 2.5. Meaning of pins depending of the module model

Couple(Twisted Port Pin Octopus V35/V11 V24 X21 E1/T1

pair) (DB15) wire color
1 Shield- no wire Shield + Gnd Shield Shield + Gnd unused
First 2,9 Brown,White- TX+,TX- TX,TXC TX+,TX- Txa,Txb
Brown
Second 3,10 Red,Black-Red RX+,RX- RX,RXC C+,C- Rxa,Rxb
Third 4,11 Yellow,Black- TXC+,TXC- RTS,DTECLK RX+,RX- unused,unused
Yellow
Fourth 5,12 Green,Black- RXC+,RXC- CTS,DTR I+,I- unused,unused
Green
Fifth 6,13 Blue,White- DTECLK DSR,RI CLK+,CLK- unused,unused
Blue +,DTECLK-
Sixth 7,14 Light DTR,RTS GND,unused DTECLK unused,unused
Blue,Light +,DTECLK-
Blue-Blue
Seventh 8,15 Light Blue-Dark CTS,DCD DCD,unused unused,unused unused,unused
Green,Light
Blue-Light
Green

Abilis software numbers the synchronous ports as shown in the table:

Table 2.6. ESB2 modules and corresponding software resources

HW Module SW Resource
mod. 0 SYNC-1
mod. 1 SYNC-2
mod. 2 SYNC-3
mod. 3 SYNC-4

Tip
Interesting chapters:Section 52.5, “How to configure HDSL/SHDSL connections using V.35/G.703
synchronous ports”

2.9.1.1. How to connect modules

The X1 connector of the each interface module is inserted into X3, X5, X7 or X9 (depending on the module number)
connector of the ESB2 card. The X2 connector of the each interface module is inserted into X4, X6, X8 or X10 (depending
on the module number) connector of the ESB2 card.

21
Draft Abilis hardware Draft

Figure 2.18. Placement of the module connectors on the ESB2 board

Each module has two side:

• the board side which is connected via X1 connector (50 pins);

• the line side which is connected via X2 connector (26 pins).

22
Draft Abilis hardware Draft

Figure 2.19. Example: position of connectors on a X21 module

2.9.1.2. Physical and electrical specifications

Dimensions[mm]: 245x106;

Weight: 0.15Kg;

Power supply:

23
Draft Abilis hardware Draft

2.9.2. CTI
The CTI boards are machines to deal with ISDN and VoIP phone communications. They provide TDM and VoIP switching,
voice codification and packetization, echo cancellation.

2.9.2.1. CTI-HA
CTI-HA cards are obsolete.

CTI-HA cards host 4 slots for DSP modules, each of them can hold 0, 1, 2 or 4 DSP (Digital Signal Processor, chip for voice
compression/packetization). On the right side of the card there is a slot for a daughterboard (QPRI, BRI-4 or BRI8 modules ,
respectively for ISDN Primary Rate Interface (PRI) or Basic Rate Interface (BRI) support).

Figure 2.20. CTI-HA

On the upper side of the CTI card there is a H.100 interface, which enables the connection of several CTI cards between each
other (besides through PCI bus) . The H.100 bus creates a system with a capacity of up to 2048 simultaneous calls.

Tip
Interesting chapters:Section 3.2, “ISDN Basic Rate Interface (BRI) connection”

2.9.2.2. QPRI Module

The QPRI module hosts 4 primary interfaces (PRI) and is to be installed on a CTI card.

For the ISDN-PRI (S2M) ports there is no standard physical interface. The Abilis cards use RJ45 sockets with the same
signal arrangement as the one used to access to BRI NT:

24
Draft Abilis hardware Draft

Table 2.7. QPRI module – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

Each interface presents a 120 ohm balanced impedance.

Each port can be configured as NT (Network Termination) or TE (Terminal Equipment).

2.9.2.3. BRI8 and BRI4 Module

BRI8 module, assembled on a CTI card, makes available 8 ports BRI ISDN Basic Rate (configurable S0/T0) ports). BRI4
and BRI8 modules are almost identical, but BRI4 supports only 4 ports (it uses a different chip).

Figure 2.21. BRI4 Module

Warning
Although only one PCI slot is used for the electrical connection on the external part of the cabinet, the eight
BRI ports take as much place as two slots (mechanical connection).

The BRI8 and BRI4 modules mount four RJ45 sockets with the following pinout:

25
Draft Abilis hardware Draft

Table 2.8. BRI-HFC – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

You can configure every port at logical level like NT (Network Termination) or TE (Terminal Equipment).

The BRI ports permit the use of impedance matching adapter.

Tip
Interesting chapters:

Chapter 42, CTI System;

Section 53.1, “How to configure ISDN ports to connect PBX or ISDN lines”;

Section 51.9.1, “How to recognize PCI cards model”.

2.9.3. QPRIX
The QPRIX is a stand-alone card, it has 4 primary interfaces (ISDN-PRI) and supports up to 16 DSP for 64 compressed calls.
Besides echo canceller (EC) is available up to 32 ms but it can raise up to 128 ms in the version with the additional Octasic
chip (EEC).

The maximal number of HDLC B-channels is greater then the QPRI2 and it has been extended from 32 to 60.

Through H.100 bus it can also be connected to other cards of the CTI category.

Figure 2.22. QPRIX

26
Draft Abilis hardware Draft

For the ISDN-PRI (S2M) interfaces no standard physical port is specified. The Abilis QPRIX use RJ45 sockets with the same
signal arrangement as the one used to access to BRI NT.

Table 2.9. QPRIx – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

Each interface presents a 120 ohm balanced impedance. Each port can be configured as NT (Network Termination) or TE
(Terminal Equipment).

2.9.3.1. Physical and electrical specifications

Dimensions[mm]: 312x106;

Weight: 0.20Kg;

27
Draft Abilis hardware Draft

Table 2.10. Power consumption

Condition Condition Consumption (mA)

Main 3.3 V regulator After reset 920
Main 3.3 V regulator After C6412 firmware upload 1000
Main 3.3 V regulator After FPGA firmware upload 1350
Main 3.3 V regulator After QFALC activation 1560
Main 3.3 V regulator with 36 HDLC channels up&running 1570
Main 3.3 V regulator with 64 AC channels up&running 1990
Main 3.3 V regulator with all QFALC ports 1630
connected&performing traffic
Audiocodes' 1.8 V regulator After reset 100
Audiocodes' 1.8 V regulator After KERNEL and PROGRAM 960
download
Octasic's 1.8V regulator After reset 50
Octasic's 1.8V regulator After firmware download, during BIST 140
FPGA's 1.2 V regulator Always 330
C6412's 1.2 V regulator Always 380
C6412's 2.5 V regulator Always 60

2.9.4. QPRI2
The QPRI2 is a stand-alone card, it has 4 primary interfaces (ISDN-PRI) and supports up to 6 DSP for 24 compressed calls.

Through H.100 bus it can also be connected to other cards of the CTI category.

Figure 2.23. QPRI2

For the ISDN-PRI (S2M) interfaces no standard physical port is specified. The Abilis QPRI2 use RJ45 sockets with the same
signal arrangement as the one used to access to BRI NT.

28
Draft Abilis hardware Draft

Table 2.11. QPRI2 – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

Each interface presents a 120 ohm balanced impedance. Each port can be configured as NT (Network Termination) or TE
(Terminal Equipment).

2.9.4.1. Physical and electrical specifications

Dimensions[mm]: 312x106;

Weight: 0.20Kg;

Power supply:

2.9.5. PB44X
The PB44X card has 4 primary interfaces (ISDN-PRI) and, by means of a daugtherboard (BRI4ADD, see photo), 4 ISDN
Basic Rate (ISDN-BRI) interfaces. All interfaces are freely configurable as NT / TE.

It supports up to 16 DSP for 64 compressed calls and can be connected to other CTI cards through the H.100 bus.

Tip
For information about the connection between Abilis and ISDN Basic Rate Interface (BRI) lines refer to
Section 3.2, “ISDN Basic Rate Interface (BRI) connection”.

29
Draft Abilis hardware Draft

Figure 2.24. PB44X

The PB44X cards use RJ45 plugs with the following pinout, either on the main board (4 PRI ports) or on the extension (4
BRI ports).

Table 2.12. PB44X – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

Each PRI interface presents a 120 ohm balanced impedance. Each port can be configured as NT (Network Termination) or
TE (Terminal Equipment). The BRI ports have to use an impedance matching adapter.

Warning
Although only one PCI slot is used for the electrical connection on the external part of the cabinet, the
additional 4 BRI ports occupy an additional slot (for mechanical connection only).

2.9.5.1. Physical and electrical specifications

Dimensions[mm]: 312x106;

Weight: 0.20Kg;

Power supply:

30
Draft Abilis hardware Draft

2.9.6. PB44
The PB44 card has 4 primary interfaces (ISDN-PRI) and, by means of a daugtherboard (BRI4ADD, see photo), 4 ISDN
Basic Rate (ISDN-BRI) interfaces. All interfaces are freely configurable as NT / TE.

It supports up to 6 DSP for 24 compressed calls and can be connected to other CTI cards through the H.100 bus.

Tip
For information about the connection between Abilis and ISDN Basic Rate Interface (BRI) lines refer to
Section 3.2, “ISDN Basic Rate Interface (BRI) connection”.

Figure 2.25. PB44

The PB44 cards use RJ45 plugs with the following pinout, either on the main board (4 PRI ports) or on the extension (4 BRI
ports).

31
Draft Abilis hardware Draft

Table 2.13. PB44 – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx - (inbound)
7 N.C.
8 N.C.

Each PRI interface presents a 120 ohm balanced impedance. Each port can be configured as NT (Network Termination) or
TE (Terminal Equipment). The BRI ports have to use an impedance matching adapter.

Warning
Although only one PCI slot is used for the electrical connection on the external part of the cabinet, the
additional 4 BRI ports occupy an additional slot (for mechanical connection only).

2.9.6.1. Physical and electrical specifications

Dimensions[mm]: 312x106;

Weight: 0.20Kg;

Power supply:

2.9.7. BRI-HFC4 / BRI-HFC8

2.9.7.1. BRI-HFC4 / BRI-HFC8
The BRI-HFC4 card does the same work as a composite system made with: CTI board + BRI-4 (or BRI-8) module + DSP,
but its cost is lower. It supports one/two DSP to manage four or eight simultaneous VoIP calls.

The DSPs now supports g.729 codec; besides all BRI-HFC cards are equipped with H100 bus.

Tip
For information about the connection between Abilis and ISDN Basic Rate Interface (BRI) refer to
Section 3.2, “ISDN Basic Rate Interface (BRI) connection”.

32
Draft Abilis hardware Draft

Figure 2.26. BRIHFC

The BRI-HFC cards use RJ45 plugs with the following pinout :

Table 2.14. BRI-HFC – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx # (inbound)
7 N.C.
8 N.C.

Each is freely configurable (at the logical level) like NT (Network Termination) or TE (Terminal Equipment). The BRI ports
require an impedance matching adapter.

Tip
Interesting chapters: Section 51.9, “How to know which kind of hardware is mounted on Abilis”.

2.9.7.2. Physical and electrical specifications

Dimensions[mm]: 223x106;

Weight: 0.17 Kg;

Power supply:

33
Draft Abilis hardware Draft

2.9.7.3. BRI-HFC4 / BRI-HFC8 (old model)

The BRI-HFC4 (BRI-HFC8) card does the same work as a composite system made with: CTI board + BRI-4 (or BRI-8)
module + DSP, but its cost is lower. It supports one/two DSP to manage four or eight simultaneous VoIP calls.

Unlike BRI-HFC4/BRI-HFC8, the DSPs doesn't support g.729 codec; besides all old model of BRI-HFC cards are available
in two versions:

• equipped with H100 bus

• not equipped with H100 bus

Tip
For information about the connection between Abilis and ISDN Basic Rate Interface (BRI) refer to
Section 3.2, “ISDN Basic Rate Interface (BRI) connection”.

Figure 2.27. BRIHFC (old model)

The BRI-HFC cards use RJ45 plugs with the following pinout :

34
Draft Abilis hardware Draft

Table 2.15. BRI-HFC – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Rx + (inbound)
4 Tx + (outbound)
5 Tx - (outbound)
6 Rx # (inbound)
7 N.C.
8 N.C.

Each is freely configurable (at the logical level) like NT (Network Termination) or TE (Terminal Equipment). The BRI ports
require an impedance matching adapter.

Tip
Interesting chapters: Section 51.9, “How to know which kind of hardware is mounted on Abilis”.

2.9.8. BRIO
The card ISDN BRIO supports only one BRI TE port. It is mainly used for VPN data backup on ISDN lines.

Tip
For information about the connection between Abilis and ISDN lines refer to Section 3.2, “ISDN Basic Rate
Interface (BRI) connection”.

Figure 2.28. BRIO

This card uses only one RJ45 plug with a pinout inverted (TE) respect to BRI4/BRI8 modules :

35
Draft Abilis hardware Draft

Table 2.16. BRIO – RJ45 pinout

Pin Signal
1 N.C.
2 N.C.
3 Tx + (outbound)
4 Rx + (inbound)
5 Rx - (inbound)
6 Tx - (outbound)
7 N.C.
8 N.C.

Can be connected to a NT1 network termination unit through a straight “cat 5” cable. The BRI ports require an impedance
matching adapter.

Tip
Interesting chapters: Section 3.2, “ISDN Basic Rate Interface (BRI) connection”; Chapter 42, CTI System.

2.9.8.1. Physical and electrical specifications

Dimensions[mm]: 120x61;

Weight: 0.05Kg;

Power supply:

2.9.9. POTS 4/8/16

The POTS cards belong to the CTI family and are used to connect analog telephone to the Abilis system. POTS are available
with 4 , 8 or 16 FXS (BCA) interfaces. Through the H.100 bus, when installed on the same Abilis, several POTS cards
behave like a single module (it works also with CTI or BRI-HFC cards). In this way Abilis becomes a powerful PBX system.

36
Draft Abilis hardware Draft

Figure 2.29. POTS

POTS cards have four RJ45 sockets. Each socket is to be used with an octopus cable (one RJ45 plug <-> four RJ11 plugs).
Each RJ11 is for one telephone.

Figure 2.30. “Octopus” POTS Cable

The octopus for POTS use the following pinout.

Figure 2.31. “paraOctopus” POTS Cable pinout

37
Draft Abilis hardware Draft

Table 2.17. Octopus cable pinout

RJ45 Pin RJ11 Pin

1 (a1) DEVICE 1 #1 - 1
2 (b1) DEVICE 1 #1 - 2
3 (a2) DEVICE 2 #2 - 1
4 (b2) DEVICE 2 #2 - 2
5 (a3) DEVICE 3 #3 - 1
6 (b3) DEVICE 3 #3 - 2
7 (a4) DEVICE 4 #4 - 1
8 (b4) DEVICE 4 #4 - 2

Note
A variable delay to the start of ring signals is used to prevent a current overload in case of multicast groups
with large number of Pots ports. The delay is in range of 20 to 140 msec.

Tip
Interesting chapters:

Section 51.9.1, “How to recognize PCI cards model”;

Chapter 42, CTI System;

Section 53.2, “How to configure FXS (POTS) ports for analog telephones or fax machines”.

2.9.9.1. Physical and electrical specifications

Dimensions[mm]: 312x106;

Weight: 0.27Kg;

Power supply:

2.9.10. POTS protection

This board allows to protect POTS ports from external overvoltages and overcurrents such as the ones generated from
lightnings.

Its equipped with:

• four RJ45 which must be connected to the POTS 4/8/16 card;

38
Draft Abilis hardware Draft

• four RJ45 which must be connected to the POTS phones.

Tip
Interesting chapters:

Section 3.6, “POTS protection connection”;

Section 2.9.9, “POTS 4/8/16”;

Chapter 42, CTI System;

Section 53.2, “How to configure FXS (POTS) ports for analog telephones or fax machines”.

2.9.11. VoIP
The VoIP cards belong to the CTI family, too. They are used to connect two analogue terminals to the Abilis. They have two
RJ11 sockets with FXS electrical interface and they support two VoIP calls.

Figure 2.32. VoIP

The ports of Voip cards use the following pinout:

Table 2.18. VoIP – RJ11 pinout

Pin Signal
1 N.C.
2 Analog signal (ring)
3 Analog signal (tip)
4 N.C.

Tip
VoIP card is an analog device, so on signals pinout is not requested a specific polarity.

Tip
Interesting chapters:

Section 51.9.1, “How to recognize PCI cards model”;

Chapter 42, CTI System;

39
Draft Abilis hardware Draft

Section 53.2, “How to configure FXS (POTS) ports for analog telephones or fax machines”.

2.9.11.1. Physical and electrical specifications

Dimensions[mm]: 168x66;

Weight: 0.1Kg;

Power supply:

2.9.12. ETH100
The ETH100 card provides a Fast Ethernet interface with Auto-Mode (10–100 Mbps) and Auto-TP (signals polarity)
features. Several ETH100 cards can be installed into the same CPX.

Figure 2.33. Ethernet card

Tip
Interesting chapters: Section 19.3, “IP Resources”; Section 52.2, “How to activate a new ethernet port”.

2.9.12.1. Physical and electrical specifications

Dimensions[mm]: 112x41;

40
Draft Abilis hardware Draft

Weight: 0.04Kg;

Power supply:

2.10. USB devices

2.10.1. ADSL modem
The ADSL USB modem enables one or more ADSL connections (one for each modem) directly on the Abilis without
installing any additional router. Up to 6 modems can be installed into the same Abilis.

Actually three models are supported:

• Abilis-5800UB (Supported from 7.0.6 and from 6.5.13);

• Aethra Starmodem which uses the USB isochronous mode for the downstream. (Supported from 7.0.3 and from 6.5.11);

• Thomson Speedtouch.

Figure 2.34. Abilis-5800UB

41
Draft Abilis hardware Draft

Figure 2.35. Aethra Starmodem

Figure 2.36. Thompson Speedtouch

Warning
The number of ADSL StarModem which can be connected to the same USB 1.1 OHCI/UHCI controller is
limited. Refer to Section 2.10.1.3, “Isochronous mode” to havo more information about isochronous mode.

Tip
Interesting chapters:

Section 3.5, “ADSL modem connection”;

Chapter 10, ADSL modem;

Section 52.4, “How to configure ADSL connections using USB modems”.

2.10.1.1. Led indications for Aethra Starmodem

Led Meaning State

Power Power state. OFF: USB calbe disconnected.

ON: USB calbe connected.

ADSL ADSL state. OFF or blinking GREEN: device not
able to synchronize.

ON: adsl connection established

Data Data exchange. Blinking: during data exchange.

2.10.1.2. Led indications for Thomson Speedtouch

Led Meaning State

Power Power state. Both leds OFF: modem disconnected.

DSL DSL State. Power led is RED or blinking AMBER:

device not working properly.

Power led is GREEN and DSL led is

OFF or blinking GREEN: device not
able to synchronize.

42
Draft Abilis hardware Draft

2.10.1.3. Isochronous mode

WARNINGS about isochronous mode:

• USB 1.1 interfaces are handled with one OHCI/UHCI controller every 2 ports. Usually the ports that are close each other
belongs to the same UHCI/OHCI controller;
• USB 2.0 interfaces are handled with one EHCI controller for all the ports. In some rare cases, or when a PCI add on card is
used, more EHCI controllers can be present;
• isochronous mode reserves bandwidth on each USB controller. This means that the bandwidth is permanently robbed to
other devices connected to the same controller;
• the maximal theoretical USB bandwidth on USB 1.1. FULL SPEED is 12 Mbit/sec;
• the maximal theoretical USB bandwidth on USB 2.0. HIGH SPEED is 480 Mbit/sec;
• some bandwidth must be left free for interrupt and bulk transaction;
• in Abilis CPX the maximal isochronous bandwidth limit for USB 1.1 is 9.6 Mbit/sec;
• in Abilis CPX the maximal isochronous bandwidth limit for USB 2.0 is 384 Mbit/sec;
• in Abilis CPX the isochronous bandwidth is dynamically reserved depending on the actual downstream (RX) speed, in 8
discrete step which are roughly 1,2,3,4,5,6,7,8 Mbit/sec.

As a result there is a limitation to the number of ADSL StarModem which you can connect to the same USB 1.1 OHCI/UHCI
controller, as well as combination of StarModem with GSM-BOX and UMTS-BOX/BOX2, for example:

• one StarModem at maximal speed and one UMTS-BOX/BOX2 are supported within a OHCI/UHCI controller;

• two StarModem connected to 4 mbit/sec lines and one UMTS-BOX/BOX2 are also supported.

2.10.2. UMTS-BOX2
Figure 2.37. UMTS-BOX2

UMTS-BOX2 is a device which provides two independent interfaces to the GSM/UMTS mobile network. It can be connected
to ABILIS router through an USB cable and supports full Voice, Data and SMS service.

Generally UMTS-BOX2 works with a SIM inserted in it, but using the sim remotization the device can use a sim located
anywhere in the world.

The most important benefits of sim remotization are:

• centralization of the SIM when a number of UMTS-BOX2 are dispersed in branch offices;

• the management of sims is very malleable because the association between SIM and UMTS-BOX2 can be changed using
software commands;

• the association between SIM and UMTS-BOX2 can be changed by external applications that follow arbitrary customer
rules.

The following steps are executed when connecting umtsbox2:

1. UMTS-BOX2 gets connected to abilis after 15 seconds when UMTS-BOX2/Abilis boots;

2. once UMTS-BOX2 gets connected, the communication with Abilis starts after 5 seconds;

3. If Abilis doesn't drive UMTS-BOX2, UMTS-BOX2 waits 40 seconds and then resets itself. After the reset, the procedure
starts from point #1.

4. If Abilis drives UMTS-BOX2 and the sim-container is inside the module and a sim isn't in the container, the module resets
itself. If the sim is remote this doesn't happen;

5. a module resets itself every time a remote sim is connected. If the UMTS-BOX2 is connected to a UHCI controller,
the reset can cause the disconnection of the other module. Sim-remotization must not be used when UMTS-BOX2 is
connected to an UCHI controller.

43
Draft Abilis hardware Draft

Tip
Interesting chapters:

Section 3.7, “UMTS-BOX connection”;

Chapter 11, GSM-UMTS BOX.

2.10.2.1. Led indications

Led Meaning State

Act(Module1/Module2) Umts module activity. OFF: module off or inactive.

ON: module ON, not registered with the

network or communicating.

ON FLASHING: module ON,

registered with the network but inactive
SIM 1a/1b/2a/2b Presence of sims inside 1a/1b/2a/2b ON: sim inserted while UMTS module
slots is reading the sim.

OFF: not inserted sim or not selected

sim or SIm remotization active

NOTE: the led is OFF even if the sim

is inserted and the UMTS module is not
reading the sim
PWR Power state PWR OFF and USB OFF: power cable
may be correctly connected but it
USB USB state doesn't matter; USB disconnected.

PWR OFF and USB ON: power

disconnected or usb not driven by
software; USB connected.

POWER ON and USB ON: power

correctly connected; USB connected
and driven by software.

NOTE: if USB cable is disconnected,

PWR led is always OFF even if the
power cable is correctly connected.

2.10.2.2. Physical and electrical specifications

Dimensions: 234x163x45;

Weight: 1.20Kg;

Power is provided both via USB to HUB, CODEC and PIC and with the additional power cable to SimCom modules.
SimCom modules absorpt some current from the USB anyway, because of an internal -USB-powered- USB-to-serial
converter interface chip.

Table 2.19. Power consumption on the USB

Device status Supply voltage (V) Consumed current (mA)

USB connected, modules powered 5 185
down
USB connected, module1 powered up 5 285
USB connected, module1 and module2 5 385
powered up

44
Draft Abilis hardware Draft

Table 2.20. Power consumption on the Power supply cable

Device status Supply voltage (V) Consumed current (mA)

Modules in power down 5/12 100/50
Both modules in stanbdy 5/12 250/100
Both modules during a phone call 5/12 650/300
Both modules during HSDPA 5/12 1900/640
download, 23dB power (max power)

2.10.3. GSM Box

The GSM Box is an add-on for the ABILIS CPX which provides an interface between the GSM and the fixed (private/public)
telephone network.

Figure 2.38. GSM-BOX

Thanks to the Abilis GSM Box mobile phones can be considered as “mobile extensions” of the company's telephone system.
Additionally, the Abilis “Least Cost Router” permits to select the cheapest route for any call.

The GSM Box is connected to the Abilis by means of an USB interface (see Section 3.7, “UMTS-BOX connection”), thus
requiring no additional telecom port in the ABILIS router and preservinging digital voice quality.

The main features of the GSM Box are:

• two simultaneous channels;

• works even without SIM cards;

• high-fidelity voice;

• call-back;

• unlimited Least Cost Routing (LCR);

• DTMF dial-in with voice message;

• call data records;

• SMS to e-mail;

• SMA connector with SMA detachable antennas.

There are two versions of GSM Box:

• One channel device (doesn't require an external power supply.Power is supplied by usb cable);

• two channels device (require an external 5V-DC power supply).

45
Draft Abilis hardware Draft

Tip
Interesting chapters: Chapter 11, GSM-UMTS BOX.

2.10.3.1. Led indications

Led indications for a two channels device:

Led Meaning State

POWER Power state. OFF: the 5V-DC are not provided.

ON: the 5V-DC are provided.

USB active USB state. OFF: USB connection not available.

ON: USB connection available.

Channel 1 GSM module state OFF:module powered down.

Channel 2 Blinks 0.6 s ON and 0.6 s OFF: module

powered up, loading from SIM card or
registering to the network.

Blinks 0.2 s ON and 3 s OFF: module

registered to the network and idle.

ON: GSM activity (a phone call,

internet traffic)

Led indications for a one channel device:

Led Meaning State

POWER Power state. OFF: the 5V-DC are not provided.

ON: the 5V-DC are provided.

USB active USB state. OFF: USB connection not available.

ON: USB connection available.

Channel 1 GSM module state OFF:module powered down.

Blinks 0.6 s ON and 0.6 s OFF: module

powered up, loading from SIM card or
registering to the network.

Blinks 0.2 s ON and 3 s OFF: module

registered to the network and idle.

ON: GSM activity (a phone call,

internet traffic)
Channel 2 GSM module state NOTE: it's always OFF

2.10.3.2. Physical and electrical specifications

Dimensions:

Weight:

Power supply:

46
Draft Abilis hardware Draft

2.10.4. UMTS-Key
This device allows to exchange data and sms using an UMTS key. It can be used as backup line when the main one fails, or
to establish a connection toward Internet when calling an ISDN number (data call back).

Figure 2.39. UMTS-Key

Tip
Interesting chapters:

Chapter 15, UMTS Key;

Section 53.17, “How to configure DATA CALL BACK using an UMTS Key, calling an ISDN number”.

2.10.5. Citobox
Figure 2.40. Citobox - Front view

47
Draft Abilis hardware Draft

Figure 2.41. Citobox - Rear view

Citobox allows to connect Abilis to a doorphone system integrating it with your computer telephony system.

It provides 8 digital inputs and 4 digital outputs which can be used to drive other hardware (to open a gate, to switch on
lights, etc.).

A Citobox allows to:

• connect one outdoor system and one indoor system, or two outdoor systems;

• get a call when person at the door presses the ring button;

Note
The communication is cut off when the called party hangs up or when the interface timer expires. This
timer is not programmable and its default value is 10 minutes.

• order the door opening by pressing a key that produces DTMF on your phone;

• use the inputs for up to 8 additional ring buttons. Each input will cause to dial a different number;

• view the state of inputs/output through the GPIO module, which allows interfacing with an external application through
HTTP/XML.

On the front there are:

• 2 interfaces (each interface can be used to connect a doorphone system (indoor + outdoor, outdoor + outdoor, indoor +
indoor);

• 8 digital inputs;

• 4 digital output (normally open and normally closed relays);

• 2 analog inputs (each analog input can be configured by installing an analog adaptation module inside the CITOBOX.
When no module is present, the analog inputs are not usable).

The device can accept both 5V and 12V power supply.

Tip
Interesting chapters:

Section 3.8, “Citobox connection”;

Chapter 13, Citobox.

2.10.5.1. Front Panel and connector pinout

The front panel contains the trimmers for the volume regulation, the doorphone interface connectors and the I/O connectors.

The trimmers allow to regulate the volume of the microphone and the speaker (clockwise: rise the volume, counterclockwise:
lower the volume).

The following picture shows the trimmers and the connector pinout.

48
Draft Abilis hardware Draft

Figure 2.42. Citobox trimmers and pinout

Each doorphone interface contains two relays, RA and RB, whose "normally close" pins are closed and "normally open" pins
are open when there is no active communication on the interface (default state).

49
Draft Abilis hardware Draft

Pin number Pin name Description Direction

1 RA_COM RA relay, common pin Clean contact
Table 2.21. Citobox pinout
2 RA_NC RA relay; when the Clean contact
communication on the
corresponding Doorphone
interface is inactive, this
pin is short-circuited with
RA_COM; when the
communication is active, this
pin is not connected
3 RB_COM RB relay, common pin Clean contact
4 RB_NC RB relay; when the Clean contact
communication on the
corresponding Doorphone
interface is inactive, this
pin is short-circuited with
RB_COM; when the
communication is active, this
pin is not connected
5 MIC Microphone input; connect to Input
the doorphone's microphone
6 GND Ground reference -
7 SPKR Speaker output; connect to Output
the doorphone's speaker
8 CALL CALL button; any DC or Input
AC signal, in the range
2.5-to-12.5 V on this input
triggers a CALL event on the
corresponding Doorphone
interface
9 RA_NO RA relay; when the Clean contact
communication on the
corresponding Doorphone
interface is inactive, this pin
is not connected; when the
communication is active, this
pin is short-circuited with
RA_COM
10 RB_NO RB relay; when the Clean contact
communication on the
corresponding Doorphone
interface is inactive, this pin
is not connected; when the
communication is active, this
pin is short-circuited with
RB_COM
11 FILTER_IN Auxiliary pin, leave -
disconnected if unused
(connect to 12 V DC in a
special BTicino connection
scheme in order to provide
power to the Microphone
line)
12 FILTER_OUT Auxiliary pin, leave -
disconnected if unused
(connect to MIC in a special
BTicino connection scheme,
in order to provide power to
the Microphone line)

50
Draft Abilis hardware Draft

The digital inputs are general purpose, so they can be used to connect any kind of hardware (additional ring buttons, digital
sensors, etc.). Refer to Section 13.3, “CTI port configuration” to have more information about their configuration.

Table 2.22. Digital input pinout

Pin Description
IN_X (a) Negative
IN_X (b) Positive

The digital outputs can drive any kind of device, accordingly with the electrical specifications.

The digital outputs are relay-based and have 3 volt free contacts (i.e. dry contacts, i.e. clean contacts): common, normally
open and normally closed.

The OUT_NO is the normally open pin. When the DIG_OUT is set to 0, OUT_COM and OUT_NO are disconnected, while
when DIG_OUT is set to 1 they are short-circuited.

The OUT_NC is the normally closed pin. When the DIG_OUT is set to 0, OUT_COM and OUT_NC are short-circuited,
while when DIG_OUT is set to 1 they are disconnected.

Figure 2.43. Digital output

Warning
Output relays support:

• a maximum switching current of 1 A (the moment when the relay is turned into CLOSED);

• a maximum carrying current of 2 A (during normal operation, stable CLOSED);

• DC voltage max. 220 V, AC voltage max. 250 V.

Table 2.23. Digital output pinout

Pin Description
OUT_COM Common pin
OUT_NO Normally opened digital out
OUT_NC Normally closed digital out

2.10.5.2. Led indications

Led Meaning State

Power Power state. OFF: external power supply
disconnected or faulty.

51
Draft Abilis hardware Draft

Led Meaning State

ON: external power supply is
connected.
Active USB state. OFF: USB cable disconnected.

Blinks fast (0.5 s ON, 0.5 s OFF):

Abilis is not driving the device.

Blinks slowly (3 s ON, 3 s OFF): Abilis

software is correctly driving the device.

2.10.5.3. Functional block scheme

The CITO-BOX is composed by two parts: the CITO part and the IO part. They are managed by two separated PIC
microcontrollers: the CITO-PIC and the IO-PIC.

The CITO part offers two completely separated interfaces for doorphones. The IO part offers 8 digital inputs, 4 digital
outputs (clean contacts) and two analog inputs (available only if an analog adaptation module is present).

Each interface of the CITO part is mainly composed of 4 analog pins: SPKR, MIC, GND, CALL, which must be connected
respectively to the speaker, microphone, ground and call button signals of the doorphone.

When a continuous or alternate voltage (voltange range 2.5V - 12V, frequency range: 0Hz - 100Hz) is applied to the CALL
pin, the CITOBOX informs the Abilis, which activates the voice communication on the corresponding interface. The status
of the relays RA and RB follows the one of the communication. RA_NC and RB_NC are closed when the communication is
inactive and open when the communication is inactive, being the status of no communication the "normal" status. RA_NO
and RB_NO follow the opposite behaviour.

The volume of the microphone and the speaker can be manually regulated with the corresponding trimmers, all of which are
externally accessible on the front. The speaker and the microphone are decoupled by a transformer.

Each digital output of the IO part is a volt free contact (clean contact) and can be driven separately by the Abilis. Each output
is available both as normally closed and normally open. It supports a maximum switching current of 1 A (transition current
during the relay closure), a maximum carrying current of 2 A (after the relay closure, when the relay is stable), 220V DC
max. voltage and 250V AC max. voltage.

Each input of the IO part is separated. It can be configured as clean contact input (default) or optoisolated input (use voltages
in the range 5V - 12V). Each input can be manually configured through its corresponding couple of jumpers.

52
Draft Abilis hardware Draft

Figure 2.44. Citobox - Block scheme

53
Draft Abilis hardware Draft

2.10.5.4. Jumpers configuration (only for PCB Ver. 1.1)

Jumpers configuration allows to choose between clean contact and opto-isolated digital inputs. Jumpers configuration
is available only in PCB Ver. 1.1.The PCB version is reported on the case label. PCB version 1.0 does not allow the
configuration of digital inputs. Its digital inputs are only compatible with volt free outputs (clean contacts).

Figure 2.45. Jumpers position on PCB

54
Draft Abilis hardware Draft

Figure 2.46. Jumpers settings

2.10.5.5. Physical and electrical specifications

Dimensions: 234x163x45;

Weight: 1.20Kg;

Power supply:

2.10.6. Simbox

Simbox is a device providing an USB interface to 16 or 32 SIM phone cards.

The potential of this device significantly increases if used with UMTS-BOX2 because of sim remotization.

55
Draft Abilis hardware Draft

Sim remotization allows to use remote sim cards inserted in a Simbox with an UMTS BOX2 via IP network.

Note
Simbox is not equipped with any GSM/UMTS modem, so it cannot replace an UMTSBOX. Simbox works
togheter with one or more UMTSBOXes.

There are two versions of Simbox:

• with 16 sockets for GSM/UMTS sims

• with 32 sockets for GSM/UMTS sims.

Tip
Interesting chapters:

Section 3.9, “Simbox connection”;

Chapter 12, Simbox.

2.10.6.1. Led indications

Led Meaning State

Power Power state. OFF: external power supply
disconnected or faulty.

ON: external power supply is

connected.
SIM #nn SIM #nn state. OFF: SIM #nn card not used by the
Abilis, even if the SIM card is inserted.

ON: SIM #nn card used by the Abilis.

2.10.6.2. Functional block scheme

The SIMBOX-32 is composed of two boards: the master board and the slave board. the SIMBOX-16 is composed of the
master board. Each board allows to plug up to 16 sim cards.

Communication between FPGA and PIC is implemented on the PIC's Streaming Parallel Port (SPP) peripheral. This port
provides a fast 8-bit bus, where it is possible to connect more slave peripherals.

56
Draft Abilis hardware Draft

Figure 2.47. Simbox - Block scheme

57
Draft Abilis hardware Draft

Tip
Interesting chapters:

Section 3.9, “Simbox connection”;

Chapter 12, Simbox.

2.10.6.3. Physical and electrical specifications

Dimensions:

Weight:

Table 2.24. Power consumption

Condition Current consumption with Current consumption

PSU = 5 V (old version) with PSU = 12 V
SIM-BOX-16, all SIM cards off 568 300
SIM-BOX-16, all SIM cards with Vcc 740 410
ON
SIM-BOX-32, all SIM cards off 1000 540
SIM-BOX-32, all SIM cards with Vcc 1300 720
ON

2.10.7. RJ Switch

RJS is an ISDN, ADSL or ethernet switch. It's equipped with:

• one USB port

• 8 ports (each port includes 3 ISDN/ethernet ports)

This device checks the keepalive, so if the master (Mx) doesn't reply to the keepalive signal, the link is assumed to be down
and the line is switched to the backup device (Bx) until the link is up again.

RJS can handle up to 8 lines.

58
Draft Abilis hardware Draft

Note
Only the central pins 4,5 and 3,6 are switched! Pins 1,2 and 7,8 are not connected. Refer to chapter
Section 3.10.1, “Connection examples” to have more information about connection.

There are two versions of RJS:

• accepting only 5V power supply;

Warning
Connecting a power supply providing more than 5V-DC damages the device!

• accepting 12V power supply

Tip
Interesting chapters:

Section 3.10, “RJS connection”;

Chapter 14, RJS - RJ Switch.

2.10.7.1. Led indications

Led Meaning State

Power Power state. OFF: external power supply
disconnected or faulty.

ON: external power supply is

connected.
Active Device state. Blinks fast (0.5 s ON, 0.5 s OFF):
Abilis is not driving the device.

Blinks slowly (3 s ON, 3 s OFF): Abilis

software is correctly driving the device.

2.10.7.2. Functional block scheme

The RJ Switch is equipped with a PIC microcontroller which controls 8 onboard switches using the control lines. It is
installed on the board and it's able to switch each LINE port to the correspondent main port or backup port.

This board contains a watchdog which must be driven by the main Abilis via USB; when the main Abilis stops sending LIVE
signals to the board, the PIC understands that the main Abilis is failing and switches the line to the backup Abilis. The board's
switch core/watchdog is based on a Microchip PIC18F2450.

59
Draft Abilis hardware Draft

Figure 2.48. RJ Switch - Block scheme

Tip
Interesting chapters:

Section 3.10, “RJS connection”;

Chapter 14, RJS - RJ Switch.

2.10.7.3. Physical and electrical specifications

Dimensions:

Weight:

60
Draft Abilis hardware Draft

Table 2.25. Power consumption

Condition Current consumption on the Current consumption on the external

external power supply (mA) power supply (mA) - PSU = 12 V
- PSU = 5 V (old version)
All relays on BACKUP position 50 30
All relays on MAIN position 480 290

61
Draft Draft

Chapter 3. Physical connections

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
3.1. Numbering of the physical ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.2. ISDN Basic Rate Interface (BRI) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.2.1. Emergency connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.3. Importance of the impedance matching adapters (ISDN Adapter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.4. Connecting pots cards to patch panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.5. ADSL modem connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.6. POTS protection connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.7. UMTS-BOX connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.8. Citobox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
3.8.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.9. Simbox connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.10. RJS connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.10.1. Connection examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.10.2. Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

3.1. Numbering of the physical ports

Abilis has been conceived as a modular system to allow a number of possible configurations.

Every Abilis system is supplied with technical documents:

• Status of the software configuration (ready to use, to be configured…).

• Ports numeration.

• Connection scheme to the existing lines or machines.

• Local set ups (IP configurations, ISDN lines configuration).

Figure 3.1. Abilis rear panel

The connections usually are made on the Abilis rear panel. The chart below shows the different ports and their connection
possibilities:

62
Draft Physical connections Draft

Table 3.1. Port numbering

Port Number Description

1 : 24 CTI Port on QPRI
31 : 54 CTI Port on BRI4 or BRI8 or BRI-HFC4 or BRI-HFC8
91 : 93 ISDN Port on BRIO
101 : 196 (FXS) analog port on POTS
201 : 232 CTI port on GSM Box
ETH-x Fast Ethernet “x”
SYNC-1 : SYNC-16 Synchronous ports from 1 to 16 on ESB2

3.2. ISDN Basic Rate Interface (BRI) connection

The Abilis ISDN-BRI ports are electrically configured like Telecom NT1 ports, so:

• To connect the ports to “Terminal Equipment” systems (telephone switchboards, TA, ISDN modem, FAX, …) you must
use a straight cable cat. 5. Set up the ports at a logical level as NT (Network Termination) in the Abilis configuration.

• To connect the ports with the Telecom lines, you must use a “cross-cable (crossed) cat.5” (usually provided with red
shells). Set up the ports at a logical level as TE (Terminal Equipment) in the Abilis configuration.

Warning
The ports which are configured at a logical level as NT must always be connected to a 100 ohm impedance
matching adapter.

63
Draft Physical connections Draft

Figure 3.2. Typical connecting scheme betwenn Abilis - ISDN lines

Tip
Interesting chapters:

Section 2.9.3, “QPRIX”;

Section 2.9.5, “PB44X”;

Section 2.9.7, “BRI-HFC4 / BRI-HFC8”;

Section 2.9.8, “BRIO”;

Section 53.1, “How to configure ISDN ports to connect PBX or ISDN lines”.

3.2.1. Emergency connection

If necessary ( in case of damages, bad functioning, lack of electricity…) the user can manually by-pass Abilis and connect the
switchboard to the Telecom network. Antek suggests the following procedure:

• Disconnect the cable between the PBX switchboard and the impedance matching adapter

• Disconnect the cable between the Telecom line and the Abilis port, keeping the impedance matching adapter.

• Connect the straight cable from the switchboard to the Telecom one using the impedance matching adapter.

• Repeat this procedure for every line you want to by-pass.

64
Draft Physical connections Draft

Figure 3.3. Emergency procedure (by-pass Abilis)

Tip
To restore the telephone connections we suggest to write down precise instructions about the emergency
procedure and keep them at hand in the switchboard room, available to technicians.

3.2.1.1. Switch
To make the by-pass easier Antek provides Section 2.10.7, “RJ Switch” on request.

Tip
Interesting chapters:

Chapter 14, RJS - RJ Switch;

Section 3.10.1, “Connection examples”.

3.3. Importance of the impedance matching adapters

(ISDN Adapter)
When ISDN-BRI ports (e.g. BRI4, BRI8, BRI-HFC4, BRI-HFC8) are used, a line termination resistor (ISDN Adapter or
impedance matching adapter) must be used to avoid signal reflections. One adaper per port must be used.

The telecom NT1 Network-termination units and most of the PBX (switchboards) usually have already a line termination
resistor. Abilis BRI port doesn't have any.

Differences between a Point-to-Point connection and a Point-to-multiPoint connection:

65
Draft Physical connections Draft

Figure 3.4. ISDN Adapter

• Point-to-Point (only one device can be connected): an impedance matching adapter is ALWAYS necessary.

• Point-to-Multipoint :

• If Abilis is the only device to be connected to the network-termination unit of the S0 bus or if Abilis is the farthest
device from the NT unit, the impedance matching adapter MUST be inserted.

• If Abilis is not the farthest device, the impedance matching adapter MUST NOT be inserted.

Warning
The impedance matching adapter MUST be connected near the ISDN port of the Abilis (you can use the 10
cm cables provided with the Abilis).

Warning
Improper connection of line terminations may cause disturbances like noisy conversations, data loss, line
drops, and in general a poor and unstable service.

Tip
Interesting chapters: Section 53.1, “How to configure ISDN ports to connect PBX or ISDN lines”.

3.4. Connecting pots cards to patch panel

There are three kinds of patch panel:

• with RJ11 sockets

• with RJ45 sockets not compatible with RJ11 plugs

• with RJ45 sockets compatible with RJ11 plugs

Use an octopus cable to connect a port of a pots card to the first type of patch panel.

The second type is more popular than the third so in most cases you can't plug a RJ11 plug into a RJ45 socket of your patch
panel. Connecting a RJ11 plug into a RJ45 socket of a non compatible patch panel can cause a defective contact.

The third type can accept RJ11 plugs without issues.

Besides, a RJ45 socket can be used to connect up to 4 pots phones. In this case an adapter cable must be used to connect a
pots card to patch panel, following the scheme below.

Warning
Using the “straight” scheme of connection, crosstalk issues occurr in the part of cable from patch panel to
phones.

66
Draft Physical connections Draft

Figure 3.5. Adapter cable

Using a “straight” cable crosstalk issues occur because pair #3 couples conductors #3,6 and pair #1 couples conductors #4,5.
Crosstalk issues are located in the part of cable from patch panel to phones.

67
Draft Physical connections Draft

Figure 3.6. “Straight” scheme of connection - Conductors affected by crosstalk

3.5. ADSL modem connection

Follow the steps below to connect an USB modem.

• Power on Abilis;

• connect the modem to Abilis using the USB cable;

• connect the ADSL line cable to modem;

• add/configure the adsl resource;

• check the modem status leds (Starmodem, Speedtouch).

68
Draft Physical connections Draft

Figure 3.7. Connecting an ADSL modem

Tip
Interesting chapters:

Section 2.10.1, “ADSL modem”;

Chapter 10, ADSL modem.

3.6. POTS protection connection

Connect the POTS protection between Abilis and the POTS phones following the scheme below:

69
Draft Physical connections Draft

Figure 3.8. Connecting POTS protection

Warning
The metal case must be connected to the Abilis metal case or to the earth of the electrical system.

Tip
Interesting chapters:

Section 2.9.10, “POTS protection”;

Section 2.9.9, “POTS 4/8/16”;

Chapter 42, CTI System;

Section 53.2, “How to configure FXS (POTS) ports for analog telephones or fax machines”.

3.7. UMTS-BOX connection

In this section it is shown how to connect an UMTS Box or a GSM Box (with two channels) to the Abilis CPX.

1. Insert the bracket with power connectors in the Abilis base unit.

70
Draft Physical connections Draft

2. Connect the internal power connector of the bracket to the power supply connector.

3. Connect the USB cable to the USB port and the power supply cable to the bracket.

4. Insert one or two SIM cards in the UMTS Box.

71
Draft Physical connections Draft

5. Connect the USB cable to the USB port and the power supply cable to the connector.

Tip
Interesting chapter: Chapter 11, GSM-UMTS BOX.

3.8. Citobox connection

Figure 3.9. Citobox - front view

72
Draft Physical connections Draft

Figure 3.10. Citobox - rear view

Tip
Click here to view the front panel pinout.

Follow the steps below to connect a Citobox:

• Power on Abilis;

• connect the Citobox to Abilis using the USB cable;

• connect the power supply to Citobox;

• add/configure the CITOBOX and GPIO devices;

Figure 3.11. Connecting Citobox

Tip
Interesting chapters:

Chapter 13, Citobox;

Section 2.10.5, “Citobox”.

3.8.1. Connection examples

Antek recommends to use the following doorphone systems because they have been tested.

3.8.1.1. Example - connecting Citobox to Bticino 2 wire digital bus (External

doorphone model BTICINO 342150)
This section explains physical connection between Citobox and Bticino 2 wire digital bus.

• connect power to Citobox using the port on the rear;

• connect Abilis to Citobox using the usb port on the rear;

73
Draft Physical connections Draft

• use a RJ45 plug to connect the door phone interface and the digital output on the front panel to the digital bus adapter
following the scheme below;

• connect the digital bus Adapter for CITO-BOX to the doorphone system using 2-wire bus as explained in the following
scheme.

Tip
Click here to view the front panel pinout.

74
Draft Physical connections Draft

Figure 3.12. Citobox - connection to the Bticino 2 wire digital bus

75
Draft Physical connections Draft

• configure the highlighted parameters of the cti port #241:

[13:41:05] ABILIS_CPX:d p ctip:241

CTIP:241 DESCR:
Act card:CB-1<1>
Run OPSTATE:UP LOG:NO TYPE:USER
signalling:CITO
mode:CITO NUM:999901
MORE-BUTTONS:1,2,3,4
L1-ON: L1-OFF: L1-PULSE: L1-PULSE-T:1000 L1-PULSE-GAP:250
L2-ON: L2-OFF: L2-PULSE: L2-PULSE-T:1000 L2-PULSE-GAP:250
L3-ON: L3-OFF: L3-PULSE: L3-PULSE-T:1000 L3-PULSE-GAP:250
L4-ON: L4-OFF: L4-PULSE: L4-PULSE-T:1000 L4-PULSE-GAP:250
CITO-GAIN-IN:SYS CITO-GAIN-OUT:SYS
CITO-ES:SYS
CITO-ES-RISE-OUT:SYS CITO-ES-FALL-OUT:SYS CITO-ES-THR-OUT:0

• configure the CITOBOX section of the CTISYS resource in the following way:

[02:22:47] ABILIS_CPX:d p ctisys

RES:CtiSys --------------------------------------------------------------------
Run DESCR:CTI_System_general_properties
...
- CITOBOX defaults -----------------------------------------------------
CITO-GAIN-IN:0 CITO-GAIN-OUT:0
CITO-ES:NO
CITO-ES-RISE-OUT:20 CITO-ES-FALL-OUT:200 CITO-ES-THR-OUT:-12
...

3.8.1.2. Example - connecting Citobox to Bticino 4 wire analog bus (External

doorphone model BTICINO 332120)
This section explains the physical connections between Citobox and Bticino 4 wire analog bus.

• connect the power to Citobox using the port on the rear;

• connect the Abilis to Citobox using the usb port on the rear;

• check that you have an adapter cable like the one shown in the picture below, with a RJ45 plug at one end and two terminal
blocks at the other end. This cable is necessary to connect the doorphone interface and the digital output on the front panel
to the digital bus adapter;

Tip
Click here to view the front panel pinout.

76
Draft Physical connections Draft

Figure 3.13. Citobox - connection to the Bticino 4 wire analog bus

77
Draft Physical connections Draft

• connect the digital bus adapter for the CITO-BOX to the doorphone system using a 2-wire bus as explained in the
following scheme.

3.9. Simbox connection

Figure 3.14. Simbox - front view

Figure 3.15. Simbox - rear view

Follow the steps below to connect a Simbox:

• Power on Abilis;

• connect the Simbox to Abilis using the USB cable;

• connect the power supply to Simbox;

• insert at least one sim;

• add/configure the SIMBOX device;

Figure 3.16. Connecting Simbox

78
Draft Physical connections Draft

Tip
Interesting chapters:

Chapter 12, Simbox;

Section 2.10.6, “Simbox”.

3.10. RJS connection

Figure 3.17. RJS front view

Figure 3.18. RJS rear view

The following figure explains how to connect the ports:

Figure 3.19. RJS ports

Follow the steps below to connect a RJS:

• Power on Abilis;

• connect the switch to Abilis using the USB cable;

• connect the power supply to RJS;

79
Draft Physical connections Draft

• add/configure the RJS device;

Figure 3.20. Connecting RJS

Tip
Interesting chapters:

Section 3.10.2, “Connection cables”;

Chapter 14, RJS - RJ Switch;

Section 2.10.7, “RJ Switch”.

3.10.1. Connection examples

Before reading examples just keep in mind the following notes:

• only the central pins 4,5 and 3,6 are switched

• pins 1,2 and 7,8 are not connected

3.10.1.1. How to use a backup Abilis to increase the reliability

RJS can be used to connect two Abilis:

• a main Abilis

• a backup Abilis

The backup device is always in idle unless the master crashes. The following is the scheme to use:

80
Draft Physical connections Draft

81
Draft Physical connections Draft

When Abilis MAIN is up the isdn line is connected to M1 and so to ctip port #33 of Abilis MAIN. A call is routed through
the port #31 connected to M2, so it reaches the PBX (L2).

When Abilis MAIN is down, L1 is automatically switched on B1 (which is connected to ctip port #33 of Abilis BACKUP)
and L2 is switched on B2. A call is routed through the port #31 (of Abilis BACKUP) connected to B2, so it reaches the PBX
(L2).

Tip
Interesting chapter: Section 3.10.2, “Connection cables”.

3.10.1.2. How to connect an ISDN line

RJS can be used to automatically bypass Abilis when it's down and connect an ISDN line directly to a PBX.

The following is the scheme to use:

82
Draft Physical connections Draft

When Abilis is up:

• the ISDN line is connected to ctip #33 because L1 is switched on M1

• the PBX is connected to ctip #31 because L2 is switched on M2.

A call from the ISDN line reaches Abilis which routes it through the port #31, so the call reaches the PBX.

When Abilis is down:

83
Draft Physical connections Draft

• the isdn line is connected directly to PBX, because L1 is switched on B1 and L2 is switched on B2

A call from the ISDN line reaches directly the PBX.

Tip
Interesting chapters:

Section 3.10.2, “Connection cables”;

Section 2.9, “Abilis PCI boards and extension boards”;

Section 53.1, “How to configure ISDN ports to connect PBX or ISDN lines”.

3.10.1.3. How to connect ADSL lines

RJS can be used to switch ADSL lines. Up to 2 ADSL lines can be connected to a single port because only the central pins
4,5 and 3,6 are switched (remaining pins 1,2 and 7,8 are not connected).

Note
There must be one ADSL modem for one line and one ADSL modem for each Abilis (MAIN and
BACKUP). So four modems are needed to connect two adsl lines to RJS having two Abilis (MAIN and
BACKUP).

Use the following scheme to connect 2 adsl lines:

84
Draft Physical connections Draft

85
Draft Physical connections Draft

When Abilis MAIN is up, the ADSL lines are connected to M1, so they are used by Abilis MAIN.

When Abilis MAIN us down, the ADSL lines are switched to B1 and they are connected to Abilis BACKUP.

Caution
RJS is not suitable to connect HDSL lines with V35 interfaces.

Tip
Interesting chapters:

Section 3.10.2, “Connection cables”;

Section 2.10.1, “ADSL modem”;

Section 52.4, “How to configure ADSL connections using USB modems”;

Chapter 10, ADSL modem.

3.10.1.4. How to connect Ethernet cables.

RJS can be used to connect ethernet cables knowing that:only central pins 4,5 and 3,6 are switched (remaining pins 1,2
and 7,8 are not connected). So:

• ethernet cables which use pins 1,2 and 7,8 can't be connected

• ethernet cables can be connected but adapter cables must be used.

The adapter cable must be made so that pins 1,2 are connected to pins 3,6 and pins 4,5 remain connected to pins 4,5.

86
Draft Physical connections Draft

When Abilis MAIN is up, the cross cable is switched on M1 and so Abilis MAIN is connected to router.

When Abilis MAIN is down, the cross cable is switched to B1 and so Abilis BACKUP is connected to router.

87
Draft Physical connections Draft

Tip
Interesting chapters:

Section 3.10.2, “Connection cables”;

Chapter 14, RJS - RJ Switch;

Section 2.9.12, “ETH100”;

Section 52.1, “How to configure LAN settings”;

Section 52.2, “How to activate a new ethernet port”;

Section 19.3, “IP Resources”;

3.10.2. Connection cables

The following cables must be used to connect to RJS.

Figure 3.21. ISDN BRI and PRI cable

Figure 3.22. Ethernet cable

88
Draft Physical connections Draft

Figure 3.23. ADSL cable

89
Draft Draft

Chapter 4. Abilis firmware

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
4.1. Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.1. Firmware versioning numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.1.2. Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1.3. Compatibility of drivers.cfg files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4.1. Abilis firmware

As per now, the whole Abilis firmware can be stored within 6 megabytes of mass memory. It is made up of a large number of
modules which can however be enabled or disabled, according to actual needs.

The Abilis firmware is just one executable file which is loaded at every bootstrap along with the configuration data
(drivers.cfg) and several other items (mainly firmware which is to be downloaded into programmable chips present in
the Abilis HW adapters).

Abilis can load the operating system and configuration from:

• Compact Flash Disk (default)

• Hard Disk, used as a backup of the Compact-Flash Disk, or when a large mass-memory is required.

The same mass memory may contain several versions of the Abilis Firmware. The choice of which version is to be loaded
can be done using an appropriate command.

Tip
Interesting chapters:

• Section 51.2, “How to prepare an Abilis Compact-Flash using a PC”;

• Section 51.4, “How to remotely upgrade the Abilis firmware”;

• Section 51.7, “How to upgrade configuration files to newer firmware versions”.

4.1.1. Firmware versioning numbering

Abilis firmware versioning scheme is composed by 2 parts:

• build number

• release number

Every Abilis version has a build number, while only the official releases have a release number. “Build” versions are
special or not yet official versionswhich can be released to provide solutions to urgent needs.

There is also a different version for videosurveillance applications that is recognizable from /VID suffix after the release
number.

For example below is an example of a released version:

COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

90
Draft Abilis firmware Draft

Wednesday 15/12/2010 15:02:22 (UTC+1.00)

Logged as SUPERUSER

[15:02:22] ABILIS_CPX:

Below is instead an example of a “build” version:

COM

Abilis CPX - Ver. 3388/STD - Build 3388

Thursday 16/12/2010 16:04:39 (UTC+1.00)
Logged as SUPERUSER

[16:04:39] CPX_208:

Released versions are identified by a “3 numbers code”:

major version.minor version.patch version

• major version : radical changes in comparison to previous versions;

• minor version : not so radical changes in comparison to previous minor versions;

• patch version : small changes or bug fixes in comparison to previous versions.

For example: Version 7.0.4

4.1.2. Configuration files

The drivers.cfg file contains all the settings for Abilis functioning.

The drivers.bck is loaded in the event that drivers.cfg can't be loaded for some reason.This measure enhances the
system's reliability.

• drivers.cfg: the current configuration (in case of changes, not yet loaded);

• drivers.bck: the last saved backup (hopefully a working one!).

The drivers.cfg and drivers.bck files can be updated with save conf and save conf backup commands.

The scheme below describes how Abilis uses drivers.bck.

Figure 4.1. Abilis reliability using drivers.bck

91
Draft Abilis firmware Draft

Tip
Interesting chapters:

• Section 51.3, “How to use the Console configurator”;

• Section 51.5, “How to remotely transfer files using a terminal emulator”;

• Section 51.8, “How to copy files using a removable drive”.

4.1.3. Compatibility of drivers.cfg files

Drivers.cfg files of different releases are compatible, only if the firmware releases have the same major and minor
version numbers [91].

For example, drivers.cfg files of the releases 5.6.6 and 5.8.9 aren't compatible because the second number code is
different; instead, drivers.cfg files of the release 6.0.3 and 6.0.6 are compatible because the first two numbers code are
the same.

Every Abilis firmware release has a corresponding config.exe utility that creates and reads drivers.cfg files
compatible with the releases having the same major and minor version numbers.

Every release also provides a Configuration converter (convcfg.exe or convcfgw.exe files) that allows to update the
file format of previous versions to the current one.

Tip
If the major and minor version numbers are the same, it is better to use the config.exe utility of a more
recent patch version. In some very rare cases, you could find a new parameter, that was previously hidden in
an older patch version.

Tip
Interesting chapters:

• Section 51.2, “How to prepare an Abilis Compact-Flash using a PC”;

• Section 51.4, “How to remotely upgrade the Abilis firmware”;

• Section 51.7, “How to upgrade configuration files to newer firmware versions”.

92
Draft Draft

Chapter 5. Command language

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
5.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5.2. Command Line Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.3. Help online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.4. System accessing commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.1. LOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.2. LOGOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.4.3. CLOSE / EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.5. Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.1. D DEV (Display Devices) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.5.2. A DEV (Add Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.5.3. S DEV (Set Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.5.4. C DEV (Clear Device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6. Resources or Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.1. D P (Display Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.2. A RES (Add Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.6.3. S P (Set Parameters) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.6.4. C RES (Clear Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.7. Initialization/activation/deactivation commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.1. INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.2. D ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.3. S ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.4. D INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.7.5. S INACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.7.6. D RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.7.7. D TREE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.7.8. ALARM VIEW and ALARM RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.7.9. CALL RES and DISC RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8. General and system information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.1. D G (Display General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.8.2. D I (Display Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.8.3. D VER (Display Versions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5.8.4. CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.8.5. Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5.8.6. D DESCR (Display Descriptions) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.8.7. D PSTACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.9. Users Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
5.9.1. D USER (Display User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.9.2. A USER (Add User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.3. C USER (Clear User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5.9.4. S USER (Set User) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10. Address book management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.1. CONTACT EXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.10.2. CONTACT IMPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5.10.3. CONTACT RELOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11. Lists management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.11.1. LIST CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

93
Draft Command language Draft

5.11.2. LIST DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

5.11.3. LIST RENAME / LIST DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.4. D LIST (Display List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
5.11.5. A LIST (Add List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
5.11.6. C LIST (Clear List item) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.11.7. D ITEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.11.8. Type of lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.12. Configuration validating and saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.12.1. VALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5.12.2. SAVE CONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5.13. System management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.1. CONFLOG BACKUP and CONF BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
5.13.2. CONFLOG RESTORE / CONF RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.3. FILE COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5.13.4. FILE DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.5. FILE GET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5.13.6. FILE PUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.13.7. SYS COMPACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.8. SYS COMPACTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.9. SYS DELETE PACKAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.10. SYS DELETE VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
5.13.11. SYS UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5.13.12. SYS DIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.13.13. SYS DISK INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.14. SYS DISK CHK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.15. SYS DISK FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5.13.16. SYS DISK LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.17. SYS DISK MBR DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5.13.18. SYS DISK PARTITION INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.19. SYS DISK PARTITION ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5.13.20. SYS DISK PARTITION RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.21. SYS SET BOOT VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.13.22. SYS DISPLAY BOOT LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5.13.23. WARM START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.14. Diagnostics and Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.1. Diagnostic commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
5.14.2. Statistics Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5.15. Test functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.1. Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.2. Tracert / Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.3. Pingstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5.15.4. DSPs test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.16. Trace functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5.16.1. Trace act . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.16.2. Trace start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.3. Trace stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.16.4. Trace get . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.17. DEBUG commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.1. DEBUG RES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.17.2. DEBUG SIMULATE EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

5.1. Introduction
This chapter describes the main rules that set up the command language of the Control Port commands interpreter.

It is also possible to configure Abilis CPX without connecting to the Control Port, using the config.exe utilty program.

It is possible to log into the Control Port by using three different privileges:

• User login level (USER). Simple users may read statistics and diagnostic information but cannot do programming.
Commands allowed include “display commands” (parameters, statistics and log) and “init commands”.

94
Draft Command language Draft

• Administrator login level (ADMIN). Administrators may perform the same functions permitted to users, and may do
programming and system management (reboot, change and save configuration, and so on). Administrators are only not
allowed to deal with cryptography keys, passwords and changes of the user privileges.

• Super-User login level (SUPER). Super users have full powers.

Tip
Interesting chapters:

Chapter 16, CP - Control Port;

Chapter 17, TELNET - TELecommunication NETwork;

Chapter 18, SSH - Secure SHell;

Section 51.1, “How to enter into the Abilis control-program”.

5.2. Command Line Operations

A command consists in a series of characters, ending with <CR> (carriage return), sent to Abilis Control Port. The CP
answers with tables containing the requested information or with “COMMAND EXECUTED”; then prompts for the next
command.

Commands are divided into the following groups (Group IDs):

Table 5.1. Command groups

Group Group ID Action Minimum privilege

level required
Add operations A Adds a new item into the set Administrator
Reconfiguration operations BOOT Activates the default Administrator
configuration of an item
Clear and Delete C Clears a set of statistics or Administrator
Deletes an item
Display D Displays items, parameters User
and statistics
Search F Searches for items User
Re-initialization INIT Commits changes which have User
been made in the named item
list management LIST manages lists of items (to Administrator
create, delete, rename lists)
Move M exchanges the rank of two Administrator
items within a table
Restart R Activates currently inactive User
components
Set up S Sets up parameters of the Administrator/Super-User
named item
System commands [*] System general management [*]
or activation of special
functions

[*] Complete list of system commands is available in Section 59.1, “Complete list of On-line Commands”.

5.3. Help online

An online help function is available for every command. By typing the ? character, all the information, needed to correctly
compose the commands, are displayed.

95
Draft Command language Draft

The help function is contextual, this means the help message displayed depends on the ? character position in the command
line.

[11:08:39] ABILIS_CPX:?

ALARM Alarm operations

A Add operations
BOOT Boot operations
C Clear operations
CALL Open a Connection
CALLTRY Open a Connection
CLOSE Close current CP session
CONF Configuration management
CONFLOG Configuration and/or log files backup/restore
CONTACT Address Book
D Display operations
DEBUG Debug operations
DISC Close a Connection
DISABLE Disabling operations
EXIT Close current CP session
ENABLE Enabling operations
F Find operations
FILE File copy/delete/get/put operations
HALT Shutdown operation
HELP Detailed topic help
INIT Init operations
IPTRACE TCP/IP Trace operations
LICENCE Licence operations
LIST Lists operations
LOGIN Log-in operations
LOGOUT Log-out operations
M Move operations
MSG Voice message service
PAR Active parameter operations
PING Ping command
PINGSTAT Ping statistics command
RESTART System Restart operations
R Restart operations
S Set operations
SAVE Save operations
SHUTDOWN Shutdown operation
SOUND Sound disable/enable operations
START Start real-time logging operations
SYS System operations
TERM Terminal setting operations
TEST Testing operations
TRACE Trace operations
TRACERT Trace route command
TRACEROUTE Trace route command
TRANSFER Transfer Calls
USBDEV USB devices management
VALIDATE Current configuration validation
WARM System warm start operations
X Exchange HW device configurations and resource subtypes
?? Full list of allowed commands

Inserting the ? character in a more advanced position in the command line, only those key words and their description,
allowed by the command language to be place in that position and after on, will be displayed.

[11:19:17] ABILIS_CPX:alarm ?

VIEW Alarm view

RESET Alarm reset

96
Draft Command language Draft

The following example shows how it is possible, through the digitation of ? character in successively different positions, to
have a complete description of “Add CTI routing” command:

[11:19:17] ABILIS_CPX:a ?

CRKEY: Encryption/Decryption key identifier [1..63]

CF CF/DND (Call forwarding/Do-Not-Disturb) entry
CONTACT Address Book
CTIB CTI channels bundle
CTICL CTI cluster
CTIDISA CTI DISA Users and Services
CTIG CTI group
CTIH323 CTI H.323 Translation entry
CTIIAX CTIIAX numbers table entry
CTIL CTI link
CTILG CTI group of links
CTIPC CTI permanent connection
CTIR CTI routing
CTIRE CTI routing
CTIRR CTI routing
CTISIP CTISIP numbers table entry
CTISMS CTI SMS routings for incoming/outgoing messages
DEV: HW device identifier 'type-n', where 'n' can be [1..255]
DHCP DHCP profile/subnet/host
DNS DNS server and relay tables
FTP FTP Virtual root paths/path's access Rights
GROUP: Group name. Max. 32 ASCII characters.
HTTP HTTP Virtual root paths/path's access Rights
IKE IKE Host/Client connections and preshared keys tables
IPACL IP Access List
IPAD IP Routing Administrative Distance
IPLB IP Load Balancing entry
IPR IP Routing
IPSEC IPSEC Security policies and associations tables
LCSG Last Calling Number Service group
LCST Last Calling Number Service table entry
LIST: CPX list name
NAT NAT alias entry
OSPF OSPF area/range/neigh/host/external route
PVC PVC Connection
R SVC Routing
RES: Resource identifier 'type-n', where 'n' can be [1..999]
RIP RIP external route
USER: User name. Max. 32 ASCII characters.
VRRP VRRP Routers
WGB WG Bridge Routing

[11:19:17] ABILIS_CPX:a ctir ?

PR: CTI routing priority [0..255]

[11:19:17] ABILIS_CPX:a ctir pr:1 ?

CTI routing parameter(s):

DESCR: Description. From 0 up to 70 ASCII extended characters.

Case is preserved. Spaces are allowed.
Strings holding spaces must be written between quotation marks.
In standard format it is displayed only when not empty.
In reduced format it is not displayed.
ACT: Active/usable record flag [NO, YES]

97
Draft Command language Draft

In standard/reduced format it is displayed only when equal to NO.

EDT: Editable by HTTP users record flag [NO, YES]
In standard/reduced format it is displayed only when equal to YES.
TYPE: Type of the connection [TR, DATA, VtoC, VtoH, VtoI, VtoS, VtoD,
CtoV, CtoC, CtoH, CtoI, CtoS, CtoD, HtoV, HtoC, HtoH, HtoI, HtoS,
HtoD, ItoV, ItoC, ItoH, ItoI, ItoS, ItoD, StoV, StoC, StoH, StoI,
StoS, StoD, DtoV, DtoC, DtoH, DtoI, DtoS, DtoD, *toV, *toC, *toH,
*toI, *toS, *toD]
POI: Input CTI port/group [1..300, *, #, G1..G32, G*, PBX, CtiSLink,
CtiH323, CtiIax, CtiDisa, CtiSip]
<Only for TYPE:TR/DATA/VtoCHISD/HtoVCHISD/ItoVCHISD/DtoVCHISD/
StoVCHISD/*toVCHISD>
SR: Source Cluster identifier [0..9, A..Z, a..z, _, :] or "#", or "*",
or a list name 'list'. <Only for TYPE:CtoVCHISD/*toVCHISD>
POO: Output CTI port/group [1..300, #, G1..G32, PBX, CtiSLink, CtiH323,
CtiIax, CtiDisa, CtiSip]
<Only for TYPE:TR/DATA/CtoVHISD/VtoHISD/HtoVHISD/ItoVHISD/DtoVHISD/
StoVHISD/*toVHISD>
DS: Destination Cluster identifier [0..9, A..Z, a..z, _, :]
or "#" or "<AUTO-I>" or "<AUTO-O>". <Only for TYPE:VCHISDtoC/*toC>
NEXT: Alternative routing selection [N (or NO), U (or UNLIMITED),
L (or LIMITED), T (or TRANSFERT), BB (or BUTBUSY)] or the name
of ICAUSE list between primes (E.g.: BUTBUSY or 'my_causes').
LAST: Alternative routing, last failure reason for conditional match
[ANY, BUSY, NOANS, OTHER] or the name of ICAUSE list between
primes (E.g.: NOANS or 'my_causes').
EEC: Extended echo canceller activation [NO, IN, OUT, BOTH]
CDI: Input called address [0..9, *, #, ?, 'list'], optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes,
or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP SPECIAL VALUES for details on meaning of special values.
CDO: Output called address [0..9, *, #, 'macro'], optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CGI: Input calling address [0..9, *, #, ?, 'list'], optionally preceded
by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] and/or
PI [a, r, m, q] and/or SI [y, v, w, z, j] attributes, or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CGO: Output calling address [0..9, *, #, 'macro'], optionally preceded
by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] and/or
PI [a, r, m, q] and/or SI [y, v, w, z] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
12''listname''34)
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
SDI: Input called sub-address [AlphaNumExt, *, ?, #, ##, $, 'list'].
(E.g.: ho11, me1*, ho??12?, ho?12?*, *, #, 'listname', AA'listname')
See HELP ISDN VALUES for details on meaning of special values.
SDO: Output called sub-address [AlphaNumExt, *, #, 'macro'].
(E.g.: home123, *, #, home123'sgi', 'sgi'home123'cdi.s5', 'sdi'
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
AAA''listname.cd'', AAA'sdi'BBB''listname'.s5')
See HELP ISDN VALUES for details on meaning of special values.
SGI: Input calling sub-address [AlphaNumExt, *, ?, #, ##, $, 'list'].

98
Draft Command language Draft

(E.g.: ho11, me1*, ho??12?, ho?12?*, *, #, 'listname', AA'listname')

See HELP ISDN VALUES for details on meaning of special values.
SGO: Output calling sub-address [AlphaNumExt, *, #, 'macro'].
(E.g.: home123, *, #, home123'sgi', 'sgi'home123'cdi.s5', 'sdi'
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
AAA''listname.cd'', AAA'sgi'BBB''listname'.s5')
See HELP ISDN VALUES for details on meaning of special values.
RGI: Input redirecting address [0..9, *, #, ?, 'list'], optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
and/or PI [a, r, m, q] and/or SI [y, v, w, z, j] attributes,
or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
RGO: Output redirecting address [0..9, *, #, 'macro'], optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
and/or PI [a, r, m, q] and/or SI [y, v, w, z] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
12''listname''34)
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
T301: Alerting time-out [Dft, 5..180 sec.]
UDT: Unconditional disconnect timer [NO, 1..9999 sec.]
LCS: Enable/disable Last Calling number Service [NO, YES]
<Only for POO: not equal to CtiSlink, CtiH323, and CtiDisa>
LCST: Last Calling number Service records timeout [Sys, NONE, 1..999 hour]
<Only for POO: not equal to CtiSlink, CtiH323, and CtiDisa>
IG: Input gain [Sys, MUTE, -31..+31 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
OG: Output gain [Sys, MUTE, -31..+31 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
SG: Attenuation of DTMF or Tone signals respect to their configured
values [Sys, -31..0 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
DL: Output volume of lower DTMF tone [Sys, MUTE, -31..+3 dBm]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
DH: Output volume of higher DTMF tone [Sys, MUTE, -31..+3 dBm]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
FMRLY: Fax/Data relay [NO, YES, Sys]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FAXSP: Fax maximum speed [AUTO or 0, 2400, 4800, 7200, 9600, 12000,
14400 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
MODSP: Modem maximum speed [AUTO or 0, 2400, 4800, 7200, 9600, 12000,
14400 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FMLVL: Output volume of Fax/Data signal [Sys, -18..-3 dBm]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FMDJ: Fax/Data default jitter buffer size [Sys, 0..1000 ms]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
FMMJ: Fax/Data maximum jitter buffer size [Sys, 0..1000 ms]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
ECM: Enable/disable ECM (Error Correcting Mode) for fax [NO, YES, Sys]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>

99
Draft Command language Draft

SP: Voice compression bit rate [5300, 6000, 6300, 6400, 7200, 8000,
8800, 9600, 11200, 13200, 13340, 15200, 16000, 18400, 24000,
24800, 32000, 40000, 64000 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCIHSD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
SC: Silence compression [NO, YES, Sys]
<Only for TYPE:VtoCHISD/CtoVCIHSD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
DJ: Default jitter buffer size.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
- For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [Sys,
0..1000 msec]
- For TYPE:CtoVCHISD/*toVCHISD: [*, Sys, 0..1000 ms]
It must be minor or equal to MJ:.
MJ: Maximum jitter buffer size.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
- For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [Sys,
0..1000 msec]
- For TYPE:CtoVCHISD/*toVCHISD: [*, Sys, 0..1000 ms]
It must be major or equal to DJ:.
CODERS: Allowed coders.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
- For TYPE:CtoCHISD/HtoCHISD/ItoCHISD/DtoCHISD/*toCHISD: [* or Sys
or NONE or a list of one or more coder values (see below)].
- For TYPE:VtoCHISD/CHISDtoV/*toV: [Sys or NONE or a list of one or
more coder values (see below)]
The available coders are [Transp, G.711, G.726, G.727, GSM6.10,
Spirit, G.723.1, G.729A, ILBC, SPEEX, G.711A, G.711u]. Values can be
joined using "," operator. The position in the list defines the
preference order. The right-most value is the one with the lowest
preference.
SPOUT: Maximum preferred/allowed bit rate for the audio coder on output
side of direct transcoding [*, 5300, 6000, 6300, 6400, 7200, 8000,
8800, 9600, 11200, 13200, 13340, 15200, 16000, 18400, 24000,
24800, 32000, 40000, 64000 bps]
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
SCOUT: Silence compression output [NO, YES, Sys, *]
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
DJOUT: Default jitter buffer size output [*, Sys, 0..1000 ms]
It must be minor or equal to MJOUT:.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
MJOUT: Maximum jitter buffer size output [*, Sys, 0..1000 ms]
It must be major or equal to DJOUT:.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
CODERSOUT: Preferred list of coders for THIS routing offered to called side
[* or Sys or NONE or *,Sys or a list of one or more coder values
(see below) or *,list]
The available coders are [Transp, G.711, G.726, G.727, GSM6.10,
Spirit, G.723.1, G.729A, ILBC, SPEEX, G.711A, G.711u]. Values can be
joined using "," operator. The position in the list defines the
preference order. The right-most value is the one with the lowest
preference.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
TI1:..TI5: Time interval in the format "day,hh:mm-hh:mm", where 'day' can be:

100
Draft Command language Draft

- a single day of the week [MO, TU, WE, TH, FR, SA, SU] or
- a set of days of the week (E.g.: MO+TH or TU+TH+SU) or
- an interval of days of the week (E.g.: MO-WE or TH-SU) or
- "ALL".
Use "#" to disable the time interval.

Note
The ? character has to be separated by one or more spaces from the previous word.

A filter can be applied when asking help to semplify the search of information about a single parameter:

[20:00:02] ABILIS_CPX:d p ip-1 ? nat diffserv vrrp

Ip-1 (IP over LAN) resource parameter(s):

NAT: NAT usage [NO, INSIDE, OUTSIDE]

DIFFSERV: Differentiated Services Field (DS) management [NO, NET, BORDER]
VRRP: Enable/disable VRRP [NO, YES]

[20:00:25] ABILIS_CPX:

[20:02:58] ABILIS_CPX:d user: ? sip-busy-nochan

D USER:val [<section>] Display Users Access Control table's entries

USER:name User name. Max. 32 ASCII characters.

USER:A All entries of the Users Access Control table
USER:ALL All entries of the Users Access Control table
<section> Select the service section to be displayed between <Optional>
[OPC, PPP, FTP, HTTP, MAIL, IAX, SIP]. The specified section
is displayed only if the related service is enabled.

User's parameter(s):

SIP-BUSY-NOCHAN: Return BUSY cause instead of NOCHAN [NO, IN, OUT, BOTH]

Besides, a help section is present:

[14:13:23] ABILIS_CPX:help ?

HELP <topic> Display detailed help on a specified topic

Defined topics:

ISDN Help on ISDN topics

INTERNET Help on INTERNET topics
SS Supplementary services
TIMEZONES List of supported time zones

[14:13:26] ABILIS_CPX:help isdn ?

ATTRIBUTES ISDN number attributes

VALUES Details on meaning of special values

[14:13:30] ABILIS_CPX:help internet ?

PORTS List of assigned TCP/UDP ports

PROTOCOLS List of assigned Internet protocols

[14:13:36] ABILIS_CPX:help ss ?

KEYCODES Supplementary services keycodes

101
Draft Command language Draft

[14:13:42] ABILIS_CPX:help timezones ?

HELP TIMEZONES Show the list of supported time zones

5.4. System accessing commands

5.4.1. LOGIN
This command shows the current privilege level, through which the User accessed the Control Port.

[11:38:04] ABILIS_CPX:login

Currently logged as USER

On the contrary, if an access level is specified, the command will login the User to the Control Port using the requested
privilege.

[11:38:04] ABILIS_CPX:login super

Password:
Logged as SUPERUSER

5.4.2. LOGOUT
This command closes the current configuration session and prompts the login request.

If in the current configuration session the configuration was modified but not saved, the command displays a warning
message and queries the User for proceeding with configuration saving or not.

[11:38:04] ABILIS_CPX:logout

THE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED.

PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?y

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

In case of negative answer, the configuration session is closed but the configuration is not saved.

[11:38:04] ABILIS_CPX:logout

THE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED.

PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?n
Logged as SUPERUSER

Any other answer makes the command to be aborted and the Control Port prompt to be shown again.

[11:38:04] ABILIS_CPX:logout

THE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED.

PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?a

5.4.3. CLOSE / EXIT

This command closes the current connection to the Control Port.

If the User was connected to the Control Port through a TELNET port, then the command interpreter of the TELNET port
will be prompted.

If the User executed this command through the off-line configurator, it will terminate the configurator and go back to the MS-
DOS prompt.

If in the current configuration session the configuration was modified but not saved, the command displays a warning
message and queries the User for proceeding with configuration saving or not.

102
Draft Command language Draft

[11:38:04] ABILIS_CPX:close

CLR 00 00

[192.168.0.201] TELNETS>

5.5. Devices
5.5.1. D DEV (Display Devices)
This command shows cards and hardware devices configured and their state (active/inactive).

[11:38:04] ABILIS_CPX:d dev

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ESB-1 No Sync-1,Sync-2,Sync-3,Sync-4 . . . . . . . . 7 PCI ( 9)
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 72 PCI ( 10)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 73 PCI ( 11)
ETH-3 Yes Eth-3 . . . . . . . . . . . . . . . . . . . 74 PCI ( 12)
ETH-4 Yes Eth-4 . . . . . . . . . . . . . . . . . . . 75 PCI ( 9)
QPRI-1 No 1..4 . . . . . . . . . . . . . . . . . . . . 9 PCI ( -)
QPRI-13 No 49..52 . . . . . . . . . . . . . . . . . . . NONE PCI ( -)
BRI8-1 Yes 31..38 . . . . . . . . . . . . . . . . . . . 8 PCI ( 12)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 10 PCI ( 10)
POTS-2 Yes 117..132 . . . . . . . . . . . . . . . . . . 7 PCI ( 9)
POTS-3 No 133..148 . . . . . . . . . . . . . . . . . . NONE PCI ( -)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . - PCI ( -)
CB-1 Yes 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . 2.0
ADSLUSB-2 Yes No Adsl-2 . . . . . . . . . . . . . . . . NONE
ADSLUSB-3 Yes No Adsl-3 . . . . . . . . . . . . . . . . NONE
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 Yes No . . . . . . . . . . . . . . . . . . . 0.3.0
CELL-2 Yes No . . . . . . . . . . . . . . . . . . . 0.3.1
CODEC-1 Yes No . . . . . . . . . . . . . . . . . . . 0.3.2
SIMEMU-1 Yes No . . . . . . . . . . . . . . . . . . . 0.3.3
CELLBOX-2 203..204 . . . . . . . . . . . . . . .
CELL-3 Yes No . . . . . . . . . . . . . . . . . . . 0.0
CELL-4 Yes No . . . . . . . . . . . . . . . . . . . 0.1
CODEC-2 Yes No . . . . . . . . . . . . . . . . . . . 0.2
SIMEMU-2 Yes No . . . . . . . . . . . . . . . . . . . 0.3
UMTSKEY-8 Yes No 208 . . . . . . . . . . . . . . . . . NONE
RJS-1 Yes No Rjs-1 . . . . . . . . . . . . . . . . 1.1
SIMBOX-1 Yes No SimBox-1 . . . . . . . . . . . . . . . 1.2
GPS-1 Yes No Gps-1 . . . . . . . . . . . . . . . . 3.0
GPIO-1 Yes No Gpio-1 . . . . . . . . . . . . . . . . NONE
BLUSB-1 Yes No Blusb-1 . . . . . . . . . . . . . . . -
CITOBOX-1 241..242 . . . . . . . . . . . . . . .
CITO-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
AUDIO-1 Yes No . . . . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------

103
Draft Command language Draft

*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-4 No No Adsl-4 . . . . . . . . . . . . . . . . NONE

5.5.1.1. D PCIDEV (Display PCI Devices)

It displays information about PCI devices currently present and active in the system.

[11:38:04] ABILIS_CPX:d pcidev

PCI Server Overview:

ID Vendor Device CardName Slot/F Ver Irq

-------------------------------------------------------------------------------
0 1106 VIA 0691 BRIDGE HOST - 0/0 12.04 -
1 1106 VIA 8598 BRIDGE PCI - 1/0 0.00 -
2 1106 VIA 0686 BRIDGE ISA - 4/0 4.00 -
3 1106 VIA 0571 STORAGE IDE - 4/1 0.06 -
4 1106 VIA 3038 USB CONTROLLER UHCI - 4/2 1.10 10
5 1106 VIA 3038 USB CONTROLLER UHCI - 4/3 1.10 10
6 1106 VIA 3057 BRIDGE HOST - 4/4 4.00 -
7 10B5 PLX TECHNO 9050 BRIDGE OTHER CTI-HFC-OKI-4P 6/0 0.02 10
8 1283 ITE 8872 16550 SERIAL PORT PCI-POTS 8/0 0.01 12
9 10EC REALTEK 8139 NETWORK ETHERNET TE100-PCIWN 9/0 1.00 11
10 1283 ITE 8872 16550 SERIAL PORT PCI-POTS 10/0 0.01 10

Tip
Interesting chapters:

Section 2.9, “Abilis PCI boards and extension boards”;

Section 51.9.1, “How to recognize PCI cards model”.

5.5.1.2. D USBDEV (Display USB Devices)

It displays information about USB devices currently active and connected to Abilis.

[11:38:04] ABILIS_CPX:d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time Informatik 0000 UHCI Virtual Root Hub 0.00 0
2 0000 On Time Informatik 0000 UHCI Virtual Root Hub 0.00 1
3 0451 2046 1.25 0.0
4 06B9 THOMSON 4061 Speed Touch 330 4.00 0.1
5 06B9 THOMSON 4061 Speed Touch 330 4.00 0.0.0
6 0451 2046 1.25 0.0.1
7 0403 FTDI 6001 USB <-> Serial 4.00 0.0.1.0
8 0403 FTDI 6001 USB <-> Serial 4.00 0.0.1.1
9 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.0.1.2
10 04D8 Abilis 000C USB GSM-BOX 1.01 0.0.1.3

Tip
Interesting chapter:

Section 2.10, “USB devices”.

104
Draft Command language Draft

5.5.2. A DEV (Add Device)

This command adds a new card or a new device in the configuration. Device identifier must be indicated in the form: “type-
nnn”, where: “type” has to be one of the device's mnemonics that are allowed by the system (e.g. ETH, ESB and so on);
“nnn” must be a digit in the interval [1 - 255].

[16:32:01] ABILIS_CPX:a dev: ?

A DEV:type-n Add CPX HW device of the selected type

A DEV:type-n CTIP-NUM:val Add a CTI card, setting active only the
specified number of CTI ports.
By default all ports are set active.

DEV: HW device identifier 'type-n', where 'n' can be [1..255] <Mandatory>

CTIP-NUM: Number of CTI ports to be set active [1..32] <Optional>

Available hardware device's types:

- PCI devices:
ESB From 1 to 4 synchronous serial ports.
ASY Asynchronous serial port.
ETH Ethernet 10/100/1000 Mbit/sec.
CTIHA Card for HDLC controllers and DSPs. No PRI/BRI ports.
QPRI 4 Primary Rate E1 Interfaces (PRI).
PB44 4 PRI and 4 BRI interfaces.
BRI1 1 Basic Rate Interfaces (BRI).
BRI4 4 Basic Rate Interfaces (BRI).
BRI8 8 Basic Rate Interfaces (BRI).
BRIO Basic Rate Interface, data only.
POTS From 2 to 16 interfaces for analog telephones.
BS44 4 BRI and 4 POTS interfaces.
BS48 4 BRI and 8 POTS interfaces.
WL Wireless card 11 mbit/sec.
UG UMTS and GSM fake device for 32 GSM/UMTS devices.
CB CITOBOX device for 8 ports.
- USB devices:
ADSLUSB ADSL modem with USB interface.
CELL UMTS or GSM device.
CODEC Audio codec for every 2 UMTS or GSM devices.
SIMEMU SIM emulator for GSM or UMTS devices.
CELLBOX Container device for 2 CELL, 1 CODEC, 1 SIMEMU.
UMTSKEY UMTS 1 port device.
RJS RJ45 Switchboard USB device.
SIMBOX Sim Box USB device.
GPS GPS USB device.
GPIO General purpose input/output USB device.
BLUSB USB Boot Loader device.
CITO Signalling part of CITOBOX
AUDIO Audio part of CITOBOX
CITOBOX Container device for 1 CITO, 1 AUDIO.

For example, to add a POTS card:

[16:59:21] ABILIS_CPX:a dev:pots-1

COMMAND EXECUTED

Tip
Adding an ISDN card (QPRI, BRI8, BRI4, BRIO, POTS,…) or synchronous card (ESB), also the correlated
ports will be activated.

[23:59:39] ABILIS_CPX:a dev:brio-1

105
Draft Command language Draft

COMMAND EXECUTED

[23:59:50] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

---------------- Active ISA/PCI Cards and Physical Resources: -----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . . - 3F8 4
ETH100-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . . 8 PCI ( 12)
BRIO-1 No 91 . . . . . . . . . . . . . . . . . . . . . . NONE PCI ( -)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . . 10 PCI ( 12)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------

--------------- Inactive ISA/PCI Cards and Physical Resources: ----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE ISA/PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

[23:59:54] ABILIS_CPX:d p ctip:91

CTIP:91 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:
card:BRIO-1<1>
OPSTATE:UP LOG:NO side:TE LINE:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri-data NUM:*
BCHANS:ALL-BID

The “Not Saved (SAVE CONF)” message is displayed every time the configuration is modified but not
saved with the save conf command. The “Not Refreshed (INIT)” message is displayed every time the port
configuration is modified but not refreshed with the init res:ctisys command. These messages will disappear
after save conf or init res:ctisys commands.

5.5.3. S DEV (Set Device)

This command sets one or more configuration parameters of the specified device to the specified value.

For PCI devices, the command allows the user to set the PCI slot identifier of the board, i.e. SLOTID parameter.

For ISA devices, the command sets the memory address (ADDR parameter) and interrupt (IRQ parameter) of the device.

For USB devices, the command allows the user to set the USB port identifier of the device, i.e. USBPORTID parameter.

[17:30:52] ABILIS_CPX:s dev: ?

S DEV:val par:val [par:val] Set the specified Hw device parameter(s)

ADDR: Base Address value <ISA only>

IRQ: Interrupt value <ISA only>
SLOTID: Slot Id value [0..65534, NONE = Unassigned] <PCI only>
USBPORTID: Port Id value: from 1 up to 7 decimal values in the range
[0..14] joined by '.' (dot) or "NONE" (i.e. Unassigned)
<USB only>

106
Draft Command language Draft

5.5.4. C DEV (Clear Device)

This command allows to delete a device present in Abilis. A device, before being deleted, must be inactive. To inactive a
device type the command s inact dev: and reboot the Abilis with the command warm start.

For example:

[12:45:38] ABILIS_CPX:c dev:bri4-1

COMMAND NOT ALLOWED FOR THAT DEVICE, BECAUSE IT IS RUNNING

[12:45:38] ABILIS_CPX:s inact dev:bri4-1

COMMAND EXECUTED

After Abilis restart, it is possible to delete the device.

[18:17:04] ABILIS_CPX:c dev:bri4-1

THE SELECTED DEVICE AND THE RELATED PHYSICAL RESOURCE(s) WILL BE DELETED.
PROCEED (N/Y)?y

PROCEEDING WITH DEVICE DELETION...

COMMAND EXECUTED

5.6. Resources or Ports

5.6.1. D P (Display Parameters)
This command shows configuration parameters of one or more active CPX resources or ports. the following command
displays the command syntax:

[16:36:49] ABILIS_CPX:d p ?

D P RES:A Display parameter(s) of any resource

D P [RES:]type Display parameter(s) of any resource
of the specified type
D P [RES:]type-n[,...] Display parameter(s) of the specified
resource(s). Use '.' to avoid
recursion between resources.
D P CTIP[:val] Display parameter(s) of the specified
CTI port
D P CTIPE[:val] Display parameter(s) of the specified
CTI port in extended format

Configuration parameters are displayed using lower case and upper case characters. This kind of visualization is used to point
out that configuration parameters are grouped into two sets:

• parameters identified by lower case characters can be activated only by restarting the system;

• parameter identified by upper case characters can be activated by executing the initialization command init res:.

Here are some examples of the command execution:

[16:48:16] ABILIS_CPX:d p ssh

RES:Ssh -----------------------------------------------------------------------
Run DESCR:Secure_Shell_Protocol
LOG:NO MCAU:NO ps:128
KEEPALIVE:30 LOGIN-TOUT:60
WDIR:C:\APP\SSH\
- Server ---------------------------------------------------------------
PSER:SSHS> ser:3 tcp-locport:22
AC:YES PWD: DT:15

107
Draft Command language Draft

CDO:00 UDO:CP PROFILE:NORMAL

IPSRC:* IPSRCLIST:# MAXAUTH:6
KEYLEN:768 KEYREGENT:60 HOSTKEYLEN:1024
S-VER:1,2 S-AUTH-1:PWD S-AUTH-2:PWD
S-CIPHERS-1:ALL
S-CIPHERS-2:ALL
- Client ---------------------------------------------------------------
PCLI:SSHC> cli:3 MAXPROMPT:3
CDI:* UDI:*
C-VER:1,2 C-AUTH-1:PWD C-AUTH-2:PWD
C-CIPHERS-1:ALL DFT-CIPHER-1:3DES
C-CIPHERS-2:ALL DFT-CIPHER-2:3DES

[16:57:33] ABILIS_CPX:d p ctip:101

CTIP:101 DESCR:
Act card:POTS-1<1>
Run OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:11

[16:57:35] ABILIS_CPX:d p ctipe:101

CTIP:101 DESCR:
Act card:POTS-1<1>
Run OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:11
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:YES

5.6.2. A RES (Add Resource)

This command adds a new resource in the configuration. A resource may already exist in the system, but may not yet be
active; it can be activated with the command s act res:.

The following command allows to have a complete list of the available resources:

[16:59:21] ABILIS_CPX:a res: ?

A RES:val [SYBTYPE:val] Add CPX Resource of the selected type

RES: Resource identifier 'type-n', where 'n' can be [1..999] <Mandatory>

SUBTYPE: Resource subtype. Mandatory for X25, Sdlc, Hdlct, Fr,
Pv and Ip resource types only

Available resource's types:

- System resources:
Arc ARCHIVE service
Ssl Secure Socket Layer
MfIde Abilis Multi Function IDE Interface
X509 X509 certificate manager
UPnPC Universal Plug and Play Client
UPnPS Universal Plug and Play Server
- Management resources:
Cp Control port
Snmp Simple Network Management protocol

108
Draft Command language Draft

Sntp Simple Network Time protocol

Acnt Accounting service
Trfa Traffic Analyzer
SysLog System Log protocol
Opc Operator Panel Collector
GpioPc General Purpose I/O Panel Collector
- Connection Oriented Router resources:
X25 X.25 protocol
Sdlc SDLC/QLLC protocol
Hdlct HDLCT protocol
Pad PAD service
Xtp X25-L3 tunnelling protocol
Dummy Dummy resource
Sim Simulator resource
LPad Local PAD service
- IP resources:
Ip IP resource
Iprtr IP Router
Tcp TCP protocl
Udp UDP protocol
Telnet TELNET Server and Client
Rip Routing Information protocol
Dns Domain Name System
Http HyperText Transfer protocol
Nat Network Address Translator
Ssh Secure Shell protocol
Ospf Open Shortest Path First Routing protocol
Dhcp Dynamic Host Configuration protocol
Ftp File Transfer Protocol Server
IpSec IP Securityp rotocol
Ike Internet Keys Exchange protocol
Smtp Simple Mail Transfer protocol
Pop3 Post Office protocol Ver. 3
Radius RADIUS service
Vrrp Virtual Router Redundancy protocol
Stun Simple Traversal of UDP NATs
DhcpC Dynamic Host Configuration protocol Client
DDns Dynamic DNS Client
RSim Remote SIM
- PPP over Ethernet resources:
PoeAc Point-to-Point Protocol over Ethernet Access Concentrator
PoeCli Point-to-Point Protocol over Ethernet Client
- CTI resources:
CtiSys CTI System
CtiX25D X.25 Over ISDN D-Channel
CtiSLink HDLC Over ISDN B-Channel
CtiVsp Virtual Synchronous Port
CtiIax Inter-Asterisk eXchange Ver. 2
CtiDisa Direct Inward System Access
CtiSip Session Initiation protocol
CtiSms SMS service
CtiH323 ITU H.323 protocol
CtiGkc H.323 Gatekeeper
CtiTst CTI Tester
- Bridge resources:
Bridge IEEE Bridge
- Frame Relay resources:
Fr Frame Relay
- Pv and Ple resources:
Pv Packet voice resource
Ple P-Link emulation over IP resource
- Physical resources:

109
Draft Command language Draft

VEth Virtual Ethernet

For example, to add the Secure SHell resource (SSH):

[16:59:21] ABILIS_CPX:a res:ssh

COMMAND EXECUTED

If the resource is already present in the configuration, but not active, it is possible to activate it with the command:

[16:59:21] ABILIS_CPX:s act res:ssh

COMMAND EXECUTED

Tip
A lot of resources are automatically activated at the resource adding operation (i.e. Eth100, Adsl, Sync…)

5.6.3. S P (Set Parameters)

This command sets one or more configuration parameters of one or more active CPX resources or ports. By typing s p ?, it is
possible to display the command syntax:

[17:41:05] ABILIS_CPX:s p ?

S P RES:A par:val [par:val] Set specified parameter(s)

in any resource
S P [RES:]type par:val [par:val] Set specified parameter(s)
in any resource of the specified type
S P [RES:]type-n[,...] par:val [par:val]Set specified parameter(s)
of the specified resource(s)
S P CTIP:val Set specified parameter(s)
of the specified CTI port(s)
S P CTIPE:val Set specified parameter(s)
of the specified CTI port(s)

The parameter list, defined in the command, is left to right evaluated: the parameters are set one after the other, starting from
the leftmost. Command evaluating will terminate if one the following events will occur:

• bad parameter(s) to be set;

• value of the parameter(s) out of its allowed range;

• conflict between the parameter(s) to be set and others.

All the parameters evaluated, before the error occurrence, will get the new value; the other ones will not be changed.

Here there are some examples of the command execution:

[16:48:16] ABILIS_CPX:s p ssh pwd:password_ssh

COMMAND EXECUTED

[16:48:16] ABILIS_CPX:d p ssh

RES:Ssh -----------------------------------------------------------------------
Run DESCR:Secure_Shell_Protocol
LOG:NO MCAU:NO ps:128
KEEPALIVE:30 LOGIN-TOUT:60
WDIR:C:\APP\SSH\
- Server ---------------------------------------------------------------
PSER:SSHS> ser:3 tcp-locport:22
AC:YES PWD:**************** DT:15
CDO:00 UDO:CP PROFILE:NORMAL
IPSRC:* IPSRCLIST:# MAXAUTH:6
KEYLEN:768 KEYREGENT:60 HOSTKEYLEN:1024
S-VER:1,2 S-AUTH-1:PWD S-AUTH-2:PWD

110
Draft Command language Draft

S-CIPHERS-1:ALL
S-CIPHERS-2:ALL
- Client ---------------------------------------------------------------
PCLI:SSHC> cli:3 MAXPROMPT:3
CDI:* UDI:*
C-VER:1,2 C-AUTH-1:PWD C-AUTH-2:PWD
C-CIPHERS-1:ALL DFT-CIPHER-1:3DES
C-CIPHERS-2:ALL DFT-CIPHER-2:3DES

[17:46:26] ABILIS_CPX:s p ctip:91 descr:To_Telecom side:TE

COMMAND EXECUTED

[17:47:00] ABILIS_CPX:d p ctip:91

CTIP:91 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:To_Telecom
card:BRIO-1<1>
OPSTATE:UP LOG:NO side:TE LINE:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri-data NUM:*
BCHANS:ALL-BID

Tip
The “Not Saved (SAVE CONF)” message is displayed every time the resource configuration is modified but
not saved with the save conf command. The “Not Refreshed (INIT)” message is displayed every time the
port configuration is modified but not refreshed with the init res: command. These messages will disappear
after save conf or init res: commands.

Tip
To activate changes made on the parameters displayed by upper case characters, it is enough to execute the
initialization command init res:; for changes made on parameters displayed by lower case characters, it is
needed to restart the system with the command warm start.

5.6.4. C RES (Clear Resource)

This command allows to delete a resource present in Abilis. A resource, before being deleted, must be inactive. To inactive a
device type the command s inact res: and reboot the Abilis with the command warm start.

For example:

[12:45:38] ABILIS_CPX:c res:ssh

COMMAND NOT ALLOWED FOR 'RES:SSH' BECAUSE IT IS RUNNING

[12:45:38] ABILIS_CPX:s inact res:ssh

COMMAND EXECUTED

After Abilis restart, it is possible to delete the resource.

[18:17:04] ABILIS_CPX:c res:ssh

THE SELECTED RESOURCE WILL BE DELETED.

PROCEED (N/Y)?y

THE COMMAND WILL DELETE ALL THE REFERENCES TO THE SELECTED RESOURCE.
PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH RESOURCE DELETION...

COMMAND EXECUTED

111
Draft Command language Draft

5.7. Initialization/activation/deactivation commands

5.7.1. INIT
These commands allow to reinitialize and active parameters modified on ports and resources written in upper case characters
or refresh any tables updating. The following command allows to display the command syntax:

[12:45:38] ABILIS_CPX:init ?

CTIH323 Refreshes CTI H.323 Translation table content

CTIG Unsupported. Use INIT CTIR to refresh entries in CTI groups
CTIR Refreshes entries in CTI routings, CTIG tables and CTICL list(s)
CTISYS Refreshes parameters of CTISYS resource (RES:CtiSys) and
refreshes entries in CTI ports, clusters and LCS groups
IP Refreshes IP resources and purges queues
IPAD Refreshes IP Routing Administrative Distances
IPLB Refreshes IP Load Balancing definitions
IPR Rebuild IP Routings table
LCSG Unsupported. Use INIT CTISYS to refresh entries in LCS groups
NAT Refreshes the static table and clears the dynamic table content
RES: Refreshes parameters of a resource
USBDEV Refreshes USB Service

For example, to initialize the CTI Routing table:

[12:45:39] ABILIS_CPX:init ctir

COMMAND EXECUTED

The command init res: initializes the specified resource(s), if it is currently active and running. At the same time the
command updates configuration parameters that have been modified, activating them. The following command allows to
display the command syntax:

[12:45:39] ABILIS_CPX:init res: ?

INIT RES:A Refresh parameter(s) of any resource.

INIT RES:type Refresh parameter(s) of any resource
of the specified type.
INIT RES:type-n Refresh parameter(s) of the specified
resource.

The command will work on present, active and running resources only; otherwise the error message “RESOURCE NOT
PRESENT OR INACTIVE” will be displayed.

5.7.2. D ACT
This command displays all the cards and resources currently configured and active. Cards and resources are active, if they are
configured (present), but not necessarily running.

Setting changes and visualization are allowed only for active card and resources. Cards and resources are running only if they
are configured (present) and active when the system starts.

Here is an example of the command execution:

[11:38:04] ABILIS_CPX:d act

---------------- Active ISA/PCI Cards and Physical Resources: -----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . . - 3F8 4
ETH100-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 11)
QPRI-1 No 1..4 . . . . . . . . . . . . . . . . . . . . . 6 PCI ( 10)
BRI4-2 Yes 35..38 . . . . . . . . . . . . . . . . . . . . 6 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . . 8 PCI ( 12)
POTS-2 Yes 117..132 . . . . . . . . . . . . . . . . . . . 10 PCI ( 10)

112
Draft Command language Draft

GSM-1 Yes 201..232 . . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes Yes Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes Yes Adsl-2 . . . . . . . . . . . . . . . . 0.1
GSMUSB-1 Yes Yes . . . . . . . . . . . . . . . . . . . . 0.0.1.0
GSMUSB-2 Yes Yes . . . . . . . . . . . . . . . . . . . . 0.0.1.1
GSMCODEC-1 Yes Yes GSMUSB-1,GSMUSB-2 . . . . . . . . . . . 0.0.1.2

-------------------------- Active System Resource(s) --------------------------

Type Resource(s)
-------------------------------------------------------------------------------
MfIde 1

------------------------ Active Management Resource(s) ------------------------

Type Resource(s)
-------------------------------------------------------------------------------
Cp 1
Snmp 1
Sntp 1
Acnt 1
Trfa 1

---------------- Active Connection Oriented Router Resource(s) ----------------

Type Resource(s)
-------------------------------------------------------------------------------
X25 1 2 999
Pad 1

---------------------------- Active IP Resource(s) ----------------------------

Type Resource(s)
-------------------------------------------------------------------------------
Iprtr 1
Tcp 1
Udp 1
Telnet 1
Dns 1
Http 1
Nat 1
Ssh 1
Ftp 1
Ip 1 2 3 4 5 6 7 8 10 12 13 14

---------------- Active PPP over Ethernet Resource(s) --------------------------

Type Resource(s)
-------------------------------------------------------------------------------
PoeAc 1

--------------------------- Active CTI Resource(s) ----------------------------

Type Resource(s)
-------------------------------------------------------------------------------
CtiSLink 1
CtiSys 1
CtiH323 1
CtiIax 1
CtiDisa 1

-------------------------- Active Bridge Resource(s) --------------------------

Type Resource(s)
-------------------------------------------------------------------------------

113
Draft Command language Draft

*** NO ACTIVE BRIDGE RESOURCEs PRESENT ***

----------------------- Active Frame Relay Resource(s) ------------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO ACTIVE FRAME RELAY RESOURCEs PRESENT ***

------------------------ Active Pv and Ple Resource(s) -----------------------

Type Resource(s)
-------------------------------------------------------------------------------
Pv 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
35 36 37 38 39 40 41 42

------------------------- Active Physical Resource(s) -------------------------

Type Resource(s)
-------------------------------------------------------------------------------
Async 1
Eth100 1
Adsl 1 2

5.7.3. S ACT
These commands set active the specified card(s) or resource(s). The following command allows to display the command
syntax:

[12:45:39] ABILIS_CPX:s act ?

CTIP: CTI port identifier [1..300]

DEV: Hw device identifier 'type-n', where 'n' can be [1..255]
RES: Resource identifier 'type-n', where 'n' can be [1..999]

Warning
Activating a card or a resource does not mean to make it run. Activation makes possible to show card's/
resource's parameters and to modify them. To have a running card/resource or activate the changes made on
the card/resource, it is needed to save the configuration and restart the system.

5.7.4. D INACT
This command shows all the cards and resources currently configured but inactive. A card (resource) is inactive (or not
active) when it is present but it is not running.

Setting changes and visualization are not allowed for inactive cards/resources. Moreover configured but inactive cards/
resources are ignored when the system starts.

[11:38:04] ABILIS_CPX:d inact

--------------- Inactive ISA/PCI Cards and Physical Resources: ----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
BRI4-1 No 31..34 . . . . . . . . . . . . . . . . . . . . NONE PCI ( -)

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

------------------------- Inactive System Resource(s) -------------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE SYSTEM RESOURCEs PRESENT ***

114
Draft Command language Draft

----------------------- Inactive Management Resource(s) -----------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE MANAGEMENT RESOURCEs PRESENT ***

--------------- Inactive Connection Oriented Router Resource(s) ---------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE CONNECTION ORIENTED ROUTER RESOURCEs PRESENT ***

--------------------------- Inactive IP Resource(s) ---------------------------

Type Resource(s)
-------------------------------------------------------------------------------
Rip 1
Ospf 1
Dhcp 1
Ip 9

--------------- Inactive PPP over Ethernet Resource(s) -------------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE PPPoE RESOURCEs PRESENT ***

-------------------------- Inactive CTI Resource(s) ---------------------------

Type Resource(s)
-------------------------------------------------------------------------------
CtiX25D 1
CtiVsp 1

------------------------- Inactive Bridge Resource(s) -------------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE BRIDGE RESOURCEs PRESENT ***

---------------------- Inactive Frame Relay Resource(s) -----------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE FRAME RELAY RESOURCEs PRESENT ***

----------------------- Inactive Pv and Ple Resource(s) ----------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE PV or PLE RESOURCEs PRESENT ***

------------------------ Inactive Physical Resource(s) ------------------------

Type Resource(s)
-------------------------------------------------------------------------------
*** NO INACTIVE PHYSICAL RESOURCEs PRESENT ***

5.7.5. S INACT
These commands set inactive the specified card(s) or resource(s).

[12:45:39] ABILIS_CPX:s inact ?

CTIP: CTI port identifier [1..300]

DEV: Hw device identifier 'type-n', where 'n' can be [1..255
RES: Resource identifier 'type-n', where 'n' can be [1..999]

115
Draft Command language Draft

Warning
Deactivating a board or a port does not mean to make it not run, if it was running after the system start.
Deactivation makes not possible to show card's/resource's parameters and to modify them. To make a card/
port not running, it is needed to save the configuration and restart the system.

5.7.6. D RUN
This command shows all the currently running resources and cards. The running resources and cards are the ones which are
configured and active when at the system start.

A resource/card is still running even if it has been deactivated through the command s inact.

[11:38:04] ABILIS_CPX:d run

Running resources:

+------------+-----+----------------------------------------------------------+
| Resource | Act | Description |
+------------+-----+----------------------------------------------------------+
| Async-1 | Yes | |
| Blusb-1 | Yes | USB_Boot_Loader |
| Eth-1 | Yes | |
| Eth-2 | Yes | |
| Eth-3 | Yes | |
| Eth-4 | Yes | |
| Adsl-1 | Yes | |
| Adsl-2 | Yes | |
| Adsl-3 | Yes | |
| Rjs-1 | Yes | |
| SimBox-1 | Yes | |
| Gps-1 | Yes | |
| Gpio-1 | Yes | |
| Cp | Yes | Control_Port |
| Snmp | Yes | Simple_Network_Management_Protocol |
| Sntp | Yes | Simple_Network_Time_Protocol |
| Acnt | Yes | Accounting_Service |
| Trfa | Yes | Traffic_Analyzer |
| SysLog | Yes | System_Log_protocol |
| Opc | Yes | Operator_Panel_Collector |
| X25-50 | Yes | |
| X25-51 | Yes | |
| X25-52 | Yes | |
| X25-53 | Yes | |
| X25-54 | Yes | |
| X25-55 | Yes | |
| X25-56 | Yes | |
| X25-57 | Yes | |
| X25-58 | Yes | |
| X25-59 | Yes | |
| X25-999 | Yes | Resource_for_remote_maintenance |
| Pad-1 | Yes | |
| Xtp-1 | Yes | |
| Sim-50 | Yes | |
| Sim-51 | Yes | |
| Sim-52 | Yes | |
| Sim-53 | Yes | |
| Sim-54 | Yes | |
| Sim-55 | Yes | |
| Sim-56 | Yes | |
| Sim-57 | Yes | |
| Sim-58 | Yes | |

116
Draft Command language Draft

| Sim-59 | Yes | |
| CtiX25D | Yes | X.25_Over_ISDN_D-Channel |
| CtiSLink | Yes | HDLC_Over_ISDN_B-Channel |
| CtiVsp | Yes | Virtual_Synchronous_Port |
| CtiSys | Yes | CTI_System_general_properties |
| CtiIax | Yes | IAX2 |
| CtiDisa | Yes | Direct_Inward_System_Access |
| CtiSip | Yes | Session_Initiation_Protocol |
| CtiSms | Yes | Short_Message_Service |
| CtiAs | Yes | Cti_AS |
| Iprtr | Yes | IP_Router_general_properties |
| Tcp | Yes | Transmission_Control_Protocol |
| Udp | Yes | User_Datagram_Protocol |
| Telnet | Yes | Telnet_Server_and_Client_entities |
| Rip | Yes | Routing_Information_Protocol |
| Dns | Yes | Domain_Name_System |
| Http | Yes | HyperText_Transfer_Protocol |
| Nat | Yes | Network_Address_Translator |
| Ssh | Yes | Secure_Shell_Protocol |
| Ospf | Yes | Open_Shortest_Path_First_Routing_Protocol |
| Dhcp | Yes | Dynamic_Host_Configuration_Protocol |
| Ftp | Yes | File_Transfer_Protocol_Server |
| IpSec | Yes | IP_Security_Protocol |
| Ike | Yes | Internet_Keys_Exchange_Protocol |
| Smtp | Yes | Simple_Mail_Transfer_Protocol |
| Pop3 | Yes | Post_Office_Protocol_Ver3 |
| Radius | Yes | Remote_Authentication_Dial_In_User_Service |
| Vrrp | Yes | Virtual_Router_Redundancy_Protocol |
| DhcpC | Yes | Dynamic_Host_Configuration_Protocol_Client |
| DDns | Yes | Dynamic_DNS_Protocol_Client__antekdyndns-abilisantek |
| RSim-1 | Yes | |
| Fr-1 | Yes | |
| Fr-2 | Yes | |
| Pv-1 | Yes | |
| Pv-2 | Yes | |
| Pv-5 | Yes | |
| Pv-10 | Yes | |
| Pv-11 | Yes | |
| Pv-200 | Yes | |
| PoeAc-1 | Yes | |
| PoeCli-1 | Yes | |
| PoeCli-2 | Yes | |
| Ip-1 | Yes | |
| Ip-2 | Yes | |
| Ip-3 | Yes | |
| Ip-4 | Yes | |
| Ip-35 | Yes | |
| Ip-50 | Yes | ADSL |
| Ip-51 | Yes | |
| Ip-52 | Yes | |
| Ip-53 | Yes | |
| Ip-55 | Yes | |
| Ip-60 | Yes | |
| Ip-61 | Yes | |
| Ip-62 | Yes | |
| Ip-63 | Yes | |
| Ip-71 | Yes | |
| Ip-131 | Yes | |
| Ip-150 | Yes | |
| Ip-160 | Yes | |
| Ip-200 | Yes | |
| Ip-201 | Yes | |

117
Draft Command language Draft

| Ip-250 | Yes | |
| Bridge-1 | Yes | |
| Ssl | Yes | Secure_Socket_Layer |
| MfIde | Yes | Abilis_Multi_Function_IDE_Interface |
| UPnPS | Yes | Universal_Plug_and_Play_Server |
+------------+-----+----------------------------------------------------------+

Running CTI ports:

+------+----------+-----+-----------------------------------------------------+
| CTIP | Card | Act | Description |
+------+----------+-----+-----------------------------------------------------+
| 31 | BRI8-1 | Yes | |
| 32 | BRI8-1 | Yes | |
| 33 | BRI8-1 | Yes | |
| 34 | BRI8-1 | Yes | |
| 35 | BRI8-1 | Yes | |
| 36 | BRI8-1 | Yes | |
| 37 | BRI8-1 | Yes | |
| 38 | BRI8-1 | Yes | |
| 101 | POTS-1 | Yes | test_port_101 |
| 102 | POTS-1 | Yes | |
| 103 | POTS-1 | Yes | |
| 104 | POTS-1 | Yes | |
| 117 | POTS-2 | Yes | |
| 118 | POTS-2 | Yes | |
| 201 | UG-1 | Yes | SIM |
| 202 | UG-1 | Yes | |
| 203 | UG-1 | Yes | |
| 204 | UG-1 | Yes | |
| 208 | UG-1 | Yes | |
| 241 | CB-1 | Yes | |
| 242 | CB-1 | Yes | |
+------+----------+-----+-----------------------------------------------------+

Running hardware devices:

+-----+--------------+-----+------+-----------+
| Ind | Device | Act | Type | Connected |
+-----+--------------+-----+------+-----------+
| 2 | ASY-1 | Yes | ISA | - |
| 3 | ADSLUSB-1 | Yes | USB | Yes |
| 4 | ADSLUSB-2 | Yes | USB | No |
| 5 | ADSLUSB-3 | Yes | USB | No |
| 7 | ETH-1 | Yes | PCI | - |
| 8 | POTS-1 | Yes | PCI | - |
| 9 | UG-1 | Yes | PCI | - |
| 10 | CELL-1 | Yes | USB | No |
| 11 | CELL-2 | Yes | USB | No |
| 12 | CODEC-1 | Yes | USB | No |
| 15 | RJS-1 | Yes | USB | No |
| 16 | GPS-1 | Yes | USB | No |
| 17 | POTS-2 | Yes | PCI | - |
| 18 | CELL-3 | Yes | USB | No |
| 19 | CELL-4 | Yes | USB | No |
| 20 | CODEC-2 | Yes | USB | No |
| 21 | SIMEMU-2 | Yes | USB | No |
| 22 | SIMEMU-1 | Yes | USB | No |
| 23 | ETH-2 | Yes | PCI | - |
| 26 | BRI8-1 | Yes | PCI | - |
| 27 | BLUSB-1 | Yes | USB | No |
| 28 | GPIO-1 | Yes | USB | No |

118
Draft Command language Draft

| 29 | SIMBOX-1 | Yes | USB | Yes |

| 31 | CB-1 | Yes | PCI | - |
| 32 | CITO-1 | Yes | USB | No |
| 33 | AUDIO-1 | Yes | USB | No |
| 34 | UMTSKEY-8 | Yes | USB | No |
| 35 | ETH-3 | Yes | PCI | - |
| 36 | ETH-4 | Yes | PCI | - |
+-----+--------------+-----+------+-----------+

5.7.7. D TREE
This command shows the real status of the connections among protocol resources and the physical link. Resources can be
split into 7 groups:

• System Resource(s)

• Management Resource(s)

• Connection Oriented Router Resource(s)

• IP Resource(s)

• CTI Resource(s)

• Wireless to G.703 bridge

• Unconnected Physical Resource(s)

Before showing the resources connections, the command automatically executes a validation of the current configuration. If
the validation is successful, the command will be executed, otherwise it won't.

For more details on the configuration validation procedure see the section Section 5.12, “Configuration validating and
saving”.

[11:38:04] ABILIS_CPX:d tree

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

----------------------------- System Resource(s) ------------------------------

Ssl
MfIde
UPnPS
\---Tcp
\---Udp

--------------------------- Management Resource(s) ----------------------------

Cp
Snmp
\---Udp
Sntp
\---Udp
Acnt
\---Tcp
Trfa
SysLog
\---Udp
Opc
\---Tcp

------------------- Connection Oriented Router Resource(s) --------------------

119
Draft Command language Draft

X25-50
\---CtiSLink
X25-51
\---CtiSLink
X25-52
\---CtiSLink
X25-53
\---CtiSLink
X25-54
\---CtiSLink
X25-55
\---CtiSLink
X25-56
\---CtiSLink
X25-57
\---CtiSLink
X25-58
\---CtiSLink
X25-59
\---CtiSLink
X25-999
\---CtiSLink
Pad-1
\---Async-1
Xtp-1
\---Tcp
Sim-50
Sim-51
Sim-52
Sim-53
Sim-54
Sim-55
Sim-56
Sim-57
Sim-58
Sim-59

------------------------------- IP Resource(s) --------------------------------

Iprtr
\---Ip-1
\---Eth-1
\---Ip-2
\---Eth-2
\---Ip-3
\---Ip-4
\---Eth-4
\---Ip-35
\---CtiSLink
\---Ip-50
\---Adsl-1
\---Ip-51
\---Adsl-1
\---Ip-52
\---Adsl-3
\---Ip-53
\---CtiSLink
\---Ip-55
\---Ip-60
\---Fr-1
\---Sync-3
\---Ip-61
\---Ip-62

120
Draft Command language Draft

\---PoeAc-1
\---Eth-1
\---Ip-63
\---PoeAc-1
\---Eth-1
\---Ip-71
\---PoeCli-1
\---Eth-4
\---Ip-131
\---Ip-150
\---CtiSLink
\---Ip-160
\---Ip-200
\---Fr-1
\---Sync-3
\---Ip-201
\---Fr-2
\---Sync-4
\---Ip-250
Tcp
Udp
Telnet
\---Tcp
Rip
\---Udp
Dns
\---Udp
Http
\---Tcp
Nat
Ssh
\---Tcp
Ospf
Dhcp
\---Udp
Ftp
\---Tcp
IpSec
Ike
\---Udp
Smtp
\---Tcp
Pop3
\---Tcp
Radius
\---Udp
Vrrp
DhcpC
\---Udp
DDns
\---Tcp
RSim-1
\---Udp

-------------------- PPPoE Access Concentrator Resource(s) --------------------

PoeAc-1
\---Eth-1

------------------------------- CTI Resource(s) -------------------------------

CtiX25D
CtiSLink
CtiVsp

121
Draft Command language Draft

CtiSys
\---CTIP:101..116 (POTS-1)
\---CTIP:201..232 (UG-1)
\---CTIP:117..132 (POTS-2)
\---CTIP:133..148 (POTS-3)
\---CTIP:1..4 (QPRI-1)
\---CTIP:31..38 (BRI8-1)
\---CTIP:241..248 (CB-1)
\---CTIP:49..52 (QPRI-13)
\---(CTIL: 1) Pv-1
\---CtiSLink
\---Udp
\---(CTIL: 2) Pv-2
\---CtiSLink
\---Udp
\---(CTIL: 5) Pv-5
\---Udp
\---(CTIL: 10) Pv-10
\---Udp
\---(CTIL: 11) Pv-11
\---Udp
CtiIax
\---Udp
CtiDisa
CtiSip
\---Tcp
\---Udp
CtiSms
CtiAs

----------------------------- Bridge Resource(s) ------------------------------

Bridge-1

-------------------------- Wireless to G.703 bridge ---------------------------

*** NO ACTIVE G.703 or WIRELESS RESOURCEs PRESENT ***

--------------- Unconnected Fr, PoeCli, Pv and Ple Resource(s) ----------------

Pv-200
\---CtiSLink
PoeCli-2
\---Adsl-2

---------------------- Unconnected Physical Resource(s) -----------------------

Sync-1
Sync-2
Blusb-1
Eth-3
Rjs-1
SimBox-1
\---RSim-1
\---Udp
Gps-1
Gpio-1

5.7.8. ALARM VIEW and ALARM RESET

The command alarm view shows a list of the resources in error conditions that have generated the alarm.

[11:38:04] ABILIS_CPX:alarm view

RES:Pv-6 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) -----------

To_Abilis_6

122
Draft Command language Draft

- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | DOWN | DOWN1 | LINK-NOT-PRESENT |
+--------+---------------+----------------------+----------------------+

RES:Pv-12 - PV over IP (Abilis tunnel) (IP) -----------------------------------

To_Abilis_12
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | DOWN | DOWN1 | LINK-NOT-PRESENT |
+--------+---------------+----------------------+----------------------+

If there are no alarmed resources when the command is executed, the message “NO ALARMED RESOURCES” will be
shown.

Resources alarms are detected by a proper procedure, which is executed every 30 seconds and is activated setting the A
option in the LLOG parameter. If the L option is also set in the LLOG parameter, on alarm detection, acoustic signal and
message on the LCD display are generated.

The command alarm reset activates a reset procedure of error conditions that generated the alarm.

[11:38:04] ABILIS_CPX:alarm reset

COMMAND EXECUTED

5.7.9. CALL RES and DISC RES

The command call res: opens a connection on the specified resources. The resource value must be in the interval [0 - 999]
and has to correspond to a resource that is active and running.

The command can work only on MLM and PPP resource types, otherwise the message “COMMAND NOT ALLOWED
FOR 'RES:type-nnn” is generated.

[11:38:04] ABILIS_CPX:call res:pv-1

COMMAND EXECUTED

Open connection must be closed using the disc res: command.

If the command has been already executed on the specified resource, while the disc res: one was not, then the message
“CONNECTION ALREADY OPENED” will be displayed. The command will work only on present, active and running
resources; otherwise the error message “RESOURCE NOT PRESENT OR NOT RUNNING” will be displayed.

[11:38:04] ABILIS_CPX:disc res:pv-1

COMMAND EXECUTED

5.8. General and system information

5.8.1. D G (Display General)
This command shows general parameters about the system (i.e. system start-up elapsed time, date and time, customizable
description fields, time zone…).

Not all the shown parameters can be changed; the note “<Read Only>” refers the not modifiable ones.

[11:38:04] ABILIS_CPX:d g

Conf.Value Act.Value Description

-------------------------------------------------------------------------------
tact: YES YES Automatic TRACE activation at start-up [NO, YES]
TSAVE: YES YES Automatic TRACE saving [NO, YES]
sound: ON ON Alarm sound enable/disable [OFF, ON]
wdg: - MFIDE3 Front Panel/WatchDog interface type <Read Only>

123
Draft Command language Draft

-------------------------------------------------------------------------------
listitems: 4000 (390 Kb)
dbgsize: 20 (Kb)
DBGF: ALL
DBGSYSLOG: ALL
CONTACT:
SYSNAME: cpx-test-208
LOCATION:
SYSUPTIME: 0 days 03:02:37 (Thursday 16/12/2010 13:05:38) <Read Only>
SYSRBTIME: # (System Reboot time not set)
DATE&TIME: Thursday 16/12/2010 16:08:15 (UTC+1.00) <Read Only>
TIMEZONE: CET - Central Europe (Rome, Paris, Berlin, Prague, Brussels)
ABILIS-ID: 2001 <Read Only>

5.8.2. D I (Display Information)

This command displays the software version currently in use on the Abilis CPX, information about system memory and files
on the disk.

[11:38:04] ABILIS_CPX:d i

Abilis CPX - Ver. 7.0.3/STD - 24/11/2010 - Build 3357.17 - 24/11/2010

(c) 1994/2010 - Abilis

ABILIS-ID: 2349

Free/Total Memory: 3,668,432/67,108,864 Largest Block: 3,657,808

Free/Used/Total HD/CF space (in KB): 74,604/53,240/127,844

File Version Date Time Size Note

-------------------------------------------------------------------------------
CPX.RTB ....... 24/11/2010 21:43:20 4189385
DRIVERS.CFG v.7.0 13/01/2011 15:56:18 18432 Ok
DRIVERS.BCK v.7.0 13/01/2011 15:56:18 18432 Ok
CPX.LOG v.1.0 13/01/2011 15:56:48 51200
CPX.DBG v.1.1 13/12/2010 10:29:40 20480
CPX.XCP ....... 13/12/2010 10:29:38 51200
BS44.BIN v.13.12 19/11/2010 15:25:52 90112
BS48.BIN v.4.7 16/04/2010 19:25:10 90112
ESB2.BIN v.13.0 28/10/2004 18:38:20 17408
DELICPRG.BIN v.16.0 28/10/2004 18:38:20 6144
D1K.BIN v.312.9 30/05/2008 18:31:16 1024
D1C4F3.BIN v.312.9 30/05/2008 18:31:16 100352
D1C5F3.BIN v.312.9 30/05/2008 18:31:16 100352
D2K.BIN v.312.9 30/05/2008 18:31:16 1024
D2C4F3.BIN v.312.9 30/05/2008 18:31:16 102400
D2C4F6.BIN v.312.9 30/05/2008 18:31:16 102400
D8K.BIN v.312.9 30/05/2008 18:31:16 1024
D8C2F1.BIN v.312.9 30/05/2008 18:31:16 91136
D8C2F2.BIN v.312.9 30/05/2008 18:31:16 94208
D8C2F3.BIN v.312.9 30/05/2008 18:31:16 96256
HFC2B4.BIN v.21.0 30/07/2009 09:57:22 16384
HFC2E4.BIN v.21.0 30/07/2009 09:57:22 16384
HFC2B8.BIN v.21.0 30/07/2009 09:57:22 16384
HFC2E8.BIN v.21.0 30/07/2009 09:57:22 16384
HFC3E4.BIN v.48.0 13/08/2009 19:53:22 86016
HFC3E8.BIN v.48.0 13/08/2009 19:53:22 87040
QPRI2B.BIN v.5.0 29/12/2004 15:00:34 17408
QPRI2E.BIN v.6.0 03/03/2005 19:44:34 17408
CTIHA2.BIN v.8.0 29/06/2005 10:33:42 18432
D64A.BIN v.31.15 20/10/2010 16:22:54 69632
D64V.BIN v.6.15 25/10/2010 11:46:10 138240

124
Draft Command language Draft

QPRIX.BIN v.24.0 13/08/2009 19:53:22 251904

OCTASIC.BIN v.16.0 18/06/2008 19:31:40 175104
STH330-P.BIN v.30.12 24/02/2005 20:25:46 388096
STHUSB-I.BIN ....... .......... ........ .......... Not found
STAR-P-1.BIN v.1.0 16/11/2010 17:13:30 9216
STAR-P-2.BIN v.1.0 16/11/2010 17:13:30 212992
STAR-P-3.BIN v.1.0 16/11/2010 17:13:30 1024
SL-IT.BIN v.1.0 28/10/2004 18:38:20 1024
SRVSSL.CER ....... 28/10/2004 18:38:20 820
CLISSL.CER ....... 28/10/2004 18:38:20 820
SRVSSL.KEY ....... 28/10/2004 18:38:20 981
CLISSL.KEY ....... 28/10/2004 18:38:20 969

Other system relevant files:

File Version Date Time Size Note

-------------------------------------------------------------------------------
C:\APP\CTI\ADDRBOOK\ADDRBOOK.DAT
v.1.0 22/11/2010 10:05:20 140066
C:\APP\CTI\LCS\LCSTABLE.DAT
v.1.0 13/01/2011 18:56:12 60066
C:\APP\DHCP\DHCP.BND
v.1.0 13/01/2011 15:56:14 25600

Other files in 'C:\7-0-3':

File Date Time Size Note

-------------------------------------------------------------------------------

The first part of the output is dedicated to the information about version and release date of the software.

The second one shows information about Abilis CPX serial number, system memory and disk.

The third part of the output displays information related to system relevant files, i.e. files used by Abilis during its working
(e.g. configuration and configuration backup files, System Log file, ...).

The “Other system relevant files” section displays information about any other system relevant additional files (e.g. DHCP
bindings file, ...).

The “Other files:” section shows information about any other additional file that is found on the disk, in the current working
version directory.

Eventual detected errors are highlighted with the string “ERR[xx]”, where “xx” is the error code detected; it should be
eventually told to the Abilis CPX assistance.

5.8.3. D VER (Display Versions)

This command shows the version of the software and its modules currently in used by the Abilis CPX.

[11:38:04] ABILIS_CPX:d ver

Abilis CPX - Ver. 7.0.2/STD - 12/10/2010 - Build 3357.4 - 12/10/2010

(c) 1994/2010 - Abilis

CX : v. 2483.2 - 07/10/2010 CP : v. 5005.7 - 12/10/2010

COR : v. 2036 - 09/02/2010 CNFG : v. 3788.8 - 08/10/2010
COMMON : v. 3099 - 21/09/2010 LICENCE : v. 2032.3 - 06/10/2010
SSL : v. 2028 - 15/07/2010 CRYPT : v. 2016 - 17/04/2008
PCISRV : v. 2099 - 22/09/2010 WDG : v. 2065 - 04/05/2010
USB : v. 2088.1 - 07/10/2010 FP : v. 2013 - 25/02/2008
BLUSB : v. 2020.1 - 04/10/2010 MFIDE : v. 2046 - 03/03/2009
SYNC-ESB : v. 2087 - 22/09/2010 SDLC : v. 2019 - 16/07/2010
SYNC-ESB2 : v. 2116 - 16/07/2010 LAPB : v. 2014 - 16/07/2010
HDLCT : v. 2014 - 16/07/2010 X25 : v. 2020 - 16/07/2010

125
Draft Command language Draft

FR : v. 2037 - 16/07/2010 MLM : v. 2103 - 16/07/2010

ML : v. 2096 - 16/07/2010 ASYNC : v. 2016 - 16/07/2010
PAD : v. 2023 - 16/07/2010 ETH : v. 2304 - 16/07/2010
TR : - Module not present - ADSL : v. 2202 - 16/07/2010
ACNT : v. 2043 - 14/07/2010 IPLAN : v. 2061 - 04/08/2010
IPRTR : v. 2463.6 - 06/10/2010 ICMP : v. 2095 - 17/09/2010
TCP : v. 2108 - 13/04/2010 UDP : v. 2069 - 13/04/2010
VRRP : v. 2042 - 14/07/2010 STUN : - Module not present -
TELNET : v. 2070.1 - 01/10/2010 HTTP : v. 2676.5 - 08/10/2010
SNMP : v. 2487 - 24/09/2010 RIP : v. 2060 - 14/07/2010
OSPF : v. 2107 - 14/07/2010 SNTP : v. 2035 - 16/07/2010
DNS : v. 2068 - 16/07/2010 DDNS : v. 2032 - 07/09/2010
XTP : v. 2029 - 16/07/2010 PLINKE : v. 2105 - 23/03/2010
NAT : v. 2238.2 - 29/09/2010 PPP : v. 2190 - 02/09/2010
SSH : v. 2135.1 - 91/10/2010 POECLI : v. 2059 - 16/07/2010
DHCP : v. 2105 - 16/07/2010 POEAC : v. 2097 - 16/07/2010
FTPSRV : v. 2143 - 16/07/2010 SMTP : v. 2212.4 - 07/10/2010
POP3 : v. 2052.1 - 30/09/2010 TRFA : v. 2069 - 15/07/2010
IPSEC : v. 2088 - 21/09/2010 IKE : v. 2172.1 - 30/09/2010
X509 : v. 2018 - 15/07/2010 UPNPC : v. 2059 - 15/07/2010
UPNPS : v. 2059 - 15/07/2010 BRIDGE : v. 2042 - 16/07/2010
ARCHIVE : v. 2087 - 14/07/2010 WL : - Module not present -
GC : - Module not present - WGB : - Module not present -
BRIO : v. 2068 - 29/09/2009 LAPD : v. 2080 - 04/03/2009
Q931 : v. 2545 - 09/09/2010 sQ931 : v. 2002 - 03/11/2002
CTI-HW : v. 2783.2 - 08/10/2010 CTI-RTR : v. 3384 - 24/09/2010
CTI-H323 : - Module not present - CTI-GKC : - Module not present -
CTI-IAX : v. 2607 - 27/07/2010 CTI-DISA : v. 2211 - 26/04/2010
CTI-SIP : v. 2585 - 03/08/2010 CTI-SMS : v. 2103.1 - 07/10/2010
VMS : v. 2061 - 25/03/2010 OPC : v. 2131 - 30/07/2010
SYSLOG : v. 2011 - 16/07/2010 RJS : v. 2041 - 14/07/2010
SIMBOX : v. 2063 - 04/08/2010 GPS : v. 2023 - 16/07/2010
GPIO : v. 2077 - 15/09/2010 GPIOPC : v. 2018 - 15/07/2010
SIM : v. 2022 - 04/08/2010 DUMMY : - Module not present -
VETH : - Module not present -

The first part is dedicated to the information about version and release date of the software.

In the second one, there is a list of all the Abilis CPX software modules. The string “Module not present” refers to the
modules that do not belong to the Abilis CPX software currently in use.

5.8.4. CPU
The command d cpu estimates the average CPU load over a given time interval. It gives an estimated percentage load for the
last 1 second, 15 seconds and 5 minutes.

This command also shows the CPU speed.

[11:38:04] ABILIS_CPX:d cpu

CPU speed: 1002 Mhz

+----------+--------------+--------------+--------------+
| | Last 1 sec. | Last 15 sec. | Last 5 min. |
+----------+--------------+--------------+--------------+
| CPU Load | 6% | 6% | 6% |
+----------+--------------+--------------+--------------+

The command d cpuid shows general information about the CPU of the Abilis CPX.

[11:38:04] ABILIS_CPX:d cpuid

eax in eax ebx ecx edx

00000000 00000002 756E6547 6C65746E 49656E69

126
Draft Command language Draft

00000001 000006B1 00000003 00000000 0383F9FF

00000002 03020101 00000000 00000000 0C040882

80000000 80000004 00000000 00000000 00000000

80000001 00000000 00000000 00000000 00000000
80000002 65746E49 2952286C 6C654320 6E6F7265
80000003 294D5428 55504320 20202020 20202020
80000004 20202020 20202020 30303031 007A484D

Vendor ID: "GenuineIntel"; CPUID level 2

Intel-specific functions:
Version 000006B1
Type 0 - Original OEM
Family 6 - Pentium Pro
Model 11 -
1002MHz processor (estimate)
Stepping 1
Reserved 0

Brand index: 3 [Intel Pentium III Xeon processor]

Extended brand string: "Intel(R) Celeron(TM) CPU 1000MHz"

Feature flags: 0383F9FF

FPU Floating Point Unit
VME Virtual 8086 Mode Enhancements
DE Debugging Extensions
PSE Page Size Extensions
TSC Time Stamp Counter
MSR Model Specific Registers
PAE Physical Address Extension
MCE Machine Check Exception
CX8 COMPXCHG8B Instruction
SEP Fast System Call
MTRR Memory Type Range Registers
PGE PTE Global Flag
MCA Machine Check Architecture
CMOV Conditional Move and Compare Instructions
FGPAT Page Attribute Table
PSE-36 36-bit Page Size Extension
MMX MMX instruction set
FXSR Fast FP/MMX Streaming SIMD Extensions save/restore
SSE Streaming SIMD Extensions instruction set

TLB and cache info:

01: Instruction TLB: 4KB pages, 4-way set assoc, 32 entries
02: Instruction TLB: 4MB pages, 4-way set assoc, 2 entries
03: Data TLB: 4KB pages, 4-way set assoc, 64 entries
82: 2nd-level cache: 256KB, 8-way set assoc, 32 byte line size
08: 1st-level instruction cache: 16KB, 4-way set assoc, 32 byte line size
04: Data TLB: 4MB pages, 4-way set assoc, 8 entries
0C: 1st-level data cache: 16KB, 4-way set assoc, 32 byte line size

5.8.5. Date and Time

The command d t shows date and system local time, time zone and modality of “Standard” or “Daylight Savings” time
currently in use.

[11:38:04] ABILIS_CPX:d t

Current Local Time : Tuesday 30/11/2010 15:14:02 (UTC+1.00)

Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague...

127
Draft Command language Draft

Currently Observing : Standard Time (STD)

The command d te shows date and system local time, current time referred to the GMT time zone, the local time zone,
modality of “Standard” or “Daylight Savings” time currently in use and information about the date it will change.

[11:38:04] ABILIS_CPX:d te

Current Local Time : Tuesday 30/11/2010 15:14:06 (UTC+1.00)

Current UTC Time : Tuesday 30/11/2010 14:14:06
Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague...
Currently Observing : Standard Time (STD)
DST time will start on : Sunday 27/03/2011 at 02:00:00
DST time will end on : Sunday 30/10/2011 at 03:00:00

5.8.6. D DESCR (Display Descriptions)

This command shows the description of all resources, cards and ports active in Abilis CPX.

[11:38:04] ABILIS_CPX:d descr

Resource SubType Description

-------------------------------------------------------------------------------
Async-1
Eth-1
Eth-2
Eth-3
Adsl-1 adsl-operatorA
Rjs-1
Gpio-1
Cp Control_Port
Snmp Simple_Network_Management_Protocol
Sntp Simple_Network_Time_Protocol
Acnt Accounting_Service
SysLog System_Log_protocol
Opc Operator_Panel_Collector
GpioPc General_Purpose_I/O_Panel_Collector
X25-999 BCH Resource_for_remote_maintenance
Pad-1
Xtp-1
CtiX25D X.25_Over_ISDN_D-Channel
CtiSLink HDLC_Over_ISDN_B-Channel
CtiVsp Virtual_Synchronous_Port
CtiSys CTI_System_general_properties
CtiIax Inter-Asterisk_eXchange_Version_2
CtiDisa Direct_Inward_System_Access
CtiSip Session_Initiation_Protocol
Iprtr IP_Router_general_properties
Tcp Transmission_Control_Protocol
Udp User_Datagram_Protocol
Telnet Telnet_Server_and_Client_entities
Dns Domain_Name_System
Http HyperText_Transfer_Protocol
Nat Network_Address_Translator
Ssh Secure_Shell_Protocol
Ospf Open_Shortest_Path_First_Routing_Protocol
Dhcp Dynamic_Host_Configuration_Protocol
Smtp Simple_Mail_Transfer_Protocol
DhcpC Dynamic_Host_Configuration_Protocol_Client
RSim-1
Pv-1 IP-BCK
Pv-2 IP-BCK
Pv-5 IP Internal_Cluster_1

128
Draft Command language Draft

Pv-6 IP Internal_Cluster_2
Pv-7 IP To_Abilis_2
Pv-10 IP Internal_Cluster_1
Pv-11 IP Internal_Cluster_2
PoeAc-1
Ip-1 LAN
Ip-2 DL dmz-test
Ip-3 AIPT-BCK
Ip-4 AIPT-BCK
Ip-8 AIPT
Ip-9 AIPT To_Abilis_2
Ip-20 LAN
Ip-21 LAN
Ip-23 LAN
Ssl Secure_Socket_Layer
MfIde Abilis_Multi_Function_IDE_Interface

CTI Port Description

-------------------------------------------------------------------------------
31 to_PBX
32 to_PBX
33 to_ISDN_line
34 to_ISDN_line
101 phone_1
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222

129
Draft Command language Draft

223
224
225
226
227
228
229
230
231
232
241
242
243
244
245
246
247
248

5.8.7. D PSTACK
This command displays the association between resources and its related ports.

[11:38:04] ABILIS_CPX:d pstack

+------------+---------------+------------------------------------------------+
| Resource | Act/Run | Port(s) |
+------------+---------------+------------------------------------------------+
| Sync-1 | Act/NotRun | 54(Sync) |
| Sync-2 | Act/NotRun | 65(Sync) |
| Sync-3 | Act/NotRun | 67(Sync) |
| Sync-4 | Act/NotRun | 68(Sync) |
| Async-1 | Act/Run | 23(Async) |
| Blusb-1 | Act/Run | 171(Blusb) |
| Eth-1 | Act/Run | 24(Eth) |
| Eth-2 | Act/Run | 28(Eth) |
| Eth-3 | Act/Run | 179(Eth) |
| Eth-4 | Act/Run | 180(Eth) |
| Adsl-1 | Act/Run | 30(Adsl) |
| Adsl-2 | Act/Run | 31(Adsl) |
| Adsl-3 | Act/Run | 33(Adsl) |
| Adsl-4 | NotAct/NotRun | 48(Adsl) |
| Rjs-1 | Act/Run | 160(Rjs) |
| SimBox-1 | Act/Run | 177(SimBox) |
| Gps-1 | Act/Run | 159(Gps) |
| Gpio-1 | Act/Run | 172(Gpio) |
| Cp | Act/Run | 1(Cp) |
| Snmp | Act/Run | 2(Snmp) |
| Sntp | Act/Run | 3(Sntp) |
| Acnt | Act/Run | 15(Acnt) |
| Trfa | Act/Run | 52(Trfa) |
| SysLog | Act/Run | 167(SysLog) |
| Opc | Act/Run | 142(Opc) |
| X25-1 | NotAct/NotRun | 69(X25) |
| X25-2 | NotAct/NotRun | 72(X25) |
| X25-3 | NotAct/NotRun | 75(X25) 76(LapB) 77(Mlm) |
| X25-4 | NotAct/NotRun | 78(X25) 79(LapB) 80(Mlm) |
| X25-5 | NotAct/NotRun | 103(X25) |
| X25-6 | NotAct/NotRun | 104(X25) |
| X25-7 | NotAct/NotRun | 42(X25) |
| X25-8 | NotAct/NotRun | 59(X25) |
| X25-10 | NotAct/NotRun | 94(X25) 95(LapB) 96(Mlm) |

130
Draft Command language Draft

| X25-11 | NotAct/NotRun | 97(X25) 98(LapB) 99(Mlm) |

| X25-31 | NotAct/NotRun | 112(X25) |
| X25-32 | NotAct/NotRun | 113(X25) |
| X25-35 | NotAct/NotRun | 110(X25) |
| X25-36 | NotAct/NotRun | 111(X25) |
| X25-50 | Act/Run | 116(X25) 117(LapB) 118(Ml) |
| X25-51 | Act/Run | 119(X25) 120(LapB) 121(Ml) |
| X25-52 | Act/Run | 127(X25) 128(LapB) 129(Ml) |
| X25-53 | Act/Run | 130(X25) 131(LapB) 132(Ml) |
| X25-54 | Act/Run | 136(X25) 137(LapB) 138(Ml) |
| X25-55 | Act/Run | 139(X25) 140(LapB) 141(Ml) |
| X25-56 | Act/Run | 143(X25) 144(LapB) 145(Ml) |
| X25-57 | Act/Run | 146(X25) 147(LapB) 148(Ml) |
| X25-58 | Act/Run | 149(X25) 150(LapB) 151(Ml) |
| X25-59 | Act/Run | 152(X25) 153(LapB) 154(Ml) |
| X25-999 | Act/Run | 25(X25) 26(LapB) 27(Mlm) |
| Sdlc-1 | NotAct/NotRun | 84(Sdlc) |
| Sdlc-3 | NotAct/NotRun | 85(Sdlc) |
| Pad-1 | Act/Run | 5(Pad) |
| Xtp-1 | Act/Run | 162(Xtp) |
| Sim-1 | NotAct/NotRun | 70(Sim) |
| Sim-2 | NotAct/NotRun | 102(Sim) |
| Sim-5 | NotAct/NotRun | 105(Sim) |
| Sim-6 | NotAct/NotRun | 106(Sim) |
| Sim-7 | NotAct/NotRun | 40(Sim) |
| Sim-8 | NotAct/NotRun | 41(Sim) |
| Sim-10 | NotAct/NotRun | 73(Sim) |
| Sim-11 | NotAct/NotRun | 74(Sim) |
| Sim-31 | NotAct/NotRun | 114(Sim) |
| Sim-32 | NotAct/NotRun | 115(Sim) |
| Sim-35 | NotAct/NotRun | 107(Sim) |
| Sim-36 | NotAct/NotRun | 108(Sim) |
| Sim-37 | NotAct/NotRun | 109(Sim) |
| Sim-50 | Act/Run | 122(Sim) |
| Sim-51 | Act/Run | 123(Sim) |
| Sim-52 | Act/Run | 133(Sim) |
| Sim-53 | Act/Run | 134(Sim) |
| Sim-54 | Act/Run | 101(Sim) |
| Sim-55 | Act/Run | 135(Sim) |
| Sim-56 | Act/Run | 155(Sim) |
| Sim-57 | Act/Run | 156(Sim) |
| Sim-58 | Act/Run | 157(Sim) |
| Sim-59 | Act/Run | 158(Sim) |
| CtiX25D | Act/Run | 21(CtiX25D) |
| CtiSLink | Act/Run | 20(CtiSLink) |
| CtiVsp | Act/Run | 22(CtiVsp) |
| CtiSys | Act/Run | 19(CtiSys) |
| CtiIax | Act/Run | 64(CtiIax) |
| CtiDisa | Act/Run | 4(CtiDisa) |
| CtiSip | Act/Run | 71(CtiSip) |
| CtiSms | Act/Run | 168(CtiSms) |
| CtiAs | Act/Run | 183(CtiAs) |
| Iprtr | Act/Run | 6(Iprtr) |
| Tcp | Act/Run | 7(Tcp) |
| Udp | Act/Run | 8(Udp) |
| Telnet | Act/Run | 9(Telnet) |
| Rip | Act/Run | 10(Rip) |
| Dns | Act/Run | 12(Dns) |
| Http | Act/Run | 17(Http) |
| Nat | Act/Run | 13(Nat) |
| Ssh | Act/Run | 14(Ssh) |
| Ospf | Act/Run | 11(Ospf) |

131
Draft Command language Draft

| Dhcp | Act/Run | 87(Dhcp) |

| Ftp | Act/Run | 16(Ftp) |
| IpSec | Act/Run | 169(IpSec) |
| Ike | Act/Run | 170(Ike) |
| Smtp | Act/Run | 161(Smtp) |
| Pop3 | Act/Run | 55(Pop3) |
| Radius | Act/Run | 81(Radius) |
| Vrrp | Act/Run | 100(Vrrp) |
| DhcpC | Act/Run | 176(DhcpC) |
| DDns | Act/Run | 175(DDns) |
| RSim-1 | Act/Run | 178(RSim) |
| Fr-1 | Act/Run | 36(Fr) 37(Mlm) |
| Fr-2 | Act/Run | 124(Fr) 125(Mlm) |
| Pv-1 | Act/Run | 44(Mlm) 45(PLinkE) |
| Pv-2 | Act/Run | 46(Mlm) 47(PLinkE) |
| Pv-5 | Act/Run | 163(Mlm) 164(PLinkE) |
| Pv-10 | Act/Run | 57(Mlm) 58(PLinkE) |
| Pv-11 | Act/Run | 61(Mlm) 62(PLinkE) |
| Pv-50 | NotAct/NotRun | 89(Mlm) 90(PLinkE) |
| Pv-200 | Act/Run | 66(Ml) |
| PoeAc-1 | Act/Run | 39(PoeAc) |
| PoeCli-1 | Act/Run | 53(PoeCli) |
| PoeCli-2 | Act/Run | 182(PoeCli) |
| Ip-1 | Act/Run | 18(IpLan) |
| Ip-2 | Act/Run | 34(IpLan) |
| Ip-3 | Act/Run | 91(IpLan) |
| Ip-4 | Act/Run | 181(IpLan) |
| Ip-10 | NotAct/NotRun | 165(IpLan) |
| Ip-11 | NotAct/NotRun | 166(Ppp) |
| Ip-12 | NotAct/NotRun | 173(Mlm) |
| Ip-35 | Act/Run | 92(Mlm) |
| Ip-50 | Act/Run | 29(Ppp) |
| Ip-51 | Act/Run | 32(Ppp) |
| Ip-52 | Act/Run | 35(Ppp) |
| Ip-53 | Act/Run | 50(Ppp) |
| Ip-55 | Act/Run | 49(Mlm) |
| Ip-60 | Act/Run | 38(Mlm) |
| Ip-61 | Act/Run | 43(Mlm) |
| Ip-62 | Act/Run | 60(Ppp) |
| Ip-63 | Act/Run | 63(Ppp) |
| Ip-71 | Act/Run | 88(Ppp) |
| Ip-131 | Act/Run | 174(Mlm) |
| Ip-150 | Act/Run | 83(Ml) |
| Ip-160 | Act/Run | 86(Mlm) |
| Ip-200 | Act/Run | 82(Mlm) |
| Ip-201 | Act/Run | 126(Mlm) |
| Ip-250 | Act/Run | |
| Bridge-1 | Act/Run | 56(Bridge) |
| Ssl | Act/Run | 51(Ssl) |
| MfIde | Act/Run | 0(MfIde) |
| UPnPS | Act/Run | 93(UPnPS) |
+------------+---------------+------------------------------------------------+

Tip
Interesting chapter: Section 51.19, “How to trace the internal events for debugging purposes”.

5.9. Users Table

The service of user authentication is provided through a centralised “archive” where users are defined as well as the services
to which they have access and some service-related parameters. These services are:

132
Draft Command language Draft

• PPP
• FTP
• HTTP
• MAIL
• IAX
• SIP

Two default users exist: admin and guest: they can't be removed and are disabled by default.

Admin user can be activated only with a password not empty, while guest user can't have a password.

Users Table can be managed with the following commands:

• d user: displays the Users table;

• a user: adds a new user;

• c user: clears an existing user;

• s user: modifies the parameter of an existing user;

5.9.1. D USER (Display User)

This command shows the content of the Users Table in a synthetic format. The available syntax of the commands is:

• d user : shows the user's list;

• d user:<username> : shows the Users Table entry identified by the “user:<username>” in a synthetic format, i.e. the
parameters of the services which are not enabled are omitted.

[15:36:52] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO

[15:36:57] ABILIS_CPX:d user:admin

Parameter: | Value:
------------------+------------------------------------------------------------
USER: admin
ALIAS: admin
ID: 1 <Read Only>
PWD:
ACT: NO
GROUP:
CTIP: #
CLUS: #
OPC-MONITOR: NONE
PPP: YES
PPP-AUTH: CHAP
PPP-RES: ANY
PPP-NEIGH: #
PPP-MASK: 255.255.255.255
PPP-ROUTE: #
FTP: YES
FTP-HOMEDIR:
FTP-PROT: PLAIN,SSL
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

5.9.1.1. D USERE (Display User Extended)

This command shows the content of the Users Table in extended format. The available syntax of the command is:

• d usere : shows the list in extended format of all users

133
Draft Command language Draft

• d usere:<username> : shows the content of the Users Table in extended format, i.e. all users defined with their full set of
configuration information are displayed.

[15:41:01] ABILIS_CPX:d usere:admin

Parameter: | Value:
------------------+------------------------------------------------------------
USER: admin
ALIAS: admin
ID: 1 <Read Only>
PWD:
ACT: NO
GROUP:
CTIP: #
CLUS: #
OPC-MONITOR: NONE
OPC-ROLE: USER
OPC-VIEW: *
OPC-HIDE-NUMBERS: NO
OPC-PRIVACY: NO
PPP: YES
PPP-AUTH: CHAP
PPP-RES: ANY
PPP-NEIGH: #
PPP-MASK: 255.255.255.255
PPP-ROUTE: #
FTP: YES
FTP-HOMEDIR:
FTP-PROT: PLAIN,SSL
HTTP: YES
HTTP-PROT: PLAIN,SSL
MAIL: NO
MAIL-MB-MAXSIZE: SYS
MAIL-MB-MAXMAILS: SYS
MAIL-MSG-LIFETIME: SYS
MAIL-AUTH: SYS
IAX: NO
IAX-HOST: DYNAMIC
IAX-SRCADD: SYS
IAX-PORT: (DYNAMIC)
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 2
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER:
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:

134
Draft Command language Draft

IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: SYS
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER:
IAX-REM-PASS:
IAX-REM-AUTH: SYS
IAX-REM-REG: NO
SIP: NO
SIP-TYPE: PHONE
SIP-DOMAIN: SYS
SIP-HOST: DYNAMIC
SIP-TCP-PORT: (DYNAMIC)
SIP-UDP-PORT: (DYNAMIC)
SIP-SRCADD: SYS
SIP-PROT-IN: TCP,UDP
SIP-PROT-OUT: UDP
SIP-IP-PERMIT: *
SIP-MAXSES-BID: 2
SIP-MAXSES-IN: 0
SIP-MAXSES-OUT: 0
SIP-NUMBER:
SIP-CG-NUM: AUTO
SIP-FWD-CG-NUM: CALLER
SIP-CTIP-TYPE: SYS
SIP-RG-IN: SYS
SIP-ROUTE-BY-SD: NO
SIP-PROVIDE-SG: NO
SIP-CLIP-RULE: SYS
SIP-BUSY-NOCHAN: NO
SIP-LCS-GROUP: NONE
SIP-CPO-RTP: SYS
SIP-CPO-SIGNALLING: SYS
SIP-SS: NO
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO
SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS
SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO

135
Draft Command language Draft

SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS
SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-T38-REDUND: SYS
SIP-T38-REDUND-PCK: SYS
SIP-UA: SYS
SIP-UA-PERMIT: *
SIP-REM-USER:
SIP-REM-PASS:
SIP-REM-AUTH: SYS
SIP-REM-REG: NO
-------------------------------------------------------------------------------

5.9.2. A USER (Add User)

This command adds a new entry in the Users Table.

[15:50:16] ABILIS_CPX:a user:pippo pwd:pippo http:yes

COMMAND EXECUTED

[15:50:33] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
pippo *** YES # # NO NO YES NO NO NO

Note
A restricted user name character set can be used. Avoided those characters that are not valid in file names '\',
'/', ':', '*', '?', '"', '>', '<', '|'.

The following command displays the syntax:

[15:41:15] ABILIS_CPX:a user: ?

A USER:val [par:val] Add an entry to the Users Access Control table

USER: User name. Max. 32 ASCII characters. <Mandatory>

The strings "A" and "ALL" and "anonymous" are invalid/reserved
the system and cannot be used for user name value.

User's parameters:
...

5.9.3. C USER (Clear User)

This command deletes an entry in the Users Table.

[17:46:42] ABILIS_CPX:c user:user10

YOU ASKED TO DELETE USER 'user10'.

CTI CALLs LOGs AND ADDRESS BOOK CONTACTs OF THIS USER WILL BE DELETED.
PROCEED ANYWAY (N/Y)?y

136
Draft Command language Draft

COMMAND EXECUTED

The following command displays the syntax:

[15:47:55] ABILIS_CPX:c user: ?

C USER:val Clear a user from the Users Access Control table

USER: User name. Max. 32 ASCII characters. <Mandatory>

5.9.4. S USER (Set User)

This command modifies an entry in the Users Table.

[15:51:07] ABILIS_CPX:s user:pippo ftp:yes

COMMAND EXECUTED

[15:51:26] ABILIS_CPX:d user:pippo

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: pippo
ALIAS: pippo
ID: 3 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-MONITOR: NONE
FTP: YES
FTP-HOMEDIR:
FTP-PROT: PLAIN,SSL
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

The following command displays the syntax:

[15:47:53] ABILIS_CPX:s user: ?

S USER[E]:val par:val [par:val] Set parameter(s) of an entry of the Users

Access Control table

USER[E]: User name. Max. 32 ASCII characters. <Mandatory>

User's parameters:
...

5.10. Address book management

The address book can be managed through the web interface or the CP. Csv files can be used to import/export contacts which
are stored in the ADDRBOOK.DAT file.

5.10.1. CONTACT EXPORT

It allows to export private or public contacts to a CSV file.

[08:58:23] ABILIS_CPX:_contact export ?

137
Draft Command language Draft

PUB Public contact

PUBLIC Public contact
USER: User name. Max. 32 ASCII characters.

[09:51:22] ABILIS_CPX:contact export public c:\usr\pub\public_contacts.csv

COMMAND EXECUTED

[09:52:49] ABILIS_CPX:sys dir c:\usr\pub\

Directory listing of c:\usr\pub

. <DIR> 22/05/2009 11:59:14

.. <DIR> 22/05/2009 11:59:14
public_contacts.csv 53 09/03/2011 09:52:48

Found 2 directories, 1 files.

Total 124 MB, Used 73 MB, Free 50 MB.

5.10.2. CONTACT IMPORT

It allows to import provate or public contacts from a csv file.

[09:59:01] ABILIS_CPX:contact import public ?

CONTACT IMPORT PUB <filename> Import public contacts from the specified
file in CSV format

<filename> Absolute file name <Mandatory>

Spaces are allowed. Strings holding spaces must be
written between quotation marks.
(E.g.: "C:\USR\PUB\My contacts.csv")

[10:05:07] ABILIS_CPX:contact import public c:\usr\pub\import_public.csv

COMMAND EXECUTED

The csv file must have the following format:

NAME,OUTDIAL,NUMBER
Test,,10
Test2,,11
Test3,,12

Tip
The upload of the csv file can be done using FTP or file put command:

[10:04:37] ABILIS_CPX:file put z c:\usr\pub\import_public.csv

READY TO RECEIVE FILE...

Upload Zmodem
pub_addrbook.csv

FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

FILE TRANSFER SUCCESSFULLY COMPLETED

RECEIVED FILE 'c:\usr\pub\import_public.csv' FORMAT IS UNKNOWN.

138
Draft Command language Draft

NO CHECK DONE.

5.10.3. CONTACT RELOAD

It allows to reload contacts from the ADDRBOOK.DAT file. This command is needed after the CONTACT IMPORT
command execution in order to use the uploaded address book.

[10:13:54] ABILIS_CPX:contact reload

COMMAND EXECUTED

5.11. Lists management

By the terms “Elements Lists” we refer to a list of objects, belonging to the same homogeneous type, which are identified by
the generic term “item”.

Within the Abilis CPX, the following element types have been referred as relevant:

• IN: ISDN numbers

• IS: ISDN sub-addresses
• EC: CTIC clusters
• XN: X.25 NUAs
• XU: X.25 User data fields
• IP: IP addresses
• IR: IP addresses ranges
• DN: dialling numbers
• CR: CPX resources
• TUP: TCP/UDP ports
• IPT: Internet Protocols
• MAC: MAC Addresses
• SAP: SAP values
• H323ID: H.323 ID aliases
• CLNUM: CTICL Numbers
• INR: ISDN Number Replacement
• IN2T:ISDN Numbers to Text
• TXT:Text
• OPC:OPC Unique User IDs
• ICAUSE:ISDN Cause codes
• RU: Rules
• MR: Master Rules

Lists can be used to improve:

• call routings by accepting and/or refusing calls depending on the source numbers;
• security by accepting and/or refusing packets depending on the IP source address or protocol.

5.11.1. LIST CREATE

This command creates a new list. Type the following command to create a list of ISDN numbers:

[11:35:44] ABILIS_CPX:list create Home in List_of_Home_numbers

COMMAND EXECUTED

The following command displays the syntax:

[11:35:43] ABILIS_CPX:list create ?

LIST CREATE Name Type [Description] Create a new list

Name List name. Max. 16 characters [0..9, a..Z, _] <Mandatory>

139
Draft Command language Draft

Type List type [IN, IS, EC, XN, XU, IP, IR, DN, CR, <Mandatory>
TUP, IPT, MAC, SAP, H323ID, CLNUM, INR, IN2T, TXT,
OPC, ICAUSE, RU, MR]
Description List description. Max. 70 alphanumeric, no spaces. <Optional>

5.11.2. LIST DELETE

This command deletes an existing list. Type the following command to delete a list:

[11:52:40] ABILIS_CPX:list delete home

COMMAND EXECUTED

The following command displays the syntax:

[11:50:22] ABILIS_CPX:list delete ?

LIST DELETE Name Delete a list

Name List name. Max. 16 characters [0..9, a..Z, _] <Mandatory>

Caution
A list, to be deleted, must not be referred in any resource or table.

5.11.3. LIST RENAME / LIST DESCRIPTION

The command list rename changes the name of the list, without deleting the list;

the command list description changes or adds the field description of the list.

[12:04:13] ABILIS_CPX:list rename Home Office

COMMAND EXECUTED

[12:04:28] ABILIS_CPX:list description Office List_of_Office_numbers

COMMAND EXECUTED

By typing list rename ? or list description ? it is possible to display the command syntax:

[11:55:13] ABILIS_CPX:list rename ?

LIST RENAME Name NewName Change/Set a list name

Name List name. Max. 16 characters [0..9, a..Z, _] <Mandatory>

NewName List new name. Max. 16 characters [0..9, a..Z, _] <Mandatory>

[11:59:42] ABILIS_CPX:list description ?

LIST DESCRIPTION Name Description Change/Set a list description

Name List name. Max. 16 characters [0..9, a..Z, _] <Mandatory>

Description List description. Max. 70 alphanumeric, no spaces. <Mandatory>

5.11.4. D LIST (Display List)

This command shows list table. The available syntax of the commands is:

• d list : shows the list table

[12:15:23] ABILIS_CPX:d list

140
Draft Command language Draft

Last change: 30/11/2010 08:19:18 CET

List-Number:3 Items-Number:4 Used-Resources:251 Free-Resources:399109

Id Name Type Description Edt St Ref First Numb

-------------------------------------------------------------------------------
4 Home IN List_of_Home_numbers 0 5 2
2 NumIax IN Automatically_generated_CT... R 0 1 1
3 NumSip IN Automatically_generated_CT... R 0 2 3
1 NumClus CLNUM Automatically_generated_CT... R 0 0 0
-------------------------------------------------------------------------------
IN:ISDN Numbers, IS:ISDN Sub Addresses, EC:CTI Clusters,
XN:X25 NUAs, XU:X25 UDFs, IP:IP Addresses,
IR:IP Addresses Ranges, DN:Dialing Numbers, CR:CPX resources,
TUP:TCP and UDP ports ranges, IPT:Internet Protocols, MAC:MAC Addresses,
SAP:SAP values, H323ID:H.323 ID aliases, CLNUM:CTICL Numbers,
INR:ISDN Numbers Replacements, IN2T:ISDN Numbers to Text, TXT:Text,
OPC:OPC Unique User IDs, ICAUSE:ISDN Cause codes,
RU:Rules, MR:Master Rules.
-------------------------------------------------------------------------------

• d list:<name> : shows the content of a specific list

[12:17:04] ABILIS_CPX:d list:home

LIST:Home - IN
List_of_Home_numbers
0234865852 0269548947

• d list <type>: shows the lists of the specified type

[15:42:17] ABILIS_CPX:d list clnum

Last change: 11/05/2011 14:53:02 CET

Used-Lists: 9 Used-Items: 21 Used-Resources: 632 (bytes)

Free-Lists:241 Free-Items: 3979 Free-Resources: 398728 (bytes)

Id Name Type Description Edt St Ref First Numb

-------------------------------------------------------------------------------
4 NumClus CLNUM Automatically_generated_C... R 0 6 1
-------------------------------------------------------------------------------
IN:ISDN Numbers, IS:ISDN Sub Addresses, EC:CTI Clusters,
XN:X25 NUAs, XU:X25 UDFs, IP:IP Addresses,
IR:IP Addresses Ranges, DN:Dialing Numbers, CR:CPX resources,
TUP:TCP and UDP ports ranges, IPT:Internet Protocols, MAC:MAC Addresses,
SAP:SAP values, H323ID:H.323 ID aliases, CLNUM:CTICL Numbers,
INR:ISDN Numbers Replacements, IN2T:ISDN Numbers to Text, TXT:Text,
OPC:OPC Unique User IDs, ICAUSE:ISDN Cause codes,
RU:Rules, MR:Master Rules.
-------------------------------------------------------------------------------

• d list:a : shows the content of all the list present in the configuration

5.11.5. A LIST (Add List item)

This command adds items to a list.

[12:41:31] ABILIS_CPX:a list:home 0234865852 0269548947

COMMAND EXECUTED

[12:43:16] ABILIS_CPX:d list:home

141
Draft Command language Draft

LIST:Home - IN
List_of_Home_numbers
0234865852 0269548947

The following command displays the syntax:

[12:37:52] ABILIS_CPX:a list: ?

A LIST:Name Item1 Item2 ... Add one or more items to a list

Name List name or List identifier <Mandatory>

Item1 Item2 ... Item values separeted by space <Mandatory>

Possible Item values for each list Type:

IN item: String of max. 20 characters in the range [0..9, ?, *, #]

optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e,
d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
IS item: String of max. 20 characters in the range [0..9, a..z, A..Z, ?, *]
EC item: String of max. 8 characters in the range [0..9, a..z, A..Z, _]
XN item: String of max. 15 characters in the range [0..9, ?, *, #]
XU item: String of max. 12 characters in the range [0..9, a..z, A..Z, ?, *]
IP item: IP address in the range [000.000.000.000..255.255.255.255]
IR item: Two IP addresses separated by ':' (colon)
DN item: Sequence of four values separated by ',' (comma) e.g.: 'o,n,c,r',
where: 'o' is the order [1..32], 'n' is a dialing number i.e. a
sequence of max. 20 digits optionally preceded by TON [u, i, n, o,
s, h, c] and/or NP [x, e, d, t, l, p] attributes, 'c' is the max
number of connections [0..32], 'r' is the max. number of retries
[0..65534, NOMAX]. (E.g. 2,0376334412,2,5 or 1,ie444555,32,NOMAX).
See HELP ISDN ATTRIBUTES for details on attributes.
CR item: CPX resource 'type-n' where 'n' [1..999]
TUP item: A single TCP or UDP port mnemonic or decimal value [1..65535]
or two TCP or UDP ports mnemonic or decimal value [0..65535]
separated by ':' (colon).
See HELP INTERNET PORTS for the list of TCP/UDP ports.
IPT item: An Internet protocol mnemonic or decimal value [0..255].
See HELP INTERNET PROTOCOLS for the list of Internet protocols.
MAC item: A single MAC address in the form XX-XX-XX-XX-XX-XX.
SAP item: A single SAP values in the hexadecimal form XX.
H323ID item: String of max. 32 ASCII printable characters.
Spaces are allowed. Strings holding spaces must be written between
quotation marks. (E.g.: "12aDEF 1bx4")
CLNUM item: Sequence of two values separated by ',' (comma) e.g.:
'num,clusname', where: 'num' is the number i.e. a sequence of max
20 characters in the range [0..9, *] optionally preceded by TON
[u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes,
'clusname' is the CTI cluster name. (E.g. ne123*,my_clus)
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
INR item: Sequence of four values separated by ',' (comma) e.g.:
'num,chk,cd,cg', where: 'num' is the number i.e. a sequence
of max. 20 characters in the range [0..9, ?, *, #] optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
attributes, 'chk' is the field to be used by CTIR for the match
[CDI, CGI, SDI, SGI], 'cd' is the called number i.e. a sequence of
max. 20 characters in the range [0..9, *, #, 'macro'], 'cg' is the
calling number i.e. a sequence of max. 20 characters in the range
[0..9, *, #, 'macro'].
Both 'cd' and 'cg' can be optionally preceded by TON [u, i, n, o,
s, h, c] and/or NP [x, e, d, t, l, p] and/or PI [a, r, m, q]

142
Draft Command language Draft

and/or SI [y, v, w, z] attributes. (E.g. i55*,cgi,'CDI.S2',neq21).

See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
IN2T item: Sequence of two values separated by ',' (comma) e.g.:
'num,text', where: 'num' is the number i.e. a sequence
of max. 20 characters in the range [0..9, ?, *, #] optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
attributes, 'text' is a string of max. 64 ASCII printable
characters.
Spaces are allowed. Items whith a text holding spaces must be
written between quotation marks. (E.g.: "i555,my free text")
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
TXT item: String of max. 64 ASCII printable characters.
Spaces are allowed. Items whith a text holding spaces must be
written between quotation marks. (E.g.: "my free text")
OPC item: Sequence of three values separated by ',' (comma) e.g.: 'a,u,i',
where: 'a' is the AbilisId i.e. max. 32 characters in the range
['0'..'9', 'A'..'Z', 'a'..'z'] or "*" or "(Local)", 'u' is
the User name, i.e. max. 32 ASCII characters or "*", 'i' is the
Interface type [* or ANY, CTIP, CLUS, SIP, IAX]
(E.g. myAbilis,myUser,CTIP).
ICAUSE item: Sequence of three values separated by ',' (comma) e.g.: 'l,r,s',
where: 'l' is the ISDN location code, i.e. an hexadecimal value in
the range [00..FF] or ISDN location mnemonic in the range [U, LPN,
LN, TN, RN, RPN, INTL, BI] or "INT" or "EXT" or "ANY", 'r' is
the ISDN reason code, i.e. an hexadecimal value or two hexadecimal
values separated by ':' (colon) in the range [00..FF], 's' is the
connection state/phase, i.e. [CREQ, ALERT, ANY]. The connection
state/phase is optional and by default it is set to "CREQ".
(E.g. EXT,91,ANY or 80,90:91,CREQ).
RU item: Expression with Lists names and logical operators (AND, OR, NOT),
separeted by '.' (dot) (E.g.: List1.AND.List2)
MR item: Expression with Lists names and logical operators (AND, OR, NOT),
separeted by '.' (dot) (E.g.: List1.AND.List2)

5.11.6. C LIST (Clear List item)

The command c list deletes items from a list.

[12:43:19] ABILIS_CPX:c list:home 0234865852

COMMAND EXECUTED

[12:53:25] ABILIS_CPX:d list:home

LIST:Home - IN
List_of_Home_numbers
0269548947

The following command displays the syntax:

[12:43:19] ABILIS_CPX:c list: ?

C LIST:Name Item Remove an item from a list

Name List name or List identifier <Mandatory>

Item Item value <Mandatory, Optional only for RU list>

C LIST:Name Order Remove an item from a DN list

Name List name or List identifier <Mandatory>

Order Order value of the DN item <Mandatory>

143
Draft Command language Draft

5.11.7. D ITEM
This command shows the elements table. Lists table can store up to 2000 definitions (indexed from 1 to 2000).

Elements identifiers are sequential and they run only into the system, so they can't be used by the user in no one of the list
manipulation commands.

If the elements table is empty, the message “NO ITEMS DEFINED” is generated.

[12:43:19] ABILIS_CPX:d item

Last change: 30/11/2010 15:28:28 CET

List-Number:4 Items-Number:6 Used-Resources:311 Free-Resources:399049

Item List Type Value

-------------------------------------------------------------------------------
1 2 IN 601
2 3 IN 08351825431
3 3 IN 200
4 3 IN 901
5 4 IN 0234865852
6 4 IN 0269548947
-------------------------------------------------------------------------------
IN:ISDN Numbers, IS:ISDN Sub Addresses, EC:CTI Clusters,
XN:X25 NUAs, XU:X25 UDFs, IP:IP Addresses,
IR:IP Addresses Ranges, DN:Dialing Numbers, CR:CPX resources,
TUP:TCP and UDP ports ranges, IPT:Internet Protocols, MAC:MAC Addresses,
SAP:SAP values, H323ID:H.323 ID aliases, CLNUM:CTICL Numbers,
INR:ISDN Numbers Replacements, IN2T:ISDN Numbers to Text, TXT:Text,
OPC:OPC Unique User IDs, ICAUSE:ISDN Cause codes,
RU:Rules, MR:Master Rules.
-------------------------------------------------------------------------------

5.11.8. Type of lists

5.11.8.1. INR lists
INR lists are special kind of lists with four fields: Number/Chk/CD/CG. These lists are useful to generate speed dials.They
can be used:

• in input fields (CDI, CGI, SDI, SGI) (in this case the match is done against the Number field);

• in output fieds to change CD or CG numbers, when the called number of the original call matches the Number field.

5.11.8.1.1. Example 1 - speed dials with sip user

Use the following command to create an inr list called 'inr':

[13:46:24] ABILIS_CPX:list create inr inr inr_test

COMMAND EXECUTED

[13:47:59] ABILIS_CPX:d list

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 14/12/2010 13:47:59 CET

List-Number:9 Items-Number:19 Used-Resources:654 Free-Resources:398706

Id Name Type Description Edt St Ref First Numb

-------------------------------------------------------------------------------
1 ISDN_numbers IN list 0 1 1
2 Nodo IN Numeri_del_nodo 1 2 4

144
Draft Command language Draft

8 NumIax IN Automatically_generated_CT... R 0 0 0
6 NumSip IN Automatically_generated_CT... R 0 9 4
5 SgiAllowed IS Sub-Adresses_diretti_al_CPX 1 7 2
7 OkTelnet IR Reti_Abilitate_al_Telnet 1 13 6
3 PPP_list CR List_of_PPP_Resources 1 6 1
4 NumClus CLNUM Automatically_generated_CT... R 0 0 0
9 inr INR inr_test 0 19 1
-------------------------------------------------------------------------------
IN:ISDN Numbers, IS:ISDN Sub Addresses, EC:CTI Clusters,
XN:X25 NUAs, XU:X25 UDFs, IP:IP Addresses,
IR:IP Addresses Ranges, DN:Dialing Numbers, CR:CPX resources,
TUP:TCP and UDP ports ranges, IPT:Internet Protocols, MAC:MAC Addresses,
SAP:SAP values, H323ID:H.323 ID aliases, CLNUM:CTICL Numbers,
INR:ISDN Numbers Replacements, IN2T:ISDN Numbers to Text, TXT:Text,
OPC:OPC Unique User IDs, ICAUSE:ISDN Cause codes,
RU:Rules, MR:Master Rules.
-------------------------------------------------------------------------------

Now add an item to the list, indicating that it will be used to check the CDI number (Chk:CDI).

[13:55:42] ABILIS_CPX:a list:inr 1,cdi,111,110

COMMAND EXECUTED

[13:56:19] ABILIS_CPX:d list:inr

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:inr - INR
inr_test
Number Chk CD CG
1 CDI 111 110

Now create a routing to manage calls between sip phones:

[13:58:55] ABILIS_CPX:a ctir pr:22 descr:test_inr type:stos cdi:'inr' cdo:''inr'' cgo:''inr'' sp:64

COMMAND EXECUTED

[14:02:15] ABILIS_CPX:d ctire pr:22

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 14/12/2010 14:02:15 CET

-------------------------------------------------------------------------------
PR:22 DESCR:
ACT:YES EDT:NO
TYPE:StoS POI:CtiSip POO:CtiSip EEC:NO
NEXT:NO CDI:'inr' CDO:''inr''
LAST:ANY CGI:* CGO:''inr''
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:G.711
SPOUT:64000 SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:G.711
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

The following is the log of a call from number 10 calling number 1. The log shows that the called number is 111 even if the
real called number is 1. Besides the calling number has been changed because it has become 110.

[14:06:43] ABILIS_CPX:start ldme

145
Draft Command language Draft

Current Local Time: Tuesday 14/12/2010 14:06:49 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
141210 140750 CtiSip 10 E-CallRx CH:16 BC:Speech CD:ue1 CG:uxq10
USER:test
141210 140750 CtiSip 10 E-Route Match PR:22
141210 140750 CtiSip 10 E-CallTx BC:Speech TY:StoS CD:ue111
CG:uxq110
141210 140750 CtiSip 10 E-NumComplete CDI:ue1 CDO:ue111
141210 140750 CtiSip 10 E-AlertRx CH:17 USER:test2
141210 140750 CtiSip 10 E-AlertTx CH:16
141210 140802 CtiSip 10 E-ConnRx CH:17
141210 140802 CtiSip 10 E-ConnTx CH:16
141210 140806 CtiSip 10 E-DiscRx CH:17 CAUSE:80 9F (U, Normal,
unspecified) USER:test2
141210 140806 CtiSip 10 E-DiscConfTx CH:17
141210 140806 CtiSip 10 E-DiscTx CH:16 CAUSE:80 9F (U, Normal,
unspecified) USER:test

Displaying the active connections shows the same:

[14:08:13] ABILIS_CPX:d ctice

-------------------------------------------------------------------------------
ID:11 TYPE:StoS ST:ALERT PR:22 STI:07/00 STO:04/00 EEC:NO
START:14/12/2010 14:11:40 DURATION:0 REMAINING:-
POI:Sip GI:# SR:# POO:Sip GO:# DS:#
CDI:ue1 CDO:ue111
CGI:uxq10 CGO:uxq110
SDI: SDO:
SGI: SGO:
RGI: RGO:
CODER:Unk SP:0 FMRLY:NO FAXSP:0 DJ:0 FMDJ:0
BW:0 SC:NO MODSP:0 MJ:0 FMMJ:0

Another possibility is to indicate the field of inr list to be used in a certain cti routing:

[14:18:51] ABILIS_CPX:s ctir pr:22 cdo:''inr.cg'' cgo:''inr.cd''

COMMAND EXECUTED

[14:19:21] ABILIS_CPX:d ctire pr:22

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 14/12/2010 14:19:21 CET

-------------------------------------------------------------------------------
PR:22 DESCR:test_sip
ACT:YES EDT:NO
TYPE:StoS POI:CtiSip POO:CtiSip EEC:NO
NEXT:NO CDI:'inr' CDO:''inr.CG''
LAST:ANY CGI:* CGO:''inr.CD''
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:G.711
SPOUT:64000 SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:G.711

146
Draft Command language Draft

TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

In this case, CDO is equal to CG item of the inr list and CGO is equal to CD item of the same list. The following is the log of
the speed dial:

[14:20:56] ABILIS_CPX:start ldme

Current Local Time: Tuesday 14/12/2010 14:21:00 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
141210 142105 CtiSip 14 E-CallRx CH:24 BC:Speech CD:ue1 CG:uxq10
USER:test
141210 142105 CtiSip 14 E-Route Match PR:22
141210 142105 CtiSip 14 E-CallTx BC:Speech TY:StoS CD:ue110
CG:uxay111
141210 142105 CtiSip 14 E-NumComplete CDI:ue1 CDO:ue110
141210 142105 CtiSip 14 E-AlertRx CH:25 USER:test2
141210 142105 CtiSip 14 E-AlertTx CH:24
141210 142110 CtiSip 14 E-ConnRx CH:25
141210 142110 CtiSip 14 E-ConnTx CH:24
141210 142111 CtiSip 14 E-DiscRx CH:24 CAUSE:80 9F (U, Normal,
unspecified) USER:test
141210 142111 CtiSip 14 E-DiscConfTx CH:24
141210 142111 CtiSip 14 E-DiscTx CH:25 CAUSE:80 9F (U, Normal,
unspecified) USER:test2

The cti connection shows the same information in a different way:

[14:21:16] ABILIS_CPX:d ctice

-------------------------------------------------------------------------------
ID:15 TYPE:StoS ST:ALERT PR:22 STI:07/00 STO:04/00 EEC:NO
START:14/12/2010 14:21:25 DURATION:0 REMAINING:-
POI:Sip GI:# SR:# POO:Sip GO:# DS:#
CDI:ue1 CDO:ue110
CGI:uxq10 CGO:uxay111
SDI: SDO:
SGI: SGO:
RGI: RGO:
CODER:Unk SP:0 FMRLY:NO FAXSP:0 DJ:0 FMDJ:0
BW:0 SC:NO MODSP:0 MJ:0 FMMJ:0

5.12. Configuration validating and saving

5.12.1. VALIDATE
This command executes the validation of the configuration currently in use.

Configuration validating has been introduced to ensure correct Abilis CPX configurations.

The output of the validating procedure can be:

• positive without demanding modifications to the configuration (if the command is successful the message “VALIDATION
SUCCESSFULLY EXECUTED” will be also shown);

• negative if the validation detects some incongruencies or imprecision in it (if the command is unsuccessful the message
“VALIDATION FAILED” wil be shown).

[11:28:08] ABILIS_CPX:validate

VALIDATION IN PROGRESS ...

147
Draft Command language Draft

WARNING: RES:Tcp Changed "SESNUM" from 12 to 22

VALIDATION SUCCESSFULLY EXECUTED

5.12.2. SAVE CONF

This command saves the current configuration in the file drivers.cfg on the disk only if validation is successful.

If the validation and saving are both successful the message “SAVE EXECUTED” will be shown. If the validation fails, the
saving is NOT executed and the message “SAVE NOT EXECUTED” will be shown.

[18:09:29] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

The configuration is saved and marked with a configuration state of “configuration saved but not yet loaded”. On next restart,
if the settings of the saved configuration were correct, the configuration state will become “valid configuration”.

Checking the current configuration state is done through the command d i. In correspondence of the drivers.cfg file, in
the notes dedicated section, the string “Saved” will appear.

After the system restart, in correspondence of the loaded drivers.cfg file, in the notes dedicated section, the string “Ok”
will appear.

[16:23:01] ABILIS_CPX:d i

Abilis CPX - Ver. 9404/STD - 21/01/2011 - Build 9404 - 21/01/2011

(c) 1994/2011 - Abilis

ABILIS-ID: 2001

Free/Total Memory: 91,316,960/268,304,384 Largest Block: 91,309,040

Free/Used/Total HD/CF space (in KB): 24,010/98,340/122,350

File Version Date Time Size Note

-------------------------------------------------------------------------------
CPX.RTB ....... 24/01/2011 10:01:10 4306803
DRIVERS.CFG v.7.1 24/01/2011 11:20:44 30720 Ok
DRIVERS.BCK v.7.1 24/01/2011 11:20:42 30720 Ok
...

Save Conf command can be also used with the syntax: save conf <version>.

It allows to create a copy of the configuration file DRIVERS.CFG of the specified version directory. The <version> string
must correspond to an existing version directory in the form 'X.Y.Z' or 'X-Y-Z' or 'Y.Z' or 'Y-Z' or 'Y', where X, Y and Z are
decimal digit [0 - 9] (E.g. 6-0-6)

It can be useful after a system update and the installation of a compatible release.

[18:09:29] ABILIS_CPX:save conf 6-0-6

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

The command save conf backup is used to create a backup copy (file drivers.bck) of the configuration saved on disk.
The backup configuration is loaded at the Abilis CPX start, every time the one, saved in drivers.cfg, is not valid or the
same file is missing or corrupted.

Indeed, it is very important that the User makes backup only of those configuration correctly working.

[11:28:08] ABILIS_CPX:save conf backup

148
Draft Command language Draft

THE CURRENT SAVED CONFIGURATION WILL BECOME THE BACKUP CONFIGURATION.

PROCEED (N/Y)?y

PROCEEDING WITH SAVE BACKUP...

SAVE BACKUP EXECUTED

5.13. System management

In this section the most frequently used commands about system management are shown.

With conf and conflog commands it is possible to copy, restore or save configuration and Log files. Below there's the
commands syntax:

[15:43:26] ABILIS_CPX:conflog ?

BACKUP Copy configuration and log files to removable disk

RESTORE Load configuration files from removable disk

[15:43:26] ABILIS_CPX:conf ?

BACKUP Copy configuration to removable disk

GET Sends the configuration in memory to a remote site
INFO Display/set configuration notes
PUT Receives configuration from a remote site
RELOAD Reload the configuration from a file
RESTORE Alias of the CONFLOG RESTORE command
SAVE Alias of the SAVE CONF command(s)
VALIDATE Alias of the VALIDATE command

Tip
Interesting chapter: Section 51.8, “How to copy files using a removable drive”.

With file commands it is possible to copy/delete a file or to transfer a file from and to Abilis CF/HD. Abilis supports
XMODEM, XMODEM-1K, ZMODEM protocols for file transfer, from and to Abilis (use a terminal emulator which is
compatible with the protocols mentioned above, to transfer files or system releases).

[15:43:26] ABILIS_CPX:file ?

COPY Make a copy of a file

DELETE Delete a file
GET Send a file using XMODEM or XMODEM-1K or ZMODEM
PUT Receive a file using XMODEM or XMODEM-1K or ZMODEM

With sys commands it is possible to manage Abilis CPX system software.

The following command displays the syntax:

[15:43:26] ABILIS_CPX:sys ?

COMPACT Directory re-compacting operation

COMPACTR Directory re-compacting operation, recursive
DELETE Delete operations
DIR List operations
DISK Disk and Volume management
DISPLAY Display operations
SET Set operations
UPDATE Receive a package or a new disk image and update the system

5.13.1. CONFLOG BACKUP and CONF BACKUP

This command copies configuration and Log files (DRIVERS.CFG, DRIVERS.BCK, DHCP.BND, CPX.LOG, CPX.DBG
and CPX.XCP) of the current version or of the specified version to a removable disk.

149
Draft Command language Draft

The <version> string must correspond to an existing version directory in the form 'X.Y.Z' or 'X-Y-Z' or 'Y.Z' or 'Y-Z' or 'Y',
where X, Y and Z are decimal digit [0 - 9] (E.g.: 6-0-8).

With the command conf backup it is possible to copy only configurations file.

[15:43:26] ABILIS_CPX:conflog backup

YOU ARE GOING TO BACKUP CONFIGURATION AND LOG FILES OF CURRENT VERSION
TO 'D:\__Abilis_Cpx_Backup_And_Restore__'.
PROCEED (N/Y)?y

PROCEEDING WITH CONFIGURATION AND LOG FILES BACKUP...

FILE 'DRIVERS.CFG'... SUCCESSFULLY COPIED.
FILE 'DRIVERS.BCK'... SUCCESSFULLY COPIED.
FILE 'CPX.LOG'... SUCCESSFULLY COPIED.
FILE 'CPX.DBG'... SUCCESSFULLY COPIED.
FILE 'CPX.XCP'... SUCCESSFULLY COPIED.
FILE 'C:\APP\DHCP\DHCP.BND'... SUCCESSFULLY COPIED.

COMMAND COMPLETED

Tip
Interesting chapter: Section 51.8, “How to copy files using a removable drive”.

5.13.2. CONFLOG RESTORE / CONF RESTORE

These commands copy configuration files (DRIVERS.CFG and DRIVERS.BCK) from a removable disk to the current
version or to the specified version directory.

The <version> string must correspond to an existing version directory in the form 'X.Y.Z' or 'X-Y-Z' or 'Y.Z' or 'Y-Z' or 'Y',
where X, Y and Z are decimal digit [0 - 9] (E.g.: 6-0-8).

[15:43:26] ABILIS_CPX:conflog restore

YOU ARE GOING TO RESTORE CONFIGURATION FILES OF CURRENT VERSION

FROM 'D:\__Abilis_Cpx_Backup_And_Restore__'.
PROCEED (N/Y)?y

PROCEEDING WITH CONFIGURATION FILES RESTORE...

FILE 'D:\__Abilis_Cpx_Backup_And_Restore__\DRIVERS.CFG'... SUCCESSFULLY COPIED.
FILE 'D:\__Abilis_Cpx_Backup_And_Restore__\DRIVERS.BCK'... SUCCESSFULLY COPIED.

COMMAND COMPLETED

Tip
Interesting chapter: Section 51.8, “How to copy files using a removable drive”.

5.13.3. FILE COPY

This command makes a copy of the “srcname” file into the specified “dtsname” path/file. The following command displays
the syntax.

[15:43:26] ABILIS_CPX:file copy ?

FILE COPY srcname dstname Make a copy of a file

srcname Name of the source file to be copied <Mandatory>

Spaces are allowed. Strings holding spaces must be
written between quotation marks.
(E.g.: "C:\APP\MY USERS\aaa.log")
dstname Path or name of the target file <Mandatory>

150
Draft Command language Draft

Spaces are allowed. Strings holding spaces must be

written between quotation marks.
(E.g.: A: or C:\4-3-1\ or Fdsp.bin or C:\4-3-2\drivers.cfg)

The “srcname” must be a file name. If the path is omitted the source file is assumed to be located in the current running
version directory.

The “dstname” can either a path or a file name. If the path is omitted the destination directory is assumed to be the current
running version directory.

Wildcards characters are not accepted either in the source file name nor in the destination name.

File copies to root directory are not allowed.

Log files (Cpx.log, Cpx.dbg and Cpx.xcp) and Cpx.rtb file cannot be overwritten.

5.13.4. FILE DELETE

This command deletes the specified file. The following command displays the syntax.

[15:43:26] ABILIS_CPX:file delete ?

FILE DELETE filename Delete a file

filename Name of the file to be deleted. <Mandatory>

Spaces are allowed. Strings holding spaces must be
written between quotation marks.
(E.g.: "C:\APP\MY DATA\aaa bbb.dat")

The “filename” must be a file name. If the path is omitted the source file is assumed to be located into the current running
version directory.

Wildcards characters are not accepted in the file name.

Files that are located into root directory cannot be deleted.

File copies to root directory are not allowed.

Configuration files, log files (Cpx.log, Cpx.dbg and Cpx.xcp) and any other system file cannot be deleted from the
current running version directory.

5.13.5. FILE GET

This command allows to download files from the Abilis CPX. The following command displays the syntax.

[15:43:26] ABILIS_CPX:file get ?

FILE GET [X] fname [<ver>][1K] Send a file using XMODEM or XMODEM-1K
FILE GET Z fname [<ver>] Send a file using ZMODEM

X or Z Select the X or Z MODEM protocol (by default XMODEM is used)

XMODEM transfer is allowed only on files relative to the running
version directory or to the specified '<ver>' version directory.
ZMODEM transfer is allowed on any files. For file not relative
either to the running version directory or to the '<ver>'
version directory, the absolute file name is required i.e.
including the full path.
fname Name of the file to be sent <Mandatory>
Spaces are allowed. Strings holding spaces must be
written between quotation marks.
(E.g.: "C:\APP\MY DATA\aaa bbb.dat")
<ver> String corresponding to a version directory in <Optional>
the form [x.y.z or x-y-z or y.z or y-z or y].
(E.g.: 5.3.1 or 6-1-0 or 2189).
1K Select XMODEM-1K transfer protocol <Optional>

151
Draft Command language Draft

The transfer procedure signals its availability to send the file by the message:

READY TO SEND FILE...

When the transfer is completed the following message is shown:

FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

After pressing the Enter button, if the transfer was successful, the following message will be shown.

FILE TRANSFER SUCCESFULLY COMPLETED

5.13.6. FILE PUT

This command allows to upload files to the Abilis CPX. The following command displays the sintax:

[15:43:28] ABILIS_CPX:file put ?

FILE PUT [X] fname [<ver>] Receive a file using XMODEM or XMODEM-1K
FILE PUT Z fname [<ver>] Receive a file using ZMODEM

X or Z Select the X or Z MODEM protocol (by default XMODEM is used)

XMODEM transfer is allowed only on files relative to the running
version directory or to the specified '<ver>' version directory
and only the following files are allowed:
DRIVERS.CFG, DRIVERS.BCK, ESB2.BIN, D1K, D2K, D8K, D1C?F?.BIN,
D2C?F?.BIN, D8C?F?.BIN, DELICPRG.BIN, HFC2B4.BIN, HFC2E4.BIN,
HFC2B8.BIN, HFC2E8.BIN, QPRI2B.BIN, QPRI2E.BIN, CTIHA2.BIN,
QPRIXC64.BIN, QPRIX.BIN, OCTASIC.BIN, DHCP.BND, IKE.CNS,
SL-*.BIN, STH330-?.BIN, STHUSB-?.BIN and USB devices firmware
files.
ZMODEM transfer is allowed on any files. For file not relative
either to the running version directory or to the '<ver>'
version directory, the absolute file name is required i.e.
including the full path.
fname Name of the file to be received <Mandatory>
Spaces are allowed. Strings holding spaces must be
written between quotation marks.
(E.g.: "C:\APP\MY DATA\aaa bbb.dat")
<ver> String corresponding to a version directory in <Optional>
the form [x.y.z or x-y-z or y.z or y-z or y].
(E.g.: 5.3.1 or 6-1-0 or 2189).

The transfer procedure signals its availability to receive the file by the message:

READY TO RECEIVE FILE...

When the transfer is completed the following message is shown:

FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

After pressing the Enter button, if the transfer was successful, the following message will be shown.

FILE TRANSFER SUCCESFULLY COMPLETED

Once the file is received, it is submitted to a congruence control for checking its content validity. The User is informed
through the message:

RECEIVED FILE 'namefile' CHECK IN PROGRESS...

If the file content is not correct:

CHECK FAILED: FILE 'namefile' DELETED

If file content and version are correct:

CHECK PASSED

152
Draft Command language Draft

5.13.7. SYS COMPACT

This command compacts the specified directory. It's useful when a lot of files have been deleted or renamed in a directory to
reduce its size.

[14:13:06] ABILIS_CPX:sys compact c:

COMPACTING DIRECTORY 'c:' ...

COMMAND EXECUTED, RECOVERED 2 SHORT DIRECTORY ENTRIES

Note
This command copies all used directory entries to the start of the directory and zeros out all slack space. If
the slack space is larger than one cluster, the slack space is freed, reducing the allocated size of a directory.

5.13.8. SYS COMPACTR

This command compacts specified directory and sub-directories. It's useful when a lot of files have been deleted or renamed
in a directory and sub-directories to reduce their size.

[14:14:43] ABILIS_CPX:sys compactr c:

THIS OPERATION MAY TAKE FEW MINUTES AND LOCKS ACCESS TO DISK c:
PROCEED ANYWAY (N/Y)?y

COMPACTING DIRECTORY 'c:' AND ALL OF ITS SUBDIRECTORIES...

COMMAND EXECUTED, RECOVERED 0 SHORT DIRECTORY ENTRIES

Note
This command copies all used directory entries to the start of the directory and zeros out all slack space. If
the slack space is larger than one cluster, the slack space is freed, reducing the allocated size of a directory.

5.13.9. SYS DELETE PACKAGE

This command deletes the specified package file. Use sys delete package <name of package> where <name of package>
must be the name of a package file located in 'C:\pkg' or an absolute package file name (the full path is required).

[14:21:22] ABILIS_CPX:sys delete package test.pkg

YOU ARE GOING TO DELETE THE 'C:\PKG\TEST.PKG' PACKAGE FILE.

PROCEED (N/Y)?y

PACKAGE 'C:\PKG\TEST.PKG' DELETED

5.13.10. SYS DELETE VERSION

It deletes the specified version directory.

[14:23:25] ABILIS_CPX:sys dir c:\

Directory listing of c:\

PKG <DIR> 22/05/2009 11:59:14

LOG <DIR> 22/05/2009 11:59:14
APP <DIR> 22/05/2009 11:59:14
USR <DIR> 22/05/2009 11:59:14
LICENCE <DIR> 27/05/2010 12:26:42
6-4-6 <DIR> 10/11/2009 11:13:34
6-4-8 <DIR> 17/12/2009 12:30:40
6-5-6 <DIR> 27/05/2010 12:25:18
7-0-0 <DIR> 05/10/2010 10:29:44
6-3-10 <DIR> 22/05/2009 11:58:22
7-0-2 <DIR> 22/11/2010 10:32:38

153
Draft Command language Draft

7-0-3 <DIR> 13/12/2010 10:08:10

7-0-4 <DIR> 20/01/2011 10:58:00
BM.CFG 107 21/01/2011 12:10:38
BM.LOG 4096 21/01/2011 12:10:38
TIMECFG.DAT 30 21/01/2011 13:10:58
CPXRUN.CFG 80 21/01/2011 13:10:50
BOOTSECT.RTT 512 22/05/2009 11:58:22
bm.RTA 115200 22/05/2009 11:58:22

Found 13 directories, 6 files.

Total 124 MB, Used 59 MB, Free 65 MB.

[14:23:42] ABILIS_CPX:sys delete version 7-0-3

YOU ARE GOING TO DELETE THE 'C:\7-0-3' VERSION DIRECTORY.

PROCEED (N/Y)?y

VERSION 'C:\7-0-3' DELETED

[14:24:23] ABILIS_CPX:sys dir c:\

Directory listing of c:\

PKG <DIR> 22/05/2009 11:59:14

LOG <DIR> 22/05/2009 11:59:14
APP <DIR> 22/05/2009 11:59:14
USR <DIR> 22/05/2009 11:59:14
LICENCE <DIR> 27/05/2010 12:26:42
6-4-6 <DIR> 10/11/2009 11:13:34
6-4-8 <DIR> 17/12/2009 12:30:40
6-5-6 <DIR> 27/05/2010 12:25:18
7-0-0 <DIR> 05/10/2010 10:29:44
6-3-10 <DIR> 22/05/2009 11:58:22
7-0-2 <DIR> 22/11/2010 10:32:38
7-0-4 <DIR> 20/01/2011 10:58:00
BM.CFG 107 21/01/2011 12:10:38
BM.LOG 4096 21/01/2011 12:10:38
TIMECFG.DAT 30 21/01/2011 13:10:58
CPXRUN.CFG 80 21/01/2011 13:10:50
BOOTSECT.RTT 512 22/05/2009 11:58:22
bm.RTA 115200 22/05/2009 11:58:22

Found 12 directories, 6 files.

Total 124 MB, Used 52 MB, Free 72 MB.

5.13.11. SYS UPDATE

This command makes possible the system software update in two ways:

• By receiving from a remote source the package file holding the updated software and installing it on the CF/HD in a proper
version directory.

The transfer procedure signals its availability to receive the package file by the following messages:

[18:01:32] ABILIS_CPX:sys update

SYSTEM UPDATE PROCEDURE

PLEASE UPLOAD THE PACKAGE FILE.

READY TO RECEIVE PACKAGE...

When the transfer is completed the following message is shown:

PACKAGE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

154
Draft Command language Draft

Once the Enter button is pressed by the User, if the transfer was successful, an informative message will be shown and the
system will start the received package integrity check procedure. If the received package passes the validation procedure,
the software extraction and installation takes place.

PACKAGE TRANSFER SUCCESSFULLY COMPLETED

RECEIVED PACKAGE CHECK and EXTRACTION IN PROGRESS...

CHECK PASSED, EXTRACTION DONE.

VERSION '7-0-3' SUCCESSFULLY INSTALLED.

• By a package file already present in the 'C:\PKG' directory, installing it on the HD/CF in a proper version directory.

In this case the package file name specification is required by the User on the command line: sys update <package>. The
<package> string must be the name of a package file located in 'C:\PKG' or an absolute package file name (i.e. the full path
is required). If the specified package file is not present, the message “FILE 'C:\PKG\<package> NOT FOUND” will be
shown.

The procedure starts with a package integrity check. If the package passes the validation phase, the software extraction and
installation takes place.

[18:01:32] ABILIS_CPX:sys update 7-0-3

PACKAGE 'C:\PKG\7-0-3.PKG' CHECK and EXTRACTION IN PROGRESS (7-0-3)...

CHECK PASSED, EXTRACTION DONE.

VERSION '7-0-3' SUCCESSFULLY INSTALLED.

If the package verifications and extraction is successful, the package file is always deleted.

If the procedure fails for any reason, the package deletion takes place only after the User confirmation.

The list of currently available package files can be displayed by the command sys display packages; while a package file can
be deleted by the command sys delete package.

Once a new software version is installed on the system, it can be set to be loaded at next system startup by the command
sys set boot version. The list of currently available versions can be displayed by the command sys display versions. Old
versions, not longer useful, can be deleted by the command sys delete version.

Tip
Interesting chapter: Section 51.4, “How to remotely upgrade the Abilis firmware”.

5.13.12. SYS DIR

It shows the directory listing of the specified path.

[14:26:13] ABILIS_CPX:sys dir c:\

Directory listing of c:\

PKG <DIR> 22/05/2009 11:59:14

LOG <DIR> 22/05/2009 11:59:14
APP <DIR> 22/05/2009 11:59:14
USR <DIR> 22/05/2009 11:59:14
LICENCE <DIR> 27/05/2010 12:26:42
6-4-6 <DIR> 10/11/2009 11:13:34
6-4-8 <DIR> 17/12/2009 12:30:40
6-5-6 <DIR> 27/05/2010 12:25:18
7-0-0 <DIR> 05/10/2010 10:29:44
6-3-10 <DIR> 22/05/2009 11:58:22
7-0-2 <DIR> 22/11/2010 10:32:38
7-0-4 <DIR> 20/01/2011 10:58:00
BM.CFG 107 21/01/2011 12:10:38

155
Draft Command language Draft

BM.LOG 4096 21/01/2011 12:10:38

TIMECFG.DAT 30 21/01/2011 13:10:58
CPXRUN.CFG 80 21/01/2011 13:10:50
BOOTSECT.RTT 512 22/05/2009 11:58:22
bm.RTA 115200 22/05/2009 11:58:22

Found 12 directories, 6 files.

Total 124 MB, Used 52 MB, Free 72 MB.

5.13.13. SYS DISK INFO

It displays logical drive(s) information.

[14:43:07] ABILIS_CPX:sys disk info

Logical drive(s) information:

Drv Disk Label FAT Free space Used space Total space
Interface Sectors per block Cluster size Bootable
-------------------------------------------------------------------------------
C: HD-0 16 72 MB 52 MB 124 MB
IDE-PIO-32 1 2,048 Bytes YES
-------------------------------------------------------------------------------
D: HD-4 USB_DRIVE 32 976 MB 2 KB 976 MB
USB 2,048 Bytes YES
-------------------------------------------------------------------------------

5.13.14. SYS DISK CHK

It checks the disk drive integrity. Use sys disk chk ? to display options.

[14:27:57] ABILIS_CPX:sys disk chk

THIS OPERATION MAY TAKE FEW MINUTES AND LOCKS ACCESS TO ALL DISKS.
PROCEED ANYWAY (N/Y)?y

DISK 'C:' INTEGRITY CHECK IN PROGRESS...

DISK 'C:' INTEGRITY CHECK SUCCESSFULLY COMPLETED

NO ERRORs WERE FOUND

5.13.15. SYS DISK FORMAT

It formats the specified drive. Note that system drive c: can't be formatted.

[14:35:22] ABILIS_CPX:sys disk format d:

DO YOU REALLY WANT TO FORMAT DRIVE 'D:' (N/Y)?y

THIS OPERATION WILL DELETE ALL EXISTING DATA FROM DRIVE 'D:'.
PROCEED ANYWAY (N/Y)?y

DRIVE 'D:' FORMAT IN PROGRESS... DONE.

ENTER VOLUME LABEL (MAX. 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): udisk

DRIVE 'D: FORMATTED:

FILE SYSTEM IS FAT-32, Size: 976 MB

Bytes per sector: 512, Sectors per cluster: 4, Clusters: 500054
Serial N. 3E35-746F, Label: UDISK

COMMAND COMPLETED

156
Draft Command language Draft

5.13.16. SYS DISK LABEL

It set the label of the selected drive or remove any existing label.

[14:41:40] ABILIS_CPX:sys disk label d:

ENTER VOLUME LABEL (MAX. 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): usb_drive

COMMAND EXECUTED

[14:41:51] ABILIS_CPX:sys disk info

Logical drive(s) information:

Drv Disk Label FAT Free space Used space Total space
Interface Sectors per block Cluster size Bootable
-------------------------------------------------------------------------------
C: HD-0 16 72 MB 52 MB 124 MB
IDE-PIO-32 1 2,048 Bytes YES
-------------------------------------------------------------------------------
D: HD-4 USB_DRIVE 32 976 MB 2 KB 976 MB
USB 2,048 Bytes YES
-------------------------------------------------------------------------------

5.13.17. SYS DISK MBR DUMP

It displays Master Boot Record of a disk.

[14:45:58] ABILIS_CPX:sys disk mbr dump hd:0

Address | Hexadecimal values | Ascii values

---------+-------------------------------------------------+-----------------
00000000 | FA BE 00 7C BF 00 7A B9 00 01 FC 0E 1F 0E 07 F3| ...|..z.........
00000010 | A5 EA 16 7A 00 00 BB BE 7B 33 C9 80 3F 80 75 06| ...z....{3..?.u.
00000020 | FE C5 8B F3 EB 07 80 3F 00 75 02 FE C1 83 C3 10| .......?.u......
00000030 | 81 FB FE 7B 72 E5 83 F9 04 74 0B 81 F9 03 01 74| ...{r....t.....t
00000040 | 0A BB A6 7A EB 2C BB 87 7A EB 27 8B 4C 02 8B 14| ...z.,..z.'.L...
00000050 | B8 01 02 BB 00 7C CD 13 73 05 BB BE 7A EB 13 2E| .....|..s...z...
00000060 | A1 FE 7D 3D 55 AA 74 05 BB BE 7A EB 05 EA 00 7C| ..}=U.t...z....|
00000070 | 00 00 2E 8A 07 3C 00 74 0C 53 BB 07 00 B4 0E CD| .....<.t.S......
00000080 | 10 5B 43 EB ED EB FE 4E 6F 20 62 6F 6F 74 61 62| .[C....No bootab
00000090 | 6C 65 20 70 61 72 74 69 74 69 6F 6E 20 69 6E 20| le partition in
000000A0 | 74 61 62 6C 65 00 49 6E 76 61 6C 69 64 20 50 61| table.Invalid Pa
000000B0 | 72 74 69 74 69 6F 6E 20 74 61 62 6C 65 00 49 6E| rtition table.In
000000C0 | 76 61 6C 69 64 20 6F 72 20 64 61 6D 61 67 65 64| valid or damaged
000000D0 | 20 42 6F 6F 74 61 62 6C 65 20 70 61 72 74 69 74| Bootable partit
000000E0 | 69 6F 6E 00 53 79 73 74 65 6D 53 6F 66 74 20 42| ion.SystemSoft B
000000F0 | 6F 6F 74 20 50 61 72 74 69 74 69 6F 6E 20 53 65| oot Partition Se
00000100 | 63 74 6F 72 00 00 00 00 00 00 00 00 00 00 00 00| ctor............
00000110 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000120 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000130 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000140 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000150 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000160 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000170 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000180 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
00000190 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001A0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................
000001B0 | 00 00 00 00 00 00 00 00 14 9B 61 92 00 00 80 01| ..........a.....
000001C0 | 01 00 06 07 E0 E8 20 00 00 00 E0 E8 03 00 00 00| ...... .........
000001D0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................

157
Draft Command language Draft

000001E0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00| ................

000001F0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 AA| ..............U.

5.13.18. SYS DISK PARTITION INFO

It displays partition(s) information.

[14:47:41] ABILIS_CPX:sys disk partition info

Available Hard Disk(s) information:

HD Size Partition Drive Label FAT Size Bootable

-------------------------------------------------------------------------------
0 125 MB 1 C: 16 124 MB YES
4 984 MB 1 D: USB_DRIVE 32 976 MB YES

5.13.19. SYS DISK PARTITION ADD

It adds partition(s) to the specified disk.

[14:47:41] ABILIS_CPX:sys disk partition info

Available Hard Disk(s) information:

HD Size Partition Drive Label FAT Size Bootable

-------------------------------------------------------------------------------
0 125 MB 1 C: 16 124 MB YES
4 984 MB 1 D: USB_DRIVE 32 976 MB YES

[14:48:05] ABILIS_CPX:sys disk partition add ?

HD: Hard disk index [0..31]

[14:48:33] ABILIS_CPX:sys disk partition add hd:4

Hard Disk '4' information:

HD Size Partition Drive Label FAT Size Bootable

-------------------------------------------------------------------------------
4 984 MB 1 D: USB_DRIVE 32 976 MB YES

HARD DISK '4' ALREADY HOLDS 1 PARTITIONs.

DO YOU WANT TO ADD A NEW PARTITION (N/Y)?y

THIS OPERATION WILL SPLIT PARTITION 1 ('D:') INTO TWO PARTITIONs.

ALL DATA ON 1 ('D:') PARTITION WILL BE LOST.
PROCEED (N/Y)?y

PLEASE ENTER THE SIZE YOU WANT TO RESERVE FOR PARTITION 1 ('D:'),
THE REMAINING SPACE WILL BE ASSIGNED TO THE NEW PARTITION,
IN MBytes (0 TO EXIT): 400

THE SIZE OF PARTITION 1 ('D:') WILL BE ABOUT 400 MB

THE SIZE OF THE NEW PARTITION WILL BE ABOUT 576 MB
PROCEED (N/Y)?y

HARD DISK PARTITIONING OPERATIONS REQUIRE THAT NO FILES ARE OPENED.

IF SOME FILES ARE CURRENTLY OPENED IN THE SYSTEM,
THE COMMAND WILL WAIT UNTIL ALL FILES WILL BE CLOSED.
PROCEED (N/Y)?y

WAITING THAT ALL FILES GET CLOSED (TYPE CTRL+C + ENTER TO STOP)... DONE.

158
Draft Command language Draft

NEW PARTITION CREATION IN PROGRESS... DONE.

PARTITION 1 ('D:') SUCCESSFULLY SPLITTED ON HARD DISK '4'

PARTITION 2 ('E:') SUCCESSFULLY CREATED ON HARD DISK '4'

DRIVE 'D:' FORMAT IN PROGRESS... DONE.

ENTER VOLUME LABEL (MAX. 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): usb_drive

DRIVE 'D: FORMATTED:

FILE SYSTEM IS FAT-32, Size: 976 MB

Bytes per sector: 512, Sectors per cluster: 4, Clusters: 500054
Serial N. 3E35-7630, Label: USB_DRIVE

5.13.20. SYS DISK PARTITION RESET

It resets all existing partition(s) for the specified disk.

[15:01:10] ABILIS_CPX:sys disk partition reset hd:4

Hard Disk '4' information:

HD Size Partition Drive Label FAT Size Bootable

-------------------------------------------------------------------------------
4 984 MB 1 D: PENDRIVE 32 976 MB YES

DO YOU REALLY WANT TO DELETE ALL EXISTING PARTITIONs ON HARD DISK '4' (N/Y)?y

THIS OPERATION WILL DELETE ALL EXISTING PARTITIONs AND CREATE

A SINGLE NEW PARTITION ON HARD DISK '4'.
PROCEED (N/Y)?y

HARD DISK PARTITIONING OPERATIONS REQUIRE THAT NO FILES ARE OPENED.

IF SOME FILES ARE CURRENTLY OPENED IN THE SYSTEM,
THE COMMAND WILL WAIT UNTIL ALL FILES WILL BE CLOSED.
PROCEED (N/Y)?y

WAITING THAT ALL FILES GET CLOSED (TYPE CTRL+C + ENTER TO STOP)... DONE.

CREATING A SINGLE NEW PARTITION ON HARD DISK '4'... DONE.

PARTITION 1 ('D:') SUCCESSFULLY CREATED ON HARD DISK '4'

DRIVE 'D:' FORMAT IN PROGRESS... DONE.

ENTER VOLUME LABEL (MAX. 11 CHARACTERs, PRESS <ENTER> FOR NO LABEL): drive1

DRIVE 'D: FORMATTED:

FILE SYSTEM IS FAT-32, Size: 980 MB

Bytes per sector: 512, Sectors per cluster: 4, Clusters: 501837
Serial N. 3E35-7851, Label: DRIVE1

COMMAND COMPLETED

5.13.21. SYS SET BOOT VERSION

This command allows to change Boot Manager configuration setting the version that must be loaded at next system startup.

The list of available versions can be displayed by sys display versions command; while the current/new Boot Manager
configuration is displayed by sys display boot command.

[15:43:26] ABILIS_CPX:sys display boot

159
Draft Command language Draft

Abilis CPX Boot Manager configuration:

Previous version Current version Next Version to load

------------------------------------------------------------------------------
7-0-2 7-0-2 7-0-2

[15:43:26] ABILIS_CPX:sys set boot version 6-0-8

BOOT MANAGER CONFIGURATION UPDATED:

THE NEXT VERSION THAT WILL BE LOADED IS '7-0-3'.

COMMAND EXECUTED

[[15:43:26] ABILIS_CPX:sys display boot

Abilis CPX Boot Manager configuration:

Previous version Current version Next Version to load

------------------------------------------------------------------------------
7-0-2 7-0-2 7-0-3

5.13.22. SYS DISPLAY BOOT LOG

This command allows to show some information about Abilis boot. Every time Abilis CPX boots a log, showing the date and
time, is generated.

[14:14:57] ABILIS_CPX:_d t

Current Local Time : Wednesday 03/11/2010 14:15:00 (UTC+1.00)

Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague...
Currently Observing : Standard Time (STD)

[14:15:00] ABILIS_CPX:_warm start

PROCEED WITH WARM START (N/Y)?y

...

[14:16:37] ABILIS_CPX:_sys display boot log

Boot Manager log file:

...

***** New run at 2010-11-03 14:16:06 *****

CPX Boot manager: v. 2014 - 30/06/2009
Setting current directory
Loading configuration
Loading CPX response file
Accepting 'new' version
Saving configuration
Removing CPX response file
Writing info to shared region
Loading file: 7-0-2\CPX.RTB
Starting loaded RTB file

Caution
Releases above 7.0.0 of Abilis CPX stores in the RTC (The Real-Time-Clock chip) the UTC time rather than
the Local time. Boot Manager should be updated to the new version in order to manage the time correctly.
Unfortunately this cannot be done remotely, it requires a reinstallation of the Abilis CPX software (please

160
Draft Command language Draft

refer to How to prepare an Abilis Compact-Flash using a PC1). If BM is not reinstalled Abilis CPX 7.0
will work anyway but the time you see with SYS DISPLAY BOOT LOG will be UTC time, it will not be
adjusted to the Local Time as the new BM would do.

[12:32:35] ABILIS_CPX:_sys display boot log

Boot Manager log file:

...

***** New run at 2010-11-03 11:32:02 *****

CPX Boot manager: v. 2014 - 30/06/2009
Setting current directory
Loading configuration
Loading CPX response file
Accepting 'new' version
Saving configuration
Removing CPX response file
Writing info to shared region
Loading file: 7-0-2\CPX.RTB
Starting loaded RTB file

[12:32:42] ABILIS_CPX:_d t

Current Local Time : Wednesday 03/11/2010 12:33:10 (UTC+1.00)

Local Time Zone : CET - Central Europe (Rome, Paris, Berlin, Prague...
Currently Observing : Standard Time (STD)

Warning
Abilis CPX 7.0.0 is not compatible with very old BM. If your CF has been created from scratch with a
version 6.0.0 or later you will not have problems If your CF has been created with a version 5.x.x or earlier
you may have problems, in this situation we strongly suggest a complete reinstallation (please refer to How
to prepare an Abilis Compact-Flash using a PC2).

5.13.23. WARM START

This command immediately executes the system restart.

[11:38:04] ABILIS_CPX:warm start

• If in the current session the configuration was modified but not saved, the command displays a warning message and
queries the User for proceeding with configuration saving or not.

In case of affirmative answer, the save conf command is executed, the reset of the Abilis CPX is not executed and the
Control Port prompt is shown.

[11:38:04] ABILIS_CPX:warm start

THE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED.

PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?y

VALIDATION IN PROGRESS...
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

• If a different version from the currently running one was set to be loaded at next system start up (sys set boot version), the
command displays a warning message and queries the User for proceeding with system restart.

[11:38:04] ABILIS_CPX:warm start

BOOT MANAGER CONFIGURATION WAS MODIFIED:

161
Draft Command language Draft

THE NEXT VERSION THAT WILL BE LOADED IS '7-0-3',

WHILE THE CURRENTLY RUNNING VERSION IS '7-0-2'.

PROCEED WITH WARM START (N/Y)?y

Note
The -f option, force system warm start interrupting any operation that is in progress (e.g. configuration
saving, system updating, file uploading/downloading and so on).

[11:38:04] ABILIS_CPX:warm start -f

ATTENTION!
FORCING "WARM START" IS DANGEROUS BECAUSE ANY OPERATION IN PROGRESS
WILL BE SUDDENTLY INTERRUPTED, SIMILARLY TO A POWER OFF EVENT.
THIS ACTION CAN CAUSE FILES CORRUPTION.
PROCEED ANYWAY WITH WARM START (N/Y)?y

In case of affirmative answer, the reset of the Abilis CPX is executed, while in case of negative answer the
Control Port prompt is shown.

5.14. Diagnostics and Statistics

Abilis CPX provides a lot of information about diagnostics and statistics of ports and resources, useful for technical support.

5.14.1. Diagnostic commands

Diagnostic commands give information about the state of an Abilis resource or port (i.e. READY, UP, DOWN,
CONNECTED, DISCONNECTED, BLOCKED, …).

5.14.1.1. D D (Display Diagnostics)

The following command displays the syntax:

[12:43:19] ABILIS_CPX:d d ?

D D RES:A Display diagnostics of any resource

D D [RES:]type Display diagnostics of any resource
of the specified type
D D [RES:]type-n[,...] Display diagnostics of the specified
resource(s)
D D CTIAC[:val] Display diagnostics of CTI ACs
D D CTIEEC[:val] Display diagnostics of CTI Extended
Echo Cancelers
D D CTIHDLC[:val] Display diagnostics of CTI HDLC
controllers
D D CTICL [CLUS:name] Display diagnostics of any CTI
cluster, where 'name' is a CTI cluster
name
D D CTIL [ID:xxx] Display diagnostics of any CTI link,
where 'xxx' is a CTI link identifier
in the range [1..256]
D D CTILG [ID:xxx] Display diagnostics of any CTI group of
links, where 'xxx' is a CTI group of
links identifier in the range [1..256]
D D CTIP[:xxx] Display diagnostics of any CTI port,
where 'xxx' is a CTI port identifier
in the range [1..300]
D D LCST Display diagnostics of LCS table service

For example, to show the diagnostics of a Packet Voice IP tunnel, type:

[12:43:19] ABILIS_CPX:d d pv-1

162
Draft Command language Draft

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis2
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | READY | READY |
+--------+---------------+----------------------+----------------------+
- IP Tunnel ------------------------------------------------------------
STATE:READY MODE:EXT PATHS:SINGLE

The tunnel above is working correctly: Primary Link is READY, so the VPN is UP. In the screen-shot below, the Primary
Link is not working, so ISDN backup is guarantying the VPN working.

[12:43:19] ABILIS_CPX:d d pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis2
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | DOWN2 | CONNECTED TO |
+--------+---------------+----------------------+----------------------+
- IP Tunnel ------------------------------------------------------------
STATE:READY MODE:EXT PATHS:SINGLE

5.14.1.2. D DE (Display Diagnostics Extended)

This command shows extended information about the state of an Abilis resource or a port. The following command displays
the syntax:

[12:43:19] ABILIS_CPX:d de ?

D DE RES:A Display extended diagnostics of any

resource
D DE [RES:]type Display extended diagnostics of any
resource of the specified type
D DE [RES:]type-n[,...] Display extended diagnostics of the
specified resource(s)
D DE CTIAC[:val] Display extended diagnostics of CTI
ACs
D DE CTIEEC[:val] Display extended diagnostics of CTI
Extended Echo Cancelers
D DE CTIHDLC[:val] Display extended diagnostics of CTI
HDLC controllers
D DE CTICL [CLUS:name] Display extended diagnostics of any
CTI cluster, where 'name' is a CTI
cluster name
D DE CTIL [ID:xxx] Display extended diagnostics of any
CTI link, where 'xxx' is a CTI link
identifier in the range [1..256]
D D CTILG [ID:xxx] Display extended diagnostics of any
CTI group of links, where 'xxx' is a
CTI group of links identifier in the
range [1..256]
D DE CTIP[:xxx] Display extended diagnostics of any
CTI port, where 'xxx' is a CTI port
identifier in the range [1..300]

For example, here below is displayed the diagnostic of a Frame Relay resource:

[12:43:19] ABILIS_CPX:d d fr-1

RES:Fr-1 - FR over Dedicated Line (DL) ----------------------------------------

- Frame Relay ----------------------------------------------------------
STATE:DOWN
- Link -----------------------------------------------------------------

163
Draft Command language Draft

+--------+--- Global ----+------- P-Link -------+------- S-Link -------+

| STATE: | READY | READY | LINK-NOT-PRESENT |
+--------+---------------+----------------------+----------------------+

This diagnostic shows the state of LMI and the state of the link.

Instead here below is displayed the extended diagnostic:

[12:43:19] ABILIS_CPX:d de fr-1

RES:Fr-1 - FR over Dedicated Line (DL) ----------------------------------------

- Frame Relay ----------------------------------------------------------
STATE:DOWN
DLCI State Cong MaxThr CurMaxThr 5sec-Thr-Out 5sec-Thr-In
Cir Bc StepConst MaxThr% 5min-Thr-Out 5min-Thr-In
Tc Be Step Cir% MaxFrame-Out MaxFrame-In
------------------------------------------------------------------------
16 DOWN NO 19200 19200 0 0
19200 19200 4 100% 0 0
1.000 0 4 100% 10 10
------------------------------------------------------------------------
17 DOWN NO 1024000 1024000 0 0
1024000 1024000 4 100% 0 0
1.000 0 4 100% 10 10
------------------------------------------------------------------------
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | READY | LINK-NOT-PRESENT |
+--------+---------------+----------------------+----------------------+

This diagnostic display the state of LMI and DLCI, the troughput incoming and outcoming, etc..

5.14.2. Statistics Commands

Statistics commands give information about parameters of an Abilis resource or port (i.e. byte transmitted, byte received,
missing packets and a lot of other, depending from the kind of resource).

5.14.2.1. D S (Display Statistics)

The following command displays the syntax:

[12:43:19] ABILIS_CPX:d s ?

D S RES:A Display statistics of any resource

D S [RES:]type Display statistics of any resource
of the specified type
D S [RES:]type-n[,...] Display statistics of the specified
resource(s)
D S CTIAC[:val] Display statistics of CTI ACs
D S CTICL [CLUS:name] Display statistics of any CTI cluster,
where 'name' is a CTI cluster name
D S CTIL [ID:xxx] Display statistics of any CTI link,
where 'xxx' is a CTI link identifier
in the range [1..256]
D S CTILG [ID:xxx] Display statistics of any CTI group of
links, where 'xxx' is a CTI group of links
identifier in the range [1..256]
D S CTIP[:xxx] Display statistics of any CTI port,
where 'xxx' is a CTI port identifier
in the range [1..300]
D S LCST Display statistics of LCS table service

For example, to show the statistics of a Packet Voice IP tunnel, type:

[12:43:19] ABILIS_CPX:d s pv-1

164
Draft Command language Draft

RES:Pv-1 -- PV over IP (Abilis tunnel) (IP) -----------------------------------

--- Cleared 0 days 00:23:54 ago, on 30/11/2010 at 15:43:02 -------------
- Link -----------------------------------------------------------------
TIME-CUR-CALL:0
RTY:0 DDT:NOMAX VDT:NOMAX USRTY:0 TDEL:0 TREM:0
PLINK-DN1:1 PLINK-DN2:1 PLINK-LC-TOUT:0
SLINK-ST1:0 SLINK-ST2:0 SLINK-LC-TOUT:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
D-COMP-YES | 0| 0|D-COMP-ORIG| 0| 0|
D-COMP-NO | 0| 0|D-COMP-DONE| 0| 0|
D-BAD-COMP | 0| 0|D-COMP% | 0| 0|
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 1894| 1898|FRM | 316| 316|
IP-CHR | 10742| 12642|IP-FRM | 316| 316|
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-RED-FM | | 0|V-RED-VOICE| | 0|
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 0| 0| 0|
NOBUF | 0| 0| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 0 ( 0% ) | 151-200 | 0 ( 0% ) |
21- 50 | 0 ( 0% ) | 201-300 | 0 ( 0% ) |
51-100 | 0 ( 0% ) | 301-600 | 0 ( 0% ) |
101-150 | 0 ( 0% ) | 601-xxx | 0 ( 0% ) |
------------------------------------------------------------------------

A lot of information are available: number of characters sent and received, number of missing packets, number of P-Link
interruptions, number of seconds of ISDN backup calls, packets time arrival, and so on.

5.14.2.2. D SE (Display Statistics Extended)

This command shows extended information about parameters of an Abilis resource or port. The following command displays
the syntax:

[12:43:19] ABILIS_CPX:d se ?

D SE RES:A Display extended statistics of any

resource
D SE [RES:]type Display extended statistics of any
resource of the specified type
D SE [RES:]type-n[,...] Display extended statistics of the
specified resource(s)
D SE CTIAC[:val] Display extended statistics of CTI ACs
D SE CTICL [CLUS:name] Display extended statistics of any
CTI cluster, where 'name' is a CTI
cluster name
D SE CTIL [ID:xxx] Display extended statistics of any
CTI link, where 'xxx' is a CTI link
identifier in the range [1..256]
D D CTILG [ID:xxx] Display extended statistics of any
CTI group of links, where 'xxx' is a
CTI group of links identifier in the

165
Draft Command language Draft

range [1..256]
D SE CTIP[:xxx] Display extended statistics of any
CTI port, where 'xxx' is a CTI port
identifier in the range [1..300]

Type the following command to show the extended statistics of a Packet Voice IP tunnel:

[12:43:19] ABILIS_CPX:d se pv-1

RES:Pv-1 -- PV over IP (Abilis tunnel) (IP) -----------------------------------

--- Cleared 0 days 00:25:23 ago, on 30/11/2010 at 15:43:02 -------------
- Link -----------------------------------------------------------------
TIME-CUR-CALL:0
RTY:0 DDT:NOMAX VDT:NOMAX USRTY:0 TDEL:0 TREM:0
PLINK-DN1:1 PLINK-DN2:1 PLINK-LC-TOUT:0
SLINK-ST1:0 SLINK-ST2:0 SLINK-LC-TOUT:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
D-COMP-YES | 0| 0|D-COMP-ORIG| 0| 0|
D-COMP-NO | 0| 0|D-COMP-DONE| 0| 0|
D-BAD-COMP | 0| 0|D-COMP% | 0| 0|
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
Tunnel payload
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 2014| 2018|FRM | 336| 336|
CHR-D | 0| 0|FRM-D | 0| 0|
CHR-V | 0| 0|FRM-V | 0| 0|
CHR-C | 2014| 2018|FRM-C | 336| 336|
------------------------------------------------------------------------
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 11422| 13442|IP-FRM | 336| 336|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 0| 0|IP-FRM-V | 0| 0|
IP-CHR-C | 11422| 13442|IP-FRM-C | 336| 336|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 0| 0|D-FRM-ENC | 0| 0|
V-CHR-OPT | 0| 0|V-FRM-ENC | 0| 0|
V-SAVED% | 0| 0|C-FRM-ENC | 336| 336|
V-FRM-OPT | 0| 0| | | |
V-RED-FM | | 0|V-RED-VOICE| | 0|
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 0| 0| 0|
TOUT | 0| 0| 0|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
DUPLICATED | 0| 0| 0|
REORDERED | 0| 0| 0|

166
Draft Command language Draft

BAD-FORM | 0| 0| |
RESYNC | 0| 0| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 0 ( 0% ) | 151-200 | 0 ( 0% ) |
21- 50 | 0 ( 0% ) | 201-300 | 0 ( 0% ) |
51-100 | 0 ( 0% ) | 301-600 | 0 ( 0% ) |
101-150 | 0 ( 0% ) | 601-xxx | 0 ( 0% ) |
------------------------------------------------------------------------

5.15. Test functionalities

5.15.1. Ping
This command executes a Ping to the specified IP address using the options indicated in the command row.

The following command allows have a complete list of the allowed options of the command:

[18:01:34] ABILIS_CPX:ping ?

Usage: ping <address> [-a] [-n count] [-l size] [-i TTL] [-v TOS] [-r count]
[-w timeout] [-z delay] [-f] [-p] [-m] [-s src_address]
[-t] [-ts] [-st nnn] [-std nnn]
Options:
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-t Echo requests are sent until interrupted by user.
-l size Send buffer size.
-f Set IP header "don't fragment" flag (DF).
-i TTL Time To Live.
-v TOS Type of service [use number or D, T, R, C].
-r count Record route for count hops.
-s src_address Set source address for outgoing requests.
-w timeout Timeout to wait for each reply [10..30000 msec].
-z delay Set time delay between consecutive ping requests
[0..300000 msec].
-p Show in/out interface of ping message [IP-xxx or INTERNAL].
-m Show MAC address of the response (host or gateway).
-ts Show timeStamp.
-st nnn Show IP-nnn resource char-in/out statistics.
-std nnn Show IP-nnn resource char-in/out differential statistics.

Here is an example of the command execution.

[18:01:34] ABILIS_CPX:ping 192.168.11.253

Pinging 192.168.11.253 with 32 bytes of data:

Reply from 192.168.11.253: bytes=32 time=6 ms TTL=64

Reply from 192.168.11.253: bytes=32 time=10 ms TTL=64
Reply from 192.168.11.253: bytes=32 time=7 ms TTL=64
Reply from 192.168.11.253: bytes=32 time=14 ms TTL=64

--- 192.168.11.253 ping statistics ---

4 packets transmitted, 4 received, 0% packet loss, time 3011ms
rtt min/avg/max = 6/9/14 ms

5.15.2. Tracert / Traceroute

This command traces the route of the IP packet sent to the IP address specified in the command row.

[18:01:34] ABILIS_CPX:tracert 192.168.11.253

167
Draft Command language Draft

Tracing route to 192.168.11.253 over a maximum of 30 hops

1 6 ms 6 ms 6 ms 192.168.11.253

Trace complete.

The following command displays the syntax:

[18:01:34] ABILIS_CPX:tracert ?

Usage: tracert/traceroute <address> [-a] [-h max_hops] [-w timeout] [-z delay]
[-p] [-m] [-s src_address]
Options:
-a Resolve addresses to hostnames.
-h max_hops Maximum number of hops to search for target.
-s src_address Set source address for outgoing requests.
-w timeout Wait timeout for each reply [max. 30000 msec].
-z delay Set time delay between consecutive hosts [max. 300000 msec].
-p Show in/out interface of trace message [IP-xx or INTERNAL].
-m Show MAC address of the response (host or gateway).

5.15.3. Pingstat
This command pings a destination and retrieves the increments in CHAR-INPUT and CHAR-OUTPUT of the resource(s) used
to transmit and receive, and some statistics useful for making line performances analysis (easily importable in a spreadsheet).

[18:01:34] ABILIS_CPX:pingstat 192.168.11.253 -t -l 1 -z 1000

Pinging 192.168.11.253 with 1 bytes of data:

Reply from 192.168.11.253: IpResOut=3 IpResIn=3 bytes=1 RTT=7 ms TTL=64

date time timeStamp diffIn diffOut RTT
14/01/2008 13:26:33 0 0 0 6
14/01/2008 13:26:34 999 92 64 5
14/01/2008 13:26:35 1999 118 109 6
14/01/2008 13:26:36 3000 238 189 6
14/01/2008 13:26:37 3998 46 29 5
14/01/2008 13:26:38 4999 92 62 5
14/01/2008 13:26:39 5999 46 29 5
14/01/2008 13:26:40 6999 46 29 5
14/01/2008 13:26:41 7999 138 97 6
14/01/2008 13:26:42 8999 94 29 6
14/01/2008 13:26:43 9998 236 224 6
14/01/2008 13:26:44 11002 166 109 9
14/01/2008 13:26:45 12007 46 29 5
14/01/2008 13:26:46 13012 46 29 10
14/01/2008 13:26:47 14007 140 62 6
14/01/2008 13:26:48 15007 46 29 5
14/01/2008 13:26:49 16007 46 29 5
14/01/2008 13:26:50 17008 282 257 6
14/01/2008 13:26:51 18014 118 109 12
14/01/2008 13:26:52 19007 92 64 5
14/01/2008 13:26:53 20007 94 29 6
14/01/2008 13:26:54 21012 94 29 11
14/01/2008 13:26:55 22007 46 29 6
14/01/2008 13:26:56 23007 92 62 6
14/01/2008 13:26:57 24007 238 189 6
14/01/2008 13:26:58 25007 118 109 6
14/01/2008 13:26:59 26007 138 97 6
14/01/2008 13:27:00 27006 46 29 6
14/01/2008 13:27:01 28006 92 64 5

--- 192.168.11.253 ping statistics ---

168
Draft Command language Draft

30 packets transmitted, 30 received, 0% packet loss, time 28006ms

rtt min/avg/max = 5/6/12 ms

PREVIOUS COMMANDS ABORTED

The following command displays the syntax:

[18:01:34] ABILIS_CPX:pingstat ?

Usage: pingstat <address> [-a] [-n count] [-l size] [-i TTL] [-v TOS] [-t]
[-w timeout] [-z delay] [-f] [-m] [-s src_address]
Options:
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-t Echo requests are sent until interrupted by user.
-l size Send buffer size.
-f Set IP header "don't fragment" flag (DF).
-i TTL Time To Live.
-v TOS Type of service [use number or D, T, R, C].
-s src_address Set source address for outgoing requests.
-w timeout Timeout to wait for each reply [10..30000 msec].
-z delay Set time delay between consecutive ping requests
[10..300000 msec].
-m Show MAC address of the response (host or gateway).
Outputs:
date Date when PING request is transmitted.
time Time when PING request is transmitted.
timeStamp Time elapsed from first request (milliseconds).
diffIn Number of incoming byte since the previous request.
diffOut Number of outgoing byte since the previous request.
RTT Round Trip Time of PING request and response (in msec).

5.15.4. DSPs test

The Audio Compressors DSPs test can be invoked manually by command TEST DSP. The execution of the test is logged.

[11:58:19] ABILIS_CPX:test dsp

YOU ASKED TO EXECUTE DSPs TEST ON EVERY CARD

PROCEED (N/Y)?y

DSPs TEST IN PROGRESS

THIS MAY TAKE FEW MINUTES (Type CTRL+C + ENTER to stop)...

BRI4-1
DSP:0 - good
POTS-1
skipped (no DSP present)
UG-1
skipped (no DSP present)
CB-1
skipped (no DSP present)

Overall test result: GOOD

COMMAND COMPLETED

[11:58:24] ABILIS_CPX:d l

Current Local Time: Sunday 12/12/2010 11:58:29 (UTC+1.00)

12/12/2010 11:58:13 [00257] I: SYSTEM LOG CLEARED

169
Draft Command language Draft

12/12/2010 11:58:24 [00291] I: DSP test start

12/12/2010 11:58:24 [00292] I: DSP test end

The test can be executed using various options:

[11:58:29] ABILIS_CPX:test dsp ?

TEST DSP [card] [method] [action] [output] [msec] Executes DSPs test

DSPs test options:

card Card selection. It must be 'type-n', where 'type' can be a CTI

card type and 'n' can be [1..255]
Execute the test of the specified card. By default the test is
executed on every card.
method Testing method selection [free, wait, force].
- free: test only the ACs which are free;
- wait: disable use of AC by CTIR and wait until all AC are free,
then make the test;
- force: disable use of AC by CTIR, force close of all calls that
use AC, wait until all AC are free, then make the test.
By default only free ACs are tested.
action Action selection [log, recover].
- log: only log errors and recovery actions;
- recover: log errors and recovery action plus, in case of
failure, automatically attempt to recover the DSP
via reset.
By default only log errors and recovery are done.
output Output selection [brief, detailed, quiet].
By default brief output is provided.
msec Duration of the test of each channel [100..10000 msec]
By default 500 msec.

Note
DSPs test is always performed at startup and it's logged. If the test detects a problem it attempts up to two
times to recover by resetting the DSP and repeating the test.

In case all DSPs are OK:

30/04/2008 18:24:10 [00291] I: DSP test start

30/04/2008 18:24:13 [00292] I: DSP test end

If there's some problem:

02/05/2008 17:22:13 [00291] I: DSP test start

02/05/2008 17:22:16 [00293] W: BRI4-5 DSP#0 BBBBB recover
02/05/2008 17:22:17 [00293] W: BRI4-5 DSP#0 BBBBB recover
02/05/2008 17:22:17 [00294] W: BRI4-5 DSP#0 BBBBB bad
02/05/2008 17:22:18 [00293] W: BRI4-5 DSP#1 BBBBB recover
02/05/2008 17:22:19 [00293] W: BRI4-5 DSP#1 BBBBB recover
02/05/2008 17:22:20 [00294] W: BRI4-5 DSP#1 BBBBB bad
02/05/2008 17:22:20 [00292] I: DSP test end

5.16. Trace functionalities

By typing the following command, an informative message about every trace command syntax will be shown.

[18:01:34] ABILIS_CPX:trace ??

TRACE ACT Activate Tracer using saved values

TRACE ACT PO:xx,yy,... [par:val] Activate Tracer on specified ports
TRACE CLEAR Clear the current trace
TRACE DELETE <file> Delete trace saved on disk in <file> file

170
Draft Command language Draft

TRACE DISPLAY [par:val] Display trace of sent and received data

TRACE DISPLAY EXTENDED [par:val] Display trace of all commands
TRACE DISPLAY INFO Display trace informative header
TRACE GET [X][1K] Transfer trace using XMODEM or XMODEM-1K
[ST: and/or LEN:] or [LAST:]
TRACE GET Z [<file>] Transfer trace using ZMODEM
[ST: and/or LEN:] or [LAST:]
TRACE INACT Deactivate Tracer
TRACE PARAM Display Tracer configured parameters, active
parameters and the current Tracer state
TRACE PARAM SAVE Save current Tracer parameters values
TRACE PARAM SET par:val [par:val] Set Tracer parameters
TRACE SAVE <file> Save trace on disk in <file> file
TRACE START [par:val] Run Tracer
TRACE STOP Stop Tracer

Tip
Interesting chapter: Section 51.19, “How to trace the internal events for debugging purposes”.

5.16.1. Trace act

The trace act command activates the internal events trace function. By typing the command trace act ?, an informative
message about trace activation syntax will be shown.

[18:01:34] ABILIS_CPX:trace act ?

TRACE ACT Activate Tracer using saved values

TRACE ACT PO:xx,yy,... [par:val] Activate Tracer on specified ports

PO: Ports to be traced (max. 50) <Mandatory>

SIZE: Tracer buffer size [3..262144 Kbytes] <Optional>
DATA: Max event buffer size [10..2100 bytes] <Optional>
CMD: Commands type [RSP, RSA, STD, CTIRSIG, FR-LMI, ALL] <Optional>
LSN: SD/RV lsn to be traced [ALL, 0000..FFFE (Hex.)] <Optional>
TYPE: SD/RV type to be traced [ALL, DATA, CHK, VOICE] <Optional>
-M Force Tracer activation <Reserved>

If no parameter is specified, the following message is displayed: “NO PARAMETER SPECIFIED: USING SAVED
VALUES...”, so the trace function is activated using the setting already saved through the commands trace param set and
trace param save. The first one modifies the trace parameters that will be used for further activations of the trace, while the
second saves, in the configuration file drivers.cfg, the parameters previously activated.

The trace param command shows the parameters settings of the internal events trace and its working mode; the information
shown will depend on the trace state.

Here's the meaning of parameters:

• PO sets the list of ports (minimum 1, maximum 50) which can be traced; their values must be in the interval [0 - 999].
Ports to be traced, must be “RUNNING”, if not, the following message will be displayed “RES:xxx PORT NOT
PRESENT OR NOT RUNNING” and the trace function won't be activated; “xxx” stands for the identifier of the not
present or not running port. Refer to Section 5.8.7, “D PSTACK” to have more information about ports;

• SIZE sets the maximum allocable memory size for the trace function. If the parameter is not specified, all the available
memory will be used by the system for trace activating, except the needed quantity for system management. If the system
memory is not enough for activating the trace function, it won't be activated and the following message will be displayed
“NOT ENOUGH MEMORY TO RUN TRACE”;

• DATA sets the maximum allocable memory size for saving the single event, remaining optional parameters CMD, LSN and
TYPE make possible the activation of filters on the events traced.

Tip
It is possible to enable the automatic trace activation at system start-up, if the parameter tact, in general
system block, is set to YES.

171
Draft Command language Draft

[18:01:34] ABILIS_CPX:d g

Conf.Value Act.Value Description

------------------------------------------------------------------------------
tact: YES YES Automatic TRACE activation at start-up [NO, YES]
TSAVE: YES YES Automatic TRACE saving [NO, YES]
sound: ON ON Alarm sound enable/disable [OFF, ON]
wdg-use: YES YES Enable/disable Watchdog usage [NO, YES]
wdg: - MFIDE2 Front Panel/WatchDog interface type <Read Only>
------------------------------------------------------------------------------
DBGF: ALL
CONTACT:
SYSNAME:
LOCATION:
SYSUPTIME: 5 days 17:41:45 (Monday 03/12/2007 03:24:12) <Read Only>
SYSRBTIME: # (System Reboot time not set)
DATE&TIME: Saturday 08/12/2007 21:05:57 (GMT+1.00) <Read Only>
TIMEZONE: CET - Central Europe (Rome, Paris, Berlin, Prague, Brussels)

5.16.2. Trace start

The trace start command starts saving the events exchanged among the ports specified in the list, which has been defined
during the trace activation (through the command trace act).

If in the command row is not indicated any additional parameter, the trace will start using the settings defined during its
activation. The following optional parameters can be specified LSN, DATA, TYPE, CMD. In this way trace parameters setting
may be edited again.

If the trace is not active the following message will be displayed “TRACE INACTIVE”. By typing the following command,
an informative message about the command syntax and options will be shown.

[18:01:34] ABILIS_CPX:trace start ?

TRACE START [DATA:val][CMD:val] Run Tracer

[LSN:hex-val][TYPE:val]

DATA: Max event buffer size [10..2100 bytes] <Optional>

CMD: Commands type [RSP, RSA, STD, CTIRSIG, FR-LMI, ALL] <Optional>
LSN: SD/RV lsn to be traced [ALL, 0000..FFFE (Hex.)] <Optional>
TYPE: SD/RV type to be traced [ALL, DATA, CHK, VOICE] <Optional>

5.16.3. Trace stop

The trace stop command stops tracing the events and stores the trace content in memory until the next trace start, through
the command trace start or the deactivation of the function (command trace inact). If the trace is not active the following
message will be displayed “TRACE INACTIVE”. If the trace function is not running, the message “TRACE NOT
RUNNING” will be displayed.

5.16.4. Trace get

The trace get command transfers the content of the internal events trace, previously saved by Abilis CPX to a remote
destination, by using the XModem or ZModem protocol. Option “1K” activates file transferring through the XModem 1K
protocol.

By default, the whole content of the trace, starting from the beginning of the saving, it is transferred. It is also possible, by
using the proper optional parameter, to transfer only a part of the content:

If the trace buffer is empty or got empty by the command trace clear, the message “TRACE EMPTY” will be shown.

Before executing this command, the trace function has to be stopped, by using the command trace stop, otherwise the
message “TRACE RUNNING” will be displayed. If the trace is not active, the message “TRACE INACTIVE” will be
shown.

172
Draft Command language Draft

The transfer procedure signals its availability to transfer the trace file by the message “READY TO SEND TRACE
BUFFER...” When the transfer is completed the following message is shown: “TRACE BUFFER TRANSFER ENDED,
PRESS <ENTER> TO CONTINUE...”, after pressing the <ENTER> button, an informative message, “TRACE BUFFER
TRANSFER SUCCESSFULLY COMPLETED”, will be shown if it was successful.

[18:01:34] ABILIS_CPX:trace get ?

TRACE GET [X][1K] Transfer trace using XMODEM or XMODEM-1K

[ST: and/or LEN:] or [LAST:]
TRACE GET Z [<file>] Transfer trace using ZMODEM
[ST: and/or LEN:] or [LAST:]

X or Z Select the X or Z MODEM protocol (by default XMODEM is used)

1K Use the XMODEM-1K transfer protocol <Optional>
<file> Select the name of the file on the target host
(ZMODEM protocol only) <Optional>
ST: Trace buffer start value [in Kbytes] <Optional>
LEN: Number of Kbytes to be transmitted, starting
from the beginning of the Tracer buffer or
from the "ST:" value <Optional>
LAST: Number of Kbytes to be transmitted, starting
from the end of the Tracer buffer <Optional>

The trace can also be transferred from the memory to a file with the command trace save <filename>. The file can be
downloaded with the command file get and deleted from disk with trace delete <filename>. For example:

[21:22:34] ABILIS_CPX:trace save trace.cpx

COMMAND EXECUTED

[21:22:34] ABILIS_CPX:d i

Abilis CPX - Ver. 7.0.2/STD - 12/10/2010 - Build 3357.4 - 12/10/2010

(c) 1994/2010 - Abilis

Free/Total Memory: 175,849,376/268,435,456 Largest Block: 175,844,640

Free/Used/Total HD/CF space (in KB): 90,122/32,228/122,350

File Version Date Time Size Note

-------------------------------------------------------------------------------
CPX.RTB ....... 12/10/2010 19:36:26 4163974
DRIVERS.CFG v.7.0 30/11/2010 15:43:02 15360 Ok
DRIVERS.BCK v.7.0 30/11/2010 15:43:02 15360 Ok
CPX.LOG v.1.0 30/11/2010 15:43:30 51200
CPX.DBG v.1.1 29/10/2010 15:35:32 20480
CPX.XCP ....... 29/10/2010 15:35:30 51200
BS44.BIN v.13.3 16/04/2010 20:25:10 91136
BS48.BIN v.4.7 16/04/2010 20:25:10 90112
ESB2.BIN v.13.0 28/10/2004 19:38:20 17408
DELICPRG.BIN v.16.0 28/10/2004 19:38:20 6144
D1K.BIN v.312.9 30/05/2008 19:31:16 1024
D1C4F3.BIN v.312.9 30/05/2008 19:31:16 100352
D1C5F3.BIN v.312.9 30/05/2008 19:31:16 100352
D2K.BIN v.312.9 30/05/2008 19:31:16 1024
D2C4F3.BIN v.312.9 30/05/2008 19:31:16 102400
D2C4F6.BIN v.312.9 30/05/2008 19:31:16 102400
D8K.BIN v.312.9 30/05/2008 19:31:16 1024
D8C2F1.BIN v.312.9 30/05/2008 19:31:16 91136
D8C2F2.BIN v.312.9 30/05/2008 19:31:16 94208
D8C2F3.BIN v.312.9 30/05/2008 19:31:16 96256
HFC2B4.BIN v.21.0 30/07/2009 10:57:22 16384
HFC2E4.BIN v.21.0 30/07/2009 10:57:22 16384
HFC2B8.BIN v.21.0 30/07/2009 10:57:22 16384

173
Draft Command language Draft

HFC2E8.BIN v.21.0 30/07/2009 10:57:22 16384

HFC3E4.BIN v.48.0 13/08/2009 20:53:22 86016
HFC3E8.BIN v.48.0 13/08/2009 20:53:22 87040
QPRI2B.BIN v.5.0 29/12/2004 16:00:34 17408
QPRI2E.BIN v.6.0 03/03/2005 20:44:34 17408
CTIHA2.BIN v.8.0 29/06/2005 11:33:42 18432
D64A.BIN v.31.10 11/02/2010 14:32:50 68608
D64V.BIN v.6.7 11/05/2010 21:51:16 138240
QPRIX.BIN v.24.0 13/08/2009 20:53:22 251904
OCTASIC.BIN v.16.0 18/06/2008 20:31:40 175104
STH330-P.BIN v.30.12 24/02/2005 21:25:46 388096
STHUSB-I.BIN ....... .......... ........ .......... Not found
SL-IT.BIN v.1.0 28/10/2004 19:38:20 1024
SRVSSL.CER ....... 28/10/2004 19:38:20 820
CLISSL.CER ....... 28/10/2004 19:38:20 820
SRVSSL.KEY ....... 28/10/2004 19:38:20 981
CLISSL.KEY ....... 28/10/2004 19:38:20 969

Other system relevant files:

File Version Date Time Size Note

-------------------------------------------------------------------------------
C:\APP\CTI\ADDRBOOK\ADDRBOOK.DAT
v.1.0 03/11/2010 12:12:32 140066
C:\APP\CTI\LCS\LCSTABLE.DAT
....... .......... ........ .......... Not found
C:\APP\DHCP\DHCP.BND
v.1.0 30/11/2010 15:42:58 25600

Other files in 'C:\7-0-2':

File Date Time Size Note

-------------------------------------------------------------------------------
TRACE.CPX 30/11/2010 16:15:22 4829184

Tip
The automatic tracer saving feature can be activated, if the parameter TSAVE, in general system block, is set
to YES. If the CTISYS port is traced and a FRMWR (Firmware warning) event occurs, all drivers which are
part of CTISYS (CTIDISA, CTIIAX, CTISIP, CTIH323, CTIGKC) autosave the trace. Up to 5 traces are
kept on disk, subsequent traces causes the older to be deleted. Each trace stores up to 900 kbytes before the
event, and up to 100 kbytes or 2 minutes after the event. Also system and debug log are saved in addition to
trace.

[18:01:34] ABILIS_CPX:d g

Conf.Value Act.Value Description

------------------------------------------------------------------------------
tact: NO NO Automatic TRACE activation at start-up [NO, YES]
TSAVE: YES YES Automatic TRACE saving [NO, YES]
sound: ON ON Alarm sound enable/disable [OFF, ON]
wdg-use: YES YES Enable/disable Watchdog usage [NO, YES]
wdg: - MFIDE2 Front Panel/WatchDog interface type <Read Only>
------------------------------------------------------------------------------
DBGF: ALL
CONTACT:
SYSNAME:
LOCATION:
SYSUPTIME: 5 days 17:41:45 (Monday 03/12/2007 03:24:12) <Read Only>
SYSRBTIME: # (System Reboot time not set)
DATE&TIME: Saturday 08/12/2007 21:05:57 (GMT+1.00) <Read Only>
TIMEZONE: CET - Central Europe (Rome, Paris, Berlin, Prague, Brussels)

174
Draft Command language Draft

5.17. DEBUG commands

Debug commands show advanced diagnostic about Abilis CPX system and resources. These type of commands need
administrator or super user rights.

Note
Shown information is strictly technical and meaningless for the user; Abilis CPX technicians could need it
for detecting and solving eventual problems.

By typing the following command, it is possible to display the syntax.

[12:43:19] ABILIS_CPX:debug ?

BM Display Boot Manager configuration file

CPXRUN Display CPX Run configuration file
FILE File system information and statistics
IRQ Interrupts information and statistics
MEM Memory information and statistics
PCIDEV Display PCI service debug information
PO: CPX port number [0..999]
RES: Resource identifier 'type-n', where 'n' can be [1..999]
SIMULATE Simulate an event for debugging purposes
TASK Tasks information and statistics
USBDEV Display USB service debug information
WDGMEM Watchdog memory

5.17.1. DEBUG RES

This command shows debugging information about the specified resource. By typing the following command, it is possible
to display the command syntax.

[12:43:19] ABILIS_CPX:debug res: ?

DEBUG RES:val [par:val] Display debug information of a resource

Additional parameters:

LAYER: Select resource lower layer [L2, LINK, LAN, IP, IPT, PPP, PPPOE]
<Optional, only if PROT: not specified>
PROT: Select protocol layer [LAPB, MLM, ML, IPLAN, PLINKE, PPP, POECLI]
<Optional, only if LAYER: not specified>
SIZE: Select debug buffer size [7..63 Kbytes] <Optional>
LSN: Lsn value [0..65534(dec) or 0000..0FFFE(hex), A] <Optional>
CMD: Command string. Strings holding spaces must be written
between quotation marks (e.g. CMD:"str1 str2 ...") <Optional>

Data are stored in a 6 KB size buffer. Depending on the resource type, where the command is executed on, this buffer could
not be enough and at the end of the visualization the following message will be displayed “INCOMPLETE INFORMATION:
BUFFER SIZE TOO SHORT”. By using the option SIZE, the user can eventually increase the maximum buffer size used by
the command. The indicated value (in KB) must be in the interval [7 - 63].

By using the options LSN and CMD it is possible to select the type of debugging information to be displayed.

For example, to show debugging information of an ADSL line, type the command debug res:ip-xx prot:ppp, where xx
is the number of the ip resource associated to the ADSL line. With the options LSN, it is possible to select the type of
debugging information to be displayed; if it is set to 0, it will be displayed the command help.

[12:43:19] ABILIS_CPX:debug res:ip-5 prot:ppp

RES:Ip-5 - IP over PPP (PPP) -------------------------------------------------

ADSL-xx.xxx.xxx.xxx/32
BufferLength:384 Date/Time:30/11/2010 16:23:27 TraceTime:67955961

175
Draft Command language Draft

Usage:
LSN:0 == This help
LSN:1 == Complete debug
LSN:2 == Upper/Lower NCB status
LSN:3 == Layer states
LSN:4 == Link status
LSN:5 == Negotiated options
LSN:6 == Echo information
LSN:7 == RADIUS information
LSN:10 == Show CALL log
LSN:11 == Show PPP Negotiation log
LSN:20 == Clear CALL log
LSN:21 == Clear PPP Negotiation log

[16:23:27] ABILIS_CPX:debug res:ip-5 prot:ppp lsn:10

RES:Ip-5 - IP over PPP (PPP) -------------------------------------------------

ADSL-xx.xxx.xxx.xxx/32
BufferLength:377 Date/Time:30/11/2010 16:23:44 TraceTime:67973497

29.11.10 21:30:51 *********************

29.11.10 21:30:51 * * * * START * * * *
29.11.10 21:30:51 Calling PLink
29.11.10 21:30:51 Calling PLink - succeeded
30.11.10 13:06:10 Hanging-up PLink - succeeded
30.11.10 13:06:10 *********************
30.11.10 13:06:10 * * * * START * * * *
30.11.10 13:06:10 Calling PLink
30.11.10 13:06:10 Calling PLink - succeeded

5.17.2. DEBUG SIMULATE EVENT

The command DEBUG SIMULATE EVENT:val simulates an event for debugging purposes. Use the following command
to show all possible events:

[14:45:58] ABILIS_CPX:debug simulate event: ?

DEBUG SIMULATE EVENT:val Simulate an event for debugging purposes

Possible events:

XCP Structured exception

WDL WDLIVE1 event. It executes a never ending loop without task
switching.
WDGRESET WDG Reset. It resets WDG but doesn't make SW reset of the PC.
BLOCKAGE Complete lock. It disables ALL the interrupts and executes a never
ending loop without task switching.
TSAVE Automatic TRACE saving request (trace stop-save-start)
HOVR Heap overflow (bad allocation exception)

5.17.2.1. DEBUG SIMULATE EVENT:XCP

This command simulates the structured exception:

[10:47:52] ABILIS_CPX:debug simulate event:xcp

YOU ASKED TO SIMULATE THE 'STRUCTURED EXCEPTION' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH STRUCTURED EXCEPTION EVENT SIMULATION...

The log shows the following information:

176
Draft Command language Draft

...
12/05/2011 10:48:15 [00221] I: DEBUG SIMULATE EXCEPTION
12/05/2011 10:48:16 [00029] E: PO1
12/05/2011 10:48:16 [00032] AUTO WARM START
12/05/2011 10:48:52 [00103] -------------------- NEW RUN --------------------
...

5.17.2.2. DEBUG SIMULATE EVENT:XCP

This command simulates the WDLIVE1 event:

[10:50:16] ABILIS_CPX:debug simulate event:wdl

YOU ASKED TO SIMULATE THE 'WDLIVE1' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH WDLIVE1 EVENT SIMULATION...

The log shows the following information:

...
12/05/2011 10:52:26 [00222] I: DEBUG SIMULATE WDLIVE-1
12/05/2011 10:53:19 [00103] -------------------- NEW RUN --------------------
...

5.17.2.3. DEBUG SIMULATE EVENT:WDGRESET

This command resets WDG but doesn't make Abilis SW reset. It is useful to verify if the watchdog (MFIDE/MFPCI/
MFLPC) is really able to make HW reset of the Abilis CPX, and thus if the reset cable is properly connected.

[14:52:17] ABILIS_CPX:debug simulate event:wdgreset

YOU ASKED TO SIMULATE THE 'WDG RESET' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH WDG RESET EVENT SIMULATION...

The log shows the following information after using this command:

[14:53:25] ABILIS_CPX:d l

Current Local Time: Wednesday 11/05/2011 14:53:26 (UTC+2.00)

...
11/05/2011 14:39:10 [00092] I: Pv-6 PLink:d2 SLink:ln
11/05/2011 14:39:28 [00092] I: Pv-5 PLink:RD SLink:ln
11/05/2011 14:39:28 [00092] I: Pv-6 PLink:RD SLink:ln
11/05/2011 14:52:23 [00394] I: DEBUG SIMULATE WDG RESET
11/05/2011 14:53:00 [00103] -------------------- NEW RUN --------------------
11/05/2011 14:53:02 [00362] I: WATCHDOG MFIDE3 FW Rev. 11
11/05/2011 14:53:02 [00163] I: SYSTEM RESET
...

If the reset does not take place, the only way to restart abilis is using the warm start command:

[06:04:07] ABILIS_CPX:debug simulate event:wdgreset

YOU ASKED TO SIMULATE THE 'WDG RESET' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH WDG RESET EVENT SIMULATION...

WARNING: WDG RESET HAD NOT EFFECT.

******************************************************************************

177
Draft Command language Draft

ATTENTION!
THE SYSTEM MUST BE RESTARTED WITH 'WARM START' COMMAND.
ALLOWED COMMANDs: 'CLOSE', 'EXIT', 'WARM START'.
******************************************************************************

5.17.2.4. DEBUG SIMULATE EVENT:BLOCKAGE

This command simulates the system blockage event:

[10:53:45] ABILIS_CPX:debug simulate event:blockage

YOU ASKED TO SIMULATE THE 'SYSTEM BLOCKAGE' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH SYSTEM BLOCKAGE EVENT SIMULATION...

The log shows the following information:

...
12/05/2011 10:54:50 [00365] I: DEBUG SIMULATE BLOCKAGE
12/05/2011 10:55:53 [00103] -------------------- NEW RUN --------------------
...

5.17.2.5. DEBUG SIMULATE EVENT:TSAVE

This command simulates the trace autosave event (trace stop-save-start):

[11:02:31] ABILIS_CPX:debug simulate event:tsave

YOU ASKED TO SIMULATE THE 'TRACE AUTO SAVE' EVENT.

THIS WILL ACTIVATE CURRENT TRACE AUTOMATIC SAVING (WITHIN 2 min.),
PROCEED (N/Y)?y

PROCEEDING WITH TRACE AUTO SAVE EVENT SIMULATION...

COMMAND EXECUTED

The log shows the following information:

...
12/05/2011 11:02:39 [00284] I: DEBUG SIMULATE TRACE AUTO SAVE
12/05/2011 11:04:39 [00275] I: TRACE AUTO SAVE: STARTED (TOUT)
12/05/2011 11:04:39 [00279] I: TRACE AUTO SAVE: TRACE STOPPED
12/05/2011 11:04:39 [00280] I: TRACE AUTO SAVE: TRACE SAVED
...

5.17.2.6. DEBUG SIMULATE EVENT:HOPV

This command simulates the heap overflow event:

[11:03:49] ABILIS_CPX:debug simulate event:hovr

YOU ASKED TO SIMULATE THE 'HEAP OVERFLOW' EVENT.

THIS WILL CAUSE THE SYSTEM TO BE RESTARTED, PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH HEAP OVERFLOW EVENT SIMULATION...

The log shows the following information:

...
12/05/2011 11:06:44 [00079] I: DEBUG SIMULATE HEAP OVERFLOW
12/05/2011 11:06:44 [00030] E: P02
12/05/2011 11:06:44 [00135] MEMORY SUMMARY:
12/05/2011 11:06:44 [00136] TOT: 134,217,728
12/05/2011 11:06:44 [00137] FREE:59,870,240

178
Draft Command language Draft

12/05/2011 11:06:44 [00138] HU: 59,808,960

12/05/2011 11:06:44 [00139] HLFB:59,870,080
12/05/2011 11:06:44 [00140] HLUB: 8,388,608
12/05/2011 11:06:44 [00032] AUTO WARM START
12/05/2011 11:07:20 [00103] -------------------- NEW RUN --------------------
...

179
Draft Draft

Chapter 6. Licencing
Luigi Demuro

Table of Contents
6.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.1. ABILIS ID and the class of product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.1.2. Managing licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

6.1. Introduction
The introduction of licencing has been done by taking into consideration the products already purchased by our customer so
that they can upgrade their products with the latest release without loosing any functionality present up to release 6.5.x.

Note
This is only partially valid for Mini-Abilis equipped with FPanel watchdog that does not provide the
ABILIS-ID, where some functionalities will not be available after the upgrade to 7.0.

6.1.1. ABILIS ID and the class of product

Each Abilis CPX has unique identifier which is visible on the serial number label.

It's easy to retrieve this identifier from a remote Abilis using the commands d i or d g. The identifier is named ABILIS-ID.

[16:02:36] ABILIS_CPX:d i

Abilis CPX - Ver. 7.0.0/STD - 24/09/2010 - Build 3357.0 - 24/09/2010

(c) 1994/2010 - Abilis

ABILIS-ID: 2001

Free/Total Memory: 87,281,744/268,304,384 Largest Block: 87,266,672

Free/Used/Total HD/CF space (in KB): 66,474/55,876/122,350
...

[16:04:14] ABILIS_CPX:d g

...
ABILIS-ID: 2001 <Read Only>

The ABILIS-ID parameter is used to know the class of the product, which is used to select which features are available out-
of-the-box.

Other features may be added purchasing additional licences and installing them using the steps in the chapter Section 6.1.2,
“Managing licences”.

The identification of the class is easy:

Table 6.1. Abilis ID and class of products

Number of digits of ABILIS ID Class of product

5 or less than 5 0 (legacy production)
6 identified by the first, leftmost, number

180
Draft Licencing Draft

Examples:

• ABILIS-ID: 2001 or ABILIS-ID: 50002 are of class 0

• ABILIS-ID: 300049 has class 3, ABILIS-ID: 100031 has class 1

Note
If there's no ABILIS-ID, it means that Abilis is not equipped with MFIDE device and so it belongs to FP
class.

Below there is a table showing the Abilis CPX product classes.

Table 6.2. Class of products

Class Product
FP Former Mini-Abilis with FPANEL
0 Former Abilis Base-x with MFIDE2/MFIDE3
1 New Micro-Abilis (with BRI4-POTS4 board and MFLPC)
2 New Nano-Abilis (with MiniBRI1 board and MFLPC)
3 New Abilis Base-J with MFIDE3
4 New Mini-Abilis with MFIDE3
5 New Compact-Abilis (with ETH3-BRI4-POTS8 and MFPCI)
6 New Abilis Base-K with MFIDE3

Here's a table showing Classes and licenced features.

181
 number
service
SOFTPBXSoft- YES YES YES YES
Draft Licencing Draft
PBX
service
(OPC,
Table 6.3.Address
Licenced features
Book,
Click&Call, ...)
GPS GPS YES YES
resources
ACNT Accounting YES YES YES YES
service
TRFA Traffic YES YES YES YES YES
Analyzer
OSPF Open YES YES
Shortest
Path
First
protocol
FTPSRV FTP YES YES YES YES YES YES YES YES YES YES
server
SMTP SMTP YES YES YES YES YES
resource
POP3 POP3 YES YES YES YES YES
resource
RADIUS RADIUS YES YES YES YES
resource
VRRP VRRP YES YES
resource
POEAC PPP YES YES YES YES
Over
Ethernet
Access
Concentrator
ARCHIVEArchive YES YES YES YES
resource
CTIDISA CTI YES YES YES YES YES
DISA
service
CTIIAX CTI IAX YES YES YES YES YES YES YES YES YES YES
service
CTISIP CTI SIP YES YES YES YES YES YES YES YES YES YES
service
CTISMS CTI YES YES YES YES
SMS
service
AIPT Number 4 250 2 2 4 2 4 250 32 32
of AIPT
(Abilis
tunnel)
resources
[0,
1..250]
IKEHOSTS
Number 2 128 1 1 2 1 1 128 4 4
of IKE
hosts [0,
1..128]
(IPSEC/
IKE
resources)

182
Draft Licencing Draft

6.1.2. Managing licences

A licence is a text file whose name contains the ABILIS ID (e.g. LIC1-0000002001.TXT). It can be also a mail with the text
of the licence file.

There are three way to install a license:

• Upload the text file in the directory C:\LICENCE of the Abilis CPX compact flash using FTP (please refer to FTP
protocol1)

• Upload the text file in the directory C:\LICENCE of the Abilis CPX compact flash using the command licence put for
XMODEM or the command licence put z for ZMODEM (please refer to chapter put command2)

• Copy and paste the licence text using the command licence set

[19:49:27] ABILIS_CPX:licence SET

Please enter the licence data and terminate with CTRL+Z + ENTER
(type CTRL+C + ENTER to abort):

Tcvk+otc1AmdPyqOXloJj0oZ3LXR/dkJrv1rQl0YyA6lG6by5rvyqdOYTxDoi1i8
ul2pW0BE9sOG1ansjjDAqInA0AoNZ19FgkzJAAi5StsLOsYze/OJZ13Bh+J9Zj/9
M/lCIepQJY4jvcALWddkVlY1O0I4xfCzOdNyTnODhsVl9wpl5fibZvaLnG+c5Jnt
prsOHu+xhfnnoBXyTjkt0SHvg0druqg39SVzKtOxd4YGSO646NfhgXrYLcjVPgPl
eRFmluzTTZtUQpQGYFmh5QWel6cyvVj9Ka5MxrSoStiOdeAnte71D8N6CluJxPYY
iS1KHVzl4zGfp2ADXE778Q==

RECEIVED LICENCE CHECK AND SAVING IN PROGRESS... CHECK PASSED

RECEIVED LICENCE SAVED

[19:49:48] ABILIS_CPX:

Managing licences is easy trough the Abilis CP using the following commands:

[19:49:48] ABILIS_CPX:licence ?

COMPARE Compare ACTIVE licence and STORED licence

DISPLAY Display licences or permissions
GET Download ACTIVE licence or STORED licence file
PUT Upload STORED licence file
SET Enter STORED licence value

[19:54:04] ABILIS_CPX:licence compare ?

LICENCE COMPARE Compare ACTIVE and STORED licences

[19:54:11] ABILIS_CPX:licence display ?

LICENCE DISPLAY Display ACTIVE licence and compare it

with the STORED licence
LICENCE DISPLAY ACTIVE Display ACTIVE licence
LICENCE DISPLAY FILE Display STORED licence
LICENCE DISPLAY PERMISSIONS Display ACTIVE permissions and compare
them with the STORED ones
LICENCE DISPLAY PERMISSIONS ACTIVE Display ACTIVE permissions
LICENCE DISPLAY PERMISSIONS CLASS Display permissions pertaining to Abilis
Class Id.
LICENCE DISPLAY PERMISSIONS FILE Display STORED permissions

[19:54:22] ABILIS_CPX:licence get ?

ACTIVE Download ACTIVE licence

FILE Download STORED licence file

183
Draft Licencing Draft

[19:54:35] ABILIS_CPX:licence set ?

LICENCE SET Receive licence file from the keyboard

You can display the enabled features by the current licence using the command:

[19:55:12] ABILIS_CPX:licence display permissions

ACTIVE PERMISSIONS:

-----------|-----------|-------------------------------------------------------
Name |Value |Description
-----------|-----------|-------------------------------------------------------
ABILISID |2001 |Abilis CPX serial number
EXPIRY |NONE |Licence expiration date YYYY-MM-DD
DATACOMP |YES |Data compression service
IPLB |YES |IP Load Balancing service
LCS |YES |Last Calling number service
MULTILINK |YES |Resources over Multi-Links
SOFTPBX |YES |Soft-PBX service (OPC, Address Book, Click&Call, ...)
VMX |YES |VMX system
GPS |YES |GPS resources
ACNT |YES |Accounting service
TRFA |YES |Traffic Analyzer
OSPF |YES |Open Shortest Path First protocol
FTPSRV |YES |FTP server
SMTP |YES |SMTP resource
POP3 |YES |POP3 resource
RADIUS |YES |RADIUS resource
VRRP |YES |VRRP resource
POEAC |YES |PPP Over Ethernet Access Concentrator
ARCHIVE |YES |Archive resource
CTIDISA |YES |CTI DISA service
CTIIAX |YES |CTI IAX service
CTISIP |YES |CTI SIP service
CTISMS |YES |CTI SMS service
AIPT |250 |Number of AIPT (Abilis tunnel) resources [0, 1..250]
IKEHOSTS |128 |Number of IKE hosts [0, 1..128] (IPSEC/IKE resources)

LICENCE STORED IN FILE EQUALS THE ACTIVE ONE

184
Draft Draft

Chapter 7. Logging functionalities

Marco Bellesia
Luigi Demuro

Table of Contents
7.1. System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.2. Debug Log (Events Log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7.2.1. Displaying Log Debug saved on disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.2.2. Displaying ERR codes (D CODE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
7.3. Exceptions Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
7.4. LOG parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

7.1. System Log

Abilis CPX System Log file allows to register all the events pertinent to the global working mode.

The System Log is saved on the HD/CF in the file CPX.LOG (fixed size is 50 Kbytes) and updated every time
that an event to save occurs. New events are stored and the oldest ones are progressively deleted.

The System Log can be displayed in a running Abilis using the following command. The command d l ? shows the syntax.

[18:01:34] ABILIS_CPX:d l

Current Local Time: Friday 14/01/2011 09:49:59 (UTC+1.00)

14/01/2011 9:49:05 [00257] I: SYSTEM LOG CLEARED

14/01/2011 9:49:11 [00033] WARM START
14/01/2011 9:49:38 [00103] -------------------- NEW RUN --------------------
14/01/2011 9:49:40 [00362] I: WATCHDOG MFIDE3 FW Rev. 11
14/01/2011 9:49:40 [00163] I: SYSTEM RESET
14/01/2011 9:49:40 [00366] W: LICENCE, FILE MISSING
14/01/2011 9:49:40 [00248] I: USB PCI7/2 UHCI DE00 9
14/01/2011 9:49:40 [00150] W: MISSING STHUSB-I.BIN
14/01/2011 9:49:42 [00242] I: BRI4-1 DSP:0 DWNL OK
14/01/2011 9:49:46 [00291] I: DSP test start
14/01/2011 9:49:46 [00292] I: DSP test end
14/01/2011 9:49:46 [00286] I: CTIR ENABLED
14/01/2011 9:49:47 [00055] SYSTEM STARTED
14/01/2011 9:49:47 [00104] AUTO SAVE IN PROGRESS
14/01/2011 9:49:47 [00091] I: Pad-1 L1-ST:dn DCD:dn DTR:UP
14/01/2011 9:49:47 [00345] I: Dhcp-1 ST:in
14/01/2011 9:49:47 [00259] I: PoeAc-1 ST:ee
14/01/2011 9:49:47 [00090] I: X25-999 Layer3:down
14/01/2011 9:49:47 [00089] I: X25-999 Layer2:cg
14/01/2011 9:49:47 [00092] I: X25-999 PLink:ln SLink:RD
14/01/2011 9:49:47 [00092] I: Ip-3 PLink:d1 SLink:RD
14/01/2011 9:49:47 [00092] I: Pv-1 PLink:d1 SLink:ln
14/01/2011 9:49:47 [00092] I: Pv-2 PLink:d1 SLink:ln
14/01/2011 9:49:47 [00092] I: Ip-4 PLink:d1 SLink:ln
14/01/2011 9:49:47 [00230] I: Adsl-1 ST:DOWN
14/01/2011 9:49:47 [00346] I: DhcpC-1 ST:RD
14/01/2011 9:49:47 [00092] I: Pv-5 PLink:d1 SLink:ln
14/01/2011 9:49:47 [00092] I: Pv-6 PLink:d1 SLink:ln
14/01/2011 9:49:47 [00092] I: Ip-8 PLink:d1 SLink:ln

185
Draft Logging functionalities Draft

14/01/2011 9:49:47 [00092] I: Ip-9 PLink:d1 SLink:ln

14/01/2011 9:49:48 [00107] AUTO SAVE OK
14/01/2011 9:49:55 [00092] I: Ip-3 PLink:d2 SLink:RD
14/01/2011 9:49:55 [00092] I: Ip-4 PLink:d2 Sink:ln
14/01/2011 9:49:55 [00092] I: Pv-5 PLink:d2 SLink:ln
14/01/2011 9:49:55 [00092] I: Pv-6 PLink:d2 SLink:ln
14/01/2011 9:49:55 [00092] I: Ip-9 PLink:d2 SLink:ln

Tip
Interesting chapters: Section 60.1, “System Log messages”.

System Log events can be simultaneously sent to the current Control Port session typing the following command.

[18:01:34] ABILIS_CPX:start l

Current Local Time: Friday 14/01/2011 09:53:07 (UTC+1.00)

Start System Log content real-time logging (Type CTRL+C + ENTER to stop):

14/01/2011 9:53:20 [00092] I: Pv-5 PLink:RD SLink:ln

14/01/2011 9:53:20 [00092] I: Pv-6 PLink:RD SLink:ln

The System Log content can be cleared using the command c l.

Tip
The command allows to display the log file of another version:

[09:22:13] ABILIS_CPX:_d l ?

D L [ver] [dd/mm/yyyy] [hh:mm:ss] Display System Log

<ver> String corresponding to a version directory in <Optional>

the form [x.y.z or x-y-z or y.z or y-z or y].
(E.g.: 5.3.1 or 6-1-0 or 2189).
dd/mm/yyyy Selected date <Optional>
hh:mm:ss Selected time <Optional>

7.2. Debug Log (Events Log)

Debug log stores events pertinent to connection's opening/closing and to port's state changes.

Information provided by Debug log can be sent to technical support using email address [email protected].

Events registered in the Debug Log are grouped in the following classes:

• DIAG: Events related to port diagnostic and status.

• COR: Events related to the Connection Oriented Router.

• MLM: Events related to the Multi Link Manager driver.

• CTIR: Events related to the CTI Router.

• PPP: Events related to the Point-to-Point Protocol driver.

• ML: Events related to the Multi Links driver.

• Q931: Events related to the Q931 driver.

Events are stored in buffer of fixed length that is kept in memory. The buffer maintains the more recent events, eliminating
the oldest.

1
mailto:[email protected]

186
Draft Logging functionalities Draft

Note
Usually the Debug Log can store events for few days; however this time interval depends on the number and
the type of events to record, which can also change from customer to customer.

The Debug Log content is transferred from the memory to the file CPX.DBG in two cases: in correspondence to the user
request.

• every time the Abilis CPX is restarted;

• using the save debug command.

Note
The command is available also from MFIDE panel.

Debug log can be visualized with the following.

[18:01:34] ABILIS_CPX:d ldm

Current Local Time: Friday 14/01/2011 10:00:55 (UTC+1.00)

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
140111 115547 CtiCl-18 3225 E-CallRx CH:61 BC:3.1kHz CD:425 CG:706
140111 115547 CtiCl-18 3225 E-Route Match PR:48
140111 115547 CtiCl-11 3225 E-CallTx BC:3.1kHz TY:CtoC CD:425 CG:706
140111 115547 CtiCl-18 3225 E-ProgressTx
140111 115547 CtiCl-11 3225 E-ProgressRx
140111 115547 CtiCl-18 3225 E-ProgressTx
140111 115547 CtiCl-11 3225 E-CallFailRx CH:68 CAUSE:80 91
140111 115547 CtiCl-11 3225 E-DiscConfTx CH:68
140111 115547 CtiCl-18 3225 E-Route Fail PR:48 , search next CAUSE:80 91
140111 115547 CtiCl-18 3225 E-No Route
140111 115547 CtiCl-18 3225 E-NumComplete CDI:425 CDO:425
140111 115547 CtiCl-18 3225 E-DiscTx CH:61 CAUSE:80 91
140111 115558 CtiCl-18 3226 E-DialRx CH:63 BC:3.1kHz CD:5 CG:706
140111 115558 CtiP-128 3227 E-DialRx CH:1 BC:Speech CG:62
140111 115558 CtiCl-18 3226 E-CallRx CH:63 BC:3.1kHz CD:553 CG:706
140111 115558 CtiCl-18 3226 E-Route Match PR:32
140111 115558 CtiP-119 3226 E-CallTx BC:3.1kHz TY:CtoV CD:553 CG:706
140111 115558 CtiP-119 3226 E-AlertRx CH:1
140111 115558 CtiCl-18 3226 E-NumComplete CDI:553 CDO:553
140111 115558 CtiCl-18 3226 E-AlertTx CH:63
140111 115559 CtiP-128 3227 E-CallRx CH:1 BC:Speech CD:65 CG:62
140111 115559 CtiP-128 3227 E-Route Match PR:75
140111 115559 CtiP-131 3227 E-CallTx BC:Speech TY:TR CD:65 CG:62
140111 115559 CtiP-131 3227 E-AlertRx CH:1
140111 115559 CtiP-128 3227 E-NumComplete CDI:65 CDO:65
140111 115559 CtiP-128 3227 E-AlertTx CH:1 PI:81 88
140111 115601 CtiP-119 3226 E-ConnRx CH:1
140111 115601 CtiCl-18 3226 E-ConnTx CH:63
140111 115601 CtiP-131 3227 E-ConnRx CH:1
140111 115601 CtiP-128 3227 E-ConnTx CH:1
140111 115632 CtiP-128 3227 E-DiscRx CH:1 CAUSE:80 90
140111 115632 CtiP-128 3227 E-DiscConfTx CH:0
140111 115632 CtiP-131 3227 E-DiscTx CH:1 CAUSE:80 90
140111 115704 CtiP-116 3228 E-DialRx CH:1 BC:Speech CG:15
140111 115706 CtiP-116 3228 E-CallRx CH:1 BC:Speech CD:0014 CG:15
140111 115706 CtiP-116 3228 E-Route Match PR:92
140111 115706 CtiCl-6 3228 E-CallTx BC:Speech TY:VtoC CD:014
CG:0289038015 SCD:15
140111 115708 CtiP-116 3228 E-NumComplete CDI:00142433114 CDO:0142433114

187
Draft Logging functionalities Draft

140111 115708 CtiCl-6 3228 E-ProgressRx

140111 115715 CtiP-119 3226 E-DiscRx CH:1 CAUSE:80 90
140111 115715 CtiCl-18 3226 E-DiscTx CH:63 CAUSE:80 90
140111 115715 CtiP-119 3226 E-DiscConfTx CH:0
140111 115715 CtiCl-6 3228 E-CallFailRx CH:67 CAUSE:80 91
140111 115715 CtiP-116 3228 E-Route Fail PR:92 CAUSE:80 91
140111 115715 CtiCl-6 3228 E-DiscConfTx CH:67
140111 115715 CtiP-116 3228 E-DiscTx CH:1 CAUSE:80 91
140111 115723 CtiP-116 3229 E-DialRx CH:1 BC:Speech CG:15
140111 115725 CtiP-116 3229 E-CallRx CH:1 BC:Speech CD:0014 CG:15
140111 115725 CtiP-116 3229 E-Route Match PR:92
140111 115725 CtiCl-6 3229 E-CallTx BC:Speech TY:VtoC CD:014
CG:0289038015 SCD:15
140111 115728 CtiP-116 3229 E-NumComplete CDI:00142433114 CDO:0142433114
140111 115728 CtiCl-6 3229 E-ProgressRx
140111 115735 CtiCl-6 3229 E-CallFailRx CH:69 CAUSE:80 91
140111 115735 CtiP-116 3229 E-Route Fail PR:92 CAUSE:80 91
140111 115735 CtiCl-6 3229 E-DiscConfTx CH:69
140111 115735 CtiP-116 3229 E-DiscTx CH:1 CAUSE:80 91

The following command displays the command syntax:.

[15:43:28] ABILIS_CPX:d ldme ?

D LDME [dd/mm/yyyy] [hh:mm:ss] Display Debug Log in Memory decoding ISDN/X.25

[E:val] [RES:type-n,...] codes
[SES:val]

dd/mm/yyyy Selected date <Optional>

hh:mm:ss Selected time <Optional>
E: Event filter [DIAG, COR, Q931, CTIR, SMS, PPP, MLM, <Optional>
ML, ALL]. Filters can be joined using "," operator
(e.g.: E:COR,MLM,...).
RES: Resource list (max. 50 values 'type-n' or <Optional>
'CtiP-n' or 'CtiCl-n', where 'n' [1..999])
SES: Session filter [A, 0..65535] <Optional>

Tip
Refer to Chapter 61, Disconnection codes to know more about the list of ISDN and X.25 disconnection
codes.

The d ldme command displays the information in extended mode (i.e. the ISDN disconnection causes are decoded).

[18:01:34] ABILIS_CPX:d ldme

140111 115547 CtiCl-18 3225 E-CallRx CH:61 BC:3.1kHz CD:425 CG:706

140111 115547 CtiCl-18 3225 E-Route Match PR:48
140111 115547 CtiCl-11 3225 E-CallTx BC:3.1kHz TY:CtoC CD:425 CG:706
140111 115547 CtiCl-18 3225 E-ProgressTx
140111 115547 CtiCl-11 3225 E-ProgressRx
140111 115547 CtiCl-18 3225 E-ProgressTx
140111 115547 CtiCl-11 3225 E-CallFailRx CH:68 CAUSE:80 91 (U, User busy)
140111 115547 CtiCl-11 3225 E-DiscConfTx CH:68
140111 115547 CtiCl-18 3225 E-Route Fail PR:48 , search next CAUSE:80 91
(U, User busy)
140111 115547 CtiCl-18 3225 E-No Route
140111 115547 CtiCl-18 3225 E-NumComplete CDI:425 CDO:425
140111 115547 CtiCl-18 3225 E-DiscTx CH:61 CAUSE:80 91 (U, User busy)
140111 115558 CtiCl-18 3226 E-DialRx CH:63 BC:3.1kHz CD:5 CG:706
140111 115558 CtiP-128 3227 E-DialRx CH:1 BC:Speech CG:62
140111 115558 CtiCl-18 3226 E-CallRx CH:63 BC:3.1kHz CD:553 CG:706
140111 115558 CtiCl-18 3226 E-Route Match PR:32

188
Draft Logging functionalities Draft

140111 115558 CtiP-119 3226 E-CallTx BC:3.1kHz TY:CtoV CD:553 CG:706

140111 115558 CtiP-119 3226 E-AlertRx CH:1
140111 115558 CtiCl-18 3226 E-NumComplete CDI:553 CDO:553
140111 115558 CtiCl-18 3226 E-AlertTx CH:63
140111 115559 CtiP-128 3227 E-CallRx CH:1 BC:Speech CD:65 CG:62
140111 115559 CtiP-128 3227 E-Route Match PR:75
140111 115559 CtiP-131 3227 E-CallTx BC:Speech TY:TR CD:65 CG:62
140111 115559 CtiP-131 3227 E-AlertRx CH:1
140111 115559 CtiP-128 3227 E-NumComplete CDI:65 CDO:65
140111 115559 CtiP-128 3227 E-AlertTx CH:1 PI:81 88
140111 115601 CtiP-119 3226 E-ConnRx CH:1
140111 115601 CtiCl-18 3226 E-ConnTx CH:63
140111 115601 CtiP-131 3227 E-ConnRx CH:1
140111 115601 CtiP-128 3227 E-ConnTx CH:1
140111 115632 CtiP-128 3227 E-DiscRx CH:1 CAUSE:80 90 (U, Normal call
clearing)
140111 115632 CtiP-128 3227 E-DiscConfTx CH:0
140111 115632 CtiP-131 3227 E-DiscTx CH:1 CAUSE:80 90 (U, Normal call
clearing)
140111 115704 CtiP-116 3228 E-DialRx CH:1 BC:Speech CG:15
140111 115706 CtiP-116 3228 E-CallRx CH:1 BC:Speech CD:0014 CG:15
140111 115706 CtiP-116 3228 E-Route Match PR:92
140111 115706 CtiCl-6 3228 E-CallTx BC:Speech TY:VtoC CD:014
CG:0289038015 SCD:15
140111 115708 CtiP-116 3228 E-NumComplete CDI:00142433114 CDO:0142433114
140111 115708 CtiCl-6 3228 E-ProgressRx
140111 115715 CtiP-119 3226 E-DiscRx CH:1 CAUSE:80 90 (U, Normal call
clearing)
140111 115715 CtiCl-18 3226 E-DiscTx CH:63 CAUSE:80 90 (U, Normal
call clearing)
140111 115715 CtiP-119 3226 E-DiscConfTx CH:0
140111 115715 CtiCl-6 3228 E-CallFailRx CH:67 CAUSE:80 91 (U, User busy)
140111 115715 CtiP-116 3228 E-Route Fail PR:92 CAUSE:80 91 (U, User busy)
140111 115715 CtiCl-6 3228 E-DiscConfTx CH:67
140111 115715 CtiP-116 3228 E-DiscTx CH:1 CAUSE:80 91 (U, User busy)
140111 115723 CtiP-116 3229 E-DialRx CH:1 BC:Speech CG:15
140111 115725 CtiP-116 3229 E-CallRx CH:1 BC:Speech CD:0014 CG:15
140111 115725 CtiP-116 3229 E-Route Match PR:92
140111 115725 CtiCl-6 3229 E-CallTx BC:Speech TY:VtoC CD:014
CG:0289038015 SCD:15
140111 115728 CtiP-116 3229 E-NumComplete CDI:00142433114 CDO:0142433114
140111 115728 CtiCl-6 3229 E-ProgressRx
140111 115735 CtiCl-6 3229 E-CallFailRx CH:69 CAUSE:80 91 (U, User busy)
140111 115735 CtiP-116 3229 E-Route Fail PR:92 CAUSE:80 91 (U, User busy)
140111 115735 CtiCl-6 3229 E-DiscConfTx CH:69
140111 115735 CtiP-116 3229 E-DiscTx CH:1 CAUSE:80 91 (U, User busy)

Debug Log can be simultaneously sent to the current Control Port session using start ldm or start ldme commands. Events
are displayed in the same time that they occurs and that they are recorded into the buffer in memory.

[18:01:34] ABILIS_CPX:start ldm

Current Local Time: Friday 14/01/2011 10:03:56 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
140111 100422 CtiSip 4 E-CallRx CH:6 BC:Speech CD:10 CG:12
USER:test3
140111 100422 CtiSip 4 E-Route Match PR:23
140111 100422 CtiSip 4 E-CallTx BC:Speech TY:StoS CD:10 CG:12
140111 100422 CtiSip 4 E-NumComplete CDI:10 CDO:10

189
Draft Logging functionalities Draft

140111 100422 CtiSip 4 E-AlertRx CH:7 USER:test

140111 100422 CtiSip 4 E-AlertTx CH:6
140111 100422 CtiSip 0 E-CallForward RULE:FORK USER:test
140111 100422 CtiSip 5 E-CallRx CH:8 BC:Speech CD:419 CG:12
USER:test
140111 100422 CtiSip 5 E-No Route
140111 100422 CtiSip 5 E-CallFailTx CH:8 CAUSE:81 83
140111 100427 CtiSip 4 E-ConnRx CH:7
140111 100427 CtiSip 4 E-ConnTx CH:6
140111 100431 CtiSip 4 E-DiscRx CH:6 CAUSE:80 9F USER:test3
140111 100431 CtiSip 4 E-DiscConfTx CH:6
140111 100431 CtiSip 4 E-DiscTx CH:7 CAUSE:80 9F USER:test

The Debug Log content can be cleared through the command c ldm.

7.2.1. Displaying Log Debug saved on disk

The command d ldd displays the content of the Debug Log saved on disk with the command save debug.

To display the syntax of the command, type d ldd ?.

[18:01:34] ABILIS_CPX:d ldd ?

D LDD [dd/mm/yyyy] [hh:mm:ss] Display Debug Log on Disk

[E:val] [RES:type-n,...]
[SES:val]

dd/mm/yyyy Selected date <Optional>

hh:mm:ss Selected time <Optional>
E: Event filter [DIAG, COR, Q931, CTIR, SMS, PPP, MLM, <Optional>
ML, ALL]. Filters can be joined using "," operator
(e.g.: E:COR,MLM,...).
RES: Resource list (max. 50 values 'type-n' or <Optional>
'CtiP-n' or 'CtiCl-n', where 'n' [1..999])
SES: Session filter [A, 0..65535] <Optional>

7.2.2. Displaying ERR codes (D CODE)

The following command helps to decode isdn,sms and x25 error codes.

[14:59:16] ABILIS_CPX:d code ?

ISDN ISDN Location/Reason codes

SMS CtiSms error codes
X25 X.25 Cause/Diagnostic codes

Example:

[15:06:32] ABILIS_CPX:d code sms 321

CtiSms ERROR DECODE

Error : 0321 (0x0141) - Invalid Memory Index

Error codes are shown in the debug log and they are automatically decoded:

[18:10:34] ABILIS_CPX:d ldme

...
030511 160843 CtiSms 0 S-MsgORx A:FILE CD:ue3383223122
S:Web-interface
030511 160843 CtiSms 0 S-MsgO Match PR:1
030511 160843 CtiSms 4 S-MsgOTx P:501 CD:ue3383223122
030511 160843 CtiSms 4 S-MsgOTx Fail P:501 ERR:321 (Invalid Memory Index)

...

190
Draft Logging functionalities Draft

7.3. Exceptions Log

An exception is an event which causes the Abilis CPX restart.

When an exception happens, detailed information are saved in the Exceptions Log file CPX.XCP.

Here is an example of visualization of the Events Log stored in memory:

[18:01:34] ABILIS_CPX:d le

LOG EMPTY

Tip
The command allows to display a log file of another version:

[09:22:28] ABILIS_CPX:_d le ?

D LE [ver] Display Exceptions Log

<ver> String corresponding to a version directory in <Optional>

the form [x.y.z or x-y-z or y.z or y-z or y].
(E.g.: 5.3.1 or 6-1-0 or 2189).

The Events Log content can also be cleared through the command c le.

Note
The Exceptions Log contains a lot of information that are meaningless for the user, but that are very useful
for the Abilis CPX technicians for solving eventual problems.

If an exception happens, send the following files/information to [email protected]:

• CPX.XCP file (using file get or FTP resource);

• system log;

• drivers.cfg file;

• TRACE.CPX file.

7.4. LOG parameter

Through the LOG parameter of each resource, logging functionalities and alarms can be activated.

The following table shows the meaning of the available options:

Table 7.1. LOG parameter table

Option Meaning
D Recording of the driver state changes and/or the meaningful
events in Debug Log.
S Recording of the driver state changes and/or the meaningful
events in the System Log.
A Periodic detection of alarms. The detected alarms can
be displayed using the command alarm view or by the
MDFIDE panel.
L On alarm detection, acoustic signal plus a message on
the LCD display are generated. This function depends on
activation of alarms detection by the A option.
T Generation by the SNMP Agent of traps corresponding to
any change of the driver state and/or occurring of meaningful
events.

191
Draft Logging functionalities Draft

The following values are also allowed:

Table 7.2. LOG parameter table

Option Meaning
NO All the logging functionalities, alarms detection and
generation, above mentioned, are disabled.
ALL All the logging functionalities, alarms detection and
generation, above mentioned, are enabled.
+E The value ALL+E activates all the options and extended Log
of state changes. The value NO+E is meaningless so it is
ignored.

Options can be combined together. Some examples:

• setting LOG:DS+E, activates the extended logging functions for Debug Log and System Log;

• setting LOG:STA, activates the extended logging functions for System Log, SNMP traps generation and periodic detection
of alarm states.

Adding or deleting one or more functionalities without setting from the scratch the value of the parameters can be done using
+ and - characters.

Some examples:

• suppose the current value of is LOG:DSTA. By setting LOG:-A, the periodic detection of eventual alarm states is removed,
leaving unchanged all the remaining options; the final value is LOG:DST;

• suppose the current value of the parameter is LOG:ST. By setting LOG:+DA, the logging function of the events on the
Events Log and the periodic alarm detection are added to the already activated options; the final value is LOG:DSTA.

Note
The changes made on this parameter are immediately activated, without the need of initialization commands.

192
Draft Draft

Chapter 8. Console configurator

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
8.1. Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
8.2. Example of an off-line configuration creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
8.3. Console configurator options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.1. Example of an off-line input file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
8.3.2. Example of an off-line output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

8.1. Console configurator

The Console configurator is an utility to create/modify the Abilis CPX configuration files offline.

Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release
which you want to use; in the following page, download the “Console configurator” utility (config.exe).

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

Note
Some command are meaningless and they cannot be used, as for example statistics and diagnostic
commands.

193
Draft Console configurator Draft

Figure 8.1. config.exe

8.2. Example of an off-line configuration creation

This utility allows to create/modify Abilis configuration file drivers.cfg. The created file can be loaded on Abilis
Compact Flash using the procedures explained in the following chapters:

Section 51.5, “How to remotely transfer files using a terminal emulator”;

Section 51.2, “How to prepare an Abilis Compact-Flash using a PC”;

Section 51.8, “How to copy files using a removable drive”.

Here an example of the off-line workflow.

1. Execute the program config.exe.

• If in the folder where config.exe is saved exists a drivers.cfg file, it will be loaded.

• If in the folder where config.exe is saved there isn't a drivers.cfg file, the utility will ask to create a new one, as
follow:

ERROR: File 'DRIVERS.CFG' not found.

Create new 'DRIVERS.CFG' (N/Y) ?

By answering Y and pressing Enter a new drivers.cfg will be created with a basic configuration.

- CONFIG - v. 2066 - 12/07/2010 - For CPX release 7.0.3 - build 3357.17 -

- (c) 1994/2010 - Abilis -

Logged as SUPERUSER

[10:17:57] ABILIS_CPX:

2. Configure the Abilis CPX.

3. At the end of the configuration writing, save the changes with save conf command.

[10:29:52] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

194
Draft Console configurator Draft

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

Warning
Every software release has its own config.exe file that creates and reads drivers.cfg files;
config.exe and drivers.cfg are compatible for releases that differs only by the last digit.

Converting drivers.cfg files of previous releases version to the current one can be done using the
utilities convcfg.exe or convcfgw.exe. These utilities can be downloaded from Abilis technical
website - download section1.

8.3. Console configurator options

The config.exe file can be used with the following options:

Table 8.1. Off-line configurator options

Option Description
-? It displays the program version and the program usage
instruction.
-cFile It allows to specify the name of the configuration file. If
omitted, the assumed name is drivers.cfg. If '-pPath' is
specified too, the specified directory path is used.
-pPath It allows to specify the directory path.
-cc It allows to create the configuration file only if it does
not exist; otherwise the existing file is used. If '-cFile' is
specified too, the specified file name is used. If '-pPath' is
specified too, the specified directory path is used.
-cu It allows to create the configuration file unconditionally.
If drivers.cfg exists, it is deleted and a new
drivers.cfg file is created. If '-cFile' is specified too, the
specified file name is used. If '-pPath' is specified too, the
specified directory path is used.
-iFile It allows to specify an input file from which the program will
get the commands.
-oFile It allows to specify an output file on which the program will
copy the result of executed commands.

Tip
This options are available by executing the program from a MS-DOS shell.

8.3.1. Example of an off-line input file

The configurator can execute scripts using the “-i” option. A script contains one command per line. For example:

d r
a r pr:1 in:telnet out:telnet cdi:* udi:tln
a r pr:2 in:* out:telnet cdi:* udi:tln
d r
quit
y

The example shows how to have the config.exe program to execute the previously listed commands, stored in the
BatchCom.txt file:

C:\> config -iC:\BatchCom.txt<enter>

Here it is the execution result:

195
Draft Console configurator Draft

- CONFIG - v. 2066 - 12/07/2010 - For CPX release 7.0.3 - build 3357.17 -

- (c) 1994/2010 - Abilis -

Logged as SUPERUSER

[10:24:29] ABILIS_CPX:d r

---+--------+--------+---------------+---------------+------------+------------
PR |IN |OUT |CDI |CDO |UDI |UDO
|NEXT |CGI |CGO |PIDI |PIDO
| |IPSRC |IPDEST |FFO
-------------------------------------------------------------------------------
0 * Cp * * CP *
-------------------------------------------------------------------------------

[10:28:15] ABILIS_CPX:a r pr:1 in:telnet out:telnet cdi:* udi:tln

COMMAND EXECUTED

[10:28:27] ABILIS_CPX:a r pr:2 in:* out:telnet cdi:* udi:tln

COMMAND EXECUTED

[10:28:36] ABILIS_CPX:d r

- Not Saved (SAVE CONF) -------------------------------------------------------

---+--------+--------+---------------+---------------+------------+------------
PR |IN |OUT |CDI |CDO |UDI |UDO
|NEXT |CGI |CGO |PIDI |PIDO
| |IPSRC |IPDEST |FFO
-------------------------------------------------------------------------------
0 * Cp * * CP *
-------------------------------------------------------------------------------
1 Telnet Telnet * * TLN *
-------------------------------------------------------------------------------
2 * Telnet * * TLN *
-------------------------------------------------------------------------------

[17:29:15] ABILIS_CPX:quit

THE CURRENT CONFIGURATION WAS MODIFIED BUT NOT SAVED.

PROCEED WITH 'SAVE CONF' COMMAND (N/Y/A)?y

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[17:29:21] ABILIS_CPX:

Program exits.

8.3.2. Example of an off-line output file

Using the “-o” option, the off-line configurator redirects the standard output to a text file:

C:\> config -oC:\Output.txt<enter>

Suppose to enter the d ver command to the off-line configurator command line interpreter after the previous line execution.
A copy of the program output will be saved in text format in the specified file. Here it is the contents of Output.txt file:

- CONFIG - v. 2066 - 12/07/2010 - For CPX release 7.0.3 - build 3357.17 -

- (c) 1994/2010 - Abilis -

196
Draft Console configurator Draft

Logged as SUPERUSER

[10:35:08] ABILIS_CPX:d ver

Abilis CPX - Ver. 7.0.3 - 24/11/2010 - Build 3357.17 - 24/11/2010

CONFIG - v. 2066 - 12/07/2010
(c) 1994/2010 - Abilis

CX : v. 2483.3 - 16/11/2010 CP : v. 5005.23 - 24/11/2010

COR : v. 2036 - 09/02/2010 CNFG : v. 3788.18 - 24/11/2010
COMMON : v. 3099.10 - 24/11/2010

[17:44:46] ABILIS_CPX:exit

Program exits.

197
Draft Draft

Part II. Hardware configuration

Draft Draft

Table of Contents
9. Voip card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.1. Voip card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.2. POTS-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.3. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
9.3.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
10. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.2. ADSL-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.3. ADSL-X resource diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.1. ADLS-X resource diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.2. ADSL-X resource statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
11. GSM-UMTS BOX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1. GSM-BOX and UMTS-BOX devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.1. UG device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.2. CELLBOX fake device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.1.3. CELL device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.1.4. CODEC device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.1.5. SIMEMU device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.2. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.2.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.3. LCS - Last Calling number Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
11.3.1. LCSG - Last Calling number Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
11.3.2. LCST - Last Calling number Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.4. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.5. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.6. CTI GSM/UMTS ports diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.1. Diagnostics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.2. Statistics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.7. How to update UMTSBOX-2 firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
12. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.1. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.2. Simbox device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.3. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
12.4. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
12.5. How to update Simbox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
13. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.1. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.2. Citobox and GPIO devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.3. CTI port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
13.4. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
13.4.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
13.5. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.1. Citobox diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.2. Citobox Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.6. How to update Citobox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
14. RJS - RJ Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.1. RJS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.2. RJS device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.3. How to update RJS firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
15. UMTS Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
15.1. UMTS Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

199
Draft Draft

Chapter 9. Voip card

Luigi Demuro

Table of Contents
9.1. Voip card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.2. POTS-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
9.3. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
9.3.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

9.1. Voip card

POTS driver supports both POTS cards and Voip cards.

9.2. POTS-X device activation

Use the command a dev:pots-x to add the device where x is the hardware device identifier [1..250].

[18:06:00] ABILIS_CPX:a dev:pots-3

COMMAND EXECUTED

[18:06:11] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
ETH-3 Yes Eth-3 . . . . . . . . . . . . . . . . . . . 10 PCI ( 12)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
POTS-3 No 133..148 . . . . . . . . . . . . . . . . . . NONE PCI ( -)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . - PCI ( -)
CB-1 Yes 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

200
Draft Voip card Draft

9.3. CTI routing configuration

Calls directed to VoiP Card can't be routed in transparent mode; internal clusters and route the calls trough packet voice
resources.

9.3.1. CTI Routing table configuration

Assume that:

• Abilis has the following CTI ports configuration: ports 101 and 102 are toward the PBX;

• internal cluster are already configured.

Type the following command to verify cti port group configuration:

[18:12:13] ABILIS_CPX:d ctig

ID: PICKUP: SCAN: RULE:
---------------------------+-------------------------+-------------------------
[DESCR:]
ID: SCAN: RULE: PICKUP: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
---------------------------+-------------------------+-------------------------
PBX_group
1 NO R ST |101 102 . . . |. . . . .
---------------------------+-------------------------+-------------------------

9.3.1.1. CTIR from ISDN ports to VoiP CTI Ports

The following routings allow to route calls coming from a VoiP port (G1) toward the other VoiP port.

[18:22:32] ABILIS_CPX:a ctir pr:3 type:ctov sr:clus2 poo:g1 coders:g.711 sp:64000 cdi:* sc:no dj:0

COMMAND EXECUTED

[18:22:56] ABILIS_CPX:a ctir pr:4 type:vtoc poi:g1 ds:clus1 coders:g.711 sp:64000 cdi:3* next:u sc:

COMMAND EXECUTED

[18:23:40] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 CtoV Clus2 G1 * *
NO ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711

201
Draft Voip card Draft

-------------------------------------------------------------------------------
4 VtoC G1 Clus1 1* *
UNLIMITED ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711

-------------------------------------------------------------------------------
5 TR G1 G2 * u*
-------------------------------------------------------------------------------
6 TR G2 G1 * *
-------------------------------------------------------------------------------

The routing PR:4 routes calls coming from G1 ports to internal cluster Clus1, while the routing PR:3 accepts calls from
internal cluster Clus2 and forwards them to toward the other VoiP port.

202
Draft Draft

Chapter 10. ADSL modem

Luigi Demuro

Table of Contents
10.1. ADSL modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.2. ADSL-X device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
10.3. ADSL-X resource diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.1. ADLS-X resource diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
10.3.2. ADSL-X resource statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

10.1. ADSL modem

ADSL modem enables Abilis to connect to an adsl line without installing any additional router. Each modem can be
connected to only one adsl line, so n adsl lines need n adsl modems.

Tip
Interesting chapters:

Section 2.10.1, “ADSL modem”;

Section 3.5, “ADSL modem connection”.

Warning
The number of ADSL StarModem which can be connected to the same USB 1.1 OHCI/UHCI controller is
limited. Refer to Section 2.10.1.3, “Isochronous mode” to havo more information about isochronous mode.

10.2. ADSL-X device activation

Use the following command to add the device. More adsl modems can be used at the same time, so an hardware device
identificator is used: a dev:adslusb-x (x: HW DEVICE IDENTIFIER IN THE RANGE [1..250] IS REQUIRED).

[08:05:01] ABILIS_CPX:a dev:adslusb-1

COMMAND EXECUTED

[08:05:04] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
ETH-3 Yes Eth-3 . . . . . . . . . . . . . . . . . . . 10 PCI ( 12)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . - PCI ( -)
CB-1 Yes 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

203
Draft ADSL modem Draft

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID

-------------------------------------------------------------------------------
ADSLUSB-1 No No Adsl-1 . . . . . . . . . . . . . . . . NONE
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 Yes No . . . . . . . . . . . . . . . . . . . NONE
CODEC-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
SIMEMU-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
RJS-1 Yes No Rjs-1 . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

The resource adsl-1 is automatically set active.

[08:12:40] ABILIS_CPX:d p adsl-1

RES:Adsl-1 --------------------------------------------------------------------
Run DESCR:
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:1 usb-tx-bufsize:3200

[08:12:52] ABILIS_CPX:d p adsl-1 ?

Adsl resource parameter(s):

DESCR: Resource description [Max. 80 aphanumeric extended characters]

LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E]
(D: Debug Log; S: System Log; A: Alarm view; L: Local audible alarm;
T: SNMP traps; +E: Extended Log of state changes, see ref. manual)
max-vc: Maximal number of VC (VPI/VCI pair) supported [1..255]
aal5-max-payload: Maximum size of AAL5 payload [2100 bytes]
aal5-payload-rxbuf: Number of aal5 payload buffers in receive FIFO [1..255]
usb-rx-bufsize: Size of the USB receive buffer [1728 bytes]
usb-rx-buf: Number of USB receive buffers [1..255]
usb-tx-bufsize: Size of the USB transmit buffer [128..65472 bytes]

The default parameters are sufficient to make the device working properly.

Use the classic Abilis CPX commands syntax to change a parameter:

[08:13:02] ABILIS_CPX:s p adsl-1 descr:adsl-operatorA

COMMAND EXECUTED

[08:15:51] ABILIS_CPX:d p adsl-1

RES:Adsl-1 - Not Saved (SAVE CONF) --------------------------------------------

------------------------------------------------------------------------
Run DESCR:adsl-operatorA
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30

204
Draft ADSL modem Draft

usb-rx-bufsize:1728 usb-rx-buf:1 usb-tx-bufsize:3200

Caution
Remember to save the configuration to save changes permanently (save conf).

Tip
Interesting chapters:

Section 52.4, “How to configure ADSL connections using USB modems”;

Section 52.8, “How to share a single Internet connection among multiple computers”;

Section 52.1, “How to configure LAN settings”;

Section 52.3, “How to assign several IP addresses to the same LAN port”.

10.3. ADSL-X resource diagnostics and statistics

10.3.1. ADLS-X resource diagnostics
To display the diagnostics of the adsl-x resource the following commands are used:

d d adsl-x / d de adsl-x Shows diagnostic information, such as the state of the resource, the modem MAC
address, S/N ratio and loop attenuation, the bandwidth of download and upload, the
input and output throughput.

[18:06:40] ABILIS_CPX:d d adsl-1

RES:Adsl-1 --------------------------------------------------------------------
Adsl-EDT-"Only-Voice"
MODEM-STATE:CONNECTED MODEM-TYPE:StarModem-UM1050
MODEM-FAILURE:NONE MODEM-USB-RX-MODE:ISO
MODEM-MAC:00-30-0A-4B-BF-C1 MODEM-USB-RX-BW:2120000
------------------------------------------------------------------------
ADSL-STATE:UP ADSL-TYPE:Annex-A
ADSL-TX-SPEED:320000 ADSL-RX-SPEED:1504000
ADSL-TX-SN-MARGIN:31 ADSL-RX-SN-MARGIN:33
ADSL-TX-ATTENUATION:10 ADSL-RX-ATTENUATION:15
- ATM level virtual channel diagnostics --------------------------------
VPI VCI State Bw-Out Bw-In 5sec-Thr-Out 5sec-Thr-In
5min-Thr-Out 5min-Thr-In
------------------------------------------------------------------------
8 35 UP 289811 1362113 1584 2536
1016 1664
------------------------------------------------------------------------

Note
Additional diagnostics about S/N ratio and loop attenuation are shown only if a Starmodem is used.

Tip
Interesting chapter: Section 54.3.3, “Why the xDSL line is slow?”.

10.3.2. ADSL-X resource statistics

To display the statistics of the adsl-x resource the following commands are used:

d s adsl-x / d se adsl-x Shows statistics information, such as the number of adsl down/start, the number of
modem disconnection/connection, the number of errors on the adsl line, ecc.

205
Draft ADSL modem Draft

[18:06:40] ABILIS_CPX:d s adsl-1

RES:Adsl-1 --------------------------------------------------------------------
Adsl-EDT-"Only-Voice"
--- Cleared 0 days 12:19:27 ago, on 13/12/2010 at 21:12:53 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
ADSL-DOWN | 0| |MODEM-DISC | 0| |
ADSL-UP | 1| |MODEM-CONN | 1| |
AUTORST-A | 0| |AUTORST-U | 0| |
MANUALRST | 0| |MISALIGNED | 0| |
ATM-INV-CEL| 0| |ATM-VC-UNK | 0| |
------------------------------------------------------------------------
VPI:8 VCI:35
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CELLS | 610007| 366324|AAL5-SDU | 371548| 313908|
AAL5-CHAR | 15136608| 12397702|ERRORS | 0| 0|
------------------------------------------------------------------------

Tip
Interesting chapter: Section 54.3.3, “Why the xDSL line is slow?”.

206
Draft Draft

Chapter 11. GSM-UMTS BOX

Marco Bellesia
Angelo Pignoli

Table of Contents
11.1. GSM-BOX and UMTS-BOX devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.1. UG device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.1.2. CELLBOX fake device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
11.1.3. CELL device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
11.1.4. CODEC device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.1.5. SIMEMU device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.2. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.2.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.3. LCS - Last Calling number Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
11.3.1. LCSG - Last Calling number Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
11.3.2. LCST - Last Calling number Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.4. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.5. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
11.6. CTI GSM/UMTS ports diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.1. Diagnostics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.6.2. Statistics of CTI GSM/UMTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.7. How to update UMTSBOX-2 firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

11.1. GSM-BOX and UMTS-BOX devices activation

GSM-BOX and UMTS-BOX are devices which allow to use mobile phone SIM cards with the Abilis.

GSM-BOX and UMTS-BOX activation are based on four devices: UG, CELL, CODEC and SIMEMU.

In addition there is a fake device named CELLBOX which acts as a container of all the devices that belongs to a GSM-BOX
or UMTS-BOX; easily it permits to activate CELL, CODEC and SIMEMU devices with a single command.

Tip
Interesting chapters:

Section 3.7, “UMTS-BOX connection”;

Section 2.10.2, “UMTS-BOX2”;

Section 2.10.3, “GSM Box”;

Section 2.10.6, “Simbox”;

Chapter 12, Simbox.

11.1.1. UG device
The activation of the UG device adds in the Abilis system CTI ports from 201 to 232. Every CTI port corresponds to a SIM
card which is managed by a GSM/UMTS modem.

Add the device to the Abilis system with the following command.

[14:12:55] ABILIS_CPX:a dev:ug-1

207
Draft GSM-UMTS BOX Draft

COMMAND EXECUTED

The device may already exist in the system, but may not yet be active. Set it active with the command:

[14:13:02] ABILIS_CPX:s act dev:ug-1

DEV:GSM-1 ALREADY ACTIVE

[14:17:30] ABILIS_CPX:d dev

---------------- Active ISA/PCI Cards and Physical Resources: -----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 11)
ETH-2 Yes Eth100-2 . . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . . 6 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . . 8 PCI ( 12)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes Yes Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes Yes Adsl-2 . . . . . . . . . . . . . . . . 0.1

--------------- Inactive ISA/PCI Cards and Physical Resources: ----------------

Card(s) Run Physical Resource(s)/CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE ISA/PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or Device(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

11.1.1.1. CTI GSM/UMTS port configuration

Use the following command to modify the parameters of a CTI port:

s p ctip:<port_number> <parameter>:<value>

The d p ctip ? or d p ctipe ? commands show all available parameters.

[06:33:10] ABILIS_CPX:d p ctip:201

CTIP:201 DESCR:
Act card:UG-1<1>
Run OPSTATE:UP LOG:NO TYPE:NET-PUBLIC
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:
RSIM:NO

[06:33:14] ABILIS_CPX:d p ctipe:201

CTIP:202 DESCR:

208
Draft GSM-UMTS BOX Draft

Act card:UG-1<2>
Run OPSTATE:UP LOG:DS TYPE:USER
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:tre.it
LOOP:NO PIN:# GAIN-IN:SYS CODEC-GAIN-IN:SYS
DIALT:5 PIN2:# GAIN-OUT:SYS CODEC-GAIN-OUT:SYS
RSIM:NO
LCS-GROUP:NONE

Meaning of the most important parameters:

OPSTATE operative state [DOWN: the port is inoperative (it refuses incoming calls and doesn't allow outgoing
calls); UP: the port is fully operative].

LOG Logging functionalities activation/deactivation.

TYPE Sets the port type with respect to the customer's network [USER, NET-PUBLIC].

signalling Selects the port signalling protocol; only the AT-protocol is available for GSM/UMTS devices so a
fixed value is used [CELL].

mode Selects the layer 1 protocol mode; for GSM/UMTS is used a fixed value [CELL].

NUM Phone number assigned to CTI port. The available values are:

• *: the Calling Number offered by CTIR is passed transparently to the device;

• #: the Calling Number is not passed to the device;

• r*: enforces the presentation restricted: the Calling Number is not passed to the device;

• nnnn: exactly this number is passed as Calling Number to the device; attributes can be specified as
number prefixes

• nnnn*: the Calling Number received from CTIR is modified by replacing first four digits with
nnnn; attributes can be specified as number prefixes

• nnnn??: similar to nnnn* with the difference that only an exact number of digits as many ? is
passed after nnnn;

• ????: only an exact number of digits as many ? is passed after the nnnn.

VOICE-ROAMING: Enable/disable roaming for voice [DISABLED, ENABLED]

PDN-ROAMING Enable/disable roaming for data [DISABLED, ENABLED]

PDN-APN APN string to be used in the data connection

PDN-MODE Locks the PDN mode or leaves HC15 to choose the better available [AUTO, GPRS, UMTS]

LOOP activate Loopback mode [NO, GSM, CODEC].

PIN PIN of the SIM card.

PIN2 PIN2 of the SIM card.

GAIN-IN port input gain controlled by the GSM/UMTS module.

GAIN-OUT port output gain controlled by the GSM/UMTS module.

CODEC-GAIN-IN GSM/UMTS port input gain controlled by the Audio-codec

CODEC-GAIN-OUT GSM/UMTS port input gain controlled by the Audio-codec

DIALT Dialling timeout.

RSIM SIM remotization activation and method [NO, PERMANENT, DYNAMIC]

209
Draft GSM-UMTS BOX Draft

LCS-GROUP Last Calling number Service group identifier [NONE, 1..32]

Caution
To activate the changes made on the upper case parameters, execute the initialization command init ctisys;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

Caution
In order to avoid that the SIM card gets blocked It is ALWAYS better to remove the PIN code and all
additional services (e.g.: messagebox)

Tip
Typically, the default configuration of CTI GSM/UMTS port already allows the GSM-BOX or UMTS-BOX
to work properly.

11.1.2. CELLBOX fake device

CELLBOX device can be activated for every GSM-BOX or UMTS-BOX to add all devices needed for each equipment with
a single command: CELL, CODEC and SIMEMU.

Add the device to the Abilis system with the following command.

The device may already exist in the system, but may not yet be active. Set it active with the command s act dev:cellbox-1.

[14:24:03] ABILIS_CPX:a dev:cellbox-1

COMMAND EXECUTED

[14:24:05] ABILIS_CPX:da dev

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH100-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH100-2 Yes Eth100-2 . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes No Adsl-2 . . . . . . . . . . . . . . . . 0.1
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 No No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 No No . . . . . . . . . . . . . . . . . . . NONE
CODEC-1 No No . . . . . . . . . . . . . . . . . . . NONE
SIMEMU-1 No No . . . . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------

210
Draft GSM-UMTS BOX Draft

*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

11.1.3. CELL device

CELL devices must be activated for every SIM card connected to the Abilis CPX.

Add the device to the Abilis system with the following command.The device may already exist in the system, but may not yet
be active: set it active with the command s act dev:cell-1.

[14:24:03] ABILIS_CPX:a dev:cell-1

COMMAND EXECUTED

[14:29:07] ABILIS_CPX:a dev:cell-2

COMMAND EXECUTED

[14:48:31] ABILIS_CPX:d dev

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth100-2 . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes No Adsl-2 . . . . . . . . . . . . . . . . 0.1
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 No No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 No No . . . . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

Tip
It is recommended to use the CELLBOX command to add all devices needed with a single instruction

211
Draft GSM-UMTS BOX Draft

11.1.4. CODEC device

CODEC represents the GSM/UMTS interface that connects GSM/UMTS modems to the Abilis through USB ports. Every
device enables the connection of 2 modems. The associations between CELL and CODEC and USBPORTIDs is completely
automatic, thus avoiding any error in the assignment.

Add the device to the Abilis system with the following command; the device may already exist in the system, but may not
yet be active: set it active with the command s act dev:codec-1. This command associate the CODEC-1 to the CELL-1 and
CELL-2 devices.

[15:29:52] ABILIS_CPX:a dev:codec-1

COMMAND EXECUTED

[15:32:31] ABILIS_CPX:d dev

------------------ Active PCI Cards and Physical Resources: -------------------
Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth100-2 . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes No Adsl-2 . . . . . . . . . . . . . . . . 0.1
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 No No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 No No . . . . . . . . . . . . . . . . . . . NONE
CODEC-1 No No . . . . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

Tip
It is recommended to use the CELLBOX command to add all devices needed with a single instruction

11.1.5. SIMEMU device

SIMEMU is used to manage the microcontroller which is inside GSM-BOX or UMTS-BOX. Currently it is used only in
UMTS-BOX to reset the UMTS modules in case of troubles, in next version it will be used to manage SIM remotization.

Add the device to the Abilis system with the following command; the device may already exist in the system, but may not
yet be active: set it active with the command s act dev:simemu-1. This command associate the SIMEMU-1 to the CODEC-1
device.

212
Draft GSM-UMTS BOX Draft

[15:29:52] ABILIS_CPX:a dev:simemu-1

COMMAND EXECUTED

[15:32:31] ABILIS_CPX:d dev

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth100-1 . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth100-2 . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . NONE PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . 0.0.0
ADSLUSB-2 Yes No Adsl-2 . . . . . . . . . . . . . . . . 0.1
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 No No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 No No . . . . . . . . . . . . . . . . . . . NONE
CODEC-1 No No . . . . . . . . . . . . . . . . . . . NONE
SIMEMU-1 No No . . . . . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

Tip
It is recommended to use the CELLBOX command to add all devices needed with a single instruction

11.2. CTI Routing configuration

Calls directed to GSM/UMTS gateway can't be routed in transparent mode; you must create internal clusters and route the
calls trough packet voice resources.

11.2.1. CTI Routing table configuration

Assume that:

• Abilis has the following CTI ports configuration: ports 31 and 32 are toward the PBX, ports 33 and 34 toward the ISDN
lines and ports 201 and 202 toward GSM/UMTS gateway.

• internal cluster clus1 and clus2 are already created.

Type the following command to verify ctig configuration:

213
Draft GSM-UMTS BOX Draft

[18:12:13] ABILIS_CPX:d ctig

ID: PICKUP: SCAN: RULE:
---------------------------+-------------------------+-------------------------
[DESCR:]
ID: SCAN: RULE: PICKUP: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
---------------------------+-------------------------+-------------------------
PBX_group
1 NO R ST |31 32 . . . |. . . . .
---------------------------+-------------------------+-------------------------
ISDN_line_group
2 NO R ST |33 34 . . . |. . . . .
---------------------------+-------------------------+-------------------------
GSM_group
3 NO R ST |201 202 . . . |. . . . .
---------------------------+-------------------------+-------------------------

Tip
Interesting chapters:

Section 42.3, “CTI Ports Group”;

Section 42.6, “CTI Router”.

Warning
At this moment GSM or UMTS gateway supports only G.711 coder. Other codecs are supported by
transcoding through additional ISDN cards.

11.2.1.1. CTIR from ISDN ports to GSM or UMTS gateway

The following routings allow to route calls coming from a group of BRI ports (G1) toward GSM/UMTS gateway (G3) for
numbers starting with digit 3.

[18:22:32] ABILIS_CPX:a ctir pr:3 type:ctov sr:clus2 poo:g3 coders:g.711 sp:64000 cdi:* sc:no dj:0

COMMAND EXECUTED

[18:22:56] ABILIS_CPX:a ctir pr:4 type:vtoc poi:g1 ds:clus1 coders:g.711 sp:64000 cdi:3* next:u sc:

COMMAND EXECUTED

[18:23:40] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 CtoV Clus2 G3 * *
NO ANY NO Dft * *

214
Draft GSM-UMTS BOX Draft

64000 NO 0 40 Sys Sys * *

NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
4 VtoC G1 Clus1 3* *
UNLIMITED ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711

-------------------------------------------------------------------------------
5 TR G1 G2 * u*
-------------------------------------------------------------------------------
6 TR G2 G1 * *
-------------------------------------------------------------------------------

The routing PR:4 routes calls coming from G1 ports to internal cluster Clus1, while the routing PR:3 accepts calls from
internal cluster Clus2 and forwards them to GSM/UMTS gateway.

The NEXT parameter in the routing PR:4 is set to UNLIMITED; if call fails, it would try to use next routings.

Tip
Interesting chapter: Section 42.6, “CTI Router”.

215
Draft GSM-UMTS BOX Draft

Figure 11.1. CTIR from ISDN port

11.2.1.2. CTIR from a remote cluster to GSM or UMTS gateway

The following routing allows to route calls coming from a remote cluster (e.g. Abilis2) toward GSM gateway (G3) for
numbers starting with 3.

[18:33:54] ABILIS_CPX:a ctir pr:3 type:ctoc sr:Abilis2 ds:clus1 cdi:3* coders:g.711 sp:64000 sc:no

COMMAND EXECUTED

[18:34:38] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...

216
Draft GSM-UMTS BOX Draft

-------------------------------------------------------------------------------
3 CtoC Abilis2 Clus1 3* *
NO ANY NO Dft * *
64000 NO * * Sys Sys * *
* * 0 40 NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO
G.711

-------------------------------------------------------------------------------
4 CtoV Clus2 G3 * *
NO ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
5 VtoC G1 Clus1 3* *
UNLIMITED ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
6 TR G1 G2 * u*
-------------------------------------------------------------------------------
7 TR G2 G1 * *
-------------------------------------------------------------------------------

The routing PR:3 accepts the calls coming from the remote cluster Abilis2 toward numbers starting with 3 and forward
them to internal cluster Clus1. The call will be intercepted by the routing PR:4 and forwarded to GSM gateway.

Tip
Interesting chapters:

Section 42.4, “CTI Cluster”;

Section 42.5, “CTI Link”;

Section 42.6, “CTI Router”.

11.2.1.3. CTIR from GSM or UMTS gateway to a group of ISDN ports

The following routings allow to route calls coming from GSM/UMTS gateway (calls directed to the number of the SIM card
inserted in the CELL modem) to a group of BRI ports (G1).

[18:46:24] ABILIS_CPX:a ctir pr:3 type:vtoc poi:g3 ds:clus2 cdi:* coders:g.711 sp:64000 cdo:711 sc:

COMMAND EXECUTED

[18:49:41] ABILIS_CPX:a ctir pr:3 type:ctov sr:clus1 poo:g1 cdi:711 coders:g.711 sp:64000 sc:no dj:

COMMAND EXECUTED

[18:51:00] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO

217
Draft GSM-UMTS BOX Draft

|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO

| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5

-------------------------------------------------------------------------------
0 DATA * CtiSLink * u*
NO ANY NO Dft NO * *
* *
'SgiAllowed' *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * u*
-------------------------------------------------------------------------------
2 CtoV * G1 'Nodo' n'CDI.S2'
-------------------------------------------------------------------------------
3 CtoV Clus1 G1 711 *
NO ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
4 VtoC G3 Clus2 * 711
NO ANY NO Dft * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
5 CtoC Abilis2 Clus1 3* *
NO ANY NO Dft NO * *
64000 NO * * Sys Sys * *
* * 0 40 NO Sys * *
Sys AUTO AUTO Sys Sys
G.711
-------------------------------------------------------------------------------
6 CtoC Abilis2 Clus1 3* *
NO ANY NO Dft NO * *
64000 Sys * * Sys Sys * *
* * * * NO Sys * *
Sys AUTO AUTO Sys Sys
G.711
-------------------------------------------------------------------------------
7 CtoV Clus2 G3 * *
NO ANY NO Dft NO * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
Sys AUTO AUTO Sys Sys Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
8 VtoC G1 Clus1 3* *
UNLIMITED ANY NO Dft NO * *
64000 NO 0 40 Sys Sys * *
NO Sys * *
Sys AUTO AUTO Sys Sys Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
9 TR G1 G2 * u*

218
Draft GSM-UMTS BOX Draft

-------------------------------------------------------------------------------
10 TR G2 G1 * *
-------------------------------------------------------------------------------

The routing PR:4 accepts the calls directed to GSM gateway and forward them to internal cluster Clus2, setting as Called
Number Output (CDO) the number 711 (it supposes that this is the Post Operator number). The call generated, will be
intercepted by routing PR:3 and forwarded to G1 group (ISDN ports of PBX).

Tip
Interesting chapters:

Section 42.2, “CTI Ports configuration”;

Section 42.3, “CTI Ports Group”;

Section 42.6, “CTI Router”.

Figure 11.2. CTIR from GMS or UMTS gateway

11.3. LCS - Last Calling number Service

This service is useful to route a call received by a sim inserted in UMTS BOX, toward the last number which called the
calling number.

219
Draft GSM-UMTS BOX Draft

Suppose to have this situation:

• ctip 101 (for example number 200) make a call toward a cell phone (number 320123456)
• the call is routed through the UMTS BOX using port #201 (which corresponds to a sim whose number is 320654321)
• the LCS saves calling and called numbers in the lcs table
• a call is received by UMTS BOX: the called number is 320654321, the calling number is 320123456
• the call is automatically routed toward ctip 101 (number 200)

LCS is configurable through:

• CTISYS resource
• LCSG - last calling number group
• LCS-GROUP parameter of the ctip resource
• IAX-LCS-GROUP parameter for iax users
• SIP-LCS-GROUP parameter for sip users
• LCS and LCST parameters of CTIR resource
• LCST - Last Calling number Table

11.3.1. LCSG - Last Calling number Group

LCSG is useful to manage lcs groups. The managing is made following the classic Abilis sintax: a/c/s/d lcsg
<parameter:parameter>.

LCSG configuration holds all the rules required to manipulate the TON for CD and CG.

[10:35:38] ABILIS_CPX:d lcsg

----+--------------------------------------------------------------------------
ID: |[DESCR:]
|CPS-LIST: NAT-PREFIX: INT-PREFIX: COUNTRY-CODE:
|CB-PERMIT-CD:
|CB-UNK-CDO: CB-NAT-CDO: CB-INT-CDO:
|CB-SDO: CB-SGO: CB-CDO-DFT:
|[CTI Ports, CTI Clusters, IAX users, SIP users]
----+--------------------------------------------------------------------------
*** NO LCS GROUPs DEFINED ***

[10:40:00] ABILIS_CPX:d lcsg ?

ID: Last Calling Number Service group identifier [1..32] <Optional>

Last Calling Number Service group parameter(s):

DESCR: Entry description. From 0 up to 70 ASCII extended characters.

Spaces are not allowed. Case is preserved.
Note: it is displayed only when not empty.
CPS-LIST: Name of an IN list holding Carrier Preselection prefixes or "#".
NAT-PREFIX: National prefix. From 1 up to 6 digits (E.g. 0) or "SYS".
INT-PREFIX: International prefix. From 1 up to 6 digits (E.g. 00) or "SYS".
COUNTRY-CODE: Country code. From 1 up to 6 digits (E.g. 39) or "SYS".
CB-PERMIT-CD: Permitted called numbers/prefixes for the back call.
From 1 up to 20 characters, in the range ['0'..'9', '*']
optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d,
t, l, p] attributes or the name of a list between primes.
The '*' is allowed only alone or as the last character.
(E.g. ne1234567 or 4567* or * or 'my_list')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CB-UNK-CDO: Call Back number for UNKNOWN type CALLING. "#" or up to 20
digits ['0'..'9'] optionally preceded by TON [u, i, n, o, s, h, c]
and/or NP [x, e, d, t, l, p] attributes or 'macro'.
(E.g. CALLING or ne1234567 or ux'CALLING' or ux11'CALLING.S2')
See HELP ISDN ATTRIBUTES for details on attributes.

220
Draft GSM-UMTS BOX Draft

See HELP ISDN VALUES for details on meaning of special values.

CB-NAT-CDO: Call Back number for NATIONAL type CALLING. "#" or up to 20
digits ['0'..'9'] optionally preceded by TON [u, i, n, o, s, h, c]
and/or NP [x, e, d, t, l, p] attributes or 'macro'.
(E.g. CALLING or ne1234567 or ux'CALLING' or ux11'CALLING.S2')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CB-INT-CDO: Call Back number for INTERNATIONAL type CALLING. "#" or up to 20
digits ['0'..'9'] optionally preceded by TON [u, i, n, o, s, h, c]
and/or NP [x, e, d, t, l, p] attributes or 'macro'.
(E.g. CALLING or ne1234567 or ux'CALLING' or ux11'CALLING.S2')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CB-SDO: Call Back called sub-address [AlphaNumExt, #, *] (E.g.: *, A123, #)
See HELP ISDN VALUES for details on meaning of special values.
CB-SGO: Call Back calling sub-address [AlphaNumExt, #, *] (E.g.: *, A123, #)
See HELP ISDN VALUES for details on meaning of special values.
CB-CDO-DFT: Default call back number. "*" or up to 20 digits ['0'..'9']
optionally preceded by TON [u, i, n, o, s, h, c] and/or NP
[x, e, d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.

11.3.2. LCST - Last Calling number Table

LCS automatically stores the pair of calling and called numbers in the LCST. The table can be also manipulated with the d/a/
c lcst commands.

[10:40:02] ABILIS_CPX:d lcst

-----+----------------------+----------------------+---------------------+-----
Group| Called | Calling | Updated on (GMT) |Tout
| | | [Expiry on (GMT)] |
-----+----------------------+----------------------+---------------------+-----
1 ux12345678 ux01 16/04/2009 16:02:59 6
16/04/2009 22:02:59
-----+----------------------+----------------------+---------------------+-----
1 ux99999999 ux02 16/04/2009 16:03:20 NONE
-----+----------------------+----------------------+---------------------+-----

[10:40:27] ABILIS_CPX:d lcst ?

D LCST Display all LCS table entries

D LCST filter:val [filter:val] Display any LCS table entry matching
the specified filter(s)

Allowed filters:

GROUP: Last Calling number service group identifier [1..32] <Optional>

CD: Search for any calling number(s) starting with the given <Optional>
prefix (from 1 up to 20 digits optionally preceded by
TON [u, i, n, o, s, h, c] and NP [x, e, d, t, l, p] attributes).

Last Calling Number Service table entry parameter(s):

GROUP: Last Calling number service group identifier [1..32]

CD: Called number
CG: Calling number
Updated on: Addition/update UTC date and time
Expiry on: Expiration UTC date and time <Only for Tout: not equal to NONE>
TOUT: Entry expiration timeout [NONE, 1..999 hour]

221
Draft GSM-UMTS BOX Draft

11.4. Connecting UMTS-BOX2 to Simbox

Please, refer to chapter Chapter 12, Simbox to have information about this device.

11.5. UMTS-BOX2 sim remotization

Sim remotization allows to use a remote sim inserted in a Simbox with an UMTS BOX2 via IP network.

Sim remotization can be used only with UMTS Box2 (old devices like GSM BOX and UMTS BOX don't support sim
remotization).

Note
The minimal version number of the UMTS-BOX2 in order to use SIM remotization is 19.The version is
visible through the command D USBDEV:

[20:02:15] ABILIS_CPX:d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 EHCI Virtual Root Hub 0.00 0
2 0000 On Time 0000 OHCI Virtual Root Hub 0.00 1
3 0000 On Time 0000 OHCI Virtual Root Hub 0.00 2
4 0000 On Time 0000 UHCI Virtual Root Hub 0.00 3
5 0000 On Time 0000 UHCI Virtual Root Hub 0.00 4
6 04CC 1520 2.00 0.3
7 04D8 Abilis 000C USB SIM-BOX 9.01 1.2
8 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.3.2
9 04D8 Abilis 000C USB UMTS-BOX2 19.05 0.3.3
10 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.0
11 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.1

The most important parameter to manage SIM remotization is RSIM. It can have different values:NO, PERMANET and
DYNAMIC. Other parameters must be configured if PERMANENT value is chosen.

Table 11.1. Meaning of RSIM parameters

Value Meaning
NO SIM remotization disabled
PERMANENT the SIM remotization is enabled with configured values (see
below)
DYNAMIC the SIM remotization is enabled with configured values in
ctip preferences (see below)

Assuming that the ctip port assigned to UMTS-BOX2 is 201, use the following command to show its configuration.

[23:27:13] ABILIS_CPX:d ctip:201

CTIP:201 DESCR:
Act card:UG-1<1>
Run OPSTATE:UP LOG:NO TYPE:NET-PUBLIC
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:
RSIM:NO

In the example above, sim remotization is disabled. Use the following command to set the rsim parameter to permanent:

[23:32:43] ABILIS_CPX:s p ctip:201 rsim:permanent

222
Draft GSM-UMTS BOX Draft

COMMAND EXECUTED

[23:32:59] ABILIS_CPX:d ctip:201

CTIP:201 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:
Run card:UG-1<1>
OPSTATE:UP LOG:NO TYPE:NET-PUBLIC
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:
RSIM:PERMANENT RSIM-IP:# RSIM-SIMBOX-ID:NONE
RSIM-RES:NONE RSIM-PORT:60000 RSIM-SIM-ID:NONE
RSIM-PWD:

Note that some additional parameters are now visible. The following table shows their meaning:

Table 11.2. Meaning of parameters

Parameter (available only for RSIM:PERMANENT) Meaning
RSIM-IP SIM remotization remote IP address
RSIM-SIMBOX-ID Remote SIMBOX identifier
RSIM-RES RSIM resource
RSIM-PORT Remote UDP port used for remotization
RSIM-SIM-ID Remote SIMBOX SIM identifier
RSIM-PWD Remote SIMBOX SIM password

Use the command s ctip:xxx parameter:value to set a specific parameter. For instance use s p ctip:201 rsim-res:rsim-1 to
set the rsim resource to rsim-1 value.

The following example shows how to set the rsim parameter to dynamic:

[23:49:31] ABILIS_CPX:s ctip:201 rsim:dynamic

COMMAND EXECUTED

[23:55:04] ABILIS_CPX:d ctip:201

CTIP:201 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:
Run card:UG-1<1>
OPSTATE:UP LOG:NO TYPE:NET-PUBLIC
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:
RSIM:DYNAMIC
RSIM-RES:NONE

Note that the only parameter to configure in this case is RSIM-RES (rsim resource). The same parameters used for
PERMANENT mode can be configured for the DYNAMIC mode. Use the command s s ctip:xxx rsim:set par:val [par:val]
to configure them. They are stored automatically as CTIP preferences rather than being normal configuration parameters.

[22:37:42] ABILIS_CPX:s s ctip:201 rsim:set ip:192.168.0.208 simbox-id:1 sim-id:1

COMMAND EXECUTED

Available parameters and their meaning:

[22:38:05] ABILIS_CPX:s s ctip:201 rsim:set ?

S S CTIP:xxx RSIM:CLEAR Clear RSIM parameters and closes

223
Draft GSM-UMTS BOX Draft

connection for the specified CTI port,

where 'xxx' is a CTI port identifier
in the range [1..300].
Only for CELL (GSM/UMTS) CTI ports.
S S CTIP:xxx RSIM:SET par:val [par:val] Set RSIM parameters and orders
connection for the specified CTI port,
where 'xxx' is a CTI port identifier
in the range [1..300].
Only for CELL (GSM/UMTS) CTI ports.

SIM remotization parameter(s):

IP: Remote IP address [0-126.x.x.x, 127.0.0.1, 128.x.x.x- <Mandatory>

223.x.x.x]
PORT: Remote UDP port [1..65535] <Optional>
If missing the value 60000 is used.
SIMBOX-ID: Remote SIMBOX identifier [1..255] <Mandatory>
SIM-ID: Remote SIMBOX SIM identifier [1..32] <Mandatory>
PWD: Remote SIMBOX SIM password. <Optional>
From 0 up to 32 ASCII printable characters.
Spaces are not allowed. Case is preserved.

Use the following command to clear configured parameters.

[22:40:20] ABILIS_CPX:s s ctip:201 rsim:clear

COMMAND EXECUTED

Caution
The loading time of the remote SIM is not predictable. The full SIM load can take less than a minute or
several minutes, it depends on network speed and round trip time.

11.6. CTI GSM/UMTS ports diagnostics and statistics

11.6.1. Diagnostics of CTI GSM/UMTS ports
To show the diagnostics of the CTI Ports the following commands are used:

d d ctip / d de ctip shows the following information:

OPSTATE The overall state of the port.

VOICE-STATE The overall state of the GSM VOICE connection.

PDN-STATE The overall state of the PDN (Packet Data Network) connection.

SMS-STATE The overall state of the SMS channel.

NET The currently used GSM network name.

ROAMING Shows if the currently used UMTS/GSM network is ROAMING

type.

NET-MODE Shows if the currently used network is GSM or UMTS.

SIGNAL Signal quality (0 = -113 dBm or less, 1..30 = -111.. -53 dBm, 31 =
-51 dBm, or greater 99 = not known or not detectable, 100 = N/A
value when device isn't connected)

RXQUAL The value of BER (bit error rate) of the existing call.

IMEI Internation Mobile Equipment Identity number.

IMSI Internation Mobile Subscriber Identity number.

224
Draft GSM-UMTS BOX Draft

SIM SIM card identification number.

SMSC SMS Center number.

PWR-CONS-mA The value of the current power consumption of the GSM module.

TEMP The value of the current temperature of the GSM module.

CODEC-ISO-BW Indicates the bandwidth of the AUDIO-CODEC ISO interface.

CELL Shows if the hot-pluggable device is connected or not.

CELL-STATE Shows the state of the USB interface of the GSM USB module.

CELL-ERR Shows the reason of the not READY GSM module.

CODEC Shows if the hot-pluggable device is connected or not.

CODEC-STATE Shows the state of the USB interface of the CODEC module.

CODEC-ERR Shows the reason of the not READY GSM codec.

SIMEMU Shows if the hot-pluggable device is connected or not.

SIMEMU-STATE Shows the state of the USB interface of the SIMEMU (PIC)
module.

SIMEMU-ERR Shows the reason of the not READY GSM SIMEMU (PIC).

d d ctip:<CTIP_number> / d de Shows the diagnostics of a single port.

ctip:<CTIP_number>

Diagnostics of a CTI GSM/UMTS port when no calls are running:

[09:21:45] ABILIS_CPX:d d ctip:202

CTIP:202 ----------------------------------------------------------------------
SIM_3204748405_(EX_RETENOI_3276270837)
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SG:] CD: [SD:]
------------------------------------------------------------------------
*** All channels disconnected ***
------------------------------------------------------------------------
VOICE-STATE:READY PDN-STATE:READY SMS-STATE:READY
------------------------------------------------------------------------
NET:H3G ROAMING:NO NET-MODE:UMTS
SIGNAL:17 SIGNAL-dbm:-79 RXQUAL:0
IMEI:35739601224756 IMSI:22299220520719 SIM:N/A
SMSC:+393916263333
PWR-CONS-mA:N/A TEMP-Celsius:N/A CODEC-ISO-BW:1304000
CELL:CONNECTED CELL-STATE:READY CELL-ERR:NONE
CODEC:CONNECTED CODEC-STATE:READY CODEC-ERR:NONE
SIMEMU:CONNECTED SIMEMU-STATE:READY SIMEMU-ERR:NONE

Diagnostics of a CTI GSM port when a call is running:

[09:23:17] ABILIS_CPX:d d ctip:202

CTIP:202 ----------------------------------------------------------------------
SIM_xxxxxxxxxx
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SG:] CD: [SD:]
------------------------------------------------------------------------
1 07-LOC-ALERT 779 xxxxxxxxxx
------------------------------------------------------------------------

225
Draft GSM-UMTS BOX Draft

VOICE-STATE:IN-USE PDN-STATE:READY SMS-STATE:READY

------------------------------------------------------------------------
NET:H3G ROAMING:NO NET-MODE:UMTS
SIGNAL:17 SIGNAL-dbm:-79 RXQUAL:0
IMEI:35739601224756 IMSI:22299220520719 SIM:N/A
SMSC:+393916263333
PWR-CONS-mA:N/A TEMP-Celsius:N/A CODEC-ISO-BW:1304000
CELL:CONNECTED CELL-STATE:READY CELL-ERR:NONE
CODEC:CONNECTED CODEC-STATE:READY CODEC-ERR:NONE
SIMEMU:CONNECTED SIMEMU-STATE:READY SIMEMU-ERR:NONE

Tip
CODEC-ISO-BW shows the USB Isochronous bandwidth reserved on the USB controller to serve the CTIP.
The audio codec always reserve the bandwidth of TWO CTIP even if one is disabled.

This is what appears in the CTIR Connection (from PBX port group to GSM gateway):

[12:06:44] ABILIS_CPX:d ctic

ID Type Input Output PR State Cgi (Calling In) Cdo (Called Out)
----- ---- -------- -------- --- ------ ------------------ --------------------
1999 VtoC 31 G1 Clus1 7 ACTIVE 711 3482233445
2000 CtoV Clus2 202 G3 5 ACTIVE 711 3482233445

11.6.2. Statistics of CTI GSM/UMTS ports

To show the statistics of the CTI GSM/UMTS ports the following commands are used:

d s ctip / d se ctip Shows the statistics of all the CTI ports such as the number of calls (successfull and
unsuccessfull), the duration of the calls, the number of connection/disconnection of
the GSM/UMTS device, the number of connection/disconnection of the audio-codec
device and the number of CELL packets exchanged.

d s ctip:<CTIP_number> / d se Shows the statistics of a single CTI port.

ctip:<CTIP_number>

[16:14:19] ABILIS_CPX:d s ctip:201

CTIP:201 ----------------------------------------------------------------------
SIM-3883634235
--- Cleared 1 days 20:30:24 ago, on 25/10/2010 at 21:36:22 -------------
Layer 3 Q.931
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0|
------------------------------------------------------------------------
Layer 2 PDN
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PDN-CALL | | 0|PDN-CHAR | 0| 0|
PDN-TIME | | 0|PDN-FRM | 0| 0|
PDN-TIME-15| | 0|PDN-LOST | 0| 0|
| | |PDN-LONG | 0| 0|
------------------------------------------------------------------------
Layer 2 SMS
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SMS | 0| 0|SMS-FAIL | 0| 0|
------------------------------------------------------------------------
Layer 1 CELL (GSM/UMTS)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CELL-DISC | 0| |CODEC-DISC | 0| |
CELL-CONN | 1| |CODEC-CONN | 1| |
CELL-MANRST| 0| |CODEC-RST | 0| |
CELL-AUTRST| 0| |CODEC-UND | | 0|

226
Draft GSM-UMTS BOX Draft

CELL-HWRST | 0| |CODEC-HWRST| 0| |
CELL-OVR | 0| |CODEC-OVR | 0| |
CELL-PCK | 62814| 31405|CODEC-PCK | 160264475| 160265051|
------------------------------------------------------------------------
SIMEMU-DISC| 0| | | | |
SIMEMU-CONN| 1| | | | |
SIMEMU-RST | 0| | | | |
SIMEMU-PCK | 5| 3| | | |
SIMEMU-PCKH| 0| 0| | | |
------------------------------------------------------------------------
RSIM CELL (UMTS)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RSIM-SUCC | | 0|RSIM-PCK | 0| 0|
RSIM-FAIL | | 0|RSIM-CHAR | 0| 0|
RSIM-DISC | 0| 0|SIM-RESET | 0| |
------------------------------------------------------------------------

11.7. How to update UMTSBOX-2 firmware

Go to http://abilis.antek.it/downloads/firmwares/download.html and download the latest firmware.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

The UMTSBOX-2 firmware can be upgraded only if the current version is equal or greater than 9. Use the following
command to check the current version of firmware. In the example below firmware version is equal to 19.05.

[15:44:20] ABILIS_7.0:_d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 EHCI Virtual Root Hub 0.00 0
2 0000 On Time 0000 UHCI Virtual Root Hub 0.00 1
3 0000 On Time 0000 UHCI Virtual Root Hub 0.00 2
4 0000 On Time 0000 UHCI Virtual Root Hub 0.00 3
5 0000 On Time 0000 UHCI Virtual Root Hub 0.00 4
6 04CC 1520 2.00 0.2
7 04CC 1520 2.00 0.3
8 04D8 Abilis 000C USB CITO-BOX - GPIO 19.01 0.2.0
9 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.2.1
10 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.3.2
11 04D8 Abilis 000C USB UMTS-BOX2 19.05 0.3.3
12 04D8 Abilis 000C USB CITO-BOX - CITO 19.01 0.2.2
13 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.0
14 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.1

[15:44:26] ABILIS_7.0:_

if the above condition is met, you can add the BLUSB device typing the following command and then restart abilis1.

[15:51:01] ABILIS_CPX:a dev:blusb-1

COMMAND EXECUTED

[15:51:11] ABILIS_CPX:warm start

Updating steps:

1
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

227
Draft GSM-UMTS BOX Draft

• Upload the file umtsbox2.bin into the execution version directory (for example c:\7-0-2) without changing the file name.
The upload can be done using the file put command2 or the FTP resource3.

• use the command usbdev fw upload id:xx, where xx stands for the ID of the “USB UMTS-BOX2” (11 in the example
above).

The updating procedure can last for minutes and the result can be displayed typing D L. If the update is successful, next log
will be displayed, otherwise an error log is generated.

12/10/2010 21:26:59 [00340] W: FW UPLOAD REQUEST 04D8 000C 0.3.3

12/10/2010 21:26:59 [00341] W: FW UPLOAD REQUEST SUCCESS 04D8 000C 0.3.3
12/10/2010 21:26:59 [00267] I: CtiP-201 VOICE-ST:DOWN PDN-ST:DOWN
12/10/2010 21:27:17 [00336] W: FW UPLOAD START 04D8 000C 0.3.3
12/10/2010 21:27:19 [00337] W: FW UPLOAD SUCCESS 04D8 000C 0.3.3
12/10/2010 21:28:02 [00267] I: CtiP-201 VOICE-ST:READY PDN-ST:READY

Caution
In case of failure of updating procedure, the previous version of firmware can be restored unplugging and
plugging in the usb cable of UMTSBOX

228
Draft Draft

Chapter 12. Simbox

Luigi Demuro

Table of Contents
12.1. Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.2. Simbox device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.3. Connecting UMTS-BOX2 to Simbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
12.4. UMTS-BOX2 sim remotization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
12.5. How to update Simbox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

12.1. Simbox
Simbox is a device which holds up to 32 sims. It allow to use sim remotization only having an UMTS BOX2 device.

Refer to chapter Section 2.10.6, “Simbox” to have more information about the hardware.

Tip
Interesting chapters:

Section 2.10.6, “Simbox”;

Section 3.9, “Simbox connection”.

12.2. Simbox device activation

Use the following command to add the device.

[08:40:54] ABILIS_CPX:a dev:simbox-1

COMMAND EXECUTED

[08:40:58] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
ETH-3 Yes Eth-3 . . . . . . . . . . . . . . . . . . . 10 PCI ( 12)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . - PCI ( -)
CB-1 Yes 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . NONE
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 Yes No . . . . . . . . . . . . . . . . . . . NONE

229
Draft Simbox Draft

CODEC-1 Yes No . . . . . . . . . . . . . . . . . . . NONE

SIMEMU-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
SIMBOX-1 No No SimBox-1 . . . . . . . . . . . . . . . NONE

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

The following command is useful to enable the Simbox device.

[09:29:12] ABILIS_CPX:s p simbox-1 act:yes

COMMAND EXECUTED

[09:29:32] ABILIS_CPX:d p simbox-1

RES:SimBox-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------

------------------------------------------------------------------------
DESCR:
LOG:NO ACT:YES mxps:512
RSIM-RES:NONE
RSIM-PWD:

Caution
The resource must be initialized using init res:simbox-1.

The default parameters are sufficient to make the device working properly.At most a password may be configured to protect
the access, but of course the same password must be used in all UMTS-BOX2 which need to connect to the SIMBOX.

Tip
Interesting chapter:

Section 2.10.2, “UMTS-BOX2”;

Section 2.10.6, “Simbox”.

Use the classic Abilis CPX commands syntax to set the password (RSIM-PWD parameter):

[09:41:23] ABILIS_CPX:s p simbox-1 rsim-pwd:abilis

COMMAND EXECUTED

[09:41:32] ABILIS_CPX:d p simbox-1

RES:SimBox-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------

------------------------------------------------------------------------
DESCR:
LOG:NO ACT:YES mxps:512
RSIM-RES:NONE
RSIM-PWD:********

230
Draft Simbox Draft

Caution
The resource must be initialized using init res:simbox-1.

The following are the simbox device parameters:

[09:39:44] ABILIS_CPX:d p simbox ?

SimBox resource parameter(s):

DESCR: Resource description [Max. 80 aphanumeric extended characters]

LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E]
(D: Debug Log; S: System Log; A: Alarm view; L: Local audible alarm;
T: SNMP traps; +E: Extended Log of state changes, see ref. manual)
ACT: Operation activation [NO, YES]
mxps: Maximal packet size in the packet exchange with RSIM [300..2048]
RSIM-RES: RSim resource [NONE, RSim-XXX]
RSIM-PWD: Password required to access this SIMBOX. From 0 up to 32 ASCII
printable characters. Spaces are not allowed. Case is preserved.

12.3. Connecting UMTS-BOX2 to Simbox

The first step to connect UMTS-BOX2 to Simbox is to add and configure the RSIM resource. One RSIM resource can be use
by more than one UMTS-BOX/SIMBOX so:

• one or more SIMBOX can “LISTEN” on an RSIM resource

• one or more UMTS-BOX2 can “CALL” through an RSIM resource

Add the resource and activate it:

[23:34:16] ABILIS_CPX:a res:rsim-1

COMMAND EXECUTED

[23:36:30] ABILIS_CPX:s p rsim-1 act:yes

COMMAND EXECUTED

[23:36:56] ABILIS_CPX:d p rsim-1

RES:RSim-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
DESCR:
LOG:NO ACT:YES
mxps:512 sesnum:64 sess-buf:3 udp-locport:60000 TOS:0-N
RP1-DLY:100 RP2-DLY:200 ACK-TOUT:2000 MAX-RETRY:2
POLLTIME:60
- Server ---------------------------------------------------------------
IP-FILTER:*
- Client ---------------------------------------------------------------
SRCADD:R-ID (192.168.000.201)

Remember to save the configuration1 and that on a working Abilis, a system restart2 is required. Below there's a short
description of the most important parameters:

[23:38:04] ABILIS_CPX:d p rsim ?

RSim resource parameter(s):

DESCR: Resource description [Max. 80 aphanumeric extended characters]

1
http://www.abilis.net/fileadmin/tutorial/en/ch05s11.html#ch.commands.save
2
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

231
Draft Simbox Draft

LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E]
(D: Debug Log; S: System Log; A: Alarm view; L: Local audible alarm;
T: SNMP traps; +E: Extended Log of state changes, see ref. manual)
ACT: Operation activation [NO, YES]
mxps: Maximal size of packets exchanged with upper driver (UMTS or SIMBOX)
[300..2048]
sesnum: Number of sessions [1..250]
sess-buf: Number of buffers in each channel receiver [1..10]
udp-locport: Local UDP port [1..65535]
TOS: Type Of Service octet or Differentiated Services Field (DS):
-' p-t', i.e. PRECEDENCE and TOS values, where 'p' can be [0..7]
and 't' can be [N=None, D=Min. Delay, T=Max. Throughput, R=Max.
Reliability, C=Min. Monetary Cost]
- 'bbbbbb', i.e. DS value bit by bit, where 'b' can be [0, 1]
RP1-DLY: Time to wait between the first transmission and the first repetition
of a packet [NO, 50..1000 msec.]
RP2-DLY: Time to wait between the first and second repetition of a packet
[NO, 50..1000 msec.]
ACK-TOUT: Maximal time to wait for ACK after transmission of a packet
[1000..5000 msec.]
MAX-RETRY: Maximal number of consecutive retries when ACK-TOUT expires [0..5]
POLLTIME: Inactivity interval after which a POLL packet is sent [15..300 sec.]
---------- - Server -----------------------------------------------------------
IP-FILTER: IP addresses filter for incoming sessions [*, 1-126.x.x.x,
127.0.0.1, 128-223.x.x.x, 'list']
---------- - Client -----------------------------------------------------------
SRCADD: Source IP address used in outgoing requests [R-ID, OUT-IP,
1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]

Type on the CP the following commands to add the Simbox device and to activate it:

[21:37:08] ABILIS_CPX:a dev:simbox-1

COMMAND EXECUTED

[21:37:19] ABILIS_CPX:d dev

...
------------------ Active USB Devices and Physical Resources: -----------------
Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
...
SIMBOX-1 Yes No SimBox-1 . . . . . . . . . . . . . . . 1.2
...

[21:39:13] ABILIS_CPX:s p simbox-1 act:yes

Remember to save the configuration3 and that on a working Abilis, a system restart4 is required

Use the below command to view the configuration of the resource.

[18:37:07] ABILIS_CPX:d p simbox-1

RES:SimBox-1 ------------------------------------------------------------------
Run DESCR:
LOG:NO ACT:YES mxps:512
RSIM-RES:NONE
RSIM-PWD:

Now the parameter RSIM-RES must be configured to use the rsim resource activated above.

[23:46:32] ABILIS_CPX:s p simbox rsim-res:rsim-1

3
http://www.abilis.net/fileadmin/tutorial/en/ch05s11.html#ch.commands.save
4
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

232
Draft Simbox Draft

COMMAND EXECUTED

[23:46:48] ABILIS_CPX:d p simbox-1

RES:SimBox-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------

------------------------------------------------------------------------
DESCR:
LOG:NO ACT:NO mxps:512
RSIM-RES:RSim-1
RSIM-PWD:

Normally there's no need to change the default remaining parameters, at most a password can be set to protect access. Type s
p simbox-1 rsim-pwd:testpwd to set the word testpwd as password.

The same password must be used in all UMTS-BOX2 that need to connect to this Simbox (the parameter RSIM-PWD).
Remeber to save the configuration5 and to initialize the resource using init res:simbox-1

Assuming that:

• an UMTS-BOX2 is connected to Abilis

• the ctip resource to use is ctip 201

• the parameter RSIM is setted to PERMANENT

type the command s p ctip:201 rsim-simbox-id:1 to associate the UMTS-BOX2 to Simbox. Refer to UMTS-BOX2
remotization to learn more about UMTS-BOX2 configuration. Remeber to save the configuration6 and to initialize the
CTISYS resource using init res:ctisys.

12.4. UMTS-BOX2 sim remotization

Please, refer to chapter Section 11.5, “UMTS-BOX2 sim remotization” to have more information about this argument.

12.5. How to update Simbox firmware

Go to http://abilis.antek.it/downloads/firmwares/download.html and download the latest firmware.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

The Simbox firmware can be upgraded only if the current version is equal or greater than 8. Use the following command to
check the current version of firmware. In the example below firmware version is equal to 9.01.

[15:44:20] ABILIS_7.0:_d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 EHCI Virtual Root Hub 0.00 0
2 0000 On Time 0000 UHCI Virtual Root Hub 0.00 1
3 0000 On Time 0000 UHCI Virtual Root Hub 0.00 2
4 0000 On Time 0000 UHCI Virtual Root Hub 0.00 3
5 04D8 Abilis 000C USB SIM-BOX 9.01 3.0

[15:44:26] ABILIS_7.0:_

Add the BLUSB device typing the following command and then restart abilis7.

5
http://www.abilis.net/fileadmin/tutorial/en/ch05s11.html#ch.commands.save
6
http://www.abilis.net/fileadmin/tutorial/en/ch05s11.html#ch.commands.save
7
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

233
Draft Simbox Draft

[15:51:01] ABILIS_CPX:a dev:blusb-1

COMMAND EXECUTED

[15:51:11] ABILIS_CPX:warm start

Updating steps:

• Upload the file simbox.bin into the execution version directory (for example c:\7-0-2) without changing the file name. The
upload can be done using the file put command8 or the FTP resource9.

• use the command usbdev fw upload id:xx, where xx stands for the ID of the “USB SIM-BOX” (5 in the example above).

The updating procedure can last for minutes and the result can be displayed typing D L.

Caution
In case of failure of updating procedure, the previous version of firmware can be restored unplugging and
plugging in the usb cable of Simbox.

234
Draft Draft

Chapter 13. Citobox

Luigi Demuro

Table of Contents
13.1. Citobox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.2. Citobox and GPIO devices activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
13.3. CTI port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
13.4. CTI routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
13.4.1. CTI Routing table configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
13.5. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.1. Citobox diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.5.2. Citobox Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.6. How to update Citobox firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

13.1. Citobox
Citobox allows to connect Abilis to a doorphone system integrating it with your computer telephony system. The connection
between Abilis and Citobox is done via USB cable. Citobox activation is based on two devices: CITOBOX and GPIO.

Tip
Interesting chapters:

Section 2.10.5, “Citobox”;

Section 3.8, “Citobox connection”.

13.2. Citobox and GPIO devices activation

Add the CB fake card with the command:

[12:56:09] ABILIS_CPX:a dev:cb-1

COMMAND EXECUTED

[12:57:03] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 15 PCI ( 9)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 14 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 12 PCI ( 7)
CB-1 No 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

Add the citobox and GPIO devices to abilis using the following commands. The devices status shows now two CTIP in the
range 241 .. 248.

[21:36:02] ABILIS_CPX:A DEV:CITOBOX-1

COMMAND EXECUTED

235
Draft Citobox Draft

[21:36:12] ABILIS_CPX:A DEV:GPIO-1

COMMAND EXECUTED

[21:37:19] ABILIS_CPX:d dev

...
------------------ Active USB Devices and Physical Resources: -----------------
Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
GPIO-1 Yes Yes Gpio-1 . . . . . . . . . . . . . . . . 0.3.0
CITOBOX-1 241..242 . . . . . . . . . . . . . . .
CITO-1 Yes Yes . . . . . . . . . . . . . . . . . . . 0.3.2
AUDIO-1 Yes Yes . . . . . . . . . . . . . . . . . . . 0.3.1
...

Caution
Remember to save the configuration using save conf and that on a working Abilis, a system restart1 is
required.

Since Citobox appears as two devices (one Citobox and one GPIO which manages outputs), the GPIO device needs to be
configured setting it active with the command:

[11:43:22] ABILIS_CPX:_s p gpio-1 act:yes

COMMAND EXECUTED

[11:43:32] ABILIS_CPX:_d p gpio-1

RES:Gpio-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
DESCR:
LOG:NO ACT:YES LIVE-EXPIRY:10
- ePorter specific -----------------------------------------------------
GATE-WAIT-CONNECT:60 GATE-MAX-DURATION:300
FLAT-WAIT-CONNECT:60 FLAT-MAX-DURATION:300 FLAT-BELL-GUARD:2

Initialize the device and save the configuration with init res:gpio-1 and save conf.

GPIO resource allows to view the state of each digital input/output line and to read values from analog inputs.

[11:14:44] ABILIS_CPX:d d gpio

RES:Gpio-1 --------------------------------------------------------------------
STATE:UP USB-STATE:CONNECTED
- Digital Input Lines State --------------------------------------------
1..16| off off off off ON off off off off off . . . . . .
17..32| . . . . . . . . . . . . . . . .
33..48| . . . . . . . . . . . . . . . .
49..64| . . . . . . . . . . . . . . . .
------------------------------------------------------------------------
- Digital Output Lines State -------------------------------------------
1..16| off off off off off off off off off off off off off off off off
17..32| off off off off off off off off off off off off off off off off
33..48| off off off off off off . . . . . . . . . .
49..64| . . . . . . . . . . . . . . . .
------------------------------------------------------------------------
- Analog Input Lines State ---------------------------------------------
1.. 8| . . . . . . . .
9..16| . . . . . . . .
------------------------------------------------------------------------

236
Draft Citobox Draft

- Analog Input Lines Values --------------------------------------------

1.. 8| . . . . . . . .
9..16| . . . . . . . .
------------------------------------------------------------------------

13.3. CTI port configuration

Assuming that the cti port #241 has been added by the activation of citobox device, type d p ctip:241 ? to view a short
description of the most important parameters in the citobox section.

....

---------- CITOBOX ------------------------------------------------------------

MORE-BUTTONS: Digital input lines of additional buttons [1..8]. Line values
can be joined using ',' character or grouped using '-' character.
Lx-ON: DTMF code to set digital output [0..9, *, #, A..D] or empty
Lx-OFF: DTMF code to reset digital output [0..9, *, #, A..D] or empty
Lx-PULSE: DTMF code to make a pulse on digital output [0..9, *, #, A..D] or
empty
Lx-PULSE-T: Pulse duration on digital output [1..4294967295 ms]
Lx-PULSE-GAP: Gap duration on digital output [1..65535 ms]
CITO-GAIN-IN: Input gain adjustment [SYS, MUTE, -126..+32 dB]
CITO-GAIN-OUT: Output gain adjustment [SYS, MUTE, -59..+5 dB]
CITO-ES: Echo suppressor activation [SYS, NO, YES]
CITO-ES-RISE-OUT: Echo suppressor output line rise time [SYS, 0..1000 ms]
CITO-ES-FALL-OUT: Echo suppressor output line fall time [SYS, 0..1000 ms]
CITO-ES-THR-OUT: Echo suppressor output line threshold [SYS, -126..0 dB]

Tip
Interesting chapter: Section 42.2, “CTI Ports configuration”.

Example: additional ring buttons are connected to inputs 1,2,3,4, where the number assigned to the CTIP is 999901 (used as
calling number) and where DTMF 5 is used to drive an output which generates a 1 second pulse used to open the door.

[11:58:52] ABILIS_CPX:_s ctip:241 more-buttons:1,2,3,4 num:999901 l1-pulse:5

COMMAND EXECUTED

[12:00:00] ABILIS_CPX:_d p ctip:241

CTIP:241 - Not Saved (SAVE CONF)---------------------------------------------

Act DESCR:
card:CB-1<1>
OPSTATE:UP LOG:NO TYPE:USER
signalling:CITO
mode:CITO NUM:999901
MORE-BUTTONS:1,2,3,4
L1-ON: L1-OFF: L1-PULSE:5 L1-PULSE-T:1000 L1-PULSE-GAP:250
L2-ON: L2-OFF: L2-PULSE: L2-PULSE-T:1000 L2-PULSE-GAP:250
L3-ON: L3-OFF: L3-PULSE: L3-PULSE-T:1000 L3-PULSE-GAP:250
L4-ON: L4-OFF: L4-PULSE: L4-PULSE-T:1000 L4-PULSE-GAP:250
CITO-GAIN-IN:SYS CITO-GAIN-OUT:SYS
CITO-ES:SYS
CITO-ES-RISE-OUT:SYS CITO-ES-FALL-OUT:SYS CITO-ES-THR-OUT:SYS

[12:00:00] ABILIS_CPX:_d p ctip:241 ?

...
---------- CITOBOX ------------------------------------------------------------
MORE-BUTTONS: Digital input lines of additional buttons [1..8]. Line values
can be joined using ',' character or grouped using '-' character.

237
Draft Citobox Draft

Lx-ON: DTMF code to set digital output [0..9, *, #, A..D] or empty

Lx-OFF: DTMF code to reset digital output [0..9, *, #, A..D] or empty
Lx-PULSE: DTMF code to make a pulse on digital output [0..9, *, #, A..D] or
empty
Lx-PULSE-T: Pulse duration on digital output [1..4294967295 ms]
Lx-PULSE-GAP: Gap duration on digital output [1..65535 ms]
CITO-GAIN-IN: Input gain adjustment [SYS, MUTE, -126..+32 dB]
CITO-GAIN-OUT: Output gain adjustment [SYS, MUTE, -59..+5 dB]
CITO-ES: Echo suppressor activation [SYS, NO, YES]
CITO-ES-RISE-OUT: Echo suppressor output line rise time [SYS, 0..1000 ms]
CITO-ES-FALL-OUT: Echo suppressor output line fall time [SYS, 0..1000 ms]
CITO-ES-THR-OUT: Echo suppressor output line threshold [SYS, -126..0 dB]

Initialize the CTISYS resource with the command init res:ctisys and save the configuration.

A Citobox section is present in CTISYS:

[20:36:20] ABILIS_CPX:d p ctisys citobox

RES:CtiSys --------------------------------------------------------------------
Run DESCR:CTI_System_general_properties
- CITOBOX defaults -----------------------------------------------------
CITO-GAIN-IN:0 CITO-GAIN-OUT:0
CITO-ES:NO
CITO-ES-RISE-OUT:20 CITO-ES-FALL-OUT:200 CITO-ES-THR-OUT:-12

[20:37:39] ABILIS_CPX:_d p ctisys citobox ?

D P [RES:]CTISYS [<section>] Display parameter(s) of the CtiSys resource

<section> Display only parameters of the specified section <Optional>

[ROUTER, LCS, CALL, ADDRBOOK, EEC, DSP, AUDIO, POTS,
CELL, CITOBOX, HDLC, TONES, CLOCK]

CtiSys resource parameter(s):

CITO-GAIN-IN: Input gain adjustment [MUTE, -126..+32 dB]

CITO-GAIN-OUT: Output gain adjustment [MUTE, -59..+5 dB]
CITO-ES: Echo suppressor activation [NO, YES]
CITO-ES-RISE-OUT: Echo suppressor output line rise time [0..1000 ms]
CITO-ES-FALL-OUT: Echo suppressor output line fall time [0..1000 ms]
CITO-ES-THR-OUT: Echo suppressor output line threshold [-126..0 dB]

13.4. CTI routing configuration

Calls directed to Citobox can't be routed in transparent mode; internal clusters must be created and calls must be routed
through packet voice resources.

Note
DTMF can be simulated by means of subaddress called field (SD). Digital output can be driven using DTMF
tones. Configure the SD parameter of the rule which routes calls toward a Citobox CTIP port. Assigning
the string DTMF=x (x is the desired dtmf in range 0..9 and A..D) to the SD parameter. The call will not be
answered and will remain in ALERTING state. The call with be either dropped on T301 timeout or on abort
from caller.

Tip
Interesting chapters:

Section 42.6, “CTI Router”;

Section 42.4, “CTI Cluster”;

238
Draft Citobox Draft

Section 42.5, “CTI Link”.

13.4.1. CTI Routing table configuration

Assume that:

• Abilis has the following CTI ports configuration: ports 31 and 32 are toward the PBX, ports 33 and 34 toward the ISDN
(grouped as BRI4_ports) and ports 101/102/103/104/105 are used to connect POTS phones.

• internal clusters clus1 and clus2 are already created.

Type the following command to verify the ctig configuration:

[18:12:13] ABILIS_CPX:d ctig

--------------------------------------+--------------------+-------------------
[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
PBX_group
1 NO R ST |31 32 . . . |. . . . .
--------------------------------------+--------------------+-------------------
ISDN_line_group
2 NO R ST |33 34 . . . |. . . . .
--------------------------------------+--------------------+-------------------
POTS_phones
3 NO R ST |101 102 103 104 105 |. . . . .
--------------------------------------+--------------------+-------------------
...

Let's see some examples of CTIR configuration.

Tip
Interesting chapter: Section 42.6, “CTI Router”;

13.4.1.1. CTIR from Citobox to a group of POTS phones

The following routings allow to route calls coming from the external door phone toward the group 3 of pots phones.

[18:22:32] ABILIS_CPX:a ctir pr:1 type:ctov sr:clus1 poo:g3 cdi:* sdi:CITOBOX241 sp:64000

COMMAND EXECUTED

[18:22:56] ABILIS_CPX:a ctir pr:3 type:vtoc poi:241 ds:clus2 cdi:00 sdo:CITOBOX241 sp:64000

COMMAND EXECUTED

[18:23:40] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS

239
Draft Citobox Draft

|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * u*
-------------------------------------------------------------------------------
1 CtoV GSM1 G3 * *
NO ANY NO Dft * *
64000 Sys * * Sys Sys CITOBOX241 *
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 VtoC 241 GSM2 00 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * CITOBOX241
-------------------------------------------------------------------------------
...

The routing PR:3 routes calls coming from port 241 to internal cluster Clus2 introducing the label CITOBOX241 for SDO
parameter.

Tip
Interesting chapter: Section 42.6, “CTI Router”;

The routing PR:1 accepts calls from internal cluster Clus1 and forwards them to the group of POTS phones G3 only if SDI
parameter is equal to CITOBOX241. Using SDO/SDI parameters make the admin sure that the routing PR:1 catches calls
generated from PR:3.

Figure 13.1. CTIR from Citobox to pots phones

13.4.1.2. CTIR from Citobox to a remote cluster

Example: there is one Abilis which is connected to a Citobox (ABILIS_CPX1) and to a remote Abilis (ABILIS_CPX2). Let's
explain how to route a call from Citobox to a remote pots phone.

The following routing allows to route calls originated by the external door phone unit toward a remote cluster (e.g.
Abilis2).

[18:33:54] ABILIS_CPX1:a ctir pr:3 type:vtoc poi:241 ds:Abilis2 cdi:00 sdo:CITOBOX241

COMMAND EXECUTED

[18:34:38] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO

240
Draft Citobox Draft

|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO

| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 VtoC 241 Abilis2 00 *
NO ANY NO Dft * *
6400 Sys Sys Sys Sys Sys * CITOBOX241
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------

Obviously, the remote cluster must be correctly configured.

Tip
Interesting chapter:

Chapter 36, Tunneling proprietary protocols;

Section 42.6, “CTI Router”.

Add the following rule to the ctir of remote Abilis:

[10:29:28] ABILIS_CPX2:_a ctir pr:4 type:ctov sr:Abilis1 sdi:CITOBOX241 poo:pbx cdo:100

COMMAND EXECUTED

[10:30:02] ABILIS_CPX2:_d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 03/11/2010 10:30:02 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
4 CtoV Abilis1 PBX 00 100
NO ANY NO Dft * *
6400 Sys * * Sys Sys CITOBOX241 *
-------------------------------------------------------------------------------

This route catch a call incoming from remote cluster Abilis1 and route it to a pots phone whose number is 100. The figure
below shows the route of the call:

241
Draft Citobox Draft

Figure 13.2. Route of the call from citobox to remote Abilis

13.4.1.3. CTIR from Citobox to a mobile phone using UMTS BOX

The following routing is useful to route a call from Citobox to a mobile phone. See the chapter Chapter 11, GSM-UMTS BOX
to know how to connect and configure GSM/UMTS BOX.

Assume that ports 201 and 202 toward GSM/UMTS gateway:

[18:12:13] ABILIS_CPX:d ctig

ID: PICKUP: SCAN: RULE:
---------------------------+-------------------------+-------------------------
[DESCR:]
ID: SCAN: RULE: PICKUP: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
---------------------------+-------------------------+-------------------------
...
---------------------------+-------------------------+-------------------------
GSM_group
3 NO R ST |201 202 . . . |. . . . .
---------------------------+-------------------------+-------------------------

Warning
At this moment GSM or UMTS gateway supports only G.711 coder. Other codecs are supported by
transcoding through additional ISDN cards.

Assume to have internal clusters loop1 and loop2:

[11:12:33] ABILIS_CPX:_d cticl

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Clusters:4 Activated Clusters:16

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
...
-------------------------------------------------------------------------------
loop1 - DISABLE NO NONE PRIVATE

242
Draft Citobox Draft

[ 1] * NO
-------------------------------------------------------------------------------
loop2 - DISABLE NO NONE PRIVATE
[ 2] * NO
-------------------------------------------------------------------------------

[11:17:43] ABILIS_CPX:_d ctil

Configured Links:4 Activated Links:16

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 Pv-1 loop1 NOMAX NOMAX NONE
2 Pv-2 loop2 NOMAX NOMAX NONE
...

[15:00:09] ABILIS_CPX:d p pv-5

RES:Pv-5 - PV over IP (Abilis tunnel) (IP) ------------------------------------

Run DESCR:Internal_Cluster_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:3105 REMPORT:3106 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:192.168.000.201

[15:00:15] ABILIS_CPX:d p pv-6

RES:Pv-6 - PV over IP (Abilis tunnel) (IP) ------------------------------------

Run DESCR:Internal_Cluster_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:3106 REMPORT:3105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:192.168.000.201

Add the following rules to CTI routing table:

[11:22:45] ABILIS_CPX:_a ctir pr:4 type:vtoc poi:241 ds:loop1 sdo:CITOBOX241 sp:64000

COMMAND EXECUTED

[11:23:15] ABILIS_CPX:_a ctir pr:5 type:ctoc sr:loop2 ds:loop1 cdi:* sdi:CITOBOX241 SDO:CITOBOX2412

COMMAND EXECUTED

[11:25:22] ABILIS_CPX:_a ctir pr:6 type:ctov sr:loop2 poo:g3 sdi:CITOBOX2412 cdi:* coders:g.711 sp:

COMMAND EXECUTED

[11:31:02] ABILIS_CPX:_d ctire

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 03/11/2010 11:31:02 CET

243
Draft Citobox Draft

-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
PR:4 DESCR:
ACT:YES EDT:NO
TYPE:VtoC POI:241 DS:loop1 EEC:NO
NEXT:NO CDI:00 CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:CITOBOX241
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:Sys
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#
-------------------------------------------------------------------------------
PR:5 DESCR:
ACT:YES EDT:NO
TYPE:CtoC SR:loop2 DS:loop1 EEC:NO
NEXT:NO CDI:* CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:CITOBOX241 SDO:CITOBOX2412
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:* MJ:* ECM:Sys
CODERS:*
SPOUT:* SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:*
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#
-------------------------------------------------------------------------------
PR:6 DESCR:
ACT:YES EDT:NO
TYPE:CtoV SR:loop2 POO:G3 EEC:NO
NEXT:NO CDI:* CDO:32999999999
LAST:ANY CGI:* CGO:*
T301:Dft SDI:CITOBOX2412 SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:NO DJ:0 MJ:40 ECM:Sys
CODERS:G.711
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

The rule PR:4 route a call incoming from Citobox to internal cluster loop1 adding a label 'CITOBOX241' to SDI parameter.
Next rule (PR:5) route the call from internal cluster loop2 to loop1 keeping the SDO parameter equal to SDI one, while
rule number 6 accepts calls from internal cluster loop1 and forwards them to GSM/UMTS gateway.

Tip
Interesting chapter: Section 42.6, “CTI Router”;

The figure below shows the route of the call.

244
Draft Citobox Draft

Figure 13.3. Call routing from Citobox to UMTSBOX

13.5. Diagnostics and statistics

13.5.1. Citobox diagnostics
The following commands are used to display diagnostics:

d d ctip:n / d de ctip:n (where n is They inform about the overall state of the port (STATE), if the hot-pluggable device
241 or 242) is connected or not (CITO), the bandwidth of the AUDIO-CODEC ISO interface
(CODEC-ISO-BW), etc...

[15:11:05] ABILIS_CPX:_d de ctip:241

CTIP:241 ----------------------------------------------------------------------
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SG:] CD: [SD:]
------------------------------------------------------------------------
*** All channels disconnected ***
------------------------------------------------------------------------
STATE:DOWN AUDIO-ISO-BW:N/A
CITO:DISCONNECTED CITO-STATE:INIT CITO-ERR:UNKNOWN
AUDIO:DISCONNECTED AUDIO-STATE:INIT AUDIO-ERR:UNKNOWN

13.5.2. Citobox Statistics

The following commands are used to display statistics:

d s ctip:n / d se ctip:n (where n is Meaning of the most important statistics:

241 or 242)
CITO-CONN Number of USB connections

CITO-DISC Number of USB disconnections

CITO-OVR Number of USB receive overruns

CITO-UND Number of USB transmit underruns

CITO-RST Number of device restarts

AUDIO- Number of USB connections

CONN

AUDIO-DISC Number of USB disconnections

AUDIO- Number of USB receive overruns

OVR

AUDIO- Number of USB transmit underruns

UND

245
Draft Citobox Draft

AUDIO-RST Number of device restarts

CITO- Number of sent commands

CMD

CITO-RSP Number of received responses

CITO-IND Number of received indications

[15:14:43] ABILIS_CPX:_d s ctip:241

CTIP:241 ----------------------------------------------------------------------
--- Cleared 0 days 00:15:17 ago, on 11/03/2011 at 15:07:53 -------------
Layer 3 Q.931
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0|
------------------------------------------------------------------------
B-CHANNELs STATISTICs NOT AVAILABLE
D-CHANNELs STATISTICs NOT AVAILABLE
CITOBOX
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CITO-CONN | 0| |CITO-DISC | 0| |
CITO-PCK | 0| 0|CITO-OVR | 0| |
CITO-UND | | 0|CITO-RST | 0| |
AUDIO-CONN | 0| |AUDIO-DISC | 0| |
AUDIO-PCK | 0| 0|AUDIO-OVR | 0| |
AUDIO-UND | | 0|AUDIO-RST | 0| |
CITO-CMD | | 0|CITO-RSP | 0| |
CITO-IND | 0| |
------------------------------------------------------------------------

13.6. How to update Citobox firmware

Go to http://abilis.antek.it/downloads/firmwares/download.html and download the latest firmware.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

Citobox is composed of two devices: GPIO and Citobox. The correct procedure includes updating both GPIO and Citobox
firmwares.

The Citobox firmware can be upgraded only if the current version is equal or greater than 18. Use the following command
to check the current version of firmware. In the example below firmware version is equal to 19.01.

[15:44:20] ABILIS_7.0:_d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 EHCI Virtual Root Hub 0.00 0
2 0000 On Time 0000 UHCI Virtual Root Hub 0.00 1
3 0000 On Time 0000 UHCI Virtual Root Hub 0.00 2
4 0000 On Time 0000 UHCI Virtual Root Hub 0.00 3
5 0000 On Time 0000 UHCI Virtual Root Hub 0.00 4
6 04CC 1520 2.00 0.2
7 04CC 1520 2.00 0.3
8 04D8 Abilis 000C USB CITO-BOX - GPIO 19.01 0.2.0
9 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.2.1
10 08BB Burr-Brown from TI 2904 USB Audio CODEC 1.00 0.3.2

246
Draft Citobox Draft

11 04D8 Abilis 000C USB UMTS-BOX2 19.05 0.3.3

12 04D8 Abilis 000C USB CITO-BOX - CITO 19.01 0.2.2
13 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.0
14 05C6 SimTech , Incorporat 6000 SimTech HSDPA Modem 0.00 0.3.1

[15:44:26] ABILIS_7.0:_

Add the BLUSB device typing the following command and then restart abilis2.

[15:51:01] ABILIS_CPX:a dev:blusb-1

COMMAND EXECUTED

[15:51:11] ABILIS_CPX:warm start

Updating steps:

• Upload the files ctbgpio.bin and ctbcito.bin into the execution version directory (for example c:\7-0-2) without changing
the file name. The upload can be done using the file put command3 or the FTP resource4.

• use the command usbdev fw upload id:xx, where xx stands for the ID of the “USB CITO-BOX - GPIO” (8 in the example
above).

• use the command usbdev fw upload id:yy, where yy stands for the ID of the “USB CITO-BOX - CITO” (12 in the
example above).

The updating procedure can last for minutes and the result can be displayed typing D L.

Caution
In case of failure of updating procedure, the previous version of firmware can be restored unplugging and
plugging in the usb cable of Citobox.

2
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

247
Draft Draft

Chapter 14. RJS - RJ Switch

Luigi Demuro

Table of Contents
14.1. RJS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.2. RJS device activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
14.3. How to update RJS firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

14.1. RJS
This device is a switch of ISDN/ADSL/Ethernet lines which allows to manage up to 8 lines. The activation of the resource is
done through RJS device.

Tip
Interesting chapters:

Section 2.10.7, “RJ Switch”;

Section 3.10.1, “Connection examples”;

14.2. RJS device activation

Use the following command to add the device.

[09:33:26] ABILIS_CPX:a dev:rjs-1

COMMAND EXECUTED

[09:33:28] ABILIS_CPX:d dev

- Not Saved (SAVE CONF) -------------------------------------------------------

------------------ Active PCI Cards and Physical Resources: -------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
ASY-1 Yes Async-1 . . . . . . . . . . . . . . . . . . - 3F8 4
ETH-1 Yes Eth-1 . . . . . . . . . . . . . . . . . . . 9 PCI ( 5)
ETH-2 Yes Eth-2 . . . . . . . . . . . . . . . . . . . 8 PCI ( 10)
ETH-3 Yes Eth-3 . . . . . . . . . . . . . . . . . . . 10 PCI ( 12)
BRI4-1 Yes 31..34 . . . . . . . . . . . . . . . . . . . 12 PCI ( 10)
POTS-1 Yes 101..116 . . . . . . . . . . . . . . . . . . 11 PCI ( 9)
UG-1 Yes 201..232 . . . . . . . . . . . . . . . . . . - PCI ( -)
CB-1 Yes 241..248 . . . . . . . . . . . . . . . . . . - PCI ( -)

------------------ Active USB Devices and Physical Resources: -----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes No Adsl-1 . . . . . . . . . . . . . . . . NONE
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
CELL-2 Yes No . . . . . . . . . . . . . . . . . . . NONE
CODEC-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
SIMEMU-1 Yes No . . . . . . . . . . . . . . . . . . . NONE
RJS-1 No No Rjs-1 . . . . . . . . . . . . . . . . NONE

248
Draft RJS - RJ Switch Draft

----------------- Inactive PCI Cards and Physical Resources: ------------------

Card(s) Run Physical Resource(s) or CTI Port(s) SlotId Addr Irq
-------------------------------------------------------------------------------
*** NO INACTIVE PCI CARDs PRESENT ***

----------------- Inactive USB Devices and Physical Resources: ----------------

Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
*** NO INACTIVE USB DEVICEs PRESENT ***

Caution
After adding or setting the device active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

The following command is useful to enable the RJS device.

[09:37:23] ABILIS_CPX:s p rjs-1 act:yes

COMMAND EXECUTED

[09:37:51] ABILIS_CPX:init res:rjs-1

COMMAND EXECUTED

[09:37:55] ABILIS_CPX:d p rjs-1

RES:Rjs-1 ---------------------------------------------------------------------
Run DESCR:
LOG:NO ACT:YES LIVE-EXPIRY:120 REBOOT-PROTECTION:YES
L1:AUTO L1-DESCR:
L2:AUTO L2-DESCR:
L3:AUTO L3-DESCR:
L4:AUTO L4-DESCR:
L5:AUTO L5-DESCR:
L6:AUTO L6-DESCR:
L7:AUTO L7-DESCR:
L8:AUTO L8-DESCR:

Caution
The resource must be initialized using init res:rjs-1.

Tip
It's recommended to use a description for each line (Lx-DESCR parameters).

The most important parameters are:

[09:44:02] ABILIS_CPX:d p rjs-1 ?

Rjs resource parameter(s):

DESCR: Resource description [Max. 80 aphanumeric extended characters]

LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E]
(D: Debug Log; S: System Log; A: Alarm view; L: Local audible alarm;
T: SNMP traps; +E: Extended Log of state changes, see ref. manual)
ACT: Operation activation [NO, YES]
LIVE-EXPIRY: Expiry timeout programmed to RJ45 switch [10..600 sec]
REBOOT-PROTECTION: Avoid transition to BACKUP during a reboot [NO, YES]

249
Draft RJS - RJ Switch Draft

L1: Define state of Line 1 at boot or upon INIT [AUTO, MAIN, BACKUP]
L1-DESCR: Description for Line 1. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L2: Define state of Line 2 at boot or upon INIT [AUTO, MAIN, BACKUP]
L2-DESCR: Description for Line 2. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L3: Define state of Line 3 at boot or upon INIT [AUTO, MAIN, BACKUP]
L3-DESCR: Description for Line 3. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L4: Define state of Line 4 at boot or upon INIT [AUTO, MAIN, BACKUP]
L4-DESCR: Description for Line 4. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L5: Define state of Line 5 at boot or upon INIT [AUTO, MAIN, BACKUP]
L5-DESCR: Description for Line 5. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L6: Define state of Line 6 at boot or upon INIT [AUTO, MAIN, BACKUP]
L6-DESCR: Description for Line 6. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L7: Define state of Line 7 at boot or upon INIT [AUTO, MAIN, BACKUP]
L7-DESCR: Description for Line 7. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.
L8: Define state of Line 8 at boot or upon INIT [AUTO, MAIN, BACKUP]
L8-DESCR: Description for Line 8. Up to 70 alphanumeric extended characters.
Spaces are not allowed, case is preserved.

The most important parameters are:

LIVE-EXPIRY How much time the live signals from the Abilis CPX must be absent prior to switch to BACKUP.
The default value of 120 seconds is intentionally large to avoid problematic flapping of the lines.

REBOOT-PROTECTION When you reboot the Abilis CPX, the live signal will disappear for the period needed to have the
Abilis functional again. In some cases this may take longer that LIVE-EXPIRY.

When REBOOT-PROTECTION:YES and WARM START or RESTART SYSTEM is done, a special signal is sent to RJ45
switch that temporary increase the LIVE-EXPIRY to 10 minutes. In this way the lines are not switched during a normal
system reboot.

Note
If the RJ45 switch is POWERED OFF all the lines are switched to BACKUP.

The lines can be configured independently via L1: to L8: parameters:

AUTO This is the normal way. The line is switched to BACKUP when the RJ45 box is not driven (e.g. Abilis powered
off), and switched to MAIN when the RJ45 box is driven.

MAIN Line is forced to MAIN as soon as the RJS is powered on, and will stay MAIN.

BACKUP Line is forced to BACKUP as soon as the RJS is powered on, and will stay BACKUP.

The state of the lines can be temporary forced using the S S RES:RJS-x Lx:AUTO | MAIN | BACKUP | DEFAULT
command.

14.3. How to update RJS firmware

Go to http://abilis.antek.it/downloads/firmwares/download.html and download the latest firmware.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

The RJS firmware can be upgraded only if the current version is equal or greater than 12. Use the following command to
check the current version of firmware. In the example below firmware version is equal to 8.01.

250
Draft RJS - RJ Switch Draft

[15:44:20] ABILIS_7.0:_d usbdev

USB Server Overview:

ID VendorId/Manufacturer ProductId/Product Ver UsbPortId

-------------------------------------------------------------------------------
1 0000 On Time 0000 EHCI Virtual Root Hub 0.00 0
2 0000 On Time 0000 EHCI Virtual Root Hub 0.00 1
3 0000 On Time 0000 UHCI Virtual Root Hub 0.00 2
4 0000 On Time 0000 UHCI Virtual Root Hub 0.00 3
5 0000 On Time 0000 UHCI Virtual Root Hub 0.00 4
6 0000 On Time 0000 UHCI Virtual Root Hub 0.00 5
7 0000 On Time 0000 UHCI Virtual Root Hub 0.00 6
8 04D8 Abilis 000C RJ45 SwitchBoard 8.01 3.0

[15:44:26] ABILIS_7.0:_

Add the BLUSB device typing the following command and then restart abilis1.

[15:51:01] ABILIS_CPX:a dev:blusb-1

COMMAND EXECUTED

[15:51:11] ABILIS_CPX:warm start

Updating steps:

• Upload the file rjs.bin into the execution version directory (for example c:\7-0-2) without changing the file name. The
upload can be done using the file put command2 or the FTP resource3.

• use the command usbdev fw upload id:xx, where xx stands for the ID of the “SwitchBoard” (8 in the example above).

The updating procedure can last for minutes and the result can be displayed typing D L.

Caution
In case of failure of updating procedure, the previous version of firmware can be restored unplugging and
plugging in the usb cable of RJS.

1
http://www.abilis.net/fileadmin/tutorial/en/ch36s07.html

251
Draft Draft

Chapter 15. UMTS Key

Luigi Demuro

Table of Contents
15.1. UMTS Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

15.1. UMTS Key

This driver allows to exchange data and sms using an UMTS key.

The activation of UMTSKEY device on Abilis is needed to use UMTS-Key. Type the following command on the CP. This
will create a CTIP port which overlaps with those created with the CELLBOX.

[21:37:08] ABILIS_CPX:a dev:umtskey-1

COMMAND EXECUTED

[17:30:14] ABILIS_CPX:d ctip:201

CTIP:201 DESCR:
Act card:UG-1<1>
Run OPSTATE:UP LOG:NO TYPE:NET-PUBLIC
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:
RSIM:NO

The configuration is the same of the CELLBOX.

Tip
Interesting chapter: Section 53.17, “How to configure DATA CALL BACK using an UMTS Key, calling an
ISDN number”.

252
Draft Draft

Part III. Software resources

Draft Draft

Table of Contents
16. CP - Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1. CP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.1. Access levels to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.2. CP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2. CP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.1. CP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.2. CP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
16.2.3. CP sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3. Connecting to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3.1. Connecting through a TCP/IP network using TELNET/SSH protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3.2. Connecting through the serials-asynchronous ports of the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
17. TELNET - TELecommunication NETwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.1. TELNET resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.1.1. TELNET resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.2. TELNET diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.1. TELNET diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.2. TELNET statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.3. TELNET session status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
17.3. TELNET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
17.3.1. TELNET from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
18. SSH - Secure SHell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1. SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.1. Activating the SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.2. SSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.2. SSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.1. SSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.2. SSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.3. SSH sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
18.3. SSH commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
18.3.1. SSH from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
19. IPRTR - IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
19.1. IPRTR resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
19.1.1. IPRTR resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2. IP Routings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2.1. D IPR (Display IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
19.2.2. A IPR (Add IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
19.2.3. C IPR (Clear IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.4. S IPR (Set IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.5. IP Source Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
19.3. IP Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.1. D P IP (Display Parameter IP resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.2. A RES:IP (Add IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
19.3.3. C RES:IP (Clear IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
19.3.4. S P IP (Set Parameter IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
19.3.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
19.4. Administrative Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.1. D IPAD (Display IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.2. A IPAD (Add IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.3. C IPAD (Clear IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
19.4.4. S IPAD (Set IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5. IP Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.1. D IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.2. A IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.3. C IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
19.5.4. S IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6. IPRTR diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.1. IPRTR diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.2. IPRTR statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
19.7. IPFLOW Tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

254
Draft Software resources Draft

19.7.1. List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

19.7.2. Activating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
19.7.3. Deactivating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.4. Starting the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.5. Stopping the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.6. Display of IPFLOW parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.7. Setting IP packet filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
19.7.8. IPFLOW trace display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
20. NAT - Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1. NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.1. Frequently used expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.2. Activating the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
20.1.3. NAT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
20.2. NAT Aliases table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.1. D NAT (Display NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.2. A NAT (Add NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
20.2.3. C NAT (C NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
20.2.4. S NAT (Set NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
20.2.5. M NAT (Move NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
20.2.6. INIT RES:NAT and INIT NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
20.3. NAT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.1. NAT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.2. NAT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.3. Debug of the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
20.4. Examples of NAT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.1. Suggest an access from inside workstations to outside networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.2. Suggest an access from outside networks to internal servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
20.4.3. Configuring a DMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
21. IPSH - IP Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.1. IPSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.1.1. IPSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.2. IP Flow table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.1. D IPSH FLOW (Display IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.2. A IPSH FLOW (Add IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.3. C IPSH FLOW (Clear IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.4. S IPSH FLOW (Set IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3. IP Rule table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3.1. D IPSH RULE (Display IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
21.3.2. A IPSH RULE (Add IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.3. C IPSH RULE (Clear IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.4. S IPSH RULE (Set IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4. IP User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4.1. D IPSH USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.5. IPSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.1. IPSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.2. IPSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
22. IPACL - IP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
22.1. IP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
22.1.1. TOS (Type Of Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.1.2. Activating IPACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.2. IPACL management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
22.2.1. D IPACL (Display IP Access Control List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
22.2.2. A IPACL (Add IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
22.2.3. C IPACL (Clear IP Acces Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
22.2.4. S IPACL (Set IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
22.2.5. M IPACL (Move IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
22.2.6. F IPACL (Find IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
22.3. Examples of IPACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.1. IP packets blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.2. Giving High Priority to VoIP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
23. RIP - Routing Information Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1. RIP Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

255
Draft Software resources Draft

23.1.1. Activating the RIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

23.1.2. RIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
23.2. RIP External Routes filter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
23.2.1. D RIP EXTERNAL (Display RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.2. A RIP EXTERNAL (Add RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.3. C RIP EXTERNAL (Clear RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.4. S RIP EXTERNAL (Set RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3. RIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.1. RIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.2. RIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4. Examples of RIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4.1. Activation of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
23.4.2. Configuration of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
23.4.3. Configuration of IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
23.4.4. Configuration of IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
23.4.5. Display IP routing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
24. VRRP - Virtual Router Redundancy Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1. VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.1. Activating the VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.2. VRRP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.2. VRRP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.3. VRRP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.1. VRRP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.2. VRRP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.4. Examples of VRRP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.1. One-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.2. Load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
24.4.3. Multiple Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
24.4.4. Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
24.4.5. Virtual Routers Without Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
24.4.6. One Backup Protecting Two Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
24.4.7. Virtual Routers With Multiple IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
24.4.8. Two-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
25. DHCP - Dynamic Host Configuration Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1. DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.1. Activating DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.2. DHCP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
25.2. DHCP Relay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3. DHCP Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3.1. DHCP Server tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
25.3.2. Example of configuration of DHCP in Server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
25.3.3. DHCP bindings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
25.4. DHCP diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.1. DHCP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.2. DHCP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
25.4.3. DHCP debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5. DHCPC resource (DHCP Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.1. Activating DHCPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.2. DHCPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
25.5.3. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
26. DNS - Domain Name System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1. DNS Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.1. Activating the DNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.2. DNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
26.2. DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3. DNS Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3.1. Appendix - How DNS relay works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4. DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.1. DNS Resource as Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.2. DNS Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
26.4.3. DNS Resolver Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
26.5. DNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

256
Draft Software resources Draft

26.5.1. DNS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

26.5.2. DNS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
27. DDNS - Dynamic DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1. Dynamic DNS (DDNS) resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.1. Activating the DDNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.2. DDNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
27.1.3. DDNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
28. SMTP - Simple Mail Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1. SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.1. Activating the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.2. SMTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.2. Example of configuration of the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
28.3. SMTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
28.3.1. SMTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
28.3.2. SMTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
29. SNTP - Simple Network Time Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1. SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.1. Activating the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.2. SNTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
29.2. Examples of SNTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.1. SNTP client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.2. SNTP server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.3. SNTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.1. SNTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.2. SNTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
30. ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1. ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.1. Activating the ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.2. ALARM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.3. The ALARM table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
30.1.4. ALARM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
31. UPNP - Universal Plug and Play . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.1. UPNPS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.2. UPNPS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.3. UPNPS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
31.4. How to configure UPNP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
32. FTP - File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1. FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.1. Activating the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.2. FTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
32.2. FTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.2. FTP Virtual Root Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.2.3. FTP Virtual Paths Access Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.3. FTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.1. FTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.2. FTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.4. Example of FTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.1. Configuring the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.2. Activating the user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.3. Creating the virtual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.4. Giving access rights to user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
32.4.5. Connecting to Abilis FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
32.4.6. Access to the system version directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
33. TFTP - Trivial File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1. TFTP - Trivial File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.1. Activating the TFTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.2. TFTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
33.2. TFTP diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.1. TFTP diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.2. TFTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
34. HTTP - HyperText Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

257
Draft Software resources Draft

34.1. HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457

34.1.1. Activating the HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1.2. HTTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
34.2. HTTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.2. HTTP Virtual Root Paths Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.2.3. HTTP Virtual Paths Access Rights Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.3. HTTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.1. HTTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.2. HTTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.4. HTTPS (HTTP over SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
34.4.1. Activating the SSL resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
34.4.2. HTTP resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
34.4.3. Connecting to Abilis using HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
34.5. Appendix - HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
35. SYSLOG - The syslog protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.1. SYSLOG resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.2. SYSLOG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.3. SYSLOG diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
35.4. SYSLOG messages codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5. Win2k SYSLOG server implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.1. Kiwi SYSLOG Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.2. KLog win2k SYSLOG server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
35.6. Rsyslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
35.6.1. Rsyslog configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.2. Syslog resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.3. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7.1. SYSLOG architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
36. Tunneling proprietary protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
36.1. Tunneling proprietary protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
36.1.1. Link check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
36.2. Configuring Packet Voice tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.1. Packet Voice over IP- Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.2. IP Packet Voice - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
36.2.3. IP-BCK Packet Voice - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
36.2.4. IP Packet Voice - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
36.3. Configuring Abilis Ip Tunnels (AIPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
36.3.1. Abilis IP Tunnel over IP – Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
36.3.2. Abilis IP Tunnel over IP - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
36.3.3. Abilis IP Tunnel over IP - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
36.3.4. Abilis IP Tunnel over IP - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
36.4. Tunneling diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.1. Tunneling diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.2. Tunneling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
36.5. Appendix - LN2 parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
37. IPSEC - Internet Protocol SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.1. IPSEC - Internet Protocol SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.2. IPSEC Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.1. Activating the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.2. IPSEC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.3. IPSEC tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
37.3. IKE Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.1. Activating the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.2. IKE resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
37.3.3. IKE tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
37.4. IPSEC and IKE diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.1. IPSEC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.2. Statistics of the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.3. IKE diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.4.4. Statistics of the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.5. Example of IPSEC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

258
Draft Software resources Draft

37.5.1. Activating IPSEC parameter on the desired IP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538

37.5.2. Configuration of the Host connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
37.5.3. Configuration of the Client connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
37.5.4. Configuration of the Pre-shard Key table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
37.5.5. Outgoing IP resource for IPSEC packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
37.6. Appendix - IPSEC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
38. POEAC - PPP Over Ethernet Access Concentrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1. PoEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.1. Activating the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.2. POEAC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.2. PPP Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.3. POEAC diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
38.3.1. POEAC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
38.3.2. POEAC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
38.4. Example of POEAC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
38.4.1. Configuring the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.2. Configuring the IPRTR resource for DNS distribution to the clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.3. Activating and configuring the IP over PPP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
38.4.4. Activating and configuring the PPP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
38.5. Appendix - Point to Point protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
39. SNMP - Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1. SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.1. Activating the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.2. SNMP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
39.2. Example of configuration of the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3. SNMP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.1. SNMP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.2. SNMP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
39.4. SNMP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
39.5. Appendix - SNMP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
40. TRFA - Traffic Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1. TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.1. Activating the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.2. TRFA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.1.3. Activating the TRFA inside IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.2. TRFA diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.1. TRFA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.2. TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.3. TRFA debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3. Example of TRFA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.1. Configuring TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.2. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
40.3.3. Using HTTP for showing TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
41. LDAP - Lightweight Directory Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
41.1. LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
41.1.1. Activating the LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.1.2. LDAP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.2. LDAP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.1. User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.2. Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
41.3. LDAP use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.1. Publishing local VoIP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.2. Identifying the caller in a VoIP phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
41.3.3. Mail composing and LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
41.4. Handling contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.1. Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.2. LDAP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
41.5. LDAP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.1. LDAP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.2. LDAP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

259
Draft Draft

Chapter 16. CP - Control Port

Marco Bellesia

Table of Contents
16.1. CP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.1. Access levels to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
16.1.2. CP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2. CP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.1. CP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
16.2.2. CP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
16.2.3. CP sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3. Connecting to the Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3.1. Connecting through a TCP/IP network using TELNET/SSH protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
16.3.2. Connecting through the serials-asynchronous ports of the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

16.1. CP resource
The Control Port allows to access configuration and supervising functions. The Control Port is not a physic port, that is there
is no connector, but it is a “virtual” port of the Abilis CPX.

16.1.1. Access levels to the Control Port

It is possible to log into the Control Port by using three different privilege levels:

• User login level: “USER” is allowed to execute only some operations for supervising the Abilis CPX working mode; the
executon of “USER” not allowed commands will cause the message “COMMAND NOT ALLOWED FOR USER LOGIN
LEVEL” to be displayed.
• Administrator login level: “ADMINISTRATOR” is allowed, with some restrictions, to execute all the operations for
configuring and supervising the Abilis CPX; execution of “ADMINISTRATOR” not allowed commands will cause the
message “COMMAND NOT ALLOWED FOR ADMINISTRATOR LOGIN LEVEL” to be displayed.
• Super-User login level: SUPERUSER is able to completely manage the system.

Once the CP has been accessed, it is possible to check or modify the privilege level by using the command login.

Here is an example on how to access the Control Port through the telnet port, with USER privileges:

[192.168.0.1] TELNETS>00-CP
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Friday 14/01/2011 10:37:34 (UTC+1.00)
Logged as USER

[11:29:21] ABILIS_CPX:

The User is asked to specify the requested access level (USER, ADMINISTRATOR or SUPERUSER) and then to insert the
correspondent password. If the password is wrong, it will be asked again. After the third wrong try the connection will be
cleared.

[192.168.0.1] TELNETS>00-CP
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Friday 14/01/2011 10:39:29 (UTC+1.00)
Login:user
Password:

260
Draft CP - Control Port Draft

INVALID PASSWORD

Password:

INVALID PASSWORD

Password:

CLR F0 AE

[192.168.0.1] TELNETS>

16.1.2. CP resource parameters

The Control Port is identified by the mnemonic “CP”, correspondent to the Abilis CPX port 0 and it is provided with the
parameters described in this section.

Use the following command to show its parameters.

[11:09:16] ABILIS_CPX:d p cp

RES:Cp ------------------------------------------------------------------------
Run DESCR:Control_Port
LOG:NO PI:ABILIS_CPX: bsvc:3 ps:512
PWDU:**************** PWDA:**************** PWDS:****************
X29A:02010102010302040006050C010D000E000F011008111812121302
X29B:020100020003000402050006000700080009000A000C000D000E000F001500

Below are descriptions of the most important parameters:

LOG Logging functionalities activation/deactivation.

PI This parameter set the command interpreter prompt of the Control Port. Information about current local time
“[hh:mm:ss]” always precedes the user defined prompt. It is possible to use from 0 up to 16 ASCII characters
[33..126], spaces are not allowed. No differences between low and high case characters are made.

bsvc It sets the maximum number of connections that can be opened at the same time with the Control Port.

ps It sets the maximum size (in bytes) of packets to be sent or received.

PWD-U It sets the access password to the CP of the USER level. Once it is configured, the new password will be saved on
the Abilis CPX CF/HD, in a encrypted way, using the command save conf.

PWD-A It sets the access password to the CP of the ADMINISTRATOR level. Once it is configured, the new password will
be saved on the Abilis CPX disk, in a encrypted way, using the command save conf.

PWD-S It sets the access password to the CP of the SUPER-USER level. Once it is configured, the new password will be
saved on the Abilis CPX disk, in a encrypted way, using the command save conf.

The following command allows the administrator to change the configuration of the resource:

s p cp parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:cp;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

16.2. CP diagnostics and statistics

16.2.1. CP diagnostics
To display the diagnostics of the CP resource the following commands are used:

261
Draft CP - Control Port Draft

d d cp Shows the current state of the driver, the session privilege level actually in use and the current operative state of
the CP session (the last two parameters are shown only if the session is in the CONNECTED state).

d de cp Shows the same information displayed by d d cp command along with the last command typed.

[11:09:16] ABILIS_CPX:d d cp

RES:Cp ------------------------------------------------------------------------
Control_Port
STATE:UP
Ses State AccessLevel Action
------------------------------------------------------------------------
1 CONNECTED SUPERUSER COMMAND-MODE
2 READY
3 READY

[11:09:16] ABILIS_CPX:d de cp

RES:Cp ------------------------------------------------------------------------
Control_Port
STATE:UP
Ses State AccessLevel Action
[Last Command]
------------------------------------------------------------------------
1 CONNECTED SUPERUSER COMMAND-MODE
d de cp
2 READY
3 READY

16.2.2. CP statistics
To display the statistics of the CP resource the following commands are used:

d s cp Shows the number of data segments sent/received and the number of characters sent/received.

d se cp Shows statistic information in an extended format: the same information listed for d s cp command are shown
for each session.

[11:09:16] ABILIS_CPX:d s cp

RES:Cp ------------------------------------------------------------------------
Control_Port
--- Cleared 0 days 00:47:57 ago, on 14/01/2011 at 09:52:54 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 200| 17|CHAR | 10738| 105|
------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d se cp

RES:Cp ------------------------------------------------------------------------
Control_Port
--- Cleared 0 days 00:48:50 ago, on 14/01/2011 at 09:52:55 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 209| 18|CHAR | 11252| 113|
------------------------------------------------------------------------
- Sessions statistics --------------------------------------------------
Ses:1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 209| 18|CHAR | 11252| 113|
------------------------------------------------------------------------
Ses:2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
------------------------------------------------------------------------

262
Draft CP - Control Port Draft

Ses:3
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
------------------------------------------------------------------------

16.2.3. CP sessions status

To display the communication sessions status for the CP resource the following commands are used:

d c cp Shows the current state of sessions.

d ce cp Shows the current state of sessions in extended format.

[11:09:16] ABILIS_CPX:d c cp

Res: Ses: State: Clr:/Res: Ses: [Cg:/Cd:] Id:/Pr:

-------------------------------------------------------------------------------
Cp 1 CONN FROM Ssh 4 0
2 UP 00,00
3 UP F0,B0
-------------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d ce cp

RES:Cp
SES:1 CONN FROM RES:Ssh SES:4
CG: CD:00 PID:01000000 UD:CP
SES:2 UP CLR:00,00
SES:3 UP CLR:F0,B0

16.3. Connecting to the Control Port

The Control Port can be reached in the following ways:

• through a TCP/IP network using TELNET or SSH protocols;

• through the serials-asynchronous ports of the Abilis.

16.3.1. Connecting through a TCP/IP network using TELNET/SSH

protocols
In this case it is possible to use a personal computer provided with a TELNET (or SSH) client program.

The TELNET (or SSH) Client application makes a TCP/IP call to the Abilis CPX IP address. The TELNET (or SSH)
Server of the Abilis CPX receives the call, establishes the TCP connection, calls the Control Port and sends back the packet
containing the configured prompt (for example ABILIS_CPX:).

Note
This is the default auto-connection procedure. Refer to Section 17.1.1, “TELNET resource parameters” to
learn to configure telnet server.

COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Friday 14/01/2011 10:45:43 (UTC+1.00)
Logged as SUPERUSER

[11:29:21] ABILIS_CPX:

The Control Port needs at least one X.25 routing to be reached: the default X.25 routing table has got a routing (PR:0) for
connection to the Control Port.

[11:56:53] ABILIS_CPX:d r

263
Draft CP - Control Port Draft

---+--------+--------+---------------+---------------+------------+------------
PR |IN |OUT |CDI |CDO |UDI |UDO
|NEXT |CGI |CGO |PIDI |PIDO
| |IPSRC |IPDEST |FFO
-------------------------------------------------------------------------------
0 * Cp * * CP *
-------------------------------------------------------------------------------

16.3.2. Connecting through the serials-asynchronous ports of the

Abilis
In this case it is possible to use an asynchronous VT100 terminal or a personal computer provided with an emulation program
(TTY or VT100 or similar) connected to the serials-asynchronous ports of the Abilis with a cross-serial cable.

Parameters to use for the serial port:

• 9600 bit/sec;

• 8 bit;

• 1 stop bit;

• no parity check;

• no flow control.

Steps to follow:

• press the key <Enter> to get the PAD local port prompt, after switching on the terminal;

• digit 00-CP and the command interpreter of the local CPX Control Port will appear.

Tip
Interesting chapter:

Section 17.3, “TELNET commands”;

Section 18.3, “SSH commands”.

264
Draft Draft

Chapter 17. TELNET -

TELecommunication NETwork
Nicola Trevisani
Tomáš Klinkovský
Marco Bellesia
Luigi Demuro

Table of Contents
17.1. TELNET resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.1.1. TELNET resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
17.2. TELNET diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.1. TELNET diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.2. TELNET statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
17.2.3. TELNET session status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
17.3. TELNET commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
17.3.1. TELNET from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

17.1. TELNET resource

The Abilis CPX TELNET resource includes telnet server and client and it's present in the default configuration. It can be
used for remote CPX management or to establish connections to remote devices which support the same protocol (i.e. other
routers).

17.1.1. TELNET resource parameters

Use d p telnet command to display the parameters of the resource. By typing d p telnet ? command it is possible to display
the meaning of all parameters.

[16:55:28] ABILIS_CPX:d p telnet

RES:Telnet --------------------------------------------------------------------
DESCR:Telnet_Server_and_Client_entities
LOG:NO MCAU:NO ps:128
KEEPALIVE:30
- Server ---------------------------------------------------------------
tcpport:23 PSER:TELNETS> ser:3
AC:YES PWD: DT:15
CDO:00 UDO:CP PROFILE:NORMAL
IPSRC:* IPSRCLIST:#
- Client ---------------------------------------------------------------
PCLI:TELNETC> cli:3
CDI:* UDI:*

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

KEEPALIVE Activates and sets the value of the “Keep-Alive” time-out; the “Keep-Alive” procedure, by sending the
simple packets, keeps the TCP connection “alive” even if any data is not exchanged.

PSER The prompt of the commands interpreter of the Server TELNET resource.

265
Draft TELNET - TELecommunication NETwork Draft

ser Number of Server processes on the TELNET resource.

AC Autoconnection mode for the TELNET Server; the default value is YES. The TELNET Server automatically
generates a connection request, using information configured in CDO and UDO, whenever it receives a login
request from a Client TELNET process.

PWD The TELNET Server password, which is asked at connection.

DT Idle time interval (in minutes) after which the connection is closed.

CDO Called address field of the TELNET Server outgoing call. The parameter's default value (CDO:00).

UDO User data field of the TELNET Server outgoing call. The parameter's default value (CDO:CP).

IPSRC IP address of enabled source TELNET Client systems.

IPSRCLIST A list of IP addresses of enabled TELNET Client systems.

PCLI The prompt of the command interpreter of the Client TELNET resource.

cli Number of Client processes on the TELNET resource.

CDI Called address field of the TELNET Client incoming call.

UDI User data field of the TELNET Client incoming call.

The following command allows the administrator to change the configuration of the resource:

s p telnet parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:telnet; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

17.2. TELNET diagnostics and statistics

17.2.1. TELNET diagnostics
To display the diagnostics of the TELNET resource the following commands are used:

d d telnet / d de telnet Shows diagnostic information, such as the state of the client and server, the local and
the remote addresses-ports connected to the resource, etc..

[17:58:20] ABILIS_CPX:d d telnet

RES:Telnet --------------------------------------------------------------------
Telnet_Server_and_Client_entities
STATE:READY
- Telnet Channels ------------------------------------------------------
CH TYPE X25-State TCP-State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CLNT READY READY
2 CLNT READY READY
3 CLNT READY READY
4 SERV CONNECTED CONNECTED 192.168.000.251-23 192.168.000.029-3113
5 SERV READY LISTEN 000.000.000.000-23
6 SERV READY LISTEN 000.000.000.000-23

17.2.2. TELNET statistics

To display the statistics of the TELNET resource the following commands are used:

d s telnet Shows statistic information, such as number of segments received/sent, number of characters received/
sent, number of packets received/sent, number of calls sent/received and number of resets sent/received.

d se telnet Shows statistic information in an extended format: the same information listed for d s telnet command are
shown for each session.

266
Draft TELNET - TELecommunication NETwork Draft

[18:06:18] ABILIS_CPX:d s telnet

RES:Telnet --------------------------------------------------------------------
Telnet_Server_and_Client_entities
--- Cleared 009:23:37:23 ago, on 20/10/2006 at 18:29:17 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 710| 89|CHAR | 41057| 829|
PCK | 181| 88|CALL | 3| 26|
RESET | 0| 0|
------------------------------------------------------------------------

[18:06:40] ABILIS_CPX:d se telnet

RES:Telnet --------------------------------------------------------------------
Telnet_Server_and_Client_entities
--- Cleared 009:23:37:32 ago, on 20/10/2006 at 18:29:17 ----------------
- Telnet Channels ------------------------------------------------------
CH TYPE X25-State TCP-State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 11| 48|CHAR | 44| 258|
PCK | 11| 48|CALL | 3| 0|
RESET | 0| 0|
------------------------------------------------------------------------
2 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
3 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
4 SERV CONNECTED CONNECTED 192.168.000.251-23 192.168.000.029-3113
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 376| 22|CHAR | 22301| 332|
PCK | 85| 22|CALL | 0| 9|
RESET | 0| 0|
------------------------------------------------------------------------
5 SERV READY LISTEN 000.000.000.000-23
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 260| 14|CHAR | 15251| 146|
PCK | 66| 14|CALL | 0| 8|
RESET | 0| 0|
------------------------------------------------------------------------
6 SERV READY LISTEN 000.000.000.000-23
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 74| 6|CHAR | 4104| 105|
PCK | 22| 5|CALL | 0| 9|
RESET | 0| 0|
------------------------------------------------------------------------

17.2.3. TELNET session status

To display the communication sessions status for the TELNET resource the following commands are used:

d c telnet Shows the current state of sessions.

d ce telnet Shows the current state of sessions in extended format.

267
Draft TELNET - TELecommunication NETwork Draft

[11:09:16] ABILIS_CPX:d c telnet

Res: Ses: State: Clr:/Res: Ses: [Cg:/Cd:] Id:/Pr:

-------------------------------------------------------------------------------
Telnet 1 UP F0,B0
2 UP F0,B0
3 CONN TO Cp 1 00 0
4 UP F0,D0
5 UP 00,00
6 UP F0,D0
-------------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d ce telnet

RES:Telnet
SES:1 UP CLR:F0,B0
SES:2 UP CLR:F0,B0
SES:3 CONN TO RES:Cp SES:1
CG: CD:00 PID:01000000 UD:CP
IPSRC:192.168.000.025
SES:4 UP CLR:F0,D0
SES:5 UP CLR:00,00
SES:6 UP CLR:F0,D0

17.3. TELNET commands

While the TELNET Server process is running, the User can access the TELNET resource commands by pressing the
combination Ctrl+P.

As a consequence of this action, the prompt of the TELNET Server, configured in the parameter PSER , will be displayed.

The user can leave the command exchange procedure and start the data exchange one by pressing again the combination
Ctrl+P.

The available commands for the command interpreter of the TELNET resource are:

open This command, available only on TELNET client processes, allows the User to open a connection with
the TELNET Server process, hosting on the remote equipment identified by the specified IP.

close / exit It requests the session to be closed.

clr It requests the session to be closed.

17.3.1. TELNET from Abilis to Abilis

To open a TELNET session from an Abilis to another Abilis, the X.25 routing must be properly configured. Both Abilis must
have the follwing X.25 routings:

268
Draft TELNET - TELecommunication NETwork Draft

Example 17.1. X.25 routing

[10:38:01] ABILIS_CPX:a r pr:1 in:telnet out:telnet cdi:* udi:tln

COMMAND EXECUTED

[10:38:04] ABILIS_CPX:a r pr:2 in:* out:telnet cdi:* udi:tln

COMMAND EXECUTED

[10:38:36] ABILIS_CPX:d r

---+--------+--------+---------------+---------------+------------+------------
PR |IN |OUT |CDI |CDO |UDI |UDO
|NEXT |CGI |CGO |PIDI |PIDO
| |IPSRC |IPDEST |FFO
-------------------------------------------------------------------------------
0 * Cp * * CP *
-------------------------------------------------------------------------------
1 Telnet Telnet * * TLN *
-------------------------------------------------------------------------------
2 * Telnet * * TLN *
-------------------------------------------------------------------------------

The routing with pr:1 allows to transfer an incoming TELNET session to an outgoing TELNET session, while routing with
pr:2 allows to transfer any incoming session to an outgoing TELNET session.

Some examples follow.

Example 17.2. TELNET - Example 1

[10:39:15] ABILIS_CPX:d p telnet

RES:Telnet --------------------------------------------------------------------
Run DESCR:Telnet_Server_and_Client_entities
LOG:NO MCAU:NO ps:128
KEEPALIVE:30
- Server ---------------------------------------------------------------
tcpport:23 PSER:TELNETS> ser:6
AC:YES PWD: DT:15
CDO:00 UDO:CP PROFILE:NORMAL
IPSRC: IPSRCLIST:#
- Client ---------------------------------------------------------------
PCLI:TELNETC> cli:3
CDI:* UDI:*

[10:39:17] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] TELNETS> <--- Ctrl+P

[10:52:50] ABILIS_CPX:

Example 17.3. TELNET - Example 2

[10:39:17] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>

269
Draft TELNET - TELecommunication NETwork Draft

Example 17.4. TELNET - Example 3

[10:53:07] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>11-tln <--- see Example 17.1, “X.25 routing”

COM

[192.168.1.1] TELNETC>open 192.168.5.254

Trying 192.168.5.254 ... Open

User Access Verification

Password: *********
COM

Abilis CPX - Ver. 6.0.9 - Build 2897.34

Tuesday 13/12/2007 10:53:49 (GMT+1.00)
Login:super
Password:
Logged as SUPERUSER

[10:53:59] ABILIS_CPX_2:

270
Draft Draft

Chapter 18. SSH - Secure SHell

Nicola Trevisani
Tomáš Klinkovský
Marco Bellesia
Luigi Demuro

Table of Contents
18.1. SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.1. Activating the SSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.1.2. SSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
18.2. SSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.1. SSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.2. SSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
18.2.3. SSH sessions status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
18.3. SSH commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
18.3.1. SSH from Abilis to Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

18.1. SSH resource

The Abilis CPX SSH resource includes:

• a ssh client: it processes create the login request and provide the connection establishment with the remote unit;

• a ssh server: it processes are hosted on the remote system and provide the login service to the request of the clients.

Tip
Interesting chapter: Section 18.3, “SSH commands”.

18.1.1. Activating the SSH resource

Add the resource to the Abilis system with the following command:

[11:09:16] ABILIS_CPX:a res:ssh

RES:SSH ALREADY EXISTS

The SSH resource may already exist in the system, but may not yet be active: set it active with the command:

[11:09:21] ABILIS_CPX:s act res:ssh

COMMAND EXECUTED

Caution
After adding or setting the SSH active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

18.1.2. SSH resource parameters

The following command displays the parameters of the resource. The d p ssh ? command displays the meaning of each
parameter.

271
Draft SSH - Secure SHell Draft

[11:09:25] ABILIS_CPX:d p ssh

RES:Ssh -----------------------------------------------------------------------
Run DESCR:Secure_Shell_Protocol
LOG:NO MCAU:NO ps:128
KEEPALIVE:30 LOGIN-TOUT:60
WDIR:C:\APP\SSH\
- Server ---------------------------------------------------------------
PSER:SSHS> ser:3 tcp-locport:22
AC:YES PWD:**************** DT:15
CDO:00 UDO:CP PROFILE:NORMAL
IPSRC:* IPSRCLIST:# MAXAUTH:6
KEYLEN:768 KEYREGENT:60 HOSTKEYLEN:1024
S-VER:1,2 S-AUTH-1:PWD S-AUTH-2:PWD
S-CIPHERS-1:ALL
S-CIPHERS-2:ALL
- Client ---------------------------------------------------------------
PCLI:SSHC> cli:3 MAXPROMPT:3
CDI:* UDI:*
C-VER:1,2 C-AUTH-1:PWD C-AUTH-2:PWD
C-CIPHERS-1:ALL DFT-CIPHER-1:3DES
C-CIPHERS-2:ALL DFT-CIPHER-2:3DES

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

KEEPALIVE Activates and sets the value of the “keep-alive” time-out; the “keep-alive” procedure, by sending the simple
packets, keeps the TCP connection “alive” even if any data is not exchanged.

WDIR Directory where HOST and SERVER keys are stored.

PSER The prompt of the commands interpreter of the Server SSH resource.

ser Number of Server processes allowed on the SSH resource.

AC Auto-connection mode for the SSH Server; the default value is YES. The SSH Server automatically
generates a connection request, using information configured in CDO and UDO parameters, whenever it
receives a login request from a Client SSH process.

PWD SSH Server password, which is asked for the connection.

DT Idle time interval after which the connection is closed (in minutes).

CDO Called address field of the SSH Server outgoing call. The parameter's default value (CDO:00), along with
AC setting to YES, allows to connect to the Control port.

UDO User data field of the SSH Server outgoing call. The parameter's default value (CDO:CP), along with AC
setting to YES, allows to connect to the Control port.

IPSRC IP address of enabled source SSH Client systems.

IPSRCLIST List of IP addresses of enabled SSH Client systems.

MAXAUTH Maximum number of authentication attempts for a SSH Client.

KEYLEN SSH Server RSA key length (in bits).

KEYREGENT SSH Server RSA key regeneration time (in minutes).

HOSTKEYLEN The host RSA key length (in bits).

S-CIPHERS Cryptographic algorithms supported by the SSH Server [ALL, IDEA, DES, 3DES, BF].

S-AUTH Authentication method supported by the SSH Server [NO, PWD].

PCLI The prompt of the commands interpreter of the Client SSH resource.

cli Number of Client processes on the SSH resource.

CDI Called address field of the SSH Client incoming call.

272
Draft SSH - Secure SHell Draft

UDI User data field of the SSH Client incoming call.

DFT-CIPHER Default cipher type of SSH Client [IDEA, DES, 3DES, BF, AUTO].

MAXPROMPT Maximum number of unsuccessful inputs of password for the SSH client.

C-CIPHERS Cryptographic algorithms supported by the SSH Client [ALL, IDEA, DES, 3DES, BF].

C-AUTH Authentication method supported by the SSH Client [NO, PWD].

The following command allows the administrator to change the configuration of the resource:

s p ssh parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:ssh;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

18.2. SSH diagnostics and statistics

18.2.1. SSH diagnostics
To display the diagnostics of the SSH resource the following commands are used:

d d ssh / d de ssh Shows diagnostic information, such as the state of the client and server, the local and
the remote addresses-ports connected to the resource, etc..

[17:58:20] ABILIS_CPX:d d ssh

RES:Ssh -----------------------------------------------------------------------
Secure_Shell_Protocol
STATE:READY
- Ssh Channels ---------------------------------------------------------
CH TYPE X25-State TCP-State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CLNT READY READY
2 CLNT READY READY
3 CLNT READY READY
4 SERV READY LISTENING 000.000.000.000-22
5 SERV READY LISTENING 000.000.000.000-22
6 SERV CONNECTED CONNECTED 192.168.000.201-22 192.168.000.025-40868

18.2.2. SSH statistics

To display the statistics of the SSH resource the following commands are used:

d s ssh Shows statistic information, such as number of segments received/sent, number of characters received/sent,
number of packets received/sent, number of calls sent/received and number of resets sent/received.

d se ssh Shows statistic information in an extended format: the information listed for d s ssh command are shown for
each session.

[18:06:18] ABILIS_CPX:d s ssh

RES:Ssh -----------------------------------------------------------------------
Secure_Shell_Protocol
--- Cleared 0 days 02:56:16 ago, on 28/12/2007 at 10:27:32 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 49| 5|CHAR | 2665| 42|
PCK | 14| 5|CALL | 0| 1|
RESET | 0| 0|
------------------------------------------------------------------------

[18:06:40] ABILIS_CPX:d se ssh

273
Draft SSH - Secure SHell Draft

RES:Ssh -----------------------------------------------------------------------
Secure_Shell_Protocol
--- Cleared 0 days 02:56:21 ago, on 28/12/2007 at 10:27:32 -------------
- Ssh Channels ---------------------------------------------------------
CH TYPE X25-State TCP-State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
2 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
3 CLNT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
4 SERV READY LISTENING 000.000.000.000-22
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
5 SERV READY LISTENING 000.000.000.000-22
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 0| 0|
PCK | 0| 0|CALL | 0| 0|
RESET | 0| 0|
------------------------------------------------------------------------
6 SERV CONNECTED CONNECTED 192.168.000.201-22 192.168.000.025-40868
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 60| 6|CHAR | 3302| 51|
PCK | 17| 6|CALL | 0| 1|
RESET | 0| 0|
------------------------------------------------------------------------

18.2.3. SSH sessions status

To display the communication sessions state for the SSH resource the following commands are used:

d c ssh Shows the current state of sessions.

d ce ssh Shows the current state of sessions in extended format.

[11:09:16] ABILIS_CPX:d c ssh

Res: Ses: State: Clr:/Res: Ses: [Cg:/Cd:] Id:/Pr:

-------------------------------------------------------------------------------
Ssh 1 UP F0,B0
2 UP F0,B0
3 UP F0,B0
4 UP F0,B0
5 UP F0,B0
6 CONN TO Cp 1 00 0
-------------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d ce ssh

274
Draft SSH - Secure SHell Draft

RES:Ssh
SES:1 UP CLR:F0,B0
SES:2 UP CLR:F0,B0
SES:3 UP CLR:F0,B0
SES:4 UP CLR:F0,B0
SES:5 UP CLR:F0,B0
SES:6 CONN TO RES:Cp SES:1
CG: CD:00 PID:01000000 UD:CP
IPSRC:192.168.000.025

18.3. SSH commands

While the SSH Server process is running, the User can access the SSH resource commands by typing the combination
Ctrl+P.

As a consequence of this action, the prompt of the SSH Server, configured in the parameter PSER, will be displayed.

The user can leave the command exchange procedure and start the data exchange by typing again the combination Ctrl+P.

The available commands for the command interpreter of the SSH resource are:

open This command, available only on SSH client processes, allows the User to open a connection with the
SSH Server process, hosting on the remote equipment identified by the specified IP.

close / exit It requests the session to be closed.

clr It requests the session to be closed.

18.3.1. SSH from Abilis to Abilis

To open an SSH session from an Abilis to another Abilis, the X.25 routing must be properly configured. Both Abilis must
have the follwing X.25 routing:

Example 18.1. X.25 routing

[10:38:01] ABILIS_CPX:a r pr:3 in:ssh out:ssh cdi:* udi:ssh

COMMAND EXECUTED

[10:38:04] ABILIS_CPX:a r pr:4 in:* out:ssh cdi:* udi:ssh

COMMAND EXECUTED

[10:38:07] ABILIS_CPX:d r

---+--------+--------+---------------+---------------+------------+------------
PR |IN |OUT |CDI |CDO |UDI |UDO
|NEXT |CGI |CGO |PIDI |PIDO
| |IPSRC |IPDEST |FFO
-------------------------------------------------------------------------------
0 * Cp * * CP *
-------------------------------------------------------------------------------
1 Telnet Telnet * * TLN *
-------------------------------------------------------------------------------
2 * Telnet * * TLN *
-------------------------------------------------------------------------------
3 Ssh Ssh * * SSH *
-------------------------------------------------------------------------------
4 * Ssh * * SSH *
-------------------------------------------------------------------------------

The routing with pr:3 allows to transfer an incoming SSH session to an outgoing SSH session, while routing with pr:4
allows to transfer any incoming session to an outgoing SSH session.

Some examples follow.

275
Draft SSH - Secure SHell Draft

Example 18.2. SSH - Example 1

[10:38:17] ABILIS_CPX:d p ssh

RES:Ssh -----------------------------------------------------------------------
Run DESCR:Secure_Shell_Protocol
LOG:NO MCAU:NO ps:128
KEEPALIVE:30 LOGIN-TOUT:60
WDIR:C:\APP\SSH\
- Server ---------------------------------------------------------------
PSER:SSHS> ser:3 tcp-locport:22
AC:YES PWD:**************** DT:15
CDO:00 UDO:CP PROFILE:NORMAL
IPSRC:* IPSRCLIST:# MAXAUTH:6
KEYLEN:768 KEYREGENT:60 HOSTKEYLEN:1024
S-VER:1,2 S-AUTH-1:PWD S-AUTH-2:PWD
S-CIPHERS-1:ALL
S-CIPHERS-2:ALL
- Client ---------------------------------------------------------------
PCLI:SSHC> cli:3 MAXPROMPT:3
CDI:* UDI:*
C-VER:1,2 C-AUTH-1:PWD C-AUTH-2:PWD
C-CIPHERS-1:ALL DFT-CIPHER-1:3DES
C-CIPHERS-2:ALL DFT-CIPHER-2:3DES

[10:38:17] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] SSHS> <--- Ctrl+P

[10:38:50] ABILIS_CPX:

Example 18.3. SSH - Example 2

[10:38:17] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] SSHS>clr

CLR 00 00

[192.168.1.1] SSHS>

276
Draft SSH - Secure SHell Draft

Example 18.4. SSH - Example 3

[10:51:07] ABILIS_CPX: <--- Ctrl+P

[192.168.1.1] SSHS>clr

CLR 00 00

[192.168.1.1] SSHS>11-ssh <--- see Example 18.1, “X.25 routing”

COM

[192.168.1.1] SSHC>open 192.168.5.254

Trying 192.168.5.254 ... Open

Coding is 3DES

Enter user name:root

Enter password:********* <--- wrong password
Permission denied, please try again.
Enter password:*******

COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Friday 14/01/2011 10:58:46 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[10:51:59] ABILIS_CPX_2:

277
Draft Draft

Chapter 19. IPRTR - IP Router

Nicola Trevisani
Marco Bellesia
Luigi Demuro
Luca Castagna

Table of Contents
19.1. IPRTR resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
19.1.1. IPRTR resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2. IP Routings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
19.2.1. D IPR (Display IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
19.2.2. A IPR (Add IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
19.2.3. C IPR (Clear IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.4. S IPR (Set IP Routing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
19.2.5. IP Source Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
19.3. IP Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.1. D P IP (Display Parameter IP resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
19.3.2. A RES:IP (Add IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
19.3.3. C RES:IP (Clear IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
19.3.4. S P IP (Set Parameter IP Resource) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
19.3.5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
19.4. Administrative Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.1. D IPAD (Display IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.2. A IPAD (Add IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
19.4.3. C IPAD (Clear IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
19.4.4. S IPAD (Set IP Administrative Distance) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5. IP Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.1. D IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.2. A IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
19.5.3. C IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
19.5.4. S IPLB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6. IPRTR diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.1. IPRTR diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
19.6.2. IPRTR statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
19.7. IPFLOW Tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
19.7.1. List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
19.7.2. Activating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
19.7.3. Deactivating the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.4. Starting the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
19.7.5. Stopping the IPFLOW tracer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.6. Display of IPFLOW parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
19.7.7. Setting IP packet filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
19.7.8. IPFLOW trace display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

19.1. IPRTR resource

The IPRTR (IP Router) resource is used within the Abilis CPX to route IP datagrams between LAN and WAN ports.

IP Datagram transport on LAN is carried out using Ethernet or Token Ring protocols.

278
Draft IPRTR - IP Router Draft

IP Datagram transport on WAN is carried out using X.25 resource (obsolete) or non-X.25 resources (SYNC, Frame-Relay,
LAPB, IP Tunnel or PPP links).

19.1.1. IPRTR resource parameters

Use the following command to display the parameters of the resource. By typing d p iprtr ? command it is possible to
display the meaning of all the parameters.

[17:50:56] ABILIS_CPX:d p iprtr

RES:Iprtr ---------------------------------------------------------------------
Run DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:080.080.080.080 NAT:OUTSIDE
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:9 virtual:1
- IP Access List -------------------------------------------------------
ACL:EXT ACLBYPASS:#
COS:ENABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000

Meaning of the most important parameters:

R-ID It shows the Router ID address [AUTO: it is the default value and it's obtained considering the first IP resource of the
homonym table, whose address is not 0.0.0.0; 1-126.x.x.x, 128-223.x.x.x: it is used a specific IP].

NAT It indicates the side of the IPRTR when remote hosts connect to R-ID IP address. This information is required by
NAT in order to determine if the IP address must be translated or not. This parameter can be set only when R-ID is
not set to AUTO [NO: NAT is not configured; INSIDE: the R-ID address is in the INSIDE IP resource; OUTSIDE:
the R-ID address is in the OUTSIDE IP resource, VPN: the R-ID address is in the VPN IP resource, DMZ: the R-ID
address is in the DMZ IP resource].

ACL It activates the IP Access List service and choose the operating mode [NO: the service IP access list is disabled; STD
(Standard): datagrams are filtered by their source and destination addresses (address filtering); EXT (Extended):
datagrams are filtered by their source and destination addresses but also by the internet protocol. For TCP and UDP
protocols the logic port number is also checked (that is the service requested)].

The following command allows the administrator to change the configuration of the resource:

s p iprtr parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:iprtr; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

19.2. IP Routings table

Changes on static routings are active immediately while Abilis CPX works.

The command save conf saves onlys tatic routings inside the table.

The maximum size of the IP routings table can be configured through the parameter MAXROUTE of the IP Router resource,
whose default value is 500.

In the configuration files up to 255 static routings are saved, while the connected routings are derived from the configurations
of IP ports. See Section 19.3.5.1, “Examples of REDIS parameter use” to have more information about connected routings.

279
Draft IPRTR - IP Router Draft

The available commands for managing the IP routings table are the following:

• d ipr

• a ipr

• c ipr

• s ipr

19.2.1. D IPR (Display IP Routing)

It shows the IP routing table. By typing d ipr ? command it is possible to display the meaning of all parameters.

[14:36:28] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 010.000.020.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.255.255.000/30 | 255.255.255.252 | | 14| 0|
|*|R| | | 010.255.255.004/30 | 255.255.255.252 | 010.000.020.002 | 0|120|
| |S| | | 010.096.000.000/12 | 255.240.000.000 | |D 22| 1|
| |S| | | 010.096.000.000/12 | 255.240.000.000 | | 10| 1|
|*|R| | | 000.000.000.000/0 | 000.000.000.000 | 010.255.255.002 | 14|120|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

Meaning of the parameters:

B (Best) This parameter has only an informative value and it cannot be modified. In case that
two or more routings with the same NET value are present, it identifies the best one.

P (Provenience) This parameter has only an informative value and it cannot be modified. It shows the
origin of the routing [S: static; R: obtained from the RIP protocol; O: obtained from the
OSPF protocol; C: obtained from the configuration table of the IP ports (this kind of
routing is referred as directly connected)].

S (Status) It indicates the state of the single routing. Every time some changes occurs to IPRTR
table, routings could change their state [Empty Field: normal state; A: Added state:
routing is just added into the table and is going to be accepted. Once confirmed by
IPRTR, it will go into normal state; C: Changed state: routing has changed some
parameters and is going to be accepted. Once confirmed by IPRTR, it will go into
normal state; D: Deleted state: routing is just requested for being deleted from table.
Once request is confirmed by IPRTR, routing will be removed from the table; H:
Hidden state: routing hidden parameter is changed from NO to YES. Once request is
confirmed by IPRTR, routing will go into normal state].

H (Hide) It sets whether the static routing has to be hidden to the other dynamic routing
protocols like RIP and OSPF [NO: the field will be empty and the routing will be
inserted in the RIP and OSPF local table; YES: the character * will be shown, meaning
that the routing won't be inserted in the RIP and OSPF local table].

NET/MASK It sets the destination network of the routing; it's shown in Slash Notation.

MASK/ or SRNET/SRMASK It sets the mask related to the destination network shown in DDN (Dotted Decimal
Notation), but can also indicate address and mask (in Slash Notation) of the source
network that make true the routing.

GW It sets the address of the destination gateway, in Dotted Decimal Notation.

IP It sets the IP resource where to route the IP datagram. If, at the moment of the
visualization, the IP resource that is referenced by the routing is in DOWN state,
beside the port index, the character D will appear. The value NONE stands for “no IP
resource”; it can be used for deactivating the IP routing without cancelling it. The

280
Draft IPRTR - IP Router Draft

value R-ID stands for “Router-ID”; it cannot be manually set and it means that the
specified routing is the Router ID.

AD (Administrative Distance) Distance used for route priority into IP Routing table. This is a particular metric used
to indicate priorities between routings of the same and different protocol. Routings
with the minor AD value have a major priority.

Tip
Use the command d ipre to show the routings descriptions:

[14:41:51] ABILIS_CPX:d ipre

- Not Saved (SAVE CONF) -------------------------------------------------------

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or IPLB: |IP: |AD:|
|[DESCR:] | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|S| | | 129.132.002.021/32 | 255.255.255.255 | |D 2| 1|
|*|C| | | 192.168.000.201/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 192.168.001.000/24 | 255.255.255.000 | |D 4| 1|
|*|C| | | 192.168.031.000/24 | 255.255.255.000 | |D 21| 0|
|*|S| | | 192.168.000.000/16 | 255.255.000.000 | 192.168.000.251 | 1| 1|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.000.251 | 1| 1|
|default_GW |
| |S| | | 000.000.000.000/0 | 000.000.000.000 | |D 3|120|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.2. A IPR (Add IP Routing)

It adds a new IP static routing definition with the specified parameters. Unspecified ones are set to their default values.

To display the syntax of the command, type a ipr ?.

Tip
The -FD option can be optionally specified to force routing duplication, i.e. the addition of two routings
with the same destination network and mask, but with different destination IP resource.

Some examples follow:

[14:00:15] ABILIS_CPX:a ipr net:10.211.16.0/24 ip:4

COMMAND EXECUTED

[14:00:15] ABILIS_CPX:a ipr net:0.0.0.0/0 gw:192.168.1.254 ip:1

COMMAND EXECUTED

[14:01:01] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|S| | | 10.211.016.0000/24 | 255.255.255.000 | | 4| 1|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|

281
Draft IPRTR - IP Router Draft

|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|

+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.3. C IPR (Clear IP Routing)

It deletes from the table the IP routing identified by the specified destination network “NET:x.x.x.x”, expressed in Dotted
Decimal Notation.

To display the syntax of the command, type c ipr ?.

Some examples follow:

[13:55:27] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|S| | | 10.211.016.0000/24 | 255.255.255.000 | | 4| 1|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

[13:55:27] ABILIS_CPX:c ipr net:10.211.16.0/24 ip:4

COMMAND EXECUTED

[13:55:27] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.4. S IPR (Set IP Routing)

It sets one or more parameters to their new values, in the IP routing identified by the specified destination network
“NET:x.x.x.x”, expressed in Dotted Decimal Notation. This command can be only used to modify static IP routing
definitions in the table.

Type s ipr ? to display the syntax of the command.

Some examples follow:

[13:56:01] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|S| | | 10.211.016.0000/24 | 255.255.255.000 | | 4| 1|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

282
Draft IPRTR - IP Router Draft

[13:56:25] ABILIS_CPX:s ipr net:10.211.16.0/24 ip:6

COMMAND EXECUTED

[13:57:38] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|S| | | 10.211.016.0000/24 | 255.255.255.000 | | 6| 1|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.5. IP Source Routing

It allows to define paths to reach hosts and networks, specifying:

• the source routing network address/mask [SRNET:/SRMASK];

• the destination network address/mask [NET:/MASK:];

• the destination gateway IP address [GW];

• the outgoing IP resource [IP].

The available commands for managing the IP source routings are the following:

• d ipsr

• a ipsr

• c ipsr

• s ipsr

19.2.5.1. D IPSR (Display IP Source Routing)

It shows the IP source routings table.

By typing d ipsr ? command it is possible to display the meaning of all parameters.

[11:02:59] ABILIS_CPX:d ipsr

+-----+--------------------+--------------------+-----------------+------+----+
| ID: | NET:/MASK: | SRNET:/SRMASK: | GW: | IP: | UN:|
+-----+--------------------+--------------------+-----------------+------+----+
| 0 | 001.001.001.001/32 | 005.005.005.005/32 | 000.000.000.000 | NONE | NO |
| 1 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 0 | NO |
| 2 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | NONE | NO |
| 3 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 2 | YES|
| 4 | 002.002.000.000/16 | 005.005.005.005/32 | 000.000.000.000 | 1 | YES|
+-----+--------------------+--------------------+-----------------+------+----+

The meaning of the fields are the same of the IP Routing table.

A routing can be set to Unconditional (UN:YES) or Conditional (UN:NO).When it is set to Unconditional, it's moved on the
top of the generic routing table, in order to give it the highest priority.

IP Source routing can be displayed also in the IP routing table; in the example below they are represented with bold
characters:

[11:02:59] ABILIS_CPX:d ipr

283
Draft IPRTR - IP Router Draft

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 001.001.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 001.001.001.001/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 002.002.002.002/24 | 255.255.255.000 | | 2| 0|
|*|C| | | 003.003.003.003/24 | 255.255.255.000 | | 3| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1|
| | | | | | 002.002.002.000/24 | | 4| |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

The meaning of the route above is that the default gateway for IP source 2.2.2.0/24 is the IP resource “ip-4”.

19.2.5.2. A IPSR (Add IP Source Routing)

It adds new IP source routing. The command can only be executed by off-line configurator. To display the syntax of the
command, type a ipsr id: ?.

[14:00:15] ABILIS_CPX:a ipr net:10.124.48.0/24 srnet:192.168.1.20/32 ip:4

COMMAND EXECUTED

[13:56:01] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
| | | | | 010.124.048.000/24 | 255.255.255.000 | | | |
| | | | | | 192.168.001.020/32 | | 4| |
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.5.3. C IPSR (Clear IP Source Routing)

It removes an existing IP source routing from the related table. The command can only be executed by off-line configurator.
To display the syntax of the command, type c ipsr id: ?.

[14:00:15] ABILIS_CPX:c ipr net:10.124.48.0/24 srnet:192.168.1.20/32

COMMAND EXECUTED

[13:56:01] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.2.5.4. S IPSR (Set IP Source Routing)

It sets the parameters of the specified IP source routing to their new values. The command can only be executed for setting IP
source routing parameter by off-line configurator. To display the syntax of the command, type c ipsr id: ?

[13:56:01] ABILIS_CPX:d ipr

284
Draft IPRTR - IP Router Draft

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
| | | | | 010.124.048.000/24 | 255.255.255.000 | | | |
| | | | | | 192.168.001.020/32 | | 4| |
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

[13:56:48] ABILIS_CPX:s ipr net:10.124.48.0/24 srnet:192.168.1.20/32 ip:6

COMMAND EXECUTED

[13:57:25] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.001/32 | 255.255.255.255 | |R-ID| 0|
| | | | | 010.124.048.000/24 | 255.255.255.000 | | | |
| | | | | | 192.168.001.020/32 | | 6| |
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.3. IP Resources
The IP Router of Abilis CPX can manage up to 256 IP resources. The IP configuration of each resource is stored into the
routing table.

The available commands for managing the IP resources are the following:

• d p ip

• a res:ip

• c res:ip

• s p ip

19.3.1. D P IP (Display Parameter IP resource)

It shows the IP resources table. By omitting the IP resource identifier, the command will show all the resources currently
defined.

[08:32:56] ABILIS_CPX:d p ip

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:Lan_locale
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-1
IPADD:192.168.000.201 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:50 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------

285
Draft IPRTR - IP Router Draft

TRFA:YES TRFA-MODE:TOTALS
TRFA-IPADD:LOCALNET (192.168.000.000:192.168.000.255)
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14

RES:Ip-22 - IP over PPP (PPP) -------------------------------------------------

Run DESCR:UMTS-DATA
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:CtiSLink
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:NOMAX PPP-ENC:RAW-PPP RADIUS:NO
DT-IN:300 DT-OUT:300 UDT-IN:NOMAX UDT-OUT:NOMAX
- Dial-in --------------------------------------------------------------
DIAL-IN:NO
CGI:* SGI:DISABLED
CDI:* SDI:*
- Dial-out -------------------------------------------------------------
DIAL-OUT:YES RTY:US NRTY:30 NRTY2:3 TB:3
CGO:# SGO:#
CDO:99 SDO:#
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO
maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:
PASSWORD: LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE
REPEAT:0

RES:Ip-100 - IP virtual (VIRTUAL) ---------------------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO
P-IP:1
IPADD:192.168.001.101 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:(NO) VRRP:NO
NAT:(OUTSIDE) DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO

Note
The “Not Saved (SAVE CONF)” message is displayed every time the table is modified but not saved with
the save conf command.

Note
The “Not Refreshed (INIT)” message is displayed every time the table is modified but not refreshed with the
initialization command init res:ip.

By specifying IP resource identifier, the command will show the definition of the requested port. IP resource identifier must
be in the interval [0 - 255]. If does not exist any resource with that identifier, an error message is generated: “RESOURCE
NOT PRESENT OR INACTIVE”.

286
Draft IPRTR - IP Router Draft

[08:38:13] ABILIS_CPX:d p ip-1

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:Lan_locale
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-1
IPADD:192.168.000.201 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:50 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:TOTALS
TRFA-IPADD:LOCALNET (192.168.000.000:192.168.000.255)
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-1 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:25 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[14:47:53] ABILIS_CPX:d p ip-10

RESOURCE NOT PRESENT OR INACTIVE

Below the meaning of the most important parameters is shown:

IP over lan section

DESC Resource description

OPSTATE Operative state [DOWN, UP]

IPLOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log;
A: Alarm view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes, see ref.
manual)

STATE-DETECT Select IP resource state detection method [NORMAL, PING]: - NORMAL: the state depends on lower
interface only. - PING: the state depends on lower interface state and on result of the PING procedure.
Enabling the PING procedure, the parameters of PING section are shown.

Refer to chapter Section 52.19, “How to use state detection of IP interfaces” to view a how to.

LANRES Lower resource [NONE, Eth-XXX, VEth, Tr-XXX]

IPADD IP address of the IP resource [0-126.x.x.x, 128-223.x.x.x, DHCP]

MASK Mask [240.0.0.0 - 255.255.255.255]

DHCP-DNS Retrieve primary and secondary DNS server through DHCP [NO, YES] <Only for IPADD:DHCP>

DHCP-GW Retrieve default gateway through DHCP [NO, YES] <Only for IPADD:DHCP>

REDIS Create the related connected routing [NO: no route is created; YES: a destination route is added to IPR
table, EXT: a source route is added to IPR table]

NAT NAT usage [NO, INSIDE, OUTSIDE, VPN, DMZ]

IPSEC Enable/disable IPSEC [NO, YES]

VRRP Enable/disable VRRP [NO, YES]

DDNS Enable/disable DDNS [NO, YES]

287
Draft IPRTR - IP Router Draft

OUTSPL Output speed limitation activation [NO, YES, IPCOS]

OUTSP Output speed limitation value [64..100000 Kbit/sec] <Only for OUTSPL: not equal to NO>

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log;
A: Alarm view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes, see ref.
manual)

TRFA section:

TRFA Enables/disables traffic analysis.

TRFA-MODE Select traffic analysis mode [TOTALS: saves the total global traffic; PROT: subdivides the registration for
the main protocol models; IP: saves the totals for every single IP address; IP-PROT: subdivides the traffic
by protocol, for every single crossing IP address];

IP-RESERVE Reserves records in the traffic analysis data base: it represents the maximum IP number trace.

TRFA-SIDE Selects IP address type [LOCAL: filters the traffic by destination IP address; REMOTE: filters the traffic by
source IP address].

TRFA-IPADD IP address filter.

Link section:

LCOMP Set the compression type to use for an ip resource with subtype AIPT[-BCK], DL[-BCK], ML, BCH. Data
Compression is available only under licence.[NO: compression not active, LZO1X: is often the best choice of all,
LZO1B: is good with a large blocksize or with very redundant data, LZO1F: s good with a small blocksize or with
binary data]

PPP section:

PPP-ENC Encapsulation type [RAW-PPP, FR-IETF, RFC2364-VCMUX, RFC2364-LLCMUX]

PING section:

P-LOC Source IP address used for PING request (ECHO REQUEST) [1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] or
"R-ID" or "IPADD".

P-DST1 Ip address of the destination number 1 [1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] or "#".

P-DST2 Ip address of the destination number 2 [1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] or "#".

P-GW Ip address of the gateway [1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] or "#".

P-TOUT Timeout for the reply reception (ECHO REPLY) [100..10000 msec].

P-TRY Number of attempts considered for the state detection [2..50].

P-DLY-UP Interval between attempts while state is UP [1..60 sec].

P-DLY-UP Interval between attempts while state is UP [1..60 sec].

P-DLY-DN Interval between attempts while state is DOWN [1..60 sec].

P-THR-UP Percentage of successful attempts to declare state UP [10..100].

P-THR-DN Percentage of successful attempts to declare state DOWN [0..90].

P-BURST Number of requests sent at each attempt [1..10].

P-BURST-DLY Interval between requests pertaining to the same attempt [0..1000 msec].

P-TTL TTL value when transport layer doesn't provide one [DFT, 1..255].

19.3.2. A RES:IP (Add IP Resource)

It adds a new IP resource, identified by “IP-xx”.

Type the following command to display all the available types of IP resource.

[10:16:34] ABILIS_CPX:a res:ip ?

288
Draft IPRTR - IP Router Draft

Ip resource subtypes:

X25PVC IP over X.25 Pvc

X25BSVC IP over X.25 Bsvc
LAN IP over LAN
DL IP over Dedicated Line
DL-BCK IP over Dedicated Line with Abilis Back-up
BCH IP over B-Channel
ML IP over Multi-Links
AIPT IP over IP (Abilis tunnel)
AIPT-BCK IP over IP (Abilis tunnel) with Abilis Back-up
PPP IP over PPP
VIRTUAL IP virtual

Some examples follow:

[12:18:12] ABILIS_CPX:a res:ip-10 subtype:lan

COMMAND EXECUTED

[12:18:20] ABILIS_CPX:d p ip-10

RES:Ip-10 - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

- IP over LAN (LAN) ----------------------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:NONE
IPADD:000.000.000.000 MASK:255.255.255.255
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14

[12:18:23] ABILIS_CPX:a res:ip-11 subtype:aipt

COMMAND EXECUTED

[12:22:13] ABILIS_CPX:d p ip-11

RES:Ip-11 - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT

289
Draft IPRTR - IP Router Draft

- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2111 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:#

[12:23:06] ABILIS_CPX:a res:ip-12 subtype:dl

COMMAND EXECUTED

[12:23:31] ABILIS_CPX:d p ip-12

RES:Ip-12 - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

- IP over Dedicated Line (DL) ------------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:NONE
ENC:RAW-IP FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:NO LCOMP:NO LCR:NO
LT1:1000 LT3:3000 LN2:3 LCRKEY:DFT

Caution
After adding a new IP resource, you must restart the Abilis to make the resource running (use the command
warm start to reboot the Abilis).

Tip
Interesting chapters:

Section 52.2, “How to activate a new ethernet port”;

Section 52.3, “How to assign several IP addresses to the same LAN port”.

19.3.3. C RES:IP (Clear IP Resource)

It removes the requested IP resource from the IP resources table.

Caution
It's not possible to remove an IP resource on a running CPX with this command! It's needed to follow this
sequence:

1. Deactivate the IP resource with s inact res:ip-x command.

2. Save the configuration with save conf command.

3. Reboot the Abilis with the warm start command.

4. Clear permanently the IP resource with c res:ip-x command.

[08:50:03] ABILIS_CPX:d p ip-5

290
Draft IPRTR - IP Router Draft

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:#

[08:50:08] ABILIS_CPX:c res:ip-5

COMMAND NOT ALLOWED FOR 'RES:IP-5' BECAUSE IT IS RUNNING

[08:55:03] ABILIS_CPX:s inact res:ip-5

COMMAND EXECUTED

[08:55:25] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[15:07:05] ABILIS_CPX:warm start

At next reboot:

[08:58:31] ABILIS_CPX:c res:ip-5

THE SELECTED RESOURCE WILL BE DELETED.

PROCEED (N/Y)?y

THE COMMAND WILL DELETE ALL THE REFERENCES TO THE SELECTED RESOURCE.
PROCEED ANYWAY (N/Y)?y

PROCEEDING WITH RESOURCE DELETION...

COMMAND EXECUTED

Warning
Deleting an IP resource also its references in IPR, IPACL , IPAD and RIP EXTERNAL will be deleted!!

19.3.4. S P IP (Set Parameter IP Resource)

It sets the parameters to their new values for the specified IP resource. Parameters of each IP resource can be separately
configured depending of the connection.

The syntax of the command is:

291
Draft IPRTR - IP Router Draft

s p ip-x [par:val...]

In the example below description, neighbour IP (NEIGH), subnet mask (MASK), LOCIPADD and REMIPADD parameters will
be modified.

[09:00:43] ABILIS_CPX:d p ip-8

RES:Ip-8 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO

NAT:NO DIFFSERV:NO DDNS:NO

OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:2108 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:#

[09:01:18] ABILIS_CPX:s p ip-8 descr:To_Abilis_2 neigh:192.168.2.254 mask:255.255.255.0 locipadd:21

COMMAND EXECUTED

[09:01:25] ABILIS_CPX:d p ip-8

RES:Ip-8 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
Run DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.002.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:2108 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002

19.3.5. Examples
The following paragraphs contain some examples to explain the meaning of REDIS parameter.

292
Draft IPRTR - IP Router Draft

19.3.5.1. Examples of REDIS parameter use

The REDIS parameter manages the entry in the IPR table for the specific ip resource. The following table shows the meaning
of values:

NO No entry is created in the IPR table. Creating a route by hand

is needed to use the ip resource.
YES A destination routing with the IPADD of the IP resource is
automatically added in the routing table.
EXT A source routing with the IPADD of the IP resource is
automatically added in the routing table.

Note
REDIS:NO can be always used, but every route must be created by hand.

Examples:

The parameter REDIS of ip-2 i set to NO, so in the ipr table there's no entry automatically generated and related with this ip
address. If you want to use the ip-2 as gateway you must add a route by hand.

[15:34:07] ABILIS_CPX:_d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:YES
REDIS:NO HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[15:34:22] ABILIS_CPX:_d d ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

WAN
STATE:UP LINK-STATE:LINKREADY
CUR-IPADD:192.168.001.100 CUR-MASK:255.255.255.000
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:N/A OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Lan ------------------------------------------------------------------
STATE:LINKREADY ARP-CACHE-ITEMS:1

[15:34:25] ABILIS_CPX:_d ipr

293
Draft IPRTR - IP Router Draft

- Not Saved (SAVE CONF) -------------------------------------------------------

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|C| | | 192.168.030.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.000.000.000/29 | 255.255.255.248 | | 12| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 11| 0|
|*|S| | | 192.168.008.000/24 | 255.255.255.000 | |D 10| 1|
|*|C| | | 192.168.030.000/24 | 255.255.255.000 | | 1| 0|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

The parameter REDIS of ip-2 is set to YES, so in the ipr table there's an entry with provenience equal to C (refer to
Section 19.2.1, “D IPR (Display IP Routing)”). The route automatically created is a destination route.

[15:38:00] ABILIS_CPX:_d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:YES
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[15:38:22] ABILIS_CPX:_d d ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

WAN
STATE:UP LINK-STATE:LINKREADY
CUR-IPADD:192.168.001.100 CUR-MASK:255.255.255.000
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:N/A OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Lan ------------------------------------------------------------------
STATE:LINKREADY ARP-CACHE-ITEMS:1

[15:38:25] ABILIS_CPX:_d ipr

- Not Saved (SAVE CONF) -------------------------------------------------------

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|

294
Draft IPRTR - IP Router Draft

| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|C| | | 192.168.030.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.000.000.000/29 | 255.255.255.248 | | 12| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 11| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 2| 0|
|*|S| | | 192.168.008.000/24 | 255.255.255.000 | |D 10| 1|
|*|C| | | 192.168.030.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.001 | 2| 0|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

The parameter REDIS of ip-2 is set to EXT, so in the ipr table there's an entry with provenience equal to C (refer to
Section 19.2.1, “D IPR (Display IP Routing)”). Two routes are automatically created: a destination route and a default route
for that ip address.

Setting REDIS:EXT is useful to automatically generate a route when using two or more ADSL lines.

[15:27:59] ABILIS_CPX:_d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:YES
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[15:28:21] ABILIS_CPX:_d d ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

WAN
STATE:UP LINK-STATE:LINKREADY
CUR-IPADD:192.168.001.100 CUR-MASK:255.255.255.000
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:N/A OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Lan ------------------------------------------------------------------
STATE:LINKREADY ARP-CACHE-ITEMS:1

[15:29:05] ABILIS_CPX:_d ipr

- Not Saved (SAVE CONF) -------------------------------------------------------

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|

295
Draft IPRTR - IP Router Draft

| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|C| | | 192.168.030.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.000.000.000/29 | 255.255.255.248 | | 12| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 11| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 2| 0|
|*|S| | | 192.168.008.000/24 | 255.255.255.000 | |D 10| 1|
|*|C| | | 192.168.030.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.001 | 2| 0|
| |C| | | |[192.168.001.100/32]| 192.168.001.001 | 2| |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.4. Administrative Distance

Administrative distance let Abilis toselect the best path when there are two or more different routes towards the same
destination;the route with the lowest value of AD has the highest priority into the IP routing table.

The Administrative Distance table contains information about rules for routes priority into IP Routing table. The commands
for managing the IP Routing Administrative Distances table are the following:

• d ipad

• a ipad

• c ipad

• s ipad

19.4.1. D IPAD (Display IP Administrative Distance)

Use d ipad command to display the parameters of the resource. By typing d ipad ? command it is possible to display the
meaning of all the parameters.

[10:49:13] ABILIS_CPX:d ipad

+--------------------+---------+-----------+---------+
| NET: | PROT: | DISTANCE: | IP: |
+--------------------+---------+-----------+---------+
| 192.168.006.002/32 | RIP | 110 | |
| 192.168.006.000/24 | RIP | 120 | |
| 192.168.006.000/24 | OSPF | 100 | |
| 010.000.000.000/8 | STATIC | 10 | NONE |
| 000.000.000.000/0 | LOCAL | 5 | |
+--------------------+---------+-----------+---------+

Meaning of the parameters:

NET It indicates the destination network IP address and the mask used for setting administrative distance, in Slash
Notation (i.e. x.x.x.x/yy).

PROT This parameter defines a routing protocol for which this distance will be applied.

DISTANCE This parameter defines the distance that will be used for route priority into IP Routing table.

IP This parameter defines the IP resource value. It is allowed only when PROT parameter is set to STATIC.
[NONE: no IP resource; *: all IP resources; 1..250: it is used the specified IP resource].

19.4.2. A IPAD (Add IP Administrative Distance)

This command adds a new entry into the IP Routing Administrative distance table. To display the syntax of the command,
type a ipad ?.

Here an example.

296
Draft IPRTR - IP Router Draft

[17:22:54] ABILIS_CPX:a ipad net:0.0.0.0/0 prot:static distance:180 ip:4

COMMAND EXECUTED

[17:22:54] ABILIS_CPX:d ipad

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

+--------------------+---------+-----------+---------+
| NET: | PROT: | DISTANCE: | IP: |
+--------------------+---------+-----------+---------+
| 000.000.000.000/00 | STATIC | 180 | 4 |
+--------------------+---------+-----------+---------+

Caution
Changes made on the IP Routing Administrative distance table are NOT immediately active, they can be
activated by executing the initialization command init ipad.

[14:00:15] ABILIS_CPX:a ipr net:0.0.0.0/0 gw:192.168.0.254 ip:4 -fd

COMMAND EXECUTED

[14:01:01] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 080.080.080.080/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.005.000/24 | 255.255.255.000 | | 3| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 2| 1|
| |S| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.000.254 | 4|180|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

Note
The option “-fd” has been used because a static routing towards network 0.0.0.0/0 was already present.

The “Best” route for network 0.0.0.0/0 is the ip-2 resource; the alternative way it is the ip-4 resource that will be considered
only if the primary route is down. In normal conditions the route towards ip-4 resource is ignored.

19.4.3. C IPAD (Clear IP Administrative Distance)

This command deletes the specified entry from the IP Routing Administrative distance table, if it is present. To display the
syntax of the command type c ipad ?.

Here an example.

[18:11:52] ABILIS_CPX:c ipad net:0.0.0.0/0 prot:static distance:180 ip:4

COMMAND EXECUTED

[18:12:11] ABILIS_CPX:d ipad

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

+--------------------+---------+-----------+---------+
| NET: | PROT: | DISTANCE: | IP: |
+--------------------+---------+-----------+---------+
*** NO IP ROUTING ADMINISTRATIVE DISTANCEs DEFINED ***

297
Draft IPRTR - IP Router Draft

Caution
Changes made on the IP Routing Administrative distance table are NOT immediately active, they can be
activated by executing the initialization command init ipad.

19.4.4. S IPAD (Set IP Administrative Distance)

This command sets parameters of the selected entry of the IP Routing Administrative Distances table. To display the syntax
of the command type s ipad ?.

[18:11:52] ABILIS_CPX:s ipad net:0.0.0.0/0 ip:5

COMMAND EXECUTED

[18:12:11] ABILIS_CPX:d ipad

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

+--------------------+---------+-----------+---------+
| NET: | PROT: | DISTANCE: | IP: |
+--------------------+---------+-----------+---------+
| 000.000.000.000/00 | STATIC | 180 | 5 |
+--------------------+---------+-----------+---------+

19.5. IP Load Balancing

IPLB is a feature which allows to distribute traffic toward internet or VPN between two or more ip resources. Two methods
are allowed:

• RR: Round Robin. The packets are sequentially sent through the IP resources of the group.

• WQ: Weighted Queue. The IP resource of the group with the shorter transmission queue of the same priority is used for the
transmission of the packet under processing, otherwise packets are sent sequentially on the resources of the group.

19.5.1. D IPLB
Use the command d iplb to display the ip load balancing table.

[12:24:12] ABILIS_CPX:D IPLB

...
-------------------------------------------------------------------------------
ID:1 RULE:WQ RES1:Ip-10 GW1:192.168.255.002
RES2:Ip-11 GW2:#
RES3:Ip-12 GW3:#
RES4:# GW4:#
RES5:# GW5:#
RES6:# GW6:#
RES7:# GW7:#
RES8:# GW8:#
-------------------------------------------------------------------------------

Meaning of the most important parameters:

• ID: identification number of the iplb table

• RULE: ip resources scanning rule [RR: Round Robin, WQ: weighted queue]

• RESx: ip resources in the group [# or NONE, Ip-nnn] , where 'nnn' is an IP resource index [1..250].

• GWx: Gateway Ip address [#, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]

19.5.2. A IPLB
This command allows to add an entry into the IPLB table.

298
Draft IPRTR - IP Router Draft

[14:56:59] ABILIS_CPX:a iplb id:1 rule:wq descr:test res1:ip-1 res2:ip-2 gw1:192.168.0.232

COMMAND EXECUTED

[14:57:06] ABILIS_CPX:d iplb

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID:1 RULE:WQ DESCR:test
RES1:Ip-1 GW1:192.168.000.232
RES2:Ip-2 GW2:#
RES3:# GW3:#
RES4:# GW4:#
RES5:# GW5:#
RES6:# GW6:#
RES7:# GW7:#
RES8:# GW8:#
-------------------------------------------------------------------------------

Caution
Changes made on the IP Load Balancing table are NOT immediately active, they can be activated by
executing the initialization command init iplb. Then, remeber to save the configuration (save conf).

A routing which uses an IPLB indicates this condition by showing the IPLB in the “GW: or IPLB:” field of the D IPR output.

[15:20:35] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|S| | | 129.132.002.021/32 | 255.255.255.255 | |D 2| 1|
|*|C| | | 192.168.000.201/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 3|120|
| |S| | | 192.168.001.000/24 | 255.255.255.000 | |D 4| 1|
|*|C| | | 192.168.031.000/24 | 255.255.255.000 | |D 21| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | (IPLB ID:01) | 1| 1|
| |S| | | 000.000.000.000/0 | 000.000.000.000 | | 3|120|
| |C| | | | OUT-IP | |D 22| |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

19.5.3. C IPLB
This command allows to remove an entry of the iplb table.

[15:19:33] ABILIS_CPX:d iplb

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID:1 RULE:RR DESCR:test
RES1:Ip-1 GW1:192.168.000.232
RES2:Ip-2 GW2:#
RES3:# GW3:#
RES4:# GW4:#
RES5:# GW5:#
RES6:# GW6:#
RES7:# GW7:#
RES8:# GW8:#
-------------------------------------------------------------------------------

299
Draft IPRTR - IP Router Draft

[15:20:21] ABILIS_CPX:c iplb id:1

COMMAND EXECUTED

[15:20:33] ABILIS_CPX:d iplb

IPLB TABLE IS EMPTY

Caution
Changes made on the IP Load Balancing table are NOT immediately active, they can be activated by
executing the initialization command init iplb. Remeber to save the configuration (save conf).

19.5.4. S IPLB
This command allows to change the parameters of an entry inside the iplb table:

[15:26:20] ABILIS_CPX:d iplb

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID:1 RULE:RR DESCR:test
RES1:Ip-1 GW1:192.168.000.232
RES2:Ip-2 GW2:#
RES3:# GW3:#
RES4:# GW4:#
RES5:# GW5:#
RES6:# GW6:#
RES7:# GW7:#
RES8:# GW8:#
-------------------------------------------------------------------------------

[15:26:24] ABILIS_CPX:s iplb id:1 res2:ip-3

COMMAND EXECUTED

[15:26:58] ABILIS_CPX:d iplb

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID:1 RULE:RR DESCR:test
RES1:Ip-1 GW1:192.168.000.232
RES2:Ip-3 GW2:#
RES3:# GW3:#
RES4:# GW4:#
RES5:# GW5:#
RES6:# GW6:#
RES7:# GW7:#
RES8:# GW8:#
-------------------------------------------------------------------------------

Caution
Use command init iplb to activate changes on the IP Load BalancingThen, remeber to save the
configuration (save conf).

19.6. IPRTR diagnostics and statistics

19.6.1. IPRTR diagnostics
To display the diagnostics of the IPRTR resource the following commands are used:

300
Draft IPRTR - IP Router Draft

d d iprtr / d de iprtr Shows diagnostic information, such as the state of the resource and the routings table,
the current percentage of routings present into routing table, the current number of
routings present into the table, the maximum number of routings reached from start-
up into the table and the maximum number of routings present into the table (this
information indicate the MAXROUTE parameter).

[18:06:40] ABILIS_CPX:d d iprtr

RES:Iprtr ---------------------------------------------------------------------
IP_Router_general_properties
STATE:READY
ROUTINGs TABLE Diagnostics
-----------|---State---|-Current%--|--Current--|---Peak----|----Max----|
ROUTINGS |NORMAL | 5| 29| 29| 500|
------------------------------------------------------------------------

19.6.2. IPRTR statistics

To display the statistics of the IPRTR resource the following commands are used:

d s iprtr / d se iprtr Statistic information are divided into two groups: one dedicated to IP Router (the
number of IP datagrams sent/received, number of IP datagrams discarded due to
header errors and to wrong destination address, etc..), the other one to the ICMP (the
number of ICMP messages sent/received, the number of bad ICMP messages received,
the number of “Unreachable destination” ICMP messages, etc..).

[18:06:40] ABILIS_CPX:d s iprtr

RES:Iprtr ---------------------------------------------------------------------
IP_Router_general_properties
--- Cleared 23 days 13:45:07 ago, on 03/12/2007 at 03:20:52 ------------
ROUTER Statistics
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
DGM | 30476317| 3759615|HDR-ERR | 52| |
ADDR-ERR | 0| |FRW-DGM | | 26743001|
UNK-PROT | 394| |DISCARDS | 0| 1813|
LOCAL-DGM | 3479964| |NO-ROUT | | 0|
REAS-TOUT | 0| |REAS-REQD | 28| |
REAS-OK | 28| |REAS-FAIL | 0| |
FRAG-OK | | 145|FRAG-FAIL | | 23|
FRAG-CREATE| | 290|ROUT-DISC | 0| |
------------------------------------------------------------------------
ICMP Statistics
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
MSG | 5294| 37497|ERR | 334| |
DEST-UNRICH| 1382| 33732|T-EXCEED | 23| 573|
PARM-PROB | 0| 0|SRC-QUENCH | 1| 0|
REDIRECT | 615| 0|ECHO | 3176| 16|
ECHO-REP | 97| 3176|TSTAMP | 0| 0|
TSTAMP-REP | 0| 0|ADMASK | 0| 0|
ADMASK-REP | 0| 0|
------------------------------------------------------------------------

19.7. IPFLOW Tracer

IPFLOW is a service used to trace IP packets flow inside IPRTR resource. Using a detailed filter is possible to trace only
required IP packets starting from incoming interface to outgoing interface or internal upper layers.

Each IP packet makes a list of several steps inside IPRTR (not all steps are made by all packets, this could depend by
configuration and by packet type):

PACKET IN packet is received from an IP resource interface;

IPACL CHECK packet is analyzed by IPACL service;

301
Draft IPRTR - IP Router Draft

IPSEC DECODE packet received in IPSEC format is decoded from ciphered to plain format;

NAT packet is translated by NAT rules.

INTERNAL DESTINATION packet is forwarded to internal upper layers.

EXTERNAL DESTINATION packet is going to be routed to an outgoing IP resource interface.

IPSEC ENCODE packet is ciphered into IPSEC format.

PACKET OUT packet is sent to an outgoing IP resource interface.

For each step, IPFLOW displays some information related to IP packet and some others related to step itself. For example,
during PACKET IN step we can have:

Packet IN:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
SIP:4 SRC-MAC:00-1E-8C-D5-5E-16 DST-MAC:00-0C-42-07-47-97 DST-MAC-TYPE:U

In the previous example we can see 2 rows. First row is related to IP packet and contain information about its fields, like
source IP address (SA), destination IP address (DA), IP protocol (PROT), source and destination protocol port (SPO and
DPO, shown only for TCP/UDP protocols) and packet length (LEN). This row can be present for each step if current values
differ from information printed on previous step.

Second row contains information related only to Packet IN step like source IP interface (SIP), source MAC address (SRC-
MAC), destination MAC address (DST-MAC), destination MAC type (DST-MAC-TYPE). Each step contain specific
information related to its purpose.

19.7.1. List of commands

To see all the commands present for IPFLOW tracer service is possible to use the command ipflow ?; the IPFLOW tracer to
be used needs to be activated first, and then started.

[18:48:37] ABILIS_CPX:ipflow ?

ACT Activate trace

DISPLAY Ipflow display operations
FILTER Packet filtering rules
INACT Deactivate trace
PARAM Trace parameters operations
START Start trace
STOP Stop trace

19.7.2. Activating the IPFLOW tracer

IPFLOW tracer must be activated before being used. The activation command allows abilis system to allocate memory
required to store packet traced. During activation of this service is possible to specify maximum number of IP packets that
can be stored (SIZE) and the possibiliy to use a circular list of IP packets (RECIRCLE). We can see the ranges of activation
parameters using ipflow act ? command.

[18:48:42] ABILIS_CPX:ipflow act ?

IPFLOW ACT [par:val] Activate trace

Trace parameter(s):

SIZE: Tracer packet number [100..10000] <Optional>

RECIRCLE: Tracer can recirculate [NO, YES] <Optional>

Caution
When activating IPFLOW tracer, is possibile that abilis system doesn't have enough memory to allocate
required buffer. In this case, will be printed a COMMAND FAILURE message. See below:

[16:00:40] ABILIS_CPX:ipflow act size:10000

302
Draft IPRTR - IP Router Draft

COMMAND FAILURE

IPFLOW tracer cannot be activated if it was already activated previously. If IPFLOW needs to be re-activated (e.g. in
case that SIZE or RECIRCLE value must be changed), it must be deactivated first. This is what happen when IPFLOW is
activated twice before deactivating it.

[16:00:50] ABILIS_CPX:ipflow act size:5000 recircle:no

IPFLOW TRACER ALREADY ACTIVE

Setting recircle to NO will make IPFLOW service to trace only first SIZE packets. Once that limit is reached, no more
packets will be traced until tracer is stopped and started again. If recircle is set to YES, once reached SIZE packets number
during tracing, the olders packet will be removed to allow tracing of the new one.

During activation command, in case that parameters are set with an invalid value, a specific error message code will be
printed about. For example:

[16:13:29] ABILIS_CPX:ipflow act size:99999999

BAD VALUE 'SIZE:99999999'

19.7.3. Deactivating the IPFLOW tracer

When IPFLOW is not more used, it can be deactivated in order to deallocate memory that could be useful for other run-time
services present into abilis system (like TRACE for example).

[18:49:27] ABILIS_CPX:ipflow inact ?

IPFLOW INACT Deactivate trace

To deactivate IPFLOW tracer, ipflow inact command is used.

[16:35:25] ABILIS_CPX:ipflow inact

COMMAND EXECUTED

Caution
Once IPFLOW is no more active, all the IP packets traced previously will be lost.

There are some situation where IPFLOW cannot be deactivated. This could happen in case that IPFLOW wasn't activated
before, or in case that IPFLOW is started but not stopped yet. In this case some related error message will be printed.

[16:31:04] ABILIS_CPX:ipflow inact

IPFLOW TRACER NOT ACTIVE

[16:31:13] ABILIS_CPX:ipflow inact

IPFLOW TRACER NOT STOPPED

19.7.4. Starting the IPFLOW tracer

Once IPFLOW tracer is activated, it must be started to make packet trace.

[18:59:27] ABILIS_CPX:ipflow start ?

IPFLOW START Start trace

To start IPFLOW tracer, ipflow start command is used.

[19:35:25] ABILIS_CPX:ipflow start

COMMAND EXECUTED

303
Draft IPRTR - IP Router Draft

When IPFLOW is started, all the packet that matches with specified filtering parameters will be traced and stored into tracer
list. Up to SIZE packets can be store at the same time.

There are some situation where IPFLOW cannot be started. This could happen in case that IPFLOW wasn't activated before,
or in case that IPFLOW is already started but not stopped yet. In this case some related error message will be printed.

[16:31:04] ABILIS_CPX:ipflow start

IPFLOW TRACER NOT ACTIVE

[16:31:13] ABILIS_CPX:ipflow start

IPFLOW TRACER ALREADY STARTED

Everytime trace is started, all the previous counters and IP packets traced will be automatically erased.

19.7.5. Stopping the IPFLOW tracer

Once IPFLOW has traced what we need, it can be stopped by the specific stop command.

[18:49:27] ABILIS_CPX:ipflow stop ?

IPFLOW STOP Stop trace

To stop IPFLOW tracer, ipflow stop command is used.

[16:35:25] ABILIS_CPX:ipflow stop

COMMAND EXECUTED

When IPFLOW is stopped, no other packets will be analyzed and traced (in case that they matches with filter configured).

There are some situation where IPFLOW cannot be stopped. This could happen in case that IPFLOW wasn't activated and
started before. In this case some related error message will be printed.

[17:51:53] ABILIS_CPX:ipflow stop

IPFLOW TRACER NOT ACTIVE

[17:51:59] ABILIS_CPX:ipflow stop

IPFLOW TRACER NOT STARTED

19.7.6. Display of IPFLOW parameters

Is possible to see IPFLOW parameters currently configured and tracing status.

[18:25:20] ABILIS_CPX:ipflow param ?

IPFLOW PARAM Display trace parameters

To display IPFLOW tracer parameters and status, ipflow param command is used.

[18:27:39] ABILIS_CPX:ipflow param

Parameter Value Description

-------------------------------------------------------------------------------
SIZE: 10000 Tracer packets number
RECIRCLE: YES Tracer packet recirculation
STATUS: INACTIVE Current status of ipflow trace
ANALYZED: 0 Number of packets analyzed
CAPTURED: 0 Number of packets currently traced

SIZE and RECIRCLE fields contain values previously set during ipflow act command. In case that ipflow act is executed
without specifying them, value used will be that indicated by ipflow param command.

304
Draft IPRTR - IP Router Draft

Status field indicates the IPFLOW tracing state. It can have several values:

INACTIVE tracer is not activated yet. No resources are currently allocated;

ACTIVE tracer is activated but not started yet. Resources are currently allocated but tracing is not performed;

RUNNING tracer is activated and started. All IP packets that matches filtering rules are stored into tracer list;

ANALYZED and CAPTURED fields can increase their number only during RUNNING status. ANALYZED field indicates
all the IP packets being analyzed by IPFLOW that could be tracer or not depending on filtering options. CAPTURED
contains only all that IP packets that after being analyzed by IPFLOW, they matched with filtering rules and then were stored
into tracer list. These fields are initialized everytime that IPFLOW tracer is started.

19.7.7. Setting IP packet filter

When IPFLOW is started, packet are traced following specific rules that can be configured with the following commands:

[18:49:02] ABILIS_CPX:ipflow filter ?

IPFLOW FILTER [DISPLAY [ID:val]] Display trace filter(s)

IPFLOW FILTER ADD ID:val [par:val] Add new trace filter
IPFLOW FILTER CLEAR ID:val [par:val] Clear existing trace filter
IPFLOW FILTER USED Display used trace filters
IPFLOW FILTER SET ID:val par:val [par:val] Set trace filter parameters

ID: Ipflow filter identifier [0..31] <Optional>

Ipflow filter parameter(s):

SNET: Source Ip Network Range: <Optional>

a single Ip address [0.0.0.1-255.255.255.255] or subnet [x.x.x.x/y]
or Ip addresses range separated by ':' (colon) or or the name of
an IP/IR/RU/MR list between primes or "*" (any Ip address)
DNET: Destination Ip Network Range: <Optional>
a single Ip address [0.0.0.1-255.255.255.255] or subnet [x.x.x.x/y]
or Ip addresses range separated by ':' (colon) or or the name of
an IP/IR/RU/MR list between primes or "*" (any Ip address)
NET: Source OR Destination Ip Network Range: <Optional>
a single Ip address [0.0.0.1-255.255.255.255] or subnet [x.x.x.x/y]
or Ip addresses range separated by ':' (colon) or or the name of
an IP/IR/RU/MR list between primes or "*" (any Ip address)
PROT: Internet Protocol: <Optional>
Internet protocol mnemonic or decimal value [0..255] or "*" (Any
Internet protocol) or the name of an IPT/RU/MR list between primes.
(E.g.: icmp or 1 or * or 'List)
SPO: Source Ports Range: <Optional for PROT:TCP/UDP>
a single port mnemonic or decimal value [0..65535] or a port range
values separated by ':' (colon) or "*" (any port) or the name of a
TUP/RU/MR list between primes. (E.g.: 23 or SSH or 1:1200 or 'List')
DPO: Destination Ports Range: <Optional for PROT:TCP/UDP>
a single port mnemonic or decimal value [0..65535] or a port range
values separated by ':' (colon) or "*" (any port) or the name of a
TUP/RU/MR list between primes. (E.g.: 23 or SSH or 1:1200 or 'List')
PO: Source or Destination Ports Range: <Optional for PROT:TCP/UDP>
a single port mnemonic or decimal value [0..65535] or a port range
values separated by ':' (colon) or "*" (any port) or the name of a
TUP/RU/MR list between primes. (E.g.: 23 or SSH or 1:1200 or 'List')
SIP: Source Ip resource [1..250, INT, *] <Optional>

Up to 32 filters can be set using a fixed identifier. Each filter record can be added, removed and set in every tracing moment,
but the values really used by IPFLOW will be during the execution of ipflow start command. In fact, we can distinguish
between 2 different display commands:

IPFLOW FILTER [DISPLAY] all filters present will be loaded and used by IPFLOW after ipflow start command;

305
Draft IPRTR - IP Router Draft

IPFLOW FILTER USED filter displayed in this command are exactly filters used during tracing phase
(RUNNING state);

Using ipflow filter used command when IPFLOW is not in running state will display empty information:

[11:59:00] ABILIS_CPX:ipflow filter display

-------------------------------------------------------------------------------
ID: SNET:/NET: DNET:
SIP: PROT:
SPO:/PO: DPO:
-------------------------------------------------------------------------------
0 192.168.000.005 192.168.000.200
4 tcp
telnet(23)
-------------------------------------------------------------------------------

[11:59:35] ABILIS_CPX:ipflow filter used

-------------------------------------------------------------------------------
ID: SNET:/NET: DNET:
SIP: PROT:
SPO:/PO: DPO:
-------------------------------------------------------------------------------
*** NO USED FILTERS ***

If ipflow filter used command is executed during running state, will be shown filters currently in use by IPFLOW:

[12:06:20] ABILIS_CPX:ipflow filter display

-------------------------------------------------------------------------------
ID: SNET:/NET: DNET:
SIP: PROT:
SPO:/PO: DPO:
-------------------------------------------------------------------------------
0 192.168.000.005 192.168.000.200
4 tcp
telnet(23)
-------------------------------------------------------------------------------

[12:06:24] ABILIS_CPX:ipflow filter used

-------------------------------------------------------------------------------
ID: SNET:/NET: DNET:
SIP: PROT:
SPO:/PO: DPO:
-------------------------------------------------------------------------------
0 192.168.000.005 192.168.000.200
4 tcp
telnet(23)
-------------------------------------------------------------------------------

In order to reset ipflow filter used display, user must be execute ipflow inact command.

19.7.8. IPFLOW trace display

To display what IPFLOW has traced, ipflow display command is used. For example:

--------------------------------------------------------------------------------
REC: 1
Packet IN:
SA:192.168.000.200 DA:192.168.000.005 PROT:tcp SPO:23 DPO:2768 LEN:552
SIP:INTERNAL
NAT:

306
Draft IPRTR - IP Router Draft

IncomingSide:OUTSIDE
DstRC:NONE
SrcRC:NONE
External destination:
DIP:4 DST-GW:DIRECT
Packet OUT:
DIP:4 SRC-MAC:00-00-00-00-00-00 DST-MAC:00-00-00-00-00-00
DST-GW:192.168.000.005
Main return Code: GOOD
--------------------------------------------------------------------------------
REC: 2
Packet IN:
SA:192.168.000.200 DA:192.168.000.005 PROT:tcp SPO:23 DPO:2768 LEN:552
SIP:INTERNAL
NAT:
IncomingSide:OUTSIDE
DstRC:NONE
SrcRC:NONE
External destination:
DIP:4 DST-GW:DIRECT
Packet OUT:
DIP:4 SRC-MAC:00-00-00-00-00-00 DST-MAC:00-00-00-00-00-00
DST-GW:192.168.000.005
Main return Code: GOOD
--------------------------------------------------------------------------------
REC: 3
Packet IN:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
SIP:4 SRC-MAC:00-1E-8C-D5-5E-16 DST-MAC:00-0C-42-07-47-97 DST-MAC-TYPE:U
NAT:
IncomingSide:OUTSIDE
DstRC:NONE
SrcRC:NONE
Internal destination:
Packet forwarded to internal tcp upper layer
Main return Code: GOOD (TCP)

Display command can be executed only if IPFLOW has been activated.

[12:43:40] ABILIS_CPX:ipflow display

IPFLOW TRACER NOT ACTIVE

IPFLOW Display usually is made after ipflow stop command, but it can be done also during running state.

Caution
During display command on running state, ABILIS system can generate IP packets by its own (commonly
TELNET/SSH packet if user is connected remotely by such protocols). If these packets match with IPFLOW
filter, we'll have that IPFLOW trace its own packets generated. In such situation, ipflow display command
will terminate with a "IPFLOW TRACER BUFFER UNDERRUN" message.

Each IP packet record stored has the complete flow of packet inside IPRTR. As written previously, there are several steps
that a packet can follow. Here we have them in detail.

19.7.8.1. BASIC INFORMATION

STEP XXX:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40

For each step of the record (e.g. PACKET IN, IPACL, NAT...) there are present some information about IP packet. These
information are displayed in a single row. If packet information is the same of previous step (data is still unchanged)
this information will be omitted. Usually IP packet information can change during IPSEC or NAT steps. Basic IP packet
information indicates:

307
Draft IPRTR - IP Router Draft

SA Source IP address;

DA Destination IP address;

PROT IP carried protocol;

SPO Source port of carried protocol (TCP or UDP);

DPO Destination port of carried protocol (TCP or UDP);

ID Identifier of carried protocol (ICMP);

LEN IP packet length;

19.7.8.2. PACKET IN
Packet IN:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
SIP:4 SRC-MAC:00-1E-8C-D5-5E-16 DST-MAC:00-0C-42-07-47-97 DST-MAC-TYPE:U

Second row contains these information:

SIP Source IP resource. It is the IP resource where packet come from. It can have several values indicating
incoming interface or INTERNAL in case that packet has been generated internally by ABILIS system;

SRC-MAC This is the source MAC address of the sender of the packet. MAC address is related to ETHERNET
layer;

DST-MAC This is the destination MAC address of the receiver of the packet. MAC address is related to
ETHERNET layer (in this step the receiver MAC address will be the one present on the ABILIS ethernet
card);

DST-MAC-TYPE MAC destination type of the packet received. This information is detected by lower layer and can
indicate 3 different types;

U Unicast: packet: is for a single receiver;

B Broadcast: packet: is for all the receivers present on that specific network;

M Multicast: packet: is for selective receivers present on that specific network;

19.7.8.3. IPACL CHECK

IPACL check:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
IPACL ID:1 IPCOS:NORMAL CRDIR:ENCRYPT CRKEY:DFT

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second row contains these information:

IPACL Contain the number of IPACL matched by IP packet. In case of no match, there will be printed NO-MATCH and
all the following fields will be omitted;

IPCOS Class of service (priority) applied to IP packet. It can be:

HIGH High priority, packet will be threated with the highest priority;

NORMAL Normal priority, packet will be threated with middle priority;

LOW Low priority, packet will be threated with the lowest priority;

CRDIR Ciphering mode. This information can have 3 different types;

NONE IP Packet format is not changed;

308
Draft IPRTR - IP Router Draft

ENCRYPT IP Packet is ciphered;

DECRYPT IP packet is deciphered;

CRKEY This field is present only in case that CRDIR is set as ENCRYPT/DECRYPT. It contains the CRKEY used for
ciphering algorithm;

19.7.8.4. IPSEC DECODE

IPSEC decode:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
RetCode:GOOD Tunnel:YES NatSide:INSIDE IntDst:YES

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second row contains these information:

RetCode Contain the result of the IPSEC management of the IP packet. It can have several results:

GOOD IP packet has been correctly managed by IPSEC service;

REASS IP packet is only a fragment of a bigger packet. It needs to be reassembled before being managed
by IPSEC service;

BYPASSED IP packet has been analyzed and bypassed. No additional IPSEC operations were done to packet;

DROPPED IP packet has been analyzed and discarded. Due to IPSEC rules, IP packet cannot be forwarded;

Tunnel Indicates if packet decoded is taken from an IPSEC tunnel;

NatSide Upon decoding an IP packet from tunnel, it can have different side types:

NONE Tunnel hasn't a NAT side;

INSIDE Tunnel has an INSIDE side;

OUTSIDE Tunnel has an OUTSIDE side;

VPN Tunnel has a VPN side;

DMZ Tunnel has a DMZ side;

NP Side not present. This situation happens when IPSEC return code is not good;

IntDst This is simply a flag indicating if packet decoded by IPSEC will have ABILIS system as final destination;

19.7.8.5. NAT
NAT:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
IncomingSide:OUTSIDE
DstRC:GOOD OutgoingIPRes:IP-4 OutgoingSide:INSIDE Added:YES
SrcRC:GOOD OutgoingIPRes:IP-4 OutgoingSide:INSIDE Added:YES
IPSecOutgoingSide:INSIDE

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second and next rows contain these information:

IncomingSide Contains the NAT side of the interface where IP packet comes from. It can be:

309
Draft IPRTR - IP Router Draft

NONE Packet comes from a NONE NAT side;

INSIDE Packet comes from an INSIDE NAT side;

OUTSIDE Packet comes from an OUTSIDE NAT side;

VPN Packet comes from a VPN NAT side;

DMZ Packet comes from a DMZ NAT side;

DstRC/SrcRC Contain the return code of the NAT processing phase to IP packet (processes are separated
between source and destination):

GOOD Packet has been translated;

INACT NAT service is not active;

NONE Packet is not translated;

TCPRESET TCP session cannot be opened, a RESET message will be sent to the originator of
the TCP packet;

CHKSUMERR Packet received has a bad checksum and it will be discarded;

This field will be hidden in case that DstRC/SrcRC are set to NONE.

OutgoingIPRes Destination IP resource. It is the IP resource where packet is going to be sent.

OutgoingSide Contain the NAT side of the interface where IP packet is going to be sent. It can be:

INSIDE Packet is going to an INSIDE NAT side;

OUTSIDE Packet is going to an OUTSIDE NAT side;

VPN Packet is going to a VPN NAT side;

DMZ Packet is going to a DMZ NAT side;

This field will be hidden in case that DstRC/SrcRC are set to NONE.

Added Indicates that current IP packet has made NAT to add a translation rule into its dynamic table
(this value is present only in case that translation is created. In all other situation this field will be
hidden);

IPSecOutgoingSide Is possible that a packet could be encoded by IPSEC into a tunnel In case of IPSEC tunnel, it can
have following values:

NONE Tunnel hasn't a NAT side;

INSIDE Tunnel has an INSIDE side;

OUTSIDE Tunnel has an OUTSIDE side;

VPN Tunnel has an VPN side;

DMZ Tunnel has an DMZ side;

NP Side not present. This situation happens when IPSEC return code is not good;

19.7.8.6. INTERNAL DESTINATION

Internal destination:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
Packet forwarded to internal tcp upper layer

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

310
Draft IPRTR - IP Router Draft

This step hasn't additional information to show. Only a single descriptive row is present to indicate that IP packet destination
is ABILIS itself, indicating which IP protocol will manage it.

19.7.8.7. EXTERNAL DESTINATION

External destination:
SA:192.168.000.005 DA:192.168.010.200 PROT:tcp SPO:2768 DPO:23 LEN:40
DIP:3 DST_GW:192.168.10.001
LoadBalance:1

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second and next rows contain these information:

DIP Destination IP resource. It is the IP resource where packet is sent.

DST-GW This indicated which is the IP gateway where IP packet will be forwarded. If the receiver host is directly
on the same network and there is no need of a gateway, will be printed DIRECT instead;

LoadBalance In case of load-balancing, this will indicate which is the pool of IP resources where IP packet could be
sent. In case of no load-balancing detected, this row will be missing;

19.7.8.8. IPSEC ENCODE

IPSEC encode:
SA:192.168.000.005 DA:192.168.000.200 PROT:tcp SPO:2768 DPO:23 LEN:40
RetCode:GOOD Tunnel:YES NatSide:OUTSIDE

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second row contains these information:

RetCode Contain the result of the IPSEC management of the IP packet. It can have several results:

GOOD IP packet has been correctly managed by IPSEC service;

REASS IP packet is only a fragment of a bigger packet. It needs to be reassembled before being managed
by IPSEC service;

BYPASSED IP packet has been analyzed and bypassed. No additional IPSEC operations were done to packet;

DROPPED IP packet has been analyzed and discarded. Due to IPSEC rules, IP packet cannot be forwarded;

Tunnel Indicates that packet encoded will go into an IPSEC tunnel;

NatSide Upon encoding an IP packet for IPSEC tunnel, it can have different side types:

NONE Tunnel hasn't a NAT side;

INSIDE Tunnel has an INSIDE side;

OUTSIDE Tunnel has an OUTSIDE side;

VPN Tunnel has a VPN side;

DMZ Tunnel has a DMZ side;

NP Side not present. This situation happens when IPSEC encoding return code is not good;

19.7.8.9. PACKET OUT

Packet OUT:

311
Draft IPRTR - IP Router Draft

SA:192.168.000.005 DA:192.168.010.200 PROT:tcp SPO:2768 DPO:23 LEN:40

DIP:1 SRC-MAC:00-00-00-00-00-00 DST-MAC:00-00-00-00-00-00
DST-GW:192.168.10.001

Caution
First description row about IP packet fields will be hidden in case that all the fields will be the same of
previous step.

Second and next rows contain these information:

DIP Destination IP resource. It is the IP resource where packet is sent.

SRC-MAC This is the source MAC address of the sender of the packet. MAC address is related to ETHERNET layer (in
this step the sender MAC address will be the one generated by ABILIS. Usually it will be 00-00-00-00-00-00
except for specific protocol usage, e.g. like DHCP);

DST-MAC This is the destination MAC address of the receiver of the packet. MAC address is related to ETHERNET layer
(in this step the receiver MAC address will be the one present on the outgoing interface network. Usually it will
be 00-00-00-00-00-00 except for specific protocol usage, e.g. like DHCP);

312
Draft Draft

Chapter 20. NAT - Network Address

Translation
Marco Bellesia
Luigi Demuro

Table of Contents
20.1. NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.1. Frequently used expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
20.1.2. Activating the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
20.1.3. NAT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
20.2. NAT Aliases table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.1. D NAT (Display NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
20.2.2. A NAT (Add NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
20.2.3. C NAT (C NAT alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
20.2.4. S NAT (Set NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
20.2.5. M NAT (Move NAT Alias) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
20.2.6. INIT RES:NAT and INIT NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
20.3. NAT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.1. NAT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.2. NAT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
20.3.3. Debug of the NAT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
20.4. Examples of NAT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.1. Suggest an access from inside workstations to outside networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
20.4.2. Suggest an access from outside networks to internal servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
20.4.3. Configuring a DMZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

20.1. NAT resource

Abilis implements NAT1 (Network Address Translation) with PAT2 (Port Address Translation) and IPACL (IP Access
Control List) services.

By properly specifying:

• source IP address or network;

• destination IP address or network;
• source UDP/TCP port;
• destination UDP/TCP port;
• sSource/Destination IP resource;
• TOS (Type of Service) for packets priority management by services;

a high level of security is granted.

Note
Abilis is not a Firewall! It implements basic firewall function, but evolved features must be commissioned to
a “real” firewall. Abilis and firewall can coexist with no problems.

20.1.1. Frequently used expression

• Inside. The set of networks there are subject of translation, usually “private” networks.

1
http://en.wikipedia.org/wiki/Network_address_translation
2
http://en.wikipedia.org/wiki/Port_address_translation

313
Draft NAT - Network Address Translation Draft

• Outside. All other networks, usually “public” addresses located on the Internet.
• Inside local IP address. The IP address which was assigned to a host on the inside network.
• Inside global IP address. The IP address of an inside host as it appears to the outside networks. If, as usual, the outside
network is the Internet, the address must be one of the “public” addresses which the ISPs have assigned to user's router for
those connections. In the table of NAT Aliases this term called as ANET:.
• Processed IP packet. It mean in this packet was changed a source or destination address in some cases a source or
destination port was changed too.
• Ignored IP packet. It mean that this packet was not changed.
• Static Address Translation. The user can establish a one-to-one mapping between the inside local and global addresses,
which happens when the number (netmask) of inside local and global addresses are identical.
• Dynamic Source Address Translation. The user can establish dynamic mapping between the inside and global addresses,
which happens when the number (netmask) of inside local and global addresses are different.
• Port Address Translation (PAT). The user can save addresses in the global address pool by allowing source ports in TCP
connections or UDP conversations to be translated. Different local addresses will be mapped to the same global address,
with port translation providing the necessary uniqueness for TCP/UDP and other tricks providing uniqueness for ICMP.
• Extended filtering in PAT mode. The purpose of this feature is to allow a selective activation of the PAT translation
based on the destination TCP/UDP port and on the IP protocol, with the result that network managers can empower their
control of the network by:
• Granting access only to some service, e.g. web and ftp.
• Blocking access only to specific services, e.g. realaudio / realvideo servers
• Precisely distinguishing inbound connections from outbound ones
• Allowing internal users to access ANY service on the Internet while outside users may access only a restricted set
• Destination port mapping. This behaviour is very useful in many situations, the most frequents are:
• The user has just one public IP address and on the internal LAN there are more computers on several IP addresses
running different services that must be reached from outside, e.g. FTP, HTTP, SMTP and so on
• The user has just one public IP address and on the internal LAN there are more computers on several IP addresses
running the same service with different contents, e.g. a commercial web, a technical web, a restricted access web.

20.1.2. Activating the NAT resource

Add the resource to the Abilis system with the command:

[11:01:39] ABILIS_CPX:a res:nat

RES:NAT ALREADY EXISTS

The NAT resource may already exist in the system, but may not yet be active: set it active with the command:

[11:01:48] ABILIS_CPX:s act res:nat

COMMAND EXECUTED

Caution
After adding or setting the NAT active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[11:01:39] ABILIS_CPX:s p nat act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p nat

RES:Nat - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

Run DESCR:Network_Address_Translator
LOG:DS ACT:YES dimtable:1000
DNS-ALG:NO SNMP-ALG:NO PPTP-ALG:NO IKE-AWARE:YES
- Not PAT mode parameters ----------------------------------------------
TOUT:3600
- PAT mode parameters --------------------------------------------------
FRAG:5 ICMP:5 DNS:5 SNMP:5 SNTP:5
UDP-OPENING:5 UDP-CONN:180
TCP-OPENING:5 TCP-CONN:360 TCP-CLOSING:15 TCP-CLOSED:1

314
Draft NAT - Network Address Translation Draft

TCP-RST:YES PPTP-CONN:360
INSIDE-MIL:300 OUTSIDE-MIL:50 VPN-MIL:NOLIMIT DMZ-MIL:NOLIMIT
MIL-TIME:2

20.1.3. NAT resource parameters

Use the following command to display resource parameters; teh command d p nat ? displays the meaning of all parameters.

[11:01:39] ABILIS_CPX:d p nat

RES:Nat -----------------------------------------------------------------------
Run DESCR:Network_Address_Translator
LOG:DS ACT:YES dimtable:1000
DNS-ALG:NO SNMP-ALG:NO PPTP-ALG:NO IKE-AWARE:YES
- Not PAT mode parameters ----------------------------------------------
TOUT:3600
- PAT mode parameters --------------------------------------------------
FRAG:5 ICMP:5 DNS:5 SNMP:5 SNTP:5
UDP-OPENING:5 UDP-CONN:180
TCP-OPENING:5 TCP-CONN:360 TCP-CLOSING:15 TCP-CLOSED:1
TCP-RST:YES PPTP-CONN:360
INSIDE-MIL:300 OUTSIDE-MIL:50 VPN-MIL:NOLIMIT DMZ-MIL:NOLIMIT
MIL-TIME:2

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT NAT runtime activation/deactivation.

dimtable It specifies how many translations can be created at the same time.

DNS-ALG Enable/disable DNS Application Level Gateway [NO, YES]

SNMP-ALG Enable/disable SNMP Application Level Gateway [NO, YES]

PPTP-ALG Enable/disable PPTP Application Level Gateway [NO, YES]

IKE-AWARE Enable/disable IKE awareness. Minimise remap of UDP ports 500 and 4500 [NO, YES]

TOUT This value sets the timeout of static and dynamic translations, i.e. those created without the PAT mode. If
the translation is not used for the specified time (i.e. no packets need it), it times out and it has removed by
the translation table.

FRAG Time-out for linkable fragment identifier [1..240 sec]

ICMP Time-out for ICMP link type [1..240 sec]

DNS Time-out for DNS link type [1..240 sec]

SNMP Time-out for SNMP link type [1..240 sec]

SNTMP Time-out for SNTP link type [1..240 sec]

UDP-OPENING Time-out for UDP links in Opening state [1..240 sec]

UDP-CONN Time-out for UDP links in Connected state [60..65535 sec]

TCP-OPENING Time-out for TCP links in Opening state [1..240 sec]

TCP-CONN Time-out for TCP links in Connected state [60..65535 sec]

TCP-CLOSING Time-out for TCP links in Closed state [1..240 sec]

TCP-RST Enable sending of RESET for expired links [NO, YES]

PPTP-CONN Time-out for PPTP links in Connected state [60..65535 sec]

INSIDE-MIL Maximal number of links that same IP address on INSIDE interface can open at the same time
[NOLIMIT, 1..10000]

315
Draft NAT - Network Address Translation Draft

OUTSIDE-MIL Maximal number of links that same IP address on OUTSIDE interface can open at the same time
[NOLIMIT, 1..10000]

VPN-MIL Maximal number of links that same IP address on VPN interface can open at the same time [NOLIMIT,
1..10000]

DMZ-MIL Maximal number of links that same IP address on DMZ interface can open at the same time [NOLIMIT,
1..10000]

MIL-TIME Resync time used for maximal initiator links procedure [2..30 sec]

The following command allows the administrator to change the configuration of the resource:

s p nat parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:nat;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

20.2. NAT Aliases table

The table of NAT Aliases can store up to 255 entries, indexed starting from 0 up to 254.

The entry priority index sets the entries verification order and must be sequential. The priority index for NAT Aliases is used
as a reference for operations of insertion, modification and deletion.

Commands for handling the table of NAT Aliases are the following:

• d nat

• a nat

• c nat

• s nat

• m nat

Changes made in the table are activated by executing the command init nat without needing to restart Abilis CPX.

20.2.1. D NAT (Display NAT alias)

This command shows the content of the Table of NAT Alias.

[16:41:45] ABILIS_CPX:d nat

UPNP maps not present

Configured maps
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC 192.168.000.000/24 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.001.000/24 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 010.100.100.000/24 * OUT-IP
OUT * * AUTO YES

316
Draft NAT - Network Address Translation Draft

-------------------------------------------------------------------------------
3 OUT DST * 083.211.161.025/32 083.211.161.025/32
IN * * * YES
-------------------------------------------------------------------------------

NAT supports 4 divided zones: INSIDE, OUTSIDE, DMZ, VPN (an ip resource can be assigned freely to one of these
zones).

Meaning of parameters:

PR NAT alias entry priority [A, 0..254].<Optional>

INAT Input NAT [NONE, IN (or INSIDE), OUT (or OUTSIDE), VPN, DMZ] Values can be joined using ',' character.
<Optional>

ONAT Output NAT [NONE, IN (or INSIDE), OUT (or OUTSIDE), VPN, DMZ] Values can be joined using ',' character.
<Optional>

SIP Source IP resource [1..250, *, NONE]

DIP Destination IP resource [1..250, *, NONE]

ADD Address translation type [SRC, DST]

SNET Source Network IP address [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] and mask length [0-32] or "*" or the
name of an IP/IR/RU/MR list for network IP addresses between primes or "Ip-nnn", where 'nnn' is an IP resource
index in [1..250]. (E.g.: * or 192.168.0.1/32 or 'ListName' or Ip-23)

SPO Allowed source TCP/UDP port(s): <Only for PROT:TCP/UDP> a single port mnemonic or decimal value [1..65535]
or two port values separated by ':' (colon) or "*" (Any port) or the name of a TUP/RU/MR list between primes (E.g.:
22 or SSH or 1:1024 or * or 'List')

PROT Allowed IP protocols [ICMP, TCP, UDP, *, NONE]. <Only for PAT:YES> Values can be joined using ',' character.

DNET Destination Network IP address [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] and mask length [0-32] or "*" or the
name of an IP/IR/RU/MR list for network IP addresses between primes or "Ip-nnn", where 'nnn' is an IP resource
index in [1..250]. (E.g.: * or 192.168.0.1/32 or 'ListName' or Ip-23)

DPO Allowed destination TCP/UDP port(s): <Only for PROT:*|TCP|UDP> a single port mnemonic or decimal value
[1..65535] or two port values separated by ':' (colon) or "*" (Any port) or the name of a TUP/RU/MR list between
primes (E.g.: 22 or SSH or 1:1024 or * or 'List')

TOUT Translation time-out of the entry[SYS, 60..65535 sec]

ANET Alias network IP address [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x] and mask length [0-32] or "OUT-IP" or "Ip-
nnn", where 'nnn' is an IP resource index in [1..250]. (E.g.: 192.168.0.1/32 or OUT-IP or Ip-1)

APO Alias source or destination TCP/UDP port: <Only for PROT:*|TCP|UDP> a single port mnemonic or decimal value
[1..65535] or "*" (leaves the port unchanged) or AUTO (for ADD:SRC assigns a dynamic and currently unused port
number, for ADD:DST behaves like "*") (E.g.: SSH or 22 or * or AUTO) The aliased port is 'SPO' for ADD:SRC
records and 'DPO' for ADD:DST.

PAT Port address translation [NO, YES]

Type the command d nat ? to view available options.

20.2.2. A NAT (Add NAT alias)

This command adds a new entry in the Table of NAT Alias with “PR:xxx” priority and it may set the parameters to the
specified values.

The syntax of the command is:

a nat pr:xxx [par:val]

[17:28:09] ABILIS_CPX:d nat

UPNP maps not present

317
Draft NAT - Network Address Translation Draft

Configured maps
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------

[17:29:36] ABILIS_CPX:a nat pr:1 inat:in onat:out add:src snet:192.168.5.0/24 anet:217.1.1.1/32 pat

COMMAND EXECUTED

[16:47:33] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

Tip
Interesting chapters:

Section 20.4, “Examples of NAT configuration”;

Section 52.7, “How to configure the Network Address Translation (NAT)”;

Section 52.9, “How to access IP hosts and services which are behind a NAT manager (port forwarding)”.

20.2.3. C NAT (C NAT alias)

This command removes from the Table of NAT Alias the entry, whose priority is “PR:xxx”. Next entries are decremented by
one, so that the table is still contiguous.

The syntax of the command is:

c nat pr:xxx

[17:36:39] ABILIS_CPX:d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:

318
Draft NAT - Network Address Translation Draft

SIP: DIP: PROT: TOUT:

-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.004.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

[16:51:15] ABILIS_CPX:_c nat pr:2

COMMAND EXECUTED

[16:52:06] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

20.2.4. S NAT (Set NAT Alias)

It sets to new values the parameters of the NAT Alias entry specified by “PR:xxx”.

The syntax of the command is:

s nat pr:xxx par:val [par:val]

[16:52:06] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

[16:53:51] ABILIS_CPX:_s nat pr:1 snet:192.168.3.0/24 anet:217.1.1.2/32

319
Draft NAT - Network Address Translation Draft

COMMAND EXECUTED

[16:54:18] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.003.000/24 * 217.001.001.002/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

Tip
Interesting chapters:

Section 20.4, “Examples of NAT configuration”;

Section 52.7, “How to configure the Network Address Translation (NAT)”;

Section 52.9, “How to access IP hosts and services which are behind a NAT manager (port forwarding)”.

20.2.5. M NAT (Move NAT Alias)

It changes the NAT Alias entry priority value “PR:xxx” to “PR:yyy”. Therefore the entry position, inside the table, will be
changed and the whole table will be sorted again to guarantee its contiguity.

The syntax of the command is:

m nat pr:xxx pr:yyy

[16:55:44] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.003.000/24 * 217.001.001.002/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

[16:55:53] ABILIS_CPX:_m nat pr:2 pr:1

320
Draft NAT - Network Address Translation Draft

COMMAND EXECUTED

[16:56:06] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.003.000/24 * 217.001.001.002/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

20.2.6. INIT RES:NAT and INIT NAT

Description of commands:

• init nat: it refreshes the NAT static table and clears the NAT dynamic table content.

• init res:nat: it refreshes the NAT static table but DOESN'T clear the NAT dynamic table content.

The “Not Refreshed (INIT)” message is displayed every time the table is modified but not refreshed.

[16:56:37] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.003.000/24 * 217.001.001.002/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

[16:58:27] ABILIS_CPX:_init nat

COMMAND EXECUTED

[16:58:48] ABILIS_CPX:_d nat

321
Draft NAT - Network Address Translation Draft

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF) -------------------------------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 IN SRC 192.168.005.000/24 * 217.001.001.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.003.000/24 * 217.001.001.002/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

20.3. NAT diagnostics and statistics

20.3.1. NAT diagnostics
To display the diagnostics of the NAT resource the following commands are used:

d d nat / d de nat Shows diagnostic information, such as the state of the resource, the current number of
translations present into NAT table, the maximum number of translations reached from
start-up into the NAT table and the maximum number of translations present into the
table (this information indicate the dimtable parameter).

[18:06:40] ABILIS_CPX:d d nat

RES:Nat -----------------------------------------------------------------------
Network_Address_Translator
STATE:READY
-----------|--- CUR ---|-- PEAK ---|--- MAX ---|
LINKS | 68| 417| 1000|
------------------------------------------------

20.3.2. NAT statistics

To display the statistics of the NAT resource the following commands are used:

d s nat / d se nat Shows statistic information, such as the number of processed ICMP/TCP/UDP/FTP/
DNS/SNMP/SNTP packets, the number of processed FRAGMENT ID/FRAGMENT
POINTER packets, etc..

[18:06:40] ABILIS_CPX:d s nat

RES:Nat -----------------------------------------------------------------------
Network_Address_Translator
--- Cleared 0 days 02:44:37 ago, on 03/11/2010 at 14:16:24 -------------
REQ:1427707 SUCCESS:692528 IGNORED:734527
OVERFLOW:0 TCP-RST:230647 ERROR:0
FTP-OVR:0 DNS-OVR:0 SNMP-MF:0
FTP-BCT:0 DNS-EF:0 PPTP-MT:0
------------------------------------------------------------------------
-----------|---INSIDE--|--OUTSIDE--|----VPN----|----DMZ----|
BLOCKED | 649| 0| 0| 0|
------------------------------------------------------------------------
ICMP-ERR | 0| 0| 0| 0|

322
Draft NAT - Network Address Translation Draft

TCP-ERR | 0| 0| 0| 0|
UDP-ERR | 0| 0| 0| 0|
------------------------------------------------------------------------
ICMP-SRC | 0| 0| 0| 0|
ICMP-DST | 0| 673| 0| 0|
TCP-SRC | 111815| 0| 0| 0|
TCP-DST | 0| 97366| 0| 0|
UDP-SRC | 226209| 0| 0| 0|
UDP-DST | 0| 256465| 0| 0|
GRE-SRC | 0| 0| 0| 0|
GRE-DST | 0| 0| 0| 0|
OTHERS-SRC | 0| 0| 0| 0|
OTHERS-DST | 0| 0| 0| 0|
------------------------------------------------------------------------
ONATDISCARD| 0| 0| 0| 0|
------------------------------------------------------------------------
FRAG-ID:0 FRAG-POINTER:0
FRAG-UNRESOLVED:0 FRAG-HEADER-FOUND:0
------------------------------------------------------------------------

20.3.3. Debug of the NAT resource

Caution
To view these commands you need to have administrator or super user rights.

Type the following command to view allowed ones:

[00:07:36] ABILIS_CPX:debug res:nat lsn:0

RES:Nat -----------------------------------------------------------------------
Network_Address_Translator
BufferLength:1824 Date/Time:03/11/2010 17:06:51 TraceTime:10227853

Usage:
LSN:0 - This help (default).
LSN:1 - Debug unavailable: use D NAT MAPS instead.
LSN:2 - View statistics and information.
LSN:3 CMD:DISPLAY - Show current NAT trace (default).
LSN:3 CMD:ACT[,param,...] - Activate the trace.

List of NAT activate parameters (for LSN:3 CMD:ACT).

No parameters (default) - Trace all packets unconditionally.
CHK - Trace packets with wrong checksum.
TCPRST - Trace packets when NAT originates a TCP reset.
ERR - Trace packets that cause an error.
NOTLN - Trace packets ignore TELNET packets..
<IP add> - Trace packets only to/from these addresses (up to 4).

LSN:3 CMD:START - Start the trace.

LSN:3 CMD:STOP - Stop the trace.
LSN:3 CMD:INACT - Deactivate the trace.
LSN:4 - Display headers of last 10 packets with checksum error.
LSN:4 CMD:EXT - Display last 10 packets with checksum error.
LSN:4 CMD:CLR - Clear checksum failures history.
LSN:5 - View links between recods on the dynamic table.
LSN:6 CMD:CLR - Initialize Peak diagnostic information.
LSN:7 - View translation filter.
LSN:7 CDM:EXT - View translation filter with extended translation info.
LSN:8 - View configured table.
LSN:9 - View virtual table.
LSN:10 - View dynamic table.

323
Draft NAT - Network Address Translation Draft

LSN:11 - View dynamic table with TCP session status.

LSN:12 - Display information of last 10 UPNP commands.
LSN:12 CMD:CLR - Clear UPNP command history.
LSN:13 - Display information of last 20 packets with ONAT discard error.
LSN:13 CMD:CLR - Clear ONAT discard failures history

To view the current NAT sessions type (the command debug res:nat lsn:1 is no more available):

[00:10:18] ABILIS_CPX:d nat maps

Number of records in standard table: 21

S A TYPE SRC-ADDRESS SP/ID DST-ADDRESS DP/ID ALS-ADDRESS ALIAS TM

-------------------------------------------------------------------------------
IOS UDP 192.168.030.002 11826 086.101.152.080 26211 192.168.001.100 9060 180
IOS UDP 192.168.030.002 11826 080.230.085.012 30615 192.168.001.100 9061 54
IOS UDP 192.168.030.002 11826 084.097.119.138 41956 192.168.001.100 9247 93
IOS UDP 192.168.030.002 11826 200.117.084.037 45252 192.168.001.100 9063 180
IOS UDP 192.168.030.002 11826 077.083.166.003 34588 192.168.001.100 9064 180
IOS UDP 192.168.030.002 11826 151.021.081.198 32605 192.168.001.100 9068 164
IOS TCP 192.168.030.002 2220 095.076.135.237 18586 192.168.001.100 9109 360
IOS UDP 192.168.030.002 11826 077.030.154.190 41899 192.168.001.100 9206 58
IOS UDP 192.168.030.002 11826 095.250.024.242 34375 192.168.001.100 9250 104
IOS UDP 192.168.030.002 11826 079.024.059.147 31351 192.168.001.100 9251 105
IOS UDP 192.168.030.002 11826 193.198.056.247 45682 192.168.001.100 9115 16
IOS TCP 192.168.030.002 2254 064.012.028.207 443 192.168.001.100 9116 352
IOS UDP 192.168.030.002 11826 095.076.135.237 18586 192.168.001.100 9258 147
IOS UDP 192.168.030.002 11826 151.048.102.187 45873 192.168.001.100 9093 18
IOS TCP 192.168.030.002 2287 205.188.001.209 443 192.168.001.100 9123 144
IOS TCP 192.168.030.002 2296 064.012.030.056 443 192.168.001.100 9124 223
IOS UDP 192.168.030.001 5060 083.211.227.015 5060 192.168.001.100 9100 110
IOS UDP 192.168.030.002 11826 217.164.063.250 36112 192.168.001.100 9127 149
IOS TCP 192.168.030.002 2200 064.004.061.123 1863 192.168.001.100 9104 350
IOS UDP 192.168.030.002 11826 093.146.163.169 31586 192.168.001.100 9130 103
IOS TCP 192.168.030.002 2366 080.230.085.012 30615 192.168.001.100 9217 355

Meaning of parameters:

S (SIDE) it's composed by two letters. The first shows the input side and the second the translation side ( I :
INSIDE, O: OUTSIDE, V: VPN, D: DMZ).

A it shows if the translation must be applied to the suorce address or to the destination one(S: SOURCE D:
DESTINATION).

TYPE it shows the packets protocol. The translation is applied only if TYPE matches with the protocol of the
packets to analyse. (ICMP, UDP, DNS, SNTP, SNMP, TCP, FTPc, FTPd, FRAG, PPTc, PPTd).

SRC-ADDRESS it shows the applied filter on the source address. If the received packet source address doesn't match with
SRC-ADDRESS, the translation is not applied.

SP/ID If TYPE is FRAG, PPT or ICMP, it shows the packet ID used to verify if the translation matches. If TYPE
is TCP or UDP, it shows the packet source port.

DST-ADDRESS it shows the applied filter on the destination address. If the received packet destination address doesn't
match with DST-ADDRESS, the translation is not applied.

DP/ID If TYPE is FRAG, PPT or ICMP, it shows the packet ID used to verify if the translation matches. If TYPE
is TCP or UDP, it shows the packet destination port.

ALS-ADDRESS if TYPE, SRC-ADDRESS, SP/ID, DST-ADDRESS, DP/ID, ALS-ADDRESS match, it shows the new ip
address which will be assigned to the one in the packet. If A:S, the source address is replaced with ALS-
ADDRESS. if A:D, the destination address is replaced with ALS-ADDRESS.

ALIAS if TYPE, SRC-ADDRESS, SP/ID, DST-ADDRESS, DP/ID, ALS-ADDRESS match, it shows the new
DP/ID which will be assigned to the one in the packet. If A:S, the current SP/ID is replaced with ALIAS.
if A:D, the DP/ID is replaced with ALIAS.

324
Draft NAT - Network Address Translation Draft

TM it's the translation lifetime. When TM reaches 0, the translation is deleted. Each time the translation is
matched, the TM is initialized to a specific value depending of NAT resource configuration.

20.4. Examples of NAT configuration

In this section will be shown any examples of NAT configuration.

20.4.1. Suggest an access from inside workstations to outside

networks
Suppose to have the following situation.

Figure 20.1. Network scheme for NAT Example n.1

Type the following command to allow the “inside” network 192.168.1.0/24 to reach the “outside” network 10.0.0.0/24 by
using the CPX IP address (10.0.0.1) as “alias” and allowing the Port Address Translation.

[08:57:37] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------

[08:57:46] ABILIS_CPX:_a nat pr:1 inat:in onat:out add:src snet:192.168.1.0/24 anet:10.0.0.1/32 pat

COMMAND EXECUTED

325
Draft NAT - Network Address Translation Draft

[08:58:38] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
1 IN SRC 192.168.001.000/24 * 010.000.000.001/32
OUT * * AUTO YES
-------------------------------------------------------------------------------

[08:58:44] ABILIS_CPX:_init nat

COMMAND EXECUTED

After applying this rule, a host “inside” network 192.168.1.0/24 can reach the “outside” network 10.0.0.0/24:

ubuntu@ubuntu:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 20:cf:30:42:36:9c
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::22cf:30ff:fe42:369c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5511 errors:0 dropped:0 overruns:0 frame:0
TX packets:3044 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5509729 (5.5 MB) TX bytes:255424 (255.4 KB)
Interrupt:47

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:83 errors:0 dropped:0 overruns:0 frame:0
TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8610 (8.6 KB) TX bytes:8610 (8.6 KB)

wlan0 Link encap:Ethernet HWaddr 74:f0:6d:7d:08:25

UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ubuntu@ubuntu:~$ ping 10.0.0.2

PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_req=1 ttl=127 time=1.19 ms
64 bytes from 10.0.0.2: icmp_req=2 ttl=127 time=1.06 ms
64 bytes from 10.0.0.2: icmp_req=3 ttl=127 time=1.10 ms
64 bytes from 10.0.0.2: icmp_req=4 ttl=127 time=1.12 ms
^C
--- 10.0.0.2 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 1.067/1.123/1.199/0.053 ms

Example of IP packet translation:

326
Draft NAT - Network Address Translation Draft

Table 20.1. Example of IP packet translation

Source IP address Destination IP address

Before translation: 192.169.1.2:XXX 10.0.0.3:ZZZ
After translation: 10.0.0.1:YYY 10.0.0.3:ZZZ

20.4.2. Suggest an access from outside networks to internal servers

Goal description. We have just one public IP address. Inside LAN there are three servers with several IP addresses running
the same service with different contents, e.g. a commercial web, a technical web, a restricted access web. Abilis must be
configured so that each server can be reached using the public IP address.

327
Draft NAT - Network Address Translation Draft

Figure 20.2. Network scheme for NAT Example n.2

328
Draft NAT - Network Address Translation Draft

Three of our servers are described in outside network (for example Internet) as :

• 192.168.1.100:81 - main HTTP server of our company

• 192.168.1.100:82 - HTTP server for technical support

• 192.168.1.100:83 - HTTP server for developers

The following records have been added to NAT static table:

[12:08:06] ABILIS_CPX:_a nat pr:1 inat:out onat:in add:dst dnet:192.168.1.100/32 anet:192.168.30.11

COMMAND EXECUTED

[12:08:16] ABILIS_CPX:_a nat pr:2 inat:out onat:in add:dst dnet:192.168.1.100/32 anet:192.168.30.12

COMMAND EXECUTED

[12:08:20] ABILIS_CPX:_a nat pr:3 inat:out onat:in add:dst dnet:192.168.1.100/32 anet:192.168.30.13

COMMAND EXECUTED

[12:11:16] ABILIS_CPX:_d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
0 IN SRC Ip-1 * OUT-IP
OUT * * AUTO YES
-------------------------------------------------------------------------------
1 OUT DST * 192.168.001.100/32 192.168.030.011/32
IN * 81 http(80) YES
* * TCP SYS
-------------------------------------------------------------------------------
2 OUT DST * 192.168.001.100/32 192.168.030.012/32
IN * 82 http(80) YES
* * TCP SYS
-------------------------------------------------------------------------------
3 OUT DST * 192.168.001.100/32 192.168.030.013/32
IN * 83 http(80) YES
* * TCP SYS
-------------------------------------------------------------------------------

[12:11:19] ABILIS_CPX:_init nat

COMMAND EXECUTED

329
Draft NAT - Network Address Translation Draft

Figure 20.3. Web Server 192.168.30.11

330
Draft NAT - Network Address Translation Draft

Figure 20.4. Web Server 192.168.30.12

331
Draft NAT - Network Address Translation Draft

Figure 20.5. Web Server 192.168.30.13

332
Draft NAT - Network Address Translation Draft

Table 20.2. Example of IP packet translation

Source IP address Destination IP address

Destination translation
Before translation: XXX.XXX.XXX.XXX:YYY 192.168.1.100:81
After translation: XXX.XXX.XXX.XXX:YYY 192.168.30.11:80
Destination translation
Before translation: XXX.XXX.XXX.XXX:YYY 192.168.1.100:82
After translation: XXX.XXX.XXX.XXX:YYY 192.168.30.12:80
Destination translation
Before translation: XXX.XXX.XXX.XXX:YYY 192.168.1.100:83
After translation: XXX.XXX.XXX.XXX:YYY 192.168.30.13:80

20.4.3. Configuring a DMZ

Connect the ETH100 cards following the scheme below

NAT resource must be configurated so that:

• servers located in the DMZ can be reachable from the external interface

• computers inside the LAN can reach internet and servers

• servers located in the DMZ cannot reach computers inside LAN

333
Draft NAT - Network Address Translation Draft

Figure 20.6. Network scheme

Assuming to have the ip address already assigned to network interfaces, IP resources must be configured in the following
way:

[19:00:30] ABILIS_CPX:s p ip-1 nat:outside

COMMAND EXECUTED

[19:00:42] ABILIS_CPX:s p ip-20 nat:inside

COMMAND EXECUTED

[19:00:52] ABILIS_CPX:s p ip-21 nat:dmz

COMMAND EXECUTED

[19:01:00] ABILIS_CPX:d p ip-1

RES:Ip-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:Lan_locale
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-1
IPADD:192.168.000.201 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO

334
Draft NAT - Network Address Translation Draft

OUTBUF:50 OUTQUEUE:FAIR MTU:1500 BRD:NET

OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:TOTALS
TRFA-IPADD:LOCALNET (192.168.000.000:192.168.000.255)
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-1 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:25 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[19:01:12] ABILIS_CPX:d p ip-20

RES:Ip-20 - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:192.168.030.001 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[19:01:16] ABILIS_CPX:d p ip-21

RES:Ip-21 - IP over LAN (LAN) -------------------------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-3
IPADD:192.168.031.001 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:DMZ DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-3 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

335
Draft NAT - Network Address Translation Draft

[19:01:21] ABILIS_CPX:init res:ip-1

COMMAND EXECUTED

[19:01:33] ABILIS_CPX:init res:ip-20

COMMAND EXECUTED

[19:01:36] ABILIS_CPX:init res:ip-21

COMMAND EXECUTED

[19:01:38] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

Add the following rules to NAT Aliases table:

[08:33:30] ABILIS_CPX:a nat pr:1 inat:in onat:dmz add:src snet:192.168.30.0/24 dnet:192.168.31.0/24

COMMAND EXECUTED

[08:34:23] ABILIS_CPX:a nat pr:2 inat:out onat:dmz add:dst snet:* dnet:192.168.0.201/32 danet:192.

COMMAND EXECUTED

[08:35:13] ABILIS_CPX:a nat pr:3 inat:in onat:out add:src snet:192.168.30.0/24 anet:192.168.0.201/3

COMMAND EXECUTED

[08:36:33] ABILIS_CPX:d nat

UPNP maps not present

Configured maps
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------
-------------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO: PAT:
SIP: DIP: PROT: TOUT:
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
1 IN SRC 192.168.030.000/24 192.168.031.000/24 192.168.031.001/32
DMZ * * AUTO YES
-------------------------------------------------------------------------------
2 IN SRC 192.168.030.000/24 * 192.168.000.201/32
OUT * * AUTO YES
-------------------------------------------------------------------------------
3 OUT DST * 192.168.000.201/32 192.168.031.100/32
DMZ * * AUTO YES
-------------------------------------------------------------------------------

[08:36:40] ABILIS_CPX:init nat

COMMAND EXECUTED

[08:36:51] ABILIS_CPX:save conf

336
Draft NAT - Network Address Translation Draft

COMMAND EXECUTED

The rule PR:1 is useful to allow LAN to reach servers located in the DMZ, the rule PR:2 allows to reach a server with ip
address 192.168.31.100 located in the DMZ from Internet, while PR:3 allows LAN to reach Internet.

337
Draft Draft

Chapter 21. IPSH - IP Shaping

Luca Castagna

Table of Contents
21.1. IPSH resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.1.1. IPSH resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
21.2. IP Flow table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.1. D IPSH FLOW (Display IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
21.2.2. A IPSH FLOW (Add IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.3. C IPSH FLOW (Clear IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
21.2.4. S IPSH FLOW (Set IP Shaping Flow) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3. IP Rule table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
21.3.1. D IPSH RULE (Display IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
21.3.2. A IPSH RULE (Add IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.3. C IPSH RULE (Clear IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
21.3.4. S IPSH RULE (Set IP Shaping Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4. IP User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.4.1. D IPSH USER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
21.5. IPSH diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.1. IPSH diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
21.5.2. IPSH statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

21.1. IPSH resource

The IPSH (IP Shaping) resource is used within the Abilis CPX to control network traffic in order to increase/decrease usable
bandwidth for some kind of packets that meet certain criteria.

These criteria are configured using a specific flow table. Once the criteria is matched, a specific traffic shaping rule will
define the behaviour to use for those packets.

21.1.1. IPSH resource parameters

Use the following command to display the parameters of the resource. By typing d p ipsh ? command it is possible to display
the meaning of all the parameters.

[17:50:56] ABILIS_CPX:d p ipsh

RES:IpSh ----------------------------------------------------------------------
Run DESCR:IP_Shaping_service
LOG:NO ACT:YES buf:2000 maxuser:500
MAXUSER-EXCEED:BYPASS

Note
The “Not Saved (SAVE CONF)” message is displayed every time the port is modified but not saved with
the save conf command.

Note
The “Not Refreshed (INIT)” message is displayed every time the port is modified but not refreshed with the
initialization command init res:ipsh or init ipsh.

Meaning of the parameters:

338
Draft IPSH - IP Shaping Draft

DESCR Resource description. From 0 up to 79 Alphanumeric extended characters. Case is preserved.

Spaces are allowed. Strings holding spaces must be written between quotation marks (E.g.:
"str1 str2").

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S:
System Log; A: Alarm view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of
state changes, see ref. manual).

ACT Resource activation [NO, YES].

buf Maximum number of packets which can be hold in shaping queues [500..10000].

maxuser IMaximum number of simultaneous processable users [100..1000].

MAXUSER-EXCEED Behaviour to adopt when maxuser limit is exceeded [DROP, BYPASS, LIMIT].

MAXUSER-EXCEED- Throughput limitation for packets that exceeds maxuser limit [64..100000 kbit/sec]
LIMIT
Note
Only for MAXUSER-EXCEED:LIMIT.

The following command allows the administrator to change the configuration of the resource:

s p ipsh parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ipsh; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

21.2. IP Flow table

Changes on IP Flow table are active only after an init res:ipsh command.

The command save conf saves all flows inside the table. In the configuration files up to 255 flows are saved.

The available commands for managing the IP flow table are the following:

• d ipsh flow

• a ipsh flow

• c ipsh flow

• s ipsh flow

21.2.1. D IPSH FLOW (Display IP Shaping Flow)

It shows the IP shaping flow table. By typing d ipsh flow ? command it is possible to display the meaning of all parameters.

[14:36:28] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 64 350 PRE-NAT 192.168.000.000/24
1 OUT 1 256 5000 POST-NAT 192.168.000.000/24

Note
The “Not Saved (SAVE CONF)” message is displayed every time the table is modified but not saved with
the save conf command.

339
Draft IPSH - IP Shaping Draft

Note
The “Not Refreshed (INIT)” message is displayed every time the table is modified but not refreshed with the
initialization command init res:ipsh or init ipsh.

Meaning of the parameters:

PR Priority of IPSH flow [0..254].

DESRC Entry description. From 0 up to 70 Alphanumeric extended characters. Case is preserved. Spaces are allowed.
Strings holding spaces must be written between quotation marks (E.g. "str1 str2").

DIR Flow direction [IN, OUT] When 'IN', the shaping in made by checking the source IP of packets received by Abilis
CPX. When 'OUT', the shaping in made by checking the destination IP of packets transmitted by Abilis CPX.

RULE Rule assigned to current flow [#, LOWBW, HIGHBW, 1..32] When '#', rule is not assigned. When 'LOWBW',
bandwidth is limited to LOWBW: value. When 'HIGHBW', bandwidth is limited to HIGHBW: value. When
1..32, identifier of a dynamic rule in the IPSH RULE table.

LOWBW Lower bandwidth limit [64..100000 kbit/sec]. The actual bandwidth limit will be modulated between LOWBW:
and HIGHBW: according to the RULE: algorithm.

HIGHBW Higher bandwidth limit [64..100000 kbit/sec] The actual bandwidth limit will be modulated between LOWBW:
and HIGHBW: according to the RULE: algorithm.

CHECK Where to check IP address [PRE-NAT, POST-NAT, PRE-IPSEC, POST-IPSEC].

• When 'PRE-NAT', the analisys is performed before NAT.

• When 'POST-NAT', the analisys is performed after NAT.

• When 'PRE-IPSEC', the analisys is performed before IPSEC.

• When 'POST-IPSEC', the analisys is performed after IPSEC.

IP IP address filter. For DIR:IN the filter is applied on SOURCE IP. For DIR:OUT the filter is applied on
DESTINATION IP. Single Ip address [0.0.0.1-255.255.255.255] or subnet [x.x.x.x/y] or Ip addresses range
separated by ':' (colon) or the name of an IP/IR/RU/MR list between primes or "#" or "*".

21.2.2. A IPSH FLOW (Add IP Shaping Flow)

It adds a new IP flow definition with the specified parameters. Unspecified ones are set to their default values.

To display the syntax of the command, type a ipsh flow ?.

Some examples follow:

[14:00:15] ABILIS_CPX:a ipsh flow pr:0 rule:1 lowbw:512 highbw:8192 ip:192.168.0.5

COMMAND EXECUTED

[14:00:15] ABILIS_CPX:a ipsh flow pr:1 dir:out rule:1 lowbw:256 highbw:4096 check:post-nat ip:192.1

COMMAND EXECUTED

[14:01:01] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 512 8192 PRE-NAT 192.168.000.005
2 OUT 1 256 4096 POST-NAT 192.168.000.000/24

21.2.3. C IPSH FLOW (Clear IP Shaping Flow)

It deletes from the table the IP flow identified by the specified “PR:xx”.

340
Draft IPSH - IP Shaping Draft

To display the syntax of the command, type c ipsh flow ?.

Some examples follow:

[13:55:27] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 512 8192 PRE-NAT 192.168.000.005
1 IN 1 256 4096 PRE-NAT 192.168.000.000/24
2 OUT 1 256 4096 POST-NAT 192.168.000.000/24

[13:55:27] ABILIS_CPX:c ipsh flow pr:1

COMMAND EXECUTED

[13:55:27] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 512 8192 PRE-NAT 192.168.000.005
1 OUT 1 256 4096 POST-NAT 192.168.000.000/24

21.2.4. S IPSH FLOW (Set IP Shaping Flow)

It sets one or more parameters to their new values into IP flow table, identified by the specified “PR:xx”.. This command can
be only used to modify specific IP flow definitions in the table.

Type s ipsh flow ? to display the syntax of the command.

Some examples follow:

[13:56:01] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 512 8192 PRE-NAT 192.168.000.005
1 IN 1 256 4096 PRE-NAT 192.168.000.000/24

[13:56:25] ABILIS_CPX:s ipsh flow pr:1 dir:out check:post-nat

COMMAND EXECUTED

[13:57:38] ABILIS_CPX:d ipsh flow

---+---------------------------------------------------------------------------
PR:|[DESCR:]
|DIR:|RULE:| LOWBW:|HIGHBW:|CHECK: |IP:
---+----+-----+-------+-------+----------+-------------------------------------
0 IN 1 512 8192 PRE-NAT 192.168.000.005
1 OUT 1 256 4096 POST-NAT 192.168.000.000/24

21.3. IP Rule table

Changes on IP Rule table are active only after an init res:ipsh command.

The command save conf saves all rules inside the table. In the configuration files up to 32 rules are saved.

341
Draft IPSH - IP Shaping Draft

The available commands for managing the IP rule table are the following:

• d ipsh rule

• a ipsh rule

• c ipsh rule

• s ipsh rule

21.3.1. D IPSH RULE (Display IP Shaping Rule)

It shows the IP shaping rule table. By typing d ipsh rule ? command it is possible to display the meaning of all parameters.

[14:36:28] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

Note
The “Not Saved (SAVE CONF)” message is displayed every time the table is modified but not saved with
the save conf command.

Note
The “Not Refreshed (INIT)” message is displayed every time the table is modified but not refreshed with the
initialization command init res:ipsh or init ipsh.

Meaning of the parameters:

ID IP Shaping rule identifier [1..32].

DESCR Entry description. From 0 up to 70 Alphanumeric extended characters. Case is preserved. Spaces are allowed.
Strings holding spaces must be written between quotation marks (E.g. "str1 str2"). It is displayed only when
not empty.

TI1 Time interval indicating rule enable. The format used to specify the interval is: "day,hh:mm-hh:mm", where
'day' can be: a single day [MO, TU, WE, TH, FR, SA, SU] or a set of days (E.g.: MO+TH or TU+TH+SU
etc.) or an interval.(E.g.: MO-WE or TH-SU etc. or ALL).

TI2 Time interval indicating rule enable. The format used to specify the interval is: "day,hh:mm-hh:mm", where
'day' can be: a single day [MO, TU, WE, TH, FR, SA, SU] or a set of days (E.g.: MO+TH or TU+TH+SU
etc.) or an interval.(E.g.: MO-WE or TH-SU etc. or ALL).

TYPE Rule type [#, VARIANCE, VARIANCE-WH]

• When '#', rule type is not defined.

• When 'VARIANCE', rule must follow variance algorithm.

• When 'VARIANCE-WH', rule must follow variance algorithm. Bandwidth range is affected by working
hours (WH-TI).

PERIOD Time interval used for algorithm rule calculation [30..1800 sec].

THRESHOLD Variance threshold: above or equal threshold the traffic is interactive, below it is stream. [0..20].

STEP- Reduction percentage for each reduction step, calculated respect to current bandwidth limit. [0..90].
DOWN

STEP-UP Increasing percentage for each increase step, calculated respect to current bandwidth limit. [110..500].

WH-TI1 Time interval during which the WH-LOWBW: and WH-HIGHBW: reductions take place. The format used
to specify the interval is: "day,hh:mm-hh:mm", where 'day' can be: a single day [MO, TU, WE, TH, FR,

342
Draft IPSH - IP Shaping Draft

SA, SU] or a set of days (E.g.: MO+TH or TU+TH+SU etc.) or an interval.(E.g.: MO-WE or TH-SU etc. or
ALL).

Note
Only for TYPE:VARIANCE-HW.

WH-TI2 Time interval during which the WH-LOWBW: and WH-HIGHBW: reductions take place. The format used
to specify the interval is: "day,hh:mm-hh:mm", where 'day' can be: a single day [MO, TU, WE, TH, FR,
SA, SU] or a set of days (E.g.: MO+TH or TU+TH+SU etc.) or an interval.(E.g.: MO-WE or TH-SU etc. or
ALL).

Note
Only for TYPE:VARIANCE-HW.

WH- Reduction percentage during working hours applied to LOWBW: value specified in the IPSH FLOW that
LOWBW references this rule. [10..90].

Note
Only for TYPE:VARIANCE-HW.

WH- Reduction percentage during working hours applied to HIGHBW: value specified in the IPSH FLOW that
HIGHBW references this rule. [10..90].

Note
Only for TYPE:VARIANCE-HW.

21.3.2. A IPSH RULE (Add IP Shaping Rule)

It adds a new IP rule definition with the specified parameters. Unspecified ones are set to their default values.

To display the syntax of the command, type a ipsh rule ?.

Some examples follow:

[14:00:15] ABILIS_CPX:a ipsh rule id:1 type:variance step-up:200

COMMAND EXECUTED

[14:01:01] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

21.3.3. C IPSH RULE (Clear IP Shaping Rule)

It deletes from the table the IP rule identified by the specified “ID:xx”.

To display the syntax of the command, type c ipsh rule ?.

Some examples follow:

[13:55:27] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

343
Draft IPSH - IP Shaping Draft

ID:2 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE-WH PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:150
WH-TI1:ALL,00:00-23:59
WH-TI2:#
WH-LOWBW:50 WH-HIGHBW:50

[13:55:27] ABILIS_CPX:c ipsh rule id:2

COMMAND EXECUTED

[13:55:27] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

21.3.4. S IPSH RULE (Set IP Shaping Rule)

It sets one or more parameters to their new values into IP rule table, identified by the specified “ID:xx”.. This command can
be only used to modify specific IP rule definitions in the table.

Type s ipsh rule ? to display the syntax of the command.

Some examples follow:

[13:56:01] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:ALL,00:00-23:59 TI2:#
TYPE:VARIANCE PERIOD:300 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

[13:56:25] ABILIS_CPX:s ipsh rule id:1 period:60 ti1:mo-fr,08:30-12:30 ti2:mo-fr,14:00-18:00

COMMAND EXECUTED

[13:57:38] ABILIS_CPX:d ipsh rule

ID:1 DESCR:
TI1:MO-FR,08:30-12:30 TI2:MO-FR,14:00-18:00
TYPE:VARIANCE PERIOD:60 THRESHOLD:10
STEP-DOWN:50 STEP-UP:200

21.4. IP User table

User table contain all the information about users that have been matched into IP SHAPING flow table and their incoming/
outgoing bandwith has a specific maximum limit.

21.4.1. D IPSH USER

Use the command d ipsh user to display the ip load balancing table.

[12:24:12] ABILIS_CPX:d ipsh user

USER-IP CB-OUT CB-IN THR-OUT THR-IN %OUT %IN V-OUT V-IN

--------------- ------- ------- ------- ------- ---- ---- ----- -----
192.168.000.002 NA 4096 NA 0 NA 0 NA NA
192.168.000.003 NA 4096 NA 0 NA 0 NA NA
192.168.000.005 4096 8192 0 0 0 0 NA NA
192.168.000.015 NA 4096 NA 0 NA 0 NA NA

344
Draft IPSH - IP Shaping Draft

192.168.000.029 NA 4096 NA 0 NA 0 NA NA
192.168.000.034 NA 4096 NA 0 NA 0 NA NA
192.168.000.035 NA 4096 NA 0 NA 0 NA NA
192.168.000.066 NA 4096 NA 0 NA 0 NA NA
192.168.000.082 NA 4096 NA 0 NA 0 NA NA
192.168.000.113 NA 4096 NA 0 NA 0 NA NA
192.168.000.114 NA 4096 NA 0 NA 0 NA NA
192.168.000.126 NA 4096 NA 0 NA 0 NA NA
192.168.000.131 NA 4096 NA 0 NA 0 NA NA
192.168.000.134 NA 4096 NA 0 NA 0 NA NA
192.168.000.139 NA 4096 NA 0 NA 0 NA NA
192.168.000.150 NA 4096 NA 0 NA 0 NA NA
192.168.000.152 NA 4096 NA 0 NA 0 NA NA
192.168.000.160 NA 4096 NA 0 NA 0 NA NA
192.168.000.168 NA 4096 NA 0 NA 0 NA NA
192.168.000.169 NA 4096 NA 0 NA 0 NA NA
192.168.000.171 NA 4096 NA 0 NA 0 NA NA
192.168.000.248 NA 4096 NA 0 NA 0 NA NA
192.168.000.249 NA 4096 NA 0 NA 0 NA NA

Meaning of the most important parameters:

• USER-IP: IP address of the user with traffic shaped.

• CB-OUT: Current max bandwidth in output.

• CB-IN: Current max bandwidth in input.

• THR-OUT: Instant throughput out (last 5 seconds interval).

• THR-IN: Instant throughput in (last 5 seconds interval).

• %OUT: Average usage of the available output-bandwidth (altoghether).

• %IN: Average usage of the available input-bandwidth (altoghether).

• V-OUT: Current accumulated variance of the output data-flow.

• V-IN: Current accumulated variance of the input data-flow.

21.5. IPSH diagnostics and statistics

21.5.1. IPSH diagnostics
To display the diagnostics of the IPSH resource the following commands are used:

d d ipsh / d de ipsh Shows diagnostic information, such as the state of the resource, the current and
maximum number of buffers reached from start-up into the IPRTR's incoming/
outgoing FIFOs and the maximum number of users present into the user table (this
information indicate the maxuser parameter).

[18:06:40] ABILIS_CPX:d d ipsh

RES:IpSh ----------------------------------------------------------------------
IP_Shaping_service
STATE:READY
MAX-BUF:2000 CUR-BUF:23 PEAK-BUF:952
MAX-S-BUF:10000 CUR-S-BUF:0 PEAK-S-BUF:339
MAX-USER:500 CUR-USER:19 PEAK-USER:39

21.5.2. IPSH statistics

To display the statistics of the IPSH resource the following commands are used:

d s ipsh / d se ipsh Show statistic information, such the number of IP datagrams analyzed sent/received,
number of IP datagrams shaped due to ip shaping flow matching and those ignored

345
Draft IPSH - IP Shaping Draft

because don't match. There are also dropped packets due to MAXUSER-EXCEED set
with DROP or out-of-buffer due to buf parameter.

[18:06:40] ABILIS_CPX:d s ipsh

RES:IpSh ----------------------------------------------------------------------
IP_Shaping_service
--- Cleared 4 days 18:57:29 ago, on 16/09/2011 at 17:42:18 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
ANALYZED | 92348416| 92328825|SHAPED | 17811290| 26150576|
IGNORED | 74537126| 66178249|DROPPED | 0| 0|
OUTBUF | 0| 0|MAXUSERS-EX| 0| 0|
------------------------------------------------------------------------

346
Draft Draft

Chapter 22. IPACL - IP Access

Control List
Marco Bellesia

Table of Contents
22.1. IP Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
22.1.1. TOS (Type Of Service) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.1.2. Activating IPACL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
22.2. IPACL management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
22.2.1. D IPACL (Display IP Access Control List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
22.2.2. A IPACL (Add IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
22.2.3. C IPACL (Clear IP Acces Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
22.2.4. S IPACL (Set IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
22.2.5. M IPACL (Move IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
22.2.6. F IPACL (Find IP Access Control List filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
22.3. Examples of IPACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.1. IP packets blocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
22.3.2. Giving High Priority to VoIP packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

22.1. IP Access Control List

Using IP Access Control List, Abilis CPX filters transit datagrams basing on the information carried by the header (source
address and destination, internet protocol version and numbers of logical port) and not on their content.

Two ways of filtering are allowed:

• STD (Standard): in this case the such called “address filtering” procedure is executed; only IP source and destination
addresses of the packet are checked.

• EXT (Extended): in this case the “service filtering” procedure is executed; IP source, IP destination addresses of the
packet, the internet protocol version and, for TCP, UDP protocols, the logical port numbers (indeed also the requested
service).

IPACL provides two different kinds of filters:

• PERMIT: permitted to transit.

• DENY: denied to transit.

Filters also allow assigning each datagram data flow a different service class:

• HIGH: service class “HIGH”.

• NORMAL: service class “NORMAL”.

• LOW: service class “LOW”.

Usually the service classes are also called “priorities” so that it is possible to speak of “the traffic prioritisation”.

Tip
This feature is very important when VoIp and Data applications use the same link. In these cases, voice
packets must have the highest priority.

Moreover it is possible to activate the cryptographic functionalities of data content in datagrams:

347
Draft IPACL - IP Access Control List Draft

• CRKEY: cryptography key to be used.

• CRDIR: cryptography direction (encode decode).

Changes on IPACL are immediately active so no Abilis CPX restart is required.

Caution
“Packet filtering” definitions must be added carefully cause the access to the Abilis by IP may be
blocked!

22.1.1. TOS (Type Of Service)

TOS is just a hint to the routing algorithm that helps it choose among various paths to a destination. Each datagram data flow
can be associated with a different Type Of Service (TOS).

The Type of Service is used to indicate the quality of the service desired.

It's abstract set of parameters characterizing the service choices provided in the networks which make up the internet.

Type of service indication is used by gateways to:

• select the actual transmission parameters for a particular network;

• choose the network to use for the next hop;
• choose the next gateway;

when routing an internet datagram.

The five values allowed are:

• N = None;
• D = Minimize Delay;
• T = Maximize Throughput;
• R = Maximize Reliability;
• C = Minimize Monetary Cost.

22.1.2. Activating IPACL

The IP Access Control List must be enabled into the IPRTR Resource.

[15:14:30] ABILIS_CPX:d p iprtr

RES:Iprtr ---------------------------------------------------------------------
DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.001.001)
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:4 virtual:0
- IP Access List -------------------------------------------------------
ACL:NO ACLBYPASS:#
COS:DISABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:062.094.000.001 PPP-DNS-SEC:062.094.000.002

The highlight parameters manages the IPACL activation and functionality mode.

ACL It activates the IP Access List service and chooses the operating mode [NO, STD, EXT].

ACLBYPASS It sets the IP address of the IP datagram received that will be managed without considering filters eventually
defined in the IP Access List [*: stands for “any IP address”, that is the IP access list service will be applied
to any IP datagrams; #: stands for “no IP address”, that is the IP access list service will NOT be applied to
any IP datagrams; 1-126.x.x.x, 128-223.x.x.x].

348
Draft IPACL - IP Access Control List Draft

COS It activates/deactivates the IP classes of service. Class of service is a feature used to assign different
priorities to specific paths of IP datagrams. The assignment of this priority is done by IPRTR upon
reception of every IP datagram, using the information present in the IPACL.

COSDFT It sets the Class of IP service default value [LOW, NORMAL, HIGH].

COSBALANCE It activates/deactivates the balance functionality of the IP classes of service. This procedure provides an
acceptable service to each class by avoiding that higher priority classes are too prevalent respect the lower
ones. The user, through the parameters NORMRATE and LOWRATE, can set the percentage balance ratio.

NORMRATE It sets the percentage balance ratio between resources allocated for the classes with “NORMAL” priority
and the ones with “HIGH” priority.

LOWRATE It sets the percentage balance ratio between resources allocated for the classes with “LOW” priority and the
ones with “NORMAL” priority.

For example, the command for enable the IPACL in Extended mode and the COS Management is:

[15:28:50] ABILIS_CPX:s p iprtr acl:ext cos:enabled

COMMAND EXECUTED

[15:36:47] ABILIS_CPX:d p iprtr

RES:Iprtr - Not Saved (SAVE CONF) ---------------------------------------------

------------------------------------------------------------------------
DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.001.001)
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:4 virtual:0
- IP Access List -------------------------------------------------------
ACL:EXT ACLBYPASS:#
COS:ENABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:062.094.000.001 PPP-DNS-SEC:062.094.000.002

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:iprtr; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

22.2. IPACL management

The IP Access Control List can store up to 256 filters definitions.

In this section will be described the commands for the IP Access Control List management.

These are the commands:

• d ipacl

• a ipacl

• c ipacl

• s ipacl

• m ipacl

• f ipacl

349
Draft IPACL - IP Access Control List Draft

Every filter is identified by a priority index which is used to add, modify and delete IPACL entries.

Priority indexes, every time a filter is added or deleted, are automatically kept in sequential order.

Changes to IPACL are immediately active, so there's no need to restart Abilis CPX.

22.2.1. D IPACL (Display IP Access Control List)

It shows the current content of the IP access list. By omitting the priority, the command will show all the filters currently in
the table.

Type d ipacl ?, to display the syntax of the command.

[15:45:59] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:0

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
*** NO IP ACCESS LISTS DEFINED ***

Meaning of the parameters:

PR The priority index sets the filter verifying order. The verifying procedure is executed on each datagram. It
starts from the filter with priority 0 and continues until the suitable datagram is found or the list ends. If the IP
datagram doesn't match any filter, it will be routed; if the IP services class functionality is activated, the Router
will assign to the datagram the default priority set in the parameter COSDFT of the port IPRTR.

TYPE This command sets whether the datagram, matching the filter, have to be routed (filter matched type PERMIT)
or discarded (filter matched type DENY).

IPCOS This parameter is displayed and configurable only for PERMIT filters type. It is considered only if the IP classes
service are activated (COS:ENABLED) [DFT (default); HIGH; NORMAL; LOW].

SA It sets the IP address which the datagrams source address has to match (or be contained in). It may be expressed
as:
• a single value, using the Dotted Decimal Notation (E.g.: 150.200.192.192).
• an interval, by separating the two IP addresses with : (colon) character (E.g.: 192.168.0.0:192.168.0.100).
• the name of an Elements List of type IP or IR or RU or MR, written between primes (E.g.: 'My_List').
• the * (asterisk) string, that stands for “any IP address”.

DA It sets the IP address (IP interval of addresses) which the datagrams destination address has to match (or be
contained in). It may be expressed as:
• a single value, using the Dotted Decimal Notation (E.g.: 150.200.192.192).
• an interval, by separating the two IP addresses with : (colon) character (E.g.: 192.168.0.0:192.168.0.100).
• the name of an Elements List of type IP or IR or RU or MR, written between primes (E.g.: 'My_List').
• the * (asterisk) string, that stands for “any IP address”.

PROT It sets the Internet protocol where the filter can be applied on. It may be expressed as:
• mnemonic or numeric identifier [1 - 254] of an Internet Protocol (E.g.: tcp or 6).
• the name of an Elements List of type IPT or RU or MR, written between primes (E.g.: 'My_List').
• the tcpudp string, that stands for “tcp and/or udp protocols”.
• the * (asterisk) string, that stands for “any Internet protocol”.

SPO This parameter is used only for TCP and UDP protocols type. It sets the source port (interval of ports) that the
datagrams source port has to match (or be contained in). It may be expressed as:
• mnemonic or numeric identifier [1 - 65535] of a TCP/UDP port (E.g.: telnet or 23).
• an interval, by separating the two TCP/UDP ports value with : (colon) character (E.g. 23:161 or telnet:snmp).
• the name of an Elements List of type TUP or RU or MR, written between primes (E.g.: 'My_List').

350
Draft IPACL - IP Access Control List Draft

• the * (asterisk) string, that stands for “any TCP/UDP port”.

DPO This parameter is used only for TCP and UDP protocols type. It sets the destination port (interval of ports) that
the datagrams destination port has to match (or be contained in). It may be expressed as:
• mnemonic or numeric identifier [1 - 65535] of a TCP/UDP port (E.g.: telnet or 23).
• an interval, by separating the two TCP/UDP ports value with : (colon) character (E.g. 23:161 or telnet:snmp).
• the name of an Elements List of type TUP or RU or MR, written between primes (E.g.: 'My_List').
• the * (asterisk) string, that stands for “any TCP/UDP port”.

PO This parameter is used only for TCP and UDP protocols type, in alternative to the parameters SPO and DPO. It
sets the port value (or an interval of values) which the datagram source or destination port has to match (or be
contained in).
• mnemonic or numeric identifier [1 - 65535] of a TCP/UDP port (E.g.: telnet or 23).
• an interval, by separating the two TCP/UDP ports value with : (colon) character (E.g. 23:161 or telnet:snmp).
• the name of an Elements List of type TUP or RU or MR, written between primes (E.g.: 'My_List').
• the * (asterisk) string, that stands for “any TCP/UDP port”.

TOS-IN Input Type of Service octet or Differentiated Services Field. It may be expressed as:
• * or *-* means “don't change”.
• p-t, PRECEDENCE and TOS values, where p can be [0..7, *] and t can be [combination of N: None; D:
Minimize Delay; T: Maximize Throughput; R: Maximize Reliability; C: Minimize Monetary Cost; *].
• bbbbbb, DS value bit by bit, where b can be [0, 1, x] and x means “don't care”.

TOS-OUT Output Type of Service octet or Differentiated Services Field. It may be expressed as:
• * or *-* means “don't change”.
• p-t, PRECEDENCE and TOS values, where p can be [0..7, *] and t can be [combination of N: None; D:
Minimize Delay; T: Maximize Throughput; R: Maximize Reliability; C: Minimize Monetary Cost; *].
• bbbbbb, DS value bit by bit, where b can be [0, 1, x] and x means “don't care”.

SIP It sets the IP port from where the datagrams have to come in for matching the filter [* (any IP port): it allows
to accept any IP resource; INT (internal IP resource): it allows to accept datagrams routed to any internal IP
resource].

DIP It sets the IP port where the datagrams have to be routed to for matching the filter [* (any IP port): it allows
to accept any IP resource; INT (internal IP resource): it allows to accept datagrams routed to any internal IP
resource].

CRDIR It specifies whether the datagrams, matching the filter, have to be routed transparently (value NONE) or they
have to be encrypted (value ENCRYPT) or decrypted (value DECRYPT).

CRKEY It defines the cryptographic key to be used for datagrams matching the filter.

TI Time interval; this parameters allows to specify a time band for which the IPACL can be used. The time band
must be indicated in the following form:

ggg-hh1:mm1-hh2:mm2

where
• ggg: is the indication of the day/s of the week in which the routing can be utilized and can assume the
following values:
• single day: [MO, TU, WE, TH, FR, SA, SU].
• a set of days: (es.: MO+TH or TU+TH+SU etc.).
• an interval: (es.: MO-WE or TH-SU etc. or ALL).
• hh1:mm1: is the indication of the beginning of the hourly interval of the validity of the routing.
• hh2:mm2: is the indication of the end of the hourly interval of the validity of the routing.

Use * to make the time interval to be ignored.

22.2.2. A IPACL (Add IP Access Control List filter)

It adds a new filter to the IP access list, with priority “PR:xxx” and it sets the requested parameters to the specified values.

The syntax of the command is:

a ipacl pr:xxx TYPE:val SA:val DA:val PROT:val [SPO:val DPO:val] [par:val]

[11:56:37] ABILIS_CPX:d ipacl

351
Draft IPACL - IP Access Control List Draft

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

[11:56:38] ABILIS_CPX:a ipacl pr:1 type:permit sa:192.168.0.50:192.168.0.60 da:* prot:tcp spo:* dpo

COMMAND EXECUTED

[11:58:02] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

- Not Saved (SAVE CONF) -------------------------------------------------------

Tot-IPACL-Number:3

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 PERMIT 192.168.000.050:192.168.000.060 *
DFT tcp * http(80)
* * 2 5 NONE
-------------------------------------------------------------------------------
2 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

22.2.3. C IPACL (Clear IP Acces Control List filter)

It deletes the specified definition, if present in the IP access list. The priority of those filters, whose “PR:xxx” is higher that
the deleted one, is decremented by one, because of table contiguity.

The syntax of the command is:

c ipacl pr:xx

352
Draft IPACL - IP Access Control List Draft

[11:58:02] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:3

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 PERMIT 192.168.000.050:192.168.000.060 *
DFT tcp * http(80)
* * 2 5 NONE
-------------------------------------------------------------------------------
2 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

[11:58:04] ABILIS_CPX:c ipacl pr:1

COMMAND EXECUTED

[11:58:57] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

- Not Saved (SAVE CONF) -------------------------------------------------------

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

22.2.4. S IPACL (Set IP Access Control List filter)

It sets the values of the specified filter. The syntax of the command is:

s ipacl pr:xxx par:val [par:val]

[11:58:57] ABILIS_CPX:d ipacl

353
Draft IPACL - IP Access Control List Draft

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

[11:58:58] ABILIS_CPX:s ipacl pr:0 prot:tcp

COMMAND EXECUTED

[12:00:46] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

- Not Saved (SAVE CONF) -------------------------------------------------------

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT tcp *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

22.2.5. M IPACL (Move IP Access Control List filter)

It changes the filter priority value from “PR:xxx” to “PR:yyy”.

The syntax of the command is:

m ipacl pr:xxx pr:yyy

[12:01:38] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

354
Draft IPACL - IP Access Control List Draft

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------

[12:01:39] ABILIS_CPX:m ipacl pr:0 pr:1

COMMAND EXECUTED

[12:01:43] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT 192.168.000.001:192.168.000.010 *
DFT * *
* * 2 5 NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 2 5 NONE
-------------------------------------------------------------------------------

22.2.6. F IPACL (Find IP Access Control List filter)

It verifies how the IP datagram, specified in the command, will be managed depending on the current content of the IP access
list.

The command has two different ways of searching in the IP access list:

• Standard searching mode: the search is made by verifying the source and destination IP address fields, the Type Of
Service and source IP port value; optionally it can make a verification on the destination IP port;

• Extended searching mode: the search is made by verifying the source and destination IP address, the Type Of Service,
Internet protocol, source and destination ports (required only for TCP and UDP protocols); optionally it can make a
verification on the destination IP port;

These are the syntax of the commands:

• f ipacl [STD] SrcAddr DstAddr TOS SrcIp [DstIp] [Time]

355
Draft IPACL - IP Access Control List Draft

• f ipacl EXT SrcAddr DstAddr TOS Protocol SrcPort DstPort SrcIp [DstIp] [Time]

[12:43:54] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:2

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT * *
LOW * *
* * INT * NONE
-------------------------------------------------------------------------------
1 DENY * *
* *
* * 1 * NONE
-------------------------------------------------------------------------------

[12:44:08] ABILIS_CPX:f ipacl EXT 1.1.1.1 2.2.2.2 C tcp 1024 2000 1

EXTENDED SEARCH RESULT:

IP FORWARDING IS NOT PERMITTED

[12:44:12] ABILIS_CPX:f ipacl EXT 1.1.1.1 2.2.2.2 C tcp 1024 2000 INT

EXTENDED SEARCH RESULT:

MATCH FOUND WITH IPACL PR:0

IP FORWARDING IS PERMITTED:
- OUTPUT TOS/DS: 0-TR/000011 (00001100 [0C])
- IP CLASS OF SERVICE: LOW
- ENCRYPTION/DECRYTPTION DIRECTION: NONE

22.3. Examples of IPACL configuration

22.3.1. IP packets blocking
In this example is shown how to block the connections from the IP address 192.168.20.1 to the Abilis HTTP service (i.e. IP
address 192.168.20.253).

[15:54:19] ABILIS_CPX:a ipacl pr:0 type:deny prot:tcp sa:192.168.20.1 spo:* da:192.168.20.253 dpo:8

COMMAND EXECUTED

[15:54:21] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

- Not Saved (SAVE CONF) -------------------------------------------------------

Tot-IPACL-Number:1

356
Draft IPACL - IP Access Control List Draft

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 DENY 192.168.020.001 192.168.020.253
tcp * http(80)
-------------------------------------------------------------------------------

22.3.2. Giving High Priority to VoIP packets

In the following example is shown how to assign the highest priority to the voice IP packets, when data and voice share the
same line.

[16:16:35] ABILIS_CPX:a ipacl pr:0 type:permit ipcos:high tos-in:*-d prot:udp sa:* da:* sip:int spo

COMMAND EXECUTED

[16:16:35] ABILIS_CPX:d ipacl

IPRTR resource parameters: ACL:EXT ACLBYPASS:#

COS:ENABLED COSDFT:NORMAL

Tot-IPACL-Number:1

-------------------------------------------------------------------------------
PR: [DESCR:]
TYPE: SA: DA:
IPCOS: PROT: SPO:/PO: DPO:
TOS-IN: TOS-OUT: SIP: DIP: CRDIR: CRKEY:
TI:
-------------------------------------------------------------------------------
0 PERMIT * *
HIGH udp * *
*-D * INT * NONE
-------------------------------------------------------------------------------

This rule means that all the packets with any IP source address and any UDP port, marked as “Minimum Delay” (TOS-
IN:*-D) must be sent with HIGH priority, leaving the same value of TOS (TOS-OUT:*).

357
Draft Draft

Chapter 23. RIP - Routing Information

Protocol
Nicola Trevisani
Marco Bellesia

Table of Contents
23.1. RIP Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1.1. Activating the RIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
23.1.2. RIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
23.2. RIP External Routes filter table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
23.2.1. D RIP EXTERNAL (Display RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.2. A RIP EXTERNAL (Add RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.3. C RIP EXTERNAL (Clear RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
23.2.4. S RIP EXTERNAL (Set RIP External Routes filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3. RIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.1. RIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
23.3.2. RIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4. Examples of RIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
23.4.1. Activation of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
23.4.2. Configuration of RIP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
23.4.3. Configuration of IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
23.4.4. Configuration of IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
23.4.5. Display IP routing tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

23.1. RIP Resource

The RIP resource implements the homonym routing protocols RIP1 and RIP2 for TCP/IP networks. RIP1 and RIP2 protocols
periodically extract information from IP Routings table and send them to the neighbour systems.

Sent information are:

• a list of destination networks managed by the IP router of Abilis CPX;

• the “distance” (or metric) needed to reach the destination networks.

Activating the “Routing Protocol” (RP) in the IP Resource is needed.

23.1.1. Activating the RIP resource

Add the resource to the Abilis system with the following command.

[15:43:30] ABILIS_CPX:a res:rip

RES:RIP ALREADY EXISTS

The RIP resource may already exist in the system, but may not yet be active: set it active with the command:

[16:02:48] ABILIS_CPX:s act res:rip

COMMAND EXECUTED

358
Draft RIP - Routing Information Protocol Draft

Caution
After adding or setting the RIP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[11:01:39] ABILIS_CPX:s p rip act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p rip

RES:Rip - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Routing_Information_Protocol
LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR
AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES
- ASBR section ---------------------------------------------------------
LOCAL:YES STATIC:YES OSPF:NO
LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:*
DEF-METRIC:1

23.1.2. RIP resource parameters

Use the following command to display the parameters of the resource; the command d p rip ? displays the meaning of all
parameters.

[16:02:53] ABILIS_CPX:d p rip

RES:Rip -----------------------------------------------------------------------
Run DESCR:Routing_Information_Protocol
LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR
AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES
- ASBR section ---------------------------------------------------------
LOCAL:YES STATIC:YES OSPF:NO
LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:*
DEF-METRIC:1

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT RIP runtime activation/deactivation.

udp-locport RIP local UDP port [520]

fifo Number of buffers in the RIP fifo [1..50]

maxroutes Maximum number of routes in the route table [500..10000]

SH Split Horizon: this parameter sets the routing update mode used by the RIP resource [NO: update
information sent by the RIP resource on the net will include all the IP routings stored in the IP
routing table; YES: update information sent by the RIP resource on the net will only include those
routings not obtained from the interface where the information are sent to. This updating procedure
is referred as “Split Horizon”; PR: routings should not be included in the update information,
however they are sent as well but their metric is set to 16 hops. This updating procedure is referred
as “Split Horizon and Poison Reverse”].

AUT This parameter sets the authentication functionality of information received and forwarded by the
RIP resource [NO: no authentication is applied on the information exchanged by the Abilis CPX with
other routers; STD: authentication algorithm includes sending update messages of the password as it
is set in the parameter PWD; MD5: the algorithm MD5 is used for authenticating the update messages
jointly with the password set in the parameter PWD].

PWD It sets the password used for the authentication function.

359
Draft RIP - Routing Information Protocol Draft

UT RIP updates period [10..600]

LT RIP route life time [30..1800]

GT RIP garbage collection period [10..1800]

ASBR Autonomous System Boundary Router: the router locates in point where RIP AS connects with other
AS that does not use RIP routing protocol. An ASBR is used to distribute routes received from other
ASs throughout its own AS. Usually this parameter will set to YES, because only in this case RIP
can import external routing. In case that ASBR is set to NO, RIP table will be filled only by routings
obtained by other RIP routers in the network.

LOCAL, STATIC, Enables/disables usage of LOCAL, STATIC and OSPF routes for the redistribution into RIP [NO,
OSPF YES];

LOCAL-METRIC, Metric used to redistribute LOCAL, STATIC and OSPF routes imported from the IPRTR route table
STATIC-METRIC, into RIP [0..16, *]; the value * stands for “use default”, i.e. indicates to use the DEF-METRIC
OSPF-METRIC parameter value.

DEF-METRIC It sets the default metric value that will be used for redistribution routes, of any type, imported from
the IPRTR routing table into RIP. Used when a “protocol specific” value does not override it.

The following command allows the administrator to change the configuration of the resource:

s p rip parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:rip;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

Normally you don't need to configure all the listed parameters. Many of them belong to the RIP protocol advanced options,
which are optional.

The basic options are LOG:YES to activate resource, and ASBR:YES to allow import of external routing.

23.2. RIP External Routes filter table

The table of RIP External Routes contains information about filtering rules for routes which are external to the RIP domain
and which could be imported into the RIP domain.

This table is used only when this router is declared as ASBR (ASBR:YES).

The table of RIP External Routes is used as follow:

1. An empty table is a “default accept” table.

2. A table with only “ignore” records is still a “default accept” table.

3. A table with at least one “accept” record for a protocol becomes a “default ignore” for that protocol.

In the first case, the filtering is possible only “by protocol” (through the parameters LOCAL, STATIC and OSPF).

In the second case, routes are ignored.

In the third case, all the routes for the protocol having at least one “accept” record are ignored, except those explicitly
accepted.

Commands for managing the table of RIP External Routes are the following:

• d rip external

• a rip external

• c rip external

• s rip external

360
Draft RIP - Routing Information Protocol Draft

23.2.1. D RIP EXTERNAL (Display RIP External Routes filter)

This command shows the content of the Table of RIP External Routes.

[17:20:03] ABILIS_CPX:d rip external

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
192.168.006.002/32 OSPF ACCEPT 5
192.168.006.000/24 LOCAL IGNORE 1
010.000.000.000/8 ANY ACCEPT 10
000.000.000.000/0 ANY ACCEPT *
----------------------------------------------

Meaning of the parameters:

EXTERNAL It specifies the external IP network that can be imported (or not) into RIP resource.

PROT This parameter defines a routing protocol for which this filter will be applied [ANY, LOCAL, STATIC, OSPF];

ACTION This parameter indicates if the selected network EXTERNAL can be accepted or ignored by RIP resource
[IGNORE: do not distribute this IP addresses into RIP; ACCEPT: distribute this IP addresses into RIP]. This
means that all the routing present in the IP Routings table which matches with EXTERNAL will be imported to
RIP table in case that ACTION is set to ACCEPT (and then will be used also specified metric METRIC), and
will be not imported in case that it is set to IGNORE.

METRIC This parameter sets the metric value that will be used for redistribution routes, of LOCAL, STATIC or OSPF
type, imported from the IP Routings table into RIP. The value * stands for “use default metric”.

Allowed syntax of the command are:

• d rip external: it shows the table.

• d rip external:x.x.x.x/yy PROT:val: it shows the specified entry.

23.2.2. A RIP EXTERNAL (Add RIP External Routes filter)

It adds a new entry to the Table of RIP External Routes.

The syntax of the command is:

a rip external:x.x.x.x/yy prot:val action:val [metric:val]

Example: add a rule for accept the RIP packets for the net 192.168.5.0/24 (static routing) and assign to it the exporting metric
value 5.

[16:19:36] ABILIS_CPX:a rip external:192.168.5.0/24 prot:static action:accept metric:5

COMMAND EXECUTED

[16:19:39] ABILIS_CPX:d rip external

- Not Saved (SAVE CONF) -------------------------------------------------------

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
192.168.005.000/24 STATIC ACCEPT 5
----------------------------------------------

23.2.3. C RIP EXTERNAL (Clear RIP External Routes filter)

It deletes the RIP external route entry identified by the specified mandatory parameters.

The syntax of the command is:

361
Draft RIP - Routing Information Protocol Draft

c rip external:x.x.x.x/yy prot:val

Example: clear the entry added in previous paragraph.

[16:20:11] ABILIS_CPX:d rip external

- Not Saved (SAVE CONF) -------------------------------------------------------

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
192.168.005.000/24 STATIC ACCEPT 5
----------------------------------------------

[16:21:41] ABILIS_CPX:c rip external:192.168.5.0/24 prot:static

COMMAND EXECUTED

[16:21:50] ABILIS_CPX:d rip external

- Not Saved (SAVE CONF) -------------------------------------------------------

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
*** NO RIP EXTERNAL ROUTEs DEFINED ***

23.2.4. S RIP EXTERNAL (Set RIP External Routes filter)

It sets to new values the parameters of the RIP external route entry.

The syntax of the command is:

s rip external:x.x.x.x/yy prot:val par:val [par:val...]

Example: change the metric value to an already existing entry.

[16:28:38] ABILIS_CPX:d rip external

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
192.168.005.000/24 STATIC ACCEPT 5
----------------------------------------------

[16:28:52] ABILIS_CPX:s rip external:192.168.5.0/24 prot:static metric:3

COMMAND EXECUTED

[16:29:13] ABILIS_CPX:d rip external

- Not Saved (SAVE CONF) -------------------------------------------------------

----------------------------------------------
EXTERNAL: PROT: ACTION: METRIC:
----------------------------------------------
192.168.005.000/24 STATIC ACCEPT 3
----------------------------------------------

23.3. RIP diagnostics and statistics

23.3.1. RIP diagnostics
To display the diagnostics of the RIP resource the following commands are used:

362
Draft RIP - Routing Information Protocol Draft

d d rip / d de rip Shows diagnostic information, such as the state of the resource, the state of the RIP
routing table, the current percentage of routings present into routing table, the current
number of routings present into routing table, the maximum number of routings
reached from start-up into table, the MAX-ROUTES parameter present into RIP
resource.

[18:06:40] ABILIS_CPX:d d rip

RES:Rip -----------------------------------------------------------------------
Routing_Information_Protocol
STATE:READY
------------------------------------------------------------------------
RIP ROUTINGs TABLE Diagnostics
-----------|---State---|-Current%--|--Current--|---Peak----|----Max----|
ROUTINGS |NORMAL | 52| 260| 263| 500|

23.3.2. RIP statistics

To display the statistics of the RIP resource the following commands are used:

d s rip Shows statistic information, such as the number of RIP version 1 and version 2 messages sent/received, the
overall number of messages received with a bad RIP version/command, the overall number of messages
received with a bad routing and the overall number of messages lost during transmission.

d se rip Shows statistic information in an extended format: the information listed for d s rip command are shown along
with the number of update request received/sent, the number of responses (sent/received) to the update request,
the number of NORMAL/FLASH update messages sent/received, the number of datagrams with a REQUEST/
RESPONSE command and the number of datagrams sent/received with a command different from REQUEST
or RESPONSE sent/received.

[18:06:40] ABILIS_CPX:d s rip

RES:Rip -----------------------------------------------------------------------
Routing_Information_Protocol
--- Cleared 158:19:30:57 ago, on 21/07/2007 at 15:57:28 ----------------
CHANGES:0 QUERIES:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FRM-V1 | 197| 1880|FRM-V2 | 18510552| 9287082|
BAD-VER | 0| |BAD-CMD | 0| |
BAD-ROUT | 0| |LOST | | 0|
------------------------------------------------------------------------

[18:06:40] ABILIS_CPX:d se rip

RES:Rip -----------------------------------------------------------------------
Routing_Information_Protocol
--- Cleared 158:19:30:51 ago, on 21/07/2007 at 15:57:29 ----------------
CHANGES:0 QUERIES:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FRM-V1 | 197| 1880|FRM-V2 | 18510552| 9287071|
BAD-VER | 0| |BAD-ROUT | 0| |
REQ-UPD | 385| 26|RESP-UPD | | 3361|
NORM-UPD | | 8573150|FLASH-UPD | | 712414|
REQ-CMD | 387| 26|RESP-CMD | 18510362| 9288925|
OTHER-CMD | 0| 0|BAD-CMD | 0| |
LOST | | 0|
------------------------------------------------------------------------

23.4. Examples of RIP configuration

In this section is described a typical example of RIP application.

363
Draft RIP - Routing Information Protocol Draft

Figure 23.1. RIP - Example

The purpose is:

• to ensure automatic switch to backup connection between two remote sites, when primary link is down; in one of the two
sites primary and backup connection are not managed by the same router.

In the chart we find the following elements:

• Site 1

• Abilis-1P: router that manages the primary connection with Abilis-2;

• Abilis-1B: router that manages the backup connection with Abilis-2.

• Site 2

• Abilis2: remote router connected to Site1 with a primary and backup link.

In this example is not required to analyze the kind of connection between the two sites.

In the following sections will be shown how to configure the Abilis of “Site 1”:

1. Activation of RIP resources.

2. Configuration of RIP resources.

3. Configuration of IP and IP Router resources.

4. Display IP routing tables.

In this example won't be necessary to use the RIP External Routes filter table: it means that the general rule will be “accept”.

23.4.1. Activation of RIP resources

Add the RIP resource on both Abilis of “Site1” with the following command; the RIP resource may already exist in the
system, but may not yet be active: set it active with the command s act res:rip.

• Abilis-1P:

[15:43:30] ABILIS_1P:a res:rip

RES:RIP ALREADY EXISTS

364
Draft RIP - Routing Information Protocol Draft

[16:02:48] ABILIS_1P:s act res:rip

COMMAND EXECUTED

Caution
After adding or setting the RIP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[11:01:39] ABILIS_CPX:s p rip act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p rip

RES:Rip - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Routing_Information_Protocol
LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR
AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES
- ASBR section ---------------------------------------------------------
LOCAL:YES STATIC:YES OSPF:NO
LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:*
DEF-METRIC:1

• Abilis-1B:

Repeat the same procedure for Abilis-1B.

23.4.2. Configuration of RIP resources

• Abilis-1P:

Abilis-1P is the Abilis that manage the primary link to Abilis2, so its metric default value must be the lowest one: it will be
leaved to default value 1. So, on this Abilis is enough to enable the resource.

• Abilis-1B:

Abilis-1B is the Abilis that manage the backup link to Abilis-2, so its metric default value must be higher the Abilis-1P
one: it will be set to the value 3.

[11:01:39] ABILIS_CPX:s p rip def-metric:3

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p rip

RES:Rip - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Routing_Information_Protocol
LOG:NO ACT:YES locport:520 fifo:15 max-routes:500 SH:PR
AUT:NO PWD: UT:30 LT:180 GT:120 ASBR:YES
- ASBR section ---------------------------------------------------------
LOCAL:YES STATIC:YES OSPF:NO
LOCAL-METRIC:* STATIC-METRIC:* OSPF-METRIC:*
DEF-METRIC:3

With this command we have assigned to all the IP routings of Abilis-1B the metric value 3, so they will be exported with
this cost.

23.4.3. Configuration of IP resources

Now indicating on which IP resources the RIP protocol is to be active is needed.

365
Draft RIP - Routing Information Protocol Draft

The Abilis-1P and Abilis-1B are connected on the same Ethernet LAN, so we have to active RIP on the correspondent IP
resources (res:ip-1).

The parameters which must be set are:

RP It's used to activate/deactivate routing protocols on this interface; when RIP protocol is
selected, the specific parameter section will be activated.

RIPSEND It sets the protocol used for sending RIP updates [RIP1, RIP2B, NO];

RIPRECV It sets the protocol accepted for receiving RIP updates [RIP1, RIP2, BOTH, NO];

RIPNU (normal update) It sets whether RIP updates have to be sent regularly or only in case of variations;[NO:
updates are sent only if the routing table is changed,YES: updates are sent regularly
according to the RIP resource];

RIPMETRIC It sets the metric associated to IP port according to meant and the rules prescribed by the
routing algorithm RIP.

• Abilis-1P:

[09:37:33] ABILIS_1P:s p ip-1 rp:rip

COMMAND EXECUTED

[09:37:45] ABILIS_1P:d p ip-1

RES:Ip-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO
LANRES:Eth100-1
IPADD:192.168.001.254 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:RIP
NAT:NO IPSEC:NO DIFFSERV:NO VRRP:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- RIP section ----------------------------------------------------------
RIPSEND:RIP2B RIPRECV:BOTH RIPNU:YES RIPMETRIC:1
- TRFA section ---------------------------------------------------------
TRFA:NO
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth100-1 ------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

• Abilis-1B:

[09:37:33] ABILIS_1B:s p ip-1 rp:rip

COMMAND EXECUTED

[09:37:45] ABILIS_1B:d p ip-1

RES:Ip-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO
LANRES:Eth100-1
IPADD:192.168.001.253 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:RIP
NAT:NO IPSEC:NO DIFFSERV:NO VRRP:NO

366
Draft RIP - Routing Information Protocol Draft

OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET

OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- RIP section ----------------------------------------------------------
RIPSEND:RIP2B RIPRECV:BOTH RIPNU:YES RIPMETRIC:1
- TRFA section ---------------------------------------------------------
TRFA:NO
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth100-1 ------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

Caution
To initialize the resources, use the init res:ip-1 command (to set act the changes made on uppercase
parameters) and remember to save the configuration to preserve the modifications (save conf).

23.4.4. Configuration of IP Router

It's important take a look also to the IP router configuration:

[10:44:33] ABILIS_1P:d p iprtr

RES:Iprtr ---------------------------------------------------------------------
DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.001.254)
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:1 virtual:0
- IP Access List -------------------------------------------------------
ACL:NO ACLBYPASS:#
COS:DISABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000

The parameter DEF-RIP-AD sets the default value of the Administrative Distance for the routes received from RIP.

The parameter DEF-LOCAL-AD sets the default value of the Administrative Distance for local-connected routes.

When IPRTR gets routing from different routings protocol, must give them a specific priority. This parameter can be
overridden in case of current routing is present in administrative distance table.

By joining this two parameters it's possible to complete configurations: the DEF-LOCAL-AD parameter on Abilis-1B will
have a higher value than the Abilis-1P's one, so that the local-connected routes of Abilis-1B will have the lowest priority.

Remember that the aim is to ensure automatic switch to backup connection between two remote sites. When primary link
is down, the Abilis-1B must inform Abilis-1P that the better way to reach the “Site2” is through it, but during the normal
working Abilis-1B must know that the way to reach the “Site2” is through Abilis-1P.

On Abilis-1B:

[11:15:43] ABILIS_1B:s p iprtr DEF-LOCAL-AD:180

COMMAND EXECUTED

[11:50:30] ABILIS_1B:d p iprtr

367
Draft RIP - Routing Information Protocol Draft

RES:Iprtr - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.001.253)
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:180 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:1 virtual:0
- IP Access List -------------------------------------------------------
ACL:NO ACLBYPASS:#
COS:DISABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000

Caution
To initialize the resources, use the init res:iprtr command (to set act the changes made on uppercase
parameters) and remember to save the configuration to preserve the modifications (save conf).

23.4.5. Display IP routing tables

Now let see what happens in the routing tables of the two Abilis when functioning on primary link and backup link.

This will be the routings table when primary link is active.

[12:46:18] ABILIS_1P:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|R| | | 192.168.001.253/32 | 255.255.255.255 | 192.168.001.253 | 1|120|
|*|C| | | 192.168.001.254/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.002.000/24 | 255.255.255.000 | | 5| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

[14:26:47] ABILIS_1B:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.253/32 | 255.255.255.255 | |R-ID|180|
|*|R| | | 192.168.001.254/32 | 255.255.255.255 | 192.168.001.254 | 1|120|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|R| | | 192.168.002.000/24 | 255.255.255.000 | 192.168.001.254 | 1|120|
| |C| | | 192.168.002.000/24 | 255.255.255.000 | | 5|180|
|*|R| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

In this situation Abilis-1B receives from Abilis-1P the route for the Site2's network (192.168.2.0/24): the priority of this route
is higher than the route local-connected, so the RIP route will be considered the best.

Otherwise, this will be the routing table when backup link is operating.

[12:46:18] ABILIS_1P:d ipr

368
Draft RIP - Routing Information Protocol Draft

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|R| | | 192.168.001.253/32 | 255.255.255.255 | 192.168.001.253 | 1|120|
|*|C| | | 192.168.001.254/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|R| | | 192.168.002.000/24 | 255.255.255.000 | 192.168.001.253 | 1|120|
| |C| | | 192.168.002.000/24 | 255.255.255.000 | |D 5| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

[14:26:47] ABILIS_1B:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.001.253/32 | 255.255.255.255 | |R-ID|180|
|*|R| | | 192.168.001.254/32 | 255.255.255.255 | 192.168.001.254 | 1|120|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.002.000/24 | 255.255.255.000 | | 5|180|
|*|R| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 1| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

In this situation Abilis-1P receives from Abilis-1B the route for the Site2's network (192.168.2.0/24): the IP resource 5 on
Abilis-1P is declared down (D 5), so the correspondent route won't be sent by RIP; the RIP route will be considered the best,
so the packets for the remote network will be sent through Abilis-1B.

In this way (supposing that Abilis-1P is the default gateway for the network 192.168.1.0/24), the users in Site1 could reach
the Site2's network through the backup link, without change anything on their terminals!

369
Draft Draft

Chapter 24. VRRP - Virtual Router

Redundancy Protocol
Luca Castagna
Marco Bellesia
Luigi Demuro

Table of Contents
24.1. VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.1. Activating the VRRP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
24.1.2. VRRP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.2. VRRP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
24.3. VRRP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.1. VRRP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.3.2. VRRP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
24.4. Examples of VRRP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.1. One-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
24.4.2. Load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
24.4.3. Multiple Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
24.4.4. Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
24.4.5. Virtual Routers Without Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
24.4.6. One Backup Protecting Two Masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
24.4.7. Virtual Routers With Multiple IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
24.4.8. Two-sided protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

24.1. VRRP resource

The VRRP1 feature must be purchased separately. Refer to Chapter 6, Licencing to know more about licences.

24.1.1. Activating the VRRP resource

Add the resource to the Abilis system with the following command:

[15:43:30] ABILIS_CPX:a res:vrrp

RES:VRRP ALREADY EXISTS

The VRRP resource may already exist in the system, but may not yet be active: set it active with the command:

[16:02:48] ABILIS_CPX:s act res:vrrp

COMMAND EXECUTED

Caution
After adding or setting the VRRP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[16:51:53] ABILIS_CPX:s p vrrp act:yes

1
http://en.wikipedia.org/wiki/Vrrp

370
Draft VRRP - Virtual Router Redundancy Protocol Draft

COMMAND EXECUTED

[16:52:04] ABILIS_CPX:d p vrrp

RES:Vrrp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:Virtual_Router_Redundancy_Protocol
LOG:NO ACT:YES mxps:256 TOS:0-N

24.1.2. VRRP resource parameters

Use the following command to display the parameters of the resource; by typing d p vrrp ? command it is possible to display
the meaning of all parameters.

[16:52:04] ABILIS_CPX:d p vrrp

RES:Vrrp ----------------------------------------------------------------------
Run DESCR:Virtual_Router_Redundancy_Protocol
LOG:NO ACT:NO mxps:256 TOS:0-N

Meaning of the parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime VRRP activation/deactivation.

mxps Sets the maximum size of the packets handled (expressed in bytes).

TOS Sets the TOS value for VRRP service.

The following command allows the administrator to change the configuration of the resource:

s p vrrp parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:vrrp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

24.2. VRRP table

Once VRRP resource is created, VRRP table will be present also, used to set virtual routers.

[11:58:26] ABILIS_CPX:d vrrp

-------------------------------------------------------------------------------
ID: NAME: IP: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA: DEP-RES:
IP1: IP2: IP3: IP4:
-------------------------------------------------------------------------------
*** NO VRRP ROUTERs DEFINED ***

Each record of the table allow to configure up to 4 virtual IP addresses. This is an example of master virtual router.

[15:28:20] ABILIS_CPX:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:

371
Draft VRRP - Virtual Router Redundancy Protocol Draft

HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:

DEP-RES:
-------------------------------------------------------------------------------
0 VirtualID_1 1 NONE 100 YES
1 MASTER NONE
192.168.050.200 192.168.050.201 192.168.050.202 #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Meaning of the most important parameters:

IP IP resource where virtual IPs will be applied to.

VRID Virtual Router IDentifier: this is a number used to identify current router ID. Every different router which is
going to handle MASTER and BACKUP functionalities on the same IP addresses must have also the same
router ID.

PRIO Virtual router priority used when sending datagrams to the other virtual routers. High values means higher
priority.

INIT-STATE Initial state of the VRRP router. This value indicates if at start-up current virtual router must be MASTER
or BACKUP.

DEP-RES Virtual router dependency resource. Status of specified resource will affect status of virtual router: if the
resource goes down, also virtual router will goes down allowing another backup virtual router to become
active. Multiple resources can be specified separated by comma in DEP-RES: parameter, (e.g. S VRRP ID:0
DEP-RES:Ip-1,Ip-2,Ip-3,Ip-4).

Note
The VRRP entry can become active only if all the DEP-RES are UP.

IPx Virtual router IP address assigned to specific IP: resource.

HIDE-IPx Hide IPx in RIP and OSPF updates.

The previous VRRP table can be managed with these commands:

• d vrrp : display all VRRP table entries;

• a vrrp id:val [par:val] : add a VRRP table entry;

• c vrrp id:val : clear a VRRP table entry;

• s vrrp id:val [par:val] : set parameters of a VRRP table entry.

The example below shows how to configure the Virtual router as BACKUP.

[15:28:20] ABILIS_CPX:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 VirtualID_1 1 NONE 100 YES
1 MASTER NONE
192.168.050.200 192.168.050.201 192.168.050.202 #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

372
Draft VRRP - Virtual Router Redundancy Protocol Draft

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:vrrp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

24.3. VRRP diagnostics and statistics

24.3.1. VRRP diagnostics
To display the diagnostics of the VRRP resource the following commands are used:

d d vrrp / d de vrrp Shows diagnostic information, such as the state of the resource, the number of VRRP
routers, the VRRP router name and identifier, the IP interface, the Virtual Router
identifier and priority, etc..

[18:06:40] ABILIS_CPX:d d vrrp

RES:Vrrp ----------------------------------------------------------------------
Virtual_Router_Redundancy_Protocol
STATE:DOWN ROUTERS-NUMB:0
- Routers diagnostics: -------------------------------------------------
Id: Name: Ip: VRId: Prio: Preempt:
Adver-Int: I-State: State: T-Stamp: Auth:
------------------------------------------------------------------------
*** NO VRRP ROUTERs ***

24.3.2. VRRP statistics

To display the statistics of the VRRP resource the following commands are used:

d s vrrp Shows statistic information of VRRP resource, such as the total number of received/sent advertisiment
packets, the total number of sent gratuitous ARP packets, the total number of dropped incoming
advertisiment packets, etc..

d se vrrp Shows statistic information of VRRP resource (the information listed for d s vrrp command) and the
statistics of VRRP router.

[18:06:40] ABILIS_CPX:d s vrrp

RES:Vrrp ----------------------------------------------------------------------
Virtual_Router_Redundancy_Protocol
--- Cleared 0 days 03:32:21 ago, on 27/12/2007 at 10:30:50 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PKT | 0| 0|PKT-ARP | | 0|
DROP | 0| |LONG | 0| |
NO-BUF | 0| |BAD-CHK | 0| |
BAD-FORMAT | 0| |FIND | 0| |
------------------------------------------------------------------------

[18:06:40] ABILIS_CPX:d se vrrp

RES:Vrrp ----------------------------------------------------------------------
Virtual_Router_Redundancy_Protocol
--- Cleared 0 days 03:32:24 ago, on 27/12/2007 at 10:30:51 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PKT | 0| 0|PKT-ARP | | 0|
DROP | 0| |LONG | 0| |
NO-BUF | 0| |BAD-CHK | 0| |
BAD-FORMAT | 0| |FIND | 0| |
------------------------------------------------------------------------

373
Draft VRRP - Virtual Router Redundancy Protocol Draft

*** NO VRRP ROUTERs ***

24.4. Examples of VRRP configuration

The following examples explains the distinction between virtual routers with and without owner.

24.4.1. One-sided protection

The following figure shows a simple network with two VRRP routers implementing one virtual router.

Figure 24.1. One-sided protection

The shape in the drawing labeled with VRID V1 (or 37 as an illustration that VRID is an integer) indicates that R1 and R2
are members of the VRRP virtual router V1. Router R1 is the master in virtual router V1 and R2 is the backup. As long as the
master is functional, all traffic destined to the external network gets directed to R1. But as soon as R1 fails, R2 takes over as
the master and starts handling packets forwarded to the interface associated with IP(R1).

Figure 24.1, “One-sided protection” represents this situation.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------

374
Draft VRRP - Virtual Router Redundancy Protocol Draft

ID: NAME: IPRES: VRID: PRIO: PREEMPT:

ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.2. Load sharing

Note that in Figure 24.2, “Load sharing between VRRP routers”, R2 router is completely idle during its backup periods. Its
whole purpose in the network consists of being a backup for R1. R2 is a purely redundant device. This may be considered
underutilization or waste of a valuable resource.

In such circumstances the network deployer may decide to assign R2 as a default router to some hosts on the LAN (H3
and H4), implementing a loadsharing scheme: the traffic coming from H1 and H2 is handled by R1, and H3-H4 traffic is
forwarded to R2.

However, the protection of R2 needs to be explicitly set up. To create this setup, we need to define two virtual routers, V1
and V2, and we need to define the opposite roles to our routers in V1 and V2. Figure 24.2, “Load sharing between VRRP
routers” illustrates this setup.

375
Draft VRRP - Virtual Router Redundancy Protocol Draft

Figure 24.2. Load sharing between VRRP routers

In this setup R1 is defined as the master of the V1 and R2 as the backup. In V2, R2 is the master and R1 acts as the backup.
This configuration implements:

• a load-sharing arrangement between R1 and R2;

• a mutual protection setup by having two routers acting as backups for each other.

Note
In case of failure of one of the routers, one can suffer some degradation in the network service, unless the
network is engineered accordingly.

Advantages of load sharing:

• network managers know when one fails: it is much easier to detect the failure of an active device than of equipment which
is in a passive monitoring mode;

• an active device is kept in a fully working state (software and hardware upgrades).

Following configuration shows setting parameters of R1:

376
Draft VRRP - Virtual Router Redundancy Protocol Draft

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------
1 CPX_V2 1 73 100 YES
1 BACKUP NONE
192.032.005.002 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------
1 CPX_V2 1 73 100 YES
1 MASTER NONE
192.032.005.002 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.3. Multiple Backups

The examples we have introduced so far were of the 1-to-1 cardinality; even in the mutual protection case, we had a pair
of 1-to-1 configurations. VRRP supports 1-to-N redundancy cardinalities where N can be greater than 1. Example: the R1
router is backed up by two routers, R2 and R3, without any load sharing. Figure 24.3, “Virtual router with multiple backups”
represents such a configuration.

377
Draft VRRP - Virtual Router Redundancy Protocol Draft

Figure 24.3. Virtual router with multiple backups

In this configuration R1 is designated as the default router for all the hosts and the master of the virtual router V1. R2, R3 are
redundant backups ready to take over the default router role if R1 fails. A mechanism for deciding which one of the routers,
R2 or R3, should become the master is needed.

VRRP uses the mechanism of priorities:

• priorities range normally between 1 and 255;

• the value 0 has a special meaning to indicate that the current master is releasing its mastership responsibility;

• the higher the number, the higher the priority.

• in case of failover the VRRP elects the router with the highest priority as the master.

If there are more routers having the same priority, VRRP uses a second criterion based on IP address:

• each VRRP router is associated with a set of IP addresses identifying its multiple (real) interfaces;

• using an algorithm (the smallest one, the first one in the list, etc.) a router selects one of its IP addresses as its primary IP
address;

• the router with the greater primary IP address becomes the master.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

378
Draft VRRP - Virtual Router Redundancy Protocol Draft

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R3:

[16:13:22] ABILIS_CPX_R3:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.4. Ownership
Take the configuration depicted in Figure 24.3, “Virtual router with multiple backups”. In this configuration the IP address
protected by the virtual router V1 is the IP address of the router R1, so R1 is at the same time the master and the owner of the
virtual router V1. VRRP requires the owner to assume the priority 255 and to become the master at the initialization.

When a owner becomes operational again, it becomes unconditionally master again.

Besides, as long as it is operational, an owner remains master regardless of the status of the other VRRP routers.

379
Draft VRRP - Virtual Router Redundancy Protocol Draft

When neither the current master nor the router that is in the process of becoming operational is an owner the result depends
on the priorities of the routers as well as on the value of preemption mode flag. The preemption flag regulates whether a new
operational nonowner can displace the current master based on its priority.

Let us call a master becoming operational after a failure a new contestant and use the term incumbent for the current
master from the perspective of its bid for a new election.

• Since the mastership of an owner is unconditional, a new contestant cannot displace an incumbent owner. By the same
token, a new contestant that is also an owner always displaces the incumbent.

• If the incumbent and the new contestant are not owners, in such cases the decision depends on the priorities and the
preemption mode. If the priority of the incumbent is higher than that of the new contestant, the incumbent stays in its
office.

• If the priority of the new contestant is higher than that of the incumbent and if the preemption mode is set to true, the new
contestant becomes the master. On the other hand, if the preemption mode is defined as false, in such cases the incumbent
keeps its office even if it were to have lower priority.

24.4.5. Virtual Routers Without Owner

VRRP allows to use at most one owner in a virtual router. So, there can be virtual routers protecting IP addresses that are
not owned by any specific router. Figure 24.4, “Virtual router without an owner” shows a virtual router in which none of the
group members is an owner of the protected address(es).

Figure 24.4. Virtual router without an owner

The main advantage of having a virtual router without an owner is the flexibility it gives to the network administrator. Since
the protected IP address is not the real address of any one of the participant routers, the administrator can change these
physical routers or their addresses without any need to reconfigure the virtual router itself or the hosts.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 250 YES
1 MASTER NONE

380
Draft VRRP - Virtual Router Redundancy Protocol Draft

192.032.005.010 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.010 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R3:

[16:13:22] ABILIS_CPX_R3:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 10 YES
1 BACKUP NONE
192.032.005.010 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.6. One Backup Protecting Two Masters

This example explain how to implement an N-to-1 redundancy using VRRP.

Assumption: having three VRRP routers (R1, R2, and R3) into our local networks consisting of two segments.

Goal: R2 is the back up router for both R1 and R3.

Define two different virtual routers, V1 and V2, and designate R1 as the master of V1 and R3 as the master of V2. The VRRP
router R2 assumes the role of the backup both in V1 and V3. Figure 24.5, “One backup for two masters” illustrates this
configuration.

381
Draft VRRP - Virtual Router Redundancy Protocol Draft

Figure 24.5. One backup for two masters

Disadvantages:

• at the failure of R1, R2 assumes the responsibility of handling IP(R1), and if during that period R3 also fails, R2 also starts
handling packets forwarded toward IP(R2). This arrangement may lead to unacceptable service degradation unless the
network is overengineered and/or R2 is a mighty powerful box.
• The two virtual routers in our illustration are associated with two LAN segments. R1 is on A and R3 is on B, whereas R2 is
associated with both through its two interfaces: R2.1 and R2.2.
• The router backing up two masters is not protected.
• In the event of its failure, both R1 and R2 become unprotected.

Advantages:

• given the cost considerations for backup lines N-to-1 arrangements may be quite plausible from an economic point of
view.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

382
Draft VRRP - Virtual Router Redundancy Protocol Draft

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.001 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------
1 CPX_V2 1 73 100 YES
1 BACKUP NONE
192.168.205.003 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R3:

[16:13:22] ABILIS_CPX_R3:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V2 1 73 100 YES
1 MASTER NONE
192.032.205.003 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.7. Virtual Routers With Multiple IP Addresses

VRRP may be used to protect multiple IP addresses with a single virtual router. A physical interface may have multiple IP
addresses which can be on the same or different subnets, the latter being referred to as multinetting. Multinetting is used
to renumber a network, that is, assign new addresses with a different subnet definition.

When a VRRP router has more than one address associated with its interface, it can have all its addresses protected by one
single virtual router. The router in question qualifies as the owner of all addresses, but only one of those addresses is used as
primary for the purposes of VRRP traffic.

These considerations are still true in case of multinetting. Figure 24.6, “Virtual router protecting multiple IP addresses”
depicts a virtual router protecting a default router configured for multinetting.

383
Draft VRRP - Virtual Router Redundancy Protocol Draft

Figure 24.6. Virtual router protecting multiple IP addresses

Note that the LAN segment is partitioned into two subnets: 192.32.5.0 and 192.32.205.0. Router R2, the owner of both
addresses IP(R2)5 and IP(R2)205, is the master of the virtual router V1.

Router R1 is the backup and is similarly configured. Although the IP addresses are in different subnets, they are associated
with the same virtual router V1, and they are both protected by the same virtual router V1. One of the addresses designated
via configuration as primary would be picked for V1; in this example, 192.32.5.2 and router R1 would be the backup. The
VRRP mechanism and VRRP exchanges will be on this subnet 192.32.5.0, and 192.32.5.2 will be the primary IP address of
virtual router V1.

The other address, 192.32.205.2, would simply piggyback on the protection offered by VRRP to the primary address because
both of them are on the same interface.

As long as R2 is operational, R1 will stay in the backup status; but when R2 fails, VRRP will detect the failure and R1 will
become the master and route on behalf of 192.32.5.2 as well as 192.32.205.2, since R1 is configured accordingly. In other
words, all IP addresses in a multinetted interface will switch over to the backup. We do realize that it is possible to have one
virtual router, not multiple ones, to protect more than one IP address as long as all physical routers within a virtual router
have a multinetted configuration on the same set of subnets.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.005.002 # # #

384
Draft VRRP - Virtual Router Redundancy Protocol Draft

NO NO NO NO
NONE
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.005.002 # # #
NO NO NO NO
NONE
-------------------------------------------------------------------------------

24.4.8. Two-sided protection

The following Figure 24.7, “Virtual router protecting two-sided IP addresses” shows two simple networks with two VRRP
routers implementing two virtual router depending each other.

385
Draft VRRP - Virtual Router Redundancy Protocol Draft

Figure 24.7. Virtual router protecting two-sided IP addresses

The shape in the drawing labeled with VRID V1 (or 37 as an illustration that VRID is an integer) indicates that R1 and R2
are members of the VRRP virtual router V1.

Router R1 is the master in virtual router V1 and R2 is the backup.

Each virtual router depends on the status of the other IP network it owns. For example, if IP1 (R1) goes down, it will force
also IP2 (R1) going down, allowing R2 to become the virtual master router for both interfaces it owns.

Following configuration shows setting parameters of R1:

[16:13:22] ABILIS_CPX_R1:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:

386
Draft VRRP - Virtual Router Redundancy Protocol Draft

DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 MASTER NONE
192.032.015.001 # # #
NO NO NO NO
Ip-2
-------------------------------------------------------------------------------
1 CPX_V2 2 73 100 YES
1 MASTER NONE
192.032.030.001 # # #
NO NO NO NO
Ip-1
-------------------------------------------------------------------------------

Following configuration shows setting parameters of R2:

[16:13:22] ABILIS_CPX_R2:d vrrp

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
ID: NAME: IPRES: VRID: PRIO: PREEMPT:
ADVER-INT: INIT-STATE: AUTH: AUTH-DATA:
IP1: IP2: IP3: IP4:
HIDE-IP1: HIDE-IP2: HIDE-IP3: HIDE-IP4:
DEP-RES:
-------------------------------------------------------------------------------
0 CPX_V1 1 37 100 YES
1 BACKUP NONE
192.032.015.002 # # #
NO NO NO NO
Ip-2
-------------------------------------------------------------------------------
1 CPX_V2 2 73 100 YES
1 BACKUP NONE
192.032.030.002 # # #
NO NO NO NO
Ip-1
-------------------------------------------------------------------------------

387
Draft Draft

Chapter 25. DHCP - Dynamic Host

Configuration Protocol
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
25.1. DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.1. Activating DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
25.1.2. DHCP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
25.2. DHCP Relay Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3. DHCP Server Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
25.3.1. DHCP Server tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
25.3.2. Example of configuration of DHCP in Server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
25.3.3. DHCP bindings table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
25.4. DHCP diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.1. DHCP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
25.4.2. DHCP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
25.4.3. DHCP debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5. DHCPC resource (DHCP Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.1. Activating DHCPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
25.5.2. DHCPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
25.5.3. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

25.1. DHCP resource

The Abilis DHCP1 module implements three working mode:

• BOOTP relay agent (Relay mode): internet host or router that passes DHCP messages between DHCP clients and DHCP
servers.

• DHCP Server: internet host that returns configuration parameters to DHCP clients.

• DHCP Client: internet host which retrieves configuration parameters from a server.

25.1.1. Activating DHCP resource

Add the resource to the Abilis system with the following command.

[17:14:59] ABILIS_CPX:a res:dhcp

RES:DHCP ALREADY EXISTS

The DHCP resource may already exist in the system, but may not yet be active: set it active with the command:

[17:15:17] ABILIS_CPX:s act res:dhcp

COMMAND EXECUTED

1
http://en.wikipedia.org/wiki/Dhcp

388
Draft DHCP - Dynamic Host Draft
Configuration Protocol

Caution
After adding or setting the DHCP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p dhcp act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p dhcp

RES:Dhcp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Dynamic_Host_Configuration_Protocol
LOG:DS ACT:YES srv-udp-locport:67 cli-udp-locport:68
msg-len:1472 mode:RELAY MAX-HOPS:4 SRV:#
LOCIPADD:R-ID (192.168.001.001)
WDIR:C:\APP\DHCP\

25.1.2. DHCP resource parameters

Use the following command to display the parameters of the resource; by typing d p dhcp ? command, the meaning of all
parameters is shown.

[17:15:17] ABILIS_CPX:d p dhcp

RES:Dhcp ----------------------------------------------------------------------
Run DESCR:Dynamic_Host_Configuration_Protocol
LOG:DS ACT:YES srv-udp-locport:67 cli-udp-locport:68
msg-len:1472 mode:RELAY MAX-HOPS:4 SRV:#
LOCIPADD:R-ID (192.168.001.001)
WDIR:C:\APP\DHCP\

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime DHCP activation/deactivation.

srv-udp-locport Server side UDP port [default is 67].

cli-udp-port Client side UDP port [default is 68].

msg-len Maximum length of DHCP message, actually the UDP payload [548..2048];

mode It specifies the mode of DHCP port working [SERVER, RELAY].

Parameters for mode:RELAY only:

MAX-HOPS It specifies the maximum number of DHCP relay agent hops.

SRV It specifies the DHCP Server to which requests must be forwarded; it can be set to an IP address, in Dotted
Decimal Notation, or the name of an IP list;

LOCIPADD It specifies the IP address that DHCP relay agent will use as “source address” in the requests relayed to the
server.

Parameters for mode:SERVER only:

max-clients Maximum number of supported DHCP clients; it actually determines the size of the binding database on
disk and in memory.

ICMPCHK Enables ICMP checking of IP address. When it is set to YES, ICMP checking is enabled. Before sending
the DHCPOFFER message, the server sends two ICMP ping requests to check the IP address which was
allocated. If both timeouts expire, the server will send the DHCP offer message, otherwise it will mark this
IP address as abandoned and will not send response.

389
Draft DHCP - Dynamic Host Draft
Configuration Protocol

MAC-FILTER Enables/disables the selection of serviceable clients based on their MAC address. When it is set to YES,
MAC filtering is enabled. When DHCP receives an incoming request and before processing it, the DHCP
verifies that the sender's MAC address is allowed by using MAC-LIST and MAC-RULE parameters
current setting (MAC-LIST and MAC-RULE appear when MAC-FILTER is set to YES).

WDIR Selects the directory where DHCP.BND (BND stays for binding) file is saved. A binding is a collection of
configuration parameters, including at least an IP address, associated with or “bound to” a DHCP client.
Bindings are managed by DHCP servers.

The following command allows the administrator to change the configuration of the resource:

s p dhcp parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:dhcp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

25.2. DHCP Relay Mode

DHCP is designed to use the BOOTP2 protocol specifications so that DHCP messages are passed between DHCP clients and
DHCP servers.

For example, to allow the relay of DHCP packets to the server 192.168.0.250, type the command:

[18:08:56] ABILIS_CPX:s p dhcp act:yes mode:relay srv:192.168.0.250

COMMAND EXECUTED

[18:08:56] ABILIS_CPX:d p dhcp

RES:Dhcp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:Dynamic_Host_Configuration_Protocol
LOG:DS ACT:YES srvport:67 cliport:68
msg-len:1472 mode:RELAY MAX-HOPS:4 SRV:192.168.000.250
LOCIPADD:R-ID (192.168.001.001)
WDIR:C:\APP\DHCP\

25.3. DHCP Server Mode

A DHCP server is an Internet host that returns configuration parameters to DHCP clients.

Two steps are required to configure Abilis as DHCP server:

• setting the mode parameter to SERVER;

• configuring the DHCP Server tables.

[09:56:36] ABILIS_CPX:s p dhcp mode:server

COMMAND EXECUTED

[09:56:45] ABILIS_CPX:d p dhcp

RES:Dhcp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:Dynamic_Host_Configuration_Protocol
LOG:DS ACT:YES srvport:67 cliport:68
msg-len:1472 mode:SERVER max-clients:300 ICMPCHK:NO
MAC-FILTER:NO
WDIR:C:\APP\DHCP\

2
http://en.wikipedia.org/wiki/Bootstrap_Protocol

390
Draft DHCP - Dynamic Host Draft
Configuration Protocol

Caution
To activate the changes made on the lowercase parameters a save conf and an Abilis restart are required (i.e.
with warm start command).

25.3.1. DHCP Server tables

The configuration of DHCP server mode is based on three tables:

• DHCP Profiles table: table containing all the parameters to be distributed to clients (i.e. IP Address, Gateway, WINS,
DSN, Domain, …);

• DHCP Subnets: table containing the network IP address of the DHCP subnet, the subnet mask, the pools of addresses to
distribute and the “lease” time of the IP addresses;

• DHCP Hosts: allows to define a static association between a specific MAC-ADDRESS of a client and an IP address.

Tip
Interesting chapters:

Section 52.15.2, “How to activate the DHCP in server mode”;

Section 25.3.2, “Example of configuration of DHCP in Server mode”.

25.3.1.1. DHCP Profiles table

The DHCP Profiles table can hold up to 129 definitions, indexed from 0 up to 128.

The user can arbitrarily add/delete the definitions from the index 1 to 128. The profile with index 0 can't be deleted because
it's a default profile.

Changes made on the table can be activated by executing the initialization command init res:dhcp.

The commands for the DHCP Profiles table management are:

• d dhcp prof:xxx[,yyy,...] : display DHCP profile;

• a dhcp prof:xxx [par:val] : add DHCP profile;

• c dhcp prof:xxx[,yyy,...] :clears DHCP profile;

• s dhcp prof:xxx[,yyy,...] par:val [par:val]: set DHCP profile parameters.

A complete list of available configuration parameters is available by typing d dhcp prof: ?.

[09:24:57] ABILIS_CPX:d dhcp prof: ?

D DHCP PROF:xxx[,yyy,...] Display DHCP profile [0..128, A]

DHCP Profile parameter(s):

NAME: Profile name. From 0 up to 32 ASCII characters.

Spaces are not allowed. Case is preserved.
TTL: IP time-to-live [0, 1..255]
KEEPALIVE: TCP keepalive interval [0, 15..65535 sec.]
NB-SCOPE-ID: Netbios scope identifier. From 0 up to 32 ASCII characters.
Spaces are not allowed. Case is preserved.
NB-NODE-TYPE: Netbios node type [UNK, B, P, M, H]
DOMAIN: IP domain name. From 0 up to 32 ASCII characters.
Spaces are not allowed. Case is preserved.
GW1: First gateway [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
GW2: Second (backup) gateway [0.0.0.0, 1-126.x.x.x, 127.0.0.1,
128-223.x.x.x]
GW3: Third (backup) gateway [0.0.0.0, 1-126.x.x.x, 127.0.0.1,
128-223.x.x.x]
DNS1: Primary Domain Name server [0.0.0.0, 1-126.x.x.x, 127.0.0.1,

391
Draft DHCP - Dynamic Host Draft
Configuration Protocol

128-223.x.x.x]
DNS2: Secondary Domain Name server [0.0.0.0, 1-126.x.x.x, 127.0.0.1,
128-223.x.x.x]
SMTP: Simple Mail Transport Protocol (SMTP) server [0.0.0.0,
1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
POP3: Post Office Protocol (POP3) server [0.0.0.0, 1-126.x.x.x,
127.0.0.1, 128-223.x.x.x]
NNTP: Network News Transport Protocol (NNTP) server [0.0.0.0,
1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
WWW: World Wide Web (WWW) server [0.0.0.0, 1-126.x.x.x, 127.0.0.1,
128-223.x.x.x]
FINGER: Finger server [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
IRC: Internet Relay Chat server [0.0.0.0, 1-126.x.x.x, 127.0.0.1,
128-223.x.x.x]
NTP: NTP/SNTP server [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
TIME: TIME server [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
WINS1: First WINS server [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
WINS2: Second WINS server [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
TFTP: TFTP server name. From 0 up to 64 ASCII characters.
Spaces are not allowed. Case is preserved.
BOOTFILE: Bootfile name. From 0 up to 128 ASCII characters.
Spaces are not allowed. Case is preserved.

25.3.1.2. DHCP Subnets table

The DHCP Subnets table can hold up to 128 definitions.

Changes made on the table can be activated by executing the initialization command init res:dhcp.

The commands for the DHCP Subnets table management are:

• d dhcp lan:xxx[,yyy,...] : display DHCP subnet;

• a dhcp lan:xxx [par:val] : add DHCP subnet;

• c dhcp lan:xxx[,yyy,...] :clears DHCP subnet;

• s dhcp lan:xxx[,yyy,...] par:val [par:val]: set DHCP subnet parameters.

A complete list of available configuration parameters is available by typing d dhcp lan: ?.

[09:27:06] ABILIS_CPX:d dhcp lan: ?

D DHCP LAN:xxx[,yyy,...] Display DHCP subnet [1..128, A]

DHCP Subnet parameter(s):

NAME: Subnet name. From 0 up to 32 ASCII characters.

Spaces are not allowed. Case is preserved.
NET: Network address in DDN or network address and mask in Slash
Notation [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]/[0..32]
MASK: Network mask in DDN [0.0.0.0, 128.0.0.0-255.255.255.252]
POOL1: First IP pool. A single IP address [1-126.x.x.x, 128-223.x.x.x]
or two IP addresses separated by ':' (colon) or "#".
(E.g.: 150.200.192.192 or 192.168.0.0:192.168.0.100)
POOL2: Second IP pool. A single IP address [1-126.x.x.x, 128-223.x.x.x]
or two IP addresses separated by ':' (colon) or "#".
(E.g.: 150.200.192.192 or 192.168.0.0:192.168.0.100)
POOL3: Third IP pool. A single IP address [1-126.x.x.x, 128-223.x.x.x]
or two IP addresses separated by ':' (colon) or "#".
(E.g.: 150.200.192.192 or 192.168.0.0:192.168.0.100)
POOL4: Fourth IP pool. A single IP address [1-126.x.x.x, 128-223.x.x.x]
or two IP addresses separated by ':' (colon) or "#".
(E.g.: 150.200.192.192 or 192.168.0.0:192.168.0.100)
POOL5: Fifth IP pool. A single IP address [1-126.x.x.x, 128-223.x.x.x]

392
Draft DHCP - Dynamic Host Draft
Configuration Protocol

or two IP addresses separated by ':' (colon) or "#".

(E.g.: 150.200.192.192 or 192.168.0.0:192.168.0.100)
PROF: Profile [NONE, 1..128]
DEF-LEASE: Default lease time of the IP address [60..1000000 sec.]
MAX-LEASE: Maximum lease time of the IP address [60..1000000 sec.]

25.3.1.3. DHCP Hosts table

The DHCP Hosts table can hold up to 500 definitions, indexed from 1 up to 500.

Changes made on the table can be activated by executing the initialization command init res:dhcp.

The commands for the DHCP Hosts table management are:

• d dhcp host:xxx[,yyy,...] : display DHCP host;

• a dhcp host:xxx [par:val] : add DHCP host;

• c dhcp host:xxx[,yyy,...] :clears DHCP host;

• s dhcp host:xxx[,yyy,...] par:val [par:val]: set DHCP host parameters.

A complete list of available configuration parameters is available by typing d dhcp host: ?

[09:27:33] ABILIS_CPX:d dhcp host: ?

D DHCP HOST:xx Display DHCP host [1..500, A]

DHCP Host parameter(s):

MAC: MAC address [00-00-00-00-00-01..FF-FF-FF-FF-FF-FF]

IP: IP address [0.0.0.0, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
PROF: Profile [LAN, 1..128]
NAME: Host name. From 0 up to 32 ASCII characters.
Spaces are not allowed. Case is preserved.

25.3.2. Example of configuration of DHCP in Server mode

In this example the DHCP Server is configured to distribute the following parameters:

• Network address: 192.168.0.0/24

• IP pool of addresses: from 192.168.0.131 to 192.168.0.179
• DNS server 1:192.168.0.232
• DNS server 2:192.168.0.251
• Default Gateway: 192.168.0.232
• WINS server: 192.168.0.50
• SMTP server: 192.168.0.250
• POP3 server: 192.168.0.250
• No static association between MAC-ADDRESS and any leased IP
• ICMP checking of IP address
• No MAC Filtering

First, set the dhcp resource active.

[15:20:37] ABILIS_CPX:s p dhcp act:yes mode:server

COMMAND EXECUTED

[15:40:56] ABILIS_CPX:d p dhcp

RES:Dhcp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:Dynamic_Host_Configuration_Protocol
LOG:DS ACT:YES srvport:67 cliport:68
msg-len:1472 mode:SERVER max-clients:300 ICMPCHK:NO
MAC-FILTER:NO

393
Draft DHCP - Dynamic Host Draft
Configuration Protocol

WDIR:C:\APP\DHCP\

Configure the DHCP Profiles table.

[15:54:54] ABILIS_CPX:a dhcp prof:1 name:Private_LAN gw1:192.168.0.232 dns1:192.168.0.232 dns2:192.

COMMAND EXECUTED

[15:55:11] ABILIS_CPX:d dhcp prof

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

PROF: |NAME:
-------------------------------------------------------------------------------
0 Default_profile
1 Private_LAN

[15:55:27] ABILIS_CPX:d dhcp prof:1

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
-------------+-----------------------------------------------------------------
PROF: 1
NAME: Private_Lan
GW1: 192.168.000.232
DNS1: 192.168.000.232
DNS2: 192.168.000.251
SMTP: 192.168.000.250
POP3: 192.168.000.250
WINS1: 192.168.000.050
---------------------------------------------------

Configure the DHCP Subnets table setting the network address, the pool and the identifier of DHCP Profile.

[16:02:17] ABILIS_CPX:a dhcp lan:1 name:Private_Lan net:192.168.0.0/24 pool1:192.168.0.131:192.168.

COMMAND EXECUTED

[16:03:22] ABILIS_CPX:d dhcp lan

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

LAN: |NET: |MASK:

-------------------------------------------------------------------------------
1 192.168.000.000 255.255.255.000

[16:03:26] ABILIS_CPX:d dhcp lan:1

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
-------------+-----------------------------------------------------------------
LAN: 1
NAME: Private_Lan
NET: 192.168.000.000/24
MASK: 255.255.255.000
POOL1: 192.168.000.131:192.168.000.179
PROF: 1
-------------------------------------------------------------------------------

Configuration of DHCP Hosts table is not required.

Now the configuration is complete.

394
Draft DHCP - Dynamic Host Draft
Configuration Protocol

Caution
To initialize the resource, use command init res:dhcp (to set act the changes made on uppercase parameters
and in the tables) and save the configuration with save conf command to make the changes permanent.

Caution
To set act changes made on lowercase parameters a save conf and an Abilis restart are needed (i.e. with
warm start command).

Tip
Interesting chapters: Section 52.15.2, “How to activate the DHCP in server mode”.

25.3.3. DHCP bindings table

The DHCP bindings table is the memory data base which stores bindings allocated for DHCP clients.

A binding record includes the information about allocated IP address, start time and end time of lease, profile which is
currently used by a DHCP client and some other information.

The Table of DHCP bindings is used in server mode only.

Tip
Refer to Section 25.3.3.1, “Appendix - how DHCP bindings table works” to have more information about
DHCP bindings tables functioning.

Commands for handling DHCP bindings table are:

• d dhcp bind: it displays DHCP bindings summary, in a synthetic format;

• d dhcp binde: it display DHCP bindings details, in an extended format;

• c dhcp bind: this command allows to remove a DHCP binding entry from the DHCP bindings table identified by the
specified IP address.

Some examples follow.

[11:34:14] ABILIS_CPX:d dhcp bind

------------------+----------------+------+-----------------+------------------
MAC: |IP: |PROF: |Last request(GMT)|Expiry on(GMT)
------------------+----------------+------+-----------------+------------------
00-0C-6E-DE-2B-C1 192.168.000.002 1 27/12/2007 14:26 07/02/2036 06:28
00-0C-6E-E9-DE-29 192.168.000.003 1 27/12/2007 11:56 07/02/2036 06:28
00-0C-6E-DE-2C-15 192.168.000.005 1 28/12/2007 09:46 07/02/2036 06:28
00-08-54-01-D5-B7 192.168.000.006 1 05/10/2007 06:27 07/02/2036 06:28
00-40-CA-63-34-E5 192.168.000.008 1 28/12/2007 07:45 07/02/2036 06:28
00-48-54-13-23-E7 192.168.000.009 1 28/12/2007 10:22 07/02/2036 06:28
00-48-54-13-22-78 192.168.000.010 1 27/12/2007 12:45 07/02/2036 06:28
00-40-CA-63-34-6A 192.168.000.011 1 20/12/2007 09:46 07/02/2036 06:28
00-40-CA-63-34-CD 192.168.000.012 1 11/12/2007 15:49 07/02/2036 06:28
00-03-93-D9-71-94 192.168.000.014 1 28/12/2007 10:23 07/02/2036 06:28
00-08-54-02-00-78 192.168.000.024 1 12/12/2007 18:19 07/02/2036 06:28
00-40-CA-63-35-15 192.168.000.025 1 28/12/2007 07:16 07/02/2036 06:28
00-40-CA-63-34-E3 192.168.000.029 1 28/12/2007 08:57 07/02/2036 06:28
00-0C-6E-DE-2B-FD 192.168.000.030 1 28/12/2007 08:12 07/02/2036 06:28
00-40-CA-63-34-F2 192.168.000.032 1 28/12/2007 08:36 07/02/2036 06:28
00-40-CA-63-34-F8 192.168.000.033 1 28/12/2007 08:14 07/02/2036 06:28
00-0C-6E-DE-2B-C8 192.168.000.034 1 13/12/2006 11:33 07/02/2036 06:28
00-40-CA-63-34-82 192.168.000.035 1 28/12/2007 08:12 07/02/2036 06:28
00-40-CA-63-34-97 192.168.000.158 1 28/12/2007 07:45 28/12/2007 17:45
00-09-45-52-65-5B 192.168.000.161 1 28/12/2007 10:07 28/12/2007 20:07
00-09-45-52-10-44 192.168.000.166 1 28/12/2007 08:34 28/12/2007 18:34

395
Draft DHCP - Dynamic Host Draft
Configuration Protocol

00-07-85-51-F5-D6 192.168.000.171 1 28/12/2007 09:53 28/12/2007 19:53

00-40-CA-63-34-99 192.168.000.174 1 28/12/2007 09:45 28/12/2007 19:45

[11:34:21] ABILIS_CPX:d dhcp binde

----+-----+-------------------+-----------------+-------+----------------------
O: | ST: | MAC: | IP: | PROF: | Last request(GMT)
| Expiry on(GMT)
----+-----+-------------------+-----------------+-------+----------------------
H ACT 00-0C-6E-DE-2B-C1 192.168.000.002 1 27/12/2007 14:26:45
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-0C-6E-E9-DE-29 192.168.000.003 1 27/12/2007 11:56:22
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-0C-6E-DE-2C-15 192.168.000.005 1 28/12/2007 09:46:46
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-08-54-01-D5-B7 192.168.000.006 1 05/10/2007 06:27:24
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-E5 192.168.000.008 1 28/12/2007 07:45:54
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-48-54-13-23-E7 192.168.000.009 1 28/12/2007 10:22:51
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-48-54-13-22-78 192.168.000.010 1 27/12/2007 12:45:53
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-6A 192.168.000.011 1 20/12/2007 09:46:24
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-CD 192.168.000.012 1 11/12/2007 15:49:57
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-03-93-D9-71-94 192.168.000.014 1 28/12/2007 10:23:08
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-08-54-02-00-78 192.168.000.024 1 12/12/2007 18:19:31
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-35-15 192.168.000.025 1 28/12/2007 07:16:40
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-E3 192.168.000.029 1 28/12/2007 08:57:33
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-0C-6E-DE-2B-FD 192.168.000.030 1 28/12/2007 08:12:27
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-F2 192.168.000.032 1 28/12/2007 08:36:31
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-F8 192.168.000.033 1 28/12/2007 08:14:59
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-0C-6E-DE-2B-C8 192.168.000.034 1 13/12/2006 11:33:52
07/02/2036 06:28:15
-------------------------------------------------------------------------------
H ACT 00-40-CA-63-34-82 192.168.000.035 1 28/12/2007 08:12:12
07/02/2036 06:28:15

396
Draft DHCP - Dynamic Host Draft
Configuration Protocol

-------------------------------------------------------------------------------
P EXP 00-0C-0C-01-5C-81 192.168.000.131 1 29/11/2007 10:59:42
29/11/2007 20:59:42
-------------------------------------------------------------------------------
P EXP 00-0C-0C-01-5B-BE 192.168.000.132 1 07/12/2007 10:17:12
07/12/2007 20:17:12
-------------------------------------------------------------------------------
P EXP 00-40-CA-63-34-B8 192.168.000.133 1 11/12/2007 21:58:05
12/12/2007 07:58:05
-------------------------------------------------------------------------------
P EXP 00-0C-29-52-67-31 192.168.000.134 1 17/12/2007 17:59:25
18/12/2007 03:59:25
-------------------------------------------------------------------------------
P EXP 00-16-36-EA-44-84 192.168.000.135 1 19/12/2007 10:10:38
19/12/2007 20:10:38
-------------------------------------------------------------------------------
P EXP 00-E0-4C-03-27-BC 192.168.000.136 1 18/12/2007 17:29:46
19/12/2007 03:29:46
-------------------------------------------------------------------------------
P EXP 00-0D-60-CE-7D-1D 192.168.000.150 1 07/11/2007 13:53:53
07/11/2007 23:53:53
-------------------------------------------------------------------------------
P EXP 00-E0-00-9B-D5-BB 192.168.000.151 1 08/08/2007 14:24:57
09/08/2007 00:24:57
-------------------------------------------------------------------------------
P EXP 00-07-95-BF-3A-7E 192.168.000.152 1 02/10/2007 10:36:55
02/10/2007 20:36:55
-------------------------------------------------------------------------------
P EXP 00-02-3F-0D-D5-A0 192.168.000.153 1 28/09/2007 07:22:33
28/09/2007 17:22:33
-------------------------------------------------------------------------------
P EXP 00-90-33-0F-02-EE 192.168.000.154 1 05/11/2007 18:18:39
06/11/2007 04:18:39
-------------------------------------------------------------------------------
P EXP 00-0F-20-CC-22-3C 192.168.000.155 1 17/10/2007 16:09:36
18/10/2007 02:09:36
-------------------------------------------------------------------------------
P EXP 00-16-6F-41-4B-EE 192.168.000.156 1 26/10/2007 13:42:41
26/10/2007 23:42:41
-------------------------------------------------------------------------------
P EXP 00-18-41-08-A0-74 192.168.000.157 1 25/10/2007 12:39:59
25/10/2007 22:39:59
-------------------------------------------------------------------------------
P ACT 00-40-CA-63-34-97 192.168.000.158 1 28/12/2007 07:45:26
28/12/2007 17:45:26
-------------------------------------------------------------------------------
P EXP 00-15-F2-03-06-4C 192.168.000.159 1 03/10/2007 08:01:28
03/10/2007 18:01:28
-------------------------------------------------------------------------------
P EXP 00-4F-4E-12-42-B9 192.168.000.160 1 19/11/2007 07:29:56
19/11/2007 17:29:56
-------------------------------------------------------------------------------
P ACT 00-09-45-52-65-5B 192.168.000.161 1 28/12/2007 10:07:13
28/12/2007 20:07:13
-------------------------------------------------------------------------------
P EXP 00-A0-D1-38-A4-14 192.168.000.163 1 07/09/2007 14:59:33
08/09/2007 00:59:33
-------------------------------------------------------------------------------
P EXP 00-16-D4-F2-06-A3 192.168.000.164 1 26/10/2007 15:32:37
27/10/2007 01:32:37
-------------------------------------------------------------------------------
P REL 00-40-8C-80-40-C2 192.168.000.165 1 23/11/2007 10:40:17

397
Draft DHCP - Dynamic Host Draft
Configuration Protocol

23/11/2007 10:42:40
-------------------------------------------------------------------------------
P ACT 00-09-45-52-10-44 192.168.000.166 1 28/12/2007 08:34:23
28/12/2007 18:34:23
-------------------------------------------------------------------------------
P EXP 00-03-93-D9-71-94 192.168.000.167 1 14/09/2007 06:40:59
14/09/2007 16:40:59
-------------------------------------------------------------------------------
P EXP 00-40-CA-63-34-C7 192.168.000.169 1 16/11/2007 10:00:05
16/11/2007 20:00:05
-------------------------------------------------------------------------------
P EXP 00-15-F2-59-09-7C 192.168.000.170 1 20/11/2007 15:31:45
21/11/2007 01:31:45
-------------------------------------------------------------------------------
P ACT 00-07-85-51-F5-D6 192.168.000.171 1 28/12/2007 09:53:45
28/12/2007 19:53:45
-------------------------------------------------------------------------------
P EXP 00-11-D8-70-A6-1D 192.168.000.172 1 30/08/2007 08:00:15
30/08/2007 18:00:15
-------------------------------------------------------------------------------
P EXP 00-0C-0C-01-48-AA 192.168.000.173 1 26/09/2007 12:34:27
26/09/2007 22:34:27
-------------------------------------------------------------------------------
P ACT 00-40-CA-63-34-99 192.168.000.174 1 28/12/2007 09:45:49
28/12/2007 19:45:49
-------------------------------------------------------------------------------
P EXP 00-0C-0C-01-48-BE 192.168.000.175 1 26/09/2007 12:33:29
26/09/2007 22:33:29
-------------------------------------------------------------------------------
P EXP 00-09-45-63-97-70 192.168.000.176 1 03/09/2007 11:54:48
03/09/2007 21:54:48
-------------------------------------------------------------------------------
P EXP 00-16-36-3E-1B-CB 192.168.000.177 1 16/11/2007 16:00:02
17/11/2007 02:00:02
-------------------------------------------------------------------------------
P EXP 00-1D-60-70-BE-1A 192.168.000.178 1 16/10/2007 08:24:22
16/10/2007 18:24:22
-------------------------------------------------------------------------------
P EXP 00-40-F4-BC-F5-3D 192.168.000.179 1 07/12/2007 13:54:03
07/12/2007 23:54:03
-------------------------------------------------------------------------------

Meaning of the most important parameters:

O Origin of the binding [H: allocated from host tables; P: allocated from IP pools of one of subnets
from subnets table; ?: origin unknown].

ST State of the binding [REL: released; ACT:active, EXP: expired, ABD: abandoned, UNK: unknown
(error state)].

MAC The binded MAC address of the DHCP client.

IP The IP address assigned to the DHCP client with the MAC address.

PROF The identifier of DHCP profile from profiles table.

Last request(GMT) The GMT date and time value when the lease was assigned/renewed the last time.

Expiry on(GMT) The GMT date and time value when the lease will expire.

Here there are few samples of bindings clear commands:

[15:00:45] ABILIS_CPX:c dhcp bind ip:192.168.0.161

YOU ARE GOING TO DELETE THE SPECIFIED DHCP BINDING ENTRY FROM THE DATA BASE IN MEMORY.
DO YOU WANT TO PROCEES (Y/N)? Y

398
Draft DHCP - Dynamic Host Draft
Configuration Protocol

COMMAND EXECUTED

[15:00:45] ABILIS_CPX:c dhcp bind ip:a

YOU ARE GOING TO DELETE THE WHOLE CONTENT OF THE DHCP BINDINGS DATA BASE IN MEMORY.
DO YOU WANT TO PROCEES (Y/N)? Y

COMMAND EXECUTED

25.3.3.1. Appendix - how DHCP bindings table works

DHCP bindings tables is stored in the DHCP.BND file in the location defined by the WDIR parameter.

It allows storage of up to max-clients bindings, one per each record.

Every one minute the DHCP server checks the bindings table and saves all bindings to the file, if the table was changed since
the last time it was updated.

During Abilis CPX DHCP resource start-up, the DHCP driver executes the following operations:

• if the file DHCP.BND exists:

• reads the bindings table from the CF;
• updates the file, making a write operation try;
• writing attempt successful: the DHCP server goes to the ACTIVE state;
• writing attempt unsuccessful: the DHCP server goes to the STOP state; it writes a warning message into the System
Log (i.e. “W: DHCP STOPPED”) and it doesn't load the bindings DHCP.BND file content.
• if the file doesn't exist:

• it tries to create it. If it can't, the server goes to the STOP state and it writes a warning message into the System Log (i.e.
“W: DHCP STOPPED”).

After loading the DHCP.BND file, the DHCP server checks the bindings according to the current configuration of the DHCP
driver. The records which don't conform to the current configuration will be marked as “not valid” and they will not be used
by the DHCP server.

The DHCP server makes the next checks when loading bindings and marks the binding as “invalid” in all the following
cases:

• The subnet record which is corresponding to the IP address from the binding is not found in the subnets table.

• The profile identifier from the binding is not found in the the profiles table.

If the binding is static (i.e. allocated from the hosts):

• The host record with the IP and MAC addresses which are corresponding to the IP and MAC addresses from the loading
binding is not found in the hosts table.

• The IP address from the binding is found in one of the pools of the subnet record (i.e. if the corresponding subnet record
was found).

if the binding is dynamic (i.e. allocated from the pools):

• The host record with the IP and MAC addresses which are corresponding to the IP and MAC addresses from the loading
binding is found in the hosts table;

• The IP address from the binding is not found in one of the pools of the subnet record (i.e. if the corresponding subnet
record was found).

25.4. DHCP diagnostics, statistics and debug

25.4.1. DHCP diagnostics
The following commands are used to display diagnostics:

d d dhcp / d de dhcp It informs about the MODE configuration [RELAY/SERVER], the STATE of the
resource [DOWN, INACT, STOP, ACTIVE, ERR] and the current bindings situation.

[17:49:20] ABILIS_CPX:d d dhcp

399
Draft DHCP - Dynamic Host Draft
Configuration Protocol

RES:Dhcp ----------------------------------------------------------------------
Dynamic_Host_Configuration_Protocol
MODE:SERVER STATE:ACTIVE
- Server Bindings ------------------------------------------------------
------- Summary -------|------- Types ---------|------- States ---------
MAX |300 |ACT-STATIC |20 |ACTIVE |35 |
USED |67 |ACT-DYNAMIC |15 |EXPIRED |32 |
FREE |233 | | |RELEASED |0 |
REUSABLE |32 |ALL-STATIC |20 |ABANDONED |0 |
| |ALL-DYNAMIC |47 |INCOMPLETE |0 |
| | | |INVALID |0 |
------------------------------------------------------------------------

25.4.2. DHCP statistics

The following commands are used to display statistics:

d s dhcp / d se dhcp Statistics are divided between Server mode and Relay mode.

Meaning of the most important statistics about Server mode:

• REQUESTS: it shows the total number of packets sent from DHCP client to DHCP
server.

• RESPONSES: it shows the total number of packets sent from DHCP server to DHCP
client.

• CHAR: it shows the total number of received (INPUT) and sent (OUTPUT)
characters. UDP interface overhead excluded.

• PCK: it shows the total number of received (INPUT) and sent (OUTPUT) packets.

• LONG: it shows the total number of lost received (INPUT) and number of not sent
(OUTPUT) DHCP packets which are too long for the configured msg-len value from
configuration.

• BAD-FORMAT: it shows the total number of lost received DHCP packets with bad
format.

• UNK-IPP: it shows the total number of received packets with “unknown” IP

resource. This situation can occur only for software bugs.

The other statistics are “simple” counters of the relative packets used by DHCP
protocols.

Meaning of the most important statistics about Server mode:

• REQUESTS: it shows the total number of good incoming requests received from
client which are suitable for relaying (INPUT) and the total number of requests
actually relayed to the servers (OUTPUT). In the case of multiple servers the counter
is increased for each of them.

• RESPONSES: it shows the total number of good incoming responses received from
server(s) which are suitable for relaying to the client (INPUT) and the total number
of responses actually relayed to the client (OUTPUT).

• HOP-EXCEED: number of discarded requests because the “hops number” value

in the DHCP packet exceeded the threshold. Incremented for client's request that
was already relayed by several agents and their count, present in 'hops' field of the
received packet, exceeds the threshold configured in MAX-HOPS.

• BAD-GW: it shows the total number of discarded responses for “not matching”
gateway address ('giaddr' field in DHCP packet). Incremented for every server's
response packet whose 'giaddr' field value does not match any address of the router's
interfaces.

400
Draft DHCP - Dynamic Host Draft
Configuration Protocol

[11:42:10] ABILIS_CPX:d s dhcp

RES:Dhcp ----------------------------------------------------------------------
Dynamic_Host_Configuration_Protocol
--- Cleared 0 days 15:02:19 ago, on 27/12/2007 at 20:51:58 -------------
------------------------------------------------------------------------
Server mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
REQUESTS | 49| |RESPONSES | | 23|
CHAR | 14820| 6900|PCK | 49| 23|
LONG | 0| 0|BAD-FORMAT | 0| |
UNK-IPP | 0| | | | |
DISCOVER | 2| |OFFER | | 2|
REQUEST | 21| |ACK | | 21|
DECLINE | 0| |NAK | | 0|
RELEASE | 0| | | | |
INFORM | 26| |
------------------------------------------------------------------------
Relay mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
REQUESTS | 0| 0|RESPONSES | 0| 0|
HOP-EXCEED | 0| |BAD-GW | 0| |
------------------------------------------------------------------------

25.4.3. DHCP debug

The following commands allows to purge INVALID bindings which may appear upon networks configuration changes.

[20:57:46] ABILIS_CPX:_debug res:dhcp

RES:Dhcp ----------------------------------------------------------------------
Dynamic_Host_Configuration_Protocol
BufferLength:454 Date/Time:04/03/2011 20:57:50 TraceTime:47980

Usage:
LSN:0 - This help
LSN:1 - Complete debug
LSN:2 - Statistics
LSN:3 - DHCP log
LSN:3 CMD:CLR - Clear DHCP log
LSN:4 - Incoming datagrams dump
LSN:4 CMD:CLR - Clear incoming datagrams dump
LSN:5 - Restore host table
LSN:6 CMD:<MAC> - Delete INV (invalid) bindings with specified MAC
LSN:6 CMD:ALL - Delete ALL INV (invalid) bindings

25.5. DHCPC resource (DHCP Client)

The DHCPC resource can retrieve the ip address when abilis is used as dhcp client.

25.5.1. Activating DHCPC resource

Add the resource to the Abilis system; the DHCP resource may already exist in the system, but may not yet be active: set it
active with the command s act res:dhcp.

[09:47:27] ABILIS_CPX:a res:dhcpc

COMMAND EXECUTED

Caution
After adding or setting the DHCPC active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

401
Draft DHCP - Dynamic Host Draft
Configuration Protocol

[09:48:58] ABILIS_CPX:s p dhcpc act:yes

COMMAND EXECUTED

RES:DhcpC - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:Dynamic_Host_Configuration_Protocol_Client
LOG:DS ACT:YES msg-len:1472
cli-udp-locport:68 srv-udp-remport:67 TOS:0-N
DHCP-SERVER:* DHCP-SERVER-LIST:#

25.5.2. DHCPC resource parameters

The default parameters suffice to make the resource to work properly.

The most important parameters are:

[10:45:42] ABILIS_CPX:_d p dhcpc

RES:DhcpC ---------------------------------------------------------------------
Run DESCR:Dynamic_Host_Configuration_Protocol_Client
LOG:DS ACT:YES msg-len:1472
cli-udp-locport:68 srv-udp-remport:67 TOS:0-N
DHCP-SERVER:* DHCP-SERVER-LIST:#

[10:51:42] ABILIS_CPX:_d p dhcpc ?

DhcpC resource parameter(s):

DESCR: Resource description [Max. 80 aphanumeric extended characters]

LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E]
(D: Debug Log; S: System Log; A: Alarm view; L: Local audible alarm;
T: SNMP traps; +E: Extended Log of state changes, see ref. manual)
ACT: Operation activation [NO, YES]
msg-len: Maximum length of DHCP message, actually the UDP payload
[548..2048]
cli-udp-locport: Client UDP port [68] <Read Only>
srv-udp-remport: DHCP Server UDP port [67] <Read Only>
TOS: Type Of Service octet or Differentiated Services Field (DS):
-' p-t', i.e. PRECEDENCE and TOS values, where 'p' can be [0..7]
and 't' can be [N=None, D=Min. Delay, T=Max. Throughput, R=Max.
Reliability, C=Min. Monetary Cost]
- 'bbbbbb', i.e. DS value bit by bit, where 'b' can be [0, 1]
DHCP-SERVER: DHCP Server IP address [*, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]
DHCP-SERVER-LIST: Name of an IP/IR/RU/MR list of DHCP Server IP addresses
[#, 0..9, a..z, A..Z, _]

Refer to Section 52.15.3, “How to activate the DHCP in client mode” to view a further example of configuration.

402
Draft DHCP - Dynamic Host Draft
Configuration Protocol

25.5.3. Example of configuration

Configure the DHCPC and IP-2 resources so that Abilis retrieves the ip address from the ADSL router. The first step is to
activate the DHCPC resource and then optionally configure the DHCP-SERVER parameter:

[16:43:03] ABILIS_CPX:_s p dhcpc dhcp-server:192.168.1.254

COMMAND EXECUTED

[16:43:33] ABILIS_CPX:_d p dhcpc

RES:DhcpC - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:Dynamic_Host_Configuration_Protocol_Client
LOG:DS ACT:YES msg-len:1472
cli-udp-locport:68 srv-udp-remport:67 TOS:0-N
DHCP-SERVER:192.168.001.254 DHCP-SERVER-LIST:#

Now IP-2 resource must be configured to use DHCP. Display diagnostics for IP-2 resource helps to view the retrieved ip
address:

[16:48:46] ABILIS_CPX:_s p ip-2 ipadd:dhcp

COMMAND EXECUTED

[16:48:58] ABILIS_CPX:_d p ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:YES
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO

403
Draft DHCP - Dynamic Host Draft
Configuration Protocol

dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5

pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[16:49:04] ABILIS_CPX:_d d ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

WAN
STATE:UP LINK-STATE:LINKREADY
CUR-IPADD:192.168.001.100 CUR-MASK:255.255.255.000
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:N/A OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Lan ------------------------------------------------------------------
STATE:LINKREADY ARP-CACHE-ITEMS:1

There are three other parameters which can be used to fit the configuration to needs:

DHCP-GW Retrieve default gateway through DHCP [NO, YES]. Default value is YES.

DHCP-GW-AD Administrative distance assigned to the default route obtained from a DHCP server [0..255]. Default value
is 0.

DHCP-DNS Retrieve primary and secondary DNS server through DHCP [NO, YES]. Default value is YES.

For example, configure IP-2 resource in the following way to retrieve only ip address and default gateway:

[17:05:54] ABILIS_CPX:_s p ip-2 dhcp-gw:yes dhcp-dns:no

COMMAND EXECUTED

[17:07:53] ABILIS_CPX:_init res:ip-2

COMMAND EXECUTED

[17:08:15] ABILIS_CPX:_d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:NO
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[17:08:18] ABILIS_CPX:_d ipr

Destination routes and conditional source routes:

404
Draft DHCP - Dynamic Host Draft
Configuration Protocol

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|C| | | 192.168.030.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.000.000.000/29 | 255.255.255.248 | | 12| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 11| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 2| 0|
|*|S| | | 192.168.008.000/24 | 255.255.255.000 | |D 10| 1|
|*|C| | | 192.168.030.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 000.000.000.000/0 | 000.000.000.000 | 192.168.001.254 | 2| 0|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

In some cases it's useful to retrieve only ip address:

[17:11:15] ABILIS_CPX:_s p ip-2 dhcp-gw:no

COMMAND EXECUTED

[17:20:18] ABILIS_CPX:_init res:ip-2

COMMAND EXECUTED

[17:20:29] ABILIS_CPX:_d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over LAN (LAN) ----------------------------------------------------
Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:NO DHCP-GW-AD:0 DHCP-DNS:NO
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

[17:20:33] ABILIS_CPX:_d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| |*| 127.000.000.001/32 | 255.255.255.255 | |LOOP| 0|
|*|C| | | 192.168.030.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 010.000.000.000/29 | 255.255.255.248 | | 12| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 11| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 2| 0|

405
Draft DHCP - Dynamic Host Draft
Configuration Protocol

|*|S| | | 192.168.008.000/24 | 255.255.255.000 | |D 10| 1|

|*|C| | | 192.168.030.000/24 | 255.255.255.000 | | 1| 0|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

[17:20:57] ABILIS_CPX:_d d ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

WAN
STATE:UP LINK-STATE:LINKREADY
CUR-IPADD:192.168.001.100 CUR-MASK:255.255.255.000
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:N/A OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Lan ------------------------------------------------------------------
STATE:LINKREADY ARP-CACHE-ITEMS:1

Tip
Interesting chapters:

Section 52.15, “How to activate the DHCP resource”;

Section 19.3, “IP Resources”.

406
Draft Draft

Chapter 26. DNS - Domain Name

System
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
26.1. DNS Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.1. Activating the DNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
26.1.2. DNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
26.2. DNS Resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3. DNS Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
26.3.1. Appendix - How DNS relay works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4. DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.1. DNS Resource as Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
26.4.2. DNS Server Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
26.4.3. DNS Resolver Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
26.5. DNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
26.5.1. DNS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
26.5.2. DNS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

26.1. DNS Resource

The Abilis CPX DNS1 resource may behave as a DNS Resolver, as a DNS Relay or as a DNS Server too.

26.1.1. Activating the DNS resource

Add the resource to the Abilis system with the following command.

[12:18:28] ABILIS_CPX:a res:dns

RES:DNS ALREADY EXISTS

The DNS resource may already exist in the system, but may not yet be active: set it active with the command:

[12:18:31] ABILIS_CPX:s act res:dns

COMMAND EXECUTED

Caution
After adding or setting the DNS active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p dns act:yes

COMMAND EXECUTED

1
http://en.wikipedia.org/wiki/Dns

407
Draft DNS - Domain Name System Draft

[17:15:17] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:# SECONDARY:#
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:NO relay-size:500 RELAY-TOUT:10
SERVER:NO
IPSRC:* IPSRCLIST:#

26.1.2. DNS resource parameters

Use the following command to display the parameters of the resource; the command d p dns ? displays the meaning of all
parameters.

[12:18:35] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:# SECONDARY:#
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:NO relay-size:500 RELAY-TOUT:10
SERVER:NO
IPSRC:* IPSRCLIST:#

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime DNS activation/deactivation.

SRCADD Sets the IP address to be set in every outgoing DNS request.

TOS Sets the TOS value for DNS service;

SERVERS Servers IP resource [AUTO, Ip-nnn, STATIC], where 'nnn' is an IP resource index [1..250]. [AUTO: DNS
resolver uses the servers retrieved by an IP resources that negotiates them e.g. IP-PPP. DNS: parameter of
IP resources must be set to RETRIEVE, Ip-nnn: DSN resolver uses the available servers through Ip-nnn
resource, STATIC: DNS resolver uses PRIMARY and SECONDARY servers].

PRIMARY Sets the IP address of the primary DNS server, which the Abilis CPX resource refers to for name resolution.

SECONDARY Sets the IP address of the secondary DNS server, which the Abilis CPX port refers to for name resolution.

DELAY Sets the maximum time (in seconds) to wait for a response from the DNS server.

RTY Sets how many times a request has to be sent to the DNS server if the DNS Resolver doesn't get any
response in the expected time interval fixed in the DELAY parameter.

CACHE Activates/deactivates the DNS cache.

cache-size Sets the maximum size of the cache (expressed in bytes).

408
Draft DNS - Domain Name System Draft

RELAY Activates/deactivates the DNS Relay feature for DNS resource. DNS relay allows the relay of external DNS
requests of DNS clients from CPX to DNS server.

relay-size Sets the maximum size of the relay table (expressed in bytes).

RELAY-TOUT Sets the time of life (in seconds) for a record in DNS relay table.

SERVER Activates/deactivates the DNS Server feature for DNS resource.

IPSRC Selects the IP address of the client from which the requests will be accepted.

IPSRCLIST Sets the list of DNS Client systems enabled to use the DNS Relay or Server services.

The following command allows the administrator to change the configuration of the resource:

s p dns parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:dns;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

26.2. DNS Resolver

The DNS Resolver resolves queries incoming directly from Abilis.

The example below shows how to configure the DNS Resouce as Resolver.

[16:37:46] ABILIS_CPX:s p dns act:yes primary:62.94.0.1 secondary:62.94.0.2

COMMAND EXECUTED

[16:39:44] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:062.094.000.001 SECONDARY:062.094.000.002
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:NO relay-size:500 RELAY-TOUT:10
SERVER:NO
IPSRC:* IPSRCLIST:#

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:dns.; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

In the example above, CACHING is enabled (CACHE:YES): responses are stored in cache a period which depends on the size
of the cache (cache-size parameter).

26.3. DNS Relay

When Abilis acts as DNS resolver, it seems a DNS server to other IP stations while it simply forwards the requests to real
DNS servers. Their responses are forwarded back to the original requesters.

409
Draft DNS - Domain Name System Draft

Tip
Refer to chapter Section 26.3.1, “Appendix - How DNS relay works” to know more information about DNS
realy functioning.

The example below shows how to configure the DNS Resouce as Relay.

[17:12:51] ABILIS_CPX:s p dns act:yes relay:yes

COMMAND EXECUTED

[17:13:12] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:062.094.000.001 SECONDARY:062.094.000.002
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:YES relay-size:500 RELAY-TOUT:10
SERVER:NO
IPSRC:* IPSRCLIST:#

Filters on the IP addresses allowed to the DNS service can be applied by combining the parameters IPSRC and
IPSRCLIST.

In the following example, the “DN_Allowed” list will be created and the range of IP from 192.168.1.10 to 192.168.1.50 will
be added; otherwise, the address 192.168.1.100 will be set as the IP address Source.

[17:46:50] ABILIS_CPX:list create DNS_Allowed ir IP_Addresses_allowed_to_DNS_service

COMMAND EXECUTED

[17:48:04] ABILIS_CPX:a list:dns_allowed 192.168.1.10:192.168.1.50

COMMAND EXECUTED

[17:48:19] ABILIS_CPX:d list:dns_allowed

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:DNS_Allowed - IR
IP_Addresses_allowed_to_DNS_service
192.168.001.010:192.168.001.050

[17:49:20] ABILIS_CPX:s p dns ipsrc:192.168.1.100 ipsrclist:dns_allowed

COMMAND EXECUTED

[17:49:23] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO

410
Draft DNS - Domain Name System Draft

PRIMARY:062.094.000.001 SECONDARY:062.094.000.002
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:YES relay-size:500 RELAY-TOUT:10
SERVER:NO
IPSRC:192.168.001.100 IPSRCLIST:DNS_Allowed

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:dns.; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

26.3.1. Appendix - How DNS relay works

The Abilis CPX DNS Resolver first requests the primary DNS Server.

• if it doesn't get any response, it forwards the same query to both primary and secondary server after 500 milliseconds;

• if no response is received, another request is sent to both servers after 1 second;

• in case of no answer, the same procedure is repeated after 1 second and after 2 seconds;

• if the DNS Resolver doesn't get any answer within 4 seconds, it terminates the procedure.

This procedure is repeated for a number of times equal to the value set in the RTY parameter. The delay (in seconds) between
two subsequent queries can be set with the DELAY parameter.

26.4. DNS Server

26.4.1. DNS Resource as Server
To configure the DNS Resouce as a Server type the following command:

[11:56:50] ABILIS_CPX:s p dns act:yes server:yes

COMMAND EXECUTED

[11:57:20] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:# SECONDARY:#
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:NO relay-size:500 RELAY-TOUT:10
SERVER:YES
IPSRC:* IPSRCLIST:#

Filters on the IP addresses allowed to the DNS service can be applied by combining the parameters IPSRC and
IPSRCLIST.

In the following example, the “DNS_Allowed” list will be created and the range of IP from 192.168.1.10 to 192.168.1.50 will
be added; otherwise, the address 192.168.1.100 will be set as the IP address Source.

[17:46:50] ABILIS_CPX:list create DNS_Allowed ir IP_Addresses_allowed_to_DNS_service

COMMAND EXECUTED

411
Draft DNS - Domain Name System Draft

[17:48:04] ABILIS_CPX:a list:dns_allowed 192.168.1.10:192.168.1.50

COMMAND EXECUTED

[17:48:19] ABILIS_CPX:d list:dns_allowed

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:DNS_Allowed - IR
IP_Addresses_allowed_to_DNS_service
192.168.001.010:192.168.001.050

[17:49:20] ABILIS_CPX:s p dns ipsrc:192.168.1.100 ipsrclist:dns_allowed

COMMAND EXECUTED

[17:49:23] ABILIS_CPX:d p dns

RES:Dns - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
Run DESCR:Domain_Name_System
LOG:NO ACT:YES
udp-locport:53 SRCADD:OUT-IP TOS:0-N
- Resolver -------------------------------------------------------------
SERVERS:AUTO
PRIMARY:# SECONDARY:#
DELAY:5 RTY:1
CACHE:YES cache-size:500
- Relay/Server ---------------------------------------------------------
RELAY:NO relay-size:500 RELAY-TOUT:10
SERVER:YES
IPSRC:192.168.001.100 IPSRCLIST:DNS_Allowed

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:dns.; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

26.4.2. DNS Server Table

DNS server table can store up to 300 definitions (association between IP address and name). The table can be displayed with
the following command. The d dns ? command displays the meaning of parameters.

[17:08:16] ABILIS_CPX:d dns server

Total records:0 Direct Lookup:0 Reverse Lookup:0 D&R Lookup:0

-------------------------------------------------------------------------------
ID: DIR: NAME: IP: TTL:
-------------------------------------------------------------------------------
*** NO DNS SERVER ENTRIES DEFINED ***

Meaning of the fields:

ID DNS table entry identifier

DIR Usage of the record [D (direct): domain names are translated into IP addresses; R (reverse): it is allowed the inverse
lookup of the DNS record; DR (direct and reverse): the two features are allowed].

NAME domain name.

IP IP address.

412
Draft DNS - Domain Name System Draft

TTL The Time To Live sets the duration storage into a DNS cache system before it's considered expired.

The previous DNS records Table can be managed with these commands:

• d dns : displays all Local DNS server table entries;

• d dns filter:val [filter:val] : displays any Local DNS server table entry matching the specified filter(s);

• a dns id:val name:<name> ip:<ip> [par:val] : adds a Local DNS server table entry;

• c dns id:val : clears a Local DNS server table entry;

• s dns id:val [par:val] : sets parameters of a Local DNS server table entry.

Example: assign to the IP addresses 192.168.1.20 and 192.168.1.30 the domain names john.lan and frank.lan; the first entry
will be set as direct, while the second as “both” (direct+reverse).

[17:10:12] ABILIS_CPX:a dns server id:1 dir:d name:john.lan ip:192.168.1.20

COMMAND EXECUTED

[17:10:21] ABILIS_CPX:a dns server id:2 dir:dr name:frank.lan ip:192.168.1.30

COMMAND EXECUTED

[17:10:46] ABILIS_CPX:d dns server

- Not Saved (SAVE CONF) -------------------------------------------------------

Total records:2 Direct Lookup:1 Reverse Lookup:0 D&R Lookup:1

- Direct Lookup records: ------------------------------------------------------

ID: DIR: NAME: IP: TTL:
-------------------------------------------------------------------------------
1 D john.lan 192.168.001.020 3600
2 DR frank.lan 192.168.001.030 3600

- Reverse Lookup records: -----------------------------------------------------

ID: DIR: NAME: IP: TTL:
-------------------------------------------------------------------------------
2 DR frank.lan 192.168.001.030 3600

Caution
Changes made in the DNS Server Table don't require initialization commands.

Set the PC DNS address to point to the IP address of the CPX. Now ping from a PC one of the domain names configured in
the DNS server table; the result will be:

C:\Documents and Settings\Administrator>ping frank.lan

Esecuzione di Ping frank.lan [192.168.0.30] con 32 byte di dati:

Risposta da 192.168.0.30: byte=32 durata<10ms TTL=128

Risposta da 192.168.0.30: byte=32 durata<10ms TTL=128
Risposta da 192.168.0.30: byte=32 durata<10ms TTL=128
Risposta da 192.168.0.30: byte=32 durata<10ms TTL=128

Statistiche Ping per 192.168.0.30:

Pacchetti: Trasmessi = 4, Ricevuti = 4, Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 0ms, Massimo = 0ms, Medio = 0ms

26.4.3. DNS Resolver Table

The DNS resolver give the chance to choose two different set of DNS:

413
Draft DNS - Domain Name System Draft

• one for domain lookup (translation from host name to ip address);

• one for reverse lookup (translation from ip address to host name).

Each set is composed from a primary and a secondary DNS server.

Use the following command to add a primary dns server (ip address 1.1.1.1) and a secondary dns server (ip address 2.2.2.2)
for the domain mydomain.test. The DNS resource uses these servers to resolve <any>.mydomain.test.

[19:32:57] ABILIS_CPX:a dns resolver domain id:1 name:mydomain.test pri:1.1.1.1 sec:2.2.2.2

COMMAND EXECUTED

[19:33:08] ABILIS_CPX:d dns resolver domain

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: NAME: PRI: SEC:
-------------------------------------------------------------------------------
1 mydomain.test 001.001.001.001 002.002.002.002

[19:33:34] ABILIS_CPX:_save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

Type the command s dns resolver domain id:1 [parameterN:valueN] to modify an existing entry.

[10:09:54] ABILIS_CPX:_s dns resolver domain id:1 pri:3.3.3.3

COMMAND EXECUTED

[10:12:57] ABILIS_CPX:_d dns resolver domain

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: NAME: PRI: SEC:
-------------------------------------------------------------------------------
1 mydomain.test 003.003.003.003 002.002.002.002

[10:12:58] ABILIS_CPX:_save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

Use the following command to clear the entry identified by id:N.

[10:19:52] ABILIS_CPX:_c dns resolver domain id:1

COMMAND EXECUTED

[10:20:02] ABILIS_CPX:_d dns resolver domain

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: NAME: PRI: SEC:
-------------------------------------------------------------------------------
*** NO DNS RESOLVER DOMAIN ENTRIES DEFINED ***

Use the following command to add a primary dns server (ip address 192.168.0.1) and a secondary dns server (ip address
192.168.0.2) for the ip network 10.10.10.0/24. The DNS resource uses these servers to do a reverse lookup for the net
10.10.10.0/24.

414
Draft DNS - Domain Name System Draft

[19:36:11] ABILIS_CPX:a dns resolver reverse id:1 net:10.10.10.0/24 pri:192.168.0.1 sec:192.168.0.2

COMMAND EXECUTED

[19:36:43] ABILIS_CPX:d dns resolver reverse

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: NET: PRI: SEC:
-------------------------------------------------------------------------------
1 010.010.010.000/24 192.168.000.001 192.168.000.002

[19:37:04] ABILIS_CPX:_save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

Displaying,modifying or clearing an entry can be done using the same command explained above, replacing domain with
reverse:

Table 26.1. Managing DNS resolver table

d dns resolver reverse to display the reverse dns resolver parameters

s dns resolver reverse pri:192.168.0.5 to set the ip address of primary dns server equal to
192.168.0.5
c dns resolver reverse id:1 to clear the entry identified by id equal to 1

26.5. DNS diagnostics and statistics

26.5.1. DNS diagnostics
The following commands are used to display the diagnostics of the DNS resource :

d d dns / d de dns It informs about the state of the resource, the state of the CACHE, the RELAY and the
SERVER mode, the number of records currently occupied with pending requests (for
CACHE,RELAY and SERVER), the maximum number of simultaneously pending
records ever reached (for CACHE, RELAY and SERVER) and the maximum number
of simultaneously pending requests (for CACHE, RELAY and SERVER).

[17:49:20] ABILIS_CPX:d d dns

RES:Dns -----------------------------------------------------------------------
Domain_Name_System
STATE:READY
-----------|-- STATE --|--- CUR ---|-- PEAK ---|--- MAX ---|
CACHE |READY | 11| 32| 500|
RELAY |READY | 16| 16| 500|
SERVER |READY | | | |
------------------------------------------------------------

26.5.2. DNS statistics

To display the statistics of the DNS resource the following commands are used:

d s dns / d se dns Statistics are divided between Resolver and Relay mode and between Primary
(PRI-) and Secondary (SEC-) DNS server. For Resolver mode are shown statistics
such as the number of queries, resolved hostname, unknown hostname, etc... For Relay
mode are shown statistics such as the number of total and succesfull clients' requests,
the number of clients' requests discarded because the table was full or the source IP
was not allowed, etc..

415
Draft DNS - Domain Name System Draft

[11:42:10] ABILIS_CPX:d s dns

RES:Dns -----------------------------------------------------------------------
Domain_Name_System
--- Cleared 0 days 18:35:33 ago, on 27/12/2007 at 20:51:58 -------------
- Resolver -------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PRI-QUERIES| | 0|SEC-QUERIES| | 0|
PRI-RES | 0| |SEC-RES | 0| |
PRI-UNK | 0| |SEC-UNK | 0| |
PRI-RTY-OVR| 0| |SEC-RTY_OVR| 0| |
PRI-TOUT | 0| |SEC-TOUT | 0| |
PRI-ERRORS | 0| |SEC-ERRORS | 0| |
------------------------------------------------------------------------
- Relay ----------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
REQ-TOTAL | 175| |PRI-REQ-RSP| 162| 163|
REQ-SUCC | 174| |SEC-REQ-RSP| 1| 1|
REQ-BAD | 0| |PRI-NOMATCH| 1| |
OVERFLOW | 0| |SEC-NOMATCH| 0| |
DROP-ACCESS| 0| |RSP-BAD | 0| |
------------------------------------------------------------------------

416
Draft Draft

Chapter 27. DDNS - Dynamic DNS

Luigi Demuro

Table of Contents
27.1. Dynamic DNS (DDNS) resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.1. Activating the DDNS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
27.1.2. DDNS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
27.1.3. DDNS diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

27.1. Dynamic DNS (DDNS) resource

DYNAMIC DNS allows to find Abilis with its dynamic address, using a fixed name.

27.1.1. Activating the DDNS resource

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

[10:34:45] ABILIS_CPX:_a res:ddns

COMMAND EXECUTED

[10:34:50] ABILIS_CPX:_save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Tcp Changed "SESNUM" from 103 to 104
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

On a working Abilis, a system restart (warm start) is required to make the DDNS resource running.

Then activate the resource:

[10:45:08] ABILIS_CPX:_s p ddns act:yes

COMMAND EXECUTED

[10:45:32] ABILIS_CPX:_d p ddns

RES:DDns - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Dynamic_DNS_Protocol_Client
LOG:NO ACT:YES sesnum:1 TOS:0-N
SERVICE:dyndns.org
SERVER:AUTO (members.dyndns.org)
PORT:80 RETRY-DELAY:60 UPDATE-PERIOD:AUTO
USER: PWD:

[10:45:41] ABILIS_CPX:_init res:ddns

COMMAND EXECUTED

[10:46:48] ABILIS_CPX:_save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

417
Draft DDNS - Dynamic DNS Draft

SAVE EXECUTED

27.1.2. DDNS resource parameters

Use the following command to view the resource parameters, the command d p ddns ? displays the meaning of all
parameters.

[15:03:23] ABILIS_CPX:_d p ddns

RES:DDns ----------------------------------------------------------------------
Run DESCR:Dynamic_DNS_Protocol_Client
LOG:NO ACT:YES sesnum:1 TOS:0-N
SERVICE:dyndns.org
SERVER:AUTO (members.dyndns.org)
PORT:80 RETRY-DELAY:60 UPDATE-PERIOD:AUTO
USER:abilistest PWD:********

• DESCR: Resource description [Max. 80 aphanumeric extended characters]

• LOG: State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log; A: Alarm
view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes, see ref. manual)

• ACT: Operation activation [NO, YES]

• sesnum: Maximum number of client sessions [1..255]

• TOS: Type Of Service octet or Differentiated Services Field (DS): -' p-t', i.e. PRECEDENCE and TOS values, where 'p'
can be [0..7] and 't' can be [N=None, D=Min. Delay, T=Max. Throughput, R=Max. Reliability, C=Min. Monetary Cost] -
'bbbbbb', i.e. DS value bit by bit, where 'b' can be [0, 1]

• SERVICE: DDNS service name [dyndns.com, dyndns.org, dyndns.it, no-ip.com, zoneedit.com, dtdns.com, minidns.net]

• SERVER: DDNS server FQDN. “AUTO” or from 0 up to 64 characters in the range ['0'..'9', 'a'..'z', '-', '.']. Case is not
preserved. When “AUTO”, the service's server is used.

• PORT: Remote TCP port of the server [0..65535]

• RETRY-DELAY: Delay between subsequent TCP reconnections [30..3600 sec.]. NOTE: There is no limit to the
reconenction attempt.

• UPDATE-PERIOD: Update period of dynamic DNS records on the server [AUTO, 1..60 days]. When AUTO the
provider's default rules are obeyed.

• USER: User identification on the server. From 0 up to 32 ASCII characters. Case is preserved. Spaces are allowed. Strings
holding spaces must be written between quotation marks (E.g.: “/aaa bbb/”)

• PWD: User password on the server. From 0 up to 32 ASCII characters. Case is preserved. Spaces are allowed. Strings
holding spaces must be written between quotation marks (E.g.: “/aaa bbb/”)

27.1.2.1. Example

418
Draft DDNS - Dynamic DNS Draft

Add the DDNS resource and configure it choosing the service name and inserting name and password of an active dyndns
account.

Tip
Please refer to chapter Section 52.10.1, “How to setup DDNS service using dyndns.org” to learn how to
create an account on dyndns.org.

[18:32:46] ABILIS_CPX:_s p ddns service:dyndns.org user:abilistest pwd:abilistest

COMMAND EXECUTED

[18:32:54] ABILIS_CPX:_d p ddns

RES:DDns ----------------------------------------------------------------------
Run DESCR:Dynamic_DNS_Protocol_Client
LOG:NO ACT:YES sesnum:1 TOS:0-N
SERVICE:dyndns.org
SERVER:AUTO (members.dyndns.org)
PORT:80 RETRY-DELAY:60 UPDATE-PERIOD:AUTO
USER:abilistest PWD:********

Configure the ip resource, so type the following commands:

[17:38:10] ABILIS_CPX:s p ip-24 ddns:yes ddns-fqdn:abilistest.dyndns.org

COMMAND EXECUTED

[17:38:42] ABILIS_CPX:d p ip-24

RES:Ip-24 - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

- IP over PPP (PPP) ----------------------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Adsl-1
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------
DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RFC2364-VCMUX RADIUS:NO
VPI:8 VCI:35
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO
maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:provider_user
PASSWORD:******** LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE
REPEAT:0
RES:Adsl-1 --------------------------------------------------------------------
Run DESCR:adsl-operatorA
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:3 usb-tx-bufsize:3200

On a working Abilis, an initialization of DDNS and ip-24 resources is required (init res:ddns and init res:ip-24). Remeber
to save the configurations (save conf)

419
Draft DDNS - Dynamic DNS Draft

27.1.3. DDNS diagnostics and statistics

27.1.3.1. DDNS diagnostics
The following commands are used to display the diagnostics of the DDNS resource:

d d ddns / d de ddns It informs about the state of the resource, the ip address of the resource, the account used on
dyndns.org and the state of the authentication.

[15:25:58] ABILIS_CPX:_d d ddns

RES:DDns ----------------------------------------------------------------------
Dynamic_DNS_Protocol_Client
STATE:ACTIVE SESNUM:1 CLIENTS:3
SERVER:members.dyndns.org
PORT:80 CUR-QUERIES:0 PEAK-QUERIES:1
------------------------------------------------------------------------
RES STATE IP UPDATE-TIME
FQDN
SERVER-RESPONSE
------------------------------------------------------------------------
Ip-2 REGISTERED 192.168.001.100 03/11/2010 15:25:58
abilistest.dyndns.org
good 192.168.1.100
------------------------------------------------------------------------

27.1.3.2. DDNS statistics

To display the statistics of the DNS resource the following commands are used:

d s ddns / d se ddns Statistics show many information like: tcp protocol errors, the number of requests, the
number of successful/wrong request, etc.

[15:30:30] ABILIS_CPX:_d s ddns

RES:DDns ----------------------------------------------------------------------
Dynamic_DNS_Protocol_Client
--- Cleared 0 days 01:14:07 ago, on 03/11/2010 at 14:16:25 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHAR | 284| 560|REQUESTS | | 2|
DNS-ERRS | 0| |SUCCESS | 1| |
TCP-ERRS | 0| |ERRORS | 1| |
DDNS-ERRS | 1| |
------------------------------------------------------------------------

420
Draft Draft

Chapter 28. SMTP - Simple Mail

Transfer Protocol
Luigi Demuro

Table of Contents
28.1. SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.1. Activating the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.1.2. SMTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
28.2. Example of configuration of the SMTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
28.3. SMTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
28.3.1. SMTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
28.3.2. SMTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

28.1. SMTP resource

SMTP resource allows to use Abilis as local relay or with external SMTP relay server. Mail for the local domain are sent
through local relay, mail to an external domain are sent through the configured external server.

SMTP can be used with CTISMS resource in order to send/receive sms via email (if an UMTS-BOX is installed).

Tip
Refer to chapter Section 53.19, “How to configure CTISMS to send sms via emails” to have more
information about sending sms using emails.

28.1.1. Activating the SMTP resource

Add the resource to the Abilis system with the following command:

[15:50:39] ABILIS_CPX:a res:smtp

RES:SMTP ALREADY EXISTS

The SMTP resource may already exist in the system, but may not yet be active: set it active with the command:

[15:50:43] ABILIS_CPX:s act res:smtp

COMMAND EXECUTED

Caution
After adding or setting the SNMP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[09:31:37] ABILIS_CPX:s p smtp act:yes

COMMAND EXECUTED

28.1.2. SMTP resource parameters

Use the following command to display the parameters of the resource; the d p smtp ? command shows the meaning of
parameters.

[09:58:41] ABILIS_CPX:d p smtp

421
Draft SMTP - Simple Mail Transfer Protocol Draft

RES:Smtp ----------------------------------------------------------------------
Run DESCR:Simple_Mail_Transfer_Protocol
LOG:NO ACT:YES tcp-locport:25 internal-mails:10
SRCADD:192.168.000.001 TOS:0-N
ses-tot:10 SES-RESERVED-IN:2 SES-RESERVED-OUT:2
DT:120 MAX-IP-SES:2 MAX-RCPT:100
IPSRC:127.000.000.001 IPSRCLIST:SmtpRelay
LOCAL-DOMAIN:sms.lan
HELOHOST:noname
wdir:C:\APP\MAIL\
max-fail-notif:50 MB-MAXSIZE:5000
MSG-MAXSIZE:65535 MB-MAXMAILS:1000 STORE-MB:NO
-- Local SMTP relay ----------------------------------------------------
RELAY-NET:192.168.000.000/24 RELAY-IPSRCLIST:#
RELAY-AUTH:DISABLED
QUEUE-LIFE-TIME:86400 MAIL-TRY-DELAY:300
-- External SMTP server for relay --------------------------------------
SERVER:mail.xx.it SERVER-AUTH:NO
SERVER-USER:
SERVER-PWD:
-- SMS Gateway ---------------------------------------------------------
SMS-GW:YES SMS-PERMIT:RELAY
SMS-IP:# SMS-SENDER:#

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime SNMP activation/deactivation.

tcp-locport Local TCP port on which SMTP service is listening [1..65535].

internal-mails Number of simultaneous internal mails that can be sent [1..255].

SRCADD Source IP address for outgoing requests [R-ID, OUT-IP, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x].

TOS Used to enstablish the frame priority. First field [default: 0] Second field specify the type of the
frame [N=None, D=Min. Delay, T=Max. Throughput, R=Max. Reliability, C=Min. Monetary
Cost].

Refer to Type of Service to have more information.

ses-tot Total number of sessions [1..255].

SES-RESERVED-IN Number of sessions reserved for incoming mails only [0..255].

SES-RESERVED- Number of sessions reserved for outgoing mails only [0..255].

OUT

DT Inactivity disconnection time-out [30..65535 sec.].

MAX-IP-SES Maximum number of simultanous incoming sessions from the same IP address [1..255].

MAX-RCPT Maximum number of recipients for single message [1..65535].

IPSRC Incoming requests: accepted source IP address [*, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x].

if net: 0.0.0.0 All IPs are allowed

In the case that one needs to restrict the access, he has to set in IPSRC the ip address of a client
which must always have access, e.g. the IP address of the administrator console, and add further
IPs using IPSRCLIST.

IPSRCLIST Incoming requests: name of the IP/IR/RU/MR list for source IP address acceptance [#, 0..9, a..z,
A..Z, _].

If IPSRCLIST:0 List is not used

422
Draft SMTP - Simple Mail Transfer Protocol Draft

If IPSRCLIST: name_list The parameter contains list identifier

LOCAL-DOMAIN Local domain for local mailboxes. From 0 up to 64 characters in the range ['0'..'9', 'a'..'z', '-', '.'].
Case is not preserved.

HELOHOST Name used by the Abilis SMTP server when executing the HELO/EHLO command while sending
an email. "noname" or from 1 up to 64 characters in the range ['0'..'9', 'a'..'z', '-', '.']. Case is
preserved.

wdir Working directory where the messages are stored. It cannot be empty. Physical full path in DOS
notation, i.e. starting with a drive letter in the range ['A'..'Z'] and ending with the '\' character. Max.
128 characters. Case is preserved. Spaces are allowed. Strings holding spaces must be written
between quotation marks (E.g.: "C:\My dir\").

max-fail-notif Maximum dimension of the mail failure notification, in the range [1 - 100] Kbytes.

MSG-MAXSIZE Maximum dimension of a single mail, in Kbytes [100 - 65535].

MB-MAXSIZE Maximum size of users mailboxes, in Kbytes [100..250000, NOMAX].

MB-MAXMAILS Maximum number of mails for a single mailbox [10 - 1000].

STORE-MB Allow server to store message for local mailboxes [NO, YES].

Local SMTP relay section:

RELAY-NET IP network allowed for mail relay. "#" or network address and mask in Slash Notation [x.x.x.x/yy],
[1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]/[0..32].

RELAY-IPSRCLIST Name of an IP/IR/RU/MR list containing additional IP addresses allowed for SMTP relay [#, 0..9,
a..z, A..Z, _].

RELAY-AUTH Allowed SMTP authentication types [DISABLED, LOGIN, DIGEST].

QUEUE-LIFE-TIME Amount of seconds before a deferred mail causes a mail failure notification. Range [300 - 1048576]
seconds.

MAIL-TRY-DELAY Amount of time between a mail sending try and another one, in the range [60 - 65535] seconds.

External SMTP server for relay section:

SERVER FQDN name of SMTP Relay server to which all the mails for not local domain are forwarded. From 0 up to 64
characters in the range ['0'..'9', 'a'..'z', '-', '.']. Case is not preserved.

SERVER- Authentication type to use logging in relay server [NO, LOGIN, DIGEST].
AUTH
This option set if authentication is allowed and what authentication types are allowed.

SERVER- Username of the account on the relay server. Up to 60 ASCII characters. Spaces are not allowed. Case is
USER preserved.

SERVER- Password of the account on the relay server. Up to 60 ASCII characters. Spaces are not allowed. Case is
PWD preserved.

SMS Gateway section:

SMS- Enable/disable SMS services [NO, YES].

GW

SMS- Permitted method [NONE, RELAY, IP, SENDER]. Values can be joined using ',' character.
PERMIT

SMS-IP Name of an IP/IR/RU/MR list of allowed IP addresses or "#" or "*".

SMS- Name of a TXT/RU/MR list of allowed senders or "#" or "*".

SENDER

The command that allows the configuration of the resource to be modified has the following syntax:

423
Draft SMTP - Simple Mail Transfer Protocol Draft

s p smtp par:val...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:smtp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

28.2. Example of configuration of the SMTP resource

The example below shows how to configure the SNMP resource and to relay emails using an external SMTP server:

[10:21:28] ABILIS_CPX:s p smtp local-domain:test.lan relay-net:192.168.0.0/24 server:209.85.229.109

server-user:user server-pwd:password server-auth:digest

COMMAND EXECUTED

[10:25:52] ABILIS_CPX:d p smtp

RES:Smtp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Simple_Mail_Transfer_Protocol
LOG:NO ACT:YES tcp-locport:25 internal-mails:10
SRCADD:OUT-IP TOS:0-N
ses-tot:10 SES-RESERVED-IN:2 SES-RESERVED-OUT:2
DT:120 MAX-IP-SES:2 MAX-RCPT:100
IPSRC:* IPSRCLIST:#
LOCAL-DOMAIN:test.lan
HELOHOST:noname
wdir:C:\APP\MAIL\
max-fail-notif:50 MB-MAXSIZE:5000
MSG-MAXSIZE:2000 MB-MAXMAILS:1000 STORE-MB:NO
-- Local SMTP relay ----------------------------------------------------
RELAY-NET:192.168.000.000/24 RELAY-IPSRCLIST:#
RELAY-AUTH:DISABLED
QUEUE-LIFE-TIME:86400 MAIL-TRY-DELAY:300
-- External SMTP server for relay --------------------------------------
SERVER:209.85.229.109 SERVER-AUTH:DIGEST
SERVER-USER:user
SERVER-PWD:***
-- SMS Gateway ---------------------------------------------------------
SMS-GW:NO SMS-PERMIT:RELAY
SMS-IP:# SMS-SENDER:#

This configuration allows the 192.168.0.0/24 net to use Abilis as smtp relay for both local domain (test.lan) and non-local
domains (through server 209.85.229.109). Use your account username and password to use the external smtp server.

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:smtp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

Note
The value of SERVER parameter can be the FQDN of external SMTP server configuring the DNS resource
or it's ip address.

Tip
Interesting chapter: Section 53.19, “How to configure CTISMS to send sms via emails”.

424
Draft SMTP - Simple Mail Transfer Protocol Draft

28.3. SMTP diagnostics and statistics

28.3.1. SMTP diagnostics
The following commands are used to display the diagnostics of the SMTP resource:

d d smtp Shows the state of the resource.

d de smtp Shows the state of the resource, and information about smtp sessions.

[10:25:56] ABILIS_CPX:d d smtp

RES:Smtp ----------------------------------------------------------------------
Simple_Mail_Transfer_Protocol
STATE:ACTIVE CUR-SES:10 ACTIVE-IN:0 ACTIVE-OUT:0
MIX-IN:0 MIX-OUT:0 QUEUE-OUT:0 QUEUE-DEFER:0
------------------------------------------------------------------------

[10:31:49] ABILIS_CPX:d de smtp

RES:Smtp ----------------------------------------------------------------------
Simple_Mail_Transfer_Protocol
STATE:ACTIVE CUR-SES:10 ACTIVE-IN:0 ACTIVE-OUT:0
MIX-IN:0 MIX-OUT:0 QUEUE-OUT:0 QUEUE-DEFER:0
- Smtp Sessions --------------------------------------------------------
CH TYPE TCP-State LocAdd-LocPort RemAdd-RemPort SMTP-State
------------------------------------------------------------------------
0 OUT READY READY
1 OUT READY READY
2 IN LISTEN 000.000.000.000-25 READY
3 IN LISTEN 000.000.000.000-25 READY
4 IN LISTEN 000.000.000.000-25 READY
5 IN LISTEN 000.000.000.000-25 READY
6 IN LISTEN 000.000.000.000-25 READY
7 IN LISTEN 000.000.000.000-25 READY
8 IN LISTEN 000.000.000.000-25 READY
9 IN LISTEN 000.000.000.000-25 READY

28.3.2. SMTP statistics

The following commands are used to display the statistics of the SMTP resource:

d s smtp Shows the statistics of the SMTP resource, such as the number of successful incoming TCP connections
(CALL-SUCC in), the number of successful outgoing TCP connections (CALL-SUCC out), the number
of unsuccessful incoming TCP connections (CALL-FAIL in), the number of unsuccessful outgoing TCP
connections (CALL-FAIL out), the number of accepted external mails (EXT-SUCC),etc..

d se smtp Shows the statistics of the SMTP resource for each session.

[10:31:53] ABILIS_CPX:d s smtp

RES:Smtp ----------------------------------------------------------------------
Simple_Mail_Transfer_Protocol
--- Cleared 0 days 01:29:23 ago, on 04/02/2011 at 09:09:27 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 7| 2|CALL-FAIL | 0| 0|
EXT-SUCC | 5| 0|EXT-FAIL | 2| 1|
NOTIFY | | 5|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 1|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 5| 0|RELAY-FAIL | 0| 2|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|

425
Draft SMTP - Simple Mail Transfer Protocol Draft

------------------------------------------------------------------------

[10:38:50] ABILIS_CPX:d se smtp

RES:Smtp ----------------------------------------------------------------------
Simple_Mail_Transfer_Protocol
--- Cleared 0 days 01:29:30 ago, on 04/02/2011 at 09:09:27 -------------
- Smtp Sessions --------------------------------------------------------
CH TYPE TCP-State LocAdd-LocPort RemAdd-RemPort SMTP-State
------------------------------------------------------------------------
0 OUT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 0| 1|CALL-FAIL | 0| 0|
EXT-SUCC | 0| 0|EXT-FAIL | 0| 1|
NOTIFY | | 5|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 0| 0|RELAY-FAIL | 0| 1|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
1 OUT READY READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 0| 1|CALL-FAIL | 0| 0|
EXT-SUCC | 0| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 1|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 0| 0|RELAY-FAIL | 0| 1|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
2 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 0| 0|EXT-FAIL | 1| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 0| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
3 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 1| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 1| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
4 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 1| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 1| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
5 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|

426
Draft SMTP - Simple Mail Transfer Protocol Draft

CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 1| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 1| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
6 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 0| 0|EXT-FAIL | 1| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 0| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
7 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 1| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 1| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
8 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 1| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 1| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 1| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------
9 IN LISTEN 000.000.000.000-25 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL-SUCC | 0| 0|CALL-FAIL | 0| 0|
EXT-SUCC | 0| 0|EXT-FAIL | 0| 0|
NOTIFY | | 0|NOTIFY-LT | | 0|
NOTIFY-SUCC| | 0|NOTIFY-FAIL| | 0|
LOCAL-SUCC | 0| 0|LOCAL-FAIL | 0| 0|
RELAY-SUCC | 0| 0|RELAY-FAIL | 0| 0|
INT-SUCC | 0| 0|INT-FAIL | 0| 0|
------------------------------------------------------------------------

427
Draft Draft

Chapter 29. SNTP - Simple Network

Time Protocol
Nicola Trevisani
Luigi Demuro

Table of Contents
29.1. SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.1. Activating the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
29.1.2. SNTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
29.2. Examples of SNTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.1. SNTP client configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.2.2. SNTP server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
29.3. SNTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.1. SNTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
29.3.2. SNTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

29.1. SNTP resource

The Abilis CPX SNTP1 resource can work as:

SNTP client It loads time data from a remote SNTP server and sets the Abilis internal clock accordingly.

SNTP server It provides time data to other SNTP clients.

Figure 29.1. SNTP resource as both SNTP client and server

If the Client process is not active the server process operates as a primary reference source of synchronization; if the client
process is active the server process operates as a secondary reference source of synchronization.

29.1.1. Activating the SNTP resource

Add the resource to the Abilis system with the following command:

1
http://en.wikipedia.org/wiki/SNTP

428
Draft SNTP - Simple Network Time Protocol Draft

[09:58:31] ABILIS_CPX:a res:sntp

RES:SNTP ALREADY EXISTS

The SNTP resource may already exist in the system, but may not yet be active: set it active with the command:

[09:58:35] ABILIS_CPX:s act res:sntp

COMMAND EXECUTED

Caution
After adding or setting the SNTP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

29.1.2. SNTP resource parameters

The following command displays the parameters of the resource; the d p sntp ? command shows the meaning of parameters.

[09:58:41] ABILIS_CPX:d p sntp

RES:Sntp ----------------------------------------------------------------------
Run DESCR:Simple_Network_Time_Protocol
LOG:NO
- Client ---------------------------------------------------------------
CLIACT:YES udp-remport:123
HOST-1:# HOST-2:#
HOST-3:# HOST-4:#
SRCADD:R-ID (192.168.000.201)
POLLP:60 NRTY:3 TBW:30 TBD:30
- Server ---------------------------------------------------------------
SERVACT:NO udp-locport:123
IPSRC:* IPSRCLIST:#

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

CLIACT Activates/deactivates the SNTP Client.

HOST-x Sets the IP address of the SNTP Server host number x to which the Client process of the Abilis will send its
synchronization requests.

SRCADD Sets the IP address for outgoing Client synchronization requests.

POLLP Sets the time interval (in minutes) after which to start the synchronization procedure of the SNTP Client of
Abilis.

NRTY Sets the maximum number of repetitions for each synchronization attempt.

TBW Sets the time interval (in seconds) after which the request sent by the SNTP Client of the Abilis will be
considered failed, if no answer from the SNTP Server is received.

TBD Sets the time interval (in seconds) between a failed synchronization request and its successive one.

SERVACT Activates/deactivates the SNTP Server functionality;

udpport UDP port that is used by the SNTP port (Read Only parameter).

IPSRC Sets the IP address of the SNTP Client enabled to query the Server process of Abilis.

IPSRCLIST Sets the list of SNTP Client systems enabled to query the Server process of Abilis.

The command which allows the configuration of the resource to be modified has the following syntax:

s p sntp par:val...

429
Draft SNTP - Simple Network Time Protocol Draft

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:sntp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

29.2. Examples of SNTP configuration

29.2.1. SNTP client configuration
Configure the SNTP resource to take the synchronization form the NTP host 129.132.2.21.

[11:05:38] ABILIS_CPX:s p sntp cliact:yes host-1:129.132.2.21 pollp:1440

COMMAND EXECUTED

[11:06:17] ABILIS_CPX:d p sntp

RES:Sntp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Simple_Network_Time_Protocol
LOG:NO
- Client ---------------------------------------------------------------
CLIACT:YES udp-remport:123
HOST-1:129.132.002.021 HOST-2:#
HOST-3:# HOST-4:#
SRCADD:R-ID (192.168.000.201)
POLLP:1440 NRTY:3 TBW:30 TBD:30
- Server ---------------------------------------------------------------
SERVACT:NO udp-locport:123
IPSRC:* IPSRCLIST:#

With this configuration, Abilis will send a synchronization request every 1440 minutes (POLLP parameter) to the host
129.132.2.21.

Tip
Interesting chapter: Section 52.20.1, “How to activate the SNTP client”.

29.2.2. SNTP server configuration

Configure the SNTP resource to act as Server. Only the IP addresses of the LAN 192.168.1.0/24 will be enabled to the
service (list: sntp_allowed).

[11:42:10] ABILIS_CPX:s p sntp servact:yes ipsrc:192.168.0.100 ipsrclist:sntp_allowed

COMMAND EXECUTED

[11:42:18] ABILIS_CPX:d p sntp

RES:Sntp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Simple_Network_Time_Protocol
LOG:NO
- Client ---------------------------------------------------------------
CLIACT:YES
HOST-1:129.132.002.021 HOST-2:#
HOST-3:# HOST-4:#
SRCADD:R-ID (192.168.001.001)
POLLP:1440 NRTY:3 TBW:30 TBD:30
- Server ---------------------------------------------------------------

430
Draft SNTP - Simple Network Time Protocol Draft

SERVACT:YES udpport:123
IPSRC:192.168.000.100 IPSRCLIST:SNTP_Allowed

With this configuration, Abilis works as Server and Client simultaneously.

Tip
Interesting chapter: Section 52.20.2, “How to activate the SNTP server”.

29.3. SNTP diagnostics and statistics

29.3.1. SNTP diagnostics
The following commands are used to display the diagnostics of the SNTP resource:

d d sntp / d de sntp It shows the status of the client and server, the IP address of the SNTP server and the
date and time of the last synchronization.

[11:42:10] ABILIS_CPX:d d sntp

RES:Sntp ----------------------------------------------------------------------
Simple_Network_Time_Protocol
Local Clock Synchronized: External Clock Reference 129.132.002.021
Clock last synchronized on 29/12/2007 at 18:40:58 Delta:1 sec.
Server-STATE:INACTIVE
Client-STATE:READY

29.3.2. SNTP statistics

The following command are used to display the statistics of the SNTP resource:

d s sntp / d se sntp It shows the statistic information, such as the number of packets sent/received by the
SNTP Server/Client, the number of invalid packets received by the SNTP Server/
Client, the number of packets received by the SNTP Server from a disabled SNTP
Client, the number of packets received with a IP address not valid, the number of
successful synchronizations or number of failed synchronizations.

[11:42:10] ABILIS_CPX:d s sntp

RES:Sntp ----------------------------------------------------------------------
Simple_Network_Time_Protocol
--- Cleared 0 days 05:05:19 ago, on 29/12/2007 at 13:39:56 -------------
Server:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SER-PCK | 0| 0|SER-BADPCK | 0| |
SER-BADSRC | 0| |
------------------------------------------------------------------------
Client:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-PCK | 6| 7|CLI-BADPCK | 0| |
CLI-BADSRC | 0| |CLI-TOUT | 1| |
SUCC-SYNC | 6| |FAIL-SYNC | 0| |
------------------------------------------------------------------------

431
Draft Draft

Chapter 30. ALARM resource

Luigi Demuro

Table of Contents
30.1. ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.1. Activating the ALARM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.2. ALARM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
30.1.3. The ALARM table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
30.1.4. ALARM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

30.1. ALARM resource

This resource manages alarms inside Abilis CPX. It permits to send SNMP traps notifications through emails to the
configured recipients. Configuring the smtp and snmp resources is needed to send emails.

30.1.1. Activating the ALARM resource

Add the resource to the Abilis system with the following command.

[17:32:07] ABILIS_CPX:a res:alarm

COMMAND EXECUTED

The ALARM resource may already exist in the system, but may not yet be active: set it active with the following command.

[17:34:00] ABILIS_CPX:s act res:alarm

COMMAND EXECUTED

Caution
You must save the configuration and restart the Abilis to make the resource running (use the command
warm start to reboot the Abilis) after adding or setting the ALARM active.

[17:35:45] ABILIS_CPX:s p alarm act:yes

COMMAND EXECUTED

[17:35:51] ABILIS_CPX:d p alarm

RES:Alarm - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:Alarms_manager
LOG:NO ACT:YES fifo-size:100
MAIL-ENABLE:YES
MAIL-FROM:SYS

Caution
Execute the initialization command init res:alarm to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

30.1.2. ALARM resource parameters

Use the command below to display the parameters of the resource; the d p alarm ? command shows the meaning of
parameters.

432
Draft ALARM resource Draft

[17:42:10] ABILIS_CPX:d p alarm

RES:Alarm ---------------------------------------------------------------------
Run DESCR:Alarms_manager
LOG:NO ACT:YES fifo-size:100
MAIL-ENABLE:YES
MAIL-FROM:SYS

Meaning of the parameters:

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log; A: Alarm
view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes).

ACT Operation activation [NO, YES].

fifo-size Notifications fifo size [10..500].

MAIL-ENABLE Enable/disable e-mail sending [NO, YES].

MAIL-FROM Sender of e-mail. From 0 up to 128 ASCII printable characters. Spaces are not allowed. Case is preserved.
[SYS: the sender is the one configured in the MAIL-FROM parameter fo CTISYS resource]

The following command allows the administrator to change the configuration of the resource:

s p alarm parameter:value...

Caution
Execute the initialization command init res:alarm to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

30.1.3. The ALARM table

The alarm table contains the rules to monitor Abilis resources. The table can store up to 10 rules ordered by the ID parameter.

30.1.3.1. Displaying the ALARM Table (D ALARM)

This command shows the alarm table. If ID is omitted, the command shows all routings.

[16:45:15] ABILIS_CPX:_d alarm

-------------------------------------------------------------------------------
ID: |ENABLED:|MONITOR:|RES: |ACTION:
|MAIL-RCPT:
|MAIL-RCPT-LIST:
-------------------------------------------------------------------------------
0 YES TRAP * MAIL
[email protected]
#
-------------------------------------------------------------------------------

Meaning of parameters:

ID Identifier of Alarms management rule [0..9] <Mandatory>.

ENABLED Enable/disable this entry usage [NO, YES]. Default is NO.

MONITOR Alarm/event to be monitored [NONE, TRAP]. Default is NONE.

RES Resource for which the alarm/event is monitored or name. Default is #.

ACTION Action to be executed when the monitored alarm/event occurs [NONE, MAIL]. Default is NONE.

MAIL-RCPT Default e-mail recipient(s). From 0 up to 128 ASCII printable characters. Spaces are not allowed.
Case is preserved. (Only for ACTION:MAIL). Default is <empty>.

433
Draft ALARM resource Draft

MAIL_RCPT-LIST TXT list of e-mail recipients [#, ListName] (Only for ACTION:MAIL). Default is <empty>.

30.1.3.2. Adding an ALARM (A ALARM)

This command adds a new alarm to the table with ID:xx, setting the indicated parameters to the specified values. Unspecified
parameters are set to default values.The table can store up to 10 rules, so the ID parameter must be in the range [0...9].

[18:06:34] ABILIS_CPX:a alarm id:0 enabled:yes monitor:trap res:* action:mail mail-rcpt:alarms@mydo

COMMAND EXECUTED

[18:09:03] ABILIS_CPX:d alarm id:0

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: |ENABLED:|MONITOR:|RES: |ACTION:
|MAIL-RCPT:
|MAIL-RCPT-LIST:
-------------------------------------------------------------------------------
0 YES TRAP * MAIL
[email protected]
#
-------------------------------------------------------------------------------

Warning
Changes made on the ALARM table are immediately active. Remeber to save the configuration (save conf).

30.1.3.3. Deleting an ALARM (C ALARM)

It clears the alarm with the specified ID.

[18:33:33] ABILIS_CPX:d alarm

-------------------------------------------------------------------------------
ID: |ENABLED:|MONITOR:|RES: |ACTION:
|MAIL-RCPT:
|MAIL-RCPT-LIST:
-------------------------------------------------------------------------------
0 YES TRAP * MAIL
[email protected]
#
-------------------------------------------------------------------------------

[18:33:36] ABILIS_CPX:c alarm id:0

COMMAND EXECUTED

[18:34:00] ABILIS_CPX:d alarm

ALARM TABLE IS EMPTY

Warning
Changes made on the ALARM table are immediately active. Remeber to save the configuration (save conf).

30.1.3.4. Modifying the ALARM Table (S ALARM)

This command sets the parameters of the rule identified by “ID:xx” to their new values. The syntax of the command is: s
alarm id:xxx [par:value].

[18:38:54] ABILIS_CPX:d alarm

434
Draft ALARM resource Draft

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: |ENABLED:|MONITOR:|RES: |ACTION:
|MAIL-RCPT:
|MAIL-RCPT-LIST:
-------------------------------------------------------------------------------
2 NO TRAP * MAIL
[email protected]
#
-------------------------------------------------------------------------------

[18:38:58] ABILIS_CPX:s alarm id:2 enabled:yes

COMMAND EXECUTED

[18:41:42] ABILIS_CPX:d alarm

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: |ENABLED:|MONITOR:|RES: |ACTION:
|MAIL-RCPT:
|MAIL-RCPT-LIST:
-------------------------------------------------------------------------------
2 YES TRAP * MAIL
[email protected]
#
-------------------------------------------------------------------------------

Warning
Changes made on the ALARM table are immediately active. Remeber to save the configuration (save conf).

30.1.4. ALARM diagnostic and statistics

30.1.4.1. ALARM diagnostic
The following command is used to display the diagnostics of the ALARM resource:

d d alarm it shows the state of the resource (STATE), the state of the email sending (MAIL-ENABLED), the number
of notifications inside the FIFO (CUR-FIFO), the maximum number of notifications inside the FIFO (PEAK-
FIFO), the maximum number of notifications which can be managed by the FIFO (MAX-FIFO).

[12:13:10] ABILIS_CPX:d d alarm

RES:Alarm ---------------------------------------------------------------------
Alarms_manager
STATE:ACTIVE MAIL-ENABLED:YES
CUR-FIFO:0 PEAK-FIFO:1 MAX-FIFO:100

30.1.4.2. ALARM statistics

The following commands are used to display the statistics of the ALARM resource:

d s alarm it shows the statistics of the ALARM resource like: the number of received notifications (ALARM), the
number of notifications successfully inserted in the FIFO (ALARM-SUCC), the number of notifications
not inserted in the FIFO because the it's full (ALARM-OVR), the number of notifications not inserted in
the FIFO for any other reason, the number of trap notifications extracted from FIFO (TRAP), the number
of notifications successfully managed (TRAP-SUCC), the number of discarded notifications because they
don't match any rule (TRAP-DISC), the number of sent mails (MAIL), the number of successfully sent mails
(MAIL-SUCC), the number of mails (MAIL-FAIL) whose sendig is failed.

[12:14:52] ABILIS_CPX:d s alarm

435
Draft ALARM resource Draft

RES:Alarm ---------------------------------------------------------------------
Alarms_manager
--- Cleared 0 days 00:39:03 ago, on 05/05/2011 at 11:36:38 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
ALARM | 1| 1|ALARM-OVR | 0| |
ALARM-SUCC | 1| 1|ALARM-FAIL | 0| 0|
TRAP | 1| |MAIL | | 1|
TRAP-SUCC | 1| |MAIL-SUCC | | 1|
TRAP-DISC | 0| |MAIL-FAIL | | 0|
------------------------------------------------------------------------

436
Draft Draft

Chapter 31. UPNP - Universal Plug

and Play
Luigi Demuro

Table of Contents
31.1. UPNPS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.2. UPNPS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
31.3. UPNPS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
31.4. How to configure UPNP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

31.1. UPNPS resource

Abilis has the UPNPS1 resource, which can be a UPNP server and client.

31.2. UPNPS configuration

Add the resource to the Abilis system with the following command.

[11:09:16] ABILIS_CPX:a res:upnps

RES:UPNP ALREADY EXISTS

The UPNPS resource may already exist in the system, but may not yet be active: set it active with the command:

[11:09:21] ABILIS_CPX:s act res:upnps

COMMAND EXECUTED

On a working Abilis, a system restart is needed to make the resource running.

Use the below command to display the parameters of the resource:

[14:53:51] ABILIS_CPX:d p upnps

RES:UPnPS --------------------------------------------------------------------
Run Run DESCR:Universal_Plug_and_Play_Server
LOG:NO ACT:NO sesnum:5 udp-locport:1900 tcp-locport:1900
MAX-AGE:1800 TOS:0-N
IPSRC:* IPSRCLIST:#
WDIR:C:\APP\UPNP\

[14:58:56] ABILIS_CPX:_s p upnps act:yes

COMMAND EXECUTED

[14:59:00] ABILIS_CPX:_init res:upnps

COMMAND EXECUTED

[14:59:18] ABILIS_CPX:_d p upnps

1
http://en.wikipedia.org/wiki/Universal_Plug_and_Play

437
Draft UPNP - Universal Plug and Play Draft

RES:UPnPS ---------------------------------------------------------------------
Run DESCR:Universal_Plug_and_Play_Server
LOG:NO ACT:YES sesnum:5 udp-locport:1900 tcp-locport:1900
MAX-AGE:1800 TOS:0-N
IPSRC:* IPSRCLIST:#
WDIR:C:\APP\UPNP\

Below are descriptions of the most important parameters:

LOG activates the logging and the generation of the alarms [NO, D (=Debug Log), S (=System Log), A (=Alarm
view), L (=Local audible alarm), T (=SNMP traps), ALL] [+E (=Extended Log of state changes)].

ACT enables/disables the resource [NO, YES].

sesnum Number of sessions that the UPNP server module can support.

udp-locport Local UDP port of UPNP server. Default value = 1900.

tcp-locport Local TCP port of UPNP server. Default value = 1900.

MAX-AGE Number of seconds the server' advertisement is valid.

IPSRCLIST Incoming requests: name of the IP/IR/RU/MR list for source IP address acceptance.

IPRSC Incoming requests: accepted source IP address.

The following command allows the administrator to change the configuration of the resource:

s p upnps name:value...

31.3. UPNPS diagnostic and statistics

The following commands is used to display the diagnostic of the UPNPS resource:

[18:06:40] ABILIS_CPX:d d upnps

RES:UPnPS ---------------------------------------------------------------------
Universal_Plug_and_Play_Server
STATE:ACTIVE SESNUM:5
CUR-REQUESTS:0 PEAK-REQUESTS:2
- HTTP Channels --------------------------------------------------------
CH TCP-State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
0 LISTENING 000.000.000.000-0
1 LISTENING 000.000.000.000-0
2 LISTENING 000.000.000.000-0
3 LISTENING 000.000.000.000-0
4 LISTENING 000.000.000.000-0

Use the below command to view UPNPS statistics:

[18:06:40] ABILIS_CPX:d s upnps

RES:UPnPS ---------------------------------------------------------------------
Universal_Plug_and_Play_Server
--- Cleared 0 days 00:51:14 ago, on 13/12/2010 at 14:14:04 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SSDP-CHR | 3468| 10893|SSDP-FRM | 29| 39|
SSDP-LOST | 0| |SSDP-BADFMT| 0| |
SOAP-REQ | 17| |SOAP-RSP | | 14|
SOAP-ERR | 3| |TCP-CHR | 15900| 77380|
------------------------------------------------------------------------

438
Draft UPNP - Universal Plug and Play Draft

31.4. How to configure UPNP server

Assuming to have the above network, configure Abilis so that it can be used as a UPNP server only by the pc inside lan (to
avoid security issues).

The first step is to add and activate the UPNPS resource, then type the following commands:

[15:23:32] ABILIS_CPX:_s p upnps ipsrc:192.168.30.2

COMMAND EXECUTED

[15:25:31] ABILIS_CPX:_d p upnps

RES:UPnPS - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:Universal_Plug_and_Play_Server
LOG:NO ACT:YES sesnum:5 udp-locport:1900 tcp-locport:1900
MAX-AGE:1800 TOS:0-N
IPSRC:192.168.030.002 IPSRCLIST:#
WDIR:C:\APP\UPNP\

[15:25:34] ABILIS_CPX:_init res:upnps

COMMAND EXECUTED

This is the result using GUPnP Universal Control Point on Ubuntu:

439
Draft UPNP - Universal Plug and Play Draft

440
Draft Draft

Chapter 32. FTP - File Transfer

Protocol
Marco Bellesia
Luigi Demuro

Table of Contents
32.1. FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.1. Activating the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
32.1.2. FTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
32.2. FTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
32.2.2. FTP Virtual Root Paths table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.2.3. FTP Virtual Paths Access Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
32.3. FTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.1. FTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.3.2. FTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
32.4. Example of FTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.1. Configuring the FTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
32.4.2. Activating the user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.3. Creating the virtual path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
32.4.4. Giving access rights to user “ftpuser” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
32.4.5. Connecting to Abilis FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
32.4.6. Access to the system version directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450

32.1. FTP resource

Abilis FTP1 server supports both active and passive mode and FTP over SSL operations.

Virtual directories are used to limit the access to real file system.

File naming convention from client's point of view is UNIX-like:

• the path delimiter is "/";

• file names start with "/" without volume specification (such as A: in DOS-like notation).

Each user has configurable rights for each path.

32.1.1. Activating the FTP resource

Add the resource to the Abilis system with the following command:

[16:35:45] ABILIS_CPX:a res:ftp

RES:FTP ALREADY EXISTS

The FTP resource may already exist in the system, but may not yet be active: set it active with the command:

[16:35:50] ABILIS_CPX:s act res:ftp

1
http://en.wikipedia.org/wiki/Ftp

441
Draft FTP - File Transfer Protocol Draft

COMMAND EXECUTED

Caution
After adding or setting the FTP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p ftp act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p ftp

RES:Ftp - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

Run DESCR:File_Transfer_Protocol_Server
LOG:NO ACT:YES max-cli:4
tcp-locport-c:21 tcp-locport-d:20 TOS:0-N
IPSRC:* IPSRCLIST:#
DATA-TOUT:30 DT:300 REJ-1024:YES SAME-IP:YES SYSDRIVES:NO
MAX-PWD-FAIL:4 DELAY-PWD-FAIL:5
MAX-IP-SES:NOMAX MAX-USER-SES:2
ANONYMOUS-USER:DENY REGISTERED-USER:PERMIT
ANONYMOUS-HOMEDIR:

32.1.2. FTP resource parameters

Use the below command to display the parameters of the resource; the d p ftp ? command shows the meaning of all
parameters.

[12:18:35] ABILIS_CPX:d p ftp

Run DESCR:File_Transfer_Protocol_Server
LOG:NO ACT:YES max-cli:4
tcp-locport-c:21 tcp-locport-d:20 TOS:0-N
IPSRC:* IPSRCLIST:#
DATA-TOUT:30 DT:300 REJ-1024:YES SAME-IP:YES SYSDRIVES:NO
MAX-PWD-FAIL:4 DELAY-PWD-FAIL:5
MAX-IP-SES:NOMAX MAX-USER-SES:2
ANONYMOUS-USER:DENY REGISTERED-USER:PERMIT
ANONYMOUS-HOMEDIR:

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime FTP activation/deactivation.

max-cli Maximum number of simultaneous client connections (every client needs 2 FTP connections).

IPSRC Client IP address allowed to connect to FTP server.

IPSRCLIST List of additional client IP addresses allowed to connect to FTP server

DATA-TOUT Data transmit/receive time-out.

DT Inactivity time-out.

REJ-1024 Enables/disables data connections to client's ports lower then 1024 (only for active mode).

SAME-IP Allows to restrict data connection to the same IP of the control connection (for both active and
passive mode).

SYSDRIVES Allows to create a /sysdrives/ virtual path from which it is possible to access to all system
drives and their subdirectories.

442
Draft FTP - File Transfer Protocol Draft

MAX-PWD-FAIL Maximum number of password attempts.

DELAY-PWD-FAIL Delay after failed PASS command.

MAX-IP-SES Limits number of simultaneous CONTROL connections that can be established from a client's IP
address.

MAX-USER-SES Limits number of simultaneous CONTROL connections that an user can establish from the
SAME IP with the SAME USER login.

ANONYMOUS-USER Allows anonymous log-in.

REGISTERED-USER Allows registered users log-in.

ANONYMOUS-HOMEDIR Anonymous home directory, initiating and terminated by the '/' (slash) character.

The following command allows the administrator to change the configuration of the resource:

s p ftp parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:ftp;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

32.2. FTP tables

The access to FTP resources is based on:

• authentication of the user in the Users table;

• creation of a virtual path in the FTP Virtual Roots Path table;

• creation of a access rights for that virtual Path in the FTP Virtual Paths Access Rights table.

32.2.1. Users table

Users can access to FTP server only if they are enabled to FTP service (parameter FTP set tot YES).

[17:13:00] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
ftpuser *** YES # # NO YES NO NO NO NO
guest NO # # NO NO NO NO NO NO

Type the command d user:<user> to show the detailed user configuration parameters.

[17:13:05] ABILIS_CPX:d user:ftpuser

Parameter: | Value:
------------------+------------------------------------------------------------
USER: ftpuser
ALIAS: ftpuser
ID: 10 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *

443
Draft FTP - File Transfer Protocol Draft

OPC-MONITOR: NONE
FTP: YES
FTP-HOMEDIR:
FTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

Meaning of the parameters:

FTP Enables/disables the FTP service.

FTP-HOMEDIR FTP user's home directory.

FTP-PROT User's access protocol [PLAIN: not encrypted; SSL: encrypted].

32.2.2. FTP Virtual Root Paths table

FTP Virtual Paths Table specifies the association between virtual paths and their respective physical paths.

Virtual paths can be added/set/displayed/cleared with the commands:

a/s/d/c ftp path:<virtual path> [phys-path:<physical path>]

The whole table can be shown with the follwoing command. By default the table contains the following entries:

[17:16:13] ABILIS_CPX:d ftp path

Parameter: | Value:
------------+------------------------------------------------------------------
PATH: /pub/
PHYS-PATH: C:\USR\PUB\
-------------------------------------------------------------------------------
PATH: /pub2/
PHYS-PATH: D:\USR\PUB\
-------------------------------------------------------------------------------
PATH: /usr/
PHYS-PATH: C:\USR\
-------------------------------------------------------------------------------
PATH: /usr2/
PHYS-PATH: D:\USR\
-------------------------------------------------------------------------------

To show a specific path:

[17:25:52] ABILIS_CPX:d ftp path:/pub/

Parameter: | Value:
------------+------------------------------------------------------------------
PATH: /pub/
PHYS-PATH: C:\USR\PUB\
-------------------------------------------------------------------------------

Meaning of the parameters:

PATH Specifies a directory virtual path with UNIX notation. Virtual path / needs not to be specified because /
does never refer to physical path, it is only the “container” of virtual paths. The maximum length is of 32
characters.

PHYS-PATH Specifies a directory physical path, with DOS notation (it starts with the disk letter and it ends with the
character \ ). The maximum length is of 128 characters.

32.2.3. FTP Virtual Paths Access Rights table

This table specifies the associations between virtual paths, users and their respective access rights.

Access rights for a specific virtual path can be added/set/displayed/cleared with the following commands.

444
Draft FTP - File Transfer Protocol Draft

a ftp rights path:<virtual path> | adds the path only.

id:<id>

a ftp rights path:<virtual adds user and path.

path> |id:<id> [user:<user>
file:<file rights> dir:<dir rights>
recur:yes|no mode:plain,ssl]

s ftp rights path:<virtual sets rights and other parameters for an already existent user.
path> |id:<id> user:<user>
[file:<file rights> dir:<dir rights>
recur:yes|no mode:plain,ssl]

c ftp rights path:<virtual path> | deletes an existing user; if the user is the last one the path is not deleted.
id:<id> user:<user>

d ftp rights displays rights summary.

d ftp rights path:<virtual path> | displays rights for a specific path.

id:<id>

d ftp rights user:<user> displays rights that a user has on all paths; the paths for which the user is not defined
are skipped.

Example of the output (by default the table contains the following entries):

[17:53:58] ABILIS_CPX:d ftp rights

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /pub/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /pub2/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sysdrives/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /usr/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /usr2/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------

The rights are split in “file rights” and “directory rights” and are configured/viewed with two different parameters: FILE and
DIR.

Table 32.1. FILE parameters values

R W D N
Read Write Delete Rename

Table 32.2. DIR parameters values

L C D N
List Create Delete Rename

The syntax is:

445
Draft FTP - File Transfer Protocol Draft

FILE:[+|-R][+|-W][+|-D][+|-N] DIR:[+|-L][+|-C][+|-D][+|-N]

• The + sets granted right.

• The - sets denied right.
• If + or - is not specified, the value + is assumed, so it may be omitted.
• Not specified right is left unchanged.
• FILE and DIR values do not care of the characters' position.
• FILE and DIR values are case insensitive.

The following commands are equivalent:

1. S FTP RIGHTS PATH:/ USER:test FILE:+R+W+D+N

S FTP RIGHTS PATH:/ USER:test FILE:rwdn

S FTP RIGHTS PATH:/ USER:test FILE:NdwR

2. S FTP RIGHTS PATH:/ USER:test FILE:+D-N

S FTP RIGHTS PATH:/ USER:test FILE:D-N

S FTP RIGHTS PATH:/ USER:test FILE:-ND

32.3. FTP diagnostics and statistics

32.3.1. FTP diagnostics
To display the diagnostics of the FTP resource the following commands are used:

d d ftp / d de ftp Shows diagnostic information such as the state of the resource, the maximum number
of clients allowed, the number of current CONNECTED/LOGGED/DATA-SESSION
(for PLAIN o SSL mode), the maximum number of CONNECTED/LOGES/DATA-
SESSION reached from start-up (for PLAIN o SSL mode), the IP addresses and ports
of clients connected, etc..

[19:00:30] ABILIS_CPX:d d ftp

RES:Ftp -----------------------------------------------------------------------
File_Transfer_Protocol_Server
STATE:ACTIVE MAX-CLI:4
-- Clients --------|--TOT CUR---|--TOT PEAK--|--SSL CUR---|--SSL PEAK--|
CONNECTED | 1| 1| 0| 0|
LOGGED | 1| | 0| |
DATA-SESSION | 0| 1| 0| 0|
------------------------------------------------------------------------
-- Sessions states -----------------------------------------------------
SES C-STATE C-REM C-LOC USER
D-STATE D-REM D-LOC
------------------------------------------------------------------------
4 LOGGED 192.168.002.010-3110 192.168.002.002-21 anonymous
READY 000.000.000.000-0 000.000.000.000-0

32.3.2. FTP statistics

To display the statistics of the FTP resource the following commands are used:

d s ftp Shows the number of sent/received characters and packets for both data and control sessions, the number of
received valid commands on control session and the number of sent responses.

d se ftp Shows statistic information in an extended format: the same information listed for d s ftp command are shown
for each session.

[19:01:14] ABILIS_CPX:d s ftp

446
Draft FTP - File Transfer Protocol Draft

RES:Ftp -----------------------------------------------------------------------
File_Transfer_Protocol_Server
--- Cleared 000:03:02:24 ago, on 15/09/2007 at 15:59:39 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CTRL-CHR | 211| 921|CTRL-PCK | 20| 27|
DATA-CHR | 0| 366|DATA-PCK | 0| 2|
COMMAND | 20| |REPLY | | 27|
------------------------------------------------------------------------

[19:02:03] ABILIS_CPX:d se ftp

RES:Ftp -----------------------------------------------------------------------
File_Transfer_Protocol_Server
--- Cleared 000:03:02:53 ago, on 15/09/2007 at 15:59:40 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CTRL-CHR | 211| 921|CTRL-PCK | 20| 27|
DATA-CHR | 0| 366|DATA-PCK | 0| 2|
COMMAND | 20| |REPLY | | 27|
------------------------------------------------------------------------
SES C-STATE C-REM C-LOC USER
D-STATE D-REM D-LOC
------------------------------------------------------------------------
4 LOGGED 192.168.002.010-3110 192.168.002.002-21 anonymous
READY 000.000.000.000-0 000.000.000.000-0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CTRL-CHR | 74| 322|CTRL-PCK | 8| 9|
DATA-CHR | 0| 183|DATA-PCK | 0| 1|
COMMAND | 8| |REPLY | | 9|
------------------------------------------------------------------------

32.4. Example of FTP configuration

The example shows how:

• to configure the FTP resource;

• to activate the user “ftpuser”;

• to create a virtual path;

• to give access rights to “ftpuser”.

32.4.1. Configuring the FTP resource

Activating the resource suffices without configuring all listed parameters.

[16:45:57] ABILIS_CPX:s p ftp act:yes

COMMAND EXECUTED

[16:47:43] ABILIS_CPX:d p ftp

RES:Ftp - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
DESCR:File_Transfer_Protocol_Server
LOG:NO ACT:YES max-cli:4
tcp-locport-c:21 tcp-locport-d:20 TOS:0-N
IPSRC:* IPSRCLIST:#
DATA-TOUT:30 DT:300 REJ-1024:YES SAME-IP:YES SYSDRIVES:NO
MAX-PWD-FAIL:4 DELAY-PWD-FAIL:5
MAX-IP-SES:NOMAX MAX-USER-SES:2
ANONYMOUS-USER:DENY REGISTERED-USER:PERMIT
ANONYMOUS-HOMEDIR:

447
Draft FTP - File Transfer Protocol Draft

32.4.2. Activating the user “ftpuser”

Add the user “ftpuser” in the Users table:

[16:02:24] ABILIS_CPX:a user:ftpuser pwd:ftpuser ftp:yes

COMMAND EXECUTED

[16:05:08] ABILIS_CPX:s user:ftpuser ftp-homedir:/test1/

COMMAND EXECUTED

[17:29:55] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
ftpuser *** YES # # NO YES NO NO NO NO
guest NO # # NO NO NO NO NO NO

[22:32:04] ABILIS_CPX:d user:ftpuser

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: ftpuser
ALIAS: ftpuser
ID: 10 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
FTP: YES
FTP-HOMEDIR: /test1/
FTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

32.4.3. Creating the virtual path

Create the association between virtual path /test1/ and physical path c:\usr\pub\test1\ (that corresponds to
ftpuser's FTP-HOMEDIR).

[16:11:57] ABILIS_CPX:a ftp path:/test1/ phys-path:c:\usr\pub\test1\

COMMAND EXECUTED

[22:32:36] ABILIS_CPX:d ftp path

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
------------+------------------------------------------------------------------
PATH: /pub/
PHYS-PATH: C:\USR\PUB\
-------------------------------------------------------------------------------
PATH: /pub2/

448
Draft FTP - File Transfer Protocol Draft

PHYS-PATH: D:\USR\PUB\
-------------------------------------------------------------------------------
PATH: /test1/
PHYS-PATH: c:\usr\pub\test1\
-------------------------------------------------------------------------------
PATH: /usr/
PHYS-PATH: C:\USR\
-------------------------------------------------------------------------------
PATH: /usr2/
PHYS-PATH: D:\USR\
-------------------------------------------------------------------------------

Note
Supposing: test1 directory has been created by an user with administrator's rights (e.g. user admin).

Caution
Execute the initialization command init res:ftp to activate changes.

32.4.4. Giving access rights to user “ftpuser”

Give access rights to user “ftpuser” on directory c:\usr\pub\test1\.

[16:21:35] ABILIS_CPX:a ftp rights path:/test1/ user:ftpuser file:rwdn dir:lcdn recur:yes prot:plai

COMMAND EXECUTED

[22:33:27] ABILIS_CPX:d ftp rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /pub/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /pub2/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sysdrives/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /test1/
ftpuser rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /usr/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /usr2/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------

Give to ftpuser read-only rights on directory usr and its subdirectories (virtual path /usr/).

[16:29:04] ABILIS_CPX:a ftp rights path:/usr/ user:ftpuser file:r-w-d-n dir:l-c-d-n recur:yes prot:

COMMAND EXECUTED

449
Draft FTP - File Transfer Protocol Draft

[22:34:17] ABILIS_CPX:d ftp rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /pub/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /pub2/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sysdrives/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /test1/
ftpuser rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /usr/
admin rwdn lcdn YES PLAIN,SSL
ftpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /usr2/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------

32.4.5. Connecting to Abilis FTP server

An FTP client can be used to connect to Abilis FTP server.

The logged-in user accesses the directory /test1/ (c:\usr\pub\test1\) using the configured rights (create/rename/
delete new directories or files). Outside directories can only be viewed.

32.4.6. Access to the system version directories

Settting the SYSDRIVES parameter to YES is needed to access to the system version directories, e.g. C:\6-0-9\ (/
sysdrives/C/6-0-9/).

[16:45:57] ABILIS_CPX:s p ftp sysdrives:yes

COMMAND EXECUTED

[16:47:43] ABILIS_CPX:d p ftp

RES:Ftp - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
DESCR:File_Transfer_Protocol_Server
LOG:NO ACT:YES max-cli:4
tcp-locport-c:21 tcp-locport-d:20 TOS:0-N
IPSRC:* IPSRCLIST:#
DATA-TOUT:30 DT:300 REJ-1024:YES SAME-IP:YES SYSDRIVES:YES
MAX-PWD-FAIL:4 DELAY-PWD-FAIL:5
MAX-IP-SES:NOMAX MAX-USER-SES:2
ANONYMOUS-USER:DENY REGISTERED-USER:PERMIT
ANONYMOUS-HOMEDIR:

The access is enabled by default for the user “admin”; access rights to user “ftpuser” can be given with the following
command:

450
Draft FTP - File Transfer Protocol Draft

[15:19:20] ABILIS_CPX:a ftp rights path:/sysdrives/ user:ftpuser file:rwdn dir:lcdn recur:yes prot:

COMMAND EXECUTED

[15:20:01] ABILIS_CPX:d ftp rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
1 /pub/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /pub2/
admin rwdn lcdn YES PLAIN,SSL
anonymous r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sysdrives/
admin rwdn lcdn YES PLAIN,SSL
ftpuser rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /test1/
ftpuser rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /usr/
admin rwdn lcdn YES PLAIN,SSL
ftpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /usr2/
admin rwdn lcdn YES PLAIN,SSL
-------------------------------------------------------------------------------

451
Draft Draft

Chapter 33. TFTP - Trivial File

Transfer Protocol
Luigi Demuro

Table of Contents
33.1. TFTP - Trivial File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.1. Activating the TFTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
33.1.2. TFTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
33.2. TFTP diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.1. TFTP diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
33.2.2. TFTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454

33.1. TFTP - Trivial File Transfer Protocol

The TFTP1 has been introduced to bootstrap certain ip phones models.

33.1.1. Activating the TFTP resource

Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:tftp

RES:TFTP ALREADY EXISTS

The TFTP resource may already exist in the system, but may not yet be active: set it active with the following command.

[09:10:00] ABILIS_CPX:s act res:tftp

COMMAND EXECUTED

Caution
You must restart the Abilis to make the resource running (use the command warm start to reboot the
Abilis) after adding or setting the TFTP active.

[13:07:41] ABILIS_CPX:d p tftp

RES:Tftp ----------------------------------------------------------------------
Run DESCR:Trivial_File_Transfer_protocol
LOG:NO ACT:NO udp-locport:69 srv-sess:10 TOS:0-N
RTY:5 TOUT:3 WRITE-PERMISSIONS:NO
IPSRC:* IPSRCLIST:#
WDIR:C:\APP\TFTP\

Caution
Execute the initialization command init res:tftp to activate the changes made on the upper case parameters;
use save conf and warm start commands to set active the changes made on the lowercase parameters.

[10:50:25] ABILIS_CPX:s p tftp act:yes

COMMAND EXECUTED

1
http://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol

452
Draft TFTP - Trivial File Transfer Protocol Draft

[10:51:33] ABILIS_CPX:d p tftp

RES:Tftp - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Trivial_File_Transfer_protocol
LOG:NO ACT:YES udp-locport:69 srv-sess:10 TOS:0-N
RTY:5 TOUT:3 WRITE-PERMISSIONS:NO
IPSRC:* IPSRCLIST:#
WDIR:C:\APP\TFTP\

[10:51:41] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[10:51:53] ABILIS_CPX:init res:tftp

COMMAND EXECUTED

33.1.2. TFTP resource parameters

Use the command below to display the parameters of the resource; the d p tftp ? command shows the meaning of parameters.

[13:07:41] ABILIS_CPX:d p tftp

RES:Tftp ----------------------------------------------------------------------
Run DESCR:Trivial_File_Transfer_protocol
LOG:NO ACT:NO udp-locport:69 srv-sess:10 TOS:0-N
RTY:5 TOUT:3 WRITE-PERMISSIONS:NO
IPSRC:* IPSRCLIST:#
WDIR:C:\APP\TFTP\

Meaning of the most important parameters:

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log; A: Alarm
view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes).

ACT Operation activation [NO, YES].

udp-locport TFTP server local UDP port [default is 69].

srv-sess Number of TFTP server sessions [1..255].Default is 10.

TOS Type Of Service octet or Differentiated Services Field (DS): -' p-t', i.e. PRECEDENCE and TOS
values, where 'p' can be [0..7] and 't' can be [N=None, D=Min. Delay, T=Max. Throughput,
R=Max. Reliability, C=Min. Monetary Cost] - 'bbbbbb', i.e. DS value bit by bit, where 'b' can be
[0, 1]. Default is 0-N.

RTY Number of retransmissions [1..30]. Default is 5.

TOUT Time that TFTP waits for TFTP peer responses [1..15 sec.]. Default is 3.

WRITE-PERMISSIONS Specifies the write permissions [NO: write permission disabled, YES:write permission enabled,
IF-EXISTS:????]. Default is NO.

IPSRC Incoming requests: accepted source IP address [*, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x]. Default
is *.

IPSRC-LIST Incoming requests: name of the IP/IR/RU/MR list for source IP address acceptance [#, 0..9, a..z,
A..Z, _]. Default is #.

WDIR Directory where message files are located. It cannot be empty. Physical full path in DOS
notation, i.e. starting with a drive letter in the range ['A'..'Z'] and ending with the '\' character.

453
Draft TFTP - Trivial File Transfer Protocol Draft

Max. 128 characters. Case is preserved. Spaces are allowed. Strings holding spaces must be
written between quotation marks (E.g.: "C:\My dir\"). Default is C:\APP\TFTP\.

The following command allows the administrator to change the configuration of the resource:

s p tftp parameter:value...

Caution
Execute the initialization command init res:tftp to activate the changes made on the upper case parameters;
use save conf and warm start commands to set active the changes made on the lowercase parameters.

33.2. TFTP diagnostic and statistics

33.2.1. TFTP diagnostic
The following command is used to display the diagnostics of the TFTP resource:

d d tftp it shows the state of the resource (STATE), the number of current used TFTP sessions (CUR-SESS), the peak
of used TFTP sessions (PEAK-SESS), the number of maximum TFTP sessions (MAX-SESS). The command
shows also the sessions and the clients ip addresses.

[11:37:57] ABILIS_CPX:d d tftp

RES:Tftp ----------------------------------------------------------------------
Trivial_File_Transfer_protocol
STATE:ACTIVE
CUR-SESS:0 PEAK-SESS:0 MAX-SESS:10
------------------------------------------------------------------------
SES RemAdd-RemPort
------------------------------------------------------------------------
0 000.000.000.000-0
1 000.000.000.000-0
2 000.000.000.000-0
3 000.000.000.000-0
4 000.000.000.000-0
5 000.000.000.000-0
6 000.000.000.000-0
7 000.000.000.000-0
8 000.000.000.000-0
9 000.000.000.000-0

33.2.2. TFTP statistics

The following commands are used to display the statistics of the TFTP resource:

d s tftp it shows the statistics of the TFTP resource, such as the total number of incoming/outgoing characters
from UDP (CHR), the total number of incoming/outgoing packets from UDP (FRM), the total number of
lost incoming packets with too long length (LONG), the total number of lost incoming packets: buffer is
full (LOST), the total number of lost incoming packets with bad format (BAD-FMT), the total number
of lost incoming packets with source IP addreess which not allowed (BAD-SRC), the total number of
received packet with error opcode (ERRORS), the total number of timeouts (TOUT), the total number of
retransmissions (RETRANS).

d se tftp it shows the TFTP resource statitics shown by the previous command sorted by session.

[11:46:13] ABILIS_CPX:d s tftp

RES:Tftp ----------------------------------------------------------------------
Trivial_File_Transfer_protocol
--- Cleared 0 days 00:11:25 ago, on 05/05/2011 at 11:36:38 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|

454
Draft TFTP - Trivial File Transfer Protocol Draft

LONG | 0| 0|LOST | 0| 0|
BAD-FMT | 0| 0|BAD-SRC | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------

[11:48:03] ABILIS_CPX:d se tftp

RES:Tftp ----------------------------------------------------------------------
Trivial_File_Transfer_protocol
--- Cleared 0 days 00:11:30 ago, on 05/05/2011 at 11:36:38 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
LONG | 0| 0|LOST | 0| 0|
BAD-FMT | 0| 0|BAD-SRC | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:3
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:4
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:5
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:6
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:7
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|

455
Draft TFTP - Trivial File Transfer Protocol Draft

CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:8
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------
SES:9
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
ERRORS | 0| |TOUT | 0| |
RETRANS | | 0|
------------------------------------------------------------------------

456
Draft Draft

Chapter 34. HTTP - HyperText

Transfer Protocol
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
34.1. HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1.1. Activating the HTTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
34.1.2. HTTP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
34.2. HTTP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
34.2.2. HTTP Virtual Root Paths Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.2.3. HTTP Virtual Paths Access Rights Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
34.3. HTTP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.1. HTTP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.3.2. HTTP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
34.4. HTTPS (HTTP over SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
34.4.1. Activating the SSL resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
34.4.2. HTTP resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
34.4.3. Connecting to Abilis using HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
34.5. Appendix - HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

34.1. HTTP resource

Abilis HTTP1 server allows to access to the web interface. Many but not all configurations can be done using web pages.
Only the CP allows to configure each Abilis feature.

Abilis HTTP2 server supports both PLAIN and SSL operations. The securty level can be managed by:

• allowing access only to a restricted list of ip addresses;

• configuring http rights for users.

Tip
Refer to Section 34.5, “Appendix - HTTP” to have more information about HTTP.

34.1.1. Activating the HTTP resource

Add the resource to the Abilis system with the following command:

[12:25:41] ABILIS_CPX:a res:http

RES:HTTP ALREADY EXISTS

The HTTP resource may already exist in the system, but may not yet be active: set it active with the command:

[12:25:44] ABILIS_CPX:s act res:http

1
http://en.wikipedia.org/wiki/HTTP
2
http://en.wikipedia.org/wiki/HTTP

457
Draft HTTP - HyperText Transfer Protocol Draft

COMMAND EXECUTED

Caution
After adding or setting the HTTP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p http act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p http

RES:Http - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Run DESCR:HyperText_Transfer_Protocol
LOG:NO ACT:YES LOGIN-COOKIE-TOUT:1440
WDIR:C:\APP\HTTP\
START-PAGE:SYS (/sys/pub/cpx.htm)
SYS-CSS:SYS (/sys/pub/cpx.css)
- HTTP plain -----------------------------------------------------------
ACT-P:YES locport-p:80 sesnum-p:12
IPSRC-P:* IPSRCLIST-P:#
- HTTP ssl -------------------------------------------------------------
ACT-S:NO locport-s:443 sesnum-s:0
IPSRC-S:* IPSRCLIST-S:#

34.1.2. HTTP resource parameters

Use the following command to display the parameters of the resource; the d p http ? command shows the meaning of
parameters.

[17:25:33] ABILIS_CPX:d p http

RES:Http ----------------------------------------------------------------------
Run DESCR:HyperText_Transfer_Protocol
LOG:NO ACT:NO LOGIN-COOKIE-TOUT:1440
WDIR:C:\APP\HTTP\
START-PAGE:SYS (/sys/pub/cpx.htm)
SYS-CSS:SYS (/sys/pub/cpx.css)
- HTTP plain -----------------------------------------------------------
ACT-P:YES locport-p:80 sesnum-p:12
IPSRC-P:* IPSRCLIST-P:#
- HTTP ssl -------------------------------------------------------------
ACT-S:NO locport-s:443 sesnum-s:0
IPSRC-S:* IPSRCLIST-S:#

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime HTTP activation/deactivation.

LOGIN-COOKIE-TOUT Lifetime of the cookie used to store login information.

WDIR Directory where temporary files are saved.

START-PAGE Selects the HTTP start page.

SYS-CSS Selects Cascading Style Sheets for dynamic pages.

ACT-P Activates/deactivates the PLAIN protocol.

sesnum-p HTTP TCP/IP PLAIN sessions number.

IPSRC-P Client IP addresses allowed to connect to HTTP server in PLAIN mode.

458
Draft HTTP - HyperText Transfer Protocol Draft

IPSRCLIST-P Additional list of client IP addresses allowed to connect to HTTP server in PLAIN mode.

ACT-S Activates/deactivates the SSL protocol.

sesnum-s HTTP TCP/IP SSL sessions number.

IPSRC-S Client IP addresses allowed to connect to HTTP server in SSL mode.

IPSRCLIST-S Additional list of client IP addresses allowed to connect to HTTP server in PLAIN mode in SSL
mode.

The following command allows the administrator to change the configuration of the resource:

s p http parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:http; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

34.2. HTTP tables

Abilis implements an access control system based on:

• authentication of the user in the Users table;

• creation of a virtual path in the HTTP Virtual Roots Path table;

• creation of a access right for that virtual Path in the FTP Virtual Paths Access Rights table.

34.2.1. Users table

Users can access to HTTP server only if they are enabled to HTTP service (parameter HTTP set tot YES).

[16:50:04] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
httpuser YES # # NO NO YES NO NO NO

To show the detailed user configuration parameters, type the command d user:<username>.

[16:50:06] ABILIS_CPX:d user:httpuser

Parameter: | Value:
------------------+------------------------------------------------------------
USER: httpuser
ALIAS: httpuser
ID: 3 <Read Only>
PWD:
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-MONITOR: NONE
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

Tip
Interesting chapter: Section 5.9, “Users Table”.

459
Draft HTTP - HyperText Transfer Protocol Draft

Meaning of the parameters:

HTTP Enables/disables the HTTP service.

HTTP-PROT User's access protocol [PLAIN: not encrypted; SSL: encrypted].

34.2.2. HTTP Virtual Root Paths Table

HTTP Virtual Paths Table specifies the association between virtual paths and their respective physical paths.

Virtual Paths can be added/set/displayed/cleared with the commands:

a/s/d/c http path:<virtual path> [phys-path:<physical path>]

The whole table can be shown with the following command. The table is empty by default:

[15:12:11] ABILIS_CPX:d http path

Parameter: | Value:
------------+------------------------------------------------------------------
PATH: /test/
PHYS-PATH: c:\usr\pub\test\
-------------------------------------------------------------------------------
PATH: /trfafiles/
PHYS-PATH: c:\app\trfa\
-------------------------------------------------------------------------------

Type the below command to show a specific path:

[15:12:15] ABILIS_CPX:d http path:/test/

Parameter: | Value:
------------+------------------------------------------------------------------
PATH: /test/
PHYS-PATH: c:\usr\pub\test\
-------------------------------------------------------------------------------

Meaning of the parameters:

PATH Specifies a directory virtual path with UNIX notation. Virtual path / needs not to be specified because /
does never refer to physical path, it is only the “container” of virtual paths. The maximum length is of 32
characters.

PHYS-PATH Specifies a directory physical path, with DOS notation (it starts with the disk letter and it ends with the
character \ ). The maximum length is of 128 characters.

34.2.3. HTTP Virtual Paths Access Rights Table

This table specifies the associations between virtual paths, users and their respective access rights.

Access rights for a specific virtual path can be added/set/displayed/cleared with the following commands.

a http rights path:<virtual path> adds the path only.

| id:<id>

a http rights path:<virtual adds user and path.

path> | id:<id> [user:<user>
file:<file rights> dir:<dir rights>
recur:yes|no mode:plain,ssl]

s http rights path:<virtual sets rights and other parameters for an already existent user.
path> | id:<id> user:<user>
[file:<file rights> dir:<dir rights>
recur:yes|no mode:plain,ssl]

c http rights path:<virtual path> deletes an existing user; if the user is the last one the path is not deleted.
| id:<id> user:<user>

460
Draft HTTP - HyperText Transfer Protocol Draft

d http rights displays rights summary.

d http rights path:<virtual path> displays rights for a specific path.

| id:<id>

d http rights user:<user> displays rights which a user has on all paths; the paths for which the user is not defined
are skipped.

Tip
Access rights for a specific virtual path can be added/set/displayed/cleared specifying the path or the id: the
following commands are equivalent.

[12:14:07] ABILIS_CPX:_d http rights id:1

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
test2 r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

[12:14:17] ABILIS_CPX:_d http rights path:/sys/

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
test2 r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

An example of the output is shown below (by default the table contains the following entries):

[17:54:31] ABILIS_CPX:d http rights

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

The rights are split in “file rights” and “directory rights” and are configured/viewed with two different parameters: FILE and
DIR.

Table 34.1. FILE parameters values

R W D N
Read Write Delete Rename

Table 34.2. DIR parameters values

L C D N
List Create Delete Rename

461
Draft HTTP - HyperText Transfer Protocol Draft

The syntax is:

FILE:[+|-R][+|-W][+|-D][+|-N] DIR:[+|-L][+|-C][+|-D][+|-N]

• The + sets granted right.

• The - sets denied right.

• If + or - is not specified, the value + is assumed, so it may be omitted.

• Not specified right is left unchanged.

• FILE and DIR values do not care of the characters' position.

• FILE and DIR values are case insensitive.

The following commands are equivalent:

1. S HTTP RIGHTS PATH:/ USER:test FILE:+R+W+D+N

S HTTP RIGHTS PATH:/ USER:test FILE:rwdn

S HTTP RIGHTS PATH:/ USER:test FILE:NdwR

2. S HTTP RIGHTS PATH:/ USER:test FILE:+D-N

S HTTP RIGHTS PATH:/ USER:test FILE:D-N

S HTTP RIGHTS PATH:/ USER:test FILE:-ND

34.3. HTTP diagnostics and statistics

34.3.1. HTTP diagnostics
The following commands are used to display diagnostics:

d d http / d de http Shows diagnostic information such as the state of the resource, the maximum number
of connections, the IP address-ports of clients connected, etc..

[15:53:04] ABILIS_CPX:d d http

RES:Http ----------------------------------------------------------------------
HyperText_Transfer_Protocol
STATE:READY MAX-CONN:12
------------------------------------------------------------------------
CH State LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
0 LISTENING 000.000.000.000-80
1 LISTENING 000.000.000.000-80
2 LISTENING 000.000.000.000-80
3 LISTENING 000.000.000.000-80
4 CONNECTED 192.168.000.231-80 192.168.000.029-1315
5 LISTENING 000.000.000.000-80
6 LISTENING 000.000.000.000-80
7 LISTENING 000.000.000.000-80
8 LISTENING 000.000.000.000-80
9 LISTENING 000.000.000.000-80
10 LISTENING 000.000.000.000-80
11 LISTENING 000.000.000.000-80

34.3.2. HTTP statistics

The following commands are used to display statistics:

d s http Shows the number of sent/received characters, the number of received request from the resource and the
number of received GET, POST or PUT request from the resource.

462
Draft HTTP - HyperText Transfer Protocol Draft

d se http Shows statistic information in an extended format: the same information listed for d s http command are
shown for each session.

[15:53:05] ABILIS_CPX:d s http

RES:Http ----------------------------------------------------------------------
HyperText_Transfer_Protocol
--- Cleared 000:00:00:00 ago, on 08/11/2006 at 15:59:02 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 4228062| 42640997|REQ | 10402| |
REQ-GET | 10402| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------

[15:59:02] ABILIS_CPX:d se http

RES:Http ----------------------------------------------------------------------
HyperText_Transfer_Protocol
--- Cleared 000:00:00:00 ago, on 08/11/2006 at 15:59:14 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 4228062| 42640997|REQ | 10402| |
REQ-GET | 10402| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |
REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |
REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 19512| 50419968|REQ | 48| |
REQ-GET | 48| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:3
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 2668171| 2598680832|REQ | 6564| |
REQ-GET | 6564| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:4
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 2361| 1880576|REQ | 6| |
REQ-GET | 6| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:5
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |
REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:6
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |

463
Draft HTTP - HyperText Transfer Protocol Draft

REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:7
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |
REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:8
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 856243| 2207517696|REQ | 2107| |
REQ-GET | 2107| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:9
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 24058| 62927360|REQ | 59| |
REQ-GET | 59| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:10
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 657717| 1699701504|REQ | 1618| |
REQ-GET | 1618| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------
CH:11
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|REQ | 0| |
REQ-GET | 0| |REQ-POST | 0| |
REQ-PUT | 0| |
------------------------------------------------------------------------

34.4. HTTPS (HTTP over SSL)

Adding the SSL (Secure Socket Layer) resource and configuring properly the HTTP resource are needed to enable the HTTP
over SSL resource.

34.4.1. Activating the SSL resource

Add the resource to the Abilis system with the following command.

[12:25:41] ABILIS_CPX:a res:ssl

RES:SSL ALREADY EXISTS

The SSL resource may already exist in the system, but may not yet be active: set it active with the command:

[12:25:44] ABILIS_CPX:s act res:ssl

COMMAND EXECUTED

Caution
After adding or setting the SSL active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p ssl act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p ssl

464
Draft HTTP - HyperText Transfer Protocol Draft

RES:Ssl - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

-----------------------------------------------------------------------
Run DESCR:Secure_Socket_Layer
LOG:NO ACT:YES max-cli:2 max-srv:4
mpxs:2048 SEND-TOUT:20 CACH-TOUT:300 AUTH-CLI:NO
PWDKEY-CLI:DFT PWDKEY-SRV:DFT
CERT-PATH:SYS (C:\6-0-9\)

Caution
Use the init res:ssl command to activate the changes made and save the configuration with the save conf
command to make the changes permanent.

34.4.2. HTTP resource configuration

Set the ACT-S to YES and the sesnum-s to a value different from zero.

[16:55:46] ABILIS_CPX:s p http act-s:yes sesnum-s:12

COMMAND EXECUTED

[16:55:59] ABILIS_CPX:d p http

RES:Http - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:HyperText_Transfer_Protocol
LOG:NO ACT:YES LOGIN-COOKIE-TOUT:1440
WDIR:C:\APP\HTTP\
START-PAGE:SYS (/sys/pub/cpx.htm)
SYS-CSS:SYS (/sys/pub/cpx.css)
- HTTP plain -----------------------------------------------------------
ACT-P:YES locport-p:80 sesnum-p:12
IPSRC-P:* IPSRCLIST-P:#
- HTTP ssl -------------------------------------------------------------
ACT-S:YES locport-s:443 sesnum-s:12
IPSRC-S:* IPSRCLIST-S:#

Caution
Use the init res:http command to activate the changes made and save the configuration with the save conf
command to make the changes permanent.

The Virtual Paths Access Rights are the same of the HTTP protocol: verify that the SSL protocol is enabled in the table and
in the user's parameters with the following commands:

[15:12:54] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

[17:53:34] ABILIS_CPX:d user:httpuser

465
Draft HTTP - HyperText Transfer Protocol Draft

Parameter: | Value:
---------------+---------------------------------------------------------------
USER: httpuser
PWD: *********
ACT: YES
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

34.4.3. Connecting to Abilis using HTTPS

Type inside a common browser the URL https://<Abilis IP Address> to connect to Abilis Web Interface using
HTTPS protocol.

Before connection, it will be requested to accept the digital certificate: click I understand the risk and then Add Exception.
The Abilis CPX Web Interface it is shown.

34.5. Appendix - HTTP

Hypertext Transfer Protocol3 (HTTP) is a communication protocol used to transfer or convey information on the World Wide
Web. Every HTTP server program operates by accepting HTTP requests from the network, and providing an HTTP response
to the requester. The HTTP response typically consists of an HTML document, but can also be a raw text file, an image, or
some other type of document; if something bad is found in client request or while trying to serve the request, an HTTP server
has to send an error response which may include some custom HTML or text messages to better explain the problem to end
users.

HTTP traffic is very insecure, all data is transferred in clear text; for this reason it was developed HTTPS (Hyper Text
Transfer Protocol Secure), a secure version of the HTTP. HTTPS is not a separate protocol, but refers to the combination
of a normal HTTP interaction over an encrypted Secure Sockets Layer4 (SSL) or Transport Layer Security5 (TLS) transport
mechanism based on digital certificates. Most typically HTTP data is sent over TCP/IP port 80, whereas SSL HTTP data is
sent over port 443.

3
http://en.wikipedia.org/wiki/HTTP
4
http://en.wikipedia.org/wiki/Transport_Layer_Security
5
http://en.wikipedia.org/wiki/Transport_Layer_Security

466
Draft Draft

Chapter 35. SYSLOG - The syslog

protocol
Konstantin Trubkin
Luigi Demuro

Table of Contents
35.1. SYSLOG resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.2. SYSLOG configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
35.3. SYSLOG diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
35.4. SYSLOG messages codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5. Win2k SYSLOG server implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.1. Kiwi SYSLOG Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
35.5.2. KLog win2k SYSLOG server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
35.6. Rsyslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
35.6.1. Rsyslog configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.2. Syslog resource configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
35.6.3. Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
35.7.1. SYSLOG architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

35.1. SYSLOG resource

The Abilis SYSLOG module implements two working modes:

• SYSLOG Device. Generates (by API function) and sends own SYSLOG messages.

• SYSLOG Relay. Receives the messages and forward it to another machine(s) (SYSLOG receivers).

Tip
Refer to chapter Section 35.7, “Appendix” to know more about syslog protocol.

35.2. SYSLOG configuration

Add the resource to the Abilis system with the following command:

[11:09:16] ABILIS_CPX:a res:syslog

RES:SYSLOG ALREADY EXISTS

The SYSLOG resource may already exist in the system, but may not yet be active: set it active with the command:

[11:09:21] ABILIS_CPX:s act res:syslog

COMMAND EXECUTED

Use the following command to display the parameters of the resource:

[10:54:52] ABILIS_CPX:d p syslog

RES:SysLog --------------------------------------------------------------------

467
Draft SYSLOG - The syslog protocol Draft

Run DESCR:System_Log_protocol
LOG:NO ACT:YES queue-size:64 udp-locport:514 RELAY:NO
LOCAL-SEVERITY:ALL
LOCAL-SOURCES:SYS
SRCADD:R-ID (192.168.000.201) TOS:0-N
HOSTNAME:
HOSTNAME-IP:R-ID (192.168.000.201)
IPSRC:* IPSRCLIST:#
RECEIVER1:# RECEIVER2:#
RECEIVER3:# RECEIVER4:#

Warning
After adding or setting the SYSLOG active, you must restart the Abilis to make the resource running (use
the command warm start to reboot the Abilis).

Below are descriptions of the most important parameters:

LOG activates the logging and the generation of the alarms [NO, D (=Debug Log), S (=System Log), A
(=Alarm view), L (=Local audible alarm), T (=SNMP traps), ALL] [+E (=Extended Log of state
changes)].

ACT enables/disables the resource [NO, YES].

queue-size Maximum pending SYSLOG requests [32...2048].

RELAY Activation/deactivation of SYSLOG relay mode.

TOS enables Type Of Service (TOS) or Differentiated Services Field (DS) [-' p-t', i.e. PRECEDENCE
and TOS values, where 'p' can be [0...7] and 't' can be [N (=None), D (=Min. Delay), T (=Max.
Throughput), R (=Max. Reliability), C (=Min. Monetary Cost)] - 'bbbbbb', i.e. DS value bit by bit,
where 'b' can be [0, 1]].

LOCAL-SEVERITY Allowed message severities [EMERGENCY, ALERT, CRITICAL, ERROR, WARNING, NOTICE,
INFO, DEBUG, ALL]. Values can be joined using ',' character.

LOCAL-SOURCES Allowed message sources [SYS, DBG, ALL]. Values can be joined using ',' character.

IPSRC Selects the IP address of the client from which the requests will be accepted.

IPSRCLIST Sets the list of DNS Client systems enabled to use the SYSLOG relay service.

SRCADD Source IP address for outgoing messages [R-ID: the source IP address of the outgoing datagrams will
be set to the current RouterID value; OUT-IP: the source IP address of the outgoing datagrams will
be set on the base of the output IP interface; 1-126.x.x.x, 128-223.x.x.x: the source IP
address of the outgoing datagrams will be set to the selected value; Ip-nnn: use the current IPADD
of the specified IP resource].

HOSTNAME Value of HOSTNAME part of outgoing SYSLOG messages.

HOSTNAME-IP IP form of HOSTNAME part of outgoing SYSLOG messages. [R-ID: HOSTNAME will be set to
the IP address of the current RouterID value; OUT-IP: HOSTNAME will be set to the IP address of
output IP interface; 1-126.x.x.x, 128-223.x.x.x: HOSTNAME will be set to the selected
IP address.

RECEIVERx IP address of SYSLOG receiver #x (collector or next relay) to forward SYSLOG messages [#,
1.0.0.0...126.255.255.255, 128.0.0.0...223.255.255.255]

The following command allows the administrator to change the configuration of the resource:

s p syslog name:value...

35.3. SYSLOG diagnostic and statistics

To display the diagnostic and the statistics of the SYSLOG resource the following commands are used:

468
Draft SYSLOG - The syslog protocol Draft

d d syslog Shows diagnostic information, such as the state of the SYSLOG client and the ip address and ports of
SYSLOG servers which Abilis is connected to;

d s syslog Shows statistic information, such as number of characters received/sent, number of packets received/sent,
number of lost packets with too long length, bad format or with answer that doesn't match to request.

[18:06:40] ABILIS_CPX:d d syslog

RES:SysLog --------------------------------------------------------------------
System_Log_protocol
STATE:READY RELAY-STATE:INACTIVE
----------------------|--- CUR ---|-- PEAK ---|
PENDING-REQUEST | 0| 2|
----------------------|--- CUR ---|-- PEAK ---|--- MAX ---|
PENDING-QUEUE (Kbytes)| 0| 0| 64|
-----------------------------------------------------------

[11:49:14] ABILIS_CPX:d s syslog

RES:SysLog --------------------------------------------------------------------
System_Log_protocol
--- Cleared 0 days 15:02:15 ago, on 22/12/2010 at 20:47:04 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
USER | 161| |RELAY | 0| |
CHR | 0| 11238|PCK | 0| 161|
MODIFIED | 0| |LONG | 0| |
NO-QUEUE | 0| |
------------------------------------------------------------------------

35.4. SYSLOG messages codes

Use the following commands to show a short description of syslog codes:

• help syslog: it shows the list of System Log event;

• help syslog nnnnn: it shows help on the specified System Log event.

Example:

[15:38:06] ABILIS_CPX:help syslog 212

------+-----------+------------------------------------------------------------
Code | Severity | Description
------+-----------+------------------------------------------------------------
00212 | INFO | SYS SET BOOT VERSION COMMAND has been executed.

35.5. Win2k SYSLOG server implementations

Win2k doesn't support SYSLOG protocol by default. But some free implementation of SYSLOG protocol are present.

35.5.1. Kiwi SYSLOG Daemon

Kiwi SYSLOG deamon1 Kiwi Syslog Daemon is a freeware Syslog Daemon for Windows. It receives, logs, displays and
forwards syslog messages from hosts such as routers, switches, unix hosts and any other syslog enabled device

Main features of Kiwi deamon:

• Display the message in the scrolling window.

• Logging the message to a text file.

1
http://www.kiwisyslog.com/kiwi-syslog-daemon-overview/

469
Draft SYSLOG - The syslog protocol Draft

• Forward the message to another syslog daemon.

• Log to an ODBC database.

• Log to the NT Application Event Log.

• E-mail the message to someone via SMTP.

• Triggering a sound alarm.

• Running an external program.

• Send an SNMP Trap message.

• Page someone using NotePager Pro.

Kiwi deamon can be downloaded from this address2.

By default when Kiwi Syslog Daemon is installed it contains a single Rule that has no Filters. This means that all syslog
messages that arrive are processed by the Actions in this Rule. The Rule contains two separate Actions: a Display Action
which displays all information received to Display00 'in real time'; and a Log to File Action. This Action logs all the
information to a file called “SyslogCatchall.txt” which is located in the Logs directory of your Kiwi Syslog installations
folder.

This is a very basic initial setup for Kiwi Syslog Daemon. If this Rule is turned off or deleted, no messages will be displayed
or logged to file.

To manage your syslog messages, you can create further filters and actions that will allow you to process the messages to
your own requirements.

Figure 35.1. Kiwi deamon main window

2
http://www.kiwisyslog.com/kiwi-syslog-daemon-download/

470
Draft SYSLOG - The syslog protocol Draft

Figure 35.2. Kiwi deamon setup window

To receive messages from Abilis SYSLOG driver you should select UDP transport. UDP port should be set to the 514.

471
Draft SYSLOG - The syslog protocol Draft

Figure 35.3. Kiwi deamon setup UDP transport window

35.5.2. KLog win2k SYSLOG server

KLog3 is win32 implementation of *nix SYSLOG daemon to support remote logging of message from syslog-enabled unix
servers, routers and other networked devices and applications.

KLog can be downloaded from this address4. After installation it's fully ready to work.

3
http://kin.klever.net/klog/
4
http://kin.klever.net/klog/binaries

472
Draft SYSLOG - The syslog protocol Draft

Figure 35.4. KLog main window

35.6. Rsyslog
Rsyslog is a syslog daemon installed on Ubuntu. The purpose is to collect information and store them in /var/log/
syslog file.

Note
Rsyslog daemon can store information using databases like MySQL, SQlite, SyBase. Search documentation
on Internet to know how to configure it.

473
Draft SYSLOG - The syslog protocol Draft

35.6.1. Rsyslog configuration

Edit the file /etc/rsyslog.conf to enable rsyslog daemon to collect syslog events from a client. There are two
protocols available to collect information: UDP and TCP. Abilis uses UDP protocol so edit /etc/rsyslog.conf
uncommenting lines:

$ModLoad imudp

$UDPServerRun 514

# /etc/rsyslog.conf Configuration file for rsyslog.

#
# For more information see
# /usr/share/doc/rsyslog-doc/html/rsyslog_conf.html
#
# Default logging rules can be found in /etc/rsyslog.d/50-default.conf

#################
#### MODULES ####
#################

$ModLoad imuxsock # provides support for local system logging

$ModLoad imklog # provides kernel logging support (previously done by rklogd)
#$ModLoad immark # provides --MARK-- message capability

$KLogPath /proc/kmsg

# provides UDP syslog reception

$ModLoad imudp
$UDPServerRun 514

# provides TCP syslog reception

#$ModLoad imtcp
#$InputTCPServerRun 514

Type service rsyslog restart to restart syslog daemon and apply the new configuration.

root@ubuntu-desktop:/var/log# service rsyslog restart

rsyslog start/running, process 2372
root@ubuntu-desktop:/var/log#

Tip
If rsyslog is not installed, type sudo apt-get install rsyslog to install it.

35.6.2. Syslog resource configuration

Add Syslog resource and then configure it so that RECEIVER1 parameter is equal to ip address of your syslog server.

[15:26:07] ABILIS_CPX:s p syslog receiver1:192.168.30.1

COMMAND EXECUTED

[15:26:15] ABILIS_CPX:d p syslog

RES:SysLog - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
Run DESCR:System_Log_protocol
LOG:NO ACT:YES queue-size:64 udp-locport:514 RELAY:NO
LOCAL-SEVERITY:ALL
LOCAL-SOURCES:SYS
SRCADD:R-ID (192.168.000.201) TOS:0-N

474
Draft SYSLOG - The syslog protocol Draft

HOSTNAME:
HOSTNAME-IP:R-ID (192.168.000.201)
IPSRC:* IPSRCLIST:#
RECEIVER1:192.168.030.001 RECEIVER2:#
RECEIVER3:# RECEIVER4:#

[15:26:19] ABILIS_CPX:init res:syslog

COMMAND EXECUTED

[15:26:27] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

35.6.3. Results
The following are the information collected by linux syslog server.

root@ubuntu-desktop:/var/log# tail -f syslog

Dec 23 15:10:51 192.168.0.201 Abilis-CPX [00033] WARM START#015
Dec 23 15:11:35 192.168.0.201 Abilis-CPX [00092] I: Ip-3 PLink:d2 SLink:RD#015
Dec 23 15:11:35 192.168.0.201 Abilis-CPX [00092] I: Ip-4 PLink:d2 SLink:ln#015
Dec 23 15:11:35 192.168.0.201 Abilis-CPX [00092] I: Pv-5 PLink:d2 SLink:ln#015
Dec 23 15:11:35 192.168.0.201 Abilis-CPX [00092] I: Pv-6 PLink:d2 SLink:ln#015
Dec 23 15:11:35 192.168.0.201 Abilis-CPX [00092] I: Ip-9 PLink:d2 SLink:ln#015
Dec 23 15:11:53 192.168.0.201 Abilis-CPX [00092] I: Pv-5 PLink:RD SLink:ln#015
Dec 23 15:11:53 192.168.0.201 Abilis-CPX [00092] I: Pv-6 PLink:RD SLink:ln#015
Dec 23 15:15:47 192.168.0.201 Abilis-CPX [00033] WARM START#015
Dec 23 15:16:30 192.168.0.201 Abilis-CPX [00092] I: Ip-3 PLink:d2 SLink:RD#015
Dec 23 15:16:30 192.168.0.201 Abilis-CPX [00092] I: Ip-4 PLink:d2 SLink:ln#015
Dec 23 15:16:30 192.168.0.201 Abilis-CPX [00092] I: Pv-5 PLink:d2 SLink:ln#015
Dec 23 15:16:30 192.168.0.201 Abilis-CPX [00092] I: Pv-6 PLink:d2 SLink:ln#015
Dec 23 15:16:30 192.168.0.201 Abilis-CPX [00092] I: Ip-9 PLink:d2 SLink:ln#015
Dec 23 15:16:48 192.168.0.201 Abilis-CPX [00092] I: Pv-5 PLink:RD SLink:ln#015
Dec 23 15:16:48 192.168.0.201 Abilis-CPX [00092] I: Pv-6 PLink:RD SLink:ln#015

35.7. Appendix
The SYSLOG5 protocol provides a transport to allow a machine to send event notification messages across IP networks to
event message collectors.

Syslog messages are not formatted, the protocol is simply designed to transport these event messages. The scenario includes:

• a device which originates messages;

• the SYSLOG process which may send messages to a collector;

No acknowledgement of the receipt is made.

SYSLOG uses the user datagram protocol (UDP). The UDP port that has been assigned to SYSLOG is 514. It is
recommended that the source port also be 514.

SYSLOG protocol definitions:

• Device. A machine that can generate a message.

• Relay. A machine that can receive the message and forward it to another machine.
• Collector. A machine that receives the message and does not relay it to any other machines. This has been commonly
known as a SYSLOG server.
• Sender. Any device or relay when it sends a message.

5
http://en.wikipedia.org/wiki/syslog

475
Draft SYSLOG - The syslog protocol Draft

• Receiver. Any relay or collector, when it receives the message.

35.7.1. SYSLOG architecture

The architecture of the devices may be summarized as follows:

• Senders send messages to relays or collectors with no knowledge of whether it is a collector or relay.
• Senders may be configured to send the same message to multiple receivers.
• Relays may send all or some of the messages that they receive to a subsequent relay or collector. In the case where they do
not forward all of their messages, they are acting as both a collector and a relay. In the following diagram, these devices
will be designated as relays.
• Relays may also generate their own messages and send them on to subsequent relays or collectors. In that case it is acting
as a device. These devices will also be designated as a relay in the following diagram.

Some possible SYSLOG architectures:

Figure 35.5. SYSLOG architectures

476
Draft Draft

Chapter 36. Tunneling proprietary

protocols
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
36.1. Tunneling proprietary protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
36.1.1. Link check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
36.2. Configuring Packet Voice tunnels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.1. Packet Voice over IP- Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
36.2.2. IP Packet Voice - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
36.2.3. IP-BCK Packet Voice - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
36.2.4. IP Packet Voice - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
36.3. Configuring Abilis Ip Tunnels (AIPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
36.3.1. Abilis IP Tunnel over IP – Extended Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
36.3.2. Abilis IP Tunnel over IP - Extended-Server/Extended Client Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
36.3.3. Abilis IP Tunnel over IP - Extended Mode with ISDN backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
36.3.4. Abilis IP Tunnel over IP - Extended Mode with Double Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
36.4. Tunneling diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.1. Tunneling diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
36.4.2. Tunneling statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
36.5. Appendix - LN2 parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525

36.1. Tunneling proprietary protocols

Abilis supports two types of virtual tunneling, which can be applied to different level 2 links:

• PV (Packet Voice): for UDP packetised voice only.

• AIPT (Abilis IP Tunnel): for data and voice exchange.

Both virtual tunnels support several operation modes:

• Tunnelling Mode

477
Draft Tunneling proprietary protocols Draft

Table 36.1. Tunnelling modes

Mode Description Note

STD Standard No out-of-sequence packet reordering!
Use STD only for tunnels through LAN
and high quality WAN.
EXT Extended EXT supports out-of-sequence packet
reordering, extended statistics and
diagnostics. Use EXT for PV or AIPT
tunnels through WAN, when both
linked Abilis have a static IP Address.
EXT-SERVER Extended Server Use the combination of EXT-SERVER
and EXT-CLIENT, for PV or AIPT
tunnels, when one side has dinamyc
IP address (client) and the other side
has static address (the server must have
static IP address).
EXT-CLIENT Extended Client EXT client is also to be used in PV or
AIPT tunnels when Abilis is placed
behind a router doing NAT/PAT

• ART Protocol: “Abilis Redundant Tunneling” sends the same information on two different lines. The receiving Abilis
discards the packet which arrives second (out-of sequence). The probability that the same packet is lost on both links
equals the product of the original probabilities. Example: two links with 10% failure rate (a very high one!) ends up with
1%, which is normally negligible

Tip
It is avdisable to use ART ONLY with lines with the same speed. In case of lines with different speeds,
the packets are sent with the maximum speed of the slower line.

• Backup over ISDN: in case of failure of the permanent VPN connection, the Abilis PV or AIPT tunnels may be
instantaneously switched onto ISDN backup lines.

• Link Check: it is a procedure used to detect end-to-end link (or emulated p-link) real functioning, regardless of the lower
protocol layers states.

• Encryption: it activates the cryptography of the data sent on the virtual VPN and define up to 63 256 bit cryptography key
(exist also a default cryptography key that can be used in configuration).

• MPX (Multiplexing): this owner protocol allows to share the same link (VPN) for transmission of data and packetised
voice (also Link Check, if enabled).

• LOG: activates/deactivates logging functionalities of meaningful events of the VPNs. These functionalities can be applied
to IP tunnel or Link Level.

36.1.1. Link check

Link check allows to automatically manage an eventual “True link backup” (onto ISDN line) in case of failure of the
permanent VPN connection. When activating a packet voice or ip tunnel, Abilis checks continuosly the link using the below
parameters:

LLOG Link Check logging activation/deactivation.

LMPX Activates the multiplexing of DATA, “Link-Check”, VOICE frames type [NO: Abilis MPX multiplexing is not
active; YES: Abilis MPX multiplexing is active only for the data protocols LAPB and LINK-FR; EXT: Abilis
MPX multiplexing is active for ANY data protocol]. The default value is YES;

LC Enables/disables the use of the “Link-Check” protocol, and consequently the transmission of “Link-check”
frames. The link-check protocol is automatically disabled when MPX:NO. Note:with LC:NO the “true link
backup” is disabled. The default value is YES;

478
Draft Tunneling proprietary protocols Draft

LCR Enables and selects the cryptography to be applied on the frames passing through the resource. Cryptography can
be selectively applied to the different traffic types (VOICE and DATA). [NO: no cryptography is applied; DATA:
cryptography is applied only on DATA traffic type; VOICE: cryptography is applied only on VOICE traffic type;
ALL: cryptography is always in use, whatever is the traffic data type].

LCRKEY Selects the key to be used for cryptography operations. Users can choose either the default key supplied by the
system (LCRKEY:DFT), or one of the keys defined in the cryptography keys table, in which case the numeric
value (from 1 to 63) corresponding to the desired LCRKEY has to be specified. If the configured value refers to
a missing LCRKEY it will be shown inside square brackets (e.g. CRKEY:[5] means that the key number 5 is not
present in the table). If the parameter LCR is set to NO, the value of LCRKEY is useless.

LT1 Maximum time to wait for a Link-Check “probe” acknowledge. If this time elapses without receiving the
acknowledge the “probe” is immediately repeated, as a result “not acknowldged probes” are repeated every LT1
milliseconds. The default is 3000;

LT3 This is the time interval between a correctly sent and acknowledged Link-Check “probe” and the next one to send
while the link is regularly working (e.g. P-LINK state is READY). It has relationships with the parameter LT1:
and it has to satisfy the simple rule: LT3 > LT1 * 2. The default is 9000;

LN2 Sets the maximum number of Link-Check “probes” retransmission. The default is 3.

Tip
Refer to chapter Section 36.5, “Appendix - LN2 parameter” to have more information about LN2
parameter.

LCOMP Set the compression type to use for an ip resource with subtype AIPT[-BCK], DL[-BCK], ML, BCH. Data
Compression is available only under licence.[NO: compression not active, LZO1X: is often the best choice of all,
LZO1B: is good with a large blocksize or with very redundant data, LZO1F: s good with a small blocksize or with
binary data]

These parameters are in the link section:

[10:42:48] ABILIS_CPX:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.201) REMIPADD:#

Abilis sends a link-check every LT3 msec. If there's no response, Abilis sends it again every LT1 msec for LN2 times. Using
the default values it can take from 9 to 18 seconds to consider the link down.

The default values can be changed useing the sintax:

• s p pv-<id> par:<value> for a PV tunnel

479
Draft Tunneling proprietary protocols Draft

• s p ip-<id> par:<value> for an AIPT tunnel.

Tip
LT1 parameter has relationships with the parameter T1: and it has to satisfy the simple rule: T3 > T1 * 2.

36.2. Configuring Packet Voice tunnels

Packet Voice is a virtual tunnel typically used for voice communications between Abilis.

To setup a Packet-Voice, first add a PV resource with the command:

a res:pv-<id> subtype:<value>

id is simply the identification number and subtype is the kind of resource to be used. The following command shows
supported subtypes.

[17:27:43] ABILIS_CPX:a res:pv-1 subtype: ?

Pv resource subtypes:

DL PV over Dedicated Line

DL-BCK PV over Dedicated Line with Abilis Back-up
BCH PV over B-Channel
FR PV over Frame Relay
FR-BCK PV over Frame Relay with Abilis Back-up
VSP PV over VSP
VSP-BCK PV over VSP with Abilis Back-up
IP PV over IP (Abilis tunnel)
IP-BCK PV over IP (Abilis tunnel) with Abilis Back-up
ML PV over Multi-Links

36.2.1. Packet Voice over IP- Extended Mode

The extended mode is used when both Abilis have a static IP address.

The following example considers two Abilis with a static public IP address each one.

• IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

First, add a new resource on both Abilis:

[17:31:47] ABILIS_CPX_1:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:38:55] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------

480
Draft Tunneling proprietary protocols Draft

DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

[17:42:52] ABILIS_CPX_2:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:45:08] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

Warning
Save the configuration with the command save conf and restart the Abilis with the command warm start.

The most important parameters to configure are:

• DESCR: description of the resource.

• MODE: operating mode.

• LOCPORT: UDP port number of the local Abilis (port used for the data exchange).

• REMPORT: UDP port number of the remote Abilis.

• LOCIPADD: IP address of the local Abilis.

• REMIPADD: IP address of the remote Abilis.

Tip
The above parameters must mirror each other (i.e. the value of LOCPORT on “Abilis 1” must be the same of
REMPORT on “Abilis 2” and vice versa; the same for LOCIPADD/REMIPADD).

[17:50:29] ABILIS_CPX_1:s p pv-1 mode:ext remport:3101 locipadd:217.1.1.1 remipadd:217.2.2.2 descr:

COMMAND EXECUTED

[18:00:04] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_2
- Link -----------------------------------------------------------------

481
Draft Tunneling proprietary protocols Draft

LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO

LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002

[17:59:20] ABILIS_CPX_2:s p pv-1 mode:ext remport:3101 locipadd:217.2.2.2 remipadd:217.1.1.1 descr:

COMMAND EXECUTED

[18:02:30] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

[16:55:21] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:55:25] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002

[17:02:43] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

482
Draft Tunneling proprietary protocols Draft

WARNING: RES:Pv-1 Changed "MPX" from NO to YES

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[18:02:30] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001

Now the configuration of the VPN is completed.

Tip
Interesting chapter: Section 52.14.1, “How to configure a voice tunnel where both Abilis have a static public
IP address”.

36.2.2. IP Packet Voice - Extended-Server/Extended Client Mode

This mode is useful to configure a VPN between two Abilis when one of them hasn't a static public IP address or is placed
behind a router doing NAT/PAT.

Consider an Abilis with a static public IP address and the other one with dynamic public IP address:

• IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• IP address of the “Abilis” (ABILIS_CPX_2): dynamic

“ABILIS 1” will be set as EXT-SERVER; “ABILIS_CPX_2” will be set as EXT-CLIENT.

First, add a new resource on both Abilis:

[17:31:47] ABILIS_CPX_1:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:38:55] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT

483
Draft Tunneling proprietary protocols Draft

- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#

[17:42:52] ABILIS_CPX_2:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:45:08] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

In EXT-SERVER and EXT-CLIENT modality, new parameters will appear:

[17:28:19] ABILIS_CPX_1:s p pv-1 mode:ext-server

COMMAND EXECUTED

[18:00:01] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
CLI-ID:#
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) IP-FILTER:*

[17:27:48] ABILIS_CPX_2:s p pv-1 mode:ext-client

COMMAND EXECUTED

[18:00:24] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE

484
Draft Tunneling proprietary protocols Draft

PATH:SINGLE LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT

ID:R-ID (192.168.001.254)
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

Configuration of both Abilis must mirror each other. This the meaning of the “new” parameters:

• ID: on client side, is the identification IP address sent by the client to the server.

• CLI-ID: on server side, is the client identifier IP address. It can be also a “virtual value”, but it must set at the same value
of parameter ID on client side.

Tip
ID and CLI-ID can be also a “virtual values”, but they must set at the same value or the VPN will not
work!

Configure on “Abilis 1”the following parameters:

• DESCR: description of the resource.

• LOCPORT: UDP port number of the local Abilis (port used for the data exchange).

• REMPORT: UDP port number of the remote Abilis.

• LOCIPADD: IP address of the local Abilis.

• CLI-ID: client identifier IP address.

Configure on “Abilis 2”the following parameters:

• DESCR: description of the resource.

• LOCPORT: UDP port number of the local Abilis (port used for the data exchange).

• REMPORT: UDP port number of the remote Abilis.

• LOCIPADD: IP address of the local Abilis.

• REMIPADD: IP address of the remote Abilis.

• ID: identification IP address sent by the client to the server.

[11:47:35] ABILIS_CPX_1:s p pv-1 descr:To_Abilis_2 cli-id:192.168.1.1 locipadd:217.1.1.1 remport:31

COMMAND EXECUTED

[11:50:15] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
CLI-ID:192.168.001.001
OUT-IP:AUTO
LOCIPADD:217.001.001.001 IP-FILTER:*

[11:47:58] ABILIS_CPX_2:s p pv-1 descr:To_Abilis_1 locipadd:out-ip remipadd:217.1.1.1 remport:3101

485
Draft Tunneling proprietary protocols Draft

COMMAND EXECUTED

[11:51:58] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
ID:R-ID (192.168.001.254)
OUT-IP:AUTO
LOCIPADD:OUT-IP REMIPADD:217.001.001.001

Tip
The OUT-IP value on LOCIPADD of “Abilis 2” means that it is used the IP address of the IP resource
through which the packet is sent out. It is mandatory because Abilis has a dynamic IP address.

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

[11:50:17] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[12:05:20] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
CLI-ID:192.168.001.001
OUT-IP:AUTO
LOCIPADD:217.001.001.001 IP-FILTER:*

[11:52:00] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

486
Draft Tunneling proprietary protocols Draft

SAVE EXECUTED

[12:05:27] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
ID:R-ID (192.168.001.254)
OUT-IP:AUTO
LOCIPADD:OUT-IP REMIPADD:217.001.001.001

Now the configuration of the VPN is completed.

Tip
Interesting chapter: Section 52.14.2, “How to configure a voice tunnel where one Abilis has a dynamic
public IP address or is placed behind a router doing NAT/PAT”.

36.2.3. IP-BCK Packet Voice - Extended Mode with ISDN backup

In case of failure of the permanent VPN connection, the Abilis tunnels may be instantaneously switched onto ISDN backup
lines. The PV subtype requested for this configuration is PV-BCK.

The following example considers two Abilis placed in remote sides, with a static public IP address and a backup ISDN line
each one :

• IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• ISDN line connected to “Abilis 1” (ABILIS_CPX_1): 01234567

• IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

• ISDN line connected to “Abilis 2” (ABILIS_CPX_2): 01765432

First, add a new resource on both Abilis:

[12:17:46] ABILIS_CPX_1:a res:pv-1 subtype:ip-bck

COMMAND EXECUTED

[12:18:13] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------

487
Draft Tunneling proprietary protocols Draft

DESCR:
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#
- Back-Up --------------------------------------------------------------
BRTY:LIN BNRTY:0 BTB:3 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:#
CGI:* CGO:#
SDI:* SDO:#
SGI:DISABLED SGO:#

[12:17:50] ABILIS_CPX_2:a res:pv-1 subtype:ip-bck

COMMAND EXECUTED

[12:18:28] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------
DESCR:
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#
- Back-Up --------------------------------------------------------------
BRTY:LIN BNRTY:0 BTB:3 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:#
CGI:* CGO:#
SDI:* SDO:#
SGI:DISABLED SGO:#

IP configuration of both Abilis remains the same shown in Section 36.2.1, “Packet Voice over IP- Extended Mode”.

The configuration of ISDN backup is realized in the Back-Up section. Generally, the following fields are used:

• SGI: Input calling sub-address.

• SGO: Output calling sub-address.

• CDO: Output called number (ISDN of remote side).

SGI and SGO are special ISDN's fields where users can insert alphanumeric string. Abilis uses them as a sort of password to
discriminate the backup calls: the field SGO of local Abilis is “inserted” in outgoing calls and verified in SGI field on remote
Abilis and vice versa (the values of SGI and SGO on both Abilis must mirror each other).

Other interesting parameters are:

• BRTY: it allows to select the backup calls repetition rule;

488
Draft Tunneling proprietary protocols Draft

Table 36.2. Rules of call repetition on failure

Value Calls repetition rules

LIN The time interval between a call attempt and the next one is
fixed and configurable through the parameter TB
INC The time interval between a call attempt and the next one, is
doubled at every attempt, starting with the value defined in
the parameter TB
US The abbreviation US stands for “unattended site”. In this
case the S-Link channel driver activates the following
procedure until success: 1. the driver executes a number
of tries equal to the value of the parameter BNRTY: every
BTB seconds, or until three consecutive “link-check” errors
occur; 2. the driver makes 8 calls every 15 minutes; 3. the
driver makes 4 calls every 1 hour; 4. the driver makes 9
calls every 2 hours; 5. the driver makes 8 calls every 6
hours; 6. the driver is placed in the state STOPPED1 or
STOPPED2 caused by the last error; This procedure allows
an “automatic recovery” from critical situations within
three days from the first failure occurrence, afterwards a
maintenance intervention is required.

• BNRTY: it specifies the maximum number of backup call repetitions

• BTB: it defines the “base” time interval that the retry procedure set in BRTY: uses to calculate the delay between a call
attempt that fails and the next one

• BAC: configures the autoconnection mode [DOD, NAILED-UP]

• DOD: the B-channel is connected using dial-on-demand rules.

• NAILED-UP: the B-channel is spontaneously connected at boot, and reconnected in case of drop for any reason.

[12:33:00] ABILIS_CPX_1:s p pv-1 mode:ext remport:3101 locipadd:217.1.1.1 remipadd:217.2.2.2 descr:

COMMAND EXECUTED

[16:12:40] ABILIS_CPX_1:s p pv-1 brty:us bnrty:30 btb:10 sgi:abilis1-abilis2 sgo:abilis2-abilis1 cd

COMMAND EXECUTED

[16:14:19] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------
DESCR:To_Abilis_2
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01765432
CGI:* CGO:#
SDI:* SDO:#

489
Draft Tunneling proprietary protocols Draft

SGI:ABILIS1-ABILIS2 SGO:ABILIS2-ABILIS1

[12:18:30] ABILIS_CPX_2:s p pv-1 mode:ext remport:3101 locipadd:217.2.2.2 remipadd:217.1.1.1 descr:

COMMAND EXECUTED

[16:02:59] ABILIS_CPX_2:s p pv-1 brty:us bnrty:30 btb:10 sgi:abilis2-abilis1 sgo:abilis1-abilis2 cd

COMMAND EXECUTED

[16:14:58] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------
DESCR:To_Abilis_1
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01234567
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS2-ABILIS1 SGO:ABILIS1-ABILIS2

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

[16:15:09] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:17:41] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

DESCR:To_Abilis_2
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT

490
Draft Tunneling proprietary protocols Draft

OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01765432
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS1-ABILIS2 SGO:ABILIS2-ABILIS1

[16:15:14] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:17:45] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

DESCR:To_Abilis_1
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01234567
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS2-ABILIS1 SGO:ABILIS1-ABILIS2

Now the configuration of the VPN is completed.

Tip
Interesting chapter: Section 52.14.3, “How to configure a voice tunnel with the “backup over ISDN”
option”.

36.2.4. IP Packet Voice - Extended Mode with Double Path

Activating the ART (Abilis Redundant Tunneling) protocol, also named “Double Path”, can increase the reliability of the
VPN.

Tip
It is avdisable to use ART ONLY with lines with the same speed. In fact, if ART is used with lines with
different speed, packets are sent with a maximum speed equal to that one of the slower line.

Moreover, if a line is saturated, the entire Tunnel doesn't work properly!

Warning
When double path is active the traffic is obviously duplicated: this could be very “dangerous” on pay per use
lines!

491
Draft Tunneling proprietary protocols Draft

The following example considers two Abilis: each one has two different Internet lines with static public IP addresses.

• First IP address of “Abilis 1” (ABILIS_CPX_1) : 217.1.1.1

• Second IP address of “Abilis 1” (ABILIS_CPX_1): 80.80.80.80

• First IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

• Second IP address of “Abilis 2” (ABILIS_CPX_2): 81.81.81.81

First, add a new resource on both Abilis:

[17:27:07] ABILIS_CPX_1:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:28:13] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#

[17:27:12] ABILIS_CPX_2:a res:pv-1 subtype:ip

COMMAND EXECUTED

[17:28:18] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

Configuring MODE:EXT and PATH:DOUBLE new parameters will appear:

[17:28:29] ABILIS_CPX_1:s p pv-1 mode:ext path:double

492
Draft Tunneling proprietary protocols Draft

COMMAND EXECUTED

[17:31:21] ABILIS_CPX_1:d p pv-1

RRES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#
OUT-IP2:AUTO
LOCIPADD2:R-ID (192.168.000.254) REMIPADD2:#

[17:28:21] ABILIS_CPX_2:s p pv-1 mode:ext path:double

COMMAND EXECUTED

[17:31:38] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#
OUT-IP2:AUTO
LOCIPADD2:R-ID (192.168.001.254) REMIPADD2:#

Tip
The parameter PATH must be set ad the same value on both the CPX or the VPN will not work.

New parameters are:

• OUT-IP2: second output IP resource (AUTO will send the packets to the default gateway specified in IP routing table; it's
also possible to specify the ID and the gateway of the outgoing IP resource).

• LOCIPADD2: second IP address that the local Abilis will use as “source address” for the path 2.

• REMIPADD2: second IP address of the remote Abilis for the path 2.

Configuration of other parameters of both Abilis must mirror each other; see Section 36.2.1, “Packet Voice over IP- Extended
Mode”.

[17:54:42] ABILIS_CPX_1:s p pv-1 remport:3101 locipadd:217.1.1.1 remipadd:217.2.2.2 locipadd2:80.80

descr:To_Abilis_2

COMMAND EXECUTED

[17:54:52] ABILIS_CPX_1:d p pv-1

493
Draft Tunneling proprietary protocols Draft

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
OUT-IP2:3 GW2:#
LOCIPADD2:080.080.080.080 REMIPADD2:081.081.081.081

[17:55:09] ABILIS_CPX_2:s p pv-1 remport:3101 locipadd:217.2.2.2 remipadd:217.1.1.1 locipadd2:81.81

descr:To_Abilis_1

COMMAND EXECUTED

[17:56:01] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) (IP) --------------------------------------
DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
OUT-IP2:3 GW2:#
LOCIPADD2:081.081.081.081 REMIPADD2:080.080.080.080

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

[17:54:54] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[18:02:19] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT

494
Draft Tunneling proprietary protocols Draft

- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
OUT-IP2:3 GW2:#
LOCIPADD2:080.080.080.080 REMIPADD2:081.081.081.081

[17:56:05] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Pv-1 Changed "MPX" from NO to YES
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[18:02:16] ABILIS_CPX_2:d p pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) (IP) ------------------------------------

DESCR:To_Abilis_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
OUT-IP2:3 GW2:#
LOCIPADD2:081.081.081.081 REMIPADD2:080.080.080.080

Now the configuration of the VPN is completed.

Tip
Interesting chapter: Section 52.14.4, “How to configure a voice tunnel with the “double-path” option”.

36.3. Configuring Abilis Ip Tunnels (AIPT)

Abilis Ip Tunnel is a virtual tunnel typically used for Data and Voice communications between Abilis.

To setup an Abilis IP Tunnel, first add an IP resource:

a res:ip-<id> subtype:<value>

id is simply the identification number and subtype is the kind of resource to be used. The following command shows
supported subtypes.

[14:58:13] ABILIS_CPX_1:a res:ip-2 subtype: ?

Ip resource subtypes:

X25PVC IP over X.25 Pvc

X25BSVC IP over X.25 Bsvc
LAN IP over LAN
DL IP over Dedicated Line
DL-BCK IP over Dedicated Line with Abilis Back-up
BCH IP over B-Channel
ML IP over Multi-Links
AIPT IP over IP (Abilis tunnel)

495
Draft Tunneling proprietary protocols Draft

AIPT-BCK IP over IP (Abilis tunnel) with Abilis Back-up

PPP IP over PPP
VIRTUAL IP virtual

36.3.1. Abilis IP Tunnel over IP – Extended Mode

The extended mode is used when both Abilis have a static IP address.

The following example considers two Abilis with a static public IP address each one.

• Public IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• Private IP address of “Abilis 1” (ABILIS_CPX_1): 192.168.0.254/24

• Public IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

• Private IP address of “Abilis 2” (ABILIS_CPX_2): 192.168.1.254/24

First, add a new resource on both Abilis:

[14:58:52] ABILIS_CPX_1:a res:ip-5 subtype:aipt

COMMAND EXECUTED

[15:06:29] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#

[14:58:14] ABILIS_CPX_2:a res:ip-5 subtype:aipt

COMMAND EXECUTED

496
Draft Tunneling proprietary protocols Draft

[15:06:37] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

The most important parameters to configure are:

• DESCR: description of the resource.

• MODE: operating mode.

• LOCPORT: UDP port number of the local ABILIS (port used for the data exchange).

• REMPORT: UDP port number of the remote ABILIS.

• LOCIPADD: IP address of the local ABILIS.

• REMIPADD: IP address of the remote ABILIS.

• NEIGH: IP address of the neighbour router (the other Abilis).

• MASK: mask of remote LAN.

• NAT: NAT usage.

• LCR: Encryption/Decryption activation.

• FRAG: link fragmentation.

• FRAGSIZE: maximum size of link frames fragments.

Tip
The above parameters must mirror each other (i.e. the value of LOCPORT on “Abilis 1” must be the same of
REMPORT on “Abilis 2” and vice versa; the same for LOCIPADD/REMIPADD).

[15:17:46] ABILIS_CPX_1:s p ip-5 descr:To_Abilis_2 neigh:192.168.1.254 mask:255.255.255.0 nat:insid

mode:ext remport:2105 locipadd:217.1.1.1 remipadd:217.2.2.2

COMMAND EXECUTED

[15:21:02] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

497
Draft Tunneling proprietary protocols Draft

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------

DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002

[15:06:44] ABILIS_CPX_2:s p ip-5 descr:To_Abilis_1 neigh:192.168.0.254 mask:255.255.255.0 nat:insid

mode:ext remport:2105 locipadd:217.2.2.2 remipadd:217.1.1.1

COMMAND EXECUTED

[15:22:37] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES. Also LMPX will be changed from YES to EXT: it can be set
to YES only for data protocols LAPB and LINK-FR (this VPN is based on UDP protocol).

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

498
Draft Tunneling proprietary protocols Draft

Tip
Encryption of data packets has been activated (LCR:DATA) and the default Encryption Key has been used
(LCRKEY:DFT). Usage of encryption is useful to increase the security of data transmission.

Tip
Fragmentation has been activated (FRAG:FRF12 FRAGSIZE:800): it's recommended on VPN realized over
Internet lines.

[15:21:05] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Iprtr Changed "LINKS:" from 1 to 2
WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[15:21:29] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002

[15:22:40] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:Iprtr Changed "LINKS:" from 1 to 2
WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:22:53] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO

499
Draft Tunneling proprietary protocols Draft

NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO

OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001

Now the configuration of the VPN is completed.

Tip
Interesting chapters:

Section 52.13.1, “How to configure a VPN tunnel where both Abilis have a static public IP address”;

Section 19.3, “IP Resources”.

36.3.2. Abilis IP Tunnel over IP - Extended-Server/Extended Client

Mode
This mode permits to configure a VPN between two Abilis when one of them hasn't a static public IP address or is placed
behind a router doing NAT/PAT.

Example: Abilis has a static public IP address and the other one has a dynamic public IP address:

• Public IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• Private IP address of “Abilis 1” (ABILIS_CPX_1): 192.168.0.254/24

• Public IP address of “Abilis 2” (ABILIS_CPX_2): dynamic

• Private IP address of “Abilis 2” (ABILIS_CPX_2): 192.168.1.254/24

“ABILIS 1” will be set as EXT-SERVER; “ABILIS_CPX_2” will be set as EXT-CLIENT.

First, add a new resource on both Abilis:

[14:58:52] ABILIS_CPX_1:a res:ip-5 subtype:aipt

COMMAND EXECUTED

[15:06:29] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:

500
Draft Tunneling proprietary protocols Draft

OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL

FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#

[14:58:14] ABILIS_CPX_2:a res:ip-5 subtype:aipt

COMMAND EXECUTED

[15:06:37] ABILIS_CPX_2:d p ip-5

RRES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

In EXT-SERVER and EXT-CLIENT modality, new parameters will appear:

[17:34:37] ABILIS_CPX_1:s p ip-5 mode:ext-server

COMMAND EXECUTED

[17:34:54] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000

501
Draft Tunneling proprietary protocols Draft

REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO

NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
CLI-ID:#
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) IP-FILTER:*

[17:34:45] ABILIS_CPX_2:s p ip-5 mode:ext-client

COMMAND EXECUTED

[17:35:13] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
ID:R-ID (192.168.001.254)
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

Configuration of both Abilis must mirror each other. This the meaning of the “new” parameters:

• ID: on client side, is the identification IP address sent by the client to the server.

• CLI-ID: on server side, is the client identifier IP address. It can be also a “virtual value”, but it must set at the same value
of parameter ID on client side.

Tip
ID and CLI-ID can be also a “virtual values”, but they must set at the same value or the VPN will not
work!

Configure on “Abilis 1”the following parameters:

• DESCR: description of the resource.

• LOCPORT: UDP port number of the local Abilis (port used for the data exchange).

502
Draft Tunneling proprietary protocols Draft

• REMPORT: UDP port number of the remote Abilis.

• LOCIPADD: IP address of the local Abilis.

• CLI-ID: client identifier IP address.

• NEIGH: IP address of the neighbour router (the other Abilis).

• MASK: mask of remote LAN.

• NAT: NAT usage.

• LCR: Encryption/Decryption activation.

• FRAG: link fragmentation.

• FRAGSIZE: maximum size of link frames fragments.

Configure on “Abilis 2”the following parameters:

• DESCR: description of the resource.

• LOCPORT: UDP port number of the local Abilis (port used for the data exchange).

• REMPORT: UDP port number of the remote Abilis.

• LOCIPADD: IP address of the local Abilis.

• REMIPADD: IP address of the remote ABILIS

• ID: identification IP address sent by the client to the server

• NEIGH: IP address of the neighbour router (the other Abilis).

• MASK: mask of remote LAN.

• NAT: NAT usage.

• LCR: Encryption/Decryption activation.

• FRAG: link fragmentation.

• FRAGSIZE: maximum size of link frames fragments.

[17:35:00] ABILIS_CPX_1:s p ip-5 descr:To_Abilis_2 neigh:192.168.1.254 mask:255.255.255.0 nat:insid

remport:2105 cli-id:192.168.1.254 locipadd:217.1.1.1

COMMAND EXECUTED

[17:54:30] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT

503
Draft Tunneling proprietary protocols Draft

CLI-ID:192.168.001.254
OUT-IP:AUTO
LOCIPADD:217.001.001.001 IP-FILTER:*

[17:35:14] ABILIS_CPX_2:s p ip-5 descr:To_Abilis_1 neigh:192.168.0.254 mask:255.255.255.0 nat:insid

remport:2105 id:192.168.1.254 locipadd:out-ip remipadd:217.1.1.1

COMMAND EXECUTED

[17:59:32] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
ID:192.168.001.254
OUT-IP:AUTO
LOCIPADD:OUT-IP REMIPADD:217.001.001.001

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES. Also LMPX will be changed from YES to EXT: it can be set
to YES only for data protocols LAPB and LINK-FR (this VPN is based on UDP protocol).

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

Tip
Encryption of data packets has been activated (LCR:DATA) and the default Encryption Key has been used
(LCRKEY:DFT). Usage of encryption is useful to increase the security of data transmission.

Tip
Fragmentation has been activated (FRAG:FRF12 FRAGSIZE:800): it's recommended on VPN realized over
Internet lines.

[17:58:29] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

504
Draft Tunneling proprietary protocols Draft

SAVE EXECUTED

[18:04:10] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-SERVER D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
CLI-ID:192.168.001.254
OUT-IP:AUTO
LOCIPADD:217.001.001.001 IP-FILTER:*

[17:59:34] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[18:04:28] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT-CLIENT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
ID:192.168.001.254
OUT-IP:AUTO
LOCIPADD:OUT-IP REMIPADD:217.001.001.001

Now the configuration of the VPN is completed.

505
Draft Tunneling proprietary protocols Draft

Tip
Interesting chapters:

Section 52.13.2, “How to configure a VPN tunnel where one Abilis has a dynamic public IP address or is
placed behind a router doing NAT/PAT”;

Section 19.3, “IP Resources”.

36.3.3. Abilis IP Tunnel over IP - Extended Mode with ISDN backup

In case of failure of the permanent VPN connection, the Abilis tunnels may be instantaneously switched onto ISDN backup
lines. The AIPT subtype requested for this configuration is AIPT-BCK.

Example: two Abilis are placed in remote sides, each one has a with a static public IP address and a backup ISDN line:

• Public IP address of “Abilis 1” (ABILIS_CPX_1): 217.1.1.1

• Private IP address of “Abilis 1” (ABILIS_CPX_1): 192.168.0.254/24

• ISDN line connected to “Abilis 1” (ABILIS_CPX_1): 01234567

• Public IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

• Private IP address of “Abilis 2” (ABILIS_CPX_2): 192.168.1.254/24

• ISDN line connected to “Abilis 2” (ABILIS_CPX_2): 01765432

First, add a new resource on both Abilis.

[15:35:35] ABILIS_CPX_1:a res:ip-5 subtype:aipt-bck

COMMAND EXECUTED

[15:36:01] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------

506
Draft Tunneling proprietary protocols Draft

TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#
- Back-Up --------------------------------------------------------------
BRTY:LIN BNRTY:0 BTB:3 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:#
CGI:* CGO:#
SDI:* SDO:#
SGI:DISABLED SGO:#

[15:35:35] ABILIS_CPX_2:a res:ip-5 subtype:aipt-bck

COMMAND EXECUTED

[15:36:08] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#
- Back-Up --------------------------------------------------------------
BRTY:LIN BNRTY:0 BTB:3 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:#
CGI:* CGO:#
SDI:* SDO:#
SGI:DISABLED SGO:#

IP configuration of both Abilis remains the same shown Section 36.3.1, “Abilis IP Tunnel over IP – Extended Mode”.
Consideration about ISDN Back-up configuration are the same reported here [488].

To complete the configuration type the following commands:

[16:37:00] ABILIS_CPX_1:s p ip-5 descr:To_Abilis_2 neigh:192.168.1.254 mask:255.255.255.0 nat:insid

mode:ext remport:2105 locipadd:217.1.1.1 remipadd:217.2.2.2

507
Draft Tunneling proprietary protocols Draft

COMMAND EXECUTED

[16:38:33] ABILIS_CPX_1:s p ip-5 brty:us bnrty:30 btb:10 sgi:abilis1-abilis2 sgo:abilis2-abilis1 cd

COMMAND EXECUTED

[16:41:13] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01765432
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS1-ABILIS2 SGO:ABILIS2-ABILIS1

[16:41:20] ABILIS_CPX_2:s p ip-5 descr:To_Abilis_1 neigh:192.168.0.254 mask:255.255.255.0 nat:insid

mode:ext remport:2105 locipadd:217.2.2.2 remipadd:217.1.1.1

COMMAND EXECUTED

[16:40:04] ABILIS_CPX_2:s p ip-5 brty:us bnrty:30 btb:10 sgi:abilis2-abilis1 sgo:abilis1-abilis2 cd

COMMAND EXECUTED

[16:42:55] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO

508
Draft Tunneling proprietary protocols Draft

- TRFA section ---------------------------------------------------------

TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01234567
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS2-ABILIS1 SGO:ABILIS1-ABILIS2

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES. Also LMPX will be changed from YES to EXT: it can be set
to YES only for data protocols LAPB and LINK-FR (this VPN is based on UDP protocol).

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

Tip
Encryption of data packets has been activated (LCR:DATA) and the default Encryption Key has been used
(LCRKEY:DFT). Usage of encryption is useful to increase the security of data transmission.

Tip
Fragmentation has been activated (FRAG:FRF12 FRAGSIZE:800): it's recommended on VPN realized over
Internet lines.

[16:49:19] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:49:22] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ----------

DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO

509
Draft Tunneling proprietary protocols Draft

- TRFA section ---------------------------------------------------------

TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01765432
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS1-ABILIS2 SGO:ABILIS2-ABILIS1

[16:49:27] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[16:49:29] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ----------

DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:01234567
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS2-ABILIS1 SGO:ABILIS1-ABILIS2

Now the configuration of the VPN is completed.

510
Draft Tunneling proprietary protocols Draft

Tip
Interesting chapters:

Section 52.13.3, “How to configure a VPN tunnel with the “backup over ISDN” option”;

Section 19.3, “IP Resources”.

36.3.4. Abilis IP Tunnel over IP - Extended Mode with Double Path

To increase the reliability of the VPN, it is possible to activate the ART (Abilis Redundant Tunneling) protocol, also named
“Double Path”.

Tip
It is avdisable to use ART ONLY with lines with the same speed. In fact, if ART is used with lines with
different speed, packets are sent with a maximum speed equal to that one of the slower line.

Moreover, if a line is saturated, the entire Tunnel doesn't work properly!

Warning
When double path is active the traffic is obviously duplicated: this could be very “dangerous” on pay per use
lines!

Example: there are two Abilis. Each one has two different Internet lines with static public IP addresses.

• First IP address of “Abilis 1” (ABILIS_CPX_1) : 217.1.1.1

• Second IP address of “Abilis 1” (ABILIS_CPX_1): 80.80.80.80

• Private IP address of “Abilis 1” (ABILIS_CPX_1): 192.168.0.254/24

• First IP address of “Abilis 2” (ABILIS_CPX_2): 217.2.2.2

• Second IP address of “Abilis 2” (ABILIS_CPX_2): 81.81.81.81

• Private IP address of “Abilis 2” (ABILIS_CPX_2): 192.168.1.254/24

First, add a new resource on both Abilis:

[17:09:11] ABILIS_CPX_1:a res:ip-5 subtype:aipt

COMMAND EXECUTED

[17:10:18] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000

511
Draft Tunneling proprietary protocols Draft

REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO

NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#

[17:09:19] ABILIS_CPX_2:a res:ip-5 subtype:aipt

COMMAND EXECUTED

[17:10:13] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO
LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#

Configuring MODE:EXT and PATH:DOUBLE new parameters will appear:

[17:18:28] ABILIS_CPX_1:s p ip-5 mode:ext path:double

COMMAND EXECUTED

[17:18:35] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500

512
Draft Tunneling proprietary protocols Draft

OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.000.254) REMIPADD:#
OUT-IP2:AUTO
LOCIPADD2:R-ID (192.168.000.254) REMIPADD2:#

[17:10:16] ABILIS_CPX_2:s p ip-5 mode:ext path:double

COMMAND EXECUTED

[17:18:40] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:NO
IPADD:000.000.000.000 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2100 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.254) REMIPADD:#
OUT-IP2:AUTO
LOCIPADD2:R-ID (192.168.001.254) REMIPADD2:#

Tip
The parameter PATH must be set ad the same value on both the CPX or the VPN will not work.

New parameters are:

• OUT-IP2: second output IP resource (AUTO will send the packets to the default gateway specified in IP routing table; it's
also possible to specify the ID of the outgoing IP resource).

• LOCIPADD2: second IP address that the local Abilis will use as “source address” for the path 2.

• REMIPADD2: second IP address of the remote Abilis for the path 2

Configuration of other parameters of both Abilis must mirror each other; see Section 36.3.1, “Abilis IP Tunnel over IP –
Extended Mode”.

[17:18:52] ABILIS_CPX_1:s p ip-5 descr:To_Abilis_2 neigh:192.168.1.254 mask:255.255.255.0 nat:insid

513
Draft Tunneling proprietary protocols Draft

remport:2105 locipadd:217.1.1.1 remipadd:217.2.2.2 locipadd2:80.80.80.80 remipadd2:81.81.81.81 out-

COMMAND EXECUTED

[17:33:17] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
OUT-IP2:3 GW2:#
LOCIPADD2:080.080.080.080 REMIPADD2:081.081.081.081

[17:18:55] ABILIS_CPX_2:s p ip-5 descr:To_Abilis_1 neigh:192.168.0.254 mask:255.255.255.0 nat:insid

remport:2105 locipadd:217.2.2.2 remipadd:217.1.1.1 locipadd2:81.81.81.81 remipadd2:80.80.80.80 out-

COMMAND EXECUTED

[17:35:08] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
OUT-IP2:3 GW2:#
LOCIPADD2:081.081.081.081 REMIPADD2:080.080.080.080

514
Draft Tunneling proprietary protocols Draft

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES. Also LMPX will be changed from YES to EXT: it can be set
to YES only for data protocols LAPB and LINK-FR (this VPN is based on UDP protocol).

Tip
Activation of Link Check protocol is recommended (LC:YES): the parameter must be set at the same value
on both Abilis or the VPN will not work.

Tip
Encryption of data packets has been activated (LCR:DATA) and the default Encryption Key has been used
(LCRKEY:DFT). Usage of encryption is useful to increase the security of data transmission.

Tip
Fragmentation has been activated (FRAG:FRF12 FRAGSIZE:800): it's recommended on VPN realized over
Internet lines.

[17:33:19] ABILIS_CPX_1:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[17:37:31] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.001.001.001 REMIPADD:217.002.002.002
OUT-IP2:3 GW2:#
LOCIPADD2:080.080.080.080 REMIPADD2:081.081.081.081

[17:35:10] ABILIS_CPX_2:save conf

VALIDATION IN PROGRESS ...

WARNING: RES:IP-5 Changed "LMPX" from YES to EXT
WARNING: RES:IP-5 Changed Abilis IP Tunnel "MPX" from NO to YES, because Link "LMPX" = EXT
VALIDATION SUCCESSFULLY EXECUTED

515
Draft Tunneling proprietary protocols Draft

SAVE EXECUTED

[17:44:27] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.254
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:EXT LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:DOUBLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:217.002.002.002 REMIPADD:217.001.001.001
OUT-IP2:3 GW2:#
LOCIPADD2:081.081.081.081 REMIPADD2:080.080.080.080

Now the configuration of the VPN is completed.

Tip
Interesting chapters:

Section 52.13.4, “How to configure a VPN tunnel with the “double path” option”;

Section 19.3, “IP Resources”.

36.4. Tunneling diagnostics and statistics

36.4.1. Tunneling diagnostics
To display the diagnostics of tunneling resource the following commands are used:

d d pv / d de pv Shows the current state of the Packet Voice resources.

d d ip / d de ip Shows the current state of the Aipt resources.

Some examples follow.

[11:09:16] ABILIS_CPX:d d pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis_2
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | READY | READY |
+--------+---------------+----------------------+----------------------+
- IP Tunnel ------------------------------------------------------------
STATE:READY MODE:EXT-CLIENT PATHS:SINGLE

516
Draft Tunneling proprietary protocols Draft

[11:09:16] ABILIS_CPX:d d ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ----------

To_Abilis_2
STATE:LINKREADY
OUTBUF:100 S-OUTBUF:500 CUR-OUTSP:256 OUTSP-TOUT:N/A
INBUF:0 S-INBUF:0 CUR-INSP:N/A INSP-TOUT:N/A
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | READY | READY |
+--------+---------------+----------------------+----------------------+
- IP Tunnel ------------------------------------------------------------
STATE:READY MODE:EXT PATHS:SINGLE

Here is the meaning of the most important parameters.

Global STATE Global current state [READY: the link is ready; DOWN: the link is down; ERR: software error].

P-Link STATE It reports the “P-Link” channel current state. P-Link stands for Permanent link and defines a permanent
connection toward the remote device.

Table 36.3. P-Link state

State Meaning Values reported into:

System Log, Debug
Log and LCD display
READY The P-Link is ready and usable. RD
LINK-NOT-PRESENT The value configured does not ln
refer to a valid or running port.
LINK-ERROR The value configured is a valid le
and running port, however
there are problems with other
parameters.
DOWN1 P-Link channel is down because d1
of a DOWN state in the lower
protocol driver.
DOWN2 P-Link channel is down because d2
the “link-check protocol”
detected a failure, while the state
in the lower protocol driver is
“UP”.
ERR Software error NA

S-Link STATE It reports the “S-Link” channel current state. S-Link stands for Switched link and defines a switched
connection toward the remote device. A switched connection is established only upon request.

517
Draft Tunneling proprietary protocols Draft

Table 36.4. S-Link state

518
Draft Tunneling proprietary protocols Draft

36.4.2. Tunneling statistics

The following commands are used to display the statistics of tunneling resource:

d s pv Shows the statistics of the Packet Voice resources.

d se pv Shows the statistics of the Packet Voice resources in extended mode.

d se pv-n path:m Shows the statistics of Packet Voice with id n about path number m[1,2] in extended mode.

d s ip Shows the statistics of the Aipt resources.

d se ip Shows the statistics of the Aipt resources in extended mode.

d se ip-n path:m Shows the statistics of the Aipt resource with id n about path number m[1,2] in extended mode.

Some examples follow.

[11:09:16] ABILIS_CPX:d s pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis_2
--- Cleared 14 days 23:14:00 ago, on 03/12/2007 at 03:22:29 ------------
- Link -----------------------------------------------------------------
PLINK-DN1:0 PLINK-DN2:6
SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0
RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 21550200| 25131315|FRM | 1430094| 1603480|
IP-CHR | 52462731| 65112357|IP-FRM | 858376| 943377|
BAD-SRC | 1| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
CLI-TOUT | 0| |CLI-REMAP | 0| |
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 0| 36| 0|
NOBUF | 0| 0| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 1125539 ( 98% ) | 151-200 | 67 ( 0% ) |
21- 50 | 18492 ( 1% ) | 201-300 | 55 ( 0% ) |
51-100 | 794 ( 0% ) | 301-600 | 34 ( 0% ) |
101-150 | 171 ( 0% ) | 601-xxx | 2 ( 0% ) |
------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d se pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis_2
--- Cleared 14 days 23:14:33 ago, on 03/12/2007 at 03:22:29 ------------
- Link -----------------------------------------------------------------
PLINK-DN1:0 PLINK-DN2:6
SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0
RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0| | | |

519
Draft Tunneling proprietary protocols Draft

V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
Tunnel payload
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 21550241| 25131358|FRM | 1430101| 1603487|
CHR-D | 0| 0|FRM-D | 0| 0|
CHR-V | 19841058| 23421755|FRM-V | 1145238| 1318538|
CHR-C | 1709183| 1709603|FRM-C | 284863| 284949|
------------------------------------------------------------------------
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 52462968| 65112638|IP-FRM | 858383| 943384|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 42777621| 53714769|IP-FRM-V | 573520| 658435|
IP-CHR-C | 9685347| 11397869|IP-FRM-C | 284863| 284949|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 1| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 58782024| 77481813|D-FRM-ENC | 0| 0|
V-CHR-OPT | 42777621| 54373204|V-FRM-ENC | 1145293| 1318538|
V-SAVED% | 27| 29|C-FRM-ENC | 284863| 284949|
V-FRM-OPT | 563888| 649165| | | |
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 0| 36| 0|
TOUT | 0| 9| 0|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
REORDERED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 0| 55| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 1125539 ( 98% ) | 151-200 | 67 ( 0% ) |
21- 50 | 18492 ( 1% ) | 201-300 | 55 ( 0% ) |
51-100 | 794 ( 0% ) | 301-600 | 34 ( 0% ) |
101-150 | 171 ( 0% ) | 601-xxx | 2 ( 0% ) |
------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d s ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ----------

To_Abilis_2
--- Cleared 068:00:55:32 ago, on 11/10/2007 at 01:43:14 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 545221183| 3126307834|
DG | 4520989| 5187958|ICMP | 18395| 5920|
TCP | 4449652| 5118319|UDP | 52942| 63719|
ESP | 0| 0|AH | 0| 0|
BRD | 0| |CAL | 0| 0|
RST | 0| |LONG | 0| 0|

520
Draft Tunneling proprietary protocols Draft

SHORT | 0| |LOST-LOOP | | 0|
LOST-BUF | 0| 1|LOST-OTH | | 0|
B-VER | 0| |B-ICMP | 0| |
B-LEN | 0| |NO-ROUTE | 0| |
B-FCS | 0| |UNK-PROT | 0| |
TTL-EXP | | 0|LOST-INC-DG| 207| |
LOST-ACC | 0| |B-ENC-HDR | 0| |
SLARP-FRM | 0| 0|SLARP-CHAR | 0| 0|
SLARP-KEEP | 0| 0|SLARP-DOWN | 0| |
IPP-DOWN | 0| |SP-LIM-OVFL| | 0|
------------------------------------------------------------------------
- Link -----------------------------------------------------------------
PLINK-DN1:0 PLINK-DN2:18
SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0
RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 118|SUCC-CALL | 0| 451|
TIME-CALL | 0| 312251| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 619979878| 2986895451|FRM | 11388167| 13914840|
IP-CHR | 902523376| 3345300110|IP-FRM | 8335792| 10811999|
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
CLI-TOUT | 0| |CLI-REMAP | 0| |
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 1938| 1808| 0|
NOBUF | 0| 0| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 6107220 ( 99% ) | 151-200 | 0 ( 0% ) |
21- 50 | 7160 ( 0% ) | 201-300 | 0 ( 0% ) |
51-100 | 64 ( 0% ) | 301-600 | 0 ( 0% ) |
101-150 | 0 ( 0% ) | 601-xxx | 0 ( 0% ) |
------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d se ip-5

RES:Ip-5 - IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ----------

To_Abilis_2
--- Cleared 068:00:56:19 ago, on 11/10/2007 at 01:43:14 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 0| 0|CHAR | 545221183| 3126307834|
DG | 4520989| 5187958|ICMP | 18395| 5920|
TCP | 4449652| 5118319|UDP | 52942| 63719|
ESP | 0| 0|AH | 0| 0|
BRD | 0| |CAL | 0| 0|
RST | 0| |LONG | 0| 0|
SHORT | 0| |LOST-LOOP | | 0|
LOST-BUF | 0| 1|LOST-OTH | | 0|
B-VER | 0| |B-ICMP | 0| |
B-LEN | 0| |NO-ROUTE | 0| |
B-FCS | 0| |UNK-PROT | 0| |
TTL-EXP | | 0|LOST-INC-DG| 207| |
LOST-ACC | 0| |B-ENC-HDR | 0| |
SLARP-FRM | 0| 0|SLARP-CHAR | 0| 0|
SLARP-KEEP | 0| 0|SLARP-DOWN | 0| |
IPP-DOWN | 0| |SP-LIM-OVFL| | 0|

521
Draft Tunneling proprietary protocols Draft

------------------------------------------------------------------------
- Link -----------------------------------------------------------------
PLINK-DN1:0 PLINK-DN2:18
SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0
RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 118|SUCC-CALL | 0| 451|
TIME-CALL | 0| 312251| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
Tunnel payload
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 619979938| 2986895511|FRM | 11388177| 13914850|
CHR-D | 503428075| 2869005065|FRM-D | 4137409| 6406663|
CHR-V | 109740277| 109806385|FRM-V | 6115512| 6118416|
CHR-C | 6811586| 8084061|FRM-C | 1135256| 1389771|
------------------------------------------------------------------------
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 902523716| 3345300450|IP-FRM | 8335802| 10812009|
IP-CHR-D | 631689372| 3067611618|IP-FRM-D | 4137426| 6406663|
IP-CHR-V | 232235590| 230691183|IP-FRM-V | 3063120| 3015575|
IP-CHR-C | 38598754| 46997649|IP-FRM-C | 1135256| 1389771|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 317674319| 317832529|D-FRM-ENC | 4137426| 6406663|
V-CHR-OPT | 232235590| 230691183|V-FRM-ENC | 6115639| 6118416|
V-SAVED% | 26| 27|C-FRM-ENC | 1135256| 1389771|
V-FRM-OPT | 2901720| 2985432| | | |
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 1938| 1808| 0|
TOUT | 1888| 968| 0|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
REORDERED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 17| 127| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 6107220 ( 99% ) | 151-200 | 0 ( 0% ) |
21- 50 | 7160 ( 0% ) | 201-300 | 0 ( 0% ) |
51-100 | 64 ( 0% ) | 301-600 | 0 ( 0% ) |
101-150 | 0 ( 0% ) | 601-xxx | 0 ( 0% ) |
------------------------------------------------------------------------

[10:53:25] ABILIS_CPX:d se pv-7 path:1

RES:Pv-7 - PV over IP (Abilis tunnel) (IP) ------------------------------------

To_Abilis_2

522
Draft Tunneling proprietary protocols Draft

--- Cleared 0 days 00:08:27 ago, on 16/12/2010 at 10:50:39 -------------

PATH:1
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 0| 6012|IP-FRM | 0| 167|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 0| 0|IP-FRM-V | 0| 0|
IP-CHR-C | 0| 6012|IP-FRM-C | 0| 167|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 0| 0|D-FRM-ENC | 0| 0|
V-CHR-OPT | 0| 0|V-FRM-ENC | 0| 0|
V-SAVED% | 0| 0|C-FRM-ENC | 0| 167|
V-FRM-OPT | 0| 0| | | |
V-RED-FM | | 0|V-RED-VOICE| | 0|
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
DUPLICATED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 0| 0| 0|
------------------------------------------------------------------------

[10:59:06] ABILIS_CPX:d se pv-7 path:2

RES:Pv-7 - PV over IP (Abilis tunnel) (IP) ------------------------------------

To_Abilis_2
--- Cleared 0 days 00:08:56 ago, on 16/12/2010 at 10:50:38 -------------
PATH:2
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 0| 6336|IP-FRM | 0| 176|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 0| 0|IP-FRM-V | 0| 0|
IP-CHR-C | 0| 6336|IP-FRM-C | 0| 176|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 0| 0|D-FRM-ENC | 0| 0|
V-CHR-OPT | 0| 0|V-FRM-ENC | 0| 0|
V-SAVED% | 0| 0|C-FRM-ENC | 0| 176|
V-FRM-OPT | 0| 0| | | |
V-RED-FM | | 0|V-RED-VOICE| | 0|

523
Draft Tunneling proprietary protocols Draft

-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|

NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
DUPLICATED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 0| 0| 0|
------------------------------------------------------------------------

[11:03:44] ABILIS_CPX:d se ip-9 path:1

RES:Ip-9 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

To_Abilis_2
--- Cleared 0 days 00:00:24 ago, on 16/12/2010 at 11:03:29 -------------
PATH:1
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 0| 216|IP-FRM | 0| 6|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 0| 0|IP-FRM-V | 0| 0|
IP-CHR-C | 0| 216|IP-FRM-C | 0| 6|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |
LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 0| 0|D-FRM-ENC | 0| 0|
V-CHR-OPT | 0| 0|V-FRM-ENC | 0| 0|
V-SAVED% | 0| 0|C-FRM-ENC | 0| 6|
V-FRM-OPT | 0| 0| | | |
V-RED-FM | | 0|V-RED-VOICE| | 0|
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
DUPLICATED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 0| 0| 0|
------------------------------------------------------------------------

[11:03:53] ABILIS_CPX:d se ip-9 path:2

RES:Ip-9 - IP over IP (Abilis tunnel) (AIPT) ----------------------------------

To_Abilis_2
--- Cleared 0 days 00:00:29 ago, on 16/12/2010 at 11:03:29 -------------
PATH:2
IP level counters (actual IP traffic)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
IP-CHR | 0| 288|IP-FRM | 0| 8|
IP-CHR-D | 0| 0|IP-FRM-D | 0| 0|
IP-CHR-V | 0| 0|IP-FRM-V | 0| 0|
IP-CHR-C | 0| 288|IP-FRM-C | 0| 8|
------------------------------------------------------------------------
Errors
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
LONG-D | 0| 0|LOST-D | 0| |
LONG-V | 0| 0|LOST-V | 0| |

524
Draft Tunneling proprietary protocols Draft

LONG-C | 0| 0|LOST-C | 0| |
BAD-SRC | 0| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
------------------------------------------------------------------------
Special counters for extended mode
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CLI-TOUT | 0| |CLI-REMAP | 0| |
V-CHR-NOPT | 0| 0|D-FRM-ENC | 0| 0|
V-CHR-OPT | 0| 0|V-FRM-ENC | 0| 0|
V-SAVED% | 0| 0|C-FRM-ENC | 0| 8|
V-FRM-OPT | 0| 0| | | |
V-RED-FM | | 0|V-RED-VOICE| | 0|
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
NOBUF | 0| 0| 0|
OUT-SEQ | 0| 0| 0|
DUPLICATED | 0| 0| 0|
BAD-FORM | 0| 0| |
RESYNC | 0| 0| 0|
------------------------------------------------------------------------

36.5. Appendix - LN2 parameter

It sets the maximum number of Link-Check “probes” retransmission.

If this counter runs over, it means “N2” Link-Check “probes” have been sent without receiving any acknowledge, the P-Link
or S-Link channel are declared out of service.

In the case it occurs on the P-Link channel, the communication will be activated on the S-Link channel, providing that it is
properly configured.

In the case it occurs with the S-Link channel, the connection is closed with the code 80 90 80 8B; if it happens three times
consecutively the port will be placed in the “STOPPED2” state, without being able to receive or make further calls.

To recover from the error it is necessary to execute the init res: command. If alarm detection was enabled, i.e. if LOG is set
with the “A” option, it is also possible to recover from the error with the alarm reset command or using the analogous menu
available on the LCD display of the front panel. If the communication cannot go on any longer either on P-Link or S-Link,
the upper level driver will be advised of the error and point out a “Level 1 Down”.

525
Draft Draft

Chapter 37. IPSEC - Internet Protocol

SECurity
Marco Bellesia
Luigi Demuro

Table of Contents
37.1. IPSEC - Internet Protocol SECurity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
37.2. IPSEC Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.1. Activating the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.2. IPSEC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
37.2.3. IPSEC tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
37.3. IKE Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.1. Activating the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
37.3.2. IKE resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
37.3.3. IKE tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
37.4. IPSEC and IKE diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.1. IPSEC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.2. Statistics of the IPSEC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
37.4.3. IKE diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.4.4. Statistics of the IKE resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
37.5. Example of IPSEC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
37.5.1. Activating IPSEC parameter on the desired IP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
37.5.2. Configuration of the Host connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
37.5.3. Configuration of the Client connections table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
37.5.4. Configuration of the Pre-shard Key table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
37.5.5. Outgoing IP resource for IPSEC packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
37.6. Appendix - IPSEC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

37.1. IPSEC - Internet Protocol SECurity

Abilis IPSEC resource supports the creation of a Security Association (SA) using IKE mode.

It uses a Diffie-Hellman key echange to set up a shared session secret from wich cryptographic keys are derived; a pre-shared
key is used to mutually authenticate the communicating parties.

An IPSEC VPN is managed through the following resources/tables:

• IPSEC resource;

• IPSEC tables (Security Associations table, Policy tables);

• IKE resource;

• IKE tables (Host connections table, Client connections table, Pre-Shared key table);

Tip
Refer to chapter Section 37.6, “Appendix - IPSEC protocol” to have more information about IPSEC
protocol.

526
Draft IPSEC - Internet Protocol SECurity Draft

37.2. IPSEC Resource

37.2.1. Activating the IPSEC resource
Add the resource to the Abilis system with the following command:

[15:50:39] ABILIS_CPX:a res:ipsec

RES:IPSEC ALREADY EXISTS

The IPSEC resource may already exist in the system, but may not yet be active: set it active with the command:

[15:50:43] ABILIS_CPX:s act res:ipsec

COMMAND EXECUTED

Caution
After adding or setting the IPSEC active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p ipsec act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p ipsec

RES:Ipsec - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

Run DESCR:IP_Security_Protocol
LOG:DS ACT:YES MODE:IKE mxps:2048 IN-CHK:YES TTL:COPY
ECN:NOCARE DF:CLEAR TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1334

Warning
To activate IPSEC reource 16 MB of free RAM are requested. Verify it with the command d i; for example:

[17:39:21] ABILIS_CPX:_d i

Abilis CPX - Ver. 7.0.3/STD - 24/11/2010 - Build 3357.17 - 24/11/2010

(c) 1994/2010 - Abilis

Free/Total Memory: 171,796,256/268,435,456 Largest Block: 171,796,256

Free/Used/Total HD/CF space (in KB): 89,572/32,778/122,350

37.2.2. IPSEC resource parameters

Use the following command to display the parameters of the resource; the below command shows the meaning parameters.

[09:58:41] ABILIS_CPX:d p ipsec

RES:IpSec ---------------------------------------------------------------------
Run DESCR:IP_Security_Protocol
LOG:DS ACT:YES MODE:IKE mxps:2048 IN-CHK:YES TTL:COPY
ECN:FORBIDDEN DF:CLEAR TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1334

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime IPSEC activation/deactivation.

MODE Working mode of IPSEC port [MANUAL; IKE].

mxps Maximum length of IP datagram which can be processed.

527
Draft IPSEC - Internet Protocol SECurity Draft

IN-CHK Inbound policy check flag.

TTL Specifies the Time-To-Live field for the outer IP header in tunnel mode [COPY: TTL field will be
copied from the inner IP header to the tunnel one; 1..255].

ECN Specifies ECN (Explicit Congestion Notification) consideration mode on IPSEC tunnels in tunnel
mode. ECN is an experimental addition to the IP architecture that provides notification of onset of
congestion to delay- or loss-sensitive applications [ALLOWED; FORBIDDEN; NOCARE].

DF DF (Don't Fragment) bit manipulation in tunnel mode during encapsulation [CLEAR: clear DF bit on
outer IP header; SET: set DF bit on outer IP header; COPY: copy DF bit from inner to outer IP header].

TCP-MSS-CLAMP Activates/deactivates the TCP MSS (Maximum Segment Size) Clamping procedure used to control the
size of TCP segments.

TCP-MSS-VALUE TCP MSS clamping value.

The command that allows the configuration of the resource to be modified has the following syntax:

s p ipsec par:val...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ipsec; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

37.2.3. IPSEC tables

A particular SA may protect ip datagrams using only one of security protocol between: AH or ESP.

Enhanced security policy may be implemented using multiple SAs.

The term “security association bundle” or “SA bundle” is applied to a sequence of SAs through which traffic must be
processed to satisfy a security policy. The order of the sequence is defined by the policy.

37.2.3.1. Security Associations table

This table is used only when mode parameter is set to MANUAL.

The Security Associations table can store up to 256 entries, indexed starting from 0 up to 255.

Changes made in the table are activated by executing the command init res:ipsec.

Commands for handling Security Associations table are:

d/a/c/s ipsec sa:"id-num" [par:val...]

The d ipsec sa ? command displays the meaning of parameters.

[11:46:52] ABILIS_CPX:d ipsec sa

-------------------------------------------------------------------------------
SA: NAME: SPI: SRC-IP: PROT: AUTH: CIPHER:
BUNDLE: TUNNEL: IPRES: SIDE: DST-IP: AUTHKEY: ENCKEY:
-------------------------------------------------------------------------------
*** NO IPSEC SECURITY ASSOCIATIONS DEFINED ***

Meaning of the most important parameters:

SPI Specifies Security Parameter Index (SPI).

BUNDLE Number of SA bundle group.

SRC-IP Source IP address for the Security Association.

DST-IP Destination IP address for the Security Association.

PROT Protocol for this security association record [AH, ESP].

528
Draft IPSEC - Internet Protocol SECurity Draft

AUTH authentication method for the AH or ESP protocols [NONE, MD5, SHA].

AUTHKEY Authentication key for the AH or ESP protocols (only for AUTH not equal to NONE). ASCII printable string. For
MD5 authentication key: exactly 16 characters are required. For SHA authentication key: exactly 20 characters
are required.

CIPHER Encryption algorithm for the ESP protocol [NONE, DES, 3DES, IDEA, CAST, BLOWFISH, AES128, AES192,
AES256].

ENCKEY Encryption key for the ESP protocol (only for PROT:ESP and CIPHER not equal to NONE). For DES encryption
key: exactly 8 characters are required. For IDEA, CAST, BLOWFISH, AES128 encryption key: exactly 16
characters. For 3DES, AES192 encryption key: exactly 24 characters are required. For AES256 encryption key:
exactly 32 characters are required.

TUNNEL Tunnel mode flag.

IPRES Tunnel IP resource.

SIDE Tunnel side [NONE, AUTO, INSIDE, OUTSIDE, VPN, DMZ].

37.2.3.2. Policy table

This table is used only when mode parameter is set to MANUAL.

The Policy table can store up to 256 entries, indexed starting from 0 up to 255.

Changes made in the table are activated by executing the command init res:ipsec.

Commands for handling Policy table are:

d/a/c/s ipsec policy:"id-num" [par:val...]

By typing d ipsec policy ?, it is possible to display the meaning of the parameters.

[11:46:54] ABILIS_CPX:d ipsec policy

-------------------------------------------------------------------------------
POLICY: NAME: NET-SRC: PORT-SRC:
DIR: BUNDLE: RULE: NET-DST: PORT-DST:
-------------------------------------------------------------------------------
*** NO IPSEC SECURITY POLICIES DEFINED ***

Meaning of the most important parameters:

DIR Direction for the policy record [OUT: outbound direction (used as packet filter); IN: inbound direction (used
for inbound policy check)].

BUNDLE Number of SA bundle group associated with this policy record.

RULE Rule for the policy record [BYPASS: packet will be bypassed by IPSEC (outbound direction only); DROP:
packet will be dropped by IPSEC (outbound direction only); IPSEC: packet will be processed by IPSEC].

NET-SRC Source subnet address and mask in Slash Notation.

NET-DST Destination subnet address and mask in Slash Notation.

PROT-SRC Source port of the upper protocol (TCP, UDP).

PROT-DST Destination port of the upper protocol (TCP, UDP).

37.3. IKE Resource

37.3.1. Activating the IKE resource
Add the resource to the Abilis system with the following command:

[15:50:39] ABILIS_CPX:a res:ike

RES:IKE ALREADY EXISTS

529
Draft IPSEC - Internet Protocol SECurity Draft

The IKE resource may already exist in the system, but may not yet be active: set it active with the command:

[15:50:43] ABILIS_CPX:s act res:ike

COMMAND EXECUTED

Caution
After adding or setting the IKE active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p ike act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p ike

RES:Ike - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------

------------------------------------------------------------------------
DESCR:Internet_Keys_Exchange_Protocol
LOG:DS ACT:NO mxps:2048 max-hosts:16
TOS:0-N NRTY:3 TB:10
NATT:AUTO NATT-N-IKE:YES NATT-PF:YES NATT-KA:20
MODE-CFG-DNS:#
WDIR:C:\APP\IKE\
ASN1-DN-SYS:

37.3.2. IKE resource parameters

Use the following command to display the parameters of the resource. The d p ike ? command shows the meaning of
parameters.

[09:58:41] ABILIS_CPX:d p ike

RES:Ike -----------------------------------------------------------------------
Run DESCR:Internet_Keys_Exchange_Protocol
LOG:DS ACT:YES mxps:2048 max-hosts:16
TOS:0-N NRTY:3 TB:10
NATT:AUTO NATT-N-IKE:YES NATT-PF:YES NATT-KA:20
MODE-CFG-DNS:#
WDIR:C:\APP\IKE\
ASN1-DN-SYS:

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime IPSEC activation/deactivation.

mxps Maximum length of UDP datagram that can be processed.

max-hosts Maximum number of simultaneous clients [1..128].

TOS Type Of Service octet or Differentiated Services Field (DS):

-' p-t', i.e. PRECEDENCE and TOS values, where 'p' can be [0..7] and 't' can be [N=None, D=Min.
Delay, T=Max. Throughput, R=Max. Reliability, C=Min. Monetary Cost]

- 'bbbbbb', i.e. DS value bit by bit, where 'b' can be [0, 1].

NRTY Maximum number of packet retransmissions.

TB Retransmission delay.

WDIR Working directory; it cannot be empty (physical full path in DOS notation).

NATT NAT traversal activation. If NAT traversal is enabled, IPsec AH algorithm must be disabled.

530
Draft IPSEC - Internet Protocol SECurity Draft

NATT-N-IKE NAT traversal NON-IKE marker activation.

NATT-PF NAT traversal NAT traversal port floating activation.

NATT-KA NAT traversal keep-alive timer.

MODE-CFG-DNS IP address of DNS server for the MODE-CFG mode [#, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x].

ASN1-DN-SYS Specifies system Distinguished Name.

The command that allows the configuration of the resource to be modified has the following syntax:

s p ike par:val...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:ike;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

37.3.3. IKE tables

IKE tables define the control and cryptographic characteristics of the Hosts and Clients:

• the Host connections table defines the mechanisms to establish the Security Association and the encryption algorithms;

• the Client connections table defines the characteristics and the security parameters for a single IPSec VPN;

• the Preshared Keys Table contains the secret key for mutual authentication.

37.3.3.1. Host connections table

The Host connections table can store up to 128 entries, indexed starting from 0 up to 127.

Changes made in the table are activated by executing the command init res:ike.

Commands for handling Host connections table are:

d/a/c/s ike host:"id-num" [par:val...]

The d ike host ? command displays the meaning of parameters.

[18:47:07] ABILIS_CPX:d ike host

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
HOST: NAME: LOC-IP: NATT: XAUTH:
AUTH: HASH: DH: CIPHER: REM-IP: SIDE: MODE-CFG:
XAUTH-USER: XAUTH-PWD:
-------------------------------------------------------------------------------
0 Agent_01 080.080.080.080 SYS NO
PSK MD5 MODP1024 3DES * INSIDE NO

-------------------------------------------------------------------------------

[20:33:37] ABILIS_CPX:d ike host:0

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
------------+------------------------------------------------------------------
HOST: 0
NAME: Agent_01
LOC-IP: 080.080.080.080
REM-IP: *
NATT: SYS
AUTH: PSK

531
Draft IPSEC - Internet Protocol SECurity Draft

HASH: MD5
DH: MODP1024
CIPHER: 3DES
SIDE: INSIDE
XAUTH: NO
XAUTH-USER:
XAUTH-PWD:
MODE-CFG: NO
KEYING-TRIES: 3
LIFE-TIME: 3600
DPD-ENABLE: NO
DPD-DELAY: 30
DPD-TIMEOUT: 120
DPD-ACTION: STOP
ID-TYPE: IP
IP: 080.080.080.080
PEER-ID-TYPE: IP
PEER-IP: 192.168.101.001
-------------------------------------------------------------------------------

Meaning of the most important parameters:

LOC-IP IP address that IKE will use as source address.

REM-IP Peer's IP address for this connection.

NATT NAT traversal activation [SYS, NO, YES, AUTO]

AUTH Authentication method for the ISAKMP/OAKLEY negotiation [PSK, RSASIG].

HASH Hash algorithm for the ISAKMP/OAKLEY negotiation [MD5, SHA].

DH Diffi-Hellman group for the ISAKMP/OAKLEY negotiation [MODP768, MODP1024, MODP1536].

CIPHER Encryption algorithm for the ISAKMP/OAKLEY negotiation [DES, 3DES, IDEA, CAST, BLOWFISH,
AES128, AES192, AES256].

SIDE NAT side assigned to the tunnel [NONE, AUTO, INSIDE, OUTSIDE, VPN, DMZ].

XAUTH Type of XAUTH [NO, SERVER, CLIENT] (for cisco compatibility).

XAUTH-USER XAUTH user name for host connection.

XAUTH-PWD XAUTH password for host connection.

MODE-CFG Type of Mode config [NO, SRV-PUSH, SRV-REQUEST] (for iphone compatibility).

KEYING-TRIES Specifies how many times IKE should try to negotiate an SA, either for the first time or for rekeying
[INFINITE, 1..100].

LIFE-TIME Specifies how long IKE will propose that an ISAKMP SA be allowed to live. The range is [600..86400]
sec.

DPD-ENABLE Enables/disables DPD (Dead peer detection) procedure support (the function must necessarily supported
by the IPSec client) [NO, YES]. DPD is a keepalive mechanism that enables the router to detect when the
connection between the router and a remote IPSec peer has been lost. DPD enables the router to reclaim
resources and to optionally redirect traffic to an alternate failover destination. If DPD is not enabled, the
traffic continues to be sent to the unavailable destination.

DPD-DELAY Time interval between DPD checks. It must be lower than DPD-TIMEOUT.

DPD-TIMEOUT Time interval of missing DPD replies after which peer is declared dead. It must be greater then DPD-
DELAY.

DPD-ACTION Action executed upon peer is detected dead [STOP, RESTART].

ID-TYPE Type of local host for the connection [AUTO: local ID will be set automatically in run-time as local
IP address; IP: local ID is local IP address; FQDN: local ID is fully-qualified domain name (FQDN);
USER-FQDN: local ID is fully-qualified user domain name (FQDN)].

532
Draft IPSEC - Internet Protocol SECurity Draft

IP Local ID IP address (only for ID-TYPE not equal to AUTO).

FQDN Local ID fully-qualified domain name (FQDN) or user-FQDN.

PEER-ID-TYPE Peer's ID type [AUTO, IP, FQDN, USER-FQDN].

PEER-IP Peer's ID IP address (only for PEER-ID-TYPE not equal to AUTO).

PEER-FQDN Peer's ID fully-qualified domain name (FQDN) or user-FQDN.

Note
The FQDN and PEER-FQDN parameters are used as password and they do not have necessarily be referred
to existing domains.

37.3.3.2. Client connections table

The Client connections table can store up to 128 entries, indexed starting from 0 up to 127.

Changes made in the table are activated by executing the command init res:ike.

Commands for handling Client connections table are:

d/a/c/s ike cli:"id-num" [par:val...]

The d ike cli ? command displays the meaning of the parameters.

[18:47:32] ABILIS_CPX:d ike cli

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
CLI: NAME: HOST-ID: RULE: LIFE-TIME: PFS:
ESP: ESP-CIPHER: ESP-AUTH: PASSIVE: PERMANENT: NET-LOC:
AH: AH-AUTH: TUNNEL: NET-REM:
MODE-CFG-DNS:
-------------------------------------------------------------------------------
0 Agent_Cli1 0 IPSEC 28800 YES
YES 3DES MD5 YES YES 192.168.001.000/24
NO MD5 YES 192.168.101.001/32
SYS
-------------------------------------------------------------------------------

[20:46:06] ABILIS_CPX:d ike cli:0

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
------------+------------------------------------------------------------------
CLI: 0
NAME: Agent_Cli1
HOST-ID: 0
RULE: IPSEC
PASSIVE: YES
PERMANENT: YES
TUNNEL: YES
ESP: YES
ESP-CIPHER: 3DES
ESP-AUTH: MD5
AH: NO
AH-AUTH: MD5
LIFE-TIME: 28800
PFS: YES
NET-LOC: 192.168.001.000/24
NET-REM: 192.168.101.001/32
MODE-CFG-DNS: SYS
-------------------------------------------------------------------------------

533
Draft IPSEC - Internet Protocol SECurity Draft

Meaning of the most important parameters:

RULE Rule for this client connection [BYPASS, DROP, IPSEC]

PASSIVE Mode of negotiation. [NO: negotiation can be started as initiator and as responder; YES: negotiation can
be started as responder only; it is useful for a server]. If related host LOC-IP is set to an “IP resource”,
PASSIVE must be forced to NO; if related host REM-IP is set to *, PASSIVE must be forced to YES,
even if LOC-IP is set to an “IP resource” .

PERMANENT Mode of negotiation [NO: after driver starting or after init command (re-)negotiation will not be started
automatically as initiator; YES: after driver starting or after init command (re-)negotiation of this
connection will be started automatically as initiator].

TUNNEL Mode of IPSEC negotiation [NO: Transport mode, YES: Tunnel mode].

ESP Enables/disables IPSEC ESP protocol .

ESP-CIPHER Encryption algorithm for IPSEC ESP protocol [NONE, DES, 3DES, IDEA, CAST, BLOWFISH, AES128,
AES192, AES256].

ESP-AUTH Authentication algorithm for IPSEC ESP protocol [NONE, MD5, SHA].

AH Enables/disables IPSEC AH protocol.

AH-AUTH Authentication algorithm for IPSEC AH protocol [MD5, SHA].

LIFE-TIME Specifies how long IKE will propose that an IPSEC SA be allowed to live. The range is [600..86400]
sec.

PFS Enables/disables Perfect Forward Secrecy. PFS provides additional security by means of a Diffie-
Hellman shared secret value. With PFS, if one key is compromised, previous and subsequent keys are
secure because they are not derived from previous keys.

NET-LOC Local subnet address and mask in Slash Notation.

NET-REM Remote subnet address and mask in Slash Notation.

MODE-CFG-DNS IP address of DNS server for the MODE-CFG mode.

Note
More clients can be referred to a same IKE Host.

37.3.3.3. Pre-shared keys table

The Pre-shared keys table can store up to 64 entries, indexed starting from 0 up to 127.

Changes made in the table are activated by executing the command init res:ike.

Commands for handling Host connections table are:

d/a/c/s ike psk:"id-num" [par:val...]

The d ike psk ? command displays the meaning of parameters.

[18:47:53] ABILIS_CPX:d ike psk

-------------------------------------------------------------------------------
PSK: KEY: ID-TYPE: IP: FQDN:
-------------------------------------------------------------------------------
1 ******** ANONYMOUS

Meaning of the most important parameters:

KEY Specifies preshared key for this record.

ID-TYPE Type of peer ID [UNDEF, IP, FQDN, USER-FQDN, ANONYMOUS].

IP Remote IP address.

FQDN Remote fully-qualified domain name (FQDN) or user-FQDN.

534
Draft IPSEC - Internet Protocol SECurity Draft

37.4. IPSEC and IKE diagnostics and statistics

37.4.1. IPSEC diagnostics
To display the diagnostics of the IPSEC resource the following commands are used:

d d ipsec / d de ipsec Shows the IPSEC resource diagnostics (the state of the resource, the working mode,
the inbound policy check flag, the inbound security policies, etc..) and the IPSEC
Security Associations diagnostics (the number of bundle of Security Association
record, the state of Security Association record, etc..).

[11:42:10] ABILIS_CPX:d d ipsec

RES:IpSec ---------------------------------------------------------------------
IP_Security_Protocol
STATE:ACTIVE MODE:IKE IN-CHK:YES
POLICY-IN :1 SA-IN :1 SA-BND-IN :1
POLICY-OUT:1 SA-OUT:1 SA-BND-OUT:1
- Security Associations diagnostics: -----------------------------------
SA Bundle State SPI SrcIp Auth SoftTime
Prot Tunnel DstIp Cipher HardTime
------------------------------------------------------------------------
0 0 MATURE C4DCB36E 192.168.006.002 MD5 INFINITE
ESP YES 192.168.006.001 3DES INFINITE
------------------------------------------------------------------------
1 1 MATURE 1969FC22 192.168.006.001 MD5 INFINITE
ESP YES 192.168.006.002 3DES INFINITE
------------------------------------------------------------------------

37.4.2. Statistics of the IPSEC resource

To display the statistics of the IPSEC resource the following commands are used:

d s ipsec Shows the IPSEC resource statistics such as the total number of IP frames received/sent by IPSEC resource
from/to IP, the total number of characters received/sent by IPSEC port from/to IP, the total number of
bypassed incoming/outgoing IKE packets, etc..

d se ipsec Shows the IPSEC resource statistics and the IPsec Security Associations statistics (the total number of
incoming/outgoing characters processed by Security Association, the total number of incoming/outgoing IP
frames processed by Security Association, etc..).

[11:42:10] ABILIS_CPX:d s ipsec

RES:IpSec ---------------------------------------------------------------------
IP_Security_Protocol
--- Cleared 0 days 01:53:11 ago, on 05/12/2010 at 11:18:42 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FRM | 1922| 4729|CHR | 70005| 455647|
FRM-OK | 9| 0|CHR-OK | 1912| 0|
FRM-DROP | 0| 0|CHR-DROP | 0| 0|
FRM-BYPASS | 1913| 4729|CHR-BYPASS | 68093| 455647|
------------------------------------------------------------------------
FRM-IKE | 40| 40|NATT-KA | 0| 0|
NO-POLICY | 0| 4707|LONG | 0| 0|
BAD-SA | 0| 0|NO-SA | 0| 0|
BAD-FMT | 0| 0|AUTH-FAIL | 0| |
BAD-CBLK | 0| |BAD-CHK | 0| |
REP-CHK | 0| 0|BAD-ECN | 0| |
------------------------------------------------------------------------

[11:42:10] ABILIS_CPX:d se ipsec

RES:IpSec ---------------------------------------------------------------------

535
Draft IPSEC - Internet Protocol SECurity Draft

IP_Security_Protocol
--- Cleared 0 days 01:53:43 ago, on 05/12/2010 at 11:18:42 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FRM | 1934| 4760|CHR | 70648| 459620|
FRM-OK | 10| 0|CHR-OK | 2192| 0|
FRM-DROP | 0| 0|CHR-DROP | 0| 0|
FRM-BYPASS | 1924| 4760|CHR-BYPASS | 68456| 459620|
------------------------------------------------------------------------
FRM-IKE | 40| 40|NATT-KA | 0| 0|
NO-POLICY | 0| 4738|LONG | 0| 0|
BAD-SA | 0| 0|NO-SA | 0| 0|
BAD-FMT | 0| 0|AUTH-FAIL | 0| |
BAD-CBLK | 0| |BAD-CHK | 0| |
REP-CHK | 0| 0|BAD-ECN | 0| |
------------------------------------------------------------------------
- Security Associations statistics: ------------------------------------
SA:3 CHR:0 AUTH-FAIL:0 BAD-CBLK:0
FRM:0 REPLAY-CHK:0 BAD-ECN:0
------------------------------------------------------------------------
SA:2 CHR:560 AUTH-FAIL:0 BAD-CBLK:0
FRM:2 REPLAY-CHK:0 BAD-ECN:0
------------------------------------------------------------------------

37.4.3. IKE diagnostics

To display the diagnostics of the IKE resource the following commands are used:

d d ike / d de ike Shows diagnostic information such as the current state of the IKE resource and the
IPSEC resource, the current number of ISAKMP and IPSEC Security Associations, the
local and remote IP address-port, etc...

[11:42:10] ABILIS_CPX:d d ike

RES:Ike -----------------------------------------------------------------------
Internet_Keys_Exchange_Protocol
IKE-STATE:ACTIVE IPSEC-STATE:ACTIVE
CUR-MAX-HOSTS:16 CUR-HOSTS:2
ISAKMP-SA:0 ISAKMP-SA-EST:0 IPSEC-SA:0 IPSEC-SA-EST:0
- Security Associations diagnostics: -----------------------------------
SerialNo Name Type Side
LocIp-LocPort LocNet/LocMask State ReplaceTime
RemIp-RemPort RemNet/RemMask Pending ExpiryTime
------------------------------------------------------------------------
1 IPsec RESPONDER
192.168.006.001/500 192.168.006.001/32 QUICK-R2 3422
192.168.006.002/500 192.168.006.002/32 0 3542
------------------------------------------------------------------------
2 ISAKMP RESPONDER
192.168.006.001/500 000.000.000.000/00 MAIN-R3 3420
192.168.006.002/500 000.000.000.000/00 0 3540
------------------------------------------------------------------------

37.4.4. Statistics of the IKE resource

To display the statistics of the IKE resource the following commands are used:

d s ike / d se ike Shows statistic information such as the total number of characters received/sent by IKE
resource from/to UDP, the total number of UDP datagrams received/sent by IKE port
from/to UDP, the total number of lost incoming UDP datagrams because buffer is full,
etc..

[11:42:10] ABILIS_CPX:d se ike

536
Draft IPSEC - Internet Protocol SECurity Draft

RES:Ike -----------------------------------------------------------------------
Internet_Keys_Exchange_Protocol
--- Cleared 7 days 05:47:11 ago, on 22/12/2007 at 16:36:57 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 13472| 12716|LONG | 0| 0|
FRM | 87| 89|BAD-FMT | 0| |
FRM-LOST | 0| |DUPLICATED | 0| |
------------------------------------------------------------------------
-----------|--ISAKMP---|---IPSEC---|
SA-R | 14| 19|
SA-I | 0| 0|
SA-EST-R | 14| 19|
SA-EST-I | 0| 0|
AUTH-FAIL | 0| 0|
NO-PROP | 0| 0|
------------------------------------------------------------------------

37.5. Example of IPSEC configuration

Consider an IPSEC VPN in TUNNEL mode that uses IKE protocol and an ANONYMOUS access, as shown in the following
figure.

Figure 37.1. IPSEC configuration example

Caution
The IPSEC connection works ONLY if the LAN, where the PC client is connected to, is different from the
LAN of Abilis (e.g. in the previous case if the PC client IP address is belonging to the 192.168.1.0/24 the
IPSEC connection doesn't work!).

Tip
Interesting chapters:

Section 52.11.1, “How to configure a RAS using IPSEC VPN server”;

537
Draft IPSEC - Internet Protocol SECurity Draft

Section 52.11.2, “How to configure a RAS using IPSEC VPN server with iPHONE”.

37.5.1. Activating IPSEC parameter on the desired IP resource

Set the IPSEC parameter to YES in the IP resource in which you want to encapsulate IPSEC packets (outgoing traffic). If
you want to use the IP-2 resource (ADSL line), type:

[15:54:12] ABILIS_CPX:s p ip-2 ipsec:yes

COMMAND EXECUTED

[16:08:53] ABILIS_CPX:d p ip-2

RES:Ip-2 - IP over PPP (PPP) --------------------------------------------------

Run DESCR:ADSL_line
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Adsl-1
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:YES VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RFC2364-VCMUX RADIUS:NO
VPI:8 VCI:35
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO
maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:abilis
PASSWORD:******** LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE
REPEAT:0
RES:Adsl-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------
------------------------------------------------------------------------
DESCR:
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:1 usb-tx-bufsize:3200

Caution
To activate the changes made, execute the initialization command init res:ip-2.

37.5.2. Configuration of the Host connections table

Add an IKE Host:

[16:06:36] ABILIS_CPX:a ike host:0 name:user_1

COMMAND EXECUTED

Give the host the following characteristics:

• local IP used for the VPN: 81.81.81.81;

• ip resource used for the VPN: ip-2 (ADSL line);

• no verify of the client's IP address that tries to open the VPN;

• authentication method: PSK;

538
Draft IPSEC - Internet Protocol SECurity Draft

• hash algorithm: MD5;

• Diffie-Hellman group: MODP1024;

• encryption algorithm: 3DES;

• NAT type: inside;

• Fully Qualified Name identification for the local and remote side.

[16:16:33] ABILIS_CPX:s ike host:0 loc-ip:81.81.81.81 rem-ip:*

COMMAND EXECUTED

[16:16:59] ABILIS_CPX:s ike host:0 auth:PSK hash:MD5 dh:MODP1024 cipher:3DES

COMMAND EXECUTED

[16:17:09] ABILIS_CPX:s ike host:0 side:inside id-type:fqdn fqdn:www.ufficio.it

COMMAND EXECUTED

[16:17:21] ABILIS_CPX:s ike host:0 peer-id-type:fqdn peer-fqdn:www.casa.it

COMMAND EXECUTED

[17:55:47] ABILIS_CPX:d ike host:0

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
------------+------------------------------------------------------------------
HOST: 0
NAME: user_1
LOC-IP: 081.081.081.081
REM-IP: *
NATT: SYS
AUTH: PSK
HASH: MD5
DH: MODP1024
CIPHER: 3DES
SIDE: INSIDE
XAUTH: NO
XAUTH-USER:
XAUTH-PWD:
MODE-CFG: NO
KEYING-TRIES: 3
LIFE-TIME: 3600
DPD-ENABLE: NO
DPD-DELAY: 30
DPD-TIMEOUT: 120
DPD-ACTION: STOP
ID-TYPE: FQDN
FQDN: www.ufficio.it
PEER-ID-TYPE: FQDN
PEER-FQDN: www.casa.it
-------------------------------------------------------------------------------

Caution
To activate the changes made, execute the initialization command init res:ike.

37.5.3. Configuration of the Client connections table

Add an IKE client:

539
Draft IPSEC - Internet Protocol SECurity Draft

[16:29:57] ABILIS_CPX:a ike cli:0 name:user_1

COMMAND EXECUTED

Give the host the following characteristics:

• IPSEC negotiation: tunnel mode;

• ip address of the server: 192.168.1.0/24;

• ip address of the client: 192.168.200.1/32.

[16:30:15] ABILIS_CPX:s ike cli:0 host-id:0 tunnel:yes

COMMAND EXECUTED

[16:30:33] ABILIS_CPX:s ike cli:0 net-loc:192.168.1.0/24 net-rem:192.168.200.1/32

COMMAND EXECUTED

[16:40:16] ABILIS_CPX:d ike cli:0

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Parameter: | Value:
------------+------------------------------------------------------------------
CLI: 0
NAME: user_1
HOST-ID: 0
RULE: IPSEC
PASSIVE: YES
PERMANENT: YES
TUNNEL: YES
ESP: YES
ESP-CIPHER: 3DES
ESP-AUTH: MD5
AH: NO
AH-AUTH: MD5
LIFE-TIME: 28800
PFS: YES
NET-LOC: 192.168.001.000/24
NET-REM: 192.168.200.001/32
MODE-CFG-DNS: SYS
-------------------------------------------------------------------------------

Caution
To activate the changes made, execute the initialization command init res:ike.

37.5.4. Configuration of the Pre-shard Key table

If a PSK authentication is set in the IKE Host table ,you must define a secret key for mutual authentication. In our example
type for an ANONYMOUS PSK:

[16:51:32] ABILIS_CPX:a ike psk:0 key:shared_key id-type:anonymous

COMMAND EXECUTED

[16:52:11] ABILIS_CPX:d ike psk

or
- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

-------------------------------------------------------------------------------
PSK: KEY: ID-TYPE: IP: FQDN:

540
Draft IPSEC - Internet Protocol SECurity Draft

-------------------------------------------------------------------------------
0 ******** ANONYMOUS

Caution
To activate the changes made, execute the initialization command init res:ike.

37.5.5. Outgoing IP resource for IPSEC packets

Ensuring that outgoing IPSEC packets are routed toward appropriate resource is important.

Add a static route for remote network (in our situation only for host 192.168.200.1/32) towards IP-2 resource (specifying
eventually the gateway).

[16:51:32] ABILIS_CPX:a ipr net:192.168.200.1/32 ip:2

COMMAND EXECUTED

[16:52:17] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 081.081.081.081/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|S| | | 192.168.200.001/32 | 255.255.255.255 | | 2| 1|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 2| 1|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

37.6. Appendix - IPSEC protocol

Internet Protocol SECurity1 (IPSEC) is a suite of protocols for protecting communications over IP networks by authenticating
and/or encrypting each IP packet in a data stream. The set of security services offered includes:

• access control;
• connectionless integrity;
• data origin authentication;
• protection against replays;
• confidentiality (encryption);
• limited traffic flow confidentiality.

These services are provided at the network layer (layer 3 of the OSI model), offering protection for IP and/or upper layer
protocols. IPsec also includes protocols for cryptographic key estabilishment such as Internet Key Exchange2 (IKE).

IPsec uses two protocols that can be applied either separately or together to provide a desired set of security services:

• Authentication Header (AH): protects the IP packet header from third party interference and spoofing, by computing a
cryptographic checksum and hashing of the IP packet header fields with a secure hashing function. This is then followed
by an additional header that contains the hash, to allow the information in the packet to be authenticated.

• Encapsulating Security Payload (ESP): protects the IP packet data from third party interference, by encrypting the
contents using symmetric cryptography algorithms.

All implementations of AH and ESP must support the concept of a Security Association (SA). SA is simply the bundle of
algorithms and parameters (such as keys) that is being used to encrypt a particular flow. Two types of SAs are defined:

• Transport mode: only the payload of the original IP packet is encrypted because IPsec header appears immediately
after the IP header and before higher layer protocols (e.g., TCP or UDP). Transport mode is used for host-to-host
communications.

1
http://en.wikipedia.org/wiki/IPsec
2
http://en.wikipedia.org/wiki/IKE

541
Draft IPSEC - Internet Protocol SECurity Draft

• Tunnel mode: the entire IP packet is encrypted and it must be encapsulated into a new IP packet for routing to work.
Tunnel mode is used for network-to-network communications (secure tunnels between routers) or host-to-network and
host-to-host communications over the Internet.

542
Draft Draft

Chapter 38. POEAC - PPP Over

Ethernet Access Concentrator
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
38.1. PoEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.1. Activating the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
38.1.2. POEAC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.2. PPP Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
38.3. POEAC diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
38.3.1. POEAC diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
38.3.2. POEAC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
38.4. Example of POEAC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
38.4.1. Configuring the POEAC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.2. Configuring the IPRTR resource for DNS distribution to the clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
38.4.3. Activating and configuring the IP over PPP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
38.4.4. Activating and configuring the PPP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
38.5. Appendix - Point to Point protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552

38.1. PoEAC resource

38.1.1. Activating the POEAC resource
Add the resource to the Abilis system with the following command, where n is resource identifier (in the range [1...999]).

[12:25:41] ABILIS_CPX:a res:poeac-1

COMMAND EXECUTED

Caution
After adding the POEAC active, you must restart the Abilis to make the resource running (use the command
warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p poeac-1 act:yes

COMMAND EXECUTED

[12:59:38] ABILIS_CPX:d p poeac

RES:PoeAc-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:
LOG:DS ACT:YES ethres: max-ipres:12 ipres-rxbuf:2
ACNAME: max-links:0 links-rxbuf:50
EMPTY-EQ-ANY:NO ALL-SERVICES-OFFER:NO
TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414
- Links ----------------------------------------------------------------

543
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

*** NO LINKs CONFIGURED ***

38.1.2. POEAC resource parameters

Use the following command to display the parameters of the resource; the d p poeac ? command shows the meaning of
parameters.

[17:25:33] ABILIS_CPX:d p poeac

RES:PoeAc-1 -------------------------------------------------------------------
Run DESCR:
LOG:DS ACT:YES ethres:NONE max-ipres:12 ipres-rxbuf:2
ACNAME: max-links:0 links-rxbuf:50
EMPTY-EQ-ANY:NO ALL-SERVICES-OFFER:NO
TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414
- Links ----------------------------------------------------------------
*** NO LINKs CONFIGURED ***

Meaning of the most important parametrs:

LOG Logging functionalities activation/deactivation.

ACT Runtime POEAC activation/deactivation.

ethres Lower Eth100 resource; the value NONE makes the POEAC unusable.

max-ipres Sets the number of PPPoE sessions the module can support. There can't be more than this
amount of external sessions connecting at once.

ipres-rxbuf Sets the number of PPPoE packets received from client a module can hold while sending other
packets to remote PPP.

ACNAME Access Concentrator name; the name of the Access Concentrator is sent along with responses
to hosts. This parameter can be left blank in case there is only one AC in the network for each
service-name requested.

max-links Maximum number of concurrent relay link sessions.

links-rxbuf Number of receive buffers for each relay link session.

EMPTY-EQ-ANY Select whether the EMPTY service specified in PADI and PADR has to be considered a
univocal service (more secure) or ANY service.

ALL-SERVICES-OFFER Select whether PADO will contain only the requested service (more secure) or the list of all
other available services too (less secure).

TCP-MSS-CLAMP Forces POEAC to change value of Maximum Segment Size in all TCP packets to one equal or
lower than set with TCP-MSS-VALUE option to avoid certain problems with PPP over Ethernet
“black hole”. Also can be used to reduce link latency at the cost of some bandwidth loss.

TCP-MSS-VALUE Specifies maximal allowed value for TCP Maximum Segment Size option. This option is only
visible if MSS clamping is allowed via TCP-MSS-CLAMP parameter.

The following command allows the administrator to change the configuration of the resource:

s p poeac-n parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:poeac; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

38.2. PPP Users table

For each host that must use the POEAC resource an entry into Users Table must be added. Users can be created to receive a
static or a dynamic IP address.

• Users with static IP: the parameter PPP-RES of the user must be set to the value of the correspondent IP resource.

544
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

• Users with dynamic IP: the parameter PPP-RES is not set to a specific IP resource, but to a “list of IP resources”.

[16:50:04] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
user_1 *** YES # # YES NO NO NO NO NO

Below there's an example of an user with static IP.

[16:50:04] ABILIS_CPX:a user:user_1 pwd:user_1 ppp:yes ppp-res:ip-101

COMMAND EXECUTED

[16:50:04] ABILIS_CPX:d user:user_1

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: user_1
ALIAS: user_1
ID: 2 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
PPP: YES
PPP-AUTH: CHAP
PPP-RES: Ip-101
PPP-NEIGH: #
PPP-MASK: 255.255.255.255
PPP-ROUTE: #

Below there's an example of an user with dynamic IP.

[16:06:21] ABILIS_CPX:list create PPP_list cr List_of_PPP_Resources

COMMAND EXECUTED

[16:06:26] ABILIS_CPX:a list:ppp_list ip-101 ip-102 ip-103

COMMAND EXECUTED

[16:06:31] ABILIS_CPX:d list:ppp_list

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:PPP_list - CR
List_of_PPP_Resources
Ip-100 Ip-101 Ip-102

[16:08:36] ABILIS_CPX:a user:user_1 ppp:yes pwd:user_1 ppp-res:'ppp_list'

COMMAND EXECUTED

[16:10:09] ABILIS_CPX:d user:user_1

545
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: user_1
ALIAS: user_1
ID: 2 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
PPP: YES
PPP-AUTH: CHAP
PPP-RES: 'PPP_list'
PPP-NEIGH: #
PPP-MASK: 255.255.255.255
PPP-ROUTE: #
-------------------------------------------------------------------------------

Meaning of the parameters:

PPP Enables/disables the PPP service.

PPP-AUTH PPP authentication protocol [PAP; CHAP; MSCHAPV1; MSCHAPV2; ALL].

PPP-RES IP resource over PPP or name of a CPX resources list.

PPP-NEIGH PPP neighbour IP address.

PPP-MASK PPP neighbour network mask.

PPP-ROUTE PPP neighbour additional route.

38.3. POEAC diagnostics and statistics

38.3.1. POEAC diagnostics
The following commands are used to display the diagnostics of the POEAC resource:

d d poeac / d de poeac Shows diagnostic information of the POEAC resource (the status of the resource, the
number of current sessions, the number of maximum sessions available, etc..) and the
diagnostics of the POEAC sessions (the status of the session, the remote MAC address,
the time time since session was connected., etc..).

[15:53:04] ABILIS_CPX:d d poeac

RES:PoeAc-1 -------------------------------------------------------------------
STATE:READY CUR-IPRES:0 MAX-IPRES:12 CUR-LINKS:0 MAX-LINKS:0
------------------------------------------------------------------------
-- Session diagnostics -------------------------------------------------
SESNUM: RESOURCE: STATE: CLI-MAC: SES-ID: CONN-TIME:
TYPE: LINK: SERVICE-NAME:
------------------------------------------------------------------------
001 Ip-103 DISCONNECTED 00-13-D4-A1-4B-34 000A 0
IpRes user_3
------------------------------------------------------------------------
002 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
003 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------

546
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

004 DISCONNECTED 00-00-00-00-00-00 0000 0

IpRes
------------------------------------------------------------------------
005 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
006 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
007 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
008 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
009 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
010 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
011 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------
012 DISCONNECTED 00-00-00-00-00-00 0000 0
IpRes
------------------------------------------------------------------------

38.3.2. POEAC statistics

The following commands are used to display the statistics of the POEAC resource:

d s poeac Shows the statistics of the POEAC resource such as the number of successful connection establishments
with this Access Concentrator, the total number of attempts a connection was tried but failed, the total data
bytes received/sent, the total system bytes received/sent, etc..)

d se poeac Shows the statistics of the POEAC resource and the statistics of each session.

[15:53:05] ABILIS_CPX:d s poeac

RES:PoeAc-1 -------------------------------------------------------------------
--- Cleared 1 days 04:15:20 ago, on 29/12/2007 at 13:39:44 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 10| 0|FAIL-CALL | 0| 0|
CHR-PPP | 18690834| 506607701|CHR-SYS | 2064| 1896|
PCK-PPP | 207524| 372641|PCK-SYS | 32| 32|
LOST-PPP | 0| |LOST-SYS | 0| |
DROPPED-PPP| 0| |DROPPED-SYS| 0| |
------------------------------------------------------------------------

[15:59:02] ABILIS_CPX:d se poeac

RES:PoeAc-1 -------------------------------------------------------------------
--- Cleared 1 days 04:15:25 ago, on 29/12/2007 at 13:39:44 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 10| 0|FAIL-CALL | 0| 0|
CHR-PPP | 18690834| 506607701|CHR-SYS | 2064| 1896|
PCK-PPP | 207524| 372641|PCK-SYS | 32| 32|
LOST-PPP | 0| |LOST-SYS | 0| |
DROPPED-PPP| 0| |DROPPED-SYS| 0| |
------------------------------------------------------------------------
-- Session statistics --------------------------------------------------
SESNUM:001 TYPE:IpRes RESOURCE:Ip-103
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|

547
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

CHR-PPP | 450495| 3828997|PCK-PPP | 2842| 3667|

LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:002 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:003 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:004 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:005 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:006 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:007 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:008 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:009 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:010 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:011 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------
SESNUM:012 TYPE:IpRes RESOURCE:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR-PPP | 0| 0|PCK-PPP | 0| 0|
LOST-PPP | 0| |DROPPED-PPP| 0| |
------------------------------------------------------------------------

38.4. Example of POEAC configuration

Consider the following example: suppose that PoeAC clients are connected through a wireless link.

548
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

Tip
Interesting chapter: Section 52.11.3, “How to configure a RAS using PPPoE connections with an Ethernet/
WiFi network”.

38.4.1. Configuring the POEAC resource

Configure the maximum number of PPPoE sessions with a value equal to the number of users which you want to enable (for
example 10 users), configure the lower Eth100 resource (in this case: Eth-2) and give a name to the Access Concentrator.

[11:43:00] ABILIS_CPX:s p poeac-1 max-ipres:10 acname:wlan ethres:eth-2

COMMAND EXECUTED

[11:43:03] ABILIS_CPX:d p poeac-1

RES:PoeAc-1 - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:
LOG:DS ACT:YES ethres:Eth-2 max-ipres:10 ipres-rxbuf:2
ACNAME:wlan max-links:0 links-rxbuf:50
EMPTY-EQ-ANY:NO ALL-SERVICES-OFFER:NO
TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414
- Links ----------------------------------------------------------------
*** NO LINKs CONFIGURED ***
RES:Eth-2 - Not Saved (SAVE CONF) ---------------------------------------------
------------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

38.4.2. Configuring the IPRTR resource for DNS distribution to the

clients
Configuring the PPP-DNS-PRI and PPP-DNS-SEC parameters in the IPRTR resource is needed to redistribute the IP
addresses of the DNS servers to the clients.

[12:01:24] ABILIS_CPX:s p iprtr PPP-DNS-PRI:62.94.0.1 PPP-DNS-SEC:62.94.0.2

549
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

COMMAND EXECUTED

[12:11:57] ABILIS_CPX:d p iprtr

RES:Iprtr - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.000.1)
maxroute:500 DFTTTL:64 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:7 virtual:0
- IP Access List -------------------------------------------------------
ACL:EXT ACLBYPASS:#
COS:ENABLED COSDFT:LOW
COSBALANCE:YES NORMRATE:100 LOWRATE:0
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:062.094.000.001 PPP-DNS-SEC:062.094.000.002

38.4.3. Activating and configuring the IP over PPP resources

Set act as many IP resources of type PPP as the number of users to manage with the command a res:ip-n subtype:ppp.

[12:11:59] ABILIS_CPX:a res:ip-101 subtype:ppp

COMMAND EXECUTED

Caution
To set act the changes made, a save conf and an Abilis restart are needed (i.e. with warm start command).

[12:11:59] ABILIS_CPX:d p ip-101

RES:Ip-101 - IP over PPP (PPP) ------------------------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:NONE
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RAW-PPP RADIUS:NO
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO
maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:
PASSWORD: LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE

The most important parameters are:

LOWRES Lower resource (must be the correspondent PoEAC resource).

IPADD IP address assigned to the PPP Server.

NEIGH IP address assigned to the PPP Client.

550
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

NAT NAT usage [NO; INSIDE; OUTSIDE].

LOCAL Client Authentication protocol.

REMOTE Server Authentication protocol.

TCP-MSS-CLAMP It decides whether to perform TCP MSS clamping; if set, forces PPP to change value of Maximum
Segment Size in all TCP packets to one equal or lower than set with TCP-MSS-VALUE option to avoid
certain problems with PPP over Ethernet “black hole”. Also can be used to reduce link latency at the
cost of some bandwidth loss.

DNS It estabilishes the DNS addresses negotiation [NO: no DNS address negotiation is performed;
PROVIDE: PPP can provide DNS addresses to a remote host; RETRIEVE: PPP requests DNS
addresses from a remote host].

SERVICENAME PPP over Ethernet Service name: name under which this link can be requested from the client. If the
client specifies a certain ServiceName, Server answers only if it has link with tha exactly name. If
Client specifies no name, it means any line is acceptable.

According to previous example, configure the IP over PPP resources with the following features:

• LOWRES resource: POEAC-1;

• server IP address: 192.168.10.201;

• client IP address: 192.168.10.101;

• service name: user_1;

• enable TCP MSS clamping;

• enable DNS negotiation;

[12:48:09] ABILIS_CPX:s p ip-101 lowres:poeac-1 ipadd:192.168.10.201 neigh:192.168.10.101 nat:insid

COMMAND EXECUTED

[14:46:44] ABILIS_CPX:s p ip-101 servicename:user_1 tcp-mss-clamp:yes dns:provide local:none remote

COMMAND EXECUTED

[14:46:50] ABILIS_CPX:d p ip-101

RES:Ip-101 - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

- IP over PPP (PPP) ----------------------------------------------------
Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:PoeAc-1
IPADD:192.168.010.201 MASK:255.255.255.255 NEIGH:192.168.010.101
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RAW-PPP RADIUS:NO
SERVICENAME:user_1
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:YES TCP-MSS-VALUE:1414
maxmru:1500 DNS:PROVIDE
- Authentication -------------------------------------------------------
USERNAME:
PASSWORD: LOCAL:NONE
SERVNAME: REMOTE:CHAP

551
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

REPEAT:0

Caution
To set act the changes made, use init res:ip-101 command followed by init ipr and save the configuration
with save conf command to make the changes permanent.

Repeat the same operations for each user by changing the number of the IP resource (i.e. IP-102, IP-103…).

38.4.4. Activating and configuring the PPP users

Add an entry in the Users table for each IP resource which you have activated.

[15:53:42] ABILIS_CPX:a user:user_1 ppp:yes pwd:user_1 ppp-res:ip-101

COMMAND EXECUTED

[15:54:06] ABILIS_CPX:d user:user_1

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: user_1
ALIAS: user_1
ID: 2 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
PPP: YES
PPP-AUTH: CHAP
PPP-RES: Ip-101
PPP-NEIGH: #
PPP-MASK: 255.255.255.255
PPP-ROUTE: #
-------------------------------------------------------------------------------

The command must be repeated for all other users.

The connection to the Access Concentrator can be done by using standard Windows PPPoE client or common routers that
support this protocol.

38.5. Appendix - Point to Point protocol

The Point-to-Point Protocol1 (PPP) is the most widely used protocol for connecting hosts over the peer-to-peer connection,
such as modem, ISDN link or a direct cable connection. It supports transmitting multi-protocol datagrams over a single
link, along with such features as authentication, link quality monitoring and flexible set of options which can be negotiated
between two connecting hosts.

The PPP over Ethernet2 (PPPoE) protocol allows hosts inside an Ethernet-based network to access external hosts via PPP
through the bridge host (Access Concentrator). It is most often used to access an xDSL line from inside the network, the DSL
or cable modem playing the role of the AC.

Thus, for successful connection two physical parts are required: client PPPoE module (on every host wishing to use PPPoE)
and one or more Access Concentrators. They are presented in a CPX by two modules: POECLI for client part, and POEAC as
a server part, described in this chapter.

1
http://en.wikipedia.org/wiki/Point-to-Point_Protocol
2
http://en.wikipedia.org/wiki/Pppoe

552
Draft POEAC - PPP Over Ethernet Draft
Access Concentrator

PPPoE Access Concentrators (AC) answer the PPPoE request coming from a client site PPPoE application. It offers
standard PPP features such as authentication, encryption, and compression. It allows connection with login and password for
Internet connection accounting purposes. Also, the IP address on the other side of the link is only assigned when the PPPoE
connection is open, allowing the dynamic reuse of IP addresses.

553
Draft Draft

Chapter 39. SNMP - Simple Network

Management Protocol
Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
39.1. SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.1. Activating the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
39.1.2. SNMP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
39.2. Example of configuration of the SNMP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3. SNMP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.1. SNMP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
39.3.2. SNMP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
39.4. SNMP Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
39.5. Appendix - SNMP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559

39.1. SNMP resource

The activation of SNMP resource allows to configure Abilis as a SNMP agent. The configuration is quite simple, because
few parameters must be modified.

The MIB (Management Information Base) contains the description of the configuration/statistics “objects” available in the
SNMP Agents and their availability to be controlled by SNMP Managers.The variables accessible via Abilis CPX SNMP
resource are described in the Abilis proprietary MIB that can be downloaded from Abilis technical website - download
section1.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

Refer to Section 39.5, “Appendix - SNMP Protocol” to have more information about SNMP protocol.

39.1.1. Activating the SNMP resource

Add the resource to the Abilis system with the following command:

[15:50:39] ABILIS_CPX:a res:snmp

RES:SNMP ALREADY EXISTS

The SNMP resource may already exist in the system, but may not yet be active: set it active with the command:

[15:50:43] ABILIS_CPX:s act res:snmp

COMMAND EXECUTED

1
http://abilis.antek.it/downloads/cpx2k/download.html

554
Draft SNMP - Simple Network Draft
Management Protocol

Caution
After adding or setting the SNMP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[17:14:59] ABILIS_CPX:s p snmp act:yes

COMMAND EXECUTED

[17:15:17] ABILIS_CPX:d p snmp

RES:Snmp - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

-----------------------------------------------------------------------
Run DESCR:Simple_Network_Management_Protocol
LOG:NO ACT:YES
- Agent ----------------------------------------------------------------
locport:161
COMMUNITY:public
IPSRC:* IPSRCLIST:#
- Traps ----------------------------------------------------------------
TRAP:NO AUTHTRAP:NO TRAPREP:10
TRAPDEST:# TRAPSRC:R-ID (192.168.001.001)

39.1.2. SNMP resource parameters

Use the following command to display the parameters of the resource; the d p snmp ? command shows the meaning of
parameters.

[09:58:41] ABILIS_CPX:d p snmp

RES:Snmp ----------------------------------------------------------------------
Run DESCR:Simple_Network_Management_Protocol
LOG:NO ACT:YES
- Agent ----------------------------------------------------------------
locport:161
COMMUNITY:public
IPSRC:* IPSRCLIST:#
- Traps ----------------------------------------------------------------
TRAP:NO AUTHTRAP:NO TRAPREP:10
TRAPDEST:# TRAPSRC:R-ID (192.168.001.001)

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime SNMP activation/deactivation.

COMMUNITY Sets the keyword used by the authentication procedure of those SNMP management systems able to query
the SNMP Agent of the Abilis CPX. Only those, which have the same value of the “Community Name” as
the local SNMP port, are allowed to supervise. If it doesn't match, the query frames are rejected and, if the
parameter AUTHTRAP is set to YES, a wrong authentication message is sent to the SNMP Manager, whose IP
is configured in the parameter TRAPDEST.

IPSRC Sets the IP address of the SNMP source management from which the SNMP Agent of the Abilis can receive
requests.

IPSRCLIST Sets the list of the SNMP management systems able to query the SNMP Agent of the Abilis CPX.

TRAP Enables/disables the generation of informative asynchronous signalling (trap) to the SNMP Manager, which
IP address must be declared in the TRAPDEST parameter.

AUTHTRAP Enables/disables the generation of the wrong authentication signalling if SNMP resource receives requests
from not authorized SNMP Manager processes.

TRAPREP Sets the time interval (in minutes) which has to pass before resending the trap.

555
Draft SNMP - Simple Network Draft
Management Protocol

TRAPDEST Sets the IP address (or a list of IP addresses) of the management system to which the TRAPS generated by
the SNMP Agent of the Abilis must be sent.

TRAPSRC Sets the source IP address to be used for outgoing traps.

The command that allows the configuration of the resource to be modified has the following syntax:

s p snmp par:val...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:snmp; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

39.2. Example of configuration of the SNMP resource

The example below shows how to configure the SNMP resource and to enable the SNMP Agent to the remote IP address
81.81.81.81 and to send TRAPS to the host 192.168.1.201.

[18:06:44] ABILIS_CPX:s p snmp act:yes ipsrc:81.81.81.81 trap:yes trapdest:192.168.1.201 traprep:60

COMMAND EXECUTED

[18:06:50] ABILIS_CPX:d p snmp

RES:Snmp - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

-----------------------------------------------------------------------
Run DESCR:Simple_Network_Management_Protocol
LOG:NO ACT:YES
- Agent ----------------------------------------------------------------
locport:161
COMMUNITY:public
IPSRC:081.081.081.081 IPSRCLIST:#
- Traps ----------------------------------------------------------------
TRAP:YES AUTHTRAP:NO TRAPREP:60
TRAPDEST:192.168.001.201 TRAPSRC:R-ID (192.168.001.001)

This configuration allows Abilis to accept the SNMP request from host 81.81.81.81 and to send any traps to the host
192.168.1.201 every 60 minutes.

Tip
Interesting chapter: Section 52.21, “How to activate the SNMP agent”.

39.3. SNMP diagnostics and statistics

39.3.1. SNMP diagnostics
To display the diagnostics of the SNMP resource the following commands are used:

d d snmp Shows the state of the resource.

d de snmp Shows the state of the resource, and information about the last sent trap.

[15:53:04] ABILIS_CPX:d d snmp

RES:Snmp ----------------------------------------------------------------------
Simple_Network_Management_Protocol
STATE:READY

[15:53:04] ABILIS_CPX:d de snmp

RES:Snmp ----------------------------------------------------------------------

556
Draft SNMP - Simple Network Draft
Management Protocol

Simple_Network_Management_Protocol
STATE:READY
- Last sent trap: ------------------------------------------------------
Loc. Date |Loc. Time| Trap | Resource
----------+---------+-----------------------------+---------------------
00/00/0000 00:00:00 coldStart Unknown-0
------------------------------------------------------------------------

39.3.2. SNMP statistics

To display the statistics of the SNMP resource the following commands are used:

d s snmp Shows the statistics of the SNMP resource, such as the number of sent/received packets, the number of
GetRequest frames received, the number of GetNext frames received, the number of SetRequest frames
received, the number of GetResponse frames sent, etc..

d se snmp Shows the statistics of the SNMP resource, the Traps service statistics, the Standard traps statistics and the
Enterprise specific traps statistics.

[15:53:05] ABILIS_CPX:d s snmp

RES:Snmp ----------------------------------------------------------------------
Simple_Network_Management_Protocol
--- Cleared 080:17:02:45 ago, on 11/10/2007 at 01:40:36 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PCK | 14| 14|GET-REQ | 13| 0|
GET-NEXT | 1| 0|SET-REQ | 0| 0|
GET-RESP | 0| 14|TRAP | 0| 0|
BAD-VER | 0| |BAD-COM-N | 0| |
BAD-COM-U | 0| |ASN-ERR | 0| |
TOO-BIG | 0| 0|NO-NAME | 0| 0|
BAD-VAL | 0| 0|RONLY | 0| |
GEN_ERR | 0| 0|REQ_VAR | 17| |
SET_VAR | 0| |
------------------------------------------------------------------------

[15:59:02] ABILIS_CPX:d se snmp

RES:Snmp ----------------------------------------------------------------------
Simple_Network_Management_Protocol
--- Cleared 080:17:02:49 ago, on 11/10/2007 at 01:40:36 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
PCK | 14| 14|GET-REQ | 13| 0|
GET-NEXT | 1| 0|SET-REQ | 0| 0|
GET-RESP | 0| 14|TRAP | 0| 0|
------------------------------------------------------------------------
Traps service statistics:
-----------|--OUTPUT---|-----------|--OUTPUT---|-----------|--OUTPUT---|
REQ | 1921|REQ-SUCC | 0|REQ-FAIL | 1921|
EVENT | 0|EVENT-SUCC | 0|EVENT-FAIL | 0|
SEND | 0|SEND-SUCC | 0|SEND-FAIL | 0|
------------------------------------------------------------------------
Standard traps statistics:
-----------|--OUTPUT---|-----------|--OUTPUT---|-----------|--OUTPUT---|
COLDSTART | 0|LINKDOWN | 0|AUTHFAIL | 0|
WARMSTART | 0|LINKUP | 0|EGPNL | 0|
------------------------------------------------------------------------
Enterprise specific traps statistics:
-----------|--OUTPUT---|-----------|--OUTPUT---|-----------|--OUTPUT---|
SYNC-DN | 0|ETH-DN | 0|TR-DN | 0|
SYNC-UP | 0|ETH-RD | 0|TR-OPEN | 0|
SNTP-UNSYN | 0|X25-DN | 0|LAPB-DN | 0|
SNTP-SYN | 0|X25-RD | 0|LAPB-CN | 0|
HDLCT-DN | 0|PAD-L1-DN | 0|IPLAN-DN | 0|

557
Draft SNMP - Simple Network Draft
Management Protocol

HDLCT-UP | 0|PAD-L1-UP | 0|IPLAN-RD | 0|

SDLC-PU-DN | 0|FTP-DN | 0|BDG-DN | 0|
SDLC-PU-ST | 0|FTP-RD | 0|BDG-RD | 0|
SDLC-PU-CN | 0|BDG-LAN-DN | 0|BDG-LNK-DN | 0|
BDG-ALL-DN | 0|BDG-LAN-RD | 0|BDG-LNK-RD | 0|
PRI-ISDN-DN| 0|BRI-ISDN-DN| 0|FR-DN | 0|
PRI-ISDN-UP| 0|BRI-ISDN-RD| 0|FR-UP | 0|
PRI-S0-IN | 0|BRI-S0-IN | 0|FR-DLCI-DN | 0|
PRI-S0-DN | 0|BRI-S0-DN | 0|FR-DLCI-AC | 0|
PRI-S0-UP | 0|BRI-S0-UP | 0|FR-DLCI-BL | 0|
PRI-S16-IN | 0|BRI-S16-IN | 0|FR-DLCI-IN | 0|
PRI-S16-DN | 0|BRI-S16-DN | 0|FR-DLCI-NP | 0|
PRI-S16-UP | 0|BRI-S16-UP | 0|FR-DLCI-RM | 0|
MLM-PL-DN | 0|ML-ALL-DN | 0|PPP-ST | 0|
MLM-PL-RD | 0|ML-ALL-RD | 0|PPP-DN | 0|
MLM-SL-ST | 0|ML-SOME-RD | 0|PPP-RD | 0|
MLM-SL-RD | 0|ML-SL-ST | 0|PPP-UP | 0|
MLM-SL-US | 0|ML-SL-RD | 0|POEAC-DN | 0|
IP-DN | 0|ML-PL-DN | 0|POEAC-UP | 0|
IP-UP | 0|ML-PL-UP | 0|POECLI-DN | 0|
ADSL-DN | 0|CELL-V-DN | 0|POECLI-UP | 0|
ADSL-UP | 0|CELL-V-UP | 0|CELL-PDN-DN| 0|
OPC-DN | 0|SYSLOG-DN | 0|CELL-PDN-UP| 0|
OPC-UP | 0|SYSLOG-UP | 0| | |
GPIOPC-DN | 0|GPIO-DN | 0|GPS-DN | 0|
GPIOPC-UP | 0|GPIO-UP | 0|GPS-UP | 0|
| |RJS-DN | 0|SIMBOX-DN | 0|
| |RJS-UP | 0|SIMBOX-UP | 0|
------------------------------------------------------------------------

39.4. SNMP Console

Combining the SNMP resource with a SNMP Console provides a powerful instrument of network monitoring. For example:

• network diagram;

• polling for network monitoring;

• sending of e-mail, sms and so on when a trap is received;

• network load graphs construction.

• etc.

Example of consoles may be Ipswitch WhatsUp Gold2 or Zabbix3. Below is a screen-shot of a WhatsUp Gold's Map used for
network monitoring.

Figure 39.1. WhatsUp Gold console

2
http://www.whatsupgold.com/
3
http://www.zabbix.com/

558
Draft SNMP - Simple Network Draft
Management Protocol

39.5. Appendix - SNMP Protocol

The Simple Network Management Protocol4 (SNMP) allows the exchange of configuration information, statistics, alarms,
etc, between suitable devices for network supervision, called SNMP Managers, and processes called SNMP Agent, running
aboard the devices to be controlled. The protocol also allows the Agent processes to send unsolicited messages, called Traps,
to the Manager ones for pointing out particular events such as alarms, exceptions, etc.

4
http://en.wikipedia.org/wiki/Snmp

559
Draft Draft

Chapter 40. TRFA - Traffic Analyzer

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
40.1. TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.1. Activating the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
40.1.2. TRFA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.1.3. Activating the TRFA inside IP resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
40.2. TRFA diagnostics, statistics and debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.1. TRFA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.2. TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
40.2.3. TRFA debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3. Example of TRFA configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.1. Configuring TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
40.3.2. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
40.3.3. Using HTTP for showing TRFA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

40.1. TRFA resource

The Abilis CPX TRFA resource provides the following features:

• Configures each IP interface for the desired capture detail (TOTALS, by IP, by PROTOCOL, by IP and PROTOCOL).
The configuration parameters related to this function are present in the IP resource configuration.
• Shows the total traffic for each interface.
• Shows the traffic by IP address.
• Shows the traffic by protocol/applications (FTP, TELNET, etc.).
• Shows the traffic by IP address and a protocol/application.
• Shows the desired traffic types of the last day/week/month/year.
• Shows the traffic as individual interface or all summed interfaces.
• Shows graph or table view.
• Results are presented using the Abilis HTTP server (see HTTP resource).

Configuring the TRFA resource and the section inside the IP resources are needed to activate the IP Traffic Analyzer.

40.1.1. Activating the TRFA resource

Add the resource to the Abilis system with the following command:

[11:01:39] ABILIS_CPX:a res:trfa

RES:TRFA ALREADY EXISTS

The TRFA resource may already exist in the system, but may not yet be active: set it active with the command:

[11:01:48] ABILIS_CPX:s act res:trfa

COMMAND EXECUTED

Caution
After adding or setting the TRFA active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

560
Draft TRFA - Traffic Analyzer Draft

[11:01:39] ABILIS_CPX:s p trfa act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p trfa

RES:Trfa - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Traffic_Analyzer
LOG:DS ACT:YES max-addresses:1000 max-png:5 BAK:NO
WDIR:C:\APP\TRFA\

40.1.2. TRFA resource parameters

Use the following command to display the parameters of the resource; the d p trfa ? command shows the meaning of
parameters.

[17:06:43] ABILIS_CPX:d p trfa

RES:Trfa ----------------------------------------------------------------------
Run DESCR:Traffic_Analyzer
LOG:DS ACT:YES max-addresses:1000 max-png:5 BAK:NO
WDIR:C:\APP\TRFA\

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime TRFA activation/deactivation.

max-addresses Maximum number of pair “IP resource,IP address” in the TRFA address table.

max-png Maximum number of PNG shell objects. This objects will be used to create PNG files for TRFA's
HTML information page. If you have a lot of interfaces with active TRFA and TRFA's HTML
information page is created too slowly, then increase this value. Each PNG shell object gets about 400K
memory.

BAK Enables/disables back-up file creation.

WDIR Directory where traffic data files are stored.

The following command allows the administrator to change the configuration of the resource:

s p trfa parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init res:trfa;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

40.1.3. Activating the TRFA inside IP resources

Activating the traffic survey on an IP resource, type:

[17:45:32] ABILIS_CPX:s p ip-1 trfa:yes

COMMAND EXECUTED

[17:45:41] ABILIS_CPX:d p ip-1

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-1

561
Draft TRFA - Traffic Analyzer Draft

IPADD:192.168.000.201 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:YES VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:50 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:TOTALS
TRFA-IPADD:LOCALNET (192.168.000.000:192.168.000.255)
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-1 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:25 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

In the “TRFA Section” the following parameters will appear:

TRFA Enables/disables traffic analysis.

TRFA-MODE Select traffic analysis mode [TOTALS: saves the total global traffic; PROT: subdivides the registration for
the main protocol models; IP: saves the totals for every single IP address; IP-PROT: subdivides the traffic
by protocol, for every single crossing IP address];

IP-RESERVE Reserves records in the traffic analysis data base: it represents the maximum IP number trace.

TRFA-SIDE Selects IP address type [LOCAL: filters the traffic by destination IP address; REMOTE: filters the traffic by
source IP address].

TRFA-IPADD IP address filter.

40.2. TRFA diagnostics, statistics and debug

40.2.1. TRFA diagnostics
The following commands are used to display the diagnostics of the TRFA resource:

d d trfa / d de trfa Shows the current status of the resource, the current status of the active address array,
the current status of the active traffic array, the number of seconds to reach next event,
the percentage of use of the active address/backup array, the currently record saved
in the active address/backup array, the maximum number of simultaneously record
in the active address/backup array, the actual size of the active address/backup array
and the number of requests that were discarded because active address/backup array is
overflow.

[15:53:04] ABILIS_CPX:d d trfa

RES:Trfa ----------------------------------------------------------------------
Traffic_Analyzer
STATE:ACTIVE ACTIVE-STATE:NORMAL BACKUP-STATE:NORMAL EVENT: 32
------------------------------------------------------------------------
---ARRAY---|---PERC----|----CUR----|---PEAK----|----MAX----|----OVR----|
ACTIVE | 1| 13| 21| 1000| 0|
BACKUP | 1| 11| 20| 1000| 0|
------------------------------------------------------------------------

40.2.2. TRFA statistics

To display the statistics of the TRFA resource the following commands are used:

d s trfa / d se trfa Shows the total number of requests, the number of requests that were successfully
executed, the number of requests that were not satisfied, the number of requests for

562
Draft TRFA - Traffic Analyzer Draft

which the traffic tracing was not activated and the number of failures due to an address
overflow.

[15:53:05] ABILIS_CPX:d s trfa

RES:Trfa ----------------------------------------------------------------------
Traffic_Analyzer
--- Cleared 1 days 05:32:41 ago, on 29/12/2007 at 13:39:43 -------------
- Send/Receive statistics ----------------------------------------------
-----------|---TOTAL---|---SUCC----|---FAIL----|---INACT---|-OVERFLOW--|
REQUESTS | 3882659| 3882659| 0| 0| 0|
------------------------------------------------------------------------

40.2.3. TRFA debug

The debug commands are useful for various activities, e.g. clearing files, removing data originated from a temporary
configuration error, removing obsolete data after a line change, etc..

[11:44:43] ABILIS_CPX:_debug res:trfa

RES:Trfa ----------------------------------------------------------------------
Traffic_Analyzer
BufferLength:1007 Date/Time:07/03/2011 11:44:46 TraceTime:226070834

Usage:
LSN:0 - This help
LSN:3 - Log commands (help)
LSN:4 - DATA File status
LSN:5 - BACKUP File status
LSN:6 - TEMPORARY File status
LSN:10 - Purge help
LSN:10 CMD:PURGE,param,... - Purge specific information

List of TRFA PURGE parameters:

IPRES:nnn - Purge data from IP-RES indicated.
TYPE:ssss - Type of purge (ALL, IP, IP-PROT).
ARCHIVE:ssss - Type of archive (DAY, WEEK, MONTH, YEAR, *=any).
IP:x.x.x.x - Purge data with specified IP (only for TYPE:IP/IP-PROT).
(single IP or range x.x.x.x-y.y.y.y or *=any).
PROT:sss - Purge data with specified protocol (only for TYPE:IP-PROT).
(ICMP, TCP, UDP, OTHERPROT, FTP, TELNET, SMTP, DNS, POP3
POP3SSL, SNMP, HTTP, HTTPS, OTHERTCP, OTHERUDP).
FROM:ddmmyyyy[-hhmm] - Starting range time (*=no limit).
TO:ddmmyyyy[-hhmm] - Ending range time (*=no limit).

40.3. Example of TRFA configuration

Specifications:

• Activate the statistic survey of the LAN interface (ip-1) and the internet connection (ip-2).

• Activate the TOTALS survey on the LAN resource, .

• Activate the IP-PROT survey (gathers the traffic dividing it by protocol for every source IP address) on the Internet
connection resource.

40.3.1. Configuring TRFA resource

Set the BAK parameter to NO to block the creation of back-up files.

[11:25:48] ABILIS_CPX:s p trfa bak:no

563
Draft TRFA - Traffic Analyzer Draft

COMMAND EXECUTED

[11:26:00] ABILIS_CPX:d p trfa

RES:Trfa - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
DESCR:Traffic_Analyzer
LOG:DS ACT:YES max-addresses:1000 max-png:5 BAK:NO
WDIR:C:\APP\TRFA\

Activate the TRFA survey on the private LAN (IP-1 resource).

[11:13:18] ABILIS_CPX:s p ip-1 trfa:yes

COMMAND EXECUTED

[11:13:20] ABILIS_CPX:d p ip-1

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:LAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-1
IPADD:192.168.030.001 MASK:255.255.255.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:TOTALS
TRFA-IPADD:LOCALNET (192.168.030.000:192.168.030.255)
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-1 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

Activate the TRFA survey on the Internet connection (ip-2 resource) and configure it with following the specifications.

[11:20:18] ABILIS_CPX:s p ip-2 trfa:yes

COMMAND EXECUTED

[11:21:02] ABILIS_CPX:s p ip-2 trfa:yes trfa-mode:ip-prot trfa-side:remote trfa-ipadd:*

COMMAND EXECUTED

[11:46:03] ABILIS_CPX:d p ip-2

RES:Ip-2 - IP over LAN (LAN) --------------------------------------------------

Run DESCR:WAN
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LANRES:Eth-2
IPADD:DHCP DHCP-GW:YES DHCP-GW-AD:0 DHCP-DNS:YES
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:YES
OUTBUF:100 OUTQUEUE:FAIR MTU:1500 BRD:NET
OUTSPL:NO
INBUF:0 mru:1500 SRCV:NO
- DDNS section ---------------------------------------------------------

564
Draft TRFA - Traffic Analyzer Draft

DDNS-FQDN:abilistest.dyndns.org
- TRFA section ---------------------------------------------------------
TRFA:YES TRFA-MODE:IP-PROT IP-RESERVE:AUTO TRFA-SIDE:REMOTE
TRFA-IPADD:*
- Lan ------------------------------------------------------------------
LOG:NO arpcache:200 CACHETIMER:120
rxbuf:4 txbuf:14
RES:Eth-2 ---------------------------------------------------------------------
Run DESCR:
LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO
dma-rxbuf:250 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5
pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25

Tip
Interesting chapters: Section 19.3, “IP Resources”.

40.3.2. Configuration of the HTTP rights

Add the user “trfa” and enable it to HTTP.

[11:01:39] ABILIS_CPX:a user:trfa pwd:trfa http:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
trfa *** YES # # NO NO YES NO NO NO

Add the HTTP rights for the user “trfa”.

[11:01:39] ABILIS_CPX:a http rights path:/sys/trfa/ user:trfa

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d http rights

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/trfa/
trfa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Tip
Interesting chapters:

Section 34.2, “HTTP tables”;

Chapter 43, The web interface.

565
Draft TRFA - Traffic Analyzer Draft

40.3.3. Using HTTP for showing TRFA statistics

The TRFA resource allows to save and analyze the traffic for one or more IP interfaces.

40.3.3.1. Parameters of request

Follow the steps described in Section 43.3.1, “IP Traffic Analyzer”.

The TRFA starting page will be shown.

Figure 40.1. TRFA - starting page

Definition of the configurable parameters:

Period selection. It allows the definition of the time period that will be used as a report base.

• Current year

• Archive information. There are three previous years and current year.

Warning
The archive information will be available only if you have already run the
TRFA resource. You cannot, obviously, get information about periods
preceding the installation of the TRFA.

If you select the current year, you can define the report period more precisely.

• Year: the minimal period is one day.

• Month: the minimal period is two hours.

• Week: the minimal period is 30 minutes (half an hour).

• Day: the minimal period is five minutes.

Window display. A window where you can choose the time period: day/week/month/year.

• Sliding: views the whole period preceding the current time and date. For instance: if you select
the “day” period and the current time is 10.PM, you will get a report of the last 24 hours: until
10PM of the preceding day.

• Beginning: views the period starting from the beginning of the current day: For instance, it is
9.PM, and you select the “day” period you will view the report starting at 0.AM and ending at
9.PM.

Display information as. It detects an output view of the report.

• Picture: in this case traffic information will be represented as a picture.

• Table: in this case the traffic information will be represented as a table.

566
Draft TRFA - Traffic Analyzer Draft

Note
You can always switch to another view: graph/table and vice versa.
To switch from graph to table, click on the graph; to switch from
table to graph, click on Switch to PICTURE view.

Report type. It defines if the output information will or will not be grouped.

• Individuals: the traffic information will be represented in separated graphs.

• Sums: the traffic information will be represented in a unique grap.

Units. Defines the kilobytes size that will be used for the report. You can use, if you prefer, a value equal to 1000 bytes
as 1024 bytes.

Multiplier. This parameter defines the unit that will be used to show the traffic information. You can select: bits per
second (Bits/Sec) or bytes per second (Bytes/Sec).

IP Resource. Filters the traffic information for a selected period by IP resource only.

IP Address. Filters the traffic information for a selected period by selected IP addresses (or IP addresses intervals)
only.

Protocols. Filters the traffic information for a selected period by selected protocols only.

Report. This button generates the graphs or the table.

Reset. Restores the default settings.

TOP 10 IP Shows the ten IP addresses that have generated the most traffic on an IP resource and the amount of traffic. It
simultaneously generates IN, OUT, IN+OUT traffic.

TOP 20 IP Shows the twenty IP addresses that have generated the most traffic on an IP resource and the amount of
traffic. It simultaneously generates IN, OUT, IN+OUT traffic.

40.3.3.2. Example of request

Below there are examples of IP Traffic Analyzer consultations through HTTP interface.

40.3.3.2.1. Request by IP resource

Example of view: IP-1 and IP-2 resources week graphs.

1. In Period Selection click week option.

2. Select IP-1 and IP-2 in the IP resource list. (click on IP-1 and keep the Ctrl button pressed while clicking on IP-2).

3. Keep the other default settings: Window display Sliding, Display information as Picture, Report type Individuals:

Figure 40.2. TRFA Example 1 - Settings

4. To view the graphs click on the Report button.

567
Draft TRFA - Traffic Analyzer Draft

Figure 40.3. TRFA Example 1 - Graphs generation

Note
The graph is grey in the period in which the TRFA was not activated.

5. To view the tables click on the graph.

Figure 40.4. TRFA Example 1 - Table

40.3.3.2.2. Request by Selected IP Address

View example: IP-2 resource day graph generated by the IP 192.168.30.3.

1. In Period Selection select Day option.

2. Select IP-2 in the IP resource list.

3. Select Selected IP in the IP address filter.

4. Type the IP address 192.168.30.3 in the label.

5. Keep the other default settings: Window display Sliding, Display information as Picture, Report type Individuals.

568
Draft TRFA - Traffic Analyzer Draft

Figure 40.5. TRFA Example 2 - Settings

6. To view the graph, click on the Report button.

Figure 40.6. TRFA Example 2 - Graph generation

569
Draft TRFA - Traffic Analyzer Draft

7. To view the table click on the graph.

570
Draft TRFA - Traffic Analyzer Draft

Figure 40.7. TRFA Example 2 - Table

571
Draft TRFA - Traffic Analyzer Draft

40.3.3.2.3. TOP 10 Request

Let’s try to view: the 10 IP addresses that have generated the most traffic on the IP-2 resource, and quantify that traffic:

1. In Period Selection select Day option.

2. Select IP-2 in the IP-resource list.

3. Keep the other default settings: Window display Sliding, Display information as Picture, Report type Individuals.

Figure 40.8. TRFA Example 3 - Settings

4. To view the graph click on the TOP TEN IP button.

Figure 40.9. TRFA Example 3 - Graph Generation

Note
You can get this view only if you select one IP resource from the IP resource list at a time.

5. To view the table and the whole traffic total of the single IP click on the graph.

572
Draft TRFA - Traffic Analyzer Draft

Figure 40.10. TRFA Example 3 - Table

573
Draft TRFA - Traffic Analyzer Draft

Caution
To make this view work, you must configure the TRFA on the IP resource in TRFA-MODE:IP or in
TRFA-MODE:IP-PROT.

40.3.3.2.4. Request by Protocols

To view the day traffic of SMTP conveyed through the IP-1 resource follow these instructions:

1. In Period Selection select Day option.

2. Select IP-2 in the IP-resource list.

3. Select SMTP in the Protocols list.

4. Keep the other default settings: Window display Sliding, Display information as Picture, Report type Individuals.

Figure 40.11. TRFA Example 4 - Settings

5. To view the graph click on the Report button.

Figure 40.12. TRFA Example 4 - Graph Generation

6. To get the table view, click on the graph.

574
Draft TRFA - Traffic Analyzer Draft

Figure 40.13. TRFA Example 4 - Table

Caution
To make this view work, you must configure the TRFA on the IP resource in TRFA-MODE:PROT or
TRFA-MODE:IP-PROT.

575
Draft Draft

Chapter 41. LDAP - Lightweight

Directory Access Protocol
Alfredo Sorbello

Table of Contents
41.1. LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
41.1.1. Activating the LDAP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.1.2. LDAP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
41.2. LDAP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.1. User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
41.2.2. Rights table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
41.3. LDAP use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.1. Publishing local VoIP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
41.3.2. Identifying the caller in a VoIP phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
41.3.3. Mail composing and LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
41.4. Handling contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.1. Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
41.4.2. LDAP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
41.5. LDAP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.1. LDAP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
41.5.2. LDAP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602

41.1. LDAP resource

The LDAP resource allows Abilis to provide the features of a LDAP server.

LDAP is an application protocol for accessing and maintaining distributed directory information services over an Internet
Protocol network, it is defined in terms of ASN.1, the latest version is Version 3 and published as RFC 4510.

The LDAP server provides organized set of records with a hierarchical structure and may be used as a corporate electronic
mail directory or a telephone directory that is a list of contacts including a name and a phone number.

The server may be accessed via LDAP clients like:

• LDAP administration tools

• LDAPAdmin http://ldapadmin.sourceforge.net/index.html

• JXplorer http://jxplorer.org/

• Advanced VoIP phones

• snom3XX serie http://www.snom.com/it/home/

• Advanced PBX

• Mail clients

• Thunderbird http://www.mozillaitalia.org/thunderbird/

• MS Outlook http://office.microsoft.com/it-it/outlook/

Note
The LDAP resource does not provide the features of a LDAP client so Abilis CPX cannot connect to
external LDAP servers.

576
Draft LDAP - Lightweight Draft
Directory Access Protocol

41.1.1. Activating the LDAP resource

Add the resource to the Abilis system using the following command:

[15:50:39] ABILIS_CPX:a res:ldap

RES:LDAP ALREADY EXISTS

The LDAP resource may already exist in the system but may not yet be active, set it active using the command:

[15:50:43] ABILIS_CPX:s act res:ldap

COMMAND EXECUTED

Caution
After adding or setting the LDAP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[09:31:37] ABILIS_CPX:s p ldap act:yes

COMMAND EXECUTED

41.1.2. LDAP resource parameters

Use the d p ldap command to display the parameters of the resource; the d p ldap ? command shows the meaning of
parameters.

[09:58:41] ABILIS_CPX:d p res:ldap

RES:Ldap ----------------------------------------------------------------------
Run DESCR:Lightweight_Directory_Access_protocol
LOG:NO ACT:YES tcp-locport:389 sesnum:10
mxps:2048 TOS:0-N DT:300
IPSRC:* IPSRCLIST:
SIZE-LIMIT:NO TIME-LIMIT:NO
max-entries:1000 USER-SYNC:NO DC-FIRST-ATTR:cn
root:dc=abilis,dc=net
wdir:C:\APP\LDAP\

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime LDAP activation/deactivation.

TOS Used to enstablish the frame priority. First field [default: 0] Second field specify the type of the frame
[N=None, D=Min. Delay, T=Max. Throughput, R=Max. Reliability, C=Min. Monetary Cost].

Refer to Type of Service to have more information.

tcp-locport Local TCP port on which LDAP service is listening [1..65535].

sesnum Total number of sessions [1..255].

mxps maximum size of LDAP message [2048..4096].

DT Inactivity disconnection time-out [300..3600 sec].

IPSRC Incoming requests: accepted source IP address [*, 1-126.x.x.x, 127.0.0.1, 128-223.x.x.x].

if net: 0.0.0.0 All IPs are allowed

In the case that one needs to restrict the access, he has to set in IPSRC the ip address of a client which
must always have access, e.g. the IP address of the administrator console, and add further IPs using
IPSRCLIST.

IPSRCLIST Incoming requests: name of the IP/IR/RU/MR list for source IP address acceptance [#, 0..9, a..z, A..Z,
_].

577
Draft LDAP - Lightweight Draft
Directory Access Protocol

If IPSRCLIST:0 List is not used

If IPSRCLIST: <list_id> The parameter contains list identifier

SIZE-LIMIT Maximum number of entries that LDAP server will return for a search operation [NO, 1..65535]

TIME-LIMIT Maximum time allowed for the search operation. If set, the result can fail of can be partial [NO,
1..65535 sec]

max-entries Maximum number of entries (Address books and contacts), in the LDAP data base [100..10000]

USER-SYNC Determines if Abilis users can be inserted into LDAP database, and kept synchronized [NO, YES]

DC-FIRST-ATTR Determines the first attribute to be used in the distinguished name (DN) of contacts [cn, uid]
(temporarily available only for the system address book)

root Specifies the distinguished name (DN) for the root entry. From 1 up to 128 Alphanumeric extended
characters. Case is preserved. Spaces are allowed. Strings holding spaces must be written between
quotation marks (E.g.: \"dc=my book,dc=my root\").

wdir Working directory where the LDAP files are stored. It cannot be empty. Physical full path in DOS
notation, i.e. starting with a drive letter in the range ['A'..'Z'] and ending with the '\' character. Max.
128 characters. Case is preserved. Spaces are allowed. Strings holding spaces must be written between
quotation marks (E.g.: "C:\My dir\").

The command that allows the configuration of the resource to be modified has the following syntax:

s p ldap par:val...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ldap; while to activate the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

41.2. LDAP tables

41.2.1. User table
This table allows the LDAP administrator to handle the LDAP accounts and the user's data auto-publication.

Use the d user command to display the parameters of the users; the d user: ? command shows the meaning of all parameters.

[21:29:02] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP: LDAP:
--------------------------------+--------------+-------------------------------
admin *** NO # # YES YES YES NO NO NO NO
guest NO # # NO NO NO NO NO NO NO

To allow an user to access LDAP, the LDAP parameter must be set to YES.

[21:29:04] ABILIS_CPX:s user:admin act:yes ldap:yes

COMMAND EXECUTED

[21:31:07] ABILIS_CPX:s user:guest act:yes ldap:yes

COMMAND EXECUTED

[21:32:02] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP: LDAP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO YES
guest YES # # NO NO NO NO NO NO YES

578
Draft LDAP - Lightweight Draft
Directory Access Protocol

In the example the LDAP account for the user admin and the user guest (anonymous) was activated.

Type the following command to create a new user with LDAP account.

[21:31:12] ABILIS_CPX:a user:test act:yes pwd:test ldap:yes

COMMAND EXECUTED

[21:34:18] ABILIS:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP: LDAP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO YES
guest YES # # NO NO NO NO NO NO YES
test *** YES # # NO NO NO NO NO NO YES

Type the following command to view user test's details:

[21:34:20] ABILIS_CPX:d user:test

Parameter: | Value:
------------------+------------------------------------------------------------
USER: test
ALIAS: test
ID: 3 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
HTTP: YES
HTTP-PROT: PLAIN,SSL
LDAP: YES
LDAP-OWN-ADDRBOOK: NO
LDAP-USER-SYNC: SYS
LDAP-NUMBER: NONE
-------------------------------------------------------------------------------

Note
This command displays only the parameters related to enabled drivers; if you want to see all the user
parameters type the d usere:<ldap_user> command.

Meaning of the most parameters:

LDAP Enables/disables the LDAP account for the user [NO, YES], the default is NO.

LDAP-OWN-ADDRBOOK Enable/disable user's personal address book [NO, YES], the default is NO. This parameter acts
only if LDAP parameter is enabled.

LDAP-USER-SYNC Determine if the user has to be added to LDAP System address book [SYS, NO, YES], the
default is SYS, that is the USER-SYNC parameter in PORT (the default is NO).

LDAP-NUMBER Determine which is the main user phone number [NONE, CTIP, CLUS CTISIP, CTIIAX]. The
number that is actually used is filtered by macroes that depends on the interface:

• CTIP, the phone number is provided by the LDAP-NUM parameter of the CTI port specified
in CTIP user parameter.

• CLUS, the phone number is provided by the LDAP-NUM parameter of the Cluster specified in
CLUS user parameter.

579
Draft LDAP - Lightweight Draft
Directory Access Protocol

• CTISIP, the phone number is provided by the SIP-LDAP-NUM user parameter (if the SIP
account is active).

• CTIIAX, the phone number is provided by the IAX-LDAP-NUM user parameter (if the IAX
account is active).

41.2.2. Rights table

The LDAP tree is composed of a root (that is configurable via the parameter root) and its branches. One branch is reserved to
the address books.

There are two kinds of addres books:

• Main

The address book is accessible from any allowed user via a ldap right table.

• Personal

The address book contains the contacts that are accessible only by the related account. A LDAP account may enable the
personal address book via the user parameter LDAP-OWN-ADDRBOOK.

There are three main address books that are automatically created:

• SYSTEM

It will contain all (and only) the synchronized contacts which information is gathered by the user table and the CTI and
CLUSTER resources. Currently the synchronized attributes are the common name and the telephone number.

• CONTACTS

It is intented to contain the contacts for internal usage in a company.

• PUBLISHED

It is intended to contain the contacts for external use, i.e. provided to third part companies.

580
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.1. An example of LDAP tree

To display the rights of the addess books use the following command.

[21:41:10] ABILIS_CPX:d ldap rights

-------------------------------------------------------------------------------
ID: ADDRESSBOOK:
USER: GRANTS:
-------------------------------------------------------------------------------
1 contacts
admin rwcd
anonymous ----
-------------------------------------------------------------------------------
2 published
admin rwcd
anonymous r---
-------------------------------------------------------------------------------
3 system
admin rw--
anonymous ----
-------------------------------------------------------------------------------

Where the rwcd chars mean:

• r - right to access the address book and read contacts

581
Draft LDAP - Lightweight Draft
Directory Access Protocol

• w - right to modify the contacts in the address book

• c - right to create new contacts in the address book

• d - right to delete contacts in the address book

In the system address book [580] the creation and the deletion of contacts is never allowed because it is internally auto-
synchronized.

The rights of Admin and Anonymous on default address books are explicit (note that by default the anonymous has access
only to published [580]), other users have implicit rights.

New users with LDAP parameter enabled have the "r" right in all the main address books (also the new ones) and the its
personal addressBook (LDAP-OWN-ADDRBOOK enabled).

If a different behavior is needed for a user, an explicit entry is added. In example to remove the visibility of system address
book to the user "test" use the following command:

[21:41:00] ABILIS_CPX:a ldap rights id:3 user:test grants:

COMMAND EXECUTED

[21:41:10] ABILIS:d ldap rights

-------------------------------------------------------------------------------
ID: ADDRESSBOOK:
USER: GRANTS:
-------------------------------------------------------------------------------
1 contacts
admin rwcd
anonymous ----
-------------------------------------------------------------------------------
2 published
admin rwcd
anonymous r---
-------------------------------------------------------------------------------
3 system
admin rw--
anonymous ----
test ----
-------------------------------------------------------------------------------

41.3. LDAP use cases

41.3.1. Publishing local VoIP users
This section instructs you to access the system address book [580] of the Abilis LDAP server and keep synchronized the
voip users.

Add and active the LDAP resource as explained in the chapter: "activating the LDAP resource".

Create a LDAP account.

[21:44:12] ABILIS_CPX:a user:test act:yes pwd:test ldap:yes

COMMAND EXECUTED

If anonymous authentication is required, the guest user must be active and its LDAP parameter enabled.

[21:44:12] ABILIS_CPX:s user:guest act:yes ldap:yes

COMMAND EXECUTED

582
Draft LDAP - Lightweight Draft
Directory Access Protocol

Note
By default the anonymous user has access just to the "published" address book, so use the command s ldap
rights id:3 user:anonymous grants:r to allow anonymous to access the system address book [580].
You may also want to limit the access of LDAP client to the LAN then use the command s p res:ldap ip-
src:192.168.0.0/16 and execute the initialization command init res:ldap.

Check the users to be kept synchronized, in this example let's created a few users.

[00:18:51] ABILIS_CPX:a user:frank iax:yes iax-number:2222

COMMAND EXECUTED

[00:18:56] ABILIS_CPX:a user:anne sip:yes sip-number:3333

COMMAND EXECUTED

[00:19:29] ABILIS_CPX:a user:george ctip:101

COMMAND EXECUTED

[00:23:56] ABILIS_CPX:a cticl clus:myclus

COMMAND EXECUTED

[00:24:05] ABILIS_CPX:s cticl clus:myclus num:7777

COMMAND EXECUTED

[00:24:08] ABILIS_CPX:a user:jack clus:myclus

COMMAND EXECUTED

Enable LDAP-USER-SYNC in each user you want to keep synchronized in the system address book [580] and specify the
phone interface via the LDAP-NUMBER user parameter.

[00:18:51] ABILIS_CPX:s user:frank ldap-user-sync:yes ldap-number:ctiiax

COMMAND EXECUTED

[00:18:56] ABILIS_CPX:s user:anne ldap-user-sync:yes ldap-number:ctisip

COMMAND EXECUTED

[00:19:29] ABILIS_CPX:s user:george ldap-user-sync:yes ldap-number:ctip

COMMAND EXECUTED

[00:24:08] ABILIS_CPX:s user:jack ldap-user-sync:yes ldap-number:clus

COMMAND EXECUTED

You may set USER-SYNC:YES in LDAP resource port but you should not use this way in most cases. You may errouneusly
synchronize users you want to keep hidden. Moreover if this parameter is switched from YES to NO you risk to lost part of
saved data (non synchronized attributes of synchronized contacts).

You may also modify, via macros, the number provided to LDAP via LDAP-NUM parameter in CTIIAX/CTISIP/CTIP/
CLUSTER interfaces.

[21:47:12] ABILIS_CPX:s user:frank iax-ldap-num:02'IAX-NUMBER'

COMMAND EXECUTED

583
Draft LDAP - Lightweight Draft
Directory Access Protocol

[21:47:33] ABILIS_CPX:s user:anne sip-ldap-num:'SIP-NUMBER.s2'

COMMAND EXECUTED

[21:48:44] ABILIS_CPX:s ctip:101 ldap-num:02'NUM'

COMMAND EXECUTED

[21:48:55] ABILIS_CPX:s cticl clus:myclus ldap-num:'NUM'123

COMMAND EXECUTED

[21:49:00] ABILIS_CPX:init res:ctisys

INIT CTI SYSTEM IN PROGRESS, THIS MAY TAKE FEW MINUTES...

COMMAND EXECUTE

Note
Any modfication to CTI ports or Clusters need the CTI system initialization via the command init res:ctisys.

Hide the address books you are not interested in via the LDAP rights table. The following commands allow just the system
address book will be visible to the user named "test".

[21:49:08] ABILIS_CPX:a ldap rights id:1 user:test grants:-r

COMMAND EXECUTED

[21:49:28] ABILIS_CPX:a ldap rights id:2 user:test grants:-r

COMMAND EXECUTED

The user may now access LDAP server via LDAP client or via Abilis web interface. To access web pages provide the LDAP
accont with additional HTTP rights.

[21:49:08] ABILIS_CPX:s user:test http:yes

COMMAND EXECUTED

[21:49:35] ABILIS_CPX:a http rights id:2 user:test file:r dir:l

COMMAND EXECUTED

To know how to read/modify/create/remove contacts via the web interface or via a LDAP client check the chapter "handling
contacts".

41.3.2. Identifying the caller in a VoIP phone

Advanced VoIP phones include a LDAP client able to translate the number of an incoming call to the corresponding contact
name. The task of this section is to configure the Abilis LDAP server to provide its contacts to VoIP phones.

Add and active the LDAP resource as explained in the chapter: "activating the LDAP resource".

You may also want to limit the access of LDAP client to the LAN (i.e. 192.168.X.X) via the ipsrc and ipsrclist parameters.

[20:09:28] ABILIS_CPX: s p ldap ipsrc:192.168.0.0

COMMAND EXECUTED

[20:11:12] ABILIS_CPX:list create ldap_allow ir

COMMAND EXECUTED

584
Draft LDAP - Lightweight Draft
Directory Access Protocol

[20:11:20] ABILIS_CPX:a list:ldap_allow 192.168.0.0:192.168.0.254

COMMAND EXECUTED

[20:14:26] ABILIS_CPX:s p res:ldap ipsrclist:ldap_allow

COMMAND EXECUTED

[20:14:30] ABILIS_CPX:d p res:ldap

RES:Ldap - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Lightweight_Directory_Access_protocol
LOG:NO ACT:YES tcp-locport:389 sesnum:10
mxps:2048 TOS:0-N DT:300
IPSRC:192.168.000.000 IPSRCLIST:ldap_allow
SIZE-LIMIT:NO TIME-LIMIT:NO
max-entries:1000 USER-SYNC:NO
root:dc=abilis,dc=net
wdir:C:\APP\LDAP\

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ldap; while to activate the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

Create a LDAP account.

[21:44:12] ABILIS_CPX:a user:test act:yes pwd:test ldap:yes

COMMAND EXECUTED

The user automatically gains the reading right over all the main address books.

If the anonymous authentication is required, the guest user must be active and its LDAP parameter enabled.

[21:44:12] ABILIS_CPX:s user:guest act:yes ldap:yes

COMMAND EXECUTED

The guest by default has not the right to access the system address book [580] and the contacts address book [580] so
let's grant it.

[13:15:27] ABILIS_CPX:s ldap rights id:1 user:guest grants:r

COMMAND EXECUTED

[13:15:27] ABILIS_CPX:s ldap rights id:3 user:guest grants:r

COMMAND EXECUTED

Let's configure a Snom 300 VoIP phone to display the LDAP attribute "common name" instead of displaying just the calling
number.

Via the web interface of the SNOM open the Advanced section page and set the following parameters:

Parameter Value
LDAP name filter (&(telephoneNumber=*)(sn=%))
LDAP number filter (&(telephoneNumber=%)(sn=*))
Server Address <IP address or FQDN of Abilis>

585
Draft LDAP - Lightweight Draft
Directory Access Protocol

Port 389
Base dc=addressBooks,dc=abilis,dc=net
Username <The name of an Abilis user allowed to LDAP
(LDAP:YES)>
Password <The password of an Abilis user allowed to LDAP
(LDAP:YES)>
LDAP name attributes cn sn displayName
LDAP number attributes mobile telephoneNumber ipPhone
LDAP display name %cn

Note
Changing the "Base" parameter you may change the scope of contacts, i.e. to access only the contacts
address book [580] set "Base" as addressBook=contacts,dc=addressBooks,dc=abilis,dc=net.

The SNOM web interface should look in this way:

Figure 41.2. SNOM 300 Advanced web page

586
Draft LDAP - Lightweight Draft
Directory Access Protocol

Now the phone will display the Common Name provided by the Abilis LDAP server instead of any known calling number.

Figure 41.3. SNOM 300 LCD when the calling number is known to LDAP server

To know how to read/modify/create/remove contacts via the web interface or via a LDAP client check the chapter "handling
contacts".

41.3.3. Mail composing and LDAP

The goal of this section is to configure a mail client (Thunderbird) to enable autocompletion when editing the recipient of a
message.

Add and active the LDAP resource as explained in the chapter: "activating the LDAP resource".

You may also want to limit the access of LDAP clients to the LAN (i.e. 192.168.X.X) via the ipsrc and ipsrclist parameters.

[20:09:28] ABILIS_CPX: s p ldap ipsrc:192.168.0.0

COMMAND EXECUTED

587
Draft LDAP - Lightweight Draft
Directory Access Protocol

[20:11:12] ABILIS_CPX:list create ldap_allow ir

COMMAND EXECUTED

[20:11:20] ABILIS_CPX:a list:ldap_allow 192.168.0.0:192.168.0.254

COMMAND EXECUTED

[20:14:26] ABILIS_CPX:s p res:ldap ipsrclist:ldap_allow

COMMAND EXECUTED

[20:14:30] ABILIS_CPX:d p res:ldap

RES:Ldap - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Lightweight_Directory_Access_protocol
LOG:NO ACT:YES tcp-locport:389 sesnum:10
mxps:2048 TOS:0-N DT:300
IPSRC:192.168.000.000 IPSRCLIST:ldap_allow
SIZE-LIMIT:NO TIME-LIMIT:NO
max-entries:1000 USER-SYNC:NO
root:dc=abilis,dc=net
wdir:C:\APP\LDAP\

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ldap; while to activate the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

Thunderbird doesn't support LDAP user authentication so let's enable the anonymous user in Abilis (guest) and set its LDAP
right to allow him to access the contacts address book [580].

[17:50:23] ABILIS:s user:guest act:yes ldap:yes

COMMAND EXECUTED

[17:51:16] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP: LDAP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES YES NO NO YES
guest YES # # NO NO NO NO NO NO YES

[17:51:24] ABILIS:s ldap rights id:1 user:anonymous grants:r

COMMAND EXECUTED

[17:52:07] ABILIS:d ldap rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: ADDRESSBOOK:
USER: GRANTS:
-------------------------------------------------------------------------------
1 contacts
admin rwcd
anonymous r---
-------------------------------------------------------------------------------
2 published
admin rwcd

588
Draft LDAP - Lightweight Draft
Directory Access Protocol

anonymous r---
-------------------------------------------------------------------------------
3 system
admin rw--
anonymous ----
-------------------------------------------------------------------------------

In Thunderbird open the Account Settings dialog (select Tools ->Account Settings) then select your account and click the
Composition & Addressing tab, finally add a new LDAP dir.

Figure 41.4. Account Settings Dialog / Composition & Addressing Tab

Click the Add button and use the following parameters.

Parameter Value

589
Draft LDAP - Lightweight Draft
Directory Access Protocol

Name <doesn't matter>

Hostname <IP address or FQDN of Abilis>
Base DN addressBook=Contacts,dc=addressBooks,dc=abilis,dc=net
Port number 389

Note
Changing the "Base DN" parameter you may change the scope of contacts, i.e. to access all main address
books set base as dc=addressBooks,dc=abilis,dc=net and execute the command s ldap rights id:3
user:anonymous grants:r

The dialog should appear in this way:

Figure 41.5. LDAP properties

Set the Abilis LDAP server as the current LDAP for this account.

Then you may try to write a mail using the "common name" of a person and Thunderbird will autocomplete the mail address
for you. In the example the "Contacts" address book include the contact of "Clark Kent", the tooltip will appear as soon as
you write a few chars.

590
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.6. Autocompletion

To know how to read/modify/create/remove contacts via the web interface or via a LDAP client check the chapter "handling
contacts".

41.4. Handling contacts

There are two ways to access the Abilis LDAP server, the Abilis web interface or a LDAP client.

41.4.1. Web Interface

To access the LDAP web interface via a browser an Abilis User must be active, must have HTTP and LDAP parameters set
to yes and must have HTTP and LDAP rights.

Using the admin account you need just to use the following command:

[21:29:04] ABILIS_CPX:s user:admin act:yes ldap:yes http:yes

COMMAND EXECUTED

If you use another account remember to allow the HTTP rights too.

[21:49:08] ABILIS_CPX:s user:test act:yes ldap:yes http:yes

COMMAND EXECUTED

[21:49:35] ABILIS_CPX:a http rights id:2 user:test file:r dir:l

COMMAND EXECUTED

Non-administrator users by default have only the "read" right. Administrator has the full control.

If you want a LDAP account be also able to modify/create/remove contacts allowing it to have full rights then issue following
commands:

[21:49:08] ABILIS_CPX:a ldap rights id:1 user:test grants:rwcd

COMMAND EXECUTED

591
Draft LDAP - Lightweight Draft
Directory Access Protocol

[21:49:28] ABILIS_CPX:a ldap rights id:2 user:test grants:rwcd

COMMAND EXECUTED

[21:49:38] ABILIS_CPX:a ldap rights id:3 user:test grants:rw

COMMAND EXECUTED

Let's use admin account in this examples, anyway you know how to use another account.

Log in the web interface as admin and click the "LDAP Address books" link.

Figure 41.7. Abilis main web page

Look at the LDAP administration page.

592
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.8. LDAP adminstration page

The administrator has full access to all the address books. The interface include also the name of Base DN for each address
book. The interface also allows to import/export a single address book.

Note
To import/export the whole LDAP DB or to handle personal address books visit the "Advanced LDAP
administration" page. Although LDAP server include disaster recovery features, a periodical backup (via
exporting) of address books or the whole DB is suggested.

Click on contacts address book [580].

593
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.9. LDAP Contacts address book

Then you may add a new contact via the "Add" button.

594
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.10. Contact details

Note
In system address book, synchronized attributes "commonName" and "telephoneNumber" cannot be edited
although having the "w" right.

595
Draft LDAP - Lightweight Draft
Directory Access Protocol

41.4.2. LDAP Client

To access LDAP server via a LDAP client install LDAPAdmin http://ldapadmin.sourceforge.net/index.html or JXplorer
http://jxplorer.org/ in a PC.

You also need an Abilis user that must have the LDAP parameter set to yes.

Using the admin account you need just to use the following command:

[21:29:04] ABILIS_CPX:s user:admin act:yes ldap:yes

COMMAND EXECUTED

If you use another account remember to allow LDAP rights too.

[21:49:08] ABILIS_CPX:s user:test act:yes ldap:yes

COMMAND EXECUTED

Non-administrator users by default have only the "read" right. Administrator has full control.

If you want a LDAP account be able also to modify/create/remove contacts allowing it to have full rights issue following
commands.

[21:49:08] ABILIS_CPX:a ldap rights id:1 user:test grants:rwcd

COMMAND EXECUTED

[21:49:28] ABILIS_CPX:a ldap rights id:2 user:test grants:rwcd

COMMAND EXECUTED

[21:49:38] ABILIS_CPX:a ldap rights id:3 user:test grants:rw

COMMAND EXECUTED

Open LDAPAdmin and create a new connection.

Let's access as user "test"

596
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.11. LDAP admin connection page

Edit following parameters.

Parameter Value
Host <IP address of Abilis>
TCP port 389
Base DN dc=abilis,dc=net
Username <The name of an Abilis user allowed to LDAP
(LDAP:YES)>
Password <The password of an Abilis user allowed to LDAP
(LDAP:YES)>

Caution
LDAP uses plain autentication on a non encrypted connection so use the account only in controlled networks
or at least use an ad hoc LDAP account (a user that can just access LDAP) to avoid to share a password with
other Abilis services for that user.

597
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.12. The address book viewed by LDAP admin tool

Add a new entry.

598
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.13. Adding a new entry

Add the obectClass organizationalPerson via the Objectclass combobox.

599
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.14. Add the objectClass

Edit attributes and set the Rdn as "cn=<common name>".

600
Draft LDAP - Lightweight Draft
Directory Access Protocol

Figure 41.15. Edit attributes

Note
Use the save button to save the entry, if you receive a message explaining that the operation cannot be
completed you may not have the permission to do such operation.

41.5. LDAP diagnostics and statistics

41.5.1. LDAP diagnostics
The following command is used to display the diagnostics of the LDAP resource:

d d ldap Shows the state of the resource and its sessions

[20:14:32] ABILIS_CPX:d d ldap

RES:Ldap ----------------------------------------------------------------------
Lightweight_Directory_Access_protocol
STATE:ACTIVE DB-LOADED:YES
CUR-SES:0 PEAK-SES:0 MAX-SES:4
ENTRIES:9/250 ATTRIBUTES:28/9000 ATTR-VALUES:39/11000
- LDAP Sessions diagnostics --------------------------------------------

601
Draft LDAP - Lightweight Draft
Directory Access Protocol

SES: State RemAdd-RemPort User

------------------------------------------------------------------------
0 IDLE 000.000.000.000-0
1 IDLE 000.000.000.000-0
2 IDLE 000.000.000.000-0
3 IDLE 000.000.000.000-0

41.5.2. LDAP statistics

The following commands are used to display the statistics of the LDAP resource:

d s ldap Shows the statistics of the LDAP resource, such as:

CHR Total number of incoming/outgoing characters from UDP.

FMR Total number of incoming/outgoing packets to UDP

LONG Total number of refused incoming packets with too long length.

BAD-FMT Total number of refused incoming malformed packets.

BAD-SRC Total number of refused incoming packets with not allowed source IP address.

TIME- Total number of timeouts.

OUT

d se ldap Shows the statistics of the LDAP resource for each session.

[20:30:09] ABILIS_CPX:d s ldap

RES:Ldap ----------------------------------------------------------------------
Lightweight_Directory_Access_protocol
--- Cleared 0 days 01:57:24 ago, on 14/11/2011 at 18:32:49 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|
LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------

[20:30:13] ABILIS_CPX:d se ldap

RES:Ldap ----------------------------------------------------------------------
Lightweight_Directory_Access_protocol
--- Cleared 0 days 01:57:29 ago, on 14/11/2011 at 18:32:48 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|
LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------
- LDAP Sessions statistics ---------------------------------------------
SES:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|
LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------
SES:1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|
LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------
SES:2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|

602
Draft LDAP - Lightweight Draft
Directory Access Protocol

LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------
SES:3
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FMR | 0| 0|
LONG | 0| |BAD-FMT | 0| |
BAD-SRC | 0| |TIME-OUT | 0| |
------------------------------------------------------------------------

603
Draft Draft

Part IV. CTI System

Draft Draft

Table of Contents
42. CTI System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
42.1. CTI System module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.2. CTI Ports configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.3. CTI Ports Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
42.3.1. POTS and CTI Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
42.4. CTI Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
42.4.1. Internal clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
42.4.2. CPO - Call path optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
42.5. CTI Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.5.1. CTI Link Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.6. CTI Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
42.6.1. Display CTI Routing Table (D CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
42.6.2. Add CTI Routing Table (A CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
42.6.3. Clear CTI Routing Table (C CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
42.6.4. Set CTI Routing Table (S CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
42.6.5. Move CTI Routing Table (M CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
42.6.6. Macro functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
42.7. CTI routing for POTS devices (“PBX Group”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
42.8. CTI System Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
42.9. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.1. CTI Ports diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.2. CTI Ports statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
42.9.3. CTI Cluster diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
42.9.4. CTI Link diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.5. CTI connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.6. DSP and Audio Coders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
42.10. Examples of CTI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.1. Configuration of a VPN to transport voice and data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.2. Configuration of a VPN to transport only voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
42.11. Soft-PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.1. Supplemetary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.2. User call logs and mails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
42.11.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
42.11.4. Administrative pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
42.11.5. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
42.12. FAX Relay with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.1. Fax over packet networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.2. Fax Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.3. Abilis configurations for best results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
42.12.4. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
42.12.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
43. The web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
43.1. The web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
43.2. Section 1 - User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.2. Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
43.2.4. Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
43.2.5. CTI incoming/outgoing calls log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
43.2.6. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
43.3. Section 2 - Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.1. IP Traffic Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.2. Operator Panel Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
43.3.3. SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
43.3.4. Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
43.4. Section 3 - Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.1. Configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.2. Users administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
43.4.3. Groups administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

605
Draft CTI System Draft

43.4.4. Lists administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

43.4.5. Disa administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
43.4.6. CTI administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
43.4.7. Voice Mail administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
44. OPC - Operator Panel Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1. OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.1. Activating the OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.2. OPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
44.2. OPC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.3. OPC Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
44.3.1. The panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
44.3.2. The table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
44.3.3. Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
44.3.4. Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
45. IAX - Inter-Asterisk eXchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1. CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1.1. Activating the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1.2. CTIIAX resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
45.2. CTIIAX tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.2. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
45.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
45.4. Example of IAX configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
45.4.1. Configuration of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.3. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
45.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
45.5. Connecting Abilis and Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.1. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.2. Activation of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.3. Example 1: Abilis and Asterisk have static IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.4. Example 2: Abilis has a static address and Asterisk has a dynamic address . . . . . . . . . . . . . . . . . . . . . . . . . 797
45.5.5. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
45.6. CTIIAX diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.1. CTIIAX diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.2. CTIIAX statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
45.6.3. Debug of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
45.7. Appendix - IAX protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
46. SIP - Session Initiation Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1. CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.1. Activating the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.2. CTISIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
46.2. CTISIP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.2. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
46.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
46.4. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
46.4.1. Activation and configuration of the CtiSip resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.3. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
46.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
46.5. Connecting Abilis and a SIP proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.1. Activation of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.2. Example: Abilis and a proxy registered in Abilis domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.3. Example: Proxy and Abilis registered in Proxy remote domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
46.5.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
46.6. Busy Lamp Field (BLF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.1. Dialog an presence monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.2. BLF in Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
46.7. CTISIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
46.7.1. CTISIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

606
Draft CTI System Draft

46.7.2. CTISIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835

46.7.3. Debug of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
46.8. Appendix - SIP protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.1. SIP and NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.2. Solution to SIP NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
46.8.3. SIP NAT Trasversal problem with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
47. DISA - Direct Inward System Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
47.1. CTIDISA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.1. User identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.2. Post-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
47.1.3. Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
47.1.4. Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.1.5. Data Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2. CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.1. Activating the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.2. CTIDISA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
47.3. CTIDISA tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
47.3.1. CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
47.3.2. CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
47.4. Example of Post Selection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
47.4.4. Configuring the CTI Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
47.5. Example of Automatic Call Distribution configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.5.4. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.6. Example of Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
47.6.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.6.4. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.7. Example of Data Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.3. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8. Message files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.1. File audio format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.2. Commands to manage audio files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.8.3. Example of insertion of WAV files and creation of CPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.9. CTIDISA diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.1. CTIDISA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.2. CTIDISA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
47.9.3. Advanced Debug of the CtiDisa resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
47.10. DISA administration through web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.1. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.2. DISA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
48. CTIAS - CTI Advanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1. CTIAS - CTI Advanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.1. Activating the CTIAS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.2. CTIAS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2. CTIVM - CTI Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.1. Activating the CTIVM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.2. CTIVM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
48.2.3. CTIVM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
48.2.4. CTIVM configuration through CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
48.2.5. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
49. CTISMS - CTI SMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1. CTISMS - CTI SMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1.1. Activating the CTISMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887

607
Draft CTI System Draft

49.1.2. CTISMS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888

49.2. CTISMS Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.1. CTISMS IN routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.2. CTISMS OUT routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
49.3. CTISMS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.1. CTISMS diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.2. CTISMS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
50. ACNT - Accounting resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1. ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.1. Activating the ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.2. ACNT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2. ACNT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.1. ACNT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.2. ACNT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
50.3. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

608
Draft Draft

Chapter 42. CTI System

Nicola Trevisani
Marco Bellesia
Luigi Demuro

Table of Contents
42.1. CTI System module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.2. CTI Ports configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
42.3. CTI Ports Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
42.3.1. POTS and CTI Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
42.4. CTI Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
42.4.1. Internal clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
42.4.2. CPO - Call path optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
42.5. CTI Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.5.1. CTI Link Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
42.6. CTI Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
42.6.1. Display CTI Routing Table (D CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
42.6.2. Add CTI Routing Table (A CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
42.6.3. Clear CTI Routing Table (C CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
42.6.4. Set CTI Routing Table (S CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
42.6.5. Move CTI Routing Table (M CTIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
42.6.6. Macro functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
42.7. CTI routing for POTS devices (“PBX Group”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
42.8. CTI System Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
42.9. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.1. CTI Ports diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
42.9.2. CTI Ports statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
42.9.3. CTI Cluster diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
42.9.4. CTI Link diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.5. CTI connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
42.9.6. DSP and Audio Coders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
42.10. Examples of CTI configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.1. Configuration of a VPN to transport voice and data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
42.10.2. Configuration of a VPN to transport only voice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
42.11. Soft-PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.1. Supplemetary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
42.11.2. User call logs and mails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
42.11.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
42.11.4. Administrative pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
42.11.5. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
42.12. FAX Relay with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.1. Fax over packet networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.2. Fax Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
42.12.3. Abilis configurations for best results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
42.12.4. Diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
42.12.5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

609
Draft CTI System Draft

42.1. CTI System module

The Abilis CTI1 (Computer Telephony Integration) System module (CTISYS) works at the network (level 3) and transport-
level (level 4) of the ISO-OSI model.

The CTISYS is a smart switch able to exchange both circuit-switched telephony channels (TDM) and packet-switched (VoIP,
VoN) channels with all the reasonable degrees of freedom:

• packet channels to TDM ones;

• TDM to packet;
• TDM to TDM;
• packet to packet.

The table below shows the different types of connection supported by the CTI System:

Table 42.1. CTI connection side types

Type Description
DATA Data: data connection (HDLC framing) from Abilis CPX to
ISDN port or from ISDN port to Abilis CPX.
V Voice: digital voice stream.
C Cluster: compressed voice stream in form of data packets.
H H.323: connection to a device that supports H.323 protocol.
I IAX: connection to a device that supports IAX protocol.
S SIP: connection to a device that supports SIP protocol.
D DISA: connection to the Direct Inward System Access.

All the possible combinations of connections are possible; for more details refer to CTIR section; IAX, SIP and DISA
routings are explained in the corresponding chapters.

The bandwidth depends on the used coder: G.711, G.726, G.727, GSM6.10, Spirit, G.723.1, G.729A, Transp

For compressed phone calls directly sent onto the Frame Relay network, a Spirit 723 coder with net compression at 6400 bps
and gross space memory of 8800 bps are usually used.

On an IP network the bandwidth is 22 kbps for the first call, the following simultaneous calls (from the same source to the
same destination) add a bandwidth of only 8,8 kbps for each single call.

42.2. CTI Ports configuration

When an ISDN or POTS device (QPRIX, BRI8, BRI4, BRIO, POTS,…) is added in the configuration also its related CTI
ports are activated (for further informations refer to Section 5.5, “Devices”).

The following command modifies the parameters of a CTI port:

s p ctip:<port_number> <parameter>:<value>

The commands d p ctip ? or d p ctipe ? shows available parameters.

Here is an example of configuration of a BRI card.

[12:38:14] ABILIS_CPX:s p ctip:31 side:NT line:PP descr:to_PBX

COMMAND EXECUTED

[12:38:14] ABILIS_CPX:s p ctip:32 side:NT line:PP descr:to_PBX

COMMAND EXECUTED

[12:38:14] ABILIS_CPX:s p ctip:33 side:TE line:PP descr:to_ISDN_line

COMMAND EXECUTED

1
http://en.wikipedia.org/wiki/Computer_telephony_integration

610
Draft CTI System Draft

[12:38:14] ABILIS_CPX:s p ctip:34 side:TE line:PP descr:to_ISDN_line

COMMAND EXECUTED

[12:38:14] ABILIS_CPX:d p ctip

CTIP:31 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_PBX
Run card:BRI4-1<1>
OPSTATE:UP LOG:NO side:NT line:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri BUS:SHORT NUM:*
BCHANS:ALL-BID

CTIP:32 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_PBX
Run card:BRI4-1<2>
OPSTATE:UP LOG:NO side:NT line:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri BUS:SHORT NUM:*
BCHANS:ALL-BID

CTIP:33 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_ISDN_line
Run card:BRI4-1<3>
OPSTATE:UP LOG:NO side:TE LINE:PP TYPE:NET-PUBLIC
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri L12-ACT:AUTO BUS:SHORT NUM:*
BCHANS:ALL-BID

CTIP:34 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_ISDN_line
Run card:BRI4-1<4>
OPSTATE:UP LOG:NO side:TE LINE:MP TYPE:NET-PUBLIC
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri L12-ACT:AUTO BUS:SHORT NUM:*
BCHANS:ALL-BID

[16:24:15] ABILIS_CPX:d p ctipe:31

CTIP:31 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_PBX
Run card:BRI4-1<1>
OPSTATE:UP LOG:NO side:NT line:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:YES CT:BOTH SS:NO
mode:Bri BUS:SHORT NUM:*
BCHANS:ALL-BID
X25:NO (XTEI:10) XK:7 XN200:3 xn201:260 XN202:3
XT200:1 XT202:2 XT203:10
Q931:YES (QTEI:0) QK:1 QN200:3 qn201:260 QN202:3 QT200:1
QT202:2 QT203:10 TDISC:90 QT301:180 QT302:15 QT303:4
QT304:30 QT305:30 QT308:4 QT310:30 QT313:6 QT316:15
DIALT:5 scrst:YES ORCD:0 ICT-T1:500 ICT-T2:500
SQNRTY1:15 SQDELAY1:30 SQDELAY2:5
LCS-GROUP:NONE BUSY-NOCHAN:NO OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:NO CLIP-RULE:PRIVATE
SS-CF-DND:YES

[16:24:19] ABILIS_CPX:d p ctipe:32

CTIP:32 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

611
Draft CTI System Draft

Act DESCR:to_PBX
Run card:BRI4-1<2>
OPSTATE:UP LOG:NO side:NT line:PP TYPE:USER
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri BUS:SHORT NUM:*
BCHANS:ALL-BID
X25:NO (XTEI:10) XK:7 XN200:3 xn201:260 XN202:3
XT200:1 XT202:2 XT203:10
Q931:YES (QTEI:0) QK:1 QN200:3 qn201:260 QN202:3 QT200:1
QT202:2 QT203:10 TDISC:90 QT301:180 QT302:15 QT303:4
QT304:30 QT305:30 QT308:4 QT310:30 QT313:6 QT316:15
DIALT:5 scrst:YES ORCD:0 ICT-T1:500 ICT-T2:500
SQNRTY1:15 SQDELAY1:30 SQDELAY2:5
LCS-GROUP:NONE BUSY-NOCHAN:NO OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:NO CLIP-RULE:PRIVATE
SS-CF-DND:YES

[16:24:24] ABILIS_CPX:d p ctipe:33

CTIP:33 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_ISDN_line
Run card:BRI4-1<3>
OPSTATE:UP LOG:NO side:TE LINE:PP TYPE:NET-PUBLIC
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri L12-ACT:AUTO BUS:SHORT NUM:*
BCHANS:ALL-BID
X25:NO (XTEI:10) XK:7 XN200:3 xn201:260 XN202:3
XT200:1 XT202:2 XT203:10
Q931:YES (QTEI:0) QK:1 QN200:3 qn201:260 QN202:3 QT200:1
QT202:2 QT203:10 TDISC:90 QT301:180 QT302:15 QT303:4
QT304:30 QT305:30 QT308:4 QT310:30 QT313:6 QT316:15
DIALT:5 scrst:YES ORCD:0 ICT-T1:500 ICT-T2:500
SQNRTY1:15 SQDELAY1:30 SQDELAY2:5
LCS-GROUP:NONE BUSY-NOCHAN:NO OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:NO CLIP-RULE:PRIVATE
SS-CF-DND:YES

[16:24:25] ABILIS_CPX:d p ctipe:34

CTIP:34 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_ISDN_line
Run card:BRI4-1<4>
OPSTATE:UP LOG:NO side:TE LINE:PP TYPE:NET-PUBLIC
signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:NO
mode:Bri L12-ACT:AUTO BUS:SHORT NUM:*
BCHANS:ALL-BID
X25:NO (XTEI:10) XK:7 XN200:3 xn201:260 XN202:3
XT200:1 XT202:2 XT203:10
Q931:YES (QTEI:0) QK:1 QN200:3 qn201:260 QN202:3 QT200:1
QT202:2 QT203:10 TDISC:90 QT301:180 QT302:15 QT303:4
QT304:30 QT305:30 QT308:4 QT310:30 QT313:6 QT316:15
DIALT:5 scrst:YES ORCD:0 ICT-T1:500 ICT-T2:500
SQNRTY1:15 SQDELAY1:30 SQDELAY2:5
LCS-GROUP:NONE BUSY-NOCHAN:NO OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:NO CLIP-RULE:PRIVATE
SS-CF-DND:YES

Meaning of the most important parameters:

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log;
A: Alarm view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes)

side Port behaviour [TE: if the port is connected to an ISDN line; NT: if the port is connected to a PBX].

612
Draft CTI System Draft

LINE Line type [MP if the line is Multi-Point; PP if the line is Point-to-Point].

NUM Phone number assigned to CTI port. The available values are:

• *: the Calling Number offered by CTIR is passed transparently to the device;

• #: the Calling Number is not passed to the device;

• ##: enforces the presentation restricted: the Calling Number is not passed to the device;

• nnnn: exactly this number is passed as Calling Number to the device;

• nnnn*: the Calling Number received from CTIR is modified by replacing first four digits with
nnnn;

• nnnn??: similar to nnnn* with the difference that only an exact number of digits as many ? is
passed after nnnn;

• ????: only an exact number of digits as many ? is passed after the nnnn.

SS Enable/disable supplementary services accessible through "*" as first digit in called number [NO, YES]

SS-PICKUP Supplementary service. Pickup permissions [NO, GROUP, ANY]

SS-CF-DND Supplementary service. Call forwarding and Do-Not-Disturb [NO, YES]

SS-PRES-CG Supplementary service. Calling present [NO, YES]

OUT-DIAL-TONE Enable/disable the outside dial tone generation [SYS, NO, YES] <Only for mode: equal to E1-ISDN,
Bri or Pots>.

LCS-GROUP Last Calling number Service group identifier [NONE, 1..32] <Only for mode: not equal to Pots>

Here is an example of configuration of a POTS port.

[20:47:01] ABILIS_CPX:s p ctip:101 num:18 descr:phone_1

COMMAND EXECUTED

[20:47:01] ABILIS_CPX:d p ctip:101

CTIP:101 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:phone_1
Run card:POTS-1<1>
OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:18

[20:47:59] ABILIS_CPX:d p ctipe:101

CTIP:101 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:phone_1
Run card:POTS-1<1>
OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:18
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:YES

Meaning of the most important parameters:

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log;
A: Alarm view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes)

613
Draft CTI System Draft

NUM Phone number assigned to CTI port. The available values are:

• *: the Calling Number offered by CTIR is passed transparently to the device;

• #: the Calling Number is not passed to the device;

• ##: enforces the presentation restricted: the Calling Number is not passed to the device;

• nnnn: exactly this number is passed as Calling Number to the device;

• nnnn*: the Calling Number received from CTIR is modified by replacing first four digits with
nnnn;

• nnnn??: similar to nnnn* with the difference that only an exact number of digits as many ? is
passed after nnnn;

• ????: only an exact number of digits as many ? is passed after the nnnn.

SS Enable/disable supplementary services accessible through "*" as first digit in called number [NO, YES]

SS-PICKUP Supplementary service. Pickup permissions [NO, GROUP, ANY]

SS-CF-DND Supplementary service. Call forwarding and Do-Not-Disturb [NO, YES]

SS-PRES-CG Supplementary service. Calling present [NO, YES]

OUT-DIAL-TONE Enable/disable the outside dial tone generation [SYS, NO, YES] <Only for mode: equal to E1-ISDN,
Bri or Pots>.

CLIP Caller Identification Presentation [NO, YES, EXT, SYS]

MIN-FLASH Minimal duration of the on-hook transition to detect a FLASH [SYS, 50..1000 ms]

MAX-FLASH Maximal duration of the on-hook transition to detect a FLASH [SYS, 50..1000 ms]

IN-GAIN-ADJ Input (Receive) gain adjustment respect to the gain present in the country coefficient file [SYS, MUTE,
COUNTRY, -12..+12 dB]

OUT-GAIN-ADJ Output (Transmit) gain adjustment respect to the gain present in the country coefficient file [SYS,
MUTE, COUNTRY, -12..+12 dB]

Caution
To activate the changes made on the upper case parameters, execute the initialization command init ctisys;
while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are required
(i.e. with warm start command).

42.3. CTI Ports Group

CTI ports can be grouped to simplify the routing management; groups created can be used in CTI Routings Table as if they
were an unique logical port.

Use the following commands to manage the CTI Groups:

• a ctig id:xx [par:value] : adds a new CTI Group

• s ctig id:xx [par:value] : sets a CTI Group

• c ctig id:xx : clears a CTI Group

• d ctig : displays the CTI Group table

The d ctig ? command shows all available parameters.

Here is an example: the G1 group contains the BRI ports (ctip:31 and ctip:32) towards PBX, the G2 group contains the BRI
ports towards ISDN lines (ctip:33 and ctip:34).

[12:38:19] ABILIS_CPX:a ctig id:1 p1:31 p2:32 descr:to_PBX

COMMAND EXECUTED

614
Draft CTI System Draft

[12:38:19] ABILIS_CPX:a ctig id:2 p1:33 p2:34 descr:to_ISDN_line

COMMAND EXECUTED

[12:38:19] ABILIS_CPX:d ctig

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

--------------------------------------+--------------------+-------------------
[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
to_PBX
1 NO R ST |31 32 . . . |. . . . .
--------------------------------------+--------------------+-------------------
to_ISDN_line
2 NO R ST |33 34 . . . |. . . . .
--------------------------------------+--------------------+-------------------

Meaning of the most important parameters:

SCAN It establishes the algorithm with which the ports listed in the group are scanned. The available values are:

• R: stands for “Round-Robin” algorithm and it indicates that the scanning of the ports occurs in a circular
manner, ensuring that all of them are evenly utilized;

• P: stands for “Priority” algorithm and it is used to indicate that the ports are scanned starting from the first to
the last;

• M: stands for “Multicasting” algorithm and it is used to indicate that all the port are alerted simultaneously.

RULE It establishes the rule with which the CTI router will try the connection on the next port listed in the group, in the
case that the connection on the previous port fails. The available values are:

• ST: the next port is used only for following codes: “internal causes” (i.e. those with location=0xFF), “0x92 no
user responding”, “all causes in classes 02, 05, 06” (0xA2-0xAF, 0xC1-0xCF, 0xD1-0xDF);

• IN: the next port is used only for internal causes (i.e. those with location=0xFF);

• UN: the next port is always evaluated if the previous one fails;

• EU: at this moment it works like UN.

PICKUP Enables/disables the group for call pickup; generally used for POTS ports.

Caution
Changes made on the CTI Groups are not immediately active. To activate them, execute the initialization
command init ctir.

42.3.1. POTS and CTI Group

A special group, called PBX, exists for POTS cards . See the relative section in the paragraphs below to understand how to
use it.

The most important features which the CTI Group allows on CTI POTS ports are:

• MULTICASTING: allows simultaneously alert to more CTI POTS ports;

• PICK-UP: allows answering an incoming call on a phone, from another one connected to the same POTS card.

The configuration of these two features is made on CTI Group (as shown above).

[12:16:29] ABILIS_CPX:d ctig

[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64

615
Draft CTI System Draft

--------------------------------------+--------------------+-------------------
1 NO R ST |101 102 103 104 . |. . . . .
--------------------------------------+--------------------+-------------------

In a CTI Group, add the ports which must be alerted simultaneously and set the scanning method parameter SCAN:M, to
activate Multicasting.

In a CTI Group add the ports which must support this service and set the Pick-Up parameter PICKUP:Y to activate Pick-up.

There are two methods for using the Pick-Up:

• Generic call Pick-Up: allows the Pick-Up of the incoming call on all phones connected to the CTI ports that belong to the
CTI group; if more than one call is coming in, the oldest one will be picked-up. The operation is:

• pick-up the telephone handset;

• dial “* 0” (asterisk than zero).

• Specific call Pick-Up: allows the pick-up of a specific incoming call on a specific phone connected to the CTI ports that
belong to the CTI group. The operation is:

• pick up the telephone handset;

• dial “* 1+NUM” (asterisk, than one, then the value of the parameter NUM assigned to the correspondent CTI POTS
port, i.e.*104 )

42.4. CTI Cluster

A “Cluster” identifies a connection, used to transport compressed phone calls, between two Abilis. Each cluster is identified
with a clear label registered in the Abilis configuration.

The following commands to manage the CTI Clusters use:

• a cticl id:xx [par:value] : adds a new CTI Cluster

• s cticl id:xx [par:value] : sets a CTI Cluster

• c cticl id:xx : clears a CTI Cluster

• d cticl : displays the CTI Cluster table

The d cticl ? command shows all available parameters.

The example below shows how to add the cluster Abilis2 (the number associated to the cluster is 0123456).

[15:17:02] ABILIS_CPX:a cticl id:Abilis2 descr:Cluster_to_Abilis2 num:0123456

COMMAND EXECUTED

[15:17:32] ABILIS_CPX:d cticl

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Clusters:6 Activated Clusters:8

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
Abilis2 Cluster_to_Abilis2
[ 1] ue* DISABLE NO NONE PRIVATE
0123456 NO

Meaning of the most important parameters:

CG-IN-REWRITE Rewrites the calling number received from the cluster, after NUMx and NUM processing.

RG-IN Enable/disable management of incoming redirecting [DISABLE, ENABLE].

616
Draft CTI System Draft

SS Enable/disable supplementary services [NO, YES].

CPO Sets for which direction the Call Path Optimization is allowed [NO: Call Transfer is not sent out and
it is ignored in input, IN: Call Transfer is accepted in input but it is not sent out, OUT: Call transfer is
sent out but it is ignored in input, BID: Call Transfer is sent out and it is accepted in input].

NUM Phone number assigned to the CTI cluster. The available values are:

• *: the Calling Number offered by CTIR is passed transparently to the device;

• #: the Calling Number is not passed to the device;

• ##: enforces the presentation restricted: the Calling Number is not passed to the device;

• nnnn: exactly this number is passed as Calling Number to the device;

• nnnn*: the Calling Number received from CTIR is modified by replacing first four digits with
nnnn;

• nnnn??: similar to nnnn* with the difference that only an exact number of digits as many ? is
passed after nnnn;

• ????: only an exact number of digits as many ? is passed after the nnnn.

NUMx additional phone number(s) assigned to this cluster.

LCS-GROUP Last Calling number Service group identifier [NONE, 1..32]

CLIP-RULE Specifies the treatment of the CG number for calls TO the cluster (OUTGOING) [PRIVATE, PUBLIC]. If
PRIVATE the CG is sent unmodified, if PUBLIC the CG is emptied when PI is set to RESTRICTED.

A list of cluster numbers (NumClus) is automatically generated by the system; it contains the correspondence between
Clusters and their respective numbers.

[15:22:55] ABILIS_CPX:d list

List-Number:1 Items-Number:0 Used-Resources:80 Free-Resources:30640

Id Name Type Description St Ref First Numb

-------------------------------------------------------------------------------
1 NumClus CLNUM Automatically_generated_CT... R 0 0 0
-------------------------------------------------------------------------------
IN:ISDN Numbers, IS:ISDN Sub Addresses, EC:CTI Clusters,
XN:X25 NUAs, XU:X25 UDFs, IP:IP Addresses,
IR:IP Addresses Ranges, DN:Dialing Numbers, CR:CPX resources,
TUP:TCP and UDP ports ranges, IPT:Internet Protocols, MAC:MAC Addresses,
SAP:SAP values, H323ID:H.323 ID aliases, CLNUM:CTICL Numbers,
INR:ISDN Numbers Replacements, IN2T:ISDN Numbers to Text, TXT:Text,
OPC:OPC Unique User IDs, ICAUSE:ISDN Cause codes,
RU:Rules, MR:Master Rules.
-------------------------------------------------------------------------------

[15:29:34] ABILIS_CPX:d list:NumClus

LIST:NumClus - CLNUM
Automatically_generated_CTI_Clusters_Numbers_list_(ReadOnly)
Number CtiCluster
0123456 Abilis2

This list can be used to simplify the structure of the CTI Routings : an unique rule can route all the calls for the Clusters, by
verifying the called number configured. See the example in the CTI Routing section further details.

Caution
Changes made on the CTI Clusters are not immediately active. To activate them, execute the initialization
command init ctisys.

617
Draft CTI System Draft

42.4.1. Internal clusters

Internal clusters are clusters which point one another and located in the same Abilis. They can be created using packet voice
resources with parameters LOCIPADD and REMIPADD equal to the local ip address of Abilis.

Tip
Interesting chapters: Chapter 36, Tunneling proprietary protocols.

Figure 42.1. Internal clusters

42.4.1.1. Configuring packet voices

Add two Packets Voice over IP and configure them as below:

[17:07:13] ABILIS_CPX:a res:pv-10 subtype:ip

COMMAND EXECUTED

[17:07:22] ABILIS_CPX:a res:pv-11 subtype:ip

COMMAND EXECUTED

[17:08:46] ABILIS_CPX:s p pv-10 remport:3111 remipadd:192.168.1.1 descr:Internal_Cluster_1 MPX:YES

618
Draft CTI System Draft

COMMAND EXECUTED

[17:08:58] ABILIS_CPX:s p pv-11 remport:3110 remipadd:192.168.1.1 descr:Internal_Cluster_2 MPX:YES

COMMAND EXECUTED

[[15:04:20] ABILIS_CPX:d p pv-10

RES:Pv-10 - PV over IP (Abilis tunnel) (IP) -----------------------------------

DESCR:Internal_Cluster_1
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:3110 REMPORT:3111 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.001) REMIPADD:192.168.001.001

[15:04:24] ABILIS_CPX:d p pv-11

RES:Pv-11 - PV over IP (Abilis tunnel) (IP) -----------------------------------

DESCR:Internal_Cluster_2
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:STD D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:YES
LOCPORT:3111 REMPORT:3110 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:R-ID (192.168.001.001) REMIPADD:192.168.001.001

Caution
After adding or setting the resources active, you must restart the Abilis to make the device running (use the
command warm start to reboot the Abilis).

Tip
Interesting chapter: Section 36.2, “Configuring Packet Voice tunnels”.

42.4.1.2. CTI clusters configuration

Add two clusters:

[17:16:38] ABILIS_CPX:a cticl clus:Clus1 descr:Internal_Cluster_1

COMMAND EXECUTED

[17:16:59] ABILIS_CPX:a cticl clus:Clus2 descr:Internal_Cluster_2

COMMAND EXECUTED

[17:17:39] ABILIS_CPX:d cticl

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Clusters:2 Activated Clusters:8

619
Draft CTI System Draft

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
Clus1 Internal_Cluster_1
[ 1] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------
Clus2 Internal_Cluster_2
[ 2] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------

Caution
To activate the changes made, execute the initialization command init res:ctisys. and the command save
conf to make changes permanent.

Tip
Interesting chapters: Section 42.4, “CTI Cluster”.

42.4.1.3. CTI link configuration

Associate the Packets Voice and the Clusters in the CTI Link table:

[17:18:00] ABILIS_CPX:a ctil id:1 res:Pv-10 clus:clus1

COMMAND EXECUTED

[17:18:09] ABILIS_CPX:a ctil id:2 res:Pv-11 clus:clus2

COMMAND EXECUTED

[17:20:23] ABILIS_CPX:d ctil

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Links:2 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 Pv-10 Clus1 NOMAX NOMAX NONE
2 Pv-11 Clus2 NOMAX NOMAX NONE

Caution
To activate the changes made, execute the initialization command init res:ctisys. and the command save
conf to make changes permanent.

Tip
Interesting chapters: Section 42.5, “CTI Link”.

42.4.2. CPO - Call path optimization

The call path optimization allows to optimize the path of calls. Supposing to have the following scheme:

620
Draft CTI System Draft

A call is received by Abilis 1 and the operator routes the call toward Abilis 2. Then the remote user reroutes the call toward
the Operator. Without CPO the calls (one from Abilis 1 to Abilis2 and one from Abilis 2 to Abilis 1) remain active and can
cause a degradation of the quality.

With CPO active the calls drawed with dotted lines are closed and the initial one remains active.

Note
CPO feature is available also for IAX and SIP resources.

621
Draft CTI System Draft

42.5. CTI Link

To transfer compressed phone calls the CTI Link associates a cluster with a data resource.

The following commands to manage the CTI Links use:

• a ctil id:xx [par:value] : adds a new CTI Link;

• s ctil id:xx [par:value] : sets a CTI Link;

• c ctil id:xx : clears a CTI Link;

• d ctil : displays the CTI Link table.

The d ctil ? command shows all available parameters.

The example below shows how to associate the cluster Abilis2 with the resource pv-1.

[15:55:24] ABILIS_CPX:a ctil id:1 res:pv-1 clus:abilis2 maxbw:64000

COMMAND EXECUTED

[15:55:35] ABILIS_CPX:d ctil

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Links:1

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 Pv-1 Abilis2 64000 NOMAX NONE

Tip
For each CTI Link you can define a maximum bandwidth to use with compressed phone calls; this could be
very interesting if you want to limit the number of calls toward a specific direction. A link inside a group
and a further maximum bandwidth (GROUP-MAXBW) can be configured.

Caution
Changes made on the CTI Links are not immediately active. To activate them, execute the initialization
command init ctisys.

42.5.1. CTI Link Group

CTI Link can be joined together in groups. For each group a value of MAX Bandwidth can be established. This can be very
useful to limit the number of simultaneous compressed calls for the CTI Links which belong to the group.

The following commands to manage the CTI Link Groups use:

• a ctilg id:<ctilg_number> [group-maxbw:<maxbw_value>] [descr:<description>] : adds a new CTI Link Group;

• s ctilg id:<ctilg_number> [group-maxbw:<maxbw_value>] [descr:<description>] : sets an existing CTI Link Group;

• c ctilg id:<ctilg_number> : clears a CTI Link Group;

• d ctilg [id:<ctilg_number>] : displays the list of CTI Link Group or a specific one.

The d ctilg ? command shows all available parameters. The Example below shows how to create a new CTI Link Group and
how join a CTI Link in the group.

[09:31:12] ABILIS_CPX:a ctilg id:1 group-maxbw:64000 descr:Collaborators

622
Draft CTI System Draft

COMMAND EXECUTED

[09:37:00] ABILIS_CPX:d ctilg

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

ID: GROUP-MAXBW: GROUP-MAXCON: DESCR:

-------------------------------------------------------------------------------
1 64000 NOMAX Collaborators

[11:28:10] ABILIS_CPX:d ctil

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 Pv-1 Abilis2 64000 NOMAX NONE

[11:28:23] ABILIS_CPX:s ctil id:1 group:1

COMMAND EXECUTED

[11:28:43] ABILIS_CPX:d ctil

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 Pv-1 Abilis2 64000 NOMAX 1 ( 64000 NOMAX)

Caution
Changes made on the CTI Link Groups are not immediately active. To activate them, execute the
initialization command init ctisys.

42.6. CTI Router

The CTI Router is a smart telephone exchange. As a simplified description we may say that CTI Router processes an
incoming call in following steps: it receives the call request, it finds an appropriate routing, it performs the outgoing call.

To manage the CTI Router the following commands are used:

• d ctir : displays the CTI Routing table or a specific routing;

• a ctir : adds a new CTI routing;

• c ctir : deletes an existing CTI routing;

• s ctir : modifies an existing CTI routing;

• m ctir : moves an existing CTI routing.

The d ctir ? command shows all available parameters.

The following table explanes the meaning of those special values.

623
Draft CTI System Draft

Table 42.2. Special characters and values available in CTI routing table

Value Description Examples

* can be used to replace a sequence of CDI:*, CDI:2345*, CDI:*456
digits or a part of it (at the beginning or
the end of a sequence)
? in a sequence of numbers it can be used CDI:4??, CDI:???234, CDI:34??67,
to mean “any digit” CDI:123?
# means “NONE” CGO:#
## forces disallow CGO:##
#! forces allow CGO:#!
PBX CTI POTS Port group POO:PBX
CtiH323 H.323 connection POO:CtiH323
CtiIax IAX connection POO:CtiIax
CtiSip SIP connection POO:CtiSip
CtiDisa DISA connection POO:CtiDisa
CtiSLink DATA connection POO:CtiSLink
'list' specification of an element list, type IN CDI:'node', CDI:'ToAbilis2'
(list of ISDN numbers) or RU (Rule), or
MR (Master Rule)
'macro' macro functions CDO:'CDI.S2'
<AUTO-I> , <AUTO-O> special value of DS field <Only for DS:<AUTO-I> , DS:<AUTO-O>
TYPE:VtoC/CtoC/ItoC/StoC/DtoC>

Tip
The characters * and ? can be combined, example: “*2??35?” or “15??74*”.

42.6.1. Display CTI Routing Table (D CTIR)

It shows the CTI routings table in a short format. If priority is omitted, the command shows all routings.

[12:06:58] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------

Below the meaning of the most important parameters:

624
Draft CTI System Draft

• TYPE: Type of the connection [TR, DATA, VtoC, VtoH, VtoI, VtoS, VtoD, CtoV, CtoC, CtoH, CtoI, CtoS, CtoD, HtoV,
HtoC, HtoH, HtoI, HtoS, HtoD, ItoV, ItoC, ItoH, ItoI, ItoS, ItoD, StoV, StoC, StoH, StoI, StoS, StoD, DtoV, DtoC, DtoH,
DtoI, DtoS, DtoD, *toV, *toC, *toH, *toI, *toS, *toD]

• POI: Input CTI port/group

• POO: Output CTI port/group

• CDI: Called Input Number

• CDO: Called Output Number

• CGI: Calling Input Number

• CGO: Calling Output Number

Note
The values of parameters CDI, CDO, CGI, CGO, can be optionally preceeded by TON (Type Of
Number). TON can have the following values:

u Unknown
i International number
n National number
o (Operator network) Network specific number
s Subscriber number
c (Coded) Abbreviated number
h Alphanumeric (GSM/UMTS only)

• NEXT: allows searching for an alternative routing in the CTI routings table, when the primary routing fails. The admitted
values are the following:

• N (or No): in the event of failure of the routing, no procedure for seeking an alternative routing is put into effect.

• L (or Limited): next routing is evaluated only for internal causes, i.e. those with location=0xFF (i.e. network out
of service, all channels engaged, etc…);

• U (or Unlimited): next routing is evaluated for every cause except: 0x91 (user busy) or 0x93 (no user responding,
user alerted);

• T (or Transfer): next routing is always evaluated.

• BB (or ButBusy): next routing is evaluated for any reason except BUSY.

• DS: Destination Cluster identifier [0..9, A..Z, a..z, _, :].

Besides, two special values of DS (Destination Cluster) are available on VtoC, ItoC, DtoC, StoC and CtoC routings, to
simplify the structure of the CTIR:

• <AUTO-I> : by specifying this value in DS, the routing will be matched according to the standard rules. The destination
cluster will be chosen by comparing the field CDI with the NUMs set in each cluster. When the match is found, the
correspondent cluster will be the real destination of the call.

• <AUTO-O> : by specifying this value in DS, the routing will be matched according to the standard rules. The
destination cluster will be chosen by comparing the field CDO with the NUMs set in each cluster. When the match is
found, the correspondent cluster will be the real destination of the call.

Lists can be used to simplify the structure of the CTI Routings: an unique instruction can route all the calls of the Clusters,
by verifying the configured called number. See the example in the CTI Routing section for further details.

• SR: Source Cluster identifier [0..9, A..Z, a..z, _, :] or “#”, or “*”, or a list name “list”. <Only for TYPE:CtoVCHISD/
*toVCHISD>

• T301(Alerting time-out): defines the Alerting time-out, which is the duration of the call alerting state. When the time-
out expires, administrator may choose to end the call or carry out a search for an alternative routing by configuring the

625
Draft CTI System Draft

NEXT parameter. [Dft (default): this time-out corresponds to the time-out defined by the Provider of the ISDN line or by
the devices (i.e. PABX) connected to the Abilis].

• LCS: Enable/disable Last Calling number Service [NO, YES] <Only for POO: not equal to CtiSlink, CtiH323, and
CtiDisa>

• LCST: Last Calling number Service records timeout [Sys, NONE, 1..999 hour] <Only for POO: not equal to CtiSlink,
CtiH323, and CtiDisa>

• RGI: Input redirecting address [0..9, *, #, ?, 'list'], optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
and/or PI [a, r, m, q] and/or SI [y, v, w, z, j] attributes, or [##, $].

• RGO: Output redirecting address [0..9, *, #, 'macro'], optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d,
t, l, p] and/or PI [a, r, m, q] and/or SI [y, v, w, z] attributes. (E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5', 12''listname''34)

• TI1..TI5 (Time band of validity of the routing): these parameters allow the user to specify up to 5 time bands for which
the CTI routing can be used.

The time bands must be indicated in the following form:

ggg-hh1:mm1-hh2:mm2

where:

• ggg: is the indication of the day/s of the week in which the routing can be utilized and can assume the following values:

• single day: [MO, TU, WE, TH, FR, SA, SU]

• a set of days: (es.: MO+TH or TU+TH+SU etc.)

• an interval: (es.: MO-WE or TH-SU etc. or ALL)

• hh1:mm1: is the indication of the beginning of the hourly interval of the validity of the routing

• hh2:mm2: is the indication of the end of the hourly interval of the validity of the routing

Default values are TI1:ALL,00:00-23:59 and TI2...TI5:#: routing is valid on all days of the week (ALL) throughout the
day (from 00.00 to 23.59). The value # on other TI means that the time intervals are disabled.

By specifying a priority value, the command shows the routing identified by specified priority.

[12:07:00] ABILIS_CPX:d ctir pr:2

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------

The routings are scanned in sequence starting from the lowest priority. When a call arrives, all its parameters are compared
with the rules of the table. The one which satisfies all the parameters will be matched; otherwise, the CTI Router will go on
with the scan.

The command d ctire shows an extended view of the CTI routings,

[12:07:19] ABILIS_CPX:d ctire pr:2

-------------------------------------------------------------------------------

626
Draft CTI System Draft

PR:23 DESCR:
ACT:YES EDT:NO
TYPE:VtoC POI:G1 DS:Abilis2 EEC:NO
NEXT:UNLIMITED CDI:'ToAbilis2' CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:6400 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:Sys
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

Meaning of the routing: if a VtoC call comes from CTI group G1 (POI:G1), the called number belongs to the list
ToAbilis2 (CDI:'ToAbilis2'), routes it to the cluster Abilis2. The parameter NEXT:Unlimited routes the call to the
next routing if this one fails.

Viewing CTIR rules in a reduced format can be done using:

[11:19:20] ABILIS_CPX:d ctirr pr:1

Last change: 12/12/2010 11:01:00 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
1 StoV CtiSip PBX 5?? *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------

Meaning of the routing: if Stov call comes from ctisip resource and the called number is made by three digits, starting with
5, the call is routed toward the special group PBX. The parameter SP is set to 64000 and the parameter CODERS is set to
G.711, so only sip call using this codec will be accepted.

42.6.1.1. Display Cti Routing Table using filters

Using filters may help to search the desidered rule/s.

[15:52:50] ABILIS_CPX:_d ctire ?

D CTIR[E|R] Display all CTI Routings

D CTIR[E|R] filter:val [filter:val] Display any CTI Routing matching the
specified filter(s)

Allowed filters:

PR: CTI routing priority [0..255] <Optional>

TYPE: Type of the connection [TR, DATA, VtoC, VtoH, VtoI, VtoS,
VtoD, CtoV, CtoC, CtoH, CtoI, CtoS, CtoD, HtoV, HtoC, HtoH,
HtoI, HtoS, HtoD, ItoV, ItoC, ItoH, ItoI, ItoS, ItoD, StoV,

627
Draft CTI System Draft

StoC, StoH, StoI, StoS, StoD, DtoV, DtoC, DtoH, DtoI, DtoS,
DtoD, *toV, *toC, *toH, *toI, *toS, *toD] <Optional>
POI: Input CTI port/group [1..300, *, #, G1..G32, G*, PBX,
CtiSLink, CtiH323, CtiIax, CtiDisa, CtiSip] <Optional>
SR: Source Cluster identifier [0..9, A..Z, a..z, _, :] or "#",
or a list name between primes 'list' or a string preceded
and/or followed by '*' (E.g.:"*mystr" or "mystr*" or
"*mystr*") or "*". <Optional>
POO: Output CTI port/group [1..300, #, G1..G32, PBX, CtiSLink,
CtiH323, CtiIax, CtiDisa, CtiSip] <Optional>
DS: Destination Cluster identifier [0..9, A..Z, a..z, _, :]
or "#" or "<AUTO-I>" or "<AUTO-O>" or a string preceded
and/or followed by '*' (E.g.:"*mystr" or "mystr*" or
"*mystr*") or "*". <Optional>

CTI routing parameter(s):

DESCR: Description. From 0 up to 70 ASCII extended characters.

Case is preserved. Spaces are allowed.
Strings holding spaces must be written between quotation marks.
In standard format it is displayed only when not empty.
In reduced format it is not displayed.
ACT: Active/usable record flag [NO, YES]
In standard/reduced format it is displayed only when equal to NO.
EDT: Editable by HTTP users record flag [NO, YES]
In standard/reduced format it is displayed only when equal to YES.
TYPE: Type of the connection [TR, DATA, VtoC, VtoH, VtoI, VtoS, VtoD,
CtoV, CtoC, CtoH, CtoI, CtoS, CtoD, HtoV, HtoC, HtoH, HtoI, HtoS,
HtoD, ItoV, ItoC, ItoH, ItoI, ItoS, ItoD, StoV, StoC, StoH, StoI,
StoS, StoD, DtoV, DtoC, DtoH, DtoI, DtoS, DtoD, *toV, *toC, *toH,
*toI, *toS, *toD]
POI: Input CTI port/group [1..300, *, #, G1..G32, G*, PBX, CtiSLink,
CtiH323, CtiIax, CtiDisa, CtiSip]
<Only for TYPE:TR/DATA/VtoCHISD/HtoVCHISD/ItoVCHISD/DtoVCHISD/
StoVCHISD/*toVCHISD>
SR: Source Cluster identifier [0..9, A..Z, a..z, _, :] or "#", or "*",
or a list name 'list'. <Only for TYPE:CtoVCHISD/*toVCHISD>
POO: Output CTI port/group [1..300, #, G1..G32, PBX, CtiSLink, CtiH323,
CtiIax, CtiDisa, CtiSip]
<Only for TYPE:TR/DATA/CtoVHISD/VtoHISD/HtoVHISD/ItoVHISD/DtoVHISD/
StoVHISD/*toVHISD>
DS: Destination Cluster identifier [0..9, A..Z, a..z, _, :]
or "#" or "<AUTO-I>" or "<AUTO-O>". <Only for TYPE:VCHISDtoC/*toC>
NEXT: Alternative routing selection [N (or NO), U (or UNLIMITED),
L (or LIMITED), T (or TRANSFERT), BB (or BUTBUSY)] or the name
of ICAUSE list between primes (E.g.: BUTBUSY or 'my_causes').
LAST: Alternative routing, last failure reason for conditional match
[ANY, BUSY, NOANS, OTHER] or the name of ICAUSE list between
primes (E.g.: NOANS or 'my_causes').
EEC: Extended echo canceller activation [NO, IN, OUT, BOTH]
CDI: Input called address [0..9, *, #, ?, 'list'], optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes,
or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP SPECIAL VALUES for details on meaning of special values.
CDO: Output called address [0..9, *, #, 'macro'], optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.

628
Draft CTI System Draft

CGI: Input calling address [0..9, *, #, ?, 'list'], optionally preceded

by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] and/or
PI [a, r, m, q] and/or SI [y, v, w, z, j] attributes, or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CGO: Output calling address [0..9, *, #, 'macro'], optionally preceded
by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] and/or
PI [a, r, m, q] and/or SI [y, v, w, z] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
12''listname''34)
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
SDI: Input called sub-address [AlphaNumExt, *, ?, #, ##, $, 'list'].
(E.g.: ho11, me1*, ho??12?, ho?12?*, *, #, 'listname', AA'listname')
See HELP ISDN VALUES for details on meaning of special values.
SDO: Output called sub-address [AlphaNumExt, *, #, 'macro'].
(E.g.: home123, *, #, home123'sgi', 'sgi'home123'cdi.s5', 'sdi'
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
AAA''listname.cd'', AAA'sdi'BBB''listname'.s5')
See HELP ISDN VALUES for details on meaning of special values.
SGI: Input calling sub-address [AlphaNumExt, *, ?, #, ##, $, 'list'].
(E.g.: ho11, me1*, ho??12?, ho?12?*, *, #, 'listname', AA'listname')
See HELP ISDN VALUES for details on meaning of special values.
SGO: Output calling sub-address [AlphaNumExt, *, #, 'macro'].
(E.g.: home123, *, #, home123'sgi', 'sgi'home123'cdi.s5', 'sdi'
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
AAA''listname.cd'', AAA'sgi'BBB''listname'.s5')
See HELP ISDN VALUES for details on meaning of special values.
RGI: Input redirecting address [0..9, *, #, ?, 'list'], optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
and/or PI [a, r, m, q] and/or SI [y, v, w, z, j] attributes,
or [##, $].
(E.g.: 123, 123*, 12?, 12?*, *, #, ##, $, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
RGO: Output redirecting address [0..9, *, #, 'macro'], optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p]
and/or PI [a, r, m, q] and/or SI [y, v, w, z] attributes.
(E.g.: 123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi', ''listname'',
''listname.cd'', ''listname.cg'.s2', ''listname'.s5',
12''listname''34)
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
T301: Alerting time-out [Dft, 5..180 sec.]
UDT: Unconditional disconnect timer [NO, 1..9999 sec.]
LCS: Enable/disable Last Calling number Service [NO, YES]
<Only for POO: not equal to CtiSlink, CtiH323, and CtiDisa>
LCST: Last Calling number Service records timeout [Sys, NONE, 1..999 hour]
<Only for POO: not equal to CtiSlink, CtiH323, and CtiDisa>
IG: Input gain [Sys, MUTE, -31..+31 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
OG: Output gain [Sys, MUTE, -31..+31 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
SG: Attenuation of DTMF or Tone signals respect to their configured
values [Sys, -31..0 dB]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
DL: Output volume of lower DTMF tone [Sys, MUTE, -31..+3 dBm]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>
DH: Output volume of higher DTMF tone [Sys, MUTE, -31..+3 dBm]
<Only for TYPE:VtoCHISD/CHISDtoV/*toVCHISD>

629
Draft CTI System Draft

FMRLY: Fax/Data relay [NO, YES, Sys]

<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FAXSP: Fax maximum speed [AUTO or 0, 2400, 4800, 7200, 9600, 12000,
14400 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
MODSP: Modem maximum speed [AUTO or 0, 2400, 4800, 7200, 9600, 12000,
14400 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FMLVL: Output volume of Fax/Data signal [Sys, -18..-3 dBm]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
FMDJ: Fax/Data default jitter buffer size [Sys, 0..1000 ms]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
FMMJ: Fax/Data maximum jitter buffer size [Sys, 0..1000 ms]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
ECM: Enable/disable ECM (Error Correcting Mode) for fax [NO, YES, Sys]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
SP: Voice compression bit rate [5300, 6000, 6300, 6400, 7200, 8000,
8800, 9600, 11200, 13200, 13340, 15200, 16000, 18400, 24000,
24800, 32000, 40000, 64000 bps]
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCIHSD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
SC: Silence compression [NO, YES, Sys]
<Only for TYPE:VtoCHISD/CtoVCIHSD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
DJ: Default jitter buffer size.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
- For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [Sys,
0..1000 msec]
- For TYPE:CtoVCHISD/*toVCHISD: [*, Sys, 0..1000 ms]
It must be minor or equal to MJ:.
MJ: Maximum jitter buffer size.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHIDS/*toVCHISD>
- For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [Sys,
0..1000 msec]
- For TYPE:CtoVCHISD/*toVCHISD: [*, Sys, 0..1000 ms]
It must be major or equal to DJ:.
CODERS: Allowed coders.
<Only for TYPE:VtoCHISD/CtoVCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/
DtoVCHISD/*toVCHISD>
- For TYPE:CtoCHISD/HtoCHISD/ItoCHISD/DtoCHISD/*toCHISD: [* or Sys
or NONE or a list of one or more coder values (see below)].
- For TYPE:VtoCHISD/CHISDtoV/*toV: [Sys or NONE or a list of one or
more coder values (see below)]
The available coders are [Transp, G.711, G.726, G.727, GSM6.10,
Spirit, G.723.1, G.729A, ILBC, SPEEX, G.711A, G.711u]. Values can be
joined using "," operator. The position in the list defines the
preference order. The right-most value is the one with the lowest
preference.
SPOUT: Maximum preferred/allowed bit rate for the audio coder on output
side of direct transcoding [*, 5300, 6000, 6300, 6400, 7200, 8000,
8800, 9600, 11200, 13200, 13340, 15200, 16000, 18400, 24000,
24800, 32000, 40000, 64000 bps]
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/

630
Draft CTI System Draft

*toVCHISD>
SCOUT: Silence compression output [NO, YES, Sys, *]
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
DJOUT: Default jitter buffer size output [*, Sys, 0..1000 ms]
It must be minor or equal to MJOUT:.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
MJOUT: Maximum jitter buffer size output [*, Sys, 0..1000 ms]
It must be major or equal to DJOUT:.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
CODERSOUT: Preferred list of coders for THIS routing offered to called side
[* or Sys or NONE or *,Sys or a list of one or more coder values
(see below) or *,list]
The available coders are [Transp, G.711, G.726, G.727, GSM6.10,
Spirit, G.723.1, G.729A, ILBC, SPEEX, G.711A, G.711u]. Values can be
joined using "," operator. The position in the list defines the
preference order. The right-most value is the one with the lowest
preference.
<Only for TYPE:CtoCHISD/HtoCHISD/ItoCHISD/StoCHISD/DtoCHISD/
*toVCHISD>
TI1:..TI5: Time interval in the format "day,hh:mm-hh:mm", where 'day' can be:
- a single day of the week [MO, TU, WE, TH, FR, SA, SU] or
- a set of days of the week (E.g.: MO+TH or TU+TH+SU) or
- an interval of days of the week (E.g.: MO-WE or TH-SU) or
- "ALL".
Use "#" to disable the time interval.

The below command filters all rules whose type is CTOV:

[15:03:40] ABILIS_CPX:d ctir type:ctov

Last change: 12/12/2010 11:01:00 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
9 [cito_gsm]
CtoV Clus2 G3 * 33312345
NO ANY NO Dft * *
64000 Sys * * Sys Sys CITOBOX2422 *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
12 [test-citobox]
CtoV Clus1 31 * *
NO ANY NO Dft * *
64000 Sys * * Sys Sys CITOBOX241 *
-------------------------------------------------------------------------------

631
Draft CTI System Draft

42.6.1.2. RGI and RGO parameters

This two parameters has been introduced to insert the right value in the CG field for transferred calls and for centrals which
doesn't comply with ISDN standard.

Assuming to have a user who calls a number on which there's a call transfer and supposing that:

• the user's phone number is 07779660

• the called number is 08889661

• the call is forwarded toward number 01111

the calling number received from 01111 is the user's phone number 08889661. The number 07779660 is stored in a field
called RG, according to ISDN standard.

When the transferred call reaches centrals not complying to ISDN standard, a trick can be used: Abilis can store the number
of the initial caller (07779660) in the CG field, while the number which trasfers calls is stored in the RG field.

A call originated by a call transfer may be identified because RG field is not empty, while a normal call has RG field empty.
This is used to create special routings which are effective only for call transfers.

Use the following values to intercept normal calls:

RGI:## Missing information element

RGI:# Missing or Empty information element

Set the RGI parameter to a specific value to intercept only calls originated by call transfers.

Setting RGI:*, the rule intercepts every kind of call (tranferred or not). The following table shows the range of RGI values:

[14:43:43] ABILIS_CPX:help isdn values

Meaning of special values used in ISDN CDI/CGI/SGI/SDI/RGI fields:

632
Draft CTI System Draft

-----------+-------------------------------------------------------------------
Symbol | Meaning
-----------+-------------------------------------------------------------------
* | Don't care.
# | Missing or Empty information element
## | Missing information element
$ | Empty or Non-empty information element
?* | Non-empty information element
-----------+-------------------------------------------------------------------

The following are the log and cti connection shown during a normal call from 901 to 902. Please note that there RGO field is
empty.

[09:58:51] ABILIS_CPX:_start ldme

Current Local Time: Thursday 16/12/2010 09:58:57 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
161210 095903 CtiSip 12 E-CallRx CH:18 BC:Speech CD:ue902
CG:uxq901 USER:test
161210 095903 CtiSip 12 E-Route Match PR:6
161210 095903 CtiSip 12 E-CallTx BC:Speech TY:StoS CD:ue902
CG:uxq901
161210 095903 CtiSip 12 E-NumComplete CDI:ue902 CDO:ue902
161210 095903 CtiSip 12 E-AlertRx CH:19 USER:test2
161210 095903 CtiSip 12 E-AlertTx CH:18

PREVIOUS COMMAND(s) ABORTED

[09:59:08] ABILIS_CPX:_d ctice

-------------------------------------------------------------------------------
ID:12 TYPE:StoS ST:ALERT PR:6 STI:07/00 STO:04/00 EEC:NO
START:16/12/2010 09:59:03 DURATION:0 REMAINING:-
POI:Sip GI:# SR:# POO:Sip GO:# DS:#
CDI:ue902 CDO:ue902
CGI:uxq901 CGO:uxq901
SDI: SDO:
SGI: SGO:
RGI: RGO:
CODER:Unk SP:0 FMRLY:NO FAXSP:0 DJ:0 FMDJ:0
BW:0 SC:NO MODSP:0 MJ:0 FMMJ:0

The following are logs and cti connection shown during a trasferred call. User test (phone number 901) calls user:test2
(phone number 902). User test2 trasfers calls to a cellphone (phone number 333xxxxxx). Please note that RGO field is not
empty, because there's a transferred call.

[12:28:00] ABILIS_CPX:_start ldme

Current Local Time: Thursday 16/12/2010 12:28:22 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
161210 122825 CtiSip 24 E-CallRx CH:34 BC:Speech CD:ue902
CG:uxq901 USER:test
161210 122825 CtiSip 24 E-Route Match PR:6
161210 122825 CtiSip 24 E-CallTx BC:Speech TY:StoS CD:ue902

633
Draft CTI System Draft

CG:uxq901
161210 122825 CtiSip 0 E-CallForward RULE:ALWAYS USER:test2
161210 122825 CtiSip 24 E-NumComplete CDI:ue902 CDO:ue902
161210 122825 CtiSip 25 E-CallRx CH:36 BC:Speech CD:ux8333xxxxxx
CG:uxq901 RG:uxq902 USER:test2
161210 122825 CtiSip 25 E-Route Match PR:5
161210 122825 CtiSip 25 E-CallTx BC:Speech TY:StoS
CD:ux333xxxxxx CG:uxq901
RG:uxq902 SCD:08xxxxxx
161210 122825 CtiSip 25 E-NumComplete CDI:ux83299783725
CDO:ux3299783725
161210 122825 CtiSip 26 E-CallTransfer SES/ID-IN:25 SES/ID-OUT:24
161210 122831 CtiSip 26 E-ProgressRx PI:81 88 USER:08351825479
161210 122831 CtiSip 26 E-ProgressTx PI:81 88

PREVIOUS COMMAND(s) ABORTED

[12:28:35] ABILIS_CPX:_d ctice

-------------------------------------------------------------------------------
ID:26 TYPE:StoS ST:CREQ PR:TRS[6/5] STI:09/00 STO:03/00 EEC:NO
START:16/12/2010 12:28:25 DURATION:0 REMAINING:-
POI:Sip GI:# SR:# POO:Sip GO:# DS:#
CDI:ue902 CDO:ux333xxxxxx
CGI:uxq901 CGO:uxq901
SDI: SDO:08xxxxxx
SGI: SGO:
RGI: RGO:uxq902
CODER:G.711A SP:64000 FMRLY:NO FAXSP:0 DJ:100 FMDJ:200
BW:66400 SC:YES MODSP:0 MJ:250 FMMJ:400

The cti routing pr:5 is used to call the cellphone. This rule intercept normal calls and trasferred calls, because RGI:*.

[12:37:26] ABILIS_CPX:_d ctire pr:5

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 16/12/2010 12:36:27 CET

-------------------------------------------------------------------------------
PR:5 DESCR:
ACT:YES EDT:NO
TYPE:StoS POI:CtiSip POO:CtiSip EEC:NO
NEXT:NO CDI:8* CDO:'CDI.S2'
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:08xxxxxx
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:G.711
SPOUT:64000 SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:G.711
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

Example: administrator can configure Abilis so that users cannot trasfer calls to cellphones. Rule pr:5 must be modified
setting RGI:## and rule pr:6 must be created.

[12:40:26] ABILIS_CPX:_s ctir pr:5 rgi:##

COMMAND EXECUTED

634
Draft CTI System Draft

[12:40:34] ABILIS_CPX:_d ctire pr:5

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 16/12/2010 12:36:27 CET

-------------------------------------------------------------------------------
PR:5 DESCR:
ACT:YES EDT:NO
TYPE:StoS POI:CtiSip POO:CtiSip EEC:NO
NEXT:NO CDI:8* CDO:'CDI.S2'
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:08xxxxxx
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:## RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:G.711
SPOUT:64000 SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:G.711
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

[12:44:49] ABILIS_CPX:_a ctir pr:6 type:stov poo:none cdi:8* cdo:'cdi.s2' rgi:?* sp:64000 coders:g.

COMMAND EXECUTED

[12:44:57] ABILIS_CPX:_d ctire pr:6

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 16/12/2010 12:44:57 CET

-------------------------------------------------------------------------------
PR:6 DESCR:
ACT:YES EDT:NO
TYPE:StoV POI:CtiSip POO:NONE EEC:NO
NEXT:NO CDI:8* CDO:'CDI.S2'
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:?* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:G.711
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

The following is the log of a transferred call to a cellphone: the call fails.

[12:46:17] ABILIS_CPX:_start ldme

Current Local Time: Thursday 16/12/2010 12:46:26 (UTC+1.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
161210 124629 CtiSip 29 E-CallRx CH:41 BC:Speech CD:ue902
CG:uxq901 USER:test
161210 124629 CtiSip 29 E-Route Match PR:7
161210 124629 CtiSip 29 E-CallTx BC:Speech TY:StoS CD:ue902
CG:uxq901
161210 124629 CtiSip 0 E-CallForward RULE:ALWAYS USER:test2
161210 124629 CtiSip 29 E-NumComplete CDI:ue902 CDO:ue902
161210 124629 CtiSip 30 E-CallRx CH:43 BC:Speech CD:ux8333xxxxxx

635
Draft CTI System Draft

CG:uxq901 RG:uxq902 USER:test2

161210 124629 CtiSip 30 E-Route Match PR:6
161210 124629 CtiSip 30 E-InternalFail PR:6 CAUSE:FF A8 (CPX, No port
available (NO_PORT))
161210 124629 CtiSip 30 E-Route Fail PR:6 CAUSE:81 83 (LPN, No
route to destination)
161210 124629 CtiSip 30 E-CallFailTx CH:43 CAUSE:81 83 (LPN, No route
to destination)
161210 124629 CtiSip 29 E-DiscTx CH:41 CAUSE:81 90 (LPN, Normal
call clearing) USER:test

42.6.2. Add CTI Routing Table (A CTIR)

It adds a new CTI routing with PR:xx priority setting the indicated parameters to the specified values. Unspecified parameters
are set to default values. The CTI routings table can store up to 256 routing definitions, so the priority value must be in the
interval [0 - 255].

If a routing with “PR:xx” is already present in the table, it will get “PR:xx+1” priority.

Example: how to configure a Transparent (TR) routing which routes every call (CDI:*) coming from the CTI Ports Group G1
(connected to the PABX) to CTI Ports Group G2 (connected to the ISDN lines), without any alternative routings.

[15:30:01] ABILIS_CPX:a ctir pr:3 type:tr poi:g1 poo:g2 cdi:*

COMMAND EXECUTED

[15:30:50] ABILIS_CPX:d ctire pr:3

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 24/11/2010 15:30:50 CET

-------------------------------------------------------------------------------
PR:3 DESCR:
ACT:YES EDT:NO
TYPE:TR POI:G1 POO:G2 EEC:NO
NEXT:NO CDI:* CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

Warning
Changes made on the CTI routings table are not immediately active. To activate them, execute the
initialization command init ctir

42.6.3. Clear CTI Routing Table (C CTIR)

It deletes a CTI routing from the routing table. Priority of remaining routings (if higher than the removed one) are decreased
because of table continuity. The syntax of the command is c ctir pr:xx.

[12:28:06] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT

636
Draft CTI System Draft

|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
3 TR G1 G2 * *
-------------------------------------------------------------------------------

[12:31:19] ABILIS_CPX:c ctir pr:3

COMMAND EXECUTED

[12:31:51] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------

Warning
Changes made on the CTI routings table are not immediately active. To activate them, execute the
initialization command init ctir

42.6.4. Set CTI Routing Table (S CTIR)

Sets the parameters of CTI routing identified by “PR:xx” to their new values. The syntax of the command is:

s ctir pr:xxx type:<type> [par:value]

Note
Parameters may change according to the TYPE of the routing selected!

[12:37:09] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO

637
Draft CTI System Draft

|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO

| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
3 TR G1 G2 * *
-------------------------------------------------------------------------------

[12:37:32] ABILIS_CPX:s ctir pr:3 poo:g3 cdi:528

COMMAND EXECUTED

[12:37:36] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
3 TR G1 G3 528 *
-------------------------------------------------------------------------------

Warning
Changes made on the CTI routings table are not immediately active. To activate them, execute the
initialization command init ctir

The routing which has been modified routes the calls coming from G1 to the group G3 if the called number is 528.

Other interesting parameters available on CTI Routing tables are T301, TIx, NEXT, and DS:<AUTO-I>/<AUTO-O>.

Example: enable a CTI routing just on Tuesday and Wednesday from 18:00 to 20:30.

[12:37:40] ABILIS_CPX:s ctir pr:3 ti1:tu-we,18:00-20:30

COMMAND EXECUTED

[15:35:00] ABILIS_CPX:d ctire pr:3

638
Draft CTI System Draft

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 24/11/2010 15:35:00 CET

-------------------------------------------------------------------------------
PR:3 DESCR:
ACT:YES EDT:NO
TYPE:TR POI:G1 POO:G3 EEC:NO
NEXT:NO CDI:528 CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
TI1:TU-WE,18:00-20:30 TI2:# TI3:# TI4:# TI5:#

Example: how to combine the use of T301 and NEXT. Calls must be forwarded to the next routing if there is no answer after
15 seconds .

[13:50:10] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |TYPE |POI/SR [SR] |POO/DS |CDI |CDO
|NEXT |LAST |TON |T301|UDT |CGI |CGO
|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT| |SGI |SGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 VtoC G1 Abilis2 'ToAbilis2' *
UNLIMITED ANY Sys Dft NO * *
-------------------------------------------------------------------------------
3 TR G1 G2 * *
-------------------------------------------------------------------------------
4 TR G2 G1 * *
-------------------------------------------------------------------------------

[13:50:12] ABILIS_CPX:s ctir pr:4 t301:15 next:t

COMMAND EXECUTED

[13:50:43] ABILIS_CPX:a ctir pr:5 type:vtoc poi:g2 ds:abilis2 cdi:*

COMMAND EXECUTED

[13:50:54] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS

639
Draft CTI System Draft

|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 TR G1 G2 00 *
-------------------------------------------------------------------------------
4 TR G2 G1 00 *
TRANSFERT ANY NO 15 * *
-------------------------------------------------------------------------------
5 VtoC G2 Abilis2 * *
-------------------------------------------------------------------------------

Warning
Changes made on the CTI routings table are not immediately active. To activate them, execute the
initialization command init ctir

When routing PR:4 is matched, the call will alert for 15 seconds on G1 ports group and if no answer occurs, it will be
transferred to the next routing and compressed to “Abilis2”.

42.6.5. Move CTI Routing Table (M CTIR)

Moves the CTI routing priority from the value “PR:xx” to the new value “PR:yy”. Other definitions present in the table are
re-sorted because of table continuity.

[14:02:43] ABILIS_CPX:d ctir

[13:50:54] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 TR G1 G2 00 *
-------------------------------------------------------------------------------
4 TR G2 G1 00 *
TRANSFERT ANY NO 15 * *
-------------------------------------------------------------------------------
5 VtoC G2 Abilis2 * *
-------------------------------------------------------------------------------

[15:38:34] ABILIS_CPX:m ctir pr:3 pr:5

COMMAND EXECUTED

[15:38:40] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 24/11/2010 15:38:40 CET

640
Draft CTI System Draft

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
3 TR G2 G1 00 *
TRANSFERT ANY NO 15 * *
-------------------------------------------------------------------------------
4 VtoC G2 Abilis2 * *
-------------------------------------------------------------------------------
5 TR G1 G2 00 *
-------------------------------------------------------------------------------

Warning
Changes made on the CTI routings table are not immediately active. To activate them, execute the
initialization command init ctir

42.6.6. Macro functions

A macro-instruction can only contain:

• decimal digits '0' - '9';

• names of input caller's address and sub-address fields: 'CGI' and 'SGI';

• names of input called's address fields and sub-address fields: 'CDI' and 'SDI';

• the '.' (dot) character, which is used as a separator;

• the sequences ".3xx", ".Lxx" and ".Rxx".

Table 42.3. Table Lxx, Rxx, 3xx macros

Sequence Operative meaning
yy.Sxx It takes the characters of field "yyy" starting from position
"xx".
yyy.Lxx It takes up to "xx" characters of field "yyy", starting from the
leftmost.
yyy.Rxx It takes up to "xx" characters of field "yyy", staring from the
rightmost.

Examples:

• CDO:'SGI': the called address field of the outgoing call will contain the same value as is contained in the field for the
called sub-address of the incoming call.

• CDO:1023'SGI': the called address field of the outgoing call will contain the numerical sequence "1023" followed by the
content of the called sub-address of the incoming call.

• CDO:1023'SGI.S02': the called address field of the outgoing call will contain the numerical sequence "1023" followed by
the content of the called sub-address of the incoming call, starting from the 2nd character (.S02).

• CDO:1023'SGI.R02': the called address field of the outgoing call will contain the numerical sequence "1023" followed by
at most two characters taken from the content of the called sub-address of the incoming call, starting from the right most
(.R02).

641
Draft CTI System Draft

42.7. CTI routing for POTS devices (“PBX Group”)

CTI POTS ports (CTI Ports from 101 to 196) allow the connection between Abilis and analogue phone devices. Each one is
identified with a two digits number (NUM parameter); the NUM value can be set by the user and must be unique (default values
start from 01,02…).

[15:40:09] ABILIS_CPX:d p ctip:101

CTIP:101 DESCR:
Act card:POTS-1<1>
Run OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:01

[15:40:25] ABILIS_CPX:d p ctipe:101

CTIP:101 DESCR:
Act card:POTS-1<1>
Run OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:01
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:YES

Routings can be added using the POTS ports number (101-196) in POI or POO parameters.

The special value PBX can be used: CTI Router verifies the last two digits of the Called Input number and compares them
with the field NUM of the CTI POTS ports. The call is routed to the correspondent port that matches.

Example: route the calls arriving from cluster Abilis2 to the analogue devices connected to the POTS, by verifying the last
two digits of the called number (i.e. 02345678xx).

[15:40:31] ABILIS_CPX:a ctir pr:2 type:ctov sr:Abilis2 poo:pbx cdi:02345678??

COMMAND EXECUTED

[15:41:32] ABILIS_CPX:d ctir pr:2

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 24/11/2010 15:41:32 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
2 CtoV Abilis2 PBX 02345678?? *
-------------------------------------------------------------------------------

With this rule the calls to 0234567821 is routed to the ports with NUM:21.

642
Draft CTI System Draft

By configuring the routing specifying the number of the CTI POTS ports, each call will be routed on the corresponding port
without verifying the called number.

[14:45:35] ABILIS_CPX:a ctir pr:2 type:ctov sr:Abilis2 poo:101 cdi:*

COMMAND EXECUTED

[14:51:16] ABILIS_CPX:d ctir pr:2

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
2 CtoV Abilis2 101 * *
-------------------------------------------------------------------------------

The routing above routes every call which comes from the cluster Abilis2 to CTIP:101.

42.8. CTI System Resource

The majority of the parameters which are present in CTI Routing can be defined as default value (Sys): the default value
will be the one setup by the CTISYS resource.

Use the following command to display the parameters of the resource; the d p ctisys ? command shows the meaning of
parameters.

[14:59:02] ABILIS_CPX:d p ctisys

RES:CtiSys --------------------------------------------------------------------
Run DESCR:CTI_System_general_properties
- Router ---------------------------------------------------------------
ROUTING:PREFIX max-ctoc:50 au-law:A-LAW NP-CT:YES
OUT-DIAL-TONE:NO OUT-DIAL-DIGIT:0
MAIL-FROM:Abilis-Test208<[email protected]>
CALLS-LOG-DIR:C:\APP\USERS\
NAT-PREFIX:0 INT-PREFIX:00 COUNTRY-CODE:39
TON-TO-PREFIX:NO
- Last Calling number Service ------------------------------------------
LCST:6 lcs-dir:C:\APP\CTI\LCS\
- Call&Ring ------------------------------------------------------------
CALLTRY-TOUT:30 CALLTRY-NRTY:15
- Address Book ---------------------------------------------------------
addrbook-dir:C:\APP\CTI\ADDRBOOK\
ADDRBOOK-PUB-PROTECTED:NO
- EEC ------------------------------------------------------------------
TAIL:128 NLP:YES CNM:NORMAL AEC:NO
TAIL-BASE:0 NLP-A:1 VQE-TONE-DISABLER:YES AEC-TAIL:1024
HLC:NO NLP-B:0 VQE-ACT-DELAY:300 AEC-ERL-DFT:0
HLC-THR:-10 ERL-DFT:-6
- Dsp firmwares and configurations for C6412 on QPRIX and PB44X --------
CARD-TYPE: (AC482 EEC) | fw: hdlc-b: g.729a: ec: ac:
------------------------+------------------------------------
1 no no | D64V 8 YES 32 (10)

643
Draft CTI System Draft

2 no yes | D64V 8 YES 0 (18)

3 yes no | D64A 32
4 yes yes | D64A 32
------------------------+------------------------------------
- Dsp firmwares for AC48x ----------------------------------------------
dsp1-fw:D1C5F3 dsp2-fw:D2C4F3 dsp8-fw:D8C2F1
dsp1-coderset:EXTENDED dsp2e-fw:D2C4F3
- Audio compressors defaults -------------------------------------------
IN-GAIN:0 OUT-GAIN:0 SIG-GAIN:0 DFT-JBUF:0
DTMF-HIGH:-4 DTMF-LOW:-6 DTMF:OUTBAND MAX-JBUF:250
FM-RELAY:YES FM-LEVEL:-9 FM-DFT-JBUF:200 FM-MAX-JBUF:400
SC:NO SID-GEN:NO SID-USE:NO ECM:YES
AT:YES AT-CODE:C AT-DURATION:100
CODERS:G.711,G.726,G.727,ILBC,GSM6.10,Spirit,G.723.1,G.729A,SPEEX,Transp
- POTS defaults --------------------------------------------------------
CLIP:EXT CLIP-STD:ETSI CLIP-TAS:RP MIN-FLASH:50
SENSING:YES ABF:NO HPF:YES DEBOUNCE:16 MAX-FLASH:200
COUNTRY:IT (SL-IT.BIN) POTS-NUM-LENGTH:3
POTS-IN-GAIN-ADJ:COUNTRY POTS-OUT-GAIN-ADJ:COUNTRY BC:Speech
POTS-AT:NO POTS-AT-CODE:C POTS-AT-DURATION:100 POTS-AT-GAIN:0
POTS-DT:NO POTS-DT-CODE:D POTS-DT-DURATION:100
- CELL (GSM/UMTS) defaults ---------------------------------------------
CELL-GAIN-IN:0 CELL-GAIN-OUT:0 pdn-rxbuf:30
CELL-CODEC-GAIN-IN:0 CELL-CODEC-GAIN-OUT:0
- CITOBOX defaults -----------------------------------------------------
CITO-GAIN-IN:0 CITO-GAIN-OUT:0
CITO-ES:YES
CITO-ES-RISE-OUT:0 CITO-ES-FALL-OUT:0 CITO-ES-THR-OUT:0
- HDLC -----------------------------------------------------------------
dmaframe:2100 bdframe:2100 bcframe:64 bvframe:264
rxdmabuf:3 bdrxbuf:14 bcrxbuf:3 bvrxbuf:3
txdmabuf:2 bdtxbuf:1 bctxbuf:1 bvtxbuf:3
- Tones and ringing patterns -------------------------------------------
- Tones -------------------+------+------+------+------+------+------+
TONESET:ABILIS | T1 | S1 | T2 | S2 | T3 | S3 |
----------+------+------+------+------+------+------|
DIAL-xx: |(7000)|( 0)|( 0)|( 0)|( 0)|( 0)|
OUT-DIAL-xx: |( 200)|( 200)|( 600)|(1000)|( 0)|( 0)|
ALERT-xx: |(1000)|(4000)|( 0)|( 0)|( 0)|( 0)|
BUSY-xx: |( 500)|( 500)|( 0)|( 0)|( 0)|( 0)|
DISC-xx: |( 200)|( 200)|( 0)|( 0)|( 0)|( 0)|
HOLD-xx: | 110 | 110 | 110 | 1500 | 0 | 0 |
MENU-xx: | 110 | 2000 | 0 | 0 | 0 | 0 |
- POTS Ringing ------------+------+------+------+------+------+------+
EXT-xx: | 1000 | 4000 | 0 | 0 | 0 | 0 |
INT-xx: | 400 | 200 | 400 | 3000 | 0 | 0 |
PKC-xx: | 500 | 500 | 500 | 500 | 1500 | 2000 |
+------+------+------+-------------+------+
- Clock Sources for H100 cards -----------------------------------------
CLK:LIST
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| P1:..P10:| 34 | . | . | . | . | . | . | . | . | . |
|P11:..P20:| . | . | . | . | . | . | . | . | . | . |
|P21:..P30:| . | . | . | . | . | . | . | . | . | . |
|P31:..P40:| . | . | . | . | . | . | . | . | . | . |
|P41:..P50:| . | . | . | . | . | . | . | . | . | . |
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
- Clock Sources for NOT-H100 cards -------------------------------------
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+
| CARD: | CLK: | P1: | P2: | P3: | P4: | P5: | P6: | P7: | P8: |
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+
*** No NOT-H100 cards present or active ***

644
Draft CTI System Draft

These are the most frequently used parameters.

In the Router section, the parameter ROUTING (Routing Management) allows to set two kinds of CTI Routing functioning:

• ROUTING:EN-BLOC. The CTI Router waits to receive the complete number (from the line, the PABX or other connected
devices) before choosing the routing. The routing table management is easier, but the disadvantage is that, at the end of
dialing, the user must press the “#” on the phone or wait a time out of (generally) 5 seconds (see parameter DIALT on CTI
Ports) before the call starts.

• ROUTING:PREFIX. The CTI Router verifies the rule to match at the receipt of a single digit. The configuration of the CTI
Routing table is a bit more difficult and delicate, but the advantage is that the user is not required to press “#” on the phone
or wait any time at the end of dialing.

• MAIL-FROM: the default sender of emails.

User demand must be considered when choosing the system.

Besides, the out dial tone is now played when a user picks up a POTS phone and dials the OUT-DIAL-DIGIT value (the
OUT-DIAL-xx tone is played):

There are various parameters used to configure the out dial tone generation:

• OUT-DIAL-TONE: enable/disable the outside dial tone generation [NO, YES].

• OUT-DIAL-DIGIT: digit for outside selection ['0'..'9']

The section Last Calling number Service allows to choose two system parameters:

• LCST: Last Calling number Service records timeout [NONE, 1..999 hour]

• lcs-dir: Last Calling number Service Working directory path

The Last Calling number Service is useful if GSM/UMTS Box is installed, but it can be used with ISDN ports, CLUSTERS,
as well as with SIP and IAX users.

The section Call&Ring allows to configure two parameters about call&ring feature:

• CALLTRY-TOUT: number of seconds between retries [30..600 sec].

• CALLTRY-NRTY: Number of retries [1..30].

The most important parameters of EEC section are:

AEC Acoustic Echo Canceller. When set to YES is enables for ALL the EEC channels the capability to cancel
acoustic echo too. In normal telecom applications the AEC is not needed.

TAIL-BASE The EEC can cancel echo in the range 0..128 msec. By specifying here a value greater than 0 the range is
value+128ms. For example if TAIL-BASE is 256, the EEC is able to cancel echo between 256 and 384 msec.

Tip
Use the following command to display the availability of Extended Echo Canceler (EEC):

[14:25:58] ABILIS_CPX:d d ctieec

-------------------------------------------------------------------------------
EEC Card Chan State CurDelay MaxDelay Tail TailBase CurERL MaxERL
-------------------------------------------------------------------------------
0 QPRI-1 0 FREE
1 QPRI-1 1 FREE
2 QPRI-1 2 FREE
3 QPRI-1 3 FREE
4 QPRI-1 4 FREE
5 QPRI-1 5 FREE
6 QPRI-1 6 FREE
7 QPRI-1 7 FREE
8 QPRI-1 8 FREE
9 QPRI-1 9 FREE
10 QPRI-1 10 FREE
11 QPRI-1 11 FREE

645
Draft CTI System Draft

12 QPRI-1 12 FREE
13 QPRI-1 13 FREE
14 QPRI-1 14 FREE
15 QPRI-1 15 FREE
16 QPRI-1 16 FREE
17 QPRI-1 17 FREE
18 QPRI-1 18 FREE
19 QPRI-1 19 FREE
20 QPRI-1 20 FREE
21 QPRI-1 21 FREE
22 QPRI-1 22 FREE
23 QPRI-1 23 FREE
24 QPRI-1 24 FREE
25 QPRI-1 25 FREE
26 QPRI-1 26 FREE
27 QPRI-1 27 FREE
28 QPRI-1 28 FREE
29 QPRI-1 29 FREE
30 QPRI-1 30 FREE
31 QPRI-1 31 FREE
32 QPRI-1 32 FREE
33 QPRI-1 33 FREE
34 QPRI-1 34 FREE
35 QPRI-1 35 FREE
36 QPRI-1 36 FREE
37 QPRI-1 37 FREE
38 QPRI-1 38 FREE
39 QPRI-1 39 FREE
40 QPRI-1 40 FREE
41 QPRI-1 41 FREE
42 QPRI-1 42 FREE
43 QPRI-1 43 FREE
44 QPRI-1 44 FREE
45 QPRI-1 45 FREE
46 QPRI-1 46 FREE
47 QPRI-1 47 FREE
48 QPRI-1 48 FREE
49 QPRI-1 49 FREE
50 QPRI-1 50 FREE
51 QPRI-1 51 FREE
52 QPRI-1 52 FREE
53 QPRI-1 53 FREE
54 QPRI-1 54 FREE
55 QPRI-1 55 FREE
56 QPRI-1 56 FREE
57 QPRI-1 57 FREE
58 QPRI-1 58 FREE
59 QPRI-1 59 FREE
60 QPRI-1 60 FREE
61 QPRI-1 61 FREE
62 QPRI-1 62 FREE
63 QPRI-1 63 FREE

The output of the above command is the following if Abilis is equipped with mixed ECC cards and non-
ECC cards:

[14:33:25] ABILIS_CPX:d d ctieec

-------------------------------------------------------------------------------
EEC Card Chan State CurDelay MaxDelay Tail TailBase CurERL MaxERL
-------------------------------------------------------------------------------
*** No EECs ***

646
Draft CTI System Draft

The section named Dsp firmwares and configurations for C6412 on QPRIX and PB44X allows to choose some
parameters of the embedded vocoders.

TRANSPARENT, G711 and G729a vocoders are available as embedded vocoders through QPRIX and PB44X. The
advantage is there's no need of additional DSP. The most important characteristics and limitations are:

• echo canceller (EC) is available up to 32 ms but it can raise up to 128 ms in the version with the additional Octasic chip
(EEC)

• fax relay is not currently supported

• Mixing cards with and without additional DSPsis not allowed, as well as mixing embedded vocoders and additional DSPs
on the same card.

The choice of vocoders and echo canceller tail defines the number of available channels (ac). This number is automatically
computed by Abilis once the type of vocoder and the echo canceller tail are set.

On the left side of the section there is the card type, this is required because the QPRIX and PB44X can be manufactured in 4
main types. On the right side there are 3 parameters to configure:

• HDLC channels (named hdlc-b)

• g.729a support (named g.729a)

• echo canceller tail (named ec)

The ac value is automatically computed and shows the number of available voice channels (in the above example there are 18
channels for card type 2). Use the command s p ctisys card-type:2 g.729a:no to disable g729a support for card type 2. The
number of available channels (ac) is automatically updated to 64.

[17:12:34] ABILIS_CPX:_d p ctisys dsp

RES:CtiSys - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
Run DESCR:CTI_System_general_properties
- Dsp firmwares and configurations for C6412 on QPRIX and PB44X --------
CARD-TYPE: (AC482 EEC) | fw: hdlc-b: g.729a: ec: ac:
------------------------+------------------------------------
1 no no | D64V 8 YES 32 (10)
2 no yes | D64V 8 NO 0 (64)
3 yes no | D64A (32)
4 yes yes | D64A (32)
------------------------+------------------------------------
- Dsp firmwares for AC48x ----------------------------------------------
dsp1-fw:D1C4F3 dsp2-fw:D2C4F3 dsp8-fw:D8C2F2
dsp1-coderset:NORMAL dsp2e-fw:D2C4F6

Into Audio compressors defaults section there are the default values used in the system profile (Sys).

When a compressed call between two Abilis is setup, the coder use must be “negotiated”: the available coders set is defined
in CODERS field. The order of the list items defines also the order of scan precessing.

CODERS:G.711,G.726,G.727,GSM6.10,Spirit,G.723.1,G.729A,Transp

In this section there are other interesting and very important parameters:

• SC (Silence compression): enables or disables the compression of the “silence” during compressed calls for bandwidth use
reduction.

• FM-RELAY (Fax Data relay): enables or disables the Fax Relay management.

• MAX-JBUF (Max. jitter buffer size): sets the maximum compensating time of voice frames arrival variation (very
important on WAN realized on Internet connections).

Tip
As is well known, Internet lines are affected from latency and time arrival variation of frames caused by
network congestion, timing drift, or route changes (this is the definition of jitter). When Internet lines are

647
Draft CTI System Draft

used for the VoIp application, it's fundamental to set the properly CTISYS parameter to obtain good results
and good quality communication.

The jitter buffer is managed by DFT-JBUF and MAX-J BUF parameters. Too low values can cause
chopped voice (sensation of metallic sound) during emptying of jitter-buffer. Too high values can modify
the voice tone and introduce a perceptible delay of voice (also echo can be noticed). For a good optimization
evaluating the line in use is needed.

Generally, on lines with a low time arrival variation of the frames, good values can be: DFT-JBUF:80 and
MAX-JBUF:250.

In the POTS defaults section there are general parameters of CTI POTS Ports. The most important are:

• CLIP (Caller Identification Presentation): enables or disables the CLI on POTS ports (caller number visualization)
[NO:clip disabled, YES: clip enabled, EXT: the display of the phone will show the address book name, if supported from
the phone];

• SENSING: measures electrical parameters currently present at the analogue interface.

Through CELL section, the administrator can configure some system parameter for UMTS BOX devices:

• CELL-GAIN-IN: Input gain adjustment [MUTE, -84..+6 dB]

• CELL-GAIN-OUT: Output gain adjustment [MUTE, -84..+6 dB]

• CELL-CODEC-GAIN-IN: Audio-codec input gain adjustment [MUTE, -126..+32 dB]

• CELL-CODEC-GAIN-OUT: Audio-codec output gain adjustment [MUTE, -59..+5 dB]

• pdn-rxbuf: Size, in kbytes, of the PDN receive buffer [10..255]

The CITOBOX section allows to configure system parameters for CITOBOX devices:

• CITO-GAIN-IN: Input gain adjustment [MUTE, -126..+32 dB]

• CITO-GAIN-OUT: Output gain adjustment [MUTE, -59..+5 dB]

• CITO-ES: Echo suppressor activation [NO, YES]

• CITO-ES-RISE-OUT: Echo suppressor output line rise time [0..1000 ms]

• CITO-ES-FALL-OUT: Echo suppressor output line fall time [0..1000 ms]

• CITO-ES-THR-OUT: Echo suppressor output line threshold [-126..0 dB]

In the Tones and ringing patterns section, the TONESET parameter allows to choose the dial tone and other tones (i.e.
alerting tone, busy tone…). By default, it is set to ABILIS and it means that the dial tone is a continuous one, but others are
available: ITALY (simulates the Italian Telecom dial tone) or USERDEF (allows the user to customize the tones). The tones
change by configuring the sequence and the duration of TONEs and SILENCEs (T1, S1, T2...).

- Tones and ringing patterns -------------------------------------------

- Tones -------------------+------+------+------+------+------+------+
TONESET:ABILIS | T1 | S1 | T2 | S2 | T3 | S3 |
----------+------+------+------+------+------+------|
DIAL-xx: |(7000)|( 0)|( 0)|( 0)|( 0)|( 0)|
OUT-DIAL-xx: |( 200)|( 200)|( 600)|(1000)|( 0)|( 0)|
ALERT-xx: |(1000)|(4000)|( 0)|( 0)|( 0)|( 0)|
BUSY-xx: |( 500)|( 500)|( 0)|( 0)|( 0)|( 0)|
DISC-xx: |( 200)|( 200)|( 0)|( 0)|( 0)|( 0)|
HOLD-xx: | 110 | 110 | 110 | 1500 | 0 | 0 |
MENU-xx: | 110 | 2000 | 110 | 2000 | 0 | 0 |
- POTS Ringing ------------+------+------+------+------+------+------+
EXT-xx: | 1000 | 4000 | 0 | 0 | 0 | 0 |
INT-xx: | 400 | 200 | 400 | 3000 | 0 | 0 |
PKC-xx: | 500 | 500 | 500 | 500 | 1500 | 2000 |
+------+------+------+-------------+------+

Into Clock sources section it is possible to select where the port(s) take the ISDN clock signal. These are the available
values:

• INT: clock signal is generated by Abilis;

648
Draft CTI System Draft

• ANYTE: clock signal is taken from one of the TE ISDN ports that are present in the configuration; scanning from left to
right;

• LIST: clock signal is taken from one of the ports manually inserted into P1...P50 fields; scanning from left to right.

Ctisys parameters are distributed to all the routings, but on each routing they can be manually changed.

[15:28:36] ABILIS_CPX:d ctire pr:4

-------------------------------------------------------------------------------
PR:4 DESCR:
ACT:YES EDT:NO
TYPE:VtoC POI:G2 DS:Abilis2 EEC:NO
NEXT:UNLIMITED CDI:* CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:6400 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:Sys
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

The CITIBOX section allows to configure the CITOBOX default audio settings:

• CITO-GAIN-IN: Input gain adjustment [MUTE, -126..+32 dB];

• CITO-GAIN-OUT: Output gain adjustment [MUTE, -59..+5 dB];

• CITO-ES: Echo suppressor activation [NO, YES];

• CITO-ES-RISE-OUT: Echo suppressor output line rise time [0..1000 ms];

• CITO-ES-FALL-OUT: Echo suppressor output line fall time [0..1000 ms];

• CITO-ES-THR-OUT: Echo suppressor output line threshold [-126..0 dB].

42.9. Diagnostics and statistics

This section is an overview of the most frequently commands used to display the diagnostics and statistics of the CTI
resources.

42.9.1. CTI Ports diagnostics

To show the diagnostics of the CTI Ports (ISDN Basic or Primary Rate) the following commands are used:

d d ctip / d de ctip Shows the diagnostics of all the CTI ports.

d d ctip:<CTIP_number> / d de Shows the diagnostics of a single CTI port.

ctip:<CTIP_number>

Example: ISDN BRI port diagnostics.

[15:45:27] ABILIS_CPX:d d ctip:38

CTIP:38 ----------------------------------------------------------------------
Port_to_Telecom
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SCG:] CD: [SCD:]
------------------------------------------------------------------------
*** All channels disconnected ***
- Sapi ------- TEI -- STATE --------------------------------------------
16 (X.25 ) 10 00-INACTIVE
0 (Q.931) 102 07-CONNECTED
------------------------------------------------------------------------
ISDN-STATE:F7-READY LINE-DOWN:1 SLIPS:N/A

649
Draft CTI System Draft

Data shows that the physical layer is UP (ISDN-STATE:F7-READY) and the TEI has been correctly negotiated (TEI-102
, STATE:07-CONNECTED). The message “*** All channels disconnected ***” indicates that no calls are connected.

Example: ISDN PRI port diagnostic.

[16:46:29] ABILIS_CPX:d d ctip:1

CTIP:1 ----------------------------------------------------------------------
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SCG:] CD: [SCD:]
------------------------------------------------------------------------
1 10-CONNECTED-FROM 3462244566
5 10-CONNECTED-TO 38227064
11 10-CONNECTED-TO 231
14 10-CONNECTED-FROM 347855710
15 07-LOC-ALERT 335586497 509
17 10-CONNECTED-TO 2
- Sapi ------- TEI -- STATE --------------------------------------------
16 (X.25 ) 10 00-INACTIVE
0 (Q.931) 0 07-CONNECTED
------------------------------------------------------------------------
ISDN-STATE:PRI-UP SLIPS:63
RxAlarms:NONE TxAlarms:NONE

Data shows that the physical layer is UP (ISDN-STATE:PRI-UP) and the TEI has been correctly negotiated (TEI-0
STATE:07-CONNECTED). Several calls are present (CONNECTED-FROM , CONNECTED-TO) on this port and for each one
the corresponding PRI channel in use (CH:1-5-11...) is indicated.

42.9.2. CTI Ports statistics

To show the statistics of the CTI Ports (ISDN Basic or Primary Rate) the following commands are used:

d s ctip Shows the statistics of all the CTI ports.

d s ctip:<CTIP_number> Shows the statistics of a single CTI port.

Example: ISDN BRI port statistics.

[15:55:24] ABILIS_CPX:d s ctip:31

CTIP:31 ----------------------------------------------------------------------
TO_PBX
--- Cleared 0 days 06:55:06 ago, on 24/11/2010 at 09:00:34 -------------
Layer 3 Q.931
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0|
------------------------------------------------------------------------
Layer 2 Sapi 16 (X.25) TEI:10
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 0|T200-UP | | 0|
REP | 0| 0|INFO | 0| 0|
UI | 0| 0|RR | 0| 0|
RNR | 0| 0|REJ | 0| 0|
FRMR | 0| 0|SABME | 0| 0|
UA | 0| 0|DISC | 0| 0|
DM | 0| 0|N200-OVER | | 0|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 2 Sapi 0 (Q.931) TEI:ALL
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 0|T200-UP | | 0|
REP | 0| 0|INFO | 4| 4|

650
Draft CTI System Draft

UI | 0| 0|RR | 4973| 4973|

RNR | 0| 0|REJ | 0| 0|
FRMR | 0| 0|SABME | 1| 1|
UA | 1| 1|DISC | 0| 0|
DM | 0| 0|N200-OVER | | 0|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 1 B-Channels (HDLC)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
CHR-D | 0| 0|FRM-D | 0| 0|
CHR-V | 0| 0|FRM-V | 0| 0|
CHR-C | 0| 0|FRM-C | 0| 0|
ERRORS | 0| 0|
------------------------------------------------------------------------
Layer 1 D-Channel
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 19954| 19954|FRM | 4979| 4979|
CHR-D | 19954| 19954|FRM-D | 4979| 4979|
ERRORS | 1| 0|
------------------------------------------------------------------------
Layer 1 alarms
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SLIPS | N/A| N/A|LINE-DOWN | 0| |
------------------------------------------------------------------------

The data “Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS” shows the time interval elapsed from the last
reset of statistics (in the format “days:hours:minutes:seconds”) and date/time of its execution (in the format “day:month:year”
and “hours:minutes:seconds”).

All the other statistics present give detailed and sensitive informations about the connection between Abilis and the other
devices (i.e. PABX, the ISDN line…). The statistics regard all the three level of ISO-OSI model:

• the physical layer (Layer 1) which shows the number of physical errors, the characters both on D-Channel and B-Channels
and so on;

• the LAPD level (Layer 2) which shows the number of packets that the devices exchange;

• the Q.931 level (Layer 3) which the information about the overall duration of the connection or the number of successful
incoming calls over all the channels.

More informations can be viewedusing the following commands:

d se ctip Shows the extended statistics of all the CTI ports.

d se ctip:<CTIP_number> Shows the extended statistics of a single CTI port.

Example: extended statistics for the previous ISDN BRI port.

[15:55:40] ABILIS_CPX:d se ctip:31

CTIP:31 ----------------------------------------------------------------------
Linea_ISDN_verso_PABX
--- Cleared 0 days 06:56:41 ago, on 24/11/2010 at 09:00:34 -------------
Layer 3 Q.931
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0|
------------------------------------------------------------------------
Layer 2 Sapi 16 (X.25) TEI:10
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 0|T200-UP | | 0|
REP | 0| 0|INFO | 0| 0|
UI | 0| 0|RR | 0| 0|
RNR | 0| 0|REJ | 0| 0|

651
Draft CTI System Draft

FRMR | 0| 0|SABME | 0| 0|
UA | 0| 0|DISC | 0| 0|
DM | 0| 0|N200-OVER | | 0|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 2 Sapi 0 (Q.931) TEI:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 0|T200-UP | | 0|
REP | 0| 0|INFO | 4| 4|
UI | 0| 0|RR | 4993| 4993|
RNR | 0| 0|REJ | 0| 0|
FRMR | 0| 0|SABME | 1| 1|
UA | 1| 1|DISC | 0| 0|
DM | 0| 0|N200-OVER | | 0|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 1 B-Channels (HDLC)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 0| 0|FRM | 0| 0|
CHR-D | 0| 0|FRM-D | 0| 0|
CHR-V | 0| 0|FRM-V | 0| 0|
CHR-C | 0| 0|FRM-C | 0| 0|
ERRORS | 0| 0| | | |
D-ABORT | | 0|D-LONG | 0| 0|
D-TXUND | | 0|D-SHORT | | 0|
D-LOST | 0| | | | |
V-ABORT | | 0|V-LONG | 0| 0|
V-TXUND | | 0|V-SHORT | | 0|
V-LOST | 0| | | | |
C-ABORT | | 0|C-LONG | 0| 0|
C-TXUND | | 0|C-SHORT | | 0|
C-LOST | 0| | | | |
ABORT | 0| |UNALIGNED | 0| |
BAD-FCS | 0| |SHORT | 0| |
CHR-OVR | 0| |FRM-OVR | 0| |
------------------------------------------------------------------------
Layer 1 D-Channel
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 20034| 20034|FRM | 4999| 4999|
CHR-D | 20034| 20034|FRM-D | 4999| 4999|
ERRORS | 1| 0| | | |
D-ABORT | | 0|D-LONG | 0| 0|
D-TXUND | | 0|D-SHORT | | 0|
D-LOST | 0| | | | |
ABORT | 0| |UNALIGNED | 0| |
BAD-FCS | 1| |SHORT | 0| |
CHR-OVR | 0| |FRM-OVR | 0| |
------------------------------------------------------------------------
Layer 1 alarms
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SLIPS | N/A| N/A|LINE-DOWN | 0| |
------------------------------------------------------------------------

The informations displayed are the same as previously, but more detailed and splitted (i.e. the generic “ERRORS” is
subdivided in D-ABORT, D-TXUND, ABORT, BAD-FCS…).

42.9.3. CTI Cluster diagnostics and statistics

Use the following commands to show diagnostics and statistics of CTI Clusters:

d d cticl / d de cticl Shows the state of the clusters.

652
Draft CTI System Draft

d s cticl / d se cticl Shows statistics about clusters such as the number of total/successful/failed calls, the
total duration of the calls and the statistics of the DSP.

[16:16:35] ABILIS_CPX:d d cticl

---------+---------+-----------------------------------------------------------
CLUS: |Int |STATE:
---------+---------+-----------------------------------------------------------
CPX_1 1 [01] ALL-UP
CPX_2 2 [02] ALL-UP
CPX_3 3 [03] ALL-UP
CPX_4 4 [04] ALL-UP

[16:16:35] ABILIS_CPX:d s cticl

CLUS:CPX_1 Int:1 [01]

--- Cleared 1 days 20:04:42 ago, on 17/12/2007 at 21:04:44 -------------

-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 12| 8|SUCC-CALL | 9| 7|
FAIL-CALL | 3| 1|TIME-CALL | 4966| 861|
------------------------------------------------------------------------
--- Local and remote DSP statistics, updated at call end ---------------
-----------|---LOCAL---|--REMOTE---|-----------|---LOCAL---|--REMOTE---|
VOICE-UND | 544| 0|VOICE-OVR | 12| 0|
FM-UND | 0| 0|FM-OVR | 0| 0|
------------------------------------------------------------------------
CLUS:CPX_2 Int:2 [02]

--- Cleared 1 days 20:04:42 ago, on 17/12/2007 at 21:04:44 -------------

-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 41| 6|SUCC-CALL | 18| 4|
FAIL-CALL | 23| 2|TIME-CALL | 2681| 1156|
------------------------------------------------------------------------
--- Local and remote DSP statistics, updated at call end ---------------
-----------|---LOCAL---|--REMOTE---|-----------|---LOCAL---|--REMOTE---|
VOICE-UND | 0| 3|VOICE-OVR | 0| 0|
FM-UND | 0| 0|FM-OVR | 0| 0|
------------------------------------------------------------------------
CLUS:CPX_3 Int:3 [03]

--- Cleared 1 days 20:04:42 ago, on 17/12/2007 at 21:04:44 -------------

-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 114| 151|SUCC-CALL | 90| 102|
FAIL-CALL | 24| 49|TIME-CALL | 14804| 12960|
------------------------------------------------------------------------
--- Local and remote DSP statistics, updated at call end ---------------
-----------|---LOCAL---|--REMOTE---|-----------|---LOCAL---|--REMOTE---|
VOICE-UND | 387| 2507|VOICE-OVR | 152| 0|
FM-UND | 0| 6|FM-OVR | 38| 0|
------------------------------------------------------------------------
CLUS:CPX_4 Int:4 [04]
--- Cleared 1 days 20:04:42 ago, on 17/12/2007 at 21:04:44 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 0| 0|SUCC-CALL | 0| 0|
FAIL-CALL | 0| 0|TIME-CALL | 0| 0|
------------------------------------------------------------------------
--- Local and remote DSP statistics, updated at call end ---------------
-----------|---LOCAL---|--REMOTE---|-----------|---LOCAL---|--REMOTE---|
VOICE-UND | 0| 0|VOICE-OVR | 0| 0|
FM-UND | 0| 0|FM-OVR | 0| 0|
------------------------------------------------------------------------

653
Draft CTI System Draft

42.9.4. CTI Link diagnostics and statistics

Use the following commands to show the diagnostics and statistics of CTI Links:

d d ctil / d de ctil Shows the state of the links.

d s ctil / d se ctil Shows statistics about links such as the number of total/successful/failed calls and the
total duration of all calls.

[16:16:35] ABILIS_CPX:d d ctil

ID: CLUS: RES: LINK-STATE: CLUS-LINK-STATE: MAXBW: CURBW: CON:

-------------------------------------------------------------------------------
1 CPX_1 Pv-1 L1-CONNECTED L2-CONNECTED 64000 11000 1
2 CPX_2 Pv-2 L1-CONNECTED L1-CONNECTED NOMAX 0 0
3 CPX_3 Pv-3 L1-CONNECTED L1-CONNECTED NOMAX 0 0
4 CPX_4 Pv-4 L1-CONNECTED L1-CONNECTED NOMAX 0 0

[16:16:35] ABILIS_CPX:d s ctil

ID:1 CLUS:CPX_1
--- Cleared 3 days 17:25:39 ago, on 10/01/2008 at 20:17:52 ------------------
----------------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 68| 5|SUCC-CALL | 44| 3|
FAIL-CALL | 24| 2|TIME-CALL | 9820| 241|
GROUP-MAXBW-OVR | 0| 0|VFM-OVR | | 0|
GROUP-MAXCON-OVR| 0| 0|Q931c-OVR | | 0|
-----------------------------------------------------------------------------
ID:2 CLUS:CPX_2
--- Cleared 3 days 17:25:39 ago, on 10/01/2008 at 20:17:52 ------------------
----------------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 0| 1|SUCC-CALL | 0| 1|
FAIL-CALL | 0| 0|TIME-CALL | 0| 0|
GROUP-MAXBW-OVR | 0| 0|VFM-OVR | | 0|
GROUP-MAXCON-OVR| 0| 0|Q931c-OVR | | 0|
-----------------------------------------------------------------------------
ID:3 CLUS:CPX_3
--- Cleared 3 days 17:25:39 ago, on 10/01/2008 at 20:17:52 ------------------
----------------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 3| 2|SUCC-CALL | 3| 1|
FAIL-CALL | 0| 1|TIME-CALL | 563| 56|
GROUP-MAXBW-OVR | 0| 0|VFM-OVR | | 0|
GROUP-MAXCON-OVR| 0| 0|Q931c-OVR | | 0|
-----------------------------------------------------------------------------
ID:4 CLUS:CPX_4
--- Cleared 3 days 17:25:39 ago, on 10/01/2008 at 20:17:52 ------------------
----------------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CALL | 7| 15|SUCC-CALL | 6| 12|
FAIL-CALL | 1| 3|TIME-CALL | 1211| 5317|
GROUP-MAXBW-OVR | 0| 0|VFM-OVR | | 0|
GROUP-MAXCON-OVR| 0| 0|Q931c-OVR | | 0|
-----------------------------------------------------------------------------

Values of VMF-OVR and Q931c-OVR fields greater than zero show there is some sort of overload of the system (it is needed
to check for abnormal CPU consumption). A value greater than 0 may also indicate an overload of the cluster, i.e. an attempt
to use more bandwidth than the link itself is able to sustain.

42.9.5. CTI connections

It shows the currently present CTI Router connections. Information is displayed in a short format.

[18:51:21] ABILIS_CPX:d ctic

ID Type Input Output PR State Cgi (Calling In) Cdo (Called Out)

654
Draft CTI System Draft

----- ---- -------- -------- --- ------ ------------------ --------------------

202 DATA 557 4 1 ACTIVE 02205241
2892 TR 3 G2 1 G1 25 ACTIVE 29350252 505
2903 TR 3 G2 1 G1 25 ACTIVE 335824923 7
2937 TR 3 G2 1 G1 25 ACTIVE 7
2939 TR 3 G2 1 G1 25 ACTIVE 362520 224
2944 TR 3 G2 1 G1 25 ACTIVE 32169134 218
2945 TR 1 G1 3 24 ALERT 35250561

Use the following command to view ctic in extended format.

[08:38:19] CPX_ANTEK-PBX:_d ctic

ID Type Input Output PR State Cgi (Calling In) Cdo (Called Out)
---- ---- -------- -------- --- ------ ------------------- --------------------
1260 CtoC CPINLIN PlinkCo2 100 ACTIVE 702 0033382501154
1261 VtoC 37 PlinkCo2 138 ACTIVE 35 0458960815

[08:38:33] CPX_ANTEK-PBX:_d ctice

-------------------------------------------------------------------------------
ID:1260 TYPE:CtoC ST:ACTIVE PR:100 STI:10/00 STO:10/00 EEC:NO
START:20/12/2010 08:36:33 DURATION:105 REMAINING:-
POI:305 GI:# SR:CPINLIN POO:351 GO:# DS:PlinkCo2
CDI:ue0033382501154 CDO:ue0033382501154
CGI:ueay702 CGO:neay03761626202
SDI: SDO:
SGI: SGO:
RGI: RGO:
CODER:Spirit SP:6400 FMRLY:YES FAXSP:9600 DJ:0 FMDJ:200
BW:11000 SC:NO MODSP:7200 MJ:100 FMMJ:400
-------------------------------------------------------------------------------
ID:1261 TYPE:VtoC ST:ACTIVE PR:138 STI:10/00 STO:10/00 EEC:NO
START:20/12/2010 08:37:13 DURATION:67 REMAINING:-
POI:37 GI:# SR:# POO:351 GO:# DS:PlinkCo2
CDI:ue00458960815 CDO:ue0458960815
CGI:uxay35 CGO:neay03761626235
SDI: SDO:35
SGI: SGO:
RGI: RGO:
CODER:Spirit SP:6400 FMRLY:YES FAXSP:9600 DJ:50 FMDJ:200
CTIAC:0 BW:11000 SC:NO MODSP:7200 MJ:150 FMMJ:400
MODE:VOICE CurJ:120 TopJ:140 AvgJ:87 FaxPg:0 ECM:NO
UND:39 OVR:22

The message “NO CTI CONNECTIONS” is generated if no CTI connection is running.

42.9.6. DSP and Audio Coders

The following command shows the available DSP and their state; it shows the maximum number of possible simultaneous
calls.

[08:40:39] ABILIS_CPX:_d d ctiac

-------------------------------------------------------------------------------
AC Card DSP/C Bus/TS DSPState ACState ModeIn ModeOut Coder Ctip/BC
-------------------------------------------------------------------------------
0 BRI4-2 0/0 1/00 RUN IDLE - - - -
1 BRI4-2 0/1 1/01 RUN IDLE - - - -
2 BRI4-2 0/2 1/02 RUN IDLE - - - -
3 BRI4-2 0/3 1/03 RUN IDLE - - - -
4 BRI4-2 1/0 1/05 RUN IDLE - - - -
5 BRI4-2 1/1 1/06 RUN IDLE - - - -
6 BRI4-2 1/2 1/07 RUN IDLE - - - -

655
Draft CTI System Draft

7 BRI4-2 1/3 1/08 RUN IDLE - - - -

8 UG-1 0/0 0/00 RUN IDLE - - - -
9 UG-1 0/1 0/01 RUN IDLE - - - -

Use the following command to view informations in extended format.

[16:16:41] ABILIS_CPX:d de ctiac

-------------------------------------------------------------------------------
AC Card DSP/C Bus/TS DSPState ACState ModeIn ModeOut Coder Ctip/BC
Dtmf DhVol DlVol FmLevel InGain OutGain SigGain MaxFaxSp MaxModSp
SC V-DJ V-MJ V-CurJ V-TopJ V-AvgJ EC BypassCoder
ECM FM-DJ FM-MJ FM-CurJ FM-TopJ FM-AvgJ FaxTxPg FaxFlowState
-------------------------------------------------------------------------------
0 BRI4-2 0/0 8/00 RUN IDLE - - - -
1 BRI4-2 0/1 8/01 RUN IDLE - - - -
2 BRI4-2 0/2 8/02 RUN IDLE - - - -
3 BRI4-2 0/3 8/03 RUN IDLE - - - -
4 BRI4-2 1/0 9/05 RUN IN-USE VOICE VOICE Spirit/6.4k 108/01
OUTBAND -4 -6 -9 0 0 0 9600 7200
NO 50 150 80 100 68 YES -
200 400 0 0 0 0 -
5 BRI4-2 1/1 9/06 RUN IDLE - - - -
6 BRI4-2 1/2 9/07 RUN IDLE - - - -
7 BRI4-2 1/3 9/08 RUN IDLE - - - -
8 UG-1 0/0 0/00 RUN IDLE - - - -
9 UG-1 0/1 0/01 RUN IDLE - - - -

The following command shows the available coders supported by CTI cards installed and the number of simultaneous calls.

[08:44:19] ABILIS_CPX:_d d ctisys

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
CTIR-STATE:ENABLED CALLS-CURRENT:1 CALLS-PEAK:7
AC-STATE:ENABLED AC-CURRENT:0 AC-PEAK:5
------------------------------------------------------------------------
-- Number of simultaneous calls ----------------------------------------
| State: Alerting/Connected | State: Any |
---------------|---Current---|----Peak-----|---Current---|----Peak-----|
TR | 0 | 3 | 0 | 3 |
DATA | 0 | 0 | 0 | 0 |
VtoCHISD | 0 | 3 | 0 | 3 |
CHISDtoCHISD | 1 | 6 | 1 | 6 |
CHISDtoV | 0 | 2 | 0 | 2 |
ALL | 1 | 7 | 1 | 7 |
------------------------------------------------------------------------
- Available coders -----------------------------------------------------
-- Coder ---|-- Bit rates (kbps) --|-- Coder ---|-- Bit rates (kbps) --|
G.711A |64 |G.711u |64 |
G.723.1 |5.3, 6.3 |G.726 |16, 24, 32, 40 |
G.729A |8 |TRANSPARENT |64 |
Spirit |6.4, 7.2, 8, 8.8, 9.6 |G.727 |16/16, 24/16, 24/24, |
| | |32/16, 32/24, 32/32, |
| | |40/16, 40/24, 40/32 |
------------------------------------------------------------------------
- Clock Sources for H100 cards -----------------------------------------
CLK:38
- Clock Sources for NOT-H100 cards -------------------------------------
*** No NOT-H100 cards running ***

Type the following commands to show the statistics about DSP and audio coders:

[08:48:57] ABILIS_CPX:_d s ctiac

656
Draft CTI System Draft

-------------------------------------------------------------------------------
AC's Statistics were cleared 6 days 11:37:33 ago, on 13/12/2010 at 21:12:18
-------------------------------------------------------------------------------

AC:0 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 86| |CLOSE | 86| |
PCK | 521791| 446607|CHR | 20656562| 15657186|
VOICE-UND | | 424|FM-UND | | 0|
VOICE-OVR | | 105|FM-OVR | | 0|
VOICE-LOST | 0| |FM-LOST | 0| |
FRM | 633056| 446390|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 501398| 429708|FRM-FAX-REL| 88| 1291|
FRM-SILENCE| 120687| 15317|FRM-CED | 1| 2|
FRM-SID | 7502| 0|FRM-FAX-DUM| 3330| |
FRM-DTMF | 50| 0|FAX-TOUT | 0| |
TX-UND | | 404|RX-OVR | 0| |
MDC | 0| |CMD | | 1376|
------------------------------------------------------------------------

AC:1 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 83| |CLOSE | 83| |
PCK | 266191| 222528|CHR | 16375754| 13084940|
VOICE-UND | | 3117|FM-UND | | 0|
VOICE-OVR | | 314|FM-OVR | | 0|
VOICE-LOST | 1| |FM-LOST | 0| |
FRM | 339277| 222144|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 256918| 209117|FRM-FAX-REL| 630| 5469|
FRM-SILENCE| 62069| 7497|FRM-CED | 7| 0|
FRM-SID | 3175| 0|FRM-FAX-DUM| 16445| |
FRM-DTMF | 33| 2|FAX-TOUT | 0| |
TX-UND | | 2886|RX-OVR | 1| |
MDC | 0| |CMD | | 1093|
------------------------------------------------------------------------

AC:2 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 85| |CLOSE | 85| |
PCK | 212028| 213795|CHR | 11544936| 11103158|
VOICE-UND | | 677|FM-UND | | 0|
VOICE-OVR | | 341|FM-OVR | | 3|
VOICE-LOST | 2| |FM-LOST | 0| |
FRM | 258895| 213321|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 205093| 206882|FRM-FAX-REL| 707| 1828|
FRM-SILENCE| 44488| 4546|FRM-CED | 2| 4|
FRM-SID | 2275| 0|FRM-FAX-DUM| 6324| |
FRM-DTMF | 6| 3|FAX-TOUT | 0| |
TX-UND | | 615|RX-OVR | 0| |
MDC | 0| |CMD | | 1224|
------------------------------------------------------------------------

AC:3 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 81| |CLOSE | 81| |
PCK | 329029| 353294|CHR | 16531696| 14974230|
VOICE-UND | | 3287|FM-UND | | 0|
VOICE-OVR | | 1369|FM-OVR | | 0|
VOICE-LOST | 5| |FM-LOST | 0| |
FRM | 414667| 351840|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 320074| 340720|FRM-FAX-REL| 176| 1323|

657
Draft CTI System Draft

FRM-SILENCE| 87166| 9734|FRM-CED | 2| 0|

FRM-SID | 3181| 0|FRM-FAX-DUM| 4051| |
FRM-DTMF | 17| 0|FAX-TOUT | 0| |
TX-UND | | 2904|RX-OVR | 0| |
MDC | 0| |CMD | | 1361|
------------------------------------------------------------------------

AC:4 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 84| |CLOSE | 84| |
PCK | 424578| 388329|CHR | 37589920| 34629560|
VOICE-UND | | 663|FM-UND | | 0|
VOICE-OVR | | 566|FM-OVR | | 3|
VOICE-LOST | 0| |FM-LOST | 0| |
FRM | 479323| 387648|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 414983| 381352|FRM-FAX-REL| 983| 88|
FRM-SILENCE| 57939| 6141|FRM-CED | 0| 4|
FRM-SID | 3063| 0|FRM-FAX-DUM| 2292| |
FRM-DTMF | 63| 0|FAX-TOUT | 0| |
TX-UND | | 629|RX-OVR | 0| |
MDC | 0| |CMD | | 1271|
------------------------------------------------------------------------

AC:5 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 84| |CLOSE | 84| |
PCK | 600272| 497017|CHR | 26027434| 19455056|
VOICE-UND | | 579|FM-UND | | 0|
VOICE-OVR | | 119|FM-OVR | | 0|
VOICE-LOST | 0| |FM-LOST | 0| |
FRM | 734820| 496826|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 576501| 481701|FRM-FAX-REL| 126| 1948|
FRM-SILENCE| 144277| 13088|FRM-CED | 2| 2|
FRM-SID | 8851| 0|FRM-FAX-DUM| 5061| |
FRM-DTMF | 2| 34|FAX-TOUT | 0| |
TX-UND | | 249|RX-OVR | 0| |
MDC | 0| |CMD | | 1153|
------------------------------------------------------------------------

AC:6 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 84| |CLOSE | 84| |
PCK | 374751| 373547|CHR | 18749814| 16331086|
VOICE-UND | | 1775|FM-UND | | 0|
VOICE-OVR | | 904|FM-OVR | | 2|
VOICE-LOST | 3| |FM-LOST | 0| |
FRM | 488459| 372587|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 357758| 355873|FRM-FAX-REL| 1495| 2515|
FRM-SILENCE| 113082| 14123|FRM-CED | 4| 2|
FRM-SID | 5827| 0|FRM-FAX-DUM| 10236| |
FRM-DTMF | 57| 11|FAX-TOUT | 0| |
TX-UND | | 1517|RX-OVR | 1| |
MDC | 0| |CMD | | 1229|
------------------------------------------------------------------------

AC:7 CARD:BRI4-2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 81| |CLOSE | 81| |
PCK | 444140| 354474|CHR | 19114900| 14292406|
VOICE-UND | | 1133|FM-UND | | 0|
VOICE-OVR | | 438|FM-OVR | | 0|
VOICE-LOST | 5| |FM-LOST | 0| |

658
Draft CTI System Draft

FRM | 563101| 353994|FRM-FAX-BYP| 0| 0|

FRM-VOICE | 428131| 340864|FRM-FAX-REL| 328| 2156|
FRM-SILENCE| 122093| 10900|FRM-CED | 4| 0|
FRM-SID | 5856| 0|FRM-FAX-DUM| 6635| |
FRM-DTMF | 54| 18|FAX-TOUT | 0| |
TX-UND | | 925|RX-OVR | 0| |
MDC | 0| |CMD | | 1180|
------------------------------------------------------------------------

AC:8 CARD:UG-1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 7| |CLOSE | 7| |
PCK | 23489| 26284|CHR | 4231724| 3758240|
VOICE-UND | | 1|FM-UND | | 0|
VOICE-OVR | | 0|FM-OVR | | 0|
VOICE-LOST | 0| |FM-LOST | 0| |
FRM | 525661| 525661|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 25778| 23489|FRM-FAX-REL| 0| 0|
FRM-SILENCE| 0| 0|FRM-CED | 0| 0|
FRM-SID | 0| 0|FRM-FAX-DUM| 0| |
FRM-DTMF | 506| 0|FAX-TOUT | 0| |
TX-UND | | 2899|RX-OVR | 0| |
MDC | 0| |CMD | | 0|
------------------------------------------------------------------------

AC:9 CARD:UG-1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
OPEN | 31| |CLOSE | 31| |
PCK | 201627| 212001|CHR | 34132161| 32260320|
VOICE-UND | | 8735|FM-UND | | 0|
VOICE-OVR | | 0|FM-OVR | | 0|
VOICE-LOST | 0| |FM-LOST | 0| |
FRM | 4239821| 4239851|FRM-FAX-BYP| 0| 0|
FRM-VOICE | 211833| 201627|FRM-FAX-REL| 0| 0|
FRM-SILENCE| 0| 0|FRM-CED | 0| 0|
FRM-SID | 0| 0|FRM-FAX-DUM| 0| |
FRM-DTMF | 168| 0|FAX-TOUT | 0| |
TX-UND | | 10983|RX-OVR | 0| |
MDC | 0| |CMD | | 0|
------------------------------------------------------------------------

[08:49:51] ABILIS_CPX:_d s ctisys

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
--- Cleared 6 days 11:38:43 ago, on 13/12/2010 at 21:12:18 --------------
-- Number of successful (connected) calls, updated at call end ----------
------------|---INPUT---|--OUTPUT---|--LOCAL----|--TRANSIT--|----SUM----|
TR | 4| 7| 76| 0| 87|
DATA | 0| 0| 0| | 0|
VtoCHISD | 3| 148| 0| 31| 182|
CHISDtoCHISD| 34| 1| 0| 334| 369|
CHISDtoV | 99| 0| 2| 6| 107|
SUM | 140| 156| 78| 371| 745|
-------------------------------------------------------------------------
-- Seconds of successful (connected) calls, updated at call end ---------
------------|---INPUT---|--OUTPUT---|--LOCAL----|--TRANSIT--|----SUM----|
TR | 954| 1099| 5914| 0| 7967|
DATA | 0| 0| 0| | 0|
VtoCHISD | 37| 31690| 0| 4265| 35992|
CHISDtoCHISD| 1877| 40| 0| 98884| 100801|
CHISDtoV | 28223| 0| 542| 3825| 32590|

659
Draft CTI System Draft

SUM | 31091| 32829| 6456| 106974| 177350|

-------------------------------------------------------------------------
-- Number of unsuccessful calls -----------------------------------------
------------|---INPUT---|--OUTPUT---|--LOCAL----|--TRANSIT--|----SUM----|
TR | 0| 5| 26| 0| 31|
DATA | 0| 0| 0| | 0|
VtoCHISD | 0| 58| 0| 18| 76|
CHISDtoCHISD| 1| 0| 0| 138| 139|
CHISDtoV | 38| 0| 3| 21| 62|
SUM | 39| 63| 29| 177| 308|
-------------------------------------------------------------------------
-- Internal failures for not connected calls ----------------------------
------------|---INPUT---|--OUTPUT---|--LOCAL----|--TRANSIT--|----SUM----|
NoRoute | | | | | 0|
NoDest | | | | | 0|
NoPcmRes | 0| 0| 0| 0| 0|
NoAcRes | 0| 0| 0| 0| 0|
NoEecRes | 0| 0| 0| 0| 0|
NoHdlcRes | 0| 0| 0| | 0|
NoAcCodec | 0| 0| 0| 0| 0|
PlinkFail | 0| 0| | 0| 0|
BwLimit | | 0| | 11| 11|
IsdnL1down | 0| 0| 0| 0| 0|
IsdnL2down | 0| 0| 0| 0| 0|
-------------------------------------------------------------------------
-- Internal failures after call connected -------------------------------
------------|---INPUT---|--OUTPUT---|--LOCAL----|--TRANSIT--|----SUM----|
PlinkFail | 0| 0| | 0| 0|
IsdnL1down | 0| 0| 0| 0| 0|
IsdnL2down | 0| 0| 0| 0| 0|
-------------------------------------------------------------------------

42.10. Examples of CTI configuration

This section shows how to configure a VPN between two Abilis to transport data and compressed phone calls and a VPN to
transport only voice data.

42.10.1. Configuration of a VPN to transport voice and data.

Consider an Abilis placed in “Site 1”that is connected to another Abilis placed in “Site 2” with a VPN (with backup ISDN)
which transports data and compressed phone calls.

42.10.1.1. Configuration scheme

660
Draft CTI System Draft

Site 1:

• 1 HDSL line with the following parameters:

• AR: 2048000 bit/sec

• encapsulation: fr-ietf

• CIR = MCR: 512000 bit/sec

• PCR: 1600000 bit/sec

• TC: 0.010 sec

• standard: cisco

• DLCI: 20

• IP address: 80.80.80.80/32

• 2 ISDN BRI lines (Point-to-Point) with the following numbers:

• 0212345678

• 0212345679 (used for the backup of the VPN)

• 1 ISDN PBX

• calling number presentation

Site 2:

• 1 ADSL line with the following parameters:

• speed: 1024/256 Kbit/sec

• PPP authentication: rfc2364-vcmux

• VPI: 8

• VCI: 35

• username: abilis_2

• password: abilis_2

• IP address negotiated (81.81.81.81)

• 2 ISDN BRI lines (Point-to-Point) with the following numbers:

• 0611223344

• 0611223345 (used for the backup of the VPN)

• 1 ISDN PBX

• calling number presentation

42.10.1.2. Configuration of IP resources

This section shows how to configure the ip resources on both Abilis.

Warning
The eth-1 card and the ip-1 resource are already present in the configuration.

• ABILIS 1

Set up the IP address of the LAN of “Abilis 1”:

[16:16:35] ABILIS_CPX_1:s p ip-1 ipadd:192.168.0.1 mask:255.255.255.0 nat:inside descr:LAN_Site_1

661
Draft CTI System Draft

COMMAND EXECUTED

Add a synchronous ESB card:

[16:16:35] ABILIS_CPX_1:a dev:esb-1

COMMAND EXECUTED

The execution of this command adds 4 synchronous port: use the sync-1 port and set up the clock source (external) and
the speed (Access Rate):

[16:16:35] ABILIS_CPX_1:s p sync-1 clk:ext sp:2048000 descr:HDSL_line

COMMAND EXECUTED

Add a frame relay resource on a dedicated line (subtype:dl):

[16:16:35] ABILIS_CPX_1:a res:fr-1 subtype:dl

COMMAND EXECUTED

Associate the lowres:sync-1 to the fr-1 resource and set up the standard (cisco), the Access Rate (2048000 bit/sec)
and activate the LMI:

[16:16:35] ABILIS_CPX_1:s p fr-1 lowres:sync-1 std:cisco ar:2048000 lmi:yes

COMMAND EXECUTED

Add a ip resource on a dedicated line (subtype:dl):

[16:16:35] ABILIS_CPX_1:a res:ip-2 subtype:dl

COMMAND EXECUTED

Associate the lowres:fr-1 to the ip-2 resource and set up the encapsulation type (fr-ietf):

[16:16:35] ABILIS_CPX_1:s p ip-2 lowres:fr-1 enc:fr-ietf

COMMAND EXECUTED

Set up the IP address of the HDSL line and the NAT type (outside):

[16:16:35] ABILIS_CPX_1:s p ip-2 ipadd:80.80.80.80 mask:255.255.255.255 nat:outside

COMMAND EXECUTED

Configure the parameter of the frame relay resource:

• DLCI=20

• CIR=1024000 bit/sec

• BC=CIR*TC=512000*0.010=5120 bit

• BE=(PCR-MCR)*TC=(1600000-512000)*0.010=10880 [bit].

[16:16:35] ABILIS_CPX_1:s p ip-2 dlci:20 cir:1024000 bc:10240 be:10880

COMMAND EXECUTED

Configure the outgoing speedlimit with a speed equal to PCR value:

[16:16:35] ABILIS_CPX_1:s p ip-2 outspl:yes outsp:1600

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_1:d p ip-2

662
Draft CTI System Draft

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over Dedicated Line (DL) ------------------------------------------
DESCR:
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Fr-1
ENC:FR-IETF FRAG:NO
IPADD:080.080.080.080 MASK:255.255.255.255 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:YES OUTSP:1600
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:NO LCOMP:NO LCR:NO
LT1:1000 LT3:3000 LN2:3 LCRKEY:DFT
- Frame Relay ----------------------------------------------------------
DLCI:20 CC:YES SC:4
CIR:1024000 BC:10240 BE:10880

[16:16:35] ABILIS_CPX_1:d p fr-1

RES:Fr-1 - Not Saved (SAVE CONF) ----------------------------------------------

- FR over Dedicated Line (DL) ------------------------------------------
DESCR:
LOWRES:Sync-1
- Frame Relay ----------------------------------------------------------
LOG:DS
SIDE:USER-UNI pvc:1
STD:CISCO AR:2048000 LMI:YES
T391:10 T392:15 N391:6 N392:3 N393:4
- Link -----------------------------------------------------------------
LLOG:DS LMPX:NO LCOMP:NO LCR:NO
LT1:1000 LT3:3000 LN2:3 LCRKEY:DFT
RES:Sync-1 - Not Saved (SAVE CONF) --------------------------------------------
------------------------------------------------------------------------
DESCR:HDSL_line
LOG:DS int:V24 CLK:EXT SP:2048000 CLK-INV:NONE
CODING:NRZ IDLE:FLAG mode:FULL RTSDLY:0 CD:NO
FDCD:500 FCTS:500 MPX:NO
E1-FRAMING:CRC4 HAUL:SHORT
CH:ALL
frame:2100 d-rxbuf:14 dma-rxbuf:10 dma-txbuf:1

Add an AIPT resource in Extended mode with ISDN backup:

[16:16:35] ABILIS_CPX_1:a res:ip-5 subtype:aipt-bck

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p ip-5 descr:To_Abilis_2 neigh:192.168.1.1 mask:255.255.255.0 nat:inside

mode:ext remport:2105 locipadd:80.80.80.80 remipadd:81.81.81.81

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p ip-5 brty:us bnrty:30 btb:10 sgi:abilis1-abilis2 sgo:abilis2-abilis1 c

COMMAND EXECUTED

Set up the speedlimit of the VPN:

663
Draft CTI System Draft

[16:16:35] ABILIS_CPX_1:s p ip-5 outspl:yes outsp:240

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_1:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:To_Abilis_2
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.001.001
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:YES OUTSP:240
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:080.080.080.080 REMIPADD:081.081.081.081
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:0611223345
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS1-ABILIS2 SGO:ABILIS2-ABILIS1

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES and LMPX parameter from YES to EXT.

Give the highest priority to the voice IP packets:

[16:16:35] ABILIS_CPX_1:s p iprtr acl:ext cos:enabled

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a ipacl pr:0 type:permit ipcos:high tos-in:*-d prot:udp sa:* da:* sip:int

COMMAND EXECUTED

• ABILIS 2

Set up the IP address of the LAN of “Abilis 2”:

[16:16:35] ABILIS_CPX_2:s p ip-1 ipadd:192.168.1.1 mask:255.255.255.0 nat:inside descr:LAN_Site_2

COMMAND EXECUTED

Add the ADSL USB modem. The execution of this command creates the adsl-1 resource.

664
Draft CTI System Draft

[16:16:35] ABILIS_CPX_2:a dev:adslusb-1

COMMAND EXECUTED

Add the ip resource ip-2 (subtype:ppp):

[16:16:35] ABILIS_CPX_2:a res:ip-2 subtype:ppp

COMMAND EXECUTED

Associate the ip-2 resource to the lowres:adsl-1 and set up the IP address of the resource (retrieve), the IP address
of the neighbour router (retrieve) and the NAT type (outside):

[16:16:35] ABILIS_CPX_2:s p ip-2 lowres:adsl-1 ipadd:retrieve neigh:retrieve nat:outside descr:ADS

COMMAND EXECUTED

Set up the encapsulation type (ppp-enc), the Virtual Path Identifier (VPI) and the Virtual Channel Identifier (VCI) of
the ADSL line:

[16:16:35] ABILIS_CPX_2:s p ip-2 ppp-enc:rfc2364-vcmux vpi:8 vci:35

COMMAND EXECUTED

Configure the authentication parameters (username and password) of the ADSL line:

[16:16:35] ABILIS_CPX_2:s p ip-2 username:abilis_2 password:abilis_2

COMMAND EXECUTED

Set up the speedlimit with a speed slightly lower than the upload speed of the ADSL line:

[16:16:35] ABILIS_CPX_2:s p ip-2 outspl:yes outsp:240

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_2:d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over PPP (PPP) ----------------------------------------------------
DESCR:ADSL_line
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Adsl-1
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:YES OUTSP:240
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RFC2364-VCMUX RADIUS:NO
VPI:8 VCI:35
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO
maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:abilis_2
PASSWORD:******** LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE
REPEAT:0
RES:Adsl-1 - Not Saved (SAVE CONF) --------------------------------------------

665
Draft CTI System Draft

------------------------------------------------------------------------
DESCR:
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:3 usb-tx-bufsize:3200

Add an AIPT resource in Extended mode with ISDN backup:

[16:16:35] ABILIS_CPX_2:a res:ip-5 subtype:aipt-bck

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:s p ip-5 descr:To_Abilis_1 neigh:192.168.0.1 mask:255.255.255.0 nat:inside

mode:ext remport:2105 locipadd:81.81.81.81 remipadd:80.80.80.80

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:s p ip-5 brty:us bnrty:30 btb:10 sgi:abilis2-abilis1 sgo:abilis1-abilis2 c

COMMAND EXECUTED

Set up the speedlimit of the VPN:

[16:16:35] ABILIS_CPX_2:s p ip-5 outspl:yes outsp:240

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_2:d p ip-5

RES:Ip-5 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over IP (Abilis tunnel) with Abilis Back-up (AIPT-BCK) ------------
DESCR:To_Abilis_1
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
BCKRES:CtiSLink
FRAG:FRF12 FRAGSIZE:800
IPADD:000.000.000.000 MASK:255.255.255.000 NEIGH:192.168.000.001
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:INSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:YES OUTSP:240
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:DATA
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:100 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:2105 REMPORT:2105 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:081.081.081.081 REMIPADD:080.080.080.080
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:0212345679
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS2-ABILIS1 SGO:ABILIS1-ABILIS2

666
Draft CTI System Draft

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES and LMPX parameter from YES to EXT.

Give the highest priority to the voice IP packets:

[16:16:35] ABILIS_CPX_2:s p iprtr acl:ext cos:enabled

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a ipacl pr:0 type:permit ipcos:high tos-in:*-d prot:udp sa:* da:* sip:int

COMMAND EXECUTED

42.10.1.3. Configuration of the CTI resource

• ABILIS 1

Add the BRI-4/HFC card:

[16:16:35] ABILIS_CPX_1:a dev:bri4-1

COMMAND EXECUTED

The execution of this command creates the CTI ports from 31 to 34. Configure the ports 31 and 32 towards PBX and 33
and 34 ports to ISDN lines:

[16:16:35] ABILIS_CPX_1:s p ctip:31 side:nt line:pp descr:To_PBX

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p ctip:32 side:nt line:pp descr:To_PBX

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p ctip:33 side:te line:pp descr:To_ISDN_lines_(0212345678)

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p ctip:34 side:te line:pp descr:To_ISDN_lines_(0212345679)

COMMAND EXECUTED

Add G1 group that groups CTI ports towards PBX and G2 that groups CTI ports towards ISDN lines:

[16:16:35] ABILIS_CPX_1:a ctig id:1 p1:31 p2:32 descr:To_PBX

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a ctig id:2 p1:33 p2:34 descr:To_ISDN_lines

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:d ctig

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

--------------------------------------+--------------------+-------------------
[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
To_PBX

667
Draft CTI System Draft

1 NO R ST |31 32 . . . |. . . . .
--------------------------------------+--------------------+-------------------
To_ISDN_lines
2 NO R ST |33 34 . . . |. . . . .
--------------------------------------+--------------------+-------------------

Add To_Site_2 list containing numbers to route towards tunnel; the list contains the unique number of “Site
2” (0611223344):

[16:16:35] ABILIS_CPX_1:list create To_site_2 in Numbers_to_Site_2

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a list:To_Site_2 0611223344

COMMAND EXECUTED

Add Node list containing numbers of local PBX:

[16:16:35] ABILIS_CPX_1:list create Node in Local_Numbers

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a list:Node 0212345678

COMMAND EXECUTED

Add a cluster for compressed calls towards “Site 2”:

[16:16:35] ABILIS_CPX_1:a cticl id:Site_2 descr:Compressed_phones_towards_Site_2

COMMAND EXECUTED

Add a CTI Link and associate the Site_2 cluster to ip-5 resource:

[16:16:35] ABILIS_CPX_1:a ctil id:1 res:ip-5 clus:Site_2

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:d ctil

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 ip-5 Site_2 NOMAX NOMAX NONE

[16:16:35] ABILIS_CPX_1:d cticl

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Clusters:1

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
Site_2 Compressed_phones_towards_Site_2
[ 1] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------

668
Draft CTI System Draft

Add a CTI routing (type:DATA) to route outcoming ISDN backup calls:

[16:16:35] ABILIS_CPX_1:a ctir pr:1 type:data poo:g2 cdi:*

COMMAND EXECUTED

Add a CTI routing (type:CtoV) for calls coming from “Site 2” and directed to the local PBX:

[16:16:35] ABILIS_CPX_1:a ctir pr:2 type:CtoV sr:* poo:g1 cdi:'Node'

COMMAND EXECUTED

Add a CTI routing (type:VtoC) for compressed calls directed to “Site 2”, with next parameter set to u (unlimited) to
route calls on ISDN lines if it is not possible to route them towards the Tunnel:

[16:16:35] ABILIS_CPX_1:a ctir pr:3 type:VtoC next:u poi:g1 ds:Site_2 cdi:'To_Site_2'

COMMAND EXECUTED

Add two CTI routings (type:TR) to guarantee the transparent calls from PBX towards ISDN lines and from PBX towards
ISDN lines:

[16:16:35] ABILIS_CPX_1:a ctir pr:4 type:tr poi:g1 poo:g2 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a ctir pr:5 type:tr poi:g2 poo:g1 cdi:*

COMMAND EXECUTED

Here it is the result of the configuration:

[16:32:06] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 09:08:57 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 CtoV * G1 'Node' *
-------------------------------------------------------------------------------
3 VtoC G1 Site_2 'To_site_2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
4 TR G1 G2 * *
-------------------------------------------------------------------------------
5 TR G2 G1 * *
-------------------------------------------------------------------------------

669
Draft CTI System Draft

Tip
Remember to save the configuration with the save conf command.

• ABILIS 2

The configuration of CTI ports and CTI groups is identical to “Abilis 1”. For the remaining configuration it is only needed
to change the ISDN numbers.

Add To_Site_1 list containing numbers to route towards tunnel; in this example the list contains the unique number of
“Site 1” (0212345678):

[16:16:35] ABILIS_CPX_2:list create To_site_1 in Numbers_to_Site_1

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a list:To_Site_2 0212345678

COMMAND EXECUTED

Add Node list containing numbers of local PBX:

[16:16:35] ABILIS_CPX_2:list create Node in Local_Numbers

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a list:Node 0611223344

COMMAND EXECUTED

Add a cluster for compressed calls towards “Site 1”:

[16:16:35] ABILIS_CPX_2:a cticl id:Site_1 descr:Compressed_phones_towards_Site_1

COMMAND EXECUTED

Add a CTI Link and associate the Site_1 cluster to ip-5 resource:

[16:16:35] ABILIS_CPX_2:a ctil id:1 res:ip-5 clus:Site_1

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:d ctil

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 ip-5 Site_1 NOMAX NOMAX NONE

[16:16:35] ABILIS_CPX_2:d cticl

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Clusters:1

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------

670
Draft CTI System Draft

Site_1 Compressed_phones_towards_Site_1
[ 1] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------

Add the following routings:

[16:16:35] ABILIS_CPX_2:a ctir pr:1 type:data poo:g2 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a ctir pr:2 type:CtoV sr:* poo:g1 cdi:'Node'

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a ctir pr:3 type:VtoC next:u poi:g1 ds:Site_1 cdi:'To_Site_1'

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a ctir pr:4 type:tr poi:g1 poo:g2 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:a ctir pr:5 type:tr poi:g2 poo:g1 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_2:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 09:14:16 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 CtoV * G1 'Node' *
-------------------------------------------------------------------------------
3 VtoC G1 Site_1 'To_site_1' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
4 TR G1 G2 * *
-------------------------------------------------------------------------------
5 TR G2 G1 * *
-------------------------------------------------------------------------------

Tip
Remember to save the configuration with the save conf command.

671
Draft CTI System Draft

42.10.2. Configuration of a VPN to transport only voice.

Consider the previous example and suppose that the Abilis in “Site 1” is connected to another Abilis in “Site 3” with a VPN
that transports only compressed phone calls.

42.10.2.1. Configuration scheme

Site 1:

• Add an ADSL line with the following parameters to the previous configuration:

• speed: 1024/256 Kbit/sec

• PPP authentication: rfc2364-mux

• VPI: 8

• VCI: 35

• username: abilis_1

• password: abilis_1

• IP address negotiated (60.60.60.60)

Site 2:

• 1 ADSL line with the following parameters:

• speed: 1024/256 Kbit/sec

• PPP authentication: rfc1483-llcmux

• VPI:8

• VCI:35

• IP address: 61.61.61.61/30

• 2 ISDN Basic Rate Interface lines (Point-to-Point) with the following numbers:

• 045566789, 0455668888, 045566999 (used for the backup of the VPN)

• 1 ISDN PBX

• calling number presentation

42.10.2.2. Configuration of IP resources

In this section it is shown how to configure the ip resources on both Abilis.

672
Draft CTI System Draft

Warning
The eth-1 card and the ip-1 resource are already present in the configuration.

• ABILIS 1

Add the ADSL USB modem. The execution of this command creates the adsl-1 resource.

[16:16:35] ABILIS_CPX_1:a dev:adslusb-1

COMMAND EXECUTED

Add the ip resource ip-3 (subtype:ppp):

[16:16:35] ABILIS_CPX_1:a res:ip-3 subtype:ppp

COMMAND EXECUTED

Associate the ip-3 resource to the lowres:adsl-1 and set up the IP address of the resource (retrieve), the IP address
of the neighbour router (retrieve) and the NAT type (outside):

[16:16:35] ABILIS_CPX_1:s p ip-3 lowres:adsl-1 ipadd:retrieve neigh:retrieve nat:outside descr:ADS

COMMAND EXECUTED

Set up the encapsulation type (ppp-enc), the Virtual Path Identifier (VPI) and the Virtual Channel Identifier (VCI) of
the ADSL line:

[16:16:35] ABILIS_CPX_1:s p ip-3 ppp-enc:rfc2364-vcmux vpi:8 vci:35

COMMAND EXECUTED

Configure the authentication parameters (username and password) of the ADSL line:

[16:16:35] ABILIS_CPX_1:s p ip-3 username:abilis_1 password:abilis_1

COMMAND EXECUTED

Set up the speedlimit with a speed slightly lower than the upload speed of the ADSL line:

[16:16:35] ABILIS_CPX_1:s p ip-3 outspl:yes outsp:240

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_1:d p ip-3

RES:Ip-3 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over PPP (PPP) ----------------------------------------------------
DESCR:ADSL_line
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Adsl-1
IPADD:RETRIEVE NEIGH:RETRIEVE
REDIS:EXT HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500
OUTSPL:YES OUTSP:240
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Ppp ------------------------------------------------------------------
LOG:DS NRTY3:3 PPP-ENC:RFC2364-VCMUX RADIUS:NO
VPI:8 VCI:35
- Tcp-MSS/Lcp/IpCp -----------------------------------------------------
TCP-MSS-CLAMP:NO

673
Draft CTI System Draft

maxmru:1500 DNS:NO
- Authentication -------------------------------------------------------
USERNAME:abilis_1
PASSWORD:******** LOCAL:CHAP,PAP
SERVNAME: REMOTE:NONE
REPEAT:0
RES:Adsl-1 - Not Saved (SAVE CONF) --------------------------------------------
------------------------------------------------------------------------
DESCR:
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:3 usb-tx-bufsize:3200

Add a Packet Voice resource in Extended mode with ISDN backup:

[16:16:35] ABILIS_CPX_1:a res:pv-1 subtype:ip-bck

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p pv-1 mode:ext remport:3101 locipadd:60.60.60.60 remipadd:61.61.61.61 d

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:s p pv-1 brty:us bnrty:30 btb:10 sgi:abilis1-abilis3 sgo:abilis3-abilis1 c

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------
DESCR:To_Abilis_3
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:060.060.060.060 REMIPADD:061.061.061.061
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:045566999
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS1-ABILIS3 SGO:ABILIS3-ABILIS1

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

It is important to ensure that outgoing packets are routed towards the appropriate resource. If it is necessary, add a static
towards the remote Abilis (ip:61.61.61) through IP-2 resource.

[16:16:35] ABILIS_CPX_1:a ipr net:61.61.61.61/32 ip:3

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:d ipr

674
Draft CTI System Draft

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: or |IP: |AD:|
| | | | | | SRNET:/SRMASK: | IPLB: | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|*|C| | | 192.168.000.001/32 | 255.255.255.255 | |R-ID| 0|
|*|C| | | 080.080.080.080/32 | 255.255.255.255 | | 2| 0|
|*|C| | | 192.168.000.000/24 | 255.255.255.000 | | 1| 0|
|*|C| | | 192.168.001.000/24 | 255.255.255.000 | | 5| 0|
|*|C| | | 061.061.061.061/32 | 255.255.255.255 | | 3| 0|
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 2| 0|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

• ABILIS 3

Set up the IP address of the LAN of “Abilis 3”:

[16:16:35] ABILIS_CPX_3:s p ip-1 ipadd:192.168.2.1 mask:255.255.255.0 nat:inside descr:LAN_Site_3

COMMAND EXECUTED

Add the ADSL USB modem. The execution of this command creates the adsl-1 resource.

[16:16:35] ABILIS_CPX_3:a dev:adslusb-1

COMMAND EXECUTED

Add the ip resource ip-2 (subtype:ppp):

[16:16:35] ABILIS_CPX_3:a res:ip-2 subtype:dl

COMMAND EXECUTED

Associate the ip-2 resource to the lowres:adsl-1 and set up the IP address and the NAT type (outside):

[16:16:35] ABILIS_CPX_3:s p ip-2 lowres:adsl-1 ipadd:61.61.61.61 mask:255.255.255.248 nat:outside

COMMAND EXECUTED

Set up the encapsulation type (enc), the Virtual Path Identifier (VPI) and the Virtual Channel Identifier (VCI) of the
ADSL line:

[16:16:35] ABILIS_CPX_3:s p ip-2 enc:rfc1483-llcmux vpi:8 vci:35

COMMAND EXECUTED

Set up the speedlimit with a speed slightly lower than the upload speed of the ADSL line:

[16:16:35] ABILIS_CPX_3:s p ip-2 outspl:yes outsp:240

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_3:d p ip-2

RES:Ip-2 - Not Saved (SAVE CONF) ----------------------------------------------

- IP over Dedicated Line (DL) ------------------------------------------
DESCR:ADSL_line
OPSTATE:UP IPLOG:NO STATE-DETECT:NORMAL
LOWRES:Adsl-1
ENC:RFC1483-LLCMUX
IPADD:061.061.061.061 MASK:255.255.255.248 NEIGH:000.000.000.000
REDIS:YES HIDE:NO RP:NONE IPSEC:NO VRRP:NO
NAT:OUTSIDE UPNP:NO DIFFSERV:NO DDNS:NO
OUTBUF:100 OUTQUEUE:FAIR MTU:1500

675
Draft CTI System Draft

OUTSPL:YES OUTSP:240
INBUF:0 mru:1500 SRCV:NO
- TRFA section ---------------------------------------------------------
TRFA:NO
- Link -----------------------------------------------------------------
LLOG:DS LMPX:NO LCOMP:NO LCR:NO
LT1:1000 LT3:3000 LN2:3 LCRKEY:DFT
- ATM/ADSL -------------------------------------------------------------
VPI:8 VCI:35
RES:Adsl-1 - Not Saved (SAVE CONF) --------------------------------------------
------------------------------------------------------------------------
DESCR:
LOG:DS max-vc:1 aal5-max-payload:2100 aal5-payload-rxbuf:30
usb-rx-bufsize:1728 usb-rx-buf:3 usb-tx-bufsize:3200

Add a Packet Voice resource in Extended mode with ISDN backup:

[16:16:35] ABILIS_CPX_3:a res:pv-1 subtype:ip-bck

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:s p pv-1 mode:ext remport:3101 locipadd:61.61.61.61 remipadd:60.60.60.60 d

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:s p pv-1 brty:us bnrty:30 btb:10 sgi:abilis3-abilis1 sgo:abilis1-abilis3 c

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:d p pv-1

RES:Pv-1 - Not Saved (SAVE CONF) ----------------------------------------------

- PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) --------------
DESCR:To_Abilis_1
BCKRES:CtiSLink
- Link -----------------------------------------------------------------
LLOG:DS LMPX:YES LC:YES LCOMP:NO LCR:NO
LT1:3000 LT3:9000 LN2:3 LCRKEY:DFT
- IP Tunnel ------------------------------------------------------------
TLOG:NO MODE:EXT D-TOS:0-N V-TOS:0-D C-TOS:0-D
MPX:NO RS-BUF:10 D-TOUT:1000 V-TOUT:100 V-RED:NONE
PATH:SINGLE LOCPORT:3101 REMPORT:3101 CR:NO CRKEY:DFT
OUT-IP:AUTO
LOCIPADD:061.061.061.061 REMIPADD:060.060.060.060
- Back-Up --------------------------------------------------------------
BRTY:US BNRTY:30 BTB:10 BAC:DOD
DDT:220 VDT:10 UDT:NOMAX
CDI:* CDO:0212345679
CGI:* CGO:#
SDI:* SDO:#
SGI:ABILIS3-ABILIS1 SGO:ABILIS1-ABILIS3

Tip
Saving the configuration with save conf command, the validation procedure will automatically change the
parameter MPX (Multiplexing) from NO to YES.

Give the highest priority to the voice IP packets:

[16:16:35] ABILIS_CPX_3:s p iprtr acl:ext cos:enabled

COMMAND EXECUTED

676
Draft CTI System Draft

[16:16:35] ABILIS_CPX_3:a ipacl pr:0 type:permit ipcos:high tos-in:*-d prot:udp sa:* da:* sip:int

COMMAND EXECUTED

42.10.2.3. Configuration of CTI resources

• ABILIS 1

Add a cluster for compressed calls towards Site 3:

[16:16:35] ABILIS_CPX_1:a cticl id:Site_3 descr:Compressed_phones_towards_Site_3

COMMAND EXECUTED

Add a CTI Link and associate the Site_3 cluster to pv-1 resource:

[16:16:35] ABILIS_CPX_1:a ctil id:2 res:pv-1 clus:Site_3

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:d ctil

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 ip-5 Site_2 NOMAX NOMAX NONE
2 pv-1 Site_3 NOMAX NOMAX NONE

[16:16:35] ABILIS_CPX_1:d cticl

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Clusters:2

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
Site_2 Compressed_phones_towards_Site_2
[ 1] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------
Site_3 Compressed_phones_towards_Site_3
[ 2] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------

Tip
Remember to save the configuration with the save conf command.

Add To_Site_3 list containing numbers to route towards tunnel:

[16:16:35] ABILIS_CPX_1:list create To_site_3 in Numbers_to_Site_3

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_1:a list:To_Site_3 045566*

COMMAND EXECUTED

677
Draft CTI System Draft

Add a CTI routing (type:VtoC) for compressed calls directed to “Site 3”, with next parameter set to u (unlimited) to
route calls on ISDN lines in case if it is not possible to route them towards the Tunnel:

[16:16:35] ABILIS_CPX_1:a ctir pr:4 type:VtoC next:u poi:g1 ds:Site_3 cdi:'To_Site_3'

COMMAND EXECUTED

Here it is the result of the configuration:

[16:16:35] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 09:34:21 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 CtoV * G1 'Node' *
-------------------------------------------------------------------------------
3 VtoC G1 Site_2 'To_site_2' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
4 VtoC G1 Site_3 'To_site_3' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
5 TR G1 G2 * *
-------------------------------------------------------------------------------
6 TR G2 G1 * *
-------------------------------------------------------------------------------

• ABILIS 3

The configuration of CTI ports and CTI groups is identical to “Abilis 1”. For the remaining configuration it is only needed
to change the ISDN numbers.

Add To_Site_1 list containing numbers to route towards tunnel:

[16:16:35] ABILIS_CPX_3:list create To_Site_1 in Numbers_to_Site_1

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:a list:To_Site_1 0212345678

COMMAND EXECUTED

Add Node list containing numbers of local PBX:

[16:16:35] ABILIS_CPX_3:list create Node in Local_Numbers

COMMAND EXECUTED

678
Draft CTI System Draft

[16:16:35] ABILIS_CPX_3:a list:Node 045566*

COMMAND EXECUTED

Add a cluster for compressed calls towards “Site 1”:

[16:16:35] ABILIS_CPX_3:a cticl id:Site_1 descr:Compressed_phones_towards_Site_1

COMMAND EXECUTED

Add a CTI Link and associate the Site_1 cluster to pv-1 resource:

[16:16:35] ABILIS_CPX_3:a ctil id:1 res:pv-1 clus:Site_1

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:d ctil

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Links:1 Activated Links:8

ID: RES: CLUS: MAXBW: MAXCON: GROUP: (GROUP-MAXBW: GROUP-MAXCON:)

-------------------------------------------------------------------------------
1 pv-1 Site_1 NOMAX NOMAX NONE

[16:16:35] ABILIS_CPX_3:d cticl

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Clusters:1

---------+----------------------+---------+-----+-----------+------------------
CLUS: |[DESCR:]
[Int] |CG-IN-REWRITE: |RG-IN: |SS: |LCS-GROUP: |CLIP-RULE:
|NUM: |CPO:
|NUMx:
---------+----------------------+---------+-----+-----------+------------------
Site_1 Compressed_phones_towards_Site_1
[ 1] - DISABLE NO NONE PRIVATE
* NO
-------------------------------------------------------------------------------

Add the following routings:

[16:16:35] ABILIS_CPX_3:a ctir pr:1 type:data poo:g2 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:a ctir pr:2 type:CtoV sr:* poo:g1 cdi:'Node'

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:a ctir pr:3 type:VtoC next:u poi:g1 ds:Site_1 cdi:'To_Site_1'

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:a ctir pr:4 type:tr poi:g1 poo:g2 cdi:*

COMMAND EXECUTED

[16:16:35] ABILIS_CPX_3:a ctir pr:5 type:tr poi:g2 poo:g1 cdi:*

COMMAND EXECUTED

679
Draft CTI System Draft

[16:16:35] ABILIS_CPX_3:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 09:41:09 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 DATA CtiSLink G2 * *
-------------------------------------------------------------------------------
2 CtoV * G1 'Node' *
-------------------------------------------------------------------------------
3 VtoC G1 Site_1 'To_site_1' *
UNLIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
4 TR G1 G2 * *
-------------------------------------------------------------------------------
5 TR G2 G1 * *
-------------------------------------------------------------------------------

Tip
Remember to save the configuration with the save conf command.

42.11. Soft-PBX
This section describes the main features of the CTI resource which can be modified through the web interface or the CP.

42.11.1. Supplemetary services

Supplementary service is not active by default for BRI ports while it's active by default for POTS ports. They can be enabled
choosing the kind of interface (CTIP,CLUSTER,SIP or IAX).

When these services are activated:

• the call forwarding and the do-not-disturb (SS-CF-DND) features are active by default;

• the pickup is active only for calls of the belonging group (SS-PICKUP:GROUP).

Use the following command to activate supplementary services for the CTIP interface:

[11:59:03] ABILIS_CPX:s ctip:32 ss:yes

COMMAND EXECUTED

[12:00:08] ABILIS_CPX:d ctipe:32

CTIP:32 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:to_PBX
Run card:BRI4-1<2>
OPSTATE:UP LOG:NO side:NT line:PP TYPE:USER

680
Draft CTI System Draft

signalling:DSS1 TEI:STANDARD HOLD:NO CT:NO SS:YES

mode:Bri BUS:SHORT NUM:*
BCHANS:ALL-BID
X25:NO (XTEI:10) XK:7 XN200:3 xn201:260 XN202:3
XT200:1 XT202:2 XT203:10
Q931:YES (QTEI:0) QK:1 QN200:3 qn201:260 QN202:3 QT200:1
QT202:2 QT203:10 TDISC:90 QT301:180 QT302:15 QT303:4
QT304:30 QT305:30 QT308:4 QT310:30 QT313:6 QT316:15
DIALT:5 scrst:YES ORCD:0 ICT-T1:500 ICT-T2:500
SQNRTY1:15 SQDELAY1:30 SQDELAY2:5
LCS-GROUP:NONE BUSY-NOCHAN:NO OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:NO CLIP-RULE:PRIVATE
SS-CF-DND:YES

Type the command s user:test sip:yes sip-ss:yes to activate supplementary services for a sip user, or s user:test iax:yes iax-
ss:yes for a iax user.

The following command helps to verify the new parameters.

[16:05:48] ABILIS_CPX:d user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: alice
ALIAS: alice
ID: 5 <Read Only>
...
IAX-SS: YES
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
...
SIP-SS: YES
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
...
-------------------------------------------------------------------------------

Type the command s cticl clus:clus1 ss:yes to activate supplementary services for a cluster.

[16:06:32] ABILIS_CPX:d cticl

- Not Saved (SAVE CONF) -------------------------------------------------------

Configured Clusters:1

--------------+----------------------+------------------------+------------+---
CLUS: [Int]|[DESCR:]
|NUM: |CG-IN-REWRITE: |CLIP-RULE: |SS:
|NUMx:
--------------+----------------------+------------------------+------------+---
clus1 [ 1] * - PRIVATE YES

42.11.1.1. Pickup
1. Configuring pickup for POTS/BRI ports.

Pickup can be configured managing the SS-PICKUP parameter.

SS-PICKUP pickup permission [NO:pickup disabled, GROUP:pickup enabled only for call of the belonging group,
ANY:pickup enabled].

681
Draft CTI System Draft

Warning
Setting PICKUP parameter to YES for the group is required! Refer to Section 42.3, “CTI Ports Group”
to have more informations.

[12:42:02] ABILIS_CPX:s ctipe:101 ss-pickup:any

COMMAND EXECUTED

[12:42:19] ABILIS_CPX:d ctipe:101

CTIP:101 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:phone_1
Run card:POTS-1<1>
OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:18
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:ANY SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:YES

Remeber to save the configurations (save conf) and initialize the CTISYS resource (init res:ctisys).

2. Configuring pickup for SIP/IAX users.

SIP users are enabled only to pickup every call setting SIP-SS-PICKUP to ANY (SIP-SS-PICKUP:GROUP is not
permitted). Remeber to enable supplemetary services.

[12:34:49] ABILIS_CPX:s user:test sip-ss-pickup:any

COMMAND EXECUTED

[12:34:57] ABILIS_CPX:d user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: test
ALIAS: test
...
SIP-SS: YES
SIP-SS-PICKUP: ANY
...
-------------------------------------------------------------------------------

IAX users are enabled only to pickup every call setting IAX-SS-PICKUP to ANY (IAX-SS-PICKUP:GROUP is not
permitted). Remeber to enable supplemetary services.

[12:37:21] ABILIS_CPX:s user:iax_user iax-ss-pickup:any

COMMAND EXECUTED

[12:39:30] ABILIS_CPX:d user:iax_user

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: iax_user

682
Draft CTI System Draft

ALIAS: iax_user
...
IAX-SS: NO
IAX-SS-PICKUP: ANY
...
-------------------------------------------------------------------------------

Now configure CTI preferences or CTI advanced preferences for the user. This last configuration can be done using the
web interface.

42.11.1.2. Activating of call forward and DND

1. Activating DND for POTS/BRI ports.

CF and DND are enabled by default and managed through the SS-CF-DND parameter.

SS-CF-DND Call forwarding and Do-Not-Disturb [NO, YES]. The dafault value is YES.

The command below disables CF and DND.

[12:49:04] ABILIS_CPX:s ctip:101 ss-cf-dnd:no

COMMAND EXECUTED

[12:50:15] ABILIS_CPX:d ctipe:101

CTIP:101 - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

Act DESCR:phone_1
Run card:POTS-1<1>
OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:18
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:ANY SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:NO

The above example deactivate the CF and DND for cti port #101.

Remeber to save the configurations (save conf) and initialize the CTISYS resource (init res:ctisys).

2. Activating call forward and DND for SIP/IAX users.

Call forward and DND for SIP users can be configured using the following parameter:

SIP-SS-CF-DND Call forwarding and Do-Not-Disturb [NO, YES]. The dafault value is YES.

The command below disables CF and DND.

[14:43:29] ABILIS_CPX:s user:test sip-ss-cf-dnd:no

COMMAND EXECUTED

[14:44:32] ABILIS_CPX:d user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: test
ALIAS: test
...
SIP-SS: YES

683
Draft CTI System Draft

SIP-SS-PICKUP: ANY
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: NO

Remember to save the configuration.

Call forward and DND for IAX users can be configured using the following parameter:

IAX-SS-CF-DND Call forwarding and Do-Not-Disturb [NO, YES]. The dafault value is YES.

The command below disables CF and DND.

[14:47:44] ABILIS_CPX:s user:iax_user iax-ss-cf-dnd:no

COMMAND EXECUTED

[14:48:10] ABILIS_CPX:d user:iax_user

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: iax_user
ALIAS: iax_user
...
IAX-SS: NO
IAX-SS-PICKUP: ANY
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: NO

Remember to save the configuration.

42.11.1.2.1. Configuring DND

This feature can be configured using CTI preferences or CTI advanced preferences via web interface or via CP.

1. Configuring DND for a CTI port.

• Configuring DND using CP and CTI preferences.

Set the value of CTIP-ACTION parameter to DND in CTI preferences. Use the below command:

[14:21:51] ABILIS_CPX:s pref user:test ctip-action:dnd

COMMAND EXECUTED

[14:33:27] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 14:33:27 CET <Read Only>
PWD: ***
--------------------
CTIP-CLIP: SYS
CTIP-ACTION: DND
CTIP-CF-RULE: ALWAYS
CTIP-CF-TOUT: 15
CTIP-CF-DLY: 10
CTIP-CF-CDO: ux#
CTIP-CF-CGO: *

...

Remember to save the configuration.

684
Draft CTI System Draft

• Configuring DND using CP and CTI advanced preferences.

Verify that CTIP-ACTION si set to ADVANCED to use CTI advanced preferences.

Add a rule to cti advanced preferences for the specified user:

[14:59:38] ABILIS_CPX:a cf user:test pr:2 enabled:yes in-use:yes action:dnd

COMMAND EXECUTED

[15:02:13] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 15:02:13 CET)
------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES ANY ALL,00:00-23:59 CF
NO 4* * FORK
* 11 15 0
------------------------------------------------------------------------------
2 YES YES ANY ALL,00:00-23:59 DND
NO * * ALWAYS
------------------------------------------------------------------------------

Remember to save the configuration.

Rules are ordered using the PR parameter which can be used as reference to modify values:

s cf user:<username> parameter:<value>

Remember to save the configuration.

2. Configuring DND for SIP/IAX users.

• Configuring DND using CP and CTI preferences.

• Configuration for SIP users.

Configure the following parameter:

SIP-ACTION action [CF:call forward enabled, DND: DND enabled, ADVANCED: enables CTI advanced
preferences]. The default is ADVANCED.

[15:11:17] ABILIS_CPX:s pref user:test sip-action:dnd

COMMAND EXECUTED

[15:20:30] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 15:20:30 CET <Read Only>
PWD: ***
...
--------------------
SIP-CLIP: SYS
SIP-ACTION: DND
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 15

685
Draft CTI System Draft

SIP-CF-DLY: 0
SIP-CF-CDO: 12
SIP-CF-CGO: *
...

Remember to save the configuration.

• Configuration for IAX users.

Configure the following parameter:

IAX-ACTION action [CF:call forward enabled, DND: DND enabled, ADVANCED: enables CTI advanced
preferences]. The default is ADVANCED.

[15:20:35] ABILIS_CPX:s pref user:test iax-action:dnd

COMMAND EXECUTED

[15:21:39] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 15:21:39 CET <Read Only>
PWD: ***
...
--------------------
IAX-CLIP: SYS
IAX-ACTION: DND
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: ux#
IAX-CF-CGO: *
...

Remember to save the configuration.

• Configuring DND using CP and CTI advanced preferences.

• Configuration for SIP users.

Verify that SIP-ACTION si set to ADVANCED to use CTI advanced preferences.

[15:24:23] ABILIS_CPX:d pref user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 15:23:59 CET <Read Only>
PWD: ***
...
--------------------
SIP-CLIP: SYS
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 15
SIP-CF-DLY: 0
SIP-CF-CDO: 12
SIP-CF-CGO: *
...

686
Draft CTI System Draft

Add a rule to cti advanced preferences for the specified user:

[15:34:48] ABILIS_CPX:a cf user:test pr:2 enabled:yes in-use:yes if:sip action:dnd

COMMAND EXECUTED

[15:35:32] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 15:35:32 CET)
------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES ANY ALL,00:00-23:59 CF
NO 4* * FORK
* 11 15 0
------------------------------------------------------------------------------
2 YES YES SIP ALL,00:00-23:59 DND
NO * * ALWAYS
------------------------------------------------------------------------------

The above rule enables DND only for SIP interface (IF:SIP).

Rules are ordered using the PR parameter which can be used as reference to modify values:

s cf user:<username> parameter:<value>

Remember to save the configuration.

• Configuration for IAX users.

Verify that IAX-ACTION si set to ADVANCED to use CTI advanced preferences.

[15:24:23] ABILIS_CPX:d pref user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 15:23:59 CET <Read Only>
PWD: ***
...
--------------------
IAX-CLIP: SYS
IAX-ACTION: ADVANCED
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: ux#
IAX-CF-CGO: *
...

Add a rule to cti advanced preferences for the specified user:

[15:38:03] ABILIS_CPX:a cf user:test pr:1 enabled:yes in-use:yes if:iax action:dnd

COMMAND EXECUTED

[15:38:48] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 15:38:48 CET)

687
Draft CTI System Draft

------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES IAX ALL,00:00-23:59 DND
NO * * ALWAYS
------------------------------------------------------------------------------

The above rule enables DND only for IAX interface (IF:IAX).

Rules are ordered using the PR parameter which can be used as reference to modify values:

s cf user:<username> parameter:<value>

Remember to save the configuration.

42.11.1.2.2. Configuring CF

1. Configuring CF for CTIP ports.

• Configuring CF using CP and CTI preferences.

Configure the following parameters for the user who is associated to this ctip port.

CTIP-ACTION CTIP interface: action [CF: call forward enabled, DND:dnd enabled, ADVANCED:use cti
advanced preferences];

CTIP-CF-RULE rule for call forwarding [ALWAYS, BUSY, NOANS, OTHERS, FORK]. Values [BUSY, NOANS,
OTHERS, FORK] can be joined using ',' character.

CTIP-CF-TOUT Time-out for the 'NOANS' rule [5..180 sec.]

CTIP-CF-CDO output called number for call forwarding. From 1 up to 20 digits in the range ['0'..'9'] or "#"
optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.

CTIP-CF-CGO output calling number for call forwarding [*, USER].

Example:

[16:36:42] ABILIS_CPX:s pref user:test ctip-action:cf ctip-cf-rule:always ctip-cf-cdo:12

COMMAND EXECUTED

[16:38:54] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 16:38:54 CET <Read Only>
PWD: ***
--------------------
CTIP-CLIP: SYS
CTIP-ACTION: CF
CTIP-CF-RULE: ALWAYS
CTIP-CF-TOUT: 15
CTIP-CF-DLY: 10
CTIP-CF-CDO: 12
CTIP-CF-CGO: *
...

• Configuring CF using CP and CTI advanced preferences.

Verify that CTIP-ACTION si set to ADVANCED to use CTI advanced preferences.

688
Draft CTI System Draft

Add a rule to cti advanced preferences for the specified user:

[16:43:41] ABILIS_CPX:a cf user:test pr:1 enabled:yes in-use:yes if:ctip action:cf rule:always c

COMMAND EXECUTED

[16:46:07] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 16:46:07 CET)
------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES CTIP ALL,00:00-23:59 CF
NO * * ALWAYS
* 12 15 10
------------------------------------------------------------------------------

Remember to save the configuration.

The most important parameter are:

ADMIN Entry reserved to the Administrator [NO, YES].

ENABLED Enable/disable this entry [NO, YES].

IN-USE Activate/deactivate the rule [NO, YES].

IF Interface type [ANY, CTIP, CLUS, SIP, IAX].

ACTION Action [NONE, CF, DND]

RULE Rule for call forwarding [ALWAYS, BUSY, NOANS, OTHERS, FORK]. Values [BUSY, NOANS,
OTHERS, FORK] can be joined using ',' character.

CDO Outgoing Called Number. Max 20 characters in the range [0..9, *, #, 'macro'] optionally preceded by TON
[u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.

2. Configuring CF for SIP/IAX users.

• Configuring CF using CP and CTI preferences.

• Configuration for SIP users.

Configure at least the following parameters:

SIP-ACTION action [CF:call forward enabled, DND: DND enabled, ADVANCED: enables CTI advanced
preferences]. The default is ADVANCED.

SIP-CF-CDO output called number for call forwarding. From 1 up to 20 digits in the range ['0'..'9'] or "#"
optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.

[17:25:25] ABILIS_CPX:s pref user:test sip-action:cf sip-cf-cdo:12

COMMAND EXECUTED

[17:31:15] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 17:31:15 CET <Read Only>

689
Draft CTI System Draft

PWD: ***
...
--------------------
SIP-CLIP: SYS
SIP-ACTION: CF
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 15
SIP-CF-DLY: 0
SIP-CF-CDO: 12
SIP-CF-CGO: *
...

Remember to save the configuration.

Advanced configurations can be done using remaining parameters.

• Configuration for IAX users.

Configure at least the following parameters:

IAX-ACTION action [CF:call forward enabled, DND: DND enabled, ADVANCED: enables CTI advanced
preferences]. The default is ADVANCED.

IAX-CF-CDO output called number for call forwarding. From 1 up to 20 digits in the range ['0'..'9'] or "#"
optionally preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.

[17:32:17] ABILIS_CPX:s pref user:test iax-action:cf iax-cf-cdo:12

COMMAND EXECUTED

[17:36:22] ABILIS_CPX:d pref user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 17:36:22 CET <Read Only>
PWD: ***
...
--------------------
IAX-CLIP: SYS
IAX-ACTION: CF
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: 12
IAX-CF-CGO: *
...

Remember to save the configuration.

Advanced configurations can be done using remaining parameters.

• Configuring CF using CP and CTI advanced preferences.

• Configuration for SIP users.

Verify that SIP-ACTION si set to ADVANCED to use CTI advanced preferences.

[15:24:23] ABILIS_CPX:d pref user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>

690
Draft CTI System Draft

LAST-CHANGE: 02/02/2011 15:23:59 CET <Read Only>

PWD: ***
...
--------------------
SIP-CLIP: SYS
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 15
SIP-CF-DLY: 0
SIP-CF-CDO: 12
SIP-CF-CGO: *
...

Add a rule to cti advanced preferences for the specified user:

[17:43:37] ABILIS_CPX:a cf user:test pr:1 enabled:yes in-use:yes if:sip cdo:12 action:cf rule:

COMMAND EXECUTED

[17:44:23] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 17:44:23 CET)
------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES SIP ALL,00:00-23:59 CF
NO * * ALWAYS
* 12 15 10
------------------------------------------------------------------------------

Rules are ordered using the PR parameter which can be used as reference to modify values:

s cf user:<username> parameter:<value>

Remember to save the configuration.

• Configuration for IAX users.

Verify that IAX-ACTION si set to ADVANCED to use CTI advanced preferences.

[15:24:23] ABILIS_CPX:d pref user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 02/02/2011 15:23:59 CET <Read Only>
PWD: ***
...
--------------------
IAX-CLIP: SYS
IAX-ACTION: ADVANCED
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: ux#
IAX-CF-CGO: *
...

Add a rule to cti advanced preferences for the specified user:

[17:46:59] ABILIS_CPX:a cf user:test pr:1 enabled:yes in-use:yes if:iax cdo:12 action:cf rule:

691
Draft CTI System Draft

COMMAND EXECUTED

[17:47:07] ABILIS_CPX:d cf user:test

- Not Saved (SAVE CONF) -------------------------------------------------------

USER:test (Last change: 02/02/2011 17:47:07 CET)
------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES IAX ALL,00:00-23:59 CF
NO * * ALWAYS
* 12 15 10
------------------------------------------------------------------------------

Rules are ordered using the PR parameter which can be used as reference to modify values:

s cf user:<username> parameter:<value>

Remember to save the configuration.

42.11.2. User call logs and mails

The information presented are now exactly as seen by the user terminal, POTS, ISDN, SIP, IAX, CLUS, and can be used by
the user to create the advanced call forwarding rules. After logging in the web interface, click Users Administration then click
CTI call logs.

Please refer to Section 43.2.3.2, “CTI preferences” section to learn how to activate/deactivate logs and mails.

Figure 42.2. Web interface

A web page showing a table displays a list of all users with links to their own incoming and outgoing calls logs.

692
Draft CTI System Draft

Figure 42.3. Users incoming/outgoing logs page

Clicking Incoming calls log for user 08888888888, you can obtain all logs for incoming calls to the user selected. Click
Extended to have more details on the incoming calls.

Figure 42.4. Incoming call logs

Each forwarder can receive his own mails and have his own call logs. In the following example there are three sip users: test,
test2and test3. Below there's a table showing users and their own sip numbers:

Table 42.4. xxx

User Sip number

test 10
test2 11
test3 12

The user test make a call to user test2 dialling 11, but the user test 2 forwards every call to user test3 (see the image below).
The user test3 is offline.

693
Draft CTI System Draft

Figure 42.5. User test2 preferences

The following screenshots show the logs for users test,test2 (forwarder who receives his own logs) and test3.

Figure 42.6. user test outgoing log

Figure 42.7. user test2 incoming log

Figure 42.8. user test2 outgoing log (forwarded call)

694
Draft CTI System Draft

Figure 42.9. user test3 incoming log

Besides, other features included are:

• manual transfers are logged too

• OPC transfers also generate a call forward mail with rule=OPC.

42.11.3. User preferences

Abilis can manage heterogeneous multicast group of phones (fork). User logged in can change only his own preferences
clicking the link User Preferences on the Home page. Administrator can change every user's preferences using the link
Users administration on the Home page.

Figure 42.10. User preferences

42.11.3.1. Call Forward

After opening the Users CTI Preferences page, select CF/CF-ALWAYS/CF-FORK (call forward) for an interface.

If CF is selected, choose the rule to use (CF on Busy, No answer with relative delay, Others or always) and insert the number
to call inside Forward Called textbox. Refer to the above figure to view the User Preferences page.

Tip
Refer to Section 43.2.3.4, “CTI preferences administration through CP” to know how to configure Users
preferences using CP.

42.11.3.2. Fork
After opening the Users CTI Preferences page, select CF-FOK (call forward) for an interface. Type the delay for the fork rule
in the textbox and the number to call in the textbox Forward Called.

In the example shown in the above figure, forking is enabled for user test2 and for sip interface. Forking delay is 10 seconds
and the called number is 12. When a sip call is received from user test2, the call is forked to number 12 after 10 seconds.

Tip
Remeber to configure CTIR rule to route forked calls. For example a rule is needed to fork a call from a sip
phone to pots phone.

695
Draft CTI System Draft

FORK rule consists in leaving own phone to ring and simultaneously make an outgoing call, for example to own mobile. The
first that answers will take the call. Besides ticking the checkboxes Busy and Others with more phones “forking” to the “next
one” Abilis can manage groups of different kind of phones.

This new release includes some changes in the list of KEY codes for Supplementary Services: the old code *57 now becomes
*54. From 7.0.0 version of Abilis firmware, the *57 code is used to enable FORK using as calling number the own one. The
*58 code is used to enable FORK using as calling number the one of the incoming call. Type the command help ss keycodes
to show all available keycodes.

Tip
Refer to Section 43.2.3.4, “CTI preferences administration through CP” to know how to configure Users
preferences using CP.

42.11.3.3. DND
After opening the Users CTI Preferences page, select DND (Do Not Disturb) for an interface in the Action row. Refer to the
above figure to view the User Preferences page.

Tip
Refer to Section 43.2.3.4, “CTI preferences administration through CP” to know how to configure Users
preferences using CP.

42.11.4. Administrative pages

Administrative pages allows to configure Abilis. Log into the web interface as administrator and click CTI Administration to
access the CTI routings page.

On the next page click CTI routings.

Figure 42.11. Cti administration page

In the CTI routings view/change page, the administrator can add/delete/move cti routing rules through the icons or buttons
shown below:

• delete icon used to cancel a cti routing rule

696
Draft CTI System Draft

Figure 42.12. delete icon

• move icon used to move a cti routing rule

Figure 42.13. move icon

• insert icon used to insert a cti routing rule

Figure 42.14. insert icon

• add button used to add cti routing rule

Figure 42.15. add button

Please refer to chapter CTI Router to learn the meaning of various parameters. Administrator can make some fields editable
by users ticking the checkbox near the name of the considered parameter (image below).

Figure 42.16. CTI routing addition page

697
Draft CTI System Draft

Administrator can make a list editable by users in the List administration page (Image below). Tick the checkbox to enable
the Set and Reset buttons.

Figure 42.17. Editable list

Press the Set button to let a user to modify the list created.

42.11.5. Advanced user activities

The page Advanced user activities allows the users to modify lists and portion of routing rules enabled by the administrator.

The page is located in /sys/advuser/ path so a proper http rights configuration is needed.

[11:27:01] ABILIS_CPX:a http rights path:/sys/advuser/ user:test

COMMAND EXECUTED

[11:27:09] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /sys/advuser/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

Don't forget to use init res:http to initialize the http resource and save conf to save the configuration.

Click Advanced user activities in the CPX home page then click CTI Routings view/change to access a page where users can
modify portion of routings enabled to be modified or click List view/change to access a page where the user can modify lists.

Figure 42.18. Advanced users activities page

698
Draft CTI System Draft

In the following page there is a table with a list of rules which can be edited by the user. The choice can be done among the
rules enabled by the administrator.

Figure 42.19. CTI routings view

Clicking the link corresponding to the PR parameter of a rule, a user can modify only the parameters enabled by
administrator, in the example below only ACT, TYPE and DESCR parameters.

Figure 42.20. CTI routings view

Click List view/change to view a table containing the lists which can be edited. Only the lists enabled by administrator can be
modified by a user.

Figure 42.21. List view

Click the name of a list to change its parameters.

699
Draft CTI System Draft

Figure 42.22. Change list parameters

42.12. FAX Relay with Abilis

This section briefly describes fax relay method and the conditions required to offer a reliable fax relay service.

42.12.1. Fax over packet networks

Group 3 faxes communicates using a standardised analogue telephone channel which transports frequencies in range
300-3100 Hz with small distortion. This actually means that the fax machines send the data related to scanned image using
modems, more precisely V.26, V.27, V.29 modems.

There are two basic ways to transport fax over packet networks:

• fax bypass:

the fax signal is treated as a normal phone call. The voice compressors like G.723.1, G.729, GSM, etc ... are not able to
transport fax signals since fax signals tolerate a much smaller distortion than voice. At the time of writing only G.726 and
G.727 at 40 kbit/sec are able to pass faxes acceptably. Of course G.711 and fully TRANSPARENT coders, which both
requires 64 kbit/sec, transport fax signal without any additional distortion.

• fax relay:

the fax signal is demodulated locally and converted into data packets which are sent to remote site for re-modulation.
This process requires much less bandwidth on the packet network than fax bypass: the demodulation extracts the original
data bits, which can be at one of the bit rates available in group 3 faxes, i.e. 9.6, 7.2, 4.8, 2.4, and only this information is
transported over the packet network. Recently group 3 faxes have been extended with a 14.4 kbit/sec bit rates using V.34
modulation scheme. Abilis CPX supports also this method.

42.12.2. Fax Relay

Fax relay is a method which:

• demodulates fax signals locally;

• converts demodulated fax signals into data packets;

• have the following feature: fax data packets are transported to remote side;

• have the following feature: remote side converts data packets into fax data and remodulates them locally.

In this process there are four points where problems can arise:

• errors on analogue channel (modulation/demodulation);

• packet loss and late packets;

• excess delays;

700
Draft CTI System Draft

• incompatibilities between fax machines, and between fax machines and the Abilis CPX fax relay engine.

42.12.2.1. Errors on analogue channel

This may occur because:

• The CTI SYSTEM clock between Abilis CPX and the Fax machine (or PABX if it is in the middle) is not synchronised.
This is actually the usual problem of ISDN/TDM synchronisation issues between devices, while tolerable with voice calls
become critical with fax/data connections.

• The level of the analogue signals is not adequate. It's very rare to have the need to change default level, which is of #9
dbm.However Abilis CPX allows to change it via FM-LEVEL: parameter in CTISYS and FMLEVEL parameter in CTIR.

42.12.2.2. Packet loss and late packets

Fax relay and fax bypass are similar to voice, they require real time treatment. The only difference is that they can tolerate a
little bit higher round-trip delay.

The literature widely available on Internet explains very well the challenges of transporting real time data over packet
networks. This is not the place where we will explain them deeply, but we want to summarise few key points:

• Packet networks work with message store-and-forward paradigm, therefore hops and queues introduce variable delays in
packet delivery. This effect is called jitter.

• Although coders, silence suppression, and other techniques, may make the packet exchange discontinued, voice and faxes
produces and uses data at constant bit rate, based on a clock available at A/D and D/A converters.

• Each application has its own tolerable delays which poses constrains to buffers dimensioning.

• Buffering, also known as jitter-compensation, has to be dimensioned as a trade-off to cover all the above points and
provide the desired, or acceptable, quality of the service.

Packet loss and late packets are far the most critical problem, which may have several causes:

• network packet loss;

• buffer overflows;

• buffer underflows;

• insufficient jitter compensation.

42.12.2.3. Excess delay

The round-trip delay of land line telephone networks is usually of some millisecond, maximal some tenth.

The round-trip delay of satellite telephone networks is at least 500 msec.

The fax protocol tolerates delays which are between 1 to 3 seconds, therefore if the network offers a round-trip delay above 1
second ... problems “may” arise.

42.12.2.4. Incompatibilities
Fax bypass does not make any inspection of the fax signal and therefore compatibility is not an issue.

Fax relay has to demodulate the signal locally and make some other “inspection”, so fax machine and the Abilis fax relay
engine may not understand each other correctly.

42.12.3. Abilis configurations for best results

42.12.3.1. Jitter compensation
The default fax relay jitter compensation parameters are usually adequate, i.e. FM-DFT-JBUF:200 and FM-MAX-
JBUF:400.

Both Abilis at the two sides of fax relay connection must have these values set. Each Abilis CPX can jitter compensate the
packets it RECEIVES. These parameters affects only the CPX where they are set, for the receive direction.

701
Draft CTI System Draft

They can be increased if the network shows a higher jitter, but there is a risk to fall in the excessive delay problem explained
above.

42.12.3.2. Fax speed

Although faxes should work at all standard speeds of 9.6, 7.2, 4.8, 2.4, and in some cases also 14.4 and 12 kbit/sec, our
experiences shows that speeds below 9.6 are badly supported.

For higher reliability, at least speed of 9.6 must be allowed by configuring SP:9600 in CTIR. Since we want to use only 6.4k
for voice, a routing which intercepts numbers assigned to faxes and uses SP:9600 is required.

42.12.3.3. ECM
The ECM negotiation is disabled. This reduces incompatibilities problems and make lower failure chances in presence of
packet loss.

42.12.3.4. Clock sync

The clock synchronisation between devices interconnected by ISDN/TDM interfaces, i.e. cpx-pabx, pabx-isdnfax is still
mandatory, but the synchronisation of the clocks of the fax-relay endpoints is no more required if FM-DFT-JBUF:200 and
FM-MAX-JBUF:400 are correctly used.

It means that Abilis in “Site A” and Abilis in “Site B” which relay faxes each other through Internet, may run different ISDN/
TDM clocks without having negative effects to faxes. It means that either or both sides may miss interconnection to ISDN
network!

On the other hand synchronisation to a unique clock is always preferred when possible. With unique synchronisation the
voice can be handled without buffer underrun/overrun also if silence suppression is disabled. Silence suppression is the only
way to avoid that sooner or later one direction will persistently work at overrun condition (with high delay!) and the other at
underrun condition (jitter compensation absent).

42.12.3.5. Fm-relay parameter

The fm-relay parameter in the CTISYS resource enables/disbales the fax/data relay as default value for all ports. If FM-
RELAY parameter is set to YES, the DSPs is enabled to recognize a fax handshaking tone. If this tone is generated by a fax
near a phone and during a voice call, the fax handshaking tone reaches the microphone and it's recognized by the DSP. The
result is that the local user (near the fax) hears only silence and the remote user hears the fax tone synchronization.

To avoid this:

• set to NO the FM-RELAY parameter in the CTISYS resource

• set to yes the FMRLY parameter in the fax cti routing rule to enable fax/data relay only for that routing

Refer to chapter How to configure fax modem relay parameter to view an example of configuration.

42.12.3.6. V-RED parameter

The V-RED parameter of a packet voice resource allows to activate/deactivate redundancy for Voice and/or Modem/Fax
packets over clusters. Since fax relay is very sensitive to packet loss this feature is very useful to increase the fax relay
reliability on connections with packet loss.

If the previous parameters have been set correctly and several issues with fax are still present, administrator can try to set the
V-RED parameter to FM (Fax Modem) for best results. V-RED must be set to FM on both local and remote Abilis.

42.12.4. Diagnostics and statistics

The statistics of PV and IP tunnels (AIPT) can be used to measure packet loss and to have an idea on jitter values.
Remember that faxes are very sensible to packet loss.

The statistics to check carefully are MISSING and time arrival variation of voice frames. MISSING should not increase, and
time arrival variation should not increase for values above 200 msec. If those two statistics increase ... fix the network (or
network connections).

The statistics an diagnostics of Audio Compressors (CTIAC) provide many useful information. Jitter measures, available
when an Audio Compressor is IN-USE, may be useful to troubleshoot fax connections.

702
Draft CTI System Draft

An example of AC extended diagnostics is:

[16:16:35] ABILIS_CPX:d de ctiac:0

-------------------------------------------------------------------------------
AC Card DSP/C Bus/TS DSPState ACState ModeIn ModeOut Coder Ctip/BC
Dtmf DhVol DlVol FmLevel InGain OutGain SigGain MaxFaxSp MaxModSp
SC V-DJ V-MJ V-CurJ V-TopJ V-AvgJ EC BypassCoder
ECM FM-DJ FM-MJ FM-CurJ FM-TopJ FM-AvgJ FaxTxPg FaxFlowState
-------------------------------------------------------------------------------
0 QPRI-1 0/0 4/05 RUN IN-USE FAX - Spirit/6.4k -
OUTBAND -4 -4 -9 0 0 0 9600 7200
YES 100 250 0 0 0 NO -
YES 200 400 0 216 22 0 Tx-DIS

where:

• ECM: Error Correction Mode, fax.

• V-DJ: Voice Negotiated Default Jitter Buffer.

• V-MJ: Voice Negotiated Maximal Jitter Buffer.

• V-CurJ: Voice Current Jitter Buffer.

• V-TopJ: Voice Top Reached Jitter Buffer.

• V-AvgJ: Voice Average Reached Jitter Buffer.

• EC: Echo Canceler.

• FM-DJ: FAX/MODEM Default Jitter Buffer.

• FM-MJ: FAX/MODEM Negotiated Maximal Jitter Buffer.

• V-CurJ: FAX/MODEM Current Jitter Buffer.

• FM-TopJ: FAX/MODEM Top Reached Jitter Buffer.

• V-AvgJ: FAX/MODEM Average Reached Jitter Buffer.

• FaxTxPg: Tax Transmitted Pages.

• FaxFlowState: Fax Flow Current State.

42.12.5. Conclusion
For a successful fax relay here is a check list:

• Use FM-DFT-JBUT:200 and FM-MAX-JBUF:400.

• Use CTI routings with SP:9600 or higher.

• Use network connection with very low packet loss.

• Use network connection with round-trip delay not higher than 1 second.

Abilis FM-DFT-JBUF and FM-MAX-JBUF may be increased a little bit in presence of network connections with bigger
jitter, but reasonably to value not greater than 400 and 600 respectively. Clock synchronisation between the Abilis CPX at the
two endpoints of the fax relay connection is not required.

703
Draft Draft

Chapter 43. The web interface

Luigi Demuro

Table of Contents
43.1. The web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
43.2. Section 1 - User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.2. Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
43.2.3. User preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
43.2.4. Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
43.2.5. CTI incoming/outgoing calls log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
43.2.6. Advanced user activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
43.3. Section 2 - Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.1. IP Traffic Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
43.3.2. Operator Panel Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
43.3.3. SMS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
43.3.4. Control Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
43.4. Section 3 - Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.1. Configuration information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
43.4.2. Users administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
43.4.3. Groups administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
43.4.4. Lists administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
43.4.5. Disa administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
43.4.6. CTI administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
43.4.7. Voice Mail administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

43.1. The web interface

The Home page shows different services divided into three sections:

• section 1 - User, every link (but Advanced user activities) is always reachable by a user logged in

• User preferences

• Address books

• CTI incoming calls log

• CTI outgoing calls log

• Advanced user activities

• section 2 - Applications, reachable by a user logged in and enjoining the right HTTP privileges

• IP traffic analyzer

• Operator Control Panel

• SMS gateway

• Control Port

• section 3 - Administration, reachable by a user logged in and enjoyining the right HTTP privileges

• Configuration Information

• Users administration

• Groups administration

704
Draft The web interface Draft

• Lists administration

• DISA administration

• CTI administration

• Voice Mail administration

Figure 43.1. Abilis CPX Home page

The following default virtual path correspond to link Advanced user activities of section 1:

• /sys/advuser/ : Advanced user activities

The following default virtual paths correspond to links of section 2:

• /sys/trfa/ : Ip traffic analyzer;

• /sys/opc/ : Operator Panel Control;

705
Draft The web interface Draft

• /sys/sms/: SMS gateway;

• /sys/cp/ : Control Port;

The following default virtual paths correspond to links of section 3:

• /sys/admin/ (with recur:no): Configuration information

• /sys/admin/users/: Users administration

• /sys/admin/groups/: Groups administration

• /sys/admin/lists/: Lists administration

• /sys/admin/disa/: DISA administration;

• /sys/admin/ (with recur:yes):every link of section 3 (useful to give quickly all administration privileges).

The access to specific services (IP traffic analyzer, PBX extension states, Control Port, User preferences, Users
administration, DISA administration) is allowed only for enabled users (users with appropiate rights must be created).

Warning
Cookies must be enabled.

Warning
Abilis SNTP server must be active and properly configured (it is possible to set an expiration date for the
cookie, parameter: LOGIN-COOKIE-TOUT).

43.2. Section 1 - User

43.2.1. Creation of the user
Creating an user and enable it to HTTP service to access Abilis CPX Web Interface. Add the user httpuser with password
httpuser.

[22:50:09] ABILIS_CPX:a user:httpuser pwd:httpuser http:yes

COMMAND EXECUTED

[22:50:09] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
httpuser *** YES # # NO NO YES NO NO NO

Tip
Interesting chapter: Section 5.9, “Users Table”.

43.2.2. Login
Go to Abilis' home page and click login, insert User name and Password and press Send button.

706
Draft The web interface Draft

The following page will be shown if user name and password are right.

Click Site start-page or CPX home to view the home page.

43.2.3. User preferences

The User preferences link allows to modify the profile of the user who is logged in.

43.2.3.1. Change password

Go to Abilis' Home Page, login and select the User preferences link.

The next page shows the list of editable parameters.

Clicking Change password you will be moved to the following page: insert the old and the new password and then press the
Submit button to validate the operation.

707
Draft The web interface Draft

The operation will be validated in this page:

43.2.3.2. CTI preferences

The CTI preferences page is divided in three sections.

Section 1 Interface - it's the particular interface for the considered user. [CTIP, CLUS, IAX, SIP].

Clip - it allows to choose if the CLIP of the user who transfers calls must be displayed or not. [SYS:the
configuration depends on that of the port (example: the CLIP-RULE parameter fo CTISIP resource),
RESTRICTED: CLIP not displayed, ALLOWED: CLIP displayed].

Action - it allows to chose the behaviour of the interface.

• ADVANCED: it allows to use an advanced configuration (refer to Section 43.2.3.3, “CTI advanced
preferences”) where a user can choose the CF on NOANSWER, on BUSY, on OTHER reasons, the
weekday and time where the rule is valid, the calling and the called number for which the call is valid, and
so on;

• DND: it's the Do Not Disturb service;

• CF: it allows to transfer a call choosing the cause (ALWAYS, BUSY, NO-ASNWER). The textbox near
no-aswer checkbox shows the number of seconds aftwer which the call is transferred;

• CF-ALWAYS: tha call is always trasferred;

• CF-FORK: it allows to enable forking. Refer to chapter Section 42.11.3, “User preferences” to learn more
about it.

Voice-Mail - it activates/deactivates the voice mail [NO, YES].

Forward Called - it show the number to which the call is forwarderd.

Forward Calling - it allows to configure the output calling number [*, USER].

Section 2 This section contains the parameters to configure e-mail notifications.

Event - choosing of the event [VOICE MAIL, CALL FAILURE, CALL FORWARD, SEIZED CALL].

Enabled - e-mail notification enabled/disabled.

Recipient List - IN2T list used to select recipients for email on call forward on the base of called numbers.

Default Recipient - default recipient(s) for email notifications.

Outgoing message - ougoing message set for the voice mail.

End message - end message set for the voice mail.

Section 3 Calls log - it enables/disables the calls log.

Number of calls - calls number to keep in the log file.

Call&Ring (POTS only) - it allows to configure Call&Ring settings. Configure the Interval to set the timeout
[SYS, 30..600 sec] and the maximal number of retry [SYS, 1..30].

TON to PREFIX - it allows to convert TON to the corresponding PREFIX in notification mails, call logs,
operator panel control (OPC) [SYS, NO, YES].

708
Draft The web interface Draft

Tip
Configure the sending email address setting the MAIL-FROM parameter in the CTISYS resource (s p ctisys
mail-from:[email protected]).

Figure 43.2. CTI preferences page

43.2.3.3. CTI advanced preferences

Click CTI advanced preferences to view a list of rules created for the user logged in.

Click add to create a rule:

709
Draft The web interface Draft

In the example above, DND is active for a call incoming from number 10 on Saturday and Sunday.

Tip
Interesting chapter: Section 43.4.2.4, “Example - How to change advanced settings for a sip user”.

43.2.3.4. CTI preferences administration through CP

CTI prefereces are administrable both via web interface or via CP. The best choice is to use the web interface, but if you have
to manage Abilis remotely via Telnet or SSH you need to know how to use the CP.

Use the following commands to administrate user CTI preferences:

• d pref user[:<user>]: this command shows user preferences

• d pref ctip[:<ctip>]: This command shows CTIP preferences when it is not assigned to a user, a limit set of preferences is
available.

• s pref user:<user> <par:><val> [<par:><val>] ...:This command sets one or more user preference.

• s pref ctip:<ctip> <par:><val> [<par:><val>] ...: This command sets one or more preference for an unassigned CTIP.

Example:

[12:54:23] ABILIS_CPX:d pref user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test
ID: 4 <Read Only>
LAST-CHANGE: 29/04/2011 16:01:55 CET <Read Only>
PWD: ***
--------------------
CTIP-CLIP: SYS
CTIP-ACTION: ADVANCED
CTIP-CF-RULE: ALWAYS
CTIP-CF-TOUT: 15
CTIP-CF-DLY: 10
CTIP-CF-CDO: ux#
CTIP-CF-CGO: *
CTIP-VM: NO

710
Draft The web interface Draft

CTIP-VM-RULE: NOANS,OTHERS
CTIP-VM-TOUT: 15
--------------------
CLUS-CLIP: SYS
CLUS-ACTION: ADVANCED
CLUS-CF-RULE: ALWAYS
CLUS-CF-TOUT: 15
CLUS-CF-DLY: 10
CLUS-CF-CDO: ux#
CLUS-CF-CGO: *
CLUS-VM: NO
CLUS-VM-RULE: NOANS,OTHERS
CLUS-VM-TOUT: 15
--------------------
IAX-CLIP: SYS
IAX-ACTION: ADVANCED
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: ux#
IAX-CF-CGO: *
IAX-VM: NO
IAX-VM-RULE: NOANS,OTHERS
IAX-VM-TOUT: 15
--------------------
SIP-CLIP: SYS
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 15
SIP-CF-DLY: 0
SIP-CF-CDO: 12
SIP-CF-CGO: *
SIP-VM: NO
SIP-VM-RULE: NOANS,OTHERS
SIP-VM-TOUT: 15
--------------------
VM-RCPT-LIST: #
VM-RCPT:
VM-OGM-MSG: SYS
VM-END-MSG: SYS
--------------------
MAIL-FAIL: NO
MAIL-FAIL-RCPT-LIST: #
MAIL-FAIL-RCPT:
MAIL-FWD: NO
MAIL-FWD-RCPT-LIST: #
MAIL-FWD-RCPT:
SEIZED-CALLS: NO
--------------------
CTI-CALLS-LOG: YES
CTI-CALLS-LOG-IN: 30
CTI-CALLS-LOG-OUT: 30
--------------------
CALLTRY-TOUT: SYS
CALLTRY-NRTY: SYS
--------------------
TON-TO-PREFIX: SYS
-------------------------------------------------------------------------------

The following command shows the meaning of parameters:

[13:15:25] ABILIS_CPX:d pref user:test ?

711
Draft The web interface Draft

D PREF USER:val Display Users preferences table's entries

USER:name User name. Max. 32 ASCII characters.

USER:A All entries of the Users preferences table
USER:ALL All entries of the Users preferences table

User's preferences:

ID: Internal user identifier [1..251] <Read Only>

LAST-CHANGE: Last time at witch the entry has been updated <Read Only>
PWD: User password. From 0 up to 32 ASCII printable characters.
Spaces are not allowed. Case is preserved.
CTIP-CLIP: CTIP interface: Caller Identification Presentation [RESTRICTED,
ALLOWED, SYS]
CTIP-ACTION: CTIP interface: action [ADVANCED, DND, CF, CF-ALWAYS, CF-FORK]
CTIP-CF-RULE: CTIP interface, call forward: rule [ALWAYS, BUSY, NOANS, OTHERS,
FORK]. Values [BUSY, NOANS, OTHERS, FORK] can be joined using
',' character.
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
CTIP-CF-TOUT: CTIP interface, call forward: Time-out for the 'NOANS' rule
[5..180 sec.]
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
CTIP-CF-DLY: CTIP interface, call forward: Delay for the 'FORK' rule
[0..180 sec.]
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS'>
CTIP-CF-CDO: CTIP interface, call forward: output called number. From 1 up to
20 digits in the range ['0'..'9'] or "#" optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CTIP-CF-CGO: CTIP interface, call forward: output calling number [*, USER]
CTIP-VM: CTIP interface: voice mail activation/deactivation [NO, YES]
CTIP-VM-RULE: CTIP interface, voice mail: rule [ALWAYS, BUSY, NOANS, OTHERS].
Values [BUSY, NOANS, OTHERS] can be joined using ',' character.
CTIP-VM-TOUT: CTIP interface, voice mail: Time-out for the 'NOANS' rule
[5..180 sec.]
CLUS-CLIP: CLUS interface: Caller Identification Presentation [RESTRICTED,
ALLOWED, SYS]
CLUS-ACTION: CLUS interface: action [ADVANCED, DND, CF, CF-ALWAYS, CF-FORK]
CLUS-CF-RULE: CLUS interface, call forward: rule [ALWAYS, BUSY, NOANS, OTHERS,
FORK]. Values [BUSY, NOANS, OTHERS, FORK] can be joined using
',' character.
<Read Only for CLUS-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
CLUS-CF-TOUT: CLUS interface, call forward: Time-out for the 'NOANS' rule
[5..180 sec.]
<Read Only for CLUS-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
CLUS-CF-DLY: CLUS interface, call forward: Delay for the 'FORK' rule
[0..180 sec.]
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS'>
CLUS-CF-CDO: CLUS interface, call forward: output called number. From 1 up to
20 digits in the range ['0'..'9'] or "#" optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CLUS-CF-CGO: CLUS interface, call forward: output calling number [*, USER]
CLUS-VM: CLUS interface: voice mail activation/deactivation [NO, YES]
CLUS-VM-RULE: CLUS interface, voice mail: rule [ALWAYS, BUSY, NOANS, OTHERS].
Values [BUSY, NOANS, OTHERS] can be joined using ',' character.
CLUS-VM-TOUT: CLUS interface, voice mail: Time-out for the 'NOANS' rule
[5..180 sec.]
IAX-CLIP: IAX interface: Caller Identification Presentation [RESTRICTED,
ALLOWED, SYS]

712
Draft The web interface Draft

IAX-ACTION: IAX interface: action [ADVANCED, DND, CF, CF-ALWAYS, CF-FORK]

IAX-CF-RULE: IAX interface, call forward: rule [ALWAYS, BUSY, NOANS, OTHERS,
FORK]. Values [BUSY, NOANS, OTHERS, FORK] can be joined using
',' character.
<Read Only for IAX-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
IAX-CF-TOUT: IAX interface, call forward: Time-out for the 'NOANS' rule
[5..180 sec.]
<Read Only for IAX-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
IAX-CF-DLY: IAX interface, call forward: Delay for the 'FORK' rule
[0..180 sec.]
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS'>
IAX-CF-CDO: IAX interface, call forward: output called number. From 1 up to
20 digits in the range ['0'..'9'] or "#" optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
IAX-CF-CGO: IAX interface, call forward: output calling number [*, USER]
IAX-VM: IAX interface: voice mail activation/deactivation [NO, YES]
IAX-VM-RULE: IAX interface, voice mail: rule [ALWAYS, BUSY, NOANS, OTHERS].
Values [BUSY, NOANS, OTHERS] can be joined using ',' character.
IAX-VM-TOUT: IAX interface, voice mail: Time-out for the 'NOANS' rule
[5..180 sec.]
SIP-CLIP: SIP interface: Caller Identification Presentation [RESTRICTED,
ALLOWED, SYS]
SIP-ACTION: SIP interface: action [ADVANCED, DND, CF, CF-ALWAYS, CF-FORK]
SIP-CF-RULE: SIP interface, call forward: rule [ALWAYS, BUSY, NOANS, OTHERS,
FORK]. Values [BUSY, NOANS, OTHERS, FORK] can be joined using
',' character.
<Read Only for SIP-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
SIP-CF-TOUT: SIP interface, call forward: Time-out for the 'NOANS' rule
[5..180 sec.]
<Read Only for SIP-ACTION equal to 'CF-ALWAYS' or 'CF-FORK'>
SIP-CF-DLY: SIP interface, call forward: Delay for the 'FORK' rule
[0..180 sec.]
<Read Only for CTIP-ACTION equal to 'CF-ALWAYS'>
SIP-CF-CDO: SIP interface, call forward: output called number. From 1 up to
20 digits in the range ['0'..'9'] or "#" optionally preceded by
TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes.
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
SIP-CF-CGO: SIP interface, call forward: output calling number [*, USER]
SIP-VM: SIP interface: voice mail activation/deactivation [NO, YES]
SIP-VM-RULE: SIP interface, voice mail: rule [ALWAYS, BUSY, NOANS, OTHERS].
Values [BUSY, NOANS, OTHERS] can be joined using ',' character.
SIP-VM-TOUT: SIP interface, voice mail: Time-out for the 'NOANS' rule
[5..180 sec.]
VM-RCPT-LIST: IN2T list used to select Voice Mail recipient(s) on the base
of called numbers [#, ListName]
VM-RCPT: Defult Voice Mail recipient(s).
From 0 up to 128 ASCII printable characters. Spaces are not
allowed. Case is preserved.
VM-OGM-MSG: Name of the file holding the Outgoing Message.
"SYS" or from 1 up to 20 characters. Names holding spaces must be
written between quotation marks (E.g.: "My message").
VM-END-MSG: Name of the file holding the End Message.
"SYS" or from 1 up to 20 characters. Names holding spaces must be
written between quotation marks (E.g.: "My message").
MAIL-FAIL: Enable/disable email notification when a call directed to the user
fails [NO, YES]
MAIL-FAIL-RCPT-LIST: IN2T list used to select recipients for e-mail on call
failure on the base of called numbers [#, ListName]
MAIL-FAIL-RCPT: Defult recipient(s) for email on call failure.

713
Draft The web interface Draft

From 0 up to 128 ASCII printable characters. Spaces are not

allowed. Case is preserved.
MAIL-FWD: Enable/disable email notification when a call directed to the user
is forwarded [NO, YES]
MAIL-FWD-RCPT-LIST: IN2T list used to select recipients for email on call
forward on the base of called numbers [#, ListName]
MAIL-FWD-RCPT: Default recipient(s) for email on call forward.
From 0 up to 128 ASCII printable characters. Spaces are not
allowed. Case is preserved.
SEIZED-CALLS: Enable/disable email notification when a call directed to
the user is seized [NO, YES]
CTI-CALLS-LOG: Enable/disable CTI calls logging [NO, YES]
CTI-CALLS-LOG-IN: Number of calls to be logged in incoming calls log file
[10..200] <Only when CTI-CALLS-LOG: not equal to YES>
CTI-CALLS-LOG-OUT: Number of calls to be logged in outgoing calls log file
[10..200] <Only when CTI-CALLS-LOG: not equal to YES>
CALLTRY-TOUT: Timeout [SYS, 30..600 sec]
CALLTRY-NRTY: Number of retry [SYS, 1..30]
TON-TO-PREFIX: Convert TON to the corresponding PREFIX in notification mails,
call logs, operator panel control (OPC) [SYS, NO, YES]

43.2.3.5. CTI advanced preferences administration through CP

The following are the commands to administrate CTI advanced preferences:

• d cf user[:<user>]: This command shows user preferences.

• s cf user:<user> <par:><val> [<par:><val>] ...: This command sets one or more user preference.

[12:58:21] ABILIS_CPX:d cf user:test

USER:test (Last change: 02/02/2011 11:44:10 CET)

------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES ANY ALL,00:00-23:59 CF
NO 4* * FORK
* 11 15 0
------------------------------------------------------------------------------

The following command shows the meaning of parameters:

[13:16:10] ABILIS_CPX:d cf user:test ?

D CF USER:A Display all CF/DND entries defined for Users

D CF USER:ALL Display all CF/DND entries defined for Users
D CF USER:name PR:A Display all CF/DND entries of the specified user
D CF USER:name PR:ALL Display all CF/DND entries of the specified user
D CF USER:name PR:val Display selected CF/DND entry of the specified user

USER: User name. Max. 32 ASCII characters.

PR: CF/DND entry priority [1..500]

CF/DND (Call forwarding/Do-Not-Disturb) entry parameter(s):

ADMIN: Entry reserved to the Administrator [NO, YES]

ENABLED: Enable/disable this entry [NO, YES]
IN-USE: Activate/deactivate the rule [NO, YES]
IF: Interface type [ANY, CTIP, CLUS, SIP, IAX]
TI: Time interval during which the rule has to be applied in the format
is "day,hh:mm-hh:mm", where 'day' can be: a single day [MO, TU,
WE, TH, FR, SA, SU] or a set of days (E.g.: MO+TH or TU+TH+SU etc.)

714
Draft The web interface Draft

or an interval.(E.g.: MO-WE or TH-SU etc. or ALL).

ACTION: Action [NONE, DND, CF, VM]
CGI: Incoming Calling Number. Max 20 characters in the range [0..9, *, #,
?, 'list'] optionally preceded by TON [u, i, n, o, s, h, c] and/or
NP [x, e, d, t, l, p] and/or PI [a, r, m, q] and/or SI [y, v, w, z,
j] attributes.
(e.g.: 123, 123*, 12?, 12?*, *, #, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CDI: Incoming Called Number. Max 20 characters in the range [0..9, *, #,
?, 'list'] optionally preceded by TON [u, i, n, o, s, h, c] and/or
NP [x, e, d, t, l, p] attributes.
(e.g.: 123, 123*, 12?, 12?*, *, #, 'listname', 123'listname')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
RULE: Rule for call forwarding [ALWAYS, BUSY, NOANS, OTHERS, FORK].
Values [BUSY, NOANS, OTHERS, FORK] can be joined using ','
character.
TOUT: Time-out for the 'NOANS' rule [5..180 sec.]
DLY: Delay for the 'FORK' rule [0..180 sec.]
CGO: Outgoing Calling Number. "USER" or max 20 characters in the range
[0..9, *, #, 'macro'] optionally preceded by TON [u, i, n, o, s, h,
c] and/or NP [x, e, d, t, l, p] and/or PI [a, r, m, q] and/or SI [y,
v, w, z] attributes.
(e.g.: USER, ie123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.
CDO: Outgoing Called Number. Max 20 characters in the range [0..9, *, #,
'macro'] optionally preceded by TON [u, i, n, o, s, h, c] and/or NP
[x, e, d, t, l, p] attributes.
(e.g.: ne123, *, #, 123'cdi', 'cdi'123'cgi.s5', 'sdi')
See HELP ISDN ATTRIBUTES for details on attributes.
See HELP ISDN VALUES for details on meaning of special values.

43.2.4. Address Book

The address book is useful to associate names and numbers through a private and a public section. It can be used for the
following purposes:

• allow POTS phones to call a number present in the address book;

• convert numbers to names in the notifications emails and user logs.

Address book administration is available from the HTTP interface and even from CP (through commands a/d/s/c contact).

43.2.4.1. Address book web interface.

Click Address book and the following page will be shown.

Figure 43.3. Address Book interface

On the top left corner of the page there are two arrows which allow to browse the address book pages back and forward.

In the next section of the page there are various icons:

• Abort icon

715
Draft The web interface Draft

Figure 43.4. Abort icon

• Transfer a call icon

Figure 43.5. Transfer call icon

• Export icon

Figure 43.6. Export icon

Contacts can be exported imported using csv files:

Figure 43.7. Import export page

• Add a contact icon

Figure 43.8. Add contact icon

To add a contact click the add a contact icon

and follow these steps:

• choose the type of contact (PRIVATE or PUBLIC)

• fill the name field (from 1 up to 32 extended characters. Case is preserved)

• fill the outdial field (Up to 8 digits. OutDial + Number cannot exceed 20 digits)

• fill the number field (from 1 up to 20 digits.outdial + number cannot exceed 20 digits).

• click submit to save the contact

716
Draft The web interface Draft

Figure 43.9. Address book: add a contact

Click the arrow on the top left of the page and go back to the first page of the address book web interface. Searching contacts
can be done filling the text box. Javascripts permits a search-as-you-type operation.

Click the search button or use special character thicking the checkbox advanced search.

Contacts can be sorted by name or number (Sort by listbox); the user can choose: to show only private/public contacts (show
contacts listbox), the number of contacts per page (contacts per page listbox), the number of columns per page (Columns per
page listbox).

The table on the center of the address book page shows the search results.

Figure 43.10. Address book:search results

Click the radiobutton sms to compose an sms to the correspondig user, filling number and message fields.

Figure 43.11. Address book: sending an sms

Click click&call or call&ring radiobutton to use these features.

Tip
Interesting chapter: Section 53.19, “How to configure CTISMS to send sms via emails”.

43.2.5. CTI incoming/outgoing calls log

Click incoming calls log to display the log of all calls of the logged in user (Refer to paragraph User preferences to know how
to enalbe/disable incoming/outgoing calls log):

Figure 43.12. Incoming calls log

717
Draft The web interface Draft

Click Outgoing calls log to view the log about outgoing calls. Clicking a number, a user can do the following actions directly
from log page:

• click to call;

• abort a call;

• call try;

• add new address book entry.

Warning
CTI call logs are now available only for SOFT-PBX licence.

Tip
Interesting chapters:

Section 43.2.3.2, “CTI preferences”;

Chapter 6, Licencing.

43.2.6. Advanced user activities

It allows the user to edit CTI Routings and lists enabled by the administrator.

Use the following commands to give the correct rights to access this page.

[11:28:19] ABILIS_CPX:a http rights path:/sys/advuser/ user:httpuser

COMMAND EXECUTED

[11:28:46] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL

718
Draft The web interface Draft

-------------------------------------------------------------------------------

The following page will be shown if no routing or list is enabled by administrator, otherwise a list of editable routings/lists
will appear (see the paragraph CTI administration):

43.3. Section 2 - Applications

43.3.1. IP Traffic Analyzer
Giving appropriate rights to the user is needed to access this page, so use the following commands:

[11:28:50] ABILIS_CPX:a http rights path:/sys/trfa/ user:httpuser

COMMAND EXECUTED

[11:40:04] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

719
Draft The web interface Draft

7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Login and click IP traffic analyzer to access the following page:

Refer to paragraph Using HTTP for showing TRFA statistics to learn how to use this feature.

Refer to chapter TRFA - traffic analyzer to have more informations about the resource.

43.3.2. Operator Panel Control

It shows the status of each interfaces associated to each user.

By default, the anonymous access in this section is disabled; add the path in the HTTP Virtual Paths Access Rights Table for
httpuser.

[11:56:28] ABILIS_CPX:a http rights path:/sys/opc/ user:httpuser

COMMAND EXECUTED

[22:51:00] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

Go to Abilis' Home Page, login and select the Operator Panel Control link.

The next page shows the interface status of the each user enabled to OPC.

Please, refer to chapter OPC- Operator Panel Control to know more about OPC's features.

720
Draft The web interface Draft

43.3.3. SMS Gateway

Activate CTISMS resource, then give the user appropriate access rights.

[11:50:17] ABILIS_CPX:a http rights path:/sys/sms/ user:httpuser

COMMAND EXECUTED

[11:50:40] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
8 /sys/sms/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Click SMS Gateway to jump to the following page:

There are various ways to send sms using the links on the bottom of page:

• uploading a csv file;

• composing a sms using the browser;

721
Draft The web interface Draft

Click Uploaded files to view the list of file already uploaded:

43.3.4. Control Port

The Control Port page shows the main informations about the system (diagnostics, statistics, …) and its configurations
(general informations, …).

By default, the anonymous access in this section is disabled; add the path in the HTTP Virtual Paths Access Rights Table for
httpuser.

[12:35:48] ABILIS_CPX:a http rights path:/sys/cp/ user:httpuser

COMMAND EXECUTED

[22:53:51] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /sys/cp/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

Go to Abilis Home page, login and select the Control Port link.

722
Draft The web interface Draft

The table of active devices can be shown clicking Hw devices configuration.

43.4. Section 3 - Administration

43.4.1. Configuration information
In this page an user with administration rights can store memos about the running configuration.

This link belongs to administration section, so a user must have the proper rights to access this page.

Warning
The page is in the /sys/admin/ path so the RECUR parameter must be set to NO, otherwise the user gains
access to all administration links.

[14:08:22] ABILIS_CPX:a http rights path:/sys/admin/ user:httpuser recur:no

COMMAND EXECUTED

[14:08:32] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-----------------------------------------------------Configu--------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
9 /sys/admin/
httpuser r--- l--- NO PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/

723
Draft The web interface Draft

httpuser r--- l--- YES PLAIN,SSL

-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
8 /sys/sms/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

The following is the Configuration information page:

43.4.2. Users administration

The User administration service allows to modify the profiles and the configurations of the PPP, FTP, HTTP, MAIL, IAX
and SIP users.

Caution
Generally the access to this section is reserved to users with administrator's rights.

The anonymous access is disabled by default; add the path in the HTTP Virtual Paths Access Rights Table for httpuser.

[14:08:39] ABILIS_CPX:a http rights path:/sys/admin/users/ user:httpuser

COMMAND EXECUTED

[14:16:06] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
9 /sys/admin/
httpuser r--- l--- NO PLAIN,SSL
-------------------------------------------------------------------------------
10 /sys/admin/users/
httpuser r--- l--- YES PLAIN,SSL

724
Draft The web interface Draft

-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
8 /sys/sms/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Go to Abilis Home page, login and select the Users administration link.

Users can be created, removed or modified (this operations are similar to typing d/a/c/s user command on the control port);
Saving the configuration can be done pressing the Save configuration button.

Tip
Refer to Section 5.9, “Users Table” to know how to administrate users through CP.

43.4.2.1. Example of user creation

Let's see how to create a new IAX user.

In the previous page click on Add new user link: this page will be shown.

725
Draft The web interface Draft

Insert the username and the password and click on Add button. The operation will be validated in this page:

Then click on User Administration to come back to the starting page of the session.

Click on View/Change user: this page will be shown.

Select from the list the user that you want to modify (iaxuser in this case): the following page will be shown.

Select the protocol/s that you want to enable (in this case select IAX) and click on Submit button. The operation will be
validated in this page.

726
Draft The web interface Draft

Click on User Administration to come back in the starting page of the session.

Click on IAX (in the Advanced user settings section): this page will be shown.

Select from the list the user to modify (iaxuser in this case): this page will be shown.

Set the field and click on the Submit button. The operation will be validated in this page.

Click on User Administration to come back to starting page of the session.

727
Draft The web interface Draft

Click on Save configuration button to save the changes.

Click on Yes button to confirm.

Tip
Refer to Section 5.9, “Users Table” to know how to administrate users through CP.

43.4.2.2. Example of user deletion

Let's see how to delete an user.

Click Remove user on the User administration page.

Click the user to delete and then click the YES button.

728
Draft The web interface Draft

Click OK to return to Remove users page.

Tip
Remember to save the configuration to make the change permanent.

Tip
Refer to Section 5.9, “Users Table” to know how to administrate users through CP.

43.4.2.3. Example of user change

Click View/Change user on the User administration page. A list with all users is shown:

Click the user to change, for example httpuser:

Change parameters and click Submit button, click ok on the following page:

729
Draft The web interface Draft

Tip
Remember to save the configuration to make the change permanent.

Tip
Refer to Section 5.9, “Users Table” to know how to administrate users through CP.

43.4.2.4. Example - How to change advanced settings for a sip user

Click SIP on User administration page, a list of sip users is shown.

Click the user to modify:

Change user's parameters and then click submit button. Click OK button on the confirmation page:

Tip
Remember to save the configuration to make the change permanent.

43.4.2.5. Example - How to change assigned numbers

Click CTI assigned numbers on the Users administration page. A list of users with their assigned numbers is shown:

Click the user to modify, change the assigned number and then click Set button:

730
Draft The web interface Draft

The following page confirms the change. Click OK button.

Tip
Remember to save the configuration to make the change permanent.

43.4.3. Groups administration

This page allows to add/remove/change a group or to change a group preferences.

Click Group administration on the CPX home page.

43.4.3.1. Example of group creation

Click Add new group, insert the name and click Add button.

The following page confirms the change. Click OK button.

731
Draft The web interface Draft

The new group is shown in the list of groups.

Tip
Remember to save the configuration to make the change permanent.

43.4.3.2. Example of group deletion

Click Remove group, a list of existing groups is shown.

Click tho group to delete and then click YES button.

Click OK button on the confirmation page.

The group is deleted.

732
Draft The web interface Draft

Tip
Remember to save the configuration to make the change permanent.

43.4.3.3. Viewing/changing a group

Click View/Change group on the Group administration page. A list of existing group is shown.

Click the group to change, add a description, add users and click Submit button

Click OK button on confirmation page.

Click Back button on the following page.

733
Draft The web interface Draft

The user has been added to the group.

43.4.3.4. Changing CTI advanced preferences

Click CTI advanced preferences on Group administration page. A list of existing groups is shown.

Click the group and click Add button.

Enable DND for calls incoming on CTIP interface, calling every number starting with 012345, only on Saturday. Then, click
the Submit button on the bottom of page.

Click OK button on the following page.

734
Draft The web interface Draft

The rule for the group has been added.

43.4.4. Lists administration

The List administration service allows to modify add/remove/modify lists.

Caution
Generally the access to this section is reserved to users with administrator's rights.

By default, the anonymous access is disabled; add the path in the HTTP Virtual Paths Access Rights Table for httpuser.

[09:24:07] ABILIS_CPX:a http rights path:/sys/admin/lists/ user:httpuser

COMMAND EXECUTED

[09:24:32] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /sys/admin/lists/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/cp/
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

Go to Abilis Home page, login and select the Lists administration link.

On the next page the user can create, remove or modify a list (this operations are similar to typing d/a/c/s list command on
the control port); save the configuration pressing the Save configuration button.

735
Draft The web interface Draft

Tip
Interesting chapter: Section 5.11, “Lists management”.

43.4.4.1. Example of list creation

Let's see how to create a new list of numbers.

In the previous page click on Add new list link: this page will be shown.

Insert the list name, description and select the type. Then click Add button. The operation will be validated in this page:

Tip
Interesting chapter: Section 5.11, “Lists management”.

43.4.4.2. Example of list deletion

Let's see how to delete a list of numbers.

In the previous page click on Remove existing list link: this page will be shown.

Click the list to delete, then click YES button on the following page:

736
Draft The web interface Draft

Click OK button on the confirmation page:

Tip
Interesting chapter: Section 5.11, “Lists management”.

43.4.4.3. Viewing/changing a list

Let's see how to modify a list of numbers.

In the previous page click on View/Change list link: this page will be shown.

Click the list to change. The following page allows to edit the name and the description of the list, to insert items. Click Add
button to insert an item:

Click OK button on the confirmation page:

737
Draft The web interface Draft

Tip
Interesting chapter: Section 5.11, “Lists management”.

43.4.5. Disa administration

This section allows to add/remove/change services and users, to display diagnostics and to manage messages sets.

Caution
Generally the access to this section is reserved to users with administrator's rights.

By default, the anonymous access is disabled; add the path in the HTTP Virtual Paths Access Rights Table for httpuser.

[10:49:09] ABILIS_CPX:a http rights path:/sys/admin/disa/ user:httpuser

COMMAND EXECUTED

[10:49:14] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
9 /sys/admin/
httpuser r--- l--- NO PLAIN,SSL
-------------------------------------------------------------------------------
11 /sys/admin/disa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/admin/lists/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
10 /sys/admin/users/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

738
Draft The web interface Draft

2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
8 /sys/sms/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Click Login on the CPX home page and insert login and password. Click the DISA administration link to access to the
following page.

Tip
Interesting chapter: Chapter 47, DISA - Direct Inward System Access.

43.4.5.1. Example of service creation

Click Add new service, insert the name and click Add button.

The following page confirms the change. Click DISA administration button.

Tip
Remember to save the configuration to make the change permanent.

739
Draft The web interface Draft

Tip
Interesting chapter: Section 47.3.1, “CTIDISA Service table”.

43.4.5.2. Example of service deletion

Click Remove service, a list of existing service is shown.

Click tho service to delete and then click YES button.

This is the confirmation page:

Tip
Remember to save the configuration to make the change permanent.

Tip
Interesting chapter: Section 47.3.1, “CTIDISA Service table”.

43.4.5.3. Viewing/changing a service

Click View/Change service on the DISA administration page. A list of existing service is shown.

740
Draft The web interface Draft

Click the service to change. Set new parameters and click Submit button.

Click OK button on confirmation page.

Click Back button on the following page.

Tip
Interesting chapter: Section 47.3.1, “CTIDISA Service table”.

43.4.5.4. Example of user creation

Click Add new user on the DISA administration page. On the following page insert the user name and click Add button.

741
Draft The web interface Draft

Click DISA administration link on the confirmation page.

Tip
Remember to save the configuration.

Tip
Interesting chapter: Section 47.3.2, “CTIDISA User table”.

43.4.5.5. Example of user deletion

Click Remove user on the DISA administration page. The following page shows the list of existing users. Click the user to
remove.

Click YES Button to confirm the deletion.

Click DISA administration link on the confirmation page.

742
Draft The web interface Draft

Tip
Remember to save the configuration.

Tip
Interesting chapter: Section 47.3.2, “CTIDISA User table”.

43.4.5.6. View/change users

Click View/Change user on the DISA administration page. The following page shows the list of existing users. Click the
user to change.

Set parameters as needed and click Submit button.

Click OK button on the following page.

Tip
Remember to save the configuration.

Tip
Interesting chapter: Section 47.3.2, “CTIDISA User table”.

43.4.5.7. Managing messages sets

This page allows to Extract/Rebuild/Update messages sets used by CTIDISA resource.

Click Message set(s) View/Change to view the list of existing messages sets.

743
Draft The web interface Draft

Tip
Interesting chapter: Section 47.8, “Message files”.

43.4.6. CTI administration

This page allows to administer numbers, CTI preferences and CTI routings.

Caution
Generally the access to this section is reserved to users with administrator's rights.

By default, the anonymous access is disabled; add the path in the HTTP Virtual Paths Access Rights Table for httpuser.

[13:26:27] ABILIS_CPX:a http rights path:/sys/admin/cti/ user:httpuser

COMMAND EXECUTED

[13:27:28] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
9 /sys/admin/
httpuser r--- l--- NO PLAIN,SSL
-------------------------------------------------------------------------------
12 /sys/admin/cti/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
11 /sys/admin/disa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
6 /sys/admin/lists/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
10 /sys/admin/users/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
5 /sys/advuser/
httpuser r--- l--- YES PLAIN,SSL

744
Draft The web interface Draft

-------------------------------------------------------------------------------
4 /sys/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
test r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
8 /sys/sms/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
7 /sys/trfa/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

Go to Abilis Home page, login and click CTI administration to access to the following page.

Tip
Interesting chapter: Chapter 42, CTI System.

43.4.6.1. CTIP assigned numbers administration

This page allows to change numbers assigned to a CTIP interface.

Click CTIP assigned numbers to view a list of the CTIP interfaces.

Click an interface to change, set the new number and click Set button.

745
Draft The web interface Draft

Then click OK button on the following page.

Click Back button on the following page.

Tip
Interesting chapter: Section 42.2, “CTI Ports configuration”.

43.4.7. Voice Mail administration

This section allows to view/change system/users' messages.

Caution
Generally the access to this section is reserved to users with administrator's rights.

By default, the anonymous access is disabled; add the path in the HTTP Virtual Paths Access Rights Table for httpuser.

[11:26:29] ABILIS_CPX:a http rights path:/sys/admin/vm/ user:httpuser

COMMAND EXECUTED

[11:27:04] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:

746
Draft The web interface Draft

-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
...
-------------------------------------------------------------------------------
12 /sys/admin/vm/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
...

Click Login on the CPX home page and insert login and password. Click the Voice Mail administration link to access to the
following page.

Figure 43.13. Voice Mail administration page

Click System Message set(s) View/Change to view/change the system message sets. The following page allows to modify
end/ogm message sets.

Figure 43.14. Voice Mail - System message sets

747
Draft The web interface Draft

• Extract - It allows to convert CPM files into Wav files. Files can be downloaded using the command file get.

• Rebuild - It allows to rebuild [751] the message set.

• Update - it allows to update the message set.

Click User's Message set(s) View/Change to view/change the user's message sets. Each user can customize his own
messages, so the folowing page shows all user's message sets. Extract/Rebuild/Update are available for User's Message set(s).

Tip
Interesting chapter: Section 48.2, “CTIVM - CTI Voice Mail”.

43.4.7.1. Voice Mail administration through web interface

Click User's Message set(s) View/Change,insert the message set name in the textbox and click Add button.

The following page confirms the change. Click Ok button.

748
Draft The web interface Draft

The list of message sets is updated:

Click the message set name to update. The list will show OGM (Out Going Message) and END (End message) folders.

Click the message set to configure (in this case OGM), select the file to use and click Upload button.

Tip
Message files must be recorded on a PC and saved in WAV format with CCITT A-law (or u-law) 8KHz, 8
bit, Mono (Windows sound recorder supports it).

749
Draft The web interface Draft

Click Ok button on the confirmation page.

The message has been uploaded. Click Rebuild to convert the file from wav to CPM format.

750
Draft The web interface Draft

Click Yes on the confirmation page.

Click Ok button when the conversion is accomplished.

751
Draft The web interface Draft

The CPM file is now present. Click the Select button to use it and Ok on the confirmation page. The selected message is now
the default one for user test-set (VM-OGM-MSG parameter in the CTI preferences).

Note
The user must exists otherwise the following message is shown.

752
Draft The web interface Draft

43.4.7.2. Voice Mail administration through CP

Create the message set:

[12:48:29] ABILIS_CPX:msg add vm user test-set

VM USER MESSAGE SET 'test2' ADDED.

Note
The dir c:\app\vm\users\ is created.

[12:36:39] ABILIS_CPX:sys dir c:\app\vm\users

Directory listing of c:\app\vm\users

. <DIR> 21/04/2011 12:15:18

.. <DIR> 21/04/2011 12:15:18
test-set <DIR> 06/05/2011 12:36:16

Found 3 directories, 0 files.

Total 124 MiB, Used 84 MiB, Free 39 MiB.

Upload a wav file in the right directory under the created one, using the file put command.

[12:45:10] ABILIS_CPX:file put z c:\app\vm\users\test-set\ogm\message1.wav

READY TO RECEIVE FILE...

Upload Zmodem
message1.wav

FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

FILE TRANSFER SUCCESSFULLY COMPLETED

RECEIVED FILE 'c:\app\vm\users\test-set\ogm\message1.wav' FORMAT IS UNKNOWN.

NO CHECK DONE.

Rebuild the message set:

[12:47:25] ABILIS_CPX:msg rebuild vm user test-set

YOU ASKED TO REBUILD VM USER 'test-set'

PROCEED (N/Y)?y

MSG REBUILD IN PROGRESS ON VM

THIS MAY TAKE FEW MINUTES (Type CTRL+C + ENTER to stop)...

Converting C:\APP\VM\USERS\test-set\OGM\message1.wav
Converting to G711A/64k .......... END
Converting to G723.1/5.3k .......... END
Converting to G723.1/6.3k .......... END
Converting to G729A/8k .......... END

753
Draft The web interface Draft

Converting to Spirit/6.4k .......... END

Converting to Spirit/7.2k .......... END
Converting to Spirit/8.0k .......... END
Converting to Spirit/8.8k .......... END
Converting to Spirit/9.6k .......... END

COMMAND COMPLETED

Refer to Section 48.2.5.2, “Working dir structure” to know more about the VM working dir structure.

commands to manage audio

Tip
Interesting chapters:

Section 48.2, “CTIVM - CTI Voice Mail”;

Section 48.2.4, “CTIVM configuration through CP”.

754
Draft Draft

Chapter 44. OPC - Operator Panel

Control
Luigi Demuro

Table of Contents
44.1. OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.1. Activating the OPC resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
44.1.2. OPC resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
44.2. OPC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.2.1. Creation of the user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
44.3. OPC Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
44.3.1. The panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
44.3.2. The table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
44.3.3. Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
44.3.4. Special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

44.1. OPC resource

The OPC service (Operator's Panel Control) shows the CTI ports' status and the information about the current telephone calls.
The OPC allows authorized users to initiate and transfer calls simply using the mouse.

In order to run the OPC, both the HTTP and OPC resources must be active.

Tip
Interesting chapter: Chapter 34, HTTP - HyperText Transfer Protocol.

44.1.1. Activating the OPC resource

Add the resource to the Abilis system with the following command:

[16:27:36] ABILIS_CPX:a res:opc

COMMAND EXECUTED

The OPC resource may already exist in the system, but may not yet be active: set it active with the following command.

[16:27:41] ABILIS_CPX:s p opc act:yes

COMMAND EXECUTED

The OPC resource may collect call information from the local as well as from remote Abilis. The operator can view the
call status of several sites in the same web page. The parameter abilisid of the OPC resource has the purpose to permit the
programmer to choose which is the wished ABILIS target.

[16:38:12] ABILIS_CPX:s p opc abilisid:myabilis

COMMAND EXECUTED

The new abilisid is available in runtime for both local and remote.

Tip
Refer to Section 44.1.2, “OPC resource parameters” to have more informations about collecting information
from a remote Abilis. A how to is available directly at this link.

755
Draft OPC - Operator Panel Control Draft

44.1.2. OPC resource parameters

The following command shows the current values of the OPC parameters (use d p opc ? fo a short online help).

[16:48:43] ABILIS_CPX:d p opc

RES:Opc -----------------------------------------------------------------------
DESCR:Operator_Panel_Collector
LOG:NO ACT:YES XML-TOUT:60 XML-MIN-DELAY:500
maxusers:200 maxcalls:200 maxclients:20 maxremotes:5
ABILISID:myabilis
- OPC Remote collectors ------------------------------------------------
REM:0 ABILISID: ENABLED:NO
SRCADD:R-ID (192.168.030.001) TOS:0-N
SERVER:
PROT:PLAIN PORT:AUTO RETRY-DELAY:60
LOGIN:
PASSWORD:
-----------------------------------------------------------------
REM:1 ABILISID:test ENABLED:NO
SRCADD:R-ID (192.168.030.001) TOS:0-N
SERVER:192.168.001.150
PROT:PLAIN PORT:AUTO RETRY-DELAY:60
LOGIN:admin
PASSWORD:********
-----------------------------------------------------------------
REM:2 ABILISID: ENABLED:NO
SRCADD:R-ID (192.168.030.001) TOS:0-N
SERVER:
PROT:PLAIN PORT:AUTO RETRY-DELAY:60
LOGIN:
PASSWORD:
-----------------------------------------------------------------
REM:3 ABILISID: ENABLED:NO
SRCADD:R-ID (192.168.030.001) TOS:0-N
SERVER:
PROT:PLAIN PORT:AUTO RETRY-DELAY:60
LOGIN:
PASSWORD:
-----------------------------------------------------------------
REM:4 ABILISID: ENABLED:NO
SRCADD:R-ID (192.168.030.001) TOS:0-N
SERVER:
PROT:PLAIN PORT:AUTO RETRY-DELAY:60
LOGIN:
PASSWORD:
-----------------------------------------------------------------

Meaning of the most important parameters:

DESCR resource description [max 80 alphanumeric characters, not including <space>]LOG

LOG set to NO if events are not to be recorded into the Abilis LOG files, otherwhise: D: Debug Log; S: System
Log; A: Alarm view; L: Local audible alarm; T:SNMP traps; +E: Extended Log of state changes (see LOG
parameter1 for more details)

ACT [YES/NO] to set the OPC active/inactive during runtime (init res:OPC to commit the change)

maxusers Max. number of users to be stored in the OPC table.

maxcalls Max. number of users to be stored in the OPC table.

maxclients Max. number of monitors that can require information from OPC.

maxremotes Max. number of external remote collector that can be stored locally.

756
Draft OPC - Operator Panel Control Draft

ABILISID identifier used when exporting information outside local collector.

REM remote collector index [0..(maxremotes: - 1)].

ENABLED enable/disable connection to the server [NO, YES].

SRCADD source IP address for outgoing connections.

SERVER ip address of the remote abilis.

LOGIN login used to authenticate to the remote Abilis.

PASSWORD password used to authenticate to the remote Abilis.

The syntax for setting the OPC parameters is the usual one: s p opc parameter:value

Caution
As usual, changes on parameters whose name is displayed in UPPERCASE can be committed with the
command init res:opc, whilst changes on parameters written in LOWERCASE require a new system's
startup (SAVE CONF and WARM START).

Tip
Refer to chapter Section 53.11, “How to configure opc to collect call information from a remote abilis” to
configure opc to collect call information from a remote abilis.

44.2. OPC configuration

The OPC service uses HTTP resource, so Control Panel users must be enabled to use HTTP. Their HTTP-RIGHTS have to
grant access to the /sys/opc/ data directory.

Tip
Refer to Section 43.1, “The web interface” to have more information about http directories.

44.2.1. Creation of the user

Users can access to HTTP server only if they are enabled to HTTP service (parameter HTTP set to YES). To verify the
current users' rights:

[16:50:05] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO

As shown above, only the admin user is enabled to HTTP service. The following command creates a new user called “opc1”
and enabled for the HTTP service.

[17:22:50] ABILIS_CPX:a user:opc1 http:yes

COMMAND EXECUTED

[17:23:12] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin NO # # YES YES YES NO NO NO

757
Draft OPC - Operator Panel Control Draft

guest NO # # NO NO NO NO NO NO
opc1 YES # # NO NO YES NO NO NO

Tip
Interesting chapter: Section 5.9, “Users Table”.

The appropriate http-rights must be assigned so that user opc1 is allowed to access this path:

[18:01:03] ABILIS_CPX:a http rights path:/sys/opc/ user:opc1

COMMAND EXECUTED

[18:03:45] ABILIS_CPX:d http rights

- Not Saved (SAVE CONF) -------------------------------------------------------

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/opc/
opc1 r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------

Additional specifications for the OPC users are: OPC USER-PORTS CORRELATION, OPC-MONITOR and OPC-
RIGHTS.

Each user may have assigned up to four interfaces: a CTIP (a.g a POTS port or an ISDN or a GSM/UMTS port), a CTI
CLUSTER, SIP and IAX.

The OPC-USER PORTS CORRELATION states which CTIP or CLUSTER ports are to be assigned the user (for SIP/IAX
users this specification is given automatically when the SIP or IAX rights are granted).

The OPC-MONITOR parameter permits to specify which of the interfaces linked to the user are to be notified the OPC
management.

The following example shows how to correlate the user “opc1” to the analogue port#100 (ctip:100) and notify the OPC
management only the information relevant to the CTIP ports assigned to him.

[18:12:30] ABILIS_CPX:s user:opc1 ctip:100 opc-monitor:ctip

COMMAND EXECUTED

[18:13:17] ABILIS_CPX:d user:opc1

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: opc1
ALIAS: opc1
ID: 3 <Read Only>
PWD:
ACT: YES
GROUP:
CTIP: 100
CLUS: #
OPC-ROLE: USER

758
Draft OPC - Operator Panel Control Draft

OPC-VIEW: *
OPC-MONITOR: CTIP
OPC-HIDE-NUMBERS: NO
OPC-PRIVACY: NO
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

The OPC-MONITOR parameter can take the following values: NONE (to disable opc monitoring), ALL (to monitor every
kind of interface), CTIP (to monitor POTS, ISDN or GSM ports), IAX (to monitor IAX2 interfaces), SIP (to monitor SIP
interfaces), CLUS (to monitor clusters).

For example, assuming that the user “opc2” has both a sip and a iax account, the following commands can be used:

Table 44.1. Commands to configure opc

s user:opc2 ctip:101 opc-monitor:ctip,sip to monitor only ctip and sip interfaces

s user:opc2 ctip:101 opc-monitor:ctip,sip,iax to monitor ctip,sip and iax interfaces

If the OPC-MONITOR parameter is set to a value different from NONE (this is the default one), some other opc related
parameter are shown:

• OPC-ROLE: this parameter can be equal to USER or OPERATOR (enables advanced features like buttons drag&drop).
The default is: USER

• OPC-VIEW: list of users that can be seen on the OPC panel by this user. The default is: *

• OPC-HIDE_NUMBERS: if set to YES, the user will not see calling and called numbers.The default is: NO

• OPC-PRIVACY: if set to YES, it hides to every monitor the calling and the called numbers of the calls to and from this
user. The default is: NO

44.3. OPC Web Interface

The OPC web interface allows to monitor the users/calls state of local and remote Abilis. Follow next steps to gain access to
OPC panel:

• point your browser to Abilis ip address

Figure 44.1. Browser points to Abilis ip address

• click on login to log in to Abilis

• fill the fields with user name and password of the user created in the chapter Section 44.2.1, “Creation of the user”.

• click Operator Panel Control

Abilis has two way to show the OPC panel:

• the panel view;

• the table view.

Tip
Interesting chapter: Section 43.1, “The web interface”.

759
Draft OPC - Operator Panel Control Draft

44.3.1. The panel view

The panel view shows a box for each user and for each kind of interface. A button may have three colors:

• grey: user/interface offline

• green: user/interface online and not receveing/doing a phone call

• red: user/interface online and receiving/doing a call

Figure 44.2. Panel view

Each box always shows on the center the user name, on the top right corner the interface and on the top left corner the
number (for cluster there is no number but a *).

• ctip box

Figure 44.3. Ctip box

• sip box (offline in figure)

Figure 44.4. Sip box

760
Draft OPC - Operator Panel Control Draft

• iax box (offline in figure)

Figure 44.5. Iax box

• cluster box

Figure 44.6. Cluster Box

Tip
Refer to chapter Section 44.3.4, “Special features” to know more about buttons on the bottom of boxes.

During a call the button turns red and it shows the calling/called number on the bottom left corner. The called number is
preceded by “>” for outgoing calls. The number is preceded by “<” for incoming calls.

Figure 44.7. Example of incoming call

Click a button to open a window with more information like: alias, abilisid, time and so on.

Figure 44.8. Additional window

44.3.2. The table view

This kind of view orders users/interfaces in a table with the following columns:

761
Draft OPC - Operator Panel Control Draft

• Abilisid

• Username

• Alias

• Interface

• Number

• Status

• Calls

Figure 44.9. Table view

The entries of the table can be ordered by clicking the name of the column, so data can be sorted in increasing/decreasing
order by alias, number, interface and so on.

The color of the icon of the status is:

• grey: if user/interface is offline;

• green: if user/interface is online and is not receveing/doing a phone call;

• red: if user/interface is online and is receiving/doing a call.

During a call the field Calls shows three icon indicating:

• the state of the call;

• the direction of the call;

• the called/calling number.

762
Draft OPC - Operator Panel Control Draft

Figure 44.10. Icons of the table view

This icon shows also the duration of the call just keeping the mouse pointer on it.

44.3.3. Preferences
On the bottom of the page there's a menu showing the link Preferences.

Figure 44.11. Preferences

On this page, the choosing of the kind of interface to monitor for every user is available.(please refer to opc-monitor
parameter in the chapter Section 44.2.1, “Creation of the user”). All interfaces can be selected by thicking the checkbox
Select ALL on the top left corner of the page.

Figure 44.12. Interface selection

763
Draft OPC - Operator Panel Control Draft

44.3.4. Special features

This chapter describes the features: drag&drop, click&call, call&ring, dnd, call forward and fork features.

44.3.4.1. Drag&drop feature

It allows the operator the transfer of a call in alerting state to another user shown on the panel, or to any number.

Dragging and dropping the box in alerting state to the box of the target user, let the operator transfer the call to a user shown
on the panel.

Clicking on transfer icon, let the operator trasfer calls to the entered number.

44.3.4.2. Click&call feature

It enables only POTS phones to call a user in the address book or in the panel. There are three cases to be examined:

• phone is on-hook: in this case the phone will ring and the call will start when you pick-up the phone;

• phone is off-hook: the call immediately begins;

• phone is off-hook while on another call: the old phone call is parked and the new one begins.

Click the button shown in the figure below to use this feature.

Figure 44.13. Click&call button

When the phone is on-hook, Abilis can send to user's telephone the number you are going to call or even the name associated
in the address book.

Refer to chapter Section 42.8, “CTI System Resource” to know more about CTISYS resource parameters.

[16:32:42] ABILIS_CPX:s p ctisys clip:EXT

COMMAND EXECUTED

Use the below command and look at the POTS section of the resource to verify changes.

[16:33:12] ABILIS_CPX:d p ctisys

RES:CtiSys - Not Saved (SAVE CONF) --------------------------------------------

------------------------------------------------------------------------
DESCR:CTI_System_general_properties
- Router ---------------------------------------------------------------
ROUTING:PREFIX max-ctoc:50 au-law:A-LAW NP-CT:NO
OUT-DIAL-TONE:NO OUT-DIAL-DIGIT:0
MAIL-FROM:SYS
CALLS-LOG-DIR:C:\APP\USERS\
NAT-PREFIX:0 INT-PREFIX:00 COUNTRY-CODE:39
TON-TO-PREFIX:YES
- Last Calling number Service ------------------------------------------

764
Draft OPC - Operator Panel Control Draft

LCST:6 lcs-dir:C:\APP\CTI\LCS\
- Call&Ring ------------------------------------------------------------
CALLTRY-TOUT:60 CALLTRY-NRTY:15
- Address Book ---------------------------------------------------------
addrbook-dir:C:\APP\CTI\ADDRBOOK\
ADDRBOOK-PUB-PROTECTED:NO
- EEC ------------------------------------------------------------------
TAIL:128 NLP:YES CNM:NORMAL AEC:NO
TAIL-BASE:0 NLP-A:1 VQE-TONE-DISABLER:YES AEC-TAIL:1024
HLC:NO NLP-B:0 VQE-ACT-DELAY:300 AEC-ERL-DFT:0
HLC-THR:-10 ERL-DFT:-6
- Audio compressors defaults -------------------------------------------
dsp1-fw:D1C4F3 dsp2e-fw:D2C4F6 dsp8-fw:D8C2F2 dsp1-coderset:NORMAL
IN-GAIN:0 OUT-GAIN:0 SIG-GAIN:0 DFT-JBUF:0
DTMF-HIGH:-4 DTMF-LOW:-6 DTMF:OUTBAND MAX-JBUF:100
FM-RELAY:YES FM-LEVEL:-9 FM-DFT-JBUF:200 FM-MAX-JBUF:400
SC:YES SID-GEN:NO SID-USE:NO ECM:YES
AT:NO AT-CODE:C AT-DURATION:100
CODERS:G.711,G.726,G.727,ILBC,GSM6.10,Spirit,G.723.1,G.729A,SPEEX,Transp
- POTS defaults --------------------------------------------------------
CLIP:EXT CLIP-STD:ETSI CLIP-TAS:RP MIN-FLASH:50
SENSING:YES ABF:NO HPF:YES DEBOUNCE:16 MAX-FLASH:200
COUNTRY:IT (SL-IT.BIN) POTS-NUM-LENGTH:2
POTS-IN-GAIN-ADJ:COUNTRY POTS-OUT-GAIN-ADJ:COUNTRY BC:Speech
POTS-AT:NO POTS-AT-CODE:C POTS-AT-DURATION:100 POTS-AT-GAIN:0
POTS-DT:NO POTS-DT-CODE:D POTS-DT-DURATION:100
- CELL (GSM/UMTS) defaults ---------------------------------------------
CELL-GAIN-IN:0 CELL-GAIN-OUT:0 pdn-rxbuf:30
CELL-CODEC-GAIN-IN:0 CELL-CODEC-GAIN-OUT:0
- HDLC -----------------------------------------------------------------
dmaframe:2100 bdframe:2100 bcframe:64 bvframe:264
rxdmabuf:3 bdrxbuf:14 bcrxbuf:3 bvrxbuf:3
txdmabuf:2 bdtxbuf:1 bctxbuf:1 bvtxbuf:3
- Tones and ringing patterns -------------------------------------------
- Tones -------------------+------+------+------+------+------+------+
TONESET:ABILIS | T1 | S1 | T2 | S2 | T3 | S3 |
----------+------+------+------+------+------+------|
DIAL-xx: |(7000)|( 0)|( 0)|( 0)|( 0)|( 0)|
OUT-DIAL-xx: |( 200)|( 200)|( 600)|(1000)|( 0)|( 0)|
ALERT-xx: |(1000)|(4000)|( 0)|( 0)|( 0)|( 0)|
BUSY-xx: |( 500)|( 500)|( 0)|( 0)|( 0)|( 0)|
DISC-xx: |( 200)|( 200)|( 0)|( 0)|( 0)|( 0)|
HOLD-xx: | 110 | 110 | 110 | 1500 | 0 | 0 |
MENU-xx: | 110 | 2000 | 0 | 0 | 0 | 0 |
- POTS Ringing ------------+------+------+------+------+------+------+
EXT-xx: | 1000 | 4000 | 0 | 0 | 0 | 0 |
INT-xx: | 400 | 200 | 400 | 3000 | 0 | 0 |
PKC-xx: | 500 | 500 | 500 | 500 | 1500 | 2000 |
+------+------+------+-------------+------+
- Clock Sources for H100 cards -----------------------------------------
CLK:ANYTE
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| P1:..P10:| . | . | . | . | . | . | . | . | . | . |
|P11:..P20:| . | . | . | . | . | . | . | . | . | . |
|P21:..P30:| . | . | . | . | . | . | . | . | . | . |
|P31:..P40:| . | . | . | . | . | . | . | . | . | . |
|P41:..P50:| . | . | . | . | . | . | . | . | . | . |
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
- Clock Sources for NOT-H100 cards -------------------------------------
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+
| CARD: | CLK: | P1: | P2: | P3: | P4: | P5: | P6: | P7: | P8: |
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+

765
Draft OPC - Operator Panel Control Draft

*** No NOT-H100 cards present or active ***

On a working Abilis an initialization of CTISYS resource is required (save conf and init res:ctisys).

44.3.4.3. Call&ring feature

This feature allows to implement the call reservation only for POTS phones. A POTS phone retries to call a number until
the call reaches ALERTING or ACTIVE state. When one of these states is reached, the phone rings and the reserved call
begins. There are various way to launch call&ring procedure:

• when a call fails, enter the code *9 during the disconnection phase and place the phone on-hook;

• using the address book or operator panel HTTP pages.

To abort the call&ring procedure, pick up the phone and enter the code *9 at the dial tone.

Click the button shown in the figure below to use this feature from operator panel.

Figure 44.14. Call&ring button

If another call is placed while the call&ring procedure is active, the procedure is suspended and it's restored at the end of the
call.

The maximum number of retries and the number of seconds between retries can be assigned to two parameters of CTISYS
resource in the call&ring section. Use the below command to view their values.

[17:08:59] ABILIS_CPX:d p ctisys

RES:CtiSys --------------------------------------------------------------------
DESCR:CTI_System_general_properties
- Router ---------------------------------------------------------------
ROUTING:PREFIX max-ctoc:50 au-law:A-LAW NP-CT:NO
OUT-DIAL-TONE:NO OUT-DIAL-DIGIT:0
MAIL-FROM:SYS
CALLS-LOG-DIR:C:\APP\USERS\
NAT-PREFIX:0 INT-PREFIX:00 COUNTRY-CODE:39
TON-TO-PREFIX:YES
- Last Calling number Service ------------------------------------------
LCST:6 lcs-dir:C:\APP\CTI\LCS\
- Call&Ring ------------------------------------------------------------
CALLTRY-TOUT:60 CALLTRY-NRTY:15
- Address Book ---------------------------------------------------------
addrbook-dir:C:\APP\CTI\ADDRBOOK\
ADDRBOOK-PUB-PROTECTED:NO
- EEC ------------------------------------------------------------------
TAIL:128 NLP:YES CNM:NORMAL AEC:NO
TAIL-BASE:0 NLP-A:1 VQE-TONE-DISABLER:YES AEC-TAIL:1024

766
Draft OPC - Operator Panel Control Draft

HLC:NO NLP-B:0 VQE-ACT-DELAY:300 AEC-ERL-DFT:0

HLC-THR:-10 ERL-DFT:-6
- Audio compressors defaults -------------------------------------------
dsp1-fw:D1C4F3 dsp2e-fw:D2C4F6 dsp8-fw:D8C2F2 dsp1-coderset:NORMAL
IN-GAIN:0 OUT-GAIN:0 SIG-GAIN:0 DFT-JBUF:0
DTMF-HIGH:-4 DTMF-LOW:-6 DTMF:OUTBAND MAX-JBUF:100
FM-RELAY:YES FM-LEVEL:-9 FM-DFT-JBUF:200 FM-MAX-JBUF:400
SC:YES SID-GEN:NO SID-USE:NO ECM:YES
AT:NO AT-CODE:C AT-DURATION:100
CODERS:G.711,G.726,G.727,ILBC,GSM6.10,Spirit,G.723.1,G.729A,SPEEX,Transp
- POTS defaults ------------------------nrtyC--------------------------------
CLIP:EXT CLIP-STD:ETSI CLIP-TAS:RP MIN-FLASH:50
SENSING:YES ABF:NO HPF:YES DEBOUNCE:16 MAX-FLASH:200
COUNTRY:IT (SL-IT.BIN) POTS-NUM-LENGTH:2
POTS-IN-GAIN-ADJ:COUNTRY POTS-OUT-GAIN-ADJ:COUNTRY BC:Speech
POTS-AT:NO POTS-AT-CODE:C POTS-AT-DURATION:100 POTS-AT-GAIN:0
POTS-DT:NO POTS-DT-CODE:D POTS-DT-DURATION:100
- CELL (GSM/UMTS) defaults ---------------------------------------------
CELL-GAIN-IN:0 CELL-GAIN-OUT:0 pdn-rxbuf:30
CELL-CODEC-GAIN-IN:0 CELL-CODEC-GAIN-OUT:0
- HDLC -----------------------------------------------------------------
dmaframe:2100 bdframe:2100 bcframe:64 bvframe:264
rxdmabuf:3 bdrxbuf:14 bcrxbuf:3 bvrxbuf:3
txdmabuf:2 bdtxbuf:1 bctxbuf:1 bvtxbuf:3
- Tones and ringing patterns -------------------------------------------
- Tones -------------------+------+------+------+------+------+------+
TONESET:ABILIS | T1 | S1 | T2 | S2 | T3 | S3 |
----------+------+------+------+------+------+------|
DIAL-xx: |(7000)|( 0)|( 0)|( 0)|( 0)|( 0)|
OUT-DIAL-xx: |( 200)|( 200)|( 600)|(1000)|( 0)|( 0)|
ALERT-xx: |(1000)|(4000)|( 0)|( 0)|( 0)|( 0)|
BUSY-xx: |( 500)|( 500)|( 0)|( 0)|( 0)|( 0)|
DISC-xx: |( 200)|( 200)|( 0)|( 0)|( 0)|( 0)|
HOLD-xx: | 110 | 110 | 110 | 1500 | 0 | 0 |
MENU-xx: | 110 | 2000 | 0 | 0 | 0 | 0 |
- POTS Ringing ------------+------+------+------+------+------+------+
EXT-xx: | 1000 | 4000 | 0 | 0 | 0 | 0 |
INT-xx: | 400 | 200 | 400 | 3000 | 0 | 0 |
PKC-xx: | 500 | 500 | 500 | 500 | 1500 | 2000 |
+------+------+------+-------------+------+
- Clock Sources for H100 cards -----------------------------------------
CLK:ANYTE
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| P1:..P10:| . | . | . | . | . | . | . | . | . | . |
|P11:..P20:| . | . | . | . | . | . | . | . | . | . |
|P21:..P30:| . | . | . | . | . | . | . | . | . | . |
|P31:..P40:| . | . | . | . | . | . | . | . | . | . |
|P41:..P50:| . | . | . | . | . | . | . | . | . | . |
+----------+-----+-----+-----+-----+-----+-----+-----+-----+-----+-----+
- Clock Sources for NOT-H100 cards -------------------------------------
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+
| CARD: | CLK: | P1: | P2: | P3: | P4: | P5: | P6: | P7: | P8: |
+------------+-------+-----+-----+-----+-----+-----+-----+-----+-----+
*** No NOT-H100 cards present or active ***

The following command is useful to set the number of retries to 30 and the number of seconds between retries to 10s. On a
working Abilis an initialization of CTISYS resource is required (save conf and init res:ctisys).

[17:15:21] ABILIS_CPX:s p ctisys calltry-tout:30 calltry-nrty:10

COMMAND EXECUTED

[17:15:32] ABILIS_CPX:save conf

767
Draft OPC - Operator Panel Control Draft

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

44.3.4.4. DND - Do Not Disturb

DND can be activated using CTI Preferences or CTI Advanced Preferences. When a user enables DND by CTI Preferences
and for a certain interface, the following icon is shown on the bottom of the relative box:

Figure 44.15. DND Icon - CTI Preferences

If DND is enabled by CTI Advanced Preferences, the following icon is shown:

Figure 44.16. DND Icon - CTI Advanced Preferences

Tip
Interesting chapters:

Section 43.2.3.2, “CTI preferences”;

Section 43.2.3.3, “CTI advanced preferences”;

Section 43.2.3.4, “CTI preferences administration through CP”;

Section 42.11.1, “Supplemetary services”.

44.3.4.5. CF - Call Forward

CF can be activated using CTI Preferences or CTI Advanced Preferences. When a user enables CF for a certain interface, the
following icon is shown on the bottom of the relative box:

768
Draft OPC - Operator Panel Control Draft

Figure 44.17. CF Icon - CTI Preferences

If CF is enabled by CTI Advanced Preferences, the following icon is shown:

Figure 44.18. CF Icon - CTI Advanced Preferences

Tip
Interesting chapters:

Section 43.2.3.2, “CTI preferences”;

Section 43.2.3.3, “CTI advanced preferences”;

Section 43.2.3.4, “CTI preferences administration through CP”;

Section 43.2.3.5, “CTI advanced preferences administration through CP”;

Section 42.11.1, “Supplemetary services”.

44.3.4.6. Fork on alerting

When a user configures calls fork a icon is shown on the bottom of the relative box:

Figure 44.19. Fork Icon

Tip
Interesting chapters:

769
Draft OPC - Operator Panel Control Draft

Section 43.2.3.2, “CTI preferences”;

Section 43.2.3.3, “CTI advanced preferences”;

Section 43.2.3.4, “CTI preferences administration through CP”;

Section 43.2.3.5, “CTI advanced preferences administration through CP”;

Section 42.11.1, “Supplemetary services”.

770
Draft Draft

Chapter 45. IAX - Inter-Asterisk

eXchange
Marco Bellesia
Luigi Demuro

Table of Contents
45.1. CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1.1. Activating the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
45.1.2. CTIIAX resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
45.2. CTIIAX tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
45.2.2. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 778
45.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
45.4. Example of IAX configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 781
45.4.1. Configuration of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
45.4.3. CTIIAX translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
45.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
45.5. Connecting Abilis and Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.1. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
45.5.2. Activation of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.3. Example 1: Abilis and Asterisk have static IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
45.5.4. Example 2: Abilis has a static address and Asterisk has a dynamic address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
45.5.5. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
45.6. CTIIAX diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.1. CTIIAX diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
45.6.2. CTIIAX statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
45.6.3. Debug of the CTIIAX resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
45.7. Appendix - IAX protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807

45.1. CTIIAX resource

The Abilis IAX driver provides gateway functionalities between IAX and ISDN networks for audio services only; it is not
intended to support full IAX to IAX videoconferencing gateway. The Abilis IAX driver can be interfaced with:

• Physical Volp phones with IAX support

• Softphone program for PC (e.g. Idefisk, laxtalk, …)

• PBX Digium Asterisk

45.1.1. Activating the CTIIAX resource

Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:ctiiax

RES:CTIIAX ALREADY EXISTS

The CTIIAX resource may already exist in the system, but may not yet be active: set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctiiax

771
Draft IAX - Inter-Asterisk eXchange Draft

COMMAND EXECUTED

Caution
You must restart the Abilis to make the resource running (use the command warm start to reboot the
Abilis) after adding or setting the CTIIAX active.

[11:01:39] ABILIS_CPX:s p ctiiax act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p ctiiax

RES:CtiIax - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
DESCR:Inter-Asterisk_eXchange_Version_2
LOG:NO ACT:YES
mxps:2172 sesnum:10 udp-locport:4569
SRCADD:OUT-IP TOS:0-D
IPSRC:* IPSRCLIST:#
AUTH:MD5 REM-AUTH:MD5 CTIP-TYPE:USER
LIFETIME:60 REM-LIFETIME:60 NP-CT:SYS
RETR-FREQ:400 TRUNK:NO ROUTING:EN-BLOC
RETR-EXCEED:10000 TRUNK-FREQ:40 DIALT:5
RETR-EXCEED-FAST:2000 TRUNK-TS:YES T302:15
PLAY-DTMF:150 CHAN-FREQ:20 ROUTE-BY-SD:NO
PLAY-SILENCE:100 DISC-AUDIO:NO PROVIDE-SG:NO
DETECT-DTMF:40 CLIP-RULE:PRIVATE CPO:NO
DETECT-SILENCE:40 RG-IN:DISABLE CPO-STATE:ACCEPT
NETSTATS:NO TRANSFER:IAX CPO-DROP:NO
HTML-IN:
HTML-OUT:

Caution
Execute the initialization command init res:ctiiax to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

45.1.2. CTIIAX resource parameters

Use the below command to display the parameters of the resource; the d p ctiiax ? command shows the meaning of
parameters.

[11:01:39] ABILIS_CPX:d p ctiiax

RES:CtiIax - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
DESCR:Inter-Asterisk_eXchange_Version_2
LOG:NO ACT:YES
mxps:2172 sesnum:10 udp-locport:4569
SRCADD:OUT-IP TOS:0-D
IPSRC:* IPSRCLIST:#
AUTH:MD5 REM-AUTH:MD5 CTIP-TYPE:USER
LIFETIME:60 REM-LIFETIME:60 NP-CT:SYS
RETR-FREQ:400 TRUNK:NO ROUTING:EN-BLOC
RETR-EXCEED:10000 TRUNK-FREQ:40 DIALT:5
RETR-EXCEED-FAST:2000 TRUNK-TS:YES T302:15
PLAY-DTMF:150 CHAN-FREQ:20 ROUTE-BY-SD:NO
PLAY-SILENCE:100 DISC-AUDIO:NO PROVIDE-SG:NO
DETECT-DTMF:40 CLIP-RULE:PRIVATE CPO:NO

772
Draft IAX - Inter-Asterisk eXchange Draft

DETECT-SILENCE:40 RG-IN:DISABLE CPO-STATE:ACCEPT

NETSTATS:NO TRANSFER:IAX CPO-DROP:NO
HTML-IN:
HTML-OUT:

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime CTIIAX activation/deactivation.

sesnum Maximum number of IAX simultaneous sessions.

udp-locport UDP port number on which the incoming IAX (call signalling protocol) call is accepted.

SRCADD Source IP address for outgoing connections [R-ID: the source IP address of the outgoing
datagrams will be set to the current RouterID value; OUT-IP: the source IP address of the
outgoing datagrams will be set on the base of the output IP interface; 1-126.x.x.x,
128-223.x.x.x: the source IP address of the outgoing datagrams will be set to the selected
value; Ip-nnn: use the current IPADD of the specified IP resource].

TOS Sets the TOS value for CTIIAX resource.

IPSRC Specifies which client's IP address is allowed to access and called by IAX server.

IPSRCLIST Name of the IP address list (IP/IR/RU/MR) from which the request for access can be accepted.

AUTH Authentication method offered to authenticating/registering users (incoming calls/registrations).

REM-AUTH Authentication method when Abilis is authenticating/registering to a peer (outgoing calls/

registrations).

LIFETIME Default duration of incoming registration; users must register themselves before this time interval
expires.

REM-LIFETIME Default duration of outgoing registration; Abilis must register before this time interval expires.

CTIP-TYPE CTIP type assigned to CTIIAX driver.

NP-CT Enables/disables Net-Public to Net-Public call transfer [NO: NP to NP disabled; YES: NP to NP

enabled, except when both calls are outgoing, which is not allowed to avoid the “hang trunk”
problem; SYS: NP to NP depends on NP-CT in CtiSys].

ROUTING Routing management.

DIALT Dialling timeout.

T302 Timeout for “empty” setup.

RETR-FREQ Retransmission frequency (time interval between a retransmission attempt of a IAX full frame and
another one if acknowledgement doesn't arrive).

RETR-EXCEED Retransmission time limit (maximum time for which a frame can stay unacknowledged).

RETR-EXCEED-FAST Retransmission time limit for NEW and REGREQ messages (these messages are used to setup
a call); a shorter timeout for these messages helps in keeping small the time lost in case of peer
failure and make a more effective alternative routing.

TRUNK Enables/disables trunking.

TRUNK-FREQ Trunk frequency: it represents how much time to wait prior to send the UDP packet. During this
time other voice packets coming form the same or other channels can be inserted in the same UDP
header thus sensibly reducing the transmisison overhead; of course it adds some delay, but great
benefit toward the bandwidth saving.

TRUNK-TS Enables/disables individual timestamps in a meta trunk.

773
Draft IAX - Inter-Asterisk eXchange Draft

CHAN-FREQ Channel frequency for bandwidth optimisation. It represents how many msec of voice are desired
to be packed into a single UDP packet; it's a “desire” in the sense that the actual optimisation will
depend on the frame length in msec of the coder in use, and the result will be an a approximation
by defect.

ROUTE-BY-SD It allows routing using subaddress called field (SD) [NO: the SD is completely ignored; YES: the
user corresponding to SD is searched: if found the call is forwarded to that user, otherwise the
standard search in CtiIax table is performed; USER: the user corresponding to SD is searched: if
found and the user has parameter IAX-ROUTE-BY-SD:YES, the call is forwarded to that user,
otherwise the standard search in CtiIax table is performed].

PROVIDE-SG Allows insertion of IAX USER NAME in subaddress calling field [NO: disable insertion
of USERNAME in calling subaddress; YES: enable insertion of USERNAME in calling
subaddress; USER: insertion of USERNAME in calling subaddress depends on individual user
configuration]. When it is enabled, either as result of value YES or because value is USER and
the user corresponing to the subaddress content allows it, the call sent to CTIR will include in the
subaddress calling field the IAX USER NAME of the caller.

PLAY-DTMF Duration of a DTMF played from a DTMF FULL FRAME. When CTIIAX has to convert a
DTMF FULL FRAME command to CTIR DTMF frame, it produces as many frames as needed
to cover the period specified by this parameter. The actual interval must be rounded to the value
immediately higher than configured one.

PLAY-SILENCE Duration of a silence played after a PLAY-DTMF. When CTIIAX has to convert a DTMF FULL
FRAME command to CTIR DTMF frame, it produces as many frames as needed to cover the
perios specified by PLAY-DTMF parameter. Before a new DTMF can be played, a silence period
must elapse, and this is controlled by this parameter.

DETECT-DTMF Duration of a DTMF from CTIR in order to allow digit recognition. When CTIIAX received
DTMF frames from CTIR, and after it created the most accurate and monotonical timestamp, the
DTMF length is measured and for a successful digit recognition it must be of at least the length
specified here. If the configured value is not an exact multiple of the frame rate, it must be rounded
to the next upper value multiple of frame rate.

DETECT-SILENCE Duration of a silence after a DTMF from CTIR in order to recognise a digit.

TRANSFER Unattended call transfer handling type [IAX: the handling respects IAX specifications: the original
call is dropped; CPX: the handling is modified by Abilis: the original call is kept up in case that
transferred one fails(user busy, not reacheable, etc...)].

CPO Enables/disables Call Path Optimization between two IAX users. It is used when IAX-CPO:SYS
in user service, otherwise the value of IAX-CPO is used.

CPO-STATE Earlier state of both call legs in which the Call Path Optimization can be ordered [ACCEPT: CPO
on ACCEPT receiving; RINGING: CPO on RINGING receiving; ANSWER: CPO on ANSWER
receiving].

CPO-DROP Enables/disables call drop on Call Path Optimization (CPO) failure. If enabled, the call will drop if
CPO will fail. It is used when IAX-CPO-DROP:SYS in user service, otherwise the value of IAX-
CPO-DROP is used.

NETSTATS Enables/disables network statistics and checks connection every the specified value of seconds.

HTML-IN URL to send to a caller IAX user using the HTML full frame of the IAX protocol.

HTML-OUT URL to send to a called IAX user using the HTML full frame of the IAX protocol.

The following command allows the administrator to change the configuration of the resource:

s p ctiiax parameter:value...

Caution
Execute the initialization command init res:ctiiax to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

774
Draft IAX - Inter-Asterisk eXchange Draft

45.2. CTIIAX tables

45.2.1. Users table
IAX users must be registrated in the Users table; all the parameters mandatory for the registration, the authentication and the
IAX identification are defined in each Abilis user's profile.

Use the following command to display the parameters of the users; the d user: ? command shows the meaning of parameters.

[08:47:38] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
iax_user YES # # NO NO NO NO YES NO

To view the details of a single user type the following command:

[08:47:39] ABILIS_CPX:d user:iax_user

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: iax_user
ALIAS: iax_user
ID: 9 <Read Only>
PWD:
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
IAX: YES
IAX-HOST: DYNAMIC
IAX-SRCADD: SYS
IAX-PORT: (DYNAMIC)
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 2
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER:
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:

775
Draft IAX - Inter-Asterisk eXchange Draft

IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: SYS
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER:
IAX-REM-PASS:
IAX-REM-AUTH: SYS
IAX-REM-REG: NO
-------------------------------------------------------------------------------

Note
The above command displays only the parameters related to enabled driver; if you want to see all the user
parameters type the d usere:iax_user command.

Meaning of the most important parameters:

IAX Enables/disables IAX service for the user.

IAX-HOST IP address of the IAX host (the ip address of the user) [DYNAMIC: IP is not known in advance,
it is known after the user executes the registration; 1.0.0.0-126.255.255.255,
128.0.0.0-223.255.255.255: remote IP is known in advance; calls and registrations are
performed and accepted only with this IP].

IAX-SRCADD Source IP address for outgoing connections [R-ID: the source IP address of the outgoing
datagrams will be set to the current RouterID value; OUT-IP: the source IP address of the
outgoing datagrams will be set on the base of the output IP interface; 1-126.x.x.x,
128-223.x.x.x: the source IP address of the outgoing datagrams will be set to the selected
value; Ip-nnn: use the current IPADD of the specified IP resource; SYS: uses the value in
SRCADD parameter in CTIIAX resource].

IAX-PORT UDP port on which the remote user is listening; Abilis outgoing UDP calls for this user will be
sent to this port.

IAX-IP-PERMIT Range of allowed IP addresses of the IAX user.

IAX-MAXSES-BID Maximum number of simultaneous bidirectional sessions.

IAX-MAXSES-IN Maximum number of simultaneous reserved input sessions.

IAX-MAXSES-OUT Maximum number of simultaneous reserved output sessions.

IAX-NUMBER Number that identifies the user; if this number is not null, it is used to route calls to the user.

IAX-CG-NUM Calling number to use for calls coming from the user. The parameter accepts from 1 up to 20
characters in the following range: [AUTO: enforces caller id information element equal to IAX-
NUMBER; [0..9]: enforces the content with these exact digits; [0..9]*: replaces first specified
digits and passes the remaining transparently; *: passes calling address information element
transparently; #: removes calling number information element; ##: enforces the presentation
restricted: the calling number is sent empty; ##[0..9]: enforces the presentation restricted: the
calling number is sent with these exact digits; ##[0..9]*: enforces the presentation restricted:
the first specified digits are replaced and the remaining are passed transparently; ##*: enforces the
presentation restricted: the calling number is sent transparently].

IAX-FWD-CG-NUM Indicates how the calling number is managed in unconditional call transfers and call forwarding
[CALLER: the calling number of the original call is passed to the new recipient; USER: the calling
number of the IAX user performing the action is passed to the new recipient].

IAX-ROUTE-BY-SD Allows routing using subaddress called field. Calls from CTIR and directed to IAX users are first
directed to the user with a USERNAME equal to what is specified in Subaddress Called; if such

776
Draft IAX - Inter-Asterisk eXchange Draft

user does not exists, or the user disallows IAX-ROUTE-BY-SD, the call is routed using standard
CTIIAX table matches.

IAX-PROVIDE-SG Allows insertion of IAX USER NAME in subaddress calling field.

IAX-LCS-GROUP Last Calling number Service group identifier [NONE, 1..32].

IAX-CONTEXT Context string to use for resource dial-plan choice in other IAX peers.

IAX-PROVIDE-NAME Rule to provide CALLING NAME in outgoing calls [BLANK: provides an empty CALLING
NAME; SG: provides Calling Subaddress as CALLING NAME; REM-USER: provides IAX-
REM-USER as CALLING NAME; NO: doesn't provide CALLING NAME].

IAX-AUTH Authentication types offered to autenticating/registering users (incoming calls/registrations) [SYS:

uses the value in AUTH parameter in CTIIAX resource; PLAIN: basic authentication via user/
password; MD5: MD5 authentication type].

IAX-NETSTATS Indicates how often the user availability is checked [SYS: uses the value in NETSTATS parameter
in CTIIAX resource; 1..60: frequency for statistics (sec); NO: No statistics].

IAX-TRUNK Enables/disables trunking [SYS: uses the value in TRUNK parameter in CTIIAX resource; NO:
doesn't allow trunking; YES: allows trunking].

IAX-TRUNK-FREQ IAX trunk frequency [SYS: uses the value in TRUNK-FREQ parameter in CTIIAX resource;
20..240: frequency for trunking (msec)].

IAX-CHAN-FREQ IAX desired channel frequency for bandwidth optimisation, to be rounded down to a codec frame
length multiple [SYS: uses the value in CHAN-FREQ parameter in CTIIAX resource; 30..90:
frequency for banwidth optimisation].

IAX-CPO Enables/disables Call Path Optimization (CPO) [SYS: uses the value in CPO parameter in CTIIAX
resource; NO: doesn't allow CPO; YES: allows CPO].

IAX-CPO-STATE Earlier state of both call legs in which the Call Path Optimization can be ordered [SYS: uses the
value in CPO-STATE parameter in CTIIAX resource; RINGING: CPO on RINGING receiving;
ANSWER: CPO on ANSWER receiving].

IAX-CPO-DROP Enables/disables call drop on Call Path Optimization (CPO) failure [SYS: uses the value in CPO-
DROP parameter in CTIIAX resource; NO: call will not drop on CPO failure.; YES: call will drop
on CPO failure.].

IAX-SS Enable/disable IAX supplementary services

IAX-SS-PICKUP IAX supplementary service. Pickup permissions [NO, ANY]

IAX-SS-PRES-CG IAX supplementary service. Calling present [NO, YES]

IAX-SS-CF-DND IAX supplementary service. Call forwarding and Do-Not-Disturb [NO, YES]

IAX-TRANSFER Unattended call transfer handling type [SYS: uses the value in IAX-TRANSFER parameter in
CTIIAX resource; IAX: the handling respects IAX specifications: the original call is dropped;
CPX: the handling is modified by Abilis: the original call is kept up in case that transferred one
fails].

IAX-HTML-IN URL to send to a caller IAX user using the HTML full frame of the IAX protocol.

IAX-HTML-OUT URL to send to a called IAX user using the HTML full frame of the IAX protocol.

IAX-REM-USER The name used in the remote IAX server to identify the Abilis (this name is used for both
registration and authentication purposes).

IAX-REM-PASS The password used in the remote IAX server to identify the Abilis (this password is used for both
registration and authentication purposes).

IAX-REM-AUTH Authentication method when Abilis is authenticating/registering to a peer (outgoing calls/

registrations) [SYS: uses the value in REM-AUTH parameter in CTIIAX resource; PLAIN: basic
authentication via user/password; MD5: MD5 authentication type].

777
Draft IAX - Inter-Asterisk eXchange Draft

IAX-REM-REG Enables/disables the registration of the Abilis to the remote IAX server.

45.2.2. CTIIAX translation table

This table contains relations between an IAX-number (or a prefix, when * is included in the number) and a IAX-user. The
calls which CTIR forwards to CTIIAX find the destination user by matching the called number. It's the result of CDO field of
the CTI routing, with the CDI field of the table.

When the parameter IAX-CG-NUM is set to AUTO, calls from CTIIAX to CTIR have the callerid provided by IAX user
validated against the CTIIAX translation table and the IAX-number set in user service. In case of validation failure the
callerid will be overwritten with the value configured in the IAX-number of the user table (*, as wildcard, is not included).

To view the details of the CTIIAX translation table, type :

[08:59:25] ABILIS_CPX:d ctiiax

- Not Saved (SAVE CONF) -------------------------------------------------------

Total:2 Connected:1 Static:1

NUMx: USER: P:
------------------------------------------------------------
7* asterisk S
200 iax_user C

There are two types of entries:

• connected: when you specify an IAX-NUMBER in the IAX users chart, the CDI parameter you find in the table will be
the same. In case the routings are connected the letter C will appear under the P item.

Tip
The connected entries are automatically added.

• statics : when you don't specify an IAX-NUMBER in the IAX user table, but you associate it by hand in the table: this
system is used when you need to add several numbers to the same user (for instance in case of static routings) the letter S
will appear under the P item.

To manage the IAX translation table use the following commands:

• a ctiiax numx:<IAX-NUMBER> username:<name> : adds a new IAX-NUMBER;

• s ctiiax numx:<IAX-NUMBER> username:<name> : modifies the username of an existing IAX-NUMBER;

• c ctiiax numx:<IAX-NUMBER> : clears an IAX-NUMBER;

• d ctiiax numx:<IAX-NUMBER> : displays the list of IAX-NUMBER or a specific one.

Tip
More IAX-numbers can be associated to a single user.

The IAX users creation creates the NumIax list in which are located all the IAX-NUMBERS of the users (it is very useful
for the CTIR configuration).

To view the list type:

[16:40:26] ABILIS_CPX:d list:numiax

LIST:NumIax - IN
Automatically_generated_CTI_IAX_Numbers_list_(ReadOnly)
601 602

Note
It is a “read only” list as it is automatically created by the system.

778
Draft IAX - Inter-Asterisk eXchange Draft

45.3. CTI Routings

In order to route the calls to and from the CTIIAX resource, adding the appropiate routings in the CTI Router is needed.

The destination or the source of the IAX group appears as CtiIax. When a CTI routing is created there's no need to specify
it, because it is automatically compiled.

To view all the configurable parameters type:

[13:47:29] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------

The routing types involved with CTIIAX are:

Table 45.1. CTIIAX routing

Type Description Transcoding supported

VtoI Voice to IAX NO
CtoI Cluster to IAX YES
HtoI H.323 to IAX YES
DtoI DISA to IAX YES
StoI SIP to IAX YES
ItoV IAX to Voice NO
ItoC IAX to Cluster YES
ItoH IAX to H.323 YES
ItoD IAX to DISA YES
ItoS IAX to SIP YES
ItoI IAX to IAX YES

Tip
Transcoding is allowed when parameter CODERSOUT is different from *.

The transcoding is possible only for the coders supported by Abilis. Refer to Section 42.8, “CTI System
Resource” to have more information about CTISYS resource. To view them, type:

[14:09:52] ABILIS_CPX:d d ctisys

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
-- Number of simultaneous calls ----------------------------------------
| State: Alerting/Connected | State: Any |
---------------|---Current---|----Peak-----|---Current---|----Peak-----|
TR | 0 | 0 | 0 | 0 |
DATA | 0 | 0 | 0 | 0 |
VtoCHISD | 0 | 0 | 0 | 0 |

779
Draft IAX - Inter-Asterisk eXchange Draft

CHISDtoCHISD | 0 | 0 | 0 | 0 |
CHISDtoV | 0 | 0 | 0 | 0 |
ALL | 0 | 0 | 0 | 0 |
------------------------------------------------------------------------
- Available coders -----------------------------------------------------
-- Coder ---|-- Bit rates (kbps) --|-- Coder ---|-- Bit rates (kbps) --|
G.711-A |64 |G.711-u |64 |
TRANSPARENT |64 |Spirit |6.4, 7.2, 8, 8.8, 9.6 |
------------------------------------------------------------------------
- Clock Sources for H100 cards -----------------------------------------
CLK:INT
- Clock Sources for NOT-H100 cards -------------------------------------
*** No NOT-H100 cards running ***

The following parameters are useful when configuring a CTIIAX routing.

SPOUT Allows to set the maximum bandwidth the coder can use in output [*: preserves the bit rate value; 5300;
6000; 6300; 6400; 7200; 8000; 8800; 9600; 11200; 13200; 13340; 15200; 16000; 18400;
24000; 24800; 32000; 40000; 64000 bps].

Warning
If you set SPOUT:9600, you will not be able to use CODERS which need greater bit rates
(e.g. G.711 works at 64 Kbps).

CODERSOUT Allows to filter/select the available coder audio sets for the output. When you set the parameters * you don't
enable the cross-encoding, you automatically keep the coder used in the incoming call. When you set specific
values or value combinations, you can increase or reduce the set of available coders. Example:

• CODERSOUT:*,Sys : adds, in output, to the coders already present in input, the set described in the
CTISYS resource;

• CODERSOUT:Sys : allows to use, in output, only the coders described in the CTISYS resource;

• CODERSOUT:<specific coder> : enables, in output, only the chosen coder. You can also specify
many coders (divide their names/codes with a comma ,);

• CODERSOUT:*,<coder list> : adds, in output to the already present coders, the coders indicated in
the list; you can also only specify the list;

• CODERSOUT:<coder list> : enables to use in output only the coders present in the list.

Tip
The coder position, inside the coders list in the CTISYS resource, defines the order of
preference.

SP Allows tho set the maximum bandwidth the coder can use in input [5300; 6000; 6300; 6400; 7200;
8000; 8800; 9600; 11200; 13200; 13340; 15200; 16000; 18400; 24000; 24800; 32000; 40000;
64000 bps].

Warning
If you set SPOUT:9600, you will not be able to use CODERS which need greater bit rates
(e.g. G.711 works at 64 Kbps).

CODERS Allows to limit the available audio sets during the negotiation. The various configuration values are:

• CODERS:* : accepts in input all the coders;

• CODERS:Sys : accepts in input only the coders specified in the CTISYS resource;

• CODERS:<specific coder> : accepts in input only the indicated coder. You can also specify several
coders (divide their name/code with a comma ,);

• CODERS:<coder list> : accepts in input only the coders indicated in the list.

780
Draft IAX - Inter-Asterisk eXchange Draft

Tip
The coder position, inside the coders list in the CTISYS resource, defines the order of
preference.

DJ Default Jitter buffer size; it must be minor or equal to MJ.

• For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [sys, 0..1000 msec];

• For TYPE:CtoVCHISD/*toVCHISD: [*, sys, 0..1000 ms].

MJ Maximum Jitter buffer size; it must be major or equal to DJ [sys, 0..1000 msec].

• For TYPE:VtoCHISD/HtoVCHISD/ItoVCHISD/StoVCHISD/DtoVCHIDS: [sys, 0..1000 msec];

• For TYPE:CtoVCHISD/*toVCHISD: [*, sys, 0..1000 ms].

DJOUT Default Jitter buffer size output; it must be minor or equal to MJOUT [sys, 0..1000 msec];

MJOUT Maximum Jitter buffer size output; it must be major or equal to DJOUT [*, sys, 0..1000 ms].

45.4. Example of IAX configuration

Figure 45.1. Configuration scheme

In the figure there are the following elements:

• Site 1:

• IAX phone;

• PC with Zoiper program for IAX communications;

• analog phone connected to a POTS port of the Abilis;

• Abilis that manages all the systems and a VPN with “Site 2”.

• Site 2:

• Asterisk server;

• analog telephone connected to a POTS port of the Abilis.

• Abilis that manages interconnection with Asterisk and a VPN with “Site 1”;

781
Draft IAX - Inter-Asterisk eXchange Draft

The purpose is:

• to enable the communication between the IAX users (IAX phone and PC with Zoiper);

• to enable the communication between the POTS telephone of “Site 1” and the IAX users;

• to enable the communication between the IAX users of “Site 1” and the analog phone phone of “Site 2”;

• to forward to the Asterisk of “Site 2” the calls sent to “Site 1” in case “Site 1” is busy or doesn't answer.

In this example suppose that the POTS cards, used to manage the analog phones and configured for Cluster and CtiLink for
compressed phone calls, are already active on Abilis.

45.4.1. Configuration of the CTIIAX resource

Activate the CTIIAX resource in the Abilis of “Site 1” and enable up to 15 IAX connections.

[16:14:44] ABILIS_CPX_1:s p ctiiax act:yes sesnum:15

COMMAND EXECUTED

[16:16:12] ABILIS_CPX_1:d p ctiiax

RES:CtiIax - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

------------------------------------------------------------------------
DESCR:Inter-Asterisk_eXchange_Version_2
LOG:NO ACT:YES
mxps:2172 sesnum:15 udp-locport:4569
SRCADD:OUT-IP TOS:0-D
IPSRC:* IPSRCLIST:#
AUTH:MD5 REM-AUTH:MD5 CTIP-TYPE:USER
LIFETIME:60 REM-LIFETIME:60 NP-CT:SYS
RETR-FREQ:400 TRUNK:NO ROUTING:EN-BLOC
RETR-EXCEED:10000 TRUNK-FREQ:40 DIALT:5
RETR-EXCEED-FAST:2000 TRUNK-TS:YES T302:15
PLAY-DTMF:150 CHAN-FREQ:20 ROUTE-BY-SD:NO
PLAY-SILENCE:100 DISC-AUDIO:NO PROVIDE-SG:NO
DETECT-DTMF:40 CLIP-RULE:PRIVATE CPO:NO
DETECT-SILENCE:40 RG-IN:DISABLE CPO-STATE:ACCEPT
NETSTATS:NO TRANSFER:IAX CPO-DROP:NO
HTML-IN:
HTML-OUT:

Keep all the default parameters.

Repeat the same operation for the Abilis of “Site 2.”

45.4.2. Users configuration

Activate the two IAX users in the Abilis of “Site 1” (the IAX phone and the PC with Zoiper) and one IAX user in the Abilis
of “Site2” (Asterisk).

45.4.2.1. “IaxPhone” user configuration.l

Add the user in the Abilis of “Site 1” and enable it to IAX :

[16:19:06] ABILIS_CPX_1:a user:iaxphone iax:yes

COMMAND EXECUTED

[16:20:23] ABILIS_CPX_1:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------

782
Draft IAX - Inter-Asterisk eXchange Draft

admin *** YES # # YES YES YES NO NO NO

guest NO # # NO NO NO NO NO NO
iaxphone YES # # NO NO NO NO YES NO

Give the new user the following characteristics:

• password: iaxphone

• host: 192.168.0.100

• simultaneous half-duplex calls: 2

• IAX number: 520

[16:20:35] ABILIS_CPX_1:s user:iaxphone pwd:iaxphone iax-host:192.168.0.100 iax-maxses-bid:2 iax-nu

COMMAND EXECUTED

[16:21:30] ABILIS_CPX_1:d user:iaxphone

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: iaxphone
ALIAS: iaxphone
ID: 11 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
IAX: YES
IAX-HOST: 192.168.000.100
IAX-SRCADD: SYS
IAX-PORT: 4569
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 2
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER: 520
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:
IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: SYS

783
Draft IAX - Inter-Asterisk eXchange Draft

IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER:
IAX-REM-PASS:
IAX-REM-AUTH: SYS
IAX-REM-REG: NO
-------------------------------------------------------------------------------

Tip
If the IAX-AUTH parameter is set to SYS, you must define, on the IAX Phone, the protocol specified in the
AUTH parameter of the CTIIAX resource as authentication algorithm (in the present case MD5).

45.4.2.2. “Zoiper” user configuration

Add the user in the Abilis of “Site 1” and enable it to IAX:

[16:26:23] ABILIS_CPX_1:a user:zoiper iax:yes

COMMAND EXECUTED

[16:26:27] ABILIS_CPX_1:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
iaxphone *** YES # # NO NO NO NO YES NO
zoiper YES # # NO NO NO NO YES NO

Configure the new user in the following way:

• password: zoiper

• host: dynamic (the PC receives the IP address from a DHCP server)

• half-duplex call: 1

• IAX number: 620

[16:26:33] ABILIS_CPX_1:s user:zoiper pwd:zoiper iax-host:dynamic iax-maxses-bid:1 iax-number:620

COMMAND EXECUTED

[16:27:19] ABILIS_CPX_1:d user:zoiper

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: zoiper
ALIAS: zoiper
ID: 9 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE

784
Draft IAX - Inter-Asterisk eXchange Draft

IAX: YES
IAX-HOST: DYNAMIC
IAX-SRCADD: SYS
IAX-PORT: (DYNAMIC)
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 1
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER: 620
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:
IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: SYS
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER:
IAX-REM-PASS:
IAX-REM-AUTH: SYS
IAX-REM-REG: NO
-------------------------------------------------------------------------------

Tip
If the IAX-AUTH parameter is set to SYS, you must define, on the Zoiper settings, the protocol specified in
the AUTH parameter of the Ctilax resource as authentication algorithm (in the present case MD5).

45.4.2.3. “Asterisk” user configuration

Add the user in the the Abilis of “Site 2” and enable it to IAX:

[16:28:42] ABILIS_CPX_2:a user:asterisk iax:yes

COMMAND EXECUTED

[16:31:41] ABILIS_CPX_2:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
asterisk YES # # NO NO NO NO YES NO

785
Draft IAX - Inter-Asterisk eXchange Draft

guest NO # # NO NO NO NO NO NO

Give the new user the following characteristics:

• password: asterisk;

• host: 217.1.2.2;

• simultaneous half-duplex calls: 10;

• IAX number: all the calls toward numbers starting with 7;

• enable the registration to the remote IAX node (Asterisk) using username “abilis”, password “swordfish” and MD5
authentication.

[16:34:46] ABILIS_CPX_2:s user:asterisk pwd:swordfish iax-host:217.1.2.2 iax-maxses-bid:10 iax-trun

iax-rem-auth:md5 iax-rem-reg:yes

COMMAND EXECUTED

[16:35:52] ABILIS_CPX_2:d user:asterisk

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: asterisk
ALIAS: asterisk
ID: 10 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
IAX: YES
IAX-HOST: 217.001.002.002
IAX-SRCADD: SYS
IAX-PORT: 4569
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 10
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER:
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:
IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS

786
Draft IAX - Inter-Asterisk eXchange Draft

IAX-NETSTATS: SYS
IAX-TRUNK: YES
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER: abilis
IAX-REM-PASS: *********
IAX-REM-AUTH: MD5
IAX-REM-REG: YES
-------------------------------------------------------------------------------

Tip
The IAX-NUMBER field of this user is empty, add a static routing in the CTIIAX translation table to route
toward this user the calls addressed to numbers starting with 7.

45.4.3. CTIIAX translation table

45.4.3.1. CTIIAX translation table of “Site 1”
Since we have specified the IAX-NUMBER parameter for the two IAX users of “Site 1”, the two routings will be
automatically connected in the table.

[17:02:10] ABILIS_CPX_1:d ctiiax

Total:2 Connected:2 Static:0

CDI: USERNAME: P:
----------------------------------------------------------
620 zoiper C
520 iaxphone C

45.4.3.2. CTIIAX transaltion table of “Site 2”

In the configuration of “Asterisk” user for Abilis of “Site 2”, we haven't specified any IAX-NUMBER, so the following chart
will be empty.

[17:00:48] ABILIS_CPX_2:d ctiiax

Total:0 Connected:0 Static:0

CDI: USERNAME: P:
----------------------------------------------------------
*** NO CTI IAX ENTRIES DEFINED ***

Add a static routing in the CTIIAX table to route the calls directed to the numbers starting with 7 to this user.

[17:15:44] ABILIS_CPX_2:a ctiiax numx:7* username:asterisk

COMMAND EXECUTED

[17:23:16] ABILIS_CPX_2:d ctiiax

- Not Saved (SAVE CONF) -------------------------------------------------------

Total:1 Connected:0 Static:1

NUMx: USER: P:
------------------------------------------------------------

787
Draft IAX - Inter-Asterisk eXchange Draft

7* asterisk S

45.4.4. CTI Routings configuration

45.4.4.1. CTI Routings of “Site 1”
The purpose is:

• to connect the IAX users (iaxphone and Zoiper);

• to connect the IAX users and the analog phone connected to the POTS on the Abilis of “Site 1”;

• to connect the IAX users and the analog phone connected to the POTS of “Site 2”;

• to forward the input calls of the ISDN line toward the remote Asterisk, in case the POTS telephone of Abilis is busy or
doesn't answer after 20 seconds.

45.4.4.1.1. Communication between the IAX users.

Add the routing:

[17:06:37] ABILIS_CPX_1:a ctir pr:1 type:itoi cdi:'numiax'

COMMAND EXECUTED

[17:06:46] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 10:56:23 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 ItoI CtiIax CtiIax 'NumIax' *
-------------------------------------------------------------------------------

[17:06:52] ABILIS_CPX_1:d list:numiax

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:NumIax - IN
Automatically_generated_CTI_IAX_Numbers_list_(ReadOnly)
520 620

Tip
Transcoding is not activated because SPOUT and CODERSOUT parameters are set to the default value *; set
the SP parameter value to a value greater than 6400 (default value) to increase the available coder pool.

[17:29:14] ABILIS_CPX_1:s ctir pr:1 sp:64000

COMMAND EXECUTED

788
Draft IAX - Inter-Asterisk eXchange Draft

[17:29:19] ABILIS_CPX_1:d ctire

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 10:57:22 CET

-------------------------------------------------------------------------------
PR:0 DESCR:
ACT:YES EDT:NO
TYPE:DATA POI:* POO:CtiSLink EEC:NO
NEXT:NO CDI:* CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
RGI:* RGO:*
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#
-------------------------------------------------------------------------------
PR:1 DESCR:
ACT:YES EDT:NO
TYPE:ItoI POI:CtiIax POO:CtiIax EEC:NO
NEXT:NO CDI:'NumIax' CDO:*
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
LCS:NO LCST:Sys RGI:* RGO:*
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:64000 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:*
SPOUT:* SCOUT:* DJOUT:* MJOUT:*
CODERSOUT:*
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

45.4.4.1.2. Communication between the analog phone and the IAX users.

Add the routings:

[17:30:57] ABILIS_CPX_1:a ctir pr:2 type:vtoi poi:pbx cdi:'numiax' sp:64000

COMMAND EXECUTED

[17:31:04] ABILIS_CPX_1:a ctir pr:3 type:itov poo:101 cdi:420 sp:64000

COMMAND EXECUTED

[17:31:13] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 10:58:57 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 ItoI CtiIax CtiIax 'NumIax' *

789
Draft IAX - Inter-Asterisk eXchange Draft

NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
2 VtoI PBX CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
3 ItoV CtiIax 101 420 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

The PR:2 routing, routes the calls coming from the Abilis POTS port toward the CTIIAX and directed to one number of the
numiax list. The CTIIAX routing table will forward the call to the user.

The PR:3 routing, routes toward port 101 (where the analog phone is connected) the calls coming from one of the IAX users
and directed to the number 420.

45.4.4.1.3. Communication between the IAX users and the remote analog phone.
Add the following routings:

[17:34:55] ABILIS_CPX_1:a ctir pr:4 type:itoc ds:site2 sp:64000 cdi:320

COMMAND EXECUTED

[17:35:05] ABILIS_CPX_1:a ctir pr:5 type:ctoi sr:* cdi:'numiax' sp:64000

COMMAND EXECUTED

[17:35:14] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 20/12/2010 11:00:04 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 ItoI CtiIax CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
2 VtoI PBX CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
3 ItoV CtiIax 101 420 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
4 ItoC CtiIax site2 320 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *

790
Draft IAX - Inter-Asterisk eXchange Draft

-------------------------------------------------------------------------------
5 CtoI * CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------

The PR:4 routing routes toward the Site 2 cluster the calls coming from IAX users and directed to the number 320 (the
analog phone of the remote site).

The PR:5 routing routes toward the Ctilax the calls coming from any cluster and directed to one of the numbers of the
numiax list (numbers given to the IAX users). The Ctilax translation table will forward the call to the user.

45.4.4.1.4. Transfer the incoming calls from the ISDN line towards Asterisk, in case the analog
phone of “Abilis 1” is busy or doesn't answer after 20 seconds.

Add the following routings:

[17:35:18] ABILIS_CPX_1:a ctir pr:6 poi:34 poo:101 cdi:* t301:20 next:t

COMMAND EXECUTED

[17:37:07] ABILIS_CPX_1:a ctir pr:7 type:vtoc poi:34 ds:site2 cdi:* cdo:701

COMMAND EXECUTED

[17:37:15] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 20/12/2010 11:03:04 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 ItoI CtiIax CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
2 VtoI PBX CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
3 ItoV CtiIax 101 420 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
4 ItoC CtiIax Clus2 320 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
5 CtoI * CtiIax 'NumIax' *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *

791
Draft IAX - Inter-Asterisk eXchange Draft

-------------------------------------------------------------------------------
6 TR 34 101 * *
TRANSFERT ANY NO 20 * *
-------------------------------------------------------------------------------
7 VtoC 34 Clus2 * 701
-------------------------------------------------------------------------------

The PR:6 routing routes toward port 101 (analog phone) the calls coming from the ISDN line (CTIP:34). In
case the telephone is busy or doesn't answer after 20 seconds (T301:20), the call is forwarded to the next routing
(NEXT:TRANSFERT).

The PR:7 routing routes the calls toward the Site 2 cluster; the numbers starting with 7 are sent to the remote Asterisk.

45.4.4.2. CTI Routings of Abilis of “Site 2”

The purpose is:

• to connect the analog phone of “Site2” and the IAX users of the Abilis of “Site 1”;

• to forward to Asterisk the calls coming from “Site 1” in case of the remote analog phone is busy or doesn't answer.

45.4.4.2.1. Communication between the IAX users and the remote analog phone.
Use normal routings for compressed phone calls:

[16:27:38] ABILIS_CPX_2:list create remoteiax IN

COMMAND EXECUTED

[16:27:38] ABILIS_CPX_2:list description remoteiax IAX_user's_number_of_site_1

COMMAND EXECUTED

[16:27:38] ABILIS_CPX_2:a list:remoteiax 520 620

COMMAND EXECUTED

[16:27:38] ABILIS_CPX_2:d list:remoteiax

- Not Saved (SAVE CONF) -------------------------------------------------------

LIST:RemoteIAX - IN
IAX_user's_number_of_site_1
520 620

[17:42:26] ABILIS_CPX_2:a ctir pr:1 type:ctov sr:* poo:101 cdi:320

COMMAND EXECUTED

[17:42:34] ABILIS_CPX_2:a ctir pr:2 type:vtoc poi:pbx ds:site1 cdi:'remoteiax'

COMMAND EXECUTED

[17:42:41] ABILIS_CPX_2:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 20/12/2010 11:05:51 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO

792
Draft IAX - Inter-Asterisk eXchange Draft

|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH

|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 CtoV * 101 320 *
-------------------------------------------------------------------------------
2 VtoC PBX site1 'remoteiax' *
-------------------------------------------------------------------------------

The PR:1 routing routes to port ctip:101 the calls coming from any cluster and addressed to the number 320.

The PR:2 routing routes the calls coming from an analog phone to the cluster site1, when the called number belongs to the
RemoteIAX list.

45.4.4.2.2. Transfer the incoming calls from Site 1 towards Asterisk, in case the analog remote
phone is busy or doesn't answer.

Add the routing:

[17:42:44] ABILIS_CPX_2:a ctir pr:3 type:ctoi sr:* cdi:7* sp:64000

COMMAND EXECUTED

[17:47:10] ABILIS_CPX_2:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 20/12/2010 11:05:51 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 CtoV * 101 320 *
-------------------------------------------------------------------------------
2 VtoC PBX Clus1 'remoteiax' *
-------------------------------------------------------------------------------
3 CtoI * CtiIax 7* *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------

The PR:3 routing routes toward CTIIAX resource the calls coming from any cluster; when the called number starts with 7 the
Ctilax routing table forwards the call toward to Asterisk.

Asterisk offers many options :

• answering service (saves the messages and sends them as mail enclosures);

• virtual answering service ( in case the called number gives no answer, Asterisk sends a mail containing the calling number
with data and time);

• operator service;

793
Draft IAX - Inter-Asterisk eXchange Draft

• ...

Tip
Asterisk offers many solutions of advanced call management (conference, answering service, operator
service…); to every service you can assign a specific code and manage them with a single routing.

The PR:3 routing forwards to Asterisk all the calls starting with 7: Configuring the routing of the remote
Abilis,the answering service can be assigned to number 701, the conferences to number 750, the operator to
number 711, etc…

The calls converge toward this Abilis, the PR:3 routing allows the matching, and Asterisk manages the calls
depending on the selected number.

45.5. Connecting Abilis and Asterisk

This section contains instructions for a correct set-up of Abilis CPX and Asterisk interconnection.

Tip
Abilis generates the alerting tone after RINGING when ALERTING without progress in-band-info is
received from CTIR. The audio is sent after RINGING acknowledgment. Alerting tone is generated
according to CTISYS tones configuration.

45.5.1. Checklist of parameters

Below there are the parameters which Abilis MUST send to Asterisk to allow him to complete the general context and to add
the Abilis context in /etc/asterisk/iax.conf file.

Asterisk Context Asterisk Parameter Description Value

general allow Allowed codecs. In local “alaw”, and “G729” if
environment G.711 should be available.
used; in Internet environment
G.729 is the best choice but
licence from Digium costs
10$ for each IAX2 channel.
G.711 is required for IAX
FAX.
general trunkfreq Frequency for metatrunking 40
bandwidth optimization, in
milliseconds.
general trunktimestamps Individual miniframe yes
timestamp inside metatrunk
frame.
abilis type User rights ( to call and be friend
called ).
abilis username The username with which Value of USER parameter in
Asterisk presents itself to Abilis Users table.
Abilis.
abilis secret The password with which Value of PWD and IAX-
Asterisk authenticates to REM-PASS parameters in
Abilis, and vice versa Abilis Abilis CPX Users table. For
authenticates to Asterisk. simplicity we use a single
user in Asterisk (the context
abilis), and this requires that
in Abilis PWD and IAX-
REM-PASS are set identical.
abilis host The Abilis IP Address or <ABILIS_IP_ADDRESS> or
FQDN. <ABILIS_FQDN>

794
Draft IAX - Inter-Asterisk eXchange Draft

Asterisk Context Asterisk Parameter Description Value

abilis trunk Allow metatrunking yes

45.5.2. Activation of the CTIIAX resource

For the activation of the CTIIAX resource refer to Section 45.1.1, “Activating the CTIIAX resource”.

In common use, you don't need to configure all the listed parameters, many of them belong to the IAX protocol advanced
options. The basic options are:

• ACT: to activate the resource.

• sesnum: to define the amount of simultaneous connections.

• SRCADD: source IP address for outgoing connections [R-ID: the source IP address of the outgoing datagrams will be set
to the current RouterID value; OUT-IP: the source IP address of the outgoing datagrams will be set on the base of the
output IP interface; 1-126.x.x.x, 128-223.x.x.x: the source IP address of the outgoing datagrams will be set to
the selected value; Ip-nnn: use the current IPADD of the specified IP resource].

Tip
If Abilis has only one IP resource (and therefore only one IP address) , you can use the default value;
otherwise if Abilis has more IP resoures and more IP addresses the suggested configuration is OUT-IP.

45.5.3. Example 1: Abilis and Asterisk have static IP addresses

Assumptions:

• Abilis has the static IP address 192.168.1.254.

• Asterisk has the static IP address 192.168.1.100.

• Abilis has an IAX user called “asterisk” with password “swordfish”.

• Asterisk provides advanced services like IVR and voice mail: suppose that 10 sessions are needed.

Now you have to create an IAX user representing Asterisk.

[14:49:07] ABILIS_CPX:a user:asterisk pwd:swordfish iax:yes iax-host:192.168.1.100 iax-maxses-bid:1

COMMAND EXECUTED

[14:49:07] ABILIS_CPX:s user:asterisk iax-number:* iax-trunk:yes iax-rem-user:abilis iax-rem-pass:s

COMMAND EXECUTED

Below the result is displayed (emphasized parameters are the values different from defaults):

[14:49:07] ABILIS_CPX:d user:asterisk

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------

795
Draft IAX - Inter-Asterisk eXchange Draft

USER: asterisk
ALIAS: asterisk
ID: 9 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
IAX: YES
IAX-HOST: 192.168.001.100
IAX-SRCADD: SYS
IAX-PORT: 4569
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 10
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER: *
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:
IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: YES
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS
IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER: abilis
IAX-REM-PASS: *********
IAX-REM-AUTH: MD5
IAX-REM-REG: YES
-------------------------------------------------------------------------------

The CTIIAX table, used to route calls toward IAX users, gets automatically populated with a unique route because you set
IAX-NUMBER:*.

[14:49:07] ABILIS_CPX:d ctiiax

- Not Saved (SAVE CONF) -------------------------------------------------------

Total:1 Connected:1 Static:0

NUMx: USER: P:

796
Draft IAX - Inter-Asterisk eXchange Draft

------------------------------------------------------------
* asterisk C

The asterisk configuration file /etc/asterisk/extensions.conf must contain a context for managing the calls. For
our convenience we use here the name from-abilis:

[from-abilis]
exten => 123,1,Answer() ; answer, play, hangup
exten => 123,2,Playback(welcome)
exten => 123,3,Hangup

exten => 222,1,Answer() ; answer, play, forward call to another number (999)
exten => 222,2,Playback(welcome)
exten => 222,3,Dial(IAX2/abilis/999)

The asterisk configuration file /etc/asterisk/iax.conf must be modified to include the following lines in the
general context:

[general]
disallow=all ; first disallow every coder
allow=alaw ; then enable only G.711 A-law
trunkfreq=40 ; trunkfrequency 40 msec
trunktimestamps=yes ; individual miniframes timestamp

and the following lines in the abilis context:

[abilis]
type=friend
username=asterisk ;the same of USER in Abilis
secret=swordfish ;the same of PWD and IAX-REM-PASS in Abilis
host=192.168.1.254 ;Abilis static address
context=from-abilis ;name of the desired context from extensions.conf
trunk=yes ;enable trunking

Caution
Remember to reload the Asterisk service.

Abilis and Asterisk interconnection is now correctly configured.

45.5.4. Example 2: Abilis has a static address and Asterisk has a

dynamic address

Assumptions:

• Abilis has the static IP address 192.168.1.254.

• Asterisk has a dynamic IP address.

• Abilis has an IAX user called “asterisk” with password “swordfish”.

• Asterisk provides advanced services like IVR and voice mail: suppose that 10 sessions are needed.

The steps are the same as in the Section 45.5.3, “Example 1: Abilis and Asterisk have static IP addresses”,there is just one
parameter different in Abilis and one directive to add in Asterisk configuration.

797
Draft IAX - Inter-Asterisk eXchange Draft

Add the user:

[14:49:07] ABILIS_CPX:a user:asterisk pwd:swordfish iax:yes

COMMAND EXECUTED

or set it to DYNAMIC if the user is already present.

[14:49:07] ABILIS_CPX:s user:asterisk iax-host:dynamic

COMMAND EXECUTED

The Abilis user configuration differs from Section 45.5.3, “Example 1: Abilis and Asterisk have static IP addresses” by the
fields emphasized below :

[14:49:07] ABILIS_CPX:d user:asterisk

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: asterisk
ALIAS: asterisk
ID: 9 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
IAX: YES
IAX-HOST: DYNAMIC
IAX-SRCADD: SYS
IAX-PORT: (DYNAMIC)
IAX-IP-PERMIT: *
IAX-MAXSES-BID: 10
IAX-MAXSES-IN: 0
IAX-MAXSES-OUT: 0
IAX-NUMBER: *
IAX-CG-NUM: AUTO
IAX-FWD-CG-NUM: CALLER
IAX-CTIP-TYPE: SYS
IAX-RG-IN: SYS
IAX-ROUTE-BY-SD: NO
IAX-PROVIDE-SG: NO
IAX-CLIP-RULE: SYS
IAX-BUSY-NOCHAN: NO
IAX-LCS-GROUP: NONE
IAX-CPO: SYS
IAX-CPO-STATE: SYS
IAX-CPO-DROP: SYS
IAX-SS: NO
IAX-SS-PICKUP: NO
IAX-SS-PRES-CG: YES
IAX-SS-CF-DND: YES
IAX-CONTEXT:
IAX-PROVIDE-NAME: BLANK
IAX-AUTH: SYS
IAX-NETSTATS: SYS
IAX-TRUNK: YES
IAX-TRUNK-FREQ: SYS
IAX-TRUNK-TS: SYS

798
Draft IAX - Inter-Asterisk eXchange Draft

IAX-CHAN-FREQ: SYS
IAX-TRANSFER: SYS
IAX-DISC-AUDIO: SYS
IAX-HTML-IN: SYS
IAX-HTML-OUT: SYS
IAX-REM-USER: abilis
IAX-REM-PASS: *********
IAX-REM-AUTH: MD5
IAX-REM-REG: YES
-------------------------------------------------------------------------------

The asterisk configuration file /etc/asterisk/iax.conf must be modified to include in the general context the
register directive:

[general]
disallow=all ; first disallow every coder
allow=alaw ; then enable only G.711 A-law
trunkfreq=40 ; trunk frequency 40 msec
trunktimestamps=yes ; individual miniframes timestamp

register=>asterisk:[email protected] ;activate registration TO abilis

Caution
Remember to reload the Asterisk service.

Abilis and Asterisk interconnection is now correctly configured.

45.5.5. CTI Routings configuration

In order to route calls to and from the CTIIAX resource, adding the appropriate routings in the CTIR table is needed.

45.5.5.1. Any coder, transcoding disallowed

In this example every call arriving from ISDN/POTS/GSM/CLUSTER is routed to IAX users, and every call arriving from
IAX users is first sent to cluster test; in case of failure (NEXT:LIMITED) it is attempted on ISDN/POTS/GSM group G1.

In this situation any coder with maximal speed 6400 (the default for SP parameter) is allowed, but transcoding is disallowed,
which means that the same coder must be used in Asterisk and in the Abilis where a CtoV or CtoI routing will terminate the
call to an ISDN/POTS/GSM port or to another IAX user.

Cluster test is only useful to the example, any cluster can be used.

[14:49:07] ABILIS_CPX:a ctir pr:0 type:vtoi poi:* cdi:*

COMMAND EXECUTED

[14:49:28] ABILIS_CPX:a ctir pr:1 type:ctoi sr:* cdi:*

COMMAND EXECUTED

[14:50:06] ABILIS_CPX:a ctir pr:2 type:itoc ds:test cdi:* next:limited

COMMAND EXECUTED

[14:50:08] ABILIS_CPX:a ctir pr:3 type:itov poo:g1 cdi:*

COMMAND EXECUTED

[14:50:15] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 09:41:16 CET

799
Draft IAX - Inter-Asterisk eXchange Draft

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 VtoI * CtiIax * *
-------------------------------------------------------------------------------
1 CtoI * CtiIax * *
-------------------------------------------------------------------------------
2 ItoC CtiIax test * *
LIMITED ANY NO Dft * *
-------------------------------------------------------------------------------
3 ItoV CtiIax G1 * *
-------------------------------------------------------------------------------

Tip
Set SP:8000 in every routing to allow G.729A .

45.5.5.2. Only G.711 on Asterisk, any coder on Cluster, transcoding allowed

In this example every call arriving from ISDN/POTS/GSM/CLUSTER is routed to IAX users, and every call arriving from
IAX users is first sent to cluster test, and in case of failure (NEXT:LIMITED) it is attempted on ISDN/POTS/GSM group
G1.

In this situation only G.711 A-law or u-law is possible between Asterisk and Abilis, but since transcoding is enabled by
CODERSOUT <> * the ItoC and CtoI routings will negotiate for the “C” side any coder with maximal speed up 6400 bps.

[15:26:02] ABILIS_CPX:a ctir pr:0 type:vtoi poi:* cdi:* sp:64000

COMMAND EXECUTED

[15:26:10] ABILIS_CPX:a ctir pr:1 type:ctoi sr:* cdi:* spout:64000 codersout:G.711

COMMAND EXECUTED

[15:26:22] ABILIS_CPX:a ctir pr:2 type:itoc ds:test cdi:* next:limited sp:64000 coders:g.711 spout:

COMMAND EXECUTED

[15:26:36] ABILIS_CPX:a ctir pr:3 type:itov poo:g1 cdi:* sp:64000

COMMAND EXECUTED

[15:26:44] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 09:42:59 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO

800
Draft IAX - Inter-Asterisk eXchange Draft

|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO

| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 VtoI * CtiIax * *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
1 CtoI * CtiIax * *
NO ANY NO Dft * *
6400 Sys * * Sys Sys * *
64000 * * * NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO
*
G.711
-------------------------------------------------------------------------------
2 ItoC CtiIax test * *
LIMITED ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
6400 * * * NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO
G.711
*,Sys
-------------------------------------------------------------------------------
3 ItoV CtiIax G1 * *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

Tip
To allow G.729A you have to set SP:8000 in CtoI PR:1 and SPOUT:8000 in ItoC PR:2.

45.5.5.2.1. Transcoding optimisation

When the Abilis-Asterisk interconnection occurs via local LAN, i.e. with high speed, minimal delays, minimal jitter, the
transcoding can be optimized so that the Asterisk side uses minimal jitter, therefore minimal delays, while the WAN side
uses the values optimal for WAN link.

This is obtained by properly setting DJ, MJ, DJOUT, MJOUT. For example, type:

[15:32:28] ABILIS_CPX:s ctir pr:1 djout:0 mjout:80

COMMAND EXECUTED

[15:42:21] ABILIS_CPX:s ctir pr:2 dj:0 mj:80 djout:sys mjout:sys

COMMAND EXECUTED

Tip
DJ and MJ in pr:1 as well as DJOUT and MJOUT in pr:2 may assume other values appropriate for the
WAN link or specifically required by calls matching the routing.

45.5.5.2.2. Fax

When transcoding takes place in IoC and CtoI, with G.711 toward Asterisk FAX relay can be used! It means that if your
asterisk is properly set-up to manage faxes via G.711 coder, you can exchange FAX with following characteristics:

801
Draft IAX - Inter-Asterisk eXchange Draft

• use G.711, 64 kbps plus IP overhead on the Abilis-Asterisk interconnection;

• use G3 Fax relay, 2400/4800/9600/14400 kbps plus IP overhead on the WAN link.

If you want to forcedly disable fax relay you have just to set FMRELAY:NO in the desired routing, e.g.:

[15:48:21] ABILIS_CPX:s ctir pr:0 fmrelay:no

COMMAND EXECUTED

[15:48:35] ABILIS_CPX:s ctir pr:1 fmrelay:no

COMMAND EXECUTED

[15:49:01] ABILIS_CPX:s ctir pr:2 fmrelay:no

COMMAND EXECUTED

[15:49:29] ABILIS_CPX:s ctir pr:3 fmrelay:no

COMMAND EXECUTED

45.6. CTIIAX diagnostics and statistics

45.6.1. CTIIAX diagnostics
Use the following commands to display the diagnostics of the CTIIAX resource:

d d ctiiax Shows diagnostic information, such as the state of the resource, the currently used channels, the remote
IAX username/address/port, the calling and the called number.

d de ctiiax Shows diagnostic information in an extended format: the same information listed for d d ctiiax command
and the state of Unattended/Attended Call Transfer, the minimum/average/maximum lag value during the
call and the jitter value (calculated as variance of the lag) in least 10 seconds.

[22:15:27] ABILIS_CPX:d d ctiiax

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
STATE:ACTIVE UDP-STATE:OPENED USED-CHAN:1
- IAX Channels diagnostics ---------------------------------------------
CH: IAXState User RemAdd-RemPort
Q931State CallId CG CD
------------------------------------------------------------------------
0 CONNECTED asterisk160 192.168.000.253-4569
10-CONNECTED-TO 636 9916 749
------------------------------------------------------------------------
1 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
2 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
3 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
4 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
5 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
6 DISCONNECTED

802
Draft IAX - Inter-Asterisk eXchange Draft

00-DISCONNECTED
------------------------------------------------------------------------
7 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
8 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
9 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------

[22:15:30] ABILIS_CPX:d de ctiiax

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
STATE:ACTIVE UDP-STATE:OPENED USED-CHAN:1
- IAX Channels diagnostics ---------------------------------------------
CH: IAXState User RemAdd-RemPort
Q931State CallId CG CD
Q932State UCTState ACTState CPOState
MinLag MaxLag AvgLag LastLag 10sec-JitterLag
------------------------------------------------------------------------
0 CONNECTED asterisk160 192.168.000.253-4569
10-CONNECTED-TO 636 9916 749
IDLE - - -
- - - - -
------------------------------------------------------------------------
1 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
2 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
3 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
4 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
5 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
6 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
7 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
8 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
9 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------

45.6.2. CTIIAX statistics

Use the following commands to display the statistics of the CTIIAX resource:

d s ctiiax Shows statistic information, such as the number of incoming/outgoing accepted/rejected calls, the number
of incoming/outgoing succesful/failed registrations, the number of incoming/outgoing succesful/failed
transmission requests.

803
Draft IAX - Inter-Asterisk eXchange Draft

d se ctiiax Shows statistic information in an extended format: the same information listed for d se ctiiax command
are shown for each session.

[22:15:27] ABILIS_CPX:d s ctiiax

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
--- Cleared 45 days 03:25:16 ago, on 07/11/2007 at 18:50:14 ------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 1023| 5569|FAIL-CALL | 53| 1304|
SUCC-REG | 51217| 12807|FAIL-REG | 12| 52198|
SUCC-QUAL | 0| |FAIL-QUAL | 31| |
SUCC-TRAN | 2520| |FAIL-TRAN | 1018| |
SUCC-TXREQ | 0| 0|FAIL-TXREQ | 0| 0|
EXP-RETRY | 12| 53530|DTMF | 34| 100|
QUELCH | 2461| |UNQUELCH | 2416| |
LOST-JITTER| | 0|OUTSEQ-FULL| 21| |
LOST-NOBUF | 0| 0|OUTSEQ-MINI| 7| |
BLACKLISTED| 0| |UNSUPPORTED| 0| 0|
TRUNK-OVR | | 0|
------------------------------------------------------------------------

[22:15:30] ABILIS_CPX:d se ctiiax

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
--- Cleared 45 days 03:25:23 ago, on 07/11/2007 at 18:50:15 ------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 1023| 5569|FAIL-CALL | 53| 1304|
SUCC-REG | 51217| 12807|FAIL-REG | 12| 52198|
SUCC-QUAL | 0| |FAIL-QUAL | 31| |
SUCC-TRAN | 2520| |FAIL-TRAN | 1018| |
SUCC-TXREQ | 0| 0|FAIL-TXREQ | 0| 0|
EXP-RETRY | 12| 53530|DTMF | 34| 100|
QUELCH | 2461| |UNQUELCH | 2416| |
LOST-JITTER| | 0|OUTSEQ-FULL| 21| |
LOST-NOBUF | 0| 0|OUTSEQ-MINI| 7| |
BLACKLISTED| 0| |UNSUPPORTED| 0| 0|
TRUNK-OVR | | 0|
------------------------------------------------------------------------
CH:0 CallId:24026 CG:3381834848 CD:601
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 334| 301|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:1 CallId:17799 CG: CD:621
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:2 CallId:1488 CG:671 CD:601
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 1184| 1178|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:3 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|

804
Draft IAX - Inter-Asterisk eXchange Draft

------------------------------------------------------------------------
CH:4 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:5 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:6 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:7 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:8 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------
CH:9 CallId:0 CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
VOICE-FRM | 0| 0|LOST | 0| |
OUTSEQ-FULL| 0| |LOST-JITTER| | 0|
OUTSEQ-MINI| 0| |LOST-NOBUF | | 0|
------------------------------------------------------------------------

45.6.3. Debug of the CTIIAX resource

Below debug commands are described. They are useful to view the authentication/registration logs and the registered IAX
users table.

Note
To use these commands you need to have administrator or super user rights.

Type the following command to display the syntax:

[14:09:58] ABILIS_CPX:debug res:ctiiax lsn:0

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
BufferLength:931 Date/Time:29/06/2007 14:10:00 TraceTime:4812354

Usage:

LSN:0 - This help

LSN:1 - Extra channels diags
LSN:2 - Show transferring diags
LSN:3 - Show debug log
LSN:3 CMD:CLR - Clear debug log

805
Draft IAX - Inter-Asterisk eXchange Draft

LSN:3 CMD:SET:[DFT | CLR | FULL | [level,...]] - Set log event mask

No parameters - Show current events log mask
DFT - Log default events (ERR events only)
CLR - Clear log event mask
FULL - Log all events
levels:
ERR - Log only error events
REG - Registration events
INFO - Informative events
LSN:4 - Show registered users
LSN:10 CMD:UserName - Force Abilis registration with this user
LSN:11 CMD:UserName - Force User unregisterring.

Type the following command to display the event logs connected with the users registation:

[18:04:09] ABILIS_CPX:debug res:ctiiax lsn:3

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
BufferLength:16243 Date/Time:28/06/2007 18:05:56 TraceTime:<NotRunning>

DD/MM/YYYY HH:MM:SS - CALLID DESCRIPTION

28/06/2007 16:20:03 - [17449] Error in IN channel with 192.168.0.167:4569
28/06/2007 16:20:03 - [17449] Retransmission out of time FF 6, 14
28/06/2007 16:20:28 - [17451] Error in OUT channel with 192.168.0.100:4569
28/06/2007 16:20:28 - [17451] Password is not valid, peer:iaxphone

This table shows data, time, identification of the event and the description of the error.

Possible errors could be:

• unknown user;

• codec not supported;

• retransmission out of time (happens when you are cut off).

Most common usage are:

• debug res:ctiiax lsn:3 : shows log;

• debug res:ctiiax lsn:3 cmd:clr : clear log;

• debug res:ctiiax lsn:3 cmd:set:err : set log mask to log only errors events;

• debug res:ctiiax lsn:3 cmd:set:err,reg : set log mask to log only errors and registration events;

• debug res:ctiiax lsn:3 cmd:set:full : set log mask to log any event.

The following command shows the registration table (remote peers registered with Abilis and remote peers Abilis is
registered to). Registration in IAX is a way to avoid NAT troubles and mantain connectivity between IAX peers.

[17:03:12] ABILIS_CPX:debug res:ctiiax lsn:4

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
BufferLength:324 Date/Time:18/01/2008 11:24:47 TraceTime:<NotRunning>

User Host Port REG LIFETIME AGE

-------------------------------------------------------------------------------
asterisk 192.168.000.250 4569 REMOTE 60 12
zoiper 192.168.000.024 4569 LOCAL 60 35
-------------------------------------------------------------------------------

Meaning of the parameters:

User Username registered in the user table (d user).

806
Draft IAX - Inter-Asterisk eXchange Draft

Host IP address of the user.

Port UDP port of the user.

REG Registration of the user [REMOTE: Abilis is registered to a remote peer; LOCAL: a remote peer is registered to
Abilis].

LIFETIME How often (in seconds) the registration is requested.

AGE Time (in seconds) since last valid registration.

In the previous example, Abilis is registered to the remote peer asterisk (ip address: 192.168.0.250) which needs Abilis
registration each 60 seconds; Abilis registered itself 12 seconds ago.

The user zoiper (ip address: 192.168.0.24) is registered to Abilis; it registered itself 35 seconds ago.

45.7. Appendix - IAX protocol

IAX is the Inter Asterisk eXchange1 protocol used by Asterisk2, a PBX3 open source server from Digium. It provides
control and transmission of any type of streaming media over Internet Protocol (IP) networks, including video but is targeted
primarly at the control of IP voice calls.

IAX now most commonly refers to IAX2, the Version 2 of the IAX protocol. The original IAX protocol has been deprecated
almost universally in favor of IAX2; subsequent references to IAX, in this tutorial, refer to Version 2.

The primary design goals for the IAX protocol are: minimize bandwidth usage for both control and media with specific
emphasis on individual voice calls and provide native support for Network Address Translation (NAT).

IAX is a peer-to-peer media and signaling protocol; the signaling component is similar to the Session Initiation Protocol
(SIP). With respect to media, sequencing and timing information is included in IAX frames.

The basic design approach for IAX multiplexes signaling and multiple media streams over a single User Datagram Protocol
(UDP) association between two Internet hosts. In this facet of its design, it is actually two protocols in one, a protocol for
signaling sessions and a protocol for transporting the actual media streams themselves. This approach differs from the overall
architecuture of other IETF-based protocols that separate the control (SIP) and media stream (RTP/RTCP) components using
different protocols. Because signaling and media share the same UDP port number (4569) , IAX does not suffer from the
NAT traversal problems associated with SIP.

Tip
Interesting links: The IAX protocol.4

1
http://en.wikipedia.org/wiki/IAX
2
http://www.asterisk.org/
3
http://en.wikipedia.org/wiki/Pbx

807
Draft Draft

Chapter 46. SIP - Session Initiation

Protocol
Marco Bellesia
Luigi Demuro
Alfredo Sorbello

Table of Contents
46.1. CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.1. Activating the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
46.1.2. CTISIP resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
46.2. CTISIP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.1. Users table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
46.2.2. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
46.3. CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
46.4. Example of configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
46.4.1. Activation and configuration of the CtiSip resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.2. Users configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
46.4.3. CTISIP translation table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
46.4.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
46.5. Connecting Abilis and a SIP proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.1. Activation of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.2. Example: Abilis and a proxy registered in Abilis domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
46.5.3. Example: Proxy and Abilis registered in Proxy remote domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
46.5.4. CTI Routings configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
46.6. Busy Lamp Field (BLF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.1. Dialog an presence monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
46.6.2. BLF in Abilis CPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
46.7. CTISIP diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
46.7.1. CTISIP diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
46.7.2. CTISIP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
46.7.3. Debug of the CTISIP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
46.8. Appendix - SIP protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.1. SIP and NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
46.8.2. Solution to SIP NAT trasversal problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
46.8.3. SIP NAT Trasversal problem with Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840

46.1. CTISIP resource

The Abilis SIP driver provides gateway functionalities between SIP and ISDN networks for audio services only; it is not
intended to support full SIP to SIP videoconferencing gateway. The Abilis SIP driver can be interfaced with:

• Physical Volp telephones with SIP support;

• Softphone program for PC;

• PBX Digium Asterisk.

46.1.1. Activating the CTISIP resource

Add the resource to the Abilis system with the following command.

808
Draft SIP - Session Initiation Protocol Draft

[09:08:14] ABILIS_CPX:a res:ctisip

RES:CTISIP ALREADY EXISTS

The CTISIP resource may already exist in the system, but may not yet be active: set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctisip

COMMAND EXECUTED

Caution
After adding or setting the CTISIP active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[11:01:39] ABILIS_CPX:s p ctisip act:yes

COMMAND EXECUTED

Caution
Execute the initialization command init res:ctisip to activate the changes made on the upper case
parameters. Use the command save conf and restart Abilis (i.e. with warm start command) to set act the
changes made on the lowercase parameters.

46.1.2. CTISIP resource parameters

Use the command d p ctisip to show the parameters of the resource and use the command d p ctisip ? to display the meaning
of the parameters.

[11:02:19] ABILIS_CPX:d p res:ctisip

RES:CtiSip --------------------------------------------------------------------
Run DESCR:Session_Initiation_Protocol
LOG:NO ACT:YES mxps:2172
sesnum:10 non-invite-sesnum:50 tcp-sesnum:10
tcp-locport:5060 UDP-PORT-BASE:6000 SIP-TOS:0-N
udp-locport:5060 UDP-PORT-RANGE:200 RTP-TOS:0-D
SRCADD:OUT-IP
EXTERNAL-IP:OUT-IP
IPSRC:* IPSRCLIST:#
SUB-LIFETIME:180 max-sub:100
AUTH:DIGEST KEEPALIVE:90 CTIP-TYPE:USER
LIFETIME:120 DISC-AUDIO:NO NP-CT:SYS
REM-AUTH:DIGEST T1:500 ROUTING:EN-BLOC
REM-LIFETIME:120 T2:4 DIALT:5
AUTH-TOUT:4 T4:5 T302:15
AUTH-TOUT-INVITE:4 CHAN-FREQ:20 ROUTE-BY-SD:NO
DTMF-MODE:RFC2833 T38:NO PROVIDE-SG:NO
PLAY-DTMF:100 T38-G711:NO CLIP-RULE:PRIVATE
PLAY-SILENCE:100 T38-PACKING:1 RG-IN:DISABLE
DETECT-DTMF:40 T38-REDUND:REDUNDANCY CPO-RTP:NO
DETECT-SILENCE:40 T38-REDUND-PCK:1 CPO-SIGNALLING:NO
DOMAIN:
UA:AUTO (Abilis CPX - Ver. 3570/STD-D - Build 3570)

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime CTISIP activation/deactivation.

sesnum Maximum number of SIP simultaneous sessions.

809
Draft SIP - Session Initiation Protocol Draft

non-invite-sesnum Number of SIP sessions/dialogs initiated by NON-INVITE methods: i.e. Register, Subscribe and
Notify.

tcp-ses Number of reserved TCP sessions available for SIP channels; this value must not be greater than
sesnum [0..254, AUTO: inherit value from sesnum].

tcp-locport Local TCP port of SIP protocol.

udp-locport Local UDP port of SIP protocol.

UDP-PORT-BASE Base local UDP port usable for RTP/RTCP sessions; this feature is required to assign high
priority to RTP/RTCP packets.

UDP-PORT-RANGE Range of permitted local UDP ports usable for RTP/RTCP sessions; this value must not be lower
than (sesnum * 2 + 50).

SIP-TOS Sets the TOS value for SIP protocol.

RTP-TOS Sets the TOS value for RTP protocol.

SRCADD Source IP address for outgoing connections [R-ID: the source IP address of the outgoing
datagrams will be set to the current RouterID value; OUT-IP: the source IP address of the
outgoing datagrams will be set on the base of the output IP interface; 1-126.x.x.x,
128-223.x.x.x: the source IP address of the outgoing datagrams will be set to the selected
value; Ip-nnn: use the current IPADD of the specified IP resource].

EXTERNAL-IP Abilis external IP address. [R-ID: the source IP address of the outgoing datagrams will be set
to the current RouterID value; OUT-IP: the source IP address of the outgoing datagrams will be
set on the base of the output IP interface; 1-126.x.x.x, 128-223.x.x.x: the source IP
address of the outgoing datagrams will be set to the selected value]. When OUT-IP or R-ID are
set, the address must be determined at the call start and must not change until call end.

IPSRC Specifies which client's IP address is allowed to access and called by SIP server; a client is
accepted if it also satisfies SIP-IP-PERMIT specified in User table.

IPSRCLIST Name of the IP address list (IP/IR/RU/MR) from which the request for access can be accepted; a
client is accepted if it also satisfies SIP-IP-PERMIT specified in User table.

SUB-LIFETIME Expiration time of incoming subscriptions.

max-sub Maximum number of subscriptions that CTISIP may handle independently from the event type,
the subscriber and the monitored resource.

AUTH Authentication method offered to authenticating/registering users (incoming calls/registrations).

REM-AUTH Authentication method when Abilis is authenticating/registering to a peer (outgoing calls/

registrations).

LIFETIME Default duration of incoming registration; users must register themselves before this time interval
expires.

REM-LIFETIME Default duration of outgoing registration; Abilis must register before this time interval expires.

AUTH-TOUT SIP NOT-INVITE authentication timeout for incoming/outgoing calls initiated by REGISTER
method.

AUTH-TOUT-INVITE SIP INVITE authentication timeout for incoming/outgoing calls initiated by INVITE method.

KEEPALIVE Session keepalive time; when this session inactivity timer expires a RE-INVITE or UPDATE
message is sent.

CTIP-TYPE CTIP type assigned to CTISIP driver.

NP-CT Enables/disables Net-Public to Net-Public call transfer [NO: NP to NP disabled; YES: NP to NP

enabled, except when both calls are outgoing, which is not allowed to avoid the “hang trunk”
problem; SYS: NP to NP depends on NP-CT in CtiSys].

ROUTING Routing management [PREFIX, EN-BLOC].

810
Draft SIP - Session Initiation Protocol Draft

DIALT Dialing timeout.

T302 Timeout for “empty” setup.

ROUTE-BY-SD It allows routing using subaddress called field (SD) [NO: the SD is completely ignored; YES: the
user corresponding to SD is searched: if found the call is forwarded to that user, otherwise the
standard search in CTISIP table is performed; USER: the user corresponding to SD is searched: if
found and the user has parameter SIP-ROUTE-BY-SD:YES, the call is forwarded to that user,
otherwise the standard search in CTISIP table is performed].

PROVIDE-SG Allows insertion of SIP USER NAME in subaddress calling field [NO: disable insertion
of USERNAME in calling subaddress; YES: enable insertion of USERNAME in calling
subaddress; USER: insertion of USERNAME in calling subaddress depends on individual user
configuration]. When it is enabled, either as result of value YES or because value is USER and
the user corresponing to the subaddress content allows it, the call sent to CTIR will include in the
subaddress calling field the SIP USER NAME of the caller.

DTMF-MODE DTMF mode used by CTISIP in outgoing DTMF [INBAND: the outband DTMF received from
CTIR is not dropped, only the audio stream is passed; INFO: the outband DTMF received from
CTIR is sent using INFO message; RFC2833: the outband DTMF received from CTIR is sent
using RFC2833 payload].

PLAY-DTMF Duration of a DTMF played from a DTMF FULL FRAME. When CTISIP has to convert a
DTMF FULL FRAME command to CTIR DTMF frame, it produces as many frames as needed
to cover the period specified by this parameter. The actual interval must be rounded to the value
immediately higher than configured one.

PLAY-SILENCE Duration of a silence played after a PLAY-DTMF. When CTISIP has to convert a DTMF FULL
FRAME command to CTIR DTMF frame, it produces as many frames as needed to cover the
perios specified by PLAY-DTMF parameter. Before a new DTMF can be played, a silence period
must elapse, and this is controlled by this parameter.

DETECT-DTMF Duration of a DTMF from CTIR in order to allow digit recognition. When CTISIP received
DTMF frames from CTIR, and after it created the most accurate and monotonical timestamp,
the DTMF length is measured and for a successful digit recognition it must be of at least the
length specified here. If the configured value is not an exact multiple of the frame rate, it must be
rounded to the next upper value multiple of frame rate.

DETECT-SILENCE Duration of a silence after a DTMF from CTIR in order to recognise a digit.

T1 SIP T1 time; Round Trip Time (RTT) estimate.

T2 SIP T2 time; maximum retransmission interval for NON-INVITE requests and INVITE
responses.

T4 SIP T4 time; maximum duration that a message can remain in the network.

CHAN-FREQ Channel frequency for bandwidth optimisation. It represents how many msec of voice are desired
to be packed into a single UDP packet; it's a “desire” in the sense that the actual optimisation will
depend on the frame length in msec of the coder in use, and the result will be an a approximation
by defect.C

CPO-RTP Enables/disables Call Path Optimization between two SIP users. It is used when SIP-CPO:SYS
in user service, otherwise the value of SIP-CPO is used.

DOMAIN Domain for local users. If Abilis has clients in the public side you can also specify a FQDN.

The following command allows the administrator to change the configuration of the resource:

s p ctisip parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ctisip; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

811
Draft SIP - Session Initiation Protocol Draft

46.2. CTISIP tables

46.2.1. Users table
SIP users must be registrated in the Users table. All the parameters, mandatory for the registration, the authentication and the
SIP identification are defined in each Abilis user's profile.

Use the below command to display the parameters of the users; the d user: ? command shows the meaning of all parameters.

[11:15:19] ABILIS_CPX:d user

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
test *** YES # # NO NO YES NO NO YES

Type the following command to view user's details:

[11:15:19] ABILIS_CPX:d user:test

Parameter: | Value:
------------------+------------------------------------------------------------
USER: test
ALIAS: test
ID: 4 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: OPERATOR
OPC-VIEW: *
OPC-MONITOR: SIP
OPC-HIDE-NUMBERS: NO
OPC-PRIVACY: NO
HTTP: YES
HTTP-PROT: PLAIN,SSL
SIP: YES
SIP-TYPE: PHONE
SIP-DOMAIN: SYS
SIP-HOST: DYNAMIC
SIP-TCP-REMPORT: (DYNAMIC)
SIP-UDP-REMPORT: (DYNAMIC)
sip-udp-locport: SYS
SIP-SRCADD: SYS
SIP-PROT-IN: TCP,UDP
SIP-PROT-OUT: UDP
SIP-IP-PERMIT: *
SIP-MAXSES-BID: 4
SIP-MAXSES-IN: 0
SIP-MAXSES-OUT: 0
SIP-NUMBER: 10
SIP-CG-NUM: AUTO
SIP-FWD-CG-NUM: CALLER
SIP-CTIP-TYPE: SYS
SIP-RG-IN: SYS
SIP-ROUTE-BY-SD: NO
SIP-PROVIDE-SG: NO
SIP-CLIP-RULE: SYS
SIP-BUSY-NOCHAN: NO
SIP-LCS-GROUP: NONE

812
Draft SIP - Session Initiation Protocol Draft

SIP-CPO-RTP: SYS
SIP-CPO-SIGNALLING: SYS
SIP-SS: NO
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO
SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS
SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-T38-REDUND: SYS
SIP-T38-REDUND-PCK: SYS
SIP-UA: SYS
SIP-UA-PERMIT: *
SIP-REM-USER:
SIP-REM-PASS:
SIP-REM-AUTH: SYS
SIP-REM-REG: NO
------------------------------------------------------------------------------

Note
This command displays only the parameters related to enabled driver; if you want to see all the user
parameters type the d usere:sip_user command.

Meaning of the most parameters:

SIP Enables/disables SIP service for the user.

SIP-TYPE • PHONE: The user is a SIP client of Abilis, in example it is a phone or a softphone and SIP-
DOMAIN specifies the local domain of Abilis. Usually the user registers on Abilis or has a static
SIP-HOST and SIP-UDP/TCP-PORT.

• LOCAL-PEER: The user is a Peer as Abilis and SIP-DOMAIN specifies the local domain of
Abilis. Calling and Called numbers are both passed to the user. Usually the user registers on
Abilis or has a static SIP-HOST and SIP-UDP/TCP-PORT.

• SERVER: The user is a SIP server for Abilis and SIP-DOMAIN specifies the remote domain.
Usually the Abilis registers on this user.

• REMOTE-PEER: The user is a Peer as Abilis and SIP-DOMAIN specifies the remote
domain.Calling and Called numbers are both passed to the user. Usually the Abilis registers on
this user.

Before 7.3.4 version a different naming was used. Here is the matching table:

Table 46.1. SIP-TYPE matching table

Current name Previous Name

PHONE PHONE
LOCAL-PEER LOCAL-PROXY
SERVER REMOTE-PROXY
REMOTE-PEER <not available>

SIP-DOMAIN Domain of the called SIP UA server in outgoing calls.

813
Draft SIP - Session Initiation Protocol Draft

SIP-HOST IP address of the SIP UAC/UAS. Domain and Host may differ, because SIP registrar server
may be different from SIP proxy; normally proxies and SIP registrar server are co-located
[DYNAMIC: IP is not known in advance, it is known after the user executes the registration;
1.0.0.0-126.255.255.255, 128.0.0.0-223.255.255.255: remote IP is known in
advance; calls and registrations are performed and accepted only with this IP].

SIP-TCP-REMPORT TCP port on which the remote user is listening; Abilis outgoing TCP calls for this user will be
sent to this port [DYNAMIC: the port is learned from incoming registration; 1..65535: calls and
registrations are performed and accepted only with this port].

SIP-UDP-REMPORT UDP port on which the remote user is listening; Abilis outgoing UDP calls for this user will be
sent to this port [DYNAMIC: the port is learned from incoming registration; 1..65535: calls and
registrations are performed and accepted only with this port].

sip-udp-locport UDP port on which the Abilis is listening for this user [SYS, AUTO, 1..65535] . The default value
is"SYS" and refers to the port parameter udp-locport. "AUTO" and a port different from the one
configured in SIP port parameter "udp-locport" may be assigned only to SIP-TYPE REMOTE-
PEER or SERVER. Note that this is a lower cased parameter, it means that an Abilis CPX reboot
must be performed to apply changes, in detail you need to save the configuration ( command save
conf ) and restart the Abilis ( via the command warm start ).

SIP-SRCADD Source IP address for outgoing connections [R-ID: the source IP address of the outgoing datagrams
will be set to the current RouterID value; OUT-IP: the source IP address of the outgoing datagrams
will be set on the base of the output IP interface; 1-126.x.x.x, 128-223.x.x.x: the source
IP address of the outgoing datagrams will be set to the selected value; Ip-nnn: use the current
IPADD of the specified IP resource; SYS: uses the value in SRCADD parameter in CTISIP resource].

SIP-PROT-IN Transport protocol used to receive calls from this user.

SIP-PROT-OUT Transport protocol used to place outgoing calls to this user.

SIP-IP-PERMIT Range of allowed IP addresses of the SIP user.

SIP-MAXSES-BID Maximum number of simultaneous bidirectional sessions.

SIP-MAXSES-IN Maximum number of simultaneous reserved input sessions.

SIP-MAXSES-OUT Maximum number of simultaneous reserved output sessions.

SIP-NUMBER Number that identifies the user; if this number is not null, it is used to route calls to the user.

SIP-CG-NUM Calling number to use for calls coming from the user. The parameter accepts from 1 up to 20
characters in the following range: [AUTO: enforces caller id information element equal to SIP-
NUMBER; [0..9]: enforces the content with these exact digits; [0..9]*: replaces first specified
digits and passes the remaining transparently; *: passes calling address information element
transparently; #: removes calling number information element; ##: enforces the presentation
restricted: the calling number is sent empty; ##[0..9]: enforces the presentation restricted: the
calling number is sent with these exact digits; ##[0..9]*: enforces the presentation restricted:
the first specified digits are replaced and the remaining are passed transparently; ##*: enforces the
presentation restricted: the calling number is sent transparently].

SIP-FWD-CG-NUM Indicates how the calling number is managed in unconditional call transfers and call forwarding
[CALLER: the calling number of the original call is passed to the new recipient; USER: the calling
number of the SIP user performing the action is passed to the new recipient].

SIP-ROUTE-BY-SD Allows routing using subaddress called field. Calls from CTIR and directed to SIP users are first
directed to the user with a USERNAME equal to what is specified in Subaddress Called; if such user
does not exists, or the user disallows SIP-ROUTE-BY-SD, the call is routed using standard CTISIP
table matches.

SIP-PROVIDE-SG Allows insertion of SIP USER NAME in subaddress calling field.

SIP-LCS-GROUP Last Calling number Service group identifier [NONE, 1..32].

SIP-AUTH Authentication types offered to autenticating/registering users (incoming calls/registrations) [SYS:

uses the value in AUTH parameter in CTISIP resource; PLAIN: basic authentication via user/
password; DIGEST: DIGEST authentication type].

814
Draft SIP - Session Initiation Protocol Draft

SIP-CHAN-FREQ SIP desired channel frequency for bandwidth optimisation, to be rounded down to a codec frame
length multiple [SYS: uses the value in CHAN-FREQ parameter in CTISIP resource; 30..90:
frequency for banwidth optimisation].

SIP-CPO-RTP Enables/disables Call Path Optimization (CPO) [SYS: uses the value in CPO parameter in CTISIP
resource; NO: doesn't allow CPO; YES: allows CPO].

SIP-SS Enable/disable SIP supplementary services [NO, YES]

SIP-SS-PICKUP SIP supplementary service. Pickup permissions [NO, ANY]

SIP-SS-PRES-CG SIP supplementary service. Calling present [NO, YES

SIP-SS-CF-DND supplementary service. Call forwarding and Do-Not-Disturb [NO, YES]

SIP-REMOTE-NAT Position of the client in Internet [NO: requests and responses to the customer's phone occurs on the
Contact header field specified. RTP checks that remote ip/address matches with which one specified
in SDP (symmetric RTP is not allowed); STRICT: requests and responses to the customer's phone
occurs on the same address/port from which the remote requests/responses came from. RTP checks
that remote address matches with which one of signaling (symmetric RTP is allowed); LOOSE:
requests and responses to the customer's phone occurs on the same address/port from which remote
requests/responses came from (symmetric RTP is fully allowed with no address checking)].

SIP-LOCAL-NAT NAT traversal method [NO, EXTERNAL-IP].

SIP-EXTERNAL-IP IP address of the SIP UA.

SIP-KEEPALIVE Enables/disables the SIP KEEPALIVE.

SIP-DTMF-MODE DTMF mode sent to the remote UA [SYS: uses DTMF-MODE value in CTISIP resource; INBAND:
the outband DTMF received from CTIR is not dropped, only the audio stream is passed; INFO: the
outband DTMF received from CTIR is sent using INFO message; RFC2833: the outband DTMF
received from CTIR is sent using RFC2833 payload].

SIP-REM-USER The name used in the remote SIP UA server to identify the Abilis; this name is used for both
registration and authentication purposes.

SIP-REM-PASS The password used in the remote SIP UA server to identify the Abilis; this password is used for both
registration and authentication purposes.

SIP-REM-AUTH Authentication method when Abilis is authenticating/registering to a peer (outgoing calls/

registrations) [SYS: uses the value in REM-AUTH parameter in CTISIP resource; PLAIN: basic
authentication via user/password; DIGEST: DIGEST authentication type].

SIP-REM-REG Enables/disables the registration of the Abilis to the remote SIP UA server [NO; YES: Abilis
periodically register to the remote UA to inform remote peer about its IP address and TCP/UDP
port].

46.2.2. CTISIP translation table

This table contains relations between a SIP-number (or a prefix, when * is included in the number) and a SIP-user. Calls
which CTIR forwards to CTISIP finds the destination user by matching the called number (matching between the CDO field
of the CTI routing and the CDI field of this table).

When SIP-CG-NUM:AUTO in the Users table, calls from CTISIP to CTIR will have:

• the callerid provided by SIP user validated in the CTISIP translation table;

• the SIP-number set in user service.

In case of validation failure the callerid will be overwritten with the value configured in the SIP-number of the user table (*,
as wildcard, is not included).

Type the following command to view the details of the CTISIP translation table:

[17:22:35] ABILIS_CPX:d ctisip

815
Draft SIP - Session Initiation Protocol Draft

Total:4 Connected:4 Static:0

NUMx: USER: P:
------------------------------------------------------------
500 test4 C
12 test3 C
11 test2 C
10 test C

There are two types of entries:

• connected: when SIP-NUMBER is set in the SIP users chart, the CDI parameter in the chart will be the same. In case the
routings are connected, the letter C will appear under the P item.

Tip
The connected entries are automatically added.

• statics: when a SIP-NUMBER is not specified in the SIP users chart and it's associated by hand in the chart, the letter S
will appear under the P item. This system is used to add several numbers to the same user (for instance in case of static
routings).

Use the following commands to manage the SIP translation table:

• a ctisip numx:<SIP-NUMBER> username:<name> : adds a new SIP-NUMBER;

• s ctisip numx:<SIP-NUMBER> username:<name> : modifies the username of an existing SIP-NUMBER;

• c ctisip numx:<SIP-NUMBER> : clears a SIP-NUMBER;

• d ctisip numx:<SIP-NUMBER> : displays the list of SIP-NUMBER or a specific one.

Tip
To a single user can be associated more SIP-numbers.

The SIP users creation generates automatically the NumSip list in which are located all the SIP-NUMBERS associated to the
users (it is very useful for the CTIR configuration).

Type the following command to view the list :

[15:28:03] ABILIS_CPX:d list:numsip

LIST:NumSip - IN
Automatically_generated_CTI_SIP_Numbers_list_(ReadOnly)
10 11 12
500

Note
It is a “read only” list, you cannot modify it, as it is automatically created by the system.

46.3. CTI Routings

Appropiate routings must be added in the CTI Router, in order to route the calls to and from the CTISIP resource.

The destination or the source of the SIP group appears as CtiSip (this is the default value).

To view all the configurable parameters type:

[13:47:29] ABILIS_CPX:d ctir

816
Draft SIP - Session Initiation Protocol Draft

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------

The routing types involved with CtiSip are:

Table 46.2. CtiSip routing

Type Description Transcoding supported

VtoS Voice to SIP NO
CtoS Cluster to SIP YES
HtoS H.323 to SIP YES
DtoS DISA to SIP YES
ItoS IAX to SIP YES
StoV SIP to Voice NO
StoC SIP to Cluster YES
StoH SIP to H.323 YES
StoD SIP to DISA YES
StoI SIP to IAX YES
StoS SIP to SIP YES

Tip
Transcoding is allowed when parameter CODERSOUT is different from *.

The transcoding is possible only for the coders supported by Abilis. To view them, type:

[14:09:52] ABILIS_CPX:d d ctisys

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
-- Number of simultaneous calls ----------------------------------------
| State: Alerting/Connected | State: Any |
---------------|---Current---|----Peak-----|---Current---|----Peak-----|
TR | 0 | 0 | 0 | 0 |
DATA | 0 | 0 | 0 | 0 |
VtoCHISD | 0 | 0 | 0 | 0 |
CHISDtoCHISD | 0 | 0 | 0 | 0 |
CHISDtoV | 0 | 0 | 0 | 0 |
ALL | 0 | 0 | 0 | 0 |
------------------------------------------------------------------------
- Available coders -----------------------------------------------------
-- Coder ---|-- Bit rates (kbps) --|-- Coder ---|-- Bit rates (kbps) --|
G.711-A |64 |G.711-u |64 |
TRANSPARENT |64 |Spirit |6.4, 7.2, 8, 8.8, 9.6 |
------------------------------------------------------------------------
- Clock Sources for H100 cards -----------------------------------------
CLK:INT
- Clock Sources for NOT-H100 cards -------------------------------------

817
Draft SIP - Session Initiation Protocol Draft

*** No NOT-H100 cards running ***

Tip
For further information about transcoding refer to Section 45.3, “CTI Routings”.

46.4. Example of configuration

Figure 46.1. Configuration scheme

In the figure there are the following elements:

• Site 1

• SIP phone;

• PC with Zoiper program for SIP communications.

• analog phone connected to a POTS port of the Abilis.

• Abilis which manages all the systems and a VPN with “Site 2”.

• Site 2

• SIP phone;

• Abilis that manages all the systems and a VPN with “Site 1”.

The purpose is to enable the communication between:

• SIP users in “Site 1” (SIP phone and PC with Zoiper);

• the POTS phone and the SIP users of “Site 1”;

• SIP users in “Site 1” and the SIP users in “Site 2”.

Assumptions: the POTS cards, used to manage the analog phones and configured for Cluster and CtiLink for compressed
phone calls, are already active on Abilis.

Tip
Interesting chapter: Section 53.7, “How to register a SIP telephone onto Abilis”.

818
Draft SIP - Session Initiation Protocol Draft

46.4.1. Activation and configuration of the CtiSip resource

Activate the CTISIP resource in the Abilis of “Site 1” and enable up to 10 SIP connections.

[10:27:42] ABILIS_CPX_1:s p ctisip act:yes sesnum:10

COMMAND EXECUTED

[10:27:53] ABILIS_CPX_1:d p ctisip

RES:CtiSip - Not Saved (SAVE CONF), Not Refreshed (INIT) ----------------------

Run DESCR:Session_Initiation_Protocol
LOG:NO ACT:YES
mxps:2172 sesnum:10 tcp-ses:0
tcp-locport:5060 UDP-PORT-BASE:6000 SIP-TOS:0-N
udp-locport:5060 UDP-PORT-RANGE:200 RTP-TOS:0-D
SRCADD:OUT-IP
EXTERNAL-IP:OUT-IP
IPSRC:* IPSRCLIST:#
AUTH:DIGEST KEEPALIVE:90 CTIP-TYPE:USER
LIFETIME:120 DISC-AUDIO:NO NP-CT:SYS
REM-AUTH:DIGEST T1:500 ROUTING:EN-BLOC
REM-LIFETIME:120 T2:4 DIALT:5
AUTH-TOUT:4 T4:5 T302:15
AUTH-TOUT-INVITE:4 CHAN-FREQ:20 ROUTE-BY-SD:NO
DTMF-MODE:RFC2833 T38:YES PROVIDE-SG:NO
PLAY-DTMF:100 T38-G711:NO CLIP-RULE:PRIVATE
PLAY-SILENCE:100 T38-PACKING:1 RG-IN:DISABLE
DETECT-DTMF:40 T38-REDUND:REDUNDANCY CPO-RTP:NO
DETECT-SILENCE:40 T38-REDUND-PCK:1 CPO-SIGNALLING:NO
DOMAIN:
UA:AUTO (Abilis CPX - Ver. 7.0.2/STD - Build 3357.4)

Keep all the default parameters .

Repeat the same operation for the Abilis of “Site 2”.

46.4.2. Users configuration

Activate two SIP user in the Abilis of “Site 1” (PC with Zoiper and SIP phone).

46.4.2.1. “Zoiper” user configuration.

Add the user in the Abilis of “Site 1” and enable it to SIP.

[10:50:19] ABILIS_CPX_1:a user:zoiper sip:yes

COMMAND EXECUTED

[10:50:28] ABILIS_CPX_1:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
zoiper YES # # NO NO NO NO NO YES

Give the new user the following characteristics:

• password: zoiper

• host: dynamic (the PC receives the IP address from a DHCP server)

819
Draft SIP - Session Initiation Protocol Draft

• simultaneous half-duplex call: 2

• SIP number: 610

[09:45:52] ABILIS_CPX_1:s user:zoiper pwd:zoiper sip-host:dynamic sip-maxses-bid:2 sip-number:610

COMMAND EXECUTED

[09:46:23] ABILIS_CPX_1:d user:zoiper

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: zoiper
ALIAS: zoiper
ID: 9 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
SIP: YES
SIP-TYPE: PHONE
SIP-DOMAIN: SYS
SIP-HOST: DYNAMIC
SIP-TCP-PORT: (DYNAMIC)
SIP-UDP-PORT: (DYNAMIC)
SIP-SRCADD: SYS
SIP-PROT-IN: TCP,UDP
SIP-PROT-OUT: UDP
SIP-IP-PERMIT: *
SIP-MAXSES-BID: 2
SIP-MAXSES-IN: 0
SIP-MAXSES-OUT: 0
SIP-NUMBER: 610
SIP-CG-NUM: AUTO
SIP-FWD-CG-NUM: CALLER
SIP-CTIP-TYPE: SYS
SIP-RG-IN: SYS
SIP-ROUTE-BY-SD: NO
SIP-PROVIDE-SG: NO
SIP-CLIP-RULE: SYS
SIP-BUSY-NOCHAN: NO
SIP-LCS-GROUP: NONE
SIP-CPO-RTP: SYS
SIP-CPO-SIGNALLING: SYS
SIP-SS: NO
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO
SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS

820
Draft SIP - Session Initiation Protocol Draft

SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-T38-REDUND: SYS
SIP-T38-REDUND-PCK: SYS
SIP-UA: SYS
SIP-UA-PERMIT: *
SIP-REM-USER:
SIP-REM-PASS:
SIP-REM-AUTH: SYS
SIP-REM-REG: NO
-------------------------------------------------------------------------------

46.4.2.2. “Sip phone” user configuration

Add the user in the Abilis of “Site 1” and enable it to SIP.

[09:51:19] ABILIS_CPX_1:a user:sip_phone sip:yes

COMMAND EXECUTED

[09:51:31] ABILIS_CPX_1:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
sip_phone YES # # NO NO NO NO NO YES
zoiper *** YES # # NO NO NO NO NO YES

Give the new user the following characteristics:

• password:sip_phone

• host: dynamic (the PC receives the IP address from a DHCP server)

• 2 simultaneous half-duplex calls

• SIP number: 630

[09:51:51] ABILIS_CPX_1:s user:sip_phone pwd:sip_phone sip-host:dynamic sip-maxses-bid:2 sip-number

COMMAND EXECUTED

[09:52:38] ABILIS_CPX_1:d user:sip_phone

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: sip_phone
ALIAS: sip_phone
ID: 10 <Read Only>
PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
SIP: YES
SIP-TYPE: PHONE
SIP-DOMAIN: SYS
SIP-HOST: DYNAMIC
SIP-TCP-PORT: (DYNAMIC)

821
Draft SIP - Session Initiation Protocol Draft

SIP-UDP-PORT: (DYNAMIC)
SIP-SRCADD: SYS
SIP-PROT-IN: TCP,UDP
SIP-PROT-OUT: UDP
SIP-IP-PERMIT: *
SIP-MAXSES-BID: 2
SIP-MAXSES-IN: 0
SIP-MAXSES-OUT: 0
SIP-NUMBER: 630
SIP-CG-NUM: AUTO
SIP-FWD-CG-NUM: CALLER
SIP-CTIP-TYPE: SYS
SIP-RG-IN: SYS
SIP-ROUTE-BY-SD: NO
SIP-PROVIDE-SG: NO
SIP-CLIP-RULE: SYS
SIP-BUSY-NOCHAN: NO
SIP-LCS-GROUP: NONE
SIP-CPO-RTP: SYS
SIP-CPO-SIGNALLING: SYS
SIP-SS: NO
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO
SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS
SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-T38-REDUND: SYS
SIP-T38-REDUND-PCK: SYS
SIP-UA: SYS
SIP-UA-PERMIT: *
SIP-REM-USER:
SIP-REM-PASS:
SIP-REM-AUTH: SYS
SIP-REM-REG: NO
-------------------------------------------------------------------------------

Add another “sip_phone” user in the Abilis of “Site 2” and assign it the SIP-NUMBER:910 (the configuration is similar to
that one of “Site 1”).

46.4.3. CTISIP translation table

46.4.3.1. CTISIP translation table of “Site 1”
Since the SIP-NUMBER parameter for the SIP users of “Site 1” is specified, the routings will be automatically connected in
the table.

[11:25:38] ABILIS_CPX_1:d ctisip

Total:2 Connected:2 Static:0

NUMx: USERNAME: P:
----------------------------------------------------------
610 zoiper C

822
Draft SIP - Session Initiation Protocol Draft

630 sip_phone C

Further modifications are not necessary.

46.4.3.2. CTISIP transaltion table of “Site 2”

Since the SIP-NUMBER parameter for the SIP user of “Site 2” is specified, the routing will be automatically connected in the
table.

[12:03:55] ABILIS_CPX_2:d ctisip

Total:1 Connected:1 Static:0

NUMx: USERNAME: P:
----------------------------------------------------------
910 sip_phone C

Further modifications are not necessary.

46.4.4. CTI Routings configuration

46.4.4.1. Abilis CTI Routing of “Site 1”
The purpose is to enable the communication between:

• SIP users in “Site 1” (SIP phone and PC with Zoiper);

• the POTS phone and the SIP users of “Site 1”;

• SIP users in “Site 1” and the SIP users in “Site 2”.

46.4.4.1.1. Communication between the SIP users

To connect up the PC with Zoiper and the SIP phone in “Site 1”, type:

[10:27:19] ABILIS_CPX_1:a ctir pr:0 type:stos cdi:'numsip' sp:64000

COMMAND EXECUTED

[16:42:17] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:25:10 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 StoS CtiSip CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
---------------------------------------------------------------------------

[13:49:17] ABILIS_CPX_1:d list:numsip

LIST:NumSip - IN
Automatically_generated_CTI_SIP_Numbers_list_(ReadOnly)

823
Draft SIP - Session Initiation Protocol Draft

610 630

We set up the SP parameter to 64000 to keep the available coder pool.

46.4.4.1.2. Communication between the analog phone and the SIP users
Add the following routings:

[17:22:52] ABILIS_CPX_1:a ctir pr:1 type:stov poo:101 cdi:01 sp:64000

COMMAND EXECUTED

[17:23:10] ABILIS_CPX_1:a ctir pr:2 type:vtos poi:pbx cdi:'numsip' sp:64000

COMMAND EXECUTED

[16:42:17] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:26:01 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 StoS CtiSip CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
1 StoV CtiSip 101 01 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
2 VtoS PBX CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

The PR:1 routing routes toward port 101 (where the analog phone is connected) the calls coming from one of the SIP users
and directed to the number 01.

The PR:2 routing routes the calls coming from the Abilis POTS port towards the CTISIP and directed to one number of the
NumSip list; the CTISIP translation table will forward the call to the user.

46.4.4.1.3. Communication between the SIP users in “Site 1” and the SIP users in “Site 2”
Add a StoC and a CtoS routing with the following commands to connect up the PC with Zoiper in “Site 1” and the sip phone
in “Site 2”:

[10:27:19] ABILIS_CPX_1:a ctir pr:3 type:stoc ds:site2 cdi:910 sp:64000

COMMAND EXECUTED

[10:29:50] ABILIS_CPX_1:a ctir pr:4 type:ctos sr:* cdi:'numsip' sp:64000

COMMAND EXECUTED

824
Draft SIP - Session Initiation Protocol Draft

[16:33:00] ABILIS_CPX_1:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:30:04 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 StoS CtiSip CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
1 StoV CtiSip 101 01 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
2 VtoS PBX CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
3 StoC CtiSip site2 910 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
4 CtoS * CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------

We set up the SP parameter to 64000 to keep the available coder pool.

The PR:3 routing routes towards the Site2 cluster the calls coming from SIP users and directed to the number 910.

The PR:4 routing routes towards the CTISIP the calls coming from any cluster and directed to one of the numbers of the
NumSip list; the CtiSip translation table will forward the calls to the user.

46.4.4.2. Abilis CTI Routing of “Site 2”

46.4.4.2.1. Communication between the SIP users in “Site 2” and the SIP users in “Site 1”

The example is similar to the configuration of the Abilis of the “Site 1”; type the following commands:

[10:39:13] ABILIS_CPX_2:a ctir pr:0 type:stoc ds:site1 cdi:610 sp:64000

COMMAND EXECUTED

[10:40:10] ABILIS_CPX_2:a ctir pr:1 type:ctos sr:* cdi:'numsip' sp:64000

COMMAND EXECUTED

[10:40:17] ABILIS_CPX_2:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:31:56 CET

825
Draft SIP - Session Initiation Protocol Draft

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 StoC CtiSip site1 610 *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
1 CtoS * CtiSip 'NumSip' *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------

[13:49:17] ABILIS_CPX_2:d list:numsip

LIST:NumSip - IN
Automatically_generated_CTI_SIP_Numbers_list_(ReadOnly)
910

Like the previous chart, the SP parameters is set at 64000 to keep the available coder pool.

The PR:0 routing routes toward the “Site1”cluster the calls coming from SIP users and directed to the number 610.

The PR:1 routing routes toward the CTISIP the calls coming from any cluster and directed to one of the numbers of the
NumSip list; the CTISIP translation table will forward the calls to the user.

46.5. Connecting Abilis and a SIP proxy

This section contains instructions for a correct set-up of Abilis CPX and SIP proxy interconnection.

46.5.1. Activation of the CTISIP resource

For the activation of the CTISIP resource refer to Section 46.1.1, “Activating the CTISIP resource”.

The basic parameters to configure are:

• ACT: to activate the resource.

• sesnum: to define the amount of simultaneous connections.

• SRCADD: source IP address for outgoing connections [R-ID: the source IP address of the outgoing datagrams will be set
to the current RouterID value; OUT-IP: the source IP address of the outgoing datagrams will be set on the base of the
output IP interface; 1-126.x.x.x, 128-223.x.x.x: the source IP address of the outgoing datagrams will be set to
the selected value; Ip-nnn: use the current IPADD of the specified IP resource].

Tip
If Abilis has only one IP resource (and only one IP address) , you can use the default value; otherwise if
Abilis has more IP resoures and more IP addresses the suggested configuration is OUT-IP.

• DOMAIN: if Abilis has clients in the public side you can also specify a FQDN.

46.5.2. Example: Abilis and a proxy registered in Abilis domain

In this case the proxy is a “normal” user like a soft phone but the SIP-TYPE is LOCAL-PEER.

826
Draft SIP - Session Initiation Protocol Draft

46.5.3. Example: Proxy and Abilis registered in Proxy remote

domain

In the figure there are the following elements:

• Abilis is an user of SIP proxy domain “voip.it”;

• “voip.it” is static IP address: 88.88.88.88;

• Abilis has a static IP address;

• Abilis has only one SIP user.

• Abilis user is “voipclient” with password “swordfish”.

• SIP proxy provides advanced services like IVR and voice mail, let's say that 10 sessions are needed.

Now you have to create a SIP user representing the user that is client of voip.it SIP proxy:

[14:49:07] ABILIS_CPX:a user:voipclient pwd:swordfish sip:yes

COMMAND EXECUTED

[14:49:07] ABILIS_CPX:s user:voipclient sip-type:server sip-domain:voip.it

COMMAND EXECUTED

[14:49:07] ABILIS_CPX:s user:voipclient sip-host:88.88.88.88

COMMAND EXECUTED

[14:49:07] ABILIS_CPX:s user:voipclient sip-maxses-bid:10 sip-number:*

COMMAND EXECUTED

[14:49:07] ABILIS_CPX:s user:voipclient sip-rem-reg:yes sip-rem-user:voipclient sip-rem-pass:swordf

COMMAND EXECUTED

You can show the result in this way:

[14:49:07] ABILIS_CPX:d user:voipclient

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
------------------+------------------------------------------------------------
USER: voipclient
ALIAS: voipclient

827
Draft SIP - Session Initiation Protocol Draft

ID: 9 <Read Only>

PWD: ***
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *
OPC-MONITOR: NONE
SIP: YES
SIP-TYPE: SERVER
SIP-DOMAIN: voip.it
SIP-HOST: 088.088.088.088
SIP-TCP-PORT: 5060
SIP-UDP-PORT: 5060
SIP-SRCADD: SYS
SIP-PROT-IN: TCP,UDP
SIP-PROT-OUT: UDP
SIP-IP-PERMIT: *
SIP-MAXSES-BID: 10
SIP-MAXSES-IN: 0
SIP-MAXSES-OUT: 0
SIP-NUMBER: *
SIP-CG-NUM: AUTO
SIP-FWD-CG-NUM: CALLER
SIP-CTIP-TYPE: SYS
SIP-RG-IN: SYS
SIP-ROUTE-BY-SD: NO
SIP-PROVIDE-SG: NO
SIP-CLIP-RULE: SYS
SIP-BUSY-NOCHAN: NO
SIP-LCS-GROUP: NONE
SIP-CPO-RTP: SYS
SIP-CPO-SIGNALLING: SYS
SIP-SS: NO
SIP-SS-PICKUP: NO
SIP-SS-PRES-CG: YES
SIP-SS-CF-DND: YES
SIP-AUTH: SYS
SIP-CHAN-FREQ: SYS
SIP-REMOTE-NAT: NO
SIP-LOCAL-NAT: NO
SIP-EXTERNAL-IP: SYS
SIP-KEEPALIVE: ENABLED
SIP-DTMF-MODE: SYS
SIP-DISC-AUDIO: SYS
SIP-BC-TRANSP: UDI
SIP-T38: SYS
SIP-T38-G711: SYS
SIP-T38-PACKING: SYS
SIP-T38-REDUND: SYS
SIP-T38-REDUND-PCK: SYS
SIP-UA: SYS
SIP-UA-PERMIT: *
SIP-REM-USER: voipclient
SIP-REM-PASS: *********
SIP-REM-AUTH: SYS
SIP-REM-REG: YES
-------------------------------------------------------------------------------

The CTISIP table, used to route calls toward SIP users, gets automatically populated with a unique route because you set
SIP-NUMBER:*.

828
Draft SIP - Session Initiation Protocol Draft

[14:49:07] ABILIS_CPX:d ctisip

Total:1 Connected:1 Static:0

NUMx: USERNAME: P:
----------------------------------------------------------
* voipclient C

Abilis and the Sip Proxy interconnection is now correctly configured.

Note
REMOTE-PEER handling is similar to SERVER but it allows calling/called number to pass unchanged.

46.5.4. CTI Routings configuration

Some routings in the CTIR table must be added in order to route the calls to and from the CTISIP resource.

46.5.4.1. Any coder, transcoding disallowed

Purpose of configuration: calls arriving from ISDN/POTS/GSM/CLUSTER are routed to SIP users, and calls arriving from
SIP users are first sent to cluster test; in case of failure (NEXT:LIMITED) it is attempted on ISDN/POTS/GSM group G1.

In this situation any coder with maximal speed 6400 (the default for SP parameter) is allowed, but transcoding is disallowed.
This means that the same coder must be used by the SIP proxy and Abilis.

[18:05:14] ABILIS_CPX:a ctir pr:0 type:vtos poi:* cdi:*

COMMAND EXECUTED

[18:05:18] ABILIS_CPX:a ctir pr:1 type:ctos sr:* cdi:*

COMMAND EXECUTED

[18:05:30] ABILIS_CPX:a ctir pr:2 type:stoc ds:test cdi:* next:limited

COMMAND EXECUTED

[18:05:38] ABILIS_CPX:a ctir pr:3 type:stov poo:g1 cdi:*

COMMAND EXECUTED

[18:05:51] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:36:34 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 VtoS * CtiSip * *
-------------------------------------------------------------------------------
1 CtoS * CtiSip * *
-------------------------------------------------------------------------------
2 StoC CtiSip test * *

829
Draft SIP - Session Initiation Protocol Draft

LIMITED ANY NO Dft * *

-------------------------------------------------------------------------------
3 StoV CtiSip G1 * *
-------------------------------------------------------------------------------

Tip
To allow G.729A you have to set SP:8000 in every routing.

46.5.4.2. Only G.711 on SIP proxy, any coder on Cluster, transcoding allowed
Purpose of example: calls arriving from ISDN/POTS/GSM/CLUSTER are routed to SIP users, and calls arriving from SIP
users are first sent to cluster test; in case of failure (NEXT:LIMITED) it is attempted on ISDN/POTS/GSM group G1.

In this situation only G.711 A-law or u-law can be used by SIP proxy and Abilis. Since transcoding is enabled by
CODERSOUT <> * the StoC and CtoS routings will negotiate for the “C” side any coder with maximum speed up 6400 bps.

[18:12:28] ABILIS_CPX:a ctir pr:0 type:vtos poi:* cdi:* sp:64000

COMMAND EXECUTED

[18:12:37] ABILIS_CPX:a ctir pr:1 type:ctos sr:* cdi:* spout:64000 codersout:G.711

COMMAND EXECUTED

[18:12:45] ABILIS_CPX:a ctir pr:2 type:stoc ds:test cdi:* next:limited sp:64000 coders:g.711 spout:

COMMAND EXECUTED

[18:12:53] ABILIS_CPX:a ctir pr:3 type:stov poo:g1 cdi:* sp:64000

COMMAND EXECUTED

[18:13:00] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 28/11/2010 10:38:02 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 VtoS * CtiSip * *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
1 CtoS * CtiSip * *
NO ANY NO Dft * *
6400 Sys * * Sys Sys * *
64000 * * * NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO
*
G.711
-------------------------------------------------------------------------------

830
Draft SIP - Session Initiation Protocol Draft

2 StoC CtiSip Clus1 * *

LIMITED ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
6400 * * * NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO
G.711
*,Sys
-------------------------------------------------------------------------------
3 StoV CtiSip G1 * *
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

Tip
To allow G.729A you have to set SP:8000 in CtoS PR:1 and SPOUT:8000 in StoC PR:2.

46.5.4.2.1. Transcoding optimisation

When the Abilis-SIP proxy interconnection occurs via local LAN, (i.e. with high speed, minimal delays, minimal jitter),
optimising the transcoding can be done so that the SIP proxy side uses minimal jitter, minimal delays.

This is obtained by properly setting DJ, MJ, DJOUT, MJOUT.

[18:15:17] ABILIS_CPX:s ctir pr:1 djout:0 mjout:80

COMMAND EXECUTED

[18:15:29] ABILIS_CPX:s ctir pr:2 dj:0 mj:80 djout:sys mjout:sys

COMMAND EXECUTED

Tip
DJ and MJ in pr:1 as well as DJOUT and MJOUT in pr:2 may assume other values appropriate for the
WAN link or specifically required by calls matching the routing.

46.5.4.2.2. Fax

When transcoding takes place in StoC and CtoS, with G.711 toward the SIP proxy, something interesting happens: on the
WAN FAX relay can be used! Abilis can exchange FAX with following characteristics:

• use G.711, 64 kbps plus IP overhead on the Abilis-SIP proxy interconnection;

• use G3 Fax relay, 2400/4800/9600/14400 kbps plus IP overhead on the WAN link.

Set FMRELAY:NO in the desired routing to disable fax relay:

[18:18:2] ABILIS_CPX:s ctir pr:0 fmrelay:no

COMMAND EXECUTED

[18:18:35] ABILIS_CPX:s ctir pr:1 fmrelay:no

COMMAND EXECUTED

[18:18:29] ABILIS_CPX:s ctir pr:2 fmrelay:no

COMMAND EXECUTED

[18:15:29] ABILIS_CPX:s ctir pr:3 fmrelay:no

COMMAND EXECUTED

831
Draft SIP - Session Initiation Protocol Draft

46.6. Busy Lamp Field (BLF)

Advanced SIP phones support a special feature named BLF (Busy Lamp Field). Typically BLF is a collection of lights
on a phone that indicate who is talking on other phones connected to the same PBX. The BLF is used by a receptionist or
secretary to aid in routing the incoming calls. The lights in telephone commonly have a related button to perform the direct
call or the call pick-up.

Figure 46.2. An IP phone supporting BLF

There is no RFC called "Busy Lamp Field" and actually the lights on the phone are implemented differently by different
producers

The most important RFCs related to BLF are:

• 3856 - A presence Event Package for Session Initiation Protocol (SIP)

• 4235 - An INVITE-Initiated Dialog Event Package for the Session Initialisation Protocol (SIP)

The lights on the phone may be associated to a lot of different features anyway when speaking about BLF normally there are
two options:

• Dialog Monitoring (RFC 4235). It is the most used, it displays the state of the calls associated with the Sip extension.

• Presence Monitoring (RFC 3856). It is often used by softphones, it display the human state of the user, so if the state is
busy it does not mean that he is involved in a call. He is just busy, may be he is reading a newspaper or playing darts.
Anyway Asterisk and other similar solutions convert the call state in presence state to satisfy the softphones requests.

46.6.1. Dialog an presence monitoring

Although BLF handling is implementation depended, the following common behaviors may be reported.

In case the IP phone has just one colour led:

Table 46.3. One colour led meaning

Light state Dialog monitoring Presence monitoring

Off No current calls The user is not available
Blinking At least an incoming calls is in alerting /
state
On All the remaining cases (i.e. current The user is available
calls are connected)

In case of green and red leds:

832
Draft SIP - Session Initiation Protocol Draft

Table 46.4. Two colours led meaning

Light state Dialog monitoring Presence monitoring

Off The subscription failed The subscription failed or the user is not
available.
Green On The subscription was successful and The user is available
there is no current calls.
Blinking Red At least an incoming calls is in alerting /
state
Red On All the remaining cases (i.e. current The user is busy
calls are connected)

Almost all producers offer modules to increase the number of available leds and buttons for the BLF feature.

46.6.2. BLF in Abilis CPX

In Abilis CPX, the Busy Lamp Field feature is strictly related to OPC (Operator Panel Console), i.e. all what a user can see
in OPC is available to BLF, and what is NOT available in OPC is not available in BLF. You should consider BLF as another
way to access OPC information.

BLF requires separated licence in CPX and needs also SoftPBX licence as it is required by OPC.

Abilis CPX introduced just a couple of port parameters specific for BLF:

• SUB-LIFTIME - Expiration time of incoming subscriptions. Range 60-3600 seconds, default 180.

• max-sub - Maximum number of subscriptions that CTISIP may handle independently from the event type, the subscriber
and the monitored resource. Range 0-1000, default 100.

There are no new user parameters to handle BLF.

Please refer to OPC driver to configure this service in Abilis CPX.

For a smooth operation of BLF it is necessary that CTIP/CLUS/SIP/IAX interfaces and users have all different numbers
assigned. In case that the same number is assigned to a two or more of them the following priority order will be used : CTIP,
then CLUS, then SIP, then IAX.

IP phones keys must be properly configured in order to monitor an extension and/or perform call pickup on that extension.
There are optional strings that can be used.

Table 46.5. Request URI for Abilis BLF feature

<number>@domain The related user is in the local Abilis, the monitored interface
is chosen after a search of the <number> in CTIP/CLUS/SIP/
IAX interfaces
<user>/<number>@domain The <user> is in local Abilis and the monitored interface is
CTISIP. The <number> is needed in case of direct call
<interface>/<user>/<number>@domain The <user> is in local Abilis and the monitored <interface>
is specified in the request URI. The <number> is needed in
case of direct call
<abilisid>/<interface>/<user>/<number>@domain The <user> may be in a remote Abilis with <abilisid>
identifier specified in OPC configuration, the CTI
<interface> is specified in the Request Uri. The <number> is
needed in case of direct call

Also note that the SIP user to perform Call Pick-up must have SIP-SS:yes and SIP-SS-PICKUP:ANY.

[19:52:11] ABILIS:d user:test

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test

833
Draft SIP - Session Initiation Protocol Draft

...
SIP-SS: YES
SIP-SS-PICKUP: ANY
...
-------------------------------------------------------------------------------

About Call pick-up feature also note that there are different handlings in different phones.

Normally the IP phones uses the number provided via SIP signalling (NOTIFY) to perform call pick-up, i.e. it occurs with
SNOM and Thomson/Tecnicolor phones.

The Yealink phones default need to specify the number to perform call pick-up in their web interface but they have an
advanced option of the Account: Dialog-Info Call Pickup (default is disabled, just enable it) that allow them to use the
number provided by SIP signalling.

Finally the Grandstream phones need to specify the call pick-up prefix (default is ** to be changed in *1), and ignores the
SIP signalling about call picked up number.

46.7. CTISIP diagnostics and statistics

46.7.1. CTISIP diagnostics
To display the diagnostics of the CTISIP resource the following commands are used:

d d ctisip Shows diagnostic information, such as the state of the resource, the currently used channels, the remote
SIP username, the local/remote IP address-port of the SIP channel for incoming packets, the calling and
the called number.

d de ctisip Shows diagnostic information in an extended format: the same information listed for d d ctisip command
and the state of Unattended/Attended Call Transfer, the local/remote IP address-port of the SIP channel for
outgoing packets, the local/remote IP address-port for RTP and RTCP channel.

[12:34:34] ABILIS_CPX:d d ctisip

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
STATE:ACTIVE UDP-STATE:CLOSED USED-CHAN:0
- SIP Channels diagnostics ---------------------------------------------
CH: SIPState Prot TcpLsn SIP-LocAdd-Port-In SIP-RemAdd-Port-In
Q931State CG CD
User CallId
------------------------------------------------------------------------
0 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
1 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
2 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
3 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
4 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
5 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
6 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------

834
Draft SIP - Session Initiation Protocol Draft

7 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
8 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
9 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------

[12:34:34] ABILIS_CPX:d de ctisip

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
STATE:ACTIVE UDP-STATE:CLOSED USED-CHAN:0
- SIP Channels diagnostics ---------------------------------------------
CH: SIPState Prot TcpLsn SIPLocAdd-Port-In SIPRemAdd-Port-In
SIPLocAdd-Port-Out SIPRemAdd-Port-Out
Q931State CG CD
User CallId
Q932State UCTState ACTState CPOState
RTPState RTPLocAdd-LocPort RTPRemAdd-RemPort
RTCPState RTCPLocAdd-LocPort RTCPRemAdd-RemPort
------------------------------------------------------------------------
0 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
1 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
2 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
3 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
4 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
5 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
6 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
7 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
8 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------
9 DISCONNECTED
00-DISCONNECTED
------------------------------------------------------------------------

46.7.2. CTISIP statistics

To display the statistics of the CTISIP resource the following commands are used:

d s ctisip Shows statistic information, such as the number of incoming/outgoing accepted/rejected calls, the
number of incoming/outgoing succesful/failed registrations, the number of incoming/outgoing reinvites,
the number of successful incoming/outgoing transfers, the number of expired retransmission timer in
incoming/outgoing calls.

835
Draft SIP - Session Initiation Protocol Draft

d se ctisip Shows statistic information in an extended format: the same information listed for d se ctisip command
are shown for each session.

[12:34:34] ABILIS_CPX:d s ctisip

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
--- Cleared 20 days 16:33:47 ago, on 03/12/2007 at 03:21:24 ------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 0| 0|FAIL-CALL | 0| 0|
SUCC-REG | 0| 0|FAIL-REG | 0| 0|
SUCC-TRAN | 0| 0|FAIL-TRAN | 0| 0|
EXP-RETRY | 0| 0|DTMF | 0| 0|
HOLD | 0| 0|UN-HOLD | 0| 0|
UNKNOWN | 0| 0|REINVITES | 0| 0|
LOST-NOBUF | 0| 0|OUTSEQ | 0| |
BLACKLISTED| 0| |
------------------------------------------------------------------------

[12:34:34] ABILIS_CPX:d se ctisip

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
--- Cleared 0 days 00:23:42 ago, on 19/12/2010 at 10:09:52 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-CALL | 0| 0|FAIL-CALL | 0| 0|
SUCC-REG | 0| 0|FAIL-REG | 0| 0|
SUCC-TRAN | 0| 0|FAIL-TRAN | 0| 0|
EXP-RETRY | 0| 0|DTMF | 0| 0|
HOLD | 0| 0|UN-HOLD | 0| 0|
UNKNOWN | 0| 0|REINVITES | 0| 0|
LOST-NOBUF | 0| 0|OUTSEQ | 0| |
BLACKLISTED| 0| |
------------------------------------------------------------------------
CH:0 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:1 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:2 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:3 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:4 CallId:

836
Draft SIP - Session Initiation Protocol Draft

CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:5 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:6 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:7 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:8 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------
CH:9 CallId:
CG: CD:
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
RTP-PCK | 0| 0|RTCP-PCK | 0| 0|
RTP-LOST | 0| 0|SIP-OUTSEQ | 0| |
RTP-OUTSEQ | 0| |RTP-NOBUF | 0| 0|
------------------------------------------------------------------------

46.7.3. Debug of the CTISIP resource

Below debug commands are described.

Note
To use these commands you need to have administrator or super user rights.

Type the following command to display the syntax of the command:

[12:34:34] ABILIS_CPX:debug res:ctisip lsn:0

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
BufferLength:1027 Date/Time:28/11/2010 10:39:59 TraceTime:<NotRunning>

Usage:

LSN:0 - This help

LSN:1 - Extra channels diags

837
Draft SIP - Session Initiation Protocol Draft

LSN:3 - Show debug log

LSN:3 CMD:CLR - Clear debug log
LSN:3 CMD:SET:[DFT | CLR | FULL | [level,...]] - Set log event mask
No parameters - Show current events log mask
DFT - Log default events (ERR events only)
CLR - Clear log event mask
FULL - Log all events
levels:
ERR - Log only error events
REG - Registration events
INFO - Informative events
LSN:4 - Show registered users
LSN:10 CMD:UserName - Force Abilis registration with this user
LSN:11 CMD:UserName - Force User unregistering
LSN:20 CMD:NumPackets - Simulates loss of NumPackets packets from CTIR
LSN:21 CMD:NumPackets - Simulates loss of NumPackets packets to CTIR

Type the below command to view the event logs connected with the users registration:

[12:37:17] ABILIS_CPX:debug res:ctisip lsn:3

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
BufferLength:10838 Date/Time:18/01/2008 11:37:06 TraceTime:<NotRunning>

DD/MM/YYYY HH:MM:SS - CHANNEL DESCRIPTION

10/12/2007 09:33:26 - [ 30] Error in OUT channel with 62.62.62.62:5060
10/12/2007 09:33:26 - [ 30] AUTH timer timeout
10/12/2007 11:08:09 - [ 30] Error in OUT channel with 62.62.62.62:5060
10/12/2007 11:08:09 - [ 30] AUTH timer timeout
10/12/2007 15:34:56 - [ 30] Error in OUT channel with 62.62.62.62:5060
10/12/2007 15:34:56 - [ 30] AUTH timer timeout
10/12/2007 15:40:44 - [ 30] Error in OUT channel with 62.62.62.62:5060
10/12/2007 15:40:44 - [ 30] AUTH timer timeout
10/12/2007 17:46:24 - [ 30] Error in OUT channel with 62.62.62.62:5060
10/12/2007 17:46:24 - [ 30] AUTH timer timeout

This table shows data, time, identification of the event and the description of the error.

Possible errors could be:

• unknown user;

• codec not supported;

• retransmission out of time (happens when you're cut off).

Most common usage are:

• debug res:ctisip lsn:3 : shows log;

• debug res:ctisip lsn:3 cmd:clr : clear log;

• debug res:ctisip lsn:3 cmd:set:err : set log mask to log only errors events;

• debug res:ctisip lsn:3 cmd:set:err,reg : set log mask to log only errors and registration events;

• debug res:ctisip lsn:3 cmd:set:full : set log mask to log any event.

The following command allows to show the registration table (remote peers registered with Abilis and remote peers Abilis is
registered to).

[17:03:12] ABILIS_CPX:debug res:ctisip lsn:4

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
BufferLength:324 Date/Time:18/01/2008 11:38:56 TraceTime:<NotRunning>

838
Draft SIP - Session Initiation Protocol Draft

User Host Prot Port REG LIFETIME AGE

-------------------------------------------------------------------------------
sip_proxy 062.062.062.062 UDP 5060 REMOTE 120 21
zoiper 192.168.000.024 UDP 5060 LOCAL 60 35
-------------------------------------------------------------------------------

Meaning of the parameters:

User Username registered in the user table (d user).

Host IP address of the user.

Prot Transport protocol.

Port UDP port of the user.

REG Registration of the user [REMOTE: Abilis is registered to a remote peer; LOCAL: a remote peer is registered to
Abilis].

LIFETIME How often (in seconds) the registration is requested.

AGE Time (in seconds) since last valid registration.

In the previous example, Abilis is registered to the remote peer sip_proxy (ip address: 62.62.62.62) which needs Abilis
registration each 120 seconds; Abilis registered itself 21 seconds ago.

The user zoiper (ip address: 192.168.0.24) is registered to Abilis; it registered itself 35 seconds ago.

46.8. Appendix - SIP protocol overview

The Session Initiation Protocol1 (SIP) is an application-layer control (signaling) protocol for creating, modifying, and
terminating multimedia sessions with one or more participants.

SIP can be used with other IETF protocols to build a complete multimedia architecture, such as the Real-time Transport
Protocol2 (RTP) for transporting real-time data and providing QoS feedback, the Real-time streaming protocol (RTSP)
for controlling delivery of streaming media, the Media Gateway Control Protocol (MEGACO) for controlling gateways to
the Public Switched Telephone Network (PSTN) and the Session Description Protocol3 (SDP) for describing multimedia
sessions.

The main features of the SIP protocol are:

• Lightweight: about computational view, not about bandwidth.

• Transport independent: SIP can be used with UDP, TCP, ATM & so on.

• Text-based (UTF-8): SIP messages have a header with multiple header fields and a message body.

SIP is modular and uses other protocols to define media details (SDP) and voice timing and synchronization (RTP). The SDP
protocol is inserted in the message body (e.g. in a INVITE message) and it contains the RTP UDP port number; classic SIP
implementations use TCP port 5060 and/or UDP port 5060 to handle signaling and various UDP ports for RTP.

SIP is a peer-to-peer protocol; the peers in a session are called User Agents (UAs). An user agent can function in one of the
following roles:

• User agent client (UAC): a client application which initiates the SIP request.

• User agent server (UAS): a server application which contacts the user when a SIP request is received and that returns a
respone on behalf the user.

46.8.1. SIP and NAT trasversal problem

When a SIP client initializes a communication, it sends to a server an INVITE request which contains the number of the UDP
port used by RTP. If the client is behind a NAT the UDP port for RTP will be mapped in different mode, so SIP Server will
be not able to send voice to right port and this cause the SIP NAT Traversal problem.

1
http://en.wikipedia.org/wiki/Sip
2
http://en.wikipedia.org/wiki/Real-time_Transport_Protocol
3
http://en.wikipedia.org/wiki/Session_Description_Protocol

839
Draft SIP - Session Initiation Protocol Draft

There are four types of NATs:

• Full Cone: all requests from the same internal IP address and port are mapped to the same external IP address and port.
Any external host can send a packet to the internal host, by sending a packet to the mapped external address.

• Restricted Cone: all requests from the same internal IP address and port are mapped to the same external IP address
and port. Unlike a Full Cone NAT, an external host (with IP address X) can send a packet to the internal host only if the
internal host had previously sent a packet to IP address X.

• Port Restricted Cone: it is like a Restricted Cone NAT, but the restriction includes port numbers. An external host can
send a packet, with source IP address X and source port P, to the internal host only if the internal host had previously sent a
packet to IP address X and port P.

• Symmetric: all requests from the same internal IP address and port, to a specific destination IP address and port, are
mapped to the same external IP address and port. If the same host sends a packet with the same source address and port,
but to a different destination, a different mapping is used. Only the external host that receives a packet can send an UDP
packet back to the internal host.

46.8.2. Solution to SIP NAT trasversal problem

If the client is behind one of the first three NAT types, the solution for NAT trasversal is simple. The client must find out
how its internal address:port pair looks to the world (i.e. the NAT mapping) and then it must put that information into the
SDP message (instead of the information reflecting its internal address:port pair). There are two basic methods for a client
to determine the NAT mapped public address:port pair; the first is to ask the NAT, the second is to ask someone outside the
NAT what the actual address:port should be.

There are a lot of proposal about the solution:

1. UPnP: a client queries the NAT via UPnP (Universal Plug and Play) protocol asking what mapping it should use if it
wants to receive on port P; the NAT responds with the address:port pair needed to reach the client on this port P. This
solution doesn't work with Symmetric NATs and cascading NATs; furthermore there is a huge installed base of existing
NATs that do not support UPnP.

2. External query: a server sits listening for packets (call this a NAT probe); when it receives a packet from a client, it
returns a message from the same port to the source of the received packet containing the address:port pair which it sees
as the source of that packet. The client can then determine if it is behind a NAT and the public address:port pair it should
use in SDP message in order for the endpoint to reach it. This solution doesn't work with Symmetric NATs and cascading
NATs.

3. STUN (Simple Traversal of UDP Through NATs): is a protocol for setting up the kind of NAT probe. It returns the public
address:port pair and can also determine which kind of NAT the client is behind. Clients can set their SDP messages
accordingly; the STUN server does not sits in the signaling or media data path. This solution doesn't work with Symmetric
NATs.

4. Connection Oriented Media: the client must send out a RTP to, and receive RTP back from the same IP address. Any
RTP connection between an endpoint outside a NAT and one inside a NAT must be estabilished point to point. The
endpoint outside the NAT must wait until it receives a packet from the client before it can know where to reply. The
client informs the endpoint to wait for the incoming packet through the addition of the a=direction:active tag in the
SDP message; this approach is useful in Symmetri NATs but is still problematic because there are not many endpoints
supporting this tag.

5. Symmetric RTP: the server simply “ignore” the RTP UDP port indicated in SDP of the INVITE request and always
respond to the port from where it receives RTP traffic. This solution works well and is the de-facto solution used by Cisco
Gateways to problems arising from symmetric NATs.

6. TURN (Trasversal Using Realy NATs): complements STUN and places the probe in the signaling and media path. The
probe terminates the media for both endpoints so that the probe which detected the address:port pair is also the probe
which is sending the client media. In this way the symmetric issue is taken care of.

7. Media Relay: combines the strengths of both “Symmetric RTP” and the “TURN server”. The relay can send media
packets to an endpoint on a port previously used send a media packet to the relay. As opposed to the TURN server, since
the relay has access to the SIP message this media port manipulation is quite trivial.

46.8.3. SIP NAT Trasversal problem with Abilis

The following figure shows the various situation concerning NAT trasversal problem with Abilis.

840
Draft SIP - Session Initiation Protocol Draft

Figure 46.3. NAT trasversal problem with Abilis

The cases 2 and 6 never work because a thrid part with public IP would be needed, while in the cases 3 and 7 there is no
NAT.

Consider the other situations:

• Case 1: UAC behind a NAT connected to public IP UAS. If UAC is behind a full cone NAT, restricted cone NAT, port
restricted NAT then a simple STUN server may be used. In case of symmetric NAT, UAC have to hope that UAS supports
symmetric RTP, like CISCO gateways and Asterisk PBX do.

• Case 4: public IP UAC connected to UAS behind a NAT. Similar but opposite to case 1.

• Case 5: UAS behind a NAT connected to a public IP UAC. In this case NAT will contain a port forwarding for TCP port
5060 and UDP port 5060, and other UDP ports needed by RTP; the UAS will send SDP using the configured public IP
address (it should be known), and public domain. Qualifying should be on to maintain a pinhole in the NAT.

• Case 8: public IP UAS connected to a UAC behind a NAT. UAS should support “Symmetric RTP”.

841
Draft Draft

Chapter 47. DISA - Direct Inward

System Access
Marco Bellesia
Luigi Demuro

Table of Contents
47.1. CTIDISA overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.1. User identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
47.1.2. Post-selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
47.1.3. Automatic Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
47.1.4. Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.1.5. Data Call Back . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2. CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.1. Activating the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
47.2.2. CTIDISA resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
47.3. CTIDISA tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
47.3.1. CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
47.3.2. CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
47.4. Example of Post Selection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
47.4.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
47.4.4. Configuring the CTI Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
47.5. Example of Automatic Call Distribution configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
47.5.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.5.4. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
47.6. Example of Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
47.6.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
47.6.3. Configuring the CTIDISA User table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.6.4. CTI Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
47.7. Example of Data Call Back configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.1. Configuring the CTIDISA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.2. Configuring the CTIDISA Service table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
47.7.3. Configuring CTI Routings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8. Message files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.1. File audio format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
47.8.2. Commands to manage audio files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.8.3. Example of insertion of WAV files and creation of CPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
47.9. CTIDISA diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.1. CTIDISA diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
47.9.2. CTIDISA statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
47.9.3. Advanced Debug of the CtiDisa resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
47.10. DISA administration through web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.1. Configuration of the HTTP rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
47.10.2. DISA administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

842
Draft DISA - Direct Inward System Access Draft

47.1. CTIDISA overview

DISA (Direct Inward System Access) is a PBX feature which allows callers from the outside to access internal system
features. DISA allows teleworkers to call the corporate telephone system, enter an authorization code and gain access to
system features. Users interact only through audio messages.

Abilis DISA driver supports five functionalities:

• User identification;

• Post-Selection;

• Automatic Call Distribution;

• Call Back;

• Data Call Back.

Calls passing through DISA can be divided in two parts: INCOMING and OUTGOING. The first one, refers to call's arrival
to the Abilis until the user identification; the second one refers to post-selection.

47.1.1. User identification

The INCOMING part can be divided in 3 phases:

1. Pre-identification

2. User identification

3. Reassignment of the service

47.1.1.1. Pre-identification
It refers to the call arrival to the DISA: it is called pre-identification because Abilis doesn't know if the user will enter the PIN
code or the post-selection yet.

During this phase the assignment of the service is made.

Note
A service is a collection of functions, rules, mechanisms!

47.1.1.1.1. Assignment of the service

This assignment can be based upon verification of:

• incoming called number (CDI);

• calling number (CGI);
• incoming called number AND calling number.

Pre-identification can fail in case of:

• calling number not present in the list of CGI users (if RESTRICTED-CALLING parameter is set to YES);
• maximum number of simultaneous calls on DISA has been reached (MAX-CALLS parameter).

The service defines the operations a certain user is allowed to perform:

• the tone set used in different phases;

• the maximum number of simultaneous connections for users assigned to the same service;
• the activation of Automatic Call Distribution (ACD) or Call Back (CB);
• a list of numbers enabled to be called (PERMIT parameter).

The Default service is assigned to all calls which has not been matched with other configured services.

843
Draft DISA - Direct Inward System Access Draft

The call can come from a ISDN port, a Cluster or other CTI resources like H.323, IAX or SIP and it's routed to CtiDisa
resource. The possible routings are VtoD, CtoD, HtoD, ItoD, StoD and *toD.

When the call arrives to the DISA (if the pre-identification phase doesn't fail), the user who has called hears the tone or the
welcome message (this means that the assignment of the service has happened).

It follows the phase of user identification.

47.1.1.2. User-identification
The Anonymous user is created by the system and identifies all callers not configured in other users.

An user can be identified in three ways:

• calling number: the user is identified verifying the number used for the call;
• PIN: the user is identified verifying the insertion of a PIN code (PIN starts with the '*' character and ends with '#');
• PIN + calling number: the user is identified by means of a PIN entering and the calling number.

Caution
If CGI and PIN fields are empty, the user will be considered anonymous (default user).

In the configuration of a user, the service assigned, the maximum number of simultaneous calls, the PIN code, one or more
calling numbers (CGI) for the identification and a list of numbers enabled and/or denied to be called (PERMIT and DENY
parameter) can be defined.

Tip
The combination of PERMIT (for services and users) and DENY (only for users) allows to further define
the user security clearance level in the post-selection phase; example: if a user is identified as belonging to a
service enabled to call numbers starting with 6, you can further define the user as cleared to call only number
601 or deny calls to 605 by specifying the proper value in the user's config file.

The identification can fail in case of:

• wrong PIN (in this case the call will be immediately rejected).

47.1.1.3. Reassignment of the service

When the user has been identified, he is assigned to a service. Generally, the user is assigned to the same service in which is
authenticated; it is also possible to change the destination service (SERVICE parameter).

47.1.2. Post-selection
The OUTGOING part represents the post-selection phase. From this moment a user can:

• call an internal extension number;

• make a new call.

Other interesting characteristic is the TRANSFER functionality. it allows the call's hung up from DISA when the call in post-
selection has been connected. Example: if the incoming call is VtoD and the post-selection DtoV, it will be maintained a
single “VtoV” (or transparent, TR) call.

47.1.2.1. Failure of post-selection

if post-selection fails, loops can be enabled so that the user can do a new post-selection.

There are four type of loops, in case of:

• call not answered (the selected user has not answered);

• busy (the internal extension of the selected user is busy);
• selection not allowed;
• other (all other disconnection codes, e.g: non-existent number, non-existent routing...).

844
Draft DISA - Direct Inward System Access Draft

Defining whether loops are active, in case one of the previous conditions happens, can be done.For each condition a tone or a
message to inform the user about the “status” of the call can be defined.

The maximum number of allowed loops before the call is permanently rejected (MAX-LOOPS parameter) can be defined.
This last phase is named BYE and can be identified from a specific message (it cannot be replaced by a tone!).

47.1.3. Automatic Call Distribution

DISA Automatic Call Distribution (ACD) allows Abilis to act like a Call Center device. When all operators are busy, the
incoming calls get queued. The waiting calls are forwarded to the first free operator on a FIFO-based approach.

The queues are individually generated for each called number and are totally indipendent.

If the user goes to a service with ACD:YES, he cannot digit the PIN (the user is in now in the post-selection phase).

If the user goes to a service with ACD:NO, inserts a PIN and then goes to another service with ACD:YES, the user goes to this
post-selection.

If the user goes to a service with ACD:YES and then goes to another service with ACD:NO, the AUTO-CDO of the first service
is maintained.

47.1.3.1. Queued calls

Queued calls are forwaded to an operator in two cases:

• the active call belonging to the same queue becomes disconnected.

If the caller hungs up before the operator, the call is forwarded after 5 seconds; in the opposite situation the call is
forwarded after 1 second (because Abilis immeditely realizes that the operator is free).

• the interval of attempts expires (the timer is resetted for every attempt).

This interval is editable in the ACD-INTERVAL parameter. During this phase the caller hears the LOOPDIAL message.
Abilis continues to call the selected internal extension every ACD-INTERVAL seconds and in case the operator gets free,
the call goes to ALERTING status and subsequently to ACTIVE status.

Note
When a call in queue goes to ALERTING status, it is immediately removed from queue; if it fails (for
example if the operator doesn't answer), the call is re-inserted in the queue (in the last position).

During the LOOPDIAL phase, the caller has two choices:

• to wait that the selected internal extension gets free;

• to select a new internal extension entering the last position of the new queue.

Note
If the user is not allowed to call the selected number, the call exits form the queue and enters into the loop.
The CALLNA message is played and then the AFTERPIN (if it is configured) or INITDIAL message. This
sequence is valid also if the call is “aborted” with the “**” during the ALERTING status (in this case the
DISC message is played).

When the ACD is active, the MAX-LOOPS parameter is automatically set to 99, while the TRANSFER parameter is disabled.

47.1.3.2. AUTO-CDO parameter

An “Automatic Called Number” (AUTO-CDO parameter) can be defined in the service configuration . When the call is
connected to DISA, the AUTO-CDO simulates the insertion of a called number. The following situations can happen:

• ACD:NO and AUTO-CDO configured: after user identification, in case of loop, the user will have to insert another number;

• ACD:YES and AUTO-CDO configured: the number configured in AUTO-CDO will be repeated until it is not changed by the
user. If the number is not allowed the INITDIAL and AFTERPIN tone will be played.

845
Draft DISA - Direct Inward System Access Draft

47.1.4. Call Back

DISA Call Back is a feature which allows an user to dial into a CPX , get the call refused, and receive a return call which
establishes the connection. Once connected, the user can place calls with usual DISA services. The caller is not charged at all,
since the original call is rejected.

DISA Call Back can be described in the following sequences:

• user dials-in;
• the pre-identification assigns a service;
• if the service allows Call Back the user is identified only by its calling number (only users without PIN can use this
service);

Caution
Call Back can proceed only if it is enabled for the service AND the user; otherwise the call-back is
aborted, the user identification is cleared, and DISA resumes to “not Call Back” call exactly at the
moment where pre-identification is complete. The new user identification requires either a PIN or the first
digit of the called number to be entered.
• the call reaches the alerting state and instead of being connected, it is refused;
• after a configurable delay DISA calls back the user; the number called is obtained by adding a prefix to the user calling
number. There can be different prefixes for the three main different types of calling numbers: UNKNOWN, NATIONAL,
INTERNATIONAL;
• if Call Back fails, it can be repeated for a configured number of times, with a configurable delay between each call;
• once Call Back gets answered, the DISA proceeds in the same way as if the call was originated by user itself, except for
the user identification which is already complete.

47.1.5. Data Call Back

DISA Data Call Back is a feature which allows an user to command an internet connection for a remote device by a call. The
call is rejected (so is free of charge) and the configured data resource ( only IP and X25 resources ) is ordered to make a data
call.

DISA Data Call Back follows the below steps:

• user dials-in;

• the pre-identification assigns a service;

• the call reaches the alerting state and instead of being connected, it is refused;

• the configured data resource makes a data call.

Note
Once the connection toward internet is established, Abilis can be reached through a FQDN configuring the
DDNS resource.

47.2. CTIDISA resource

47.2.1. Activating the CTIDISA resource
Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:ctidisa

RES:CTIDISA ALREADY EXISTS

The CTIDISA resource may already exist in the system, but may not yet be active: set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctidisa

846
Draft DISA - Direct Inward System Access Draft

COMMAND EXECUTED

Caution
After adding or setting the CTIDISA active, you must restart the Abilis to make the resource running (use
the command warm start to reboot the Abilis).

Warning
DISA activation requires at least 30 MByte of free RAM (the activation of the module needs 13 MByte; the
configuration of users and services will increase the occupation of the RAM). Refer to Section 54.6.1, “How
can I view the current RAM usage?” to know how to know the RAM usage.

[11:01:39] ABILIS_CPX:s p ctidisa act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p ctidisa

RES:CtiDisa - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:YES
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE
WDIR:C:\APP\DISA\

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ctidisa; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

47.2.2. CTIDISA resource parameters

Use the following command to display the parameters of the resource; the d p ctidisa ? command shows the meaning of
parameters.

[12:01:25] ABILIS_CPX:d p ctidisa

RES:CtiDisa -------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:YES
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE
WDIR:C:\APP\DISA\

Meaning of the most important parameters:

LOG Logging functionalities activation/deactivation.

ACT Runtime CTIDISA activation/deactivation.

sesnum number of DISA simultaneous sessions (max. number of simultaneous calls)

RESTRICTED-CALLING Rejects calls from calling numbers that are not present in CTIDISA User table (CGI parameter).

PROVIDE-SG Allows insertion of CTIDISA User name in subaddress calling field .

Note
By default, DISA doesn't allow ISDN subaddress fields.

847
Draft DISA - Direct Inward System Access Draft

CALL-ABORT Sequence of digits to abort an outgoing call that is in any states prior to ACTIVE.

CALL-REPEAT Sequence of digits to repeat last call (when a session is in LOOPDIAL).

PIN-START Digit used to open PIN sequence (it is not editable).

PIN-END Digit used to close PIN sequence (it is not editable).

NP-CT Allows NET-PUBLIC to NET-PUBLIC call transfer; when both calls are outgoing, this transfer
is not allowed to avoid the “hang trunk” problem.

CTIP-TYPE CTIP type assigned to CTIDISA resource.

WDIR Working Directory where file messages are loaded.

The following command allows the administrator to change the configuration of the resource:

s p ctidisa parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:ctidisa; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart
are required (i.e. with warm start command).

47.3. CTIDISA tables

47.3.1. CTIDISA Service table
The CtiDisa Service Table can be managed with these commands:

• d ctidisa service : displays the complete table;

• d ctidisa service:<name> : displays the parameters of the specified service;

• a ctidisa service:<name> [par:val] : adds a new service in the table;

• c ctidisa service:<name> : clears the specified service in the table;

• s ctidisa service:<name> [par:val] : sets the configuration of the specified service.

The d ctidisa service ? command shows the meaning of parameters.

[12:02:51] ABILIS_CPX:d ctidisa service

Total number of services:1

-------------------------------------------------------------------------------
SERVICE:Default DESCR:System_default_service
MODE: DISA |INTRO-STATE: CREQ |INTRO:
ROUTING: PREFIX |CONN-DELAY: 6 |WELCOME:
MAX-CALLS: NOMAX |TRANSFER: NO |INITDIAL:
BC: Speech | |AFTERPIN: #
CB: NO |DIAL-TOUT: 30 |LOOPDIAL:
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL:
CB-NRTY: 1 |NUM-TOUT: 15 |CALLNA:
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT:
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: 0 |BUSY:
CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER:
CB-CGO: # |LOOP-NOANSWER: YES |DISC:
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD:
AUTO-CDO: # |LOOP-OTHER: YES |BYE: #
TOUT-CDO: #
PERMIT: *

848
Draft DISA - Direct Inward System Access Draft

CDI: -
CGI: -
-------------------------------------------------------------------------------

Note
The Default service is automatically created by the system. It is assigned to the calls which doesn't match
with other configured services; default values can be edited, except CDI and CGI fields.

Meaning of the most important parameters:

MODE Operational mode [DISA: the behaviour is the standard DISA behaviour; ACD: the Automatic Call
Distribution is enabled; INTRO: the behaviour is that of a “responder” for not-paid messages; DATA-
CB: the behaviour is that of ordering a CALL request to the specified resource and reject the call].

ROUTING Routing type for outgoing calls [PREFIX; EN-BLOC].

MAX-CALLS Maximum number of simultaneous calls allowed to this service.

BC Bearer Capability in outgoing calls [AUTO, Speech, 3.1Khz].

Refer to B-CHANNEL1 to have more information,

CB Enables/disables the Call Back.

CB-DELAY Time between the end of the incoming call and the Call Back call by the DISA.

CB-NRTY Maximum number of Call Back attempts.

CB-UNK-CDO Call Back number for UNKNOWN type.

CB-NAT-CDO Call Back number for NATIONAL type.

CB-INT-CDO Call Back number for INTERNATIONAL type.

CTIP-TYPE CTIP type for outgoing calls.

AUTO-CDO Automatic Called Number; if service matches and this field is not null, the number configured here is
automatically dialled (any other digit entered by the user is discarded).

PERMIT Permitted called number/prefixes.

CDI Incoming Called number that can be used at pre-identification. If it is set to DISABLED [#], the pre-
identification is performed using calling number.

CGI List of calling numbers that can be used at pre-identification to find the user. Use - prefix to delete
from the list a calling number previously inserted (e.g. “-123456”): several calling numbers can be
set joining values by the character , (e.g. “CGI:1234,5555,-77777”). This field is not allowed for the
Anonymous user and it is possible to set up to 2000 numbers.

CONN-DELAY Sets the duration of ALERTING state for incoming calls to DISA (i.e. the time between the reception
of the call and the response by the DISA).

TRANSFER Enables/disables call transfer after outgoing call is established; this function is inhibited when in the
service ACD is active.

ACD Enables/disables the Automatic Call Distribution.

ACD-INTERVAL Time interval in which a call in a queue tries to verify if the currently ACTIVE call gets disconnected.

DIAL-TOUT Maximum time to wait for the insertion of the first digit in post-selection (during INITDIAL).

PIN-TOUT Maximum time to wait for the insertion of the first digit of the PIN.

NUM-TOUT Maximum time to wait to complete the insertion of the number in post-selection.

BUSYDISC Duration of the played BUSY and DISC CtiSys tone.

849
Draft DISA - Direct Inward System Access Draft

MAX-LOOPS Maximum number of loop enabled [0-99: when the ACD is set to YES, this value is automatically set to
99 and it is not editable].

LOOP-BUSY Enables/disables the loop when the reason of a call failure is “user busy” (cause 0x91).

LOOP-NOANSWER Enables/disables the loop when the reason of a call failure is “user not responding, user alerted” (cause
0x93).

LOOP-DENIED Enables/disables the loop when the reason of a call failure is “selection not allowed for the user” (in
this kind of error the call was not sent to CTIR).

LOOP-OTHER Enables/disables the loop for reasons other than those precisely recognised (e.g. non-existent routing).

DISC-CAUSE Used to set the disconnect cause after the INTRO message has been played. This is useful for setting up
alternative routings. (Only for MODE:INTRO).

INTRO...BYE Refer to Section 47.8.1, “File audio format” to have more inforamations about these parameters.

47.3.2. CTIDISA User table

The CTIDISA User Table can be managed with these commands:

• d ctidisa user : displays the complete table;

• d ctidisa user:<name> : displays the parameters of the specified user;

• a ctidisa user:<name> [par:val] : adds a new user in the table;

• c ctidisa user:<name> : clears the specified user in the table;

• s ctidisa user:<name> [par:val] : sets the configuration of the specified user.

The d ctidisa user ? command shows the meaning of parameters.

[10:47:14] ABILIS_CPX:d ctidisa user

Total number of users:1

-------------------------------------------------------------------------------
USER:Anonymous
PIN: # |MAX-CALLS: NOMAX |PERMIT: SERVICE
SERVICE: AUTO |CB: NO |DENY: *
CGI: -
-------------------------------------------------------------------------------

Note
The Anonymous user is automatically created by the system; it identifies all the callers not configured in
others users.

Meaning of the most important parameters:

PIN Personal Identification Number code assigned to the user; if it is set to #, the user is identified only by its
calling number.

SERVICE Service name assigned to the user; if it is set to AUTO, the service discovered at the pre-identification phase is
used.

MAX-CALLS Maximum number of simultaneous calls allowed to the user.

CB Enable/disable Call Back [NO, YES].

PERMIT Permitted called numbers/prefixes.

DENY Denied called numbers/prefixes.

850
Draft DISA - Direct Inward System Access Draft

CGI List of calling numbers that can be used at pre-identification to find the user. Use - prefix to delete from the
list a calling number previously inserted (e.g. “-123456”): several calling numbers can be set joining values
by the character , (e.g. “CGI:1234,5555,-77777”). This field is not allowed for the Anonymous user and it is
possible to set up to 2000 numbers.

47.4. Example of Post Selection configuration

Purpose of example: how to configure the DISA resource to activate a “simple” post-selection.

Pre-identification is made through the called number verification.

Identification of the user is made through the PIN and the calling number verification.

Tip
More examples are available at Section 53.15, “How to configure CTIDISA to implement a responder”.

47.4.1. Configuring the CTIDISA resource

Activate the resource and set the RESTRICTED-CALLING parameter to NO.

[10:32:38] ABILIS_CPX:s p ctidisa act:yes restricted-calling:no

COMMAND EXECUTED

[10:32:56] ABILIS_CPX:d p ctidisa

RES:CtiDisa - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:NO
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE
WDIR:C:\APP\DISA\

Caution
To activate the changes made execute the initialization command init res:ctidisa.

47.4.2. Configuring the CTIDISA Service table

Create the “testdisa” service with the following characteristics:

• maximum number of simultaneous calls: 3;

• TRANSFER mode active;

• duration of ALERTING state for incoming calls: 0 seconds;

• Automatic Call Distribution disabled;

• maximum number of loops: 4;

• LOOP enabled for “user busy”, “no answer”, “selection not allowed” and “all other reasons”;

• tone set: “test”;

• pre-identification based on the called number “003”;

• call enabled in post-selection toward numbers starting with 5.

Type the following commands.

851
Draft DISA - Direct Inward System Access Draft

[17:50:26] ABILIS_CPX:a ctidisa service:testdisa

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:testdisa max-calls:3 transfer:yes conn-delay:0

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:testdisa MAX-LOOPS:4 LOOP-BUSY:yes LOOP-NOANSWER:yes LOOP-D

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:testdisa INTRO:test WELCOME:test INITDIAL:test AFTERPIN:tes

BUSY:test NOANSWER:test DISC:test HOLD:test BYE:test

[17:50:26] ABILIS_CPX:s ctidisa service:testdisa cdi:003 permit:5*

COMMAND EXECUTED

This is the result:

[17:50:26] ABILIS_CPX:d ctidisa service

- Not Saved (SAVE CONF) -------------------------------------------------------

Total number of services:2

-------------------------------------------------------------------------------
SERVICE:Default DESCR:System_default_service
MODE: DISA |INTRO-STATE: CREQ |INTRO:
ROUTING: PREFIX |CONN-DELAY: 6 |WELCOME:
MAX-CALLS: NOMAX |TRANSFER: NO |INITDIAL:
BC: Speech | |AFTERPIN: #
CB: NO |DIAL-TOUT: 30 |LOOPDIAL:
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL:
CB-NRTY: 1 |NUM-TOUT: 15 |CALLNA:
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT:
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: 0 |BUSY:
CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER:
CB-CGO: # |LOOP-NOANSWER: YES |DISC:
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD:
AUTO-CDO: # |LOOP-OTHER: YES |BYE: #
TOUT-CDO: #
PERMIT: *
CDI: -
CGI: -
-------------------------------------------------------------------------------
SERVICE:testdisa DESCR:
MODE: DISA |INTRO-STATE: CREQ |INTRO: test
ROUTING: PREFIX |CONN-DELAY: 0 |WELCOME: test
MAX-CALLS: 3 |TRANSFER: YES |INITDIAL: test
BC: Speech | |AFTERPIN: test
CB: NO |DIAL-TOUT: 30 |LOOPDIAL: test
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL: test
CB-NRTY: 1 |NUM-TOUT: 15 |CALLNA: test
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT: test
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: 4 |BUSY: test
CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER: test
CB-CGO: # |LOOP-NOANSWER: YES |DISC: test
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD: test
AUTO-CDO: # |LOOP-OTHER: YES |BYE: test
TOUT-CDO: #
PERMIT: 5*

852
Draft DISA - Direct Inward System Access Draft

CDI: 003
CGI: #
-------------------------------------------------------------------------------

47.4.3. Configuring the CTIDISA User table

Create two users, “user1” and “user2”, with the following characteristics:

User1:

• identification through the PIN: 2709;

• no service re-assignation;

• 1 simultaneous call;

• post-selection enabled toward all numbers allowed to service in which the caller has been identified;

• none verification of calling number.

User2:

• identification through the calling number;

• no service re-assignation;

• 1 simultaneous call;

• post-selection enabled toward number 515 and not enabled toward number 520;

• verification of the calling number (e.g. 12345678).

Configure “user1”:

[10:58:14] ABILIS_CPX:a ctidisa user:user1

COMMAND EXECUTED

[11:11:17] ABILIS_CPX:s ctidisa user:user1 PIN:2709 service:auto max-calls:1 permit:service deny:#

COMMAND EXECUTED

Configure “user2”:

[11:11:16] ABILIS_CPX:a ctidisa user:user2

COMMAND EXECUTED

[11:16:53] ABILIS_CPX:s ctidisa user:user2 service:auto max-calls:1 permit:515 deny:520 cgi:1234567

COMMAND EXECUTED

This is the result:

[11:22:40] ABILIS_CPX:d ctidisa user

Total number of users:3

-------------------------------------------------------------------------------
USER:Anonymous
PIN: # |MAX-CALLS: NOMAX |PERMIT: SERVICE
SERVICE: AUTO |CB: NO |DENY: *
CGI: -
-------------------------------------------------------------------------------
USER:user1

853
Draft DISA - Direct Inward System Access Draft

PIN: 2709 |MAX-CALLS: 1 |PERMIT: SERVICE

SERVICE: AUTO |CB: NO |DENY: #
CGI: *
-------------------------------------------------------------------------------
USER:user2
PIN: # |MAX-CALLS: 1 |PERMIT: 515
SERVICE: AUTO |CB: NO |DENY: 520
CGI: 12345678
-------------------------------------------------------------------------------

47.4.4. Configuring the CTI Routing

Assume to receive calls from a group of BRI ports (G2) or from clusters; route the calls toward DISA and enable post-
selection toward a group of POTS ports.

Configure incoming routings (toward DISA):

[10:27:28] ABILIS_CPX:a ctir pr:1 type:vtod poi:g2 cdi:00?

COMMAND EXECUTED

[10:27:51] ABILIS_CPX:a ctir pr:2 type:ctod sr:* cdi:00? sp:64000

COMMAND EXECUTED

Configure outgoing routing (from DISA toward PBX):

[10:28:31] ABILIS_CPX:a ctir pr:3 type:dtov poo:pbx cdi:5?? cdo:'cdi.s2' sp:64000

COMMAND EXECUTED

This is the result:

[10:28:36] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 10/11/2010 09:34:44 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
1 VtoD G2 CtiDisa 00? *
-------------------------------------------------------------------------------
2 CtoD * CtiDisa 00? *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------
3 DtoV CtiDisa PBX 5?? 'CDI.S2'
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------
...

854
Draft DISA - Direct Inward System Access Draft

-------------------------------------------------------------------------------

47.5. Example of Automatic Call Distribution

configuration
Pre-identification is based on called number verification. User identification is based on calling number verification. The
automatic call is enabled toward a number in post-selection (possible only after user identification).

Refer to Section 47.5, “Example of Automatic Call Distribution configuration” to have more information about ACD.

Tip
More examples are available at Section 53.15, “How to configure CTIDISA to implement a responder”.

47.5.1. Configuring the CTIDISA resource

Activate the resource and set the RESTRICTED-CALLING parameter to NO.

[10:32:38] ABILIS_CPX:s p ctidisa act:yes restricted-calling:no

COMMAND EXECUTED

[10:32:56] ABILIS_CPX:d p ctidisa

RES:CtiDisa - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:NO
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE
WDIR:C:\APP\DISA\

Caution
To activate the changes made execute the initialization command init res:ctidisa.

47.5.2. Configuring the CTIDISA Service table

Create the “acd” service with the following characteristics:

• maximum number of simultaneous calls: 5;

• duration of ALERTING status for incoming calls: 0 seconds;

• Automatic Call Distribution enabled;

• time interval between two call attempts: 15 seconds;

• LOOP enabled for “user busy”, “no answer”, “selection not allowed” and “all other reasons”;

• use of tone set “test”;

• pre-identification based on the called number: 002;

• call enabled in post-selection toward number 501;

• automatic call toward number 501, after identification.

Type the following commands.

[17:50:26] ABILIS_CPX:a ctidisa service:acd

855
Draft DISA - Direct Inward System Access Draft

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:acd max-calls:5 conn-delay:0

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:acd mode:acd acd-interval:15

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:acd LOOP-BUSY:yes LOOP-NOANSWER:yes LOOP-DENIED:yes LOOP-OT

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:acd INTRO:test WELCOME:test INITDIAL:test AFTERPIN:test LOO

BUSY:test NOANSWER:test DISC:test HOLD:test BYE:test

[17:50:26] ABILIS_CPX:s ctidisa service:acd cdi:002 permit:501

COMMAND EXECUTED

[17:50:26] ABILIS_CPX:s ctidisa service:acd auto-cdo:501

COMMAND EXECUTED

This is the result:

[10:47:25] ABILIS_CPX:d ctidisa service

- Not Saved (SAVE CONF) -------------------------------------------------------

Total number of services:2

-------------------------------------------------------------------------------
SERVICE:acd DESCR:
MODE: ACD |INTRO-STATE: CREQ |INTRO: test
ROUTING: PREFIX |CONN-DELAY: 0 |WELCOME: test
MAX-CALLS: 5 |TRANSFER: NO |INITDIAL: test
BC: Speech |ACD-INTERVAL: 15 |AFTERPIN: test
CB: NO |DIAL-TOUT: 30 |LOOPDIAL: test
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL: test
CB-NRTY: 1 |NUM-TOUT: 15 |CALLNA: test
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT: test
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: (99) |BUSY: test
CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER: test
CB-CGO: # |LOOP-NOANSWER: YES |DISC: test
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD: test
AUTO-CDO: 501 |LOOP-OTHER: YES |BYE: test
TOUT-CDO: #
PERMIT: 501
CDI: 002
CGI: #
-------------------------------------------------------------------------------
SERVICE:Default DESCR:System_default_service
MODE: DISA |INTRO-STATE: CREQ |INTRO:
ROUTING: PREFIX |CONN-DELAY: 6 |WELCOME:
MAX-CALLS: NOMAX |TRANSFER: NO |INITDIAL:
BC: Speech | |AFTERPIN: #
CB: NO |DIAL-TOUT: 30 |LOOPDIAL:
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL:
CB-NRTY: 1 |NUM-TOUT: 15 |CALLNA:
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT:
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: 0 |BUSY:

856
Draft DISA - Direct Inward System Access Draft

CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER:

CB-CGO: # |LOOP-NOANSWER: YES |DISC:
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD:
AUTO-CDO: # |LOOP-OTHER: YES |BYE: #
TOUT-CDO: #
PERMIT: *
CDI: -
CGI: -
-------------------------------------------------------------------------------

47.5.3. Configuring the CTIDISA User table

Create the user “acd” with the following characteristics:

• identification through the calling number;

• no service re-assigning;

• maximum number of simultaneous call: 3;

• post-selection enabled toward all numbers allowed to service in which the caller has been identified;

• verification of the calling number: 01234567.

Type the following commands.

[10:58:14] ABILIS_CPX:a ctidisa user:acd

COMMAND EXECUTED

[15:41:04] ABILIS_CPX:s ctidisa user:acd service:auto max-calls:3 permit:* deny:# cgi:01234567

COMMAND EXECUTED

This is the result:

[15:42:20] ABILIS_CPX:d ctidisa user:acd

- Not Saved (SAVE CONF) -------------------------------------------------------

Total number of users:4

-------------------------------------------------------------------------------
USER:acd
PIN: # |MAX-CALLS: 3 |PERMIT: *
SERVICE: AUTO |CB: NO |DENY: #
CGI: 01234567
-------------------------------------------------------------------------------

47.5.4. Configuring CTI Routings

Assume to receive calls from a group of BRI ports (G2) or from clusters; route the calls toward DISA and enable post-
selection toward a group of POTS ports.

Configure incoming routings (toward DISA):

[12:05:34] ABILIS_CPX:a ctir pr:1 type:vtod poi:g2 cdi:00?

COMMAND EXECUTED

[12:29:54] ABILIS_CPX:a ctir pr:2 type:ctod sr:* cdi:00? sp:64000

COMMAND EXECUTED

Configure outgoing routing (from DISA toward PBX):

857
Draft DISA - Direct Inward System Access Draft

[14:29:04] ABILIS_CPX:a ctir pr:3 type:dtov poo:pbx cdi:5?? cdo:'cdi.s2' sp:64000

COMMAND EXECUTED

This is the result:

[12:05:48] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF) -------------------------------------------------------

Last change: 20/12/2010 12:05:48 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 VtoD G2 CtiDisa 00? *
-------------------------------------------------------------------------------
2 CtoD * CtiDisa 00? *
NO ANY NO Dft * *
64000 Sys * * Sys Sys * *
-------------------------------------------------------------------------------
3 DtoV CtiDisa PBX 5?? 'CDI.S2'
NO ANY NO Dft * *
64000 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

47.6. Example of Call Back configuration

This section shows a Call Back example, in which users call DISA from a mobile phone; the user identification is based on
the calling number verification.

Tip
More examples are available at Section 53.15, “How to configure CTIDISA to implement a responder”.

47.6.1. Configuring the CTIDISA resource

Activate the resource and set the RESTRICTED-CALLING parameter to YES.

[10:32:38] ABILIS_CPX:s p ctidisa act:yes restricted-calling:yes

COMMAND EXECUTED

[10:32:56] ABILIS_CPX:d p ctidisa

RES:CtiDisa - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:YES
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE

858
Draft DISA - Direct Inward System Access Draft

WDIR:C:\APP\DISA\

Caution
To activate the changes made execute the initialization command init res:ctidisa.

47.6.2. Configuring the CTIDISA Service table

Create the “call_back” service with the following characteristics:

• maximum number of simultaneous calls: 5;

• duration of ALERTING state for incoming calls: 4 seconds;

• Call Back enabled;

• Call Back delay: 5 seconds

• number of Call Back attempts: 3

• maximum number of loop:3

• LOOP enabled for “user busy”, “no answer”, “selection not allowed” and “all other reasons”;

• use of tone set “test”;

• pre-identification based on calling number: 3456789012.

Type the following commands.

[14:55:16] ABILIS_CPX:a ctidisa service:call_back

COMMAND EXECUTED

[14:55:37] ABILIS_CPX:s ctidisa service:call_back max-calls:5 conn-delay:4

COMMAND EXECUTED

[14:57:07] ABILIS_CPX:s ctidisa service:call_back cb:yes cb-delay:5 cb-nrty:3

COMMAND EXECUTED

[15:01:02] ABILIS_CPX:s ctidisa service:call_back max-loops:3 LOOP-BUSY:yes LOOP-NOANSWER:yes LOOP-

COMMAND EXECUTED

[15:02:35] ABILIS_CPX:s ctidisa service:call_back INTRO:test WELCOME:test INITDIAL:test AFTERPIN:te

IDENFAIL:test CALLNA:test ALERT:test BUSY:test NOANSWER:test DISC:test HOLD:test BYE:test

COMMAND EXECUTED

[15:04:53] ABILIS_CPX:s ctidisa service:call_back cgi:3456789012 cdi:*

COMMAND EXECUTED

This is the result:

[03:33:15] ABILIS_CPX:d ctidisa service:call_back

- Not Saved (SAVE CONF) -------------------------------------------------------

Total number of services:3

-------------------------------------------------------------------------------
SERVICE:call_back DESCR:

859
Draft DISA - Direct Inward System Access Draft

MODE: DISA |INTRO-STATE: CREQ |INTRO: test

ROUTING: PREFIX |CONN-DELAY: 4 |WELCOME: test
MAX-CALLS: 5 |TRANSFER: NO |INITDIAL: test
BC: Speech | |AFTERPIN: test
CB: YES |DIAL-TOUT: 30 |LOOPDIAL: test
CB-DELAY: 5 |PIN-TOUT: 15 |IDENFAIL: test
CB-NRTY: 3 |NUM-TOUT: 15 |CALLNA: test
CB-UNK-CDO: 'CGI' |BUSYDISC: 4 |ALERT: test
CB-NAT-CDO: 0'CGI' |MAX-LOOPS: 3 |BUSY: test
CB-INT-CDO: 00'CGI' |LOOP-BUSY: YES |NOANSWER: test
CB-CGO: # |LOOP-NOANSWER: YES |DISC: test
CTIP-TYPE-O: * |LOOP-DENIED: YES |HOLD: test
AUTO-CDO: # |LOOP-OTHER: YES |BYE: test
TOUT-CDO: #
PERMIT: *
CDI: *
CGI: 3456789012
-------------------------------------------------------------------------------

47.6.3. Configuring the CTIDISA User table

Create the user “call_back” with the following characteristics:

• Call Back enabled;

• identification through the calling number: 3456789012;

• no service re-assignation;

• maximum number of simultaneous call: 1.

Type the following commands.

[10:58:14] ABILIS_CPX:a ctidisa user:call_back

COMMAND EXECUTED

[15:11:38] ABILIS_CPX:s ctidisa user:call_back cb:yes service:auto max-calls:1 permit:service deny:

COMMAND EXECUTED

This is the result:

[03:35:29] ABILIS_CPX:d ctidisa user:call_back

- Not Saved (SAVE CONF) -------------------------------------------------------

Total number of users:5

-------------------------------------------------------------------------------
USER:call_back
PIN: # |MAX-CALLS: 1 |PERMIT: SERVICE
SERVICE: AUTO |CB: YES |DENY: #
CGI: 3456789012
-------------------------------------------------------------------------------

47.6.4. CTI Routing configuration

Assume to receive calls from a group of ports (G2) associated to UMTS Box; enable Call Back toward this ports.

To verify the configuration of the group of ports type:

[12:04:16] ABILIS_CPX:d ctig

--------------------------------------+--------------------+-------------------

860
Draft DISA - Direct Inward System Access Draft

[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
1 NO R ST |31 32 33 34 . |. . . . .
--------------------------------------+--------------------+-------------------
2 NO R ST |201 202 203 204 . |. . . . .
--------------------------------------+--------------------+-------------------

Configure incoming routings (toward DISA):

[12:05:34] ABILIS_CPX:a ctir pr:1 type:vtod poi:g2 cdi:* sp:64000 coders:g.711 mj:80 dj:0

COMMAND EXECUTED

Configure outgoing routing (from DISA toward PBX):

[14:29:04] ABILIS_CPX:a ctir pr:2 type:dtov poo:g2 cdi:0039* cdo:'cdi.s5' sp:64000 coders:g.711 mj:

COMMAND EXECUTED

[14:29:04] ABILIS_CPX:a ctir pr:3 type:dtov poo:g1 cdi:* sp:64000 coders:g.711 mj:80 dj:0

COMMAND EXECUTED

This is the result:

[16:05:49] ABILIS_CPX:d ctir

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 20/12/2010 11:59:24 CET

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5

-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 VtoD G2 CtiDisa * *
NO ANY NO Dft * *
64000 Sys 0 80 Sys Sys * *
* *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
2 DtoV CtiDisa G2 0039* 'CDI.S5'
NO ANY NO Dft * *
64000 Sys 0 80 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------
3 DtoV CtiDisa G1 * *

861
Draft DISA - Direct Inward System Access Draft

NO ANY NO Dft * *
64000 Sys 0 80 Sys Sys * *
NO Sys * *
* *
Sys AUTO AUTO Sys Sys NO Sys Sys Sys Sys Sys
G.711
-------------------------------------------------------------------------------

47.7. Example of Data Call Back configuration

Data-cb allows to order a connection toward Internet making a phone call. The call is rejected and so it's free of charge.

Tip
More examples are available at Section 53.15, “How to configure CTIDISA to implement a responder”.

47.7.1. Configuring the CTIDISA resource

Activate the resource and set the RESTRICTED-CALLING parameter to YES.

[10:32:38] ABILIS_CPX:s p ctidisa act:yes restricted-calling:yes

COMMAND EXECUTED

[10:32:56] ABILIS_CPX:d p ctidisa

RES:CtiDisa - Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------

------------------------------------------------------------------------
Run DESCR:Direct_Inward_System_Access
LOG:NO ACT:YES sesnum:10 RESTRICTED-CALLING:YES
PROVIDE-SG:NO CALL-ABORT:** CALL-REPEAT:** PIN-START:* PIN-END:#
NP-CT:SYS CTIP-TYPE:NET-PRIVATE
WDIR:C:\APP\DISA\

Caution
To activate the changes made execute the initialization command init res:ctidisa.

47.7.2. Configuring the CTIDISA Service table

Create the “call_back” service with the following characteristics:

• maximum number of simultaneous calls: 5;

• calling input number which activates the data call back is 10;

• the data call back uses res:ip-6 to establish a connection toward internet

Type the following commands.

[05:15:50] ABILIS_CPX:a ctidisa service:data_cb

COMMAND EXECUTED

[05:17:33] ABILIS_CPX:s ctidisa service:data_cb mode:data-cb max-calls:5 cdi:10 cd-res:ip-6

COMMAND EXECUTED

[05:17:38] ABILIS_CPX:d ctidisa service:data_cb

- Not Saved (SAVE CONF) -------------------------------------------------------

862
Draft DISA - Direct Inward System Access Draft

Total number of services:4

-------------------------------------------------------------------------------
SERVICE:data_cb DESCR:
MODE: DATA-CB |CD-RES: Ip-6
MAX-CALLS: NOMAX |DISC-CAUSE: 81,90
CDI: 10
CGI: #
-------------------------------------------------------------------------------

47.7.3. Configuring CTI Routings

Ports 31 and 32 are connected to an ISDN line and they belong to the group G1. Assume to order a connection toward
Internet calling the ISDN number 09999901. CTIR routes calls to DISA which establish a connection toward Internet using
data call back.

[05:51:17] ABILIS_CPX:d ctig

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

--------------------------------------+--------------------+-------------------
[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
1 NO R ST |31 32 . . . |. . . . .
--------------------------------------+--------------------+-------------------

Configure routing toward DISA:

[05:54:26] ABILIS_CPX:a ctir pr:1 type:vtod poi:g1 cdi:09999901 cdo:10

COMMAND EXECUTED

[05:54:58] ABILIS_CPX:d ctire pr:1

- Not Saved (SAVE CONF), Not Refreshed (INIT) ---------------------------------

Last change: 14/11/2010 05:54:58 CET

PR:1 DESCR:data_cb
ACT:YES EDT:NO
TYPE:VtoD POI:G1 POO:CtiDisa EEC:NO
NEXT:NO CDI:09999901 CDO:10
LAST:ANY CGI:* CGO:*
T301:Dft SDI:* SDO:*
UDT:NO SGI:* SGO:*
RGI:* RGO:*
IG:Sys OG:Sys SG:Sys DL:Sys DH:Sys
FMRLY:Sys FAXSP:AUTO MODSP:AUTO FMLVL:Sys FMDJ:Sys FMMJ:Sys
SP:6400 SC:Sys DJ:Sys MJ:Sys ECM:Sys
CODERS:Sys
TI1:ALL,00:00-23:59 TI2:# TI3:# TI4:# TI5:#

47.8. Message files

Every DISA action corresponds to a tone or a message, which informs the user on the action realized. Filenames are
predefined for the event correlated to the message. This section shows how to load the message files and how to compile
them with Abilis.

47.8.1. File audio format

Message files must be recorded on a PC and saved in WAV format with CCITT A-law (or u-law) 8KHz, 8 bit, Mono
(Windows sound recorder supports it).

863
Draft DISA - Direct Inward System Access Draft

Figure 47.1. Audio file format

Messages must be renamed according to the following table:

864
Draft DISA - Direct Inward System Access Draft

Table 47.1. Message filenames

Filename Event Notes

INTRO Intro message. This message is played before the call
goes ACTIVE. When the network
allows it to pass it can be used to play
an introductory message prior to start
the paid part of the call.
WELCOME Welcome message. This message welcomes callers. It is
played only once and it is interrupted
when the caller enters a digit; when it
ends the INITDIAL phase will start
or AUTO-CDO is called. It can't be a
CtiSys tone.
INITDIAL Initial dial. It is the first dial message played; from
this moment the user can make a call or
enter a PIN (the message is interrupted
when the caller enters a digit).
AFTERPIN Pin entered and user identification It is played when the user enters a
succeeded. PIN and the identification has been
successfully.
IDENFAIL Identification failure message. It is played when the identification fails;
it can occur only when user enters a
wrong PIN.
CALLNA Called number not allowed. It is played when the number/prefix
called by the user is not allowed.
LOOPDIAL Dial after loop. It is played when the post-selection
fails (and loop is active) or when ACD
is active. If this file is missing the
INITDIAL message is played.
ALERT Alerting message. It is played when called number is
alerting. Normally this file is not
present and DISA uses default CtiSys
tones.
BUSY User Busy (cause 0x91). It is played when a call fails with reason
“user busy” (ISDN cause 0x91).
NOANSWER User not answered after a timeout It is played when a call fails with
(cause 0x93). reason “user not responding, user
alerted” (ISDN cause 0x93).
DISC Generic failures. It is played upon failures not covered by
specific events.
HOLD Call Parked. It is played when the call gets parked; it
requires that DISA still control the call
in active state. Normally this file is not
present and DISA uses default CtiSys
tones.
BYE Goodbye. It is played before closing the call.
Normally this file is not present and
DISA doesn't reproduce anything (the
file can't be a CtiSys tone).

Audio files must be loaded, using either FTP of FILE PUT commands, into the appropriate directory (or a subdirectory) of
the following location:

• <disa-working-dir>\MSG\ , tipically C:\APP\DISA\MSG\

For example if you want to create the messages set “prova”, the files must be copied in the directory:

865
Draft DISA - Direct Inward System Access Draft

• C:\APP\DISA\MSG\prova

Warning
The subdirectory “msg” (and its subdirectories) doesn't exist by default; you must previously create them
with an FTP client or using the command msg add ctidisa <msgset>. Go to the FTP section for more
information about FTP resource.

Once WAV files are loaded, they must be converted in the CPM (CPX Packed Messages) format (i.e. the format that allows
Abilis to play the messages with any coder supported).

47.8.2. Commands to manage audio files

File messages can be managed with the following commands:

• msg update ctidisa [MsgSet [MsgName]]: recreates CPM files only if the corresponding WAV file is newer;

• msg rebuild ctidisa [MsgSet [MsgName]]: recreates CPM files regardless of the corresponding WAV file date/time;

• msg extract ctidisa [MsgSet [MsgName]]: extracts the G.711 A-law from the CPM file and writes the corresponding
WAV file. The date/time of the extracted WAV should be set equal to the CPM date/time, so that the MSG UPDATE
command doesn't recognise it as newer.

Warning
The operation could persist for some minutes; the duration depends on the number of coder installed in the
CPX.

47.8.3. Example of insertion of WAV files and creation of CPM

This section shows an example of use of the rebuild command.

1. Connect through FTP to the Abilis and create the directory <disa-working-dir>\MSG (tipically C:\APP\DISA\MSG).

Warning
You must log in the Abilis with an user enabled to create and edit directories and files. (see FTP section).

2. Record an audio file for every event (WELCOME, INITDIAL, AFTERPIN, LOOPDIAL, IDENFAIL, CALLNA,
ALERT, BUSY, NOANSWER, DISC, HOLD, BYE) and save it in the following formats (you can use the Windows
sound recorder):

• WAV CCITT A-law 8KHz, 8 bit, Mono

• WAV CCITT u-law 8KHz, 8 bit, Mono

3. Rename the files according the syntax event.wav (e.g. initdial.wav, alert.wav, …).

4. Load the files into the directory naming the “message set” desired; you have two possibilities:

• through FTP: you must access to the directory and load the wav files (the FTP user must have the requested
authorizations);

• from CPX prompt with the FILE PUT command.

If you want to load the file bye.wav in the “test” directory, type:

[00:56:19] ABILIS_CPX:file put z c:\app\disa\msg\test\bye.wav

READY TO RECEIVE FILE...

Upload Zmodem

bye.wav (17.8 KB, 0:00 min = 18246 cps eff)

866
Draft DISA - Direct Inward System Access Draft

FILE TRANSFER ENDED, PRESS <ENTER> TO CONTINUE...

FILE TRANSFER SUCCESSFULLY COMPLETED

RECEIVED FILE 'c:\app\disa\msg\test\bye.wav' FORMAT IS UNKNOWN.

NO CHECK DONE.

Note
The command must be repeated for every file.

5. To verify the directory content, type:

[00:15:12] ABILIS_CPX:sys dir c:\app\disa\msg\test

Directory listing of c:\app\disa\msg\test

. <DIR> 30/06/2006 00:11:48

.. <DIR> 30/06/2006 00:11:48
afterpin.wav 17566 30/06/2006 00:12:02
alert.wav 17686 30/06/2006 00:12:02
busy.wav 17486 30/06/2006 00:12:02
bye.wav 18246 30/06/2006 00:12:02
callna.wav 22606 30/06/2006 00:12:02
disc.wav 18126 30/06/2006 00:12:02
hold.wav 18326 30/06/2006 00:12:02
idenfail.wav 20086 30/06/2006 00:12:02
initdial.WAV 18046 30/06/2006 00:12:02
loopdial.wav 16486 30/06/2006 00:12:02
noanswer.wav 19886 30/06/2006 00:12:02
welcome.wav 16435 30/06/2006 00:12:02

Found 2 directories, 12 files.

Total 62 MB, Used 11 MB, Free 50 MB.

6. Create the CPM file with the command:

[00:15:16] ABILIS_CPX:msg rebuild ctidisa test

YOU ASKED TO REBUILD CTIDISA test

PROCEED (N/Y)?y

MSG REBUILD IN PROGRESS ON CTIDISA test

THIS MAY TAKE FEW MINUTES (Type CTRL+C + ENTER to stop)...

Converting C:\APP\DISA\MSG\test\afterpin.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\alert.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\busy.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\bye.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\callna.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\disc.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\hold.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\idenfail.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\initdial.WAV
Converting to G711A/64k .......... END

867
Draft DISA - Direct Inward System Access Draft

Converting C:\APP\DISA\MSG\test\loopdial.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\noanswer.wav
Converting to G711A/64k .......... END
Converting C:\APP\DISA\MSG\test\welcome.wav
Converting to G711A/64k .......... END

COMMAND COMPLETED

7. Type the following command to verify the directory content:

[00:18:04] ABILIS_CPX:sys dir c:\app\disa\msg\test

Directory listing of c:\app\disa\msg\test

. <DIR> 30/06/2006 00:11:48

.. <DIR> 30/06/2006 00:11:48
afterpin.wav 17566 30/06/2006 00:12:02
alert.wav 17686 30/06/2006 00:12:02
busy.wav 17486 30/06/2006 00:12:02
bye.wav 18246 30/06/2006 00:12:02
callna.wav 22606 30/06/2006 00:12:02
disc.wav 18126 30/06/2006 00:12:02
hold.wav 18326 30/06/2006 00:12:02
idenfail.wav 20086 30/06/2006 00:12:02
initdial.WAV 18046 30/06/2006 00:12:02
loopdial.wav 16486 30/06/2006 00:12:02
noanswer.wav 19886 30/06/2006 00:12:02
welcome.wav 16435 30/06/2006 00:12:02
afterpin.CPM 18346 30/06/2006 00:18:18
alert.CPM 18469 30/06/2006 00:18:18
busy.CPM 18264 30/06/2006 00:18:20
bye.CPM 19043 30/06/2006 00:18:20
callna.CPM 23512 30/06/2006 00:18:20
disc.CPM 18920 30/06/2006 00:18:22
hold.CPM 19125 30/06/2006 00:18:22
idenfail.CPM 20929 30/06/2006 00:18:22
initdial.CPM 18838 30/06/2006 00:18:24
loopdial.CPM 17239 30/06/2006 00:18:24
noanswer.CPM 20724 30/06/2006 00:18:26
welcome.wav 19765 30/06/2006 00:18:26

Found 2 directories, 24 files.

Total 62 MB, Used 12 MB, Free 50 MB.

8. The wav files can be deleted from the directory; you have two possibilities:

• through FTP: you must access to the directory and delete the wav files (the FTP user must have the requested
authorizations);

• from CPX prompt with the file delete command.

Type the below command to delete the bye.wav file in the “test” directory:

[19:05:57] ABILIS_CPX:file delete c:\app\disa\msg\test\bye.wav

FILE 'C:\APP\DISA\MSG\TEST\BYE.WAV' IS GOING TO BE DELETED.

PROCEED (N/Y)?y

FILE 'C:\APP\DISA\MSG\TEST\BYE.WAV' DELETED

Note
The command must be repeated for every file.

868
Draft DISA - Direct Inward System Access Draft

47.9. CTIDISA diagnostics and statistics

47.9.1. CTIDISA diagnostics
The following commands are used to display the diagnostics of the CTIDISA resource:

d d ctidisa Shows diagnostic information, such as the state resource, the number of used channels, the name of the
identified user and service, the Q931 state of the incoming/outgoing call, the calling/called number of the
incoming/outgoing call, the connection time of the current incoming/outgoing call, the current number of
loop.

d de ctidisa Shows diagnostic information in an extended format: the same information listed for d d ctidisa and in
addition the call identifier of incoming/outgoing call, the internal state of the channel, the type of tone/
message and the name of CTISYS tone or Vocal message which are playing.

[03:45:23] ABILIS_CPX:d d ctidisa

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
STATE:ACTIVE USED-CHAN:0
- DISA Channels diagnostics --------------------------------------------
CH: User Q931State-In CGI Time-In Nrty
Service Q931State-Out CDO Time-Out Loop
------------------------------------------------------------------------
0 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
1 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
2 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
3 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
4 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
5 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
6 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
7 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
8 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------
9 DISCONNECTED 0 0
DISCONNECTED 0 0
------------------------------------------------------------------------

[03:56:05] ABILIS_CPX:d de ctidisa

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
STATE:ACTIVE USED-CHAN:0
- DISA Channels diagnostics --------------------------------------------
CH: User Q931State-In CGI Time-In Nrty
Service Q931State-Out CDO Time-Out Loop

869
Draft DISA - Direct Inward System Access Draft

Id-In Id-Out Phase Playing Tone/Message

------------------------------------------------------------------------
0 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
1 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
2 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
3 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
4 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
5 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
6 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
7 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
8 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------
9 DISCONNECTED 0 0
DISCONNECTED 0 0
0 0
------------------------------------------------------------------------

47.9.2. CTIDISA statistics

The following commands are used to display the statistics of the CTIDISA resource:

d s ctidisa Shows statistic information, such as the number of incoming/outgoing calls, the number of incoming/
outgoing calls that reached ACTIVE state, the number of incoming/outgoing calls that were closed prior
to reach ACTIVE state, the number of incoming/outcoming voice frames;

d se ctidisa Shows statistic information in an extended format: the same information listed for d s ctidisa command
are shown for each channel.

[22:15:27] ABILIS_CPX:d s ctidisa

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
--- Cleared 091:01:20:34 ago, on 01/10/2007 at 04:51:42 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-CALL | 5182| |I-SUCC-CALL| 5107| |
I-TIME-CALL| 695438| |I-FAIL-CALL| 0| |
I-VOICE-FRM| 34847445| 40743886| | | |

870
Draft DISA - Direct Inward System Access Draft

O-CALL | | 4369|O-SUCC-CALL| | 4010|

O-TIME-CALL| | 592376|O-FAIL-CALL| | 1000|
O-VOICE-FRM| 26127200| 26127186|
------------------------------------------------------------------------

[22:15:30] ABILIS_CPX:d se ctidisa

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
--- Cleared 091:01:21:12 ago, on 01/10/2007 at 04:51:41 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-CALL | 5182| |I-SUCC-CALL| 5107| |
I-TIME-CALL| 695438| |I-FAIL-CALL| 0| |
I-VOICE-FRM| 34847445| 40743886| | | |
O-CALL | | 4369|O-SUCC-CALL| | 4010|
O-TIME-CALL| | 592376|O-FAIL-CALL| | 1000|
O-VOICE-FRM| 26127200| 26127186|
------------------------------------------------------------------------
CH:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 1096| 1098|I-DTMF | 1| |
O-VOICE-FRM| 0| 0|
------------------------------------------------------------------------
CH:1
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 8805| 10777|I-DTMF | 1| |
O-VOICE-FRM| 5981| 5981|
------------------------------------------------------------------------
CH:2
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 17402| 18212|I-DTMF | 1| |
O-VOICE-FRM| 16219| 16219|
------------------------------------------------------------------------
CH:3
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 18028| 22767|I-DTMF | 1| |
O-VOICE-FRM| 12621| 12621|
------------------------------------------------------------------------
CH:4
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 1289| 2045|I-DTMF | 1| |
O-VOICE-FRM| 0| 0|
------------------------------------------------------------------------
CH:5
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 6285| 8882|I-DTMF | 1| |
O-VOICE-FRM| 2996| 2996|
------------------------------------------------------------------------
CH:6
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 8851| 13394|I-DTMF | 1| |
O-VOICE-FRM| 3016| 3016|
------------------------------------------------------------------------
CH:7
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 0| 0|I-DTMF | 0| |
O-VOICE-FRM| 0| 0|
------------------------------------------------------------------------
CH:8
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 0| 0|I-DTMF | 0| |
O-VOICE-FRM| 0| 0|

871
Draft DISA - Direct Inward System Access Draft

------------------------------------------------------------------------
CH:9
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
I-VOICE-FRM| 0| 0|I-DTMF | 0| |
O-VOICE-FRM| 0| 0|
------------------------------------------------------------------------

47.9.3. Advanced Debug of the CtiDisa resource

This section shows the commands used to view the state of the calls and the queues of the CtiDISA resource.

Note
To use these commands you need to have administrator or super user rights.

Type tyhe following command to view the commands allowed:

[03:59:00] ABILIS_CPX:debug res:ctidisa lsn:0

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
BufferLength:288 Date/Time:14/11/2010 03:59:07 TraceTime:<NotRunning>

DISA port: Debug info

LSN:0 This help message
LSN:1 Driver object (bin)
LSN:2 Diagnostics (txt)
LSN:3 Statistics (txt)
LSN:100 FRMWR test (txt)
LSN:200 Start tracing of voice frames (txt)
LSN:201 Stop tracing of voice frames (txt)
Subobjects:
CMD:Cx Channel (0-y)

The following command shows the number of used channels and the number of the used/free queues.

[10:55:10] ABILIS_CPX:debug res:ctidisa lsn:2

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
BufferLength:243 Date/Time:25/06/2007 10:55:14 TraceTime:<NotRunning>

DISA port - diagnostics

--------------+----------
Name | Value
--------------+----------
State | ACTIVE
Used channels | 2
FIFO - used | 0
FIFO - free | 29
--------------+----------

The following command shows the statistics of the calls.

[10:55:57] ABILIS_CPX:debug res:ctidisa lsn:3

RES:CtiDisa -------------------------------------------------------------------
Direct_Inward_System_Access
BufferLength:451 Date/Time:25/06/2007 10:55:59 TraceTime:<NotRunning>

DISA port - statistics

------------+----------

872
Draft DISA - Direct Inward System Access Draft

Name | Value
------------+----------
Event IN | 14397
Event OUT | 12300
Call IN | 1440
Call ACC | 1440
Call REJ | 0
Voice IN | 11835552
Voice OUT | 13004449
Handle OPN | 3525
Handle CLS | 3523
Handle DSC | 0
Timer RSQ | 3960
Timer CLR | 2492
Timer EXP | 1468
------------+----------

47.10. DISA administration through web interface

Creating an user and enabling it to the HTTP service are needed to access the Abilis CPX Web Interface.

47.10.1. Configuration of the HTTP rights

Add the user “disa” and enable it to HTTP.

[11:01:39] ABILIS_CPX:a user:disa pwd:disa http:yes

COMMAND EXECUTED

[04:02:54] ABILIS_CPX:d user

- Not Saved (SAVE CONF) -------------------------------------------------------

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
disa *** YES # # NO NO YES NO NO NO
guest NO # # NO NO NO NO NO NO

Add the HTTP rights for the user “disa”.

[11:01:39] ABILIS_CPX:a http rights path:/sys/admin/disa/ user:disa

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d http rights

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
-------------------------------------------------------------------------------
1 /sys/
admin r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
2 /sys/pub/
anonymous r--- ---- YES PLAIN,SSL
-------------------------------------------------------------------------------
3 /sys/admin/disa/
disa r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------

47.10.2. DISA administration

Go to Abilis Home page, login and click CTI administration to access to the following page.

873
Draft DISA - Direct Inward System Access Draft

For example, by clicking on Message set(s) View/Change link, it is possible to manage the message files.

874
Draft Draft

Chapter 48. CTIAS - CTI Advanced

Services
Luigi Demuro

Table of Contents
48.1. CTIAS - CTI Advanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.1. Activating the CTIAS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
48.1.2. CTIAS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2. CTIVM - CTI Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.1. Activating the CTIVM resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
48.2.2. CTIVM resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
48.2.3. CTIVM diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
48.2.4. CTIVM configuration through CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
48.2.5. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884

48.1. CTIAS - CTI Advanced Services

CTIAS resource is the container of CTI plugins (voice mail and other services which will be developed in the future
releases). Administrator can choose to:

• activate CTIAS and then the desired plugins;

• activate directly the desired plugin. Abilis will automatically activate the CTIAS resource if it's not.

48.1.1. Activating the CTIAS resource

Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:ctias

RES:CTIAS ALREADY EXISTS

The CTIAS resource may already exist in the system, but may not yet be active. Set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctisms

COMMAND EXECUTED

Caution
You must restart the Abilis to make the resource running (use the command warm start to reboot the
Abilis) after adding or setting the CTIAS active.

[13:07:41] ABILIS_CPX:d p ctias

RES:CtiAs ---------------------------------------------------------------------
Run DESCR:CTI_Advanced_Services_entry_point
sesnum:0 TC-SESNUM:1

Caution
Execute the initialization command init res:ctias to activate the changes made on the upper case parameters;
use save conf and warm start commands to set active the changes made on the lowercase parameters.

875
Draft CTIAS - CTI Advanced Services Draft

48.1.2. CTIAS resource parameters

Use the command below to display the parameters of the resource; the d p ctias ? command shows the meaning of
parameters.

[13:07:41] ABILIS_CPX:d p ctias

RES:CtiAs ---------------------------------------------------------------------
Run DESCR:CTI_Advanced_Services_entry_point
sesnum:0 TC-SESNUM:1

Meaning of the parameters:

sesnum Number of sessions that the CTIAS can support at once [0..255] <ReadOnly>.

TC-SESNUM Number of on-the-fly simultaneous transcoding session allowed for ALL plugins [0..255].

The following command allows the administrator to change the configuration of the resource:

s p ctias parameter:value...

Caution
Execute the initialization command init res:ctias to activate the changes made on the upper case parameters;
use save conf and warm start commands to set active the changes made on the lowercase parameters.

48.2. CTIVM - CTI Voice Mail

Voice mail is a centralized system of stored telephone messages which are sent via email by Abilis. The voice mail can be
managed both via the web interface and CP.

Abilis provides a system message set for voice mail, but every user can customize its own messages.

The CTIVM resource requires the SOFT-PBX licence.

48.2.1. Activating the CTIVM resource

Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:ctivm

COMMAND EXECUTED

The CTIVM resource may already exist in the system, but may not yet be active. Set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctivm

COMMAND EXECUTED

Caution
You must restart the Abilis to make the resource running (use the command warm start to reboot the
Abilis) after adding or setting the CTIVM active.

Tip
If the CTIVM resource is activated and the CTIAS resource is not, Abilis automatically adds the CTIAS
resource:

[12:11:11] ABILIS_CPX:a res:ctivm

COMMAND EXECUTED (ADDED ALSO RES:CtiAs)

[12:15:48] ABILIS_CPX:s p ctivm act:yes

COMMAND EXECUTED

876
Draft CTIAS - CTI Advanced Services Draft

[12:15:56] ABILIS_CPX:d p ctivm

RES:CtiVm - Not Saved (SAVE CONF), Not Refreshed (INIT) -----------------------

------------------------------------------------------------------------
Run DESCR:CTI_Voice_Mail_service
LOG:NO ACT:YES sesnum:5 TC-SESNUM:1 BUSY-NOCHAN:YES
CONN-DELAY:0 MSGLEN:90
RCPT:
RCPT-LIST:#
OGM-MSG:default END-MSG:default
wdir:C:\APP\VM\

[12:16:00] ABILIS_CPX:save conf

VALIDATION IN PROGRESS ...

VALIDATION SUCCESSFULLY EXECUTED

SAVE EXECUTED

[12:16:13] ABILIS_CPX:init res:ctivm

COMMAND EXECUTED

Caution
Execute the initialization command init res:ctivm to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

48.2.2. CTIVM resource parameters

Use the command below to display the parameters of the resource; the d p ctivm ? command shows the meaning of
parameters.

[14:08:12] ABILIS_CPX:d p ctivm

RES:CtiVm ---------------------------------------------------------------------
Run DESCR:CTI_Voice_Mail_service
LOG:NO ACT:YES sesnum:5 TC-SESNUM:1 BUSY-NOCHAN:YES
CONN-DELAY:0 MSGLEN:90
RCPT:
RCPT-LIST:#
OGM-MSG:default END-MSG:default
wdir:C:\APP\VM\

Meaning of parameters:

DESCR Resource description. From 0 up to 79 Alphanumeric extended characters. Spaces are not allowed. Case is
preserved.

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log; A: Alarm
view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes, see ref. manual) ACT: Operation
activation [NO, YES].

ACT Runtime CTIVM activation/deactivation.

sesnum Number of sessions that the VM plugin can support at once [1..255]. Default is 5.

TC-SESNUM Number of on-the-fly simultaneous transcoding sessions allowed for VM plugin [0..255]. Default is 1.

BUSY-NOCHAN Return BUSY cause instead of NOCHAN [NO, YES]. Default is YES.

CONN-DELAY Connection delay [0..60 sec.]. Default is 0.

MSGLEN Maximal length of stored message [10..180 sec.]. Default is 90.

877
Draft CTIAS - CTI Advanced Services Draft

RCPT Defult Voice Mail recipient(s). From 0 up to 128 ASCII printable characters (used when a call is not for a
user). Spaces are not allowed. Case is preserved. Default is empty.

RCPT-LIST IN2T list used to select Voice Mail recipient(s) on the base of called numbers [#, ListName]. Default is #.

OGM-MSG Name of the file holding the Outgoing Message. From 1 up to 20 characters. Names holding spaces must
be written between quotation marks (E.g.: "Dft out message"). Default is default.

END-MSG Name of the file holding the End Message. From 1 up to 20 characters. Names holding spaces must be
written between quotation marks (E.g.: "Sys end message"). Default is default.

wdir Directory where message files are located. It cannot be empty. Physical full path in DOS notation, i.e.
starting with a drive letter in the range ['A'..'Z'] and ending with the '\' character. Max. 128 characters.
Case is preserved. Spaces are allowed. Strings holding spaces must be written between quotation marks
(E.g.: "C:\My dir\"). Default is C:\APP\VM\.

The following command allows the administrator to change the configuration of the resource:

s p ctivm parameter:value...

Caution
Execute the initialization command init res:ctivm to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

48.2.3. CTIVM diagnostic and statistics

48.2.3.1. CTIVM diagnostic
The following command is used to display the diagnostics of the CTIVM resource:

d d ctivm it shows the state of the resource sorted by session (sesnum parameter).

MAILER- CTIVM sender state (WAITING:sender is waiting for new mail to be sent.
STATE SEARCHING: sender is searching on disk for new mail to be sent. CHECKING": sender
is checking metadata file.SENDING: sender is sending the mail. DELETING: sender is
deleting metadata file and WAV file.)

TC-STATE CTIVM transcoder state.(WAITING: transcoder is waiting for new CPM to be

transcoded. SEARCHING: sender is searching on disk for new CPM to be transcoded.
CHECKING: sender is checking metadata file. TRANSCODING: transcoder is
transcoding CPM to WAV. DELETING: transcoder is deleting metadata file and CPM
file.)

SES CTIVM session number.

VM-State CTIVM session state. (READY: session is READY for incoming call. OGM: session
is playing OGM message. OGM-BEEP: session is playing BEEP pattern after having
played OGM message. RECORDING: session is recording to WAV or to CPM. END-
BEEP: session is playing BEEP pattern prior to play END message. END: session is
playing END message.)

User CTIVM session current user name.

Q931-state CTIVM session Q931 state. (DISCONNECTED: session is disconnected. 04-REM-

ALERT: session received a call from CTIR and is alerting. 10-CONNECTED: session is
connected)

CG CTIVM session current calling number.

CD CTIVM session current called number.

[10:52:40] ABILIS_CPX:d d ctivm

RES:CtiVm ---------------------------------------------------------------------
CTI_Voice_Mail_service
STATE:ACTIVE MAILER-STATE:WAITING TC-STATE:WAITING

878
Draft CTIAS - CTI Advanced Services Draft

------------------------------------------------------------------------
SES: VM-State User
Q931-State CG CD
------------------------------------------------------------------------
0 READY
00-DISCONNECTED
------------------------------------------------------------------------
1 READY
00-DISCONNECTED
------------------------------------------------------------------------
2 READY
00-DISCONNECTED
------------------------------------------------------------------------
3 READY
00-DISCONNECTED
------------------------------------------------------------------------
4 READY
00-DISCONNECTED
------------------------------------------------------------------------

48.2.3.2. CTIVM statistics

The following command is used to display the statistics of the CTIVM resource:

d s ctivm it shows the statistics of the CTIVM resource such as the total number of successfully sent mails (SENT), the
total number of successfully transcoded CPM files (TRANSCODED).

[11:59:31] ABILIS_CPX:d s ctivm

RES:CtiVm ---------------------------------------------------------------------
CTI_Voice_Mail_service
--- Cleared 0 days 00:24:18 ago, on 05/05/2011 at 11:36:38 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SENT | | 0|TRANSCODED | | 0|
------------------------------------------------------------------------

48.2.4. CTIVM configuration through CP

VM can be configured using the users' CTI preferences or the CTI advanced preferences.

Tip
Interesting chapter: Section 43.4.7, “Voice Mail administration”.

48.2.4.1. VM parameters - CTI preferences

Each interface has its own VM parameters.

[09:31:49] ABILIS_CPX:d pref user:test2

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test2
ID: 5 <Read Only>
LAST-CHANGE: 05/05/2011 16:55:59 CET <Read Only>
PWD: ***
--------------------
CTIP-CLIP: SYS
CTIP-ACTION: ADVANCED
CTIP-CF-RULE: ALWAYS
CTIP-CF-TOUT: 15
CTIP-CF-DLY: 10
CTIP-CF-CDO: ux#
CTIP-CF-CGO: *

879
Draft CTIAS - CTI Advanced Services Draft

CTIP-VM: NO
CTIP-VM-RULE: NOANS,OTHERS
CTIP-VM-TOUT: 15
--------------------
CLUS-CLIP: SYS
CLUS-ACTION: ADVANCED
CLUS-CF-RULE: ALWAYS
CLUS-CF-TOUT: 15
CLUS-CF-DLY: 10
CLUS-CF-CDO: ux#
CLUS-CF-CGO: *
CLUS-VM: NO
CLUS-VM-RULE: NOANS,OTHERS
CLUS-VM-TOUT: 15
--------------------
IAX-CLIP: SYS
IAX-ACTION: ADVANCED
IAX-CF-RULE: ALWAYS
IAX-CF-TOUT: 15
IAX-CF-DLY: 10
IAX-CF-CDO: ux#
IAX-CF-CGO: *
IAX-VM: NO
IAX-VM-RULE: NOANS,OTHERS
IAX-VM-TOUT: 15
--------------------
SIP-CLIP: SYS
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 5
SIP-CF-DLY: 10
SIP-CF-CDO: ux12
SIP-CF-CGO: *
SIP-VM: YES
SIP-VM-RULE: NOANS,OTHERS
SIP-VM-TOUT: 5
--------------------
VM-RCPT-LIST: #
VM-RCPT: [email protected]
VM-OGM-MSG: Message1
VM-END-MSG: SYS
--------------------
MAIL-FAIL: NO
MAIL-FAIL-RCPT-LIST: #
MAIL-FAIL-RCPT:
MAIL-FWD: NO
MAIL-FWD-RCPT-LIST: #
MAIL-FWD-RCPT:
SEIZED-CALLS: NO
--------------------
CTI-CALLS-LOG: YES
CTI-CALLS-LOG-IN: 30
CTI-CALLS-LOG-OUT: 30
--------------------
CALLTRY-TOUT: SYS
CALLTRY-NRTY: SYS
--------------------
TON-TO-PREFIX: SYS
-------------------------------------------------------------------------------

Meaning of parameters:

CTIP-VM Voice mail activation/deactivation [NO, YES]. Default is NO.

880
Draft CTIAS - CTI Advanced Services Draft

CTIP-VM-RULE Voice mail rule [ALWAYS, BUSY, NOANS, OTHERS]. Values [BUSY, NOANS, OTHERS] can be
joined using ',' character. Default is NOANS,OTHERS.

CTIP-VM-TOUT Voice mail: Time-out for the 'NOANS' rule [5..180 sec.]. Default is 15.

CLUS-VM Voice mail activation/deactivation [NO, YES]. Default is NO.

CLUS-VM-RULE Voice mail rule [ALWAYS, BUSY, NOANS, OTHERS]. Values [BUSY, NOANS, OTHERS] can be
joined using ',' character. Default is NOANS,OTHERS.

CLUS-VM-TOUT Voice mail: Time-out for the 'NOANS' rule [5..180 sec.]. Default is 15.

IAX-VM Voice mail activation/deactivation [NO, YES]. Default is NO.

IAX-VM-RULE Voice mail rule [ALWAYS, BUSY, NOANS, OTHERS]. Values [BUSY, NOANS, OTHERS] can be
joined using ',' character. Default is NOANS,OTHERS.

IAX-VM-TOUT Voice mail: Time-out for the 'NOANS' rule [5..180 sec.]. Default is 15.

SIP-VM Voice mail activation/deactivation [NO, YES]. Default is NO.

SIP-VM-RULE Voice mail rule [ALWAYS, BUSY, NOANS, OTHERS]. Values [BUSY, NOANS, OTHERS] can be
joined using ',' character. Default is NOANS,OTHERS.

SIP-VM-TOUT Voice mail: Time-out for the 'NOANS' rule [5..180 sec.]. Default is 15.

VM-RCPT-LIST IN2T list used to select Voice Mail recipient(s) on the base of called numbers [#, ListName].

VM-RCPT Defult Voice Mail recipient(s). From 0 up to 128 ASCII printable characters. Spaces are not allowed.
Case is preserved.

VM-OGM-MSG Name of the file holding the Outgoing Message. "SYS" or from 1 up to 20 characters. Names holding
spaces must be written between quotation marks (E.g.: "My message"). Default is SYS.

VM-END-MSG Name of the file holding the End Message. "SYS" or from 1 up to 20 characters. Names holding spaces
must be written between quotation marks (E.g.: "My message"). Default is SYS.

48.2.4.2. VM parameters - CTI advanced preferences

VM can be configured through CTI advanced preferences. Type the command below to view the CTI advanced preferences
rules.

[09:55:44] ABILIS_CPX:d cf user:test2

USER:test2 (Last change: 06/05/2011 09:55:57 CET)

------------------------------------------------------------------------------
PR |ENABLED|IN-USE|IF |TI |ACTION
ADMIN|CGI |CDI |RULE
|CGO |CDO |TOUT |DLY
------------------------------------------------------------------------------
1 YES YES ANY ALL,00:00-23:59 VM
NO * * NOANS,OTHERS
15
------------------------------------------------------------------------------

VM can be activated setting the ACTION parameter to VM.

In the previous example, VM is activated (ACTION:VM) for every interface (IF:ANY), at any time (TI:ALL,00:00-23:59), if
user test2 doesn't answer, or for any other cause, (RULE:NOANS,OTHERS) after 15 seconds (TOUT:15).

48.2.4.3. Example - how to configure CTIVM through CP

Assume to have two sip users: test2 (with sip number 11) and test3 (with sip number 12).

[16:26:28] ABILIS_CPX:d user

881
Draft CTIAS - CTI Advanced Services Draft

USER: PWD: ACT: CTIP: CLUS: PPP: FTP: HTTP: MAIL: IAX: SIP:
--------------------------------+--------------+-------------------------------
admin *** YES # # YES YES YES NO NO NO
guest NO # # NO NO NO NO NO NO
test2 *** YES # # NO NO NO NO NO YES
test3 *** YES # # NO NO NO NO NO YES

The voice mail settings are stored in users' preferences. Type the following command to show the settings for test2 user:

[16:31:35] ABILIS_CPX:d pref user:test2

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test2
ID: 5 <Read Only>
LAST-CHANGE: 21/04/2011 16:31:26 CET <Read Only>
PWD: ***
...
--------------------
SIP-CLIP: SYS
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 5
SIP-CF-DLY: 10
SIP-CF-CDO: ux12
SIP-CF-CGO: *
SIP-VM: NO
SIP-VM-RULE: NOANS,OTHERS
SIP-VM-TOUT: 15
--------------------
VM-RCPT-LIST: #
VM-RCPT:
VM-OGM-MSG: SYS
VM-END-MSG: SYS
--------------------
...

These settings show that the voice mail service is not activated because SIP-VM parameter is set to NO. Change the
parameters values in the following way:

[16:38:13] ABILIS_CPX:s pref user:test2 sip-vm:yes vm-rcpt:[email protected]

COMMAND EXECUTED

[16:39:14] ABILIS_CPX:d pref user:test2

- Not Saved (SAVE CONF) -------------------------------------------------------

Parameter: | Value:
--------------------+----------------------------------------------------------
USER: test2
ID: 5 <Read Only>
LAST-CHANGE: 21/04/2011 16:39:14 CET <Read Only>
PWD: ***
...
--------------------
SIP-CLIP: SYSV
SIP-ACTION: ADVANCED
SIP-CF-RULE: ALWAYS
SIP-CF-TOUT: 5
SIP-CF-DLY: 10
SIP-CF-CDO: ux12

882
Draft CTIAS - CTI Advanced Services Draft

SIP-CF-CGO: *
SIP-VM: YES
SIP-VM-RULE: NOANS,OTHERS
SIP-VM-TOUT: 15
--------------------
VM-RCPT-LIST: #
VM-RCPT: [email protected]
VM-OGM-MSG: SYS
VM-END-MSG: SYS
--------------------

...

The call is passed to the voice mail after 15 seconds (SIP-VM-TOUT) If test2 doesn't answer.

[16:47:09] ABILIS_CPX:start ldme

Current Local Time: Thursday 21/04/2011 16:47:22 (UTC+2.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
210411 164726 CtiSip 8 E-CallRx CH:7 BC:Speech CD:ue11 CG:uxq10
USER:test
210411 164726 CtiSip 8 E-Route Match PR:9 TYPE:StoS
210411 164726 CtiSip 8 E-CallTx BC:Speech TY:StoS CD:ue11
CG:uxq10
210411 164726 CtiSip 8 E-NumComplete CDI:ue11 CDO:ue11
210411 164726 CtiSip 8 E-AlertRx CH:8 USER:test2
210411 164726 CtiSip 8 E-AlertTx CH:7
210411 164741 CtiSip 0 E-VoiceMail RULE:NOANS USER:test2
210411 164741 CtiSip 9 E-CallRx AS:CtiVm CH:9 BC:Speech CD:ue11
CG:uxq10 RG:uxay11 USER:test2
210411 164741 CtiSip 9 E-Route Match PR:INT TYPE:*toA
210411 164741 CtiVm 9 E-CallTx AS:CtiVm BC:Speech TY:StoA
CD:ue11 CG:uxq10 RG:uxay11
210411 164741 CtiSip 9 E-NumComplete CDI:ue11 CDO:ue11
210411 164741 CtiSip 10 E-CallTransfer SES/ID-IN:9 SES/ID-OUT:8
210411 164741 CtiVm 10 E-ConnRx CH:3 USER:test2
210411 164741 CtiSip 10 E-ConnTx CH:7
210411 164832 CtiSip 10 E-DiscRx CH:7 CAUSE:80 9F (U, Normal,
unspecified) USER:test
210411 164832 CtiSip 10 E-DiscConfTx CH:7
210411 164832 CtiVm 10 E-DiscTx CH:3 CAUSE:80 9F (U, Normal,
unspecified) USER:test2

An e-mail (with the following text) is sent from Abilis to the recipient specified in the VM-RCPT parameter. The e-mail has
a wav file as attachment.

883
Draft CTIAS - CTI Advanced Services Draft

Figure 48.1. CTIVM email

Tip
Interesting chapter: Section 43.4.7, “Voice Mail administration”.

Tip
Configure the smtp resource to let Abilis send e-mails.

Tip
The e-mails sender can be configured by MAIL-FROM parameter of CTISYS resource.

48.2.5. Appendix
48.2.5.1. Meaning of log
A new kind of routing is available (*toA) to manage calls toward Abilis advanced services. Two hidden rules are always
inside the CTIR:

884
Draft CTIAS - CTI Advanced Services Draft

• a rule to encode a call on-the-fly, so that the file is directly saved in WAV format (one DSP per call is used);

• a rule to save the call in its original format (used if there's no free DSP); the file is encoded in the WAV format when a
DSP is free.

These rules are called INT rules (INTernal).

[16:47:09] ABILIS_CPX:start ldme

Current Local Time: Thursday 21/04/2011 16:47:22 (UTC+2.00)

Start Debug Log content real-time logging (Type CTRL+C + ENTER to stop):

Date Time Resource Ses Event Parameters

------ ------ ---------- ----- -------------- ---------------------------------
210411 164726 CtiSip 8 E-CallRx CH:7 BC:Speech CD:ue11 CG:uxq10
USER:test
210411 164726 CtiSip 8 E-Route Match PR:9 TYPE:StoS
210411 164726 CtiSip 8 E-CallTx BC:Speech TY:StoS CD:ue11
CG:uxq10
210411 164726 CtiSip 8 E-NumComplete CDI:ue11 CDO:ue11
210411 164726 CtiSip 8 E-AlertRx CH:8 USER:test2
210411 164726 CtiSip 8 E-AlertTx CH:7
210411 164741 CtiSip 0 E-VoiceMail RULE:NOANS USER:test2
210411 164741 CtiSip 9 E-CallRx AS:CtiVm CH:9 BC:Speech CD:ue11
CG:uxq10 RG:uxay11 USER:test2
210411 164741 CtiSip 9 E-Route Match PR:INT TYPE:*toA
210411 164741 CtiVm 9 E-CallTx AS:CtiVm BC:Speech TY:StoA
CD:ue11 CG:uxq10 RG:uxay11
210411 164741 CtiSip 9 E-NumComplete CDI:ue11 CDO:ue11
210411 164741 CtiSip 10 E-CallTransfer SES/ID-IN:9 SES/ID-OUT:8
210411 164741 CtiVm 10 E-ConnRx CH:3 USER:test2
210411 164741 CtiSip 10 E-ConnTx CH:7
210411 164832 CtiSip 10 E-DiscRx CH:7 CAUSE:80 9F (U, Normal,
unspecified) USER:test
210411 164832 CtiSip 10 E-DiscConfTx CH:7
210411 164832 CtiVm 10 E-DiscTx CH:3 CAUSE:80 9F (U, Normal,
unspecified) USER:test2

48.2.5.2. Working dir structure

The wdir parameter of CTIVM resource specify which is the working directory on the CF. The default value is C:\APP\VM\.

885
Draft CTIAS - CTI Advanced Services Draft

Figure 48.2. Structure of CTIVM working folder

A user can choose to use system default messages (stored in system folder) or customized messages (stored in USER folder).

Tip
Interesting chapter: Section 43.2.3.2, “CTI preferences”.

886
Draft Draft

Chapter 49. CTISMS - CTI SMS

resource
Luigi Demuro

Table of Contents
49.1. CTISMS - CTI SMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1.1. Activating the CTISMS resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
49.1.2. CTISMS resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2. CTISMS Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.1. CTISMS IN routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
49.2.2. CTISMS OUT routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
49.3. CTISMS diagnostic and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.1. CTISMS diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
49.3.2. CTISMS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891

49.1. CTISMS - CTI SMS resource

CTISMS resource allows to send SMS through an UMTS-BOX device.

If it's used toghether with SMTP resource, it allows to send/receive sms through emails.

Tip
Interesting chapters:

Section 53.19, “How to configure CTISMS to send sms via emails”;

Section 53.18, “How to configure CTISMS to send sms using the web interface”.

49.1.1. Activating the CTISMS resource

Add the resource to the Abilis system with the following command.

[09:08:14] ABILIS_CPX:a res:ctisms

RES:CTISMS ALREADY EXISTS

The CTISMS resource may already exist in the system, but may not yet be active: set it active with the command:

[09:10:00] ABILIS_CPX:s act res:ctisms

COMMAND EXECUTED

Caution
You must restart the Abilis to make the resource running (use the command warm start to reboot the
Abilis) after adding or setting the CTISMS active.

[11:01:39] ABILIS_CPX:s p ctisms act:yes

COMMAND EXECUTED

[13:07:41] ABILIS_CPX:d p ctisms

RES:CtiSms - Not Saved (SAVE CONF), Not Refreshed (INIT)-----------------------

DESCR:Short_Message_Service

887
Draft CTISMS - CTI SMS resource Draft

LOG:NO ACT:YES MAX-SMS-SPLIT:1 ALLOW-UNICODE:NO

DFT-IN:NO
DFT-SMTP:
wdir:C:\APP\SMS\

Caution
Execute the initialization command init res:ctisms to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

49.1.2. CTISMS resource parameters

Use the below command to display the parameters of the resource; the d p ctisms ? command shows the meaning of
parameters.

[14:08:12] ABILIS_CPX:d p ctisms

RES:CtiSms --------------------------------------------------------------------
Run DESCR:Short_Message_Service
LOG:NO ACT:YES MAX-SMS-SPLIT:1 ALLOW-UNICODE:NO
DFT-IN:NO
DFT-SMTP:
wdir:C:\APP\SMS\

Meaning of the most important parameters:

LOG State changes log and alarm generation [NO, D, S, A, L, T, ALL] [+E] (D: Debug Log; S: System Log; A: Alarm
view; L: Local audible alarm; T: SNMP traps; +E: Extended Log of state changes, see ref. manual) ACT: Operation
activation [NO, YES].

ACT Runtime CTISMS activation/deactivation.

MAX-SMS-SPLIT Maximal number of SMS for a single outgoing message [1..4].

ALLOW-UNICODE Allow/disallow UNICODE encoding [NO, YES].

UNICODE is disallow, only LATIN-1 is used

DFT-IN Default route for incoming SMS [NO: No default route, message deleted , SMTP: Message routed to
SMTP].

DFT-SMTP SMTP recipient()s for default route. From 0 up to 128 ASCII printable characters. Spaces are not
allowed. Case is preserved.

wdir Working directory. It cannot be empty. Physical full path in DOS notation, i.e. starting with a drive
letter in the range ['A'..'Z'] and ending with the '\' character. Max. 128 characters. Case is preserved.
Spaces are allowed. Strings holding spaces must be written between quotation marks (E.g.: "C:\My dir
\").

The following command allows the administrator to change the configuration of the resource:

s p ctisms parameter:value...

Caution
Execute the initialization command init res:ctisms to activate the changes made on the upper case
parameters; use save conf and warm start commands to set active the changes made on the lowercase
parameters.

49.2. CTISMS Routing

49.2.1. CTISMS IN routing
This table contains routings for incoming messages. Each routing is identified with a priority number (PR parameter). Use the
following message to display the rules:

888
Draft CTISMS - CTI SMS resource Draft

[14:14:05] ABILIS_CPX:d ctisms in

----+-------+------------------------+---------+----------+--------------------
PR: |ACT: |CG: |DEST: |LIFETIME: |HEADER:
|RULE: |TEXT:
----+-------+------------------------+---------+----------+--------------------
0 NO * SMTP 21600 REMOVE
MAIL
-------------------------------------------------------------------------------

Rules can be managed using the standard syntax:

a/s/c/m ctisms in pr:x parameter:<value>...

The command d ctisms in ? displays the meaning of parameters:

PR Priority of CTISMS routing for incoming messages [A, 0..63].

ACT Enable/DIsable the record.

CG Allowed calling numbers/prefixes. From 1 up to 20 characters, in the range ['0'..'9', '*'] or "#" optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] and/or PI [a, r, m, q] and/or SI [y, v, w, z]
attributes or the name of an IN/IN2T/INR/RU/MR list between primes. The '*' is allowed only alone or as the
last character. (E.g. # or ne# or 1234567 or 4567* or * or 'my_list').

DEST Destination application [SMTP].At this time only SMTP is available for incoming messages.

LIFETIME Maximal time a message can be kept in the incoming queue.

HEADER Treatment of the message part used for routing [REMOVE, KEEP]. The initial part of the message used for
routing can be removed or kept prior to pass the message to the application. Typically it will be necessary to
remove it.

RULE Message verification rule [MAIL: message is checked according to MAIL rule, PREFIX: message is checked
according to PREFIX rule].

TEXT First part of the message for matching PREFIX rule. From 0 up to 20 ASCII characters. Case is preserved.
Spaces are allowed. Strings holding spaces must be written between quotation marks (E.g.: "my text"). <Only
for RULE:PREFIX>.

Note
When a sms is received, an email is sent to the configured recipient. The mail subject contains the
information of the port on which the message has been received.

Tip
Interesting chapters:

Section 53.19, “How to configure CTISMS to send sms via emails”;

Section 53.18, “How to configure CTISMS to send sms using the web interface”.

49.2.2. CTISMS OUT routing

This table contains the routings for outgoing messages. Each routing is identified with a priority number (PR parameter). Use
the following message to display the rules:

[14:52:55] ABILIS_CPX:d ctisms out

----+-------+-------------------------+-----+---------+-------+-------+--------
PR: |ACT: |CD: |POO: |LIFETIME:|DELAY: |SPLIT: |UNICODE:
|SOURCE:|SENDER-ID:
----+-------+-------------------------+-----+---------+-------+-------+--------
0 NO * 201 1800 300 SYS SYS
SMTP *

889
Draft CTISMS - CTI SMS resource Draft

-------------------------------------------------------------------------------
1 NO * 201 1800 300 SYS SYS
FILE *
-------------------------------------------------------------------------------

Rules can be managed using the standard syntax:

a/s/c/m ctisms out pr:x parameter:<value>...

The command d ctisms in ? displays the meaning of parameters:

PR Priority of CTISMS routing for incoming messages [A, 0..63].

ACT Enable/DIsable the record.

CD Allowed called numbers/prefixes. From 1 up to 20 characters, in the range ['0'..'9', '*'] or "#" optionally
preceded by TON [u, i, n, o, s, h, c] and/or NP [x, e, d, t, l, p] attributes or the name of an IN/IN2T/INR/RU/
MR list between primes. The '*' is allowed only alone or as the last character. (E.g. # or ne# or 1234567 or
4567* or * or 'my_list').

POO Output CTI Port or group [NONE, 1..300, G1..G32].

LIFETIME Maximal time a message can be kept in the outgoing queue [10..1048576 sec].

DELAY Delay betyween subsequent attempts [60..3600 sec].

SPLIT Maximal number of SMS for a single outgoing message [SYS, 1..4].

UNICODE Allow/disallow UNICODE encoding [SYS???, NO, YES].

SOURCE Source application [SMTP: SMTP application, FILE: FILE to SMS application].

SENDER-ID Textual identifier of the sender. "*" or from 1 up to 64 ASCII charcters or the name of TXT list between
primes. Case is preserved. Spaces are allowed. Strings holding spaces must be written between quotation
marks (E.g.: "my sender id" or * or 'listname').

49.3. CTISMS diagnostic and statistics

49.3.1. CTISMS diagnostic
The following command is used to display the diagnostics of the SMTP resource:

d d ctisms Shows the state of the resource.

[10:52:40] ABILIS_CPX:d d ctisms

RES:CtiSms --------------------------------------------------------------------
Short_Message_Service
STATE:ACTIVE
------------------------------------------------------------------------
APP:SMTP APP-STATE:CLOSED
APP:FILE APP-STATE:OPENED

[10:31:49] ABILIS_CPX:d de smtp

RES:Smtp ----------------------------------------------------------------------
Simple_Mail_Transfer_Protocol
STATE:ACTIVE CUR-SES:10 ACTIVE-IN:0 ACTIVE-OUT:0
MIX-IN:0 MIX-OUT:0 QUEUE-OUT:0 QUEUE-DEFER:0
- Smtp Sessions --------------------------------------------------------
CH TYPE TCP-State LocAdd-LocPort RemAdd-RemPort SMTP-State
------------------------------------------------------------------------
0 OUT READY READY
1 OUT READY READY
2 IN LISTEN 000.000.000.000-25 READY
3 IN LISTEN 000.000.000.000-25 READY

890
Draft CTISMS - CTI SMS resource Draft

4 IN LISTEN 000.000.000.000-25 READY

5 IN LISTEN 000.000.000.000-25 READY

49.3.2. CTISMS statistics

The following commands are used to display the statistics of the SMTP resource:

d s ctisms Shows the statistics of the SMTP resource, such as the number of incoming messages from application
(SUCC-MSG-APPL in), the number of outgoing messages to application (SUCC-MSG-APPL out), the
number of incoming incorrect messages from application (FAIL-MSG-APPL in), the number of failure
outgoing message to application (FAIL-MSG-APPL out), etc...

[10:52:49] ABILIS_CPX:d s ctisms

RES:CtiSms --------------------------------------------------------------------
Short_Message_Service
--- Cleared 0 days 01:43:44 ago, on 04/02/2011 at 09:09:27 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-MSG | 0| 0|FAIL-MSG | 0| 0|
------------------------------------------------------------------------
------------------------------------------------------------------------
APP:SMTP
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-MSG | 0| 0|FAIL-MSG | 0| 0|
------------------------------------------------------------------------
APP:FILE
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SUCC-MSG | 0| 0|FAIL-MSG | 0| 0|
------------------------------------------------------------------------

891
Draft Draft

Chapter 50. ACNT - Accounting

resource
Marco Bellesia
Luigi Demuro

Table of Contents
50.1. ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.1. Activating the ACNT resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
50.1.2. ACNT resource parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2. ACNT diagnostics and statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.1. ACNT diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
50.2.2. ACNT statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
50.3. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

50.1. ACNT resource

The Accounting Agent resource of the Abilis CPX is responsible of transmitting, through a TCP/IP network, accounting
information to a remote host. A software application, named Collector provides data collecting, reports generating and
presenting to the end user.

For further information refer to Section 50.3, “Appendix”.

50.1.1. Activating the ACNT resource

Add the resource to the Abilis system with the command:

[11:01:39] ABILIS_CPX:a res:acnt

RES:ACNT ALREADY EXISTS

The ACNT resource may already exist in the system, but may not yet be active: set it active with the command:

[11:01:48] ABILIS_CPX:s act res:acnt

COMMAND EXECUTED

Caution
After adding or setting the ACNT active, you must restart the Abilis to make the resource running (use the
command warm start to reboot the Abilis).

[11:01:39] ABILIS_CPX:s p acnt act:yes

COMMAND EXECUTED

[11:01:39] ABILIS_CPX:d p acnt

RES:Acnt - Not Saved (SAVE CONF), Not Refreshed (INIT) ------------------------

------------------------------------------------------------------------
Run DESCR:Accounting_Service
LOG:NO ACT:YES locport:2060 tcpses:3 FILTER:ALL

892
Draft ACNT - Accounting resource Draft

- Collector ------------------------------------------------------------
IPADD:# CR:AUTO CRKEY:DFT
- Additional collector(s) ----------------------------------------------
ADD-IPLIST:* ADD-CR:AUTO ADD-CRKEY:DFT

Caution
Execute the initialization command init res:acnt to activate the changes made on the upper case parameters;
changes made on the lowercase parameters require a save conf and an Abilis restart (i.e. with warm start
command).

Set the parameter ACT to YES to allow the connection from the Collector program.

The configuration above allows the connection from at maximum 3 Collector from any IP address; to enable the connection
form specific IP addresses, it is needed to set the IPADD and ADD-IPLIST parameters.

50.1.2. ACNT resource parameters

Use the following command to display the parameters of the resource. The d p acnt ? command shows the meaning of
parameters.

[11:01:39] ABILIS_CPX:d p acnt

RES:Acnt ----------------------------------------------------------------------
Run DESCR:Accounting_Service
LOG:NO ACT:YES locport:2060 tcpses:3 FILTER:ALL
- Collector ------------------------------------------------------------
IPADD:# CR:AUTO CRKEY:DFT
- Additional collector(s) ----------------------------------------------
ADD-IPLIST:* ADD-CR:AUTO ADD-CRKEY:DFT

Below are descriptions of the most important parameters:

ACT Runtime activation/deactivation.

locport Local TCP port for incoming connections; by default is 2060.

tcpses Number of TCP sessions.

FILTER It defines a filter to be applied on the Accounting information to be collected [ALL: any accounting event
is collected; CONNECTED: only information related to successful connections are collected; FAILED: only
information related to failed connections are collected].

IPADD Main collector IP address. If it is set to #, the resource accept connections from any IP address.

CR Additional Encryption/Decryption activation.

CRKEY Additional Encryption/Decryption key index.

The following command allows the administrator to change the configuration of the resource:

s p acnt parameter:value...

Caution
To activate the changes made on the upper case parameters, execute the initialization command init
res:acnt; while to set act the changes made on the lowercase parameters a save conf and an Abilis restart are
required (i.e. with warm start command).

50.2. ACNT diagnostics and statistics

50.2.1. ACNT diagnostics
The following commands are used to display the diagnostics of the ACNT resource:

893
Draft ACNT - Accounting resource Draft

d d acnt / d de acnt Shows diagnostic information, such as the current state of the connection, the current mode
for exchanging accounting data, whether data exchanged on the current connection are
encrypted, the local IP Address/port and the remote IP address/port of the PC in which is
executed the Collector application.

[11:09:16] ABILIS_CPX:d d acnt

RES:Acnt ----------------------------------------------------------------------
Accounting_Service
STATE:READY
- Accounting channels --------------------------------------------------
Ch State Mode Crypt LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CONN-FROM SIMPLE NO 192.168.000.232-2060 192.168.000.024-2384
2 CONN-FROM SIMPLE NO 192.168.000.231-2060 192.168.000.051-2702
3 CONN-FROM SIMPLE NO 192.168.000.232-2060 192.168.000.250-32966

50.2.2. ACNT statistics

The following commands are used to display the statistics of the ACNT resource:

d s acnt Shows statistic information, such as the number of failed/succesfull calls on the connection, the number of
sent/received characters and the number of sent/received messages.

d se acnt Shows statistic information in an extended format: the same information listed for d s acnt command are
shown for each session.

[11:09:16] ABILIS_CPX:d s acnt

RES:Acnt ----------------------------------------------------------------------
Accounting_Service
--- Cleared 2 days 13:43:44 ago, on 10/12/2007 at 20:30:08 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 4| 0|
CHAR | 40978| 519868|MSG | | 2017|
------------------------------------------------------------------------

[11:09:16] ABILIS_CPX:d se acnt

RES:Acnt ----------------------------------------------------------------------
Accounting_Service
--- Cleared 2 days 13:43:59 ago, on 10/12/2007 at 20:30:08 -------------
- Accounting channels --------------------------------------------------
Ch State Mode Crypt LocAdd-LocPort RemAdd-RemPort
------------------------------------------------------------------------
1 CONN-FROM SIMPLE NO 192.168.000.232-2060 192.168.000.024-2384
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 2| 0|
CHAR | 232| 4992|MSG | | 21|
------------------------------------------------------------------------
2 CONN-FROM SIMPLE NO 192.168.000.231-2060 192.168.000.051-2702
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 1| 0|
CHAR | 14829| 257436|MSG | | 998|
------------------------------------------------------------------------
3 CONN-FROM SIMPLE NO 192.168.000.232-2060 192.168.000.250-32966
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 1| 0|
CHAR | 25917| 257440|MSG | | 998|
------------------------------------------------------------------------

894
Draft ACNT - Accounting resource Draft

50.3. Appendix
Figure 50.1. Accounting scheme

Relevant accounting information usually include:

• call duration

• date and time of call end

• call direction (input or output)

• type of call (compressed voice, data, cluster, transparent, etc..)

• called number

• calling number

• reason of failure

• ...

The Accounting Agent resource (ACNT) offers two types of services:

• SIMPLE accounting: events are sent from Abilis CPX to the Collector at the same time they occur. The Collector prints
the event on a window and saves it into the selected file. If the TCP session is not opened the event is lost. SIMPLE
accounting can supply events to more Collectors simultaneously.

• TRANSACTION accounting: events are stored in an internal database which can be either in RAM or on the HD. When
the transaction has to take place, events are transferred to the Collector. It writes them on disk and sends acknowledge for
deletion in Abilis CPX. The transaction procedure ensure that no events are lost (except when the Abilis CPX database
becomes full), and no events are duplicated.

TRANSACTION account can deal with a unique Collector only, the counterpart identity must be checked based on IP
address (first level check), and with an addition message exchange. This is mandatory not only for security, but mainly for
database consistency.

895
Draft Draft

Part V. HowTo
Draft Draft

Table of Contents
51. HowTo - Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
51.1. How to enter into the Abilis control-program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
51.1.1. How to enter into the Abilis control-program through the TELNET protocol . . . . . . . . . . . . . . . . . . . . . . . 901
51.1.2. How to enter into the Abilis control-program through the serial-asynchronous port of the Abilis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
51.1.3. How to enter into the Abilis control-program through the SSH protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
51.1.4. How to enter into the Abilis control-program through an ISDN connection . . . . . . . . . . . . . . . . . . . . . . . . 902
51.2. How to prepare an Abilis Compact-Flash using a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
51.3. How to use the Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
51.3.1. How to create a new configuration file DRIVERS.CFG with the Console configurator . . . . . . . . . . . . . 906
51.3.2. How to modify an existing configuration file DRIVERS.CFG with the Console Configurator. . . . . . 908
51.4. How to remotely upgrade the Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
51.5. How to remotely transfer files using a terminal emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.1. How to download configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.2. How to upload configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
51.6. How to restart the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.7. How to upgrade configuration files to newer firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.8. How to copy files using a removable drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
51.8.1. How to copy configuration and log files on an USB disk through the command-line interface. . . . . 914
51.8.2. How to copy configuration and log files on an USB disk using the MFIDE front panel . . . . . . . . . . . . 915
51.8.3. How to copy configuration files from an USB disk to the Abilis HD/CF through the command-
line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
51.8.4. How to copy configuration files from an USB disk to the Abilis HD/CF using the MFIDE front
panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
51.9. How to know which kind of hardware is mounted on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.9.1. How to recognize PCI cards model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.10. How to automatically reassign the USBPORTID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
51.11. How to manage licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.12. How to view boot log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13. How to change the login passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.1. How to change the TELNET password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.2. How to change the SSH password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.3. How to change the users' passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.14. How to activate the Abilis SSH server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.15. How to open a TELNET connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.16. How to open a SSH connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
51.17. How to create a list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
51.17.1. How to create a list of ISDN numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.2. How to create a list of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.3. How to create a list of IP addresses ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.18. How to configure Abilis as a SYSLOG client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.19. How to trace the internal events for debugging purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
51.19.1. How to convert Abilis CPX traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
52. HowTo - Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
52.1. How to configure LAN settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.2. How to activate a new ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.3. How to assign several IP addresses to the same LAN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4. How to configure ADSL connections using USB modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4.1. How to configure a RFC 1483 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
52.4.2. How to configure a PPPoA (RFC 2364) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.4.3. How to configure a PPPoE connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.5. How to configure HDSL/SHDSL connections using V.35/G.703 synchronous ports . . . . . . . . . . . . . . . . . . . . . . . . . 934
52.6. How to configure the default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.1. How to configure the default IP route in case Abilis is connected to an ADSL USB or V.35/
G.703 modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.2. How to configure the default IP route in case Abilis is connected to an ethernet ADSL router. . . . . . 936
52.6.3. How to configure an alternative default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
52.7. How to configure the Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
52.8. How to share a single Internet connection among multiple computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938

897
Draft HowTo Draft

52.9. How to access IP hosts and services which are behind a NAT manager (port forwarding) . . . . . . . . . . . . . . . . . . . 938
52.10. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.1. How to setup DDNS service using dyndns.org . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.2. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
52.11. How to configure a Remote Access Server (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.1. How to configure a RAS using IPSEC VPN server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.2. How to configure a RAS using IPSEC VPN server with iPHONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
52.11.3. How to configure a RAS using PPPoE connections with an Ethernet/WiFi network . . . . . . . . . . . . . . 952
52.11.4. How to configure a RAS using ISDN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
52.12. How to configure an ISDN PPP Dial-UP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13. How to configure a VPN tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13.1. How to configure a VPN tunnel where both Abilis have a static public IP address . . . . . . . . . . . . . . . . 955
52.13.2. How to configure a VPN tunnel where one Abilis has a dynamic public IP address or is placed
behind a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
52.13.3. How to configure a VPN tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
52.13.4. How to configure a VPN tunnel with the “double path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
52.14. How to configure a voice tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
52.14.1. How to configure a voice tunnel where both Abilis have a static public IP address . . . . . . . . . . . . . . . . 962
52.14.2. How to configure a voice tunnel where one Abilis has a dynamic public IP address or is
placed behind a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
52.14.3. How to configure a voice tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
52.14.4. How to configure a voice tunnel with the “double-path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
52.15. How to activate the DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
52.15.1. How to activate the DHCP in relay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
52.15.2. How to activate the DHCP in server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
52.15.3. How to activate the DHCP in client mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
52.16. How to activate the FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17. How to activate the HTTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17.1. How to activate the HTTP over SSL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
52.18. How to activate the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
52.19. How to use state detection of IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20. How to activate the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.1. How to activate the SNTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.2. How to activate the SNTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
52.21. How to activate the SNMP agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
52.22. How to publish the users on the Abilis LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
53. HowTo - CTI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
53.1. How to configure ISDN ports to connect PBX or ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
53.2. How to configure FXS (POTS) ports for analog telephones or fax machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
53.3. How to program a group of telephone lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
53.4. How to configure fax modem relay parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
53.5. How to create a VoIP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
53.6. How to register an IAX telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
53.7. How to register a SIP telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
53.7.1. How to register a SIP telephone onto Abilis when the telephone is behind a NAT . . . . . . . . . . . . . . . . . 985
53.8. How to register Abilis as a client of Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
53.9. How to register Abilis as a client of a SIP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.10. How to configure the speedlimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.11. How to configure opc to collect call information from a remote abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.12. How to activate the Accounting service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.13. How to enable pickup service for a POTS/ISDN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.14. How to enable pickup service for a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.15. How to configure CTIDISA to implement a responder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.1. Implementing a responder using MODE:INTRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.2. Implementing a responder using MODE:DISA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.3. Getting a call on phones while the responder is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
53.16. How to configure Last Calling Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
53.17. How to configure DATA CALL BACK using an UMTS Key, calling an ISDN number . . . . . . . . . . . . . . . . . . . . 994
53.18. How to configure CTISMS to send sms using the web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19. How to configure CTISMS to send sms via emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19.1. Instructions to send emails through sms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
53.19.2. Instructions to send sms through emails using a client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997

898
Draft HowTo Draft

54. FAQ - Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002

54.1. ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.1. How can I verify if an ISDN line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.2. Back up over ISDN doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.3. How can I manage the backup over ISDN autoconnection? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.4. Is it possible to connect ISDN phones to BRI/BRI-HFC cards? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.5. Why (and how to) enable/disable analog ports on a NT1 Plus device? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.2. POTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.2.1. The connection to a PBX using pots ports doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.3. ADSL/HDSL lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.1. How can I verify if an ADSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.2. How can I verify if a HDSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.3. Why the xDSL line is slow? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
54.3.4. Why can't I reach any website? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4. CTI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.1. How can I manage alternative CTI routings? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.2. How does Round Robin scanning method work in CTI Port Group? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
54.4.3. How can I change the POTS number length? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
54.4.4. How can I activate the Caller Identification Presentation (CLIP) on POTS ports? . . . . . . . . . . . . . . . . . 1010
54.4.5. How can I manage the Calling Line Identification (CLI) for outcoming calls? . . . . . . . . . . . . . . . . . . . . 1010
54.4.6. Why during a call do I hear a fax handshaking? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
54.4.7. How can I view the maximum number of simultaneous calls supported by Abilis? . . . . . . . . . . . . . . . 1011
54.4.8. How can I view the available coders supported by the cards installed in Abilis? . . . . . . . . . . . . . . . . . . 1012
54.4.9. How can I change the volume of a compressed call? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
54.4.10. How many VoIP channels are used, depending on the call's source and destination? . . . . . . . . . . . . . 1013
54.4.11. What happens if a call fails with the “CAUSE:FF B4 (CPX,Loop)”? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
54.4.12. How can i configure sip multialerting? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5. IP router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.1. How can I query the IP routing table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.2. How does ACLBYPASS parameter work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.3. How can I view the Abilis ARP table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.4. How can I filter the NAT sessions? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
54.6. Abilis system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.1. How can I view the current RAM usage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.2. How can I view the current HD/CF space occupation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
54.6.3. How can I view the current CPU load? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.4. How can I view if the BRI card has the H.100 bus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.5. Is it possible to extract clock synchronization from BRIO cards? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.6. How can I view if the Abilis USB ports are enabled? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.7. Why do I get the error “RESOURCE NOT PRESENT OR NOT RUNNING” when I initialize
a resource? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.6.8. How can I change the Abilis prompt name? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7. Tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7.1. How can i have information about the use of ISDN backup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.8. IPSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
54.8.1. Why the outgoing traffic from CPX toward an IPSEC vpn is blocked after updating from 6.5.x
to 7.0.x? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
54.9. CTISMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.1. Can SMS to Email be sent an SMTP server different from the Abilis one? . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.2. Can SMS also send CC: and BCC:? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.3. Can SMS to Email or Email to SMS be more than 160 characters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.4. Are attachments supported for email to SMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.5. Can SMS be send thru a dialing plan to take advantage of cheaper or marketing promo when
sending SMS within the same Telco? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10. UMTS Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.1. How can I improve the quality of the calls with UMTS Box? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.2. How does Abilis manage the PIN code of a SIM card? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026

899
Draft Draft

Chapter 51. HowTo - Management

Marco Bellesia

Table of Contents
51.1. How to enter into the Abilis control-program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
51.1.1. How to enter into the Abilis control-program through the TELNET protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
51.1.2. How to enter into the Abilis control-program through the serial-asynchronous port of the Abilis . . . . . . . . . . 901
51.1.3. How to enter into the Abilis control-program through the SSH protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
51.1.4. How to enter into the Abilis control-program through an ISDN connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
51.2. How to prepare an Abilis Compact-Flash using a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
51.3. How to use the Console configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
51.3.1. How to create a new configuration file DRIVERS.CFG with the Console configurator . . . . . . . . . . . . . . . . . . . . 906
51.3.2. How to modify an existing configuration file DRIVERS.CFG with the Console Configurator . . . . . . . . . . . . . 908
51.4. How to remotely upgrade the Abilis firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
51.5. How to remotely transfer files using a terminal emulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.1. How to download configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
51.5.2. How to upload configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
51.6. How to restart the Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.7. How to upgrade configuration files to newer firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
51.8. How to copy files using a removable drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
51.8.1. How to copy configuration and log files on an USB disk through the command-line interface . . . . . . . . . . . . . 914
51.8.2. How to copy configuration and log files on an USB disk using the MFIDE front panel . . . . . . . . . . . . . . . . . . . . 915
51.8.3. How to copy configuration files from an USB disk to the Abilis HD/CF through the command-line
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
51.8.4. How to copy configuration files from an USB disk to the Abilis HD/CF using the MFIDE front panel . . . . . 916
51.9. How to know which kind of hardware is mounted on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.9.1. How to recognize PCI cards model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
51.10. How to automatically reassign the USBPORTID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
51.11. How to manage licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.12. How to view boot log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13. How to change the login passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.1. How to change the TELNET password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.2. How to change the SSH password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.13.3. How to change the users' passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
51.14. How to activate the Abilis SSH server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.15. How to open a TELNET connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
51.16. How to open a SSH connection from Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
51.17. How to create a list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
51.17.1. How to create a list of ISDN numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.2. How to create a list of IP addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.17.3. How to create a list of IP addresses ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.18. How to configure Abilis as a SYSLOG client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
51.19. How to trace the internal events for debugging purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
51.19.1. How to convert Abilis CPX traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925

51.1. How to enter into the Abilis control-program

The Abilis control-program can be reached in the following ways:

• through a TCP/IP network using the TELNET or SSH protocol;

• through the Abilis serial-asynchronous port;

• through an ISDN connection.

900
Draft HowTo - Management Draft

51.1.1. How to enter into the Abilis control-program through the

TELNET protocol
The Eth-1 port is activated by default with the following configuration:

• IP Resource: IP-1

• IP Address: 192.168.1.1

• IP Subnet Mask: 255.255.255.0

The TELNET server is activated by default.

1. Connect an ethernet RJ-45 straight cable from the Abilis Eth-1 port to a hub or switch, while making sure that your PC is
also connected to the same hub or switch. It also possible to connect an ethernet RJ-45 cross cable from the Abilis Eth-1
port to your PC.

2. Configure your PC with a free IP address in the 192.168.1.0/24 network (e.g. ip:192.168.1.2, mask:255.255.255.0).

3. Run a TELNET client (e.g. the Windows Command Prompt, Windows HyperTerminal, Zoc, Putty, etc..) and connect to
the Abilis IP address 192.168.1.1: the Abilis Control Port will appear.

In a Windows O.S. the easiest way to reach TELNET is to go to the Start Menu and choose Run; in the box which comes
up, type telnet 192.168.1.1 and press the return key or click the OK button: the Abilis Control Port will appear.

51.1.2. How to enter into the Abilis control-program through the

serial-asynchronous port of the Abilis
The serial-asynchronous port (PAD-1) is activated by default.

1. Connect an asynchronous RS232/V24 Null-Modem cable (DB9F-DB9F or DB9F-DB25F)1 from the Abilis asynchronous
port (PAD-1) to the serial DB9 or DB25 male connector of your PC.

2. Run a terminal emulator program (e.g. Windows HyperTeminal, Zoc, Putty, etc.) and configure it with the following
characteristics:

• Emulation: TTY or VT100

901
Draft HowTo - Management Draft

• Speed (bits per second): 9600

• Data bits: 8

• Stop bits: None

• Parity: 1

• Flow Control: None

3. When the PAD local port prompt appears (CPX/PAD1), type 00-cp: the Abilis Control Port will appear.

51.1.3. How to enter into the Abilis control-program through the SSH
protocol
The Eth-1 port is activated by default with the following configuration:

• IP Resource: IP-1

• IP Address: 192.168.1.1

• IP Subnet Mask: 255.255.255.0

The SSH server is not activated by default; to activate it, refer to Section 51.14, “How to activate the Abilis SSH server”.

1. Connect an ethernet RJ-45 straight cable from the Abilis Eth-1 port to a hub or switch, while making sure that your PC is
also connected to the same hub or switch. It also possible to connect an ethernet RJ-45 cross cable from the Abilis Eth-1
port to your PC.

2. Configure your PC with a free IP address in the 192.168.1.0/24 network (e.g. ip:192.168.1.2, mask:255.255.255.0).

3. Run a SSH client (e.g. the Zoc, Putty, etc.) and connect to the Abilis IP address 192.168.1.1 using the username “root” (by
default the password is empty): the Abilis Control Port will appear.

51.1.4. How to enter into the Abilis control-program through an ISDN

connection
The X25-999 resource is activated by default and it is used to receive a remote ISDN connection.

Let's see how to configure “Abilis 1” and how to connect to “Abilis 2”.

Physical connections:

• Verify that an ISDN card (QPRIX, PB44X, BRI-HFC4, BRI-HFC8, BRIO) is installed in both Abilis. If the card is not
present, insert it in a free PCI slot.

• Connect the ISDN card to NT devices.

902
Draft HowTo - Management Draft

Enter into the Abilis-1 control-program (through TELNET, SSH or the serial-asynchronous port) or open the configuration
file with the Console configurator and type the following commands.

Configure the ISDN port towards ISDN lines.

a res:x25-1 subtype:bch Add a “X25 over B-Channel” resource.
s p x25-1 cgo:01234567 cdo:01765432 Configure in the CGO parameter the ISDN number of “Abilis
1” and in the CDO parameter the ISDN number of “Abilis 2”.
s p x25-1 sgi:DISABLED sgo:CPISDN Configure the input and output calling sub-addresses.
s p x25-1 x25:dce Configure the DCE behaviour of the X25-1 port.
s r pr:0 cdi:00 Configure the routing toward the Control Port.
a r pr:1 in:* out:x25-1 cdi:221 cdo:* Add a X25 routing toward the X25-1 port. The value 221 in
the CDI parameter corresponds to X25-1 port.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the X25-1 resource running.

After Abilis restart, enter into the Abilis control-program and connect to “Abilis 2” using the following commands.

[12:18:17] ABILIS_1: <--- type the combination Ctrl+P to access to TELNET server prompt o

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>221-cp <--- connect to “Abilis 2” through the X25-1 resource.

COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 12:19:03 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[12:19:05] ABILIS_2:

903
Draft HowTo - Management Draft

To go back to “Abilis 1” prompt, type the following commands.

[12:19:47] ABILIS_2: <--- type the combination Ctrl+P to access to TELNET server prompt o

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>00-cp <--- connect to “Abilis 1” Control Port.

COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 12:20:08 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[12:20:10] ABILIS_1:

Note
Please refer to Section 51.15, “How to open a TELNET connection from Abilis” to know how to access
telnet client of remote abilis when using ISDN.

51.2. How to prepare an Abilis Compact-Flash using a PC

Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that
you want to install; in the following page, download the “Standard package” archive cpx-X.Y.Z-std-package.exe
(X.Y.Z stands for the release number).

Extract the archive double-clicking the cpx-X.Y.Z-std-package.exe. The following files will be extracted: bm.RTB,
bootd16.exe, Bootdisk.exe, cpx.pkg, install.bat, pkgmake.exe, version.bat.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

Warning
Every Abilis is associated with a specific Compact Flash unit: it may occur that the same Compact Flash
unit doesn't work with another Abilis.

If you want to substitute the Compact Flash, please contact Abilis technical support (<[email protected]>)
indicating the CF model and Abilis motherboard model (see the label on the Abilis rear panel near PCI
slots). Antek will provide a new CF compatible with your Abilis motherboard.

1. Connect a Compact Flash reader to a PC.

2. Insert a Compact Flash and delete all files. It is not recommended to format the CF. If needed, the CF must be formatted
using FAT32 file system.

Tip
It's recommended to use jame’s format tool to format the CF. Follow the steps below:

• download2 the ZIP and extract it to C:\DOS-on-CF;

• make a link to "C:\DOS-on-CF\James' Format Tool.exe" on your desktop.

Every time you need a CF with DOS installed, run the "James' Format Tool" link on your desktop and set
all the program properties as shown in the figure below:

904
Draft HowTo - Management Draft

Figure 51.1. Jame's format tool

Parameters are:

• Device - the drive letter containing the CF to format;

• File system - file system of the new CF (always choose FAT32);

• Volume label - a label displayed together with the drive letter; generally left blank;

• Format device - you have to check it in order to make a DOS-bootable CF;

• Enable compression - only available with file systems like NTFS;

• Create a DOS startup disk - leave it unchecked.

Then click "Start".

3. Open the MS-DOS prompt and go into the directory in which you have extracted the “Standard package” archive and type
the command: install <letter_associated_to_CF_reader>:

For example:

905
Draft HowTo - Management Draft

4. Copy the configuration files DRIVERS.CFG and DRIVERS.BCK on the Compact Flash into the <release_number>
directory (e.g. the F:\7-0-3\ directory).

Note
Make sure that the configuration files are compatible with the firmware version.

5. Safely remove USB CF reader from the PC.

6. Insert the Compact Flash into the MFIDE.

7. Switch on the Abilis CPX, by pressing the button POWER of the front panel. After the firmware is loaded, both LEDs of
the front panel will light every second; it means the Abilis CPX regularly started.

51.3. How to use the Console configurator

The Console configurator is an utility to create and modify the Abilis CPX configuration files offline. It is a console mode
Windows application which precisely reproduce the same Control Port interface available on a working Abilis CPX.

Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that
you want to use; in the following page, download the “Console configurator” utility (config.exe).

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

51.3.1. How to create a new configuration file DRIVERS.CFG with the

Console configurator
1. Double click the config.exe file: the following window will appear. It is also possible to open the MS-DOS prompt,
go into the directory that contains the config.exe file and type the command config.

906
Draft HowTo - Management Draft

2. Type y to confirm the creation of a new DRIVERS.CFG file.

3. A default DRIVERS.CFG file is loaded.

At the end of the configuration writing, save the changes with the save conf command and close the program with the
close or exit commands or close the window by clicking the Close Button (“X”).

907
Draft HowTo - Management Draft

51.3.2. How to modify an existing configuration file DRIVERS.CFG

with the Console Configurator
• If the config.exe and DRIVERS.CFG files are in the same directory:

• Double click the config.exe file: the DRIVERS.CFG file will be loaded.

• Open the MS-DOS prompt, go into the directory that contains the config.exe file and type the command config.

• If the config.exe and DRIVERS.CFG files are in different directories:

• Open the MS-DOS prompt, go into the directory that contains the config.exe file and type the command config -
p<path> (e.g. config -pc:\Abilis_CPX\7-0-3\).

At the end of the configuration writing, save the changes with the save conf command and close the program with the close
or exit commands or close the window by clicking the Close Button (“X”).

51.4. How to remotely upgrade the Abilis firmware

Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that
you want to install; in the following page, download the “Standard package” archive cpx-X.Y.Z-std-package.exe
(X.Y.Z stands for the release number).

Extract the archive double-clicking the cpx-X.Y.Z-std-package.exe file. The following files will be extracted:
bm.RTB, bootd16.exe, Bootdisk.exe, cpx.pkg, install.bat, pkgmake.exe, version.bat.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

1. Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal,
Zoc, ecc...).

2. Upload the cpx.pkg file with the sys update command:

• with XMODEM protocol: sys update

• with ZMODEM protocol: sys update z

908
Draft HowTo - Management Draft

For example, if you use Zoc program:

Note
If the package file is already present in the “C:\PKG\” directory, it is possible to install it with the
command: sys update <new_version> (e.g. sys update 7-0-3).

3. Once the new firmware version is installed, it's necessary to copy the configuration file into the version directory. The
procedure varies depending on compatibility of drivers.cfg files.

• If the new version installed is compatible with the current one, type the command: save conf <new_version> (e.g. save
conf 7-0-3).

• If the new version is not compatible with the current one:

a. Download the running drivers.cfg file.

b. Convert the file into the new firmware release.

c. Upload the converted file into the new version directory.

4. Configure the version that must be loaded at next system startup using the command: sys set boot version
<new_version> (e.g. sys set boot version 7-0-3).

5. Restart the Abilis.

909
Draft HowTo - Management Draft

51.5. How to remotely transfer files using a terminal

emulator
Abilis supports XMODEM, XMODEM-1K and ZMODEM file transfer protocols.

All files present in the Abilis HD/CF can be downloaded with the file get command or uploaded with the file put command.

51.5.1. How to download configuration files

1. Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal,
Zoc, ecc...).

2. Download the configuration file with the file get command.

• to download the configuration file of a running version:

• with XMODEM protocol: file get drivers.cfg

• with ZMODEM protocol: file get z drivers.cfg

• to download the configuration file of a not-running version:

• with XMODEM protocol: file get drivers.cfg <version> (e.g.. file get drivers.cfg 7-0-3)

• with ZMODEM protocol: file get z drivers.cfg <version> (e.g.. file get z drivers.cfg 7-0-3)

For example, if you use Zoc program:

910
Draft HowTo - Management Draft

51.5.2. How to upload configuration files

1. Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal,
Zoc, ecc...).

2. Upload the configuration file with the file put command.

• to upload the configuration file into a running version:

• with XMODEM protocol: file put drivers.cfg

• with ZMODEM protocol: file put z drivers.cfg

• to download the configuration into a not-running version:

• with XMODEM protocol: file put drivers.cfg <version> (e.g.. file put drivers.cfg 7-0-3)

• with ZMODEM protocol: file put z drivers.cfg <version> (e.g.. file put z drivers.cfg 7-0-3)

For example, if you use Zoc program:

911
Draft HowTo - Management Draft

51.6. How to restart the Abilis

A system restart is required in the following cases:

• a new resource or device has been added (e.g. a res:ip-2 or a dev:bri4-1);

• a new resource or device has been set active (e.g. s act res:ssh or s act dev:eth-2);

• a lowercase parameter of a resource has been modified (e.g. s p dhcp mode:server).

It is possible to restart the Abilis in two ways:

• warm start : it immediately executes the system restart.

• s g sysrbtime:<hh:mm> : it executes an automatic restart after <hh> hours and <mm> minutes. (e.g. s g
sysrbtime:01:00).

51.7. How to upgrade configuration files to newer

firmware versions
Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that
you want to install; in the following page, download the “Console Configuration Converter” file convcfg.exe or the “GUI
configuration converter” file convcfgw.exe.

912
Draft HowTo - Management Draft

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

For example, if you use the “GUI configuration converter”, follow these instructions:

1. Double-click the convcfgw.exe file: the following window will appear.

2. Select in the Source file field the file that must be converted and in the Target file field the new file.

3. Click the Convert button.

913
Draft HowTo - Management Draft

4. Click the OK button: the report messages will be shown.

5. Click the OK button to close the window and then the Exit button to close the program.

51.8. How to copy files using a removable drive

51.8.1. How to copy configuration and log files on an USB disk
through the command-line interface
Insert an USB disk in one of the Abilis USB ports.

Tip
Type the command sys disk info to verify that the USB device is correctly mounted.

[17:11:41] ABILIS_CPX:_sys disk info

Logical drive(s) information:

Drv Disk Label FAT Free space Used space Total space
Interface Sectors per block Cluster size Bootable
-------------------------------------------------------------------------------
C: HD-0 16 105 MB 13 MB 119 MB
IDE-PIO-32 1 2,048 Bytes YES
-------------------------------------------------------------------------------
D: HD-4 UDISK 32 978 MB 4 KB 978 MB
USB 4,096 Bytes YES
-------------------------------------------------------------------------------

Enter into the Abilis control-program and type the following commands.

conflog backup Copy the configuration (DRIVERS.CFG and

DRIVERS.BCK) and log files (CPX.LOG, CPX.DBG and
or CPX.XCP).

conf backup or

Copy only the configuration files (DRIVERS.CFG and

DRIVERS.BCK).

914
Draft HowTo - Management Draft

51.8.2. How to copy configuration and log files on an USB disk using
the MFIDE front panel
1. Switch on the Abilis and keep pressed the “Up” button during the system start-up. The following messages are displayed:

2. Press “OK” button: the request to insert a floppy disk in the drive will be shown:

3. Press “OK” button. The messages “CONFLOG BACKUP”, “IN PROGRESS...” will be shown and Abilis CPX will
copy current configuration and Log files (DRIVERS.CFG, DRIVERS.BCK, DHCP.BND, CPX.LOG, CPX.DBG and
CPX.XCP) to the floppy disk. During the configuration and Log files copying procedure, a message is shown informing
the User about the file that is going to be copied and about the result of the operation. These messages are of the following
form:

Where:

• FFFFFFF.FFFF is the name of the file that is going to be processed (DRIVERS.CFG, DRIVERS.BCK, DHCP.BND,
CPX.LOG, CPX.DBG and CPX.XCP);

• ... signals that the operation is still in progress;

• done signals that the operation was successfully ended;

• E-nn signals that an error occurred on the file that is going to be processed, nn is a decimal value.

If the operation is successful, the messages “CONFLOG BACKUP”, “EXECUTED” are shown; otherwise the messages
“CONFLOG BACKUP”, “ENDED WITH ERROR” will be displayed.

4. After the backup phase completion, the next step of the procedure (i.e. configuration files restore phase) is initiated:

Pressing “Left” button it is possible to go to the next step of the procedure (i.e. configuration files restore), while pressing
“Left” button it is possible to end the procedure.

915
Draft HowTo - Management Draft

5. If you press the “Left” button, these messages will be displayed:

Press “Ok” button to proceed with Abilis CPX software initialization.

Press “Left” button to restart Abilis CPX system.

Press “Up” button to execute the configuration recovery procedure from the beginning once again.

51.8.3. How to copy configuration files from an USB disk to the

Abilis HD/CF through the command-line interface
Insert an USB disk in one of the Abilis USB ports.

Tip
Type the command sys disk info to verify that the USB device is correctly mounted.

[17:11:41] ABILIS_CPX:_sys disk info

Logical drive(s) information:

Drv Disk Label FAT Free space Used space Total space
Interface Sectors per block Cluster size Bootable
-------------------------------------------------------------------------------
C: HD-0 16 105 MB 13 MB 119 MB
IDE-PIO-32 1 2,048 Bytes YES
-------------------------------------------------------------------------------
D: HD-4 UDISK 32 978 MB 4 KB 978 MB
USB 4,096 Bytes YES
-------------------------------------------------------------------------------

Enter into the Abilis control-program and type the following commands.

conflog restore / conf restore Copy the configuration files (DRIVERS.CFG,

DRIVERS.BCK) on HD/CF.

51.8.4. How to copy configuration files from an USB disk to the

Abilis HD/CF using the MFIDE front panel
1. Switch on the Abilis and keep pressed the “Up” button during the system start-up. The following messages are displayed:

2. Press “Left” button.

916
Draft HowTo - Management Draft

3. Press “OK” button: the request to insert a floppy disk in the drive will be shown:

4. Press “OK” button. The messages “CONFLOG RESTORE”, “IN PROGRESS...” will be shown and Abilis CPX will copy
configuration files (DRIVERS.CFG and DRIVERS.BCK) from the floppy disk to the HD/CF. During the configuration
and Log files copying procedure, a message is shown informing the user about the file that is going to be copied and about
the result of the operation. These messages are of the following form:

Where:

• FFFFFFF.FFFF is the name of the file that is going to be processed (DRIVERS.CFG and DRIVERS.BCK);

• ... signals that the operation is still in progress;

• done signals that the operation was successfully ended;

• E-nn signals that an error occurred on the file that is going to be processed, nn is a decimal value.

If the operation is successful, the messages “CONFLOG RESTORE”, “EXECUTED” are shown; otherwise the messages
“CONFLOG RESTORE”, “ENDED WITH ERROR” will be displayed.

After the configuration files restore phase completion, it possible either to make the Abilis CPX system start-up to
proceed; or to make the system to be restarted; or to re-execute the procedure from the beginning.

51.9. How to know which kind of hardware is mounted on

Abilis
51.9.1. How to recognize PCI cards model
Enter into the Abilis control-program and type the command d pcidev to view a list of mounted PCI devices.

[10:10:10] ABILIS_CPX:d pcidev

PCI Server Overview:

ID Vendor Device CardName Slot/F Ver Irq

-------------------------------------------------------------------------------
0 8086 INTEL 7190 BRIDGE HOST - 0/0 0.03 -
1 8086 INTEL 7191 BRIDGE PCI NORMAL - 1/0 0.03 -

917
Draft HowTo - Management Draft

2 8086 INTEL 7110 BRIDGE ISA - 7/0 0.02 -

3 8086 INTEL 7111 STORAGE IDE - 7/1 0.01 -
4 8086 INTEL 7112 USB HOST UHCI - 7/2 0.01 9
5 8086 INTEL 7113 BRIDGE OTHER - 7/3 0.02 -
6 1011 DEC 0019 NETWORK ETHERNET ETH-FL100TX 8/0 4.01 10
7 10EC REALTEK 8139 NETWORK ETHERNET ETH-RTL8139 9/0 1.00 5
8 10EC REALTEK 8139 NETWORK ETHERNET ETH-RTL8139 10/0 1.00 12
9 1283 ITE 8872 SERIAL 16550 CTI-POTS 11/0 0.01 9
10 10B5 PLX TECHNO 9050 BRIDGE OTHER CTI-HFC-OKI-4P 12/0 0.02 10

The following table shows the field Cardname and the correspondig model.

CardName Model
CTI-HFC-SWIX-4PB BRI-HFC4
CTI-HFC-SWIX-8P BRI-HFC8
CTI-HFC-OKI-4P BRI-HFC4 with H100 bus(old model)
CTI-HFC-OKI-4P BRI-HFC8 with H100 bus(old model)
CTI-HFC-4P BRI-HFC4 without H100 bus(old model)
CTI-HFC-8P BRI-HFC8 without H100 bus(old model)
CTI-POTS POTS card
CTI-VoIP Voip card

51.10. How to automatically reassign the USBPORTID

Enter into the Abilis control-program and type the command d dev to view the list of devices.

Abilis automatically assign an USB port id when a usb device is added and plugged.

[17:49:02] ABILIS_CPX:_d dev

...
------------------ Active USB Devices and Physical Resources: -----------------
Device(s) Run Con Physical Resource(s) or CTI Port(s) USBPORTID
-------------------------------------------------------------------------------
ADSLUSB-1 Yes Yes Adsl-1 . . . . . . . . . . . . . . . . 3.0
ADSLUSB-2 No No Adsl-2 . . . . . . . . . . . . . . . . 1.0.0
ADSLUSB-3 Yes Yes Adsl-3 . . . . . . . . . . . . . . . . 1.1
ADSLUSB-4 Yes Yes Adsl-4 . . . . . . . . . . . . . . . . 2.0
CELLBOX-1 201..202 . . . . . . . . . . . . . . .
CELL-1 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.1.0
CELL-2 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.1.1
CODEC-1 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.1.2
SIMEMU-1 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.1.3
CELLBOX-2 203..204 . . . . . . . . . . . . . . .
CELL-3 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.3.0
CELL-4 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.3.1
CODEC-2 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.3.2
SIMEMU-2 Yes Yes . . . . . . . . . . . . . . . . . . . 1.0.3.3
GPIO-1 Yes Yes Gpio-1 . . . . . . . . . . . . . . . . 4.0
BLUSB-1 Yes No Blusb-1 . . . . . . . . . . . . . . . -
...

The usbportid can't change on-the-fly plugging and unplugging a device on a different port. If connecting a device on a
different port is needed, follow the below steps to reconfigure the USBPORTID parameter:

s dev:[device name] usbportid:none cancel the usbportid

save conf save the configuration
warm start restart Abilis

918
Draft HowTo - Management Draft

51.11. How to manage licences

Assuming the licence file is named LIC1-0000002001.TXT, enter into the Abilis control-program and type the following
commands.

licence put LIC1-0000002001.TXT upload the licence file named LIC1-0000002001.TXT to

Abilis
warm start restart Abilis

Refer to chapter Chapter 6, Licencing to learn more about managing licences.

51.12. How to view boot log

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

sys display boot log Show the boot manager log

Caution
Read carefully the chapter SYS DISPLAY BOOT LOG to have more information about some issues arising
from updating Abilis firmware to version 7.x.

51.13. How to change the login passwords

51.13.1. How to change the TELNET password
The TELNET server is activated by default with an empty password.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p telnet pwd:telnet_pwd Configure the TELNET password.

save conf Save the configuration.

51.13.2. How to change the SSH password

The SSH server is not by default. Refer to chapter Section 51.14, “How to activate the Abilis SSH server” to activate it.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p ssh pwd:ssh_pwd Configure the SSH password.

save conf Save the configuration.

51.13.3. How to change the users' passwords

The USER, ADMIN and SUPER users are activated by default with an empty password.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p cp pwdu:user_pwd Configure the USER password.

s p cp pwda:admin_pwd Configure the ADMIN password.
s p cp pwds:super_pwd Configure the SUPER password.
save conf Save the configuration.

919
Draft HowTo - Management Draft

51.14. How to activate the Abilis SSH server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ssh Add the SSH resource.

or or

s act res:ssh If the resource already exists, set it active.

save conf Save the configuration.

On a working Abilis, a system restart is required to make the SSH resource running.

51.15. How to open a TELNET connection from Abilis

The TELNET server and client are activated by default.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a r pr:1 in:telnet out:telnet cdi:* udi:tln Transfer an incoming TELNET session to an outgoing
TELNET session.
a r pr:2 in:* out:telnet cdi:* udi:tln Transfer any incoming session to an outgoing TELNET
session.
save conf Save the configuration.

To open a TELNET connection from “ABILIS_1” to “ABILIS_2”, type the following commands.

[16:13:17] ABILIS_1: <- type Ctrl+P to access to the TELNET server prompt of “Abilis_1”.

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>1-tln <- to access to the TELNET client prompt of “Abilis_1”.

COM

[192.168.1.1] TELNETC>open 192.168.5.254 <- to open a connection to the remote host.

Trying 192.168.5.254 ... Open

User Access Verification

Password: *********
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 16:14:21 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[16:14:27] ABILIS_2:

Note
If you are connected to “ABILIS_1” through an ISDN call, if you type the combination Ctrl+P, the
TELNET server prompt of the Abilis that generates the call will be shown.

To access to the TELNET client of “ABILIS_1”, you have to type the 22n-tln command, where n refers to
the X25-n port that you have used for the connection. For example:

[10:39:17] ABILIS_1: <- type Ctrl+P to access to the TELNET server prompt of the Abili

920
Draft HowTo - Management Draft

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>221-tln <- to access to the TELNET client prompt of “Abilis_1”.

COM

[192.168.2.1] TELNETC>open 192.168.5.254 <- to open a connection to the remote host.

Trying 192.168.5.254 ... Open

User Access Verification

Password: *********
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 10:40:21 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[10:40:59] ABILIS_2:

51.16. How to open a SSH connection from Abilis

The SSH server and client aren't activated by default; to activate it, refer to Section 51.14, “How to activate the Abilis SSH
server”.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a r pr:3 in:ssh out:ssh cdi:* udi:ssh Transfer an incoming SSH session to an outgoing SSH
session.
a r pr:4 in:* out:ssh cdi:* udi:ssh Transfer any incoming session to an outgoing SSH session.
save conf Save the configuration.

To open a SSH connection from “ABILIS_1” to “ABILIS_2”, type the following commands.

[10:39:17] ABILIS_1: <- type Ctrl+P to access to the TELNET server prompt of “Abilis_1”.

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>1-ssh <- to access to the SSH client prompt of “Abilis_1”.

COM

[192.168.2.1] SSHC>open 192.168.5.254 <- to open a connection to the remote host.

Trying 192.168.5.254 ... Open

User Access Verification

Password: *********
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 10:40:58 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

921
Draft HowTo - Management Draft

[10:40:59] ABILIS_2:

Note
If you are connected to “ABILIS_1” through an ISDN call, if you type the combination Ctrl+P, the Telnet
server prompt of the Abilis that generate the call will be shown.

To access to the SSH client of “ABILIS_1”, you have to type the 22n-ssh command, where n refers to the
X25-n port that you have used for the connection. For example:

[10:39:17] ABILIS_1: <- type Ctrl+P to access to the TELNET server prompt of the Abili

[192.168.1.1] TELNETS>clr

CLR 00 00

[192.168.1.1] TELNETS>221-ssh <- to access to the SSH client prompt of “Abilis_1”.

COM

[192.168.2.1] SSHC>open 192.168.5.254 <- to open a connection to the remote host.

Trying 192.168.5.254 ... Open

User Access Verification

Password: *********
COM

Abilis CPX - Ver. 7.0.3/STD - Build 3357.17

Tuesday 21/12/2010 10:40:58 (UTC+1.00)
Login:super
Password:
Logged as SUPERUSER

[10:40:59] ABILIS_2:

51.17. How to create a list

By the terms “Elements Lists” we refer to a list of objects, belonging to the same homogeneous type, that are identified by
the generic term “item”. The possible “item” values are:

• IN: ISDN numbers

• IS: ISDN sub-addresses

• EC: CTIC clusters

• XN: X.25 NUAs

• XU: X.25 User data fields

• IP: IP addresses

• IR: IP addresses ranges

• DN: dialling numbers

• CR: CPX resources

• TUP: TCP/UDP ports

• IPT: Internet Protocols

• MAC: MAC Addresses

• SAP: SAP values

• H323ID: H.323 ID aliases

• CLNUM: CTICL Numbers

922
Draft HowTo - Management Draft

• INR: ISDN Number Replacement

• RU: Rules

• MR: Master Rules

Some examples follow.

51.17.1. How to create a list of ISDN numbers

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

list create tech_support IN Numbers_technical_support Create the list technical_support, with type
IN (Isdn Numbers) and give it the description
Numbers_technical_support.
a list:tech_support 21 24 27 02223344 Insert the numbers in the list.
save conf Save the configuration.

On a working Abilis, the changes on a list are immediately active.

51.17.2. How to create a list of IP addresses

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

list create SMTP_allowed IP Create the list SMTP_allowed, with type

IP_Address_allowed_to_SMTP IP (IP addresses) and give it the description
IP_Address_allowed_to_SMTP.
a list:SMTP_allowed 60.60.60.60 61.61.61.61 Insert the IP addresses in the list..
save conf Save the configuration.

On a working Abilis, the changes on a list are immediately active.

51.17.3. How to create a list of IP addresses ranges

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

list create NET_site2 IR Network_Site_2 Create the list NET_site2, with type IR (Ip addresses
Range) and give it the description Network_Site_2.
a list:NET_site2 10.0.0.0:10.0.0.255 10.0.2.0:10.0.2.255 Insert in the IP addresses range in the list.
save conf Save the configuration.

On a working Abilis, the changes on a list are immediately active.

51.18. How to configure Abilis as a SYSLOG client

Assuming to have:

• a syslog server with ip address 192.168.0.100

let's configure abilis to send its logs to syslog server.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:syslog Add the SYSLOG resource.

or or

s act res:syslog If the resource already exists, set it active.

s p syslog act:yes Set the resource active
s p syslog hostname:abilis Configure the host name

923
Draft HowTo - Management Draft

s p syslog receiver1:192.168.0.100 Configure the ip address of syslog server

save conf Save the configuration.

On a working Abilis, a system restart is required to make the SYSLOG resource running.

51.19. How to trace the internal events for debugging

purposes
Enter into the Abilis control-program with a Terminal Emulator with file transfer support (e.g. Windows HyperTerminal,
Zoc, ecc...), and type the following commands.

d pstack Identify the internal port number associated to the resource

for which you want to activate the trace. (e.g. suppose the
ETH100-1 resource).
trace act po:24 data:1600 Activate the trace function.
trace start Start saving the events.
trace stop Stop tracing the events.
trace get z Download the trace from Abilis.

Warning
Verify the parameters settings of the internal events trace using the command trace param. If a trace is
runnig the following message is shown:

[14:04:34] ABILIS_CPX:trace act po:19,18 data:1600

TRACE RUNNING

The trace continues to be active on ports shown by trace param command and not on those specified by
trace act command.

[14:04:50] ABILIS_CPX:trace param

Configured Value Active Value Description

------------------------------------------------------------------------------
PO: 024,019 024,019 Ports to be traced
SIZE: 8192 (Kbytes) 8192 (Kbytes) Tracer buffer size
DATA: 1600 (bytes) 1600 (bytes) Max. event buffer size
CMD: STD STD Command(s) to be traced
LSN: ALL ALL SD/RV lsn to be traced
TYPE: ALL ALL SD/RV type to be traced
STATE: - RUNNING Current Tracer state
TSAVE: NO NO Automatic trace saving
EVENTS: - 49929 Number of events
SNDRCV: - 24943 Number of send & receive
LENGTH: - 8191 (Kbytes) Current trace length

Stop the trace and set it inactive:

[14:13:42] ABILIS_CPX:trace stop

COMMAND EXECUTED

[14:15:14] LUIGI_DEMURO:trace inact

COMMAND EXECUTED

Configure the trace and follow the steps of the how to:

[14:17:40] ABILIS_CPX:trace act po:24,18 data:1600

924
Draft HowTo - Management Draft

COMMAND EXECUTED

[14:17:48] ABILIS_CPX:trace param

Configured Value Active Value Description

------------------------------------------------------------------------------
PO: 024,019 024,018 Ports to be traced
SIZE: 8192 (Kbytes) 8192 (Kbytes) Tracer buffer size
DATA: 1600 (bytes) 1600 (bytes) Max. event buffer size
CMD: STD STD Command(s) to be traced
LSN: ALL ALL SD/RV lsn to be traced
TYPE: ALL ALL SD/RV type to be traced
STATE: - ACTIVE/READY Current Tracer state
TSAVE: NO NO Automatic trace saving
EVENTS: - 0 Number of events
SNDRCV: - 0 Number of send & receive
LENGTH: - 0 (Kbytes) Current trace length

For example, if you use Zoc program:

Abilis CPX traces are saved in a proprietary format “cpx”. Follow these instructions to convert them in other formats (pcap,
bxa, ...).

51.19.1. How to convert Abilis CPX traces

Go to http://abilis.antek.it/downloads/cpx2k/download.html and click the System and tools link of the firmware Release that
you want to use; in the following page, download download a “Trace Converter” program (cpxbxa.exe, cpxtab.exe,
cpxpcap.exe or trcmgrw.exe).

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

For example, the “GUI CPX trace converter” (trcmgrw.exe) converts Abilis CPX traces into:

925
Draft HowTo - Management Draft

• BXA : is an old format used by FELINE data analyser.

• “TAB separated”: is a general purpose format usable to import data into OpenOffice or Excel speadsheets.

• PCAP: is used by Ethereal/Wireshark/Tcpdump for Ethernet/PPP/RawIP representation.

• I4B: it is a format for ISDN layer 1 representation and it can be loaded by Ethereal/Wireshark.

• VN: Visual Network format; it can be loaded by Ethereal/Wireshark for PPP representation.

For example, if you want to convert the trace in PCAP format, follow these instructions.

1. Double click the trcmgrw.exe file: the following window will appear.

2. In the To PCAP tab, select the in the Source file name field the trace that must be converted and in the Target file name
field the name of the new trace.

926
Draft HowTo - Management Draft

3. Click the OK button: in the next window select the port traced and the format.

927
Draft HowTo - Management Draft

4. Click the OK button: the result of the conversion is shown.

5. Click the OK button to close the window and then the Exit button to close the program.

928
Draft Draft

Chapter 52. HowTo - Networking

Marco Bellesia
Angelo Pignoli

Table of Contents
52.1. How to configure LAN settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.2. How to activate a new ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
52.3. How to assign several IP addresses to the same LAN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4. How to configure ADSL connections using USB modems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
52.4.1. How to configure a RFC 1483 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
52.4.2. How to configure a PPPoA (RFC 2364) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.4.3. How to configure a PPPoE connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
52.5. How to configure HDSL/SHDSL connections using V.35/G.703 synchronous ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
52.6. How to configure the default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.1. How to configure the default IP route in case Abilis is connected to an ADSL USB or V.35/G.703
modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
52.6.2. How to configure the default IP route in case Abilis is connected to an ethernet ADSL router . . . . . . . . . . . . . 936
52.6.3. How to configure an alternative default IP route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
52.7. How to configure the Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
52.8. How to share a single Internet connection among multiple computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
52.9. How to access IP hosts and services which are behind a NAT manager (port forwarding) . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
52.10. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.1. How to setup DDNS service using dyndns.org . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
52.10.2. How to setup DDNS service on Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
52.11. How to configure a Remote Access Server (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.1. How to configure a RAS using IPSEC VPN server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
52.11.2. How to configure a RAS using IPSEC VPN server with iPHONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
52.11.3. How to configure a RAS using PPPoE connections with an Ethernet/WiFi network . . . . . . . . . . . . . . . . . . . . . . 952
52.11.4. How to configure a RAS using ISDN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
52.12. How to configure an ISDN PPP Dial-UP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13. How to configure a VPN tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
52.13.1. How to configure a VPN tunnel where both Abilis have a static public IP address . . . . . . . . . . . . . . . . . . . . . . . . 955
52.13.2. How to configure a VPN tunnel where one Abilis has a dynamic public IP address or is placed behind
a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
52.13.3. How to configure a VPN tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
52.13.4. How to configure a VPN tunnel with the “double path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
52.14. How to configure a voice tunnel between two Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
52.14.1. How to configure a voice tunnel where both Abilis have a static public IP address . . . . . . . . . . . . . . . . . . . . . . . 962
52.14.2. How to configure a voice tunnel where one Abilis has a dynamic public IP address or is placed
behind a router doing NAT/PAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
52.14.3. How to configure a voice tunnel with the “backup over ISDN” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
52.14.4. How to configure a voice tunnel with the “double-path” option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
52.15. How to activate the DHCP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
52.15.1. How to activate the DHCP in relay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
52.15.2. How to activate the DHCP in server mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
52.15.3. How to activate the DHCP in client mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
52.16. How to activate the FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17. How to activate the HTTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
52.17.1. How to activate the HTTP over SSL server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
52.18. How to activate the TRFA resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
52.19. How to use state detection of IP interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20. How to activate the SNTP resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.1. How to activate the SNTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
52.20.2. How to activate the SNTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974

929
Draft HowTo - Networking Draft

52.21. How to activate the SNMP agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974

52.22. How to publish the users on the Abilis LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

52.1. How to configure LAN settings

The Eth-1 port is activated by default with the following configuration:

• IP Resource: IP-1

• IP Address: 192.168.1.1

• IP Subnet Mask: 255.255.255.0

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p ip-1 ipadd:192.168.1.254 mask:255.255.255.0 Change the IP address and the mask.

save conf Save the configuration.

On a working Abilis, you must initialize the IP-1 resource: init res:ip-1.

Caution
If you are connected to Abilis through TELNET or SSH protocol, when you execute the initialization
command, the connection will be lost!

52.2. How to activate a new ethernet port

Physical connection:

• Verify that a second Eth card is installed in the Abilis. If the card is not present, insert it in a free PCI slot.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

930
Draft HowTo - Networking Draft

a dev:eth-2 Add an ETH100 device (e.g. ETH-2).

a res:ip-2 subtype:lan Add an “IP over LAN” resource (e.g. IP-2).
s p ip-2 lanres:eth-2 Configure the ETH-2 as the IP-2 lower resource.
s p ip-2 ipadd:192.168.2.1 mask:255.255.255.0 Configure the IP address and the mask.
s p ip-2 descr:LAN_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the ETH-2 device and the IP-2 resource running.

Caution
The IP addresses of the ethernet ports must belong to different LANs!

52.3. How to assign several IP addresses to the same

LAN port
Suppose to assign to the ETH-1 port [930] a second IP address.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-10 subtype:virtual Add an “IP Virtual” resource (e.g. IP-10).

s p ip-10 p-ip:1 Configure the physical ethernet card associated to IP-10
resource.
s p ip-10 ipadd:192.168.10.1 mask:255.255.255.0 Configure the IP address and the mask.
s p ip-10 descr:Virtual_LAN Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-10 resource running.

Note
If you want to assign an IP address belonging to the same network of the IP-1 resource, you must configure
in the mask parameter the value 255.255.255.255. For example:

s p ip-10 ipadd:192.168.1.10 mask:255.255.255.255

52.4. How to configure ADSL connections using USB

modems
Physical connection:

931
Draft HowTo - Networking Draft

• Connect the USB cable from the ADSL modem to an Abilis USB port.

• Connect the ADSL modem to the telephone line using a standard RJ-11 cable.

Before proceeding with the configuration, make sure you have the following parameters available from your ISP.

Parameter Possible values

Encapsulation RFC 1483 or PPPoA (RFC 2364) or PPPoE
Multiplexing VC-Based or LLC-Based
VPI (Virtual Path Identifier) 8
VCI (Virtual Channel Identifier) 35
IP Address and Mask static (80.80.80.80/32) or dynamic
Login information (only for PPPoA or PPPoE encapsulation) username: provider_user

password: provider_pwd

The configuration varies depending on what encapsulation type you use.

Note
Abilis supports ONLY the Routing mode (not Bridge mode).

52.4.1. How to configure a RFC 1483 connection

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:adslusb-1 Add an ADSLUSB device (e.g. ADSLUSB-1).

a res:ip-3 subtype:dl Add an “IP over Dedicated Line” resource (e.g. IP-3).
s p ip-3 lowres:adsl-1 Configure the ADSL-1 as the IP-3 lower resource.
s p ip-3 enc:rfc1483-llcmux Configure a LLC-based multiplexing type.

or or

s p ip-3 enc:rfc1483-vcmux Configure a VC-based multiplexing type.

s p ip-3 vpi:8 vci:35 Configure the VPI and the VCI.
s p ip-3 ipadd:80.80.80.80 mask:255.255.255.255 Configure the IP address and the mask.
s p ip-3 descr:ADSL_RFC1483 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the ADSLUSB-1 device and the IP-3 resource running.

932
Draft HowTo - Networking Draft

Tip
Remember to configure NAT settings.

52.4.2. How to configure a PPPoA (RFC 2364) connection

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:adslusb-1 Add an ADSLUSB device (e.g. ADSLUSB-1).

a res:ip-3 subtype:ppp Add an “IP over PPP” resource (e.g. IP-3).
s p ip-3 lowres:adsl-1 Configure the ADSL-1 as the IP-3 lower resource.
s p ip-3 ppp-enc:rfc2364-vcmux Configure a VC-based multiplexing type.

or or

s p ip-3 ppp-enc:rfc2364-llcmux Configure a LLC-based multiplexing type.

s p ip-3 vpi:8 vci:35 Configure the VPI and the VCI.
s p ip-3 ipadd:retrieve neigh:retrieve Configure a dynamic IP address.

or or

s p ip-3 ipadd:80.80.80.80 Configure a static IP address.

s p ip-3 username:provider_user password:provider_pwd Configure the login information.
s p ip-3 descr:ADSL_PPPoA_(RFC2364) Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the ADSLUSB-1 device and the IP-3 resource running.

Tip
Remember to configure NAT settings.

52.4.3. How to configure a PPPoE connection

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:adslusb-1 Add an ADSLUSB device (e.g. ADSLUSB-1).

a res:poecli-1 Add a POECLI resource (e.g. POECLI-1).
a res:ip-3 subtype:ppp Add an “IP over PPP” resource (e.g. IP-3).
s p poecli-1 lowres:adsl-1 Configure the ADSL-1 as the lower POECLI-1 resource.
s p poecli-1 vpi:8 vci:35 Configure the VPI and the VCI.
s p poecli-1 ENC:RFC1483-LLCMUX PPPoE requires LLC-based multiplexing.
s p ip-3 lowres:poecli-1 Configure the POECLI-1 as the IP-3 lower resource.
s p ip-3 ipadd:retrieve neigh:retrieve Configure a dynamic IP address.

or or

s p ip-3 ipadd:80.80.80.80 Configure a static IP address.

s p ip-3 username:provider_user password:provider_pwd Configure the login information.
s p ip-3 dns:retrieve Request DNS addresses from remote servers.
s p ip-3 tcp-mss-clamp:yes Activate the TCP MSS clamping procedure.
s p ip-3 descr:ADSL_PPPoE Configure the description of the IP resource.
save conf Save the configuration.

933
Draft HowTo - Networking Draft

On a working Abilis, a system restart is required to make the ADSLUSB-1 device and the IP-3 resource running.

Tip
Remember to configure NAT settings.

52.5. How to configure HDSL/SHDSL connections using

V.35/G.703 synchronous ports
Physical connections:

• Verify that an ESB2 card is installed in the Abilis. If the card is not present, insert it in a free PCI slot.

• Connect the ESB2 synchronous port to the DCE modem using the “octopus” cable connector numbered with “0”.

Before proceeding with the configuration, make sure you have the following parameters available from your ISP.

Parameter Possible values

AR (Access Rate) 2048000 bit/sec
CIR (Committed Information Rate) 1024000 bit/sec
MCR (Minimum Cell Rate) 1024000 bit/sec
PCR (Peak Cell Rate) 1600000 bit/sec
CIR (Committed Information Rate) 1024000 bit/sec
TC (Committed rate measurement interval) 0.010 sec
LMI (Local Management Interface) standard cisco
DLCI (Data-Link Connection Identifier) 20
IP address and Mask 81.81.81.81/32

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:esb-1 Add an ESB device (e.g. ESB-1).

a res:fr-1 subtype:dl Add a “Frame Relay over Dedicated Line” resource (e.g.
FR-1).
s p fr-1 lowres:sync-1 Configure SYNC-1 resource as the lower FR-1 resource.
s p sync-1 clk:ext sp:2048000 Configure the clock source type and the Access Rate for the
SYNC-1 resource.
a res:ip-4 subtype:dl Add an “IP over Dedicated Line” resource (e.g. IP-4).

934
Draft HowTo - Networking Draft

s p ip-4 lowres:fr-1 Configure the FR-1 as the lower resource of IP-4.

s p fr-1 lmi:yes std:cisco ar:2048000 Configure the LMI standard and the Access Rate.
s p ip-4 enc:fr-ietf Configure the encapsulation type.
s p ip-4 cir:1024000 bc:10240 be:5760 Configure the CIR, BE and BC vaule.
s p ip-4 ipadd:81.81.81.81 mask:255.255.255.255 Configure the IP address and the mask.
s p sync-1 descr:HDSL_1 Configure the description of the SYNC resource.
s p fr-1 descr:HDSL_1 Configure the description of the FR resource.
s p ip-4 descr:HDSL_1 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the ESB-1 device, the FR-1 and IP-4 resources running.

Note
The BC (Committed Burst size) and BE (Excess Burst size) parameters must satisfy the following rules:

• BC = TC*CIR [bit].

• BE = (PCR-MCR)*TC [bit].

Tip
Remember to configure NAT settings.

52.6. How to configure the default IP route

52.6.1. How to configure the default IP route in case Abilis is
connected to an ADSL USB or V.35/G.703 modem

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a ipr net:0.0.0.0/0 ip:3 Add a default route by configuring in the IP parameter the
IP resource associated to the WAN connection.
save conf Save the configuration.

Note
In the Console configurator, you must type the command: a sipr id:0 net:0.0.0.0/0 ip:3

935
Draft HowTo - Networking Draft

52.6.2. How to configure the default IP route in case Abilis is

connected to an ethernet ADSL router

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a ipr net:0.0.0.0/0 gw:192.168.2.254 ip:2 Add a default route by configuring in the GW parameter the
IP address of the ADSL router and in the IP parameter the
IP resource connected to the ADSL router.
save conf Save the configuration.

Note
In the Console configurator, you must type the command: a sipr id:0 net:0.0.0.0/0 gw:192.168.2.254 ip:2

52.6.3. How to configure an alternative default IP route

Administrative distance is a feature used by routers to select the best path when there are two or more different routes
towards the same destination; the route with the lowest value of AD has the highest priority into the IP Routing table.

In the following scheme, the “Best” route for the network 0.0.0.0/0 is the IP-3 resource. Let's see how to configure the IP-4
resource as the alternative route that will be considered only if the primary one is down; in normal conditions the route
towards IP-4 resource is ignored.

936
Draft HowTo - Networking Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a ipad net:0.0.0.0/0 prot:static distance:180 ip:4 Add an entry in the IPAD table for the network 0.0.0.0/0.
a ipr net:0.0.0.0/0 ip:4 -fd Add an entry in the IPR table for the network 0.0.0.0/0.
save conf Save the configuration.

On a working Abilis, you must refresh the IPAD table: init ipad.

Note
The option -fd has been used because a static routing towards network 0.0.0.0/0 was already present.

[17:53:34] ABILIS_CPX:d ipr

Destination routes and conditional source routes:

+-+-+-+-+--------------------+--------------------+-----------------+----+---+
|B|P|S|H| NET:/MASK: | MASK: or | GW: |IP: |AD:|
| | | | | | SRNET:/SRMASK: | | | |
+-+-+-+-+--------------------+--------------------+-----------------+----+---+
...
...
|*|S| | | 000.000.000.000/0 | 000.000.000.000 | | 3| 1|
| |S| | | 000.000.000.000/0 | 000.000.000.000 | | 4|180|
+-+-+-+-+--------------------+--------------------+-----------------+----+---+

Note
In the Console configurator, you must type the command: a sipr id:1 net:0.0.0.0/0 ip:4

52.7. How to configure the Network Address Translation

(NAT)
Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:nat Add the NAT resource.

or or

s act res:nat If the resource already exists, set it active.

s p nat act:yes Enable the NAT runtime functionalities.
Configure the NAT parameter for each IP resource.
s p ip-n nat:inside NAT:INSIDE in a LAN, AIPT (AIPT-BCK) resource or
when Abilis behaves as a RAS server.
or
or
s p ip-n nat:outside
NAT:OUTSIDE in a PPP or DL (DL-BCK) resource.
or
or
s p ip-n nat:dmz
NAT:DMZ in a LAN, AIPT (AIPT-BCK) resource when a
or DMZ is configured.

s p ip-n nat:vpn or

NAT:VPN in a LAN, AIPT (AIPT-BCK) resource when a

VPN is configured.

937
Draft HowTo - Networking Draft

save conf Save the configuration.

On a working Abilis, a system restart is required to make the NAT resource running.

52.8. How to share a single Internet connection among

multiple computers
Suppose to enable the navigation to the 192.168.1.0/24 network.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

Activate the NAT resource.

a nat pr:0 inat:in onat:out add:src snet:192.168.1.0/24 Add a NAT entry for the 192.168.1.0/24 network.
anet:80.80.80.80/32 pat:yes
save conf Save the configuration.

On a working Abilis, you must refresh the NAT table: init nat.

52.9. How to access IP hosts and services which are

behind a NAT manager (port forwarding)
Suppose to enable the accesses from Internet to the following WEB and FTP servers.

938
Draft HowTo - Networking Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

Activate the NAT resource.

a nat pr:1 inat:out onat:in add:dst dnet:80.80.80.80/32 Add a NAT entry for the access to the WEB server.
anet:192.168.1.10/32 pat:yes prot:tcp dpo:8080 apo:80
a nat pr:2 inat:out onat:in add:dst net:80.80.80.80/32 Add a NAT entry for the access to the FTP server.
anet:192.168.1.20/32 pat:yes prot:tcp dpo:8021 apo:21
save conf Save the configuration.

On a working Abilis, you must refresh the NAT table: init nat.

52.10. How to setup DDNS service on Abilis

52.10.1. How to setup DDNS service using dyndns.org
Point your browser to www.dyndns.com, click Sign In. Then fill username and password if you have already an account or
Create an Account.

939
Draft HowTo - Networking Draft

Figure 52.1. Home page

If you have already an account on dyndns.com you can skip the following steps and jump to this paragraph [942].

• Fill the requested fields username, password, email

• choose the options desired in the Subscribe to section and enter the numbers of the security image

• check the privacy policy

• click the Create Account button

In the figure below username and password are abilistest. Remember these values because they will be used to configure
Abilis.

940
Draft HowTo - Networking Draft

Figure 52.2. Account creation

An email with the following text will be sent to the email address entered above. Click on the link to complete the account
creation process.

941
Draft HowTo - Networking Draft

Figure 52.3. Conformation link

Now your account is activated. Point your browser to www.dyndns.com, click Sign In and fill username and password
entered above.

942
Draft HowTo - Networking Draft

Figure 52.4. Login

After logging in, a page with services, billing and account settings is shown. Click Add Host Services in My Services column.

943
Draft HowTo - Networking Draft

Figure 52.5. Dyndns services

The following page is very important because here you can choose the DNS name associated to the dynamic ip entering
hostname and domain. For example if hostname is abilistest and the choosen domain is dyndns.org, the resulting DNS name
is abilistest.dyndns.org.

• Fill the Hostname field and select dyndns.org from the drop-down menu

• select Host with IP address radio button

• enter ip address

• select services and devices to use with the chosen hostname

• click add to cart

944
Draft HowTo - Networking Draft

Figure 52.6. Hostname configuration

Click Checkout to activate in the following page.

945
Draft HowTo - Networking Draft

Figure 52.7. Checkout

Click Next button.

946
Draft HowTo - Networking Draft

Figure 52.8. Shopping cart

Click Activate Services. Now the configuration of the services on dyndns.org is completed.

947
Draft HowTo - Networking Draft

Figure 52.9. Activation of services

In the next section there are the steps to follow to configure Abilis DDNS service.

52.10.2. How to setup DDNS service on Abilis

Assuming that the ip resource toward internet is ip-1 and it's already activated and configured (see chapters in the section
How to Networking).

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:dns Add the DDNS resource.

or or

s act res:dns If the resource already exists, set it active.

948
Draft HowTo - Networking Draft

s p ddns act:yes activate the DDNS resource

s p ddns service:dyndns.org set the ddns service name
s p ddns user:abilistest pwd:abilistest set user name and password
s p ip-1 ddns:yes enable DDNS for the resource ip-1
s p ip-1 ddns-fqdn:abilistest.dyndns.org set the FQDN for the resource ip-1
save conf save cthe configuration

On a working Abilis, a system restart is required to make the IP-5 resource running.

52.11. How to configure a Remote Access Server (RAS)

52.11.1. How to configure a RAS using IPSEC VPN server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ipsec Add the IPSEC resource.

or or

s act res:ipsec If the resource already exists, set it active.

s p ipsec act:yes Enable the IPSEC runtime functionalities.
a res:ike Add the IKE resource.

or or

s act res:ike If the resource already exists, set it active.

s p ike act:yes Enable the IKE runtime functionalities.
s p ip-3 ipsec:yes Enable the IPSEC functionality in the IP resource associate
to the WAN connection (e.g. IP-3).
Add an entry in the IKE Host and IKE Client tables for each
client that you want to enable.
a ike host:0 name:user_1 Add an entry in the IKE Host table.
s ike host:0 loc-ip:80.80.80.80 rem-ip:* Configure the local and remote IP addresses.
s ike host:0 auth:psk hash:md5 dh:modp1024 cipher:3des Configure the authentication type.

949
Draft HowTo - Networking Draft

s ike host:0 side:inside Configure NAT settings.

s ike host:0 id-type:ip ip:80.80.80.80 Configure the local ID.
s ike host:0 peer-id-type:ip peer-ip:192.168.200.1 Configure the remote ID.
a ike cli:0 name:user_1 Add an entry in the IKE Client table.
s ike cli:0 host-id:0 tunnel:yes Configure the Host ID and enable the tunnel mode.
s ike cli:0 net-rem:192.168.200.1/32 Configure the local and remote addresses and masks.
a ipr net:192.168.200.1/32 ip:3 Add a static route for remote host (if it necessary).
Repeat the previous commands for each client.
a ike psk:0 key:preshared_key id-type:anonymous Add the Preshared Key.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IPSEC and IKE resources running.

Caution
The IPSEC connection works ONLY if the LAN, where the PC client is connected to, is different from the
LAN of Abilis (e.g. in the previous case if the PC client IP address is belonging to the 192.168.1.0/24 the
IPSEC connection doesn't work!).

Tip
To configure IPSEC clients refer to Chapter 56, IPSEC clients.

52.11.2. How to configure a RAS using IPSEC VPN server with

iPHONE

950
Draft HowTo - Networking Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ipsec Add the IPSEC resource.

or or

s act res:ipsec If the resource already exists, set it active.

s p ipsec act:yes Enable the IPSEC runtime functionalities.
a res:ike Add the IKE resource.

or or

s act res:ike If the resource already exists, set it active.

s p ike act:yes Enable the IKE runtime functionalities.
s p ike nrty:5 Set the maximum number of packet retransmissions.
s p ip-3 ipsec:yes Enable the IPSEC functionality in the IP resource associate
to the WAN connection (e.g. IP-3).
Add an entry in the IKE Host and IKE Client tables for each
client that you want to enable.
a ike host:0 name:test Add an entry in the IKE Host table.
s ike host:0 loc-ip:80.80.80.80 rem-ip:* Configure the local and remote IP addresses.
s ike host:0 auth:psk hash:md5 dh:modp1024 cipher:3des Configure the authentication type.
s ike host:0 side:inside Configure NAT settings.

s ike host:0 xauth:server xauth-user:test xauth- Set host connection.

pwd:password
s ike host:0 mode-cfg:srv-request Set the type of mode.
s ike host:0 dpd-action:restart Set the ime interval of missing DPD replies after which peer
is declared dead.
a ike cli:0 name:test Add an entry in the IKE Client table.
s ike cli:0 host-id:0 tunnel:yes pfs:no Configure the Host ID, enable the tunnel mode and disable
Perfect Forward Secrecy
s ike cli:0 net-loc:0.0.0.0/0 net-rem:192.168.200.1/32 Configure the local and remote addresses and masks.
a ipr net:192.168.200.1/32 ip:3 Add a static route for remote host (if it necessary).
Repeat the previous commands for each client.
a ike psk:0 key:preshared_key id-type:anonymous Add the Preshared Key.
save conf Save the configuration.

951
Draft HowTo - Networking Draft

52.11.3. How to configure a RAS using PPPoE connections with an

Ethernet/WiFi network

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:poeac-1 Add a POEAC resource (e.g. POEAC-1).

s p poeac-1 act:yes Enable the POEAC-1 runtime functionalities.
s p poeac-1 ethres:eth-1 Configure the ETH100-1 as the POEAC-1 lower resource.
s p poeac-1 max-ipres:10 Configure the maximum number of clients.
s p poeac-1 acname:wlan descr:wlan_users Configure the name of the Access Concentrator and the
description of the POEAC-1 resource
Add an IP over PPP resource and an user in the Users Table
for each client that you want to enable.
a res:ip-101 subtype:ppp Add an “IP over PPP” resource (e.g. IP-101)
s p ip-101 lowres:poeac-1 Configure the POEAC-1 as the IP-101 lower resource.
s p ip-101 ipadd:192.168.101.1 Configure the PPPoE server IP address.
s p ip-101 neigh:192.168.101.11 Configure the PPPoE client IP address.
s p ip-101 servicename:user_1 Configure the PPPoE Service name.
s p ip-101 tcp-mss-clamp:yes Activate the TCP MSS clamping procedure.
s p ip-101 dns:provide Provide the DNS service to the client.
s p ip-101 local:none remote:chap Configure the local and remote authentication protocol.
s p ip-101 descr:user_1 Configure the description of the IP resource
a user:user_1 pwd:user_1 Add the user in the Users Table.
s user:user_1 ppp:yes ppp-res:ip-101 Enable the user to PPP service and associate the user to the
IP-101 resource.
Repeat the previous commands for each client.
s p iprtr PPP-DNS-PRI:62.94.0.1 PPP-DNS- Configure the DNS servers provided to the remote clients.
SEC:62.94.0.2
save conf Save the configuration.

On a working Abilis, a system restart is required to make the POEAC-1 and IP resources running.

Tip
Remember to configure NAT settings.

952
Draft HowTo - Networking Draft

Tip
To configure PPPoE clients refer to Chapter 57, PPPoE clients.

52.11.4. How to configure a RAS using ISDN network

Physical connections:

• Verify that an ISDN card (QPRIX, PB44X, BRI-HFC4, BRI-HFC8, BRIO) is installed in the Abilis. If the card is not
present, insert it in a free PCI slot.

• Connect the ISDN card to NT devices.

• The remote PC must be connected to an ISDN router or to a TA adapter able to generate ISDN calls.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

Add an “IP over PPP” resource for each client that you want
to enable.
a res:ip-201 subtype:ppp Add an “IP over PPP” resource (e.g. IP-201)
s p ip-201 lowres:ctislink Configure the CtiSlink as the lower resource.
s p ip-201 dial-in:yes dial-out:no Enable the incoming calls and disable the outgoing calls.
s p ip-201 cgi:01765432 Configure the calling number.
s p ip-201 ipadd:192.168.201.1 Configure the server IP address and mask.
s p ip-201 neigh:192.168.201.11 Configure the client IP address.
s p ip-201 username:provider_user Configure the login information.
password:provider_pwd
s p ip-201 tcp-mss-clamp:yes Activate the TCP MSS clamping procedure.
s p ip-201 dns:provide Provide the DNS service to the client.

953
Draft HowTo - Networking Draft

s p ip-201 local:none remote:chap Configure the local and remote authentication protocol.
s p ip-201 descr:user_1 Configure the description of the IP resource.
Repeat the previous commands for each client.
s p iprtr PPP-DNS-PRI:62.94.0.1 PPP-DNS- Configure the DNS servers provided to the remote clients.
SEC:62.94.0.2
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP resources running.

Tip
Remember to configure NAT settings.

52.12. How to configure an ISDN PPP Dial-UP connection

Physical connections:

• Verify that an ISDN card (QPRI2, PB44, BRI-HFC4, BRI-HFC8, BRIO) is installed in the Abilis. If the card is not
present, insert it in a free PCI slot.

• Connect the ISDN card to NT devices.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:ppp Add an “IP over PPP” resource (e.g. IP-5)

s p ip-5 lowres:ctislink Configure the CtiSlink as the lower resource.
s p ip-5 dial-in:no dial-out:yes Enable the outgoing calls and disable the incoming calls.
s p ip-5 nrty:30 rty:us Configure the number of ISDN calls retry.
s p ip-5 nrty3:nomax Configure the PPP authentication number retry.
s p ip-5 cdo:01765432456 Configure the called output number.
s p ip-5 username:provider_user password:provider_pwd Configure the login information.
s p ip-5 local:chap,pap remote:none Configure the local and remote authentication protocol.
s p ip-5 descr:ISDN_DIAL-UP_to_TELCO Configure the description of the IP resource.
save conf Save the configuration

On a working Abilis, a system restart is required to make the IP resources running.

Tip
Remember to configure NAT settings.

52.13. How to configure a VPN tunnel between two Abilis

The Abilis IP Tunnel (AIPT) is used to transport data and voice packets. The configuration varies depending on:

• both Abilis have a static public IP address;

• one Abilis has a dynamic public IP address or is placed behind a router doing NAT/PAT.

The AIPT tunnel supports two options:

• Backup over ISDN.

954
Draft HowTo - Networking Draft

• Double-Path.

Refer to Section 52.14, “How to configure a voice tunnel between two Abilis” to configure a tunnel for voice communication
only.

52.13.1. How to configure a VPN tunnel where both Abilis have a

static public IP address

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext Configure the EXTENDED operating mode.
s p ip-5 mask:255.255.255.0 neigh:192.168.2.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p ip-5 remipadd:81.81.81.81 remport:2105 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p ip-5 descr:VPN_to_Abilis_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext Configure the EXTENDED operating mode.
s p ip-5 mask:255.255.255.0 neigh:192.168.1.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.

955
Draft HowTo - Networking Draft

s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:81.81.81.81 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p ip-5 remipadd:80.80.80.80 remport:2105 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p ip-5 descr:VPN_to_Abilis_1 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

Tip
Remember to configure NAT settings.

52.13.2. How to configure a VPN tunnel where one Abilis has a

dynamic public IP address or is placed behind a router doing NAT/
PAT
The combination EXT-SERVER and EXT-CLIENT is used when one side (the server) has a static public IP address and
the other side (the client) has a dynamic public IP address (it could have also 2 Internet accesses) or is placed behind a router
doing NAT/PAT.

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext-server Configure the EXTENDED-SERVER operating mode.
s p ip-5 mask:255.255.255.0 neigh:192.168.2.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.

956
Draft HowTo - Networking Draft

s p ip-5 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP

pakets.
s p ip-5 remport:2105 cli-id:192.168.2.1 Configure the Remote port for incoming/outgoing UDP
packets and the Client identification IP address.
s p ip-5 descr:VPN_to_Abilis_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext-client Configure the EXTENDED-CLIENT operating mode.
s p ip-5 mask:255.255.255.0 neigh:192.168.1.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:out-ip id:192.168.2.1 Configure the Local IP address for incoming/outgoing UDP
pakets and the Identification IP address sent by the Client to
the Server.
s p ip-5 remipadd:80.80.80.80 remport:2105 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p ip-5 descr:VPN_to_Abilis_1 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

Tip
Remember to configure NAT settings.

52.13.3. How to configure a VPN tunnel with the “backup over ISDN”
option
With the “backup over ISDN” option, in case of failure of the permanent VPN connection, the Abilis tunnel is
instantaneously switched onto ISDN backup lines.

957
Draft HowTo - Networking Draft

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt-bck Add an “IP over IP (Abilis tunnel) with Abilis Back-up”
resource (e.g. IP-5).
s p ip-5 mode:ext Configure the EXTENDED operating mode.
s p ip-5 mask:255.255.255.0 neigh:192.168.2.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p ip-5 remipadd:81.81.81.81 remport:2105 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p ip-5 brty:us bnrty:30 btb:10 Configure the Retry law type, the maximum number of
consecutive calls and the Time base for delay between calls.
s p ip-5 sgi:abilis2-abilis1 sgo:abilis1-abilis2 Configure the input and output calling sub-addresses and
cdo:01765432 the output called number.
s p ip-5 descr:VPN_to_Abilis_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt-bck Add an “IP over IP (Abilis tunnel) with Abilis Back-up”
resource (e.g. IP-5).

958
Draft HowTo - Networking Draft

s p ip-5 mode:ext Configure the EXTENDED operating mode.

s p ip-5 mask:255.255.255.0 neigh:192.168.1.1 Configure the subnet mask and in the NEIGH parameter the
private IP address of the remote Abilis.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:81.81.81.81 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p ip-5 remipadd:80.80.80.80 remport:2105 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p ip-5 brty:us bnrty:30 btb:10 Configure the Retry law type, the maximum number of
consecutive calls and the Time base for delay between calls.
s p ip-5 sgi:abilis1-abilis2 sgo:abilis2-abilis1 Configure the input and output calling sub-addresses and
cdo:01234567 the output called number.
s p ip-5 descr:VPN_to_Abilis_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

Tip
Remember to configure NAT settings.

52.13.4. How to configure a VPN tunnel with the “double path”

option
With the “double path option” (also called “ART - Abilis Redundant Tunneling”), the same information is sent on two
different lines. The receiving Abilis discards the packet which arrives second (out-of sequence). The probability that the same
packet is lost on both links equals the product of the original probabilities. For example, two links with 10% failure rate (a
very high one!) ends up with 1%, which is normally negligible.

Tip
It is advisable to use ART ONLY with lines with the same speed. In case of lines with different speeds, the
packets are sent with the maximum speed of the slower line.

959
Draft HowTo - Networking Draft

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext Configure the EXTENDED operating mode.
s p ip-5 path:double Activate the Double Path.
s p ip-5 mask:255.255.255.0 neigh:192.168.2.1 Configure the subnet mask and the IP address of the
neighbour router.
s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:80.80.80.80 locipadd2:90.90.90.90 Configure the first and the second Local IP address for
incoming/outgoing UDP pakets.
s p ip-5 out-ip:auto out-ip2:4 Configure the first and the second Output IP resource.
s p ip-5 remipadd:81.81.81.81 remipadd2:91.91.91.91 Configure the first and the second Remote IP address and
remport:2105 port for incoming/outgoing UDP.
s p ip-5 descr:VPN_to_Abilis_2 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ip-5 subtype:aipt Add an “IP over IP (Abilis tunnel)” resource (e.g. IP-5).
s p ip-5 mode:ext Configure the EXTENDED operating mode.
s p ip-5 path:double Activate the Double Path.
s p ip-5 mask:255.255.255.0 neigh:192.168.1.1 Configure the subnet mask and the IP address of the
neighbour router.

960
Draft HowTo - Networking Draft

s p ip-5 frag:frf12 fragsize:800 Configure the link fragmentation type and the maximum
size of link frames fragments.
s p ip-5 lcr:data Activate the data encryption.
s p ip-5 locipadd:81.81.81.81 locipadd2:91.91.91.91 Configure the first and the second Local IP address for
incoming/outgoing UDP pakets.
s p ip-5 out-ip:auto out-ip2:4 Configure the first and the second Output IP resource.
s p ip-5 remipadd:80.80.80.80 remipadd2:90.90.90.90 Configure the first and the second Remote IP address and
remport:2105 port for incoming/outgoing UDP.
s p ip-5 descr:VPN_to_Abilis_1 Configure the description of the IP resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the IP-5 resource running.

Tip
Remember to configure NAT settings.

52.13.4.1. How to view extended statistics for each path

Enter into the Abilis control-program and type the following commands.

d se ip-5 path:1 Shows the statistics of the Aipt resource ip-5 about path
number 1 in extended mode.
d se ip-5 path:2 Shows the statistics of the Aipt resource ip-5 about path
number 2 in extended mode.

Refer to chapter Section 36.4.2, “Tunneling statistics” to view more examples.

52.14. How to configure a voice tunnel between two

Abilis
The Packet Voice tunnel (PV) is used to transport only voice packets. The configuration varies depending on:

• both Abilis have a static public IP address;

• one Abilis has a dynamic public IP address or is placed behind a router doing NAT/PAT.

The PV tunnel supports two options:

• Backup over ISDN.

• Double-Path.

To configure a tunnel for data and voice communication, refer to Section 52.13, “How to configure a VPN tunnel between
two Abilis”.

961
Draft HowTo - Networking Draft

52.14.1. How to configure a voice tunnel where both Abilis have a

static public IP address

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).
s p pv-1 mode:ext Configure the EXTENDED operating mode.
s p pv-1 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p pv-1 remipadd:81.81.81.81 remport:3101 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p pv-1 descr:PV_to_Abilis_2 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).
s p pv-1 mode:ext Configure the EXTENDED operating mode.
s p pv-1 locipadd:81.81.81.81 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p pv-1 remipadd:80.80.80.80 remport:3101 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p pv-1 descr:PV_to_Abilis_1 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

962
Draft HowTo - Networking Draft

52.14.2. How to configure a voice tunnel where one Abilis has a

dynamic public IP address or is placed behind a router doing NAT/
PAT
The combination EXT-SERVER and EXT-CLIENT is used when one side (the server) has a static public IP address and
the other side (the client) has a dynamic public IP address (it could have also 2 Internet accesses) or is placed behind a router
doing NAT/PAT.

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).
s p pv-1 mode:ext-server Configure the EXTENDED-SERVER operating mode.
s p pv-1 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p pv-1 remport:3101 cli-id:192.168.2.1 Configure the Remote port for incoming/outgoing UDP
packets and the Client identification IP address.
s p pv-1 descr:PV_to_Abilis_2 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).
s p pv-1 mode:ext-client Configure the EXTENDED-CLIENT operating mode.
s p pv-1 locipadd:out-ip id:192.168.2.1 Configure the Local IP address for incoming/outgoing UDP
pakets and the Identification IP address sent by the Client to
the Server.
s p pv-1 remipadd:80.80.80.80 remport:3101 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p pv-1 descr:PV_to_Abilis_1 Configure the description of the PV resource.

963
Draft HowTo - Networking Draft

save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

52.14.3. How to configure a voice tunnel with the “backup over

ISDN” option
With the “backup over ISDN” option, in case of failure of the permanent VPN connection, the Abilis tunnel is
instantaneously switched onto ISDN backup lines.

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip-bck Add a “PV over IP (Abilis tunnel) with Abilis Backu-up”
resource (e.g. PV-1).
s p pv-1 mode:ext Configure the EXTENDED operating mode.
s p pv-1 locipadd:80.80.80.80 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p pv-1 remipadd:81.81.81.81 remport:3101 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p pv-1 brty:us bnrty:30 btb:10 Configure the Retry law type, the maximum number of
consecutive calls and the Time base for delay between calls.
s p pv-1 sgi:abilis2-abilis1 sgo:abilis1-abilis2 Configure the input and output calling sub-addresses and
cdo:01765432 the output called number.
s p pv-1 descr:PV_to_Abilis_2 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

964
Draft HowTo - Networking Draft

a res:pv-1 subtype:ip-bck Add a “PV over IP (Abilis tunnel) with Abilis Backu-up”
resource (e.g. PV-1).
s p pv-1 mode:ext Configure the EXTENDED operating mode.
s p pv-1 locipadd:81.81.81.81 Configure the Local IP address for incoming/outgoing UDP
pakets.
s p pv-1 remipadd:80.80.80.80 remport:3101 Configure the Remote IP address and port for incoming/
outgoing UDP packets.
s p pv-1 brty:us bnrty:30 btb:10 Configure the Retry law type, the maximum number of
consecutive calls and the Time base for delay between calls.
s p pv-1 sgi:abilis1-abilis2 sgo:abilis2-abilis1 Configure the input and output calling sub-addresses and
cdo:01234567 the output called number.
s p pv-1 descr:PV_to_Abilis_2 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

52.14.4. How to configure a voice tunnel with the “double-path”

option
With the “double-path option” (also called “ART - Abilis Redundant Tunneling”), the same information is sent on two
different lines. The receiving Abilis discards the packet which arrives second (out-of sequence). The probability that the same
packet is lost on both links equals the product of the original probabilities. For example, two links with 10% failure rate (a
very high one!) ends up with 1%, which is normally negligible.

Tip
It is advisable to use ART ONLY with lines with the same speed. In case of lines with different speeds, the
packets are sent with the maximum speed of the slower line.

• ABILIS 1:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).

965
Draft HowTo - Networking Draft

s p pv-1 mode:ext Configure the EXTENDED operating mode.

s p pv-1 path:double Activate the Double Path.
s p pv-1 locipadd:80.80.80.80 locipadd2:90.90.90.90 Configure the first and the second Local IP address for
incoming/outgoing UDP pakets.
s p pv-1 out-ip:auto out-ip2:4 Configure the first and the second Output IP resource.
s p pv-1 remipadd:81.81.81.81 remipadd2:91.91.91.91 Configure the first and the second Remote IP address and
remport:3101 port for incoming/outgoing UDP.
s p pv-1 descr:PV_to_Abilis_2 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

• ABILIS 2:

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:pv-1 subtype:ip Add a “PV over IP (Abilis tunnel)” resource (e.g. PV-1).
s p pv-1 mode:ext Configure the EXTENDED operating mode.
s p pv-1 path:double Activate the Double Path.
s p pv-1 locipadd:81.81.81.81 locipadd2:91.91.91.91 Configure the first and the second Local IP address for
incoming/outgoing UDP pakets.
s p pv-1 out-ip:auto out-ip2:4 Configure the first and the second Output IP resource.
s p pv-1 remipadd:80.80.80.80 remipadd2:90.90.90.90 Configure the first and the second Remote IP address and
remport:3101 port for incoming/outgoing UDP.
s p pv-1 descr:PV_to_Abilis_1 Configure the description of the PV resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the PV-1 resource running.

52.14.4.1. How to view extended statistics for each path

Enter into the Abilis control-program and type the following commands.

d se pv-1 path:1 Shows the statistics of the Aipt resource ip-5 about path
number 1 in extended mode.
d se pv-1 path:2 Shows the statistics of the Aipt resource ip-5 about path
number 2 in extended mode.

Refer to chapter Section 36.4.2, “Tunneling statistics” to view more examples.

52.15. How to activate the DHCP resource

The DHCP resource can work in relay or server mode.

966
Draft HowTo - Networking Draft

52.15.1. How to activate the DHCP in relay mode

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:dhcp Add the DHCP resource.

or or

s act res:dhcp If the resource already exists, set it active.

s p dhcp act:yes Enable the DHCP runtime functionalities.
s p dhcp mode:relay Activate the RELAY mode.
s p dhcp srv:192.168.1.250 Configure the DHCP Server to which requests must be
forwarded.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the DHCP resource running.

967
Draft HowTo - Networking Draft

52.15.2. How to activate the DHCP in server mode

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:dhcp Add the DHCP resource.

or or

s act res:dhcp If the resource already exists, set it active.

s p dhcp act:yes Enable the DHCP runtime functionalities.
s p dhcp mode:server Activate the SERVER mode.
a dhcp prof:1 name:LAN_1 Add an entry in the DHCP profile table.
s dhcp prof:1 nb-node-type:b Configure the Netbios node type.
s dhcp prof:1 gw1:192.168.1.1 Configure the first gateway.
s dhcp prof:1 dns1:192.168.1.210 dns2:192.168.1.211 Configure the DNS servers.
s dhcp prof:1 smtp:192.168.1.220 pop3:192.168.1.220 Configure the SMTP and the POP3 servers.
a dhcp lan:1 name:LAN_1 prof:1 Add an entry in the DHCP subnet table and associate it to a
profile.
s dhcp lan:1 net:192.168.1.0 mask:255.255.255.0 Configure the Network address and the subnet mask.
s dhcp lan:1 pool1:192.168.1.10:192.168.1.50 Configure the first pool of addresses distribuited by DHCP.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the DHCP resource running.

968
Draft HowTo - Networking Draft

52.15.3. How to activate the DHCP in client mode

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:dhcpc Add the DHCPC resource.

or or

s act res:dhcpc If the resource already exists, set it active.

s p dhcpc act:yes Set active the resource.
s p ip-2 ipadd:dhcp Set the dhcp client active for ip-2 resource
save conf Save the configuration

On a working Abilis, a system restart is required to make the DHCPC resource running.

Tip
Type the command d d ip-2 to verify the acquired ip address (CUR-IPADD parameter).

Note
Using the above configuration, Abilis retrieves ip address, default gateway and dns server through DHCP.
Refer to chapter Section 25.5.3, “Example of configuration” or read the following example to learn how to
retrieve only ip address configuring parameters DHCP-GW, DHCP-GW-AD and DHCP-DNS.

52.15.3.1. How to retrieve only ip address

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

969
Draft HowTo - Networking Draft

a res:dhcpc Add the DHCPC resource.

or or

s act res:dhcpc If the resource already exists, set it active.

s p dhcpc act:yes Set active the resource.
s p ip-2 ipadd:dhcp dhcp-gw:no dhcp-dns:no Set the dhcp client active for ip-2 resource
save conf Save the configuration

On a working Abilis, a system restart is required to make the DHCPC resource running.

Tip
Type the command d d ip-2 to verify the acquired ip address (CUR-IPADD parameter).

52.16. How to activate the FTP server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ftp Add the FTP resource.

or or

s act res:ftp If the resource already exists, set it active.

s p ftp act:yes Enable the FTP runtime functionalities.
Repeat the following commands for each user that you want
to enable to FTP.
a user:ftpuser pwd:ftpuser ftp:yes Add the user ftpuser and enable it to FTP.
s user:ftpuser ftp-homedir:/test1/ Create the ftpuser Home directory.
a ftp path:/test1/ phys-path:c:\usr\pub\test1\ Create the association between the virtual and physical path
of the ftpuser Home directory.
a ftp rights path:/test1/ user:ftpuser file:rwdn dir:lcdn Give to ftpuser the access rights on its Home directory.
recur:yes prot:plain,ssl
a ftp rights path:/usr/ user:ftpuser file:r-w-d-n dir:l-c-d-n Give to ftpuser read-only rights on directory /usr/ and
recur:yes prot:plain,ssl its subdirectories.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the FTP resource running.

52.17. How to activate the HTTP server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:http Add the HTTP resource.

or or

s act res:http If the resource already exists, set it active.

s p http act:yes Enable the HTTP runtime functionalities.
Repeat the following commands for each user that you want
to enable to HTTP.
a user:httpuser pwd:httpuser http:yes Add the user httpuser and enable it to HTTP.
a http rights path:/sys/trfa/ user:httpuser Enable the httpuser to access the “IP traffic analyzer”
link.

970
Draft HowTo - Networking Draft

a http rights path:/sys/opc/ user:httpuser Enable the httpuser to access the “Operator Panel
Control” link.
a http rights path:/sys/sms/ user:httpuser Enable the httpuser to access the “SMS Gateway” link.
a http rights path:/sys/cp/ user:httpuser Enable the httpuser to access the “Control Port” link.
a http rights path:/sys/admin/ user:httpuser recur:no Enable the httpuser to access the “Configuration
information” link.
a http rights path:/sys/admin/groups/ user:httpuser Enable the httpuser to access the “Groups
administration” link.
a http rights path:/sys/advuser/ user:httpuser Enable the httpuser to access the “Advanced User
activities” link.
a http rights path:/sys/admin/users/ user:httpuser Enable the httpuser to access the “Users administration”
link.
a http rights path:/sys/admin/lists/ user:httpuser Enable the httpuser to access the “Lists administration”
link.
a http rights path:/sys/admin/disa/ user:httpuser Enable the httpuser to access the “DISA administration”
link.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the HTTP resource running.

52.17.1. How to activate the HTTP over SSL server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

Activate the HTTP server.

a res:ssl Add the SSL resource.

or or

s act res:ssl If the resource already exists, set it active.

s p ssl act:yes Enable the SSL runtime functionalities.
s p http act-s:yes Enable the HTTPS runtime functionalities.
s p http sesnum-s:12 Configure the number of HTTPS sessions
save conf Save the configuration.

On a working Abilis, a system restart is required to make the SSL resource running.

Note
Verify that the SSL protocol is enabled in the Users and HTTP Virtual Paths Access Rights tables.

[17:53:34] ABILIS_CPX:d user:httpuser

Parameter: | Value:
---------------+---------------------------------------------------------------
USER: httpuser
ALIAS: httpuser
ID: 4 <Read Only>
PWD: *******
ACT: YES
GROUP:
CTIP: #
CLUS: #
OPC-ROLE: USER
OPC-VIEW: *

971
Draft HowTo - Networking Draft

OPC-MONITOR: NONE
HTTP: YES
HTTP-PROT: PLAIN,SSL
-------------------------------------------------------------------------------

[15:12:54] ABILIS_CPX:d http rights

-------------------------------------------------------------------------------
ID: PATH:
USER: FILE: DIR: RECUR: PROT:
------------------------------------------------------------------------------
3 /sys/opc/
httpuser r--- l--- YES PLAIN,SSL
-------------------------------------------------------------------------------
...

52.18. How to activate the TRFA resource

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:trfa Add the TRFA resource.

or or

s act res:trfa If the resource already exists, set it active.

s p trfa act:yes Enable the TRFA runtime functionalities.
s p trfa bak:no Disable the file backup creation.
Activate the HTTP server and enable an user to access the
“IP traffic analyzer” link.
Repeat the following commands for each IP resource for
which you want to activate the TRFA.
s p ip-n trfa:yes Enable the traffic analysis.
s p ip-n trfa-mode:ip Select traffic analysis mode.
s p ip-n trfa-side:local TRFA-SIDE:LOCAL in a LAN, AIPT (AIPT-BCK)
resource.
or
or
s p ip-n trfa-side:remote trfa-ipadd:*
TRFA:OUTSIDE in a PPP or DL (DL-BCK) resource.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the TRFA resource running.

Tip
To enable the “TOP10 IP” feature, you must configure the TRFA-MODE parameter to IP or IP-PROT (e.g.
s p ip-n trfa-mode:ip-prot).

Tip
For the description of the TRFA web pages refer to Section 40.3.3, “Using HTTP for showing TRFA
statistics”.

972
Draft HowTo - Networking Draft

52.19. How to use state detection of IP interfaces

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p ip-2 state-detect:ping Set the state detecion of ip-2 resource to PING

s p ip-2 p-dst1:62.94.0.1 p-dst2:62.94.0.2 Set the external servers to ping.
s p ip-2 p-gw:192.168.2.254 Set the gateway to use for ping
save conf Save the configuration

On a working Abilis, an initialization of the ip resource is required (init res:ip-2).

52.20. How to activate the SNTP resource

The SNTP resource can work as client or server.

52.20.1. How to activate the SNTP client

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:sntp Add the SNTP resource.

or or

s act res:sntp If the resource already exists, set it active.

s p sntp cliact:yes Enable the SNTP client runtime functionalities.
s p sntp host-1:129.132.2.21 srcadd:out-ip Configure the SNTP host address and the Source IP address
for client requests.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the SNTP resource running.

973
Draft HowTo - Networking Draft

52.20.2. How to activate the SNTP server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

Activate the SNTP client.

s p sntp servact:yes Enable the SNTP server runtime functionalities.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the SNTP resource running.

52.21. How to activate the SNMP agent

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:snmp Add the SNMP resource.

or or

s act res:snmp If the resource already exists, set it active.

s p snmp act:yes Enable the SNMP runtime functionalities.
s p snmp ipsrc:192.168.1.50 Configure the accepted source IP address.
s p snmp trap:yes Enable SNMP traps generation.
s p snmp trapdest:192.168.1.50 Configure the Traps destination IP address.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the SNMP resource running.

974
Draft HowTo - Networking Draft

52.22. How to publish the users on the Abilis LDAP

server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ldap Add the LDAP resource.

or or

s act res:ldap If the resource already exists, set it active.

s p ldap act:yes Enable the LDAP runtime functionalities.
a user:test act:yes pwd:test ldap:yes Create a new user test with an LDAP account.
a http rights id:2 user:test file:r dir:l Allow the user test to access LDAP web.
s user:frank ldap-user-sync:yes ldap-number:ctiiax Publish the IAX user frank.
s user:anne ldap-user-sync:yes ldap-number:ctisip Publish the SIP user anne.
s user:george ldap-user-sync:yes ldap-number:ctip Publish the user george owning the CTIP 101.
ctip:101
s user:jack ldap-user-sync:yes ldap-number:clus Publish the user jack owning the CLUSTER myclus.
clus:myclus
s user:frank iax-ldap-num:02'IAX-NUMBER' Apply a macro on the published number of IAX user frank.
s user:anne sip-ldap-num:'SIP-NUMBER.s2' Apply a macro on the published number of SIP user anne.
s ctip:101 ldap-num:02'NUM' Apply a macro on the published number of CTIP 101.
s cticl clus:myclus ldap-num:'NUM'123 Apply a macro on the published number of CLUSTER
myclus.
init res:ctisys Initialize the CTI system.
save conf Save the configuration.

On a working Abilis, a system restart is required to let the LDAP resource running if it was not running previously.

Tip
The published users populate the system address book [580], to hide other address books type a ldap rights
id:1 user:test grants:-r and a ldap rights id:2 user:test grants:-r.

975
Draft HowTo - Networking Draft

Tip
For the description of the LDAP web pages refer to Section 41.4.1, “Web Interface”.

976
Draft Draft

Chapter 53. HowTo - CTI system

Marco Bellesia
Luigi Demuro
Alfredo Sorbello

Table of Contents
53.1. How to configure ISDN ports to connect PBX or ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
53.2. How to configure FXS (POTS) ports for analog telephones or fax machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
53.3. How to program a group of telephone lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
53.4. How to configure fax modem relay parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
53.5. How to create a VoIP tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
53.6. How to register an IAX telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
53.7. How to register a SIP telephone onto Abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
53.7.1. How to register a SIP telephone onto Abilis when the telephone is behind a NAT . . . . . . . . . . . . . . . . . . . . . . . . . 985
53.8. How to register Abilis as a client of Asterisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
53.9. How to register Abilis as a client of a SIP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.10. How to configure the speedlimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
53.11. How to configure opc to collect call information from a remote abilis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.12. How to activate the Accounting service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
53.13. How to enable pickup service for a POTS/ISDN port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.14. How to enable pickup service for a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
53.15. How to configure CTIDISA to implement a responder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.1. Implementing a responder using MODE:INTRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.2. Implementing a responder using MODE:DISA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
53.15.3. Getting a call on phones while the responder is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
53.16. How to configure Last Calling Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
53.17. How to configure DATA CALL BACK using an UMTS Key, calling an ISDN number . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
53.18. How to configure CTISMS to send sms using the web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19. How to configure CTISMS to send sms via emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
53.19.1. Instructions to send emails through sms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
53.19.2. Instructions to send sms through emails using a client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997

53.1. How to configure ISDN ports to connect PBX or

ISDN lines
Physical connections:

• Verify that an ISDN card (QPRIX, PB44X, BRI-HFC4, BRI-HFC8, BRIO) is installed in the Abilis. If the card is not
present, insert it in a free PCI slot.

• Connect the ISDN card to NT devices and to PBX.

The basic parameters that must be configured are:

• side:NT (it the CTI Port is connected to PBX) or TE (if the CTI Port is connected to ISDN lines);

• line:PP (if the ISDN line is Point-to-Point) or MP (if the ISDN line is Point-to-Multipoint).

Let's see how to configure a BRI card: in the standard configuration, the CTI Ports 31 and 32 are configured towards the
PBX, while the CTI Ports 33 and 34 towards ISDN lines.

977
Draft HowTo - CTI system Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:bri4-1 Add an ISDN device (e.g. BRI4-1).

s ctip:31 side:nt line:pp descr:to_PBX Configure the port behaviour, the line type (PP or MP) and
the description of the CTI Port.
s ctip:32 side:nt line:pp descr:to_PBX Configure the port behaviour, the line type (PP or MP) and
the description of the CTI Port.
s ctip:33 side:te line:pp descr:to_ISDN_line_(PP) Configure the port behaviour, the line type (PP or MP) and
the description of the CTI Port.
s ctip:34 side:te line:pp descr:to_ISDN_line_(PP) Configure the port behaviour, the line type (PP or MP) and
the description of the CTI Port.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the BRI4-1 device and the CTI Ports running.

Tip
To know if the ISDN line is PP or MP, display the statistics of the CTI Ports and verify the DISC parameter.
If the vaule is different from zero, the line is MP.

[10:00:21] ABILIS_CPX:d s ctip:33

CTIP:33 ----------------------------------------------------------------------
to_ISDN_line_(MP)

978
Draft HowTo - CTI system Draft

--- Cleared 16 days 22:07:18 ago, on 18/03/2008 at 11:03:49 ------------

Layer 3 Q.931
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 171|SUCC-CALL | 10| 3|
TIME-CALL | 604753| 1149|
------------------------------------------------------------------------
Layer 2 Sapi 16 (X.25) TEI:10
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 0|T200-UP | | 0|
REP | 0| 0|INFO | 0| 0|
UI | 0| 0|RR | 0| 0|
RNR | 0| 0|REJ | 0| 0|
FRMR | 0| 0|SABME | 0| 0|
UA | 0| 0|DISC | 0| 0|
DM | 0| 0|N200-OVER | | 0|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 2 Sapi 0 (Q.931) TEI:ALL
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
T200-DN | | 38|T200-UP | | 38|
REP | 0| 0|INFO | 544| 435|
UI | 60| 0|RR | 706| 986|
RNR | 0| 0|REJ | 0| 0|
FRMR | 0| 0|SABME | 7| 222|
UA | 191| 189|DISC | 182| 3|
DM | 3| 0|N200-OVER | | 9|
SHORT | 0| |LONG | 0| |
UNK-SAPI | 0| |BAD-FRM | 0| |
------------------------------------------------------------------------
Layer 1 B-Channels (HDLC)
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 9108202| 3330716|FRM | 113593| 108517|
CHR-D | 7418673| 1657684|FRM-D | 19114| 14961|
CHR-V | 1685249| 1668689|FRM-V | 93765| 92831|
CHR-C | 4280| 4343|FRM-C | 714| 725|
ERRORS | 873| 0|
------------------------------------------------------------------------
Layer 1 D-Channel
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 19561| 14378|FRM | 2208| 1848|
CHR-D | 19561| 14378|FRM-D | 2208| 1848|
ERRORS | 354| 0|
------------------------------------------------------------------------
Layer 1 alarms
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SLIPS | 79| N/A|LINE-DOWN | 449| |
------------------------------------------------------------------------

53.2. How to configure FXS (POTS) ports for analog

telephones or fax machines
Physical connections:

• Verify that a POTS and an ISDN card (QPRIX, PB44X, BRI-HFC4, BRI-HFC8,) is installed in the Abilis. If the cards are
not present, insert them in a free PCI slots and connect them with the H.100 bus.

Warning
The POTS card must be connected to the internal power supplier.

979
Draft HowTo - CTI system Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:pots-1 Add a POTS device (e.g. POTS-1).

Repeat the same command for each CTI POTS Port.
s ctip:101 num:21 descr:technician_1 Configure the phone number assigned to the port and the
description.
s ctip:102 num:35 descr:fax Configure the phone number assigned to the port and the
description.
s ctip:103 num:24 descr:technician_2 Configure the phone number assigned to the port and the
description.
s ctip:104 num:16 descr:administration_1 Configure the phone number assigned to the port and the
description.
.. ..
save conf Save the configuration.

On a working Abilis, a system restart is required to make the POTS-1 device and the CTI Ports running.

53.3. How to program a group of telephone lines

Let's see how to create the groups of telephone lines shown in the following scheme.

980
Draft HowTo - CTI system Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a ctig id:1 p1:31 p2:32 descr:to_PBX Add the CTI Group with ID:1 and assign it the CTI Ports 31
and 32.
a ctig id:2 p1:33 p2:34 descr:to_ISDN_lines Add the CTI Group with ID:2 and assign it the CTI Ports 33
and 33.
a ctig id:3 p1:101 p2:103 p4:108 descr:technical_office Add the CTI Group with ID:3 and assign it the CTI Ports
101, 103 and 108.
a ctig id:4 p1:105 p2:106 p4:113 Add the CTI Group with ID:3 and assign it the CTI Ports
descr:administration_office 105, 106 and 113.
save conf Save the configuration.

On a working Abilis, you must initialize the CTI Routings: init ctir.

53.4. How to configure fax modem relay parameter

Physical connections:

• Verify that a POTS card is installed in the Abilis. If the card is not present, insert it in a free PCI slot.

Warning
The POTS card must be connected to the internal power supplier.

981
Draft HowTo - CTI system Draft

Refer to chapter Section 53.2, “How to configure FXS (POTS) ports for analog telephones or fax machines” to know more
about the configuration of POTS ports.

Assumptions:

• the cluster clus1 is already configured

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p ctisys fm-relay:no Set the fax modem relay parameter to no for the ctisys
resource
a ctir pr:1 type:ctov sr:clus1 poo:pbx cdi:088888 cdo:35 add a ctir rule to route a call incoming from 088888 toward
fmrly:yes the fax. The parameter fmrly is enabled only for this routing.
save conf save the configuration

On a working Abilis, you must initialize the CTISYS resource: init ctisys.

Tip
Refer to chapter Section 42.12, “FAX Relay with Abilis” to know more about the fm-relay parameter.

53.5. How to create a VoIP tunnel

A VoIP tunnel is based on the following resources:

• CTICL (CTI CLuster): it identifies a connection, used to transport compressed phone calls, between two Abilis.

• CTIL (CTI Link): it associates the CTI CLuster to a PV or AIPT resource.

Let's see how to create the VoIP tunnel shown in the following scheme.

982
Draft HowTo - CTI system Draft

• ABILIS 1

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a cticl clus:Abilis2 num:05555667701 descr:to_Abilis_2 Add an CTI CLuster and configure the number and the
description.
a ctil id:1 res:pv-1 clus:Abilis2 Add an CTI Link and associate the resource to the cluster.
save conf Save the configuration.

On a working Abilis, you must initialize the CTISYS resource: init ctisys.

• ABILIS 2

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a cticl clus:Abilis1 num:0222334401 descr:to_Abilis_1 Add an CTI CLuster and configure the number and the
description.
a ctil id:1 res:pv-1 clus:Abilis1 Add an CTI Link and associate the resource to the cluster.
save conf Save the configuration.

On a working Abilis, you must initialize the CTISYS resource: init ctisys.

53.6. How to register an IAX telephone onto Abilis

The IAX telephone can be an IP phone or a softphone running on a PC. It can be registered in the Abilis private or public
side.

983
Draft HowTo - CTI system Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctiiax Add the CTIIAX resource.

or or

s act res:ctiiax If the resource already exists, set it active.

s p ctiiax act:yes Enable the CTIIAX runtime functionalities.
a user:iax_phone pwd:iax_phone iax:yes Add the username and password associated to the IAX
telephone and enable it to IAX protocol.
s user:iax_phone iax-number:61 Configure the IAX telephone number.
s user:iax_phone iax-maxses-bid:4 Configure the maximum number of IAX bidirectional
sessions.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the CTIIAX resource running.

Note
The previous configuration can be applied also when Asterisk must register itself onto Abilis.

Tip
For the softphones configuration refer to Chapter 58, Softphones.

53.7. How to register a SIP telephone onto Abilis

The SIP telephone can be an IP phone or a softphone running on a PC. It can be registered in the Abilis private or public side.

The configuration varies depending on the telephone is behind a NAT.

984
Draft HowTo - CTI system Draft

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctisip Add the CTISIP resource.

or or

s act res:ctisip If the resource already exists, set it active.

s p ctisip act:yes Enable the CTISIP runtime functionalities.
a user:sip_phone pwd:sip_phone sip:yes Add the username and password associated to the SIP
telephone and enable it to SIP protocol.
s user:sip_phone sip-number:61 Configure the SIP telephone number.
s user:sip_phone sip-maxses-bid:4 Configure the maximum number of SIP bidirectional
sessions.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the CTISIP resource running.

Note
It is possible to specify a FQDN in the DOMAIN parameter of the CTISIP resource. If the SIP user uses a
local domain different from the one set in the CTISIP resource, you need to specify it in the User parameter
SIP-DOMAIN. Usually you need to do it in this way when the Abilis has a public domain and the user need
to access to it via the local area network.

Note
The previous configuration can be applied also when a SIP Proxy must register itself onto Abilis. In this
case the proxy is a “normal” user like a SIP phone but the SIP-TYPE parameter must be set up to LOCAL-
PEER (e.g. s user:sip_proxy sip-type:local-peer).

Tip
For the softphones configuration refer to Chapter 58, Softphones.

53.7.1. How to register a SIP telephone onto Abilis when the

telephone is behind a NAT
Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

985
Draft HowTo - CTI system Draft

a res:ctisip Add the CTISIP resource.

or or

s act res:ctisip If the resource already exists, set it active.

s p ctisip act:yes Enable the CTISIP runtime functionalities.
a user:sip_phone pwd:sip_phone sip:yes Add the username and password associated to the SIP
telephone and enable it to SIP protocol.
s user:sip_phone sip-number:61 Configure the SIP telephone number.
s user:sip_phone sip-maxses-bid:4 Configure the maximum number of SIP bidirectional
sessions.
s user:sip_phone sip-remote-nat:strict Configure the NAT trasversal method.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the CTISIP resource running.

Note
Users which are registered onto Abilis and that stays behind the same NAT, i.e. that presents themselves to
the Abilis with the same IP address, can be configured (with SIP-CPO:YES) to exchange RTP directly each
other, without transiting through the Abilis. In such a situation, if either puts on-hold, the other will receive
RTP stream with the hold tone directly from the Abilis.

Note
It is possible to specify a FQDN in the DOMAIN parameter of the CTISIP resource. If the SIP user uses a
local domain different from the one set in the CTISIP resource, you need to specify it in the User parameter
SIP-DOMAIN. Usually you need to do it in this way when the Abilis has a public domain and the user need
to access to it via the local area network.

Note
The previous configuration can be applied also when a SIP Proxy must register itself onto Abilis. In this
case the proxy is a “normal” user like a SIP phone but the SIP-TYPE parameter must be set up to LOCAL-
PEER (e.g. s user:sip_proxy sip-type:local-peer).

Tip
For the softphones configuration refer to Chapter 58, Softphones.

986
Draft HowTo - CTI system Draft

53.8. How to register Abilis as a client of Asterisk

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctiiax Add the CTIIAX resource.

or or

s act res:ctiiax If the resource already exists, set it active.

s p ctiiax act:yes Enable the CTIIAX runtime functionalities.
s p ctiiax srcadd:192.168.1.1 If Asterisk is placed in the Abilis LAN.

or or

s p ctiiax srcadd:out-ip If Asterisk is placed in Internet.

a user:asterisk pwd:swordfish iax:yes Add the username and password associated to Asterisk and
enable it to IAX protocol.
s user:asterisk iax-host:192.168.1.31 Configure the Asterisk IP address.
s user:asterisk iax-number:* Configure the Asterisk IAX number.
s user:asterisk iax-maxses-bid:10 Configure the maximum number of IAX bidirectional
sessions.
s user:asterisk iax-trunk:yes Enable the trunking.
s user:asterisk iax-rem-reg:yes iax-rem-auth:md5 Enable the registration of Abilis onto Asterisk and configure
the authentication method.
s user:asterisk iax-rem-user:abilis iax-rem- Configure the username and password used by Abilis to
pass:swordfish register itself onto Asterisk.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the CTIIAX resource running.

987
Draft HowTo - CTI system Draft

53.9. How to register Abilis as a client of a SIP server

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctisip Add the CTISIP resource.

or or

s act res:ctisip If the resource already exists, set it active.

s p ctisip act:yes Enable the CTISIP runtime functionalities.
s p ctisip srcadd:192.168.1.1 If the SIP Proxy is placed in the Abilis LAN.

or or

s p ctisip srcadd:out-ip If the SIP Proxy is placed in Internet.

a user:sip_proxy pwd:swordfish sip:yes Add the username and password associated to the SIP Proxy
and enable it to SIP protocol.
s user:sip_proxy sip-type:server Configure the SIP type to SERVER.
s user:sip_proxy sip-domain:voip.it Configure the domain of the called SIP UA server in
outgoing calls.
s user:sip_proxy sip-host:100.100.100.100 Configure the SIP Proxy IP address.
s user:sip_proxy sip-number:* Configure the SIP telephone number.
s user:sip_proxy sip-maxses-bid:10 Configure the maximum number of SIP bidirectional
sessions.
s user:sip_proxy sip-rem-reg:yes Enable the registration of Abilis onto the SIP Proxy.
s user:sip_proxy sip-rem-user:abilis sip-rem- Configure the username and password used by Abilis to
pass:swordfish register itself onto the SIP Proxy.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the CTISIP resource running.

53.10. How to configure the speedlimit

Speedlimit is a feature that allows IPRTR to reduce the rate of its outgoing datagrams on a specific IP resource. Main usage
is to reduce speed to safe values in presence of VOICE packets, while leaving full speed to data transfers when voice is not
present.

988
Draft HowTo - CTI system Draft

The speedlimit can be activated setting the OUTSPL parameter to YES in the IP resources. The maximum speed is set in the
OUTSP parameter. Generally this parameter must be set to a value slightly lower than the maximum speed in upload of the
ADSL/HDSL line (e.g.: if the ADSL line has a maximum speed of 256 Kbit/s the OUTSP parameter must be set to 240).

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s p ip-3 outspl:yes outsp:240 Activate the Output Speedlimit and configure the speed
limitation value.
s p iprtr acl:ext cos:enabled cosbalance:yes Configure the Access List activation mode to EXT, enable
the Class-Of-Service management and the Class-Of-Service
Balancing.
a ipacl pr:0 type:permit ipcos:high tos-in:*-d prot:udp Add the standard IPACL that assigns high priority to voice
sip:int sa:* da:* spo:* dpo:* packets.
save conf Save the configuration.

On a working Abilis, you must initialize the IP-3 (init res:ip-3) and the IPRTR resources (init res:iprtr). The changes on
IPACL table are immediately active.

53.11. How to configure opc to collect call information

from a remote abilis
Assumptions:

• the OPC resource is already active on both local and remote abilis

• the user of the remote abilis can access the remote OPC (in the example login:admin, password: admin)

Enter into the local Abilis control-program or open the configuration file with the Console configurator and type the
following commands.

s p opc maxremotes:5 set the max number of remote abilis to monitor

s p opc rem:0 abilisid:test configure the abilisid of the remote abilis
s p opc rem:0 server:192.168.1.150 configure the ip address of the remote abilis
s p opc rem:0 login:admin password:admin set login and password to access the remote abilis opc
s p opc rem:0 enabled:yes enable the access the remote abilis opc
save conf save the configuration

On a working Abilis, you must initialize the OPC resource: init res:opc.

53.12. How to activate the Accounting service

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

989
Draft HowTo - CTI system Draft

a res:acnt Add the ACNT resource.

or or

s act res:acnt If the resource already exists, set it active.

s p acnt act:yes Enable the ACNT runtime functionalities.
save conf Save the configuration.

On a working Abilis, a system restart is required to make the ACNT resource running.

Tip
For the installation and configuration of the CPX Accounting software refer to Section 55.1, “CPX
accounting software”.

53.13. How to enable pickup service for a POTS/ISDN

port
The first step is to follow the instructions in the chapter How to configure FXS (POTS) ports for analog telephones or fax
machines, in order to verify physical connections and to configure the POTS device.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s ctip:101 ss:yes Enable supplementary services (ss) accessible through “*” as

first digit in called number for the port ctip 101
s ctip:101 ss-pickup:any Set the pickup permission to any call.
init res:ctisys Initialize the CTISYS resource.
save conf Save the configuration.

Tip
The parameter ss-pickup can be set to: NO to disable pickup, ANY to pickup any call or GROUP to pickup
only calls belonging to its own group (the parameter PICKUP of the group must be equal to YES).

Tip
Refer to chapter Section 53.3, “How to program a group of telephone lines” to know how to configure a
group of phones.

53.14. How to enable pickup service for a SIP account

The first step is to follow the instructions in the chapter Section 53.7, “How to register a SIP telephone onto Abilis”, in order
to create a sip account.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

s user:test sip-ss:yes Enable supplementary services (ss) accessible through “*” as

firts digit in called number for the user “test”
s user:test sip-ss-pickup:any Set the pickup permission to any call.
save conf Save the configuration.

Tip
The parameter ss-pickup can be set to: NO to disable pickup, ANY to pickup any call.

990
Draft HowTo - CTI system Draft

53.15. How to configure CTIDISA to implement a

responder
The first step to follow is to prepare the sound files to be played by DISA. More information are in the section Section 47.8,
“Message files”.

53.15.1. Implementing a responder using MODE:INTRO

Assuming:

• ports 33 and 34 are connected to ISDN lines (099993 - 0999994)

• ports 33 and 34 belong to group G2

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctidisa Add the CTIDISA resource.

or or

s act res:ctidisa If the resource already exists, set it active.

s p ctidisa act:yes Enable the CTIDISA runtime functionalities
save conf Save the configuration
warm start Restart Abilis
s p ctidisa restricted-calling:no Accept calls also from calling numbers that are not present in
CTIDISA USERs CGI
a ctidisa service:responder Create a service named “responder”
s ctidisa service:responder mode:intro Set mode:intro for the service “responder”
s ctidisa service:responder cdi:20 Set the incoming called number to be used at pre-
identification to find the service.
s ctidisa service:responder intro:responder_sound Set the name of the message group from which the message
must be taken equal to “responder_sound”.
init res:ctidisa Init ctidisa resource
save conf Save the configuration

CTI routing configuration:

a ctir pr:1 type:vtod poi:g2 cdi:09999? cdo:20 ti1:sa Add a cti rule to route a call incoming from an ISDN line to
+su,00:00-23:59 disa only on Saturday and Sunday
init ctir Initialize ctir resource
save conf Save the configuration

Caution
Phone calls incoming on ISDN lines don't reach any phone on Saturday and Sunday.

Warning
MODE:INTRO may not work! It depends on your operator.

53.15.2. Implementing a responder using MODE:DISA

Assuming:

991
Draft HowTo - CTI system Draft

• ports 33 and 34 are connected to ISDN lines (099993 - 0999994)

• ports 33 and 34 belong to group G2

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctidisa Add the CTIDISA resource.

or or

s act res:ctidisa If the resource already exists, set it active.

s p ctidisa act:yes Enable the CTIDISA runtime functionalities
save conf Save the configuration
warm start Restart Abilis
s p ctidisa restricted-calling:no Accept calls also from calling numbers that are not present in
CTIDISA USERs CGI
a ctidisa service:responder Create a service named “responder”
s ctidisa service:responder mode:disa Set mode:disa for the service “responder”
s ctidisa service:responder cdi:20 Set the incoming called number to be used at pre-
identification to find the service.
s ctidisa service:responder initdial:responder_sound Set the name of the message group from which the message
INITDIAL must be taken.
s ctidisa service:responder callna:responder_sound Set the name of the message group from which the message
CALLNA must be taken.
s ctidisa service:responder permit:# Set the permitted called numbers to none
init res:ctidisa Init ctidisa resource
save conf Save the configuration

CTI routing configuration:

a ctir pr:1 type:vtod poi:g2 cdi:09999? cdo:20 ti1:sa Add a cti rule to route a call incoming from an ISDN line to
+su,00:00-23:59 disa only on Saturday and Sunday
init ctir Initialize ctir resource
save conf Save the configuration

Caution
Phone calls incoming on ISDN lines don't reach any phone on Saturday and Sunday.

Note
A possible optimization is to set the service parameter DIAL-TOUT=CONN-DELAY+Duration of sound
message.

53.15.3. Getting a call on phones while the responder is active

Assuming:

• ports 33 and 34 are connected to ISDN lines (099993 - 0999994)

• ports 33 and 34 belong to group G2

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a res:ctidisa Add the CTIDISA resource.

992
Draft HowTo - CTI system Draft

or or

s act res:ctidisa If the resource already exists, set it active.

s p ctidisa act:yes Enable the CTIDISA runtime functionalities
save conf Save the configuration
warm start Restart Abilis
s p ctidisa restricted-calling:no Accept calls also from calling numbers that are not present in
CTIDISA USERs CGI
a ctidisa service:responder Create a service named “responder”
s ctidisa service:responder mode:disa Set mode:disa for the service “responder”
s ctidisa service:responder cdi:20 Set the incoming called number to be used at pre-
identification to find the service.
s ctidisa service:responder initdial:responder_sound Set the name of the message group from which the message
INITDIAL must be taken.
s ctidisa service:responder callna:responder_sound Set the name of the message group from which the message
CALLNA must be taken.
s ctidisa service:responder alert:responder_sound Set the name of the message group from which the message
ALERT must be taken.
s ctidisa service:responder permit:500 Set the permitted called numbers to 500
s ctidisa service:responder auto-cdo:500 Set the automatically called number to 500
s ctidisa user:anonymous permit:service deny:* Set user's permissions
init res:ctidisa Init ctidisa resource
save conf Save the configuration

CTI routing configuration:

a ctir pr:1 type:vtod poi:g2 cdi:09999? cdo:20 ti1:sa Add a cti rule to route a call incoming from an ISDN line to
+su,00:00-23:59 disa only on Saturday and Sunday
a ctir pr:2 type:dtov poo:pbx cdi:500 Add a cti rule to route a call from disa to a pots phone whose
number is 500
init ctir Initialize ctir resource
save conf Save the configuration

Caution
Phone calls incoming on ISDN lines don't reach any phone on Saturday and Sunday.

Note
A possible optimization is to set the service parameter DIAL-TOUT=CONN-DELAY+Duration of sound
message.

53.16. How to configure Last Calling Service

Assuming to have an UMTSBOX (ports 201,202), let's configure the Last Calling Service so that a call received by the sim
inserted in the port # 201 of the UMTS BOX is routed toward the last number which called the calling number.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a lcsg id:1 cb-permit-cd:* Configure the lcs group.

s ctip:201 lcs-group:1 Configure the lcs group.
save conf Save the configuration

993
Draft HowTo - CTI system Draft

On a working Abilis, the initialization of the CTISYS resource is needed (init ctisys).

Remember to set the LCS parameter to YES in the VTOC routing (the one which routes calls from UMTSBOX toward
internal cluster).

Tip
Check the lcs table to verify the association between calling and called number.

53.17. How to configure DATA CALL BACK using an

UMTS Key, calling an ISDN number
Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a dev:umtskey-1 Add the umtskey-1 device.

warm start Restart Abilis.

Type the following commands to configure the ip resource:

a res:ip-22 subtype:ppp Add an IP over PPP resource

s p ip-22 lowres:ctislink Set to CtiSLink the lowres of the ip resource
s p ip-22 nat:outside Enable nat for the ip resource.
s p ip-22 dial-in:no dial-out:yes Prevent the ctislink to accept incoming calls

and let to perform outgoing calls.

s p ip-22 nrty:30 rty:us Configure the number of calls retry
s p ip-22 nrty3:nomax Configure the PPP authentication number retry.
s p ip-22 cdo:99 Configure the called output number.
s p ip-22 username:provider_user Configure the login information.
password:provider_pwd
s p ip-22 local:chap,pap remote:none Configure the local and remote authentication protocol.
s p ip-22 descr:UMTS-DATA Configure the local and remote authentication protocol.
save conf Save the configuration.
warm start Restart Abilis.

Type the following commands to configure CTIDISA resource:

a res:ctidisa Add the CTIDISA resource.

or or

s act res:ctidisa If the resource already exists, set it active.

s p ctidisa restricted-calling:yes Rejects calls from calling numbers that

are not present in CTIDISA User table.

s p ctidisa act:yes Enable the CTIDISA runtime functionalities.
save conf Save the configuration.
warm start Restart Abilis.
a ctidisa service:data_cb Add the data_cb service.
s ctidisa service:data_cb mode:data-cb cdi:888 cd- Configure the service to use the ip resource above
res:ip-22
for data call back when the input called number is 888.

994
Draft HowTo - CTI system Draft

save conf Save the configuration.

warm start Restart Abilis.

Type the following commands to configure the data routing:

a ctir pr:1 descr:umts-data type:data cdi:* poi:ctislink Add a rule to route data to ctip 201.
poo:201
a ctir pr:2 descr:DISA_data_cb type:vtod cdi:999901 Add a rule to route a call incoming from an ISDN line to
cgi:393331234567 cdo:888 sp:64000 coders:g.711 DISA,

when the calling number is a mobile phone.

init ctir initialize the CTIR resource.
save conf Save the configuration.

Note
The result is that calling the isdn number 999901 from the number 3331234567, the call is rejected and
an internet connection is established using the UMTS Key. The key acquires a dynamic IP address so the
configuration of Dynamic DNS is needed to reach Abilis. Besides, a correct configuration of NAT resource
may be necessary for example to reach a server located behind Abilis or to enable navigation toward internet
from LAN.

53.18. How to configure CTISMS to send sms using the

web interface
Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

a user:test pwd:test Add the user and set the password.

s user:test http:yes Enable http functionalities for the user.
a http rights path::/sys/sms/ user:test Set the http rights to access the SMS Gateway page.
save conf Save the configuration.

Configure the ctisms resource:

a res:ctisms Add the CTISMS resource.

or or

s act res:ctisms If the resource already exists, set it active.

s p ctisms act:yes Enable the CTISMS runtime functionalities.
save conf Save the configuration.
warm start Restart Abilis.
s ctisms out pr:1 act:yes Enable CTI SMS routings for outgoing messages. It routes
outgoing messages stored in a csv file or sent via web
interface toward a ctip port corresponding to the desidered
sim.
init res:ctisms Initialize CTISMS resource.
save conf Save the configuration.

53.19. How to configure CTISMS to send sms via emails

Suppose to have the following scheme:

995
Draft HowTo - CTI system Draft

Figure 53.1. Scheme for the configuration of CTISMS resource

The configuration of CTISMS includes a correct configuration of SMTP and DNS resources.

Enter into the Abilis control-program or open the configuration file with the Console configurator and type the following
commands.

The following commands are useful to configure the SMTP resource:

a res:smtp Add the SMTP resource.

or or

s act res:smtp If the resource already exists, set it active.

s p smtp act:yes Enable the SMTP runtime functionalities.
save conf Save the configuration
warm start Restart Abilis
s p smtp local-domain:sms.lan Set local domain for local mailboxes
s p smtp relay-net:192.168.1.0/24 Set the ip network for the mail relay server
s p smtp server:mail.server.com Set the FQDN name of SMTP Relay server to which all the
mails for not local domain are forwarded.
s p smtp server-user:user Set user name of the account of the relay server
s p smtp server-pwd:password Set password of the account of the relay server
s p smtp sms-gw:yes Enable sms services
init res:smtp Initialize the SMTP resource
save conf Save the configuration

The following commands are useful to configure the DNS resource:

a res:dns Add the DNS resource.

or or

s act res:dns If the resource already exists, set it active.

s p dns act:yes Enable the DNS runtime functionalities.
save conf Save the configuration
warm start Restart Abilis
s p dns primary:62.94.0.1 secondary:62.94.0.2 Set the DNS primary and secondary server ip addresses
s dns server id:1 dir:d name:sms.lan ip:192.168.1.1 Add an entry in the dns server table to translate the domain
sms.lan in the corresponding ip address

996
Draft HowTo - CTI system Draft

init res:dns Initialize the resource

save conf Save the configuration

The following commands are useful to configure the CTISMS resource:

a res:ctisms Add the CTISMS resource.

or or

s act res:ctisms If the resource already exists, set it active.

s p ctisms act:yes Enable the CTISMS runtime functionalities.
save conf Save the configuration
warm start Restart Abilis
s p ctisms dft-in:smtp Set the default route for incoming sms toward smtp server
s p ctisms dft-smtp:[email protected] Set the default smtp recipient for default route equal to
[email protected]
s ctisms in pr:0 act:yes Enable CTI SMS routings for incoming messages to route an
incoming email toward smtp
s ctisms out pr:0 act:yes Enable CTI SMS routings for incoming emails to route
an outgoing sms toward a ctip port corresponding to the
desidered sim
s ctisms out pr:1 act:yes Enable CTI SMS routings for incoming csv FILE to route
outgoing sms toward a ctip port corresponding to the
desidered sim
init res:ctisms Initialize CTISMS resource
save conf Save the configuration

53.19.1. Instructions to send emails through sms

1. Create an sms inserting the email address as first string;

2. insert a blank after the email address;

3. insert the text of message after the blank.

Example: [email protected]<blank>text of message.

53.19.2. Instructions to send sms through emails using a client

1. Create an account using as smtp server the ip address of Abilis following the below steps:

a. Open Outlook Express and click tools/accounts.

997
Draft HowTo - CTI system Draft

b. Click Add/Mail.

998
Draft HowTo - CTI system Draft

c. Insert the account name.

d. Insert the email address.

e. Configure the smtp server.

999
Draft HowTo - CTI system Draft

f. Configure the account name and password.

2. compose an email to +<country code><number>@sms.lan.

1000
Draft HowTo - CTI system Draft

Example: [email protected]

1001
Draft Draft

Chapter 54. FAQ - Frequently Asked

Questions
Marco Bellesia
Luigi Demuro

Table of Contents
54.1. ISDN lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.1. How can I verify if an ISDN line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
54.1.2. Back up over ISDN doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.3. How can I manage the backup over ISDN autoconnection? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.4. Is it possible to connect ISDN phones to BRI/BRI-HFC cards? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.1.5. Why (and how to) enable/disable analog ports on a NT1 Plus device? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
54.2. POTS ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.2.1. The connection to a PBX using pots ports doesn't work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
54.3. ADSL/HDSL lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.1. How can I verify if an ADSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.2. How can I verify if a HDSL line is active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
54.3.3. Why the xDSL line is slow? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
54.3.4. Why can't I reach any website? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4. CTI system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.1. How can I manage alternative CTI routings? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
54.4.2. How does Round Robin scanning method work in CTI Port Group? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
54.4.3. How can I change the POTS number length? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
54.4.4. How can I activate the Caller Identification Presentation (CLIP) on POTS ports? . . . . . . . . . . . . . . . . . . . . . . . . 1010
54.4.5. How can I manage the Calling Line Identification (CLI) for outcoming calls? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
54.4.6. Why during a call do I hear a fax handshaking? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
54.4.7. How can I view the maximum number of simultaneous calls supported by Abilis? . . . . . . . . . . . . . . . . . . . . . . . 1011
54.4.8. How can I view the available coders supported by the cards installed in Abilis? . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
54.4.9. How can I change the volume of a compressed call? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
54.4.10. How many VoIP channels are used, depending on the call's source and destination? . . . . . . . . . . . . . . . . . . . . 1013
54.4.11. What happens if a call fails with the “CAUSE:FF B4 (CPX,Loop)”? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
54.4.12. How can i configure sip multialerting? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5. IP router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.1. How can I query the IP routing table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
54.5.2. How does ACLBYPASS parameter work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.3. How can I view the Abilis ARP table? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
54.5.4. How can I filter the NAT sessions? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
54.6. Abilis system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.1. How can I view the current RAM usage? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
54.6.2. How can I view the current HD/CF space occupation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
54.6.3. How can I view the current CPU load? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.4. How can I view if the BRI card has the H.100 bus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.5. Is it possible to extract clock synchronization from BRIO cards? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.6. How can I view if the Abilis USB ports are enabled? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
54.6.7. Why do I get the error “RESOURCE NOT PRESENT OR NOT RUNNING” when I initialize a
resource? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.6.8. How can I change the Abilis prompt name? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7. Tunnelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.7.1. How can i have information about the use of ISDN backup? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
54.8. IPSEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
54.8.1. Why the outgoing traffic from CPX toward an IPSEC vpn is blocked after updating from 6.5.x to
7.0.x? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022

1002
Draft FAQ - Frequently Asked Questions Draft

54.9. CTISMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024

54.9.1. Can SMS to Email be sent an SMTP server different from the Abilis one? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.2. Can SMS also send CC: and BCC:? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.3. Can SMS to Email or Email to SMS be more than 160 characters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.4. Are attachments supported for email to SMS? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024
54.9.5. Can SMS be send thru a dialing plan to take advantage of cheaper or marketing promo when sending
SMS within the same Telco? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10. UMTS Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.1. How can I improve the quality of the calls with UMTS Box? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
54.10.2. How does Abilis manage the PIN code of a SIM card? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026

54.1. ISDN lines

54.1.1. How can I verify if an ISDN line is active?
• In ISDN PP lines, the physical layer must be ALWAYS active.

Type the command d d ctip:xx (where xx refers to the port that you want to check) and verify if the physical and logical
layer are active:

1. physical layer active:

• for PRI lines: ISDN-STATE:PRI-UP;

• for BRI lines: ISDN-STATE:F7-READY.

2. logical layer Q.931 active: TEI=0 and STATE:07-CONNECTED.

For example:

[10:00:21] ABILIS_CPX:d d ctip:3

CTIP:3 ----------------------------------------------------------------------
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SCG:] CD: [SCD:]
------------------------------------------------------------------------
1 10-CONNECTED-TO 039997335 3419985005
- Sapi ------- TEI -- STATE --------------------------------------------
16 (X.25 ) 10 00-INACTIVE
0 (Q.931) 0 07-CONNECTED
------------------------------------------------------------------------
ISDN-STATE:PRI-UP LINE-DOWN:27 SLIPS:8
RxAlarms:NONE TxAlarms:NONE

• In ISDN MP lines the physical layer is active ONLY when there is a current call; so if the physical layer is not active, you
cannot verify if the line is correctly working.

Type the command d d ctip:xx (where xx refers to the port that you want to check) and verify if the physical and logical
layer are active:

1. physical layer active:

• for BRI lines: ISDN-STATE:F7-READY.

2. logical layer Q.931 active: TEI>=64 and STATE:07-CONNECTED.

For example:

[10:00:21] ABILIS_CPX:d d ctip:33

CTIP:33 ----------------------------------------------------------------------
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SCG:] CD: [SCD:]

1003
Draft FAQ - Frequently Asked Questions Draft

------------------------------------------------------------------------
2 10-CONNECTED-FROM 3401233729 172695572
- Sapi ------- TEI -- STATE --------------------------------------------
16 (X.25 ) 10 00-INACTIVE
0 (Q.931) 64 07-CONNECTED
------------------------------------------------------------------------
ISDN-STATE:F7-READY LINE-DOWN:27 SLIPS:8

54.1.2. Back up over ISDN doesn't work

The most frequent cause of backup ISDN not working is the configuration SGI:* in a resource over B-channel or a resource
with backup, that could intercept backup calls.

You must verify that there are no resources (X25, IP-BCK, AIPT-BCK,…) with SGI:* and eventually, to insert the correct
value or SGI:disabled.

Tip
From 6.1 Release, with the d d ctislink command, it is possible to display the resources (with their SGI
value) ready to receive a connection over B-channel. For example:

[10:00:21] ABILIS_CPX:d d ctislink

RES:CtiSLink ------------------------------------------------------------------
HDLC_Over_ISDN_B-Channel
MaxConn:9 CurrConn:0
- Sessions -------------------------------------------------------------
SES: STATE: CG: [SCG:] CD: [SCD:] RES:
------------------------------------------------------------------------
- LISTEN X25-999
CPISDN
- LISTEN Pv-1
ABILIS1-ABILIS2
- LISTEN Pv-3
ABILIS1-ABILIS3
2 CONN -TO 0211223344 Ip-10
ABILIS1-ABILIS5

54.1.3. How can I manage the backup over ISDN autoconnection?

The BAC parameter controls the backup over ISDN autoconnection mode. With value DOD the behaviour supports the Dial-
On-Demand rules, while with value NAILED-UP the B-channel is spontaneously connected at boot, and reconnected in
case of drop for any reason. In case of connection failure the retries are managed via BRTY, BNRTY, BTB parameters.
Regardless of BAC value, i.e. even if BAC:NAILED-UP, if the state of the PLINK gets READY the SLINK (B channel) will
be closed after a short timeout, in the same way as when BAC:DOD.

With the DDT and VDT parameters it is possible to configure the Data and Voice Disconnect Time-out for every resource
over B channel and every resource with backup. With the value NOMAX it is possible to disable the inactivity timers.

54.1.4. Is it possible to connect ISDN phones to BRI/BRI-HFC cards?

Yes, it is, but Abilis doesn't provide power supply; ISDN phones MUST BE self-supplied!

54.1.5. Why (and how to) enable/disable analog ports on a NT1 Plus
device?
If Abilis is connected to a NT1 Plus device, it is recommended to disable the analog ports.

Consider the following scheme: when all VoIP channels are busy, a new incoming call is refused by the CTIP:33 and the NT
device forwards the call to the analog ports; in this way the call doesn't reach the BUSY state but the ALERTING state.

1004
Draft FAQ - Frequently Asked Questions Draft

Let's see how to disable and enable the analog ports.

• How to DISABLE analog ports on a NT1 Plus device:

1. Verify that there aren't current calls.

2. Temporarily disconnect from the NT device the cable(s) coming from Abilis.

3. Connect an analog BCA telephone with DTMF to the analogic port a1/b1 (RJ11).

4. Disable the a1/b1 port dialling the sequence: # * # # * # * 1 9 * 0 #

5. Hook the telephone.

6. Disable the a2/b2 port dialling the sequence: # * # # * # * 2 9 * 0 #

7. Hook the telephone.

8. Disconnect the telephone from the NT device.

9. Connect to the NT device the cable(s) coming from Abilis.

• How to ENABLE analog ports on a NT1 Plus device:

1. Verify that there aren't current calls.

2. Temporarily disconnect from the NT device the cable(s) coming from Abilis.

3. Connect an analog BCA telephone with DTMF to analogic connector a1/b1 (RJ11).

4. Enable the a1/b1 port dialling the sequence: # * # # * # * 1 9 * 100011 #

5. Hook the telephone.

6. Enable the a2/b2 port dialling the sequence: # * # # * # * 2 9 * 100011 #

7. Hook the telephone.

8. Disconnect the telephone from the NT device.

9. Connect to the NT device the cable(s) coming from Abilis.

54.2. POTS ports

54.2.1. The connection to a PBX using pots ports doesn't work
Abilis is compatible only with DTMF tones. Verify that the PBX uses DTMF tones and not pulse dialing.

1005
Draft FAQ - Frequently Asked Questions Draft

54.3. ADSL/HDSL lines

54.3.1. How can I verify if an ADSL line is active?
Verify the state of the USB modem: “USB” and “ADSL” LEDs must be green and continuous (not blinking!).

Warning
“ADSL” LED is green and continuous even if the logical layer is down.

Warning
When “USB” LED is red, the USB connection is not active!

Type the d d adsl command and verify that:

• the modem is connected and correctly working: MODEM:CONNECTED;

• ADSL carrier is active: ADSL-STATE:UP;

• there is traffic on the line: Trh-OUT and Trh-IN columns with values different from zero and increasing over time.

For example:

[10:08:48] ABILIS_CPX:d d adsl

RES:Adsl-1 --------------------------------------------------------------------
MODEM:CONNECTED MAC:00-30-0A-4B-BF-C1
ADSL-STATE:UP ADSL-FAILURE:NONE ADSL-TYPE:Annex-A
ADSL-TX-SPEED:320000 ADSL-RX-SPEED:1504000
ADSL-TX-SN-MARGIN:31 ADSL-RX-SN-MARGIN:31
ADSL-TX-ATTENUATION:15 ADSL-RX-ATTENUATION:10
- ATM level virtual channel diagnostics --------------------------------
VPI VCI State Bw-Out Bw-In 5sec-Thr-Out 5sec-Thr-In
5min-Thr-Out 5min-Thr-In
------------------------------------------------------------------------
8 35 UP 289811 1362113 2488 3328
4904 6544
------------------------------------------------------------------------

Note
Statistics are shown only if a Starmodem is used

It is possible to restart USB modem, using the command debug res:adsl-1 lsn:255. By typing the command debug
res:adsl-1 lsn:0, it is possible to display all available debug commands.

[10:08:48] ABILIS_CPX:debug res:adsl-1 lsn:255

RES:Adsl-1 --------------------------------------------------------------------
BufferLength:57 Date/Time:23/11/2007 12:37:50 TraceTime:<NotRunning>

ADSL restart has been queued, it will be executed ASAP.

54.3.2. How can I verify if a HDSL line is active?

Verify the state of DCE3 modem: if alarm LEDs (Alarm, KO,...) are on and blinking, there can be a fault on public network.

Type the d de fr command and verify that:

• LMI state is active: STATE:LMI-UP

• DLCI state is active: DLCI STATE: ACT

1006
Draft FAQ - Frequently Asked Questions Draft

• there is traffic on the line: Trh-OUT and Trh-IN columns with values different from zero and increasing over time.

For example:

[10:41:37] ABILIS_CPX:d de fr-1

RES:Fr-1 - FR over Dedicated Line (DL) ----------------------------------------

- Frame Relay ----------------------------------------------------------
STATE:LMI-UP
DLCI State Cong MaxThr CurMaxThr 5sec-Thr-Out 5sec-Thr-In
Cir Bc StepConst MaxThr% 5min-Thr-Out 5min-Thr-In
Tc Be Step Cir% MaxFrame-Out MaxFrame-In
------------------------------------------------------------------------
20 ACT NO 256000 256000 37488 51392
256000 256000 4 100% 52968 51976
1.000 0 5 100% 1504 1504
------------------------------------------------------------------------
- Link -----------------------------------------------------------------
+--------+--- Global ----+------- P-Link -------+------- S-Link -------+
| STATE: | READY | READY | LINK-NOT-PRESENT |
+--------+---------------+----------------------+----------------------+

54.3.3. Why the xDSL line is slow?

If an ADSL/HDSL line is too slow, you have to do the following verifications.

1. Verify that the ERRORS parameter in the ADSL resource is not increasing over time.

[10:08:48] ABILIS_CPX:d s adsl

RES:Adsl-2 --------------------------------------------------------------------
--- Cleared 9 days 20:13:02 ago, on 17/12/2007 at 21:03:54 -------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
ADSL-DOWN | 0| |MODEM-DISC | 0| |
ADSL-UP | 1| |MODEM-CONN | 1| |
AUTORST-A | 0| |AUTORST-U | 0| |
MANUALRST | 0| |MISALIGNED | 0| |
ATM-VC-UNK | 0| |ATM-VC-UNK | 0| |
------------------------------------------------------------------------
VPI:8 VCI:35
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CELLS | 55127478| 24499227|AAL5-SDU | 4030698| 3521937|
AAL5-CHAR | 2505678980| 1055083922|ERRORS | 8243| 0|
------------------------------------------------------------------------

2. Verify the bandwidth occupation with the d d adsl command.

[10:08:48] ABILIS_CPX:d d adsl

RES:Adsl-1 --------------------------------------------------------------------
MODEM:CONNECTED MAC:00-30-0A-4B-BF-C1
ADSL-STATE:UP ADSL-FAILURE:NONE ADSL-TYPE:Annex-A
ADSL-TX-SPEED:320000 ADSL-RX-SPEED:1504000
ADSL-TX-SN-MARGIN:31 ADSL-RX-SN-MARGIN:31
ADSL-TX-ATTENUATION:15 ADSL-RX-ATTENUATION:10
- ATM level virtual channel diagnostics --------------------------------
VPI VCI State Bw-Out Bw-In 5sec-Thr-Out 5sec-Thr-In
5min-Thr-Out 5min-Thr-In
------------------------------------------------------------------------
8 35 UP 289811 1362113 519347 3328
518161 6544
------------------------------------------------------------------------

If the input and/or output throughput has a value near to the maximum Bandwidth available, the line is saturated.

1007
Draft FAQ - Frequently Asked Questions Draft

Note
Statistics are shown only if a Starmodem is used

3. With the d nat maps command it is possible to display the IP addresses and ports of the current NAT sessions.

[12:48:33] ABILIS_CPX:d nat maps

Number of records in standard table: 4

S A TYPE SRC-ADDRESS SP/ID DST-ADDRESS DP/ID ALS-ADDRESS ALIAS TM

-------------------------------------------------------------------------------
I S UDP 192.168.000.008 45379 128.006.229.020 57333 080.080.080.080 7668 164
I S TCP 192.168.000.008 1521 193.205.079.111 5542 080.080.080.080 52450 132
I S UDP 192.168.000.008 45379 140.078.149.003 31782 080.080.080.080 7630 70
I S FTPd 192.168.000.003 4551 212.029.147.233 20 080.080.080.080 7455 172
I S UDP 192.168.000.008 45379 143.225.070.229 35236 080.080.080.080 7631 70
I S UDP 192.168.000.008 45379 221.250.120.075 42197 080.080.080.080 7659 136
I S UDP 192.168.000.008 45379 069.246.011.036 32876 080.080.080.080 7645 104
...

In this case there is a FTP session that could use a lot of bandwidth.

Tip
For release preceding 7.x one, use debug res:nat lsn:1.

54.3.4. Why can't I reach any website?

Verify the number of current NAT sessions with the d d nat command.

[12:48:33] ABILIS_CPX:d d nat

RES:Nat -----------------------------------------------------------------------
Network_Address_Translator
STATE:READY
-----------|--- CUR ---|-- PEAK ---|--- MAX ---|
LINKS | 998| 1000| 1000|
------------------------------------------------

If the value of CUR (current) parameter is near to the value of MAX parameter, probably some sessions could be discarded.

Tip
Remember to check also the IPACL table.

54.4. CTI system

54.4.1. How can I manage alternative CTI routings?
If the called phone is busy or not responding, the call is forwarded to the next routing if in the current one the NEXT
parameter is set to TRANSFERT.

When the parameter LAST is set to BUSY or NOANS or OTHER the routings can match only if the last failure reason matches
the one specified in LAST.

Note that:

• routing with LAST <> ANY can match only if a previous routing failed; they will never match as first routing;

• when a routing with LAST <> ANY fails, the original failure reason is not updated.

1008
Draft FAQ - Frequently Asked Questions Draft

For example:

[18:19:55] ABILIS_CPX:d ctir

--+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 CtoV # PBX ?? *
TRANSFERT ANY NO Dft * *
-------------------------------------------------------------------------------
1 CtoV # PBX ?? 22
TRANSFERT BUSY NO Dft * *
-------------------------------------------------------------------------------
2 CtoV # PBX ?? 01
TRANSFERT NOANS NO Dft * *
-------------------------------------------------------------------------------
3 CtoD # CtiDisa ?? 99
NO OTHER NO Dft * *
-------------------------------------------------------------------------------

• PR:0 is main call.

• If PR:0 fails with BUSY reason PR:1 is executed, e.g. call sent to a colleague.

• If PR:0 fails with NOANS reason PR:2 is executed, e.g. call sent to PBX main operator.

• If PR:0 fails with OTHER reasons (other than BUSY and NOANS) PR:3 is executed, e.g. call sent to a DISA group that
plays a message telling that call could not be delivered.

54.4.2. How does Round Robin scanning method work in CTI Port
Group?
If in a CTI group the S parameter is set to R, the incoming calls are directed towards the CTI ports in a circular manner; e.g.
the first call is forwarded to the port set in P1 parameter, the second call is forwarded to the port set in P2 parameter, etc...

If a port is busy or not responding, the call is forwarded to next port if the R parameter is set to UN (unconditional). In case of
“no answer” the call is forwarded to the next port after the time interval set in the T301 parameter; in case of “busy” the call
is immediately forwarded to the next port.

For example:

[18:19:55] ABILIS_CPX:d ctir pr:38

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------

1009
Draft FAQ - Frequently Asked Questions Draft

28 CtoV * G1 'technicians' *
TRANSFERT ANY NO 15 * *
6400 Sys Sys Sys Sys Sys * *
-------------------------------------------------------------------------------

[18:15:21] ABILIS_CPX:d ctig

--------------------------------------+--------------------+-------------------
[DESCR:]
ID: PICKUP: SCAN: RULE: |P1 P2 P3 P4 P5 |P6 P7 P8 P9 ...
|... P62 P63 P64
--------------------------------------+--------------------+-------------------
1 YES M UN |104 110 108 . . |. . . . .
--------------------------------------+--------------------+-------------------

Note
If the T301 parameter is set to the default value (180 sec.), the call is not forwarded to the next port.

54.4.3. How can I change the POTS number length?

By default, the POTS port numbers are 2 digits long; it is possible to change their length by modifying the POTS-NUM-
LENGTH parameter in the CTISYS resource (available values are: 1,2,3 or 4). For example:

s p ctisys pots-num-length:3 Change the NUM parameter length to 3.

save conf Save the configuration.
init ctisys Initialize the CTISYS resource.

54.4.4. How can I activate the Caller Identification Presentation

(CLIP) on POTS ports?
Set the CLIP parameter to YES in the CTISYS resource.

s p ctisys clip:yes Activate the Caller Identification Presentation.

save conf Save the configuration.
init ctisys Initialize the CTISYS resource.

Tip
Refer to this paragraph [648] to know more about CLIP parameter.

54.4.5. How can I manage the Calling Line Identification (CLI) for
outcoming calls?
Calling Line Identification can be statically managed in the CGO parameter in CTI Routings:

• CGO:# : Set an empty information element. An empty information element in most cases is removed.

[18:19:55] ABILIS_CPX:d ctir pr:11

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO
EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO
|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO

1010
Draft FAQ - Frequently Asked Questions Draft

|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH

|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
1 TR G1 G2 * *
NO ANY NO Dft * #
-------------------------------------------------------------------------------

In alternative, if the call is incoming from a POTS port which is configured with SS:YES and SS-PRES-CG:YES, it is
possible to force CLIR/CLIP typing the following codes:

• *60#<number-to-dial>: make a call to <number-to-dial> hiding the calling number;

• *61#<number-to-dial>: make a call to <number-to-dial> presenting the calling number.

[22:47:50] ABILIS_CPX:d p ctipe:106

CTIP:106 DESCR:
Act card:POTS-1<6>
OPSTATE:UP LOG:NO TYPE:USER
signalling:POTS HOLD:YES CT:ICT SS:YES
mode:Pots NUM:06
LOOP:NO TEST:NO
CLIP:SYS CLIP-STD:SYS CLIP-TAS:SYS MIN-FLASH:SYS
SENSING:SYS ABF:SYS HPF:SYS DEBOUNCE:SYS MAX-FLASH:SYS
COUNTRY:SYS IN-GAIN-ADJ:SYS OUT-GAIN-ADJ:SYS
AT:SYS AT-CODE:SYS AT-DURATION:SYS BC:SYS
DT:SYS DT-CODE:SYS DT-DURATION:SYS OUT-DIAL-TONE:SYS
SS-PICKUP:GROUP SS-PRES-CG:YES NP-CT:SYS
SS-CF-DND:YES

Caution
In this case the CGO parameter in the CTIR routing must not be set to #.

54.4.6. Why during a call do I hear a fax handshaking?

During the compressed call, the calling or called phone intercepts the handshaking of a fax located near the phone. The DSP
used by Abilis identifies this signal as a request of fax transmission and starts to simulate the fax modulation.

The possible solutions are:

• mute the fax volume;

• disable the fax relay feature (FM-RELAY:NO in the setting of CTISYS resource, or FMRLY:NO in the specific CTIR
routings).

Tip
Refer to chapter Section 42.12.3.5, “Fm-relay parameter”.

54.4.7. How can I view the maximum number of simultaneous calls

supported by Abilis?
To view the maximum number of simultaneous calls supported by Abilis type the command: d d ctiac or d de ctiac for the
extended mode.

For example the following Abilis allows up to 8 simultaneous calls.

[16:16:35] ABILIS_CPX:d d ctiac

-------------------------------------------------------------------------------

1011
Draft FAQ - Frequently Asked Questions Draft

AC Card DSP/C Bus/TS DSPState ACState ModeIn ModeOut Coder Ctip/BC

-------------------------------------------------------------------------------
0 BRI4-2 0/0 8/00 RUN IDLE - - - -
1 BRI4-2 0/1 8/01 RUN IDLE - - - -
2 BRI4-2 0/2 8/02 RUN IDLE - - - -
3 BRI4-2 0/3 8/03 RUN IDLE - - - -
4 BRI4-2 1/0 9/05 RUN IN-USE VOICE VOICE Spirit/6.4k 108/01
5 BRI4-2 1/1 9/06 RUN IDLE - - - -
6 BRI4-2 1/2 9/07 RUN IDLE - - - -
7 BRI4-2 1/3 9/08 RUN IDLE - - - -

54.4.8. How can I view the available coders supported by the cards
installed in Abilis?
To view the available coders supported by CTI cards installed in Abilis type the command: d d ctisys.

[16:32:16] ABILIS_CPX:d d ctisys

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
CTIR-STATE:ENABLED CALLS-CURRENT:0 CALLS-PEAK:0
AC-STATE:ENABLED AC-CURRENT:0 AC-PEAK:0
------------------------------------------------------------------------
-- Number of simultaneous calls ----------------------------------------
| State: Alerting/Connected | State: Any |
---------------|---Current---|----Peak-----|---Current---|----Peak-----|
TR | 0 | 0 | 0 | 0 |
DATA | 0 | 0 | 0 | 0 |
VtoCHISD | 0 | 0 | 0 | 0 |
CHISDtoCHISD | 0 | 0 | 0 | 0 |
CHISDtoV | 0 | 0 | 0 | 0 |
ALL | 0 | 0 | 0 | 0 |
------------------------------------------------------------------------
- Available coders -----------------------------------------------------
-- Coder ---|-- Bit rates (kbps) --|-- Coder ---|-- Bit rates (kbps) --|
G.711A |64 |G.711u |64 |
G.726 |16, 24, 32, 40 |G.729A |8 |
TRANSPARENT |64 |Spirit |6.4, 7.2, 8, 8.8, 9.6 |
G.727 |16/16, 24/16, 24/24, |
|32/16, 32/24, 32/32, |
|40/16, 40/24, 40/32 |
------------------------------------------------------------------------
- Clock Sources for H100 cards -----------------------------------------
CLK:34
- Clock Sources for NOT-H100 cards -------------------------------------
*** No NOT-H100 cards running ***

54.4.9. How can I change the volume of a compressed call?

It is possible to modify the OUT-GAIN parameter in the CTISYS resource. For example:

s p ctisys out-gain:+3 Change the output gain in the range [MUTE, -31..+31 dB].
save conf Save the configuration.
init ctisys Initialize the CTISYS resource.

For the phones connected to POTS cards it is possible to modify the OG parameter in the specific CTI Routing. For example:

s ctir pr:5 og:+5 Change the output gain in the range [SYS, MUTE, -31..+31
dB].
save conf Save the configuration.

1012
Draft FAQ - Frequently Asked Questions Draft

init ctir Initialize the CTI Routings.

54.4.10. How many VoIP channels are used, depending on the call's
source and destination?
Codec used by the call Abilis routes VoIP channels occupied Bandwidth occupied by
coming from VoIP the call toward each channel (Kbit/s)
telephones in the LAN
SIP Codec G.711 Telecom ISDN network 1 64
SIP Codec G.729 Telecom ISDN network 1 64
SIP Codec G.711 Abilis over ISDN network 2 9
SIP Codec G.729 Abilis over ISDN network 2 9
SIP Codec G.711 VoIP provider with G.729 2 32
SIP Codec G.729 VoIP provider with Abilis 2 30 the first call, 9 the others
Codec calls
SIP Codec G.711 VoIP provider with G.729 0 32
SIP Codec G.729 VoIP provider with Abilis 2 30 the first call, 9 the others
Codec calls
SIP Codec G.711 Abilis GSM Box 0 1 GSM channel
SIP Codec G.729 Abilis GSM Box 1 1 GSM channel
IAX2 Codec G.711 Telecom ISDN network 1 64
IAX2 Codec G.729 Telecom ISDN network 1 64
IAX2 Codec G.711 Abilis over ISDN network 2 9
IAX2 Codec G.729 Abilis over ISDN network 2 9
IAX2 Codec G.711 VoIP provider with G.729 2 32
IAX2 Codec G.729 VoIP provider with Abilis 2 30 the first call, 9 the others
Codec calls
IAX2 Codec G.711 VoIP provider with G.729 0 32
IAX2 Codec G.729 VoIP provider with Abilis 2 30 the first call, 9 the others
Codec calls
IAX2 Codec G.711 Abilis GSM Box 0 1 GSM channel
IAX2 Codec G.729 Abilis GSM Box 1 1 GSM channel

Note
1 DSP manages 4 channels.

54.4.11. What happens if a call fails with the “CAUSE:FF B4

(CPX,Loop)”?
When a call ends with the disconnection code CAUSE:FF B4 (CPX,Loop), Abilis blocks the calls which enter and exit from
the same ISDN port, when in the CTI Routing the POI parameter is set to *.

To enable the loop, you must add a CTI Routing with POI:<port_number> and POO:<port_number> (e.g. POI:32,
POO:32) before the CTI Routing with POI:*.

[18:27:15] ABILIS_CPX:d ctir

---+-----+-----------------+---------+--------------------+--------------------
PR |[DESCR]
|TYPE |POI/SR [SR] |POO/DS |CDI |CDO
ACT|NEXT |LAST |EEC |T301|CGI |CGO

1013
Draft FAQ - Frequently Asked Questions Draft

EDT|SP |SC |DJ |MJ |FMDJ|FMMJ|SDI |SDO

|SPOUT|SCOUT|DJOUT|MJOUT|LCS |LCST|SGI |SGO
| |RGI |RGO
|FMRLY|FAXSP|MODSP|FMLVL|ECM |UDT |IG |OG |SG |DL |DH
|CODERS
|CODERSOUT
|TI1 .. TI5
-------------------------------------------------------------------------------
0 DATA * CtiSLink * *
-------------------------------------------------------------------------------
1 TR 32 32 * *
-------------------------------------------------------------------------------
2 TR * 32 * *
-------------------------------------------------------------------------------

54.4.12. How can i configure sip multialerting?

Sip multialerting is not yet implemented. The only way to configure sip multialerting is to use forking which let to create
heterogeneous groups of phones.

54.5. IP router
54.5.1. How can I query the IP routing table?
To understand what is the outgoing IP port of a packet, according to a specific source, type the debug res:iprtr lsn:9
cmd:src.src.src.src-dst.dst.dst.dst command.

For example:

[17:45:39] ABILIS_CPX:debug res:iprtr lsn:9 cmd:192.168.0.29-192.168.5.254

RES:Iprtr ---------------------------------------------------------------------
IP_Router_general_properties
BufferLength:137 Date/Time:22/12/2010 11:51:01 TraceTime:12047455

Route query information

Route query for SRC:192.168.000.029 and DST:192.168.005.254.

Outgoing IP Port 2, gateway 192.168.001.001.

By typing the debug res:iprtr lsn:0 command it is possible to display the help of the debug command.

[17:45:39] ABILIS_CPX:debug res:iprtr lsn:0

[16:09:00] ABILIS_CPX:debug res:iprtr lsn:0

RES:Iprtr ---------------------------------------------------------------------
IP_Router_general_properties
BufferLength:2453 Date/Time:22/12/2010 11:50:02 TraceTime:11989095

Usage:
LSN:0 == This help
LSN:1 == Complete debug
LSN:2 == Upper/Lower NCB status
LSN:3 == Display ICMP header of the last 10 packets with chksum err
LSN:3 CMD:EXT == Display ICMP extended of checksum errors
LSN:3 CMD:CLR == Clear the ICMP checksum failures history
LSN:4 == NAT/ROUTE statistics display
LSN:4 CMD:CLR == NAT/ROUTE statistics clear
LSN:5 == Speed-limit status information
LSN:6 == Speed-limit error information

1014
Draft FAQ - Frequently Asked Questions Draft

LSN:6 CMD:CLR == Speed-limit error clear

LSN:7 == Queue packet status information for ALL IP-RES
LSN:7 CMD:<IP-xx> == Queue packet status information for specific IP-RES
LSN:8 CMD:<IP-xx> == Queue flow information
LSN:9 CMD:src.src.src.src-dst.dst.dst.dst == Route query
LSN:10 == Queue forced discards for ALL IP-RES
LSN:10 CMD:<IP-xx> == Queue forced discards for specific IP-RES
LSN:11 == Queue total discards for ALL IP-RES
LSN:11 CMD:<IP-xx> == Queue total discards for specific IP-RES
LSN:12 CMD:CLR == Queue forced/total discards clear
LSN:13 == All reassembler statistics
LSN:13 CMD:<prot> == Specific protocol reassembler statistics
LSN:14 == All reassembler descriptor information
LSN:14 CMD:<prot> == Specific protocol reassembler descriptor information
LSN:15 == Registered IPs for ALL IP-RES
LSN:15 CMD:<IP-xx> == Registered IPs for specific IP-RES
LSN:16 == Registered MAC/IPs for ALL IP-RES
LSN:16 CMD:<IP-xx> == Registered MAC/IPs for specific IP-RES
LSN:17 == Queue BYTEs status information for ALL IP-RES
LSN:17 CMD:<IP-xx> == Queue BYTEs status information for specific IP-RES
LSN:18 == Load balancing configuration by ID
LSN:19 == PING status information for ALL IP-RES
LSN:19 CMD:<IP-xx> == PING status information for specific IP-RES
LSN:20 CMD:<IP-xx> == Extended PING status information for specific IP-RES
LSN:21 CMD:<IP-xx> == Extended queue flow information
LSN:22 CMD:<IP-xx> == IPACL request tracer information
LSN:22 CMD:CLR == Clear IPACL request tracer information
LSN:23 CMD:<IP-xx> == DHCP client information for specific IP-RES
LSN:24 == Load balancing configuration by IP-RES

54.5.2. How does ACLBYPASS parameter work?

In the ACLBYPASS parameter it is possible to set a source/destination IP address that bypasses the IPACL (IP Access
Control List).

ACLBYPASS parameter is used only AFTER IPACL check, and only if it returned a DENY. The result is that packets
matching IPACL PERMIT entries will get IPCOS and TOS-OUT as specified in the IPACL, while packets matching
a DENY entry may be passed because of match with ACLBYPASS with the assigment of IPCOS=COSDFT and TOS
unchanged.

[19:03:49] ABILIS_CPX:d p iprtr

RES:Iprtr ---------------------------------------------------------------------
Run DESCR:IP_Router_general_properties
- General --------------------------------------------------------------
R-ID:AUTO (192.168.000.201)
maxroute:500 DFTTTL:255 ps:2048
DEF-LOCAL-AD:0 DEF-STATIC-AD:1 DEF-OSPF-AD:110 DEF-RIP-AD:120
pvc:0 bsvc:0 LINKS:3 virtual:0
- IP Access List -------------------------------------------------------
ACL:EXT ACLBYPASS:192.168.0.232
COS:ENABLED COSDFT:NORMAL
COSBALANCE:NO NORMRATE:50 LOWRATE:50
- IP Trace -------------------------------------------------------------
tracerec:100
- Ppp-Dns --------------------------------------------------------------
PPP-DNS-PRI:000.000.000.000 PPP-DNS-SEC:000.000.000.000

54.5.3. How can I view the Abilis ARP table?

Type the command debug res:ip-1 layer:lan lsn:2. For example:

[19:03:49] ABILIS_CPX:debug res:ip-1 layer:lan lsn:2

1015
Draft FAQ - Frequently Asked Questions Draft

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Lan_locale
BufferLength:1782 Date/Time:20/03/2008 12:42:48 TraceTime:1293544007

----+----------------+------------------+-----------+-----------
ID|IP |MAC |State | Expiry [s]
----+----------------+------------------+-----------+-----------
1|192.168.000.058 |00-40-F4-BB-E6-2F |VALID | 3
2|192.168.000.208 |00-08-54-50-16-1E |VALID | 106
3|192.168.000.251 |00-48-54-13-21-22 |VALID | 26
4|192.168.000.024 |00-08-54-02-00-78 |VALID | 53
5|192.168.000.005 |00-0C-6E-DE-2C-15 |VALID | 103
6|192.168.000.029 |00-40-CA-63-34-E3 |VALID | 1
7|192.168.000.250 |00-40-CA-63-34-A2 |VALID | 103
9|192.168.000.067 |00-13-8F-7E-21-33 |VALID | 84
10|192.168.000.009 |00-48-54-13-23-E7 |VALID | 99
11|192.168.000.085 |00-04-61-75-56-F5 |VALID | 107
12|192.168.000.090 |00-40-CA-6D-1D-24 |VALID | 108
13|192.168.000.035 |00-40-CA-63-34-82 |VALID | 35
14|192.168.000.025 |00-40-CA-63-35-15 |VALID | 60
15|192.168.000.033 |00-40-CA-63-34-F8 |VALID | 76
16|192.168.000.126 |00-80-48-B3-45-4B |VALID | 20
...

By typing the debug res:ip-1 layer:lan lsn:0 command it is possible to display the help of the debug command.

[19:03:49] ABILIS_CPX:debug res:ip-1 layer:lan lsn:0

RES:Ip-1 - IP over LAN (LAN) --------------------------------------------------

Lan_locale
BufferLength:421 Date/Time:20/03/2008 12:43:40 TraceTime:1293596030

IPLAN DEBUG INFO:

LSN:0 This help message
LSN:1 IPLAN driver object
LSN:2 ARP cache: only VALID items
LSN:3 ARP cache: only VALID & OUTDATED items
LSN:4 ARP cache: all items
LSN:5 Registered local IP addresses
LSN:6 Registered multicast MAC addresses
LSN:7 Registered virtual MAC/IP addresses
LSN:9 Current timer state (ticks)
LSN:10 NCBs at lower interface
LSN:11 NCBs at upper interface

54.5.4. How can I filter the NAT sessions?

Type the command d nat maps ip:<ip_address>. For example:

[13:01:23] ABILIS_CPX:d nat maps

Number of records in standard table: 39

S A TYPE SRC-ADDRESS SP/ID DST-ADDRESS DP/ID ALS-ADDRESS ALIAS TM

-------------------------------------------------------------------------------
IOS UDP 192.168.030.001 5060 083.211.227.015 5060 192.168.001.100 1024 80
IOS UDP 192.168.030.002 11826 087.241.097.125 49152 192.168.001.100 6339 139
IOS UDP 192.168.030.002 11826 096.028.041.076 44121 192.168.001.100 1121 37
IOS TCP 192.168.030.002 59013 205.188.005.066 443 192.168.001.100 1027 358
IOS UDP 192.168.030.002 11826 178.150.129.152 61956 192.168.001.100 6331 136
IOS TCP 192.168.030.003 1038 074.125.232.112 80 192.168.001.100 6342 353
IOS TCP 192.168.030.003 1041 074.125.232.112 80 192.168.001.100 6343 355

1016
Draft FAQ - Frequently Asked Questions Draft

IOS TCP 192.168.030.002 38353 064.004.061.088 1863 192.168.001.100 1032 336

IOS UDP 192.168.030.002 11826 178.049.048.004 31799 192.168.001.100 6334 123
IOS TCP 192.168.030.003 1042 074.125.232.116 80 192.168.001.100 6344 355
IOS UDP 192.168.030.002 11826 178.213.109.009 58305 192.168.001.100 6336 125
IOS TCP 192.168.030.003 1043 063.245.209.093 80 192.168.001.100 6345 360
IOS TCP 192.168.030.003 1044 212.058.244.057 80 192.168.001.100 6346 360
IOS TCP 192.168.030.003 1045 195.022.200.144 80 192.168.001.100 6347 360
IOS UDP 192.168.030.002 11826 079.100.139.017 20685 192.168.001.100 6236 86
IOS UDP 192.168.030.002 11826 087.248.174.154 19652 192.168.001.100 6239 86
IOS UDP 192.168.030.002 11826 184.190.196.131 37255 192.168.001.100 3701 96
IOS UDP 192.168.030.002 11826 098.232.048.010 47217 192.168.001.100 3706 81
IOS UDP 192.168.030.002 11826 217.201.019.166 51716 192.168.001.100 5801 61
IOS UDP 192.168.030.002 11826 188.186.052.100 47055 192.168.001.100 5808 82
IOS UDP 192.168.030.002 11826 203.218.109.047 12984 192.168.001.100 4482 97
IOS UDP 192.168.030.002 11826 094.242.051.070 52094 192.168.001.100 1376 125
IOS UDP 192.168.030.002 11826 086.075.015.096 26070 192.168.001.100 3601 136
IOS UDP 192.168.030.002 11826 067.247.155.048 22434 192.168.001.100 2935 96
IOS UDP 192.168.030.002 11826 119.246.064.215 15665 192.168.001.100 4627 8
IOS UDP 192.168.030.002 11826 094.041.075.151 12840 192.168.001.100 5340 38
IOS UDP 192.168.030.002 11826 079.041.083.069 42176 192.168.001.100 6115 76
IOS UDP 192.168.030.002 11826 079.040.142.006 44256 192.168.001.100 4713 11
IOS UDP 192.168.030.002 11826 190.052.139.104 18460 192.168.001.100 5419 136
IOS UDP 192.168.030.002 11826 077.071.136.116 26322 192.168.001.100 5421 136
IOS UDP 192.168.030.002 11826 090.150.168.098 18684 192.168.001.100 5422 41
IOS UDP 192.168.030.002 11826 084.252.032.040 23716 192.168.001.100 6204 82
IOS UDP 192.168.030.002 11826 124.146.059.056 13975 192.168.001.100 4035 96
IOS UDP 192.168.030.002 11826 085.076.191.108 63279 192.168.001.100 4036 96
IOS UDP 192.168.030.002 11826 093.105.147.184 12357 192.168.001.100 4150 104
IOS UDP 192.168.030.002 11826 077.087.008.009 51520 192.168.001.100 3274 16
IOS UDP 192.168.030.002 11826 024.123.109.130 52283 192.168.001.100 3275 25
IOS UDP 192.168.030.002 11826 059.178.047.179 10028 192.168.001.100 4966 121
IOS UDP 192.168.030.002 11826 088.111.166.121 22324 192.168.001.100 4978 96

[13:01:32] ABILIS_CPX:d nat maps ip:192.168.30.3

Number of records in standard table: 34

S A TYPE SRC-ADDRESS SP/ID DST-ADDRESS DP/ID ALS-ADDRESS ALIAS TM

-------------------------------------------------------------------------------
IOS TCP 192.168.030.003 1038 074.125.232.112 80 192.168.001.100 6342 320
IOS TCP 192.168.030.003 1041 074.125.232.112 80 192.168.001.100 6343 322
IOS TCP 192.168.030.003 1042 074.125.232.116 80 192.168.001.100 6344 322
IOS TCP 192.168.030.003 1045 195.022.200.144 80 192.168.001.100 6347 327

By typing the debug res:nat lsn:0 command it is possible to display the help of the debug command.

[19:03:49] ABILIS_CPX:d nat maps ?

D NAT MAPS [filter:val] Display any NAT active maps matching the
specified filter(s)

Allowed filters on active maps:

IP: Separate records by IP: ipadd[/mask]

S: Separate records by source IP: ipadd[/mask]
D: Separate records by destination IP: ipadd[/mask]
A: Separate records by alias IP: ipadd[/mask]
SIDEIN: Separate records by input side of translation [IN, OUT, VPN, DMZ]
SIDEOUT: Separate records by output side of translation [IN, OUT, VPN, DMZ]
ADDR: Separate records by address type [SRC, DST]
TYPE: Separate records by type of record [ICMP, TCP, UDP, FRAG, DNS, FTP
FTPC, FTPD, SNMP, SNTP, PPTP,

1017
Draft FAQ - Frequently Asked Questions Draft

PPTPC, PPTPD]
PORT: Separate records by port/id [1..65535]
SP: Separate records by source port/id [1..65535]
DP: Separate records by destination port/id [1..65535]
AP: Separate records by alias port/id [1..65535]

Active map fields:

S Side (incoming/outgoing, can be I, O, V, D)

A Address type (source/destination, can be S, D
TYPE Protocol type
SRC-ADDRESS Source IP address
SP/ID Source port/id
DST-ADDRESS Destination IP address
DP/ID Destination port/id
ALS-ADDRESS Alias IP address
ALIAS Alias port/id
TM Map lifetime

Tip
For version preceding the release 7.x, the command debug res:nat lsn:1 cmd:ip:<ip_address> must be
used. Type debug res:nat lsn:0 to display the help of the debug command.

54.6. Abilis system

54.6.1. How can I view the current RAM usage?
Type the d i command and verify the value of the string “Free/Total Memory”. For example:

[11:38:04] ABILIS_CPX:d i

Abilis CPX - Ver. 7.0.3/STD - 24/11/2010 - Build 3357.17 - 24/11/2010

(c) 1994/2010 - Abilis

ABILIS-ID: 2349

Free/Total Memory: 171,795,952/268,435,456 Largest Block: 171,795,952

Free/Used/Total HD/CF space (in KB): 108,416/13,936/122,352

File Version Date Time Size Note

-------------------------------------------------------------------------------
CPX.RTB ....... 24/11/2010 21:43:20 4189385
DRIVERS.CFG v.7.0 22/12/2010 08:30:14 16384 Ok
DRIVERS.BCK v.7.0 21/12/2010 17:06:16 16384 Ok
...

To view the current RAM usage of each Abilis driver type the command debug mem -d. For example:

[11:38:04] ABILIS_CPX:debug mem -d

Full report of memory allocated at drivers start-up:

Driver Allocated TotUsed TotFree TotAvail

-------------------------------------------------------------------------------
IRQMNG 64 107,120 258,325,168 268,304,384
HWINT 79,872 107,184 258,325,088 268,304,384
FILE 1,216 187,056 258,244,592 268,304,384
LOGXCP 3,168 188,272 258,243,184 268,304,384
LOGSYS 21,728 191,440 258,239,872 268,304,384
LIVE 1,200 213,168 258,215,392 268,304,384
GS 48 214,368 258,214,112 268,304,384

1018
Draft FAQ - Frequently Asked Questions Draft

CNFG 80,048 214,416 258,214,048 268,304,384

CPXCFGFILE 1,414,880 294,464 258,133,856 268,304,384
LOGDBG 43,216 1,709,344 256,475,152 268,304,384
MENU 8,368 1,752,560 256,428,624 268,304,384
USB 40,720 1,760,928 256,419,408 268,304,384
ASY 10,544 1,801,648 256,377,824 268,304,384
ADSLUSB 1,420,304 1,812,192 256,366,752 268,304,384
Eth100 270,528 3,232,496 254,942,736 268,304,384
Ppp 258,432 3,503,024 254,671,776 268,304,384
Mlm 2,735,328 3,761,456 254,408,112 268,304,384
LapB 60,304 6,496,784 251,607,216 268,304,384
IpLan 303,392 6,557,088 251,544,400 268,304,384
Nat 260,496 6,860,480 251,228,496 268,304,384
PoeAc 63,456 7,120,976 250,935,760 268,304,384
CtiSys 2,069,520 7,184,432 250,868,768 268,304,384
VMS 13,904 9,253,952 248,768,880 268,304,384
CtiRouter 215,568 9,267,856 248,754,176 268,304,384
CtiPorts 868,880 9,483,424 248,537,600 268,304,384
CtiH323 1,293,408 10,352,304 247,636,944 268,304,384
CtiIax 2,324,608 11,645,712 246,336,240 268,304,384
CtiDisa 759,088 13,970,320 243,924,528 268,304,384
CtiClusters 11,434,416 14,729,408 243,134,784 268,304,384
CtiSLink 13,776 26,163,824 230,638,048 268,304,384
MfIde 48 26,177,600 230,623,392 268,304,384
Cp 1,216,592 26,177,648 230,623,328 268,304,384
X25 352,208 27,394,240 229,396,016 268,304,384
Iprtr 4,443,072 27,746,448 229,024,416 268,304,384
ICMP 74,128 32,189,520 224,186,032 268,304,384
Tcp 2,521,744 32,263,648 224,110,912 268,304,384
Ssh 1,189,840 34,785,392 221,549,664 268,304,384
Telnet 304,096 35,975,232 220,346,880 268,304,384
Http 4,118,800 36,279,328 220,031,104 268,304,384
Ftp 533,504 40,398,128 215,876,528 268,304,384
Udp 50,352 40,931,632 215,341,600 268,304,384
Snmp 115,920 40,981,984 215,287,104 268,304,384
Rip 48 41,097,904 215,161,056 268,304,384
PLinkE 4,323,936 41,097,952 215,160,992 268,304,384
Sntp 51,088 45,421,888 210,599,920 268,304,384
Dns 451,584 45,472,976 210,548,000 268,304,384
Dhcp 48 45,924,560 210,087,904 268,304,384
Ospf 48 45,924,608 210,087,840 268,304,384
Trfa 2,607,552 45,924,656 210,087,776 268,304,384
Pad 79,968 48,532,208 207,478,144 268,304,384
Acnt 235,648 48,612,176 207,397,120 268,304,384
COR 272,416 48,847,824 207,154,448 268,304,384
TRACER 8,490,592 49,120,240 206,867,856 268,304,384
DIAGTEST 39,488 57,610,832 198,376,880 268,304,384
BEEPER 2,640 57,650,320 198,337,200 268,304,384

54.6.2. How can I view the current HD/CF space occupation?

Type the d i command and verify the value of the string “Free/Used/Total HD/CF space (in KB)”. For example:

[11:38:04] ABILIS_CPX:d i

Abilis CPX - Ver. 7.0.3/STD - 24/11/2010 - Build 3357.17 - 24/11/2010

(c) 1994/2010 - Abilis

ABILIS-ID: 2349

Free/Total Memory: 171,795,952/268,435,456 Largest Block: 171,795,952

Free/Used/Total HD/CF space (in KB): 108,416/13,936/122,352

1019
Draft FAQ - Frequently Asked Questions Draft

File Version Date Time Size Note

-------------------------------------------------------------------------------
CPX.RTB ....... 12/10/2010 19:36:26 4163974
DRIVERS.CFG v.7.0 05/12/2010 15:46:54 19456 Ok
DRIVERS.BCK v.7.0 05/12/2010 15:03:14 19456 Ok
...

54.6.3. How can I view the current CPU load?

Type the d cpu command: the CPU speed and the CPU load percentages are displayed.

[11:38:04] ABILIS_CPX:d cpu

CPU speed: 1102 Mhz

+----------+--------------+--------------+--------------+
| | Last 1 sec. | Last 15 sec. | Last 5 min. |
+----------+--------------+--------------+--------------+
| CPU Load | 9% | 6% | 6% |
+----------+--------------+--------------+--------------+

54.6.4. How can I view if the BRI card has the H.100 bus?
Type the d pcidev command and verify that the OKI string is present. The HFC string identifies the BRI-HFC cards. For
example:

[11:38:04] ABILIS_CPX:d pcidev

PCI Server Overview:

ID Vendor Device CardName Slot/F Ver Irq

-------------------------------------------------------------------------------
0 8086 INTEL 7190 BRIDGE HOST - 0/0 0.03 -
1 8086 INTEL 7191 BRIDGE PCI - 1/0 0.03 -
2 8086 INTEL 7110 BRIDGE ISA - 7/0 0.02 -
3 8086 INTEL 7111 STORAGE IDE - 7/1 0.01 -
4 8086 INTEL 7112 USB CONTROLLER UHCI - 7/2 0.01 9
5 8086 INTEL 7113 BRIDGE OTHER - 7/3 0.02 -
6 10EC REALTEK 8139 NETWORK ETHERNET TE100-PCIWN 8/0 1.00 10
7 10EC REALTEK 8139 NETWORK ETHERNET TE100-PCIWN 9/0 1.00 5
8 1283 ITE 8872 16550 SERIAL PORT PCI-POTS 11/0 0.01 9
9 10B5 PLX TECHNO 9050 BRIDGE OTHER CTI-HFC-OKI-4P 12/0 0.02 10

54.6.5. Is it possible to extract clock synchronization from BRIO

cards?
No, it isn't, because BRIO cards haven't the H.100 bus.

54.6.6. How can I view if the Abilis USB ports are enabled?
Type the d pcidev command and verify that the USB CONTROLLER UHCI string is present and there is a value in the Irq
column. For example:

[11:38:04] ABILIS_CPX:d pcidev

PCI Server Overview:

ID Vendor Device CardName Slot/F Ver Irq

-------------------------------------------------------------------------------
0 8086 INTEL 7190 BRIDGE HOST - 0/0 0.03 -
1 8086 INTEL 7191 BRIDGE PCI - 1/0 0.03 -

1020
Draft FAQ - Frequently Asked Questions Draft

2 8086 INTEL 7110 BRIDGE ISA - 7/0 0.02 -

3 8086 INTEL 7111 STORAGE IDE - 7/1 0.01 -
4 8086 INTEL 7112 USB CONTROLLER UHCI - 7/2 0.01 9
5 8086 INTEL 7113 BRIDGE OTHER - 7/3 0.02 -
6 10EC REALTEK 8139 NETWORK ETHERNET TE100-PCIWN 8/0 1.00 10
7 10EC REALTEK 8139 NETWORK ETHERNET TE100-PCIWN 9/0 1.00 5
8 1283 ITE 8872 16550 SERIAL PORT PCI-POTS 11/0 0.01 9
9 10B5 PLX TECHNO 9050 BRIDGE OTHER CTI-HFC-OKI-4P 12/0 0.02 10

54.6.7. Why do I get the error “RESOURCE NOT PRESENT OR NOT

RUNNING” when I initialize a resource?
The error “RESOURCE NOT PRESENT OR NOT RUNNING” is generated when you try to initialize a resource that is not
yet running. To make the resource running, it is required to restart the Abilis.

For example:

[11:38:04] ABILIS_CPX:init res:ip-7

RESOURCE NOT PRESENT OR NOT RUNNING

[11:38:09] ABILIS_CPX:d p ip-7

RES:Ip-7 - Not Refreshed (INIT) -----------------------------------------------

- IP over IP (Abilis tunnel) (AIPT) ------------------------------------
New DESCR:
OPSTATE:UP IPLOG:NO
...

A new resource is identified by the “New” string; a running resource is identified by the “Run” string.

With the d run command, it is possible to display all the running resource. If the resource is not present in the list, it is
needed to restart the Abilis.

54.6.8. How can I change the Abilis prompt name?

The Abilis prompt is named by default with the “ABILIS_CPX” string. To modify it type:

s p cp pi:new_name Change the prompt name.

save conf Save the configuration.

54.7. Tunnelling
54.7.1. How can i have information about the use of ISDN backup?
There are several things which can be checked:

• tunneling diagnostics;

• tunnelling statistics:

SUCC-CALL shows the number of successful calls made using the ISDN backup;

TIME-CALL shows the using total time of ISDN backup.

[11:09:16] ABILIS_CPX:d s pv-1

RES:Pv-1 - PV over IP (Abilis tunnel) with Abilis Back-up (IP-BCK) ------------

To_Abilis_2
--- Cleared 14 days 23:14:00 ago, on 03/12/2007 at 03:22:29 ------------
- Link -----------------------------------------------------------------
PLINK-DN1:0 PLINK-DN2:6

1021
Draft FAQ - Frequently Asked Questions Draft

SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0

RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
FAIL-CALL | 0| 0|SUCC-CALL | 0| 0|
TIME-CALL | 0| 0| | | |
V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0|
V-BAD-CIPH | 0| |D-BAD-CIPH | 0| |
------------------------------------------------------------------------
- IP Tunnel ------------------------------------------------------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
CHR | 21550200| 25131315|FRM | 1430094| 1603480|
IP-CHR | 52462731| 65112357|IP-FRM | 858376| 943377|
BAD-SRC | 1| |NO-SERV | 0| |
NO-CRKEY | 0| 0|BAD-CIPH | 0| 0|
CLI-TOUT | 0| |CLI-REMAP | 0| |
-----------|--DATA IN--|-VOICE-IN--|-CHECK IN--|-----------------------|
MISSING | 0| 36| 0|
NOBUF | 0| 0| 0|
------------------------------------------------------------------------
-- Time arrival variation of voice frames after reordering (msec.) -----
------------------------------------------------------------------------
0- 20 | 1125539 ( 98% ) | 151-200 | 67 ( 0% ) |
21- 50 | 18492 ( 1% ) | 201-300 | 55 ( 0% ) |
51-100 | 794 ( 0% ) | 301-600 | 34 ( 0% ) |
101-150 | 171 ( 0% ) | 601-xxx | 2 ( 0% ) |
------------------------------------------------------------------------

• system log: informs about the state of tunnels. If the LLOG parameter of the PV/AIPT resource is set to ALL+E, the time
when the ISDN backup is used is stored in the system log.

54.8. IPSEC
54.8.1. Why the outgoing traffic from CPX toward an IPSEC vpn is
blocked after updating from 6.5.x to 7.0.x?
The interaction between NAT and IPSEC changes updating from 6.5.x to 7.0.x and this may cause the outgoing traffic
blocking.

Example: assuming to have:

• an INSIDE tunnel whose traffic goes out through an OUTSIDE interface;

• a NAT rule for the OUTSIDE interfaces used by the INSIDE tunnel;

the ip addresses belonging to that tunnel must not to be involved in the NAT rule.

The following is the configuration of ike hosts and ike clients:

[19:41:29] ABILIS_CPX:d ike host

----------------------------------------------------------------------------
HOST: NAME: LOC-IP: NATT: XAUTH:
AUTH: HASH: DH: CIPHER: REM-IP: SIDE:
MODE-CFG:
XAUTH-USER: XAUTH-PWD:
----------------------------------------------------------------------------
1 SOFTMEDIDC 012.034.065.078 SYS NO
PSK MD5 MODP1024 3DES xxx.xxx.xxx.xxx INSIDE NO

----------------------------------------------------------------------------
2 SOFTMEDLAB 012.034.065.078 SYS NO
PSK MD5 MODP1024 3DES xxx.xxx.xxx.xxx INSIDE NO

1022
Draft FAQ - Frequently Asked Questions Draft

----------------------------------------------------------------------------
3 SOFTMEDBCK 012.034.065.078 SYS NO
PSK MD5 MODP1024 3DES xxx.xxx.xxx.xxx INSIDE NO

----------------------------------------------------------------------------
4 MATTEO 012.034.065.078 SYS NO
PSK MD5 MODP1024 3DES xxx.xxx.xxx.xxx INSIDE NO

----------------------------------------------------------------------------
5 SMHOUSING 012.034.065.078 SYS NO
PSK MD5 MODP1024 3DES xxx.xxx.xxx.xxx INSIDE NO

----------------------------------------------------------------------------

[19:45:07] ABILIS_CPX:d ike cli

----------------------------------------------------------------------------
CLI: NAME: HOST-ID: RULE: LIFE-TIME:
PFS:
ESP: ESP-CIPHER: ESP-AUTH: PASSIVE: PERMANENT: NET-LOC:
AH: AH-AUTH: TUNNEL: NET-REM:
MODE-CFG-DNS:
----------------------------------------------------------------------------
1 NAME1 1 IPSEC 28800 NO
YES DES MD5 NO YES
192.168.002.064/28
NO MD5 YES
192.168.010.000/24
SYS
----------------------------------------------------------------------------
2 NAME2 2 IPSEC 28800 NO
YES DES MD5 NO YES
192.168.002.064/28
NO MD5 YES
192.168.011.010/32
SYS
----------------------------------------------------------------------------
3 NAME3 3 IPSEC 86400 NO
YES DES MD5 NO YES
192.168.002.064/28
NO MD5 YES
192.168.014.000/24
SYS
----------------------------------------------------------------------------
4 NAME4 4 IPSEC 86400 NO
YES DES MD5 NO NO
192.168.002.064/28
NO MD5 YES
172.016.015.000/24
SYS
----------------------------------------------------------------------------
5 NAME5 5 IPSEC 86400 NO
YES DES MD5 NO YES
192.168.002.064/28
NO MD5 YES
192.168.026.102/32
SYS
----------------------------------------------------------------------------

Create a list of private ip and a list of public ip:

[19:41:14] ABILIS_CPX:d list:PrivateIp

1023
Draft FAQ - Frequently Asked Questions Draft

LIST:PrivateIp - IR

010.000.000.000:010.255.255.255 172.016.000.000:172.031.255.255
192.168.000.010:192.168.255.255

[19:41:22] ABILIS_CPX:d list:PublicIp

LIST:PublicIp - RU

NOT.PrivateIp

Exclude private ip addresses from the NAT rule used by the tunnel setting the DNET parameter to 'PublicIp':

[19:41:28] ABILIS_CPX:d nat

UPNP maps not present

Configured maps
----------------------------------------------------------------------------
PR: [DESCR:]
INAT: ADD: SNET: DNET: ANET:
ONAT: SPO: DPO: APO:
PAT:
SIP: DIP: PROT: TOUT:
----------------------------------------------------------------------------
0 IN SRC 192.168.002.064/28 192.168.001.001/32 Ip-1
OUT * * AUTO
YES
----------------------------------------------------------------------------
1 IN SRC 192.168.002.064/28 'PublicIp' Ip-3
OUT * * AUTO
YES
----------------------------------------------------------------------------

54.9. CTISMS
54.9.1. Can SMS to Email be sent an SMTP server different from the
Abilis one?
SMS to Mail can be sent to ANY recipient. The Abilis SMTP can send mails:

• to the SMTP server resolved by MX record of DNS;

• to a SMTP relay server (e.g. that of ISP or company).

54.9.2. Can SMS also send CC: and BCC:?

Not in current implementation. Sender may specifiy at beginning of SMS one or more recipients separated by comma and
sms will be sent to those recipients.

54.9.3. Can SMS to Email or Email to SMS be more than 160

characters?
Yes. In Email to SMS a message can be splitted in up to 4 SMS (MAX-SMS-SPLIT parameter [default value 1]). In SMS to
Email several messages can be reassembled, the limit of the mail (including headers) is 2048 byes.

54.9.4. Are attachments supported for email to SMS?

Attachments are actually ignored.

1024
Draft FAQ - Frequently Asked Questions Draft

54.9.5. Can SMS be send thru a dialing plan to take advantage of

cheaper or marketing promo when sending SMS within the same
Telco?
Yes. The CTISMS OUT routing table allows to choose the outgoing port, depending on the number to which the message has
to be sent and/or the sender's email.

54.10. UMTS Box

54.10.1. How can I improve the quality of the calls with UMTS Box?
To ensure high quality for calls with UMTS Box, it is needed to verify that:

1. The Silence Compression is not enabled (SC:NO in the setting of CTISYS resource, or if SC:NO in the CTI Routings that
are used by the UMTS BOX).

2. The GSM/UMTS signal (SIGNAL parameter) is sufficient; to show the available signal, type the d d ctip:<xxx>
command, where <xxx> is the number of the CTIP port associated to the SIM card that you want to monitorate.

[19:03:49] ABILIS_CPX:d d ctip:201

CTIP:201 ----------------------------------------------------------------------
SIM-1
OPSTATE:UP STATE:UP
------------------------------------------------------------------------
CH: STATE: [Q932-STATE:] CG: [SG:] CD: [SD:]
------------------------------------------------------------------------
*** All channels disconnected ***
------------------------------------------------------------------------
VOICE-STATE:READY PDN-STATE:READY SMS-STATE:READY
------------------------------------------------------------------------
NET:Operator-1 ROAMING:NO NET-MODE:GSM
SIGNAL:29 SIGNAL-dbm:-95 RXQUAL:0
IMEI:xxxxxxxxxxxxxx IMSI:22288141316922 SIM:N/A
PWR-CONS-mA:N/A TEMP-Celsius:N/A
CELL:CONNECTED CELL-STATE:READY CELL-ERR:NONE
CODEC:CONNECTED CODEC-STATE:READY CODEC-ERR:NONE
SIMEMU:CONNECTED SIMEMU-STATE:READY SIMEMU-ERR:NONE

Signal ranges (the maximum value is 30):

• 0-10: the signal is not sufficient; the UMTS Box doesn't work correctly.

• 11-13: the signal is low; the UMTS Box can have some problems.

• 14-20: the signal is good.

• 20-30: the signal is high and the UMTS Box works correctly.

3. DJ:0 and MJ:80 in the CTIR routing used by UMTS Box in order to reduce the delays of packets.

Tip
It is possible to increase the call volume setting the CELL-GAIN-IN and CELL-GAIN-OUT parameter in
the CTISYS resource.

...
- CELL (GSM/UMTS) defaults ---------------------------------------------
CELL-GAIN-IN:0 CELL-GAIN-OUT:0 pdn-rxbuf:30
CELL-CODEC-GAIN-IN:0 CELL-CODEC-GAIN-OUT:0
- CITOBOX defaults -----------------------------------------------------
...

1025
Draft FAQ - Frequently Asked Questions Draft

54.10.2. How does Abilis manage the PIN code of a SIM card?
It is possible to set the PIN code of a SIM card in the PIN parameter of its related CTIP port.

[19:10:24] ABILIS_CPX:d p ctipe:201

Act card:UG-1<1>
Run OPSTATE:UP LOG:DS TYPE:USER
signalling:CELL
mode:CELL VOICE-ROAMING:DISABLED NUM:*
PDN-MODE:AUTO PDN-ROAMING:DISABLED
PDN-APN:tre.it
LOOP:NO PIN:1234 GAIN-IN:+9 CODEC-GAIN-IN:SYS
DIALT:5 PIN2:# GAIN-OUT:SYS CODEC-GAIN-OUT:SYS
RSIM:NO
LCS-GROUP:NONE

Caution
If you change the position of the SIM card in the UMTS Box, you must modify the PIN parameter in the
CTIP port.

It is ALWAYS better to remove the PIN code from the SIM card because Abilis inserts it into the SIM for each init ctisys
command.

In order to avoid that the SIM card gets blocked, Abilis can insert the PIN code for maximum 2 times. If the value in the PIN
parameter is changed with another one wrong, the card gets blocked.

To unlock the SIM card, it is needed to insert the PUK code using the following DEBUG command:

debug res:ctisys cmd:l1pxxxtkyyyyyyyy lsn:254, where xxx is the number of the CTIP port and yyyyyyyy is the PUK code
(PUK code has to be always 8 digits number).

The PUK code enter takes some time, so the CP response isn't immediate. The response then should be:

[19:12:02] ABILIS_CPX:debug res:ctisys cmd:l1p201tk12345678 lsn:254

RES:CtiSys --------------------------------------------------------------------
CTI_System_general_properties
BufferLength:63 Date/Time:03/10/2007 14:12:25 TraceTime:219355

PUK code 12345678 sent into the GSM module.

New PIN is 1234

1026
Draft Draft

Part VI. Separate software tools

Draft Draft

Table of Contents
55. CPX accounting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1. CPX accounting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.1. Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.2. Extractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
55.2. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040
56. IPSEC clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1. TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.1. Installing TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.2. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.3. Configuring The Greenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
57. PPPoE clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1. RASPPPoE driver for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.1. Installing RASPPPOE drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.2. Creating PPPoE Dial-Up connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.2. Routers with PPPoE support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
58. Softphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1. Zoiper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.1. Zoiper installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.2. Creating an IAX account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
58.1.3. Creating a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055

1028
Draft Draft

Chapter 55. CPX accounting software

Marco Bellesia

Table of Contents
55.1. CPX accounting software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.1. Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
55.1.2. Extractor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
55.2. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1040

55.1. CPX accounting software

Cpx accounting software is a Windows 2000/XP/Vista/7 application suite which provides the possibility to monitor every call
handled by one or more Abilis CPXs.

It consists of an agent running in Abilis CPX plus collector and extractor applications running on a Windows platform.

Software download: go to Abilis technical website - Accounting download1, select the software Release and download the
Acnt-X-Y-Z.exe file (X.Y.Z stands for the release number).

Extract the Collect (Collect.exe) and Extractor (Extract.exe) programs by double-clicking the Acnt-X-Y-Z.exe
file.

Note
Access to download section is restricted, before proceeding you need to obtain a valid username/password
from Abilis technical support (<[email protected]>).

Tip
It is reccomended to create a shortcut of Collect.exe and Extract.exe files into the Startup
directory: in this way the connection with Abilis is automatically activated at the Windows startup.

55.1.1. Collector
It collects information about phone/data calls made on Abilis and realizes a TCP connection between the PC and the
monitored Abilis on port 2060.

Note
To make the connection running, it is needed to activate the ACNT resource in Abilis.

55.1.1.1. Configuring a connection to Abilis

1. To start the program double-click the Collect.exe file.

2. Go to Connections menu and select Add CPX to list.

1
http://abilis.antek.it/downloads/cpx-acnt/download.html

1029
Draft CPX accounting software Draft

In the Change connection parameters window, configure the following fields:

• CPX Name: name of the Abilis CPX (it is just a label).

• Remote host or IP address: IP address of the Abilis CPX to monitor.

• Remote TCP port: 2060 is the default value; the ACNT resource on Abilis uses that TCP port.

• Connect automatically at startup: if it is selected, the connection to Abilis CPX is generated automatically at the
program start-up; if it is not selected, the connection must be manually done by choosing Connect to CPX form
Connections menu.

1030
Draft CPX accounting software Draft

Click the OK button to confirm.

3. This is the result:

1031
Draft CPX accounting software Draft

The Connected State indicates that the connection with the Abilis is active and the program is ready to collect
information.

4. Go to Options menu and select Application settings.

1032
Draft CPX accounting software Draft

In Autosaving tab, select Use autosave, the save frequency (by default is set up to Daily) and the time to save (by default
is set up to 23.59); at this date, the calls will be saved in a yyyy-mm-dd---hh-mm.dat file placed in the same
directory of Collect.exe.

1033
Draft CPX accounting software Draft

Click the OK button to confirm.

55.1.1.2. Showing call events

Right-click the connection icon in the list and select Show call events. This function shows the basic information of the calls
passed through the Abilis from the begin of the connection of the Collector to the Abilis (calling number, called number,
duration, date/time of disconnection, etc..).

• The last calls are on the bottom of the window.

• Unsuccessful calls are grey highlighted.

1034
Draft CPX accounting software Draft

• Clicking over on an entry shows all call information.

1035
Draft CPX accounting software Draft

1036
Draft CPX accounting software Draft

Note
The following icon in the desktop bar shows that the collector is running.

55.1.2. Extractor
Extractor is a program dedicated to export in TXT format information saved by the Collector program. The TXT file created
can be imported with a datasheet (i.e. Excel).

55.1.2.1. Configuring Autoextract function

1. To start the program double-click the Extract.exe file.

2. Go to Settings menu, and select Settings.

3. In Default mask tab, select the AllFields.msk file.

1037
Draft CPX accounting software Draft

Click the OK button to confirm.

4. In Autoextract tab, configure the following fields:

• Use autoextract: if it is selected, the DAT files will be automatically converted in TXT format (it will be also created
a backup file .BCK). The program with a configurable frequency (by default is set up to 10 minutes) will check if new
DAT files have been created.

• Path to monitor: directory where the program searches the DAT files.

• Mask to use: mask used to convert the DAT files.

Click the OK button to confirm.

55.1.2.2. Manually extracting DAT files

Click the Open button and select the DAT (or BCK) file that you want to convert: summary information will be shown about
the number of good and failed calls, the type of the call, etc...

1038
Draft CPX accounting software Draft

• If you click the Extract with default mask button, the file will be exported in TXT format, with the default mask, specified
in the Settings menu.

• If you click the Extract button, a new window allows to select the fields to insert in the mask or to load an existing mask.
When the mask has been defined, click the Export button to create a TXT file.

1039
Draft CPX accounting software Draft

55.2. Appendix
Main characteristic of CPX accounting software:

• All calls are listed (both successful and unsuccessful, outgoing or incoming); unsuccessful calls report the reason of failure.

• The complete information is filed: date and time, calling and called numbers, type of call (transparent or VoIP, voice or
data or fax...), bandwith used, jitter and packet loss specific for each call, subaddresses, etc..

• One host can receive the CDRs of many Abilis at the same time.

• For backup purposes, multiple hosts can receive the CDRs from the same Abilis.

• Data can be received through an encrypted TCP/IP connection.

1040
Draft Draft

Chapter 56. IPSEC clients

Marco Bellesia

Table of Contents
56.1. TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.1. Installing TheGreenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.2. Checklist of parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
56.1.3. Configuring The Greenbow IPSEC VPN client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

56.1. TheGreenbow IPSEC VPN client

56.1.1. Installing TheGreenbow IPSEC VPN client
Go to http://www.thegreenbow.com/ and download TheGreenbow IPSEC VPN client from Products > VPN Client >
Download1 section.

Double-click the downloaded file and install the program following the instructions.

56.1.2. Checklist of parameters

These tables show the parameters of TheGreenbow and their corresponding parameters in Abilis configuration. The
information must be inserted in a “mirror” way: i.e. “LOCAL” information for Abilis are “REMOTE” for IPSEC client and
vice versa.

Table 56.1. Phase 1 parameters

The Greenbow parameter Abilis IKE Table Abilis IKE Table parameter
Name HOST NAME
Interface HOST REM-IP
Remote Gateway HOST LOC-IP
Preshared Key PSK KEY
Encryption HOST CIPHER
Authentication HOST HASH
Key Group HOST DH
Local ID (Advanced parameter) HOST ID-TYPE
Local ID Value (Advanced parameter) HOST IP or FQDN
Remote ID (Advanced parameter) HOST PEER-ID-TYPE
Remote ID Value (Advanced HOST PEER-IP or PEER-FQDN
parameter)

1
http://www.thegreenbow.com/vpn_down.html

1041
Draft IPSEC clients Draft

Table 56.2. Phase 2 parameters

The Greenbow parameter Abilis IKE Table Abilis IKE Table parameter
Name CLI NAME
VPN Client address CLI NET-REM
Address type CLI
Remote host address CLI NET-LOC
Subnet Mask CLI NET-LOC
Encryption CLI ESP-CIPHER
Authentication CLI ESP-AUTH
Mode CLI TUNNEL

56.1.3. Configuring The Greenbow IPSEC VPN client

Suppose that Abilis is configured in the following way. Refer to Section 52.11.1, “How to configure a RAS using IPSEC
VPN server” for the configuration of IPSEC and IKE resources.

[22:54:53] ABILIS_CPX:d ike host:0

Parameter: | Value:
------------+------------------------------------------------------------------
HOST: 0
NAME: user_1
LOC-IP: 080.080.080.080
REM-IP: *
IPRES: 4
AUTH: PSK
HASH: MD5
DH: MODP1024
CIPHER: 3DES
SIDE: INSIDE
KEYING-TRIES: 3
LIFE-TIME: 3600
DPD-ENABLE: NO
DPD-DELAY: 30
DPD-TIMEOUT: 120
DPD-ACTION: STOP
ID-TYPE: IP
IP: 080.080.080.080
PEER-ID-TYPE: IP
PEER-IP: 192.168.200.001
-------------------------------------------------------------------------------

[22:54:53] ABILIS_CPX:d ike psk:0

Parameter: | Value:
------------+------------------------------------------------------------------
PSK: 0
KEY: ********
ID-TYPE: ANONYMOUS
-------------------------------------------------------------------------------

[22:54:53] ABILIS_CPX:d ike cli:0

Parameter: | Value:
------------+------------------------------------------------------------------
CLI: 0
NAME: user_1
HOST-ID: 0

1042
Draft IPSEC clients Draft

RULE: IPSEC
PASSIVE: YES
PERMANENT: YES
TUNNEL: YES
ESP: YES
ESP-CIPHER: 3DES
ESP-AUTH: MD5
AH: NO
AH-AUTH: MD5
LIFE-TIME: 28800
PFS: YES
NET-LOC: 192.168.001.000/24
NET-REM: 192.168.200.001/32
-------------------------------------------------------------------------------

Execute TheGreenbow program: the following window will appear.

1043
Draft IPSEC clients Draft

Configuration of Phase 1.

• Right click on Configuration, and select New phase 1.

• Configure Phase 1 as shown here below.

• Click the Advanced… button and configure the following window as explained.

1044
Draft IPSEC clients Draft

• Click the OK button to close the window.

• Click the Save & Apply button to save and initialize the changes made.

Configuration of Phase 2.

• In the main window right click on the selected Phase 1 and and select Add Phase 2.

• Configure Phase 1 as shown here below and click the Save & Apply button to save and initialize the changes made.

1045
Draft IPSEC clients Draft

• Then click the Open Tunnel button to open the VPN.

• When the VPN is active the “Tunnel” light at the bottom becomes green. It is possible to display the status of the
connection by clicking on Connections: this window will be shown.

1046
Draft IPSEC clients Draft

• To close the Tunnel, click the Close Tunnel button.

Tip
Interesting chapter: Section 52.11, “How to configure a Remote Access Server (RAS)”.

1047
Draft Draft

Chapter 57. PPPoE clients

Nicola Trevisani

Table of Contents
57.1. RASPPPoE driver for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.1. Installing RASPPPOE drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.1.2. Creating PPPoE Dial-Up connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
57.2. Routers with PPPoE support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049

57.1. RASPPPoE driver for Windows

57.1.1. Installing RASPPPOE drivers
Go to http://www.raspppoe.com/ and download RASPPPOE driver from Download & install1 section.

1. Extract the RASPPPOE driver file.

2. If you are running Windows 2000, right-click the My Network Places icon on your desktop and select Properties to bring
up the Network and Dial-up Connections window.

If you are running Windows XP/2003, click the Start button, select Control Panel, then click Network and Internet
Connections and then click the Network Connections control panel icon to bring up the Network Connections window. Go
to the menu and select View then Details to get a detailed view of the network connections on your machine.

3. You should find one or more Local Area Connection objects. Locate the one for the network adapter for which you want
to install PPPoE driver, right-click it and select Properties.

4. In the Properties dialog box, click the Install... button.

5. In the Select Network Component Type window, select Protocol and click the Add... button. (Note: It could take a few
seconds for the following window to come up.)

6. In the Select Network Protocol window, click the Have Disk... button.

7. In the Install From Disk window, either type the name of your temporary installation directory or click the Browse...
button to navigate to it (it does not matter which of the INF files you select, Windows will automatically pick the right one
later). Then click the OK button. A new window opens, offering the PPP over Ethernet Protocol for installation. Click OK
to start installing the protocol.

8. During installation, a window titled Digital Signature Not Found (Windows 2000) or Hardware Installation (Windows
XP/2003) may come up several times (typically four times per installed network adapter), warning you that the driver
has no digital signature or Windows Logo. Make sure you click Yes (Windows 2000) or Continue Anyway (Windows
XP/2003) every time you are prompted to allow successful installation of the protocol.

9. Back at the Local Area Connection Properties window, click Close to close the window.

57.1.2. Creating PPPoE Dial-Up connections

Follow these instructions.

1. Click the Start button on the taskbar and select Run....

2. Into the Run dial-box type raspppoe and click the OK button to run the Dial-Up connection Setup application.

3. A dialog box comes up with a combo box labeled Query available PPP over Ethernet Services through Adapter: at the top.
Select the network adapter from the list. If the protocol is only operating on one network adapter, the box will be grayed
out as there is no choice to make.

1
http://www.raspppoe.com/conf.php

1048
Draft PPPoE clients Draft

There are two connection modalities:

• Connection WITHOUT “SERVICENAME” indication (Dynamic IP Address):

• Click the Create a Dial-Up Connection for the selected Adapter button. Shortly afterwards, a shortcut to the new dial-
up connection named Connection through <Adapter Name> should show up on your desktop.

• After you have created the connection(s) you need, click the Exit button to quit the application.

• Connection WITH “SERVICENAME” indication (Static IP Address):

• Click the Create a Dial-Up Connection for the selected Adapter button. Shortly afterwards, a shortcut to the new dial-
up connection named Connection through <Adapter Name> should show up on your desktop.

• After you have created the connection(s) you need, click the Exit button to quit the application.

• Double-click the desktop icon for the dial-up connection you created.

• Click the Properties button.

• In Telephone Number field the ACNAME parameter configured in Abilis should be already present. If it is
not present, insert it and after “\” add the SERVICENAME configured in Abilis. (e.g. for ACNAME:wlan and
SERVICENAME:user_1, the Telephone Number will be: wlan\user_1).

• Click OK button to confirm.

4. Double-click the desktop icon for the dial-up connection you created.

5. In the Connection to <Connection Name> window, enter the USERNAME and PASSWORD configured in Abilis (USER
and PWD parameter in the Users Table).

6. Click the Dial button to start the connection.

Tip
For more information go to http://www.raspppoe.com/.

Tip
Refer to Section 52.11.3, “How to configure a RAS using PPPoE connections with an Ethernet/WiFi
network” to know how to configure Abilis.

57.2. Routers with PPPoE support

It is enough to insert the USERNAME and PASSWORD configured in Abilis (USER and PWD parameter in the Users
Table). If it is needed, set up the SERVICENAME parameter configured in Abilis.

For more information refer to the manual of the device.

1049
Draft Draft

Chapter 58. Softphones

Marco Bellesia

Table of Contents
58.1. Zoiper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.1. Zoiper installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
58.1.2. Creating an IAX account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
58.1.3. Creating a SIP account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055

58.1. Zoiper
58.1.1. Zoiper installation
Download Zoiper from http://www.zoiper.com/ and install it on a PC. For the instructions about the installation and the
configuration refer to Zoiper manual1.

When you start Zoiper this window appears.

You can access the Options Menu in three ways:

• right click on the ZOIPER icon in the system tray or on the phone itself and select Options submenu;

• press Alt+O on your keyboard;

• click the Options button.

In all cases the Zoiper Options screen will pop up.

The first step is to configure Audio devices: suggested value is the audio board.

1
http://www.zoiper.com/support.php

1050
Draft Softphones Draft

Note
The following icon in the system tray shows that Zoiper is running.

58.1.2. Creating an IAX account

Click on Add new IAX account and insert the name of the IAX user in the Name text box (e.g. iax_phone):

1051
Draft Softphones Draft

Click the OK button and complete account parameter with:

• Server Hostname/IP: Abilis IP address (configure the private IP address if the user is registered in the Abilis private side or
the public IP address if the user is registered in the Abilis public side).

• Username: the value of USER parameter in the Abilis Users Table;

• Password: the value of PWD parameter in the Abilis Users Table.

1052
Draft Softphones Draft

Click the OK button to confirm.

If the IAX user is already registered onto Abilis, the string Registered appears in the Account check box. The user can be
unregistered by clicking the Unregister button.

1053
Draft Softphones Draft

Note
To manually start the registration, select the user in the Account check box and press the Register button.

Type the following command to verify if the registration is correct:

[22:02:33] ABILIS_CPX:debug res:ctiiax lsn:4

RES:CtiIax --------------------------------------------------------------------
Inter-Asterisk_eXchange_Version_2
BufferLength:324 Date/Time:08/04/2008 10:52:23 TraceTime:<NotRunning>

User Host Port REG LIFETIME AGE

-------------------------------------------------------------------------------
iax_phone 192.168.001.155 4569 LOCAL 60 8
-------------------------------------------------------------------------------

If an entry exists for the “iax_phone” user, the registration is successful and the user is able to make calls.

1054
Draft Softphones Draft

To make a call simply digit a number in Phone to dial text box and press the Dial button (the first button from left under the
text box).

Tip
Interesting chapter: Section 45.6.3, “Debug of the CTIIAX resource”.

58.1.3. Creating a SIP account

Click on Add new SIP account and insert the name of the SIP user in the Name text box (e.g. sip_phone):

Click the OK button and complete account parameter with:

• Domain: Abilis domain or IP address (configure the private IP address if the user is registered in the Abilis private side or
the public IP address if the user is registered in the Abilis public side).

• Username: the value of USER parameter in the Abilis Users Table;

• Password: the value of PWD parameter in the Abilis Users Table.

1055
Draft Softphones Draft

Click the OK button to confirm.

Note
If the user is registered in the Abilis public side, you must enable a valid STUN server (e.g.
stun.zoiper.com).

1056
Draft Softphones Draft

If the SIP user is already registered onto Abilis, the string Registered appears in the Account check box. By clicking the
Unregister button, it is possible to unregister the user.

1057
Draft Softphones Draft

Note
To manually start the registration, select the user in the Account check box and press the Register button.

To verify if the registration is correct, type the command:

[22:02:33] ABILIS_CPX:debug res:ctisip lsn:4

RES:CtiSip --------------------------------------------------------------------
Session_Initiation_Protocol
BufferLength:405 Date/Time:08/04/2008 11:35:39 TraceTime:<NotRunning>

User Host Prot Port REG LIFETIME AGE

-------------------------------------------------------------------------------
sip_phone 192.168.001.155 UDP 5060 LOCAL 120 9
-------------------------------------------------------------------------------

If an entry exists for the “sip_phone” user, the registration is successful and the user is able to make calls.

1058
Draft Softphones Draft

To make a call simply digit a number in Phone to dial text box and press the Dial button (the first button from left under the
text box).

Tip
Interesting chapter: Section 46.7.3, “Debug of the CTISIP resource”.

1059
Draft Draft

Part VII. References

Draft Draft

Table of Contents
59. List of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
59.1. Complete list of On-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
59.2. Complete list of Off-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
60. Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
60.1. System Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
61. Disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1. ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.1. ISDN disconnection codes recommended by ITU (formerly CCITT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.2. Abilis CPX private ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
61.2. X.25 disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.1. ITU (formerly CCITT) X.25 codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.2. Abilis CPX internal codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084

1061
Draft Draft

Chapter 59. List of Commands

Nicola Trevisani
Marco Bellesia

Table of Contents
59.1. Complete list of On-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
59.2. Complete list of Off-line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070

59.1. Complete list of On-line Commands

Here below is reported the complete list of available commands on a running Abilis for the SUPERUSER login.

[11:26:53] ABILIS_CPX:??

List of commands allowed for SUPERUSER login:

Alarm operations:
ALARM VIEW Alarm view
ALARM RESET Alarm reset

Add operations:
A CRKEY: Encryption/Decryption key identifier [1..63]
A CF CF/DND (Call forwarding/Do-Not-Disturb) entry
A CONTACT Address Book
A CTIB CTI channels bundle
A CTICL CTI cluster
A CTIDISA CTI DISA Users and Services
A CTIG CTI group
A CTIH323 CTI H.323 Translation entry
A CTIIAX CTIIAX numbers table entry
A CTIL CTI link
A CTILG CTI group of links
A CTIPC CTI permanent connection
A CTIR CTI routing
A CTIRE CTI routing
A CTIRR CTI routing
A CTISIP CTISIP numbers table entry
A CTISMS CTI SMS routings for incoming/outgoing messages
A DEV: HW device identifier 'type-n', where 'n' can be [1..255]
A DHCP DHCP profile/subnet/host
A DNS DNS server and relay tables
A FTP FTP Virtual root paths/path's access Rights
A GROUP: Group name. Max. 32 ASCII characters.
A HTTP HTTP Virtual root paths/path's access Rights
A IKE IKE Host/Client connections and preshared keys tables
A IPACL IP Access List
A IPAD IP Routing Administrative Distance
A IPLB IP Load Balancing entry
A IPR IP Routing
A IPSEC IPSEC Security policies and associations tables
A LCSG Last Calling Number Service group
A LCST Last Calling Number Service table entry
A LIST: CPX list name
A NAT NAT alias entry

1062
Draft List of Commands Draft

A OSPF OSPF area/range/neigh/host/external route

A PVC PVC Connection
A R SVC Routing
A RES: Resource identifier 'type-n', where 'n' can be [1..999]
A RIP RIP external route
A USER: User name. Max. 32 ASCII characters.
A VRRP VRRP Routers
A WGB WG Bridge Routing

Boot operations:
BOOT DEV: HW device identifier 'type-n', where 'n' can be [1..255]

Clear operations:
C C COR connection
C CF CF/DND (Call forwarding/Do-Not-Disturb) entry
C CL CTI incoming/outgoing calls logs
C CODE Cause and diagnostic codes
C CONTACT Address Book
C CRKEY: Encryption/Decryption key identifier [1..63]
C CTIB CTI channels bundle
C CTIC CTI connections
C CTICL CTI cluster
C CTIDISA CTI DISA Users and Services
C CTIG CTI group
C CTIH323 CTI H.323 Translation entry
C CTIIAX CTIIAX numbers table entry
C CTIL CTI link
C CTILG CTI group of links
C CTIPC CTI permanent connection
C CTIR CTI routing
C CTIRE CTI routing
C CTIRR CTI routing
C CTISIP CTISIP numbers table entry
C CTISMS CTI SMS routings for incoming/outgoing messages
C DEV: HW device identifier 'type-n', where 'n' can be [1..255]
C DHCP DHCP profile/subnet/host
C DNS DNS server and relay tables
C FTP FTP Virtual root paths/path's access Rights
C GROUP: Group entry
C HTTP HTTP Virtual root paths/path's access Rights
C IKE IKE Host/Client connections and preshared keys tables
C IPACL IP Access List
C IPAD IP Routing Administrative Distance
C IPLB IP Load Balancing entry
C IPR IP Routing
C IPSEC IPSEC Security policies and associations tables
C L System Log
C LCSG Last Calling Number Service group
C LCST Last Calling Number Service table entry
C LDM Debug Log in Memory
C LDME Debug Log in Memory
C LE Exceptions Log
C LIST: CPX list name
C NAT NAT alias entry
C OSPF OSPF area/range/neigh/host/external route
C PVC PVC Connection
C R SVC Routing
C RES: Resource identifier 'type-n', where 'n' can be [1..999]
C RIP RIP external route
C S Status and statistics
C SE Status and statistics
C USER: User entry

1063
Draft List of Commands Draft

C VRRP VRRP Routers

C WGB WG Bridge Routing

Open a Connection:
CALL CTIP: CTI port identifier [1..300]
CALL RES: Resource identifier 'type-n', where 'n' can be [1..999]
CALL USER: User name. Max. 32 ASCII characters.

Open a Connection:
CALLTRY CTIP: CTI port identifier [1..300]
CALLTRY USER: User name. Max. 32 ASCII characters.

CLOSE Close current CP session.

Configuration management:
CONF BACKUP Copy configuration to removable disk
CONF GET Sends the configuration in memory to a remote site
CONF INFO Display/set configuration notes
CONF PUT Receives configuration from a remote site
CONF RELOAD Reload the configuration from a file
CONF RESTORE Alias of the CONFLOG RESTORE command
CONF SAVE Alias of the SAVE CONF command(s)
CONF VALIDATE Alias of the VALIDATE command

Configuration and/or log files backup/restore:

CONFLOG BACKUP Copy configuration and log files to removable disk
CONFLOG RESTORE Load configuration files from removable disk

Address Book:
CONTACT LOAD Import contacts from a CSV file
CONTACT SAVE Export contact to a CSV file

Display operations:
D ACT Active HW device/resource/CTI port
D C COR Connections status
D CE COR Connections extended status
D CF CF/DND (Call forwarding/Do-Not-Disturb) entry
D CL CTI incoming/outgoing calls logs
D CODE ISDN/X.25 codes descriptions
D CONTACT Address Book
D CPU CPU load percentages
D CPUID CPU identification
D CRKEY Encryption/Decryption keys
D CRKEY: Encryption/Decryption key identifier [1..63]
D CTIB CTI channels bundle
D CTIC CTI connections
D CTICE CTI connections in extended format
D CTICL CTI cluster
D CTIDISA CTI DISA Users and Services
D CTIG CTI group
D CTIH323 CTI H.323 Translation entry
D CTIIAX CTIIAX numbers table entry
D CTIL CTI link
D CTILG CTI group of links
D CTIP CTI port
D CTIP: CTI port identifier [1..300]
D CTIPC CTI permanent connection
D CTIPE CTI port in extended format
D CTIPE: CTI port identifier [1..300]
D CTIR CTI routing
D CTIRE CTI routing in extended format
D CTIRR CTI routing in reduced format

1064
Draft List of Commands Draft

D CTISIP CTISIP numbers table entry

D CTISMS CTI SMS routings for incoming/outgoing messages
D D Diagnostics
D DE Diagnostics in extended format
D DESCR Resource's description
D DEV Active/inactive hardware devices
D DHCP DHCP summary/profiles/subnets/hosts
D DNS DNS server and relay tables
D DS Resource diagnostics and statistics
D DSE Resource diagnostics and statistics in extended format
D FTP FTP Virtual root paths/path's access Rights
D G General system parameters
D GROUP Groups of Users table summary
D GROUP: Group entry
D GROUPE Groups of Users table - extended view
D GROUPE: Group entry - extended view
D HTTP HTTP Virtual root paths/path's access Rights
D I System and files information
D IKE IKE Host/Client connections and preshared keys tables
D INACT Inactive HW device/resource/CTI port
D IPACL IP Access List
D IPACLE IP Access List in extended format
D IPAD IP Routing Administrative Distance
D IPLB IP Load Balancing entry
D IPR IP Routing
D IPRS Saved static IP Routing (same of SIPR)
D IPSEC IPSEC Security policies and associations tables
D IPSR IP Source Routing
D ITEM CPX list items
D LIST CPX lists
D LIST: CPX list name
D NAT NAT alias entry
D OSPF OSPF area/range/neigh/host/external route
D SIPR Saved static IP Routing (same of IPRS)
D L System Log
D LCSG Last Calling Number Service group
D LCST Last Calling Number Service table entry
D LDD Debug Log on Disk
D LDDE Debug Log on Disk, extended visualization
D LDM Debug Log in Memory
D LDME Debug Log in Memory, extended visualization
D LE Exceptions Log
D P Resource parameters
D PCIDEV PCI devices
D PREF Preferences
D PSTACK Protocol stack
D PVC PVC Connection
D R SVC Routing
D RE SVC Routing in extended format
D RIP RIP external route
D RUN Running resources/CTI ports/HW devices
D S Statistics
D SE Statistics in extended format
D T System local date, time and time zone
D TE System local date, time and time zone, extended format
D TREE Resources tree
D USBDEV USB devices
D USER Users Access Control table summary
D USER: User entry
D USERE Users Access Control table - extended view
D USERE: User entry - extended view
D VER System and modules versions

1065
Draft List of Commands Draft

D VRRP VRRP Routers

D WGB WG Bridge Routing

Debug operations:
DEBUG BM Display Boot Manager configuration file
DEBUG CPXRUN Display CPX Run configuration file
DEBUG FILE File system information and statistics
DEBUG IRQ Interrupts information and statistics
DEBUG MEM Memory information and statistics
DEBUG PCIDEV Display PCI service debug information
DEBUG PO: CPX port number [0..999]
DEBUG RES: Resource identifier 'type-n', where 'n' can be [1..999]
DEBUG SIMULATE Simulate an event for debugging purposes
DEBUG TASK Tasks information and statistics
DEBUG USBDEV Display USB service debug information
DEBUG WDGMEM Watchdog memory

Close a Connection:
DISC CTIP: CTI port identifier [1..300]
DISC RES: Resource identifier 'type-n', where 'n' can be [1..999]
DISC USER: User name. Max. 32 ASCII characters.

Disabling operations:
DISABLE AC AC connections
DISABLE CTIR CTI connections

EXIT Close current CP session.

Enabling operations:
ENABLE AC AC connections
ENABLE CTIR CTI connections

Find operations:
F BRIDGE Bridge MAC search
F CF CF/DND (Call forwarding/Do-Not-Disturb) searches
F CONTACT Address book
F CTIDISA CTIDISA searches
F CTIIAX CTIIAX numbers search
F CTISIP CTISIP numbers search
F DNS DNS searches
F FTP FTP Virtual root paths/path's access Rights
F HTTP HTTP Virtual root paths/path's access Rights
F IPACL IP Access List
F LCST Last Calling Number Service table entry
F LIST: CPX list name
F LISTE: CPX list name
F USER Users Access Control table summary
F USER: User entry

File copy/delete/get/put operations:

FILE COPY Make a copy of a file
FILE DELETE Delete a file
FILE GET Send a file using XMODEM or XMODEM-1K or ZMODEM
FILE PUT Receive a file using XMODEM or XMODEM-1K or ZMODEM

Shutdown operation:
HALT SYSTEM System shutdown

HELP Detailed topic help.

Init operations:
INIT CTIH323 Refreshes CTI H.323 Translation table content

1066
Draft List of Commands Draft

INIT CTIG Unsupported. Use INIT CTIR to refresh entries in CTI groups
INIT CTIR Refreshes entries in CTI routings, CTIG tables and CTICL list(s)
INIT CTISYS Refreshes parameters of CTISYS resource (RES:CtiSys) and
refreshes entries in CTI ports, clusters and LCS groups
INIT IP Refreshes IP resources and purges queues
INIT IPAD Refreshes IP Routing Administrative Distances
INIT IPLB Refreshes IP Load Balancing definitions
INIT IPR Rebuild IP Routings table
INIT LCSG Unsupported. Use INIT CTISYS to refresh entries in LCS groups
INIT NAT Refreshes the static table and clears the dynamic table content
INIT RES: Refreshes parameters of a resource
INIT USBDEV Refreshes USB Service

TCP/IP Trace operations:

IPTRACE ACT Activate TCP/IP trace
IPTRACE CLEAR Clear the current TCP/IP trace
IPTRACE DISPLAY Display the current TCP/IP trace
IPTRACE INACT Deactivate TCP/IP trace
IPTRACE START Start TCP/IP trace
IPTRACE STOP Stop TCP/IP trace

Licence operations:
LICENCE COMPARE Compare ACTIVE licence and STORED licence
LICENCE DISPLAY Display licences or permissions
LICENCE GET Download ACTIVE licence or STORED licence file
LICENCE PUT Upload STORED licence file
LICENCE SET Enter STORED licence value

Lists operations:
LIST CLEAR Remove all items from a list
LIST CREATE Create a list
LIST DELETE Delete a list
LIST DESCRIPTION Add/Modify list description
LIST DISPLAY Display currently configured lists
LIST EDITABLE Set/Reset list editable flag
LIST RENAME Modify list name

LOGIN Log-in operations.

LOGOUT Log-out operations.

Move operations:
M CF CF/DND (Call forwarding/Do-Not-Disturb) entry
M CTIR CTI routing
M CTIRE CTI routing
M CTIRR CTI routing
M CTISMS CTI SMS routings for incoming/outgoing messages
M IPACL IP Access List
M NAT NAT alias entry
M R SVC Routing

Voice message service:

MSG ADD Voice message(s) adding
MSG DELETE Voice message(s) deleting
MSG DISPLAY Voice message(s) displaying
MSG EXTRACT Voice message(s) extracting
MSG REBUILD Voice message(s) rebuilding
MSG UPDATE Voice message(s) updating

Active parameter operations:

PAR RES: Resource identifier 'type-n', where 'n' can be [1..999]

1067
Draft List of Commands Draft

PING Ping command.

PINGSTAT Ping statistics command.

System Restart operations:

RESTART SYSTEM System restart

Restart operations:
R CTIAC CTI AC DSP(s)
R PVC PVC Connection
R RES: Resource identifier 'type-n', where 'n' can be [1..999]

Set operations:
S ACT Active HW device/resource/CTI port
S CF CF/DND (Call forwarding/Do-Not-Disturb) entry
S CONTACT Address Book
S CRKEY: Encryption/Decryption key identifier [1..63]
S CTIB CTI channels bundle
S CTIDISA CTI DISA Users and Services
S CTICL CTI cluster
S CTIG CTI group
S CTIH323 CTI H.323 Translation entry
S CTIIAX CTIIAX numbers table entry
S CTIL CTI link
S CTILG CTI group of links
S CTIP CTI port
S CTIP: CTI port identifier [1..300]
S CTIPC CTI permanent connection
S CTIPE CTI port
S CTIPE: CTI port identifier [1..300]
S CTIR CTI routing
S CTIRE CTI routing
S CTIRR CTI routing
S CTISIP CTISIP numbers table entry
S CTISMS CTI SMS routings for incoming/outgoing messages
S DEV: HW device identifier 'type-n', where 'n' can be [1..255]
S DHCP DHCP profile/subnet/host
S DNS DNS server and relay tables
S FTP FTP Virtual root paths/path's access Rights
S G General system parameters
S GROUP: Group entry
S GROUPE: Group entry
S HTTP HTTP Virtual root paths/path's access Rights
S IKE IKE Host/Client connections and preshared keys tables
S INACT Inactive HW device/resource/CTI port
S IPACL IP Access List
S IPAD IP Routing Administrative Distance
S IPLB IP Load Balancing entry
S IPR IP Routing
S IPSEC IPSEC Security policies and associations tables
S LCSG Last Calling Number Service group
S NAT NAT alias entry
S OSPF OSPF area/range/neigh/host/external route
S P Resource parameters
S PREF Preferences
S PVC PVC Connection
S R SVC Routing
S RE SVC Routing
S RIP RIP external route
S S Status/Signals
S T System local date and/or time
S USER: User entry

1068
Draft List of Commands Draft

S USERE: User entry

S VRRP VRRP Routers
S WGB WG Bridge Routing

Save operations:
SAVE CONF Current configuration
SAVE DEBUG Debug Log on Disk

Shutdown operation:
SHUTDOWN SYSTEM System shutdown

Sound disable/enable operations:

SOUND DISABLE Disable alarm sound
SOUND ENABLE Enable alarm sound

Start real-time logging operations:

START L System Log
START LDM Debug Log in Memory
START LDME Debug Log in Memory, extended visualization

System operations:
SYS COMPACT Directory re-compacting operation
SYS COMPACTR Directory re-compacting operation, recursive
SYS DELETE Delete operations
SYS DIR List operations
SYS DISK Disk and Volume management
SYS DISPLAY Display operations
SYS SET Set operations
SYS UPDATE Receive a package or a new disk image and update the system

TERM Terminal setting operations.

Testing operations:
TEST DSP DSPs test
TEST H100 H.100 bus test

Trace operations:
TRACE ACT Activate trace
TRACE CLEAR Clear trace
TRACE DELETE Delete trace file
TRACE DISPLAY Trace display operations
TRACE GET Transfer trace
TRACE INACT Deactivate trace
TRACE PARAM Trace parameters operations
TRACE SAVE Save trace on disk
TRACE START Start trace
TRACE STOP Stop trace

TRACERT Trace route command.

TRACEROUTE Trace route command.

Transfer Calls:
TRANSFER CTIP: CTI port identifier [1..300]
TRANSFER USER: User name. Max. 32 ASCII characters.

USB devices management:

USBDEV FW USB device Firmware management

VALIDATE Current configuration validation.

System warm start operations:

1069
Draft List of Commands Draft

WARM START System warm start

Exchange HW device configurations and resource subtypes:

X DEV: List of HW device identifiers joined by ',' character
X RES: Resource identifier 'type-n', where 'n' can be [1..999]

Comments:
# Commands starting with this character will be ignored

59.2. Complete list of Off-line Commands

Here is the complete list of commands offered by the off-line configurator command interpreter for the SUPERUSER login.

[16:35:06] ABILIS_CPX:??

List of commands allowed for SUPERUSER login:

Add operations:
A CRKEY: Encryption/Decryption key identifier [1..63]
A CF CF/DND (Call forwarding/Do-Not-Disturb) entry
A CTIB CTI channels bundle
A CTICL CTI cluster
A CTIDISA CTI DISA Users and Services
A CTIG CTI group
A CTIH323 CTI H.323 Translation entry
A CTIIAX CTIIAX numbers table entry
A CTIL CTI link
A CTILG CTI group of links
A CTIPC CTI permanent connection
A CTIR CTI routing
A CTIRE CTI routing
A CTIRR CTI routing
A CTISIP CTISIP numbers table entry
A CTISMS CTI SMS routings for incoming/outgoing messages
A DEV: HW device identifier 'type-n', where 'n' can be [1..255]
A DHCP DHCP profile/subnet/host
A DNS DNS server and relay tables
A FTP FTP Virtual root paths/path's access Rights
A GROUP: Group name. Max. 32 ASCII characters.
A HTTP HTTP Virtual root paths/path's access Rights
A IKE IKE Host/Client connections and preshared keys tables
A IPACL IP Access List
A IPAD IP Routing Administrative Distance
A IPLB IP Load Balancing entry
A IPRS Saved static IP Routing (same of SIPR)
A IPSEC IPSEC Security policies and associations tables
A IPSR IP Source Routing
A LCSG Last Calling Number Service group
A LIST: CPX list name
A NAT NAT alias entry
A OSPF OSPF area/range/neigh/host/external route
A PVC PVC Connection
A R SVC Routing
A RES: Resource identifier 'type-n', where 'n' can be [1..999]
A RIP RIP external route
A SIPR Saved static IP Routing (same of IPRS)
A USER: User name. Max. 32 ASCII characters.
A VRRP VRRP Routers
A WGB WG Bridge Routing

Boot operations:
BOOT DEV: HW device identifier 'type-n', where 'n' can be [1..255]

1070
Draft List of Commands Draft

Clear operations:
C CF CF/DND (Call forwarding/Do-Not-Disturb) entry
C CRKEY: Encryption/Decryption key identifier [1..63]
C CTIB CTI channels bundle
C CTICL CTI cluster
C CTIDISA CTI DISA Users and Services
C CTIG CTI group
C CTIH323 CTI H.323 Translation entry
C CTIIAX CTIIAX numbers table entry
C CTIL CTI link
C CTILG CTI group of links
C CTIPC CTI permanent connection
C CTIR CTI routing
C CTIRE CTI routing
C CTIRR CTI routing
C CTISIP CTISIP numbers table entry
C CTISMS CTI SMS routings for incoming/outgoing messages
C DEV: HW device identifier 'type-n', where 'n' can be [1..255]
C DHCP DHCP profile/subnet/host
C DNS DNS server and relay tables
C FTP FTP Virtual root paths/path's access Rights
C GROUP: Group entry
C HTTP HTTP Virtual root paths/path's access Rights
C IKE IKE Host/Client connections and preshared keys tables
C IPACL IP Access List
C IPAD IP Routing Administrative Distance
C IPLB IP Load Balancing entry
C IPRS Saved static IP Routing (same of SIPR)
C IPSEC IPSEC Security policies and associations tables
C IPSR IP Source Routing
C L System Log
C LCSG Last Calling Number Service group
C LE Exceptions Log
C LIST: CPX list name
C NAT NAT alias entry
C OSPF OSPF area/range/neigh/host/external route
C PVC PVC Connection
C R SVC Routing
C RES: Resource identifier 'type-n', where 'n' can be [1..999]
C RIP RIP external route
C SIPR Saved static IP Routing (same of IPRS)
C USER: User entry
C VRRP VRRP Routers
C WGB WG Bridge Routing

CLOSE Exit program.

Configuration management:
CONF INFO Display/set configuration notes
CONF RELOAD Reload the configuration from a file
CONF SAVE Alias of the SAVE CONF command(s)
CONF VALIDATE Alias of the VALIDATE command

Display operations:
D ACT Active HW device/resource/CTI port
D CF CF/DND (Call forwarding/Do-Not-Disturb) entry
D CODE ISDN/X.25 codes descriptions
D CRKEY Encryption/Decryption keys
D CRKEY: Encryption/Decryption key identifier [1..63]
D CTIB CTI channels bundle
D CTICL CTI cluster

1071
Draft List of Commands Draft

D CTIDISA CTI DISA Users and Services

D CTIG CTI group
D CTIH323 CTI H.323 Translation entry
D CTIIAX CTIIAX numbers table entry
D CTIL CTI link
D CTILG CTI group of links
D CTIP CTI port
D CTIP: CTI port identifier [1..300]
D CTIPC CTI permanent connection
D CTIPE CTI port in extended format
D CTIPE: CTI port identifier [1..300]
D CTIR CTI routing
D CTIRE CTI routing in extended format
D CTIRR CTI routing in reduced format
D CTISIP CTISIP numbers table entry
D CTISMS CTI SMS routings for incoming/outgoing messages
D DESCR Resource's description
D DEV Active/inactive hardware devices
D DHCP DHCP summary/profiles/subnets/hosts
D DNS DNS server and relay tables
D FTP FTP Virtual root paths/path's access Rights
D G General system parameters
D GROUP Groups of Users table summary
D GROUP: Group entry
D GROUPE Groups of Users table - extended view
D GROUPE: Group entry - extended view
D HTTP HTTP Virtual root paths/path's access Rights
D I System and files information
D IKE IKE Host/Client connections and preshared keys tables
D INACT Inactive HW device/resource/CTI port
D IPACL IP Access List
D IPACLE IP Access List in extended format
D IPAD IP Routing Administrative Distance
D IPLB IP Load Balancing entry
D IPRS Saved static IP Routing (same of SIPR)
D IPSEC IPSEC Security policies and associations tables
D IPSR IP Source Routing
D ITEM CPX list items
D LIST CPX lists
D LIST: CPX list name
D NAT NAT alias entry
D OSPF OSPF area/range/neigh/host/external route
D SIPR Saved static IP Routing (same of IPRS)
D L System Log
D LCSG Last Calling Number Service group
D LDD Debug Log on Disk
D LDDE Debug Log on Disk, extended visualization
D LE Exceptions Log
D P Resource parameters
D PREF Preferences
D PSTACK Protocol stack
D PVC PVC Connection
D R SVC Routing
D RE SVC Routing in extended format
D RIP RIP external route
D TREE Resources tree
D USER Users Access Control table summary
D USER: User entry
D USERE Users Access Control table - extended view
D USERE: User entry - extended view
D VER System and modules versions
D VRRP VRRP Routers

1072
Draft List of Commands Draft

D WGB WG Bridge Routing

EXIT Exit program.

Find operations:
F BRIDGE Bridge MAC search
F CF CF/DND (Call forwarding/Do-Not-Disturb) searches
F CTIDISA CTIDISA searches
F CTIIAX CTIIAX numbers search
F CTISIP CTISIP numbers search
F DNS DNS searches
F FTP FTP Virtual root paths/path's access Rights
F HTTP HTTP Virtual root paths/path's access Rights
F IPACL IP Access List
F LIST: CPX list name
F LISTE: CPX list name
F USER Users Access Control table summary
F USER: User entry

HELP Detailed topic help.

Lists operations:
LIST CLEAR Remove all items from a list
LIST CREATE Create a list
LIST DELETE Delete a list
LIST DESCRIPTION Add/Modify list description
LIST DISPLAY Display currently configured lists
LIST EDITABLE Set/Reset list editable flag
LIST RENAME Modify list name

LOGIN Log-in operations.

LOGOUT Log-out operations.

Move operations:
M CF CF/DND (Call forwarding/Do-Not-Disturb) entry
M CTIR CTI routing
M CTIRE CTI routing
M CTIRR CTI routing
M CTISMS CTI SMS routings for incoming/outgoing messages
M IPACL IP Access List
M NAT NAT alias entry
M R SVC Routing

QUIT Exit program.

Save operations:
SAVE CONF Current configuration

Set operations:
S ACT Active HW device/resource/CTI port
S CF CF/DND (Call forwarding/Do-Not-Disturb) entry
S CRKEY: Encryption/Decryption key identifier [1..63]
S CTIB CTI channels bundle
S CTIDISA CTI DISA Users and Services
S CTICL CTI cluster
S CTIG CTI group
S CTIH323 CTI H.323 Translation entry
S CTIIAX CTIIAX numbers table entry
S CTIL CTI link
S CTILG CTI group of links
S CTIP CTI port

1073
Draft List of Commands Draft

S CTIP: CTI port identifier [1..300]

S CTIPC CTI permanent connection
S CTIPE CTI port
S CTIPE: CTI port identifier [1..300]
S CTIR CTI routing
S CTIRE CTI routing
S CTIRR CTI routing
S CTISIP CTISIP numbers table entry
S CTISMS CTI SMS routings for incoming/outgoing messages
S DEV: HW device identifier 'type-n', where 'n' can be [1..255]
S DHCP DHCP profile/subnet/host
S DNS DNS server and relay tables
S FTP FTP Virtual root paths/path's access Rights
S G General system parameters
S GROUP: Group entry
S GROUPE: Group entry
S HTTP HTTP Virtual root paths/path's access Rights
S IKE IKE Host/Client connections and preshared keys tables
S INACT Inactive HW device/resource/CTI port
S IPACL IP Access List
S IPAD IP Routing Administrative Distance
S IPLB IP Load Balancing entry
S IPRS Saved static IP Routing (same of SIPR)
S IPSEC IPSEC Security policies and associations tables
S IPSR IP Source Routing
S LCSG Last Calling Number Service group
S NAT NAT alias entry
S OSPF OSPF area/range/neigh/host/external route
S P Resource parameters
S PREF Preferences
S PVC PVC Connection
S R SVC Routing
S RE SVC Routing
S RIP RIP external route
S SIPR Saved static IP Routing (same of IPRS)
S USER: User entry
S USERE: User entry
S VRRP VRRP Routers
S WGB WG Bridge Routing

TERM Terminal setting operations.

Trace operations:
TRACE DISPLAY Trace display operations
TRACE PARAM Trace parameters operations

VALIDATE Current configuration validation.

Exchange HW device configurations and resource subtypes:

X DEV: List of HW device identifiers joined by ',' character
X RES: Resource identifier 'type-n', where 'n' can be [1..999]

Comments:
# Commands starting with this character will be ignored

1074
Draft Draft

Chapter 60. Log messages

Marco Bellesia

Table of Contents
60.1. System Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075

60.1. System Log messages

Example:

[15:41:54] ABILIS_CPX:d l

Current Local Time: Wednesday 28/12/2011 15:42:05 (UTC+1.00)

28/12/2011 12:27:53 [00103] -------------------- NEW RUN --------------------

28/12/2011 12:27:53 [00398] I: ABILIS CPX Ver. 7.3.1/STD - Build 3518.17
28/12/2011 12:27:55 [00362] I: WATCHDOG MFIDE3 FW Rev. 11
28/12/2011 12:27:55 [00254] I: POWER ON
28/12/2011 12:27:55 [00164] I: RESET PRESSED
28/12/2011 12:27:55 [00371] I: LICENCE, LOADED
28/12/2011 12:27:55 [00079] I: PCI BUS PARKING CHANGED: ON CPU
28/12/2011 12:27:55 [00249] I: USB PCI11/2 EHCI 80000000 11
28/12/2011 12:27:55 [00249] I: USB PCI11/0 OHCI 80001000 9
28/12/2011 12:27:55 [00249] I: USB PCI11/1 OHCI 80002000 10
28/12/2011 12:27:55 [00248] I: USB PCI4/2 UHCI D400 10
28/12/2011 12:27:55 [00248] I: USB PCI4/3 UHCI D000 10
28/12/2011 12:27:56 [00150] W: MISSING STHUSB-I.BIN
28/12/2011 12:27:57 [00150] W: MISSING BS432.BIN
28/12/2011 12:28:00 [00242] I: QPRI-1 DSP:0 DWNL OK
28/12/2011 12:28:00 [00242] I: QPRI-1 DSP:1 DWNL OK
28/12/2011 12:28:01 [00242] I: QPRI-1 DSP:2 DWNL OK
28/12/2011 12:28:01 [00242] I: QPRI-1 DSP:3 DWNL OK
28/12/2011 12:28:02 [00242] I: QPRI-1 DSP:4 DWNL OK
28/12/2011 12:28:02 [00242] I: QPRI-1 DSP:5 DWNL OK
28/12/2011 12:28:02 [00242] I: QPRI-1 DSP:6 DWNL OK
28/12/2011 12:28:03 [00242] I: QPRI-1 DSP:7 DWNL OK
28/12/2011 12:28:06 [00242] I: BRI8-1 DSP:0 DWNL OK
28/12/2011 12:28:06 [00242] I: BRI8-1 DSP:1 DWNL OK
28/12/2011 12:28:15 [00071] TRACE ACTIVATED
28/12/2011 12:28:20 [00291] I: DSP test start
28/12/2011 12:28:24 [00292] I: DSP test end
28/12/2011 12:28:24 [00286] I: CTIR ENABLED
28/12/2011 12:28:24 [00055] SYSTEM STARTED
28/12/2011 12:28:25 [00330] I: Sntp-1 CLI-ST:RD
28/12/2011 12:28:25 [00104] AUTO SAVE IN PROGRESS
28/12/2011 12:28:25 [00266] I: CtiDisa-1 ST:AC
28/12/2011 12:28:25 [00091] I: Pad-1 L1-ST:dn DCD:dn DTR:UP
28/12/2011 12:28:25 [00270] I: Ip-51 ST:DN LINK:ld
28/12/2011 12:28:25 [00270] I: Ip-53 ST:DN LINK:ld
28/12/2011 12:28:25 [00270] I: Ip-55 ST:DN LINK:ld
28/12/2011 12:28:25 [00092] I: Pv-8 PLink:d1 SLink:ln
28/12/2011 12:28:26 [00092] I: Pv-5 PLink:d2 SLink:ln
28/12/2011 12:28:26 [00092] I: Pv-8 PLink:d2 SLink:ln
28/12/2011 12:28:27 [00107] AUTO SAVE OK

1075
Draft Log messages Draft

28/12/2011 12:28:43 [00092] I: Pv-10 PLink:RD SLink:ln

Tip
The command allows to display a log file of another version:

[09:22:13] ABILIS_CPX:_d l ?

D L [ver] [dd/mm/yyyy] [hh:mm:ss] Display System Log

<ver> String corresponding to a version directory in <Optional>

the form [x.y.z or x-y-z or y.z or y-z or y].
(E.g.: 5.3.1 or 6-1-0 or 2189).
dd/mm/yyyy Selected date <Optional>
hh:mm:ss Selected time <Optional>

Notification messages are stored in the Abilis CPX System Log file in the following format:

Table 60.1. System Log event's format

Date Time Event Code Event Text

dd/mm/yyyy hh:mm:ss [nnnnn] Textual message

Notification messages are classified on the basis of importance of the reported event. The event importance is indicated by a
prefix reported in the text of the event message itself.

The following table lists Event types and the corresponding Event text prefix:

Table 60.2. System Log event's classification

Event type Event text prefix Meaning

Unclassified none Indications of general events.
Error E: Notifications of critical errors which
require the reset of Abilis CPX. All
the sessions are closed and Abilis CPX
automatically restarts. Note that an
exception is generated and saved in the
Exceptions Log for a possible use by
Abilis engineers.
Warning W: Notifications of not critical events that
could be caused by some malfunction.
The reason must be carefully identified,
but the system will continue to function.
Informative I: Notifications of events of particular
interest that occur in the regular system
operation.

Each message also has a Severity level indicator, based on SYSLOG protocol severity classification. See SYSLOG section
for a description of SYSLOG Message Severities.

1076
 resource state [dn (DOWN),
RD (READY)].
00428 INFO I: MFIo-nnn ST:ssss Diagnostic information
Draft Log messages Draft
about MfIo resource.
'ssss' is the resource state
[in (INACTIVE), RD
Table 60.3. System Log event's List (ACTIVE)].
00429 WARNING W: LDAP - <file-name> LDAP service need to update
version update required, from db file <file-name>.
v. xxx to v. yyy
00430 WARNING W: LDAP - <file-name-1> LDAP service, db file <file-
v. xxx being saved in <file- name> save is in progress.
name-2>
00431 WARNING W: LDAP - <file-name-1> v. LDAP service, db file <file-
xxx saved in <file-name-2> name> successfully saved.
00432 WARNING W: LDAP - Error nn (ssss) LDAP service, db file <file-
saving <file-name>. name> unsuccessful save.
The number 'nn' is the
occurred error code and 'ssss'
is the related description.
Please report the event to the
Abilis CPX Help desk.
00433 WARNING W: LDAP - <file-name> LDAP service, db file <file-
being updated to v. xxx name> version update is in
progress.
00434 WARNING W: LDAP - <file-name> LDAP service, db file <file-
successfully updated to v. name> successfully updated.
xxx
00435 WARNING W: LDAP - Error nn (ssss) LDAP service, db file <file-
updating <file-name> name> unsuccessful update.
The number 'nn' is the
occurred error code and 'ssss'
is the related description.
Please report the event to the
Abilis CPX Help desk.
00436 INFO I: MfTemp-nnn ST:ssss Diagnostic information
about MfTemp resource.
'ssss' is the resource state
[in (INACTIVE), RD
(ACTIVE)].
00437 INFO I: SysCtl-nnn ST:ssss Diagnostic information
about SysCtl resource.
'ssss' is the resource state
[in (INACTIVE), RD
(ACTIVE)].
00438 WARNING W: MAIL SERVICE SMTP Mail Service: mail not sent
ERROR [nn] - ssss because of SMTP driver
error. The number 'nn' is the
occurred error code and 'ssss'
is the related description.
Please report the event to the
Abilis CPX Help desk.
00439 WARNING W: MAIL SERVICE ERROR Mail Service: mail not sent
[nn] - ssss because of service internal
error. The number 'nn' is the
occurred error code and 'ssss'
is the related description.
Please report the event to the
Abilis CPX Help desk.
00440 WARNING W: Adsl-nnn STH ADSL (STH) modem -
Unsupported FW version unsupported FW version.
'nnn' is the resource
identifier.

1077
Draft Draft

Chapter 61. Disconnection codes

Marco Bellesia

Table of Contents
61.1. ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.1. ISDN disconnection codes recommended by ITU (formerly CCITT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
61.1.2. Abilis CPX private ISDN disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
61.2. X.25 disconnection codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.1. ITU (formerly CCITT) X.25 codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
61.2.2. Abilis CPX internal codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084

61.1. ISDN disconnection codes

61.1.1. ISDN disconnection codes recommended by ITU (formerly
CCITT)
The parameter CAUSE in the debug log shows a “cause” field which corresponds to what has been specified by the ITU in
Recommendations Q.931 e Q.850.

Example: CAUSE: 82 90

Table 61.1. Disconnection code's format

First field: Location Second field: ISDN

disconnection cause
CAUSE 82 90
Description Public network serving the local user Normal call clearing
(LN)

1078
Draft Disconnection codes Draft

Table 61.2. First Field: Location

Code value (hex) Location Brief Description

80 User (U) Originated by user equipment, i.e
phone.
81 Private network serving the local user Generated by a private networking
(LPN) device, e.g. a PABX, on the side which
is directly connected to the receiving
device.
82 Public network serving the local user Generated by the public network, e.g.
(LN) a Telco, on the side which is directly
connected to the receiving device.
83 Transit network (TN) Generated somewhere in an
intermediate network on which the call
is transiting.
84 Public network serving the remote Generated by the public network, e.g. a
user (RLN) Telco, on the remote side respect to the
receiving device.
85 Private network serving the remote Generated by a private networking
user (RPN) device, e.g. a PABX, on the remote side
respect to the receiving device.
86 International network (INTL) Generated somewhere in the
international network.
87 Network beyond interworking point Generated by a non-ISDN network
(BI) interconnected to the ISDN network.
88 All other values are reserved.

1079
 C/Q.931.
DF Invalid message, unspecified. This cause is used to report
an invalid message event only when no other cause in the
Draft invalid message class applies.
Disconnection codes Draft
E0 Mandatory information element is missing. This cause
indicates that the equipment sending this cause has received
Table 61.3. Second field: ISDN disconnection cause
a message which is missing an information element which
must be present in the message before that message can be
processed.
E1 Message type non-existent or not implemented. This cause
indicates that the equipment sending this cause has received
a message with a message type which it does not recognize
either because this is a message not defined or is defined but
not implemented by the equipment sending this cause.
E2 Message not compatible with call state or message type
non-existent or not implemented. This cause indicates that
the equipment sending this cause has received a message
such that the procedures do not indicate that this is a
permissible message to receive while in the call state, or a
STATUS message was received indicating an incompatible
call state.
E3 Information element/parameter non-existent or not
implemented. This cause indicates that the equipment
sending this cause has received a message which includes
information element(s)/parameter(s) not recognized because
the information element identifier(s)/parameter name(s)
are not defined or are defined but not implemented by the
equipment sending the cause. This cause indicates that
the information element(s)/parameter(s) were discarded.
However, the information element is not required to be
present in the message in order for the equipment sending the
cause to process the message.
E4 Invalid information element contents. This cause indicates
that the equipment sending this cause has received an
information element which it has implemented; however, one
or more fields in the information element are coded in such
a way which has not been implemented by the equipment
sending this cause.
E5 Message not compatible with call state. This cause
indicates that a message has been received which is
incompatible with the call state.
E6 Recovery on timer expiry. This cause indicates that a
procedure has been initiated by the expiry of a timer in
association with error-handling procedures.
E7 Parameter non-existent or not implemented - passed
on (national use). This cause indicates that the equipment
sending this cause has received a message which includes
parameters not recognized because the parameters are not
defined or are defined but not implemented by the equipment
sending the cause. The cause indicates that the parameter(s)
were ignored. In addition, if the equipment sending this
cause is an intermediate point, then this cause indicates that
the parameter(s) were passed on unchanged.
EE Message with unrecognized parameter discarded. This
cause indicates that the equipment sending this cause has
discarded a received message which includes a parameter
that is not recognized.
EF Protocol error, unspecified. This cause is used to report a
protocol error event only when no other cause in the protocol
error class applies.
FF Interworking, unspecified. This cause indicates that there
has been interworking with a network which does not
provide causes for actions it takes. Thus, the precise cause
for a message which is being sent cannot be ascertained.

1080
Draft Disconnection codes Draft

61.1.2. Abilis CPX private ISDN disconnection codes

In Events Log messages it is sometimes possible to found codes which are not codified by ITU, or are codified as “specific
for the specified location: user”. These are specific codes used by CPX to indicate particular events.

Codes starting with FF as the first byte, report local problems, i.e. they are not messages sent or received by the network.
Codes starting with 80 as the first byte, are codes specific to CPX, sent or received by the network.

It should be noted that these “private” codes might not be transported to their destination by ISDN, exactly as happens with
the Italian Telecom network.

Table 61.4. Abilis CPX private ISDN disconnection codes

Cause locations (hex) Cause codes(hex) Meaning

FF 00 No problem is detected.
FF 97 Unconditional Disconnect Timer
timeout.
FF A0 The calling number (“CGO” in the
MLM driver) specified in the call
cannot be associated with any ISDN
line (“NUM” in the Q931 driver).
FF A1 No path between 2 B channels is
available.
FF A2 No appropriate codec is available.
FF A3 The “cause” field is absent.
FF A4 No AC is available.
FF A5 Level 1 of ISDN is inactive.
FF A6 Level 2 of ISDN is inactive, or failed to
activate.
FF A7 No HDLC is available.
FF A8 No port is detected.
FF AD No outgoing connection side is
detected.
FF AE No appropriate connection for call.
FF B3 No B channels were available.
FF B4 No loop connection detected.
FF B5 Not enough bandwidth is available.
FF B6 The CTI service is denied.
FF BF The CTI service is not available.
80 80 Closure caused by SHM feature of the
MLM driver.
80 8A Closure caused by init command issued
to the MLM driver.
80 8B Closure caused by an error discovered
by the MPX protocol in the MLM
driver, usually a failure in link-check
frame exchange.
80 8C Closure caused by the restoration of
READY state in the P-LINK interface
of the MLM driver.

1081
Draft Disconnection codes Draft

61.2. X.25 disconnection codes

61.2.1. ITU (formerly CCITT) X.25 codes
The disconnection codes caused by errors in the X.25 procedure, have a cause and a diagnostic code.

Table 61.5. ITU X.25 cause codes

Cause ( Hex ) Meaning

CAUSES OF DISCONNECTION
00 CLR DTE - Originating from DTE
01 CLR OCC - Called address busy
03 CLR INV - Request for facility not valid
05 CLR NC - Network congestion
09 CLR DER - Called address out of order
0B CLR NA - Access not allowed
0D CLR NP - Inexistent called address
11 CLR RPE - Error in X.25 procedure at the remote end
13 CLR ERR - Error in X.25 procedure at the local end
15 RPOA out of service
19 CLR RC -The called address does not accept taxation on its
charge
21 Incompatible destination
29 “Fast Select” option not available for the called address
39 Ship missing (only for mobile marine services)
RESET CAUSES
00 RES DTE - Originating from DTE
01 RES DOWN - Remote DTE out of service (only PVC)
03 RES RPE - Remote DTE caus an X.25 procedure error
05 RES ERR - Local DTE cause an X.25 procedure error
07 RES NC - Network congestion
09 RES UP - Remote DTE operative (only PVC)
0F RES UP - Network resumes service (only PVC)
11 Incompatible destination
1D RES DOWN - Network out of service (only PVC)
RESTART CAUSES
00 Originating from DTE
01 Local procedure error
D7 Network operational

1082
 25 packet disallowed: Reject not allowed
26 packet disallowed: packet too short
27 packet disallowed: packet too long
Draft Disconnection codes Draft
28 packet disallowed: GFI (General Format Identifier) not valid
29 packet disallowed: restart with GFI different from zero
Table
2A 61.6. ITU X.25 diagnostic codes packet disallowed: type of packet not compatible with the
registered facility
2B packet disallowed: interrupt confirmation not authorised
2C packet disallowed: interrupt not authorised
2D packet disallowed: reject not authorised
30 TIMER EXPIRED
31 Timer expired: for call request
32 Timer expired: for clear indication
33 Timer expired: for reset indication
34 Timer expired: for restart indication
40 CALL SET-UP PROBLEMS
41 Call-setup problems: facility or registration code not
permitted
42 Call-setup problems: parameter of the facility not permitted
43 Call-setup problems: called address not valid
44 Call-setup problems: caller's address
45 Call-setup problems: length of facility or registration not
valid
46 Call-setup problems: incoming calls barred
47 Call-setup problems: no logical channel available
48 Call-setup problems: call collision
49 Call-setup problems: facility request duplicated
4A Call-setup problems: length of the address different to zero
4B Call-setup problems: length of the facility different to zero
4C Call-setup problems: facility was not supplied when expected
4D Call-setup problems: format of the facility specified by DTE
not compatible with CCITT
50 VARIOUS
51 Various: incorrect cause code generated by DTE
52 Various: byte not aligned
53 Various: Q-bit setting meaningless
70 INTERNATIONAL PROBLEMS
71 International problems: problems of the remote network
72 International problems: problems of protocol at international
level
73 International problems: international link not in service
74 International problems: international link busy
75 International problems: problem of the facility on the transit
network
76 International problems: problem of the facility on the
destination network
77 International problems: problems on the international
routings
78 International problems: temporary routing problems
79 International problems: the DNIC being called is not
recognized
7A International problems: maintenance in progress

1083
Draft Disconnection codes Draft

61.2.2. Abilis CPX internal codes

The internal disconnection codes caused by errors in the X.25 procedure, have as cause and diagnostic the values provided by
CCITT.

Internal disconnection codes which are not caused by errors in the X.25 procedure, have FO as the cause (see also the
parameter MCAU in the port parameters) and the appropriate value for the error identification.

Some of these diagnostic codes are of considerable importance to the installer and the user of Abilis CPX, while others are
important for technical assistance of the retailer and the producer.

1084
 F0 C7 An internal error caused the
compression module to be reinitialised
F0 C8 Internal code not provided for the
Draft Disconnection codes commands SEND/RECEIVE. Draft

F0 C9 QLLC, MBIT, MBITB compressions:

disconnection as consequence of a
Table 61.7. Abilis CPX internal codes RESET received on the compressed
channel.
F0 CA Obsolete.
F0 CB Obsolete.
F0 CC Obsolete.
F0 CD Obsolete.
F0 CE Obsolete.
F0 CF Obsolete.
F0 D0 Regular disconnection caused by the
SHM feature.
F0 D1 SDLC, HDLCT: ;the received frame is
too long (greater than N1).
F0 D2 Obsolete.
F0 D3 SDLC/QLLC: ;received a too long
sequence of X25 packets with M-bit= 1
(greater than N1-2).
F0 D4 SDLC: the PU being addressed is
already in use.
F0 D5 SDLC: the PU being addressed is not
configured or does not exist.
F0 D6 SDLC: the PU has received an X.25
reset packet while in an “ACTIVE”
state (state 5, NRM) and forced the
closure.
F0 D7 SDLC: the secondary PU has not
received polling for a period longer than
“INACT”.
F0 D8 SDLC: the primary PU, in an
“ACTIVE” state, has exceeded frame
retransmission attempts.
F0 D9 SDLC: the secondary PU has sent an
FRMR frame.
F0 DA SDLC: the primary PU has received an
FRMR frame.
F0 DB SDLC/QLLC: the PU has received an
invalid X.25/QLLC sequence.
F0 E0 Obsolete.
F0 E1 Obsolete.
F0 E2 Obsolete.
F1 A0 Simulator: closure caused by the receipt
of a packet longer than MXPS.
F1 A1 Simulator: closure caused by the receipt
of a too long M-bit sequence.
F1 A2 Simulator: closure caused by the receipt
of a too short M-bit sequence.
F1 A3 Simulator: closure due to an error noted
in the comparison between the frames
sent and received.
F1 A4 Simulator: regular closure due to expiry
of the configured time out.
F1 A5 Simulator: generic regular closure.

1085
Draft Draft

Appendix A. Glossary
ADSL Asymmetric Digital Subscriber Line (see Wikipedia1 for details).

ARP Address Resolution Protocol (see Wikipedia2 for details).

BRI Basic Rate Interface (see Wikipedia3 for details).

DHCP Dynamic Host Configuration Protocol (see Wikipedia4 for details).

DNS Domain Name System (see Wikipedia5 for details).

DSP Digital Signal Processor (see Wikipedia6 for details).

DTMF Dual-Tone Multi-Frequency (see Wikipedia7 for details).

Frame relay - (see Wikipedia8 for details).

FTP File Transfer Protocol (see Wikipedia9 for details).

FXO Foreign eXchange Office (see Wikipedia10 for details).

FXS Foreign eXchange Station (see Wikipedia11 for details).

GSM Global System for Mobile communications (see Wikipedia12 for details).

H.323 - (see Wikipedia13 for details).

HDLC High-level Data Link Control (see Wikipedia14 for details).

HDSL High bit rate Digital Subscriber Line (see Wikipedia15 for details).

HTTP HyperText Transfer Protocol (see Wikipedia16 for details).

HTTPS - (see Wikipedia17 for details).

IAX Inter-Asterisk eXchange (see Wikipedia18 for details).

ICMP Internet Control Message Protocol (see Wikipedia19 for details).

IP Internet Protocol (see Wikipedia20 for details).

IPsec IP security (see Wikipedia21 for details).

ISDN Integrated Services Digital Network (see Wikipedia22 for details).

LAN Local Area Network (see Wikipedia23 for details).

LAPB Link Access Protocol, Balanced (see Wikipedia24 for details).

LAPD Link Access Procedures, D channel (see Wikipedia25 for details).

MAC Media Access Control (see Wikipedia26 for details).

NAT Network address translation (see Wikipedia27 for details).

OSPF Open Shortest Path First (see Wikipedia28 for details).

PAT Port address translation (see Wikipedia29 for details).

PBX Private Branch eXchange (see Wikipedia30 for details).

PCI Peripheral Component Interconnect (see Wikipedia31 for details).

POTS Plain Old Telephone Service (see Wikipedia32 for details).

PPP Point-to-Point Protocol (see Wikipedia33 for details).

PPPoE Point-to-Point Protocol over Ethernet (see Wikipedia34 for details).

PRI Primary Rate Interface (see Wikipedia35 for details).

1086
Draft Glossary Draft

PTSN Public Telephone Switched Network (see Wikipedia36 for details).

QoS Quality of Service (see Wikipedia37 for details).

RIP Routing Information Protocol (see Wikipedia38 for details).

RJ11 - (see Wikipedia39 for details).

RJ45 - (see Wikipedia40 for details).

SDLC Synchronous Data Link Control (see Wikipedia41 for details).

SIP Session Initiation Protocol (see Wikipedia42 for details).

SMTP Simple Mail Transfer Protocol (see Wikipedia43 for details).

SNMP Simple Network Management Protocol (see Wikipedia44 for details).

SNTP Simple Network Time Protocol (see Wikipedia45 for details).

SSL Secure Socket Layer (see Wikipedia46 for details).

SSH Secure Shell (see Wikipedia47 for details).

STUN Simple Traversal of UDP through NATs (see Wikipedia48 for details).

TCP Transmission Control Protocol (see Wikipedia49 for details).

TDM Time-Division Multiplexing (see Wikipedia50 for details).

TELNET Telecomminication Network (see Wikipedia51 for details).

UDP User Datagram Protocol (see Wikipedia52 for details).

USB Universal Serial Bus (see Wikipedia53 for details).

VoIP Voice over IP (see Wikipedia54 for details).

VPN Virtual Private Network (see Wikipedia55 for details).

VRRP Virtual Router Redundancy Protocol (see Wikipedia56 for details).

X.25 - (see Wikipedia57 for details).

xDSL Digital Subscriber Line (see Wikipedia58 for details).

1087