avaya definity g3csi pbx at home
once i got my nortel option 11e system up and running pretty much exactly as i wanted, i found myself looking for another telephony project. i had always thought it would be cool to have representative examples of products from both major north american pbx manufacturers and when i happened to come across a discussion thread on the internet where some other folks were mentioning how cheap and easy it is to get a small avaya definity going from parts, i knew i had to give it a try. as was the case when i started working with my meridian, i took lots of notes along the way as i worked with the system and i figure that i might as well put them up on the web to complement my meridian page and help out any similarly minded telephony hobbyists.

the model range

the avaya definity range has been around for roughly the same amount of time as the nortel meridian range, and it is equally as broad. definity systems range from huge installations with thousands of lines, to smaller switches with tens of lines. since this is for residential use alongside my small meridian, i of course need the smallest and most power efficient model possible. for the purpose of these experiments, then, i chose the definity prologix "G3csi" which is really quite analogous to the meridian option 11 line. both systems have ten slots for cards, and pull a couple of amps worth of 120 VAC so they are very manageable in the home.
there are a few different variants of the definity prologix. the earliest of the processors is model TN798. it supports between V4 and V6 of the definity system software. i suppose it could be considered to be a contemporary of the NTAK01 option 11 system controller, though the TN798 has a much more powerful CPU. the next version of the prologix processor was the TN798B. it was an upgraded version of the TN798 that supported V6-V8 of the definity software. this one was perhaps a contemporary of the NTBK45 option 11e system controller, although again the TN798 would have had more raw CPU power. the final prologix processor was the TN2402 board which runs V9 and above of the definity software. this would have competed with the NTDK20 option 11c product. here, raw CPU power was more evenly matched, between the MC68040 of the NTDK20 and the embedded IDT R3000 architecture core of the TN2402.
a brief aside: the definity systems in general are basically modernized and renamed descendents of the old at&t system 75 pbx from the early 1980s and they share its very interesting system architecture and realtime operating system. if you are curious about the details, there was an entire issue of the bell labs technical journal devoted entirely to papers discussing the hardware and software design of the system 75 (january 1985, volume 64, issue 1, part 2). if you live near a large university you should be able to find it in the engineering library.
anyway, back to the more practical stuff. you can find surplus boards for the definity pretty cheap. in fact, i would say that on average secondhand definity boards are a little cheaper than secondhand nortel boards, perhaps because it is slightly a smaller market and avaya more aggressively discourages the gray market. i dont think i ever paid more than fifty dollars for any single board, and you can find a lot of boards between ten and twenty dollars each. if you get lucky and pick up a nice processor that you can gain access to, you can put together a really nice pbx for way less than you would pay for buying a complete system. that being said, i have seen complete definity prologix units being sold for less than five hundred dollars so if you keep an eye out you can even score something prerolled for relatively little cash. of course me, i always find it to be the most fun when building it up board by board. in that vein i will discuss below a little bit of what makes up the definity system.
basically, a definity prologix system consists of the following components

  • at least one "compact modular cabinet" chassis which includes
    • one backplane - built in to the chassis
    • one connector bulkhead panel - built in to the chassis
    • one power supply - usually included - but always check
    • two bus terminators - inexpensive, sometimes omitted with bare chassis so check that too
  • a processor card - the main processor of the switch
  • a tone/clock card - tone board, clock controller, and call classifier
  • any number of peripheral cards - including
    • analog, 2-wire digital, 4-wire digital, and isdn bri station cards
    • analog (e.g. fxo/fxs/e&m) and digital (e.g. t1, isdn bri) trunk cards
    • ethernet cards for voip or ip based administration
    • recorded announcement cards
    • audix voice mail

the table below sums up the most common and useful parts for the definity prologix, maybe biased a little bit for V9 because that is what i am running and most familiar with.

TN798 V4-V6 processor card
TN798B V6-V8 processor card
TN2402 V9+ processor card
TN2182C tone/clock/call classifier for use with TN2402 (will also work with TN798)
TN2182B tone/clock for use with TN798/TN798B
TN799 C-LAN ethernet card. 799 for R7, 799B for R8, 799C for R9+, 799DP supports 10/100
TN767 T1 interface, supports PRI but only in small systems (G3csi)
TN464 T1/E1 user-selectable interface, supports PRI in all definity systems.
TN754 4-wire digital (DCP) line card, 8 port. B revision supports something called group paging.
TN2181 2-wire digital (DCP) line card, 16 port.
TN556 isdn bri line card, 12 port
TN793 analog line card, 24 port
TN746 analog line card, 16 port.
TN760 tie (e&m) trunk card, 4 port
TN753 analog did trunk card, 8 port
TN747 analog co trunk card, 8 port.
TN429 analog direct inward/outward dial trunk, 8 port.
TN763 analog auxiliary trunk (e.g. paging, RAN), 4-port
TN742 analog line card, 8 port
TN750 integrated recorded announcement board
650A 120 vac power supply
AHF110 tdm bus terminator
108724907 8 megabyte PCMCIA translation memory card for V9+
the same secondhand gear warning i gave for the meridian applies here as well. you can only put certain processors and tone clocks into the compact modular (csi) chassis, but pretty much all of the line cards and ancillary equipment are interchangeable between the larger definity systems and the definity prologix. so when working with the small cabinet, stick to the processors and tone clocks mentioned above if you want it to work. ignore all the network control, packet control, maintenance processor stuff; that is all for the larger systems.
also a few notes regarding getting the best deals: keep an eye out for the lower port density line cards; since we are using this for a small scale residential installation we dont really care about port density and the lower density line cards are a lot cheaper. also you will find that the TN464 T1/E1 interface is much more expensive than the TN767 T1 interface but that is only because people with larger systems must buy the TN464 to do isdn pri. since we have a small system and the TN767 will do isdn pri on a small system, we might as well use them, and they are vastly cheaper than the TN464 cards. the switch is pretty good about supporting even the most ancient vintages of most line cards so dont feel nervous buying up the older circuit packs; it will most likely work even if they predate the processor by a decade or two.
so if someone wanted to put together the smallest possible definity system, basically they would need a complete chassis with power supply, two bus terminators, a processor, a tone clock card, a line card, and a trunk card. thats it. a c-lan card is not required but is a common addition. the definity differs from the meridian in that even in the more modern system controllers, there is an external tone board however it also integrates the clock which on the meridian is an expansion to the t1 board. console serial port is still integrated into the processor card, but on the definity there is no way to add more serial ports to the system for e.g. extra consoles, dialins, or CDR logging outside of the three ports built into the processor board. on the other hand, the you can put a C-LAN ethernet board in any model of prologix system, while only the meridian option 11c supports ethernet. finally, also note that you MUST have a PCMCIA translations card for the processor to save its configuration on, unlike on the meridian where the configuration is stored on the software cartridge and on the system controller card itself.
i also want to note here that i have seen various postings on internet forums that imply that the processor board and its configuration are coupled with some sort of unique id or serial number. that is to say, you might not be able to take a memory card with configuration from one processor card and put it into another processor and use it, even if the processors are of the same model. so if you want to use a particular processor card, you have to be able to get in to the configuration stored on the card that came with it. once you are in, you can make copies of the configuration on to other memory cards, but you can only use that configuration with the one processor. i havent tested this in my lab yet but i am inclined to take the conservative route and believe that it is true so if you are buying processor cards, be sure that there is a translations card included with it. this is mostly an issue of spares planning; if you want to keep a spare processor module around in case the running one fails, you might like to just swap the processor cards, plug in your translations card, and go.
and one last note regarding translation cards: the translation memory cards used with the TN798 and TN798B processors are not cross compatible with the memory cards used with the TN2402 processor. the TN798 series processors take either a 2MB card or a 4MB card, and the TN2402 processor takes either an 8MB card or a 16MB card. the cards used with the TN2402 processor are standard 5V PCMCIA ATA memory cards, but those used with the TN798 series are not.
so anyway, looking at the system controller, you should see a switch and a bunch of lights. the switch controls the emergency transfer behaviour of the pbx and you can leave it set at the default setting which is the middle position, "auto". unlike as is the case with the nortel, the communication parameters of the console are fixed, 9600 8/N/1 with no flow control.
avaya does not break out any of the serial ports on the bulkhead for you like nortel does on the meridian. while a factory breakout cable is available that will take the RJ21 and split it out into all of the requisite ports, it seems to be hard to find. fortunately, avaya makes the RJ21 pinout of the processor card available in the definity cmc install and test guide. you can use the pinouts described there to terminate the RJ21 to a 66-block and split off the console ports as necessary. you will be interested in the TERM (J3) port which is the system console. the processor card has three serial ports onboard; one for the console, one that is intended to be hooked up to the "INADS" maintenance dial up modem, and one for use as an auxiliary port. i have only actually terminated the console port to a serial cable myself and that was pretty easy but i cant really say anything as to any possible issues regarding getting to the other two serial ports.
now that i mention the INADS dial in port i do want to take an aside and suggest to you that it is generally a bad idea to connect the INADS serial port to a modem hooked up to a telephone line, particularly prior to clearing out any existing configuration on the switch. i will leave it as an exercise for the reader to consider why this might be.
also, it should be fairly obvious, but i do just want to state explicitly that each circuit pack is wired straight back to the RJ21 connector behind it.

cabling the definity

