11-12-2003 05:34 AM - edited 03-13-2019 02:31 AM
Hi All,
I have facing problem on calls having this error (unassigned number (1)) this greatly affect my ASR. May i know what cause this,?? how can i solve this problem??
Thank regards
Chan
11-12-2003 06:04 AM
it means the Called party/Dialled number does not map to anything. Make sure you are not inadvertently stripping digits or have translation rules. If you are using Call Manager make sure that you have an extension that maps to the Called Number.
11-12-2003 06:48 AM
But have 4 dial-peer for 4 ports
Call coming in is 17711XXXXXXXXXX still having the problem..any advise?
Like
dial-peer voice 17 pots
destination-pattern 1711T
progress_ind alert enable 8
direct-inward-dial
port 0:D
prefix 0
!
dial-peer voice 18 pots
destination-pattern 1711T
progress_ind alert enable 8
direct-inward-dial
port 1:D
prefix 0
!
dial-peer voice 19 pots
destination-pattern 1711T
progress_ind alert enable 8
direct-inward-dial
port 2:D
prefix 0
!
dial-peer voice 20 pots
destination-pattern 1711T
progress_ind alert enable 8
direct-inward-dial
port 3:D
prefix 0
!
11-12-2003 07:13 AM
It all depends on you dialplan. What digits do you want to send out?
At the moment you are sending out the following digit string...
User dials 17711ABCDEFGHIJ
17711 is stripped and prefix of 0 is added. So
0ABCDEFGHIJ will be sent out. Is this what you intend?
11-12-2003 07:53 AM
yes 17711 will be strip..all the other will send to switch...
11-12-2003 08:02 AM
the number you are sending is not being recognised at the terminating switch. This is producing the Release with cause Unallocated/Unassigned number.
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