search for: progessinband

...ng that Polycom's SIP implemenation does not currectly handle these responses. See: http://bugs.digium.com/view.php?id=3129 In the future it would help that instead of nitpicking some little low level technical detail you describe what your actual problem is, you would get more input that way. progessinband=yes means that the call progress WILL BE SEND INBAND, which in 99% of cases is not needed, and does not make sense. You are also wasting additinal resources because asterisk must generate progress tones too. On 12/11/06, Douglas Garstang < dgarstang@oneeighty.com> wrote: I have progressi...

I have progressinband=yes in sip.conf, but Asterisk sends a 180-Ringing to my polycom phones and then it also sends 183-Session Progress. That doesn't seem to make sense. Shouldn't Asterisk NOT send 180-Ringing if progressinband=yes ? Doug.

...finally tracked this down to several things: a) My SIP provider sends "183 Session Progress" and inband ringback prior to sending a "180 Ringing". b) The default sip.conf file that ships with asterisk suggests using "progressinband=no" for polycom phones. c) The "progessinband=no" setting prevents the "180 Ringing" from being forwarded to the phone if it is received after the "183 Session Progress". d) Called-Parity-ID appears to be only sent to the phone with "180 Ringing" and "200 OK" responses. # this the sequence of events...