PBXware 5.3 Trunks

Trunks

Trunks are a transmission line between two systems. This transmission is done using a wide range of PSTN and VoIP technologies. This screen lists all System Trunks with the following details:

• Name

This field tell us the name of the trunk.

(ex. It can be TrunkName or IP address 192.168.1.6)

(Display)

• Provider

Provider template name.

(ex. SIP TRUNK)

• Channels

Maximum number of inbound/outbound channels available for the trunk.

e.g. 10/10

• Trunk Type

Type of a trunk

(ex. PSTN, VOIP etc.)

• Protocol

Protocol used by the trunk

(ex. SIP, IAX etc.)

• Click this button if you want to edit the trunk configuration.

• Click this button in order to delete a trunk from the system

Search

The search bar filters trunks by name and provider.

• Search

Search phrase

(ex. Provide a search phrase here and hit enter to filter the records)

([a-z][0-9])

• Name

Should the search filter be applied to trunk names.

(ex. Check the box to search trunk names)

(Check box)

• Provider

Should the search filter be applied to provider names.

(ex. Check the box to search provider names)

(Check box)

Add/Edit Trunk

When adding a new trunk, the first step requires 'Provider' and 'Device' selection.

TIP:

Although a new trunk can be created without it, it is preferred that the 'Provider' template be created first under 'Settings: Providers'.

For a basic Provider and Trunk HowTo, check out our HOWTO Create a Trunk

• Provider

Select a service provider template.

(ex. BT)

(Select box)

• Device

If the providers service requires a device in order to provide the service, this field will become visible.

(ex. None, T100)

(Select box)

VoIP (SIP/IAX)

The second step of the trunk installation and edit command, this opens the following options:

• Name or Number

Some providers require this field to be equal to the DID number (e.g.55510205); but if connecting two systems, the IP address may be used as well.

(ex. 2554433, myvoiceboxlink)

([a-z] [0-9])

• Country

Country where the service provider resides.

(Select USA, for example, if the provider is from the United States)

(Select box)

• Emergency trunk

Whether emergency services (Police, Ambulance etc.) should be dialed through this trunk.

(ex. Dialing 911 will pass the call through this trunk)

(Option buttons)

• Peer Host

The IP of the peer host to which the system sends calls.

(ex. 192.168.1.1)

(IP Address)

• Username

The username for authenticating with the service provider.

(ex. 2554433)

([0-9])

• Peer Username

The peer username for authenticating with the service provider.

(ex. 2554433)

([a-z] [0-9])

• Secret

The Secret/Password used for authenticating with the service provider.

(ex. 123456)

([a-z] [0-9])

• Peer secret

The peer secret/password used for authenticating with the service provider.

(ex. 123456)

([a-z] [0-9])

Advanced Options

General

These options are used frequently and required for normal trunk operation. Some of these fields are pre-configured with the default values. It is not recommended to change them.

• User Type

The user's relationship to the system

Example:

• user - The trunk accepts incoming calls only
• peer - The trunk makes outgoing calls only
• friend - The trunk does both incoming and outgoing calls

(Select box)

• DTMF Mode (Dual Tone Multi-Frequency)

Trunk DTMF mode. A specific frequency (consisting of two separate tones) is assigned to each key so that it can be easily identified by a microprocessor

Example:

• inband - inband audio (requires 64 kbit codec - alaw, ulaw)
• rfc2833 - default
• info - SIP INFO messages

(Select box)

• Context

Contexts define a scope within PBXware. The trunk context cannot be modified and is the same as the trunk name or number.

(ex. 2554433)

([a-z][0-9])

• Status

Set the trunk status on the system. (Active/Not Active/Suspended)

(ex. Rather than deleting the trunk, you can disable it on the system level by selecting 'Not Active' here)

(Select box)

• Qualify

Timing interval in milliseconds at which a 'ping' is sent to a host in order to find out its status.

(ex. Set this field to 2000, for example. If more time than provided here is needed to reach the host, the host is considered offline)

