Extensions allow you to configure extensions (users) and devices (telephones) in your system.


General tab

Extension*, number to dial in order to reach this extension. The extension number must be unique, and should not conflict with an existing extension number, or any other number that is assigned to any other entity within the system, such as a conference, queue, ring group, feature code, etc. The value of this field cannot be changed after the extension has been saved. 

 Name*, name to identify this extension. This is generally the end user's name or the location of the extension, e.g. Fernando Alonso or Server Room. This value will be displayed as the caller ID text for any calls placed from this extension to other users or devices on the PBX unless the Internal CID field contains a value. 

CoS Name, the dial plan can be segmented into sections, called Classes of Service (CoS). CoS are the basic organizational unit within the dial plan, and as such, they keep different sections of the dial plan independent of each other. Calltonet uses CoS to enforce security boundaries between the various parts of the dial plan, as well as to provide different classes of service to different groups of users. 

Features Password, password to access certain system features and the control panel of the phone. Email Address, email address to where the services messages will be sent.

Internal CID, internal Caller ID for the extension, consisting of two parts: the CID Name and the CID Number. This will define the caller ID text that is displayed when this user calls other (internal) users on the same PBX. This could be used when a user is part of a department in which callbacks should be directed to the department rather than directly to the user (such as a technical support department). This field is not mandatory. If the field is left blank, the user's extension will be used to set the Outbound Caller ID text. 

External CID, external Caller ID for the extension, consisting of two parts: the CID Name and the CID Number. This will define the caller ID text that is displayed when this user makes calls outside of the PBX. This could be used when a user is part of a department in which callbacks should be directed to the department rather than directly to the user (such as a technical support department). Setting the caller ID must be supported by the trunk service provider. This field is not mandatory, but if the field is left blank, the default caller ID name for the trunk placing the call will be used to set the caller ID name text. 

Emergency CID, it allows to define the caller id that will be used in case of calling an emergency number.

Account Code, this field is used to populate the Account Code field of the Call Detail Record (CDR). If the field is left blank, the Account Code field of the CDR record will also be blank. 

Devices section
This section allows you to configure the device that is linked to the extension.
▪ Technology, type of technology used by this device. The technology options are:
• PJSIP, PJSIP device
• SIP, SIP device
• IAX2, IAX device
• FXS, analog device
• NONE, extension without device.

PJSIP

User Device*, username to be used when registering this device.
Password, password (secret) associated with this device. Passwords can be the weakest link on any externally accessible PBX system, as malicious users will attempt to locate extensions having weak passwords. Extensions that authenticate by using simple passwords such as "1234" stand a good chance of being compromised, allowing an attacker to place calls through your PBX. Pick strong passwords carefully and ensure that passwords are not given to anyone who does not need to know them. Passwords should be at least 8 characters long and should include a random mixture of letters (both upper- and lower-case), numbers, and special characters.

Profile, group of settings for this device. Each technology (PJSIP, SIP, IAX2, DAHDi, or None) must have at least one (default) profile that defines attributes for the technology. You can configure these profiles in the Settings->Technology Settings->Profiles menu.

Max Contacts, maximum number of contacts that can bind to an AoR.

Codecs, list of allowed codecs. The order in which the codecs are listed determines their order of preference. If you select at least one codec, the DISALLOW=ALL parameter will be added. This will ensure that the device will only use only the codecs that you specifically define for the device. 

DTMF Mode, sets default dtmf-mode for sending Dual Tone Multi-Frequency (DTMF). The DTMF mode for a SIP device specifies how touchtone will be transmitted to the other side of the call. The default value is rfc4733. Available options are:
• Rfc4733
• info: SIP INFO messages (application/dtmf-relay)
• shortinfo: SIP INFO messages (application/dtmf)
• inband: Inband audio (requires 64 kbit codec -alaw, ulaw)
• auto: Use rfc4733 if offered, in-band otherwise

