Technical References

60 Error! No text of specified style in document.
60
For each RB
d
B created above, create a single peripheral target PTB
d
B with
the DNIS set to D. The network trunk group can be set to any valid
trunk group for the peripheral. Each PTB
d
B should target its
corresponding RB
d
B. Note that the same peripheral targets are used for all
routing clients.
For each of the PTB
d
B created above, create one label LB
dr
B for each routing
client R that will target calls to this translation route.
4.4.2. 113BAura Contact Center Post-Routed Translation Routes
Every translation-routed call goes through a post-route at the destination
peripheral (to get the label associated with the translation route DNIS). A
post-routed translation route goes through two post routes: one at the
source peripheral and one at the destination peripheral. If the source and
destination peripherals are the same Aura Contact Center ACD, the Aura
Contact Center PG handles the second post route directly without
involving the ACD.
To make this happen, create one label associated with the Aura Contact
Center PG routing client for each of the PTB
d
B defined above of the formTPF
FPT:
^XXXX
Where XXXX is the DNIS stored in PTB
d
B. When the PG receives such a
label as a response to a post route request, it issues a second post route
request using DNIS XXXX, gets back a new label, and returns the
response_type and response_value specified by that label to the GET
RESPONSE command that initiated the original post route request.
TP
PT Note that in the case being discussed, the translation route T is associated with
the Symposium ACD that is both the source and destination of the translation
route.