routing an ICR invalid number

[vztech]

Is there anyway to route invalid numbers? not using VM Pro
ICR built with . dest: # or XXXX dest: #

Example: DNIS from a PRI in 2323 if no user is configured I would like to send it back out across to another PBX (non IPO) tie line.
So 2323 might not be built in the system but 2324 is.

Im not sure this could be acomplished with a shortcode.

Thanks for any ideas

It's only dialtone!!!

 

[CarGoSki]

A default route already has that capability.

 

[sizbut]

Indeed, the default routes route purely by incoming line group and call type (voice or data). So they would normally be applied if the call didn't match the settings of any more specific call route.

Stuck in a never ending cycle of file copying.

 

[vztech]

TY

Ill give that a shot sending my destination to a dial SC

It's only dialtone!!!

 

[montyzummer]

But that means any call coming in that you don't have defined will follow that logic so be careful with that ,
You ideally want to tie it down to a range of digits using a wild card 1234xxx etc[pre][/pre]

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[vztech]

Ya thanks Monty
unfortunatley they are migrating users to the IPO on a dept basis and not a number range.
So 2222 might be on the new IPO and 2223 will still be on the old.

It's only dialtone!!!

 

[sizbut]

Sorry, yes, slightly misunderstood the question. Yes, a simple 2XX short code (if your extension range is 200 to 299) is a useful catchall to route errant calls back to the receptionist or main auto attendant.

Stuck in a never ending cycle of file copying.