<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Issue is we don't handle progress and progress media differently, maybe we should. The message is however harmless, but annoying and should probably be dealt with a bit better. Patches welcome.<div><br></div><div>Mike</div><div><br><div><div>On Aug 13, 2009, at 9:04 PM, Moises Silva wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Yes, agreed, but there is no point in sending a WARNING since is a normal condition, therefore should not even try to change the state of the channel.<br><br><div class="gmail_quote">On Thu, Aug 13, 2009 at 7:57 PM, Mathieu Rene <span dir="ltr"><<a href="mailto:mrene_lists@avgs.ca">mrene_lists@avgs.ca</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word">It probably just VETO it so it avoid sending SWITCH_MESSAGE_INDICATE_PROGRESS again since the call is already making progress from the core's point of view?<div> <br><font color="#888888"><div> <span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word"> <div><span style="font-size:12px"><div>Mathieu Rene</div><div>Avant-Garde Solutions Inc</div><div>Office: + 1 (514) 664-1044 x100</div><div>Cell: +1 (514) 664-1044 x200</div><div><a href="mailto:mrene@avgs.ca" target="_blank">mrene@avgs.ca</a></div> <div><br></div><div><font class="Apple-style-span" color="#888888"><span class="Apple-style-span" style="font-size: medium;"><font class="Apple-style-span" color="#000000"><br></font></span></font></div></span></div></div></span></div></font><div><div><div></div><div class="h5"><div>On 13-Aug-09, at 11:02 AM, Moises Silva wrote:</div><br></div></div><blockquote type="cite"><div><div> </div><div class="h5"><div class="gmail_quote">On Wed, Aug 12, 2009 at 7:19 PM, Brian West <span dir="ltr"><<a href="mailto:brian@freeswitch.org" target="_blank">brian@freeswitch.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Well you really can't ignore it... it happens with our ISDN stack<br> too. Thats what the VETO handles.<br> <font color="#888888"><br> /b<br> </font><div></div></blockquote><div><br></div><div>You lost me. What do you mean we can't ignore it? the way I see it, sure we can and we should.</div> <div><br></div><div>Currently that warning comes from the on_ringing() callback which blindly attempts to move the state of the zap channel to ZAP_CHANNEL_STATE_PROGRESS, even when the state may be already ZAP_CHANNEL_STATE_PROGRESS_MEDIA (which means on_proceed() was called first). </div> <div><br></div><div>As I see it, the VETO warning is more an aid to the programmer so you quickly realize your doing a useless state change, which should be fixed. In this case, the fix is simply checking the state of the channel before trying to move it to progress, and don't even try to move it if already in progress with media.</div> <div><br></div><div> -- </div></div>Moises Silva<br>Software Developer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a><br> </div></div></blockquote></div></div></div></blockquote></div><font class="Apple-style-span" color="#006312"><br></font></blockquote></div><br></div></body></html>