SIP endpoints are supported on IP Office audio (voice) and T.38 fax communication using SIP terminal adapters. Users can use standards-compliant IP phones using the open SIP standard, offering a choice of endpoints including special purpose devices such as conference phones, hotel phones and terminal adapters.
Prolog information
Metadata
Keywords:
IP Office supports Avaya 1100 and 1200 series phones using the SIP protocol. The phone user interface can vary when used on BCM with UNIStim. For example, with SIP, the 1100 and 1200 series IP phones only support a single call appearance although multiple calls are supported by the 1100 and 1200 series phones.
Note:
These phones are only supported on IP500 V2 control units.
In pure SIP systems, IP Office expands the feature set beyond the SIP standard offering features on SIP endpoints delivering features consistently between SIP and Avaya digital and IP endpoints.
Note:
In order to use a non-Avaya SIP endpoint with IP Office, obtain a Third-party IP Endpoint license from Avaya. This license supports endpoints based on the H.323 standard and is required for generic SIP endpoints on IP Office. Avaya IP Office SIP phones use the Avaya IP Endpoint license.
PSTN toll bypass
Toll bypass allows each system to leverage the trunk connections of the other system in the network to avoid international and long distance charges.
Standard call features
Basic Call Completion
Handling of busy called party
DTMF and ring-back tone
Hold and Retrieve
Transfer
Call Waiting presentation
Called Number display
Calling number and name display
Abandoned call
Single call appearance
Advanced call features
SIP endpoints support a number of extended features according to the SIP service samples, also referred to as Sipping-19. Features include:
Calling line identification
Hold/Consultation Hold
Attended/Unattended Transfer
Message waiting
Do not disturb
Conference Add
From in Clear when privacy is requested
User agent header (configurable) included to identify call in SIP trunks for troubleshooting
Busy lamp keys with speed-dial, status indication, and pickup
Self-labeling feature keys for softkey support including a Special feature key. The supported features are also available pressing a feature key plus the appropriate feature code. The feature codes are identical to the features codes from BCM
Feature activation key features
A large number of additional features are supported on IP Office using feature activation keys. These features include but are not limited to:
Call forward: Unconditional/Busy/no Answer
Follow me
Park/Unpark
Music on Hold
Meet me conferencing
Conference join
Ring back when free
Multiple call appearances
Note:
Does not include bridged appearances or outside-line appearances.
CTI features
The new centralized CTI web service API provides a more open platform to allow third parties add value and build solutions. Support is provided for distributed (IP Office Server Edition and SCN) environment – not limited to nodal as per current TAPI. Centralized CTI web service API is dependent on Avaya one-X® Portal access for the users. Creating a new user in IP Office with the new API does not require a reboot. SIP endpoints support the following CTI-based features using the TAPI interface:
Outgoing call (without remote activation of speakerphone/headset)
Hang up
Hold
Attended/Unattended transfer
Conferencing
Voicemail collect
Set forwarding/DND (IP Office based)
Park/Ride (IP Office based)
Video conferencing
Video conferencing is supported in the following configurations:
Local system
Small community network
Video-ready SIP trunk such as Avaya Aura®
All video communication is end-to-end; IP Office does not natively manage or perform video conferencing.
The softphone application handles video conferencing. IP Office video conference supports the following features using feature access codes:
Make calls to all phones and trunk lines as audio only
Receive audio calls
Call forwarding
Forward to voicemail recording audio streams, not video.
Application sharing
Accept several video calls in parallel to leverage the Multi-Conference Unit (MCU) functionality, for example, the Avaya 1040 system
Video requires high network bandwidth, depending on codec video quality it can be up to 1 Mbit/sec. IP Office supports with H.263 and H.264 codecs. During planning, a network assessment identifies the bandwidth requirements. Refer to product details for video requirements. Typical bandwidth requirements for HD video are:
1010: 1 Mbps for 720p/30fps
1040:
768 Kbps for 720p 30fps
1.1 Mbps for 720p 60fps
1.7 Mbps for 1080p 30fps
Parameters for passing User to User Information (UUI)
IP Office passes on the received UUI information element back to the public network in case of a transit call. This feature is supported only on SIP trunks and the UUI information element is not passed internally to other elements in the solution such as IP Office Contact Center, , and so on. The UUI information is not mapped to any other trunks types such as ISDN or H.323. IP Office carries the UUI information using a proprietary IP Office field.
Two new parameters are added in the SIP Advanced tab, Identity group, called Add UUI header and Add UUI header to redirected calls. The Add UUI header to redirected calls field is dependent on the Add UUI header field and can be selected only when Add UUI header is selected. The default value for the field is false. These configuration items are a mergeable feature and applicable to Standard and Server Edition mode on all supported IP Office platforms.
SIP Line Appearances
Trunk line selection enables the familiar line appearance operation on Powered by Avaya (Release 3.0) or IP OfficeEssential Edition, Server Edition, and IP OfficeSelect. The feature provides easier migration from familiar analog line appearances to SIP line appearances. Line appearance buttons for SIP URIs looks and operates in the same way as the analog trunk appearances. SIP trunk appearances is supported on all phones that support line appearances.
Route incoming SIP trunk calls based on an optional SIP header
This feature enables IP Office to route incoming SIP trunk calls based on optional SIP header P-Called-Party. IP Office reads the P-Called-Party ID header in the SIP message and routes the incoming SIP calls based on it. As P-Called-Party-ID is an optional header it is not parsed by default and it has to be explicitly configured. IP Office uses it for call routing only when the configuration option is selected and the header is present in the incoming SIP call. If the configuration item is checked and the header is not present IP Office uses the header configured in Call Routing Method for Incoming Call Route. P-Called-Party-ID is not used for SM trunks and SIP phones and IP Office does include this header in any outgoing messages.
Security enhancements for registration of SIP devices
This security enhancements enable administrators to allow or disallow registration of SIP devices in IP Office based on their User Agent strings. Administrators can use the configuration settings to add, modify, or remove SIP User Agent strings to SIP UA Blacklist, SIP UA Whitelist, and IP Whitelist. Subsequently, the Allowed SIP User Agents setting can be used to select which SIP User Agents are allowed for registering with IP Office. A default blacklist comes preconfigured with some known malicious user agent strings and can be updated as required. The lists can be configured using Web Manager and Manager.
SIP and H.323 Registrars disabled by default
For enhanced security with IP Office R 11.0 FP4, the H.323 and SIP Registrars are disabled by default. Whenever a new H,323 or SIP extension is added and the corresponding registrar is not enabled, IP Office system displays a warning message and prompts administrators to enable the Registrars. When resiliency support is enabled on an IP Office Line in systems having IP extensions and the systems do not have the corresponding registrars enabled, IP Office system displays a warning message and prompts administrators to enable the corresponding registrars.