On 7/1/2011 7:43 AM, Michael Picher wrote:
Well, most PBX's show you WHO is calling, not who they called. Of
course if voice goes through a server (big drawback) I suppose if some
service is calling you you might see that service.
The current ACD should always be setup on a separate line and should
not be on a user's private line.
And, not there is not a way to NOT follow the user call forwarding rules.
Also, note the big limitation of not being able to transfers by the
agents. The current ACD really doesn't like that.
On a side note, I have no idea why I am 'special' and we can do with
this with no problem. Our helpdesk handles several hundred ACD calls a
day and transfers many of them with no problem. It worked on 4.0.4 and
works on 4.2.1. I guess I should just be happy and not care why.
Mike
On Fri, Jul 1, 2011 at 8:13 AM, Anthony George <[email protected]
<mailto:[email protected]>> wrote:
Yes, that's a possibility, but it also feels like stepping back a few
years into a key-based PBX. IMO, it should just work like a *newer*
PBX(Avaya/lucent for example).
Nonetheless, the technical description on what I'm working towards has
been explained, and the ACD works, to a point.
Although, is there a way to configure the ACD, like the hunt groups,
to NOT follow the user call forwarding rules?
Anthony C. George
On Fri, Jul 1, 2011 at 5:33 AM, Michael Picher <[email protected]
<mailto:[email protected]>> wrote:
> Why don't you just have those numbers you wish to know that were
dialed ring
> in on different line keys on the phone. Then you know just by
looking at
> which line is ringing what number was dialed. Sure you're
limited by the
> number of keys on your phone but this is one method I've used in
the past to
> get around this.
> Mike
>
> On Thu, Jun 30, 2011 at 11:37 PM, Todd Hodgen
<[email protected] <mailto:[email protected]>> wrote:
>>
>> Why could you not assign an extension to each user – which is their
>> primary extension number, and have DID and other aliases point
to it. Have
>> another number that the hunt group points to. Line 3 rings,
its hunt
>> group. Line 1 or 2 ring, it’s a call to your extension.
Pretty simple.
>>
>>
>>
>> From: [email protected]
<mailto:[email protected]>
>> [mailto:[email protected]
<mailto:[email protected]>] On Behalf Of
Aaron Pursell
>> Sent: Thursday, June 30, 2011 1:49 PM
>>
>> To: Discussion list for users of sipXecs software
>> Subject: Re: [sipx-users] Polycom, sipxecs 4.4 and called id
with hunt
>> groups
>>
>>
>>
>> I see what you mean, our issue is a little bit different then.
>> However, that would be helpful to us also, because as we all
have direct
>> lines in, we're also members of the helpdesk group.
>>
>>
>>
>> Aaron Pursell, Sr.
>>
>> Network Systems Administrator
>>
>> Easter Seals - Goodwill, Northern Rocky Mountain
>> 4400 Central Ave
>> Great Falls, Montana 59405
>>
>> (406) 771-3721 <tel:%28406%29%20771-3721>
>> [email protected] <mailto:[email protected]>
>>
>> >>> Anthony George <[email protected] <mailto:[email protected]>>
6/30/2011 2:45 PM >>>
>> Definitely an issue, although more important to us, anyway, is the
>> ability for the hunt group member to see why their phone is
ringing.
>> Whether it's a personal direct call, a hunt group for Sales, a
>> failover to a hunt group for Tech Support/live answer? Just some
>> examples. All of these "call types" would be answered differently.
>>
>> Anthony C. George
>>
>>
>>
>> On Thu, Jun 30, 2011 at 4:39 PM, Aaron Pursell <[email protected]
<mailto:[email protected]>> wrote:
>> > I guess my issue with this and I assume Anthony is, in our
case, you
>> > call
>> > the "IT HELPDESK" SIPX shows that your calling an individual,
not the IT
>> > Helpdesk. So at first a lot of our users were confused
because they
>> > called
>> > the IT Helpdesk and they thought they mis-dialed because it
showed up as
>> > a
>> > specific person in the hunt group versus the hunt group.
>> >
>> >
>> > Aaron Pursell, Sr.
>> > Network Systems Administrator
>> > Easter Seals - Goodwill, Northern Rocky Mountain
>> > 4400 Central Ave
>> > Great Falls, Montana 59405
>> >
>> > (406) 771-3721 <tel:%28406%29%20771-3721>
>> > [email protected] <mailto:[email protected]>
>> >>>> Michael Picher <[email protected]
<mailto:[email protected]>> 6/30/2011 2:34 PM >>>
>> > it shows the caller, not the callee... this is correct behavior
>> >
>> > On Thu, Jun 30, 2011 at 4:30 PM, Anthony George
<[email protected] <mailto:[email protected]>> wrote:
>> >>
>> >> I'm trying to setup up hunt groups on a nearly fresh install of
>> >> sipxecs(from ISO, then yum update on stable). What I'm trying to
>> >> figure out is if I'm missing something or what. On the
display of,
>> >> say a Polycom 650, should it show the hunt group that is
being called
>> >> on the callee's phone?
>> >> Here's an example:
>> >> Hunt Group "Shop" 7402 includes users 7410,7412,7414.
>> >> If user 7415 calls 7402, shouldn't it show on
(7410,7412,7414) that a
>> >> call is coming in for "Shop" 7402?
>> >> All I'm getting is what looks like just as if 7415 was
calling each
>> >> particular user directly.
>> >>
>> >> Any ideas or documentation?
>> >> Anthony C. George
>> >> _______________________________________________
>> >> sipx-users mailing list
>> >> [email protected]
<mailto:[email protected]>
>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >
>> >
>> >
>> > --
>> > Michael Picher
>> > eZuce
>> > Director of Technical Services
>> > O.978-296-1005 X2015 <tel:978-296-1005%20X2015>
>> > M.207-956-0262 <tel:207-956-0262>
>> > @mpicher <http://twitter.com/mpicher>
>> > www.ezuce.com <http://www.ezuce.com>
>> >
>> >
>> > _______________________________________________
>> > sipx-users mailing list
>> > [email protected]
<mailto:[email protected]>
>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>> >
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
<mailto:[email protected]>
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>> ________________________________
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com <http://www.avg.com>
>> Version: 10.0.1388 / Virus Database: 1516/3735 - Release Date:
06/30/11
>>
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
<mailto:[email protected]>
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
>
>
> --
> Michael Picher
> eZuce
> Director of Technical Services
> O.978-296-1005 X2015 <tel:978-296-1005%20X2015>
> M.207-956-0262 <tel:207-956-0262>
> @mpicher <http://twitter.com/mpicher>
> www.ezuce.com <http://www.ezuce.com>
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
<mailto:[email protected]>
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
[email protected] <mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
Michael Picher
eZuce
Director of Technical Services
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com <http://www.ezuce.com>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
