CN103475640A - Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing - Google Patents

Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing Download PDF

Info

Publication number
CN103475640A
CN103475640A CN2013103475900A CN201310347590A CN103475640A CN 103475640 A CN103475640 A CN 103475640A CN 2013103475900 A CN2013103475900 A CN 2013103475900A CN 201310347590 A CN201310347590 A CN 201310347590A CN 103475640 A CN103475640 A CN 103475640A
Authority
CN
China
Prior art keywords
message
negotiation
rtp
opposite end
srtp
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.)
Pending
Application number
CN2013103475900A
Other languages
Chinese (zh)
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.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies 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 Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to CN2013103475900A priority Critical patent/CN103475640A/en
Publication of CN103475640A publication Critical patent/CN103475640A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing. The method is applied to network equipment or a terminal. The method comprises: sending a capability detection message to an opposite terminal; determining an early-stage session negotiation capability jointly supported by a local terminal and the opposite terminal; sending an Invite message to the opposite terminal so as to request the negotiation of an SRTP (Security Real-time Transport Protocol) call; after receiving from the opposite terminal a temporary response message which is aimed at the Invite message and carries RTP correlation media information, determining that the negotiation of the SRTP call fails, using the early-stage session negotiation capability jointly supported by the local terminal and the opposite terminal to send to the opposite terminal an early-stage negotiation request message which carries the RTP correlation media information so as to request the negotiation of an RTP call; and confirming that the negotiation succeeds after receiving an early-stage negotiation response message, and sending to the opposite terminal a confirmation message so as to finish an RTP negotiation. Compared to the prior art, the method and apparatus for realizing RTP backspacing can successfully realize the RTP backtracking even if there are identification errors over the opposite terminal and have excellent compatibility.

Description

