Unassigned DN by CCM 4.2.3 and 6.1.2

Unanswered Question
Sep 10th, 2008


after an CallManager upgrade from 4.2.3 to 6.1.2 I have a problem with unsassigned DN's.

With CCM 4.2.3 a call from external to a unassigned number inside the DID Range reject and a Voice from the Provider sounds: „This is not a valid number……….) This is a normal function.

The same call with CCM 6.1.2 to an unassigned number doesn't reject, instead it rings and rings and rings. Any idea which parameter is responsible for this behavior ?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Aaron Harrison Wed, 09/10/2008 - 04:18

I guess this is probably done based on the 'active' check box you can find if you go the the unallocated DN.

If it's not active then it shouldn't ring; unless of course some other element (i.e. a less specific tx pattern or RP) is being hit that you don't expect?

Run DNA with the GW CSS to see what the system thinks should happen to the call.

Hope this helps


Please rate helpful posts....


This Discussion