Device Description, a short (optional) description to identify this device.

Deny, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. This option should be in the format of an IP address and subnet, such as 192.168.25.10/255.255.255.255 (denies traffic from this specific IP address), or 192.168.1.0/255.255.255.0 (to disallow traffic for this extension from the IP range of 192.168.1.1 to 192.168.1.254). It is possible to enter a value of 0.0.0.0/0.0.0.0 to deny all of the networks by default, and, to enter specific networks from which traffic can be accepted in the permit option. This option is commonly used to restrict endpoint usage to a particular network, so that if the endpoint is stolen or otherwise removed from the network, it cannot be used to place calls and will be essentially useless. This field is not required. If it is left blank, Calltonet PBX will not block traffic for this peer from any IP address. 

Permit, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. For example, 192.168.10.0/255.255.255.0 allows traffic from any address on the 192.168.10.x network. The permit option is the opposite of the deny option. Specific IP addresses or networks can be added in this option to allow traffic for this extension from the entered IP/network. This field is not required. If it is left blank, traffic will be allowed from all IP addresses. Strengthen your system security by use of the deny and allow options, where possible. If the endpoint is static, we strongly recommend that you make proper use of the permit and deny options to ensure that traffic is only allowed from the specific address. Even if the endpoint is not static, but always resides on a known subnet, you should limit the allowed range to that specific subnet.

Ring Device, determines whether incoming calls should cause the device to ring. 

SIP

User Device*, username to be used when registering this device.
Password, password (secret) associated with this device. Passwords can be the weakest link on any externally accessible PBX system, as malicious users will attempt to locate extensions having weak passwords. Extensions that authenticate by using simple passwords such as "1234" stand a good chance of being compromised, allowing an attacker to place calls through your PBX. Pick strong passwords carefully and ensure that passwords are not given to anyone who does not need to know them. Passwords should be at least 8 characters long and should include a random mixture of letters (both upper- and lower-case), numbers, and special characters.

Profile, group of settings for this device. Each technology (SIP, IAX2, DAHDi) must have at least one (default) profile that defines attributes for the technology. You can configure these profiles in the Settings->Technology Settings->Profiles menu.

Codecs, list of allowed codecs. The order in which the codecs are listed determines their order of preference. If you select at least one codec, the DISALLOW=ALL parameter will be added. This will ensure that the device will only use only the codecs that you specifically define for the device. 

NAT, (Network Address Translation) is a technology commonly used by firewalls and routers to allow multiple devices on a LAN with 'private' IP addresses to share a single public IP address. A private IP address is an address, which can only be addressed from within the LAN, but not from the Internet outside the LAN Options:
• No: No special NAT handling other than RFC3581
• Force: Pretend there was an rport parameter even if there wasn't
• Comedia: Send media to the port Asterisk received it from regardless of where the SDP says to send it.
• Auto Force: Set the force rport option if Asterisk detects NAT
• Auto Comedia: Set the comedia option if Asterisk detects NAT

DTMF Mode, sets default dtmf-mode for sending Dual Tone Multi-Frequency (DTMF). The DTMF mode for a SIP device specifies how touchtone will be transmitted to the other side of the call. The default value is rfc2833. Available options are:
• info: SIP INFO messages (application/dtmf-relay)
• shortinfo: SIP INFO messages (application/dtmf)
• inband: Inband audio (requires 64 kbit codec -alaw, ulaw)
• auto: Use rfc2833 if offered, in-band otherwise.

Device Description, a short (optional) description to identify this device. 

Deny, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. This option should be in the format of an IP address and subnet, such as 192.168.25.10/255.255.255.255 (denies traffic from this specific IP address), or 192.168.1.0/255.255.255.0 (to disallow traffic for this extension from the IP range of 192.168.1.1 to 192.168.1.254). It is possible to enter a value of 0.0.0.0/0.0.0.0 to deny all of the networks by default, and, to enter specific networks from which traffic can be accepted in the permit option. This option is commonly used to restrict endpoint usage to a particular network, so that if the endpoint is stolen or otherwise removed from the network, it cannot be used to place calls and will be essentially useless. This field is not required. If it is left blank, Calltonet PBX will not block traffic for this peer from any IP address. 

