Outbound Disconnect by Carrier

[mikej97204]

I am having a problem where circuit outbound calls that go out QWest PRI T1's is being disconnected as soon as our G3r 9.5 pbx makes the call. Qwest said that they are seeing a Status Inquiry from us, which is what is causing the call to be dropped. If I route the calls out a different carrier, still PRI T1's, the call is completed just fine.

What is different about these calls over thousands of others that go out the same QWest T1's is that these calls are forwarded calls. Someone will call in on one of our 800 numbers, get a message prompt to dial an extention, they will dial a 4 digit extention and the call will be sent back out to a remote sales person. This is so the client doesn't have incurr long distance charges. This has worked for a long time and nothing has changed.

The Qwest techs that have been taking traces say it's the Status Inquiry that is causing the drop. I do not know what causes a Status Inquiry to be generated. Which is what I am trying to find out.

If I dial the 4 digit number internally it goes out over Qwest fine. If I dial the 800 number internally and then go through the prompt to dial the same 4 digit number, it goes out fine. It's only if I dial from a POTS line or out side our system that it gets disconnected as soon as the PBX dials it. One person said he saw this on a anti-spoofing setup by a carrier and what the call looks like is someone using our PBX illegally to make long distance calls. Qwest says they do not have that turned on and we would get a message if it was.

My main question is, what is a Status Inquiry and what is causing it to be generated? I don't have that answer and Qwest seems to be puzzled over it as well.

Thanks

Mike

 

[RTMCKEE]

Check the trunk group form. Page 2 left side towards the bottom.

Disconnect Supervision - Out?

Set to yes? if not (it's not by default) then change it to yes, and see if the call goes thru.

rtmckee

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1

 

[mikej97204]

On my ver 9.5 the Disconnect Supervision In? Out? is on page 1, but both In and Out are set to Yes.

I did check my other trunk groups that work and they are also all set to Yes for In and Out. So that is the same.


What I have done for those numbers affected is put a redirect in my routing to send them out my MCI carrier rather than the Qwest carrier. They work fine going out through MCI.

Thanks for the suggestion. As you can see, you are the first one to have a suggestion since I posted the question. Some things have easy answers and others don't. I guess this is one of those that others haven't run into. I hate having unique problems. <grin>

Thanks

Mike

 

[rejackson]

Are you saying that it has work for a long time on this PRI or is this a new one?

I think Qwest is fooling you into thinking they are dropping the call because of something your system is doing. I think your system is dropping the call.

Do a list trac tac # on the qwest trunk and do a test call. See if there is a denial event.

It sounds like a COR or COS problem between the incoming trunk, outgoing trunk, and maybe the auto attendant however that is implemented.

 

[mikej97204]

Hi Rejackson,

These are 4 PRI T1's that had existed for some time and where it had been working the way everything was configured. Then a few weeks or so before this problem, we had a problem where when we called someone, they could hear the caller but the caller couldn't hear them. We are all PRI and no VOIP. This problem turned out to be a switch problem at Qwest, which took them 3 weeks to find and admit they had a problem (more than just was were experiencing the problem). After that problem was fixed, then the above problem started happening. Nothing changed on my end, but something on the Qwest end did.

Now it is possible that Qwest had something mis-configured before the other problem and it was accepting calls from us in this paticular case all along. Then when they fixed their other problem, they did a software upgrade or fixed something in their programming that no longer accepted something from us that is not configured right in our PBX. I did have Avaya trained people look at our switch though and they said that there was nothing wrong on our end.

So it's hard to tell. I will try your suggestion though and see what it tells me. Thanks.

Mike