Alcatel Mentoring Class of Service, Trunk Groups & DISA

1. Alcatel MentoringClass of Service, Trunk Groups & DISA

2. Class of Service

3. CategoriesOverview • Connection categories (CoS) • Transfer categories (CoS) • Private calls connection categories (CoS) • Phone facilities categories (CoS) • Access categories (CoS) • Public access • Private access • Business access • Trunk group access

4. Categories Connection categories • Connection categories (CoS) • Determine the authorizations or prohibitions of calls between terminations (sets and trunks). • Each termination (set and trunk) is allocated to a category from 0 to 255. • The communication rights concern the following facilities: • direct local call between sets, call pick-up, hunt group calls • outgoing calls • incoming calls • connection between an incoming trunk and an outgoing trunk.

5. CALL cat=1 called caller Categories Connection categories • Connection categories (CoS) cat=2

6. Categories Transfer category • Transfer categories • Determine the rights of a termination to be transferred to another termination. • Each termination (set and trunk) is allocated to a transfer category from 0 to 255. • The transfer category number is the same as the connection category number.

7. TRANSFER cat=1 called caller Categories Transfer category • Transfer categories (CoS) cat=3

8. Categories Private calls connection category • Private calls connection categories • Determine the authorizations or prohibitions of private calls between virtual, PIN sets and physical sets from which the call can be made • This table permits private calls: • only from one`s own set • from all the sets • from some of the sets • This is carried out by compatibility monitoring between the PIN owner (private virtual set) and the physical set used at the time of the call • The private calls connection category number is the same as the connection category number

9. Cat=1 (PIN user) Public network Private call Cat=3 (Physical set) Categories Private calls connection category • Private calls connection categories Physical set PIN user

10. Categories Phone facilities categories • Phone facilities categories (CoS) allow: • To authorize or not a user to use specific telephone facilities (*) • To protect users against certain phone facilities (**) • To define the type of routing at off-hook (hotline) • Each user (UA, PWT, analog…) is allocated to a phone facilities category from 0 to 31.

11. Categories Phone facilities categories • Features are classified as follow: • Rights • Routing mode at off hook • Set facilities • General facilities • Local facilities • Outgoing facilities • Suffixes facilities • Abbreviated Numbers by ranges • Voice mail forwarding

12. Categories Access Categories (CoS) • Each user (UA, PWT,IP, analog…) is allocated to an access category from 0 to 31. • It is used to define the users characteristics for incoming and outgoing calls by defining: • specific services • their public access rights • their private access rights • their business access rights • their trunk group access rights

13. Trunk Groups

14. Trunk GroupsOverview • Connection to one operator: public trunk groups Digital ISDN T1 PSTN Alcatel OmniPCX Enterprise NDDI Analog

15. Trunk GroupsOverview • Connection to another Alcatel OmniPCX Enterprise Digital ABC_F2 link or trunk group Alcatel OmniPCX Enterprise Alcatel OmniPCX Enterprise ATL Analog

16. Trunk GroupsOverview • Connection to a non-Alcatel PABX Digital QSIG BC/GF Alcatel OmniPCX Enterprise ATL Analog

17. Trunk GroupsOverview • Main characteristics Number Seizure prefix Signaling Type Accesses or trunks

18. Trunk GroupsOverview • Trunk categories • Contains data concerning the communication protocol used (can be modified and depends on the country). What’s your Name? Como te llamas? Alcatel OmniPCX Enterprise

19. DISA

20. Alcatel OmniPCX Enterprise OPERATOR DISASecurity • Secured access DISA 9782603535 Access code for DISA service 9782603535+ DISA access code + ... 4590

21. DISALocking • DISA temporary locking • Automatic DISA temporary locking • DISA failure if : • 3 errors in case of DISA secret code dialing. • 3 errors in case of user secret code dialing after substitution. • DISA function is locked after 5 wrong following failures in a same DISA incoming call.

22. DISALocking • Manual unlock • Using the management tool. • Using a prefix from an authorized local station.

23. Alcatel OmniPCX Enterprise DISAFeatures • Virtual DID DISA 9782603535 19782603535+ 4595 PSTN 4595

24. Alcatel OmniPCX Enterprise DISAFeatures • Management parameters of your set DISA 9782603535 19782603535+ substitution prefix+4590 + personal code + forwarding+ voice mail number Voice mail PSTN 4590

25. Alcatel OmniPCX Enterprise DISAFeatures • Long distance call billed to the company DISA 9782603535 19782603535+ substitution prefix+4590 + personal code+ trunk circuit seizure prefix + 18188787007 PSTN 8188787007 4590

26. Alcatel OmniPCX Enterprise DISAFeatures • Call by abbreviated dialing DISA 9782603535 19782603535+ Abbreviated number Abbreviated number 1000 918188787000 PSTN 8188787000 CHARGING : call is billed to the number 4590 DISA number : 4590

27. Alcatel OmniPCX Enterprise DISAFeatures • Automatic Substitution on DISA DISA 9782603535 9782603535 Abbreviated number : 1000 Contents : 9782604533 N° ext. Disa : 4590 NDI: 9782604533 PSTN 4590

28. Inbound DISA Access code YES Guide: « Please dial your personal code » NO Dialing the Code Automatic substitution YES Presence of a DISA directory number OR OR NO Dialing substitution Code +directory N° + personal code Guide: « Please dial yourservice access key number » Calling from a local set YES OR Outbound call Set feature Call using speed dialing DISAPrinciple • Functions chart

29. A DISA Application

30. meet me conference prefix + conference code meet me conference prefix + same conference code 2 4 3 1 ACT-MG GPA meet me conference prefix + same conference code Without DISA, an external subscriber has to be transferred into a conference Meet me conference Reminder • Meet me conference reminder Conference participant Conference participant subscriber or attendant External subscriber Conference participant

31. Meet me conference Using DISA • Meet me conference using DISA (external user) Public Network DISA DISA ABC F2 GPA ACT-MG Node 1 Node 2 The external users have to use the substitution feature. DISA trunks and the GPA board could be located on different nodes

32. Trunk GroupsSome Review & Examples

33. So Why a Trunk Group? • A Trunk Group is used to logically group one or more physical trunks, with the ability to do common barring, NPD (Numbering Plan Descriminators), etc. with the group • Reminders • T1s can be provisioned as CAS or CCS, but not currently line-side • Trunk Groups support Hybrid Links • ABC-F2 and Q.SIG links provide additional features; remember ABC has more features than Q.SIG but these only work between OmniPCX nodes • Outgoing trunks could be directly seized by prefix using Professional Trunk Seize or through ARS, the former being simpler to provision, the latter providing additional routing features • Default Entity is 1 for trunks and 0 for users • Default Class of Service for Trunks is 5 • DDI Translator / Multitranslator allows for dialed number / presented number translation and substitution • Don’t forget about the CDT’s role in call handling • Up to 128 Trunk Groups • Trunk Group Supervision supported on a Reflex key to monitor TG status

34. A few words on Barring • Barring is typically done by lookup of the logical discriminator which can indicate if barring is in use • Can be within a single trunk group with 1 entity • Or, with multiple trunk groups in 1 entity • Or, with multiple trunk groups and entities • Or, more complicated if you wish • Uses real discriminators, 8 maximum per entity • Barring is done on full or partial numbers

35. A few words on ARS • Automatic Route Selection • Allows the system to select alternate routes to reach a destination • Routing can be time dependant • Up to 10 routes per destination • Uses the ARS Professional Trunk Group Seize prefix • ARS Limits • 4000 ARS route lists • 10 alternative routes in ARS route list • 8 Time Based Routes in ARS route list • Up to 10 routes in an ARS Time Based route list • Up to 100 ARS schedules • Up to 5 Time tables per ARS schedule • Up to 24 Time Slices per Day • For multi-carrier or multi-node, I always use ARS

36. A few words on CCD, IAA, Hospitality, etc. • Many things can become very important, very quickly, including: • Entity of trunk, pilot, agent • % Trunk Group used by a pilot (CCD) • DDI translation • Public Network COS • Transfer COS • Attendant groups and attendants • Generally outside the scope of this session

37. Some thoughts on use • A site wants to connect branch offices to main site. They are relatively small and have key systems which are 1-2 years old. They do have some unused capacity on the point-point link from the branch to the HQ. • Think about putting either an eMG or an IP ACT in the branch with one or more trunks, connected to the key system. Program the key system with a seize code or key for “on network” dialing to the main site. This will seize the trunk – you can choose to send the dialled digits or route the call as desired based upon site requirements. Redundancy at the branch is probably not significant since they have local trunks now. • I have provisioned my system and at turn-up, the incoming calls are being lost. The telco says the trunk is good, but I’m not sure. • OK, you can program a trunk to route to a directory number. Pick a specific extension and retry the call. If the extension rings, then something in the translator, entity, barring, CDT, etc. is wrong.

38. Some thoughts on use - IP • The customer has 2 IP connections between 2 sites. They want to overflow from one to another with IP trunks. Can we do it? • In short, not today. We cannot currently overflow from one IP trunk to another. The best thing is to provide IP networking gear which can make it appear as 1 logical connection to the OmniPCX. Use a routing protocol with metrics so that the alternate route can be used before either total congestion or when error rates become high. This is usually set in a metric in the routing algorithm. • The customer wants to add OmniPCX gear in a branch office connected by IP. They want to use IP phones and IP trunks to service the handsets and faxes in the branch. • This use is OK, however, realize that 5.0 LX will allow the IP handsets to be associated with the local eMG in the branch by use of IP domains, while 5.0 UX requires that IP phones use the INT-IP in the MAIN ACT. This can be problematic, as calling from an IP phone to a non-IP phone or resource in the branch with 5.0 UX will cause tromboning, requiring the voice path of the call to loop through the INT-IP in the Main ACT. If there are truly only fax machines in the branch, the likelihood of an IP handset calling one is small.