Updates for missing images and page order

Author: gtjoseph

docs/Deployment/Basic-PBX-Functionality/.pages

@@ -0,0 +1,7 @@
+nav:
+  - The-Most-Basic-PBX.md
+  - Registering-Phones-to-Asterisk.md
+  - Creating-Dialplan-Extensions.md
+  - Adding-Voice-Mail-to-Dialplan-Extensions.md
+  - Auto-attendant-and-IVR-Menus
+  - Making-a-Phone-Call.md

docs/Fundamentals/Asterisk-Architecture/Asterisk-Architecture-The-Big-Picture.md

@@ -10,16 +10,15 @@ Asterisk a big program with many components, with complex relationships. To be a
 An Asterisk System
 ==================
 
-AsteriskArchitecture800
+![](AsteriskArchitecture.png)
 
 Remember this is not an exhaustive diagram. It covers only a few of the common relationships between certain components.
 
-On this Page
-
-
 Asterisk Architecture
 =====================
 
+![](bigpicture.png)
+
 Asterisk has a **core** that can interact with many **modules**. Modules called channel drivers provide **channels** that follow Asterisk **dialplan** to execute programmed behavior and facilitate communication between devices or programs outside Asterisk. Channels often use **bridging** infrastructure to interact with other channels. We'll describe some of these concepts in brief below.
 
 The Core
@@ -83,6 +82,3 @@ Dialplan is the one main method of directing Asterisk behavior. Dialplan exists
 
 Dialplan can also call out through other interfaces such as [AGI](/latest_api/API_Documentation/Dialplan_Applications/AGI) to receive call control instruction from external scripts and programs. The [Dialplan](/Configuration/Dialplan) section of the wiki goes into detail on the usage of dialplan.  
 
-
-
-

docs/Getting-Started/.pages

@@ -0,0 +1,4 @@
+nav:
+  - Beginning-Asterisk.md
+  - Installing-Asterisk
+  - Hello-World.md

docs/Getting-Started/Installing-Asterisk/.pages

@@ -0,0 +1,4 @@
+nav:
+  - Installing-Asterisk-From-Source
+  - Alternate-Install-Methods
+  - Installing-Asterisk-on-Non-Linux-Operating-Systems

docs/Getting-Started/Installing-Asterisk/Installing-Asterisk-From-Source/.pages

@@ -0,0 +1,9 @@
+nav:
+  - What-to-Download
+  - Prerequisites
+  - Using-Menuselect-to-Select-Asterisk-Options.md
+  - Building-and-Installing-Asterisk.md
+  - Installing-Sample-Files.md
+  - Installing-Initialization-Scripts.md
+  - Validating-Your-Installation.md
+  - Exploring-Sound-Prompts.md

docs/Getting-Started/Installing-Asterisk/Installing-Asterisk-From-Source/Exploring-Sound-Prompts.md

@@ -5,16 +5,10 @@ pageid: 4817435
 
 Asterisk comes with a wide variety of pre-recorded sound prompts. When you install Asterisk, you can choose to install both core and extra sound packages in several different file formats. Prompts are also available in several languages. To explore the sound files on your system, simply find the sounds directory (this will be  */var/lib/asterisk/sounds** on most systems) and look at the filenames. You'll find useful prompts ("Please enter the extension of the person you are looking for..."), as well as as a number of off-the-wall prompts (such as "Weasels have eaten our phone system", "The office has been overrun with iguanas", and "Try to spend your time on hold not thinking about a blue-eyed polar bear") as well.
 
-
-
-
-
-
-!!! tip Sound Prompt Formats** Sound prompts come in a variety of file formats, such as **.wav** and **.ulaw** files. When asked to play a sound prompt from disk, Asterisk plays the sound prompt with the file format that can most easily be converted to the CODEC of the current call. For example, if the inbound call is using the **alaw** CODEC and the sound prompt is available in **.gsm** and **.ulaw** format, Asterisk will play the **.ulaw** file because it requires fewer CPU cycles to transcode to the **alaw
-    CODEC.  
+!!! tip Sound Prompt Formats
+    Sound prompts come in a variety of file formats, such as **.wav** and **.ulaw** files. When asked to play a sound prompt from disk, Asterisk plays the sound prompt with the file format that can most easily be converted to the CODEC of the current call. For example, if the inbound call is using the **alaw** CODEC and the sound prompt is available in **.gsm** and **.ulaw** format, Asterisk will play the **.ulaw** file because it requires fewer CPU cycles to transcode to the **alaw CODEC.
      You can type the command **core show translation** at the Asterisk CLI to see the transcoding times for various CODECs. The times reported (in Asterisk 1.6.0 and later releases) are the number of microseconds it takes Asterisk to transcode one second worth of audio. These times are calculated when Asterisk loads the codec modules, and often vary slightly from machine to machine.  To perform a current calculation of translation times, you can type the command **core show translation recalc 60**.
 
-      
 [//]: # (end-tip)
 
 

docs/Getting-Started/Installing-Asterisk/Installing-Asterisk-From-Source/Prerequisites/.pages

@@ -0,0 +1,6 @@
+nav:
+  - Checking-Asterisk-Requirements.md
+  - PJSIP-pjproject.md
+  - Building-and-Installing-DAHDI.md
+  - Building-and-Installing-LibPRI.md
+