A kind of RTP backing method and device realized
Technical field
The present invention relates to the network multimedia communication field, relate in particular to a kind of RTP of realization backing method and corresponding device.
Background technology
Session Initiation Protocol is the control protocol of an application layer, it is widely used in the application scenarioss such as video monitoring and the networking telephone, highly developed today in the Internet, Session Initiation Protocol almost has directly with our everyone Working Life or indirectly contact, such as people are while using voip phone in company, calling procedure will relate to the mutual of various signalings in Session Initiation Protocol; Say for another example, when the point duty personnel dispatch the live video at each crossing in command centre, the same function bringing into play the business scheduling of Session Initiation Protocol.Function, Session Initiation Protocol can be used for setting up, revises and stop Multimedia session (or meeting).Typically, by sip message, can consult media information, such as the following safety call pattern of setting forth that is about to.
The full name of SRTP is Secure Real-time Transport Protocol, i.e. safe Real-time Transport Protocol.Real-time Transport Protocol is the important technology of transferring multimedia data stream, is current the most popular a kind of multimedia data stream encapsulation technology.The main target of SRTP agreement is that the data flow of RTP carrying is encrypted, authenticates and retransmit protection.Along with the extensive use of VoIP system, the user is more and more higher for the security requirement of voip network, and such as bank, government department etc., SRTP is born under such application demand.SRTP and RTP will coexist in long-time, and how handling various relevant issues in coexisting well is important technological problems that industry need to solve.
Summary of the invention
In view of this, the invention provides a kind of RTP of realization backspace mechanism, be applied on the network equipment or terminal, this device comprises ability probe unit, efficiency test unit, initial negotiation unit, handles unit and secondary negotiation element through consultation; Wherein:
The ability probe unit, for to opposite end transmitting capacity probe message;
The efficiency test unit, consult ability for determine the common early-session of supporting in local terminal and opposite end after receiving response detected message;
The initial negotiation unit for send Invite message to opposite end, and carries SRTP related media information and consults the SRTP calling with request in this message;
Handle unit through consultation, for from opposite end, receive for Invite message and carry the provisional response message of RTP related media information, determine SRTP call negotiation failure, notice secondary negotiation element is processed;
The secondary negotiation element, send early stage negotiation request message for using local terminal and the opposite end common early-session of the supporting ability of consulting, and carry RTP related media information and call out with request negotiation RTP in this message to opposite end; Wherein
The described unit of handling through consultation, be further used for after receiving early stage negotiation response message, confirming to consult successfully, sends acknowledge message to opposite end and consult to complete RTP.
The present invention also provides a kind of RTP of realization backing method, is applied on the network equipment or terminal, and wherein the method comprises the following steps:
Steps A, to opposite end transmitting capacity probe message;
The early-session of step B, the common support of definite local terminal and opposite end after receiving response detected message is consulted ability;
Step C, send Invite message to opposite end, and carry SRTP related media information and consult SRTP with request and call out in this message;
Step D, from opposite end, receive for Invite message and carry the provisional response message of RTP related media information, determine that the SRTP call negotiation unsuccessfully goes to step E and processes;
Step e, the early-session that uses local terminal and opposite end jointly the to support ability of consulting send early stage negotiation request message to opposite end, and carry RTP related media information and consult the RTP calling with request in this message;
Step F, confirm to consult successfully after receiving early stage negotiation response message, send acknowledge message to opposite end and consult to complete RTP.
Compared to existing technologies, when can there be identification error in the present invention in opposite end, still can successfully realize the RTP rollback, and because the present invention has used the means that realize of standard, so there is excellent compatibility.
The accompanying drawing explanation
Fig. 1 is a kind of typical negotiation SRTP calling procedure schematic diagram.
Fig. 2 is a kind of typical negotiation SRTP call failure but successfully return back to the schematic diagram that RTP calls out.
Fig. 3 is the schematic diagram of a kind of typical negotiation SRTP call failure and rollback RTP failure.
Fig. 4 is logical construction and the typical hardware environment schematic diagram of RTP rollback processing unit in one embodiment of the present invention.
Fig. 5 is the schematic diagram of RTP rollback processing procedure in one embodiment of the present invention.
Fig. 6 is the schematic diagram of RTP rollback processing procedure in another embodiment of the present invention.
Embodiment
From practical application, the participant's of call role fixes often, take VoIP as example, the promoter of business is called calling party (Caller), a called side is called called (Callee), and before end of conversation, such role can't change.But, from the interaction models of Session Initiation Protocol itself, both sides' role is again dynamic change.Session Initiation Protocol adopts C/S(Client/Server, client/server) model.Caller and Callee are called as UA(User Agent, user agent), Caller and Callee all can be used as Client, simultaneously also can be as Server.As a rule, a side who initiates the signaling request can be called as UAC(User Agent Client), and a side of response is called as (User Agent Server).These are explanation no longer in detail in subsequent descriptions, and those of ordinary skills can obtain more detailed understanding with reference to relevant RFC.
Please refer to Fig. 1, the basic negotiation flow process that adopts SRTP to be called out generally includes following steps:
Step 10, UAC sends INVITE to UAS, and at the SDP(Session Description Protocol) carry SRTP related media information in message body;
Step 11, UAS, after receiving INVITE, after consulting SRTP related media information, sends successful OK200 message, and carries in SDP message body and consult successful SRTP media information, thereby set up safe calling.
In actual application process, must not irrespective problem be, for legacy network devices existing in network (such as old money router) and terminal (such as IP phone), it may not support the SRTP media negotiation, now need to do compatible consideration, allow both sides to adopt non-security RTP to call out, this mechanism is usually also referred to as fallback mechanism.Please refer to Fig. 2, a typical RTP back off procedure comprises the following steps:
Step 20, UAC sends INVITE to UAS, and carries therein SRTP related media information;
Step 21, UAS finds self not support that SRTP consults after receiving INVITE, so reply 488 message informing UAC, self does not support the SRTP media;
Step 22, UAC resends INVITE and carries RTP related media information;
Step 23, UAS sends and consults successful OK200 message after receiving that INVITE is consulted RTP related media information, sets up non-security RTP and calls out, and realizes the rollback from SRTP to the RTP media.
Step 21 has been described a kind of more satisfactory rollback situation to step 23.But, in actual network application process, some more actual problems are appeared in one's mind out again.Because each manufacturer realizes that at concrete software/hardware larger difference is arranged, sometimes above-mentioned back off procedure there will be extremely.For instance, it is the SRTP media of self not supporting that the parts of traditional network equipment or IP phone can not well be identified what carry in SDP message body, it is Real-time Transport Protocol that many equipment or terminal can be missed the SRTP protocol identification, this will cause can not be according to the processing of holding consultation of above-mentioned flow process, cause the rollback failure, call exception is taken out stitches, and it is to listen and at once hear busy tone after user's ring off-hook that the user can directly perceive anomaly.The abnormal flow process of whole appearance can, with reference to figure 3, comprise the following steps specifically:
Step 30, UAC sends INVITE to UAS, and carries SRTP related media information in SDP message body;
Step 31, because UAS is Real-time Transport Protocol by the SRTP protocol identification mistakenly, it can't not support the SRTP media by 488 notice UAC according to Fig. 2 flow process, but reply mistakenly the OK200 that carries RTP related media information after user's off-hook, replys;
Step 32, can find to consult unsuccessfully after UAC receives at once, then sends BYE message.
The invention provides a kind of early-session that utilizes and realize that RTP rollback treatment mechanism solves above-mentioned abnormal problem.Be embodied as example with software, the invention provides a kind of RTP of realization backspace mechanism, it is applied on the network equipment or terminal.Please refer to Fig. 3, the basic hardware environment of this device operation comprises CPU, internal memory, nonvolatile memory and other various hardware.From logic level, this device comprises: consult initiate unit and handle unit through consultation.Please refer to Fig. 4, in running, this device is carried out following handling process.
Step 41, the ability probe unit is to opposite end transmitting capacity probe message;
Step 42, the common early-session negotiation ability of supporting of local terminal and opposite end is determined in the efficiency test unit after receiving probe response message;
Step 43, the initial negotiation unit sends Invite message to opposite end, and carries SRTP related media information and consult the SRTP calling with request in this message;
Step 44, when receiving the response message of carrying SRTP related media information from opposite end, handle unit through consultation and send acknowledge message to opposite end to complete the SRTP negotiation;
Step 45, from opposite end receive for the Invite request message and carry the provisional response message of RTP related media information, handle unit through consultation and determine SRTP call negotiation failure, notice secondary negotiation element is processed, and goes to step 46;
Step 46, the secondary negotiation element is used the common early-session of supporting of local terminal and the opposite end ability of consulting to send early stage negotiation request message to opposite end, and carries RTP related media information and call out to ask consulting RTP in this message;
Step 47, handle unit through consultation and confirm to consult successfully after receiving early stage negotiation response message, sends acknowledge message to opposite end and consult to complete RTP.
So-called SRTP or RTP related media information can comprise usually: port numbers, address, audio frequency and video encoding and decoding standard (as the G.7 encoding and decoding of series) etc., transmission and the negotiations process of these parameters belong to prior art, and the present invention does not further expand introduction.Under normal circumstances, if SRTP is all supported in local terminal and opposite end, the negotiations process meeting successfully enters step 44 and completes the SRTP negotiation so.If it is the new equipment of supporting SRTP and RTP that certain local terminal and opposite end only have an end, the other end is the old equipment of only supporting RTP, and so whole negotiations process has two kinds of possibilities, and a kind of is that old equipment is initiated, and another kind is that new equipment is initiated.
In actual applications, if one is not supported the equipment of SRTP agreement to make a call, it can send Invite message to opposite end (namely UAS) as UAC, and what now in Invite message, carry will be RTP related media information, not have the problem of rollback.A kind of front roll-type design is arranged certainly at present, namely UAC carries RTP related media information in Invite message, but carry the SRTP mark simultaneously in this message, be used for showing self supporting SRTP, if SRTP is also supported in opposite end, and also can identify this SRTP mark, opposite end can send Invite message to consult the SRTP calling to local terminal (being now UAS) using self as UAC, because both sides support SRTP, if other consultation parameters are no problem, consulting so just can be successful.But there is obvious defect in this mode, at first this requires opposite end can identify this SRTP mark, and this mark may be privately owned definition, therefore compatible poor, is not easy extensive use.Secondly, such handling process lacks reasonability, if in negotiations process conditions permit, should preferentially consult the higher SRTP of fail safe and call out.Suppose that opposite equip. is that other manufacturers manufacture, this equipment is supported SRTP, but can not identify the SRTP mark, and the result that now both sides consult remains RTP.That is to say that this scheme can exist obviously can negotiate safer SRTP and call out, but result is consulted the lower RTP of fail safe and called out; Such result is obviously that the user is difficult to accept.
In the present invention, at first do not need to introduce the so privately owned definition of any SRTP mark, the improvement of whole software only gets final product in the new equipment/terminal as UAC at first made a call, for the legacy equipment/terminal as UAS, in back off procedure, it also can't perceive the problem of self makeing mistakes.UAC sends and carries the INVITE of SRTP related media information to UAS.Suppose that UAS is identified as RTP mistakenly by SRTP, the direct reply of its meeting is not with 180 message or 183 message of SDP, and the difference of 180 and 183 message is that ring is local produce or the far-end generation of UAC on earth.Please refer to Fig. 5, the protocol type carried in 183 response messages due to the UAS response is RTP, this protocol type is obviously inconsistent with the SRTP that request is consulted, now UAC mono-end can perceive such mistake, namely SRTP consults unsuccessfully, in the prior art, UAC can respond ACK and then send BYE message.But the present invention is after perceiving such mistake, can utilize early-session negotiation ability to be implemented to the rollback that RTP calls out.
So-called early-session negotiation ability refers to the negotiation mechanism before a kind of off-hook conversation.In current standard, can realize that before the off-hook conversation mechanism of consulting generally includes 100rel and two kinds of negotiation mechanisms of Update.The present invention utilizes the early-session mechanism of these two kinds of standard definitions to realize the rollback that RTP calls out.Please refer to Fig. 5 and take Update as example, after receiving 183 or 180 response messages of carrying RTP that UAS sends, UAC sends the Update request message to UAS, and carries RTP related media information and consult the RTP calling with request in this request message.Can respond Update OK200 response message of UAC after UAS receives, and carry RTP related media information in this response message.As previously mentioned, because 183 message or 180 message are the message of the provisional response for Invite, so UAS still needs to send a response message of the OK200 for this request message of Invite.Whole process, be equivalent to before UAS responds the OK200 response message for Invite message, inserted an early-session negotiations process, if do not insert this negotiations process, what in original I nvite request, consult due to UAC so is that SRTP calls out, after receiving that so corresponding OK200 replys, UAC handles unit through consultation and can find the media protocol Type-Inconsistencies of consulting, thereby makes mistakes.The present invention is in a Update negotiations process of insertion midway of normal initial negotiation process, this protocol type of just request of UAC being consulted is revised as RTP from SRTP, because UAC only can preserve the protocol type of current negotiation, namely SRTP has been updated to RTP, when so waiting until the OK200 response message of receiving for Invite message, UAC just checks can not find the inconsistent situation of protocol type.
Please refer to Fig. 6, this mechanism of 100rel of take is example, different from the Update handling process is, in the treatment mechanism of 100rel, need to be when sending the Invite request message, while namely making a call, need in this request message, carry " Require:100rel ", UAS receives that rear its can carry RTP media relevant information and " Required:100rel " in response message equally when replying 183 response message like this.Owing to having carried " Require:100rel " in response message, 100rel flag information namely.According to the requirement of standard, when UAC receives with 183 response message of 100rel flag information, need to send PRACK message and received 183 response messages to UAS to confirm it.That is to say, the topmost effect of PRACK message is to opposite end, to confirm self to have received response message.But the present invention utilizes PRACK message again to initiate to consult at this, and carry RTP related media information and consult the RTP calling with request in PRACK message.This PRACK message after UAS receives, because self supports RTP, therefore can reply OK200 message for this PRACK message, and carry RTP related media information in this message.The same with a upper execution mode, because 183 message are provisional responses, UAS also can send an OK200 response message for Invite message.Whole process can be understood as the early-session negotiations process of insertion midway in normal initial negotiation process equally, this protocol type of just request of UAC being consulted is revised as RTP from SRTP, because UAC only can preserve the protocol type of current negotiation, namely SRTP has been updated to RTP, when so waiting until the OK200 response message of receiving for Invite message, UAC just checks can not find the inconsistent situation of protocol type.
As previously mentioned; UAC can first send probe message usually; in Session Initiation Protocol; this message is Options message normally; in simple execution mode, suppose that local terminal only supports a kind of in 100rel or Update, now obviously can only survey a kind of ability of opposite end; namely the early-session identical with local terminal consulted ability, and follow-up handling process is fixed.If but local terminal is supported 100rel and Update simultaneously, so in preferred mode, in order to make the present invention can there is application widely, now the efficiency test unit can check whether opposite end supports 100rel and two kinds of early-sessions of Update to consult ability simultaneously, because may show in the message that opposite end (namely UAS) replys that opposite end supports a kind of in 100rel and Update, also may two kinds all support.Follow-up processing need to be determined according to the check result of UAS in the efficiency test unit, suppose that UAC mono-side acquiescence is processed according to the Update mode, when discovery opposite end in efficiency test unit is supported 100rel and Update simultaneously or is only supported Update so, its mode according to acquiescence is processed, but iff the words of supporting 100rel, need to notify initial negotiation unit and secondary negotiation element, the initial negotiation unit now needs according to notice when sending Invite message, carry therein " Require:100rel ", correspondingly the secondary negotiation element now needs to send PRACK message but not the Update request message according to notice.
At first, for implementing manufacturer of the present invention, whole back off procedure does not need the equipment of other manufacturers or terminal to coordinate, because rollback failure normally occurs between the equipment/terminal of different vendor, the rollback failure that this identification error causes can not occur between same vendor equipment/terminal usually.The present invention is by normal, insert an early-session in consulting flow process and consult flow process, even if allow normal SRTP consult flow process, makes a mistake and also can return back in time RTP and call out up.
The foregoing is only preferred embodiment of the present invention, in order to limit the present invention, within the spirit and principles in the present invention not all, any modification of making, be equal to replacement, improvement etc., within all should being included in the scope of protection of the invention.

