What are the system and network requirements for implementing KCS Fax Over IP (FoIP)?
The following requirements apply for the implementation of FoIP.
- The IP system must support either H.323 or SIP signaling.
- When using H.323 one of the following connection options must be supported:
- Integration as H.323 trunk like a standard gateway
- Integration via H.323 gatekeeper as terminal
- Integration via H.323 gatekeeper as gateway
- When using SIP one of the following connection options must be supported
- Integration as SIP gateways with optional UserId/Password authentication
- Integration via SIP registrar with optional UserId/Password authentication
- The IP system must support VoIP using G.711 pass trough (A-law or u-law) or T.38.
- When using G.711 pass trough one the following algorithms must be supported.
- When using T.38 the following has to be taking into account.
- T.38 Version 0 (according to T.38 1998 ASN.1) must be supported. According to the standard, version 0 must be supported by all T.38 compliant devices.
- The mode changes from Voice to T.38 must be signaled using H.323/SIP message (protocol based switch-over).
Proprietary methods like NSE-based switch-over (may be used by gateways connected via SCCP protocol to an IP environment) are not supported.
FoIP Network requirements
Network requirements between KCS FoIP stack and pabx / gateway.
- Available network bandwidth between FoIP and gateway per channel:
- Minimum 100 kb/s during call establishment and in G.711pass trough mode (and before switching to T.38 mode)
- Minimum 30 kb/s during transmission of T.38 data (V.17 w/o T.38 redundancy, when T.38 redundancy is used check the manual)
- Network turnaround trip time between FoIP and gateway:
- Maximum 2 seconds turnaround trip time (T.38 Fax)
- Maximum 400ms turnaround trip time (G.711 Pass Trough)
- Network jitter between FoIP and gateway:
- Maximum 400ms jitter for T.38 fax
- Maximum 30ms jitter for G.711 pass through fax
- Maximum. 60ms jitter for voice mode
TCOSS Network requirements
Network requirements between TCOSS and the FoIP stack if not running on the same machine.
- Minimum 30 kb/s available bandwidth per channel
- The average packet turnaround time with 260 byte block size must be:
- less than 400ms for up to 4 channels
- less than 200ms for up to 30 channels
- less than 80ms for up to 60 channels
- less than 20ms for up to 180 channels
- Single interruptions are tolerated up to 2000 ms. Longer interruptions may lead to a break in the current transmission. If the network is interrupted for more than 9 seconds, the KCS system may restart the KCS FoIP.
The numbers above describes the network requirements for channels with up the 14.400 bps (V.17)
- Up to 180 channels (V.17 or V.34) are supported on a single physical computer when using T.38 Fax.
- Up to 120 channels (V.17 or V.34) are supported on a single virtual machine when using T.38 Fax.
- Up to 120 G.711 pass through mode channels are supported on physical or virtual machines.
- The following CPU resources must be available:
- CPU performance results for many systems are published at www.spec.org. Start search at http://www.spec.org/cgi-bin/osgresults?conf=cpu2006 and use the SPECInt_rate_base2006 value from a system that is similar to your hardware.T
- he maximum number of channels can be calculated with the following formula:
Level of Complexity
|Kofax Communication Server - FoIP||10.3||Windows|
- More information can be found in the Kofax Communication Server Fax over IP Technical Manual which can be found in the documentation section.
- More information on the T.38 fax protocol can be found on this Wikipedia page.
- More information on A-Law and μ-law can be found on this Wikipedia page.