Customer Centralized Operator in a Network with ISDN, H.323, or SIP

When the customer group function is used, in addition to the central operator or private network answer positions, described in the previous section, calls to a common operator number can be Night Service-diverted to a customer central operator MX-ONE if the called PBX operator group has no present local PBX operator in service. Up to 2 different CCOP numbers can be defined per PBX operator group.

The possible destination numbers have the following order of priority:

• Local common operator number or local day answer position

• CCOP 1

• CCOP 2 (Note)

• Central operator or private network answer position 1

• Central operator or private network answer position 2

• Central operator or private network answer position 3

• Local answer position for call origin group without any present operator

Note: In an ISDN VPN scenario, the number of CCOPs supported depends on the number of USER INFO messages that can be sent in Service 2 (during alerting). If two USER INFO messages are allowed in Service 2, then only one CCOP is supported. When more than two USER INFO messages are allowed, both CCOP 1 and 2 are supported. Notice that in an H.323 VPN scenario the USER INFO messages are embedded in H.225 FACILITY messages.

Prerequisites

Common operator numbers must be initiated. The CCOP is reached via a common abbreviated number. The abbreviated number contains the private network number of the customer central operator. When expanded, the number must consist of the own exchange number of the customer central operator's MX-ONE, and a common operator number (number type OD and OC) in the customer central operator's MX-ONE.