like the meridian, the avaya definity uses the industry standard RJ21 pinout scheme for cabling its cards. in fact, many definity cards pin out similarly to their nortel counterparts. if you havent terminated RJ21 to a 66 block before, it can be a bit confusing, so i wanted to touch briefly on it here if you havent seen it before on my nortel page. basically, for each card, you connect the cable via 50 pin centronics to the port behind it on the definity. on the other end of the cable it is just wires, which you will punch down on a 66 block according to the RJ21 standard. i copied the pinout table below from my meridian page to help you out.
wire colordefinity pin66 block pin
white+blue stripe261
white+orange stripe273
white+green stripe285
white+brown stripe297
white+gray stripe309
red+blue stripe3111
red+orange stripe3213
red+green stripe3315
red+brown stripe3417
red+gray stripe3519
black+blue stripe3621
black+orange stripe3723
black+green stripe3825
black+brown stripe3927
black+gray stripe4029
yellow+blue stripe4131
yellow+orange stripe4233
yellow+green stripe4335
yellow+brown stripe4437
yellow+gray stripe4539
violet+blue stripe4641
violet+orange stripe4743
violet+green stripe4845
violet+brown stripe4947
violet+gray stripe5049
blue+white stripe12
orange+white stripe24
green+white stripe36
brown+white stripe48
gray+white stripe510
blue+red stripe612
orange+red stripe714
green+red stripe816
brown+red stripe918
gray+red stripe1020
blue+black stripe1122
orange+black stripe1224
green+black stripe1326
brown+black stripe1428
gray+black stripe1530
blue+yellow stripe1632
orange+yellow stripe1734
green+yellow stripe1836
brown+yellow stripe1938
gray+yellow stripe2040
blue+violet stripe2142
orange+violet stripe2244
green+violet stripe2346
brown+violet stripe2448
gray+violet stripe2550
looking at the 66 block, number the block starting at the top with the uppermost row as 1, going down, with the bottom most row being 50. punch down the requisite color of wire at the requisite 66 block position. avaya is a little bit more explicit about pin numbers in its documentation than nortel so it shouldnt be quite so confusing but the scheme is really very similar and most avaya cards have similar pinouts to their nortel counterparts (e.g. analog and 2-wire digital line cards and T1 cards). but as always you should be careful when reading manuals that mention pin numbers to be sure that they either refer to the RJ21 on the definity side, or pins on the 66 block side. if you find that it doesnt work when you count pin numbers from the 66 block side, try doing it counting pin numbers from the RJ21 side.
exactly like on the meridian, the method to the madness here for the simplest case of an analog or 2-wire digital line card, you have the case where definity pins 1+26 are tip and ring of line 1, 2+27 are tip and ring of line 2, 3+28 are tip and ring of line 3, and so forth. the cabling scheme on the 66 block means that avaya pins 1 and 26 become 66 block pins 1 and 2, avaya pins 2 and 27 become 66 block pins 3 and 4, and so on. notice how they all translate out to adjacent slots on the 66 block.

powering up the system

once everything is cabled up, just plug in the switch. there is no power button per se, the intention is that to power it off, you either pull the plug, or remove the power supply from the chassis. if all goes well, you should see some diagnostic output as follows. on a real terminal it clears the screen of boot diagnostics before showing the login prompt but i cant really represent that on the web without using a screenshot or something.
VIRTUAL MEMORY TEST             PASSED
EXCEPTION TEST                  PASSED
TIMER TEST                      PASSED
MTP TEST                        PASSED
SANITY TIMER TEST               PASSED
ADDRESS MATCHER TEST            PASSED
FLASH TEXT CHECKSUM TEST        PASSED
DECOMPRESSING IDATA             in_cnt = 641978, out_cnt = 2420736
RAM DATA CHECKSUM TEST          PASSED
MILLISEC TIMER TEST             PASSED
IOP SHARED RAM TEST             PASSED
RESET 4 (REBOOT)PERFORMED

Login:
so long as the system is passing all of the power on self tests, there isnt really so much useful information in the boot messages as there is on the meridian. basically just let the switch do its thing and eventually when it is done booting up you will land at a login prompt.
i want to note here that if you powered up your switch and note that it is basically just stuck in a reboot loop, or ending up in SPE_DOWN mode with lights on all cards red, check that you have two AHF110 tdm bus terminators installed at the rear of the switch, by the RJ21 connectors. there should be two ports there labeled TDM/LAN. hook them up there. if we had more than one switch cabinet, this is where you connect the cables between the two cabinets.
the presence of the login prompt lets us know that the switch is ready for use. if we see anything else here besides the login prompt, it is most likely a fatal error. it shouldnt take more than a few minutes to reach the login prompt after powering up the switch.

documentation

before logging in, i will briefly discuss the issue of documentation. really, the definity system is quite easy to use and there is extensive on-line help built in such that you hardly need documentation. however, if something goes wrong and you need to cross reference some error codes, or you want more in-depth information as to how the system operates, there are a few manuals available that condense all of the necessary information. you should be able to pull these down from avaya really easily with no registration required or anything like that.
definity ECS R6 installation and test for compact modular cabinets (555-230-128)
definity ECS R9 administrators guide volumes 1, 2, and 3 (555-233-506)
maintenance for avaya definity server CSI volumes 1 and 2 (555-233-119)
depending on which processor you have the installation and test guide is a little out of date but it contains the proper pinouts for the processor card, which is all we are really interested in with that manual. the pinout of the processor card is the same regardless of TN2402 or TN798. the administrators guide discusses pretty much all of the non-maintenance-related commands used in day to day operations of the switch. the maintenance guide discusses test and diagnostic procedures and contains cross-references for all of the error codes returned by various test routines. it is not so critical for using the switch that you have all of this documentation as is the case with the nortel; i was able to mostly figure the definity out just from the help system and a few cisco-definity configuration examples but they are nice references especially with regard to learning e.g. the automatic route selection system and the maintenance guide is pretty critical to have if you need to cross-reference some error codes with a verbose description of the cause.

logging in

as always i like to suggest that you peek at the documentation a little bit before logging in to the switch just to get a feel for things but as i say above the avaya is really so easy you wont get lost just jumping in. in any case, you will find yourself at the console trying to log in, and of course you need a username and password.
Login: cust
Password:
in contrast to the default state of the meridian, the definity uses both a user name and password for switch authentication. usernames generally follow the bell labs tradition of being in lower case. the password is software enforced to be between 4 and 11 alphanumeric characters, and the user is forced to include at least one numeric character in the password.
i have found that basically there are three, or perhaps four sorts of accounts on the definity. in order of privilege these are: avaya proprietary accounts, accounts for the switch vendor, fully privileged customer accounts, and limited access customer accounts. it is interesting to note that in the definity world, avaya itself seems to take a wider role in controlling the switch in contrast to the meridian where, while nortel retains access to e.g. PDT, the customer really has control of all accounts on the switch. of course, thats not to say that i am going to let it spoil my independent maintenance operations!
the avaya proprietary accounts tend to have full privileges on the switch. one account in particular, init, is especially privileged in that it and it alone has the capability to enable and disable optional features on the switch. that is to say, when the switch is first installed, avaya uses the init account to enable all of the features that the customer has paid for. vendor accounts, if any, have more or less full privilege on the switch but cannot enable or disable optional features. fully privileged customer accounts should have basically the same abilities as a vendor account. finally, limited privilege customer accounts tend to allow read-only access to the switch. really the conclusion to draw here is that so long as you have a fully privileged customer account, you dont need an avaya proprietary or even a vendor account to take control of the switch; the fully privileged customer account should be able to do everything you need. the table below describes default accounts and some alleged default passwords for the definity.
account namecommon passwordsnotes
init(variable)avaya account, one time password in R8+, highest access
inadsindspwavaya account, one time password in R9+
craftcraftpw, crftpwavaya account
maintmaintpwpossible avaya account
dadmindadmin, dadmin0, dadmin1vendor account
custcustpw, custpw0, custpw1customer account
note that in more recent revisions of the switch, the init (R8+) and inads (R9+) accounts are protected by a one time password challenge-response type of mechanism. this makes them basically impossible for us to access. the craft account is commonly mentioned on the internet in general as the main day-to-day administrator account on the switch but it seems that in later releases it drifted to being more an avaya proprietary account not for outside use and the password is certainly not craftpw on my V9 switch. it is interesting to note that the craft account is the only avaya proprietary account that is not protected by challenge-response but i have been unable to obtain the password, even after dumping the contents of the translations card and looking through it with a hex editor.
in general, this all means that you should focus your attempts on the dadmin and cust accounts. these are not defaults on the switch per se, but they have become basically de facto defaults following from how common they seem to be among avaya sites. if the cust account turns out to be fully privileged as it was on my V9 definity then you should be all set.
i suggest some common defaults above and even if those dont necessarily work, you should see some kind of pattern here and follow it accordingly. a common guideline people seem to use when setting passwords on the definity is to take the account name, suffix "pw" at the end, and tack on a number. dont be afraid to put in a little brute force work. as far as i can tell from my V9 system there is no failed login lockout threshold on the definity as there is on the meridian. the avaya will also dismiss login attempts with user names that considers absurd (e.g. too short or too long) out of hand with INCORRECT LOGIN without even prompting for a password which helps to narrow the domain somewhat, though dont let this fool you into thinking that it dismisses all attempts against usernames that dont exist at all with INCORRECT LOGIN right off the bat. it will still prompt you for a password on an account that doesnt actually exist so long as the length of the user name is within bounds.
NOTE you may come across a posting on the internet that suggests that it is easy to default a definity system by starting it up with no translations card installed. this is only half true. it is true that you can default a definity using this method, but the system with which you are left is not particularly useful. basically when you boot a definity in this way, the system loses ALL of its customer options including the privilege of running the modern software loaded on it. that is to say, it comes up running basically V1 of the definity operating system, circa about two decades ago. in this state, the system will not support much of anything useful and has basically been turned into a boat anchor. certainly this is the case for the more modern TN2402 processor. now, where i think this becomes more useful is if you have an old TN798 type processor, running something like V6. on these older processors the init account is not protected by any sort of challenge/response mechanism. i have heard that instead, there will be a numeric code on a sticker affixed to the processor module which is used as a cross reference to a great big list of default init passwords that avaya techs have for all the various definity software releases. let me tell you that i have heard some of the passwords and they are pretty strong, not something that is easily brute forced. it is never really the case that the password for the init account would be initpw as you may read on the internet. so if you know someone sympathetic with a knowledge of definity internals, you should in theory be able to boot the switch with no translations card, log in as init, switch on all of the features that you want, then insert a translations card and save. theoretically this should give you a defaulted switch.
so basically, unless you know someone over at avaya who has access to the utility that generates responses to the one time password mechanism, or you get an older TN798 series processor and use the defaulting method mentioned above, your only options are to basically buy a system controller where the seller already knows the password, guess the password, or buy processor cards on a trial and error basis until you find one with a defaulted account. as with the meridian, it is not necessarily that dreadful to have to purchase a few processors on a trial and error basis because they are usually quite inexpensive. and when purchasing processors, always remember to make sure that the processor includes its translations card!
at this point, i will assume that you have come across a valid user name and password for the switch, by whatever means. enter it at the login prompt. the first things you should see subsequent to a successful login will be a banner informing you of the software version, and a terminal type prompt.
Login: cust
Password:

