Adjunct Routing not working 1

[uzumaki]

My setup is like this:

Avaya S87xx + AES + Cisco PG + CMS

I have a main vdn 210000 vec 1000

01 wait-time 0 secs hearing ringback
02 adjunct routing link 10
03 wait-time 999 secs hearing ringback
04 announcement 45400
05 stop

and a return vdn 210085 vec 1050

01 wait-time 2 secs hearing ringback
02 queue-to skill 1000 pri h
03 stop

however i cant get this thing work because everytime i do a trace its always playing the annoucement (45400) in step 4, Its like it is skipping the step 3 in the main vdn.

My Connectivity with the CMS is not yet established and i dont have any idea if the call adjunct routing will work even the CMS is down.

 

[optionsleft]

What is the application that is using the adjunt link? The CMS has nothing to do with the adjunct routing anyway.

You can check on the CM who is using the CTI link "list cti"

mwooks

 

[uzumaki]

I'm routing to the Cisco PG via CVLAN, so if a caller comes all calls will be directed to this Main VDN. Cisco PG will be do the final decision and do a return VDN 210085 vec 1050 but this is not happening.

 

[optionsleft]

Check the following:

a. status of aes interface,link and cti in the Communcation Manager
b. status cti-link no.


And in the AES check to see if the CVLAN service is running and also the switch connection interface.

Hope this may help.

 

[uzumaki]

The CTI link is up and running including the CVLAN... No idea what went wrong. ANy other ideas?

 

[uzumaki]

We got this fix. In the new CM5.1.2 you need to turn-on the adjunct routing link in disp sys cus option page 11 even though you enabled the ASAI core and ASAI plus. This is basically a new added feature in the latest CM.

Previous CM versions when you enable the CTI link and ASAI Core/Plus you can route to adjunct already. But this case cannot unless turn-on the adjunct routing.

 

[optionsleft]

Great. Very useful tips.

Thanks