DDT; Reviewed:
SPOC 10/18/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
support redirecting a call before it is answered (using a SIP 302), and therefore the vector must
include a step that results in answering the call, such as playing an announcement, prior to
redirecting the call using REFER.
A detailed verification of such call with Communication Manager traces can be found in Section
9.1.2 for a Verizon IP Toll Free SIP-connected alternate destination. In this example, the Verizon
IP Toll Free service can be used to pass User to User Information (UUI) from the redirecting site
to the alternate destination.
1. Same as the first five steps in Figure 3.
2. Communication Manager routes the call to a vector, which answers the call, plays an
announcement, and attempts to redirect the call by sending a SIP REFER message out the
SIP trunk from which the inbound call arrived. The SIP REFER message specifies the
alternate destination in the Refer-To header. The SIP REFER message passes back through
Session Manager and the Avaya SBCE to the Verizon IP Toll Free service network.
3. The Verizon IP Toll Free service places a call to the target party contained in the Refer-To
header. Upon answer, the calling party is connected to the target party.
4. The Verizon IP Toll Free service notifies the Avaya CPE that the referred call has been
answered (NOTIFY/sipfrag 200 OK). Communication Manager sends a BYE. The calling
party and the target party can talk. The trunk upon which the call arrived in Step 1 is idle.
Verizon
IP Toll Free
Service
1
1
1
PSTN
PSTN
Phone
1
Avaya Session
Border
Controller
Avaya Aura®
Session
Manager
OK
PHONEMESSAGE
CONTACTS MENU CALL LOG
VOLUME
ABC DEF
JKL MNOGHI
1 2 3
4 5 6
TUV WXYZPQRS
7 8 9
*
[
0 #
.,@
MUTESPEAKER
HEADSET
FORWARD
Agent / Phone
Avaya Aura®
Communication
Manager
1
2
Alternate
Destination
3 3
2
2 4
4
4
Figure 4: Inbound Verizon IP Toll Free– Post-Answer SIP REFER Redirection Successful
3.2.3 Inbound IP Toll Free Call with Unsuccessful Network Call Redirection
The next call scenario illustrated in Figure 5 is similar to the previous call scenario, except that the
redirection is unsuccessful. In theory, if redirection is successful, Communication Manager can
“take the call back” and continue vector processing. For example, the call may route to an
alternative agent, phone, or announcement after unsuccessful NCR.
1. Same as Figure 4.
2. Same as Figure 4.