CN112969203B - Method for integrating multiple call modes based on android system platform - Google Patents

Method for integrating multiple call modes based on android system platform Download PDF

Info

Publication number
CN112969203B
CN112969203B CN202110131088.0A CN202110131088A CN112969203B CN 112969203 B CN112969203 B CN 112969203B CN 202110131088 A CN202110131088 A CN 202110131088A CN 112969203 B CN112969203 B CN 112969203B
Authority
CN
China
Prior art keywords
android
call
mode
soft phone
platform
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110131088.0A
Other languages
Chinese (zh)
Other versions
CN112969203A (en
Inventor
李虎
曾毅峰
王之良
高晖
金科
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Pudong Development Bank Co Ltd
Original Assignee
Shanghai Pudong Development Bank Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Pudong Development Bank Co Ltd filed Critical Shanghai Pudong Development Bank Co Ltd
Priority to CN202110131088.0A priority Critical patent/CN112969203B/en
Publication of CN112969203A publication Critical patent/CN112969203A/en
Application granted granted Critical
Publication of CN112969203B publication Critical patent/CN112969203B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

The invention relates to a method for integrating multiple call modes based on an Android system platform, which is characterized in that Android end codes adopt a self-defined View as a carrier of a soft phone service frame, after the self-defined View is instantiated, the soft phone View is added to a system's window layer of Android through a Windows manager, a Windows layer of the Android is used as a basic layer of a project entity UI, a MVP (multifunction virtual machine) architecture is adopted to conduct main frame layering adaptive to a webRTC (real time clock) passing mode on a soft phone service, four external call interfaces are packaged in a soft phone flow, and soft phone service interaction between the Android end soft phone and the service is realized through message transmission of a web end and an Android end, internal message transmission of the Android end and message transmission of a service end. Compared with the prior art, the method and the device have the advantages of ensuring the call quality, having good environmental adaptability, being suitable for the requirements of complex service scenes and the like.

Description

Method for integrating multiple call modes based on android system platform
Technical Field
The invention relates to the technical field of communication, in particular to a method for integrating multiple call modes based on an android system platform.
Background
The webRTC is an API supporting a web browser to perform real-time voice conversation or video conversation, and provides functions of audio and video acquisition, encoding and decoding, network transmission, display and the like. The method can realize the processing of the media stream, the echo cancellation and the like through an Opus audio encoder, a soundmouth open source audio processing frame and the like. The webRTC side is focused on the implementation of the BS architecture, but lacks a mature server design and deployment solution. The Opus audio encoder, the soundmouth open source audio processing framework and the like can be adopted in some links, but a whole set of solution cannot be provided at an android mobile terminal, and the speech stream is transmitted depending on data flow in a weak network environment, so that the conversation quality cannot be ensured.
Disclosure of Invention
The invention aims to overcome the defects in the prior art and provide a method for integrating multiple call modes based on an android system platform.
The purpose of the invention can be realized by the following technical scheme:
a method for integrating multiple call modes based on an Android system platform comprises the steps of taking an Android end code as a carrier of a soft phone service frame, adding the soft phone View to a system's window layer of Android through a Windows manager after the user-defined View is instantiated, taking a Windows layer of the Android as a basic layer of a project entity UI, adopting an MVP (multifunction vehicle platform) framework to adapt to a main body frame layer of a webRTC (real time clock) passing mode for the soft phone service, packaging four external call interfaces for a soft phone flow, including a dialing external call interface, a resetting external call interface, a calling core external call interface and a refreshing state external call interface, and realizing soft phone service interaction between the Android soft phone and the service through message transmission of a web end and an Android end, internal message transmission of the Android end and message transmission of a Services end.
Further, the MVP architecture is adopted to carry out main body framework layering on the soft phone service, the main body framework layering comprises a data receiving layer, a page carrier layer and a logic processing layer, and the webRTC and the double-call mode share the data receiving layer to receive main body parameters of the soft phone service.
The page carrier layer comprises a public part and a characteristic part, the public part comprises necessary display parameters in the soft phone, the characteristic part comprises a function menu adapted to the webRTC call mode, and the public part and the characteristic part are clicked by a permission seat to realize switching.
The logic processing layer sets independent presenters for the two modes according to the two communication modes of the soft phone, and sets a shared BasePrester base class for the two modes.
Furthermore, when the soft phone View is initialized, the presenters objects of the two call service modules are respectively instantiated, when the soft phone process is initiated, the main parameters of the soft phone are received by a common Model, the main parameters are distributed to different presenters for processing according to different modes after being analyzed, and the logic method of each call service module is only realized in the independent presenters.
Further, the message transmission between the web end and the Android end comprises a web calling Android method and an Android calling web method. The Android-side internal message transmission comprises a message transmission tool and an interface callback between the components. The Android end and the Services end adopt communication modes of Socket and Http for message transmission.
After a user logs in an android system, when a two-way calling mode is selected or switched, a calling party calls an identity verification request in a voice communication process through a unified API (application programming interface), when the two-way calling mode is selected or switched, the calling party initiates a conference request, a consultation request, a transfer request, a holding request or a hang-up request through the unified API, when the two-way calling mode is selected or switched, the user dials outwards and initiates an HTTP request to a soft switching platform, the soft switching platform analyzes data after receiving the HTTP request, and the calling party and a called party are firstly called according to the communication numbers of the calling party and the called party obtained through analysis; calling the called party after the calling party is connected, and bridging the conversation between the calling party and the called party by the soft switch platform after the called party is connected so as to realize voice communication between the two parties; when the mode is selected or switched to the webRTC mode, the android mobile platform initiates outbound through an API program, the soft switch platform connects the android mobile platform with the called party telephone, and then voice communication conversation between the two parties is realized, and a conference request, a consultation request, a transfer request, a hold request or a hang-up request is initiated through a unified API interface in the conversation process.
The webRTC mode maintains two websocket long connections between the soft exchange platform and the android client program, one websocket long connection performs signaling data interaction, and the other websocket long connection performs voice stream data transmission; in the webRTC mode, the android mobile platform is based on a uniform API (application program interface), the android mobile platform successfully logs in as a ready state by using a correct extension number and a correct password, and the soft switch platform receives a voice call initiated by a client from a client incoming line to the ready android mobile platform.
Compared with the prior art, the method for integrating the multiple call modes based on the android system platform provided by the invention at least has the following beneficial effects:
1) The invention is based on an android mobile platform, integrates a two-way calling soft phone technology mainly relying on voice communication 2G/3G signals of an operator and a webRTC voice communication technology mainly relying on voice communication 4G \5G signals of data flow, and provides an instant voice communication solution which has good environmental adaptability and rich functions;
2) The problems that in the mobile office process, the wireless network environment is poor and 4G communication signals cannot be guaranteed are solved through mode switching;
3) The invention can meet the requirement of rich functions at the same time, and under the scene of better wireless data environment, the equipment switched to the webRTC mode has rich soft phone functions of calling, transferring, meeting, consulting and the like so as to be suitable for the requirement of complex service scene;
4) The invention encapsulates the code implementation details of the two conversation modes and provides a uniform API interface externally, so that the application integrating the assembly can be accessed efficiently and quickly and realize the soft phone function.
Drawings
FIG. 1 is a schematic diagram of an SDK logic architecture according to an embodiment of the present invention;
fig. 2 is a flow chart illustrating the implementation of multiple call modes according to the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and the specific embodiments. It should be apparent that the described embodiments are only some of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.
Examples
The invention relates to a method for integrating multiple calling modes based on an android system platform, which is based on the android mobile platform and uses an open source webRTC frame to integrate a two-way calling soft phone technology mainly relying on voice 2G and 3G signals of an operator and a webRTC voice call technology mainly relying on a data flow 4G signal. The problems that in the mobile office process, the network environment is complex and communication signals cannot be guaranteed are solved.
The specific implementation design is as follows:
in consideration of the global property, the Android end code uses the self-defined View as a carrier of a softphone service frame, after the self-defined View is instantiated, a Windows manager is used for adding the softphone View to a system's window layer of the Android, a Windows layer of the Android is used as a basic layer of a project entity UI, and all page elements are based on Windows, so that the softphone View can exist in the system without being attached to any parent View related to the service, and the global property of the View is ensured.
The MVP architecture, namely M (model), V (View) and P (Presenter), is adopted, and according to the hierarchy, the main framework of the soft phone service is roughly divided into a data bearer class, a page carrier class and a logic processing class. Wherein the webRTC shares the data bearer class with the dual call to receive the subject parameters of the softphone service.
The page carrier class is divided into two parts, a public part and a characteristic part, wherein the public part is the necessary display parameters of the soft phone, such as soft phone parameters, extension numbers and call duration \8230, in the soft phone, and the characteristic part is mostly adapted to the webRTC call mode and mainly comprises functions of a function menu, dialing/answering and the like. The two page types are switched by manually clicking by the permission agent.
The logic processing class serves as the core of the overall architecture, whose responsibility is the processing of the business logic. According to the characteristics that the soft phone has two communication modes and the underlying logics based on the two communication modes are completely different, the two modes respectively have own presenters, the two presenters are represented as two presenters implementation classes in codes, different business logics in each flow of the soft phone are processed in the respective presenters, but the different business logics are inherited to a common BasePrester base class, so that a factory or an abstract factory method in a parent class can be shared, and the same characteristics of a small part of the two modes in code implementation can be processed.
The method comprises the steps of respectively instantiating the Presenter objects of two modules during initialization of the softphone View, receiving main parameters (interface uniformity) of the softphone by using a common Model when a softphone process is initiated, distributing the main parameters to different presenters for processing (service module independence) according to different modes after analysis, and only realizing the logic method of each module in the independent presenters, wherein even if the module carries out requirement iteration (code development expansibility) in the later stage, the code implementation (service module independence) of the other module cannot be influenced, and in sum, the softphone module takes the MVP as an architecture mode.
The interface design is based on the principle of unity, and the soft phone flow totally encapsulates four external calling interfaces: dialing a call, resetting ready, invoking a kernel and refreshing a state.
The interfaces (for dialing and calling the kernel) needing to enter the parameters (the value of the entered parameter is needed by the called function) all use String as a data receiving object, the calling party packages the String in the Json format for parameter transmission, and the main entered parameter in the soft phone process is various information of the client;
in the back-entry design, when the call is placed and the initiation interface is called, the Android end receives the parameters, then the Android end can hold the method in the sub-thread, after the asynchronous request returns the result, the sub-thread is notified to fetch the request result, and the back entry is returned;
overall, code design modes such as singleton mode, factory mode, builder mode, agent mode, adapter mode, and the like are used in common.
The SDK logic architecture diagram of the method of the present invention is shown in fig. 1. The method comprises the following steps that three message transmission scenes are involved in a soft phone module, namely, message transmission between a web end and an Android end, message transmission inside the Android end, and message transmission between the Android end and a Services end, and based on the three message transmission scenes, the Android end soft phone module realizes soft phone service interaction with specific Services;
the soft phone SDK can realize the calling of a multi-type platform at present, the basis of establishing the message transmission mode of the web and the Android is that a web end is used as a calling party or a user of the soft phone function, the message transmission is divided into two scenes, the web calls an Android method and an Android calls a web method, and the message transmission medium of the two scenes is JS (JavaScript).
1. The web calls an Android method:
the Android end customizes a JS method receiving class WebJavaScript INTERFACE to declare the JS receiving method at the Android end, and specifies an INTERFACE name for calling the Android Js method by the web end, for example, "JS _ INTERFACE" is used as the INTERFACE name for calling the Android Js method by the web end;
2. android calls a web method:
on the contrary, the Android end executes the corresponding method of the web end through the evaluateJavascript of webView to realize message transmission;
3. android-side internal messaging
The transmission of internal information of the Android terminal is completed in two modes, namely, a message transmission tool and an interface between components are called back;
1. inter-component messaging facility
Based on the message list iterative query and reflection principle in the EventBus message transmission mechanism, the message transmission is realized through the user-defined Tag, and the data transmission is realized for the soft phone module by a calling party in the soft phone flow under the condition that the calling party does not hold a soft phone object.
2. Interface callback
As a main data transmission means of the MVP mode, a callback object is created in a View layer and is realized in a Presenter, and finally the purpose of updating the View is completed by logic processing.
4. Android end and Services end message transfer
And the Android end communicates with the Services end, and communication modes related to the Android end are Socket and Http.
1.Socket
The webRTC and the dual call are developed based on different platforms, so that the webRTC and the dual call respectively maintain a long connection. The functions of the two are the same, and the Android terminal receives the real-time state of the softphone under polling connection. The Socket of the double call is always in a connection state, and the Socket of the webRTC can be started only when the softphone mode is the webRTC; the two long connections use the same reconnection strategy, namely after the Socket disconnection is detected, starting five groups once, wherein each group has an interval of five seconds, the maximum connection times are fifty times, and when the reconnection is successful, the reconnection parameters are reset;
2.Http
the soft phone has the core processes of ringing, connecting, body checking, hanging up and summarizing, wherein when the webRTC receives all the events, the webRTC sends the events through an Http request and inserts or updates the recording parameters of the database in the corresponding events; the double-call sends the recording parameters to the server only when hanging up, and other processes are completed by the server.
As shown in fig. 2, the process of implementing multiple call modes based on the method of the present invention specifically includes the following contents:
the user first logs in the android system. After logging in, the android system selects or switches the soft phone mode, namely selects or switches the two-way calling mode or the webRTC mode.
When the user selects or switches to the outbound in the double call mode, the user dials outwards and initiates an HTTP request to a soft switch platform (hereinafter referred to as a platform) through a soft phone SDK, and the Freeswitch soft switch platform can be preferentially used. The platform analyzes the data after receiving the request, and calls the calling party according to the communication numbers of the calling party and the called party obtained by analysis; the calling party calls the called party after being picked up, and the platform bridges the conversation between the calling party and the called party after the called party is picked up, so that the voice communication between the two parties is realized. Based on the voice channel, the two parties use respective mobile phones/telephones to carry out conversation. During the call, the calling party can initiate identity verification through the exposed API, the component initiates identity verification to the micro-service interface through the HTTP request, at the moment, the platform suspends the calling party, the called party enters an IVR voice flow, and the client can verify identity information according to voice prompt. And the long connection established by the websocket can push real-time soft phone states including information such as connection, hang-up and core result to the client side while talking.
When the mode is selected or switched to the webRTC mode, the android device in the webRTC mode has the function of instant messaging, an outbound call can be initiated through an API program exposed by the component, and requests such as a conference, consultation, transfer, hold, hang-up and the like can be initiated through the API in the conversation process. The webRTC mode can maintain two websocket long connections between the soft switch platform and the android client program, one of the websocket long connections carries out signaling data interaction, and the other of the webRTC long connections carries out voice stream data transmission, namely, the voice stream data is transmitted to the soft switch platform through the client mobile phone and then is tied to the android program. While the webRTC mode supports customer incoming lines. Only after the program successfully logs in through the API login interface by using the correct extension number and the password and is set to be in a ready state, the Freeswitch soft switch platform can be switched to the android device ready for the client to enter in, and the voice call initiated by the client is received. And information such as sound records, logs and the like generated in the call process can be synchronously stored in a database or NAS storage equipment.
While the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (7)

