unused directory numbers

[mark.kruse]

We're using UCM 8.6. When outside callers enter an invalid(unused) extension they get a message stating "You cannot be transferred to this number, it is busy". Although this is true, it confuses the caller into thinking that the extension they dialed is valid, which is not true.

Is there anyway to just have unused extension/DN's be invalid and not ring busy?

Thanks                

[Leonardo Santana]

Delete the unassigned directory numbers.

[mark.kruse]

thanks for the quick responses.

These directory numbers have never existed. That's the puzzling part.

Example number would be 2099. Never been created, but message stated above plays.

[allan.thomas]

Typically what I do with most deployments is configure fallback patterns for DDI incoming DN ranges in a different partition that of the translated patterns in the incoming gateway CSS. This ensures that any incoming DDIs which do not exist in the dialplan or unallocated will match a translation which directs the external call to reception.

For example you have a block of 100 Dns, 2100 to 2199 are translated to 812100 through 812199, and a second translation for the same range which translates to reception pilot in a different partition. Both partitions are in the gateway's incoming CSS, with the translation pattern to reception ordered below the first translation. If the dn 812100 exists then the first partition will be matched, if not then the second partition will be matched and the incoming call translated to reception to answer.

When you debug the isdn do you see unallocated number? If that was the case then I would expect fast busy. The message you hear doesn't sound like a typical annunciator message and something your carrier is playing out?

Regards
Allan

Sent from Cisco Technical Support iPad App

[Ayodeji Okanlawon]

Mark,

How about using route plan report to delete all un assign extensions. I believe the behaviour will be different

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[Rob Huffman]

Hi Mark,

Try this method via the Route Plan Report;

Deleting Unassigned Directory Numbers

This  section describes how to delete an unassigned directory number from the  route plan report. Directory numbers get configured and removed in the  Directory Number Configuration window of Cisco CallManager  Administration. When a directory number gets removed from a device or a  phone gets deleted, the directory number still exists in the Cisco  CallManager database. To delete the directory number from the database,  use the Route Plan Report window.

Procedure

--------------------------------------------------------------------------------

Step 1 Choose Route Plan > Route Plan Report.

The  Route Plan Report window displays. Use the three drop-down list boxes  to specify a route plan report that lists all unassigned DNs.

Step 2 Three ways exist to delete directory numbers:

a. Click the directory number that you want to delete. When the Directory Number Configuration window displays, click Delete.

b. Check the check box next to the directory number that you want to delete. Click Delete Selected.

c. To delete all found unassigned directory numbers, click Delete all Found Items.

A warning message verifies that you want to delete the directory number.

Step 3 To delete the directory number, click OK. To cancel the delete request, click Cancel.

Cheers!

Rob

PS: +5 to Deji and Leonardo for trumping my useless typing skills and coming up with

excellent replies

"May your heart always be joyful
May your song always be sung" - Bob Dylan