Claims (10)

1. realize the RTP backspace mechanism for one kind, be applied on the network equipment or terminal, this device comprises ability probe unit, efficiency test unit, initial negotiation unit, handles unit and secondary negotiation element through consultation; It is characterized in that:
The ability probe unit, for to opposite end transmitting capacity probe message;
The efficiency test unit, consult ability for determine the common early-session of supporting in local terminal and opposite end after receiving response detected message;
The initial negotiation unit for send Invite message to opposite end, and carries SRTP related media information and consults the SRTP calling with request in this message;
Handle unit through consultation, for from opposite end, receive for Invite message and carry the provisional response message of RTP related media information, determine SRTP call negotiation failure, notice secondary negotiation element is processed;
The secondary negotiation element, send early stage negotiation request message for using local terminal and the opposite end common early-session of the supporting ability of consulting, and carry RTP related media information and call out with request negotiation RTP in this message to opposite end; Wherein
The described unit of handling through consultation, be further used for after receiving early stage negotiation response message, confirming to consult successfully, sends acknowledge message to opposite end and consult to complete RTP.
2. device as claimed in claim 1 is characterized in that:
The described unit of handling through consultation, be further used for when receiving the response message of carrying SRTP related media information from opposite end, sends acknowledge message to opposite end and consult to complete SRTP.
3. device as claimed in claim 1 is characterized in that: described early-session negotiation ability is that Update consults ability, and described early stage negotiation request message is the Update request message.
4. device as claimed in claim 1 is characterized in that: described early-session negotiation ability is that 100rel consults ability, in wherein said Invite message, carries the 100rel flag information, and described early stage negotiation request message is PRACK message.
5. device as claimed in claim 1, it is characterized in that: the described unit of handling through consultation, be further used for receive early stage negotiation response message and for the OK200 message of Invite request message after confirm to consult successfully, send acknowledge message to opposite end and consult to complete RTP.
6. realize the RTP backing method for one kind, be applied to, on the network equipment or terminal, it is characterized in that, the method comprises the following steps:
Steps A, to opposite end transmitting capacity probe message;
The early-session of step B, the common support of definite local terminal and opposite end after receiving response detected message is consulted ability;
Step C, send Invite message to opposite end, and carry SRTP related media information and consult SRTP with request and call out in this message;
Step D, from opposite end, receive for Invite message and carry the provisional response message of RTP related media information, determine that the SRTP call negotiation unsuccessfully goes to step E and processes;
Step e, the early-session that uses local terminal and opposite end jointly the to support ability of consulting send early stage negotiation request message to opposite end, and carry RTP related media information and consult the RTP calling with request in this message;
Step F, confirm to consult successfully after receiving early stage negotiation response message, send acknowledge message to opposite end and consult to complete RTP.
7. method as claimed in claim 6, is characterized in that, also comprises:
Step G, when receiving the response message of carrying SRTP related media information from opposite end, send acknowledge message to opposite end and consult to complete SRTP.
8. method as claimed in claim 6 is characterized in that: described early-session negotiation ability is that Update consults ability, and described early stage negotiation request message is the Update request message.
9. method as claimed in claim 6 is characterized in that: described early-session negotiation ability is that 100rel consults ability, in wherein said Invite message, carries the 100rel flag information, and described early stage negotiation request message is PRACK message.
10. method as claimed in claim 6, is characterized in that, also comprises:
Step H, receive early stage negotiation response message and for the OK200 message of Invite request message after confirm to consult successfully, send acknowledge message to opposite end and consult to complete RTP.
CN2013103475900A 2013-08-09 2013-08-09 Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing Pending CN103475640A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2013103475900A CN103475640A (en) 2013-08-09 2013-08-09 Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2013103475900A CN103475640A (en) 2013-08-09 2013-08-09 Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing

