Telefonix pay the utmost attention to going the extra mile to help you understand technology and to make your technology acquisition a transparent, comfortable one, backed up by as much information as you need and as many demonstrations as you should ever want. That's why we're here - to help you.
Telefonix credentials include Avaya SME Expert, Avaya Partner in Customer Excellence and Microsoft Small Business Specialist. Besides our experience of the IP Office system with over 2500 installs under our belt, Telefonix Voice & Data also has a unique set of IP Office phone system packages unique to the UK.
Talk To Us We know everything there is to know about IP Office. If you have an unusual requirement, talk to us!
Demo Spend some time with us going over your project in detail, make sure it does exactly what you need.
Session Initiation Protocol (SIP, as in sipping from a fire hose on a hot day) is an open signaling protocol standard developed by the Internet Engineering Task Force (IETF) in cooperation with many industry leaders, including Avaya, for establishing, managing, and terminating real-time communications over large IP-based networks, such as the Internet. Communications via voice, video, or text (instant messaging), may take place using any combination of SIP-enabled devices, such as a softphone on a laptop computer, a wireless handheld device or PDA, a mobile phone, an instant messaging client on a desktop PC, or an IP phone with videoconferencing capabilities. SIP makes it possible to easily connect the various components of an overall communications system, rapidly deploy applications, reduce costs, and improve customer service and employee productivity by simplifying your organization's communications architecture. Vendors are increasingly incorporating SIP into their various IP communications products and Avaya with IP Office is no exception.
Avaya IP Office supports SIP for telephony functions to enable the usage of standard based SIP endpoints for Voice and Fax communication. In pure SIP systems, IP Office expands the feature set beyond the SIP standard, offering a wealth of IP Office features also on SIP endpoints delivering a feature rich system that a pure-SIP server based on the SIP standard only can't deliver. With that, IP Office delivers the best of both worlds, supporting standard based IP telephones while delivering a wealth of features consistently between SIP, digital and Avaya IP endpoints. IP Office SIP endpoint implementation is built on two major SIP components: SIP User agents, and SIP Server components.
IP Office has implemented the required functionaliy of the SIP servers mentioned below not only to provide SIP endpoint support but also to allow full interoperability between SIP endpoints, other IP telephones based on H.323, Digital and Analog telephones as well as IP Office trunks (Analog, digital or SIP based) SIP servers provide centralized information and enablement services in a SIP ecosystem. The core SIP servers and their functions are summarized here. IP Office provides the required the features of the following two servers for Voice and FAX communication.
When SIP IP telephones come online, they need to make sure that others are aware that they're available to take and make calls. The Registrar authenticates and registers the IP phone (often directly related to a specific user) when it comes online, and then stores information on the telephones logical identities.
A proxy server takes SIP requests, processes them, and passes them downstream while sending responses upstream to other SIP servers or devices. A proxy server may act as both a server and a client, and can modify a SIP request before passing it along. A proxy is involved only in the setup and teardown of a communication session. After user agents establish a session, communications occur directly between the parties. Functionality of the following two SIP servers are generally available by IP Office using existing IP Office functionality. Therefore, while functionality is provided, e.g. allowing hotdesking (also for users using a SIP-endpoint) in a small community network, a consistent methodology between SIP and non SIP endpoints is used to deliver those features.
As users roam, the network needs to be continually aware of their locations. The location service is a database that keeps track of users and their locations. The location service gets its input from the registrar server and provides key information to the proxy and redirect servers. IP Office provides hotdesking support, delivering a similar functionality but working consistently between SIP and non SIP endpoints.
If users are not in their home domains, sessions bound for them needs to be redirected to them. The redirect server maps a SIP request destined for a user to the device "closest" to the user. In IP Office, call forwarding and Follow me functionality is used to provide again consistent functionality between all type of endpoints.
SIP endpoints are supported on IP Office for Voice (Audio) and Fax (T.38) communication. This allows the usage of standard compliant IP telephones using the open SIP standard, giving customers a choice of endpoints of different manufacturers including special purpose devices like conference telephones, hotel telephones or terminal adapters. There is a wide variety of SIP endpoints that work with IP Office. SIP Endpoint support is fully integrated into IP Office core and no other components are needed. SIP extensions function like any other IP Office extension: This means they
Service Providers continue to broaden their SIP trunk offerings and SME customers are increasingly evaluating and adopting SIP trunks. IP Office R8.0 responds to these market trends, with several new SIP trunk capabilities, designed to simplify and address a wider set of implementation scenarios.
SIP Trunk Harmonisation: In prior releases of IP Office there were several differences between features supported with SIP trunks in Standard Mode vs. Partner/Norstar Mode. R8 includes additional alignment of features between the various modes of operation, thus increasing the flexibility to deploy SIP trunks in an increasing number of IP Office installations.
Early Media and Support for PRACK: SIP trunks can be configured to support early media by adding '100rel to Supported' header in the INVITE: This allows support for in-band announcements such as: branding from discount or bulk long distance providers; caller comfort in terms of progress indications when extraordinary wait times are inherent in the call scenario, for instance when trying to locate a cell phone; as well as, the ability to provide country specific ring back and other progress tones. This feature also facilitates the ability to set up conferences in the IP domain before call answer, for instance, in certain call recording scenarios or for automatic dialers' conferencing in agents.
T.38 Fax Fallback: SIP Trunks and SIP Extensions can now have the 'Fax Transport Support' configured to 'T38 Fallback' so that outgoing fax calls will use T38 fax but when the called destination doesn't support T.38 and rejects the call, a re-invite it sent for fax transport over G.711. Incoming audio calls that detect fax tones also initiate fax transport using T.38 Fallback. This enables IP Office to support additional deployments where T.38 fax may not be universally available.
Enhanced CLIR: Enable PAI and Privacy headers by default, and format 'From, PAI and Privacy'. This feature allows caller and calling party anonymity while still providing the necessary billing and traceability information (E911 services) to the network. This enhancement aligns the functionality with implementation guidelines outlined in the SIPconnect 1.1 Technical Recommendation.
Display Directory Name on In-Bound SIP Trunk Calls: IP Office Manager will now include a configuration option that will allow the selection of either the CLID or directory name as the default display for inbound calls. In previous IP Office releases only CLID display was supported over SIP trunks for incoming calls. This enhances IP Office user experience by providing the flexibility to select between personalizing the display with the personal or system directory name, and seeing the default CLID.
Template Documentation: The SIP trunk documentation covering the import of SIP trunk templates has been enhanced in R8. With the market growth of SIP trunk deployments in the SME segment, importing and using SIP trunk templates to reduce installation time and errors associated with programming, will become increasingly valuable to installers working with R8.
Relevant Tags: IP Office Info, SIP Trunking, IP Office SIP Trunking, Avaya IP Office SIP Trunking, IPO SIP Trunking, IP500 SIP Trunking, IP500V2 SIP Trunking, SIP Trunking for IP Office, SIP Trunking for IP Office IP500, SIP Trunking for Avaya IP Office IP500V2