I'm mighty certain it is:

http://track.sipfoundry.org/browse/XX-9699

If so, no amount of staring at it will fix it for you in 4.2.

On Thu, Aug 4, 2011 at 6:11 PM, Jeff Gilmore <[email protected]> wrote:

> Thanks Josh.  Not sure that applies, though, since I am not running a 4.4
> version and that looked like a new bug in 4.4.  I will eventually update to
> 4.4, but I have had so much user downtime lately due to ITSP issues, that I
> just can't face it!
>
> The behavior on the Polycom looks like what happens when a second call
> comes in when you are already on the line, but of course, there is only the
> one call.
>
> Anyone interested in looking at a trace?
>
> Thanks,
>
> Jeff
>
> On Aug 4, 2011, at 3:32 PM, Josh Patten wrote:
>
> This may be related to a bug regarding PRACK:
> http://track.sipfoundry.org/browse/XX-9699
>
> the only suggestion I have at this point is to upgrade to the latest 4.4
> release
>
>
> On Thu, Aug 4, 2011 at 1:05 PM, Jeff Gilmore <[email protected]> wrote:
>
>> I have a problem that has cropped up recently.  My extensions are mostly
>> served by SPA2102 ATA devices, but on a particular extension, I have both a
>> Polycom IP320 and an SPA2102 ATA registered.  Until recently, it worked
>> great and I could pick up incoming calls on either one.
>>
>> Now, if I receive an incoming call and try to pick it up on the Polycom,
>> it seems to grab the call, but the phone displays <answer><ignore><more> ,
>> and pressing answer does not pick up the call.  The call stops ringing, but
>> I get dead air on the Polycom.  It used to just pick up.  The SPA2102 picks
>> up calls just fine.
>>
>> This only happens with calls that come through my ITSP--local calls work
>> fine.  On these outside calls, on the caller's phone, it stops giving a ring
>> tone and acts like it has been picked up, but they get dead air.  I see the
>> callerID of the caller appear on the Polycom.
>>
>> There were some recent changes caused by problems on my ITSP's side.  They
>> moved my account to a new proxy  server and a new SBC, so I had to change
>> the IP address in my Sipx gateway configuration.  I am running Polycom
>> 3.1.3.0439 firmware, but that has not changed.  I am running sipx 4.2.1.
>>
>> Any suggestions of what might be wrong?  I have traces of both a (failed)
>> Polycom call and a (successful) SPA2102 call if you are willing to take a
>> look at them.
>>
>> Thanks!
>>
>> Jeff
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> Josh Patten
> eZuce
> Solutions Architect
> O.978-296-1005 X2050
> M.979-574-5699
>  _______________________________________________
> 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/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.326.5325

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Contract Customers:
http://support.myitdepartment.net

<http://support.myitdepartment.net>Blog:
http://blog.myitdepartment.net

Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4

Ask about our voip fax services!
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to