History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SFS-85
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Michael Durham
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
SIPfoundry Infrastructre

Transfering calls causes Polycom 650 to hard lock and reboot.

Created: 2008-03-20 21:13   Updated: 2008-03-20 21:13
Component/s: www.sipfoundry.org
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
sipXconfig (3.10.0-012060 2008-03-17T05:15:59 ecs-centos5)


 Description  « Hide
This is a fresh install of SipX 3.10 in a test lab being used as evaulation for a potential production rollout.

Environment
SipX 3.10. No issues during install. Machine boots clean with no errors.
Polycom Soundpoint 650
    Boot ROM versions: 3.2.3, 3.2.3b, 4.0.0
    SIP versions: 2.1.2, 2.2.0, 2.2.2, 3.0.0
Counterpoint X-Lite 3.0 for Windows
AAstra 57i with SIP version 2.2

The Polycom is using the standard and unaltered phone profile in SipX.

The problem: Trying to transfer a call from the Polycom to any of the other extension results in the Polycom not "letting go" of the call. Phone may hang. Pressing any of the soft keys results in the phone hard locking and reboot.

Sequense of events:
AAstra, X-lite, or Polycom (extension #1) calls Polycom (extension #2)

Polycom (extension #2) answers

Hit Transfer button or softkey on Polycom (extension #2).

Dial other AAstra, X-Lite or Polycom (extension #3)

Phone (extension #3) rings and answers

Hit transfer button or softkey on Polycom (extension #2) and nothing happens. Extension #1 is still connected and shows as being "on hold" to extension #2. Extension #2 shows being connected to extension #3. Hitting any key on the Polycom extension #2 has no effect __except__ the conference key. Hiting the conference key while trying to transfer will cause the Polycom to immediatly hard lock and reboot. Hang up Polycom on extension #2 and extensions #1 and #3 will hang up.

I've tried every supported combination of Boot and SIP software on the Polycom phones all the way to Boot 4.0.0 with SIP 3.0.0 with no change. It does not matter which order the SIP devices are used. If a Polycom is trying to transfer then the process fails.

Ok, here's the rub. I've connected this entire lot to the Switchvox demo server (demo2.switchvox.com) and EVERYTHING works as expected. No issues what so ever. This process is repeatable and predictible. I can provide further info if necessary.

Mike
msdurham@maa.com


 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.