On 5/20/2011 1:25 PM, Matt White wrote:
>>> "Matthew Kitchin (public/usenet)" 05/20/11 2:06 PM >>>
>As polite a bump request as possible to convey in an email :)
>This is continuing to happen today. Verizon is looking at their end,
and not seeing anything so far. Is there anyone that can >help me
decipher what this this means, I would be extremely appreciative.
This looks like the dreaded 482 loop issue with Polycom firmware 3.2.3
but your trace shows version 3.2.5
Maybe this is a regression in the polycom firmware.
But this bug affect remote workers where latency caused multiple
invites and the polycom didn't like it.
And I can see in your trace that sipx is not getting the response
quick enough. He sends multiple invites to the phone before he gets
the response back.
So it does look like your having latency issues and the 3.2.3 bug is
back in 3.2.5
Thank you for the quick response.
They are running 3.2.5. I don't have the captures to show it, but the
exact same thing was happening when the phones were on 3.2.4. I'm not
sure if that is relevant or not.
I am not experiencing this at any other sites. I am forwarding from a
phantom extension to another handset at this site. Would this bug/issue
be more likely to occur with this forward in place? I am not doing this
type of forward at any other sites.
I am definitely familiar with the 3.2.3 bug. We experienced that
immediately upon testing that firmware.
What would you recommend I try? Thank you again for the quick response.
-M
_______________________________________________
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/