([0-9])

• Country

Country where the service provider resides.

(Select USA, for example, if the provider is from the United States)

(Select box)

• National Dialing Code

National dialing code used at the trunk destination.

(ex. For USA 1. For the United Kingdom and Germany 0)

(Select box)

• International Dialing Code

International dialing code used at the trunk destination.

(ex. For USA 011. For the United Kingdom and Germany 00)

([0-9])

• E164 Accepted

Does the trunk support dialing destinations in the E164 format.

(ex. Enabling this option will reformat any dialed number into the following form COUNTRY_CODE + AREA_CODE + DIALED_NUMBER. For example, if you dial 5551020, the system will dial 12125551020)

(Option buttons)

• Pass-thru mode

Pass the digits dialed without any conversion (E164, National, Area code).

NOTE: When active, 'Leave National Code' and 'Local Area Code' will be disabled.

(ex. If this option is disabled, PBXware will convert all dialed numbers to the E164 format (COUNTRY_CODE + AREA_CODE + DIALED_NUMBER) and then make a call to the converted number. If this option is enabled, PBXware will directly call the DIALED_NUMBER without making any number conversions)

(Option buttons)

• Leave National Code

In some countries, the national code is stripped automatically. If set to 'Yes', the national code will not be stripped from the dialed number.

NOTE: Before setting this option to 'Yes', go to 'Settings: Servers' and enable this option as well.

(ex. 035123456 will not be striped of 0)

(Option buttons)

• Local Area Code

Add the local area code to the dialed number, if required by the service provider. (By default, the local area code is stripped when dialing).

(ex. The user dials 55510205, the local area code is 212. If the call goes through this trunk, PBXware will dial 21210205)

([0-9])

• Emergency trunk

Should emergency services (Police, Ambulance, etc) be called over this trunk.

(ex. Select 'Yes' in order to dial emergency services over this trunk).

(Option buttons)

• Prefix

Value added to all dialed numbers going over the trunk.

(ex. Prefix 5 + Dialed number 123 = System dials 5123)

([0-9])

• Test number

This is the number that the trunk will try to call when Trunk Monitoring is turned on. If the answer is not: ANSWER, BUSY, CANCEL, or NOANSWER, this call is considered non-functional and the monitoring system will send a notification email.

(1009)

([0-9])

• Check for Additional Headers (5.3.5 update)

Some trunk providers can send incoming INVITEs with additional headers (X-Mnet-InLeg) containing some custom strings. When a call enters PBXware and if the call flow results in some kind of call forwarding back to the provider, they could request this same custom header with the same value so they now which call is in question.

e.g.: System 1 > Trunk > Custom SIP Headers > X-Mnet-Inleg: 1alpha457908

System 2 > Trunk > Check for Additional Headers > X-Mnet-Inleg System 1 Calls System 2. System 2 should detect the X-Mnet-Inleg header and preserve it.

IMPORTANT: It's very important to bear in mind that if phone transfer is used then the headers CANNOT be preserved. The reason is that after the transfer is initiated the call is treated as a completely new call and we cannot get the information about preserved headers and their values. If # is used for transfer, everything should be okay.

Authentication

• Host

The IP address that the host trunk is connecting to.

(e.g.): 192.168.1.1

([0-9][a-z])

NOTE: Please note that only one IP can be added as a host, you cannot add multiple IPs.

• Authname:

Value assigned to the Digest username= SIP header

(ex. 2222)

([0-9][a-z])

• Auth

Authenticate for outbound calls to other realms.

(ex. user:secret@realm)

([0-9][a-z])

• Register

Method for registering to the remote server.

(ex. Providers may require a different form of registration to their server. You may choose between 'registration not required', 'register with phone number', 'register with username', 'register with authname', 'register with authname@host', and 'register with authname@trunk-name').

(Select box)

• Register suffix

The service provider may request different registration methods for their services. Select the proper method, as required by the provider.

(ex. 1234567)

([0-9])

• Insecure

