[asterisk-dev] [Code Review] 4379: Example configuration scenario - Super Awesome Company: Phase 1 - Patch 1

Matt Jordan reviewboard at asterisk.org
Tue Jan 27 14:34:50 CST 2015


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4379/#review14320
-----------------------------------------------------------



/branches/13/configs/examples/super_awesome_company/asterisk.conf
<https://reviewboard.asterisk.org/r/4379/#comment24807>

    Let the bikeshedding commence!
    
    I would leave this commented, and let the user determine the verbosity through their console.



/branches/13/configs/examples/super_awesome_company/asterisk.conf
<https://reviewboard.asterisk.org/r/4379/#comment24808>

    Red blobs



/branches/13/configs/examples/super_awesome_company/extensions.conf
<https://reviewboard.asterisk.org/r/4379/#comment24810>

    I know '=' is the same as '=>', but I (for some reason) still prefer '=>' in dialplan.
    
    I'm not sure why.



/branches/13/configs/examples/super_awesome_company/extensions.conf
<https://reviewboard.asterisk.org/r/4379/#comment24809>

    I wouldn't put subroutines into their own contexts. That feels like bad ol' macros to me.
    
    Since these have context only inside Internal, I'd place them there, and name the extensions based on their intended use:
    
    exten => dial_internal_exten,1,Verbose(...)
    
    etc.



/branches/13/configs/examples/super_awesome_company/extensions.conf
<https://reviewboard.asterisk.org/r/4379/#comment24824>

    I would go ahead and play either the 'busy' or 'unavailable' prompt, based again on the DIALSTATUS.
    
    That may cause you to want to rethink whether or not invoking Voicemail should be in a separate GoSub.



/branches/13/configs/examples/super_awesome_company/extensions.conf
<https://reviewboard.asterisk.org/r/4379/#comment24811>

    Spacing here looks different than in other extensions.



/branches/13/configs/examples/super_awesome_company/logger.conf
<https://reviewboard.asterisk.org/r/4379/#comment24812>

    My suggestion:
    
    console => verbose,notice,warning,error
    
    messages => notice,warning,error
    full => debug,verbose,notice,warning,error
    security => security



/branches/13/configs/examples/super_awesome_company/modules.conf
<https://reviewboard.asterisk.org/r/4379/#comment24813>

    There is no Queue yet, so I'd remove it.



/branches/13/configs/examples/super_awesome_company/modules.conf
<https://reviewboard.asterisk.org/r/4379/#comment24814>

    While Stasis is awesome, we aren't using it yet. I'd remove it.



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24815>

    Clean up the blobs



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24817>

    Put comments in where you expect people to replace things with their system. NAT settings would be one place where people will need to change the values.



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24816>

    I'd come up with a consistent 'line break' scheme. Some of these continue on past the title, some do not.
    
    They should all be the same length.



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24819>

    For the endpoint, I would also set:
    
    rtp_symmetric=yes
    force_rport=yes
    rewrite_contact=yes
    dtmf_mode=rfc4733



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24818>

    I'd use:
    
    allow=!all,g722,ulaw
    
    And remove the disallow. Single line configurations that aren't dependent on ordering FTW.



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24820>

    I'd rename these to:
    
    auth-basic
    
    aor-basic
    
    Since they are supposed to generally accompany 'endpoint-basic'



/branches/13/configs/examples/super_awesome_company/pjsip.conf
<https://reviewboard.asterisk.org/r/4379/#comment24821>

    For "good practices", I'd use the domain of the company as the 'context'/'domain' of the voicemail:
    
    mailboxes=107 at sac
    
    (Or whatever it happens to be)



/branches/13/configs/examples/super_awesome_company/voicemail.conf
<https://reviewboard.asterisk.org/r/4379/#comment24822>

    Change this to the domain of the company



/branches/13/configs/examples/super_awesome_company/voicemail.conf
<https://reviewboard.asterisk.org/r/4379/#comment24823>

    All of them should have VoiceMail pins


