Bueller?... Bueller?... Bueller?... anyone? Fry?... Fry?... Fry?... anyone? Just kidding. Some of you may not follow the joke.
Can anyone else give this scenario a try just so I know it isn't only me this is happening to? I will be glad to enter a jira at that point. Just create a hunt group and set it to ring the phone longer than 60 seconds. If other don't have t his problem, I would love to know that too! Thanks, Matthew On 4/5/2011 2:56 PM, Matthew Kitchin (public/usenet) wrote: > I'm using 4.2.1, sipxbridge, Verizon VoIP, polycom Soundpoint 450 and > 550 with firmware 3.2.4 > I have a site that is dead set on their requirements, and they want > all calls to go to all phones and ring for 2 minutes then drop the > call if nobody answers. Fun. > The only major issue I'm having right now is the 2 minutes. I cannot > get the phones in the hunt group to ring longer than 60 seconds. I > have a phantom extension set to forward to the hunt group. I set it to > forward for 120 or even 150 seconds. I have all phones in the hunt > group set to ring for 120 (or 150) seconds. The call still goes to the > fallback destination right at 60 seconds. > Googling led me to this: > http://list.sipfoundry.org/archive/sipx-dev/msg24617.html > "I've also confirmed this 60 second behavior spanning ringing hunt > groups." > Am I experiencing a known issue? Is there any fix/workaround? > I guess I could make the fall back destination for the first hunt > group an additional huntgroup that will go for another 60 seconds. > That will take an already ugly setup and make it uglier. > > Thanks, > Matthew > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
