one station cannot dial 800 numbers

[tfolino]

I have a new user who cannot dial 800 numbers she gets a fast busy. She can dial local and long distance. Her COR and COS match every other station. If I put a bridged-appearance for another line on her phone she can make the 800 number call, so it's specific to her extension.

This extension has not been used in years and we at one time had an outside vendor who supported us but now it is up to me. Any help would be greatly appreciated.

 

[EPalle]

I would trace the station.
Open the EMULATOR (you can find it in ASA under the Advanced tab - Start Emulation).

Then use the command: LIST TRACE STATION xxxx
Where xxxx is the extension of the new user.

Then make a test call to a 800 number.
The trace should show what happens in the system.

Copy/paste it up here and we will have a look.

E.

 

[tfolino]

LIST TRACE Extension 8077



time data



18:43:48 G729A ssff ps:20 rn:1/1 192.168.0.153:16384 192.168.0.101:29248

18:43:56 dial 9180070087 routeREFIX|FNPA|ARS

18:43:56 term trunk-group 1 cid 0x280

18:43:57 dial 918007008747 routeREFIX|FNPA|ARS

18:43:57 route-pattern 210 preference 1 cid 0x280

18:43:57 seize trunk-group 1 member 20 cid 0x280

18:43:57 Setup digits 18007008747

18:43:57 Calling Number & Name 6165885503 NO-CPName

18:43:57 Proceed trunk-group 1 member 20 cid 0x280

18:43:59 denial event 1190: ISDN no circ/chan avail D1=0x53 D2=0x222

18:43:59 idle trunk-group 1 member 20 cid 0x280

VOIP data from: 192.168.0.101:29248

18:43:59 Jitter:3 2 2 6 5 3 4 4 1 3: Buff:30 WC:50 Avg:3

18:43:59 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0

18:44:01 idle station 8077 cid 0x280



Thanks for any help you can offer.

 

[EPalle]

So you got a denial event 1190 => No circuit or channel available.

According to the book:
[0x22/0xA2] -
No circuit/channel available/
Negative closed user group comparison (1TR6: AT&T ISDN Protocol)
Cause Value 34 indicates that the call cannot be completed because there is no appropriate
circuit/channel available to handle the call request, or congestion exists within the ISDN
network.
Communication Manager generates this Cause Value when a call is tandeming through
Communication Manager and the trunk group to be used for the outgoing leg is:
• In “all trunks busy” condition
• Otherwise unavailable for service
• Unreachable from the incoming trunk group due to Class of Restriction (COR), FRL, trunk-to-trunk transfer restrictions, or disconnect supervision restrictions

Not sure if this helps..... but it seems that all lines are busy, no lines available.
But I guess that is not the case.
What is in route 210??? Do the other phones also takes this route when dialing 800 numbers??

 

[tfolino]

I actually did this tracert after hours when no one was in the office. Also I put a bridged appearance of another line on her phone and she can make the calls without a problem. The thing is when you go to dial it actually grabs the line that blocks it so she has to concentiously think about pressing the other line on her softphone and if she forgets she has to start over. She works at fast paced job and this situation is not ideal at all.

Here is the Trace List from her 8077 IP Softphone but she is placing the call on her brdg-appearance of 8024. It goes out over the same route pattern and the call completes.

So it is specific to 8077.


LIST TRACE

time data

16:02:56 G729A ssff ps:20 rn:1/1 192.168.0.153:16384 192.168.0.101:27968
16:03:04 dial 9180070087 routeREFIX|FNPA|ARS
16:03:04 term trunk-group 1 cid 0x1ac
16:03:06 dial 918007008747 routeREFIX|FNPA|ARS
16:03:06 route-pattern 210 preference 1 cid 0x1ac
16:03:06 seize trunk-group 1 member 19 cid 0x1ac
16:03:06 Setup digits 18007008747
16:03:06 Calling Number & Name NO-CPNumber NO-CPName
16:03:06 Proceed trunk-group 1 member 19 cid 0x1ac
VOIP data from: 192.168.0.101:27968
16:03:07 Jitter:3 2 5 4 4 3 2 3 2 3: Buff:30 WC:30 Avg:3
16:03:07 Pkloss:0 0 0 0 0 0 0 0 1 0: Oofo:0 WC:1 Avg:0
16:03:09 Alert trunk-group 1 member 19 cid 0x1ac
16:03:14 active trunk-group 1 member 19 cid 0x1ac
VOIP data from: 192.168.0.101:27968

 

