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!

UDP issues Definity R9.5

Status
Not open for further replies.

wmainc

Vendor
Feb 18, 2008
206
US
Trying to add a new 9.5 into a network of existing older Definity's. I've done this many times over the years, but this one just isn't working.
5-digits extensions
extension range in new Definity (node 2) 832xx
extension range in existing Definity that it's directly connected to (node 1) 794xx

Unable to dial between locations. List trace station from a node 2 extension just shows the station going off hook and dialing one of the node 1 extensions and then a denial message. The call never touches the trunk group. Also, trying to set up rem-vm hunt group in node 2 I get the following error when trying to enter the remote audix extension:
"79499" Extension must be an off switch (UDP) extension
Here are some of the pertinent pages:

Uniform Dialing Plan Report

Extension Codes Type Node Number / Location Code
19875 UDPCode 101
19876 UDPCode 101
199xx UDPCode 101
7803x UDPCode 101
790xx UDPCode 101
7910x UDPCode 101
792xx UDPCode 101
793xx UDPCode 101
[highlight #FCE94F] 794xx UDPCode 101[/highlight]
832xx Local

AAR DIGIT ANALYSIS TABLE
Percent Full: 9

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
[highlight #FCE94F]101 8 8 130 aar 1 n[/highlight]
2 7 7 254 aar n
3 7 7 254 aar n
4 7 7 254 aar n
5 7 7 254 aar n
6 7 7 254 aar n
7 7 7 254 aar n
8 7 7 254 aar n
9 7 7 254 aar n

Pattern Number: 130

Grp. FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No. Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 30 0 3 n user
2: n user
3: n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n y as-needed bothept none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none
 
What is the Denial Event that you are getting? Check the dialplan paramaters in both switches.

Kevin
 
Waiting for the customer to give me a call back so I can run a trace. Will post that asap.

The dialplan is set up on both ends for 5 digit UDP. This is an existing network of 12 Definity systems that I am adding #13 (although the node number for the new one is 2).
 
Because you're getting the error that 79499 must be a UDP extension, it sound like the 794xx range isn't in the UDP table. I'd double check that entry first.
 
If you look in the first post I cut and pasted the UDP table from the new node. 794xx is in the table as UDP. That's why I'm so confused. It is there, it's just acting like it's not.
 
Here is the test calls I just had the customer make from the new site. She tried two different extensions (79036 & 79499).


LIST TRACE

time data

13:44:43 hold station 83232 cid 0x81
13:44:44 active station 83232 cid 0x83
13:44:46 dial 79036
13:44:46 denial station 83232 cid 0x83
13:44:51 idle station 83232 cid 0x83
13:44:51 unhold station 83232 cid 0x81
13:45:17 hold station 83232 cid 0x81
13:45:18 active station 83232 cid 0x84
13:45:21 dial 79499
13:45:21 denial station 83232 cid 0x84
13:45:22 idle station 83232 cid 0x84
13:45:22 unhold station 83232 cid 0x81
13:49:26 idle station 83232 cid 0x81

Unfortunately, there aren't any denial event numbers.
 
check UDP Extension Search Order: for local or udp-table-first

Code:
display dialplan
                               DIAL PLAN RECORD

                                                    Local Node Number: 17
                                                      ETA Node Number:
              Uniform Dialing Plan: 5-digit       ETA Routing Pattern:
        UDP Extension Search Order: local-extensions-first

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]
 
It doesn't copy and paste very well, but it's set for udp first.

DIAL PLAN RECORD

Local Node Number: 2
ETA Node Number:
Uniform Dialing Plan: 5-digit ETA Routing Pattern:
UDP Extension Search Order: udp-table-first
FIRST DIGIT TABLE
First Length
Digit - 1 - - 2 - - 3 - - 4 - - 5 - - 6 -
1: misc
2: misc
3: misc
4: misc
5: misc
6: misc
7: misc
8: misc
9: fac
0: attd
*: fac
#: fac
 
Command: display second-digit 7


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]
 
SECOND DIGIT TABLE FOR DIGIT 7


SECOND DIGIT TABLE

Digit Identification Number of Digit Identification Number of
Digits Digits

0: extension 5 5: extension 5
1: extension 5 6: extension 5
2: extension 5 7: extension 5
3: extension 5 8: extension 5
4: extension 5 9: extension 5
 
Code:
display second-digit 7                                                     SPE B
                        SECOND DIGIT TABLE FOR DIGIT 5
SECOND DIGIT TABLE
Digit  Identification   Number of       Digit  Identification   Number of
                        Digits                                  Digits
    0:                                      5: 
    1:                                      6: 
    2:                                      7: 
    3:                                      8: 
    4:                                      9: extension          5

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]
 
I know with all of the entries being a 5 digit extension it doesn't need to have the second digit table, but all the other nodes are programmed this way so I did it this way just to keep them all the same.
 
What happens when a station dial AAR feature-access-code then 10179499

should seize in-service-idle trunk in trunk-group 30 then send last 5 digits to distant pbx

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]
 
I had to add a FAC for AAR access (*810179499), but that worked. Dialing the 5 digit extension without the FAC + 101 does not.
 
Are you sure the other switch dialplan is defined as node 1?
Can you dial udp from node 1 to node 2?

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]
 
This is the dialplan from the existing system (node 1). I don't have anybody onsite there that I know of to make a test call, but I'll see if the customer can find someone to make a call or two for me.

DIAL PLAN RECORD

Local Node Number: 1
ETA Node Number:
Uniform Dialing Plan: 5-digit ETA Routing Pattern:
UDP Extension Search Order: local-extensions-first
FIRST DIGIT TABLE
First Length
Digit - 1 - - 2 - - 3 - - 4 - - 5 - - 6 -
1: misc
2: misc
3: misc
4: misc
5: misc
6: misc
7: misc
8: misc
9: fac
0: attd
*: fac
#: fac
 
Well, I just found something funny. There was an entry in AAR digit conversion that changed anything starting with a 1 into an ARS type call. I took that out, but it still doesn't let me add 79499 as the remote-vm number in the hunt group. The customer apparently stepped away from the phone for a few minutes so I haven't been able to get any test calls done yet.
 
Got it to work. I had to set the AAR analysis table to match on 7 digits min/max instead of 8 (although I have no idea how a 5-digit extension number plus the 3 digit UDP code equals 7 digits) and then insert the first digit of the extension number in the route pattern. As soon as I set it up that way it allowed me to enter the 79499 extension in the rem-vm field of the hunt group and calls completed over the tie PRI. I'm confused as to WHY it works this way, but as long as it DOES work, I'm happy.
 
You may be able to use udp code 107 then last 4 digits of 5 digit extension, delete 2 on the route pattern (1 and 0)
total of 7 and send 5

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]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top