12.1.13.2. Service Information

Rules
- Application provides only NumberToDisplay
(no NameToDisplay). In this case NameToDisplay can be determined
in 3 possible ways:
- If NumberToDisplay is configured as station in the system then
its PERSI name will be provided as NameToDisplay. If this station
has no PERSI, then NameToDisplay is empty.
- If PIN is entered on physical device, then PIN name will be provided
as NameToDisplay. If PIN data contains no name, then NameToDisplay
is empty.
- Otherwise PERSI name of physical device will be provided. If physical
device has no PERSI, then NameToDisplay is empty.
Application provides only NameToDisplay (no NumberToDisplay).
In this case the number can be determined in 2 possible ways:
- If PIN is entered on physical device, then PIN number is provided.
- Otherwise physical device number is provided.
- If physical device has PIN entered, it is preserved and restored after
the call is terminated.
- In the called party's Call Log, NumberToDisplay and NameToDisplay
are saved. If this number is called back, it might happen that the call
fails. The call will be established only if NumberToDisplay is
configured in the system. The same happens in case of call back scenarios.
- If the physical station has restricted number and/or name (i.e. it
is secret station, SSTNO=YES in AMO SBCSU), the presentation of
NumberToDisplay and NameToDisplay will not be restricted.
The presentation will be kept as configured if one of the two parameters
misses and is determined as described above (see 1 and
2).
- To enable APCID feature for outgoing CO calls, the CO trunks must
be configured with VNCO (send Virtual Subscriber Number
to CO) in AMO COT. If VNCO is not set, the identity of
the physical station will be sent to the CO partner.
- If physical station has PUBNUM or PUBNAME set, they
are ignored. NumberToDisplay and NameToDisplay will be
sent to CO partner.
- To enable APCID feature for call forward scenarios over network,
parameters FWDN and/or FNAN have to be set in AMO COT of
the involved trunks.
- It is the application's responsibilty to use this feature as law
enacted. Sending out a legal number and name than the real calling party's
identity to a public network is always the responsibility of the initiator
of the call.
- If a call is initiated for a station with NumberToDisplay
and NameToDisplay, they will be presented as long as the station
is not idle. It means that the application populated caller id information
will not change if the station invokes any of the following features:
- HOLD - if the agent puts its partner on hold and consults, Application
Populated Caller ID information is used for the consultation call.
- RETRIEVE - Application Populated Caller ID information is presented
to the partners, since MakeCall call has not terminated and agent didn't
go to idle.
- CONSULT - same as HOLD
- RECONNECT - Application Populated Caller ID information is presented
to the partners, since MakeCall call has not terminated and agent didn't
go to idle. TRANSFER - there are three cases for TRANSFER
- agent is transferred to a new partner - the new partner will see Application
Populated Caller ID since MakeCall call has not terminated and agent
didn't go to idle.
- agent transfers a CO call to agent 2 - the CO partner is connected
to agent 2 and sees the the original Application Populated Caller ID,
even if MakeCall call has terminated and agent went to idle (the CO trunks
must be configured with VNCO in COT).
- agent transfers a TIE or internal call to agent 2 - agent 2 identity
is presented to the TIE or internal partner. Application Populated Caller
ID is deleted because MakeCall call has terminated and agent went to
idle.
- CONFERENCE - Application Populated Caller ID is still presented to the
partners, since MakeCall call has not terminated and agent didn't go
to idle.
- SINGLE STEP TRANSFER - same as TRANSFER (see TRANSFER - there are
three cases for TRANSFER)
- ALTERNATE - agent toggles from active to held call and always Application
Populated Caller ID is presented