Getting "the number you have dialed is not in service" after the IVR

FreePBX Configuration
1

So I think we had multiple issues this week. This issue has been here since the start. This system was compromised during this latest endpoint manager thing. I deleted it, upgraded the server to Debian 17, and reinstalled, then restored a backup from June 2024. Everything else works fine, but this issue is still there. I gave call logs to our SIP provider and they say it’s the phone system. I deleted the IVR and the call queue and recreated them. I could understand if the calls instantly got that message, but the system answers and routes to the IVR and plays the recording then the caller gets the message.

The main inbound route goes to time conditions then to either a day or night IVR. I changed the inbound route to a phone and it rings to the phone just fine. I changed the inbound route to just the IVR and it’s the same issue. It seems like there’s something wrong with the IVR, but I can’t figure out what. I don’t know how to track this down beyond this. Any help would be grateful!

2

I changed the inbound route to the queue and it did the same thing. It starts playing music then gives me the message so maybe it’s an issue with the queue instead of the IVR. I deleted the old queue and created a new though. I don’t think I used all the same settings. I just added a few exts and used mostly default settings when I created a new one.

3

I may have narrowed it down to a single phone that’s causing it.

4

Ok, it’s not the phone. I setup a new phone and it did the same thing. I’m going to delete her user and ext and re set them up.

5

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.