Route List does not work when number is called from Nupoint.

[mszodiac]

Hi Everyone!

I have a speed call created with an actual number that dials over XNET trunking.  In ARS, this speed call is entered that goes to Route List.  The 1st route goes to XNET trunking, 2nd route goes to ISDN trunks.

For example,
Speed call: 560-5000 - Actual number:89055000 --> This goes to XNET trunking

In ARS:
89055000 goes to route list 20
Route List 20 - 1st route = 10 --> goes to XNET
                    - 2nd route = 20 --> goes to E1
                      Route 20 goes to DMI that removes all the numbers and inserts a commercial number.

If I busy the XNET trunk and call the speed call from my desk phone, the call gets routed to the E1.

However, If I dial the speed call from Nupoint while XNET trunk is busy, I get the message "I'm sorry, extension 5605000 is not available.

I can call the speed call from Nupoint if it goes to just one route - either XNET, or E1, but not a route list.

Any idea what I'm missing?

[ZuluAlpha]

How is it being called from the NuPoint?

[mszodiac]

From a call flow.  On it it says, to reach emergency services, press 1.  1 is a blind transfer to the speed call.

[mszodiac]

Which timer kicks in on the route list? Where do we tell the system to wait a specific time before it tries the 2nd route, then wait for a specific time, then try the 3rd route?

[johnp]

There is no timer for a route list. If the first choice isn't available the it tries the second, and so on.

[mszodiac]

I got this figured out.

The 2nd route which goes to the E1 had expensive route tone enabled.  I'm guessing the Nupoint hears this as a disconnect.

My route list worked as soon as I set the expensive route tone to "No".