Got a question,
I have a VDN which points to a simple vector with 2 lines: a route-to command that forwards the call off-net to an 800#, and a stop command. Simple enough.
I received a complaint today of a delay in the transfer of a call through this VDN / Vector. When I tested by transfering a call to the VDN, it seemed like it took about 5-8 seconds for the call to finally ring on the 800#. When I direct-dialed the 800#, it seemed to go through without delay.
I tested by running a list trace VDN and Vector from the emulator, and the call routed through both of them in around a second.
Given that: 1) Both VDN/Vector transfer and dialing direct use the same ARS routing. 2) The traces indicate queue flow-through in a second, my conclusion is that this is a CO / Carrier routing problem. However - I can't account for why dialing the number direct has no delay. Thus I can't trust my conclusion.
Has anyone experienced this? What could be accounting for the off-net delay through the vector but not via direct dial?
I have a VDN which points to a simple vector with 2 lines: a route-to command that forwards the call off-net to an 800#, and a stop command. Simple enough.
I received a complaint today of a delay in the transfer of a call through this VDN / Vector. When I tested by transfering a call to the VDN, it seemed like it took about 5-8 seconds for the call to finally ring on the 800#. When I direct-dialed the 800#, it seemed to go through without delay.
I tested by running a list trace VDN and Vector from the emulator, and the call routed through both of them in around a second.
Given that: 1) Both VDN/Vector transfer and dialing direct use the same ARS routing. 2) The traces indicate queue flow-through in a second, my conclusion is that this is a CO / Carrier routing problem. However - I can't account for why dialing the number direct has no delay. Thus I can't trust my conclusion.
Has anyone experienced this? What could be accounting for the off-net delay through the vector but not via direct dial?