AlquestTech
Technical User
I could not find a thread about this, if there was one I apologize.
One of my techs is having a problem on a MICS where he has changed the DN of a port but the NAM seems not to be aware of it.
I'll make up two numbers for ease of explanation, as follows:
He changed extension 4177 to extension 2132 and 2132 to extension 4177.
The NAM allows him to build a mailbox for extension 2132, but every time he tries to build one for 4177, he gets as far as COS and then it says "mailbox cannot be created" and kicks him out of admin.
To complicate matters, every time he tries to call through the Auto Attendant, if he dial 4177 it transfers him to station 2132, (the old port for 4177).
He even tried changing 4177 to ext. 5177 yet when he dials 4177 in the Auto Attendant, it still transfers him to 2132.
Anyone know how I can fix this?
I have run into this problem before but and have worked around it by using totally new/different ports and numbers.
Unfortunately, that is not an option this time.
Would restarting the NAM clear this problem?
Does anyone know what causes this problem so we can avoid it in the future?
Thanks for any help.
One of my techs is having a problem on a MICS where he has changed the DN of a port but the NAM seems not to be aware of it.
I'll make up two numbers for ease of explanation, as follows:
He changed extension 4177 to extension 2132 and 2132 to extension 4177.
The NAM allows him to build a mailbox for extension 2132, but every time he tries to build one for 4177, he gets as far as COS and then it says "mailbox cannot be created" and kicks him out of admin.
To complicate matters, every time he tries to call through the Auto Attendant, if he dial 4177 it transfers him to station 2132, (the old port for 4177).
He even tried changing 4177 to ext. 5177 yet when he dials 4177 in the Auto Attendant, it still transfers him to 2132.
Anyone know how I can fix this?
I have run into this problem before but and have worked around it by using totally new/different ports and numbers.
Unfortunately, that is not an option this time.
Would restarting the NAM clear this problem?
Does anyone know what causes this problem so we can avoid it in the future?
Thanks for any help.