Recycling DIDs in v20

[coaffxhd]

Hi everyone,

With the removal of Inbound Routing control in v20, I seem to be missing a step with how to reset the default call handling on DIDs after I delete an extension. After an extension is deleted, it appears that the DID goes into some middle-state between unused and assigned. The DID tab on the SIP trunk just shows blank. The problem is that when calls come in to DIDs in this state, they get a "call cannot be completed" error and then get dropped. I would expect that deleting an extension would return the DID to the pool and make it unused. With our unused DIDs, they default to the main IVR as we expect. I can't seem to figure out how to put a DID back into unassigned except for deleting it from the trunk and re-adding it, which is a stupid work around IMO. Removing the DID before deleting will probably work, but that's also one thing I would prefer not to need to remember. Have I stumbled upon a glitch? Any advice?

The screenshot shows the DID tab on my trunk, where some are "unassigned" because they've never been assigned (these go to the main IVR). The red boxes show DIDs that were attached to deleted extensions and have some sort of undefined state. We want these numbers to route to the default place (an IVR) without having to specifically attach them to it. This works for the unassigned ones. Thanks in advance for any thoughts.



Thanks,
Tim

 

[TheodorosG_3CX]

This depends also on your sip trunk, are you using a 3CX Supported Provider?

 

[NicholasP_3CX]

Please check where your calls are routed to be default in your SIP trunk configuration.

All unassigned DIDs will route to this destination.

 

[coaffxhd]

This depends also on your sip trunk, are you using a 3CX Supported Provider?

I'm using Twilio on a dedicated server, which I believe is still supported.

Please check where your calls are routed to be default in your SIP trunk configuration.

All unassigned DIDs will route to this destination.

View attachment 42884

The default route for my SIP trunk is the IVR, and it works fine if the DID is listed as "unassigned" on the DID tab of the trunk. But for DIDs in that list that are just blank under the Assigned To column (boxed in red in my earlier screenshot), it gives callers an error message recording saying that the call cannot be completed. The "blanks" happen when extensions with attached DIDs are deleted. This puts the DID into an undefined state, and Default call routing is not applied. I suspect there's still an inbound routing rule for the DID assignment that is not being deleted thoroughly along with the extension and it points to an extension that no longer exists. In v18 I could go into the Inbound Rules tab, located the defunct DID rule, and just delete it. That tab no longer exists in v20.

I can work around this in three ways: 1) remove the DID before deleting the extension, 2) Re-assign the problem DID temporarily to a dummy extension and then remove it, and 3) delete the DID from the SIP trunk temporarily and re-add it. Ideally, none of these would be required and deleting an extension with an attached DID would return said DID to the "unassigned" state. Pretty sure that's what is supposed to happen, and this is just a bug.

 

[NicholasP_3CX]

This is aligned with the behaviour we had in Version 18. While it is not so visible now, a DID that was assigned to a user in Version 18 was routed to them, when the user was deleted, since the route was now no longer valid, it would default to "End Call"

This is the same behaviour, it is just not visible.

 

[coaffxhd]

Exactly. That’s what I’d do back in v18. But now the “end call” entry can’t be deleted directly since the inbound rules tab was removed. It’d be great if the DID were automatically set back to unassigned.