| 59.2. OPC configuration | ||
|---|---|---|
 | Chapter 59. OPC - Operator Panel Control |  |
| 59.2. OPC configuration | ||
|---|---|---|
| | Chapter 59. OPC - Operator Panel Control | |
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]](../images/tip.png) | Tip |
|---|---|
Refer to Chapter 67, Enable the access to the web interface to have more information about http directories. |
Users can access to HTTP server only if they're 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 |CHAT LDAP PPP FTP HTTP MAIL IAX SIP VO
------------------------+-------------+----------------------------------------
admin *** YES # # YES YES YES YES YES NO NO NO NO
guest YES # # NO YES NO NO NO NO NO NO NOAs shown above, only the admin user is enabled for 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:yesCOMMAND EXECUTED [17:23:12] ABILIS_CPX:d user- Not Saved (SAVE CONF) ------------------------------------------------------- ------------------------+-------------+---------------------------------------- USER PWD ACT|CTIP CLUS |CHAT LDAP PPP FTP HTTP MAIL IAX SIP VO ------------------------+-------------+---------------------------------------- admin *** YES # # YES YES YES YES YES NO NO NO NO guest YES # # NO YES NO NO NO NO NO NO NO opc1 YES # # NO NO NO NO YES NO NO NO NO
| Tip |
|---|---|
Interesting chapter: Section 6.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:opc1COMMAND 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 (e.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:102 opc-monitor:ctipCOMMAND EXECUTED [18:13:17] ABILIS_CPX:d user:opc1- Not Saved (SAVE CONF) ------------------------------------------------------- Parameter: | Value: --------------------+---------------------------------------------------------- USER: opc1 REAL-NAME: opc1 ID: 7 <Read Only> PWD: ACT: YES CP-LEVEL: NO SSH-IP-PERMIT: * TELNET-IP-PERMIT: * CTI-ROLE: EXTENSION GROUP: CTIP: # CTIP-CDI-PERMIT: * CLUS: # CLUS-CDI-PERMIT: * ADDRBOOK-SYNC: SYS ADDRBOOK-NUMBER: AUTO ADDRBOOK-OUTDIAL: NONE ADDRBOOK-PRIV-MAX: SYS ADDRBOOK-PUB-EDITABLE:SYS IO-MAP: # OPC-ROLE: USER OPC-VIEW: * OPC-HIDE-NUMBERS: NO OPC-MONITOR: CTIP OPC-PRIVACY: NO CHAT: NO CHAT-USER: SYS CHAT-PWD: SYS HTTP: YES HTTP-HOME-URL: 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), VO (to
monitor Virtual Office interfaces).
For example, assuming that the user “opc2” has both a SIP and a IAX account, the following commands can be used:
Table 59.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
OPC pages by this user. NONE or * or the name of an OPC Unique User
IDs list. 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
The following command display User's OPC parameters summary:
[15:11:54] ABILIS_CPX:d user opc
--------------------------------------+--------------+-------------------------
USER: PWD: ACT:|CTIP: CLUS: |OPC-MONITOR:
--------------------------------------+--------------+-------------------------
admin *** YES 111 # - - - - -
guest YES # # - - - - -
opc *** YES # # - - - - -
opc1 *** YES 122 # CTIP - - - -
opc2 *** YES 121 # CTIP IAX SIP - -
test *** YES # # - - - - VO
test2 *** YES # # CTIP - SIP - -
test3 *** YES # # CTIP - SIP - - | |  | |
| 59.1. OPC resource |  | 59.3. Web interface |