lu_tzer

Hi,

First: Definity G3siV11

Background: I am a PC technician at a midsized company who has inherited the responsibility of administering our PBX wiht no training. I've take available online courses from AvayaU. Still trying to convince my director to send me to classroom training for Definity. As such, I'm having troulbe to put it mildly.

Acquired 20 new DID's that I would like to map to 4 digit extensions. The new DID's are of the form AAA-CCC-02XX. Existing DID's (?) are AAA-BBB-50XX thru AAA-BBB-51XX and correspond to internal extensions of 5000-5199. I would like to just have the new DID's point to internal extensions 5200-5219. Can someone advise me on how to accomplish this or point me in the direction of some helpful documentation?

Thanks,

Lu

ahays

Is trunking for these new DIDs via ISDN-PRI?

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

lu_tzer

I'm not even sure how to find out.

All I know is that a request was made to provision the new DID's and they are now active. Currently, if I call one of the new DID's the call ends up at reception.

Thanks for the quick response though.

ahays

That's somewhat of a problem. What do you get when you issue the command "list trunk" ?

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

lu_tzer

Here is the output for list trunk command.


"No.","TAC","Type","Name","Members","TN","COR","CD R","Meas","Out Disp","Que Len"
"1","801","isdn","MARKET SOURCE","19","1","1","y","int","n","0"
"2","802","isdn","MARKET SOURCE","18","1","1","y","none","n","0"
"4","803","isdn","MCI Outbound","23","1","1","y","none","n","0"
"11","811","isdn","MARKET SOURCE","2","1","1","y","int","n","0"
"12","812","isdn","MARKET SOURCE","2","1","1","y","none","n","0"
"21","821","isdn","MARKET SOURCE","2","1","1","y","int","n","0"
"22","822","isdn","MARKET SOURCE","3","1","1","y","none","n","0"

ahays

Ok ... it looks like ISDN PRI. Now let's identify which trunk group that the calls are coming in on. I want your to issue the command "list trace tac XXX" where XXX is the TAC (801, 802, etc.) and then call one of the new DID's using a phone that you can identify the callerID on. You may have to do this on EACH trunk group until you can identify the one that the calls are coming in on. Once you see your call coming in, then I want your to do a "status trunk X" where "X" is the trunk group number. Here you'll be looking for the board location of the members ... i.e. the first 5 digits of any given member like 01C12. Finally, I want you to do a "list config board PPCSS" where PPCSS is the board number and tell me what kind of board it is (TN464, etc.)

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

ahays

Also, what are the new DID's? 0200 - 0219? I need to know specifically to guide you in the next step.

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

lu_tzer

I did the trace this morning and found the board location to be 01A15.

That card is a DS1 Interface TN67E Vintage 000018.

Also the DID's are 0207-0226. I would like to end up with them being mapped to extensions 5207-5226.

Thanks again for your help. I look forward to learning more.

redder

There are two ways to handle the problem one is to do a delay of the digit treatment for 0 and allow the first digit to remain 0xxx, problem is the delay time for calls to the receptionist. The other way is to change the first digit 0 to another extension range of numbers as shown.
This is page 3 of the trunk group form for the trunk group you are assigning the trunks to.
Additionally remember to change the dial plan for the digit you insert as the replacement for 0 (We just happen to use the digit 1)
INCOMING CALL HANDLING TREATMENT
Service/ Called Called Del Insert Per Call Night
Feature Len Number CPN/BN Serv
other 4 0 1 1 cpn-pref

end result 0111 will become 1111. The internal number is 1111 the outside dialed number will remain 0111.

Hope this helps.

__________________
I would rather be lucky than wrong all the time.

lu_tzer

I will give this a try today if time permits....

I'll be back in touch with the results...

Thanks y'all!

Lu

lu_tzer

I changed the INCOMING CALL HANDLING TREATMENT for the identified trunk group as shown below, but it didn't seem to have any effect. Calls made to the new DID still route directly to the receptionist.

INCOMING CALL HANDLING TREATMENT
Service/Feature Called Len Called Number Del Insert Per Call CPN/BN Night Serv
other 4 0 1 5 cpn-pref


did I do this incorrectly? Maybe something doesn't translate properly into the message board format and I entered something in the wrong field?

Thanks,

Lu/Matthew

UPDATE,

After the above APPEARED not to have any effect I went back to the "list trace tac XXX" command and found that the calls did not appear to come in consistently on the same trunk-group (????) I then adjusted the INCOMING CALL HANDLING TREATMENT as above for all trunk-groups and everything seems to be working fine. Go figure! Anything I should be on the lookout for that I may have broken during the process?

Thanks again, Al and redder! :tdn: :clap2: :beer:

redder

Can you call the 52XX extension internally as a 4 digit extension?

The translations you mae were on the trunk group for the inbound traffic only (DID trunk group)?

__________________
I would rather be lucky than wrong all the time.

lu_tzer

Everything is working fine, so far!

I had adjusted the dial plan before I ran into the inbound calling issue.