Aastra 400 Series System Manual page 205

Handling of collect calls
The handling of collect calls can be configured with various parameters per trunk
group, per user group, and per user:
Tab. 53 Handling collect calls: Trunk group configuration
Parameter
Handling of collect calls
• Reject all collect calls
• Allow all collect calls
• Depends on destination
Note:
When incoming calls arrive via SIP network interfaces, collect calls and
normal calls cannot differentiated. This is why with the setting Reject all
collect calls both collect calls and normal calls are rejected.
For the trunk group setting
ply:
• The call arrives at a user:
All collect calls are rejected if the parameter
in the user's assigned permission set.
• The call arrives at a system destination which automatically answers the call
(e.g. voice mail system):
All collect calls are rejected.
• For calls from the public ISDN network, the following also applies:
– All collect calls are rejected if the call arrives at a user group whose parameter
Offer collect calls
If the parameter
to those user group members whose permission set has the parameter
collect calls configured to Yes.
– The call goes to an external destination (e.g. via forwarding or if the call is to a
PISN user):
The external destinations are not called.
Note:
When incoming calls arrive via SIP network interfaces, collect calls and
normal calls cannot differentiated. All calls are handled like collect calls
from the public ISDN network.
System functions and features as of R3.0
syd-0367/1.3 – R3.0 – 03.2013
Meaning
Trunk group configuration
All collect calls are rejected.
Collect calls are handled as normal calls. The user can manually
reject a collect call by hanging up.
The configuration of the user's permission set or the user group
is decisive.
Depends on the
is configured to No.
Offer collect calls is configured to Yes, collect calls are offered
destination, the following responses ap-
Allow collect calls
Call routing
is configured to No
Allow
205