Vector Routing to SIP Trunks

[RacingVert]

We have recently installed some new Convergys IVR's that we are sending calls to from the Avaya CM through SIP Trunks.
The problem we are running into is that if the SIP trunks are all busy, the Vector will stop trying to route to them after 6 attempts. If one of the SIP Channels becomes available after the 6th route to attempt the call will never be sent to the SIP Trunk Group. We can route the call anywhere else but not a SIP Trunk. The vector looks like this

1 wait-time 1 secs hearing R then silence
2 route-to number 37999 with cov n if unconditionally
3 announcement 38927
4 route-to number 37999 with cov n if unconditionally
5 wait-time 2 secs hearing music
6 route-to number 37999 with cov n if unconditionally
7 wait-time 2 secs hearing music
8 route-to number 37999 with cov n if unconditionally
9 wait-time 2 secs hearing music
10 route-to number 37999 with cov n if unconditionally
11 wait-time 2 secs hearing ringback
12 route-to number 37999 with cov n if unconditionally
13 wait-time 2 secs hearing music
14 route-to number 37999 with cov n if unconditionally
15 wait-time 2 secs hearing ringback
16 route-to number 37999 with cov n if unconditionally
17 announcement 38927
18 route-to number 37999 with cov n if unconditionally
19 announcement 38927
20 route-to number 3001 with cov n if unconditionally
21 stop

37999 is the dialed string for AAR Routing to the SIP trunk. 3001 is a VDN that routes the call to a VDN that would send the call to a different Skill. If I do a list trace when making a call to this vector, it looks like the vector is routing as it should but the call won't be sent.
Wondering if anybody has any ideas or has ran into this problem?

Thanks,

 

[montyzummer]

Have you got look ahead routing set in your route pattern?

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[RacingVert]

I have tried Next and Rehu on the LAR field on the route pattern with the same results. Thanks for the suggestion.

 

[kyle555]

How long do you want CM to wait before quitting?

Maybe there's a way you can use a hunt group or queuing mechanisms on the SIP trunk group to the IVR if you're desired operation is "route it to the IVR and hang on as long as necessary to be able to do that".

 

[montyzummer]

what is the denial event on failure , also what response is cm getting when busy ?? is it 486 busy here??? you could try

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[montyzummer]

refer but you would need ~r on the route to statement for that to apply , and change the setting on pg2 of the sip trunk group that pertains to refer , cant remember what that is off the top of my head its obvious , but worth a try.

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[Mlck]

Two entry in the route pattern with next in the LAR option work for me.

Don't follow the cows

 

[RacingVert]

I did a list trace tac and am seeing a denial event 1191.