Lucent Technologies 555-230-220 User Manual
ASAI and Set Value Capabilities
10-4
Issue 7 May 1998
Communications Server CallVisor ASAI Protocol Reference
,
555-230-221.
Considerations
MWL
System cold starts cause the ECS to lose the message MWL status. Hot starts
(PE interchange) and warm starts do not affect the MWL status.
(PE interchange) and warm starts do not affect the MWL status.
To keep the MWL synchronized with the other adjuncts, the ASAI adjunct must
use the Set Value capability to update the MWL whenever the link between the
ECS and adjunct comes up from a cold start.
use the Set Value capability to update the MWL whenever the link between the
ECS and adjunct comes up from a cold start.
When an ASAI adjunct has turned on a station’s MWL and the station user
retrieves messages using the station display, then the station display shows the
message “You have adjunct messages.”
retrieves messages using the station display, then the station display shows the
message “You have adjunct messages.”
The MWL can only be turned on for a station extension. Starting with G3V4, the
Message Waiting Lamp on a station may track that physical extension or any
other physical extension. This depends on the administration of the station. In an
EAS environment, this lamp may track an agent’s messages, depending on the
system features administration.
Message Waiting Lamp on a station may track that physical extension or any
other physical extension. This depends on the administration of the station. In an
EAS environment, this lamp may track an agent’s messages, depending on the
system features administration.
The MWL cannot be turned on for an EAS agent through ASAI (a logical
extension may not be specified in the ASAI request for turning on the MWL).
Thus, this means that an ASAI request to turn on a particular MWL at a physical
station may or may not result in that MWL actually turning on.
extension may not be specified in the ASAI request for turning on the MWL).
Thus, this means that an ASAI request to turn on a particular MWL at a physical
station may or may not result in that MWL actually turning on.
Flexible Billing
1. When an ASAI adjunct makes a Flexible Billing request, the ECS normally
passes the request onto a PRI trunk on the call. The PBX does not keep a
timer while waiting for a response. “No user responding” is sent to the ASAI
adjunct only when: 1) the PRI trunk providing the Flexible Billing service is
dropped from the call before the response is returned to the PBX, or 2) a
second billing request arrives before the first has been replied to.
timer while waiting for a response. “No user responding” is sent to the ASAI
adjunct only when: 1) the PRI trunk providing the Flexible Billing service is
dropped from the call before the response is returned to the PBX, or 2) a
second billing request arrives before the first has been replied to.
It is recommended that the adjunct keep timers to determine when a
Flexible Billing request has not received an answer in a reasonable time.
The “No user responding” cause value from the ECS will make the adjunct
aware of the problem, but it will be too late to try again.
Flexible Billing request has not received an answer in a reasonable time.
The “No user responding” cause value from the ECS will make the adjunct
aware of the problem, but it will be too late to try again.
2. A billing change cannot be sent after the trunk has disconnected from the
call nor before the call has been answered. It is not necessary for the call to
reach an agent before the billing can be changed. The network considers a
call answered if it connects to an announcement or to a converse agent.
reach an agent before the billing can be changed. The network considers a
call answered if it connects to an announcement or to a converse agent.