Adjunct not answering?

[n25]

Hi, I just wanted to ask if I'm doing something wrong with this vector:

01
02 wait-time 0 secs hearing ringback
03 adjunct routing link 14
04 adjunct routing link 15
05 wait-time 10 secs hearing music
06 route-to number 7603 with cov n if unconditionally
07 stop
08
09
10
11

And here is a trace on my extension calling a VDN (177800) that routes to it:

time data

10:29:23 dial 177800
10:29:23 vector 234 cid 0x2e6a
10:29:23 active announcement 1280 cid 0x2e6a
10:29:23 xoip: faxff modemff ttyff 10.10.213.34:30776 (igc)
10:29:23 xoip: faxff modemff ttyff 10.20.213.9:18828 (igc)
10:29:23 hear annc board 25A03 ext 1280 cid 0x2e6a
10:29:33 dial 7603
10:29:33 ring vector 399 cid 0x2e6a
10:29:33 G729A ssff ps:30 rn:101/101 10.3.207.175:16704 10.10.213.33:18380
10:29:33 xoip: fax:Relay modemT tty:US 10.10.213.33:18380 uid:0x8a8d
10:29:33 active station 28357 cid 0x2e6a
10:29:34 add service observer station 186162 cid 0x2e6a
10:29:34 G729 ssff ps:30 rn:6/101 10.10.218.2:4098 10.10.213.33:18384
10:29:34 xoip: fax:Relay modemT tty:US 10.10.213.33:18384 uid:0x5b4b
10:29:38 idle trunk-group 113 member 31 cid 0x2e6b

at 10:29:33 after hearing the 10 second music it routes to VDN 7603 (default queue), I never got routed to the adjunct links. Is there a way to validate why is this happening? Is there something wrong with the vector? I've pinged both AES servers and they are responding.

 

[koglass]

What do you have collecting the digits to send back to the Adjunct Routing Step? Usually it is an IVR collecting digits and then giveing them to the step in the vector to route the call to the correct place. Here is the definition out of the Avaya Documentation for Adjunct Routing.

About Adjunct Routing
Adjunct Routing provides a means for an Adjunct Switch Application Interface (ASAI) processor
to specify the destination of a call when it encounters an adjunct routing link vector
command during vector processing.
An adjunct is any processor that is connected to a switch that can use the ASAI protocol. The
adjunct makes a routing decision according to caller information and/or agent availability, and
returns a call route response to the switch.
The switch provides information in an ASAI route request message that the adjunct application
uses to access a database and determine a route for the call. In a typical application, the ASAI
adjunct might use the dialed number, the Calling Party Number (CPN/BN), or the digits that are
collected by way of Call Prompting to access caller information and thereby determine an
appropriate call route.
Adjunct Routing can be used in conjunction with the Call Prompting and Look-Ahead Interflow
features. When combined with one of those features, the following rules apply:
? When combined with Call Prompting, Adjunct Routing can pass up to 16 digits that are
collected from the last relevant collect digits vector command.
? When combined with Look-Ahead Interflow (LAI), Adjunct Routing can pass the LAI
information element or other call center-related data (with enhanced Information
Forwarding) that was passed from the originating switch in the ISDN message or
associated with the call from the local switch.