SIP Support

IP Office supports both SIP trunks and SIP extensions.

SIP Extension Support

IP Office Release 5 adds support for SIP extension devices to the IP Office offering. Due to the wide variety of SIP devices and interpretations of standards, Avaya cannot give any guarantees of support for all SIP extension devices and features. Details of the supported features and currently tested devices are included in the IP Office Release 5: SIP Phone Details document. Examples of installation are included in the SIP Extension Installation manual.

SIP Trunk Providers

IP Office SIP trunks have been successfully tested with the following ITSP SIP providers. This table of providers is a statement of fact and not any form of recommendation from Avaya, nor does it exclude other service providers. Any details of the expected operation and service should be confirmed in writing with the individual service provider.

IP Office also supports the Avaya SIP Enablement Server (SES) for private networking between Avaya systems.

*1: The SIPGate service does not support RFC2833 for the sending of DTMF tones. SIPGate uses the alternate SIP INFO method which is not supported by the IP Office.

*2: Requires IP Office 4.1+.

*3: Requires IP Office 4.2+.

IP Office 4.0 and higher supports SIP trunks using UDP or TCP. For UDP SIP, STUN is supported for NAT Firewall traversal. Otherwise use of a service provider supporting Session Border Control (SBC) is required. TURN, sometimes used for TCP SIP traversal of NAT firewalls, is not supported.

The IP Office implementation of SIP conforms to the following SIP RFC's.