System: G3csiV9     Software Version: R009i.05.1.122.4

Terminal Type (513, 715, 4410, 4425, VT220): [513]
this is probably a fine time to discuss the user interface model at work on the definity. it is rather different than on the nortel. basically, the definity makes use of a screen oriented interface throughout. this makes it really easy to use, but makes proper terminal emulation a lot more critical. since the definity started out as an at&t product, it mostly supports at&t terminal emulations e.g. 513 or 4410. you can also use a VT220 compatible terminal but unless your terminal emulator has very good function key emulation or you have a real terminal, the user experience will probably be suboptimal. instead of just hitting a function key, you will have to use some strange escape sequences to do what you want.
so the options facing you are to either use an approximately VT220 compatible terminal or emulator and deal with the escape sequences, find a program that will emulate at&t terminal types, or find a copy of a program called definity site administrator (aka avaya site administrator) which is a windows app that basically takes the curses type interface of the definity and maps it to windows GUI forms. since i was not able to find a copy of definity site administrator and wanted the best user experience possible, i picked up an old copy of procomm plus for windows that includes all types of at&t terminal emulation types. it can be had pretty inexpensively on ebay and it has been working great for me using 4410 emulation.

managing the switch

once you have chosen your terminal type, you will be presented with a copyright notice screen and then will have the opportunity to enter commands.





                This system is restricted to authorized users
                for legitimate business purposes. Unauthorized
                access is a criminal violation of the law.

                     Copyright (c) 1992 - 2000 Avaya Inc.
                      Unpublished & Not for Publication
                             All Rights Reserved











Command:
the command structure of the definity will probably be fairly familiar to anyone who has worked on a few different types of computer networking equipment. basically you have a limited number of verbs e.g. add, change, display, list, remove, and a number of objects on which the command verbs operate. once you have logged in you can type help or hit the F5 key and it will give you a list of commands that are available to you.
the help system built in to the avaya is very comprehensive. it is context-sensitive and supports command completion. for example, if you enter a verb such as add and then hit F5 for help, it will give you a list of objects on which you can operate. if you then enter an object and hit F5 again, it will tell you what all of the optional parameters are for that particular verb-object combination. this is why you hardly need the manuals to get around on the switch.
when you find an account on the definity, the first thing you should do after logging in is to access the help system. if you see the add and change verbs listed in the commands available to you, you have a fully privileged account. if you dont see the add or change verbs in the list of commands, it means you only have a fairly useless limited privilege account.


Please enter one of the following action command words:

add                      get                      remove
busyout                  list                     reset
campon-busyout           mark                     restore
change                   monitor                  save
clear                    netstat                  set
disable                  notify                   status
display                  ping                     test
duplicate                recycle                  trace-route
enable                   release                  upgrade
erase

Enter capital 'R' to repeat the last command

Or enter  'logoff' to logoff the system





Command:
even though the command interpreter is rather different, the workflow is quite similar to that of the meridian. log in to the switch, make changes, save your changes, and log out.

card addressing

on the definity system, cards are addressed by cabinet, carrier, and slot number. individual units on a card such as a line are addressed by unit number, starting at 1. for single chassis small systems, there is only a single cabinet 1 and a single carrier, A. thus, cards are addressed e.g. 1A01, 1A02, 1A03, etc. for hypothetical cards in slot 1, slot 2, or slot 3, respectively. if you wanted the first line on a line card in slot 7, the address would for example be 1A0701. if you wanted the last timeslot on a T1 board in slot 3, the address would for example be 1A0324. be sure to always specify the card and unit numbers using two digits; for example 1A01 instead of 1A1. if you do not use a two digit format you will get errors.
you can use the "list configuration all" or "display circuit-packs" commands to display circuit packs as well as the status of their ports.
display circuit-packs                                           Page   1 of   5
                              CIRCUIT PACKS

        Cabinet: 1                            Carrier: A
                                         Carrier Type: processor

 Slot Code  Sf Mode   Name               Slot Code  Sf Mode   Name
                                          11:
  01: TN2402         PROCESSOR            12:
  02: TN2182 C       TONE/CLOCK           13:
  03: TN767  E       DS1 INTERFACE        14:
  04: TN767  E       DS1 INTERFACE        15:
  05: TN799  C       CONTROL-LAN          16:
  06: TN760  D       TIE TRUNK
  07: TN754  B       DIGITAL LINE
  08: TN2181         DIGITAL LINE
  09: TN746  B       ANALOG LINE
  10: TN556  B       BRI LINE

  '#' indicates circuit pack conflict.




logging out

when you are finished with the switch, you can use the "logoff" command to log out.
at this point you are basically on your own to figure things out with the aid of documentation, the help system, and cisco-definity configuration examples. the remainder of this document will just discuss some common procedures and useful commands, with examples.

set the date and time

set the date and time using the "set time" command. hit F3 when you are done to save the changes.
set time                                                        Page   1 of   1
                               DATE AND TIME

        DATE

            Day of the Week: Friday         Month: February
           Day of the Month: 6               Year: 2009

        TIME

            Hour: 21  Minute: 56    Second: 55   Type: Standard

                       Daylight Savings Rule: 1

  WARNING: Changing the date or time will impact BCMS, CDR and MEASUREMENTS








saving the system configuration

use the "save translation" command to save the system configuration to the pcmcia memory card.
save translation

                               SAVE TRANSLATION

Processor  Command Completion Status                                 Error Code

  SPE-A    Success                                                   0















Command successfully completed
Command:

listing existing user accounts

you can use the "list logins" command to list all of the user accounts currently on the system. the caveat is that a user will only show up in your list of logins if their level of privilege is less than or equal to your own. we just happen to know that such logins as init, inads, and craft exist a priori from the literature.
list logins

                                  LOGINS
Login   Service        Status       Pwd. Aging  ASG Blk Expiration  No. of Sess.
        Level                       Cycle (Days)        Date        Sess.  Used
cust    super-user     inactive                  n  n     /  /
scaron  super-user     active                    n  n     /  /















Command successfully completed
Command:

adding a new user

you can add new users to the definity with the "add login" command. below is an example for a new user with the login "phones". pay particular attention to the "Service Level" field. if this is set to super-user then this will be a privileged customer account with add and change permissions. if the field is set to non-super-user then it will be a nonprivileged read-only customer account. most likely you will want to create super-user logins for yourself. you may also want to set the two logoff notification and the two acknowledgement required fields to "n" which will prevent the system nagging you about things which we are generally doing on purpose every time we log out. when you are done filling out the fields, hit F3 to actually create the user account.
add login phones                                                Page   1 of   1
                                  LOGIN ADMINISTRATION

                Password of Login Making Change:

LOGIN BEING ADMINISTERED
                           Login's Name: phones
                             Login Type: customer
                          Service Level: non-super-user
                                                    Access to INADS Port? n

LOGIN'S PASSWORD INFORMATION
                         Login's Password:
                 Reenter Login's Password:
       Password Aging Cycle Length (Days):

LOGOFF NOTIFICATION
  Facility Test Call Notification? y      Acknowledgement Required? y
       Remote Access Notification? y      Acknowledgement Required? y





configure test lines

the definity supports tons of test lines and other fun sorts of things in a similar vein. as with the meridian, it is not enabled by default and must be explicly configured. unlike the meridian, however, you can dial these test numbers from a station local to the pbx without hitting a reorder tone. use "change system-parameters maintenance" and on the second page you will find fields where you can enter extension numbers for T100, T102, and T105 test lines. note that you need to have the range in which the test lines are located defined as extensions in the dialplan.
change system-parameters maintenance                            Page   2 of   3
                   MAINTENANCE-RELATED SYSTEM PARAMETERS

MINIMUM MAINTENANCE THRESHOLDS ( Before Notification )
        TTRs: 4        CPTRs: 1        Call Classifier Ports: 0
        MMIs: 0          VCs: 0

TERMINATING TRUNK TRANSMISSION TEST ( Extension )
   Test Type 100: 5500     Test Type 102: 5501     Test Type 105: 5502

ISDN MAINTENANCE
   ISDN-PRI Test Call Extension:         ISDN-BRI Service SPID:

DS1 MAINTENANCE
   DS0 Loop-Around Test Call Extension:

SPE OPTIONAL BOARDS
                     Packet Intf1? y     Packet Intf2? y
   Bus Bridge: 01A05  Inter-Board Link Timeslots  Pt0: 6  Pt1: 1  Pt2: 1





adding a station telephone

first, make sure that the card is configured in "change circuit-packs" then use "add station XXXX" where XXXX is the desired DN of the new station. configure as desired on the configuration pages. in particular note that on the definity if you configure an analog extension as a 500 set, it is dial pulse only, and if you configure an analog extension as a 2500 set, it is touch tone only. also note that in contrast to the meridian, you use the same command to configure both analog and digital extensions. so be sure to configure the proper type of phone. specify the full port of the extension for example 01A0701 for line 1 on card 7. when done hit F3 to save and exit.
add station 3000                                                Page   1 of   4
                                     STATION

Extension: 3000                            Lock Messages? n          BCC: 0
     Type: 6408D+                          Security Code:             TN: 1
     Port:                               Coverage Path 1:            COR: 1
     Name:                               Coverage Path 2:            COS: 1
                                         Hunt-to Station:

STATION OPTIONS
              Loss Group: 2                 Personalized Ringing Pattern: 1
             Data Module? n                             Message Lamp Ext: 3000
            Speakerphone: 2-way                      Mute Button Enabled? y
        Display Language: english










add station 3000                                                Page   2 of   4
                                     STATION
