|
|
Joined: Sep 2006
Posts: 16
Member
|
Member
Joined: Sep 2006
Posts: 16 |
Here's an interesting problem I have asked everyone I know and can't find an answer. The customer has a 3300 with an auto attendant; all was working well, then we moved them to a new location with a new service provider. Now, when the call connects, as viewed on my cell, there is a 3.5-4.0 second delay before the greeting starts to speak. I have edited all delay out of the greeting and asked the provider to check for anything that may be causing the delay and they say that there isn't anything in the programming that is causing it. Has anyone else seen and corrected this issue? Thanks in advance.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Mar 2005
Posts: 35
Member
|
Member
Joined: Mar 2005
Posts: 35 |
Is it a DID trunk? If so, perhaps the system is waiting for additional digits? Check the inter-digit timers in the trunk COS, and the digits absorbed in the Trunk Service Assignment, perhaps you need to make some adjustments.
|
|
|
|
Joined: Oct 2004
Posts: 1,057
Member
|
Member
Joined: Oct 2004
Posts: 1,057 |
If you call the auto-attendant from an internal extension, that does not have a mailbox, you should be answered by the main greeting. Does it sound right??
|
|
|
|
Joined: Sep 2006
Posts: 16
Member
|
Member
Joined: Sep 2006
Posts: 16 |
Thanks for the replies. It is not a did trunk and I have played with just about every timer I can think of. I did dial the vm from and internal phone and the instructions are timed normally, but the AA greeting is still delayed the same. also it doesn't matter whether it is the day or nite greeting, they are both delayed the same. I also tried to re-record the greetiing via the admin mailbox and it is still delayed.
I am ??? Thanks again for any help.
|
|
|
|
Joined: Mar 2005
Posts: 35
Member
|
Member
Joined: Mar 2005
Posts: 35 |
Have you checked the VM hunt group and port programming? Are there inactive ports in the hunt group? Are you using the same number of ports you are licensed for? If you have the same issue on incoming trunk and internal calls, then I'd make sure the VM hunt group and ports are all working properly.
|
|
|
|
Joined: Sep 2006
Posts: 16
Member
|
Member
Joined: Sep 2006
Posts: 16 |
I checked each directory number in the hunt group individually and they all have the same delay from an external number. All of the ports are assigned and all seem to be working. Unfortunately, I did not have access to the site to test all of the group numbers internally.
|
|
|
Forums84
Topics94,512
Posts639,931
Members49,844
|
Most Online5,661 May 23rd, 2018
|
|
|
|
|