Allows message archiving (if enabled) across systems.Allows group chat sessions across systems.Server-to-server federation with Google Talk.Server side federation with other public IM systems (based on Kraken IM Gateway) including:.Call initiation using corporate dialplan.Enables Fixed Mobile Convergence (FMC) application.Integration of user profile information and avatar (pending).Message archiving and search for compliance (pending).dynamic call routing based on user's presence status.Customizable "on the phone" presence status message.Federation of phone presence with IM presence.Personal group chat room for every user auto-configured.Auto-configuration of user's IM accounts.New role in sipXecs cluster management for IM/presence.XMPP based IM and presence server based on Openfire.
#Freeswitch autoanswer full#
(for a future release we will add full survivable branch capability based on the sipXecs cluster - see XX-4819)Įnterprise Instant Messaging (IM) and Presence
Certain sipXecs services can be deployed in the branch as part of the cluster (e.g. Survivable branch configuration possible with Audiocodes gateways SAS functionality (auto-configured). Branch postal address automatically proliferates to user's office address. Source routing allows call routing based on location (branch local calls are routed through local gateway preferably). A PSTN gateway can be available for calls that originate in a specific branch only or for general use. Users, phones, gateways, SBC, and servers can be assigned to a branch location. Branch office locations can be defined in the mgmt UI with a postal address. Distributed deployment: Branch provides full call server with SIP site-to-site dialing between offices. Centralized deployment: Branch only provides phones and optionally PSTN gateway for failover, reduced WAN BW consumption or E911 calls. Internal notification using email and SMS. Auto-generation of directory information. Configuration of individual Speed Dial softkeys. Call history (dialed, received, missed). The source of the call for example, when a lobby phone can only initiate calls to internal numbers. The destination of the call for example, when a user or device cannot initiate an international long distance call. Outbound call blocking - Calls from phones to PSTN numbers, or classes of numbers, can be blocked based on:. Forward on busy, no answer, do not disturb. CLIR (Call Line Identification Restriction). CLIP (Call Line Identification Presentation). CNIP (Calling party Name Identification Presentation). Intercom with auto-answer (bi-directional). Call pickup (global and directed call pickup). 3-way / 5-way video and voice conference on the phone. New: Shared lines (BLA) for boss - secretary applications (Polycom only). Admin or user configurable Busy Lamp Field (BLF) presence and softkeys. MoH music from an external streaming source. Music on Hold for IETF standards compliant phones. All components centrally managed using XML RPCĬore Calling Features (Telephony Features). Web Services REST interface for user portal functions and third party call control. Web Services SOAP interfacefor key administrative functions. SOA Architecture / Business Process Integration using Web Services Process management server for centralized cluster management. Third party call control (3PCC) server using REST interfaces. Call Detail Record (CDR) collection & processing server. 
SIP trunking server (media anchoring and B2BUA for SIP trunking & remote worker support).New: Shared Appearance Agent server to support shared lines (BLA).Presence server (Broadsoft and IETF compliant resource list server for BLF).XMPP Instant Messaging (IM) and presence server (based on Openfire).
Conferencing server based on FreeSWITCH.Media server for unified messaging and IVR (auto-attendant) services.SIP Session Router, optionally geo-redundant and load sharing.Configuration of all services and participating servers is fully automatic and Web UI based. Using the centralized cluster management system each role can be instantiated on a dedicated server or several (all) roles can be run on a single server. All the sipXecs application services are allocated to specific server roles.
0 kommentar(er)
