Review Board 1.7.16


Default state of 'meetme' hints should be Idle instead of Unavailable

Review Request #2569 - Created May 28, 2013 and updated

Leif Madsen
1.8
ASTERISK-21828
Reviewers
asterisk-dev
file, mjordan, mmichelson
Asterisk
In Asterisk 1.8, we have an issue where on startup the default device state of 'meetme' hints is Unavailable. Ideally this should be 'Idle'. We've changed the code to make the default state NOT_INUSE instead of INVALID.

Also of note, this is a dynamic conference room via the 'd' option.

e.g.

exten => 100,1,MeetMe(fancyroom,1dqM)
Restarted Asterisk, noted the state was what we wanted.
Review request changed
Updated (May 28, 2013, 1:23 p.m.)
  • In Asterisk 1.8, we have an issue where on startup the default device state of 'meetme' hints is Unavailable. Ideally this should be 'Idle'. We've changed the code to make the default state NOT_INUSE instead of INVALID.

    In Asterisk 1.8, we have an issue where on startup the default device state of 'meetme' hints is Unavailable. Ideally this should be 'Idle'. We've changed the code to make the default state NOT_INUSE instead of INVALID.
    
    Also of note, this is a dynamic conference room via the 'd' option.
    
    e.g.
    
    exten => 100,1,MeetMe(fancyroom,1dqM)
Updated information to state that this is a dyanamic conference room.
Posted (May 30, 2013, 9 a.m.)
I'm not really happy with this change because for non-dynamic conference rooms it now lies. I think a better option would be to be able to specify whether to treat the conference room as dynamic or not. The returned value would then reflect the truth for both static and dynamic.

https://reviewboard.asterisk.org/ runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to asteriskteam@digium.com.