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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Public-unknown-numbering (outbound CLID)

Status
Not open for further replies.

avayaaacc

MIS
Jul 4, 2014
74
US
I am trying to make sense public-unknown-numbering

Our environment uses three digit extensions, 001-099, 100-199 and 200-299

We have 5 trunks (4 PRIs and 1 SIP trunk), trunks 1, 2, 5, 6 and 9 (SIP)

In our public-unknown-numbering we have entries like:

Ext Len
Ext Code​
Truk Grp​
CPN Prefix​
Total CPN​
3
1​
5555555555​
10​
3
1​
1-2​
5555555555​
3
1​
5-6​
5555555555​
3
1​
9​
3​

And then this is repeated for the other range of extensions (100+, 200+). If the trunk group is left blank, isn't it fair to say that it would apply for all trunks, and we shouldn't have to specify the remaining trunks?

Also, why is the SIP trunk left with an EMPTY CLID, but a total CPN length of only 3? The SIP trunk is used by Avaya Contact Center, and the SIP trunk goes to Avaya Session Manager

And finally, what is the difference between "change public-unknown-numbering 0" vs 1, 2, 3, etc?
 
If Trunk Grp is blank it will apply to all trunks that haven't been specified in another entry.

By default it will send the extension number as CLI.
If you add a CPN Prefix that will be added first and it will then take the remaining digits from the extension up to Total CPN.

For example

If your extension is 101 and you set CPN Prefix to 9 and Total CPN digits to 3 it will send 901.

On "change public-unknown-numbering X" X refers to the Ext Len, usually I would use zero but if you have different extension lengths it can be useful.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top