Summary:ASTERISK-05803: Transfer from Polycom 600 to Zap causes Internal Server Error
Reporter:wjchan (wjchan)Labels:
Date Opened:2005-12-08 13:16:07.000-0600Date Closed:2006-01-17 16:06:18.000-0600
Versions:Frequency of
Environment:Attachments:( 0) sip-debug-301.txt
( 1) xfer-debug.txt
Description:1. Someone calls in via Zap (TDM400P)
2. Polycom 600 answers
3. Polycom 600 transfers caller to analog phone on the same TDM400P
4. Polycom 600 returns Internal Server Error


See debug log
Comments:By: Andrew Lindh (andrew) 2005-12-08 14:47:06.000-0600

I get this too on SIP transfers....same polycom 600 with SIP 1.6.3 software. Just SIP to SIP, no outside calls needed. The transfering phone generates the message at the end of the transfer.

I'll attach a SIP debug if needed. But it looks like asterisk sends a second BYE to the transfering phone and the phone responds with Internal Server Error because the call is already over and gone.

I don't see the same error with cisco (but it's set up a little differently).

I'm running asterisk version SVN-branch-1.2-r7386M

By: Kevin P. Fleming (kpfleming) 2005-12-12 22:58:11.000-0600

The 'Internal Server Error' here is in response to a '104 BYE' message, but Asterisk never sent such a message (or the log doesn't show it).

By: Olle Johansson (oej) 2005-12-20 06:54:40.000-0600

Our SIP signalling is not very good in the case of SIP transfers, so this frequently happens with Polycom phones.

By: Matt O'Gorman (mogorman) 2006-01-17 16:05:34.000-0600

this bug causes no problems other than the cosmetic error message.  It would would require massive ammounts of work to get it fixed in 1.2.  There are people who are working on reworking the way chan_sip deals with transfers so that it does it correctly however they are not in the tree yet.