| Summary: | ASTERISK-06989: Polycom 601 SP 500 Internal Server Error in response to SIP Notify messages | ||
| Reporter: | HY (harry8) | Labels: | |
| Date Opened: | 2006-05-17 11:01:56 | Date Closed: | 2011-06-07 14:02:48 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Transfers |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This thread is similar to ID 0006623. When I try to transfer a phone call (not a blind transfer), the Polycom 601 Phones generates a 500 Internal Server Error. The result for the listening side is that there is no tone when the call is transfer so it sounds like the call is dropped. I am using 1.6.5 firmware for the Polycom and 1.2.7.1 for Asterisk. I can reproduce this problem all the time, so I am not sure if this is a problem with Asterisk or the Polycom. My guess is it is some configuration on the Polycom but i have no idea what. | ||
| Comments: | By: Serge Vecher (serge-v) 2006-05-17 11:09:54 can you please test with latest trunk (rev > 27000)? By: John Laur (gork) 2006-05-17 11:20:33 This is a question out of curiosity; what do you mean "Tone when the call is transferred" ? Are you using the polycom's transfer feature or asterisk's star code to perform the transfer? I ask because I'd very much like to have the polycom's play a small indication to the person to whom a call is being transferred to indicate when the transfer has taken place, ie: Operator says, for example, "I'm transferring the call to you now.." Operator presses transfer button to complete transfer. Recipient hears a beep to indicate they are talking to the transferred caller. This is a feature on some SIP phones but I have not found that it is possible to configure polycom's for this behavior. By: Olle Johansson (oej) 2006-05-17 11:20:51 If the polycom sends that error, the problem is in the Polycom. Can you please ask them what's causing this error message? By: Russell Bryant (russell) 2006-05-19 12:08:44 Since this problem appears to be in the Polycom, I'm suspending this issue for now. If you find out that Asterisk is doing something wrong that leads to this, feel free to open a new issue. Thanks | ||