bump...   Anybody using MeetMe hints for busy-lamps on phones?  Anyone seeing this issue?<br><br><div class="gmail_quote">On Mon, Sep 28, 2009 at 11:08 AM, Paul Dugas <span dir="ltr">&lt;<a href="mailto:paul@dugasenterprises.com">paul@dugasenterprises.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I suspect the issue I&#39;m having is more specific to the MeetMe app but<br>
that&#39;s just a guess.  app_meetme.c (in 1.6.1.6) calls<br>
<br>
  ast_devstate_changed(AST_DEVICE_INUSE, &quot;meetme:%s&quot;, conf-&gt;confno)<br>
<br>
when the first caller enters a conference and<br>
<br>
  ast_devstate_changed(AST_DEVICE_NOT_INUSE, &quot;meetme:%s&quot;, conf-&gt;confno)<br>
<br>
when the last caller leaves.  Running &quot;core show hints&quot; shows the<br>
meetme:600 as Status:Unavailable most of the time after a conference<br>
ends.  Occasionally, it&#39;ll show Status:Idle.  I guess I&#39;m wondering<br>
where the hint could be getting changed to Unavailable since it<br>
doesn&#39;t look like the MeetMe app ever sets them this way.<br>
<br>
I wonder if it&#39;s a result of my using an extension pattern.  AFAIK,<br>
the 600@dialtone hint is created from the _60X@dialtone pattern when<br>
the first station subscribes.  I wonder if these polycom stations are<br>
unsubscribing or timing out thus removing the pattern-generated hint.<br>
I&#39;ll try a statically configured hint to see if that&#39;s the issue.<br>
<br>
I also wonder if there&#39;s any logic elsewhere that would ever set the<br>
initial hint status for a meetme.  With a brief look at app_meetme.c,<br>
I don&#39;t see where it updates the device state except on join/leave.<br>
<font color="#888888"><br>
P<br>
</font><div><div></div><div class="h5"><br>
On Mon, Sep 28, 2009 at 9:24 AM, Danny Nicholas &lt;<a href="mailto:danny@debsinc.com">danny@debsinc.com</a>&gt; wrote:<br>
&gt; The routine ast_extension_states in main/pbx.c is set up (in 1.4.26.1) to<br>
&gt; return these values:<br>
&gt;<br>
&gt;       switch (devstate) {<br>
&gt;        case AST_DEVICE_ONHOLD:<br>
&gt;                return AST_EXTENSION_ONHOLD;<br>
&gt;        case AST_DEVICE_BUSY:<br>
&gt;                return AST_EXTENSION_BUSY;<br>
&gt;        case AST_DEVICE_UNAVAILABLE:<br>
&gt;        case AST_DEVICE_UNKNOWN:<br>
&gt;        case AST_DEVICE_INVALID:<br>
&gt;                return AST_EXTENSION_UNAVAILABLE;<br>
&gt;        case AST_DEVICE_RINGINUSE:<br>
&gt;                return (AST_EXTENSION_INUSE | AST_EXTENSION_RINGING);<br>
&gt;        case AST_DEVICE_RINGING:<br>
&gt;                return AST_EXTENSION_RINGING;<br>
&gt;        case AST_DEVICE_INUSE:<br>
&gt;                return AST_EXTENSION_INUSE;<br>
&gt;        case AST_DEVICE_NOT_INUSE:<br>
&gt;                return AST_EXTENSION_NOT_INUSE;<br>
&gt;        case AST_DEVICE_TOTAL: /* not a device state, included for<br>
&gt; completeness */<br>
&gt;                break;<br>
&gt;<br>
&gt; These come back &quot;in English&quot; as<br>
&gt; static const struct cfextension_states {<br>
&gt;        int extension_state;<br>
&gt;        const char * const text;<br>
&gt; } extension_states[] = {<br>
&gt;        { AST_EXTENSION_NOT_INUSE,                     &quot;Idle&quot; },<br>
&gt;        { AST_EXTENSION_INUSE,                         &quot;InUse&quot; },<br>
&gt;        { AST_EXTENSION_BUSY,                          &quot;Busy&quot; },<br>
&gt;        { AST_EXTENSION_UNAVAILABLE,                   &quot;Unavailable&quot; },<br>
&gt;        { AST_EXTENSION_RINGING,                       &quot;Ringing&quot; },<br>
&gt;        { AST_EXTENSION_INUSE | AST_EXTENSION_RINGING, &quot;InUse&amp;Ringing&quot; },<br>
&gt;        { AST_EXTENSION_ONHOLD,                        &quot;Hold&quot; },<br>
&gt;        { AST_EXTENSION_INUSE | AST_EXTENSION_ONHOLD,  &quot;InUse&amp;Hold&quot; }<br>
&gt;<br>
&gt; So a line Is Unavailable on 3 conditions, but only Idle on one; unless you<br>
&gt; tweak to make UNAVAILABLE equivalent to NOT_INUSE.  I don&#39;t know the<br>
&gt; ramifications if any of the tweak.<br>
&gt;<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: <a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a><br>
&gt; [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>] On Behalf Of Paul Dugas<br>
&gt; Sent: Sunday, September 27, 2009 5:31 PM<br>
&gt; To: Asterisk Users Mailing List<br>
&gt; Subject: [asterisk-users] MeetMe Hints<br>
&gt;<br>
&gt; I&#39;ve got hints setup for my MeetMe conferences like so:<br>
&gt;<br>
&gt;    exten =&gt; _60X,hint,MeetMe:${EXTEN}<br>
&gt;<br>
&gt; and they show up in &quot;core show hints&quot; like so<br>
&gt;<br>
&gt;    600@dialtone            : MeetMe:600            State:Unavailable<br>
&gt;   Watchers  1<br>
&gt;    _60X@dialtone            : MeetMe:${EXTEN}       State:Unavailable<br>
&gt;    Watchers  0<br>
&gt;<br>
&gt; I&#39;m wondering why they&#39;re Unavailable instead of Idle.  They go to<br>
&gt; &quot;State:InUse&quot; when active but usually return to Unavailable when the<br>
&gt; conference ends.  Occasionally they end up in InUse but not<br>
&gt; consistently.<br>
&gt;<br>
&gt; Anybody know why?<br>
&gt;<br>
&gt; Paul<br>
&gt; --<br>
&gt; Paul Dugas -- Computer Engineer -- Dugas Enterprises, LLC<br>
&gt; 522 Black Canyon Park, Canton GA 30114 USA<br>
&gt; <a href="mailto:paul@dugasenterprises.com">paul@dugasenterprises.com</a> -- +1.404.932.1355<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
&gt;<br>
&gt; AstriCon 2009 - October 13 - 15 Phoenix, Arizona<br>
&gt; Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
&gt;<br>
&gt; asterisk-users mailing list<br>
&gt; To UNSUBSCRIBE or update options visit:<br>
&gt;   <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
&gt;<br>
&gt; AstriCon 2009 - October 13 - 15 Phoenix, Arizona<br>
&gt; Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br>
&gt;<br>
&gt; asterisk-users mailing list<br>
&gt; To UNSUBSCRIBE or update options visit:<br>
&gt;   <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
&gt;<br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5">Paul Dugas -- Computer Engineer -- Dugas Enterprises, LLC<br>
522 Black Canyon Park, Canton GA 30114 USA<br>
<a href="mailto:paul@dugasenterprises.com">paul@dugasenterprises.com</a> -- +1.404.932.1355<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Paul Dugas -- Computer Engineer -- Dugas Enterprises, LLC<br>522 Black Canyon Park, Canton GA 30114 USA<br><a href="mailto:paul@dugasenterprises.com">paul@dugasenterprises.com</a> -- +1.404.932.1355<br>