1. A method for integrating multiple call modes based on an Android system platform is characterized in that Android end codes adopt a self-defined View as a carrier of a soft phone service frame, after the self-defined View is instantiated, the soft phone View is added to a system's window layer of Android through a Windows manager, a Windows layer of the Android is used as a basic layer of a project entity UI, an MVP (multifunction vehicle platform) architecture is adopted to conduct main frame layering adaptive to a webRTC (real time clock) passing mode on a soft phone service, four external call interfaces are packaged for a soft phone process and comprise a dialing external call interface, a reset ready external call interface and a refresh state external call interface are called, and soft phone service interaction between the Android soft phone and the service is realized through message transfer of a web end and the Android end, internal message transfer of the Android end and service ends;
the method comprises the steps that a MVP framework is adopted to conduct main body framework layering on the soft phone service, the MVP framework comprises a data carrying layer, a page carrier layer and a logic processing layer, and the webRTC and a double-call mode share the data carrying layer to receive main body parameters of the soft phone service;
the page carrier layer comprises a public part and a characteristic part, the public part comprises necessary display parameters in the soft phone, the characteristic part comprises a function menu adapted to the webRTC calling mode, and the public part and the characteristic part are clicked by a permission seat to realize switching;
after a user logs in an android system, when a two-way calling mode is selected or switched, a calling party calls an identity verification request in a voice communication process through a unified API (application programming interface), when the two-way calling mode is selected or switched, the calling party initiates a conference request, a consultation request, a transfer request, a holding request or a hang-up request through the unified API, when the two-way calling mode is selected or switched, the user dials outwards and initiates an HTTP request to a soft switching platform, the soft switching platform analyzes data after receiving the HTTP request, and the calling party and a called party are firstly called according to the communication numbers of the calling party and the called party obtained through analysis; calling the called party after the calling party is connected, and bridging the conversation between the calling party and the called party by the soft switch platform after the called party is connected so as to realize the voice communication between the calling party and the called party; when the mode is selected or switched to the webRTC mode, the android mobile platform initiates outbound through an API program, the soft switch platform connects the android mobile platform with the called party telephone, and then voice communication conversation between the two parties is realized, and a conference request, a consultation request, a transfer request, a hold request or a hang-up request is initiated through a unified API interface in the conversation process.
2. The android system platform-based multiple call mode integration method of claim 1, wherein the logic processing layer sets independent presenters for the two modes according to the two communication modes of the softphone, and sets a common baseplayer base class for the two modes.
3. The android system platform-based multiple call mode integration method as claimed in claim 2, wherein, when a softphone View is initialized, presenters objects of two call service modules are instantiated respectively, when a softphone flow is initiated, main parameters of the softphone are received by a common Model, after parsing, the main parameters are assigned to different presenters for processing according to different modes, and a logic method of each call service module is implemented only in the presenters which are independent of the logic method.
4. The Android system platform-based multi-call-mode integration method as claimed in claim 1, wherein the message passing between the web side and the Android side includes a web-invoked Android method and an Android-invoked web method.
5. The Android system platform-based multiple call mode integration method as claimed in claim 1, wherein Android-side internal message passing includes inter-component message passing tools and interface call-backs.
6. The Android system platform-based multi-call-mode integration method as claimed in claim 1, wherein the communication modes adopted for message transfer between the Android terminal and the Services terminal are Socket and Http.
7. The android system platform-based multiple call mode integration method of claim 6, wherein the webRTC mode maintains two websocket long connections between the soft switch platform and the android client program, one websocket long connection performs signaling data interaction, and the other websocket long connection performs voice stream data transmission; in the webRTC mode, the android mobile platform is based on a uniform API (application program interface), the android mobile platform successfully logs in as a ready state by using a correct extension number and a correct password, and the soft switch platform receives a voice call initiated by a client from a client incoming line to the ready android mobile platform.
CN202110131088.0A 2021-01-30 2021-01-30 Method for integrating multiple call modes based on android system platform Active CN112969203B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110131088.0A CN112969203B (en) 2021-01-30 2021-01-30 Method for integrating multiple call modes based on android system platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110131088.0A CN112969203B (en) 2021-01-30 2021-01-30 Method for integrating multiple call modes based on android system platform

