Aastra OpenPhone 61 User Guide OpenPhone 60/60 IP on Aastra 800 and OpenCom 10 - Page 65

Hunt group call numbers, Call forwarding chains

Page 65 highlights

Making Calls Special Calls/Functions Hunt group call numbers During system configuration, the system administrator can configure call forwarding destinations for hunt group call numbers. These destinations are called when all users of a hunt group are busy and/or when a call is not accepted by any member of the hunt group within a certain time interval. You cannot view or change this call forwarding on your device. In addition, the system administrator can determine whether you can forward incoming calls to the hunt group call number or not. If the system administrator does not permit call forwarding for your hunt group call number, any call forwarding that you have programmed on your device is not carried out upon a hunt group call. Call forwarding chains The system administrator can configure the system so multiple call forwarding instances can be linked one to another to form a chain. A simple example: user A forwards to user B, who then forwards to user C. A call for user A is then directly signalled to user C. A setting in your user group regulates which call number appears on your device when a call which has been forwarded multiple times is signalled on your device: you will see either the call number of the last user who programmed the last call forwarding in the chain, or the call number of the first user in the chain. The number displayed is also saved to the caller list for missed calls. The system prevents call forwarding chains from forming a loop, e. g. when the call forwarding destination refers back to the call forwarding source. When the system detects a call forwarding loop, no further call forwarding is carried out. This can mean that - despite call forwarding being programmed - calls are nonetheless signalled on your device. A loop is also detected during call deflection. If you receive a call via a call forwarding chain and wish to deflect it to a destination call number which is already in the call forwarding chain, a negative acknowledgement tone is heard and the call signalling on your device will continue. Contact your system administrator if call forwarding is not functioning as expected on your device. The system administrator is able to analyse call forwarding chains and eliminate any possible conflicts. 61

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124

Making Calls
Special Calls/Functions
61
Hunt group call numbers
During system configuration, the system administrator can configure call for-
warding destinations for hunt group call numbers. These destinations are called
when all users of a hunt group are busy and/or when a call is not accepted by any
member of the hunt group within a certain time interval. You cannot view or
change this call forwarding on your device.
In addition, the system administrator can determine whether you can forward
incoming calls to the hunt group call number or not. If the system administrator
does not permit call forwarding for your hunt group call number, any call for-
warding that you have programmed on your device is not carried out upon a hunt
group call.
Call forwarding chains
The system administrator can configure the system so multiple call forwarding
instances can be linked one to another to form a chain. A simple example: user A
forwards to user B, who then forwards to user C. A call for user A is then directly
signalled to user C.
A setting in your user group regulates which call number appears on your device
when a call which has been forwarded multiple times is signalled on your device:
you will see either the call number of the last user who programmed the last call
forwarding in the chain, or the call number of the first user in the chain. The
number displayed is also saved to the caller list for missed calls.
The system prevents call forwarding chains from forming a loop, e. g. when the call
forwarding destination refers back to the call forwarding source. When the system
detects a call forwarding loop, no further call forwarding is carried out. This can
mean that – despite call forwarding being programmed – calls are nonetheless
signalled on your device.
A loop is also detected during call deflection. If you receive a call via a call for-
warding chain and wish to deflect it to a destination call number which is already
in the call forwarding chain, a negative acknowledgement tone is heard and the
call signalling on your device will continue.
Contact your system administrator if call forwarding is not functioning as
expected on your device. The system administrator is able to analyse call for-
warding chains and eliminate any possible conflicts.