Typically used to allow incoming calls while having a "friend" type entry defined with a username and password

Example:

• Port - Ignores the port number where the request came from
• Invite - Does not require authentication of incoming INVITEs
• Port-Invite - Does not require initial INVITE to authenticate and ignore the port where the request came from
• Very - Ignore authentication (user/password)

(Select box)

• From User

What to show when calling TO this peer FROM asterisk.

(ex. 152)

([0-9])

• From Domain

From domain data is required by some providers.

(ex. If your provider requires this information, provide the exact value here).

([a-z][0-9])

• user=phone in URI

If yes, ";user=phone" is added to uri that contains a valid phone number.

(ex. Yes, No, N/A)

(Option buttons)

• Outbound Proxy

Send outbound signaling to this proxy, not directly to the peer.

(ex. outbound.proxy.com)

([0-9][a-z].)

• Incoming IP addresses (new line seperated)

You may limit SIP traffic to and from this peer to a certain IP or network.

(ex. 10.1.1.9)

([0-9].)

IAX Specific Authentication Settings

• Encryption

Whether encryption should be used when authenticating with the peer.

(ex. Yes, No, N/A)

([a-z][0-9])

• Auth Method

Authentication method required by the provider.

(ex. md5)

([a-z] [0-9])

• RSA key

RSA authentication key

(ex. If the Auth Method is set to RSA, provide the RSA key here).

([a-z][0-9])

Network Related

These options set important network related values regarding NAT.

• Transport:

Type of transfer protocol that will be used on PBXware.

UDP (User Datagram Protocol) - With UDP, computer applications can send messages (in this case, referred to as datagrams) to other hosts on an Internet Protocol (IP) network without prior communication to set up special transmission channels or data paths.

TCP (Transmission Control Protocol) - provides reliable, ordered, error-checked delivery of a stream of octets between programs running on computers connected to an intranet or the public Internet.

TLS (Transport Layer Security) - cryptographic protocol that provides communication security over the Internet.[1] They use asymmetric cryptography for authentication of key exchange, symmetric encryption for confidentiality, and message authentication codes for message integrity.

Type: Checkbox

• Encryption:

This option enables or disables encryption in PBXware transport.

Options: Yes, No, N/A.

• Direct media

Whether to allow RTP voice traffic to bypass PBXware.

NOTE: All enhanced services for the extension have to be disabled.

(ex. Some devices do not support this, especially if one of them is behind a NAT).

(Options buttons)

• Direct RTP setup:

Here you can enable or disable the new, experimental, direct RTP setup. Setting this value to 'yes' sets up the call directly with media peer-2-peer without re-invites. Will not work for video and cases where the callee sends RTP payloads and fmtp headers in the 200 OK that does not match the callers INVITE. This will also fail if directmedia is enabled when the device is actually behind NAT.

Options: Yes, No, N/A

• Default IP

The IP address to be used until registration.

(ex. 192.168.1.1)

(IP Address)

(Option buttons)

Caller ID

• Trust Remote-Party-ID:

Defines whether PBXware allows Remote-Party-ID header

(Option button)

• Send Remote-Party-ID:

Should 'Remote-Party-ID' be added to uri.

Options:

• Use Remote-Party-ID - Use the "Remote-Party-ID" header to send the identity of the remote party
• Use P-Asserted-Identity - Use the "P-Asserted-Identity" header to send the identity of the remote party

(Select Box)

• Send Caller ID in RPID for Anonymous calls

Select whether you would like to send original Caller ID in RPID.

When making anonymous calls, FROM and PAI are presented as anonymous, while PAI should also send original CallerID. Some provider require this setting and would not present anonymous Caller ID otherwise.

(Yes, No, N/A)

• Connected Line Updates:

Connected Line Updates allows you to enable or prevent RPID updates to be sent after call is established.

This option is particularly useful as with some providers, if Use PAI is enabled, calls might start dropping short time after update is sent. Setting Connected Line Updates to No will prevent these call drops.

(Option button)

