Bypass by Procedure

Diversion bypass, both internally and in network, is done with a procedure from the calling user. If the extension is not generic, then two options are possible:

The extension is always allowed to initiate diversion bypass.
When the extension tries to initiate diversion bypass, its intrusion class of service is checked. If this class of service permits intrusion, then the bypass is also allowed. If not, the attempt to initiate bypass will be rejected.

If the extension is a generic extension, then the two options are:

The extension is always allowed to initiate diversion bypass.
When the extension tries to initiate diversion bypass, a dedicated class of service is checked to see if it is allowed to be executed from that extension or not.

The value of a specific parameter determines whether bypass is always allowed or a certain class of service (as shown above), shall be checked before permitting it.

PBX-operators are always permitted to bypass diversion.

If the same number as that of the connected party in left side of operator is dialed from the right side of the operator, all diversions are bypassed.

If a diversion cannot be bypassed due to internal barring or class of service barred, a NO PROGRESS message is sent to calling party. The call is released.

The same bypass procedure is also valid for bypass of Personal Number.

Table 1. Bypass
The user procedure for bypassing diversion is:	FCD1#

where FC is the service code for diversion bypass and D1 the directory number of the sought user.

↑