cannot call one number

[evan631]

There is a phone number that is confirmed active that we cannot call.  When we dial the number we receive a fast busy.

Is there something I can look at to see what is going on with the call?  I looked at SMDR logs and see the calls to this number, but SMDR tells me nothing.

I feel this is going to be a carrier issue, but I thought I'd ask you guys.

-Evan

[ralph]

I've seen this happen a few times.
It's always been the carrier.
If you see the call in the smdr going out the same as any other call it will be the carrier.

Ralph

[VinceWhirlwind]

There is a phone number that is confirmed active that we cannot call.  When we dial the number we receive a fast busy.

Is there something I can look at to see what is going on with the call?  I looked at SMDR logs and see the calls to this number, but SMDR tells me nothing.

I feel this is going to be a carrier issue, but I thought I'd ask you guys.

-Evan

I had one of these the other day. Every other number could be dialled fine, and that destination could accept calls from any other number but ours.
Plus it was intermittent.
 
I used this call trace:
EDT TRACE TSP L2L3 3 1 2 1
 
And I could see this in it:
    -0101010 Cause code         : network congestion   
 
Turned out the issue was the remote end, instead of just answering the call it was trying to renegotiate something and the carrier was sending back the congestion message as soon as that happened.

[evan631]

I ran the trace below, but now how do I stop it?  I even closed out the maintenance command window then reopened, and still tracing.

There is a phone number that is confirmed active that we cannot call.  When we dial the number we receive a fast busy.

Is there something I can look at to see what is going on with the call?  I looked at SMDR logs and see the calls to this number, but SMDR tells me nothing.

I feel this is going to be a carrier issue, but I thought I'd ask you guys.

-Evan

I had one of these the other day. Every other number could be dialled fine, and that destination could accept calls from any other number but ours.
Plus it was intermittent.
 
I used this call trace:
EDT TRACE TSP L2L3 3 1 2 1
 
And I could see this in it:
    -0101010 Cause code         : network congestion   
 
Turned out the issue was the remote end, instead of just answering the call it was trying to renegotiate something and the carrier was sending back the congestion message as soon as that happened.

[ralph]

CCS Trace dis

Ralph

[evan631]

thanks for the quick reply!

CCS Trace dis

Ralph

[sarond]

If you used EDT TRACE just run the command again to stop