I am working on a Magix system that is currently all analog trunks. They're going with a PRI from XO so my question is, once the DS100 is installed and configured what is the next step? I know enough to expect to lose all line appearance buttons. I know to create line pool access buttons and call park buttons. But what is the immediate next step after installing the PRI so it can handle calls? Does the Magix work like the Nortel and have a default line group? What do I change in VM to answer the incoming calls? Currently you add lines as members to the cover group but how does that work when you have no lines? I am reading the manual but I always like to ask questions.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Adding a PRI to a Magix
- Thread starter pmcook
- Start date
Since you did not mention which documents you are reading, we can only guess where you are in planning the programming and cut over. The Numbering Plan and DID numbers are very important in this process. Are you getting a new main number or reusing the old ones? Have you checked the Tek-Tips FAQs? Another helpful Avaya document is the System Planning document for the Magix that can be downloaded for free from support.avaya.com. The Magix has some defaults, but they are NOT the same as Nortel Norstar. These types of conversions have been covered many times on this forum. Search for PRI subject matter and you should find lots of info pertaining to what you are doing. Remember that the ONLY PRI protocol supported by the Legend/Magix is AT&T CUSTOM! Make sure XO knows the proper parameters and configures it with them! All that info is covered in the System Planning document.
If you get stuck... post away!
....JIM....
If you get stuck... post away!
....JIM....
- Thread starter
- #3
Good thing I asked. I found the planning document but from what I can see it just lists the defaults for the settings and those are for a T1. Is there a different document with the specific PRI setting I need to supply to XO?
So I assume then that I will use DIDs to send calls the the VM cover group?
So I assume then that I will use DIDs to send calls the the VM cover group?
- Thread starter
- #4
OK so they are getting 40 new DIDs and porting their 12 existing numbers. Correct me if I have this wrong, I just asked XO to change the switch type to AT&T Custom 5ESS. Is that all there is? Should the L1 flag be set? XO will have the DIDs live so I can do all the config prior to cutover. That's a load off.
As you know, PRI has no ringing lines. Therefore, everything you do has to be done using D-I-D numbers.
Where as before you may have had the AA answering the LINES that also appeared on the Main Console, now you will need to make the MAIN CONSOLE Extension Number an Auto Attendant.
Sometimes the PRI routes calls just fine with no special routing programming, (The Provider is sending just enough, and the correct Digits to match your numbering plan)
But other times, considering they are sending too many digits or a different set, you have to massage the INCOMING part of the ROUTE BY DIAL PLAN area (Tables 0 thru 15) to accommodate what they are doing.
-merlinmansblog.blogspot.com
Where as before you may have had the AA answering the LINES that also appeared on the Main Console, now you will need to make the MAIN CONSOLE Extension Number an Auto Attendant.
Sometimes the PRI routes calls just fine with no special routing programming, (The Provider is sending just enough, and the correct Digits to match your numbering plan)
But other times, considering they are sending too many digits or a different set, you have to massage the INCOMING part of the ROUTE BY DIAL PLAN area (Tables 0 thru 15) to accommodate what they are doing.
-merlinmansblog.blogspot.com
- Thread starter
- #6
I think I can handle the second part but the AA has me concerned at this point. Scenario: they have 2 AAs currently. One answers the first 7 lines the second answers line 8. The first 7 lines ring on 4 phones with the AA on delayed answer for day immediate for night. One of the phones is main console extension 100. They currently are not using any hunt groups. It's a doctor's office with the usual setup. So I am not sure how to make an extension an AA and duplicate the functionality.
TouchToneTommy
Vendor
Let's say the main number is 555-1234, and XO is sending 3 digits.
Renumber your 100 console to 234, and the calls will ring there. Put primary coverage -234 buttons on the other phones that need to answer the incoming calls. Keep 234 in the voicemail coverage group, and when you create it's mailbox, point it to the auto attendant. (You do this through class of service, or by pressing 3 instead of 1 when creating it)
Now calls not answered after a delay are answered by the AA.
At night, 234 and ALL the phones with coverage need to press DND to have the AA pick up immediately.
Renumber your 100 console to 234, and the calls will ring there. Put primary coverage -234 buttons on the other phones that need to answer the incoming calls. Keep 234 in the voicemail coverage group, and when you create it's mailbox, point it to the auto attendant. (You do this through class of service, or by pressing 3 instead of 1 when creating it)
Now calls not answered after a delay are answered by the AA.
At night, 234 and ALL the phones with coverage need to press DND to have the AA pick up immediately.
- Thread starter
- #8
Thanks, Tommy that makes sense. Some more questions:
1) I am not sure XO can send 3 digits, only 4 - will confirm tomorrow
2) I am not sure where you specify which AA is to pick up. I have a second AA on TN XXX-5964. Can I renumber the operator extension for that number, currently 115 to 964 or should I peel off a lower number DID and have it forwarded to 964?
3) So all 4 phones will ned to be on DND??? Is that the only way? That sons kind of odd. They currently have the scheduler setup for 5:40pm to route calls to a non-existant extension which overflows to the AA.
Seems like the Magix goes through huge changes under a PRI.
1) I am not sure XO can send 3 digits, only 4 - will confirm tomorrow
2) I am not sure where you specify which AA is to pick up. I have a second AA on TN XXX-5964. Can I renumber the operator extension for that number, currently 115 to 964 or should I peel off a lower number DID and have it forwarded to 964?
3) So all 4 phones will ned to be on DND??? Is that the only way? That sons kind of odd. They currently have the scheduler setup for 5:40pm to route calls to a non-existant extension which overflows to the AA.
Seems like the Magix goes through huge changes under a PRI.
TouchToneTommy
Vendor
1) 4 digits is fine, but you will need to use the routing tables to manipulate it to match your extensions. For instance, if your DID range is 1200 through 1239, and you want to match that to extensions 100 through 139, you would strip off the first 2 digits and add a 1. So 1200 becomes 100, 1201 becomes 101, etc.
You can also receive totally oddball digits, strip all 4, and replace with 3 digits to hit an extension. So those 12 existing numbers may need 12 routing table entries to take care of.
For XXX-5964, you CAN'T renumber 115 to 964, because the 9 conflicts with 9 for ARS. So if you receive 5964, absorb 4 digits, add 115, it ends up ringing Ext. 115.
2) What kind of voicemail do you have. Merlin Messaging, you go to 2 for mailboxes, dial the extension number, then it's 1 to assign a mailbox, 2 for Transfer Only permission, and 3 to assign to an auto attendant. Next you press 1, 2, 3, or 4 to select which AA will answer.
Merlin Mail, you assign Class Of Service 15 for AA1, COS 16 for AA2, COS 3 for AA4
Audix, you create the subscriber as an auto attendant
3) An extension must exhaust all Primary and Secondary coverage paths before the Group Coverage path will take effect. So if 115 goes into DND, all of the extensions with Primary Coverage will still ring. Once they finish ringing for the coverage, it will cover to voice mail. You'd have to ask an AT&T engineer why they designed it that way.
Remember that it's all NUMBER BASED, not line based. You can use the Night Service button to switch the greeting from Day to Night, but not to direct the calls to the AA. That will only happen when a call to an extension covers to VM and the mailbox is pointed to the AA.
You can also receive totally oddball digits, strip all 4, and replace with 3 digits to hit an extension. So those 12 existing numbers may need 12 routing table entries to take care of.
For XXX-5964, you CAN'T renumber 115 to 964, because the 9 conflicts with 9 for ARS. So if you receive 5964, absorb 4 digits, add 115, it ends up ringing Ext. 115.
2) What kind of voicemail do you have. Merlin Messaging, you go to 2 for mailboxes, dial the extension number, then it's 1 to assign a mailbox, 2 for Transfer Only permission, and 3 to assign to an auto attendant. Next you press 1, 2, 3, or 4 to select which AA will answer.
Merlin Mail, you assign Class Of Service 15 for AA1, COS 16 for AA2, COS 3 for AA4
Audix, you create the subscriber as an auto attendant
3) An extension must exhaust all Primary and Secondary coverage paths before the Group Coverage path will take effect. So if 115 goes into DND, all of the extensions with Primary Coverage will still ring. Once they finish ringing for the coverage, it will cover to voice mail. You'd have to ask an AT&T engineer why they designed it that way.
Remember that it's all NUMBER BASED, not line based. You can use the Night Service button to switch the greeting from Day to Night, but not to direct the calls to the AA. That will only happen when a call to an extension covers to VM and the mailbox is pointed to the AA.
- Thread starter
- #10
My my. I sure wish I could sell them an IP Office. I can do all this with an IPO and not work up a sweat. Everything you say makes sense now except for #3 which makes no sense and I don't know any AT&T engineers. I see I will need to make a DID route for all 12 ported numbers. We may yet do that support session. I have some money in the budget for this. I am feeling a bit over my head at the moment.
- Thread starter
- #12
There are some things that relate to night service and delayed answer but not specifically DID and auto attendant - you are correct. Do a search for DID within this forum and there is a lot of good stuff. I learned more about Magix from this site than I ever did from the sources Avaya had.
- Status
Similar threads
- Locked
- Question
- Locked
- Question