FEATURE OPTIONS
           LWC Reception: msa-spe          Auto Select Any Idle Appearance? n
          LWC Activation? y                         Coverage Msg Retrieval? y
  LWC Log External Calls? n                                    Auto Answer: none
             CDR Privacy? n                               Data Restriction? n
   Redirect Notification? y                     Idle Appearance Preference? n
 Per Button Ring Control? n
   Bridged Call Alerting? n                       Restrict Last Appearance? y
  Active Station Ringing: single

        H.320 Conversion? n          Per Station CPN - Send Calling Number?

                                                   Audible Message Waiting? n
                                                Display Client Redirection? n
                                               Select Last Used Appearance? n
                                                 Coverage After Forwarding? s






add station 3000                                                Page   3 of   4
                                     STATION
 SITE DATA
       Room:                                            Headset? n
       Jack:                                            Speaker? n
      Cable:                                           Mounting: d
      Floor:                                        Cord Length: 0
   Building:                                          Set Color:




ABBREVIATED DIALING
     List1:                    List2:                    List3:

BUTTON ASSIGNMENTS
 1: call-appr                            5:
 2: call-appr                            6:
 3: call-appr                            7:
 4:                                      8:




add station 3000                                                Page   4 of   4
                                     STATION

SOFTKEY BUTTON ASSIGNMENTS

 1: directory
 2: drop
 3: int-aut-an
 4: timer
 5: priority
 6: auto-cback
 7: abr-prog
 8: abr-spchar Char: ~p
 9: lwc-store
10: ringer-off
11: btn-view
12: admin







removing a station telephone

use the "remove station XXXX" command where XXXX is the DN of the station that you want to remove. hit F3 to save the removal and exit the screen. as is the case with adding an extension, you use the same command whether you want to remove an analog extension or a digital extension.
remove station 3000                                             Page   1 of   4
                                     STATION

Extension: 3000                            Lock Messages? n          BCC: 0
     Type: 6408D+                          Security Code:             TN: 1
     Port: 01A0802                       Coverage Path 1:            COR: 7
     Name:                               Coverage Path 2:            COS: 1
                                         Hunt-to Station:

STATION OPTIONS
              Loss Group: 2                 Personalized Ringing Pattern: 1
             Data Module? n                             Message Lamp Ext: 3000
            Speakerphone: 2-way                      Mute Button Enabled? y
        Display Language: english











adding a ds1 card

first, configure the card in "change circuit-packs" then create a ds1 configuration record with "add ds1 XXXX" where XXXX is the card e.g. 1A03 for a ds1 card in slot 3. you really configure layer 1 and layer 2 ds1 parameters here, things like coding, framing, and general signalling type. you configure layer 3 signalling specifics in the trunk group. when you are done hit F3 to save and exit.
add ds1 1a03                                                    Page   1 of   2
                                DS1 CIRCUIT PACK

            Location: 01A03                           Name: MC3810PRI
            Bit Rate: 1.544                    Line Coding: b8zs
   Line Compensation: 1                       Framing Mode: esf
      Signaling Mode: isdn-pri
             Connect: line-side
CentreVu Long Timers? n                   Country Protocol: 1
Interworking Message: PROGress            Protocol Version: a
                                                       CRC? n
           Idle Code: 11111111
                              DCP/Analog Bearer Capability: speech




      Slip Detection? n                 Near-end CSU Type: other
                          Alarm When PRI Endpoint Detached? y





add ds1 1a03                                                    Page   2 of   2
                              DS1 CIRCUIT PACK

 ESF DATA LINK OPTIONS

                     Network Management Protocol: tabs
 Send ANSI-T1.403 One-Second Performance Reports? n
                             Far-end CSU Address: b
















busyout and returning a card to service

occasionally, the system tells us that we need to busyout something before we can make a configuration change. in that case you will use the "busyout board XXXX" command to do this so that you can make the change. XXXX is the card e.g. 1A03 again for a card in slot 3. once the busyout is complete you should be able to make any configuration changes. when the changes are done and you want to bring the link back up, use the "release board XXXX" command, again where XXXX is the card e.g. 1A03.

displaying alarms

if you see that the red alarm light on the processor is lit, you should take a look at the system alarms. you do this using the "display alarms" command. this will present you with a form as follows.
display alarms                                                  Page   1 of   1
                                  ALARM REPORT

      The following options control which alarms will be displayed.
        ALARM TYPES

                   Active? y    Resolved? n
                    Major? y       Minor? y      Warning? y

        REPORT PERIOD

                 Interval: a      From:   /  /  :      To:   /  /  :

        EQUIPMENT TYPE ( Choose only one, if any, of the following )

                             Cabinet:
                        Port Network:
                        Board Number:
                                Port:
                            Category:
                           Extension:
              Trunk ( group/member ):   /


just hit F3 and you will get a full report of all the alarms on the system. here is an example of the output from my system.
display alarms

                                 ALARM REPORT

Port       Maintenance On   Alt     Alarm   Svc    Ack?  Date        Date
           Name        Brd? Name    Type    State  1 2   Alarmed     Resolved

01A04      DS1-BD      n            WARNING              02/06/21:50 00/00/00:00
01A04      DS1-BD      n            WARNING              02/06/21:50 00/00/00:00
           SYNC        n            WARNING              02/06/21:50 00/00/00:00
           SYNC        n            WARNING              02/06/21:50 00/00/00:00
           SYNC        n            WARNING              02/06/21:50 00/00/00:00
01A03      DS1-BD      n            WARNING              02/06/22:06 00/00/00:00









Command successfully completed
Command:

clearing minor PR-MAINT alarms

as i mentioned earlier on this page, we certainly arent going to hook up a modem to the INADS port and connect it to a phone line. the system does however assume that you would be doing this and throws an alarm when the INADS modem is not hooked up. to disable the INADS modem and associated alarm, use the "change system-paramaters maintenance" command and delete anything under "First OSS Endpoint" and "Second OSS Endpoint" on the first page of settings. set "Alarm Origination to OSS Numbers" to neither and set "Test Remote Access Port" to n. finally, go page 3 and set "Modem Connection" to none. hit F3 to save the changes; this should clear the minor alarm.
change system-parameters maintenance                            Page   1 of   3
                   MAINTENANCE-RELATED SYSTEM PARAMETERS

OPERATIONS SUPPORT PARAMETERS
            Product Identification: XXXXXXXXXX
                First OSS Endpoint:                    Abbrev Alarm Report? y
               Second OSS Endpoint:                    Abbrev Alarm Report? n
  Alarm Origination to OSS Numbers: neither
        Cleared Alarm Notification? y                 Suspension Threshold: 5
              Restart Notification? y
           Test Remote Access Port? n
        CPE Alarm Activation Level: none

     Customer Access to INADS Port? y
       Repeat Dial Interval (mins): 7

SCHEDULED MAINTENANCE
                  Start Time: 01 : 00                   Stop Time: 06 : 00
           Daily Maintenance: daily              Save Translation: daily
                                         Command Time-out (hours): 2
 Control



change system-parameters maintenance                            Page   3 of   3
                   MAINTENANCE-RELATED SYSTEM PARAMETERS

         Modem Connection: none
                Data Bits: 8
                   Parity: none


















cleaning out an old definity

there is a sort of workflow to cleaning out the configuration from a secondhand definity system. basically proceed in the following order
  • remove extensions assigned as incoming trunk group destinations
  • remove trunk group members
  • remove trunk groups from routing patterns
  • remove signaling groups
  • remove trunk groups
  • remove ds1 records
  • remove extensions
  • clean up dialplan and access codes
  • configure circuit packs to match your current configuration
  • reconfigure switch as desired
to remove extensions assigned as incoming trunk group destinations use "list trunk-groups" to list all of the trunk groups on the system. for each trunk-group X use "change trunk-group X" and clear out any values in the "Incoming Destination" field on the first page.
to remove trunk group members first use the "list trunk-group" command to list all of the trunk groups on the system. for each trunk group X "list members trunk-group X" to see all of the members. then for each trunk group X, use "change trunk-group X" to actually make the change. go to page 4 of the trunk-group configuration and use F4 to clear out all of the members of the trunk group. when done hit F3 to save changes and exit.
to remove trunk groups from routing patterns, use "list route-pattern" to list all of the route-patterns on the system. for each route-pattern X use "change route-pattern X" to actually make the change. clear out the grp. no, frl, npa, pfx, mrk, hop lmt, toll list, etc using the F4 key. when done hit F3 to save changes and exit. note that when we clear all entries from a route-pattern, it will automatically be deleted by the system. in performing this operation we are basically removing all of the trunks from a route.
to remove signaling groups, use the "remove signaling-group X" command for the signal group in question, X.
to remove trunk groups, use "list trunk-group" to list all of the trunk-groups on the system. then for each trunk-group X, use "remove trunk-group X" to remove it. hit F3 to confirm removal of the trunk group.
to remove a ds1 record, use "remove ds1 X" for a ds1 card X e.g. 1A03.
to remove extensions, use "list stations" to get a full list of all extensions on the system. then for each extension X, use "remove station X" and hit F3 to confirm.
now that we have cleared out trunks and stations we should be able to change the circuit pack configuration to match what we actually have in the chassis without running into any dependencies that we must remove. to configure the circuit packs, just use the "change circuit-packs" command and key the circuit pack and vintage into the field corresponding to the requisite slot.
change circuit-packs                                            Page   1 of   5
                              CIRCUIT PACKS

        Cabinet: 1                            Carrier: A
                                         Carrier Type: processor

 Slot Code  Sf Mode   Name               Slot Code  Sf Mode   Name
                                          11:
  01: TN2402         PROCESSOR            12:
  02: TN2182 C       TONE/CLOCK           13:
  03: TN767  E       DS1 INTERFACE        14:
  04: TN767  E       DS1 INTERFACE        15:
  05: TN799  C       CONTROL-LAN          16:
  06: TN760  D       TIE TRUNK
  07: TN754  B       DIGITAL LINE
  08: TN2181         DIGITAL LINE
  09: TN746  B       ANALOG LINE
  10: TN556  B       BRI LINE

  '#' indicates circuit pack conflict.




