Delay in outbound calls 1

[mrdelite29]

What would cause a caller to have to wait a good 30 seconds before the number they are calling starts to ring? They are on a 200 ICP on a T1.

 

[paterson]

30 secs? Every outbound call? Every phone?

I would first verify the time delay. Then look in the COS of the phone for timers that have that time. Adjust the value, save the changes, make another call. Did it change?



_______________________________________________________________

If you did not take enough time to get it right the first time...

What makes you think that you have time to fix it?

 

[kwbMitel]

Most likely ARS conflict timer.

Try putting a fully entered number in ARS and see if the delay is removed.

You say T1. Do you mean PRI? If not, what is the T1 connected to?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mrdelite29]

The T1 is connected to a Smart jack provided by Nuvox Communications. There isn't an CSU/DSU there.


I just looked in the ARS(digit string)

The number leading Digit is 9, Return Dial Tone is Yes, and it is unrestricted.

Now we use 9 to access an outside like. So I went to Show String.

Click on attached link below.

 

[kwbMitel]

You need to determine when the trunk is being seized.

On the maintenence side, use the show status Bay Slot CCT to view the trunks. View the most likely trunk to get the next call. The trunk will show receiver active status when the ARS digits are being dialed. This will give you an idea of when the Nuvox gear is engaged.

Just guessing here but I notice you are not set up for 10 digit local calling. This might be part of the issue as there are very few places in NA where 10 digits are not required.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mrdelite29]

I'm having the users keep track of calls and how long it takes to connect and what time they called. Meeting with nuvox at 3pm to show them what's happening. It's not a problem on long distance trunks.

I may start removing some trunks to see if it will show that it might just be a trunk or set of trunks in the trunk group

 

[kwbMitel]

With LD calls not having the issue, it makes it even more likely that your issue is with 10 digit dialing.

try setting up a digit string for your local area code + 7 digits.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[mrdelite29]

I'll give that a try

 

[mrdelite29]

I think that was the problem. I added (Area Code) +7 like you said and they are reporting faster dial outs.

Thanks for the help!

 

[mrdelite29]

One more thing, in the digit strings form there was a 1 +10 digit to follow entry. I think that was causing a decision making process for certain calls that were follow a 1888 +7, 1866 +7, and 1800 +7. I believe the tech before was trying to make sure all 1800 went to the local trunks.

 

[kwbMitel]

The difference in routing is cost.

1-888, 1-877, etc are typically toll free calls and do not need to be restricted. (Same as local calls)

The 1+10, 011, and 0 calls can all be billable calls so are separated so that they can be restricted.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.