PBX

Quick Overview of the Setup

• Create a domain to match the domain used for registering phones
• Create an extension under Accounts -> Extensions
• Register the phone to the extension. The extension number is the username for the end point.
• Test the phone by dialing the music on hold number *9664
• Setup an inbound route from Sky DANCE to the PBX.
• Validate the settings on the outbound route from Sky DANCE.
• Test

Menu: Advanced->Domains

Every Sky PBX instance will have its own domain. This can be the IP address or the name which is used when an extension will register to the PBX.

Menu: Accounts->Extensions

For a phone system to be useful, local extensions need to be configured. The first time the Extensions page is viewed, there will be no extensions listed. Click on the + next to the list in order to add an extension.

"Effective Caller ID" information is shown within your organization, "Outbound Caller ID" information will be seen by those receiving outside calls.

Fill in Extension in order to get a basic phone up and running. It is suggested that a system administrator complete the following: Extension (according to the numbering scheme used in the implementation) User list (assign a user to each extension – this allows the end-user to log into the SkyPBX web GUI and check voicemails, faxes and so on via the web. This does not have to be done immediately.) Voicemail options (e.g. have voicemail sent to a designated email address.) (editors: Toll allow is a new option – where is this used? I don’t have this set on my system yet my calls all still work)

• The range entry allows more than one extension to be created at a time. This would probably be most useful when doing automated telephone provisioning (note to editors – you’ll need to flesh this out as we now have a provisioning section on this page and I have no idea how to use it).

Save each configured extension (the save button is at the bottom of the GUI). When the save is complete, the screen is returned to the list of extensions. Click on the extension just created. Click on the password field to reveal the current password directly below the field. Note the password is displayed because it will be needed to configure a telephone to negotiate with SkyPBX. At this point, it might be prudent to test a telephone negotiating with successfully SkyPBX so that further testing can be performed, ensuring that the following are also properly configured: IP address of SkyPBX (the phone might know this as the SIP server) Extension (the extension number is the username for the phone) Password for the extension

Read the manual for your IP phone or soft phone for more information. 

Once the phone is connected you can test it by dialing *9664 which is a code for music on hold. To use a phone to call somewhere other than music on hold or another extension, configuration of the Sky_Dance entry in the Dialplan Manager is required. (See more information about call provisioning and routing under DialPlan)

Setup an Inbound Route from Sky DANCE

There are 2 steps to create an inbound route from Sky DANCE for Sky PBX. (This assumes you already have an inbound route setup in Sky DANCE that can accept traffic) 1. For inbound DIDs, create a "Called Pre Translation" entry in Sky DANCE which routes a call to the PBX using a <9999> prefix

Example: 30550022* 9999665001 - would route to PBX1 with the default setup.

If you have more than 1 PBX planned, you will need to plan on adding 2 prefixes in the Called Pre Translation table with the following format: <Sky PBX application prefix - 9999><4 digit PBX ID><Number within the Dialplan Manager for that PBX>

2. Edit the Send_to_SkyPBX entry in the Dialplan Manager to change the condition to be more specific - ie. if the prefix from Sky DANCE was 99990001 - you could just match on the 0001. To add other PBX entries you can just duplicate the Send_toSkyPBX entry to make a Send_toSkyPBX2,3 4 etc.and edit the domain name to match the new domain for the new PBX and also to change the transfer action to route to the new context.

Setup an Outbound Route to Sky DANCE

1. Edit the Send_to_SkyDance entry to modify the sip_h_X-Rg-In=3000,1000;1;1000 entries to match your setup. They should match the inbound resource group and partition used for routing the call to this PBX.

Voicemail to email

For voicemail to email configure SMTP server settings in Advanced ->Default Settings. Configure the destination email account in the settings for each extension. SkyPBX does not use an MTA (Message Transfer Agent eg. sendmail or postfix). Instead SkyPBX uses a PHP script that acts as an SMTP client and connects to the SMTP server using the account and password specified by the system and/or extension administrator. As a result, there are no queues or logs where message sent or failed can be viewed. However, if the php script was executed (whether the voicemail was successfully sent or not) there will be a file in /tmp called voicemailtoemail.txt. If voicemailtoemail.txt was created and the voicemail was not received as an email, there could have been two possible results from the action. One possible result was that the script may have executed but it did not successfully negotiate with the SMTP server. Alternately, the script successfully sent the voicemail; however, the destination email account was incorrectly assigned in the settings. If the file is not present in /tmp then it is likely that the voicemail file and directory permissions to /var/www/Skypbx/secure are incorrect. The voicemail script is v_mailto.php. If it is inaccessible to Sky DANCE then the function will not run and the file in /tmp will not be created. .