This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| userdoc:tt_ast_startup [2012/04/23 10:54] – droemel | userdoc:tt_ast_startup [2013/04/20 09:27] (current) – droemel |
|---|
| originate local/ast-startup extension s@asterisk-startup = yes</code> | originate local/ast-startup extension s@asterisk-startup = yes</code> |
| |
| In this example "originate" calls the local (dummy) extension "ast-startup", it automatically answers and calls extension "s" in context "asterisk-startup" (don't forget the " = yes" at the end of the line). | In this example "originate" calls the local (dummy) extension "ast-startup", it automatically answers and calls extension "s" in context "asterisk-startup" (don't forget the " = yes" at the end of the line :-)). |
| |
| \\ | \\ |
| \\ | \\ |
| For IP-phones with custom lamps (hints) it can help a lot to reduce the "Subscription Timer" (for BLFs) to 120 sec, otherwise it can take a long time until the lamp states will be refreshed after an Asterisk restart. | For IP-phones with custom lamps (hints) it can help a lot to reduce the "Subscription Timer" (for BLFs) to 120 sec, otherwise it can take a long time until the lamp states will be refreshed after an Asterisk restart. |
| | |
| | **Update:** At least Asterisk 1.6.2 + 1.8.x already store the custom device-states in AstDB automatically! |
| | |
| | database show CustomDevstate |
| | /CustomDevstate/My-custom-lamp : NOT_INUSE |
| | /CustomDevstate/mystate : NOT_INUSE |
| | |