Solved 1 extension always going to VM

[GDInc]

Guys, I'm lost here. We have one extension that always goes to VM. I've tried everything including deleted the inbound rules and recreating them, doing a reset on the phone, putting a new phone in, and just totally removing the entire extension and phone and rebuilding it.

Phone is a Cisco SPA525G2. Status shows available. Phone shows up properly and provisions properly. I can't do verbose logging right now because it says I need to restart to enable it (can't in the middle of the work day).

I'm not sure what else to do. Thoughts?

 

[eddv123]

Go to the extensions page and select the extension and check the status of it first.

I would also rest the call flow with the binary log viewer as well it will tell you for definite what is going on.https://www.3cx.com/docs/3cx-log-viewer/

 

[GDInc]

Looking at the logs, I'm gettng a lot of:

"Target endpoint for XXXX is VMail:9999" and "Endpoint Extn: XXXX has no forwarding rule in reason 'All calls'"

 

[eddv123]

Binary log viewer not the logs, you want to see the calls route to VM.

It should tell you why.

 

[GDInc]

Binary log viewer not the logs, you want to see the calls route to VM.

It should tell you why.

I'm using the log viewer from https://www.3cx.com/docs/3cx-log-viewer/. Is that not the right one?

 

[eddv123]

Yeah and if you find your call using the caller id (randomly generated string) C: followed by number, you can filter and see the flow.

 

[GDInc]

Oddly enough, I deleted the entire extension again, did a factory reboot on the phone, and put it all back in and it is working now.