09-10-2008 04:05 AM - edited 03-15-2019 01:10 PM
Hello,
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 ?
09-10-2008 04:18 AM
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
Aaron
Please rate helpful posts....
09-10-2008 04:42 AM
Hi,
where can I find this check box ?
Thanks
David
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide