I have a Legend 7.0 that will not let me renumber the LDN. When I go to that field in sys renumbering, it shows 800 as the LDN. When I click enter , I believe I should get a prompt to enter a new number, and I don't. I have tried back spacing the number out and entering a new one but to no avail. I was succesful in doing this on a 4.0 Magix, but it doesn't seem to work here, although the 'book' says it should work. Any help would be appreciated.(we are changing this to accomodate a new UDP going into place.) Thanks!
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!
LDN Renumbering
- Thread starter commpath
- Start date
- Thread starter
- #3
The LDN is associated with a QCC Type console only.
Of course I STRONGLY recommend AGAINST using QCC's EVER!
Exactly what are you trying to accomplish?
Of course I STRONGLY recommend AGAINST using QCC's EVER!
Exactly what are you trying to accomplish?
- Thread starter
- #5
Our PRI provider has configured their switch to allow our customer to make "on net" calls between 4 locations (all PRI T-1's) . At site 1 which is a 4.0 Magix we have taken the last four channels from the PRI and assigned them to their own pool. Calls to the PSTN dial 9 and "on net" calls dial 8 and then the four digit extension number of the party they want to reach. I was able to accomplish this by renumbering everything with an 8 including the LDN. This site works fine. Trying to accomplish the same thing at site 2 (Legend 7.0), I was able to renumber everything that started with 8 succesfully with the exception of the LDN.I am trying to maintain continuity within the sites as they have employees who move around from location to location. I really have no need for a QCC console I was wondering if a reset would help. Thanks for taking the time to get back to me.
The LDN feature is not available unless you are using the QCC operators on the Legend & Magix! Now, you have not mentioned what configuration the MAGIX 4.0 has. So you might want to reveal that. Maybe at one time the Magix had a QCC, and some of the config is still there? But does it do anything? You might be able to set up the QCC queue to overflo to a backup, but I don't have one to try it. As a possible alternative, assign the DID number to the DLC station and see if that works for you.
....JIM....
....JIM....
- Thread starter
- #7
TouchToneTommy
Vendor
Yes, even if you are not using a QCC, you should be able to renumber the LDN to something else, so that you can free up 8 to be used elsewhere.
Don't know why it won't let you renumber it, though!!
Don't know why it won't let you renumber it, though!!
OK, I stand corrected, it can be done in a non-QCC Environment.
So, I suspect the reason you are unable to do this re-numbering is probably as simple as a CONFLICT in your DIAL PLAN with the number you are trying to change it to.
So that's what I would look for.
So, I suspect the reason you are unable to do this re-numbering is probably as simple as a CONFLICT in your DIAL PLAN with the number you are trying to change it to.
So that's what I would look for.
- Thread starter
- #11
Thanks for getting back to me. I have no conflicts in my dial plan, and can not find anything under group calling. I suspect I am dealing with some corruption somewhere, that is the only thing I can figure it to be. Just so I am not crazy and second guessing myself, I went back to the 4.0 and was able to change the LDN. In the 7.0, I get to the point where I see enter old directory number and 800 is displayed. At this point I should be able to hit enter and enter new directory number should display and allow me to renumber. That does not happen, the field never changes. FYI a restart didn't help either. I guess I am going to have to use another digit if I can't make "8" work.Thanks again for your help on this one.
Of course, my test involved an R4 Magix as well.
AND - it's too darn cold to go out to my garage/lab and find an R7 to mess with.
But it does make me wonder if maybe the is a difference in the 2 designs.
AND - it's too darn cold to go out to my garage/lab and find an R7 to mess with.
But it does make me wonder if maybe the is a difference in the 2 designs.
TouchToneTommy
Vendor
Just logged into my office computer, where I have WinSPM set up for my remote sites.
Legend 4.1, Legend 7.0, Magix 3.0
All the same procedure
System Renumber, Single, More, ListDirNumber, the current number is shown, Enter, type in the new number, Enter.
Changed 800 to 600 and back again on all of them.
Something else is hanging you up. Have you started building your UDP tables already?
Legend 4.1, Legend 7.0, Magix 3.0
All the same procedure
System Renumber, Single, More, ListDirNumber, the current number is shown, Enter, type in the new number, Enter.
Changed 800 to 600 and back again on all of them.
Something else is hanging you up. Have you started building your UDP tables already?
- Thread starter
- #14
I did build my UDP ranges 2100-2199,3100-3199 and 5000-6199. I guess I will undo the UDP and then try. I too trudged through the snow and cold and was able to find a Legend 4.1 which also allowed me to renumber it. Going on-site today with another tech and maybe two heads will prevail on this one, otherwise it's another digit beside "8" for them. Thanks!
- Thread starter
- #17
I was succesfully able to renumber the remote access extension.Funny thing is when I did a ext print for 800, it showed that extension to be a member in 5 different service observing groups. When I go to the S.O. field in programming and go anyone of those groups, it shows no members assigned. Also the pickup groups and ars restriction level read 255 in the printout.Something is corrupt here as far as I can tell. I was succesfully able to renumber the Pool to "6", that will have to work for the customer, short of us replacing the processor. I hate to throw in the towel but I am not sure what to look at next. Thank you everyone for your help on this, I really appreciate your time and efforts.
You could try making a backup of the configuration, then completely default the processor. Reboot the switch and try to change the LDN. This might be a way to test the processor and clear the corruption. If successful, then restore the backup config copy to the processor, and try changing the LDN again.
This may be one way to fix it.
....JIM....
This may be one way to fix it.
....JIM....
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question