note that we might not be able to remove analog and digital station line cards even after deleting all of the station configuration. this is potentially due to a feature called TTI. to see if TTI is enabled, use the " list config board X" for the slot that we are trying to change e.g. 1A07. if the status for all of the ports is given as "t" then the TTI feature is turned on and that is most likely what is preventing us from changing the configuration at that slot. to turn off TTI, use the "change system features" command and go to the second page. there should be an option there that looks like "Terminal Translation Initialization (TTI) Enabled?" when you find it it will most likely be set to "y". change it to "n" then hit F3 to save and exit. you should then be able to make the desired changes on the form "change circuit-packs". once you have configured the circuit packs as desired, go back to the "change system features" form and turn TTI back on.
change system-parameters features                               Page   2 of  10
                    FEATURE-RELATED SYSTEM PARAMETERS
LEAVE WORD CALLING PARAMETERS
  Maximum Number of Messages Per Station (when MSA not in service): 10
               Maximum Number of External Calls Logged Per Station: 0
                     Message Waiting Indication for External Calls? n
  Stations with System-wide Retrieval Permission (enter extension)
    1:         3:         5:         7:          9:
    2:         4:         6:         8:         10:
      WARNING!  SEE USER DOCUMENTATION BEFORE CHANGING TTI STATE
                 Terminal Translation Initialization (TTI) Enabled? y
                  TTI State: voice      TTI Security Code: 1
           Record CTA/PSA/TTI Transactions in History Log? y
                             COR for PSA Dissociated Sets:

                        Customer Telephone Activation(CTA) Enabled? n
                    Prohibit Bridging Onto Calls With Data Privacy? n
                         Enhanced Abbreviated Dial Length (3 or 4): 3
                     Record All Submission Failures in History Log? y
                         Record PMS/AD Transactions in History Log? n





in the case of digital trunk cards such as the TN464 or TN767 we might have to remove a corresponding ds1 record before we remove the card in "change circuit-packs". you can use the "remove ds1 X" for each slot X e.g. 1A03 in which a ds1 board is installed. if it says that you cannot remove the synchronization source, the ds1 card that you are trying to remove was configured to be the clock synchronization source for the system. to get around this you must first install a ds1 card in another slot on the switch and configure it first. once that is done use the "change synchronization" command and set the "Primary" source over to the slot number of the other ds1 board that you configured. hit F3 to save and exit. then be sure that the ds1 record for the card that we want to take out of the circuit pack configuration has been removed. finally, you should then be able to return to "change circuit-packs" and change the card for the slot in question.

reclaiming the dial plan

as with clearing out old configuration in general, there is also a particular workflow for reclaiming the dial plan from a gray market definity. first, you must clean out the second digit table. use "display second-digit X" for each digit X from 0 to 9 as well as * and #. for each second-digit record X that actually exists we must remove the record with "remove second-digit X".
but before we remove the second digit table we might have to clear out stuff that already configured in the system with numbers that lie in the range we wish to reclaim. use the "list extension-type" to get a feel for what is going on. you can also use commands like "list trunk-group" and "list data-module" and "list stations " to see what might be holding up space in the dialplan and preventing us from making changes. when we have identified the troublesome objects, for each object X use "remove trunk-group X" or "remove data-module X" or "remove station X" as appropriate to remove them.
if running into trouble removing a data-module you may have to use "change data-module X" for each data module X in question and set "Enable Link" to "n" before removing it.
you may also run into an error that looks something like "need to remove from communication-interface processor-channels form". if this occurs, use the "display communication-interface processor-channels" command to list all of the communication-interface processor-channels on the system then use the "change communication-interface processor-channels " and set "Enable" to "n" for any in question and clear all of the fields using F4. once you save this try again to "remove data-module X" for the module in question.
you may also run into an error something like "need to remove ip routes". if this occurs, use the "display ip-route X" for various X starting at 0 or 1 and working up until the system is telling you fairly consistently that no route with that number exists. then for each ip-route X use "remove ip-route X" to remove the route. then you should be able to get rid of the data-module with "remove data-module X" where X is the extension displayed in the output of "list extension-type".
you ultimately will use the "change dialplan" command to modify the system dialplan. while you are in there, you may want to set the "Uniform Dialing Plan" parameter to "none" temporarily as that can sometimes facilitate making modifications by clearing up locks over a particular block of digits.
change dialplan                                                 Page   1 of   1
                               DIAL PLAN RECORD

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


you may want to clear out the automatic routing configuration as well, then restore what you need of it later from scratch. to do this, use "list aar digit-conversion" to get a list of all the AAR digit conversion rules on the system, then for each leading digit X use "change aar digit-conversion X" and clear out all of the fields to remove the rule. as always, hit F3 to save the changes after clearing out each page. when done with all of the AAR digit conversion rules, you will have to move on to ARS. similarly, use "list ars digit-conversion " to list all of the ARS digit conversion rules on the system. then for each leading digit X use "change ars digit-conversion X" and clear out all of the fields to remove the rule. now that you have done this, if you want to totally disable ARS (not possible for isdn pri trunks, for reasons you will see later) you can use "change feature-access-codes" to clear the value in the "Automatic Route Selection (ARS) Access Code 1" field which is usually 9.

reclaiming ARS analysis

we have to use ARS if we want to use idsn pri so it is useful to see how to basically configure ARS in the simplest possible way from scratch.
first, if we undefined 9 as a FAC in the dialplan while in the process of reclaiming it, use "change dialplan" to make first digit 9, length 1, to be FAC. you will need to remove any trunk-groups that use 9 as a DAC first if you happened to try and set any up. then use the " change feature-access-codes" and modify "Automatic Route Selection (ARS) Access Code 1" to be 9. hit F3 to save and exit. we will then clear out any remaining ARS configuration that might have been left over after our dialplan scrubbing efforts above. use the "change ars analysis X" command for each digit X from 0 to 9 as well as *. clear out everything in each and hit F3 to save. be sure to hit F3 to save changes on each page before moving along to the next or else all of the changes will be lost!
once you have cleared out the ARS analysis configuration in this fashion, you can recreate it from scratch using the "change ars analysis" command. below is a simple ARS anslysis table that basically allows everything, regardless of the first digit or total length of the dialed string, tags it as a local call, and sends it out over whatever trunks are defined in route-pattern 1.


                           ARS DIGIT ANALYSIS REPORT

                            Location:  all

               Dialed            Total        Route    Call      Node
               String          Min    Max    Pattern   Type     Number

         0                      1      28     1        locl
         1                      1      28     1        locl
         2                      1      28     1        locl
         3                      1      28     1        locl
         4                      1      28     1        locl
         5                      1      28     1        locl
         6                      1      28     1        locl
         7                      1      28     1        locl
         8                      1      28     1        locl
         9                      1      28     1        locl




once this has been done, then use "change route-pattern X" for X equal to the number of the route-pattern that you specified in the ARS analysis table (here, 1). this is where you will map trunk groups to a route-pattern. before we do this, we first must have created the trunk-group in question. once you have added a trunk-group and signaling-group and have added members to the trunk-group, you can add the trunk group to a route-pattern.
display route-pattern 1
                            Pattern Number: 1

   Grp. FRL NPA Pfx Hop Toll No.  Inserted                             DCS/ IXC
   No.          Mrk Lmt List Del  Digits                               QSIG
                             Dgts                                      Intw
 1: 1    0                                                              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  n            rest                                         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

this simplest possible ARS configuration will suffice perfectly for the configuration of an isdn pri did trunk as detailed below.

configuring a TN750 integrated announcements card

the TN750 integrated announcement card is really inexpensive and a lot of fun. you can store up to 255 seconds of recorded audio on a TN750 card, broken up into any number of individual announcements. here is how you configure one from scratch
step 1: add the board in "change circuit-packs"
change circuit-packs                                            Page   1 of   5
                              CIRCUIT PACKS

        Cabinet: 1                            Carrier: A
                                         Carrier Type: processor

 Slot Code  Sf Mode   Name               Slot Code  Sf Mode   Name
                                          11:
  01: TN2402         PROCESSOR            12:
  02: TN2182 C       TONE/CLOCK           13:
  03: TN767  E       DS1 INTERFACE        14:
  04: TN767  E       DS1 INTERFACE        15:
  05: TN799  C       CONTROL-LAN          16:
  06: TN760  D       TIE TRUNK
  07: TN750  C       ANNOUNCEMENT
  08: TN2181         DIGITAL LINE
  09: TN746  B       ANALOG LINE
  10: TN556  B       BRI LINE

  '#' indicates circuit pack conflict.




  
step 2: add a data-module for the communication channel between the PBX processor and the TN750 board. use "add data-module XXXX" for some free number XXXX defined as an extension in the dialplan. here the TN750 board is in slot 1A07 and we are giving it extension 5601.
add data-module 5601                                            Page   1 of   1
                               DATA MODULE

  Data Extension: 5601            Name: tn750c
            Type: announcement     COS: 1
           Board: 1a07             COR: 1
             ITC: restricted        TN: 1









ASSIGNED MEMBER ( Station with a data extension button for this data module )

         Ext     Name
      1:




      
step 3: define an announcement with the "change announcement" command. for each announcement, fill in an unused directory number defined as an extension in the dialplan (here, 5700). set the type as integrated and you can furnish a descriptive name for the announcement. i leave COR and TN set to 1 which is default.
set Q to y; according to avaya, this means that calls to the announcement will queue to hear the announcement if all ports on the announcement pack are busy (instead of getting reorder?) and set the Pro field to n for this example. basically if the Pro field is set to n then it can be deleted or overwritten from any station with console permissions, if set to y then it cannot.
change announcements                                            Page   1 of   8
                          ANNOUNCEMENTS/AUDIO SOURCES

Ann.
No.  Ext.  Type      COR TN  Name                        Q QLen Pro Rate Port

