The phone-only mode of Cisco Jabber CSF devices is also supported. In CME-10.5 this type is deprecated and the new ‘Jabber-CSF-Client’ should be used to configure Cisco Jabber client as well.Ĭisco Jabber CSF client can be provisioned in 2 modes: Full UC mode (with integrated IM and Presence services) and Phone only mode. In CME-10.0 we used the type ‘Jabber-Win’ to configure Cisco Jabber client. This can be used to configure any CSF based Cisco Jabber client. Therefore, you should configure the secure HTTP on Cisco Unified CME.Ī new phone type, ‘Jabber-CSF-Client’ has been added to configure the Cisco Jabber client under voice register pool. The device discovery process uses HTTPS connection. You should configure the username and password under voice register pool to identify the user logging into Cisco Unified CME through Cisco Jabber client. The client is identified by a device ID name that can be configured under the voice register pool in Cisco Unified CME. The following Unified CME features are not supported with Cisco Jabber:Ĭisco Jabber Client is a SIP-based soft client with integrated Instant Messaging and presence functionality, and uses the new Client Services Framework 2nd Generation (CSF2G) architecture.ĬSF is a unified communications engine that is reused by multiple Cisco PC-based clients and mobile clients. Voice Hunt Group (Sequential, Parallel).
Unified CME supports supplementary services such as Hold, Resume, Transfer, Call Park, and Call Pickup for the softphone SIP client.įrom Unified CME 12.5 onwards, Cisco Jabber CSF 12.1.0 client for MAC and Windows (phone-only mode) is supported. Jabber versions 9.0.x is End of Life and Unified CME 12.5 is the minimum version required for Cisco Jabber client support on Unified CME. The SIP softphone client is capable of supporting VoIP over WLAN. Unified CME Releases 12.5 and later support Cisco Jabber (The Jabber version supported on Unified CME Releases 8.6 to 10.5 is now End-of-Life).
0 kommentar(er)