Publications (2)

Publication Number Publication Date
CN112969203A CN112969203A (en) 2021-06-15
CN112969203B true CN112969203B (en) 2023-03-10

Family

ID=76272178

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110131088.0A Active CN112969203B (en) 2021-01-30 2021-01-30 Method for integrating multiple call modes based on android system platform

Country Status (1)

Country Link
CN (1) CN112969203B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125053A (en) * 2021-11-19 2022-03-01 北京鲸鲮信息系统技术有限公司 Cross-system network equipment calling method and device, electronic equipment and storage medium
CN116996640B (en) * 2023-09-25 2023-12-01 北京百悟科技有限公司 Communication system and communication method

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103731565B (en) * 2012-10-12 2016-12-21 华为技术有限公司 A kind of method of calling, equipment and system realizing HD video call
US9891891B2 (en) * 2015-05-11 2018-02-13 Inteliquent, Inc. Systems and methods for integration of carrier-based SMS and voice functionality within API platform
CN206807569U (en) * 2017-06-19 2017-12-26 上海汉傲电信科技有限公司 Softphone device

Also Published As

Publication number Publication date
CN112969203A (en) 2021-06-15

Similar Documents

Publication Publication Date Title
JP2730895B2 (en) Method and apparatus for providing call transfer function
CN112969203B (en) Method for integrating multiple call modes based on android system platform
Swinehart et al. Adding voice to an office computer network
US8325738B2 (en) Apparatus system and method for web-based phone services
US20160072950A1 (en) Server for providing enhanced services to contact center agents
CN112953925B (en) Real-time audio and video communication system and method based on SIP (Session initiation protocol) and RTC (real time communication) network
CN107018504A (en) Communication means, blacklist collocation method and device
CN114401252B (en) Calling method of telephone traffic system and telephone traffic system
CN112769680A (en) Enterprise instant voice service center management method, system and storage medium
CN112822169B (en) Integration system and method suitable for seat Web telephone application system
WO2015184780A1 (en) Method, device, and system for processing information
CN108259433B (en) Call queuing distribution method, system and server
CN115002283A (en) Virtual digital man-machine telephone answering system and method
CN113572749A (en) VoLTE-based video calling method and system
CN112153224B (en) Vehicle data sending and acquiring method and related equipment
CN101123637B (en) Intelligent phone terminal, call recording device, method and system for synchronizing call record
CN111355699B (en) Voice capability implementation system
US9042528B2 (en) Data communication
KR20040022738A (en) SMS system of internet visual phone
US8498395B2 (en) Autoplay of status in teleconference via email systems
CN111142978A (en) Method and system for making call on basis of intelligent voice equipment
CN1816133A (en) Individual privacy information handling method of hand-micro-telephone
CN112583837B (en) Converged communication intelligent scheduling system
CN114979373B (en) Call realization method and device for middle number service and electronic equipment
CN115426337B (en) Online customer service system and method based on 5G message and VoLTE

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CB03 Change of inventor or designer information

Inventor after: Tie Jincheng

Inventor after: Li Hu

Inventor after: Zeng Yifeng

Inventor after: Wang Zhiliang

Inventor after: Gao Hui

Inventor after: Jin Ke

Inventor before: Li Hu

Inventor before: Zeng Yifeng

Inventor before: Wang Zhiliang

Inventor before: Gao Hui

Inventor before: Jin Ke

CB03 Change of inventor or designer information