1    5700  integrated 1  1   test announcement           y N/A  n   64  1a07
2                     1  1                               n
3                     1  1                               n
4                     1  1                               n
5                     1  1                               n
6                     1  1                               n
7                     1  1                               n
8                     1  1                               n
9                     1  1                               n
10                    1  1                               n
11                    1  1                               n
12                    1  1                               n
13                    1  1                               n
14                    1  1                               n
15                    1  1                               n
16                    1  1                               n


step 4: now that we have defined at least one announcement, we should be able to see it show up in "list integrated-annc-boards"
list integrated-annc-boards

                           INTEGRATED ANNOUNCEMENTS
Board Location: 01A07                         Time Remaining at 32Kbps: 0

Annc.  Internal Announcement                                         Length in
Number Number   Extension    Name                        Rate        Seconds
1      1         5700        test announcement            64             0














Command successfully completed
Command:
step 5: now we can record some announcements. first of all, we need to have access to a phone with console permission in order to do the recording. console permission is an attribute set in the class of service.
use the "change cos" command to alter the classes of service such that at least one of them has console access. since mine is a very casual switch, i just give class of service 1 the console permission. this means that you can record announcements from basically any station on the network. otherwise, assign the permission to some class of service to your preference and assign that class of service to the phone that you will use for making the recordings.
change cos                                                      Page   1 of   1
                                CLASS OF SERVICE

                                0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15

 Auto Callback                  n  y  y  n  y  n  y  n  y  n  y  n  y  n  y  n
 Call Fwd-All Calls             n  y  n  y  y  n  n  y  y  n  n  y  y  n  n  y
 Data Privacy                   n  y  n  n  n  y  y  y  y  n  n  n  n  y  y  y
 Priority Calling               n  y  n  n  n  n  n  n  n  y  y  y  y  y  y  y
 Console Permissions            n  y  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Off-hook Alert                 n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Client Room                    n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Restrict Call Fwd-Off Net      y  y  y  y  y  y  y  y  y  y  y  y  y  y  y  y
 Call Forwarding Busy/DA        n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Personal Station Access (PSA)  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Extended Forwarding All        n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Extended Forwarding B/DA       n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 Trk-to-Trk Transfer Override   n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n
 QSIG Call Offer Originations   n  n  n  n  n  n  n  n  n  n  n  n  n  n  n  n





 
step 6: now that we have suitably altered the class of service, find a phone with console permission. use "display feature-access-codes" to determine the access code for the integrated announcement board.
display feature-access-codes                                    Page   1 of   4
                               FEATURE ACCESS CODE (FAC)
         Abbreviated Dialing List1 Access Code: #7
         Abbreviated Dialing List2 Access Code: #8
         Abbreviated Dialing List3 Access Code: #9
Abbreviated Dial - Prgm Group List Access Code:
                      Announcement Access Code: 820
                       Answer Back Access Code: #6
      Auto Alternate Routing (AAR) Access Code:
    Auto Route Selection (ARS) - Access Code 1: 9     Access Code 2:
                 Automatic Callback Activation: *5     Deactivation: #5
Call Forwarding Activation Busy/DA:        All: *2     Deactivation: #2
                         Call Park Access Code: *6
                       Call Pickup Access Code: *7
CAS Remote Hold/Answer Hold-Unhold Access Code: 823
                  CDR Account Code Access Code:
                        Change COR Access Code:
                   Change Coverage Access Code:

                  Data Origination Access Code:
                      Data Privacy Access Code: 835
              Directed Call Pickup Access Code: #1


 
here, the code to dial to manage recorded announcements is 820.
step 7: before you proceed any further, now that we have the recorded announcement board all configured up, you might want to do a "reset system 5" or something to make sure everything is sympatico.
step 8: when everything is up and running, to record an announcement, first dial the announcement access code (here, 820). you should land at another dial tone. at that dial tone, dial the extension of the announcement that you want to record (here, 5700). you should here a dial tone again. press 1 to begin recording. when you are done, you can hit the pound key to finish recording and save. you will land at another dial tone, at which point you can hang up.
to hear the recording, dial its extension (here, 5700). it is just an ordinary extension, available locally or from over a trunk. but please note that avaya suggests that you wait at least 15 seconds after recording an announcement before trying to play it.
if you want to re-record an announcement, just repeat this procedure and whatever you do will just overwrite the existing announcement.
if you want to delete an announcement, dial the announcement access code (here, 820) and you should land at dial tone. at the dial tone, dial the extension of the announcement in question (say, 5700). you should get another dial tone. hit 3 to delete the message and hang up the phone.
you can also remove an announcement through the command line by removing it from the announcements table with the "change announcements" command.
you dont need to do anything special to save your announcements; they are automatically synchronized to the translation card by the system.

configuring a TN799 C-LAN card for remote administration

if you have a definity with a TN799 C-LAN card, it is possible to set it up such that you can telnet to the pbx and perform administration just as if you were sitting at the console. i have this up and running with procomm telnet doing 4410 emulation and it works great. first thing you need to do is cable up the TN799 to an RJ45 jack according to the following pinouts.
ethernet signal definity wire color definity RJ21 pin 66 block pin rj-45 JACK pin
TD+ white+orange stripe 27 3 1
TD- orange+white stripe 2 4 2
RD+ white+green stripe 28 5 3
RD- orange+white stripe 3 6 6
cable from 66 block pin to RJ45 pin. if you cable it up in this way, you should be able to connect from the RJ45 jack to an ethernet switch with a straight through cable and have the link come up, no problem. a lot of people want to say that you have to hard code the speed and duplex on the switch to 10/half to make it work but my switch and avaya seem to autonegotiate just fine.
before we start, go back to "change system-parameters maintenance" and head down to page 2. under the SPE OPTIONAL BOARDS heading, be sure that Packed Intf2 is set to y and enter the slot number of the C-LAN board in the Bus Bridge field (here 1A05). note that if you do not have a C-LAN board installed in the system, you should set Packet Intf2 to n otherwise you will get an alarm.
change system-parameters maintenance                            Page   2 of   3
                   MAINTENANCE-RELATED SYSTEM PARAMETERS

MINIMUM MAINTENANCE THRESHOLDS ( Before Notification )
        TTRs: 4        CPTRs: 1        Call Classifier Ports: 0
        MMIs: 0          VCs: 0

TERMINATING TRUNK TRANSMISSION TEST ( Extension )
   Test Type 100: 5500     Test Type 102: 5501     Test Type 105: 5502

ISDN MAINTENANCE
   ISDN-PRI Test Call Extension:         ISDN-BRI Service SPID:

DS1 MAINTENANCE
   DS0 Loop-Around Test Call Extension:

SPE OPTIONAL BOARDS
                     Packet Intf1? y     Packet Intf2? y
   Bus Bridge: 01A05  Inter-Board Link Timeslots  Pt0: 6  Pt1: 1  Pt2: 1





that being done, we can now turn to system settings directly pertaining to setting up the C-LAN board for ip administration.
step 1: find a free communication-interface link number with the "display communication-interface links" command.
display communication-interface links                           Page   1 of   2

                                INTERFACE LINKS
Link Enable Est Ext   Type     Destination DTE Conn  Name
            Conn               Number      DCE Mod.
  1: n      n
  2: n      n
  3: n      n
  4: n      n
  5: n      n
  6: n      n
  7: n      n
  8: n      n
  9: n      n
 10: n      n
 11: n      n
 12: n      n
 13: n      n
 14: n      n
 15: n      n
 16: n      n
 17: n      n


step 2: use "add data-module XXXX" where XXXX is some unused number defined as an extension in the dialplan. set the type to be ethernet, specify port 17 on the c-lan card, furnish a free link number in the link field, and provide a name.
add data-module 5600                                            Page   1 of   1
                               DATA MODULE

  Data Extension: 5600            Name: avaya1
            Type: ethernet
            Port: 1a0517
            Link: 1




Network uses 1's for Broadcast Addresses? y












hit F3 when done to save the data-module configuration. now the data-module that you just created should show up in the list of communication interface links.
display communication-interface links                           Page   1 of   2

                                INTERFACE LINKS
Link Enable Est Ext   Type     Destination DTE Conn  Name
            Conn               Number      DCE Mod.
  1: y      n   5600  ETHERNET                       avaya1
  2: n      n
  3: n      n
  4: n      n
  5: n      n
  6: n      n
  7: n      n
  8: n      n
  9: n      n
 10: n      n
 11: n      n
 12: n      n
 13: n      n
 14: n      n
 15: n      n
 16: n      n
 17: n      n


 
step 3: use the "change node-names ip" command to configure an ip and host name. think of this sort of like /etc/hosts on a sun machine. it contains both static address to name mappings for other hosts on the network, and also is used to configure the ip address of the machine in question by mapping the hostname of the machine itself to an ip. here i am using hostname avaya1 and ip 172.16.1.83 for my network.
change node-names ip                                            Page   1 of   1
                                  IP NODE NAMES
    Name              IP Address           Name              IP Address
avaya1              172.16 .1  .83
default             0  .0  .0  .0
node1               192.168.2  .70
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .
                       .   .   .





		       
step 4: use "change ip-interfaces" to configure an ip interface. set type to C-LAN and slot to the slot number of your C-LAN card. fill in the vintage (e.g. B, C) in the Sfx field. enter the node name that you created earlier with the desired ip address. fill in the appropriate subnet mask and gateway. you can leave the network region set to 1. set enable to y and hit F3 to save and exit.
change ip-interfaces                                            Page   1 of   6

                                   IP INTERFACES

Enable                                                                       Net
Eth Pt Type   Slot  Code Sfx Node Name       Subnet Mask     Gateway Address Rgn
   y   C-LAN  01A05 TN799  C avaya1          255.255.255.0   172.16 .1  .1   1
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .
   n                                         255.255.255.0      .   .   .



   
step 5: use "change ip-services" to set up the telnet server on the avaya. set service type to SAT and enable it. set the local node to be the node name with the desired ip address that you created earlier. local port will be the tcp port that the avaya listens on for telnet connections. set remote node to any and the remote port to 0.
change ip-services                                              Page   1 of   2

                                   IP SERVICES
 Service     Enabled     Local        Local       Remote      Remote
  Type                   Node         Port        Node        Port