Publications (1)

Publication Number Publication Date
CN103475640A true CN103475640A (en) 2013-12-25

Family

ID=49800336

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2013103475900A Pending CN103475640A (en) 2013-08-09 2013-08-09 Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing

Country Status (1)

Country Link
CN (1) CN103475640A (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101247218A (en) * 2008-01-23 2008-08-20 中兴通讯股份有限公司 Safety parameter negotiation method and device for implementing media stream safety
CN101433025A (en) * 2006-07-21 2009-05-13 思科技术公司 System and method for establishing a communication session between two endpoints that do not both support secure media
US20110093609A1 (en) * 2008-06-16 2011-04-21 Rolf Blom Sending Secure Media Streams
CN102223355A (en) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 Negotiation method and device for safety communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101433025A (en) * 2006-07-21 2009-05-13 思科技术公司 System and method for establishing a communication session between two endpoints that do not both support secure media
CN101247218A (en) * 2008-01-23 2008-08-20 中兴通讯股份有限公司 Safety parameter negotiation method and device for implementing media stream safety
US20110093609A1 (en) * 2008-06-16 2011-04-21 Rolf Blom Sending Secure Media Streams
CN102223355A (en) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 Negotiation method and device for safety communication

Similar Documents

Publication Publication Date Title
US8599834B2 (en) Systems, methods, and computer program products for providing a manual ring-down communication line using session initiation protocol
US8363572B2 (en) Session initiation protocol extensions for call control and resource status monitoring in turrets and turret switching systems
US20080013447A1 (en) Method and Apparatus for Survivable Failover in Communication System
KR20070077062A (en) System and method for spam detection
US20050180317A1 (en) Server backup device
CN105119877A (en) Voice verification method, device and system
US20070217430A1 (en) Method and system for initiating communications
BRPI0614428A2 (en) associating a phone call with a computer protocol-based dialog such as sip
US9838447B2 (en) Method of conveying a location information representing a physical location of a first communication device, a computer program product for executing the method, and the first communication device for conveying the location information
CN108833943A (en) The encrypted negotiation method, apparatus and conference terminal of code stream
WO2015154520A1 (en) Call recording method, recording server, private branch exchange and recording system
US10230801B2 (en) Session reconstruction using proactive redirect
JP2012527831A (en) Save call logic during handoff
JP6305786B2 (en) Incoming call control apparatus, incoming call control method, and program
JP2015091125A (en) Method of expanding application interface for future application
US20150031341A1 (en) Method for responding to push notification based communication request
WO2017150281A1 (en) Early-media service control device, early-media service control method, and storage medium having program stored thereon
US10193938B2 (en) Operating a network node
WO2017152566A1 (en) Method for negotiating media coding/decoding, and terminal device
CN108810012B (en) Communication method and device based on SIP protocol
US9973623B2 (en) Methods, devices and system for logging calls for terminals
CN103475639A (en) RTP (Real-time Transport Protocol) backspacing method and apparatus
US8667149B2 (en) Communication device, communication method, and computer-readable storage medium storing communication program
CN103475640A (en) Method and apparatus for realizing RTP (Real-time Transport Protocol) backspacing
CN104901922A (en) Data service processing method and device based on session initiation protocol (SIP)

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information
CB02 Change of applicant information

Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No.

Applicant after: Xinhua three Technology Co., Ltd.

Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base

Applicant before: Huasan Communication Technology Co., Ltd.

RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20131225