t;> From:
>>> sipx-users-boun...@list.sipfoundry.org<mailto:sipx-users-boun...@list.sipfoundry.org>
>>> [mailto:sipx-users-boun...@list.sipfoundry.org<mailto:sipx-users-boun...@list.sipfoundry.org>]
>>> On Behalf Of Tony Graziano
>>>
>>> >>> This also occurred while using Cisco 2811 gateways. The Polycom
>>>>> does not
>>>>> >>> respond correctly when initiating the Hold, it does not send a
>>>>> PRACK when it
>>>>> >>> should. I had work
t;>>> >>> respond correctly when initiating the Hold, it does not send a
>>>> PRACK when it
>>>> >>> should. I had worked with polycom on this issue earlier this year
>>>> and they
>>>> >>> gave me
ld, it does not send a PRACK
>>> when it
>>> >>> should. I had worked with polycom on this issue earlier this year
>>> and they
>>> >>> gave me a patched version that they still have not released which is
>>> >>> 3.2.5.b. Seems
gave me a patched version that they still have not released which is
>> >>> 3.2.5.b. Seems to be coming up more and more on this list.
>> >>>
>> >>>
>> >>>
>> >>> From: sipx-users-boun...@list.sipfoundry.org
>> &g
his issue earlier this year and
> they
> >>> gave me a patched version that they still have not released which is
> >>> 3.2.5.b. Seems to be coming up more and more on this list.
> >>>
> >>>
> >>>
> >>> From: sipx-users-boun...@list.sipfoundr
px-users-boun...@list.sipfoundry.org
>>> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano
>>> Sent: Friday, November 04, 2011 10:09 AM
>>> To: Discussion list for users of sipXecs software
>>> Subject: Re: [sipx-users] Hold BUG on 4.4 usin
ipfoundry.org [mailto:
>> sipx-users-boun...@list.sipfoundry.org] *On Behalf Of *Tony Graziano
>> *Sent:* Friday, November 04, 2011 10:09 AM
>> *To:* Discussion list for users of sipXecs software
>> *Subject:* Re: [sipx-users] Hold BUG on 4.4 using HOLD on Polycom phones*
>>
users of sipXecs software
> *Subject:* Re: [sipx-users] Hold BUG on 4.4 using HOLD on Polycom phones**
> **
>
> ** **
>
> ok. I will see if I can reproduce in the lab and submit a tracker.
>
> On Nov 4, 2011 12:46 PM, "Kevin George" wrote:***
> *
>
> Soun
] Hold BUG on 4.4 using HOLD on Polycom phones
ok. I will see if I can reproduce in the lab and submit a tracker.
On Nov 4, 2011 12:46 PM, "Kevin George"
mailto:kevincgeo...@gmail.com>> wrote:
Sounds almost exactly like the issue I described in July. In my situation when
I pu
ok. I will see if I can reproduce in the lab and submit a tracker.
On Nov 4, 2011 12:46 PM, "Kevin George" wrote:
> Sounds almost exactly like the issue I described in July. In my situation
> when I put the (sip trunk) caller on hold, then resume, then hold again,
> then resume the call messes u
Sounds almost exactly like the issue I described in July. In my situation
when I put the (sip trunk) caller on hold, then resume, then hold again,
then resume the call messes up everytime. If I remove the moh config from
the polycom config manually, the problem doesn't occur.
I'm still running t
On 11/4/2011 9:50 AM, Tony Graziano wrote:
> Numerous firmware/bootrom versions, what I am seeing is using 4.4
> (latest) if someone calls in via siptrunk on internal, and puts the
> caller on hold (using the hold button) then resumes the call, the
> calls is stuck in CDR as ~mh~ while the call is
On 11/4/2011 9:50 AM, Tony Graziano wrote:
> Numerous firmware/bootrom versions, what I am seeing is using 4.4
> (latest) if someone calls in via siptrunk on internal, and puts the
> caller on hold (using the hold button) then resumes the call, the
> calls is stuck in CDR as ~mh~ while the call is
Numerous firmware/bootrom versions, what I am seeing is using 4.4
(latest) if someone calls in via siptrunk on internal, and puts the
caller on hold (using the hold button) then resumes the call, the
calls is stuck in CDR as ~mh~ while the call is resumed. Occasionally,
the call cannot be resumed,
15 matches
Mail list logo
