<div>Hi Keivn,</div>
<div> </div>
<div>I see. That means after "183 Session Progress", it is the PBX's job to indicate future progress for current session, for example, PBX can play MOH to endpoint.... Meanwhile, PBX shall not send "180 Ringing" after 183 to let endpoint generate ringback tone, and endpoints usually would ignore 180 after 183 as well.
</div>
<div> </div>
<div>-Jerry<br><br> </div>
<div><span class="gmail_quote">On 1/19/06, <b class="gmail_sendername">Kevin P. Fleming</b> <<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Guo-Wei Chiuan wrote:<br><br>> My goal is to indicate RINGING upon a caller channel in RING state by using
<br>> "180 Ringing" after 183 is ent.<br>> However, according to source codes, after 183 is sent(in my case, due to<br>> Playback() is done), Asterisk would not send "180 Ringing". That is what I
<br>> am trying to figure out.....<br>><br>> Maybe I shall look up RFC3960. Any ideas?<br><br>Once '183 Session Progress' is sent, it is not useful to send '180<br>Ringing' any longer... the 183 message informs the endpoint that future
<br>progress indications for this session will be provided inband via the<br>audio stream. Most (if not all) SIP endpoints would ignore any 180<br>received after a 183 anyway.<br>_______________________________________________
<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">Easynews.com</a> --<br><br>Asterisk-Dev mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br>