Internal Extension Calling Issues

Status
Not open for further replies.

OSCS

Forum User
Joined
Jun 30, 2020
Messages
5
Reaction score
0
Calls made internal extensions ring 3 times then drop, stating Call failed.

Phones are not set to "Do not disturb".
3CX server has been restarted
 
Look at the forwarding rules for the extension, also check the status of the phone which we help you in checking the correct forwarding rule.

To check status - Select the ext under Extension and click on 'Status' icon along the top

Does it affect all internal extensions, or just to one certain extension ?

Please provide more info on your setup - https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Does the echo test work *777
 
Last edited:
Hi Saqqara
This particular problem affects all extensions, however I have discovered that there are 6 extensions that are set to Do Not Disturb, so I understand that calling through to those extensions the calls may be cut or disregarded
I have now just changed their external calls to be forwarded back to the switchboard, as they do not have the voicemail function enabled.
 
What type of calls? ext to int? int to ext? int to int? Direct to ext, ring group or queues?
 
Have you looked at your logs at all for any possible causes?

Has this worked before and then started?

Try to make brand new extension, leave all its settings default, and log it on to the webclient.

call that extension from another extension and see if the problem still occurs
 
  • 3CX Version: 16.0.2.910
  • Server OS: Windows Server 2016 Standard
  • Is the 3CX Server Hosted and where? Only on the server
  • IP Phone Make/Model/Firmware: Yealink/SIP-T27G/69.85.0.5
  • Provisioning Method: Local
  • Trunk Provider or Gateway Make/Model: Don't know
  • Has the Firewall Checker passed: not sure how to do this.
  • Are custom Phone Templates being used: NO
 
The fact that it is ringing 3 times (is the set ringing, or does the caller simply hear ringback?), then dropping, would seem to indicate that a timer considers that call unanswered, and 3CX is trying to send elsewhere (normally voicemail), but can't. However, if the called set does not actually ring, it may be a no ACK issue. The 3CX Activity Log should provide clues as to what is happening.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,953
Messages
589,915
Members
164,851
Latest member
DrunkeMeister