CN111327750B - Universal programmable recording control implementation method, device and system - Google Patents

Universal programmable recording control implementation method, device and system Download PDF

Info

Publication number
CN111327750B
CN111327750B CN201811540940.4A CN201811540940A CN111327750B CN 111327750 B CN111327750 B CN 111327750B CN 201811540940 A CN201811540940 A CN 201811540940A CN 111327750 B CN111327750 B CN 111327750B
Authority
CN
China
Prior art keywords
recording
platform
service
call
standard interface
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
CN201811540940.4A
Other languages
Chinese (zh)
Other versions
CN111327750A (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.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp 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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201811540940.4A priority Critical patent/CN111327750B/en
Publication of CN111327750A publication Critical patent/CN111327750A/en
Application granted granted Critical
Publication of CN111327750B publication Critical patent/CN111327750B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/64Automatic arrangements for answering calls; Automatic arrangements for recording messages for absent subscribers; Arrangements for recording conversations
    • H04M1/65Recording arrangements for recording a message from the calling party
    • H04M1/6505Recording arrangements for recording a message from the calling party storing speech in digital form

Abstract

The invention discloses a method, a device and a system for realizing universal programmable recording control, and relates to the field of communication. The method comprises the following steps: the recording triggering unit receives the call request and then interacts with the recording service platform so as to trigger the recording service logic; the recording service platform sends the call request to the recording management platform so that the recording management platform can send the recording service logic identification customized by the customer and the corresponding standard interface parameter to the recording service platform after authenticating the call request; the recording service platform takes the standard interface parameter as the input number of the recording logic identifier and transfers the call to the recording trigger unit so that the recording trigger unit routes the call to the called side; and the recording service platform performs recording service logic processing on the call. The method and the device can realize flexible customization of the recording service logic under the conditions of not changing the dialing habit of a user, not changing numbers and not establishing a recording platform at a client side.

Description

Universal programmable recording control implementation method, device and system
Technical Field
The present disclosure relates to the field of communications, and in particular, to a method, an apparatus, and a system for implementing universal programmable recording control.
Background
With the development of internet + technology, part of industry customers have strong demands on voice call recording, and hope that the recording can be flexibly customized in the voice application scene of related industries. Currently, the mainstream voice call in the industry is recorded mainly through a recording function of a call center system built by a customer, or a recording product is provided by a newly-built recording platform.
Some of the recording implementation modes are realized based on an ISUP protocol and are not suitable for the existing network evolution requirement; some require the user to dial in the specific access code; some require the user to replace the number with a number assigned by the platform; some temporary recording operations are complicated and have a certain failure rate; some adopt three-party communication to realize the recording function, and consume resources comparatively; some users need to use independent clients to initiate calls to realize recording; the provided recording function is relatively fixed, and flexible customization can not be performed according to the application scene of the industry or dynamic interaction triggered by the recording service with the industry application system of a client before or during the call and the like.
Disclosure of Invention
The technical problem to be solved by the present disclosure is to provide a method, an apparatus and a system for implementing universal programmable recording control, which can implement flexible customization of recording service logic without changing dialing habits of users, numbers and establishing a recording platform at a client side.
According to one aspect of the disclosure, a general programmable recording control implementation method is provided, including: the recording triggering unit receives the call request and then interacts with the recording service platform so as to trigger the recording service logic; the recording service platform sends the call request to the recording management platform so that the recording management platform can send the recording service logic identification customized by the customer and the corresponding standard interface parameter to the recording service platform after authenticating the call request; the recording service platform takes the standard interface parameter as the input number of the recording logic identifier and transfers the call to the recording trigger unit so that the recording trigger unit routes the call to the called side; and the recording service platform performs recording service logic processing on the call.
Optionally, abstracting the recording service logic into an atomic capability by the recording service platform in an API (application programming interface) manner; the recording management platform combines and encapsulates different atomic capabilities into a standard interface, and the standard interface is provided for a client through an industry application platform, so that the client can call the standard interface encapsulated by the recording management platform through the industry application platform according to the industry recording requirement, and set standard interface parameters so as to customize the recording service logic; the recording management platform stores the standard interface parameters and the corresponding recording service logic, and transmits the recording number service data sent by the service activation system to the recording trigger unit so that the recording trigger unit can configure the service trigger data.
Optionally, after receiving the call request, the recording triggering unit determines whether the number in the call request activates the recording service, and if the number in the call request activates the recording service, the recording triggering unit interacts with the recording service platform based on a standard session initiation protocol SIP.
Optionally, the method further includes, before the recording service platform transfers the call to the recording triggering unit: the recording service platform judges whether to interact with the industry application platform before recording according to the standard interface parameters, if so, the calling request is pushed to the industry application platform through the recording management platform so that the industry application platform can remind a client of whether to record or not; and the industry application platform responds to the recording instruction input by the client and responds the recording instruction to the recording service platform through the recording management platform.
Optionally, the authenticating the call request by the recording management platform includes: and the recording management platform judges whether the number in the call request opens the recording service or not, and whether the recording management platform stores corresponding standard interface parameters and recording service logic or not.
Optionally, after receiving the request for calling the standard interface by the industry application platform, the recording management platform determines whether the recording number is opened, if so, determines whether the standard interface called by the industry application platform exists, and if so, stores the standard interface parameter set by the client and the corresponding recording service logic.
Optionally, the recording service platform stores the recording file after the call is recorded to the storage location of the industry application platform according to the standard interface parameters.
Optionally, the recording trigger unit comprises at least one of an IP multimedia subsystem and a soft switch.
Optionally, the interface between the recording service platform and the IP multimedia subsystem is an ISC interface for security control of the IP multimedia subsystem.
According to another aspect of the present disclosure, a general programmable recording control implementation apparatus is further provided, including: the recording triggering unit is configured to interact with the recording service platform after receiving the call request so as to trigger the recording service logic; the recording service platform is configured to send the call request to the recording management platform, and take the standard interface parameter sent by the recording management platform as the input number of the recording logic identifier to perform recording service logic processing on the call; and the recording management platform is configured to send the recording service logic identifier customized by the customer and the corresponding standard interface parameter to the recording service platform after the call request is authenticated.
Optionally, the recording service platform is further configured to abstract the recording service logic into an atomic capability in an API manner; the recording management platform is also configured to combine and package different atomic capabilities into a standard interface, and the standard interface is provided for a client through an industry application platform, so that the client can call the standard interface packaged by the recording management platform through the industry application platform according to industry recording requirements, and set standard interface parameters so as to customize a recording service logic; and the recording unit is configured to store the standard interface parameters and the corresponding recording service logic and issue the recording number service data sent by the service activation system to the recording trigger unit so that the recording trigger unit configures the service trigger data.
Optionally, the recording triggering unit is further configured to determine whether a recording service is enabled by a number in the call request after receiving the call request, and if the recording service is enabled, interact with the recording service platform based on a standard session initiation protocol SIP.
Optionally, the recording service platform is further configured to determine whether to interact with the industry application platform before recording according to the standard interface parameter, and if so, push the call request to the industry application platform through the recording management platform so that the industry application platform reminds the client whether to record; the industry application platform responds to a recording instruction input by a client, and the recording instruction is responded to the recording service platform through the recording management platform.
Optionally, the recording management platform is configured to determine whether a recording service is enabled for a number in the call request, and whether a corresponding standard interface parameter and a recording service logic are stored in the recording management platform.
Optionally, the recording management platform is further configured to determine whether the recording number is opened after receiving a request for calling the standard interface by the industry application platform, determine whether the standard interface called by the industry application platform exists if the recording number is opened, and store the standard interface parameter set by the client and the corresponding recording service logic if the standard interface called by the industry application platform exists.
Optionally, the recording service platform is further configured to store the recording file after the call is recorded according to the standard interface parameters in a storage location of the industry application platform.
Optionally, the recording trigger unit comprises at least one of an IP multimedia subsystem and a soft switch.
Optionally, the interface between the recording service platform and the IP multimedia subsystem is an ISC interface for security control of the IP multimedia subsystem.
According to another aspect of the present disclosure, a general programmable recording control implementation apparatus is further provided, including: a memory; and a processor coupled to the memory, the processor configured to execute the general purpose programmable sound recording control implementation method as described above based on instructions stored in the memory.
According to another aspect of the present disclosure, a general programmable recording control implementation system is further provided, including: a fixed-line user terminal; an industry application platform; and the general programmable recording control realizing device.
According to another aspect of the present disclosure, a computer-readable storage medium is also provided, on which computer program instructions are stored, and the instructions, when executed by a processor, implement the steps of the general-purpose programmable recording control implementation method described above.
Compared with the prior art, the recording service logic is flexibly customized under the conditions that the dialing habit of a user is not changed, the number is not changed and the recording platform is not required to be established at a client side through the information interaction of the recording trigger unit, the recording service platform and the recording management platform.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:
fig. 1 is a schematic flow chart of an embodiment of a method for implementing universal programmable recording control according to the present disclosure.
Fig. 2 is a schematic flow chart of another embodiment of a method for implementing universal programmable recording control according to the present disclosure.
Fig. 3 is a schematic flow chart of a general programmable recording control implementation method according to still another embodiment of the disclosure.
Fig. 4 is a schematic structural diagram of an embodiment of a universal programmable recording control implementation apparatus according to the present disclosure.
Fig. 5 is a schematic structural diagram of another embodiment of the universal programmable recording control implementation apparatus of the present disclosure.
Fig. 6 is a schematic structural diagram of yet another embodiment of the universal programmable recording control implementation apparatus according to the present disclosure.
Fig. 7 is a schematic structural diagram of an embodiment of a universal programmable recording control implementation system according to the present disclosure.
Fig. 8 is a schematic structural diagram of an embodiment of a general programmable recording control implementation system according to the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.
Fig. 1 is a schematic flow chart of an embodiment of a method for implementing universal programmable recording control according to the present disclosure.
In step 110, the recording triggering unit receives the call request and interacts with the recording service platform to trigger the recording service logic. The recording trigger unit includes recording trigger, and soft switch or IMS (IP Multimedia Subsystem) for carrying fixed telephone user. The recording trigger unit can realize the trigger function of the recording service of the fixed-line user, namely, the call route of the fixed-line recording needing recording points to the recording service platform.
The interface between the recording service platform and the IMS is an ISC (IMS Security Control, IP multimedia subsystem Security Control) interface. Because the intercommunication between the recording service platform and the bearing network element of the fixed telephone user is based on the standard international IMS-ISC interface, the expansibility of the application can be improved.
In step 120, the recording service platform sends the call request to the recording management platform.
In step 130, after the recording management platform authenticates the call request, the recording management platform sends the recording service logic identifier customized by the customer and the corresponding standard interface parameter to the recording service platform. For example, the recording management platform determines whether a recording service is activated by a number in the call request, whether a corresponding standard interface parameter and a recording service logic are stored, and if the recording service is activated and the corresponding standard interface parameter and the recording service logic are stored, sends a recording service logic identifier customized by the customer and the corresponding standard interface parameter to the recording service platform.
In step 140, the recording service platform uses the standard interface parameter as the entry number of the recording logic identifier, and forwards the call to the recording trigger unit, so that the recording trigger unit routes the call to the called side. For example, the recording service platform sends out a corresponding recording service logic and transfers the call to the soft switch or the IMS, and the soft switch or the IMS routes the call to the called subscriber end office in combination with the actual call routing organization rule.
In step 150, the recording service platform performs recording service logic processing on the call. For example, after the called user answers the call, the recording service platform continues to trigger the recording service logic corresponding to the user, and plays a prompt tone for the called user, and records the call.
In the embodiment, through the information interaction of the recording trigger unit, the recording service platform and the recording management platform, the flexible customization of the recording service logic is realized without changing the dialing habit of a user, changing numbers and establishing the recording platform at a client side.
Fig. 2 is a schematic flow chart of another embodiment of a method for implementing universal programmable recording control according to the present disclosure.
In step 210, the recording service platform abstractly encapsulates the recording service logic into an atomic capability in an API manner. For example, the voice recording service first interworks with the number-bearing network of the operator based on the standard SIP protocol and abstracts the call and voice recording functions in an API manner into independent atomic capabilities.
On the basis of the existing calling and recording functions of the recording service platform, in order to more flexibly realize the recording requirements of application scenes of different industries, two voice calling plugins, namely Call (originating Call) plugin and Transfer (Call forwarding), a startCall recording starting recording plugin and a stopCall recording ending recording plugin are packaged, and different interface parameters are defined in the corresponding plugins. Based on the interfaces and different parameters, different recording business logics can be flexibly customized.
For example, Call recording logic processing based on the Call plug-in includes two aspects, on one hand, parameters affecting a recording function in the Call plug-in or an event onAnswer, where the onAnswer event represents an event executed when receiving a 200OK (off-hook response) returned from the called party side after an invite Call message initiated by a Call method. Or, the startCallRecoring plug-in for starting recording is called in the onAnswer event, so that the recording can be started for the call which is called off-hook, otherwise, the recording is carried out for the whole calling process, including all signaling processes before the called user is off-hook to receive the call, and the method is suitable for recording the specific sound under the condition that the called call fails. On the other hand, only normal call sounds are recorded, for example, a startcall recording start recording plug-in is called in the onAnswer event of the call method.
The JavaScript code sample is as follows:
Call(“tel:+8659522943005”,{
timeout:60,
callerID:tel:+8659522943006,
onAnswer:function(event){
startCallRecording(URI);
}
});
stopCallRecording();
as another example, call recording logic processing based on Transfer plug-ins. In one embodiment, parameters or events in the Transfer plug-in that affect the recording function. Wherein, answerOnMedia is a parameter for playback after transparent transmission (indicating whether a calling user plays a specific playback file or directly transmits a real abnormal playback of a called user under the condition that a called call fails), true indicates playback after transparent transmission, and false does not transmit, and default is false. onConnect performs this event when the invite call from the Transfer plug receives a 200OK, indicating that the called party has answered the call. This parameter conflicts with answeron media and is higher priority than answeron media. When using the onConnect event, whatever value answerOnMedia is set to, it is forced to false at execution time, i.e., playback after no passthrough. The playvalue sets parameters for playing a specified playback file for a calling party or a called party before call recording.
In one embodiment, when the playback parameter after transmission through is set to true, the call recording records the playback and call sounds simultaneously. The start recording startCall recording plug-in is called before the transfer, which has answerOnMedia ═ true in the transfer method, and no OnConnect event.
The JavaScript code sample is as follows:
startCallRecording(URI);
transfer(“tel:+8659522943005”,{
answerOnMedia:true,
timeout:60,
callerID:”tel:+8659522943006”,
playvalue:"http://110.84.128.69:8080/voxfile/chn/1/esayCallHold.mp3"
});
stopCallRecording();
in another embodiment, when the playback parameter after transmission through is set to false, only the specific call sound is recorded in the call recording. The start recording startCallRecording plug-in is used in transfer's Onconnect event.
The examples of the javaScript code are as follows:
transfer(“tel:+8659522943005”,{
answerOnMedia:true,
timeout:60,
callerID:”tel:+8659522943006”,
playvalue:"http://110.84.128.69:8080/voxfile/chn/1/esayCallHold.mp3",
onConnect:function(event){
startCallRecording(URI);
}
});
stopCallRecording();
in another embodiment, when the playback parameter after transparent transmission is set to be false, the playback file of the calling user is set with the play value in the Transfer plug-in the recording, and only the playback file and the call sound played by the play value are recorded in the call recording. The start recording startCall recording plug-in is called before transfer, and answerOnMedia is false, and a play value parameter is used to set a play file storage path for the calling user to play the recording prompt, for example, save in http://110.84.128.69:8080/voxfile/chn/1/esayCallHold. mp 3.
The examples of the javaScript code are as follows:
startCallRecording(URI);
transfer(“tel:+8659522943005”,{
answerOnMedia:false,
timeout:60,
callerID:”tel:+8659522943006”,
playvalue:"http://110.84.128.69:8080/voxfile/chn/1/esayCallHold.mp3",
});
stopCallRecording();
in step 220, the recording management platform further performs interfacing encapsulation on the recording service logic of different application scenarios based on the atomic capabilities, parameters such as the overlay service number, the service triggering mechanism, and the real-time dynamic interaction mechanism with the client industry application platform. For example, on the basis of these atomic capabilities, the recording management platform superimposes parameters such as a service number, a service trigger mechanism, a playback mechanism, a real-time dynamic interaction mechanism with a client industry application platform, a recording file storage format, and the like, and further performs interface packaging on the recording service logic.
In step 230, the client calls the standard interface encapsulated by the recording management platform through the industry application platform according to the industry recording requirement, and sets the standard interface parameters so as to customize the recording service logic. The standard interface parameters include, for example, a recording number, a recording timing, a format for storing a recording file, a recording mode, a recording file storage mode, a recording file transmission encryption mode, whether the standard interface parameters interact with an industrial client platform before recording, whether the standard interface parameters are played for a calling number or a called number before recording, and upload a specified playback file, a path for transmitting the recording file, whether the standard interface parameters are played or played after transparent transmission is performed for a calling user before communication, and the like.
Wherein, the recording time comprises the default recording of the call or the temporary recording in the call process; the storage format of the sound recording file comprises an MP3 format, a WAV format and the like; the recording mode comprises bidirectional recording or unidirectional recording and the like; the recording file storage mode comprises the storage of one file or the storage of a calling file and a called file which are two independent files, and the like; whether the interaction with the industry client platform before recording comprises non-interaction and default recording, or interactive confirmation is needed and then whether recording, playback, call continuation and the like are judged.
In step 240, the recording management platform stores the standard interface parameters and the corresponding recording service logic, and issues the recording number service data sent by the service activation system to the recording trigger unit. When a customer applies for opening a number recording service, after an operation business opening system accepts the service, recording number service data such as the service number and the like are sent to a recording management platform through a designated interface, and the recording management platform combines a number-bearing network to send the recording number service data to a recording triggering unit.
In step 250, the recording trigger unit configures the service trigger data. The recording trigger unit configures service trigger data by combining the recording type of the client.
In step 260, the recording trigger unit receives the call request and determines whether the number in the call request activates the recording service. For example, when receiving a call request, the IMS or the soft switch bearing the number first interacts with a user data storage module of the IMS or the soft switch to query that a calling number or a called number in the call request is to accept and open a recording service.
In step 270, if the recording service is activated, the recording triggering unit interactively triggers the recording service logic with the recording service platform based on the SIP (Session Initiation Protocol). Because of the popular SIP protocol, the voice recording service platform is newly established by adopting a superposable module.
In step 280, the recording service platform sends the call request to the recording management platform. For example, after receiving the call request, the recording service platform first obtains information of the calling number and the called number in the call request, and interacts with the recording management platform.
In step 290, the recording management platform performs a secondary authentication on the call request. For example, whether the recording service is activated by the calling number and the called number or not is judged, and whether the recording management platform stores corresponding standard interface parameters and recording service logic or not is judged.
In step 2100, if the recording service is activated, the recording service platform sends the recording service logic identifier customized by the customer and the corresponding standard interface parameter to the recording service platform.
In step 2110, the recording service platform uses the standard interface parameter as the input number of the recording logic identifier, and judges whether to interact with the industry application platform before recording according to the standard interface parameter.
In step 2120, if necessary, the recording service platform pushes the call request to the industry application platform through the recording management platform, so that the industry application platform can remind the client whether to record. For example, when the recording service platform triggers the recording service logic, the recording service platform needs to push the incoming call information to an industry application platform through the recording management platform according to an interaction path for realizing setting; after receiving the push of the call, the industry application platform can perform corresponding WEB page screen popup processing on the system for the user to remind the user whether to record the call or not, whether to play the sound for the calling party or not and the like.
In step 2130, the industry application platform responds to the recording command input by the client, and the recording command is responded to the recording service platform through the recording management platform. For example, the recording instruction is responded to the recording service platform through the recording management platform in a standard interface mode, and the recording service platform performs subsequent processing of service logic according to different response messages.
In step 2140, the recording service platform forwards the call to the recording trigger unit, so that the recording trigger unit routes the call to the called side.
In step 2150, the recording service platform performs recording service logic processing on the call.
In step 2160, the recording service platform stores the recording file after the call is recorded to the storage location of the industry application platform according to the standard interface parameters.
After the call is finished, the recording service platform generates a recording file, call record information and a call ticket in a specified format according to the recording service logic of the service user and the standard interface parameter setting requirements, and pushes the recording file, the call record information and the call ticket to a storage path of an industry application platform in real time according to a specified transmission mode through the recording management platform. After receiving the recording file, the call record information and the call ticket, the designated path in the industry application platform of the client integrates the recording file, the call record information and the call ticket with the related data progress of the third-party industry application platform and presents the recording file, the call record information and the call ticket on a webpage.
In the embodiment, under the condition that a user does not perceive and does not change the existing number, the recording architecture is modularly designed based on the SIP protocol, the calling function and the recording function of the recording service platform are abstracted in an API mode, and flexible customization of the recording service logic is realized under the coordination of network elements such as an industry application platform, an operator number carrying network and the like. Different industry clients can combine different requirements, flexibly customize personalized recording service logic through an interface calling mode, and simultaneously, the clients can flexibly determine whether the call is recorded or not, whether the call is played for a called number or not and the like at different stages of ringing or phone answering and the like. After the call is finished, the recording file and the call record corresponding to the call can be automatically pushed to the client application platform in an encrypted mode according to the preset recording, and the client can integrate the related recording file, the call record and the like on the own application platform.
In the embodiment, the recording management module is tightly combined with an industry application platform of a client, the industry application platform can be flexibly and conveniently integrated with a recording service logic processing process, flexible customization of recording service logic is realized under the conditions that a user does not sense, does not change numbers, does not change dialing habits and does not need to build a recording platform, dynamic interaction with the client application platform can be realized at a recording preparation stage, during recording and at different time after recording, and the requirement of the client in the Internet and industry can be met more closely.
Fig. 3 is a schematic flow chart of a general programmable recording control implementation method according to still another embodiment of the disclosure. The recording triggering process is described in detail in this embodiment by taking a recording triggering process in which a fixed-line user terminal hanging down from the IMS dials a mobile phone as an example.
In step 310, the user accepts the application to activate the recording function of the related fixed phone number through the service activation system. And after the service opening system accepts the service, issuing an opening instruction or a closing instruction to the recording management platform. The fixed phone users hanging down from the fixed phone user bearing network can be connected with the recording service platform to realize the recording function; for the fixed telephone user carrying network which is not butted, the standard interface can be adopted to intercommunicate with the recording service platform to realize the recording function for hanging the fixed telephone, therefore, the user group capable of realizing recording is larger in the scheme.
In step 320, after receiving the instruction, the recording management platform opens or closes the recording service according to a conventional fixed phone user service opening mode.
In step 330, after the recording number service data is opened, the industry application platform calls the interface encapsulated by the recording management platform, and sets the recording service customized content of the specific fixed phone number. For example, whether the calling number or the called number is authenticated before recording, whether the calling number or the called number is played before recording and a specific playback file is uploaded, a format and an encryption mode for storing the recording file, whether the fixed telephone number for recording is set to be transmitted and then played, a logical ID of a used recording service, whether the recording process interacts information and an interaction path with an industry client application platform, a path for pushing the recording file and the like.
In one embodiment, functions of call recording, call playback and the like of different scenes are abstracted into atomic capabilities by the recording service platform, the recording management platform performs interface packaging on recording service logics of different application scenes based on the atomic capabilities, and the recording service platform can write different recording service logics based on the interfaces and in combination with recording requirements of different industries.
For example, two voice plugins, namely Call (originating Call) plugin and Transfer (Call forwarding), a startCallRecording start recording plugin and a stopCallRecording end recording plugin, are abstracted in an API manner, parameters such as answerOnMedia and playvalue are mainly abstracted in the API, the answerOnMedia is a parameter for playback after transparent transmission or not, and the playvalue is a parameter for setting a specified playback file to be played to a calling party or a called party before Call recording.
In one embodiment, the call and recording functions in the recording logic implementation are abstracted into a standard interface in an API mode, and the encapsulation mode of the interface adopts a universal HTTPS mode. Some parameters in the interface package include: the ACTION is the opening or canceling of the recording, the ACTION is 1 to open the recording service, and the ACTION is 2 to cancel the recording service; RECORD is a recording type, 1 is a calling RECORD and a called RECORD, 2 is a calling RECORD and 3 is a called RECORD; TransUrl is a path for pushing the set recording file; the file format is a recording file storage format, 1 is an MP3 format, and the others are wav formats; the PlayFile is a playback file set for the calling party or the called party before recording; if the recording management platform interacts with the industry application platform to authenticate the calling number when CallerNbrAuth is recording, 1 is authentication needed, and the others are not needed; CallerNbrAuthUrl is a path for interaction with a customer industry application platform during calling number authentication; when CalledBruath is recording, whether a recording management platform interacts with an industry application platform to authenticate a called number or not is judged, 1, authentication is needed, and the others are not needed; CalledBrAuthUrl is a path for interacting with a customer industry application platform when the called number is authenticated, and the like.
In step 340, the recording management platform receives the customized content of the client and stores the customized content of the recording service corresponding to the client. For example, the recording service logic ID of the client, and the corresponding series of recording interaction parameters are stored.
In step 350, the recording management platform combines with the number-bearing network to send the service opening data of the recording number to the soft switch or the IMS.
In step 360, the service triggering data is configured by the soft switch or the IMS in combination with the recording type of the client. The soft switch or IMS uses the recording service platform as the foot color of the application server to carry out intercommunication by the standard SIP protocol.
At step 370, the fixed-line subscriber initiates a call through IMS.
In step 380, the IMS determines that the user has subscribed to the recording service according to the Initial Filter Criterion (IFC) rule of the recording service subscribed to by the user, and determines that the called number is a non-specified special service number and needs to trigger recording of the call, and routes the call to the recording service platform.
In one embodiment, for a fixed-line user loaded through the IMS, the recording triggering mode is to trigger the subscription recording IFC through the subscription calling and called services, and to implement the triggering of recording through the interworking between a CSCF (Call Session Control Function) submodule of the IMS and a recording service platform. The IMS is required to be configured with a calling IFC template and a called IFC template triggered by recording, and the CSCF submodule is required to take a recording service platform AS the role of an AS (application server) to carry out intercommunication and butt joint by adopting an international standard ISC interface. For a fixed telephone user loaded through a soft switch, an SHLR (Smart HLR) mode + a mode of setting a plurality of access codes for preventing repeated triggering is needed.
In step 390, the recording service platform receives the call sent by IMS, and pushes the call information to the recording management platform according to the predefined interface format, and the recording management platform performs secondary authentication. For example, whether the corresponding number authorizes recording, recording of a calling recording process or a called process, a bound recording service logic, whether to interactively participate in processing of the service logic with a customer industry application platform, and the like are judged.
In step 3100, the recording management platform returns the corresponding recording service logical ID and the corresponding recording parameter to the recording service platform.
In step 3110, if the recording service platform determines that the call needs to interact with the industry application platform of the client before recording according to the recording service logic, the call information is pushed to the industry application platform of the client in real time. For example, the client side intervenes in some service judgments, such as whether the call is recorded or not, or whether the client can play a reminding sound, and the like, at this time, the recording service platform needs to push the call information to the industry application platform of the client in real time according to a predetermined interface.
In step 3120, after the industry application platform receives the push of the relevant information of the call, the industry application platform needs to perform incoming call popup or matching processing with the user number information in the database according to the number information, and then returns a response message to the recording service management platform according to the result of the judgment processing and the preset interface format. The related information of the call comprises a calling number, a called number, time and the like.
In step 3130, the recording management platform returns a response message to the recording service platform according to the recording processing requirement of the call returned by the industry application platform and the recording management information preset by the user on the recording management platform in a specified format. Then the information returned by the recording service platform and the recording management platform triggers the recording service logic bound by the user, and confirms whether the number needs to be recorded at present, whether the number needs to interact with the industry application platform of the client before recording, the format of the generated recording file, the calling and the called of the recording file are separated separately, and the like.
In step 3140, the recording service platform processes the call and returns the call to the IMS, carrying information such as the related call ID of the preamble signaling flow.
In step 3150, the IMS performs call connection processing according to the IFC trigger rule and the conventional call flow without recording.
In step 3160, the IMS sends the call to the relevant call transit network element.
In step 3170, the bearer network element initiates a call to the called user.
In step 3180, after the called user answers the call, the recording service platform records the call according to the recording service logic.
In step 3190, after the call is finished, the recording service platform generates a recording file with a specified format according to the service logic and pushes the recording file to the recording management platform for encryption management.
In step 3200, the recording management platform returns the encrypted recording file and the encrypted call record information to the client's industry application platform in an encrypted manner or via a dedicated channel according to information such as a directory for storing the recording file preset by the industry application platform.
In step 3210, the industry application platform performs matching processing after receiving the information, manages the workflow and business of the client, displays the workflow and business on the platform, and assists the client in prompting efficiency.
In the embodiment, the calling and recording functions in the recording logic implementation are abstracted in an API mode, and the recording service platform combines the recording requirements of different industry applications, programs and combines the APIs, and interacts with the service management platform in different service logic ID forms. The recording management platform further encapsulates the recording service into a product interface by different interface names through standard interface forms according to the recording logics provided by different recording logics ID, so that an industry application platform calls the standard interfaces to flexibly customize different recording service logics before the recording service is opened.
Fig. 4 is a schematic structural diagram of an embodiment of a universal programmable recording control implementation apparatus according to the present disclosure. The device comprises a recording trigger unit 410, a recording service platform 420 and a recording management platform 430.
The recording trigger unit 410 is configured to interact with the recording service platform 420 after receiving the call request in order to trigger the recording service logic. The recording trigger unit comprises recording trigger and soft switch or IMS for bearing fixed telephone users. The recording trigger means that the fixed-line user routes the voice call of the specified fixed number under the specified scene to the recording service platform in the above architecture to realize the recording function through a specific mode on the soft switch or the IMS carried by the fixed-line user.
The recording service platform 420 is configured to send the call request to the recording management platform 430, and perform recording service logic processing on the call by using the standard interface parameter sent by the recording management platform 430 as the entry number of the recording logic identifier. Namely, the recording service platform 420 implements the functions of basic call processing and recording the call.
The recording management platform 430 is configured to send the customized recording service logic identifier and the corresponding standard interface parameters to the recording service platform 420 after authenticating the call request.
In the embodiment, through the information interaction of the recording trigger unit, the recording service platform and the recording management platform, the flexible customization of the recording service logic is realized without changing the dialing habit of a user, changing numbers and establishing the recording platform at a client side.
In another embodiment of the present disclosure, the recording triggering unit 420 is further configured to determine whether the number in the call request activates the recording service after receiving the call request, and if the number in the call request activates the recording service, interact with the recording service platform 420 based on a standard SIP. If the recording triggering unit 410 is IMS, the interface between IMS and the recording service platform 420 is an ISC interface. The voice recording service platform 420 exists in the role of an application server of the IMS.
In one embodiment, the recording service platform 420 not only implements the functions of basic call processing and recording calls, but also innovatively interfaces and encapsulates the functions of call recording, call playback and the like in different scenes, and different recording service logics can be written based on the interfaces and the recording requirements of different industries. For example, the sound recording business logic is abstracted as an atomic capability in an API manner.
In one embodiment, the recording service platform 420 is further configured to determine whether to interact with the industry application platform before recording according to the standard interface parameters, and if so, push the call request to the industry application platform through the recording management platform 430 so that the industry application platform reminds the client whether to record; wherein, the industry application platform responds to the recording command input by the client, and the recording command is responded to the recording service platform 420 through the recording management platform 430.
In another embodiment, the recording service platform 420 is further configured to store the recording file after recording the call according to the standard interface parameters to a storage location of the industry application platform.
In one embodiment, the recording service logic process includes multiple aspects, for example, for a call sent from the soft switch/IMS, obtaining the number information of a calling party and a called party in the call, interacting with the recording management platform 430 to determine whether the specified number information is an authorized recording number, a calling recording flow or a called recording flow, a bundled recording logic ID, whether to play before recording, a voice file name played, a format for storing the recording, separation of the recording file from the calling party and the called party, and the like. Then, the calling and recording scripts corresponding to the recording logic ID are triggered according to the requirements of the recording management platform 430, the calling and called numbers can be simultaneously subjected to number conversion, access codes are added or deleted according to the specified requirements, and then the calling and called numbers and the soft switch/IMS are interacted to complete the subsequent calling processing. And then the service logic judges whether to record according to the call state of the called user returned by the soft switch/IMS, such as call failure, off-hook answering and the like. If the called user has off-hook answer, the logic needs to judge whether to play the appointed playback file for the calling user or the called user, for example, the voice prompt for starting recording can be played for the calling user; the voice reminding and the like of the recorded call can be played for the called party; the specific playback content is customized according to different industry clients, and different playback contents can be selected for the same industry client according to different user numbers. If not, the recording process is directly carried out. And during recording, the service logic needs to judge the user side hang-up information from the soft switch/IMS, once the user hangs up, a recording file with a specified format is generated according to the information returned by the recording management platform in advance, and the recording file is pushed to the recording management platform in real time and is subjected to subsequent interactive processing by the recording management platform. If the recording service logic processing process is abnormal or the recording management platform is abnormal, the recording service platform needs to support and indicate the soft switch/IMS to carry out subsequent call processing, and the user does not sense the call processing.
The intercommunication between the recording service platform 420 and the recording management platform 430 is based on standard universal HTTP interface intercommunication, and mainly realizes the relevant information interaction of the recording management layer. Such as uploading a recording file, checking a recording number, specifying a recording logic ID, etc.
The recording management platform 430 performs series management on the recording of the client-related number in the designated industry, including opening and closing of the recording of the designated number, production, storage, pushing, downloading and the like of recording files with different formats, interaction with the client industry application platform before recording, interaction on the recording processing of the call, and the like. The recording management platform 430 mainly has three functions: opening a recording service in a certain industry and setting a recording rule; the recording process respectively interacts with a recording service platform and a client industry application platform to realize the processing of recording authentication and participating in the recording service logic, and the processing of call recording, recording file pushing and the like after the recording is finished; and (4) packaging an interaction interface with an industry application platform.
In one embodiment, the recording management platform 430 is further configured to combine and package different atomic capabilities into a standard interface, and provide the standard interface to the client through the industry application platform, so that the client calls the standard interface packaged by the recording management platform 430 through the industry application platform according to the industry recording requirement, and sets the standard interface parameters to customize the recording service logic; and is configured to store the standard interface parameter and the corresponding recording service logic, and issue the recording number service data sent by the service activation system to the recording trigger unit 420, so that the recording trigger unit 420 configures the service trigger data.
In one embodiment, the recording management platform 430 is configured to determine whether the recording service is enabled for the number in the call request, and whether the recording management platform stores corresponding standard interface parameters and recording service logic.
In one embodiment, the recording management platform 430 is further configured to determine whether the recording number is opened after receiving the request for calling the standard interface by the industry application platform, determine whether the standard interface called by the industry application platform exists if the recording number is opened, and store the standard interface parameter set by the client and the corresponding recording service logic if the standard interface called by the industry application platform exists.
In the above embodiments, by introducing the functions and interactions of the recording trigger unit, the recording service platform and the recording management platform, different industry clients can flexibly customize personalized recording service logic by an interface calling mode according to different requirements, and at the same time, the clients can flexibly determine whether the call is recorded or not, whether the call is played to a called number or not, and the like, at different stages of ringing or phone answering and the like. After the call is finished, the recording file and the call record corresponding to the call can be automatically pushed to the client application platform in an encrypted mode according to the preset recording, and the client can integrate the related recording file, the call record and the like on the own application platform. The method realizes the imperceptible recording of the appointed call on the premise of not changing the existing number used by the user and the dialing habit of the user. The customer can utilize the information of obtaining the recording file, the call record and the like to realize the post-event tracing/auditing of complaints, the service quality improvement, the call behavior statistics, the accurate marketing of big data and the like.
Fig. 5 is a schematic structural diagram of another embodiment of the universal programmable recording control implementation apparatus of the present disclosure. The apparatus includes a memory 510 and a processor 520. Wherein: the memory 510 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory 510 is used to store instructions in the embodiments corresponding to fig. 1-3. Processor 520 is coupled to memory 510 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 520 is configured to execute instructions stored in memory.
In one embodiment, as also shown in FIG. 6, the apparatus 600 includes a memory 610 and a processor 620. Processor 620 is coupled to memory 610 through a BUS 630. The apparatus 600 may also be coupled to an external storage device 650 via a storage interface 640 for external data retrieval, and may also be coupled to a network or another computer system (not shown) via a network interface 660, which will not be described in detail herein.
Fig. 7 is a schematic structural diagram of an embodiment of a universal programmable recording control implementation system according to the present disclosure. The system comprises a fixed telephone user terminal 710, the general programmable recording control implementation device and an industry application platform 750, wherein the device comprises a recording trigger unit 720, a recording service platform 730 and a recording management platform 740, and the recording trigger unit is, for example, a soft switch or an IMS.
The fixed-line user terminal 710 is a fixed-line user terminal with a recording requirement. The soft switch or the IMS720 realizes the recording triggering and the bearing of the fixed phone user, the IMS can also forward the call to a call forwarding network element, and the call forwarding network element forwards the call to a mobile phone/other fixed phone users and the like; the recording service platform 730 realizes recording service logic; the recording management platform 740 realizes the recording series management function, comprises a specified number recording switch, and processes of generating, storing, pushing, downloading and the like of recording files with different formats, and carries out interactive processing with an industry application platform before recording; the industry application platform 750 implements a final recording application.
For clarity of describing the system of the present disclosure, as shown in fig. 8, the recording service platform 730 abstractly packages the recording service logic into atomic capabilities 1-N in an API manner, and the recording management platform 740 packages the recording service logic into a plurality of recording service logic interfaces 1-M by combining the atomic capabilities. Each client can call different interfaces through the industry application platform 750 according to different industry recording requirements, set corresponding interface parameters and customize personalized recording business logic. The recording service platform 730 takes the recording logic corresponding to the personalized recording service content as the entry parameter, and continues the subsequent calling and recording processes. The recording service platform 730 triggers the recording service logic corresponding to the user during the call, generates a file corresponding to the call according to personalized customization, and the recording management platform 740 stores the file corresponding to the pass to the storage location of the application platform of the industry designated by the client.
In one embodiment, a customer accepts a request to open a recording service for a specified number. And calling different recording service logic standardized interfaces provided by the recording management platform by the client, setting corresponding interface parameters, and customizing the personalized recording service logic. And the recording management platform stores and maps the information such as the recording service logic, the number and the like customized by the customer. The recording management platform respectively issues the recording service logic ID and the recording service trigger data customized by the customer to the recording service platform and the soft switch or the IMS bearing the recording number, and the corresponding IMS or the soft switch completes data configuration. The IMS or the soft switch uses the recording service platform as the role of an application server to carry out intercommunication by a standard SIP protocol.
When the recording service number receives and transmits a call, the IMS or the soft switch triggers the recording service according to the service trigger data signed by the user. And after receiving the recording trigger call request, the recording service platform interacts with the recording management platform, authenticates the recording number, acquires the recording logic ID customized by the user, selectively interacts with the industry application platform according to the customization requirement of the recording logic, and continues the execution of the subsequent call and recording process. When the called user is off-hook, the recording service platform selectively plays specific prompt tone and recording treatment for the calling or called according to the recording service logic signed by the user, and generates and encrypts a recording file with a specified format after the call is finished. And the information of the recording file, the call record and the like of the call of the recording management platform is pushed to an industry application platform catalog preset by a client, the application platform is put in storage and sorted and then presented to the client, and the client can perform related data analysis and processing according to the information.
The recording framework is modularly designed, the recording function is abstracted by API, the flexible customization of the recording service logic is realized by combining the recording requirements of different industries, the number and the use habit of a user do not need to be changed, and the recording is realized under the condition of no perception. The customer industry application platform may autonomously participate in the processing of the recording service at designated call occasions.
The operator can realize the provision of the recording function of the national provinces numbers based on the disclosure, including the provision of the recording function of fixed phone users, 2G mobile phone users and VOLTE mobile phone users. The method can realize the non-perception recording without changing the number and the dialing habit of the user. In addition, the method is suitable for wider customers, such as the non-perception recording of the fixed telephone numbers and the mobile phone numbers of customer service seats, customer managers and sales personnel in service industries of banks, insurance, public security and the like, and has strong reproducibility and popularization. Moreover, by using the method and the system, the call content client can perform inquiry, tracking, monitoring, storage, analysis and the like based on the own industry application platform after the call content client is in fact, the complaint problem of the service industry can be effectively solved, the service level is improved, the service quality is improved, the employee behavior is standardized, the traffic is controlled, and a data basis is provided for future service development.
In another embodiment, a computer-readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the corresponding embodiment of fig. 1-3. As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, apparatus, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Thus far, the present disclosure has been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims (19)

1. A general programmable recording control implementation method comprises the following steps:
the recording service platform abstracts the recording service logic into atomic capability in an API mode;
the recording management platform combines and encapsulates different atomic capabilities into a standard interface, and the standard interface is provided for a client through an industry application platform, so that the client can call the standard interface encapsulated by the recording management platform through the industry application platform according to industry recording requirements, and set standard interface parameters so as to customize a recording service logic;
the recording management platform stores standard interface parameters and corresponding recording service logics, and issues recording number service data sent by the service activation system to the recording trigger unit so that the recording trigger unit configures the service trigger data;
the recording triggering unit receives the call request and then interacts with the recording service platform so as to trigger the recording service logic;
the recording service platform sends the call request to a recording management platform so that the recording management platform can send a recording service logic identifier customized by a customer and a corresponding standard interface parameter to the recording service platform after authenticating the call request;
the recording service platform takes the standard interface parameter as the input number of the recording logic identifier and transfers the call to the recording trigger unit so that the recording trigger unit routes the call to the called side;
and the recording service platform performs recording service logic processing on the call.
2. The universal programmable recording control implementation method of claim 1,
the recording triggering unit judges whether the number in the call request opens the recording service after receiving the call request, and if the number in the call request opens the recording service, the recording triggering unit interacts with the recording service platform based on a standard Session Initiation Protocol (SIP).
3. The method for implementing universal programmable recording control according to claim 1, wherein the step of forwarding the call to the recording trigger unit by the recording service platform further comprises:
the recording service platform judges whether to interact with an industry application platform before recording according to the standard interface parameters, and if so, the recording service platform pushes a call request to the industry application platform through the recording management platform so that the industry application platform can remind a client of whether to record or not;
and the industry application platform responds to a recording instruction input by a client, and responds the recording instruction to the recording service platform through the recording management platform.
4. The method of claim 1, wherein the authenticating the call request by the recording management platform comprises:
and the recording management platform judges whether the number in the call request opens a recording service or not, and whether the recording management platform stores corresponding standard interface parameters and a recording service logic or not.
5. The universal programmable recording control implementation method of claim 1, further comprising:
and after receiving the standard interface calling request of the industry application platform, the recording management platform judges whether a recording number is opened, if so, judges whether a standard interface called by the industry application platform exists, and if so, stores standard interface parameters set by the client and corresponding recording service logic.
6. The method for implementing universal programmable sound recording control according to any one of claims 1-5, further comprising:
and the recording service platform stores the recording file after the call is recorded to the storage position of the industry application platform according to the standard interface parameters.
7. The programmable sound recording control implementation method of a general type according to any one of claims 1 to 5,
the recording trigger unit includes at least one of an IP multimedia subsystem and a soft switch.
8. The universal programmable recording control implementation method of claim 7,
the interface between the recording service platform and the IP multimedia subsystem is an ISC interface for the IP multimedia subsystem safety control.
9. A general programmable recording control realizing device comprises:
the recording service platform is configured to abstract the recording service logic into atomic capability in an API mode;
the recording management platform is configured to combine and package different atomic capabilities into a standard interface, and the standard interface is provided for a client through an industry application platform, so that the client can call the standard interface packaged by the recording management platform through the industry application platform according to industry recording requirements, and standard interface parameters are set so as to customize a recording service logic; the recording system is configured to store standard interface parameters and corresponding recording service logics, and send recording number service data sent by the service activation system to the recording trigger unit, so that the recording trigger unit configures the service trigger data;
the recording triggering unit is configured to interact with the recording service platform after receiving the call request so as to trigger the recording service logic;
the recording service platform is also configured to send the call request to a recording management platform, and take the standard interface parameter sent by the recording management platform as the input number of the recording logic identifier to perform recording service logic processing on the call;
and the recording management platform is also configured to send the recording service logic identifier customized by the customer and the corresponding standard interface parameter to the recording service platform after authenticating the call request.
10. The programmable sound recording control implementation apparatus of a generic type as recited in claim 9,
the recording triggering unit is also configured to judge whether a recording service is opened by the number in the call request after the call request is received, and if the recording service is opened, the recording triggering unit interacts with the recording service platform based on a standard Session Initiation Protocol (SIP).
11. The programmable sound recording control implementation apparatus of a generic type as recited in claim 9,
the recording service platform is also configured to judge whether to interact with an industry application platform before recording according to the standard interface parameters, and if so, a call request is pushed to the industry application platform through the recording management platform so that the industry application platform can remind a client of recording; and the industry application platform responds to a recording instruction input by a client, and responds the recording instruction to the recording service platform through the recording management platform.
12. The programmable sound recording control implementation apparatus of a generic type as recited in claim 9,
and the recording management platform is configured to judge whether a recording service is opened by the number in the call request, and whether a corresponding standard interface parameter and a recording service logic are stored in the recording management platform.
13. The programmable sound recording control implementation apparatus of a generic type as recited in claim 9,
the recording management platform is further configured to judge whether a recording number is opened after receiving the industry application platform calling standard interface request, judge whether a standard interface called by the industry application platform exists if the recording number is opened, and store standard interface parameters set by the client and corresponding recording service logic if the recording number exists.
14. The programmable sound recording control implementation apparatus of a general type as claimed in any one of claims 9-13,
and the recording service platform is also configured to store the recording file subjected to recording processing on the call to a storage position of an industry application platform according to the standard interface parameters.
15. The programmable sound recording control implementation apparatus of a general type as claimed in any one of claims 9-13,
the recording trigger unit includes at least one of an IP multimedia subsystem and a soft switch.
16. The programmable sound recording control implementation of claim 15, wherein,
the interface between the recording service platform and the IP multimedia subsystem is an ISC interface for the IP multimedia subsystem safety control.
17. A general programmable recording control realizing device comprises:
a memory; and
a processor coupled to the memory, the processor configured to perform the general purpose programmable sound recording control implementation of any of claims 1-8 based on instructions stored in the memory.
18. A general programmable recording control implementation system comprises:
a fixed-line user terminal;
an industry application platform; and
a programmable sound recording control implementation apparatus of the generic type as claimed in any one of claims 9-17.
19. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the general programmable recording control implementation method of any one of claims 1 to 8.
CN201811540940.4A 2018-12-17 2018-12-17 Universal programmable recording control implementation method, device and system Active CN111327750B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811540940.4A CN111327750B (en) 2018-12-17 2018-12-17 Universal programmable recording control implementation method, device and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811540940.4A CN111327750B (en) 2018-12-17 2018-12-17 Universal programmable recording control implementation method, device and system

Publications (2)

Publication Number Publication Date
CN111327750A CN111327750A (en) 2020-06-23
CN111327750B true CN111327750B (en) 2021-06-25

Family

ID=71170644

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811540940.4A Active CN111327750B (en) 2018-12-17 2018-12-17 Universal programmable recording control implementation method, device and system

Country Status (1)

Country Link
CN (1) CN111327750B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005534A (en) * 2006-01-18 2007-07-25 西安大唐电信有限公司 Method for realizing telephone recording function of telephone terminal
CN108243285A (en) * 2016-12-23 2018-07-03 中国电信股份有限公司 call recording method and system
CN108282444A (en) * 2017-01-06 2018-07-13 中国电信股份有限公司 Call recording method and device
CN108881180A (en) * 2018-05-30 2018-11-23 中国联合网络通信集团有限公司 The way of recording and recording system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9049311B2 (en) * 2012-08-17 2015-06-02 Michael Yuzefovich Automated voice call transcription and data record integration

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005534A (en) * 2006-01-18 2007-07-25 西安大唐电信有限公司 Method for realizing telephone recording function of telephone terminal
CN108243285A (en) * 2016-12-23 2018-07-03 中国电信股份有限公司 call recording method and system
CN108282444A (en) * 2017-01-06 2018-07-13 中国电信股份有限公司 Call recording method and device
CN108881180A (en) * 2018-05-30 2018-11-23 中国联合网络通信集团有限公司 The way of recording and recording system

Also Published As

Publication number Publication date
CN111327750A (en) 2020-06-23

Similar Documents

Publication Publication Date Title
US11706349B2 (en) System and method for processing telephony sessions
US11444985B2 (en) System and method for processing telephony sessions
EP4262320A1 (en) Call processing system and call processing method
WO2022147696A1 (en) Call processing method, call processing apparatus and related device
CN105100523B (en) Voice channel method for building up, apparatus and system
CN111327750B (en) Universal programmable recording control implementation method, device and system
US20130229949A1 (en) Processing Requests

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