SAT           y      avaya1           5023    any             0


















step 6: now you should be able to test ip connectivity to the avaya. the definity will respond to pings, and you should now be able to telnet to it on the defined port.
sonnet.diablonet.net> ping 172.16.1.83
PING 172.16.1.83 (172.16.1.83): 56 data bytes
64 bytes from 172.16.1.83: icmp_seq=0 ttl=254 time=2.287 ms
64 bytes from 172.16.1.83: icmp_seq=1 ttl=254 time=1.895 ms
64 bytes from 172.16.1.83: icmp_seq=2 ttl=254 time=1.818 ms
64 bytes from 172.16.1.83: icmp_seq=3 ttl=254 time=2.069 ms
^C
--- 172.16.1.83 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.818/2.017/2.287/0.180 ms
sonnet.diablonet.net> 
sonnet.diablonet.net> telnet 172.16.1.83 5023
Trying 172.16.1.83...
Connected to 172.16.1.83.
Escape character is '^]'.

Login: 
telnet> q
Connection closed.
sonnet.diablonet.net> 
for best results, you will still need to use a terminal emulator that supports at&t terminal types when coming in over a telnet connection. i find that the telnet app that comes with procomm plus works well enough.

configuring call detail recording over the C-LAN

once you have the C-LAN card set up, you can configure it quite easily to send CDR data to a host on the network. just follow the procedure below.
step 1: create an entry for the loghost in "change node-names ip". here the loghost will be the node sonnet with ip 75.144.70.42.
change node-names ip                                            Page   1 of   1
                                  IP NODE NAMES
    Name              IP Address           Name              IP Address
avaya1              172.16 .1  .83                            .   .   .
default             0  .0  .0  .0                             .   .   .
node1               192.168.2  .70                            .   .   .
sonnet              75 .144.70 .42                            .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
                       .   .   .                              .   .   .
( 3  of 3   administered node-names were displayed )
Use 'list node-names' command to see all the administered node-names
Use 'change node-names ip xxx' to change a node-name 'xxx' or add a node-name


step 2: configure the cdr service with "change ip-services". service type will be CDR1. set the local node to the node name that you assigned earlier for the ip of your switch. the local port will set itself to 0 when you pick service type CDR1. set the remote node name to that of the loghost you created above. pick an arbitrary port on the remote host to connect to.
change ip-services                                              Page   1 of   3

                                   IP SERVICES
 Service     Enabled     Local        Local       Remote      Remote
  Type                   Node         Port        Node        Port
SAT           y      avaya1           5023    any             0
CDR1                 avaya1           0       sonnet          5514

















step 3: tune cdr parameters with "change system-parameters cdr". configure the primary output format as expanded and set the primary output endpoint to be CDR1 to match the service type from the ip services configuration screen.
also note that here is where you can enable call detail recording for intra-switch calls as well as for calls that go over trunks.
change system-parameters cdr                                    Page   1 of   1
                            CDR SYSTEM PARAMETERS

 Node Number (Local PBX ID): 1                     CDR Date Format: month/day
      Primary Output Format: expanded      Primary Output Endpoint: CDR1
    Secondary Output Format:
           Use ISDN Layouts? n
       Use Enhanced Formats? n      Condition Code 'T' For Redirected Calls? n
Modified Circuit ID Display? n                  Remove # From Called Number? n
                  Record Outgoing Calls Only? n            Intra-switch CDR? y
  Suppress CDR for Ineffective Call Attempts? y     Outg Trk Call Splitting? y
      Disconnect Information in Place of FRL? n       Outg Attd Call Record? y
                                                     Interworking Feat-flag? n
 Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
                                    Calls to Hunt Group - Record: member-ext
Record Called Vector Directory Number Instead of Group or Member? n

     Inc Trk Call Splitting? n
  Record Non-Call-Assoc TSC? n
      Record Call-Assoc TSC? n   Digits to Record for Outgoing Calls: dialed
   Privacy - Digits to Hide: 0               CDR Account Code Length: 15



   
step 4: make sure that cdr logging is enabled on your trunks with "display trunk-group X" for each trunk group X. if you need to turn it on, you can use "change trunk-group" to set CDR Reports to y.
display trunk-group 1                                           Page   1 of  10
                                TRUNK GROUP

Group Number: 1                    Group Type: isdn          CDR Reports: y
  Group Name: MC3810PRI                   COR: 1        TN: 1        TAC: 600
   Direction: two-way        Outgoing Display? y
 Dial Access? y                Busy Threshold: 99          Night Service:
Queue Length: 0
Service Type: tandem                                        TestCall ITC: rest
                         Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
         Codeset to Send Display: 6     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: none
  Supplementary Service Protocol: a     Digit Handling (in/out): enbloc/enbloc

            Trunk Hunt: descend
                                                   Digital Loss Group: 13
Calling Number - Delete:     Insert:                 Numbering Format:
              Bit Rate: 1200         Synchronization: async    Duplex: full
 Disconnect Supervision - In? y  Out? y
 Answer Supervision Timeout: 0


 
step 5: use netcat or a perl script on your loghost to listen on the requisite port and collect call detail records from the avaya. at this point, you should be able to place a test call and see some data generated.
sonnet.diablonet.net> netcat -l -p 5514
0052 0001 7    9  600    98114882600#       3001                            7      23 4          1         0 1 0
02 23
02 23
0056 0001 7    9  600    98114429999#       3001                            7      23 4          1         0 1 0

isdn pri trunk configuration notes

i currently have this particular configuration up and running with no trouble between my avaya definity and a cisco mc3810 voip gateway using idsn pri. it seems to be easier to get isdn pri up and running on the definity compared to a meridian so if you have cut your teeth on meridian, the definity should be very straightforward. i am assuming that you are starting mostly from a clean base and that there are no existing automatic routing rules, ds1 records, trunk groups, signaling groups, dialplan, etc. the scenario is shown in the diagram below.
[cisco to nortel network diagram]
to get this up and running, all you need is a cisco mc3810 with the dvm module and an avaya definity with either a TN767 card or a TN464 card. the d-channel processing is either done by the central processor in the case of the TN767 or on the card itself in the case of the TN464. so you dont have to concern yourself with picking the proper d-channel daughterboard. clocking for the definity is handled by the tone/clock board. i also want to note that you do not need any kind of csu/dsu on the avaya side of things for either card so there is no need to purchase such things e.g. avaya 120A CSU/DSU. you can connect directly from the ds1 board to the cisco. the table below describes the pinouts.
definity pin66 block pinpbx side wire color on 66 blockrj45 JACK pin
4743violet+orange stripepin 5
2244orange+violet stripepin 4
4845violet+green stripepin 2
2346green+violet stripepin 1
if you terminate it in this way then you can use a straight through cable e.g. ethernet cord to connect between the jack from the definity and the cisco router.
a few other miscellaneous notes: "isdn switch-type primary-ni" on the cisco corresponds to country protocol 1, protocol version "a" in the "change ds1" form on the avaya . for this configuration we will set the "Signaling Mode" on the avaya to be isdn-pri and will also set "Connect" on the avaya to line-side. also note that on the cisco we are not using "isdn protocol-emulate network" on the D channel, Serial1:23.
we will begin with the configuration of the avaya, then move along to the configuration of the cisco.
step 1: configure the ds1 board itself using "add ds1" or "change ds1" if it has already been added. in our example the ds1 board we will be using is in slot 1A03.
display ds1 1a03                                                Page   1 of   2
                                DS1 CIRCUIT PACK

            Location: 01A03                           Name: MC3810PRI
            Bit Rate: 1.544                    Line Coding: b8zs
   Line Compensation: 1                       Framing Mode: esf
      Signaling Mode: isdn-pri
             Connect: line-side
CentreVu Long Timers? n                   Country Protocol: 1
Interworking Message: PROGress            Protocol Version: a
                                                       CRC? n
           Idle Code: 11111111
                              DCP/Analog Bearer Capability: speech




      Slip Detection? n                 Near-end CSU Type: other
                          Alarm When PRI Endpoint Detached? y





display ds1 1a03                                                Page   2 of   2
                              DS1 CIRCUIT PACK

 ESF DATA LINK OPTIONS

                     Network Management Protocol: tabs
 Send ANSI-T1.403 One-Second Performance Reports? n
                             Far-end CSU Address: b















step 2: create a new trunk group with "add trunk-group". dont fill in the member list yet, just fill out the first two pages of trunk parameters. after you have done this, you will create a signaling group (step 3). after you have created the signaling group, you return to the trunk group configuration and fill out the member list. i set the "Service Type" to tandem at the suggestion of a cisco configuration example and it seems to work well.
display trunk-group 1                                           Page   1 of  10
                                TRUNK GROUP

Group Number: 1                    Group Type: isdn          CDR Reports: y
  Group Name: MC3810PRI                   COR: 1        TN: 1        TAC: 600
   Direction: two-way        Outgoing Display? y
 Dial Access? y                Busy Threshold: 99          Night Service:
Queue Length: 0
Service Type: tandem                                        TestCall ITC: rest
                         Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
         Codeset to Send Display: 6     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: none
  Supplementary Service Protocol: a     Digit Handling (in/out): enbloc/enbloc

            Trunk Hunt: descend
                                                   Digital Loss Group: 13
Calling Number - Delete:     Insert:                 Numbering Format:
              Bit Rate: 1200         Synchronization: async    Duplex: full
 Disconnect Supervision - In? y  Out? y
 Answer Supervision Timeout: 0


display trunk-group 1                                           Page   2 of  10
TRUNK FEATURES
          ACA Assignment? n            Measured: none      Wideband Support? n
                                                          Maintenance Tests? y
                               Data Restriction? n     NCA-TSC Trunk Member:
                                      Send Name: n      Send Calling Number: y
            Used for DCS? n             Hop Dgt? n
   Suppress # Outpulsing? n    Numbering Format: public
 Outgoing Channel ID Encoding: exclusive     UUI IE Treatment: service-provider

                                                 Replace Restricted Numbers? n
                                                Replace Unavailable Numbers? n
                                                      Send Connected Number: n


               Send UCID? n
 Send Codeset 6/7 LAI IE? y                         Ds1 Echo Cancellation? n

                                          US NI Delayed Calling Name Update? n

                            Network (Japan) Needs Connect Before Disconnect? n