- Matt Jordan


On Jan. 27, 2015, 1:15 p.m., rnewton wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/4379/
> -----------------------------------------------------------
> 
> (Updated Jan. 27, 2015, 1:15 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> One of things discussed at the last AstriDevCon was better documentation (for everything!), but in particular, we mentioned needing some example configurations that pertain to a real-world scenario. That is, as opposed to the current "sample" files which are sort of all over the place at this point.
> 
> This patch proposes a basic and minimal configuration of Asterisk to satisfy the requirements for the first phase of Super Awesome Company's implementation of Asterisk.
> 
> I will submit four separate patches for the first phase, so that we don't have to review the entire thing all at once. This review is for the first patch.
> 
> Who is Super Awesome Company? See https://wiki.asterisk.org/wiki/display/AST/Super+Awesome+Company
> 
> For the first patch, I am attempting to satisfy the below requirements. The patch does not include a new make target, as I believe Matt Jordan offered to handle that.
> 
> SAC requires:
> 
>     * PJSIP connectivity for all employee desk phones.
>     * The ability for employees to call one another inside of the office.
>     * Voicemail boxes for each of the employees.
> 
> "Basic" configuration
> 
> We want SAC to have a clean system. That means:
> 
>     * No 'autoload' in modules.conf. Explicitly load a basic configuration. If SAC doesn't need the module, don't load it.
>     * Every module loaded should have a configuration file that is appropriate for it. This includes all the 'core' things that need configuration.
> 
> pjsip.conf
> 
>     * A PJSIP configuration for their desk phones. Assume every endpoint that is a phone has:
>         * A voicemail mailbox that they can subscribe to
>         * A hint for their device
>         * Note that the PJSIP configuration should adhere to best practices. That means MAC addresses for device names, etc.
> 
> extensions.conf
> 
>     * A safe dialplan for intra-company communication. This should be templated out so that it is trivial to add additional devices (use pattern matching/pattern matching hints, etc.)
>     * Receiving a Busy/Unavailable should result in going to VoiceMail
>     * A user should be able to dial something and get to their VoiceMailMain without having to enter in their extension number 
>     * Note that mapping of MAC address endpoints to extension numbers should be done in some fashion that is easily extensible.
> 
> voicemail.conf
> 
>     * Set up mailboxes for every person in SAC. Assign 'default' pins. Create reasonable basic settings.
>     * Do not set up e-mail or pager addresses.
> 
> 
> REVIEW?
> 
> Please, if possible look at this from a few angles:
> 
>  * Use the configuration, configure a couple phones and call between them. Leave voicemails and retrieve them.
>  * Have I created any security issues?
>  * Is my dialplan easy to understand?
>  * Could anything be done more efficiently without making it over-complicated?
>  * Have I over-complicated anything?
>  * Are there any critical settings I'm missing from any of the files?
> 
> A couple, more specific questions:
> 
>  * We have sample configs in /configs/samples; what directory do we want these configurations in? (I used /configs/examples for now, but I don't really like it)
>  * We have the make target "make samples" for the current samples; what do we want for these new configs?
> 
> 
> Diffs
> -----
> 
>   /branches/13/configs/examples/super_awesome_company/voicemail.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/pjsip.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/musiconhold.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/modules.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/logger.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/indications.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/extensions.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/asterisk.conf PRE-CREATION 
>   /branches/13/configs/examples/super_awesome_company/README PRE-CREATION 
> 
> Diff: https://reviewboard.asterisk.org/r/4379/diff/
> 
> 
> Testing
> -------
> 
> Setup Asterisk with configuration, connected up three phones using the first three users. Made calls between them all, left voicemails and retrieved them with all users. Verified MWI working with all phones.
> 
> 
> Thanks,
> 
> rnewton
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150127/ac6a0129/attachment-0001.html>


More information about the asterisk-dev mailing list