WO2005043879A1 - Procede de suivi d'appel sur tout le reseau dans un systeme de commutation - Google Patents

Procede de suivi d'appel sur tout le reseau dans un systeme de commutation Download PDF

Info

Publication number
WO2005043879A1
WO2005043879A1 PCT/CN2003/000911 CN0300911W WO2005043879A1 WO 2005043879 A1 WO2005043879 A1 WO 2005043879A1 CN 0300911 W CN0300911 W CN 0300911W WO 2005043879 A1 WO2005043879 A1 WO 2005043879A1
Authority
WO
WIPO (PCT)
Prior art keywords
tracking
call
terminal
message
sends
Prior art date
Application number
PCT/CN2003/000911
Other languages
English (en)
Chinese (zh)
Inventor
Qun Shi
Jianhua Tao
Original Assignee
Utstarcom (China) 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 Utstarcom (China) Co. Ltd. filed Critical Utstarcom (China) Co. Ltd.
Priority to PCT/CN2003/000911 priority Critical patent/WO2005043879A1/fr
Priority to AU2003280547A priority patent/AU2003280547A1/en
Priority to CNB2003801104879A priority patent/CN100544392C/zh
Publication of WO2005043879A1 publication Critical patent/WO2005043879A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2281—Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls

Definitions

  • the present invention relates to a softswitch telecommunication network system, and in particular, to a method for tracking the entire network and the entire process of calls and signaling when multiple entities participate in a call in a softswitch system. Background technique
  • the traditional telecommunication network consists of multiple switching nodes (telephone switches), and each switching system does not have a unified structure, and the tracking of call signaling can only be limited to a single switch.
  • a telecommunications network that includes switches A, B, and C
  • switch A initiates a call
  • switch A connects to a user in switch C through switch B (tandem office).
  • switch B tandem office
  • call signaling tracking can only be performed in each switch separately, and the entire call signaling interaction process cannot be observed. For example, switch A cannot observe the call signaling of switches B and C.
  • the traditional switching system does not have a unified structure, there is also no unified method for tracking call signaling, which prevents the traditional telecommunications network from tracking the call signals throughout the entire network.
  • a switch composed of a central processing module, a background processing module, and a switching processing module
  • when performing call tracking maintenance personnel set tracking conditions on the terminal, and the background processing module sends the tracking conditions to the switching processing.
  • the switching processing module when a call occurs, the switching processing module sends the call signaling that meets the conditions to the background processing module, and then displays it on the terminal.
  • each call signaling can only be listed simply. Maintenance personnel need to find the faulty message among a large number of messages, which is time-consuming and labor-intensive.
  • the network elements involved More, for example, the traditional switch softswitch system structure is often divided into call server CS : media gateway MG and signaling gateway SG, so call tracking is more complicated, and there is no unified call tracking specification defined in the current softswitch system. .
  • Figure 1 shows a simplified schematic of a softswitch system. It is mainly composed of entities such as application server (AS), call server (CS), signaling gateway (SG), media / relay gateway (MG / TG).
  • the application server (AS) completes the service processing
  • the call server (CS) completes the call processing
  • the signaling gateway (SG) is used for MTP processing of SS7
  • the media / relay gateway (MG / TG) is used for media access.
  • Different entities define different types of interface protocols, such as M3UA between CS and SG for transmitting MTP3 signaling; IUA / MEGACO between CS and MG / TG, and IUA for transmitting Q.931 signaling, MEGACO is used to transfer media control signaling.
  • CS and AS have not been determined in the current softswitch specifications.
  • an object of the present invention is to provide a method for tracking the entire network and the entire call in a softswitch architecture.
  • the network includes a call tracking subsystem composed of at least multiple tracking terminals and multiple tracked nodes, where each tracking terminal and at least one The tracked nodes are connected, the call involves multiple entities, and the method includes the following steps: The user initiates a tracking task on the tracking terminal and sets the tracking conditions; the tracking terminal requests the corresponding tracked node to establish a connection; the tracked node When a call occurs, the received or sent messages are buffered, and each tracking information is numbered, and the number increases with time; the tracked node searches for calls that meet the condition according to the set tracking condition; the tracked node will meet the tracking condition The extended IP datagram header of the call that was inserted into the call message as a call tracking option is sent to the tracking terminal; the tracking terminal displays the signaling interaction process of the call that meets the tracking conditions in the
  • a message sequence diagram (MSC) of the entire call can be obtained by dynamically displaying the signaling interaction process of a designated call in a graphic window on the screen of the tracking terminal in real time.
  • This message sequence diagram includes the participating network elements, instances, status identifiers, signaling interactions, and call outliers.
  • the cause of the call failure can be obtained by using the abnormal point of the call, and the real cause of the call can be obtained according to the call status and the signal.
  • the invention can also be used to quickly troubleshoot.
  • Existing fault locating technologies require manual and manual export of call record information, and then the available information is filtered from these records.
  • information can be automatically derived and filtered.
  • the prior art may require a lot of engineers to spend a lot of time to locate, and with the call tracking method of the present invention, only one engineer can solve it in a short time. If the present invention is not used, it usually takes several hours to locate a fault. After using the present invention, it only takes 5 minutes to locate and find the cause of the fault. BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a schematic structural diagram of a soft switching system used in an embodiment of the present invention
  • FIG. 2 shows a call signaling interaction process in a soft switching system according to a practical example of the present invention
  • FIG. 3 is a flowchart of a method for tracking a call throughout the entire network in a softswitch system according to an embodiment of the present invention
  • Figure 4 is a subsystem configuration diagram of call tracking
  • FIG. 6 shows the format of an IPv4 datagram
  • FIG. 7 shows the format of an IPv4 datagram option code
  • Figure 8 shows the format of the IPv4 call tracking option
  • FIG. 9 shows the format of an IPv6 datagram
  • Figure 10 shows the format of an IPv6 end-to-end extension header
  • FIG 11 shows the format of an IPv6 call tracking option
  • FIG. 12 shows an example of an MSC for call tracking according to an embodiment of the present invention
  • FIG. 13 is a process of canceling tracking according to an embodiment of the present invention. detailed description
  • Figure 2 describes the signaling interaction process of an ISDN terminal user initiating a call to PSTN / ISDN. It involves three entities, MG, CS, and SG, and requires the participation of two protocols, IUA and M3UA.
  • the MG sends a call setup message (setup) to the CS through the IUA, and the CS considers that the called number is Complete, send a call proceeding message to the MG; then the CS will send an initial address message (IAM) to the peer switch via SG; when the called party rings, the peer switch sends a full address message to the CS via SG ( ACM); CS sends ringing message (alerting) to MG;
  • CS cannot call for some reason, CS will send release message (REL) to peer switch through SG; CS will also send release message (rel) to MG ; Finally, the peer switch sends a release complete message (RLC) to the CS through the SG; the MG sends a
  • FIG. 3 describes the working procedure of the whole network tracking call in the softswitch system of the present invention.
  • the tracking console sets the tracking conditions
  • the tracking console connects to the tracked node and sets the tracking conditions to the calling gateway. Once there are calls that meet the conditions, the call tracking system will be triggered.
  • the tracking system collects related call information for each tracking information number by buffering the received or sent messages.
  • the tracked node searches for a call that satisfies the condition according to the set tracking condition.
  • step S350 the tracking node inserts the tracking information of the call that meets the tracking condition as a call tracking option into the header of the extended IP datagram of the call message, encapsulates the collected related call information into a unique IP data packet, and sends Towards the tracking terminal. Dump the IP data packets to the monitoring station via the network.
  • step S360 display the signaling interaction process of the call that meets the tracking conditions in the graphic window of the tracking terminal.
  • Figure 4 shows the subsystem configuration of call tracking. It consists of two parts, namely the tracked node and the tracking terminal.
  • the tracked nodes are tracking objects, such as CS, SG, MG, etc.
  • the tracking terminal is part of the network management and is used to display tracking information.
  • Each tracking terminal can be connected to all tracked nodes or designated tracked nodes, that is, multiple pairs Many relationships.
  • the tracking terminal 1 can communicate with the tracked node.
  • tracking terminal 2 can establish a connection with tracked node 1, 3; tracking terminal 3 can establish a connection with tracked node 2.
  • Messages need to be exchanged between the tracking terminal and the tracked node. For example, when the tracking terminal is started or stopped, the tracking terminal sends a tracking command to the tracked node. During the tracking process, the tracked node sends tracking information to the tracking terminal, that is, the entity receives Or send a message.
  • Figure 5 is the process of starting the tracking.
  • the maintenance staff starts a tracking task on the tracking terminal, and sets the tracking conditions, such as the user number, the relay ID, and the scope of the tracking, that is, the entities that need to be tracked.
  • the tracking terminal requests the tracked entity to establish a connection, and sends a tracking start instruction to the corresponding entity (all tracked entities or some entities).
  • the entity that received the tracking start command should remember the conditions of the tracking and send back the start command to confirm.
  • the tracked entity When a call occurs, the tracked entity shall cache the tracking information, such as received or sent messages, and number each tracking information (this number is valid only within the entity), and the number is incremented by time. At the same time, the tracked entity searches whether the call is a call to be tracked by the maintenance personnel according to the tracking conditions, that is, whether the tracking conditions are met, and if it is met, the tracking information of the call is sent to the tracking terminal.
  • each interface protocol such as IUA, MEGACO (H.248), M3UA, etc.
  • the format of each protocol is different, and it is not easy to expand, otherwise interoperability cannot be achieved.
  • the header of the IP datagram can be extended, in which a unified message header for call tracking is defined for implementation.
  • the interface information often contains only necessary call-related information, and the extended interface information can be used to carry call-independent tracking information. It can be said that the extended information is attached to the original interface, but does not affect the call. Need to expand The information includes: tracking terminal IP and tracking task ID, used to enable the entity receiving the message to send the tracking information related to the call to the designated tracking terminal; the tracking information number of the sender, the entity ID of the sender and the instance of the sender call ID, used to facilitate matching of sent and received messages.
  • IPv4 IPv4
  • IPv6 IPv6
  • FIG 6 shows the format of an IPv4 datagram.
  • the IP option contains multiple octets. In order to ensure that the IP header is an integer multiple of 32 bits, if the length of the IP option is not an integer multiple of 32 bits, fill it with zeros. Multiple options can be included in the IP option.
  • the first octet of each option is the option code. If the option contains data, the second octet is the option length (the length is equal to the option data length plus two, that is to say Enter the length of the option code and length itself), followed by the option data.
  • Figure 7 is the format of the option code.
  • the copy field indicates whether the option should be copied to all the fragments when the IP datagram is fragmented.
  • the option class and option number indicate the type of the option.
  • the option class and option number defined in rfc791 For:
  • IPv4 call tracking option The format of the IPv4 call tracking option is described as follows:
  • Tracking task ID length is two octets
  • Tracking terminal IP length is four octets
  • Sender entity ID length is four octets
  • Sender call instance ID length is four octets
  • Tracking information number is four octets in length
  • Figure 9 shows the format of an IPv6 datagram.
  • IPv6 content refer to rfcl883 of the Internet Engineering Task Force (IETF).
  • IETF Internet Engineering Task Force
  • multiple extension headers can be included.
  • RFC1883 defines an end-to-end extension header for end-to-end transmission of options.
  • Figure 10 illustrates the format of the end-to-end extension header.
  • the first octet indicates the type of the next header (see RFC1700 for the definition of the value of the header type), and the second octet is the length of the header (the length of all headers). This is followed by one or more IP options.
  • the first octet of each option is the type field, and its upper two bits indicate what to do if the host or router does not recognize the option.
  • the third to twenty-seventh bits are option codes.
  • the second octet is the option length (only the length of the data) followed by the option data.
  • RFC1883 defines only two fill options:
  • PadO a fixed-length padding option, has only one octet (ie type), and the type code is 0
  • Padl is a variable-length padding option that includes type, length, and padding data.
  • the type code is 1, the length is the length of the padding data, and the padding data is an octet with a value of 0.
  • Figure 11 defines the format of the IPv6 call tracking options, as described below: Types of
  • Bits 0 and 1 are 00, that is, skip this option if you do n’t know. Bit 2 is 0. Routers are not allowed to change. Bits 3 to 7 are called.
  • Tracking task ID length is two octets
  • Tracking terminal IP length is sixteen octets
  • Sender entity ID length is four octets
  • Sender call instance ID length is four octets
  • the length of the tracking information number is four octets.
  • the entity that meets the detection conditions shall send all messages related to the call to the corresponding tracking terminal (including those that have been buffered and will receive or send Message), and insert the call tracking option in the IP datagram that sends all subsequent call messages, that is, the call tracking information is filled in the extended IP header information.
  • the entity that receives the message with this option should also send all the messages of the call (including the message just received) to the designated tracking terminal, that is, infected, and remember the tracking task ID of the tracking terminal IP, when it You need to send a message to the call, and you need to add the same option (to infect the other party), so that all entities related to the call are infected.
  • To prevent tracking conditions from being nested that is, a call that has been tracked meets another tracking condition
  • the tracking conditions are no longer queried.
  • the interface between the tracked entity and the tracking terminal belongs to the internal interface of the product.
  • the interface should have the following key elements for tracking information. These key elements of tracking information are carried in the information of the standard interface extension.
  • the key elements of the tracking information include:
  • Tracking task ID There are two types: received message, sent message; sender entity ID.
  • Receiver entity ID Only valid for received messages
  • Receiver calling entity ID Only valid for received messages
  • Receiver tracking information number Only valid for received messages
  • the tracking terminal first classifies the received information into tracking tasks. This is because multiple tracking tasks can be started on a tracking terminal, and information belonging to the same tracking task should be displayed together (for example, in the same window).
  • each call instance finds out. This is because a tracking task can observe multiple calls, that is, they meet the same conditions, and the maintenance personnel need to observe each call separately (such as separate MSC diagrams). This can be determined by the association between sending and receiving messages.
  • the sender call instance ID and sender tracking information number of a sending message are the same as the sender call instance ID and sender tracking information number of the receiving message, the two messages can be considered as a pair, and the call sent and received Instances belong to the same call, so that all tracking information issued by these two call instances also belong to the same call, so that the instances and tracking information belonging to a call can be found out.
  • the MSC diagram should be drawn based on the ordered information.
  • the MSC has many vertical lines representing examples of state machines.
  • the state machine instance represents one of the examples above, since Each instance has state transitions, so it is also called a state machine instance.
  • the arrow indicates the message flow direction between instances, and the time sequence of message generation is indicated by the vertical position. The lower the value, the later the event occurs.
  • the tracking terminal In addition to drawing the MSC diagram, the tracking terminal also parses out the parameters of the message according to the information content to facilitate the maintenance personnel to read.
  • Figure 12 is an example of an MSC chart, which depicts a tracking MSC chart for a single call.
  • the tracking condition is called "635551".
  • the media gateway MG1 first triggers the call tracking system. When the call passes through the call center CS1 and the signaling gateway SG1, the call tracking information is also transmitted to the corresponding module.
  • the calling gateway (such as MG1, CS1, and SG1 in this example) and the module will all complete the call tracking task.
  • the right side of the figure shows a captured ISUP IAM message, where Seq is the sender tracking information number, Type Is the type, whose value indicates that the type is a message class; Dir is the direction, whose value indicates the received message; Source is the message sender ID, and its value indicates that the sender entity ID in CS1 is 1; Dest is the message receiver ID, which The value indicates that the receiver entity ID in SG1 is 1; OPC is the source signaling point number in the No. 7 signaling system, and its value is 32-33-55; DPC is the destination signaling point number in the No.
  • connection indictor is the connection characteristic indicator, It is no satellite (no satellite circuit), continuity not (non-conductive), outgoing echo not (no outgoing echo control).
  • FIG. 13 shows the process of canceling the tracking.
  • the maintenance staff first selects the tracking task to be canceled, and then clicks a stop button on the console, so that the console sends a stop control command to the phase
  • the tracking node should clear the tracking condition and cached tracking information after receiving the stop command, and return a confirmation message.
  • the console receives a confirmation message and the tracking task is canceled.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Technology Law (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention se rapporte à un procédé de suivi d'appel du réseau entier dans un système de commutation. Le procédé comprend les étapes suivantes: un utilisateur lance une tâche de suivi sur un terminal de suivi et définit les conditions. Les terminal demande le noeud suivi correspondant afin d'établir la liaison; le noeud stocke les messages reçus ou envoyés lorsqu'un appel à lieu et édite les nombres pour chaque information de suivi, lesdits nombres augmentant dans le temps; selon la condition de suivi définie, le noeud recherche l'appel correspondant à la condition; le noeud donne l'information de suivi de l'appel correspondant à la condition comme choix de suivi d'appel afin de l'insérer dans le haut du message de données IP d'extension de l'information d'appel et l'envoie vers le terminal de suivi; celui-ci affiche le processus de commutation de signalisation de l'appel correspondant à la condition sur la fenêtre du terminal de suivi. Grâce à ce procédé, dans un système de commutation, lorsque l'appel traverse plusieurs entités, il peut afficher tout le procédé de commutation de signalisation de l'appel directement dans le diagramme de séquence d'appel de manière à éviter rapidement les erreurs.
PCT/CN2003/000911 2003-10-28 2003-10-28 Procede de suivi d'appel sur tout le reseau dans un systeme de commutation WO2005043879A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2003/000911 WO2005043879A1 (fr) 2003-10-28 2003-10-28 Procede de suivi d'appel sur tout le reseau dans un systeme de commutation
AU2003280547A AU2003280547A1 (en) 2003-10-28 2003-10-28 A method of making a call tracing of the entire net and the whole process in a soft switch
CNB2003801104879A CN100544392C (zh) 2003-10-28 2003-10-28 在软交换系统中进行全网全程呼叫跟踪的方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2003/000911 WO2005043879A1 (fr) 2003-10-28 2003-10-28 Procede de suivi d'appel sur tout le reseau dans un systeme de commutation

Publications (1)

Publication Number Publication Date
WO2005043879A1 true WO2005043879A1 (fr) 2005-05-12

Family

ID=34529375

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2003/000911 WO2005043879A1 (fr) 2003-10-28 2003-10-28 Procede de suivi d'appel sur tout le reseau dans un systeme de commutation

Country Status (3)

Country Link
CN (1) CN100544392C (fr)
AU (1) AU2003280547A1 (fr)
WO (1) WO2005043879A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008000132A1 (fr) * 2006-06-23 2008-01-03 Huawei Technologies Co., Ltd. Système est procédé pour la collecte d'informations de signalisation sur la totalité d'un réseau et système de repérage de la signalisation sur la totalité du réseau
WO2008040257A1 (fr) * 2006-09-28 2008-04-10 Huawei Technologies Co., Ltd. Procédé, dispositif et système de poursuite de bout en bout
CN100417089C (zh) * 2005-11-01 2008-09-03 华为技术有限公司 一种呼叫日志的实现方法及设备
CN100441016C (zh) * 2005-09-05 2008-12-03 中兴通讯股份有限公司 一种移动通信网络协议信令处理系统和方法
CN101945109A (zh) * 2010-09-16 2011-01-12 电子科技大学 对七号信令网络传送过程进行路径记录及溯源追踪的方法
CN101098204B (zh) * 2006-06-29 2011-07-06 华为技术有限公司 全网信令时序还原方法
CN101114930B (zh) * 2006-07-26 2011-11-23 华为技术有限公司 业务跟踪方法及跟踪设备和系统
CN102891875A (zh) * 2011-07-21 2013-01-23 中兴通讯股份有限公司 信令跟踪方法、web客户端、服务端及信令跟踪系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8619603B2 (en) 2009-06-04 2013-12-31 Broadcom Corporation Method and system for end-to-end management of energy efficient networking protocols
CN102571402B (zh) * 2010-12-30 2014-12-10 中兴通讯股份有限公司 一种进行全程呼损分析的方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1212552A (zh) * 1997-06-18 1999-03-31 Lg情报通信株式会社 交换机中用于监视呼叫的系统和方法
CN1284232A (zh) * 1997-12-04 2001-02-14 艾利森公司 网络呼叫跟踪
WO2001047182A2 (fr) * 1999-12-21 2001-06-28 Telefonaktiebolaget Lm Ericsson (Publ) Surveillance et affichage de ressources dans un systeme de communication

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH09321869A (ja) * 1996-05-31 1997-12-12 Nec Corp 呼情報試験方法とその装置
KR100295832B1 (ko) * 1999-04-28 2001-07-12 박종섭 통화 채널 호 설정 메시지의 추적 방법

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1212552A (zh) * 1997-06-18 1999-03-31 Lg情报通信株式会社 交换机中用于监视呼叫的系统和方法
CN1284232A (zh) * 1997-12-04 2001-02-14 艾利森公司 网络呼叫跟踪
WO2001047182A2 (fr) * 1999-12-21 2001-06-28 Telefonaktiebolaget Lm Ericsson (Publ) Surveillance et affichage de ressources dans un systeme de communication

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100441016C (zh) * 2005-09-05 2008-12-03 中兴通讯股份有限公司 一种移动通信网络协议信令处理系统和方法
CN100417089C (zh) * 2005-11-01 2008-09-03 华为技术有限公司 一种呼叫日志的实现方法及设备
WO2008000132A1 (fr) * 2006-06-23 2008-01-03 Huawei Technologies Co., Ltd. Système est procédé pour la collecte d'informations de signalisation sur la totalité d'un réseau et système de repérage de la signalisation sur la totalité du réseau
CN101098204B (zh) * 2006-06-29 2011-07-06 华为技术有限公司 全网信令时序还原方法
CN101114930B (zh) * 2006-07-26 2011-11-23 华为技术有限公司 业务跟踪方法及跟踪设备和系统
WO2008040257A1 (fr) * 2006-09-28 2008-04-10 Huawei Technologies Co., Ltd. Procédé, dispositif et système de poursuite de bout en bout
CN101945109A (zh) * 2010-09-16 2011-01-12 电子科技大学 对七号信令网络传送过程进行路径记录及溯源追踪的方法
CN102891875A (zh) * 2011-07-21 2013-01-23 中兴通讯股份有限公司 信令跟踪方法、web客户端、服务端及信令跟踪系统
CN102891875B (zh) * 2011-07-21 2017-12-22 中兴通讯股份有限公司 信令跟踪方法、web客户端、服务端及信令跟踪系统

Also Published As

Publication number Publication date
AU2003280547A1 (en) 2005-05-19
CN100544392C (zh) 2009-09-23
CN1839617A (zh) 2006-09-27

Similar Documents

Publication Publication Date Title
JP3961717B2 (ja) 公衆交換電話網およびインターネットを介する呼の最適ルーティング
US7113581B2 (en) Methods and systems for providing dynamic routing key registration
US8121113B2 (en) Terminal-to-terminal communication connection control method using IP transfer network
US7254109B2 (en) Fault tolerant correlation engine method and system for telecommunications networks
JP3880867B2 (ja) Ｉｐエンドポイント間のｉｐベアラパスを管理するためのｉｐパケットアクセスゲートウェイ（ｉｐｐａｇ）システムおよび方法およびコンピュータプログラム製品
US7313129B1 (en) Arrangement for sharing a single signaling point code between multiple hosts in an IP-based network
JP3753316B2 (ja) 呼詳細記録の生成方法
US6687251B1 (en) Method and apparatus for distributed MTP Level 2 architecture
EP0753952A2 (fr) Gestion des vroes de routage dans un réseau de communication par paquets
EP1672836A1 (fr) Production de registres de détail du service téléphonique avec données de qualité de service
US6987781B1 (en) Methods and systems for routing signaling messages in a communications network using circuit identification code (CIC) information
JPH0683315B2 (ja) 通信網監視方法およびシステムおよび通信網要素
US8254540B2 (en) Method and apparatus for providing end-to-end call completion status
WO2008040257A1 (fr) Procédé, dispositif et système de poursuite de bout en bout
JP2003515969A (ja) Ｉｐ電話ネットワークにおける動的ゲートウェイ選択のための方法およびシステム
US20090190479A1 (en) Methods, systems and apparatus for monitoring and/or generating communications in a communications network
WO2005043879A1 (fr) Procede de suivi d'appel sur tout le reseau dans un systeme de commutation
US20050180396A1 (en) Managing routing path of voice over internet protocol (VoIP) system
WO2008097105A1 (fr) Procédés, système et appareil pour surveiller et/ou générer des communications dans un réseau de communications
US7263111B1 (en) System and method for interconnecting different SS7 network domains
WO2003103228A1 (fr) Mandataire d'interconnexion, et systeme et procede d'interconnection de reseaux utilisant des protocoles different
EP1519591A1 (fr) Méthodes et dispositif pour contrôler des passerelles de signalisation
Cisco Commands: debug serial interface through debug tacacs events
Cisco debug ipx - debug local-ack
Cisco

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200380110487.9

Country of ref document: CN

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP