sjered

Please help, we can't figure this one out!

I have a customer with an IP 403, they have an extension range of 4000-4099

They have four hunt groups: 4060, 4200, 4460, and 4300.

the 4060 is set to overflow to the other groups, but it won't, because none of the other hunt groups are working properly. When we dial one of the other hunt groups, all we get is an incompatible error. We created a new hunt group with extension 4079 and included the receptionist phone in the group. When dialed, there was ring tone in the dialing phone, but the receptionist phone did not ring (all settings are at default, pattern is set to group, etc.).

We are wondering if the dial plan has something to do with the problems (the hunt groups in the 4000 range seem to work just fine).

Also, we're not sure what would cause the receptionist phone to not ring (all user settings are at default).

Anyone have any ideas?

koelemon

Wihtout seeing the config it is hard to say for certain, what release is the 403? Have you tried rebooting it? You may want to also think about running the config through the Wizard offline, catches common errors that create problems that drive you crazy. If you PM me, I would be willing to have you send me the config to check out.

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info

 

sjered

403 version 2.0 (16)
We have tried rebooting
we'll try using the wizard
thanks for the offer on looking at the config, I'll let you know if we need your help.

Plenfestey

This is interesting - I too have a problem with overflow hunt groups on an IP403 version 2.0 (16).

In my case incoming group 'Main' is set to overflow to 'Unanswered', but never does. If 'Main' phones are busy, then callers get the engaged tone rather than the call being routed to phones in 'Unanswered'. I have been through the config with our supplier and he says it looks correct.

Could this be a generic problem with 403 version 2.0 (16)??

Also as an aside, when using the 2.0 Manager software I always get the error "index out of bounds (0)" when adding the overflow group to 'Main', although the added group then does appear in the list. Could this mean the added group has not been properly applied and is present in name only?

Our client is on the verge of chucking the system out and getting something else as he is so frustrated with this sort of problem.

__________________
Grumpy Old Phil

IPGuru

Do you have an overflow time set?
if yes & call quing is not enabled toy will get the problem you have described.
if you are using a collectibve (Group) group then set the ring time instead otherwise.
the error msg you are getting sugests that you have a problem with your manager application, uninstall & reinstall

__________________
Universal Plan B: - When all else fails CHEAT!

koelemon

Bingo, uninstall and reinstall is about all you can do for the manager error.

On a side note, 2.0(16) did not have a known issue about hunt group overflow and I once again agree with IPGuru about checking your Queuing on the first group as well as the overflow timer. I do this all the time and it works like a charm. All that being said, I would upgrade to 2.1 if for nothing else to be able to make hunt group changes (and many others including additions, etc.) without having to reboot. I run it in my lab and love it so far, very solid.

__________________
"There are only 10 types of people in the world,
those who can read binary and those that cannot."

PBXtech.info