• RPID with SIP UPDATE:

In certain cases, the only method by which a connected line change may be immediately transmitted is with a SIP UPDATE request. If communicating with another Asterisk server and you want to transmit such UPDATE messages to it, then you must enable this option. Otherwise, you will have to wait until you can send a re-invite to transmit the information.

• Send PAI header

The P-Asserted-Identity contains the caller ID information for the call on the INVITE SIP packet. This is the acceptable way to specify privacy information for calls. This field enables you to send the preferred PAI header using several variables:

• %CALLERIDNUM%
• %TENANT%
• %EXT%
• %TENANTEXT%

• Outbound Caller ID

If the Caller ID is not set by the UAD, the value provided here will be used instead for all outgoing calls.

(ex. 55599999)

([0-9])

• Allow ES Caller ID

Whether ES (Enhanced Services) caller ID should be allowed over this trunk.

(ex. Any extension can set a custom caller ID for each system trunk. With this option enabled, that caller ID will be used instead of the trunk outbound caller ID).

([0-9])

Channels

• Incoming Limit

The number of simultaneous incoming calls that the trunk can handle.

(ex. 4 = four simultaneous incoming calls. Any additional calls will get a busy sound).

([0-9])

• Outgoing Limit

Number of simultaneous outgoing calls that the trunk can handle.

(ex. 4 = four simultaneous outgoing calls. Any additional calls attempting to use this trunk will be rejected or will be redirected to other trunks depending on what is set in the system/extensions).

([0-9])

• Busy Level

Number of concurent calls until the user/peer is considered busy.

• E-mail on exceeded limit

Send an e-mail when the outgoing limit is reached, can be set to Yes, No, or N/A.

(Option buttons)

• Outgoing Dial Options

Advanced dial options for all outgoing calls.

(ex. trT)

([a-z])

IAX Specific Channels settings

• Notransfer

Disable the native IAX transfer.

(ex. Yes, No, N/A)

(Option buttons)

• Send ANI

Should ANI ("super" Caller ID) be sent over this trunk.

(ex. Yes, No, N/A)

(Option buttons)

• Trunk

Use IAX2 trunking with this host.

(ex. Yes, No, N/A)

(Option buttons)

Codecs

Codecs are used to convert analog to digital voice signals and vice versa. These options set preferred codecs used by the extension.

TIP: If some of the desired codecs cannot be checked, go to 'Settings: Servers: Edit: Default Codecs' and enable them under the 'Remote' group.

• Video Support

Set this option to 'Yes' to enable SIP video support.

(Yes, No, N/A)

• Auto-Framing (RTP Packetization)

If auto framing is turned on, the system will choose the packetization level based on remote ends preferences.

(ex. Yes)

(Option buttons)

Additional config

This option is used for providing additional config parameters for SIP, IAX, and MGCP configuration files. The values provided here will be written into these configuration files.

NOTE: Unless absolutely sure, do not change or add to this template.

SIP Custom headers

SIP headers is a function of SIP. These headers help convey message attributes to ensure that information packets travel along the correct path when communicating between devices existing on separate networks.

In order to use SIP Custom headers, these are the variables which can be used:

• %CALLERIDNUM%
• %TENANT%
• %EXT%
• %TENANTEXT%

NOTE: Unless absolutely sure, do not change or add to this template.

PSTN

• Name

Trunk name/number.

(ex. 032445231)

([a-z][0-9])

• Emergency trunk

Should emergency services (Police, Ambulance, etc) be called over this trunk.

(ex. Select 'Yes' in order to dial emergency services over this trunk).

(Option buttons)

• Channel(s)

Which card channels are used.

(ex. If channel 2 and 4 are used on your card, set '2, 4' here. If all four channels are used set '1-4' here).

([0-9], [,-])

• Group

Every PSTN trunk has to belong to a group. Selecting any group will enable the trunk.

(ex. With most of the cards, this option is auto detected and set. If that is the case with your card, do not change this field).

(Select box)

