This section helps you create extensions. After registration by default 100 extensions are activated while you can activate more in multiples of 100 anytime later. Extension Activation comprises 5 steps of Configuration.
Add New: You can press the Activate CheckBox & Activate using the Activate button. This just moves the extension from inactive to active mode with default properties, which can then be configured using the rest of the four tabs.
Created : This gives an overview of the extensions created. You can use search option to search and view specific extension data & edit them as mentioned below.
Export XML – This creates an XML File of all extensions which can be edited and imported directly to Com1 FXS.
Delete – This will move the active extensions to Inactive extensions.
Properties: This handles the basic properties of an extension.
Port: This identifies the port of an extension and does not get altered for life time.
Extension : By default the extension & port is the same till you choose to use flexible numbering. You can change the extension number from 1000 to 99999999 of any combination / digits.
Name – Name of the extension user, This name will be sent along with CLI in all internal calls for easy identification as well as get recorded in call billing software. It is advisable to avoid naming ext1, ext2 etc and enter real names.
Type – The extension can be of 3 types SIP,IAX or PAS(Public Address System), SIP is recommended for extensions as it is more widely supported than IAX. Choose PAS in case you are planning to connect SIP speakers for Public Address System.
Email – We recommend entering the original Email of the extension user as all reports including Daily Call Report, Voice mail pending Reports, Missed call reports or Forgot password etc … are all send to this mail id. Entering fictitious or same mail id for the same deprives the user for all the above listed features as well as many more unlisted powerful features that are being developed.
Class Of Service/Context – There are 3 Class of service for every extension.
Mobile Number – If not as critical as the Email, certain SMS related features are activated only from this data and hence recommended to give proper mobile number.
Call Group – This is grouping the extension for pickup group.
Pickup Group – Call Pickup code will work only within assigned Call Group. You can assign multiple Call Group for an extension and identified by comma separated.
Department – This helps you categorise the extensions based on the Departments like Sales, Service, Admin etc.
Features : This section is to assign access rights of various features and limits to every extension.
Voicemail – To allow/disallow voicemail facility for this extension.
Voice Logging – To allow/disallow conversation recording for this extension. If selected Yes all calls made & received by this extension will get recorded else no calls will get recorded. Generally senior executives extensions are barred from recording, however we recommend all calls be recorded and restrict access to play in the GUI for security reasons.
Mobile Extension – Otherwise referred as forking, shall hunt you in your mobile, home telephone line, alternative extension etc if your extension goes unanswered for a specific period of time say 30 sec.
Barge In – To allow/disallow someone to barge-in while the extension user is conversing with another call. Normally to be selected No for senior executives who should not be barged-in and ensure privacy
Allow DID – To allow/disallow external callers to reach you directly while the trunk is in Auto Attendant mode. Normally to be selected No for senior executives who should not be accessed by callers just by knowing the extension numbers.
Call Waiting – This fixes the number of calls an extension can handle at any point in time. Count of calls include internal as well as external calls. The caller will get engaged tone if the count exceeds or ringing tone if the count is within limits irrespective of your extension status being Busy / Free.
Dialling : This section helps you to assign authorised trunks for outward dialling & directory trunk choice for every extension. To know more about trunk grouping, read through the Outgoing section of Help menu.
Dial_0 – If the extension has 0 dialling access, all trunks not classified under reserved group can be accessed on random for outward dialling.
Directory Trunk Choice – The trunk option for Click to call, scheduled calls or any calls that needs to done in User module.
Trkgrp_80 – Assigning access rights to all trunk grouped under 80.
Trkgrp_81 – Assigning access rights to all trunk grouped under 81.
Trkgrp_82 – Assigning access rights to all trunk grouped under 82.
Trkgrp_83 – Assigning access rights to all trunk grouped under 83.
Trkgrp_84 – Assigning access rights to all trunk grouped under 84.
This section helps you create PRI trunks. Lot of care to be taken while entering as wrong entry may impact configuring the incoming calls.
Pilot Number – In spite of allotting many DID numbers to you, the operator will allot one number as Pilot number where the calls can be made to land if not configured for any incoming pattern.
Default CLI – In spite of allotting many DID numbers to you, there will be one CLI configured as default CLI which will be passed with calls unless CLI is configured for this trunk and extension under Outgoing → Trunk CLI Link
Starting Number – This is first number of the DID set allotted to you. Any wrong entry will impact incoming DID number creation.
DID_Digits – Normally it is between 3 to 8 depending upon the Operator & Exchange, Currently most of the operator gives full digits. Remember any wrong entry will impact incoming DID number creation.
DID_Nos – Normally the operator allots a 30 and above as DID. Remember any wrong entry will impact incoming DID number creation.
Type – You can either connect PCI based PRI cards or standalone external PRI to SIP gateways. If you choose to connect PCI based PRI cards then the following Dial Group Option will open up or else for gateway system will generate a SIP account to configure.
Dial Group – You can connect 8 PRI lines to COM1 IPPBX, you have to select groups serially starting from i1 – i8
You can edit / delete any PRI trunk created and a sample of PRI trunk creation is displayed below.
This section helps you create SIP trunks. Lot of care to be taken while entering as wrong entry may not register the account impacting both Incoming & Outgoing calls. SIP trunking is gaining more popularity , as it breaks not just Physical connectivity barrier but also need for any hardware interface. This uses the public IP networking than any physical wire that needs to be connected in other cases.
Operator – Name of the operator who is providing this trunk
DID Number – Applicable is only Yes is selected in the above option and configure the allotted number.
Host – The IP address / domain to which this account is mapped.
Port – Normally it is default SIP port 5060 which may vary to any other port based on service provider
Username – Provided by service provider for account authentication.
Password / Pin – Provided by service provider for account authentication.
Default CLI – Set CLI for outgoing call purposes, This is purely an operator supported feature and will work within allowed limit of the operator. Default CLI will be passed in the event of any unsupported entry.
Incoming – Configure if any incoming DID is configured for this trunk as some of the lines are taken for only outgoing purposes.
Starting Number – This is first number of the DID set allotted to you. Any wrong entry will impact incoming DID number creation.
DID_Digits – Normally it is between 3 to 8 depending upon the Operator & Exchange, Currently most of the operator gives full digits. Remember any wrong entry will impact incoming DID number creation.
DID_Nos – Normally the operator allots a 30 and above as DID. Remember any wrong entry will impact incoming DID number creation.
This menu will help integrate Com1 with another Com1 or any other PCM/TDM system over SIP Trunking. All popular brands like Matrix, Alcatel, NEC, Panasonic, Avaya or all makes that has SIP trunk option can be integrated. Feature transparency , accessing trunk from any other remote system, forwarding the incoming call , transferring a call are generally feasible between systems yet we advice caution as at times there are certain technical difficulties in accomplishing full feature transparency.
Operator – Selecting the remote system brand that is proposed to be connected.
Identity – To identify this connection among various other connection, normally system_location or as desired by you.
Password – If secondary authentication apart from IP authentication is required.
Host – The IP address / domain to which this system to be connected.
Port – Normally it is default SIP port 5060 which may vary to any other port based on service provider.
Max Channels – This may be restricted by the service provider
Outgoing Pattern – To integrate more than 1 system on the network, extension number uniqueness is mandatory and should follow an unique pattern. Any duplication of extension number can be managed by adding additional prefix as system identity else if all extension numbers are unique we can avoid an additional prefix and forward as the extension number itself. eg if the remote extension series is 500 to 599 then 5XX will be the pattern.
Outgoing Ext Digits – Actual digits of extension numbers in the remote system eg if the remote extension series is 500 to 599 then 3 will be the Ext Digits.
Incoming Pattern – Same as Outgoing Pattern – if Com1 extension series is 200 to 299 then 2XX will be the pattern.
Incoming Ext Digits – Same as Outgoing Ext Digits. eg if the com1 extension series is 200 to 299 then 3 will be the Ext Digits.
To assign DID to allow incoming calls as well as outgoing calls in the remote system, you need to complete DID Routing table as below.
This section is to configure external Trunk accessories such as GSM Gateway, FXO or Goip devices. The procedure broadly has 2 steps.
The following section will train you on how to create a SIP trunk in COM1 to attach hardware trunk accessories and the other part is explained for few of the hardware, which shall me more or less same for other hardwares. For better understanding, we use a sample of Allo GSM Gateway device to explain this configuration.
Go To – Resources —-> Hardware —-> Inventory
Select allo_gsm4 and press Save
This will create a SIP account in the PBX for the configuration in GSM Gateway
Go To – Resources —-> Hardware —-> Accounts
Make Note of Account, Pin, Incoming ID & Device ID(3 digit number after hardware eg 370 in allo_fxo4_370)
Use Add to add more accounts in case you want to group your resources.
Use Remove to remove any account.
Use radio button R to add any remarks to any account , say Telephone numbers connected to the group
Go To – Resources —-> Hardware —- Created
This gives the overview of all the external hardware connected to your Com1 IPPBX
This section helps you create Departments to categorise every extension created. This will be useful to forward the calls inside the departments in case of non response as well take department wise costing in call billing software.
You can Edit / Delete the entries.
PRI Trunks can be connected in 2 ways , either by using a hardware that can fit into the system in a PCI express slot or by a PRI gateway like the other forms of trunk to the network. PRI Cards are available in 1 Port, 2 Ports, 4 Ports & 8 Ports and multiple such cards can be connected in Com1 Ip Pbx though for stability we recommend not more than one card in one system.
PRI Gateway converts PRI Trunk to SIP Trunk. PRI Gateway has provision to insert PRI Line while output is network cable that is connected to the same network that connects Com1 Ip Pbx. PRI Gateway comes with a configuration as low as 1 Port to as high as 14 Ports with most widely sold being 1 Port. We strongly recommend Dinstar though every standard PRI Gateway can be connected to Com1 Ip Pbx.
PRI Card | PRI Gateway |