[go: up one dir, main page]

WO2007128190A1 - Procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, passerelle multimédia et système associés - Google Patents

Procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, passerelle multimédia et système associés Download PDF

Info

Publication number
WO2007128190A1
WO2007128190A1 PCT/CN2007/001062 CN2007001062W WO2007128190A1 WO 2007128190 A1 WO2007128190 A1 WO 2007128190A1 CN 2007001062 W CN2007001062 W CN 2007001062W WO 2007128190 A1 WO2007128190 A1 WO 2007128190A1
Authority
WO
WIPO (PCT)
Prior art keywords
context
endpoint
physical entity
conference bridge
virtual
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.)
Ceased
Application number
PCT/CN2007/001062
Other languages
English (en)
Chinese (zh)
Inventor
Dahai Wang
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2007128190A1 publication Critical patent/WO2007128190A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, device and system for associating a conference bridge context and a call leg (Cal L Leg ) context.
  • the H.248 protocol was improved on the basis of the earlier Media Gateway Control Protocol (MGCP).
  • the H.248 protocol is a gateway control protocol for connecting a media gateway (MGW) to a media gateway controller (MGC), and is applied between a media gateway and a media gateway controller and between a media gateway controller and an H.248 terminal. It is an important protocol that the Media Gateway Controller should support.
  • the connection model defined by the H.248 protocol includes two main concepts: Terminator and Context.
  • An endpoint is a logical entity in a media gateway that can send and receive one or more media. Endpoints can represent time division multiplexing (TDM) channels, analog telephone lines, and Real Time Transport Protocol (RTP) streams.
  • TDM time division multiplexing
  • RTP Real Time Transport Protocol
  • Endpoint types mainly have semi-permanent endpoints (such as TDM channels or analog telephone lines) and temporary endpoints (such as RTP streams for carrying voice, data and video signals or various mixed signals).
  • the attributes are represented by attributes, events, signals, and statistics, and the concept of a package is introduced in the protocol to combine various characteristic parameters of the endpoint into a package.
  • an endpoint belongs to and can only belong to a context.
  • a context is an association between endpoints. It describes the topology relationship between endpoints and the parameters of media mixing/swapping. It can be created with the ADD command, using Subtract or Move. The command is deleted.
  • the inventor has found that the third-generation partner's independent bearer circuit-switched core network (3GPP TS 23.205) protocol defines an option for implementing multi-party call and conference-type services according to a separate context, and the basic idea is : On the conference bridge resource gateway (corresponding to the aforementioned media gateway), place the conference bridge in a context, and each Ca ll Leg endpoint is placed in a different context; then the conference bridge context and Cal l Leg contexts are associated.
  • the separation of contexts brings flexibility and, to some extent, simplifies implementation, such as listening and playback can be done in the context of Cal l Leg, thus eliminating the need for conferences. Complex topology operations in the bridge context.
  • this kind of conference bridge context and Cal l Leg The association of the text requires a specific implementation, and the agreement is not provided, and the prior art does not provide a related solution.
  • An object of the embodiments of the present invention is to provide a method for associating a conference bridge context with a Cal l Leg context, a method for associating two contexts, an implementation device and a system, and providing a realistic and feasible association for separating a contextual multiparty call or conference. Program.
  • An embodiment of the present invention provides a method for associating a conference bridge context and a call leg context, where the method includes: creating a virtual endpoint in a conference bridge context and a call leg Cal l Leg context to be associated, and The endpoints are associated with the same conference bridge channel through the feature information of the conference bridge channel.
  • An embodiment of the present invention further provides a method for associating two contexts, where the method includes: creating a virtual endpoint in a first context and a second context that need to be associated, and passing the two virtual endpoints through the same physical entity. The feature information is associated.
  • the embodiment of the present invention further provides a media gateway that implements association between two contexts, where the media gateway includes: a virtual endpoint creation unit, configured to respectively create a virtual endpoint in a first context and a second context that need to be associated; And an allocating unit, configured to associate the two virtual endpoints with feature information of the same physical entity.
  • a virtual endpoint creation unit configured to respectively create a virtual endpoint in a first context and a second context that need to be associated
  • an allocating unit configured to associate the two virtual endpoints with feature information of the same physical entity.
  • the embodiment of the present invention further provides a system for implementing association between two contexts, where the system includes a media gateway controller MGC and a media gateway MGW controlled by the MGC, and the media gateway specifically includes: a virtual endpoint creation unit, Creating a virtual endpoint respectively in a first context and a second context that need to be associated; a physical entity allocation unit to associate the two virtual endpoints with feature information of the same physical entity.
  • the system includes a media gateway controller MGC and a media gateway MGW controlled by the MGC
  • the media gateway specifically includes: a virtual endpoint creation unit, Creating a virtual endpoint respectively in a first context and a second context that need to be associated; a physical entity allocation unit to associate the two virtual endpoints with feature information of the same physical entity.
  • a virtual endpoint is created in two contexts to be associated, and the two virtual endpoints are associated with the feature information of the same physical entity, and two contexts are provided.
  • the specific implementation schemes associated with each other provide a practical means of implementation for separating contextual multiparty calls or conferences.
  • 1 is a schematic diagram of a multi-party call using the method of the associated conference bridge context and the Cal l Leg context of the present invention
  • 2 is a flow chart of a first embodiment of a method for associating a conference bridge context and a Cal l Leg context by using the A side of FIG. 1;
  • FIG. 3 is a schematic diagram of a method for applying a conference bridge context and a Cal l Leg context according to the present invention.
  • FIG. 4 is a flowchart of an associated conference bridge context and a Cal 1 Leg context in the case of A in FIG. 3;
  • FIG. 5 is a schematic structural diagram of a first embodiment of a media gateway for implementing two contexts according to the present invention
  • FIG. 6 is a schematic structural diagram of a second embodiment of a media gateway for implementing two contexts according to the present invention.
  • a virtual endpoint is separately created in the conference bridge context and the Cal 1 Leg context that need to be associated, and the two virtual endpoints are associated with the same conference bridge channel through the same conference bridge channel feature information, thereby Achieve the purpose of the associated conference bridge context and Ca 11 Leg context.
  • An H.248 extension package can be predefined, and the feature information of the conference bridge channel for associating the two virtual endpoints is carried by the attributes of the extension package and passed between the two virtual endpoints.
  • the feature information of the conference bridge channel includes but is not limited to the conference bridge channel identifier or the TDM slot number of the conference bridge channel. It will be readily understood by those skilled in the art that the feature information of the conference bridge channel can also be arbitrarily selected as long as the conference bridge channel can be uniquely identified.
  • FIG. 1 is a schematic diagram of a multi-party call using the associated conference bridge context and the Cal l Leg context method of the present invention
  • FIG. 2 is an associated conference bridge context using the A side of FIG. 1 as an example.
  • the feature information of the conference bridge channel is carried by the attributes of the predefined H.248 extension package and passed between the two virtual endpoints.
  • the identifier of the defined H.248 extension is sc_mpty and its attribute is identified as
  • this attribute is used to carry the feature information of the conference bridge channel.
  • the attribute is defined as a way to be transparent to the MGC, that is, the attribute value is selected as needed. And the MGC only needs to transparently transmit between the two virtual endpoints, and the specific content and meaning are interpreted by the MGW according to the attribute value.
  • the attribute value is CHOOSE (select)
  • the MGW selects an available conference bridge channel to assign to the virtual endpoint; the attribute value is the conference bridge channel.
  • the MGW selects a conference bridge channel corresponding to the feature information and assigns it to the virtual endpoint.
  • Step 210 The MGC sends a request message ADD request to the MGW, and the request message carries the H.248 extension package sc-mpty, and the AsscCtrllnfo value of the sc_mpty value is CH00SE.
  • this step is that the MGC sends the request message to notify the MGW to create a virtual endpoint in the conference bridge context.
  • the MGW selects an available conference bridge channel to assign to the virtual endpoint. And update the AsscCtrllnfo value of sc_mpty.
  • Step 220 The MGW creates a virtual endpoint added to the conference bridge context, assigns a temporary endpoint identifier to it, selects an available conference bridge channel to assign to the virtual endpoint according to the Sc_mpty AsscCtrllnfo value CHOOSE, and features the conference bridge channel.
  • the information is assigned to AsscCtrllnfo of sc_tnpty, and then the response message ADD reply with the endpoint identifier and the H.248 extension packet sc_mpty is sent to the MGC.
  • Channel 1 becomes the common physical entity corresponding to the Call Leg context and the conference bridge context of the associated A party.
  • the feature information of the channel 1 is selected by the MGW.
  • the feature information of the selected conference bridge channel is "xxxx", and the feature information value can be used to globally uniquely identify the channel 1, and the assigned temporary endpoint identifier is T1, which is used to The virtual endpoint is identified.
  • Step 230 The MGC sends a request message ADD request to the MGW, and the request message carries the H.248 extension packet sc_mpty, and the AsscCtrllnfo value of the sc-mpty value is the feature information "XXXX" of the conference bridge channel selected by the MGW in step 220.
  • this step is that the MGC sends the request message to notify the MGW to create a virtual endpoint in the Call Leg context, and informs the MGW to select the corresponding conference bridge channel to assign to the virtual endpoint according to the AsscCtrllnfo value "xxxx" of the sc-mpty.
  • Step 240 The MGW creates a virtual endpoint and adds it to the Call Leg context, assigns a temporary endpoint identifier to it, and selects the corresponding conference bridge channel according to the sc-mpty AsscCtrllnfo value "xxxx" to assign the virtual endpoint, in other words, This virtual endpoint in the Call Leg context is associated with the conference bridge channel with feature information "xxxx", and a response message ADD reply with the endpoint identifier is sent to the MGC.
  • the MGW selects the conference bridge channel according to the Sc-mpty As scCtr l lnfo value "xxxx".
  • Channel 1 assign the conference bridge channel to the virtual endpoint.
  • the MGC does not process the sc_mpty as scCtr l lnf o value; only in the Ca ll Leg context, the MGW needs to address Channel 1 according to this value.
  • a virtual endpoint is first created in the conference bridge context, and then a virtual endpoint is created in the Ca l Leg context.
  • it is allowed to create a virtual endpoint in the Cal l Leg context first, and then create a virtual endpoint in the conference bridge context, which is more complicated in implementation than the former.
  • the virtual endpoint in the context of the Cal l Leg cannot be directly associated with a specific conference bridge channel when it is created, it must wait until the MGW selects an available conference bridge channel to be assigned to the virtual endpoint in the conference bridge context, and the conference bridge is used by the MGW.
  • the feature information of the channel is sent to the MGC, and the MGC sends a command to the MGW to implement the association between the virtual endpoint in the Cal l Leg context and the conference bridge channel that meets the above feature information.
  • all conference bridge channels can be configured in the MGW and the MGC in advance, and each conference bridge channel is assigned two endpoint identifiers (Terminating Id), which are used as the feature information of the conference bridge channel. This will be described in detail below in conjunction with Figures 3 and 4.
  • FIG. 3 is a schematic diagram of a multi-party call using the associated conference bridge context and the Ca ll Leg context method of the present invention
  • FIG. 4 is an associated conference bridge context exemplified by the A side in FIG. 3 .
  • all the conference bridge channels are configured in advance in the MGW and the MGC, and each conference bridge channel is assigned two endpoint identifiers, and the two endpoint identifiers are used as the feature information of the conference bridge channel.
  • the two endpoint identifiers can uniquely identify and address the corresponding conference bridge channel in the MGW.
  • the configurations in the MGC and the MGW must be the same.
  • the process of feature information transfer is a process in which the MGC sends the two endpoint identifiers corresponding to the same conference bridge channel in the conference bridge context and the Ca ll Leg context of the MGW.
  • the MGC sends a request message carrying the conference bridge channel endpoint identifier to the MGW, and the MGW creates two virtual endpoints according to this, and adds the two virtual endpoints respectively to the conference bridge context and the Ca ll leg context, and according to the endpoint identifier of the virtual endpoint Assign the corresponding conference bridge channel to the virtual endpoint.
  • two endpoint identifiers are configured for Channel 1 in the MGC and the MGW: T1 and T2.
  • the following is an example of the participant of the multiparty party, which is similar to the other party, and illustrates the Cal l Leg context of the party A. Steps for conference bridge context association:
  • Step 410 The MGC sends a request message ADD reques t to the MGW, where the request message carries the endpoint identifier T1.
  • this step is that the MGC sends the request to notify the MGW to add a virtual endpoint with the endpoint identifier T1 in the conference bridge context, and the MGW addresses the conference bridge channel Channel 1 according to the endpoint identifier and the saved configuration information, Channel 1 It becomes the physical entity corresponding to the conference bridge context and the Cal l Leg context where the associated A party is located.
  • Step 420 The MGW creates a virtual endpoint with the endpoint identifier T1 added to the conference bridge context, assigns the conference bridge channel Channel 1 to the virtual endpoint according to the endpoint identifier T1, and sends a response message ADD reply with the endpoint identifier T1.
  • the MGW creates a virtual endpoint with the endpoint identifier T1 added to the conference bridge context, assigns the conference bridge channel Channel 1 to the virtual endpoint according to the endpoint identifier T1, and sends a response message ADD reply with the endpoint identifier T1.
  • Step 430 The MGC sends a request message ADD reques t to the MGW, and the request message carries the endpoint identifier T2.
  • this step is that the MGC sends the request to notify the MGW to add a virtual endpoint with the endpoint identifier T2 in the context of the Cal l Leg, and the MGW addresses the conference bridge channel Channel 1 according to the endpoint identifier T2 and the saved configuration information. .
  • Step 440 The MGW creates an endpoint identifier for adding the T2 virtual endpoint to the Cal 1 Leg context, assigns the conference bridge channel Channel 1 to the virtual endpoint according to the endpoint identifier T2, and sends a response message ADD reply with the endpoint identifier T2 to MGC.
  • a virtual endpoint may also be created in the context of the Cal l Leg, and then a virtual endpoint is created in the context of the conference bridge, wherein the delivery process of the feature information is similar.
  • Both embodiments of the invention are simple and straightforward.
  • the first embodiment is more flexible, more scalable, and less manual intervention, while the second embodiment does not need to define an H.248 extension package, but requires more configuration work on the MGW and the MGC.
  • Both of the embodiments directly use the virtual endpoint to abstract the conference bridge channel resources without occupying the actual bearer port resources.
  • the six endpoints T1-T6 in FIG. 1 or 2 adopt the real bearer endpoint, it is necessary to occupy the corresponding bearer port resources, and also involves the problem of bearer interworking in the MGW, which is difficult to implement.
  • the manner in which the actual bearer port resources are occupied also has difficulties in handling certain problems, such as playing a conference.
  • FIG. 5 it is a schematic structural diagram of a first embodiment of a media gateway implementing two contexts.
  • the media gateway of this embodiment includes a virtual endpoint creation unit 50 for creating a virtual endpoint in a first context and a second context that need to be associated, and a feature information for using the two virtual endpoints to pass the same physical entity.
  • a physical entity allocation unit 51 The following describes the internal structure of the media gateway in combination with its specific working principle.
  • the virtual endpoint creation unit 50 includes a first creation subunit 501 and a second creation subunit 502, and the physical entity assignment unit 51 includes a first assignment subunit 511 and a second assignment subunit 512.
  • the first creation sub-unit 501 creates a first virtual endpoint in the first context according to the first indication information of the MGC; then, the first allocation sub-unit 511 allocates the first physical entity that is available to the first virtual endpoint. And feeding back the feature information of the first physical entity to the MGC.
  • the second creation sub-unit creates a second virtual endpoint in the second context according to the second indication information of the MGC, where the second indication information includes the first physical entity feature information. Further, the second allocation sub-unit 512 further allocates the first physical entity to the second virtual endpoint according to the first physical entity feature information in the second indication information.
  • the first virtual endpoint and the second virtual The endpoints are assigned the same physical entity (such as the same conference bridge channel), so the two endpoints are associated, that is, the first context (such as the conference bridge context) and the second context (such as the call leg context) are associated. .
  • FIG. 6 is a schematic structural diagram of a second embodiment of a media gateway implementing two contexts.
  • the media gateway of this embodiment includes a virtual endpoint creation unit 60 for creating a virtual endpoint in the first context and the second context that need to be associated, respectively, to save a pair of endpoint identifiers and physical entities for each physical entity.
  • Correspondence relationship storage unit 63 of the correspondence relationship, and physical entity allocation unit 61 for associating the virtual endpoint created by the virtual endpoint creation unit 60 with the feature information of the same physical entity according to the correspondence relationship provided by the correspondence relationship storage unit .
  • the feature information of the physical entity is a corresponding pair of endpoint identifiers.
  • the feature information of the first physical entity is a first endpoint identifier and a second endpoint identifier.
  • the internal structure of the media gateway is further introduced below in conjunction with its specific working principle.
  • the virtual endpoint creation unit 60 includes a first creation subunit 601 and a second creation subunit 60 2
  • the physical entity allocation unit 61 includes a first allocation subunit 611 and a second allocation subunit 61.
  • First, created by the first The sub-unit 601 creates a first virtual endpoint in the first context according to the first endpoint identifier indicated by the MGC; then, the correspondence relationship provided by the first assignment sub-unit 611 according to the correspondence relationship storage unit 63 (the first endpoint identifier, the first The correspondence between the two endpoint identifiers and the first physical entity is to allocate the corresponding first physical entity to the first virtual endpoint.
  • the second creation sub-unit 602 creates a second virtual endpoint in the second context according to the second endpoint identifier indicated by the MGC; and further, the correspondence relationship provided by the second association sub-unit 612 according to the correspondence relationship storage unit 63.
  • An endpoint identifier, a correspondence between the second endpoint identifier and the first physical entity, and a corresponding first physical entity is allocated to the second virtual endpoint. So far, since the first virtual endpoint and the second virtual endpoint are assigned the same physical entity (such as the same conference bridge channel), the two endpoints are associated, that is, the first context (such as the conference bridge context) and The second context (such as the call leg context) is associated.
  • the present invention also discloses a system for implementing association between two contexts, the system comprising a media gateway controller MGC and a media gateway MGW controlled by the MGC, the media gateway may have specific ones in the above two embodiments structure.
  • This scheme provides a specific implementation scheme for associating the two contexts. Moreover, since the virtual endpoint is used instead of the real bearer endpoint, the corresponding bearer port resources are not required to be occupied, and thus less involved in the MGW. The problem of carrying interoperability is therefore simple to implement. It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to be limiting, and those skilled in the art should understand that the technical solutions of the present invention may be modified or equivalently substituted without departing from the technical solutions of the present invention. The spirit of the scope should be covered by the scope of the claims of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, ainsi qu'une passerelle multimédia et un système associés. Dans le contexte de pont de conférence et le contexte de branche d'appel qui sont rendus incidents, le procédé consiste à établir une terminaison (logique) virtuelle séparément, et les informations de caractéristiques du canal du pont de conférence rendent les terminaisons virtuelles et ce même canal de pont de conférence incidents.
PCT/CN2007/001062 2006-04-29 2007-04-02 Procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, passerelle multimédia et système associés Ceased WO2007128190A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2006100780583A CN100527731C (zh) 2006-04-29 2006-04-29 一种关联会议桥上下文和呼叫腿上下文的方法
CN200610078058.3 2006-04-29

Publications (1)

Publication Number Publication Date
WO2007128190A1 true WO2007128190A1 (fr) 2007-11-15

Family

ID=38667412

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/001062 Ceased WO2007128190A1 (fr) 2006-04-29 2007-04-02 Procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, passerelle multimédia et système associés

Country Status (2)

Country Link
CN (1) CN100527731C (fr)
WO (1) WO2007128190A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780403B (zh) * 2012-10-24 2017-06-06 华为技术有限公司 电话会议的处理方法、装置和系统
CN105450427A (zh) * 2015-12-25 2016-03-30 邦彦技术股份有限公司 会议级联方法、装置
EP3560183B1 (fr) * 2016-12-23 2023-07-12 Telecom Italia S.p.A. Résolution de collision d'appel dans un réseau de communication

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1313241A2 (fr) * 2001-11-16 2003-05-21 Alcatel Canada Inc. Gestion de liens numériques SDH/SONET (HNS )
CN1545303A (zh) * 2003-11-10 2004-11-10 ����ͨѶ�ɷ����޹�˾ 承载和控制相分离的通信网络中多方会议业务的实现方法
CN1553668A (zh) * 2003-06-03 2004-12-08 华为技术有限公司 一种虚拟媒体网关之间互通的方法
US20040266437A1 (en) * 2003-04-17 2004-12-30 Spatial Communication Technologies, Inc. Method and system for providing mobile handover across multiple media gateways controlled by the same call server
WO2005107159A1 (fr) * 2004-04-29 2005-11-10 Utstarcom Telecom Co., Ltd. Procede de commande de supports permettant d'effectuer une interception legale au moyen d'un systeme de commutateur logiciel
US6996221B1 (en) * 1999-12-07 2006-02-07 Lucent Technologies Inc. Apparatus, method and system for providing telecommunication conferencing services in a multiple leg telecommunication session

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6996221B1 (en) * 1999-12-07 2006-02-07 Lucent Technologies Inc. Apparatus, method and system for providing telecommunication conferencing services in a multiple leg telecommunication session
EP1313241A2 (fr) * 2001-11-16 2003-05-21 Alcatel Canada Inc. Gestion de liens numériques SDH/SONET (HNS )
US20040266437A1 (en) * 2003-04-17 2004-12-30 Spatial Communication Technologies, Inc. Method and system for providing mobile handover across multiple media gateways controlled by the same call server
CN1553668A (zh) * 2003-06-03 2004-12-08 华为技术有限公司 一种虚拟媒体网关之间互通的方法
CN1545303A (zh) * 2003-11-10 2004-11-10 ����ͨѶ�ɷ����޹�˾ 承载和控制相分离的通信网络中多方会议业务的实现方法
WO2005107159A1 (fr) * 2004-04-29 2005-11-10 Utstarcom Telecom Co., Ltd. Procede de commande de supports permettant d'effectuer une interception legale au moyen d'un systeme de commutateur logiciel

Also Published As

Publication number Publication date
CN101043508A (zh) 2007-09-26
CN100527731C (zh) 2009-08-12

Similar Documents

Publication Publication Date Title
JP5044380B2 (ja) 配信装置及びコーデック変換装置、通信システム
EP1744517B1 (fr) Méthode et système pour jouer des fichiers multimédia
WO2009097792A1 (fr) Procédé et équipement pour établir une connexion de conférence audio
CN100571147C (zh) 一种利用媒体服务器实现子会议的方法
US20090299735A1 (en) Method for Transferring an Audio Stream Between a Plurality of Terminals
CN104756447B (zh) 一种录制会话信息的方法和录制服务器
CN1556645A (zh) 一种在下一代网络中提供个性化回铃音业务的系统及方法
WO2007128190A1 (fr) Procédé servant à rendre incidents un contexte de pont de conférence et un contexte de branche d'appel, passerelle multimédia et système associés
CN101860547A (zh) 组呼或广播呼叫接续的控制方法、装置及系统
CN103546459A (zh) 一种基于会话初始协议进行会话的方法、终端及服务器
WO2007115472A1 (fr) Procédé de réalisation d'une multisession et système et dispositif de réalisation de la multisession
CN100463404C (zh) 利用媒体资源服务器实现电话会议业务的方法
WO2012155641A1 (fr) Procédé pour la mise en œuvre d'un service de conférence multimédia et dispositif correspondant
CN102271137A (zh) 一种媒体服务器
CN101772195B (zh) Ims集群会议的创建和加入方法及分发系统和装置
US20030165145A1 (en) Apparatus and method for compulsively receiving multi-calls over internet protocol phones in internet protocol telephony system
CN100568898C (zh) 一种基于ParlayAPI的多媒体呼叫中心系统
CN1738263A (zh) 软交换系统媒体流的监听方法及采用的监听网关处理装置
CN100461878C (zh) 实现媒体网关控制协议放音的方法
CN101227473A (zh) 用于多媒体通信系统的主控会议的系统及方法
CN100589435C (zh) 一种软交换中控制媒体资源播放的装置及其方法
CN100450223C (zh) 一种在移动软交换架构下实现集群业务的方法
CN101163136B (zh) 一种利用会话初始协议软终端播放话务员工号的方法
CN101258717B (zh) 媒体网关系统与实现媒体网关内部呼叫的方法
CN100452892C (zh) 对会话进行放音的方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07720636

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07720636

Country of ref document: EP

Kind code of ref document: A1