Solved Call Script caused 3CX to reject all calls but....

[mimicadmin]

I was playing around as i need to investigate call scripts, anyways i went to Integrations | Call Scripts and added a custom one and pointed it at a DID. Then after being presented with a scripting windows i was like "Nope" i don't understand this just yet i will delete it and do some research.

From that point all calls to that DID were being rejected, after viewing the logs i could see that the calls were being stamped with the name i had given the Call Script which was "test". I was absolutely lost for a few hours trying to find out why only 1 DID wasn't working. Anyways, i restored the system which fixed the problem.

My question is how can something that was removed still linger and cause this and where could i have gone to remove it permanently?

Apologies, as i didn't backup the system while it was broken so i have no logs or evidence, just putting this out there for you 3CX gurus.

 

[YiannisH_3CX]

Hello @mimicadmin

When you created a call script and assigned a DID to it, you essentially created an inbound rule for that DID. When you deleted the call script the destination of that inbound rules was set to "End Call". Inbound rules are not deleted once an endpoint is deleted.
All you needed to do was to assign the same DID to a different destination and the problem would have been resolved.

 

[mimicadmin]

Thanks for that, yeah i cant remember if i actually did that or not, but i know how to replicate the issue. So i might test.

Cheers

 

[mimicadmin]

Hi,

I have tested this by adding a call script for a DID and then delete it which causes the DID to end call. If i then i go to lets say an IVR and assign the DID to that it will fix the issue.

Cheers