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!

TCD/COS & DDI table in Unify OS4000

Status
Not open for further replies.

persi01

Technical User
Sep 14, 2017
32
IN
Hi guys,

I am somewhat new bee to Unify products. So need some help in programming unify 4000
Current scenario:
1. Install OS4000 ver8 with analog, few digital ports with Series as 4100 to 4399
2. PRI card is configured & incoming & outgoing is working properly. PRI Line Pilot no details 020- 6657 56XX. Here service provided is sending last four digit i.e 5600 to 5699.

Requirement:
1. Need to Mapping of PRI DDI to extn no as follow 66575601 should lands on 4101 & 6657 5602 --> 4102 & so on.
2. Currently Pilot no is going when calling via PRI i.e. 020- 6657 5600
3. Need to create TCD table so that I can to deny access for LOCAL calling[i.e only Internal calling], STD calling & ISD calling based of different COS. I think in unify for this LAUTH & LCOSV is used.

guys it will be helpful if someone can share commands for above configuration.


 
Why not just setup the extensions using the Direct Dial In Range of 5600 to 5699 ?
 
Tried to convey same to client, but client what extension to be 41XX to 4399.
Need to do DDI traslation to extension series only.
 
Well to do that specific thing:

ADD-WABE:5600&&5699,,,STN,N;
ADD-WABE:4100&&4399,,,STN,N;

Then
ADD-RUFUM:DID,5600,4100;
ADD-RUFUM:DID,5601,4101;
etc.
There will be exceptions like Operators etc. but it is all achievable

 
Also when dialling out if they need their correct Direct Dial In (DDI) number to show then number modification may be required.
I assume the customer has another site with different ranges as well ?
Maybe the carrier could provide a more correct DDI range ?
 
Thanks sbcsu.. will config this & confirm back.
One more thing
1 what to define restrictions based intercom , local, national & international.
2.i have define pin in persi & in wabe there is code define as below
*18 - ACOSX
#18 - ACOSX
I want confirm is this same feature code that can be used for keypad locking..As follow *184376.
4376 is pin for extension.
 
Here is an example of defining LCOSV for local, national & international.
CHANGE-COSSU:LCOSV,1,,2&&63,,,,;
CHANGE-COSSU:LCOSV,1,,,,,0,;
CHANGE-COSSU:LCOSV,1,,,,,,"LCOS1=INTERNAL AND EMERGENCY";

CHANGE-COSSU:LCOSV,2,1&&2&64,,,,,;
CHANGE-COSSU:LCOSV,2,,,,,0,;
CHANGE-COSSU:LCOSV,2,,,,,,"LCOS2=LOCAL CALL RATE";

CHANGE-COSSU:LCOSV,3,1&&3&64,,,,,;
CHANGE-COSSU:LCOSV,3,,,,,0,;
CHANGE-COSSU:LCOSV,3,,,,,,"LCOS3=NATIONAL CALL RATE";

CHANGE-COSSU:LCOSV,4,1&&4&64,,,,,;
CHANGE-COSSU:LCOSV,4,,,,,0,;
CHANGE-COSSU:LCOSV,4,,,,,,"LCOS4=INTERNATIONAL CALL RATE";

CHANGE-COSSU:LCOSV,31,1&&64,,,,,;
CHANGE-COSSU:LCOSV,31,,,,,0,;
CHANGE-COSSU:LCOSV,31,,,,,,"LCOS31=TRUNK ACCESS ONLY";


If you have LCOSV 4 - then you also have access to 3, 2 and 1
If you have LCOSV 3 - then you do not have access to 4 but can access the ones below.

LCOSV 31 is for trunks in this example - then all extensions would have access to the trunks.
 
When I used to do this I just set up the GDTR table and told it to delete the first 2 digits I got from the phone company and replace them - so 56 would br replaced by 41, 57 would be replaced by 42, 58 would be replace by 43 ... It's all in one neat little package - unless they changed something dramatically....

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
Yes, or you can in the TDCSU -
SUPRESS=2
and
DGTPR=41

That removes the first 2 digits of incoming and replaces it with 41 so you end up with example: 5603 being replaced by 4103
 
That would work for the first 100 numbers, but unless I read it wrong I think he is implying he has 300 numbers. This may have changed, but there used to be this whole substitution table where you could tell it the number of digits to substitute, say 2, and then there would be a table of 2-digit numbers 00 thru 99, and you would tell the system when it saw 56 to replace it with 41, and so on - you would only need to make the entries for the 2-digit patters you would actually receive. I'm at home now so I would have to try to look it up at work, but there was an AMO - I don't think it was DNIT, but it might have been, and one of the options was GDTR or general digit translation rules, and I think you could have one for a single digit, 2 digits, 3 digits, etc. Back in the day I had a rogue vice president that chose his own vendor for a standalone system when he knew we were in the process of networking our systems, and that vendor provided a block of 100 numbers - the 2400 block. Well, when we finally went to network that building we were screwed, because we already had a fully populated 2400 block that had been around for 15 years, so in my case I had the Telco send me 3 digits and used the GDTR to prepend a 4 at the beginning and made their internal extensions 4400 numbers. I have had other similar situations where I told the trunk to drop digits and used the table to change the first 2 digits based on what numbers were dropped... I overlaid my entire dial plan in a new exchange in 2006 so that's when I stopped doing it - so I don't know if they got rid of that functionality or not.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
Thanks sbcsu & donb01 .
By using rufum ddi is working.
Will config dgtr for digit manipulation & lcosv setting & confirm back.

Once again thank you guys.
 
If you use DGTPR/SUPPRESS in TDCSU then you would not have to use RUFUM.
All the digits then would present themselves as you requested
 
Thank sbcsu for amo related to lcosv
I have created lcosv mention above.
Lcosv = 1 for internal
Lcosv =2 for local
Lcosv =3 for national
Lcosv =4 for international
Our access code for external dialing is 0
Now if I assign lcosv as 1 & 4 working properly.
If assign lcosv 2 , even national & international are getting dial.
Same with locosv = 3, here even international are getting dial.

Any other things need to be config.

 
The LDPLN dialling out patterns with 'LAUTH' correspond to the LCOSV

So if you have an international number block allowed in LDPLN with LAUTH=4 then you have to use LCOSV4 on a phone to grant access to that international number
 
First sbcsu thank you very much for your help.
Finally figured it out TCD tables in OS4000. Configured TCD & RUFUM, its working.

One more thing I need to define station PIN & feature code to block long distance call, by dialling *CODE+STN PIN user can now only dial internal extension number.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top