As you say below is a good thought but the memory allocation is currently set at 1,26,0,01. The only part that concerns me a bit is the last digits where as most of our 16 button display phones are set to 02. This I understand sets another block of 10 for 20 total locations, is that correct?
Many of our phone start with a 0 rather than a 1 in the first position, would that make a difference? I interpret the first position as just a new block of memory once the zero block is full (0-99). If I have a memory location of 0,46,0,02, the next open area would be 0,48,0,02? I assume I need to bump up the 46 by 2 because of the 02 on the end. Is this correct?
Also since the message button which is button 99 is set to F1118 which is a fixed memory location somewhere else, the only thing I can conclude is that I'm out of memory locations. I don't understand how Matworx could copy the buttons from one phone to another if there weren't enough memory locations. Any other ideas?
Quote:
| Originally Posted by R4+Z There is obviously a problem with the memory allocation. If the fourth digit of the memory allocation is a 1 then the user is not allowed to change it so you won't be able to store numbers from the phone. Rewrite it with a 0 as the 4th digit. You need to use MOC mode to look at the hunt group problem. It may be that one of the numbers you are trying to use is already part of a hunt group but without looking in the system you won't be able to see what the problem is. |