P_Dam TelCom
IS-IT--Management
thread940-1756204
I am having what appears to be a similar problem, but removing and re-programming the extension(s) does not fix the issue. In my case, pressing the Message Button on the 1608 or 1616 sets results in a single beep, but if I dial the Voice Mail (not Visual Voice, whatever that is) Hunt Group number I gain access as expected.
Running CM-6.0.07
Here are some rather basic questions I don't know the answer(s) to and other perhaps pertinent observations:
What is the 46xxsettings.txt file, where do I find it, and as an Admin is it normal to make adjustments in it?
The issue occurs whether using the handset or the speaker phone.
Seems to start on any given extension after either a power outage or some other restart of the phone (physical move, office re-arrangement, etc).
We upgraded/changed our Voice Mail system in early 2018 and this issue has only recently started to show up, so I don't think the problem is related to VM.
Voice Mail programming on any of the affected sets had not changed immediately prior to the problem arising, to the best of my knowledge.
Any assistance will be greatly appreciated, and please advise what if any further information I need to provide to help you help me!
Cheers,
Terry
I am having what appears to be a similar problem, but removing and re-programming the extension(s) does not fix the issue. In my case, pressing the Message Button on the 1608 or 1616 sets results in a single beep, but if I dial the Voice Mail (not Visual Voice, whatever that is) Hunt Group number I gain access as expected.
Running CM-6.0.07
Here are some rather basic questions I don't know the answer(s) to and other perhaps pertinent observations:
What is the 46xxsettings.txt file, where do I find it, and as an Admin is it normal to make adjustments in it?
The issue occurs whether using the handset or the speaker phone.
Seems to start on any given extension after either a power outage or some other restart of the phone (physical move, office re-arrangement, etc).
We upgraded/changed our Voice Mail system in early 2018 and this issue has only recently started to show up, so I don't think the problem is related to VM.
Voice Mail programming on any of the affected sets had not changed immediately prior to the problem arising, to the best of my knowledge.
Any assistance will be greatly appreciated, and please advise what if any further information I need to provide to help you help me!
Cheers,
Terry