JP2001119478A - Call connection method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a call connection method by which a software version of a communication opposite party can be recognized between exchanges and communication between exchanges with software programs of different versions can be attained. SOLUTION: When the version number of the software program of a caller exchange is older than that of a called exchange, the called exchange interprets parameter information of a packet from the caller exchange along the version of the caller exchange. In the case that the version number of the software program of the caller exchange is newer than that of the called exchange, the caller exchange interprets parameter information of a packet from the called exchange along the version of the called exchange.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a call connection method for enabling communication between an old version and a new version of software when communication between switching devices is performed using different versions of software.

[0002]

2. Description of the Related Art When software is upgraded in a switching device, if communication is performed between an old version and a new version, normal communication may not be performed due to a difference in communication contents. In such a case, the conventional switching device detects a malfunction of the communication content and disconnects the call, thereby preventing the switching device from malfunctioning. In addition, in order to enable correlation communication between the old version and the new version, the exchange device stores in advance the data of all versions of the exchange device with which the communication device is to communicate, and based on this, the exchange device of the new version is used. Information from the old version of the switching device was interpreted in a manner consistent with the old version.

[0003]

However, according to the above-described method, when a network is configured between a large number of switching devices, when upgrading the software of the switching devices, the software (or the software) of all the switching devices is updated. If the data is not changed at the same time, the normality of communication between networks cannot be guaranteed.

The present invention has been made in consideration of the above problems, and when communication is performed between switching devices having different software versions, a new version is referred to by referring to version information between switching devices for each call setting. The switching node of this version interprets information from the switching node of the old version in the form of the old version, thereby guaranteeing the normality of communication and providing a call connection method that improves the maintainability of the network. is there.

[0005]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the present invention relates to a method for connecting a call between exchanges having different versions of software. By notifying the version information of the software, the new and old versions of the software are compared, and a call connection is made based on control information corresponding to the software of the old version. Also, when version information that is newer than the version of its own software is received between the exchanges, the version of its own software is notified to the exchange to which the call is connected.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the call connection method according to the present invention will be described below in detail with reference to the drawings.

(1) Configuration of the Embodiment FIG. 5 shows the configuration of a switching apparatus 1 that accommodates a general analog telephone 2 and transmits voice over an Internet Protocol (hereinafter, referred to as IP) network. The switching device 1 mainly includes a basic module 11 and an IP network access module 12.

The basic module 11 includes a CPU 111, a hard disk 112, an analog subscriber interface unit 113 for accommodating the analog telephone 2, an audio facsimile control unit 114 for performing call connection and controlling audio / fax information, and an FA.
X modem 115 for connecting to IP network 3 such as the Internet / intranet, for example, 10B
a serial interface 117 that accommodates the LAN interface 116 such as aseT and the maintenance console 13 and is used for transmitting and receiving control information to and from the IP network access module 12.

[0009] IP network access module 12
Is a CPU 121, a voice control unit 122 for compressing voice information received from the basic module 11, etc., a LAN interface unit 123 such as 10BaseT for accommodating the IP network 3 such as the Internet / intranet, and control with the basic module 11. It has a serial interface unit 124 used for transmitting and receiving information.

(2) Operation of Embodiment Next, the operation of the embodiment will be described.

First, referring to FIG. 5, an outline of the operation when the analog telephone 2 calls the analog telephone 2 accommodated in another switching device 1 to have a conversation will be described.

The switching apparatus 1 sets up a call between the basic modules 11 via the router 4 to secure a communication path of the IP network 3. After securing the communication path, the originating exchange apparatus 1
The voice signal from the analog telephone 2 is transmitted to the basic module 11
After compression by the IP network access module 12, it is converted into an IP packet and transmitted to the IP network 3. Upon receiving the IP packet, the destination-side switching device 1 uses the IP network access module 12
The IP network access module 12 converts the packet into an analog signal and sends the analog signal to the analog telephone 2. As described above, a conversation via the IP network 3 is realized. Next, the details of the call connection operation between the switching devices will be described. The call control interface message for setting up a call between exchanges includes ITU
-Use a control packet conforming to T Recommendation Q931. Control packets include SETUP (call setup request) and CALL
_PROC (call setting reception), ALERT (call notification), CONN (response notification), CONN_ACK (response reception), DISC (disconnection), and the like.

[0013] Between the exchanges, the originating version number and the destination version number are added to the fixed header portion of the control packet format shown in FIG. 6 so that the version numbers of the communicating parties can be identified between the exchanges.

The operation in the case where communication is performed between exchanges having different software versions using the transmission / reception version numbers of the fixed header section in these control packets will be described below.

First, the operation when the software version of the calling-side switching device is older than the software version of the called-side switching device will be described with reference to the call connection sequence of FIG. 1 and the flowchart of FIG.

First, the telephone 2 connected to the originating exchange 1 is switched to the telephone 2 connected to the destination exchange 1.
Is dialed (A-1). Next, the originating exchange apparatus 1 sets its own version number to the originating version number in the fixed header part of the control packet, and issues a SETUP (call setting request) packet to the destination exchange apparatus 1 (A-
2). Upon receiving the SETUP packet, the destination exchange device 1 compares its own version number with the originating version number of the fixed header part of the control packet (A-3, S
11). As a result of the comparison, if the version number of the originating exchange device 1 is older than the version number of the destination exchange device 1, the destination exchange device 1 transmits a CALL_PROC (call setting acceptance) packet to notify that the SETUP has been accepted. It is issued to the calling-side switching device 1 in a form conforming to the version of the calling-side switching device 1 (A-4, S12). Next, the destination exchange device 1 places the telephone in a calling state, and then issues an ALERT (calling notification) packet to the originating exchange device 1 in a form conforming to the version of the originating exchange device 1 (A-5). , S13).
After the telephone 2 answers, the destination exchange 1
(Response notification) A packet is issued to the calling-side switching device 1 in a form conforming to the version of the calling-side switching device 1 (A-6). Next, the originating exchange apparatus 1 issues a CONN_ACK (response acceptance) packet to the destination exchange apparatus 1 to start a call (A-7). The receiving side exchange device 1 that has received the CONN_ACK (response acceptance) packet starts a call (A-8).

