trinetintl
Vendor
Anybody out there knows how to add features to the SNOM m9 such as Park a call? I just can't figure it out? Can the SNOM m9 be actually programmed to park a Call?
RE
APSS - SME
ACIS - SME
RE
APSS - SME
ACIS - SME
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Supported functionality for SIP endpoints in IP Office
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.
In order to use a non-Avaya SIP endpoint with IP Office, a "Third party IP endpoint license" is needed. This license will continue to support endpoints based on the H.323 standard but will also be required for generic SIP endpoints on IP Office. Avaya IP Office SIP telephones use the IP End Point license.
SIP Endpoint support is fully integrated into IP Office core. No other components are needed. SIP endpoints will need VCM module capacity in IP Office like any other IP phone.
Next to SIP telephones, SIP terminal adapters are supported to connect analog telephones and fax machines. This offers a flexibility to support Fax machines and Audio/T.38
SIP extensions function like any other IP Office extension: This means they
• Can make and receive calls to any other extension, independent of type of extension
• Delivers end to end Media just like any other IP telephone on IP Office. For calls between two SIP extensions of a SIP extension and an Avaya IP telephone, the audio is transmitted end to end for basic telephone calls. (Conferences etc. However require a VCM resource). See chapter "VCM modules" for details
• Can use short codes and authorization codes like any other telephones
• Transmit In band call progress tones are delivered from IP Office
• A SIP telephones needs to register with IP Office like any other IP telephone, Authentication with Username and password is possible
• SIP extensions support "auto create" in IP Office to make installation fast and efficient. Successful registration of an endpoint will consume one third party license
• On one IP address, several extensions can register with IP Office, each consuming a license. This enables the connection of SIP terminal adapters with more than one analogue port, giving a different extension number to each of the ports.
Advanced features:
SIP endpoints support a number of extended features according to the "SIP service samples-draft", also referred to as "Sipping-19". This includes:
• Calling line identification
• Hold/Consultation Hold
• Attended/Unattended Transfer
• Message Waiting
• Do not disturb
• Conference Add
Some telephones support several call appearances making it easy to switch between calls. Please not that this does not include "bridged appearances" or " (outside)-line appearances)
A large number of additional features are supported on IP Office using Feature activation keys. These features include but 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
SIP endpoints also support Computer Telephony Integration “CTI” and therefore applications like One-X portal for Small business: the following features are supported with One-X portal and via the TAPI interface:
• Outgoing call (without remote activation of speakerphone/headset)
• Hang up
• Hold
• Attended/Unattended transfer
• Conference (IP Office based)
• Voicemail collect
• Set forwarding/DND (IP Office based)
• Park/Ride (IP Office based)
The features work similar like "CTI" features in combination with an analog telephone, e.g. an outgoing call will first ring the SIP phone and after connect the outgoing call will be placed. Avaya Phone Manager/ Phone Manager Pro and Soft console are currently not supported in combination with SIP-endpoints.
Session Initiation Protocol
•Rec. E.164 [2] - ITU-T Recommendation E.164: The international public telecommunication numbering plan
•RFC 2833 [7] - RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
•RFC 3261 [8] - SIP: Session Initiation Protocol
•RFC 3263 [10] - Session Initiation Protocol (SIP): Locating SIP Servers
•RFC 3264 [11] - An Offer/Answer Model with Session Description Protocol (SDP)
•RFC 3323 [14] - A Privacy Mechanism for the Session Initiation Protocol (SIP)
•RFC 3489 [18] - STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
•RFC 3824 [24] - Using E.164 numbers with the Session Initiation Protocol (SIP)
•RFC 1889 – RTP
•RFC 1890 - RTP Audio
•RFC 4566 – SDP
•RFC 3265 - Event Notification
•RFC 3515 - SIP Refer
•RFC 3842 - Message Waiting
•RFC 3310 – Authentification
•RFC 2976 – INFO
•RFC 3323 - Privacy for SIP (PAI) and draft-ietf-sip-privacy-04 (RPID)
they just know it should work because they are using the SIP standard