[MadAccess]

Try deleting the station and then duplicating a working station. That wont tell you what the issue is/was but may resolve it.

 

[tfolino]

I now have a second new user, ext 8072, with the exact same problem and just 5 minutes ago I deleted 8072 and then duplicated 8071 which is an extension that has worked for years and I still can't dial out toll-free.

If I put bridged call appearance on 8072 then I can dial out.

We had a Flex circuit put in this summer and I had an outside vendor configure thw switch for it and it's like he put some restriction out there on toll-free. I can't reach him and I just don't know where to look to resolve this.

Thanks for replying and any other suggestions you might have.

 

[dufus2506]

Does this always happen from the same toll free number? Have you tried different numbers?

It's entirely possible that the problem is at the distant end. The toll free number could just belong to a company that has too few circuits to carry the traffic.

Carpe dialem! (Seize the line!)

 

[tfolino]

It happens to all toll-free numbers we try to call. If you press the brdg-call appearance on that phone you can place the call but not on the primary call appearance for those extensions 8072 and 8077.

 

[98Converter]

It looks like you may be sending the caller-id of the station, and it may not be matching some sort of account record with your service provider. As you can see the ones that work, don't send the number, but the ones failing do...

Check your ISDN PUBLIC-UNKNOWN table or public-unknown-numbering depending on version and remove anything in there related to the extensions having problems.

Thanks,
98C

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[tfolino]

You have given me a good solid lead here but I have a few questions. We have taken over a portion of business from another company and hired two of their agents. Our agreement was to show their Company Name and phone number on the caller-id. I just found out two of our existing agents that back them up have that caller-id on two lines for Outbound customer calling can't make toll-free calls either. They can place calls to local and long distance numbers.

So why would we be able to make local or long distance on those lines with that caller ID but not the toll-free calls?

We have a Flex Reach circuit with AT&T. Is that who I would need to contact? I guess I'm still confused on them letting me pass that number on local and long distance calls.

I really appreciate your help on this.

 

[98Converter]

What does a call look like thats routing local or LD? Can you capture a trace and put it here. I wonder if they're using a different circuit going out...

Thanks,
98C

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[tfolino]

We only have one circuit since Summer, it's a Flex Reach circuit. We did used to have several different circuits but not anymore. Is there someplace i can check for how their outbound calls are routed?


LIST TRACE 8072

time data

12:54:24 G729A ssff ps:20 rn:1/1 192.168.0.154:16384 192.168.0.101:25660
12:54:31 dial 9144032708 routeREFIX|FNPA|ARS
12:54:31 term trunk-group 1 cid 0x1a
12:54:32 dial 914403270800 routeREFIX|FNPA|ARS
12:54:32 route-pattern 202 preference 1 cid 0x1a
12:54:32 seize trunk-group 1 member 17 cid 0x1a
12:54:32 Setup digits 14403270800
12:54:32 Calling Number & Name 6165885503 NO-CPName
12:54:32 Proceed trunk-group 1 member 17 cid 0x1a
12:54:34 Alert trunk-group 1 member 17 cid 0x1a
VOIP data from: 192.168.0.101:25660
12:54:34 Jitter:4 3 4 3 4 4 3 4 4 4: Buff:30 WC:20 Avg:3
12:54:34 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.0.101:25660
12:54:45 Jitter:26 30 31 4 5 6 4 4 4 5: Buff:35 WC:255 Avg:7

 

[98Converter]

I would open a ticket with AT&T and in the meantime, remove the caller-ID outbound from their phones if they need to call those numbers frequently...

change public-unknown-numbering 8
change isdn public-unknown-numbering 8

And you may have to change the station form:

Page 2
Per Station CPN - Send Calling Number? n

Thanks,
98C

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.