call failed: not found

Posted on 2008-10-10
Last Modified: 2012-05-05
I have x-lite setup with my cisco call manager 6.1 to recived incoming calls is fine but when I try to dial extensions or out going call I cget the message

Call Failed: Not Found
Question by:arahming
  • 4
  • 3

Expert Comment

ID: 22693149
check that the appropriate partitions are listed in the calling search space and that your phone is using appropriate calling search space (css).  By the way, do you get dialtone when you lift the reciever?  Fast busy???

Author Comment

ID: 22693619
I get a dial tone and can dial 411 just can't dial the extension or outside lines

Expert Comment

ID: 22696316

Sounds like you've got a partition, calling search space or route list problem (or possibly a combination of more than 1).  When you can dial one route pattern (411 in this case), it's because all three of these things are correct within your IP phone's context.  A phone from a different city/state within your organization may not be able to dial something you can because they have a different context.

The notion of "context" is what I'm driving at here.  You phone (or anyone else's for that matter) require certain things that allow it to dial.  I'll try my best to summarize below:

1.  Find out what PARTITION your phone belongs to
2.  Any other IP phone you try to dial must also be located within this same partition, HOWEVER,
     A)  if two phones do not belong to the same partition, both phones need to have the other partition listed within their respective CALLING_SEARCH_SPACE.
3.  Whenever you dial a number regardless if it hits the PSTN or internal extention, voicemail, paging system..etc, Call manager always broadcasts the searches through the PARTITION that your phone belongs to.
4.  If no match is found, then it looks to the ROUTE_LISTS/HUNT_LISTS.
5.  This is where you dial-patterns are located.  You will find a route_list entry that will match the "411" pattern, and upon inspection of this route_list, you will also find that it belongs to a device pool whose partition is that of your phones.

This is how dialing "context" are bound and formed.  Just to be sure, let me summarize.  Your phone is dialing 411.  It belongs to the "ALL_PHONES" partition.  You dial 411 but Call Manager does not find an internal DN that matches 411, so it looks to the ROUTE LISTS/HUNT LISTS to locate its pattern to send it out to the correct gatway or route group.  Since 411 exists in the ROUTE PATTERN, Call Manager (CM) found that it belongs to the LOCAL_ROUTER_MGCP_OR_H323_GATEWAY (for example).  Your dialed digits were matched up with this route list and call manager passed the call to this particular router for final processing out thru this router's PSTN connection (whether PRI, T1-CAS, FXO...etc).

To be sure, you must understand that none of this would have worked if your phone wasn't in the same DEVICE POOL as the ROUTE PATTERN'sgateway's DEVICE POOL entry.  In other words 1 device pool called "MY DEVICE POOL" (for example) contains your phone and this router.  The device pool is bound by the PARTITION.  This again is how "context" is formed and differentiated among phones and devices such as gateways, CTI Route Points ...etc.
The reason you cannot dial to other devices or phone numbers is because you have something not matched by 1 or more of the above entities (partition, calling search space, device pool or route pattern)
this should get you started down the right path for what to check, but let me know specifically what you've verified to be good.  We can then eliminate those things and reduce the problem to its finer points.

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.


Author Comment

ID: 22702778
Okay I have verified that the phones are on the same partition but still have not been able to get the phones to dial out they still recive calls fine

Expert Comment

ID: 22702833
The next step after checking that both phones are on the same partition is to check each phone's CALLING SEARCH SPACE.  Take a look at their entries and then check the actual Calling search space configuration to make sure that the PARTITION that both phones are located on (you indicated they were the same PARTITIONS) include this PARTITION name.
Again, you need to make sure that the PARTITION name of the phones is inserted into the CALLING SEARCH SPACE configuration that each phone is configured to use.

Accepted Solution

icanhelp earned 500 total points
ID: 22702843
After that, you need to make sure that at phone belongs to the same device pool.

Also, in the DN configuration of each phone, DO NOT SET any parameters (such as Calling search space...etc) other than the PARTITION.  All other parameters should be inherited.

Author Closing Comment

ID: 31505158
You are a VOIP God thanks a lot

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
FreePBX to CUCM Error 1 63
Setting up a Good IVR 2 44
Cisco CUCM 10.5: password recovery 2 71
Failing ALG SIP test for new VoIP phone system 4 86
In my office we had 10 Cisco 7940G IP phones that were useless as they were showing PROTOCOL APPLICATION INVALID when started. I searched through Google and worked for a week continuously on those phones, and finally got them working. This is a di…
As companies replace their old PBX phone systems with Unified IP Communications, many are finding out that legacy applications such as fax do not work well with VoIP. Fortunately, Cloud Faxing provides a cost-effective alternative that works over an…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question