I have a station (8410 phone) that is acting oddly. You cannot call the number, it will give beep sounds when calling into. You can call out with no problems; both to outside numbers and inside 4 digit dial numbers. Seems like the phone is programmed for like a Do Not Disturb situation...but I have tried the #2 to deactivate call forwarding Busy. IS there some other programming option I should be aware of to look at? Send All Calls is not activated either. I also tried moving the station to another port on the Definity system to see if there was a clitch, to no improvement. Can call out on the station, but cannot call into??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Definity G3 system
- Thread starter mutantx
- Start date
ZeroZeroOne
Vendor
Did you try the command List Call-Forwarding to confirm there isn't any forwarding?
Can you list trace station xxxx for a call to the station and post the results?
Can you list trace station xxxx for a call to the station and post the results?
- Thread starter
- #3
the problematic number\station does not show up under the list call-forwarding command.
the list trace station does not work. This may be due to the way we are set up. I am on an Aura system, used my phone to trace off of, and nothing logs when I call out on my phone. I have used the list trace station command before on the Definity G3 that the problem station is attached to. The problem station on that Definity box is at another of our locations. I will have to trace station command a good station when I get over there again, to see what is logging when I attempt to call the problematic station. Any other ideas what it might be? I am thinking software setting or something for this individual station? This is a phone in my data center, I have other phones in there that are not having any problems. Also, if you call into the main data center number, and it is being used, the next incoming call will bounce to the problematic station and ring in....so I am told.
the list trace station does not work. This may be due to the way we are set up. I am on an Aura system, used my phone to trace off of, and nothing logs when I call out on my phone. I have used the list trace station command before on the Definity G3 that the problem station is attached to. The problem station on that Definity box is at another of our locations. I will have to trace station command a good station when I get over there again, to see what is logging when I attempt to call the problematic station. Any other ideas what it might be? I am thinking software setting or something for this individual station? This is a phone in my data center, I have other phones in there that are not having any problems. Also, if you call into the main data center number, and it is being used, the next incoming call will bounce to the problematic station and ring in....so I am told.
ZeroZeroOne
Vendor
Huh.
You said you removed and built the station again, right? That would seem to eliminate any odd station settings.
Just to confirm: 4-digit dialing from a station to this problematic station does not work? Caller hears a "beep" similar to the coverage path or forwarding. What happens if you remain on the line? Does the call go anywhere?
You can run list trace station xxxx where xxxx is the problematic station OR
You can run list trace station yyyy where yyyy is a known good station calling xxxx. Both should give you similar results.
Does the problematic station have a DID? You could try list trace TAC [trunk TAC] and watch what happens on the trunk group. You should see exactly what is happening as the call hits the DID or main number and the internal routing. This can be tricky if there is a lot of traffic since it will show you the first call to hit the trunk group and not necessarily the one you want.
Are there any weird incoming-call-handling settings? I've seen where a DID was routed to a VDN first even though a station existed.
For example:
Normal DIDs are converted to 4-digit stations by stripping off the first 6-digits. So 2125551111 would convert to extension 1111. That rule will work for anything 212 555 0000 to 9999.
The second line, however, takes a specific DID and routes it to a specific extension, such as a VDN. You could still create station 1234 but calls will never hit it. Outbound calls would work normally, and station-to-station calls would work, too. Is there a line calling out the problematic number?
Without a call trace to see exactly what is happening, I'm afraid we are left with just guessing at random things.
You said you removed and built the station again, right? That would seem to eliminate any odd station settings.
Just to confirm: 4-digit dialing from a station to this problematic station does not work? Caller hears a "beep" similar to the coverage path or forwarding. What happens if you remain on the line? Does the call go anywhere?
You can run list trace station xxxx where xxxx is the problematic station OR
You can run list trace station yyyy where yyyy is a known good station calling xxxx. Both should give you similar results.
Does the problematic station have a DID? You could try list trace TAC [trunk TAC] and watch what happens on the trunk group. You should see exactly what is happening as the call hits the DID or main number and the internal routing. This can be tricky if there is a lot of traffic since it will show you the first call to hit the trunk group and not necessarily the one you want.
Are there any weird incoming-call-handling settings? I've seen where a DID was routed to a VDN first even though a station existed.
For example:
Code:
display inc-call-handling-trmt trunk-group 1 Page 1 of 30
INCOMING CALL HANDLING TREATMENT
Service/ Number Number Del Insert Per Call Night
Feature Len Digits CPN/BN Serv
other 10 212555 6 none
other 10 2125551234 6 9999 noneNormal DIDs are converted to 4-digit stations by stripping off the first 6-digits. So 2125551111 would convert to extension 1111. That rule will work for anything 212 555 0000 to 9999.
The second line, however, takes a specific DID and routes it to a specific extension, such as a VDN. You could still create station 1234 but calls will never hit it. Outbound calls would work normally, and station-to-station calls would work, too. Is there a line calling out the problematic number?
Without a call trace to see exactly what is happening, I'm afraid we are left with just guessing at random things.
- Thread starter
- #6
Thank you for posting back ZeroZeroOne.
I did remove and recreate the station.
#1. you are correct, 4-digit dialing from a station does not work. You hear a beep similar to a busy signal, stays the same if you stay on.
#2. the list trace station feedback. X8190 being the problematic station. User called out from 8190 to my 4 digit 8360 station without problems and that is this trace.
LIST TRACE
time data
11:50:17 tone-receiver 01B0101 cid 0x18a
11:50:17 active station 8190 cid 0x18a
11:50:21 dial 8360 route:UDP|AAR
11:50:21 term trunk-group 31 cid 0x18a
11:50:21 dial 8360 route:UDP|AAR
11:50:21 route-pattern 111 preference 1 cid 0x18a
11:50:21 seize trunk-group 31 member 17 cid 0x18a
11:50:21 Setup digits 8360
11:50:21 Calling Number & Name NO-CPNumber COMPUTER ROOM
11:50:21 Proceed trunk-group 31 member 17 cid 0x18a
11:50:21 Alert trunk-group 31 member 17 cid 0x18a
11:50:21 G711MU ss
ff ps:20 rn:1/1 128.181.1.22:2888 128.1.200.22:2764
11:50:27 active trunk-group 31 member 17 cid 0x18a
11:50:27 G711MU ssff ps:20 rn:1/1 172.31.110.133:2058 128.1.200.22:2764
VOIP data from: 128.1.200.22:2764
#3. Yes, the problematic station 8190 did have a DID tied to it. I understand this means that it had a full 10 number outside tied to it....correct?
I did remove and recreate the station.
#1. you are correct, 4-digit dialing from a station does not work. You hear a beep similar to a busy signal, stays the same if you stay on.
#2. the list trace station feedback. X8190 being the problematic station. User called out from 8190 to my 4 digit 8360 station without problems and that is this trace.
LIST TRACE
time data
11:50:17 tone-receiver 01B0101 cid 0x18a
11:50:17 active station 8190 cid 0x18a
11:50:21 dial 8360 route:UDP|AAR
11:50:21 term trunk-group 31 cid 0x18a
11:50:21 dial 8360 route:UDP|AAR
11:50:21 route-pattern 111 preference 1 cid 0x18a
11:50:21 seize trunk-group 31 member 17 cid 0x18a
11:50:21 Setup digits 8360
11:50:21 Calling Number & Name NO-CPNumber COMPUTER ROOM
11:50:21 Proceed trunk-group 31 member 17 cid 0x18a
11:50:21 Alert trunk-group 31 member 17 cid 0x18a
11:50:21 G711MU ss
ff ps:20 rn:1/1 128.181.1.22:2888 128.1.200.22:276411:50:27 active trunk-group 31 member 17 cid 0x18a
11:50:27 G711MU ss
ff ps:20 rn:1/1 172.31.110.133:2058 128.1.200.22:2764VOIP data from: 128.1.200.22:2764
#3. Yes, the problematic station 8190 did have a DID tied to it. I understand this means that it had a full 10 number outside tied to it....correct?
ZeroZeroOne
Vendor
#1 Busy signal, but not the wave-off "turkey tone" that means the call did not go through?
#2 Please provide a list trace station 8190 when using another station to dial 8190. I'd like to see what incoming calls to the problem station look like.
#3 Correct. DID = Direct Inward Dial and means there should be a full number associated. If all your phone numbers are in the same range then they probably all have DIDs.
#4 Can you provide a status station 8190? You can use the CODE button (looks like a scroll with "<>" on it to format. That helps in reading the outputs.
#2 Please provide a list trace station 8190 when using another station to dial 8190. I'd like to see what incoming calls to the problem station look like.
#3 Correct. DID = Direct Inward Dial and means there should be a full number associated. If all your phone numbers are in the same range then they probably all have DIDs.
#4 Can you provide a status station 8190? You can use the CODE button (looks like a scroll with "<>" on it to format. That helps in reading the outputs.
- Thread starter
- #8
#1. yeah, I guess you can call the sound the turkey tone = meaning the call did not go thru.
#2. list trace on station 8190 gets nothing. Which is very strange.
I was confirming the DID situation, as the location where the station 8190 is located is under construction\demolition and ALOT of phone removal\line cleaning up has been happening. I have a report of other DID problems as well.
#2. list trace on station 8190 gets nothing. Which is very strange.
I was confirming the DID situation, as the location where the station 8190 is located is under construction\demolition and ALOT of phone removal\line cleaning up has been happening. I have a report of other DID problems as well.
ZeroZeroOne
Vendor
How about list trace station on another phone on same system when dialing 8190? Or list trace TAC [trunk tac] when you call from 8360? It looks like trunk group 31 a tie between your system and the G3, right?
Yet you can call OUT from 8190.... so it's physically connected and in-service.
Curious.
Yet you can call OUT from 8190.... so it's physically connected and in-service.
Curious.
- Thread starter
- #10
ZeroZeroOne
I was thinking it is a routing issue now on trunk group 31 as well. On top of everything else going on at location where 8190 is, I am working off and trying to troubleshoot from another location that upgraded to Avaya aura system. Sincerely appreciate all your feedback and input. You just confirmed one of my initial thoughts....it looks like a routing issue.
I was thinking it is a routing issue now on trunk group 31 as well. On top of everything else going on at location where 8190 is, I am working off and trying to troubleshoot from another location that upgraded to Avaya aura system. Sincerely appreciate all your feedback and input. You just confirmed one of my initial thoughts....it looks like a routing issue.
AvayaTier3
Technical User
Hardware Platform? Definity/CM software version?
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
Looks like 8360 is in a UDP/AAR table and your dialplan settings must be set to search UDP 1st. Calls to that extension route off prem via trunk group 31 according to your trace. Try "list uni" or "list udp" then get 8360 out of the table when you find it.
-CL
-CL
AvayaTier3
Technical User
Code:
change dialplan parameters Page 1 of 1
DIAL PLAN PARAMETERS
Local Node Number: 1
ETA Node Number:
ETA Routing Pattern:
UDP Extension Search Order: udp-table-first
6-Digit Extension Display Format: xx.xx.xx
7-Digit Extension Display Format: xxx-xxxx
--------------------------------------------------------------------------------
change dialplan analysis Page 1 of 12
DIAL PLAN ANALYSIS TABLE
Percent Full: 17
Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
0 4 ext
1 4 ext
2 4 ext
3 4 ext
4 4 ext
5 4 ext
6 4 ext
7 4 ext
8 4 ext
9 1 dac
* 3 dac
# 4 dac
#6 3 dac
--------------------------------------------------------------------------------
change uniform-dialplan 8 Page 1 of 2
UNIFORM DIAL PLAN TABLE
Percent Full: 0
Matching Insert Node
Pattern Len Del Digits Net Conv Num
83 4 0 122 aar n
8360 4 0 ext n
--------------------------------------------------------------------------------
change aar analysis 122 Page 1 of 2
AAR DIGIT ANALYSIS TABLE
Percent Full: 9
Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
122 7 7 111 aar 2 n
--------------------------------------------------------------------------------
change route-pattern 111
Pattern Number: 12 Pattern Name:
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 31 0 3 n user
--------------------------------------------------------------------------------
An entry like the above will let 8360 work as local extension when all the other
8300 - 8399 get shipped to aar analysisA great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Status
Similar threads
- Locked
- Question