Dang it, I meant 82 (not 90) is a hunt group and 10 was member of
that. Sorry.
On 5/17/2011 11:02 AM, Matthew Kitchin (public/usenet) wrote:
One more additional note. I forgot about this one setting. The
initial call here is routed to a phantom extension that then uses
scheduling and call forwarding to route to different handsets or
hunt groups depending on the time of day. These problems did occur
before the somewhat complicated scheduling was put in place. 10 is
an extension, and 90 is a hunt group. 10 was a member of 90. I
just removed that, because I remember some issues kind of similar
where problems occurred when an extension was dialed back to back
using automated methods like this.
On 5/17/2011 10:39 AM, Matthew Kitchin (public/usenet) wrote:
This
is a fun one. I need some pointers on where to start.
I have about 15 sites that are all roughly identical in their
setup, so I know the general design is ok.
This particular site was Sipx 4.2.1 and Polycom 450/550 firmware
3.2.4 and bootrom 4.3 up until last week.
They are now sipx 4.4 (latest) Polycom 450/550 firmware 3.2.5
and bootrom 3.2.5
Cisco 2960 POE 24 port switch
Sipxbridge, Verizon VoIP services, no IP address NATing
Verizon MPLS T1
Everything is QOSd properly. There are no errors on the router
or the switch interfaces.
Unfortunately, the problems remain even after the Sipx and
Polycom upgrade.
There are 16 Polycom 450s and 1 550. The 550 is the
receptionist, and she answers the bulk of the calls. They were
on an auto attendant, but decided they wanted a live person
answering the calls. That is when my problems started.
The path of most calls is answer, park with blind transfer, page
with paging group, user retrieves call from park on one of the
450s.
From everything we can tell, they are doing this properly. They
are experiencing 2 major problems. I am not sure if one is
causing the other or if they are related.
Problem 1, straight from the Polycom 550 user "About 7-8 times a
day when the main line rings, I go to answer it and no one is
there, but on the LED screen the first button says “answer”. You
cannot pick up the call at all and the caller hangs up and calls
back."
Problem 2, also from the 550 user "about 50% of the time the
overhead can’t be heard, then when you try to use the overhead a
second time it rings busy"
She is referring to the the paging group. Nobody hears anything.
The paging call then sits in the active calls list within sipx
indefinitely. Usually, I will have to restart the paging service
to get everything going again.
This site seems like a simple setup to me. I have several others
that are identical. I have tried everything I can think of, so
I'm ready to start at square 1 again. Can anyone give me some
tips?
Thanks as always,
Matthew
|
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
