Can anyone point me in the best direction to connect a Merlin Legend and Merlin Magix together. Both are currently located in the same building. Also, as a separate question, what would be the best way to connect them if they were in different buildings? Thanks in advance for your comments and your help!
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!
Best way to connect Merlin Legend and Merlin Magix both in same bldg.. 2
- Thread starter newlajo
- Start date
-
1
- #2
Pretty much same answer for both scenarios.
Install a DS1 Module in each one and set up a Uniform Dial Plan (UDP) network between them.
From 1 building to another, you would need a PROTECTED UNDERGROUND Cable.
There are some IP Network solutions, but they are not as good as a LOCAL UDP setup, and the hardware to make them work is usually quite costly.
Install a DS1 Module in each one and set up a Uniform Dial Plan (UDP) network between them.
From 1 building to another, you would need a PROTECTED UNDERGROUND Cable.
There are some IP Network solutions, but they are not as good as a LOCAL UDP setup, and the hardware to make them work is usually quite costly.
- Thread starter
- #3
The 400EM modules only have 4 trunk circuits, they will work for your application, but the 100D DS1 modules give you more capacity and features. Check the Legend Network Reference document for most information on networking switches. You can download it and others for free from support.avaya.com.
....JIM....
....JIM....
-
1
- #5
dagwoodsystems
Programmer
Jim and Jack are both right. Post back when you're ready to do this and I assure you that you'll get 'er done the very first time. The factors are simply a matter of a T1 crossover cable between the blades, defining the timing source and a bit of programming on both switches...that's all. Piece of cake.
Tim Alberstein
Tim Alberstein
- Thread starter
- #6
- Thread starter
- #7
Okay, I guess it moves back up with the reply I had just posted, so here is an update on what I've done so far:
I read the Merlin Networking document as well as an Avaya training manual on networking.
Switch #1 (Magix r3) is renumbered to the 2000 range. Switch #2 (Legend r7) is renumbered to the 3000 range.
All lines on the DS1 modules have been added to a pool on each of the switches. Clock sync is set to loop.
Magix has Non-Local UDP set pattern #1: 3000-3999; Legend has non-local UDP set Pattern #2: 2000-2999.
Switch identifiers are set to 21 & 22 respectively; as right next to each other is far under the 200 mile range.
Here is where the problem comes in (I think): When I try to change the Tandem PRI Settings (Lines/Trunks-->PRI-->Switch Type-->Slot #-->{select type}: It will NOT allow me to select Legend-Netwk; it just beeps at me when I try it on the programming phone or winSPM...
Needless to say, I am not able to make calls between the two systems...
I read the Merlin Networking document as well as an Avaya training manual on networking.
Switch #1 (Magix r3) is renumbered to the 2000 range. Switch #2 (Legend r7) is renumbered to the 3000 range.
All lines on the DS1 modules have been added to a pool on each of the switches. Clock sync is set to loop.
Magix has Non-Local UDP set pattern #1: 3000-3999; Legend has non-local UDP set Pattern #2: 2000-2999.
Switch identifiers are set to 21 & 22 respectively; as right next to each other is far under the 200 mile range.
Here is where the problem comes in (I think): When I try to change the Tandem PRI Settings (Lines/Trunks-->PRI-->Switch Type-->Slot #-->{select type}: It will NOT allow me to select Legend-Netwk; it just beeps at me when I try it on the programming phone or winSPM...
Needless to say, I am not able to make calls between the two systems...
OK, it sounds as if you are somewhat ahead of your self here.
From what you have posted, it appears you built the POOLS before building the PRI.
Am I right?
-merlinmansblog.blogspot.com
From what you have posted, it appears you built the POOLS before building the PRI.
Am I right?
-merlinmansblog.blogspot.com
- Thread starter
- #9
Merlinman (and anyone else looking :-})
Today's Update:
In the doc I was reading, it completly skipped what I think you are referring to as "building the PRI" (sorry, this is the first time I am doing anything like this). I found another doc that had other steps in it, and it would seem I am almost there now...
I followed the guide that was in the FAQ's section here titled Legend/Magix Initial PRI Setup. (Wish I had found that first...) A few things happened in the process of the setup. When I was going through the steps on the Magix (which I was doing first) I accidentally skipped STEP 4--Change Switch Type. I then changed it at the very end because I knew from my last attempt that was where I was getting stuck at... I then went on to do the same on the Legend, but followed Step 4 in it's correct order; and a strange thing happened: It would NOT accept any values for Step 5--PROGRAM B CHANNEL GROUP. The programming phone would just beep when I would press ENTER to try and move on to the next value. So, I went back to the MAGIX to inspect the B Channel Group--and all of the values I had entered were now gone... Is this step not needed when doing this the way I am with the cross over cable?
So, I go through the remaining steps, and attempt to call EXT-2000 (MAGIX) from EXT-3000 (LEGEND) from SA-RING--and the call goes through! But, the display showed OUTSIDE (trunk name); not the Ext # and Name (which is what I am looking for...)
I then go to try the reverse and call EXT-3000 (LEGEND) from EXT-2000 (MAGIX) from SA-RING--and I got fast busy... Just for kicks, I decided to try the same call from a line key on the PRI; and it went through; but also showed OUTSIDE (trunk name) not the EXT # and Name...
I am now going to review the UDP info and run some prints to review to hopefully see why the calls Magix to Legend are not going through without selecting one of the lines on the PRI.
I am a bit confused though as to why it would be showing the line/trunk label instead of the ext number and name...
Today's Update:
In the doc I was reading, it completly skipped what I think you are referring to as "building the PRI" (sorry, this is the first time I am doing anything like this). I found another doc that had other steps in it, and it would seem I am almost there now...
I followed the guide that was in the FAQ's section here titled Legend/Magix Initial PRI Setup. (Wish I had found that first...) A few things happened in the process of the setup. When I was going through the steps on the Magix (which I was doing first) I accidentally skipped STEP 4--Change Switch Type. I then changed it at the very end because I knew from my last attempt that was where I was getting stuck at... I then went on to do the same on the Legend, but followed Step 4 in it's correct order; and a strange thing happened: It would NOT accept any values for Step 5--PROGRAM B CHANNEL GROUP. The programming phone would just beep when I would press ENTER to try and move on to the next value. So, I went back to the MAGIX to inspect the B Channel Group--and all of the values I had entered were now gone... Is this step not needed when doing this the way I am with the cross over cable?
So, I go through the remaining steps, and attempt to call EXT-2000 (MAGIX) from EXT-3000 (LEGEND) from SA-RING--and the call goes through! But, the display showed OUTSIDE (trunk name); not the Ext # and Name (which is what I am looking for...)
I then go to try the reverse and call EXT-3000 (LEGEND) from EXT-2000 (MAGIX) from SA-RING--and I got fast busy... Just for kicks, I decided to try the same call from a line key on the PRI; and it went through; but also showed OUTSIDE (trunk name) not the EXT # and Name...
I am now going to review the UDP info and run some prints to review to hopefully see why the calls Magix to Legend are not going through without selecting one of the lines on the PRI.
I am a bit confused though as to why it would be showing the line/trunk label instead of the ext number and name...
- Thread starter
- #10
Update from very late last night:
I was able to solve the problems. There was an error in the patterns that quickly resolved the issue of not being able to use the SA key to make a call across network.
I have also (kind of) fixed the issue regarding the call information displayed; but it is displaying different information depending on what type of telephone is being used. Can anyone please tell me if this is just normal Merlin quirkiness or if I am missing something...
Magix MLX to Legend MLX: Name & Ext Display
Magix TDL to Legend MLX: Name & Ext Display
Magix (any) to Legend ATL: --no display information--
Legend MLX to Magix MLX: Name ONLY, NO EXT
Legend ATL to Magix TDL: Name ONLY, NO EXT
Legend (any) to Magix ETR: --no display information--
Legend ATL to Legend ATL: Name & SA Type (as usual)
Legend MLX to Legend MLX: Name & Ext Display
I have changed every extension on both systems for Display Pref of Name & Number, but it does not seem to be making a difference... But I am not sure if this is just NORMAL behavior or if I missed something...
Any comments or hints would be appreciated!
Thanks for your help and time!
I was able to solve the problems. There was an error in the patterns that quickly resolved the issue of not being able to use the SA key to make a call across network.
I have also (kind of) fixed the issue regarding the call information displayed; but it is displaying different information depending on what type of telephone is being used. Can anyone please tell me if this is just normal Merlin quirkiness or if I am missing something...
Magix MLX to Legend MLX: Name & Ext Display
Magix TDL to Legend MLX: Name & Ext Display
Magix (any) to Legend ATL: --no display information--
Legend MLX to Magix MLX: Name ONLY, NO EXT
Legend ATL to Magix TDL: Name ONLY, NO EXT
Legend (any) to Magix ETR: --no display information--
Legend ATL to Legend ATL: Name & SA Type (as usual)
Legend MLX to Legend MLX: Name & Ext Display
I have changed every extension on both systems for Display Pref of Name & Number, but it does not seem to be making a difference... But I am not sure if this is just NORMAL behavior or if I missed something...
Any comments or hints would be appreciated!
Thanks for your help and time!
dagwoodsystems
Programmer
ETR and ATL sets were designed for Partner and earlier Merlin machines and unfortunately won't get much more than date and time.
It must HAVE been a late night for you! You described Legend MLX to Magix MLX display behavior twice--each with different results.
I don't recall whether the extension information is carried across the network or not, but I'm sure that at the very least you'll get the name. I'll call one of my networked clients and ask them that detail if it comes to it.
Tim Alberstein
It must HAVE been a late night for you! You described Legend MLX to Magix MLX display behavior twice--each with different results.
I don't recall whether the extension information is carried across the network or not, but I'm sure that at the very least you'll get the name. I'll call one of my networked clients and ask them that detail if it comes to it.
Tim Alberstein
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question