Next, the operation in the case where the software version of the originating exchange is newer than the software version of the destination exchange will be described with reference to the call connection sequence shown in FIG.
This will be described with reference to the flowchart of FIG. 2 and the flowchart of FIG.

First, the telephone 2 connected to the originating exchange 1 dials the number of the telephone 2 connected to the destination exchange 1 (B-1). Next, the originating exchange 1
Then, its own version number is set to the outgoing version number in the fixed header part of the control packet, and a SETUP (call setting request) packet is issued to the destination exchange device 1 (B-
2). Destination exchange device 1 that has received the SETUP packet
Then, the self version number is compared with the originating version number of the fixed header part of the control packet (B-3, S1).
1). As a result of the comparison, if the version number of the destination exchange apparatus 1 is older than the version number of the originating exchange apparatus 1, the destination exchange apparatus 1 sets its own version number to the destination version number of the fixed header part of the control packet and , A version mismatch is set in the reason information, a DISC (disconnection) packet is issued to the originating switching apparatus 1, and the call connection is rejected (B
-4, S14). Next, upon receiving the DISC packet whose reason information does not match the version, the originating switching apparatus 1 sets the parameter information of the packet along the destination version number of the fixed header part of the control packet, and sets the packet.
The UP packet is retransmitted (B-5, S21). SET
Upon receiving the UP packet, the destination exchange device 1 compares its own version number with the originating version number of the fixed header part of the control packet (B-6, S11). in this case,
Since the version number of the calling-side switching device 1 and the version number of the called-side switching device 1 are equal, the called-side switching device 1
To notify that SETUP has been accepted, call
A _PROC (call setting acceptance) packet is issued to the originating exchange 1 (B-6, S15). Next, the destination exchange device 1 places the telephone 2 in the calling state, and then issues an ALERT (calling notification) packet to the calling exchange device 1 (B-7,
S13). After the telephone 2 responds, the destination exchange device 1 issues a CONN (response notification) packet to the originating exchange device 1 (B-8). Next, in the calling-side switching device 1, C
An ONN_ACK (response acceptance) packet is issued to the exchange device 1 on the receiving side to start a call (B-9). CONN_
Destination exchange device 1 that has received an ACK (response acceptance) packet
Then, a call is started (B-10).

(3) Effect of the Embodiment As described above, when the version number of the originating exchange is older than the version number of the destination exchange, the destination exchange sets the parameter information of the packet from the originating exchange. Is interpreted according to the version of the originating exchange, and if the version number of the originating exchange is newer than the version number of the destination exchange, the originating exchange sets the parameter information of the packet from the destination exchange. Is interpreted in accordance with the version of the destination-side switching device, so that a call connection process can be performed between switching devices having different versions of software. Also, regarding the contents of the version upgrade, even when the call connection sequence itself is changed, it is possible for the destination exchange to continue the subsequent procedure in conformity with the version of the originating exchange.

[0020]

As described above, according to the present invention, in a call connection method between exchanges having different versions of software, version information of own software is notified between exchanges to be set up for call. By comparing the old and new versions of the software, and by making a call connection based on the control information corresponding to the old version of the software, the exchange device can recognize the version number of the communication partner software between the exchanges. Communication can be performed between exchanges having software. Also, even when a network is configured between a large number of switching devices, it is not necessary to upgrade the software of all switching devices in the network at the same time, and it is possible to upgrade the software for each switching device. Thus, the normality of the communication can be assured even in the process until the software version upgrade of all the switching devices in the network is completed, and the maintainability of the network is improved.

[Brief description of the drawings]

FIG. 1 is a call connection sequence when an outgoing exchange apparatus of the embodiment has an old version of software.

FIG. 2 is a flowchart of an operation of the destination exchange device of the embodiment.

FIG. 3 is a call connection sequence when the software of the calling side exchange device of the embodiment is a new version.

FIG. 4 is a flowchart of an operation of the calling-side switching device of the embodiment.

FIG. 5 is a block diagram illustrating a configuration of a switching device according to the embodiment.

FIG. 6 is a format of a control packet according to the embodiment.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Switching apparatus, 2 ... Analog telephone, 3 ... IP network, 4 ... Router, 11 ... Basic module, 12 ... IP
Network access module, 13 maintenance console, 111, 121 CPU, 112 hard disk, 113 analog subscriber interface unit, 114
... Voice FAX control unit, 115 ... Fax modem unit, 11
6, 123 ... LAN interface section, 117, 124
... a serial interface unit, 122 ... a voice control unit.

Claims (3)

[Claims] 1. A method of connecting a call between exchanges having different versions of software, wherein said exchanges to be set up are notified of the version information of their own software by switching the version of said software. A call connection method, comprising comparing a new version with an old version and performing a call connection based on control information corresponding to an old version of software. 2. When the switching devices receive version information newer than the own software version, the switching device notifies the switching device of the call connection target of the own software version. Item 2. The call connection method according to Item 1. 3. The call connection method according to claim 1, wherein the version information is set in an outgoing version number of a fixed header portion of a control packet and notified.