• FXS Kewlstarts

Signaling protocol for analog circuits that better detects far-end disconnects.

(ex. Select card channels to be monitored with it. For example '1, 4' or '1-4'. These numbers should match the 'Channel(s)' field).

([0-9], [,-])

• Country

Destination of the trunk connection.

(ex. If your system is located in the USA, select USA here)

(Select box)

• E164 Accepted

Whether the trunk supports dialing destinations in the E164 format. Enabling this option will reformat any dialed number into the following form COUNTRY_CODE+AREA_CODE+DIALED_NUMBER.

(ex. If you dial 5551020, the system will dial 12125551020).

(Option buttons)

• International Dialing Code:

The international dialing code at the trunk destination.

(ex. For the USA 011, for the United Kingdom and Germany 00 etc.)

([0-9])

Advanced

Zapata

General

• Language

Default language.

(ex. us)

(Select box)

• Context

Contexts define a scope within the PBXware.

(ex. default)

([a-z][0-9])

• Status:

Trunk status

Example:

• Active
• Not Activated

(Select box)

• Signalling

Signaling method

Example:

• FXS Loopstart
• FXS Groundstart
• FXS Kewlstart
• FXO Loopstart
• FXO Groundstart
• FXO Kewlstart
• PRI CPE side
• PRI Network side
• BRI CPE side
• BRI Network side
• BRI CPE PTMP
• BRI Network PTMP

NOTE: The signaling type to use with your interface is the mandatory setting. You must set a signaling type before allocating a channel. If you are connecting analog telephone equipment, note that analog phone signaling can be a source of confusion. FXS channels are signaled with FXO signaling and vice versa. Asterisk 'talks' to internal devices as the opposite side. An FXO interface card is signaled with FXS signaling by Asterisk and should be configured as such.

• Test number

This is the number which the trunk will try to call when Trunk Monitoring is turned on. If the answer is not: ANSWER, BUSY, CANCEL, or NOANSWER, this call is considered non-functional and the monitoring system will send a notification email.

(ex. 1009)

([0-9])

• Music On Hold

Choose what music to use for Music on Hold. If not specified, the 'default' will be used.

(ex. default)

(Select box)

• Mailbox

Define a voicemail context.

(ex. 1234, 1234@context)

