Thanks for your answer. Your example would not lead to the configuration we need. All phones have to ring at the same time when the group-extension is called. When an employee leaves the desk the phone should not ring anymore and all calls to his _own_ extension have also to be redirected to the other group-members.
We did not set up any call forwarding in the phone settings. Only user-settings in SipXecs were used. We tested this behaviour with Snom360 (answer in DND: "480 Do Not Disturb") and Polycom 430/550 (not checked yet) phones. Rene >>>> On 3/25/2009 at 8:25 AM, in message >>>> > <[email protected]>, > Rene Pankratz <[email protected]> wrote: > >> Hello, >> >> We figured out a serious issue, that causes the sipXproxy process to >> > > >> take 100% CPU-usage and and breaks down the whole SipXecs. >> We can reproduce this behaviour on SipX 3.10.2, SipX 3.10.3 and >> 3.11.12-014925. >> >> The following steps lead to this problem: >> Create a hunt-group (e.g.extension 800) in SipX that consists of 3 >> telephones (e.g. 801, 802, 803). All phones shall ring at the same >> > time, > >> don't allow call forwarding. >> Modify the call forwardings of the hunt-group members via >> > Webinterface, > >> so that the other phones ring if user is busy or activated DND. >> >> Extension 801: >> Forward to 802 if no response and ring 803 at the same time. >> >> Extension 802: >> Forward to 803 if no response and ring 801 at the same time. >> >> Extension 803: >> Forward to 801 if no response and ring 802 at the same time. >> >> With this setting SipX soon starts to act in an unexpected way. >> Unfortunately some phones seemed to ring forever and soon the whole >> > SipX > >> broke down. >> Background is that the members of the hunt group shall forward their >> > > >> calls to the others when they leave their desk. We expected this >> > could > >> be done by configuring SipX in the way described above and activating >> > > >> DND when leaving the desk. >> >> Setting the call forwarding of the users to the hunt-group-extension >> > > >> causes the same beahviour. >> >> Any suggestions to solve this problem? We want to avoid setting call >> > > >> forwardings on the phones. >> >> Thanks in advance >> René Pankratz >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> >> > > > Well, according to what I think you said, it sounds like you have the > hunt group configured in a strange way. > > Normally your hunt group forwarding/no answer settings are controlled > by the hunt group withini sipxecs, not by phone settings, which is > one-way-to-do-it. > > You would create the hunt group with the "lead line" as "initially > call", then add the other lines. Make sure you have your fallback > destination defined 9what to do if noone answers, like "Use Voicemail". > Remember the hunt group allows only certain things: > > 1. You cannot circularly hunt; Ring line 200 initially, then 201-204, > then 200 again. Putting the same line in the hunt group more than once > is not a good idea. > 2. You might find call forwarding more problematic, so turn it off for > testing purposes and create your hunt group in a simple fashion and see > what happens. > 3. Please state what kind of phones you are using, it might make a > difference if the phones have some type of known issue with DND. You > never know. > > A good working example: > > Initially call: 200 930 seconds) > If no response: 202 > If no response: 203 > If no response: 204 > If no response: 300 > > (create a line of 300 with no phone and forward it all the time to > 8200, which is the voicemail for user "200", the pilot phone in the hunt > group. > > Turn off call forwarding, turn on voicemail. > > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
