Phone & Gateway Interoperability Portal
From SIPfoundry sipXecs IP PBX, The Open Source SIP PBX for Linux - Calivia
The interoperability portal is meant to provide information on phone, gateway and SBC compatibility with sipX as it relates to different versions of sipX as well as different firmware revisions.
Contents |
Introduction
In general all SIP compliant phones should work with sipX; however, there are differences in the various implementations of SIP that can lead to incompatibility. Such incompatibility normally does not prevent a phone from being able to register with sipX or perform basic functions. The difficulty comes in with some of the more specific features of SIP, such as 'transfer' and 'consultative transfer' in particular.
Terminology
- Managed Phones: Configurable remotely using sipXconfig web admin interface. Plug & play management with automated profile generation.
- Unmanaged Phones: Phone configured manually typically using the phone's Web interface or some other mechanism subscribed by the phone manufacturer
- Partially Managed Phone: Only key parameters of the phone's config are manageable through the ConfigServer Web UI. Remaining features, if used, need to be manually configured. Phones that require manual delivery of the configuration files are also considered partially managed (like most softphones).
Plug & Play Managed Devices
Phones
| Phone | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
| Polycom | 30x, 3x0, 430, 50x,
5x0, 60x, 650, 4000 | Managed | Support for 2.x & 3.x firmware | HOWTO | The Polycom phones are of high quality and known to work very well with sipX. Firmware revision 3.1.1 with 4.1.2 bootrom is recommended for sipXecs 3.10.3 and later. Music on Hold now works with this combination. |
| SNOM | 300, 320, 360 | Managed | 4.0 or better (directed call pickup requires firmware 6.2). | HOWTO | Snom phones represent the top of the market when it comes to SIP features and functionality. The new Snom 300 is supported starting in release 3.4. |
| Grandstream | BudgeTone BT-101/102 | Managed | 1.0.6.7 1.0.7.11 | HOWTO | Budgetone phones are fully supported. Starting with sipX release 3.2 also remote restart works properly. |
| Grandstream | GXP-2000 | Managed | 1.0.1.9 | HOWTO | Starting with sipX Release 3.2 GXP-2000 is fully supported including restart. |
| Cisco | 7905G, 7912G | Managed | 1.3.1 or better | HOWTO | Cisco phones work well; however, there are a few issues |
| Cisco | 7940G, 7960G | Managed | 7.1 or better | HOWTO | Generally Cisco phones work well; however, there are a few issues. |
| Hitachi | IP3000, IP5000 | Managed | Hitachi WiFi phones | ||
| ClearOne | MaxAttach IP | Managed | ClearOne Speaker Phone | ||
| KDE kphone | Softphone | Partially
managed | 4.0.5 | HOWTO | The profile generated by configServer needs to be manually transferred to the PC where kphone is running |
| LGNortel | LIP Series | Managed | HOWTO | ||
| Aastra | 53i, 55i, 57i IP Phones,
560M sidecar module. | Managed | 560M sidecar module needs to be manually configured as the issue is still not resolved fully. |
Terminal Adaptors (FXS Gateways)
| TA | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
| Grandstream | HandyTone HT-286, HT-486 | Managed | 1.0.6.7 1.0.7.11 | HOWTO | HandyTone TAs are solid products that work well with sipX. Fully supported starting in release 3.2. |
| Grandstream | HandyTone HT-386, HT-488, HT-496 | Managed | 1.0.2.16 | HOWTO | Fully supported starting in release 3.2. |
| Cisco | ATA-186/188 | Managed | 1.3.1 or better | Cisco ATAs are known to work well. | |
| AudioCodes | MP-112/114/118 FXS, MP-124 | Managed | 5.x | HOWTO |
PSTN Gateways (FXO)
| Gateway | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
| AudioCodes | TP-260, MP-114/118, Mediant E1/T1 | Managed | 5.x | HOWTO | The TP-260 is a high quality and cost effective T1/E1 PCI gateway card. |
SBCs
| SBC | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
Manually Configured Devices
Phones
| Phone | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
| Xten | eyeBeam and X-Lite | Unmanaged | 1.1 | HOWTO | eyeBeam offers very nice call state (presence) capabilities together with Polycom phones |
| SNOM | 190, 220 | Unmanaged | HOWTO | Models 190 and 220 are discontinued and no longer available. | |
| SNOM | 360 softphone | Unmanaged | 5.3 | HOWTO | The Snom 360 softphone runs the same software as the real phone. The UI is not readable on the screen though. |
| MS Windows Messenger | Unmanaged | 5.1 | HOWTO | Windows Messenger is based on SIP and supports presence. | |
| sipXphone | Pingtel, SIPfoundry | v2.8 managed
v3.0 unmanaged | 2.2 or better | HOWTO - Managed | sipXphone is depracated and replaced by sipXtapi and sipXezPhone |
| LinPhone | Unmanaged | HOWTO | |||
| SJPhone | Unmanaged | HOWTO | |||
| Pingtel | xpressa and instant xpressa | v2.8 managed
v3.0 unmanaged | HOWTO - Managed | Pingtel xpressa phones are no longer available | |
| ACT | P104SLD | Unmanaged | HOWTO | ||
| Linksys / Sipura | SPA-841, SPA-941 | Unmanaged | HOWTO | ||
| ZyXEL | Prestige 2000W WiFi | Unmanaged | HOWTO |
Any other SIP phone will will work too; however, there is currently no documentation available.
Gateways
| Gateway | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
| Mediatrix | 1204 | Unmanaged | HOWTO | Mediatrix gateways are managed using SNMP. If you have an SNMP environment that's great; if not you will have to get used to MIB trees. They work great with sipX. | |
| Vegastream | Unmanaged | HOWTO | |||
| Cisco | Unmanaged | HOWTO | |||
| Patton | SmartNodes | Unmanaged | HOWTO | The Patton gateways are known to be of good quality while reasonably priced. They support ISDN BRI. | |
| Avaya | 5.1 | Unmanaged | CM 5.1 | HOWTO | Using a CM 5 system as a gateway is a little overkill, but using sipXecs for additional services... |
SBCs
| SBC | Models | Support* | Firmware | Documentation | Comments |
|---|---|---|---|---|---|
Phone and Gateway Configuration Framework
The sipX Configuration Server implements The Framework for SIP User Agent Profile Delivery, an IETF Draft RFC. If widely adopted this framework would allow large populations of phones to be managed remotely using a new SIP event package for auto-discovery and profile distribution. In the mean time, ConfigServer supports the different mechanisms implemented by the phone and gateway manufacturers for device discovery, profile delivery, notifications, and device updates. The most common mechanism is using a TFTP server, configured as part of the sipX system, for profile distribution. During the phone's startup phase it contacts a TFTP server at an address typically received from the DHCP server.
First when the phone successfully registered with sipX by completing a SIP REGISTER exchange is it possible for ConfigServer to remotely restart the phone after configuration changes.
For more information on how to integrate additional phones and gateways into ConfigServer refer to:
Interoperability Testing
For more information on SIP interoperability testing, see Interoperability Testing.