([a-z][0-9)

• Group Method

([a-z][0-9])

This option specifies how to choose a channel to use in the specified group.

The four possible options are:

• g: select the lowest-numbered non-busy DAHDI channel (aka. ascending sequential hunt group).
• G: select the highest-numbered non-busy DAHDI channel (aka. descending sequential hunt group).
• r: use a round-robin search, starting at the next highest channel from last time (aka. ascending rotary hunt group).
• R: use a round-robin search, starting at the next lowest channel from last time (aka. descending rotary hunt group).

RX/TX

• RX Wink

Set timing parameters

Example:

• Pre-wink (50ms)
• Pre-flash (50ms)
• Wink (150ms)
• Receiver flashtime (250ms)
• Receiver wink (300ms)
• Debounce timing (600ms)

(Select box)

• RX Gain

Receive signal decibel.

(ex. If incoming sound is low and you cannot hear the other party well, set this option to 2. That should increase incoming sound by 2 decibels).

([0-9])

• TX Gain

Transmit signal decibel.

(ex. If outgoing sound is low and the other party cannot hear you well, set this option to 2. That should increase outgoing sound by 2 decibels).

([0-9])

PRI

• Switchtype

Set switch type

Example:

• National ISDN 2
• Nortel DMS100
• AT&T 4ESS
• Lucent 5ESS
• EuroISDN
• Old National ISDN 1

(Select box)

• PRI Dial Plan

Set the dial plan used by some switches

Example:

• Unknown
• Private ISDN
• Local ISDN
• National ISDN
• International ISDN

(Select box)

• PRI Local Dial Plan

Set the numbering dial plan for destinations called locally

Example:

• Unknown
• Private ISDN
• Local ISDN
• National ISDN
• International ISDN

(Select box)

• PRI Trust CID

Trust provided caller ID information.

(ex. Yes, No, N/A)

(Option buttons)

• PRI Indication

How to report 'busy' and 'congestion' on a PRI

Example:

• outofband - Signal Busy/Congestion out of band with RELEASE/DISCONNECT
• inband - Signal Busy/Congestion using in-band tones

(Select box)

• Network Specific Facility

If required by the switch, select the network specific facility

Example:

• none
• sdn
• megacom
• accunet

(Select box)

Caller ID

• Outbound Caller ID

Caller ID set for all outbound calls where the Caller ID is not set or supported by a device.

(ex. john@domain.com)

([0-9])

• Allow ES Caller ID

Should the ES (Enhanced Services) Caller ID be allowed over this trunk.

(ex. Any extension can set a custom Caller ID for each system trunk. With this option enabled, that Caller ID will be used instead of the Trunk Outbound Caller ID).

([0-9])

• Caller ID (for analog or inbound)

CallerID can be set to 'asreceived' or a specific number if you want to override it.

NOTE: Caller ID can only be transmitted to the public phone network with supported hardware, such as a PRI. It is not possible to set external caller ID on analog lines.

(ex. 'asreceived', 555648788)

([a-z][0-9])

• Use Caller ID

Whether or not to use caller ID.

(ex. Yes, No, N/A)

(Option buttons)

• Hide Caller ID

Whether or not to hide the outgoing caller ID.

(ex. Yes, No, N/A)

(Option buttons)

• Restrict CID

Whether or not to use the caller ID presentation for the outgoing call that the calling switch is sending.

(ex. Yes, No, N/A)

(Option buttons)

• Use CallerID Presentation

Whether or not to use the caller ID presentation for the outgoing call that the calling switch is sending.

(ex. Yes, No, N/A)

(Option buttons)

• CID Signalling

Set the type of caller ID signaling

Example:

• bell - US
• v23 - UK
• dtmf - Denmark, Sweden and Netherlands

(Select box)

• CID Start

What signals the start of the Caller ID

Example:

• ring = a ring signals the start
• polarity = polarity reversal signals the start

(Select box)

• Call Waiting CID

Whether or not to enable call waiting on FXO lines.

(ex. Yes, No, N/A)

(Option buttons)

• Send CallerID After

Some countries, like the UK, have different ring tones (ring-ring), which means the caller ID needs to be set later on, and not just after the first ring, as per the default.

(ex. Yes)

(Select box)

Echo Canceller

• Echo Cancel

Level of enabled echo cancellation.

(ex. 128 (Yes))

(Select box)

• Echo Training

Mute the channel briefly, for 400 minutes, at the beginning of the conversation, cancelling the echo. (Use this only if 'Echo Cancel' doesn't work as expected).

(ex. Yes, No, N/A)

(Option buttons)

• Echo Cancel When Bridged

Enable echo cancellation when bridged. It is generally not necessary and, in fact, undesirable, to echo cancel when the circuit path is entirely TDM.

(ex. Yes, No, N/A)

(Option buttons)

• Echo Canceller

Supported echo cancellers:

• mg2
• oslec
• kb1

Call Features

• Call Waiting

Whether or not to enable call waiting on FXO lines.

(ex. Yes, No, N/A)

(Option buttons)

• Three Way Calling

Supports three-way calling. If enabled, the call can be put on hold and the user will be able to make another call.

(ex. Yes, No, N/A)

(Option buttons)

• Transfer

Supports call transfer and also enables call parking (overrides the 'canpark' parameter). Requires 'Three Way Calling' = 'Yes'.

(ex. Yes, No, N/A)

(Option buttons)

• Can Call Forward

Support call forwarding.

(ex. Yes, No, N/A)

(Option buttons)

• Call Return

Whether or not to support Call Return '*69'. Dials last caller extension number.

(ex. Yes, No, N/A)

(Option buttons)

• Overlap Dial

Enable overlap dialing mode (sends overlap digits).

(ex. Yes, No, N/A)

(Option buttons)

• Pulse Dial

Use pulse dial instead of DTMF. Used by FXO (FXS signalling) devices.

(ex. Yes, No, N/A)

(Option buttons)

Call Indications

• Distinctive Ring Detection

Whether or not to do distinctive ring detection on FXO lines.

(ex. Yes, No, N/A)

(Option buttons)

• Busy Detect

Enable listening for the beep-beep busy pattern.

(ex. Yes, No, N/A)

(Option buttons)

• Busy Count

How many busy tones to go through before hanging up. Bigger settings lower the probability of random hang ups. 'Busy Detect' has to be enabled.

• 4
• 6
• 8

(Select box)

• Call Progress

Easily detect false hangups.

(ex. Yes, No, N/A)

(Option buttons)

• Immediate

Whether the channel should be answered immediately or the simple switch should provide dial tone, read digits, etc.

(ex. Yes, No, N/A)

(Option buttons)

Call Groups

• Call Group

Which group is allowed to pick up incoming calls by dialing *8. The default value is empty.

(ex. 1, 1-4)

([0-9])

• Pickup Group:

Which groups are allowed to pick up calls by dialing *8. The default value is empty.

(ex. 1, 1-4)

([0-9])

FXS Channels

• FXS Loopstart

Signals the far end that it wants the dial tone by shorting the leads.

(ex. default)

([0-9])

• FXS Groundstart

Signals the far end that it wants the dial tone by grounding one of the leads.

(ex. default)

([0-9])

Locality

• Country

Destination of the trunk connection

(ex. USA)

(Select box)

• E164 Accepted

Does the trunk support dialing destinations in the E164 format.

(ex. Enabling this option will reformat any dialed number into the following form COUNTRY_CODE+AREA_CODE+DIALED_NUMBER. For example, if you dial 5551020, the system will dial 12125551020).

(Option buttons)

• Pass-thru Mode

If this option is enabled, the number which is dialed is passed through the trunk without modification.

(ex. Yes, No, N/A)

(Option buttons)

• National Dialing Code

The national dialing code at the trunk destination.

(ex. For the USA, 1. For the United Kingdom and Germany, 0, etc.)

([0-9])

• Leave National Code

In some countries, the national code is stripped automatically. If set to 'Yes', the national code will not be stripped from the dialed number.

NOTE: Before settings this option to 'Yes', go to 'Settings: Servers' and enable this options as well.

(ex. John dials 121255510205. With this option enabled)

([0-9])

• International Dialing Code

International dialing code at the trunk destination.

(ex. For the USA 011. For the United Kingdom and Germany 00 etc.)

([0-9])

• Local Area Code

Add the local area code to the dialed number, if required by the service provider. (By default, the local area code is stripped when dialing)

(ex. The user dials 55510205, the local area code is 212. If the call goes through this trunk, PBXware will dial 21210205).

([0-9])

• Write dialing code

Should the National and International prefix be written into the configuration files.

(ex. Enable this option if required by the provider).

([0-9])

• Prefix

Value added to all dialed numbers going over the trunk.

(ex. Prefix 5, Dialed number 123, System dials 5123).

([0-9])

Other Zapata Options

• ADSI (Analog Display Services Interface)

Enable remote controlling of the screen phone with softkeys. (Only if you have ADSI compatible CPE equipment).

(ex. Yes, No, N/A)

(Option buttons)

• Jitter Buffers

Configure jitter buffers. Each one is 20 minutes long.

(ex. 4)

([0-9])

• Relax DTMF

If you are having trouble with DTMF detection, you can relax the DTMF detection parameters.

(ex. Yes, No, N/A)

(Option buttons)

• Fax Detect

Enable fax detection

Example:

• both
• incoming
• outgoing
• no

(Select box)

Span

• Span number

Number of the span.

(ex. 1)

([0-9])

• Span timing

How to synchronize the timing devices

Example:

• 0 - do not use this span as a sync source
• 1 - use as a primary sync source
• 2 - set as secondary and so forth

([a-z])

• Line build out

This is the length of the last leg of the connection and is set to zero if the length is less than 133 feet

Example:

• 0 db (CSU) / 0-133 feet (DSX-1)
• 133-266 feet (DSX-1)
• 266-399 feet (DSX-1)
• 399-533 feet (DSX-1)
• 533-655 feet (DSX-1)
• -7.5db (CSU)
• -15db (CSU)
• -22.5db (CSU)

(Select box)

• Framing

How to communicate with the hardware at the other end of the line

Example:

• For T1: Framing is one of d4 or esf.
• For E1: Framing is one of cas or ccs.

(Select box)

• Coding

How to encode communication with the other end-of-line hardware.

Example:

• For T1: coding is one of ami or b8zs
• For E1: coding is one of ami or hdb3 (E1 may also need crc)

(Select box)

• Yellow

Whether the yellow alarm is transmitted when no channels are open.

(ex. Yes, No, N/A)

(Option buttons)

Dynamic Span

• Dynamic span driver

The name of the driver (e.g. eth).

([0-9][a-z])

• Dynamic span address

Driver specific address (like a MAC for eth).

([0-9][a-z])

• Dynamic span channels

Number of channels.

(6)

• Dynamic span timing

Sets timing priority, like for a normal span. Use '0' to NOT use this as a timing source, or prioritize them as primary, secondary, etc.

(0)

FXO Channels

• FXO Loopstart

Channel(s) are signaled using FXO Loopstart protocol.

• FXO Groundstart

Channel(s) are signaled using FXO Groundstart protocol.

• FXO Kewlstart

Channel(s) are signaled using FXO Kewlstart protocol.

PRI Channels

• D-Channel(s)

For example, every ISDN BRI card has 1 D- (control) channel.

(ex. 1)

([0-9])

• B-Channels(s)

For example, every ISDN BRI card has 2 B- (data) channels.

(ex. 2)

([0-9])

Custom Trunks

Custom Trunks are used in rare cases where the PBXware Trunk setup features do not provide enough flexibility for some provider configuration. In such cases, users need to create a custom Trunk, and then change the dialplan in the trunks-in.conf file.

• Search

Users can search the existing Custom Trunks by using the search bar.

(E.g. Test)

([a-z][0-9])

• Trunk

Displays the name of the Custom Trunk

(E.g. Test)

(Display)

NOTE: Hovering the mouse over the name of a Custom Trunk and clicking it will prompt users to the 'Custom Trunk -> Edit' window.

• Context

Displays the context of the specific Custom Trunk

(E.g. 23)

(Display)

• Click this button to edit the existing Custom Trunk.

NOTE: Upon clicking the 'Edit' button, users will be prompted to a 'Custom Trunk -> Edit' window where they can edit details regarding existing Custom Trunks.

(Button)

• Click this button to delete the existing Custom Trunk.

NOTE: Upon deleting the existing Custom Trunk, the warning message will appear saying "Are you sure you want to remove XYZ?". If a user confirms his/her action of deletion by clicking 'OK', the specified Custom Trunk will be deleted.

(Button)

Add Custom Trunk

Once this button is clicked, users will be prompted to a different window where they can create new Custom Trunks.

• Trunk

Enter the name of a Custom Trunk that will be visible in the PBXware GUI

(E.g. Test)

([a-z][0-9])

NOTE: Please be notified that spaces are not allowed while adding the name of a Custom Trunk. Please refer to the further visual explanation.

Custom Trunk Example Names
1. Without Space Character (accepted)	GlobalTrunk
2. With Space Character (not accepted)	Global Trunk

• Context

Enter the context by which the system sees this Custom Trunk. This will be used when editing the dialplan.

(E.g. If a user sets the context as 'gl_trunk', then, when sending calls to the Trunk, s(he) would use this to refer to the given Trunk).

([a-z][0-9])

Next -> 6. DID