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!

Avaya CM Public Unk Numbering

Status
Not open for further replies.

RedMaligator

Systems Engineer
Jun 16, 2023
8
US
When programming and leaving the Trunk Group empty causes system to out pulse the caller ID of the DID. In the manual it says this:
Trk Grp(s)
Number of the ISDN trunk group carrying the call, or the range of trunk groups that use the same CPN Prefix.

blank — IEs are not dependent on which trunk group carries the call.

I need clarification as to this in manual, am I understanding that if left blank the IE (Internal Extension?) will out pulse the programmed #?

Ex: change public-unknown-numbering 7 ext-digits 5555555
Ext Len 7
Ext Code 5555555
Trk Grp Blank
CPN Prefix 1234567
Total CPN 7

Calling out of 5555555 thru any trunk group will be Calling Number & Name 1234567 No-CPName

The reason why I ask is because I have such a large list of trunk groups, I want to simplify the programming. Trunk Group 55 original group & Trunk Group 200 was added for expansion. Just in case its asked. If specifying trunk group, it out pulses the programmed number as requested.
Thanks!
 
My guess is that you have competing entries in your public-unknown table.

Look for entries for "5" or "55" or any other combination that would act as potential rules for this call. The public-unknown table finds the best match based on the dial-string AND the trunk group.

Code:
Ext Len   Ext Code     Trk Grp(s)     CPN Prefix     CPN Len
7         5                           1234567890     10
7         55                          2125551212     10
7         55           55             2125557777     10
7         5555555      55             0123456789     10

Rule 1: Any 7-digit station starting with "5" out any trunk displays "1234567890"
Rule 2: Any 7-digit station starting with "55" out any trunk displays "2125551212"
Rule 3: Any 7-digit station starting with "55" out trunk 55 displays "2125557777"
Rule 4: The 7-digit station matching "5555555" out trunk 55 displays "01234567890"

[ul]
[li]Since Rule 2 is more specific on the dial string, Rule 2 will affect all stations starting with "5". Rule 1 will never work.[/li]
[li]Since Rule 3 is more specific on the Trunk Group, Rule 3 will affect all stations starting with "55" when going out trunk 55. Rules 1 and 2 won't work on this specific trunk (for stations starting with "55").[/li]
[li]Since Rule 4 is more specific on the dial sting AND the trunk group, this rule will take effect.[/li]
[/ul]
 
Thank you! Yes, that makes total sense, also following behind others and cleaning up the programming sucks!
Problem is specifically I am having is:
Without a Trunk Group being specified, it will not out pulse number specified. There are no conflicts that report back in ASA duplicate entry. I am trying to setup station and/or range/ranges to out pulse main number. Nothing works without Trunk Group.

JpG_nqnfqy.jpg
 
I can only suggest you keep searching for fewer and fewer digits...
1234567
123456
12345
1234
123
12
1

Until you find all the rules that could possibly exist.

Try running "list public" to view all. If you run that in GEDI you can then export to Excel to help searching.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top