|
|
|
|
|
| CM does not treat a station as a call forwarding-no answer destination if its telephone has failed, if the user has activated do not disturb or has activated data protection and is busy, or if the user does not have trunk access (for external calls).
|
|
|
|
| If CM cannot find a station to which it can switch the call, it follows the intercept criteria.
|
|
|
|
| If no stations in a group or hunt group are available, the call camps on at all telephones in the group.
|
|
|
|
| Stations that cannot be reached via direct inward dialing, such as entrance telephones, should not be entered as stations to which calls are allocated; otherwise, an intercept will occur.
|
|
|
|
| With DTMF DID/DISA, an analog call can be released before the call forwarding-no answer process has concluded because the system uses fixed timers to prevent the trunks from freezing up.
|
|
|
|
| If a CM element does not have any entries in the first four columns, the system immediately calls the night bell regardless of the entry in the seventh column.
|
|
|
|
| If a system search is the item in a CM element, the system ignores subsequent entries in this CM element.
|
|
|
|
If a call can no longer be signaled in the system (due to an AC failure, for example), the system sends a busy signal or releases the call.
Solution:
|
| Make an entry in the second column of the AC's call destination list.
|
|
|
|
| The system searches all stations and:
|
| Does not follow call forwarding
|
| Routes only one call to each station
|
| Ignores call ringing groups
|
|
|
|
| If a destination station entered in a destination number list has activated the call diversion function (*1n) for another station or a hunt group, Call Management still analyzes the destination number list of the original destination station (when the call is not answered) and NOT the destination number list of the diversion destination.
|
|
| How incoming calls for individual stations and station call groups are dealt with when voicemail is available
|
|
| The "OpenScape Office" application suite supports voicemail for station call groups. From the point of view of the CM, an individual station and a station call group have each their own call destination list. This results in the following behavior:
|
|
•
|
If an individual station is called, and it does not answer the call, or if call forwarding is activated: The CM follows the call destination list of this station. If a personal voicemail box is also entered in this call destination list, the call is routed to this personal voicemail box.
|
|
•
|
If a station call group is called and the call is not answered or if call forwarding is activated: The CM follows the call destination list of the station call group. If a group voicemail box is entered in its list, the call is routed to this group voicemail box.
|
|
•
|
If an individual station is called and it does not answer the call or if call forwarding is activated: The CM follows the call destination list of the station:
|
| |
- |
If a station call group is entered in the call destination list, the CM of the call destination list follows this station call group.
|
| |
- |
If a personal voicemail box is also entered in the station's call destination list, the call is routed to this personal voicemail box but not to the group voicemail box.
|
|
|
|
| In HiPath 3000 V7 and earlier systems, if a remote station does not answer, outgoing internal calls from an SIP workpoint via Call Management are not forwarded to the next destination on the call destination list. Forwarding is blocked in call processing, the payload data path must be negotiated dynamically, instead of just once (as implemented). However, dynamic negotiation is not possible with SIP workpoints.
|
| This restriction is no longer in place on HiPath 3000 V8 and later systems.
|
|
