Solved

Cisco UC560 unable to receive inbound calls

Posted on 2011-09-07
1
2,695 Views
Last Modified: 2012-05-12
I currently have a UC560 that I'm having some issues configuring inbound calls on. I can make outbound calls without a worry but I keep receiving the below on inbound.

The UC560 has 4 ISDN BRI ports whereby two are for one trunkgroup and two are for another. I've attached a clean config that I've stripped to it's basics (there are all sorts of dial-peers etc I need to add in but as the fundamental inbound call doesn't appear to work I've tried to get it as simple as possible just testing on the first trunkgroup). I've also attached the translation debugs and clean the last three digits of the numbers etc.

Any help appreciated as I can't see the immediate cause as every thing I amend or test matches against doesn't seem to have an impact.

000231: Sep  7 07:57:30.079: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x01
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0x89
                Exclusive, B1
        Calling Party Number i = 0x2183, '7590199111'
                Plan:ISDN, Type:National
        Called Party Number i = 0x81, '635111'
                Plan:ISDN, Type:Unknown
000274: Sep  7 07:57:30.087: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8  callref = 0x81
        Channel ID i = 0x89
                Exclusive, B1
000275: Sep  7 07:57:30.115: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8  callref = 0x81
        Cause i = 0x809C - Invalid number format (incomplete number)
000276: Sep  7 07:57:30.163: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8  callref = 0x01
000277: Sep  7 07:57:30.167: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x81   Debug-Translation.txt Clean.txt
0
Comment
Question by:v0r73x
1 Comment
 

Accepted Solution

by:
v0r73x earned 0 total points
ID: 36498593
Ah I noticed the error, CCA seems to create a 'catch all' dial peer that look to be screwing things up when using the CLI to edit things further -

dial-peer voice 6 pots
 description catch all dial peer for BRI/PRI”
 translation-profile incoming nondialable
 incoming called-number .%
 direct-inward-dial

Deleted that and it's working fine, can't see why it would be needed? Created by CCA? Oh well...
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

Getting hacked is no longer a matter or "if you get hacked" — the 2016 cyber threat landscape is now titled "when you get hacked." When it happens — will you be proactive, or reactive?
Shadow IT is coming out of the shadows as more businesses are choosing cloud-based applications. It is now a multi-cloud world for most organizations. Simultaneously, most businesses have yet to consolidate with one cloud provider or define an offic…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

808 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