Reference:Configuration/BRI/Interop: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
(table added)
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The '''Interop''' submenu normally does not have to be adjusted. This is only necessary if, for example, malfunctions occur when transmitting H.323 calls.
Usually it should not be necessary to do any adjustments on this page. Nevertheless some ISDN implementation are not compatible to what we consider the standard.
 
Not all ISDN implementations are prepared to receive certain standard-compliant '''information elements''' (referred to as IEs). Such IEs can be created, for example, when linking up different PABXs or transmitting H.323 calls to an ISDN interface and vice-versa.
 
If malfunctions are caused by the transmission of certain IEs, the gateways can be made to remove such IEs from the transmitted messages.


{|
{|
|valign=top nowrap=true|'''Suppress Sending of HLC:'''
|valign=top nowrap=true|'''Automatic Keypad'''
| No high layer compatibility information elements are transmitted.
|This options enables Automatic Keypad sending. This means that if the first dialed digit to be sent on this interface is either '*' or '#' the digits are not sent as called party number, but as Keypad information instead. This is used on some ISDN networks for non call related supplementary services (e.g. *21*No# to set call forwarding).
|-
|valign=top nowrap=true|'''Suppress Sending of HLC'''
| The HLC (Higher Layer Compatibility) information element is used to provide end to end information about the application (e.g. Telephony) of the call. Very rarely ISDN implementations do no support it and thus reject calls. With this checkmark the sending of the HLC can be suppressed.
|-
|-
|valign=top nowrap=true|'''Suppress Sending of FTY:'''
|valign=top nowrap=true|'''Suppress Sending of FTY'''
| No facility information elements are transmitted.
| The FTY (Facility) information element is used for supplementary services. This option supresses the sending of FTY to avoid problems with incompatibilities of the facilities. No Supplementary Services are possible in this case.
|-
|-
|valign=top nowrap=true|'''Suppress Subaddress:'''
|valign=top nowrap=true|'''Suppress Subaddress'''
| No subaddress information elements are transmitted.
| No subaddress information elements are transmitted.
|-
|-
|valign=top nowrap=true|'''No Restart:'''
|valign=top nowrap=true|'''Suppress Connected Num.'''
| Disables the automatic Link Layer connection set up in Point-to-Point mode.
| No connected number information elements are transmitted.
|-
|valign=top nowrap=true|'''No Restart'''
| The Restart procedure is used by the device after establishment of the link layer to make sure no call exists on any channel. This is useful because some PBXs do no clear all calls if the link layer is disconnected. With this option this restart procedure is disabled.
|-
|valign=top nowrap=true|'''Passive Layer2'''
| Normally the device tries to establish the link layer on point to point interfaces as soon as the physical layer is established. This behaviour is especially incompatible to some ISDN conformance test equipment even if it conforms to standard. This option turns this off.
|-
|valign=top nowrap=true|'''No Overlap Receive'''
| Normally, single digit dialing (overlapped sending) is not used to call terminals (that is, devices in TE mode) on point-to-multipoint connections. Under certain circumstances however, it is possible for gateways to be connected to a PABX system in precisely this mode and then also support incoming single digit dialing (overlapped receive). In this case, an incoming SETUP message is answered, as required in the standard, with a SETUP_ACK message. Some PABXs, however, do not expect this sort of message from terminal equipment and terminate the call at this point. In such a case, the No overlap receive setting prevents the gateway from answering the incoming SETUP message with a SETUP_ACK.
|-
|valign=top nowrap=true|'''No Disc'''
| No DISC message is transmitted. REL is transmitted instead.
|-
|-
|valign=top nowrap=true|'''No Overlap Receive:'''
|valign=top nowrap=true|'''No Disc for Call Reject'''
| Normally, single digit dialling (overlapped sending) is not used to call terminals (that is, devices in TE mode) on point-to-multipoint connections. Under certain circumstances however, it is possible for gateways to be connected to a PABX system in precisely this mode and then also support incoming single digit dialling (overlapped receive). In this case, an incoming SETUP message is answered, as required in the standard, with a SETUP_ACK message. Some PABXs, however, do not expect this sort of message from terminal equipment and terminate the call at this point. In such a case, the No overlap receive setting prevents the gateway from answering the incoming SETUP message with a SETUP_ACK.
| Call Rejection is done with REL message instead of DISC.
|-
|-
|valign=top nowrap=true|'''No Disc:'''
|valign=top nowrap=true|'''Annex N'''
| No DISC information elements are transmitted. REL is transmitted instead.
| Signals the sending of inband information during call establishment according to ETS 300 102-1 Annex n (only in TE mode).
|-
|-
|valign=top nowrap=true|'''Annex N:'''
|valign=top nowrap=true|'''Automatic Progress'''
| Allows the sending of inband information during an established call (only in TE mode).
| Send a Progress message after any CallProceeding message to avoid short CallProceeding Timeout of 10s, which may be a problem with DECT handsets or if a CFNR to a public network is done.
|-
|-
|valign=top nowrap=true|'''Volume:'''
|valign=top nowrap=true|'''Volume'''
| Here, you can set a value in decibel (db) between -32db and +32db. Set a suitable value, if the standard value is inadequate or too high.
| Here, you can set a value in decibel (db) between -32db and +32db.
|-
|-
|valign=top nowrap=true|'''CR Length:'''
|valign=top nowrap=true|'''CR Length'''
| Call reference value in bytes. Select the size (in bytes) of the QSIG protocol, if the standard size is not correct.
| Length of call reference value in bytes. Normally the length of the Call reference is defined by the standard. Especially in the QSIG environment deviations from the standard are found, so it can be adjusted manually.
|-
|-
|valign=top nowrap=true|'''CHI Type:'''
|valign=top nowrap=true|'''CHI Type'''
| When using particular protocols (for example, QSIG), you can select a different interface from the one you actually have. Select Basic Rate Interface if you want to simulate a BRI interface. Select Primary Rate Interface if you want to simulate a multiplex interface.
|Coding of the Channel Information Element is different for Basic Rate (BRI) and Primary rate (PRI) interfaces, but for QSIG the PRI coding is defined for BRI interfaces as well. Some QSIG implementation use BRI coding of the Channel Information Element on a BRI interface. With this option the coding can be adjusted manually.
|}
|}

Latest revision as of 12:00, 11 March 2014

Usually it should not be necessary to do any adjustments on this page. Nevertheless some ISDN implementation are not compatible to what we consider the standard.

Automatic Keypad This options enables Automatic Keypad sending. This means that if the first dialed digit to be sent on this interface is either '*' or '#' the digits are not sent as called party number, but as Keypad information instead. This is used on some ISDN networks for non call related supplementary services (e.g. *21*No# to set call forwarding).
Suppress Sending of HLC The HLC (Higher Layer Compatibility) information element is used to provide end to end information about the application (e.g. Telephony) of the call. Very rarely ISDN implementations do no support it and thus reject calls. With this checkmark the sending of the HLC can be suppressed.
Suppress Sending of FTY The FTY (Facility) information element is used for supplementary services. This option supresses the sending of FTY to avoid problems with incompatibilities of the facilities. No Supplementary Services are possible in this case.
Suppress Subaddress No subaddress information elements are transmitted.
Suppress Connected Num. No connected number information elements are transmitted.
No Restart The Restart procedure is used by the device after establishment of the link layer to make sure no call exists on any channel. This is useful because some PBXs do no clear all calls if the link layer is disconnected. With this option this restart procedure is disabled.
Passive Layer2 Normally the device tries to establish the link layer on point to point interfaces as soon as the physical layer is established. This behaviour is especially incompatible to some ISDN conformance test equipment even if it conforms to standard. This option turns this off.
No Overlap Receive Normally, single digit dialing (overlapped sending) is not used to call terminals (that is, devices in TE mode) on point-to-multipoint connections. Under certain circumstances however, it is possible for gateways to be connected to a PABX system in precisely this mode and then also support incoming single digit dialing (overlapped receive). In this case, an incoming SETUP message is answered, as required in the standard, with a SETUP_ACK message. Some PABXs, however, do not expect this sort of message from terminal equipment and terminate the call at this point. In such a case, the No overlap receive setting prevents the gateway from answering the incoming SETUP message with a SETUP_ACK.
No Disc No DISC message is transmitted. REL is transmitted instead.
No Disc for Call Reject Call Rejection is done with REL message instead of DISC.
Annex N Signals the sending of inband information during call establishment according to ETS 300 102-1 Annex n (only in TE mode).
Automatic Progress Send a Progress message after any CallProceeding message to avoid short CallProceeding Timeout of 10s, which may be a problem with DECT handsets or if a CFNR to a public network is done.
Volume Here, you can set a value in decibel (db) between -32db and +32db.
CR Length Length of call reference value in bytes. Normally the length of the Call reference is defined by the standard. Especially in the QSIG environment deviations from the standard are found, so it can be adjusted manually.
CHI Type Coding of the Channel Information Element is different for Basic Rate (BRI) and Primary rate (PRI) interfaces, but for QSIG the PRI coding is defined for BRI interfaces as well. Some QSIG implementation use BRI coding of the Channel Information Element on a BRI interface. With this option the coding can be adjusted manually.