Image MIME Reference
CNS-INF2
Comverse Network Systems INF2 Image
image/vnd.cns.inf2
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Comverse Network Systems INF2 Image and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | CNS-INF2 | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Comverse Network Systems INF2 Image
image/vnd.cns.inf2
Extension
.inf2
Container
Proprietary Comverse Container
Compression
Proprietary
Algorithm
Unknown (Proprietary Telecom Encoding)
Color Depth
Unknown
Developed by
Comverse Network Systems (Ann McLaughlin)
Released
1999
Magic Bytes
Unknown (Proprietary)
T.38 Fax over IP (FoIP)
image/t38
Extension
.t38
Container
UDPTL or TCP (Network Transport)
Compression
Lossless (MH, MR, MMR / T.4, T.6)
Algorithm
MH (Modified Huffman)MR (Modified Read)MMR (Modified Modified Read)
Color Depth
1-bit (Monochrome B&W)
Developed by
ITU-T (International Telecommunication Union)
Released
1998
Magic Bytes
None (Network Stream)
Browser Support Comparison
| Browser | CNS-INF2 | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
CNS-INF2
CNS-INF2 Strengths
- Historically allowed Comverse to standardize media transmission internally across their global telecom messaging platforms
Limitations
- Completely obsolete and non-functional outside of decommissioned telecom infrastructure
- Undocumented, closed-source binary structure
- Zero support in modern image processing libraries like ImageMagick, libvips, or FFmpeg
T.38
T.38 Strengths
- Designed specifically to overcome the timing and packet-loss issues that plague traditional fax over standard VoIP audio codecs (like G.711)
- Reduces bandwidth requirements by transmitting fax protocol data rather than uncompressed audio tones
- Universally supported by enterprise SIP trunks and Session Border Controllers (SBCs) for FoIP
Limitations
- Not an actual image file format, causing confusion due to its 'image/' MIME classification
- Extremely complex to implement correctly over lossy UDP networks (relies on UDPTL redundancy mechanisms)
- Zero support in web browsers or standard image viewing software
When to choose which format
CNS-INF2
Use CNS-INF2 when…
- Legacy Telecom Infrastructure
- Historical Comverse Unified Messaging Systems
- Proprietary Server-to-Server Media Exchange
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers