- Joined
- Apr 4, 2011
- Messages
- 175
- Reaction score
- 12
Hi there Folks
Just sold in a 3CX system to a client and the whole thing is working brilliantly except for one extension which will not ring. The call whether it's internal or external to that extension simply diverts immediately to voicemail. On looking at the verbose logs I'm seeing this:
Here's the rub. The phone is not set to DND. It is not busy. If I put another completely different phone on that extension and provision it, exactly the same thing happens with the new phone so it's not the phone. I don't understand the "Endpoint Extn:933 has no forwarding rule on reason 'All calls'" either. I've done Google searches but nothing really fits this issue exactly.
This doesn't happen to any of the other extensions in the office or mobile extensions. If this extension is used just with web client it still doesn't work.
If anyone has had this before I would dearly like to hear about it and would so appreciate the help with this - our first 3CX cloud-based sale.
Thanks in advance.
Chris
Just sold in a 3CX system to a client and the whole thing is working brilliantly except for one extension which will not ring. The call whether it's internal or external to that extension simply diverts immediately to voicemail. On looking at the verbose logs I'm seeing this:
| 07/04/2020 20:50:25 - L:13.1[Extn:950] forwards call from Extn:933 to VMail:200 based on rule Fwd[Available/Busy] |
| 07/04/2020 20:50:25 - [Flow] Target endpoint for 933 is VMail:200 |
| 07/04/2020 20:50:25 - [Flow] Building VoiceMail target of endpoint 933 from "Support, TGIS" <sip:[email protected]:0> |
| 07/04/2020 20:50:25 - L:13.1[Extn:950] failed to reach Extn:933, reason Busy |
| 07/04/2020 20:50:25 - Leg L:13.1[Extn:950]: Refreshing OutCID from endpoint Extn:933 = [01189711933] |
| 07/04/2020 20:50:25 - [CM503016]: Call(C:13): Attempt to reach <sip:[email protected]:5060> from Extn:950 has failed. Reason: Busy |
| 07/04/2020 20:50:25 - Call(C:13): from L:13.1[Extn:950] has failed, because Extn:933 is in DND mode |
| 07/04/2020 20:50:25 - Extn:933 is in DND mode |
| 07/04/2020 20:50:25 - [Flow] Endpoint Extn:933 has no forwarding rule on reason 'All calls' |
| 07/04/2020 20:50:25 - [Flow] Call(C:13): has built target endpoint: Extn:933 for call from L:13.1[Extn:950] |
| 07/04/2020 20:50:25 - [Flow] Target endpoint for 933 is Extn:933 |
| 07/04/2020 20:50:25 - [Flow] Building target endpoint to 933 from "Support, TGIS" <sip:[email protected]:0> |
Here's the rub. The phone is not set to DND. It is not busy. If I put another completely different phone on that extension and provision it, exactly the same thing happens with the new phone so it's not the phone. I don't understand the "Endpoint Extn:933 has no forwarding rule on reason 'All calls'" either. I've done Google searches but nothing really fits this issue exactly.
This doesn't happen to any of the other extensions in the office or mobile extensions. If this extension is used just with web client it still doesn't work.
If anyone has had this before I would dearly like to hear about it and would so appreciate the help with this - our first 3CX cloud-based sale.
Thanks in advance.
Chris