Hunt Pilot Issue in Call Manager

[prizm76]

Hi All,
I'm currently using Call Manager 4.1 in my workplace which I did not setup or configure but I'm now in charge of. I'm not exactly an expert but i can configure and manage our phones as well as navigate my way around callmanager fairly well.

We have many satellite offices we need to join to our call manager, each site consists of 5 lines all of which they would like to hunt. So I went through and created Line Groups and Hunt Lists as well as a Hunt Pilot. I think the Hunt Pilot is giving me the issue as I created a Hunt Pilot at 2900. For some reason when I dial 2900 instead of broadcasting to the 5 test phones (2901-2906)I setup in the Hunt List it goes to 2200 and the receptionist picks up which is our main number for our office.

Any ideas as to why this would be? Is it an issue with the translation pattern or something? I'm usually ok with experimenting but I don't want to wipe out the receptionist and get my head handed to me.

I also apolgize if this is lacking necessary info but at this point I'm not sure what else is needed.

Thanks for any advice -- Joe

 

[pmoorey]

Hi

I'd check for any route patterns/ translation patterns that match your pilot point number, and that the numbers are reachable within the calling search space and try resetting the pilot point number.

I've also found if you have implemented Attendant Console you have to add the pilot point number to the AC user account, if not this will prevent the pilot point number from being called (I've found in the past).

Just a few ideas

HTH.

Peter
CCNA, Cisco Qualified Specialist

 

[prizm76]

Thanks for the quick reply.

I know our receptionist is using Attendant Console however our satellite locations will not be. I had to create a translation pattern for the 2900 Hunt Pilot because initial calls would result in the number being unreachable. Would the translation pattern for a Hunt Pilot be different than creating a standard phone? What special differences exist in a translation pattern for a Hunt Pilot.

I double checked the phones, I can dial every which way from the phones and to the phones to rule out some mistake on that end.

Before I created 2900 I made sure I couldn't find it anywhere in the system to make sure I wouldn't create a conflict.

I guess what my question at this point would be, is it possible that the 2200 would encompass all Hunt Pilots created in our DID range? It doesn't make sense to me but there is alot for me to learn.

 

[pndscm]

Sounds to me like you have a Translation Pattern that points all unused DN's in a partition to the receptionist and your new TP isn't reachable from the phones. Double check your Partitions and Calling Search Spaces.

 

[prizm76]

Should I create a new partition for each location and set of phones? From what I've read the partition helps manage where you can and can't call?

 

[pmoorey]

Partitions are 'groups', Calling Search Spaces list which partitions (groups) are accessible to each other.

So long as your pilot point and hunt list directory numbers are in any partitions within the same CSS they should be dialable.

As posted above I'd recommend checking your translation patterns because your pilot point directory number is being translated before it gets anywhere near the hunt group.

Do a route plan report CCMADMIN > Route Plan > Route Plan Report and then type in the pilot point to see how it is being routed!

HTH

Peter
CCNA, Cisco Qualified Specialist

 

[prizm76]

Great news, I was able to get it working but I'm not entirely sure what the problem was before. I checked the Route Plan Report and everything looked normal so I recreated the Hunt Pilot and it seemed to start working.

Thanks to all for their input and help.