| Summary: | ASTERISK-02825: SIP channel rings after answer on some calls from Polycom | ||
| Reporter: | Andrew Lindh (andrew) | Labels: | |
| Date Opened: | 2004-11-15 22:46:36.000-0600 | Date Closed: | 2004-11-16 08:17:06.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This stops some calls from working, but not all calls on all phones...so it's almost major (for me anyway). After updating to the current CVS with (chan_sip.c version>=1.564) some of my calls no longer work. I'll place a call between two SIP phones (same system) and answer the call. The calling phone will just keep "inging on the speaker as if the call is not connected....but it did connect and the display timers are running and I can hear speech from the other phone! But the caller is still hearing ringing (NOT in-band audio rinning). This happens on some, but not all calls between phones. It only seems to happen on calls FROM Polycom to any SIP phone (not ZAP channels), but not every call. It seems to be about 1 out of every 2 to 4 calls. Repeated calls FROM cisco, grandstream, zyxel or other devices do not seem to have this issue. I know when it's going to happen because I hear a double ringing on the calling phone for the first ring. If the calling phone (still hearing the ringing) puts the call on hold the remote party hears MOH....If the call is then resumed it works correctly and there is two way audio. If I back off to chan_sip.c version 1.563 things work again for every call (10 out of 10). I know this seems like a Polycom issue (and it may be), but it was working fine before! ****** ADDITIONAL INFORMATION ****** Polycom SIP software is current version 1.3.1 Affects both Polycom SoundPoint IP 500 and 600 chan_sip.c revision 1.563 and older work, current verion 1.566 does not | ||
| Comments: | By: Brian West (bkw918) 2004-11-15 22:53:14.000-0600 sipdebug and your sip.conf would be helpful. By: Mark Spencer (markster) 2004-11-15 22:54:43.000-0600 What is your inband progress setting? By: Mark Spencer (markster) 2004-11-15 22:58:09.000-0600 Try latest CVS, 1.567, too. By: Andrew Lindh (andrew) 2004-11-15 23:12:57.000-0600 progressinband is not set (commented out). So it's default (assume that's =no?). chan_sip.c 1.567 seems to have fixed the problem....that's why I listed version numbers in the bug reports....20 out of 20 calls worked this time with 1.567. I guess I should have just gone to sleep and updated CVS in the morning... Thanks! By: Mark Spencer (markster) 2004-11-15 23:16:37.000-0600 Nah, I didn't make it until I saw your bug report. | ||