Thanks for sharing, Matt. Does anyone else want to share something? - that
really sounds as if we were all part of the old-ACD supporting group, in a
group meeting :)
Just to be clear, when I said "ACD Presence" I meant the Features -> Agent
Status page, where you can even sign in/sign out agents.
Is there any documentation or setup instructions for the Contact Center of the
4.6.0 release?
Thanks for your help and assistance,
Rob Schroeder
NOTICE: This electronic mail message and any content within it are intended
exclusively for the individual(s) or
entities to which it is addre
Awesome details Matt. Thanks for sharing.
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Matt White
Sent: Friday, August 31, 2012 4:58 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] 4.4 ACD pickup Beep
On 09/01/2012 12:20 AM, Joegen Baclor wrote:
> On 08/31/2012 08:01 PM, Domenico Chierico wrote:
>> Seems that linphone sends to port 5060 some messages reporting "jaK"
>> inside for keepalive purpose.
>> Seems that this messages give troubles to the proxy.
>> I'm trying to fix this avoiding to pars
On 08/31/2012 08:01 PM, Domenico Chierico wrote:
> Seems that linphone sends to port 5060 some messages reporting "jaK"
> inside for keepalive purpose.
> Seems that this messages give troubles to the proxy.
> I'm trying to fix this avoiding to parse this as SIP stuff
>
> thanks
> Domenico Chierico
We had dedicated lines for our ACD enabled handsets. They also had a
direct assigned extension. Our support agents had a reason to have both.
I didn't realize it might or might not have helped with potential
issues. Our server was (it is still doing the job, I'm just not with
that company any m
Seems that linphone sends to port 5060 some messages reporting "jaK"
inside for keepalive purpose.
Seems that this messages give troubles to the proxy.
I'm trying to fix this avoiding to parse this as SIP stuff
thanks
Domenico Chierico
___
sipx-users mai
The audio issue you mention is likely due to resources. There is no doubt the
ACD is a resource hog. Specifically CPU. Which odd as the rest of sipx seems
to be more RAM constrained.
We used to have issues with the choppy audio until we standardized our platform
with an ODM 3-4 years ago.
IN EACH INSTANCE your UA (none of them) does not support the MOH method in
use by the system. None of what you say is "unexpected" and I don't think
its fixable except at the UA.
--
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.
What does this have to do with Cisco Hold/Resume.
Please start a new thread and somebody might respond. I have ideas but
will wait for new thread.
On Fri, Aug 31, 2012 at 4:49 AM, Ivan Pletenev wrote:
> Hi.
>>
>
> I got the same problem - we can't resume external call hold. It happened
> after
It's a valid hijak Melcon because these are the sorts of issues I have
experienced all along with the ACD. The choppy audio is usually solved
with faster equipment because the ACD is a B2BUA (the call is anchored on
that service).
The other types of issues you are describing are what have always
>
> Hi.
>
I got the same problem - we can't resume external call hold. It happened
after i did yum update. We use grandstream phones and yealink. Also i tried
call\unhold with iphone sip client media5-fone - no luck. Is there any news
on this problem?
---
Ivan Pletenev
>
> -- Пересылаемое
12 matches
Mail list logo
