Mine is a relatively high end Cisco. I don't believe the problem is my switch. 
-----Original Message-----
From: Dragan Jurkovic <[email protected]>
Sender: [email protected]
Date: Thu, 16 Jun 2011 16:00:26 
To: <[email protected]>; Discussion list for users of sipXecs 
software<[email protected]>
Subject: Re: [sipx-users] Problem with internal calls Polycom to Polycom
 -PRACK missing

For me it happens even if phones are plugged directly to Netgear
GS748TP switch. When I restarted the switch problem went away for a
while, but it seems it is back. Could it be faulty switch?

Dragan

On Thu, Jun 16, 2011 at 3:27 PM, Matthew Kitchin (usenet/public)
<[email protected]> wrote:
> Me too!
> It happened on 4.2.1 with pcom firmware 3.2.4 and still with 4.4.0 and 3.2.5. 
> After going through some traces, we replaced an old cat 5 drop with several 
> cross connects with a cat 6 home run  it seems. To have helped.
> -----Original Message-----
> From: Tony Graziano <[email protected]>
> Sender: [email protected]
> Date: Thu, 16 Jun 2011 12:29:05
> To: Discussion list for users of sipXecs 
> software<[email protected]>
> Reply-To: Discussion list for users of sipXecs software
>        <[email protected]>
> Subject: Re: [sipx-users] Problem with internal calls Polycom to Polycom -
>  PRACK missing
>
> On Thu, Jun 16, 2011 at 12:20 PM, Dragan Jurkovic <[email protected]> wrote:
>> Hi all,
>>
>>  I have a strange problem with internal calls between Polycom phones
>> (IP 331 boot rom 4.1.3, SIP 3.2.4.B). sipXecs is 4.4 with all latest
>> patches applied.
>> When calling from one station to another an attempt to answer incoming
>> call will result in following: screen still shows Ignore, Answer, More
>> options, ringing stops, and caller's phone will show that call is
>> answered. The only way  to stop the call on called phone is to go to
>> reject option. This happens randomly but very often.
>> Attached logs show that PRACK is not issued in failed call case.
>>
>>  Is this Polycom or sipXecs issue? Has anyone stumbled on this.
>>
>> What is more puzzling - we have remote site with identical
>> configuration and this never happens there!
>>
> I have also seen this with firmware 3.2.5 on a limited basis but have
> not tracked it down. It also happens on incoming trunk calls. In the
> one instance where it is happening we're in the process of replacing a
> crappy switch though, and I wanted to get that out of the way before I
> pointed fingers.
>_______________________________________________
> 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/
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to