Here's our scenario:
1. The caller places a call to our 800 number which maps to DID xxx-xxx-xxxx.
2. This DID also happens to be configured as a CDN, which as I'm told from this forum, can not be configured with a NCOS like a phone extension. All calls placed to this DID number map to our local Qwest T1 (Route 3).
3. This CDN/DID is used in our call routing software and needs to be able to send the call back out our long distance T1 (separate route - Route 0) if a long distance agent is available to take the call.
4. Currently when we try to route the call from this DID/CDN to a long distance line, the caller hears a fast busy tone.
I assume the reason we are hearing the fast busy tone is because we are trying to send the call back out the same Route the call is coming in on, when we should be sending the call back out our long distance trunk.
So, my question is this: How can a call be sent in on a local trunk and sent back out on a long distance trunk. Is there some trunk to trunk transfer setting to change that may be set to NO?
From what I've read and asked about before on this forum is that we are certainly using BARS because we dial a 9+1+number to get out to a long distance number, which utilizes our LD trunk..Right?
Our local area code is: 480, which when I print our the NPA for 1480 is shows me that I am using RLI 3.
When I print out the FRL in LD 86 for RLB/RLI 3 it displays FRL 3 with a DMI 2 using Rout 0 (this is odd since Ro
One of the area codes we need to send the call to is: 217, which when I print out the NPA for 1217 shows me that I am using RLI 3.
The same information is printed in LD 86 for RLI 3 as our local area code of 480.
Is this a trunk to trunk issue? A NCOS setting on the trunk? Any ideas?
Thanks everyone!
1. The caller places a call to our 800 number which maps to DID xxx-xxx-xxxx.
2. This DID also happens to be configured as a CDN, which as I'm told from this forum, can not be configured with a NCOS like a phone extension. All calls placed to this DID number map to our local Qwest T1 (Route 3).
3. This CDN/DID is used in our call routing software and needs to be able to send the call back out our long distance T1 (separate route - Route 0) if a long distance agent is available to take the call.
4. Currently when we try to route the call from this DID/CDN to a long distance line, the caller hears a fast busy tone.
I assume the reason we are hearing the fast busy tone is because we are trying to send the call back out the same Route the call is coming in on, when we should be sending the call back out our long distance trunk.
So, my question is this: How can a call be sent in on a local trunk and sent back out on a long distance trunk. Is there some trunk to trunk transfer setting to change that may be set to NO?
From what I've read and asked about before on this forum is that we are certainly using BARS because we dial a 9+1+number to get out to a long distance number, which utilizes our LD trunk..Right?
Our local area code is: 480, which when I print our the NPA for 1480 is shows me that I am using RLI 3.
When I print out the FRL in LD 86 for RLB/RLI 3 it displays FRL 3 with a DMI 2 using Rout 0 (this is odd since Ro
One of the area codes we need to send the call to is: 217, which when I print out the NPA for 1217 shows me that I am using RLI 3.
The same information is printed in LD 86 for RLI 3 as our local area code of 480.
Is this a trunk to trunk issue? A NCOS setting on the trunk? Any ideas?
Thanks everyone!