8.4.1.5. Service Information 
- You must follow the generating order given. In particular, before you configure the keys with the AMO TAPRO you must set TEAMBIT with the AMO SDAT because otherwise there is not enough memory for the RNGXFER keys.
- Give all nodes in a network in which the "network-wide team" is configured a new central code with the AMO ZAND that cannot be reset via AMO (only with patch). Various AMOs, which implement the new functions, query this code. This allows mixed operation and the configuration of network-wide teams or "internal teams" of the new kind and internal teams with AMO CHESE. However this should be the exception!
- You can assign a secretary to one or more executives; unlike the "old" CHESE, this assignment is not fixed because it wanders through the delegate function.
- You essentially implement the network-wide team with the feature "network-wide call pickup".
- Delegate function: Each secretary has a REP key to transfer his or her function to a delegate or representative. The delegation can only be to another secretary in this team and is a fixed assignment. You can only change the assignment by disbanding and reconfiguring the team, but this is not critical because the "care" of one or more executives can also be actively transferred by pressing the appropriate RNGXFER key(s). The RNGXFER key at the affected executive is reprogrammed when the delegation is activated.
- Use the AMO AUN to assign a three-digit team number to each station number in a network-wide team, the prime line of the executive, and all phantom lines at the secretaries assigned to this executive. DMS uses this number, which must be unambiguous throughout the network, only for administration purposes. The AMO does not check that the number is unambiguous. The "private line" of the executive (phantom) and the prime line of the secretary telephone do not receive a team number.
- The station devices of network-wide team members are configured as key sets.
- If necessary, the executive is given a "phantom line" as a private line.
- Each secretary receives one "phantom line" for each executive assigned to him or her. These must have the code for group call in their COS so that calls to the executive can also be signaled at the secretary.
- The executive's prime lines and the secretary's phantom lines are identified in the line memory as "executive" or "secr" (AMO SDAT). The executive's "private line" does not receive an executive code.
- Ring transfer: Each executive receives one RNGXFER key that he or she can use to transfer calls (or take them back) on his or her prime line to the secretary. The station number of the currently assigned secretary's phantom line for this executive is entered on the RNGXFER key. If this secretary activates a delegate, then the RNGXFER key is updated with the station number of the corresponding phantom of the current secretary. If several RNGXFER keys were activated at the secretary, the RNGXFER key destinations for all affected executives are rewritten when the delegation is activated. Each secretary receives a RNGXFER key for each assigned executive; he or she can also activate or deactivate the ring transfer for each executive with the key. Thus the secretary can actively take over the delegation for each executive of this team by pressing the corresponding RNGXFER key. In this case, the destinations are also reprogrammed on the RNGXFER keys of the affected executive.
- PUS keys are not configured.
- Direct station selection network-wide
- Direct station selection (DSS) destinations (both internal and external) for "network-wide teams" are configured only by AMO (AMO ZIELN); the DSS key is marked as "network-wide" if the destination is external. Use the pickup group to implement the network-wide relationship. The destination must be a member of a call pickup group that is on the source device. Use the new AMO ZIELN to edit all DSS destinations that are involved with the "network-wide team". You cannot change the destinations from a station device. To prevent a flood of messages concerning the signaling of the free and busy status of members of network-wide call pickup groups, station numbers that are entered somewhere as a network-wide DSS destination receive a special "direct station selection destination network-wide" identifier (AMO SDAT).
- Stations that have network-wide destinations on their DSS keys also receive a code in the line feature "source for network-wide DSS destination". The AMOs ZIEL and ZIELN evaluate this as regards regeneration.
- Each executive receives one DSS key for each secretary in the team. The contents are not reprogrammed when ring transfer is activated. Each secretary receives one DSS key for each executive in the team.
- Call pickup groups for network-wide team:
|
1 executive/1 secretary
|
|
|
Call pickup group
|
prime line (Pri) executive + phantom (Pha) of
the secretary for executive
|
|
2 executive/1 secretary
|
|
|
call pickup group 1:
|
Prime line executive1 + phantom of the secretary
for executive 1
|
|
Call pickup group 2:
|
Prime line executive2 + phantom of the secretary
for executive 2
|
|
4 executive/2 secretary
|
|
|
Call pickup group 1:
|
prime line C1 + phantom S1 for executive 1 +
phantom S2 for executive 1;
|
|
Call pickup group 2:
|
prime line C2 + phantom S1 for executive 2 +
phantom S2 for executive 2;
|
|
Call pickup group 3:
|
prime line C3 + phantom S1 for executive 3 +
phantom S2 for executive 3;
|
|
Call pickup group 4:
|
prime line C4 + Phantom S1 for executive + phantom
S2 for executive 4
|
|
4 executive/4 secretary
|
|
|
Call pickup group 1:
|
Pri_C1 + Pha_S1_ C1 + Pha_S2_ C1+Pha_S3_C1 +
Pha_S2_C1;
|
|
Call pickup group 2:
|
Pri_C2 + Pha_S1_ C2 + Pha_S2_ C2+Pha_S3_C2 +
Pha_S2_C2;
|
|
Call pickup group 3:
|
Pri_C3 + Pha_S1_ C3 + Pha_S2_ C3+Pha_S3_C3 +
Pha_S2_C3
|
|
Call pickup group 4:
|
Pri_C4 + Pha_S1_ C4 + Pha_S2_ C4 + Pha_S3_C4
+ Pha_S2_C4;
|
- If there is more than one secretary, you must configure a call pickup between the prime lines of the secretary telephones so that they can accept calls for one another.
- Destination entries (station numbers) RNGXFER key at executive prime
line executive + phantom secretary for the executive RNGXFER keys at
secretary per executive RNGXFER1: prime line executive 1 + phantom for
executive 1 RNGXFER2: prime line executive 2 + phantom for executive
2, etc. Secretarial function transfer keys at the secretary telephone You
must save the following for each REP key to activate the function transfer:
Station number of the secretary (prime line), station number of the delegate
(prime line), and station number of each assigned executive Prime line
executive 1 + phantom of the delegate for this executive Prime line executive
2 + phantom of the delegate for this executive, etc.
- Team DSS key at executive: Prime line for each secretary
- Team DSS key at secretary Prime line for each executive
- Voice calling groups. Voice calling goes only to station numbers that are on NAME or DSS keys. These keys must have the code for "voice calling" and "write protection" (AMO ZIELN) and can only be administered via AMO. Therefore you must use the AMO ZAND to set the code "voice calling only in configured user groups" (VCOCUG=YES). This feature has nothing to do with "network-wide teams" and is also not limited to certain types of station devices.
- You can also add station devices without the "executive" or "secretary" code in the network-wide pickup groups for "network-wide teams". In this way you can implement network-wide direct station selection destinations that are not directly involved in the executive/secretary relationship.
- General tips concerning the difference between DSS and NAME keys besides the LED, for the DSS key: - FWD is ignored - Do-not-disturb is ignored - With a master HT, the master is called (not the next free station) - Automatic camp-on when destination is busy
- Network-wide team also functions with the APS exchange if the current data is regenerated and then again regenerated, and this is only in individual network nodes.
- It is possible to have mixed operation, or network-wide teams or "internal teams (key systems)" and internal CHESEs, in a system. However this should be the exception!
- No station in a network-wide team is allowed to be in a local Chese.
- The secretary phantom lines must have the group call feature.
- The executive and secretary prime lines must have the FWDFAS and FWDBAS classes of service for the RNGXFER function.
- The prime line of the secretary telephone is the private line as well.
- You must use a terminal with at least 12 function keys for the feature.
- The Remote FWD feature must be released network-wide.
- You can add team members to call pickup groups with teams or remove them only by removing the entire team. Then you must reconfigure the team. The same also applies to moving team members from one node to another. You can, however, supplement or reduce "team call pickup groups" by station numbers that do not have the executive or secretary code (AMO SDAT), for example, because of DSS destination links. (Exception: primary secretary line has secretary code but does not belong to the team.)
Network requirements
- Fictitious network-wide call pickup groups for signaling network-wide direct station selection For signaling the states (ringing, free, busy) of all network-wide direct station selection destinations, configure a "fictitious network-wide call pickup group" to optimize the flood of TSC messages. This signaling is handled over this group. This call pickup group must be in each node that has a direct station selection key configured with a network-wide destination or a network-wide direct station selection destination. This group must be configured ahead of time. In each node in this call pickup group, you must enter remote links to all other nodes that you want to signal. Enter the REMAC to the correct node as the "remote link". Always use the first remote group number as the REMGRNO, although this entry is not evaluated.
- To avoid having to constantly expand this call pickup group, you should enter all nodes that could be considered for the network-wide team in this group as a user during the initial configuration.
- You must configure this call pickup group with a fictitious STN (card subscriber). Use any call pickup group number or the next free one as the "fictitious" group number.
- The parameter NWRES in the AMO AUN identifies the fictitious call pickup during configuration.
- The COT parameters CFVA, TSCS, and BLOC must be included in the COT for the circuits with the network-wide team.
Special features of the network-wide call pickup
- Separate delete branch for the fictitious call pickup group.
- You cannot add to this call pickup group with STN and you cannot delete the fictitious device.
- When you display "All" or areas, they are specially marked in the output. New error messages come with each AMO editing attempt that is denied.
- You can configure only one fictitious call pickup group in a node.
- You are not allowed to simultaneously mark the fictitious group as a "team group". You should check this on both sides.
- You must set all remote signaling parameters (REMSIGxx) to "yes".
- You can regenerate the fictitious call pickup group and you can do this in any order.
- The solution also functions if the group number of the fictitious call pickup group in a node should change for any reason.