I have the following requirement from a customer:
1) I have two users groups
2) User group A can’t transfer external calls to User Group B
3) User group B is able to transfer external calls to User Group A
4) User group A and B can transfer external calls inside their own group.
Does anybody know how to do that?
I’ve played with Connection/Transfer COS unsuccessfully because the rules of these COS talking about the Category between the caller (trunk COS in this case) and the called set but it doesn’t take into account the intermediate set (who makes the enquiry call).
Transfer Feature Configuration
-
knightr1der
Welcome to AU !
Does this help?
TRANSFER CATEGORY
This table determines the compatibilities to transfer from one category of terminations to other categories of terminations.
The transfer category is the same as the connection category (see this chapter): The assignment of a termination to a connection category provokes its assignment to the transfer category of the same rank (example : set allocated the to connection category Number 1 = allocated to transfer category Number 1).
Transfer category Id.
Each window concerns a category (example: category 10).
Transfer category
0 for NO, 1 for YES, and % for any value:
For a determined category, the transfer of each category 0 to n is authorized or forbidden.
If the termination A category is compatible with termination B category, a termination C which communicates with A can transfer A to B. Compatibility is not converse (to be converse, the category of B must be compatible too; in this case, C which communicates with B can transfer B to A).
Examples:
The transfer compatibility of the termination of category 1 with terminations of category 15 is authorized:
Category 15: 1
The transfer compatibility of the termination of category 1 with terminations of category 16 is forbidden:
Category 16: 0
Does this help?
TRANSFER CATEGORY
This table determines the compatibilities to transfer from one category of terminations to other categories of terminations.
The transfer category is the same as the connection category (see this chapter): The assignment of a termination to a connection category provokes its assignment to the transfer category of the same rank (example : set allocated the to connection category Number 1 = allocated to transfer category Number 1).
Transfer category Id.
Each window concerns a category (example: category 10).
Transfer category
0 for NO, 1 for YES, and % for any value:
For a determined category, the transfer of each category 0 to n is authorized or forbidden.
If the termination A category is compatible with termination B category, a termination C which communicates with A can transfer A to B. Compatibility is not converse (to be converse, the category of B must be compatible too; in this case, C which communicates with B can transfer B to A).
Examples:
The transfer compatibility of the termination of category 1 with terminations of category 15 is authorized:
Category 15: 1
The transfer compatibility of the termination of category 1 with terminations of category 16 is forbidden:
Category 16: 0
Hello; thank you for your tips.
However, I've reproduced the first 2 options (transfer configuration between the two groups) but there is a problem with the last requirement (transfer within the groups) at the same time.
Have you tried to do it?
The problem is that if you forbid the caller Transfer COS to be connected to a user group, then automatically you’re disabling “intraâ€
However, I've reproduced the first 2 options (transfer configuration between the two groups) but there is a problem with the last requirement (transfer within the groups) at the same time.
Have you tried to do it?
The problem is that if you forbid the caller Transfer COS to be connected to a user group, then automatically you’re disabling “intraâ€
