The issue we are experiencing is that our main number keeps giving a busy signal. The main number is configured to translate to a pilot number, which is configured to route calls to first available hunt group members. The hunt group members are extensions associated to an attendant console user.
For instance, main number is XXXX 5000, which when ringing translates internally to 3268, this is the pilot number. The hunt group configuration consists of a pilot point using this pilot number (3268). The hunt group members are,
direct call to reception, line 1; direct call to reception, line2. Where line 1 and line 2 are the associated lines of attendant console user reception. Line 1 = 2501, line 2 = 2502.
I can ring 2501 and 2502 and get to reception without a problem. The problem is when i try ringing XXXX 5000, 5000, or 3268. I keep getting busy tones.
Can anyone please provide some assistance on what may be the problem?
I have checked the configuration once again and it is correct. This has been working but it stopped working even though no changes were made. The CSS for PP reaches DNs and CSS for hunt group members reaches PP. I have restarted the TCD and CTIManager services to no avail. Event viewer doesn't report anything unusual.
As a work around the main number (5000) is now being translated to an extension (2506), which was one of the hunt group members; i did it so to bypass the hunt group and it works, which tells me the issue is with the pilot point and hunt group. So ringing the main number now is ok but only with one line as I can't use the hunt group. I need to have it operational again.
Attached is the output of the dialer number analyzer using an internal extension as the calling party and the pilot number as the dialled digits, which proves the route is fine.
Can you share any ideas as to what may be causing the hunt group or pilot point not to respond?
You are correct the problem is with your pilot 3268. If you can go into data base and reset if not then try this:
Delete the pilot 3268 and re create. Just to test you may create a new pilot number and redirect any number to it first if works try re directing 5000 if that works you know 3268 re create should work.
Thanks for the suggestions. I tried to follow all.
At the end I had to reboot the call manager (subscriber only) and it came back ok and the pilot point started to respond again. I take it that one of the services locked up for some reason. I will be logging a job with our reseller to see if there is a hot fix for this version of call manager to make it more stable otherwise may consider an upgrade to version 5.
Can any one provide any suggestions as if an upgrade will be a better option?
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...