Expert Documentation

- My IC Web for Office
- PIMphony
Access is controlled at application level (API authentication), as detailed in the table below.
table 13.1: Access Control to API
Local access
Remote access
8002/8012 Deskphone Open Open
8082 My IC Phone Open Closed (*)
My IC Mobile for iPhone Open Open
My IC Mobile for Android Open Open
My IC Web for Office Open / Closed (**) Open / Closed (***)
PIMphony Open Open / Closed (***)
(*) 8082 My IC Phone can only be used on the LAN.
My IC Mobile for Android and My IC Mobile for iPhone can be used on the LAN and on the
WAN, without restriction.
(**) By default, the access to My IC Web for Office is not authorized. To authorize the access
for a user: by OMC (Expert View) select: Users/Base stations List -> Details-> Features ->
check My IC Web Office Support
(***) As of R8.1, by default, the access to My IC Web for Office and PIMphony from the WAN
is not authorized. To authorize the access for a user: by OMC (Expert View) select:
Users/Base stations List -> Details-> Features -> check WAN API access
Note:
Up to R8.0, the access to PIMphony from the WAN is authorized. That is why, after a migration from R8.0
or lower to R8.1 or higher, it is necessary to enable the WAN API access feature right to keep the same
level of service.
13.2.1.3 Password Attempt Control
Access to the OmniPCX Office Web Services API and private API is controlled by the
authentication of users with their phone number (login) and a password.
Password length can be four digit or six digit based on the length configured in OMC: System
> System Miscellaneous >Passwords >Subscribers Password.
Locally (on the LAN) there is no restriction on connection attempts. For remote (WAN) access,
the number of consecutive failed authentication attempts is limited to three.
When the maximum number of consecutive failed authentication attempts has been reached
for a user, remote access to the API for this user is denied. While remote access is denied, all
remote authentication attempts are rejected, even if correct.
Remote access is automatically made available again after a timeout. The timeout value
depends on the number of consecutive denials. It is of five minutes after the first denial and ten
minutes after the second denial. Subsequent timeouts are multiples of five (number of denials)
until the value reaches sixty minutes.
When this value of one hour is reached, remote access (not the local one) is indefinitely
(unlimited time) locked for the user.
13-5