display trunk-group 1                                           Page   4 of  10
                                 TRUNK GROUP
                                      Administered Members (min/max):   1/23
GROUP MEMBER ASSIGNMENTS                  Total Administered Members:  23

       Port    Code Sfx Name        Night           Sig Grp
  1: 01A0301  TN767  E                                1
  2: 01A0302  TN767  E                                1
  3: 01A0303  TN767  E                                1
  4: 01A0304  TN767  E                                1
  5: 01A0305  TN767  E                                1
  6: 01A0306  TN767  E                                1
  7: 01A0307  TN767  E                                1
  8: 01A0308  TN767  E                                1
  9: 01A0309  TN767  E                                1
 10: 01A0310  TN767  E                                1
 11: 01A0311  TN767  E                                1
 12: 01A0312  TN767  E                                1
 13: 01A0313  TN767  E                                1
 14: 01A0314  TN767  E                                1
 15: 01A0315  TN767  E                                1



display trunk-group 1                                           Page   5 of  10
                                 TRUNK GROUP
                                      Administered Members (min/max):   1/23
GROUP MEMBER ASSIGNMENTS                  Total Administered Members:  23

       Port    Code Sfx Name        Night           Sig Grp
 16: 01A0316  TN767  E                                1
 17: 01A0317  TN767  E                                1
 18: 01A0318  TN767  E                                1
 19: 01A0319  TN767  E                                1
 20: 01A0320  TN767  E                                1
 21: 01A0321  TN767  E                                1
 22: 01A0322  TN767  E                                1
 23: 01A0323  TN767  E                                1
 24:
 25:
 26:
 27:
 28:
 29:
 30:


step 3: configure the signaling-group according to the settings shown in the example below. it is very easy, just tell it to use channel 24 for signaling and that it is associated with our trunk group that we just created and that is all you have to do.
display signaling-group 1                                       Page   1 of   5
                                SIGNALING GROUP

 Group Number: 1
                    Associated Signaling? y          Max number of NCA TSC: 0
                       Primary D-Channel: 01A0324     Max number of CA TSC: 0
                                                   Trunk Group for NCA TSC:
       Trunk Group for Channel Selection: 1
          Supplementary Service Protocol: a














once you have configured a ds1 record, trunk group, and signaling group, the ds1 link should pretty much have full connectivity up to iso layer 3. that is to say, the D channel should be up and you should see Q921/Q931 messages passing between the avaya and cisco. now basically all you have to do is set up the dialplan and ARS correctly on the avaya so that you can access your trunk and make some calls.
here is the dialplan. the important bits to note are primarily that we hae extensions on 3xxx and 4xxx for digital and analog sets, respectively. we use '9' as a FAC to get into ARS and we use 6xx codes for trunk access codes (every time you create a trunk-group, you must assign it as a trunk access code, even if you intend to only access it through ARS). the use of 6xx for trunk access codes seems to be something of a de facto standard in the avaya world. the silly thing of it is that you cant actually use a did isdn pri trunk through a trunk access code anyway (you must go through ARS) so the trunk code is just a nonce. attempting to use a did isdn pri through the trunk access code will just send you to a reorder tone; the system seems to just grab a trunk and then not actually wait to collect some digits from the user to send over it as a called party number.
display dialplan
                               DIAL PLAN RECORD

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


here are the ARS analysis rules. these are exactly the same as i discussed above. basically the user dials 9 to get in to ARS then anything they dial from 1 to 28 (the maximum allowed) digits gets sent out over the pri with call type local (this is an isdn call type code). this is about as facile as ARS can get. i only have one trunk so i would have preferred to just use a raw trunk access code as on the meridian but since i couldnt do that i just set up ARS as simply as possible to basically emulate how a raw access code would behave (when there is only one trunk to a route).
list ars analysis

                           ARS DIGIT ANALYSIS REPORT

                            Location:  all

               Dialed            Total        Route    Call      Node
               String          Min    Max    Pattern   Type     Number

         0                      1      28     1        locl
         1                      1      28     1        locl
         2                      1      28     1        locl
         3                      1      28     1        locl
         4                      1      28     1        locl
         5                      1      28     1        locl
         6                      1      28     1        locl
         7                      1      28     1        locl
         8                      1      28     1        locl
         9                      1      28     1        locl



Command successfully completed
Command:
here is the route-pattern that we call from ARS. again it is about as simple as can be. there is only a single entry, route-pattern 1, which contains a single trunk-group, 1, which is the pri. everything besides the trunk-group number (which i specified) is set to defaults.
list route-pattern

                                ROUTE PATTERNS
 Route Pref Trk FRL Hop IXC      BCC      TSC   CA-TSC   ITC   Service/Feature
 Pat        Grp     Lmt      0 1 2 3 4 W        Request
  1     1   1    0      user y y y y y n   n   none      rest
















Command successfully completed

here are the isdn public-unknown-numbering options, basically this determines how many digits get sent for the calling party CLID over the pri. basically it says that extensions of 4 digits in length that either start with 3 or 4 get a 4 digit CLID sent over the trunk (e.g. 3000, 3001, 4000, etc).
display isdn public-unknown-numbering                           Page   1 of   8
                    ISDN NUMBERING - PUBLIC/UNKNOWN FORMAT

Ext Ext   Trk     CPN         Total CPN  Ext Ext   Trk     CPN         Total CPN
Len Code  Grp(s)  Prefix          Len    Len Code  Grp(s)  Prefix          Len

 4  3                             4
 4  4                             4
















just for your reference, here are the customer options on my switch that pertain to isdn. note you need to have ISDN-PRI enabled on your switch for this to work. you cant change these settings as an ordinary user; that is something only the init user can do.
display system-parameters customer-options                      Page   3 of   8
                                OPTIONAL FEATURES

   Emergency Access to Attendant? y                          ISDN-BRI Trunks? y
                  Enhanced EC500? n                                 ISDN-PRI? y
          Extended Cvg/Fwd Admin? n                     Malicious Call Trace? y
     External Device Alarm Admin? n     Mode Code for Centralized Voice Mail? n
                Flexible Billing? n
   Forced Entry of Account Codes? n                 Multifrequency Signaling? y
      Global Call Classification? n Multimedia Appl. Server Interface (MASI)? n
             Hospitality (Basic)? y         Multimedia Call Handling (Basic)? n
 Hospitality (G3V3 Enhancements)? n      Multimedia Call Handling (Enhanced)? n
                    H.323 Trunks? n                       Multiple Locations? n
                                               Personal Station Access (PSA)? n
                     IP Stations? n
               ISDN Feature Plus? n
   ISDN Network Call Redirection? n




        (NOTE: You must logoff & login to effect the permission changes.)


and finally here are the feature access codes, note that we specify 9 as access code 1 to ARS.
display feature-access-codes                                    Page   1 of   4
                               FEATURE ACCESS CODE (FAC)
         Abbreviated Dialing List1 Access Code: #7
         Abbreviated Dialing List2 Access Code: #8
         Abbreviated Dialing List3 Access Code: #9
Abbreviated Dial - Prgm Group List Access Code:
                      Announcement Access Code: 820
                       Answer Back Access Code: #6
      Auto Alternate Routing (AAR) Access Code:
    Auto Route Selection (ARS) - Access Code 1: 9     Access Code 2:
                 Automatic Callback Activation: *5     Deactivation: #5
Call Forwarding Activation Busy/DA:        All: *2     Deactivation: #2
                         Call Park Access Code: *6
                       Call Pickup Access Code: *7
CAS Remote Hold/Answer Hold-Unhold Access Code: 823
                  CDR Account Code Access Code:
                        Change COR Access Code:
                   Change Coverage Access Code:

                  Data Origination Access Code:
                      Data Privacy Access Code: 835
              Directed Call Pickup Access Code: #1


one final miscellaneous avaya side configuration note: you may find that you have to raise the class of restriction (COR) on any phones that you want to use this link. the default COR is something like 0 or 1 and there are commonly 7 levels of COR, with the seventh having the most privilege. i usually just give all of my phones a COR of 7 to make things easy.
now that we are finished configuring the avaya, here is the all of the configuration on the cisco side of things that pertains to the pri trunk.
!
!
network-clock base-rate 64k
network-clock-select 1 T1 1
!
isdn switch-type primary-qsig
isdn gateway-max-interworking
!
!
voice service voip
 sip
  session transport tcp
!
!
no voice confirmation-tone
!
!
controller T1 0
 shutdown
 framing esf
 linecode b8zs
!
controller T1 1
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
 description t1 link to definity
!
translation-rule 1
 Rule 0 ^90 0
 Rule 1 ^91 1
 Rule 2 ^92 2
 Rule 3 ^93 3
 Rule 4 ^94 4
 Rule 5 ^95 5
 Rule 6 ^96 6
 Rule 7 ^97 7
 Rule 8 ^98 8
 Rule 9 ^99 9
!
!
! it is unclear where to set the timers on the avaya so we take these timers
! from avaya documentation as something approximating reality. also note that
! we are not emulating the network side with this config.
!
interface Serial1:23
 no ip address
 logging event nfas-status
 logging event subif-link-status
 isdn switch-type primary-ni
 isdn incoming-voice voice
 isdn T309-enable
 isdn T306 30000
 isdn T310 40000
 isdn send-alerting
 no cdp enable
!
!
! set bearer capacity to match that which is defined in the ds1 record
! on the avaya
!
voice-port 1:23
 bearer-cap Speech
!
! avaya digital sets on direct inward dial
!
dial-peer voice 3000 pots
 destination-pattern 3...
 supplementary-service pass-through
 direct-inward-dial
 port 1:23
 forward-digits 4
!
! avaya analog sets on direct inward dial
!
dial-peer voice 4000 pots
 destination-pattern 4...
 supplementary-service pass-through
 direct-inward-dial
 port 1:23
 forward-digits 4
!
end
home