Permit, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. For example, 192.168.10.0/255.255.255.0 allows traffic from any address on the 192.168.10.x network. The permit option is the opposite of the deny option. Specific IP addresses or networks can be added in this option to allow traffic for this extension from the entered IP/network. This field is not required. If it is left blank, traffic will be allowed from all IP addresses. Strengthen your system security by use of the deny and allow options, where possible. If the endpoint is static, we strongly recommend that you make proper use of the permit and deny options to ensure that traffic is only allowed from the specific address. Even if the endpoint is not static, but always resides on a known subnet, you should limit the allowed range to that specific subnet. 

Ring Device, determines whether incoming calls should cause the device to ring. 

IAX2 

User Device*, username to be used when registering this device.
Password, password (secret) associated with this device. Passwords can be the weakest link on any externally accessible PBX system, as malicious users will attempt to locate extensions having weak passwords. Extensions that authenticate by using simple passwords such as "1234" stand a good chance of being compromised, allowing an attacker to place calls through your PBX. Pick strong passwords carefully and ensure that passwords are not given to anyone who does not need to know them. Passwords should be at least 8 characters long and should include a random mixture of letters (both upper- and lower-case), numbers, and special characters.

Profile, group of settings for this device. Each technology (SIP, IAX2, Telephony, or None) must have at least one (default) profile that defines attributes for the technology. You can configure these profiles in the Settings->Technology Settings->Profiles menu. 

Codecs, list of allowed codecs. The order in which the codecs are listed determines their order of preference. If you select at least one codec, the DISALLOW=ALL parameter will be added. This will ensure that the device will only use only the codecs that you specifically define for the device. 

Device Description, a short (optional) description to identify this device.  

Deny, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. This option should be in the format of an IP address and subnet, such as 192.168.25.10/255.255.255.255 (denies traffic from this specific IP address), or 192.168.1.0/255.255.255.0 (to disallow traffic for this extension from the IP range of 192.168.1.1 to 192.168.1.254). It is possible to enter a value of 0.0.0.0/0.0.0.0 to deny all of the networks by default, and, to enter specific networks from which traffic can be accepted in the permit option. This option is commonly used to restrict endpoint usage to a particular network, so that if the endpoint is stolen or otherwise removed from the network, it cannot be used to place calls and will be essentially useless. This field is not required. If it is left blank, Calltonet PBX will not block traffic for this peer from any IP address. 

Permit, in a user/peer definition, allows you to limit SIP traffic to and from this peer to a certain IP or network. For example, 192.168.10.0/255.255.255.0 allows traffic from any address on the 192.168.10.x network. The permit option is the opposite of the deny option. Specific IP addresses or networks can be added in this option to allow traffic for this extension from the entered IP/network. This field is not required. If it is left blank, traffic will be allowed from all IP addresses. Strengthen your system security by use of the deny and allow options, where possible. If the endpoint is static, we strongly recommend that you make proper use of the permit and deny options to ensure that traffic is only allowed from the specific address. Even if the endpoint is not static, but always resides on a known subnet, you should limit the allowed range to that specific subnet. 

Ring Device, determines whether incoming calls should cause the device to ring. 

FXS

Channel*, the Telephony (DHADi) channel, selected from the drop-down list, that should be associated with this device. 

Profile, group of settings for this device. Each technology (SIP, IAX2, Telephony, or None) must have at least one (default) profile that defines attributes for the technology. You can configure these profiles in the Settings->Technology Settings->Profiles menu.

Device Description, a short (optional) description to identify this device.

Ring Device, determines whether incoming calls should cause the device to ring.