I just installed a new Norstar MICS 6.1, with 25 stations. It was a new install, with all the ports set at default- p101=DN 221, p102=DN 222,...etc. I created the voicemail boxes (CP150) to be the same number as the DN. Just after the install, another tech changed several ports to different DNs, to avoid any x-connect work,. Now there is p126 to DN 240, p128 to DN 237, and several others.I have had to correct a voicemail issue already, and I am wondering if there are any other possible problems or confusion this might cause in the future.
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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Changing Port Numbers for DNs
- Thread starter jjimm
- Start date
jjimm,
The port number should have no impact on the relationship between the DN and its mailbox. As "sphoneman" said, the only thing you have to be concerned with is your records keeping. I am curious as to what voicemail issues you had as a result of this.
The port number should have no impact on the relationship between the DN and its mailbox. As "sphoneman" said, the only thing you have to be concerned with is your records keeping. I am curious as to what voicemail issues you had as a result of this.
- Thread starter
- #4
I am old school, and whenever I do a new install, I like to keep things clean and straight, with good record keeping. I would like to change the ports back,and move the x-connects, but I need to research the ramifications beforehand.
One person who was supposed to move her extension 226 to a new location is still using a phone set up for extension 240, a guest phone. The numbers and features are the same, but she had no voicemail. The other tech tried to accommodate the customer with a fast fix, and built another mailbox on 240, which had none. The system refuses to accept her name on mbx 240, which is on 226. Sure, we could change the name on the mbx, but that would end up with her having two mailboxes. I am going to change delete the mbx 240 (after checking for messages), and give her the correct phone extension 226 and mbx 226, which is her extension in the company icm list, and to avoid problems in the company directory.
These "shortcuts" are making more work.
One person who was supposed to move her extension 226 to a new location is still using a phone set up for extension 240, a guest phone. The numbers and features are the same, but she had no voicemail. The other tech tried to accommodate the customer with a fast fix, and built another mailbox on 240, which had none. The system refuses to accept her name on mbx 240, which is on 226. Sure, we could change the name on the mbx, but that would end up with her having two mailboxes. I am going to change delete the mbx 240 (after checking for messages), and give her the correct phone extension 226 and mbx 226, which is her extension in the company icm list, and to avoid problems in the company directory.
These "shortcuts" are making more work.
Set relocation should not affect voice mail. if port 101 is 221 and you move the set to port 102 with set relocation on port 102 becomes ext 221 and all programming should follow. When a set CF's to voice mail it is the DN information that is transmitted to the voice mail not the port number. I have seen issues of set relocation getting confused when too many sets are move at once. I prefer to leave set relocation off but if set relocation is insisted upon by your client make sure they do them one at a time to avoid confusing the system.
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
