KR102510177B1 - Method and system for setting extension number of session initiation protocol terminal - Google Patents

Abstract

A method and system for setting an extension number of a Session Initiation Protocol (SIP) terminal may be disclosed. A method according to an embodiment includes, in a seat reservation terminal, requesting user information about a user based on login information associated with a user of a SIP terminal; In the seat reservation terminal, receiving user information from the management server; Requesting, at the seat reservation terminal, connection of the SIP terminal to a PBX (Private Branch eXchange) cloud device based on user information; and allowing access of the SIP terminal based on user information according to a connection request in the PBX cloud device.

Description

Method and system for setting extension number of SIP terminal {METHOD AND SYSTEM FOR SETTING EXTENSION NUMBER OF SESSION INITIATION PROTOCOL TERMINAL}

The present disclosure relates to a method and system for automatically setting an extension number of a Session Initiation Protocol (SIP) terminal.

In general, a private branch exchange (PBX) is a miniaturized switchboard of a telephone office, and is mainly used to establish an internal telephone network in a general company using a plurality of telephones or communication terminals. As for such a PBX, a line network (PSTN)-based private exchange was common, but as the Internet became active, a private exchange (eg, IP-PBX) based on an IP network, which is a packet network, was introduced. An IP-capable PBX provides a multimedia service, for example, a VoIP (Voice over Internet Protocol) service such as voice and video calls, through an IP network using H323 or SIP (Session Initiation Protocol).

A PBX refers to an exchange that provides various services such as call transfer, call waiting, three-way call, and call forwarding services by making the area of a company or school into one area. A telephone, facsimile, computer, etc. is connected. A PBX supports multiple telephone exchanges in one room or building. In addition, a PBX can control communication between terminals, computers, and other information processing devices by connecting to a private exchange in a company or other region. A local area network can be used using a general telephone line without additional installation of a local area network line. In addition, the PBX is connected to the trunk line switchboard and plays the same role as a terminal, and is used internally as an exchange in the PBX network. PBX can solve the inconvenience of facility such as extension of current line and inconvenience of movement.

Meanwhile, in order for the SIP terminal to access the PBX cloud device, the procedure shown in FIG. 1 may be performed. Referring to FIG. 1 , the PBX cloud device 110 sets a user ID, an authentication ID, and an authentication password required for generating a number for a SIP extension number and authenticating access (S102). The SIP terminal 120 transmits a registration request message to the PBX cloud device 110 using the user ID, authentication ID, and authentication password set in the PBX cloud device 110 (S104). The PBX cloud device 110 checks whether the user ID, authentication ID, and authentication password of the request message from the SIP terminal 120 are valid, and then allows the SIP terminal 120 to access (S106). In this way, the SIP terminal can access the PBX cloud device using a user ID, authentication ID, and authentication password set in advance.

When the SIP terminal uses a fixed extension number, the SIP terminal can access the PBX cloud device using a preset user ID, authentication ID, and authentication password. However, in order for the SIP terminal to access the PBX cloud device using a different extension number, there is a problem in that the user ID, authentication ID, and authentication password for the other extension number must be reset for the SIP terminal.

For example, as one of the office operation methods recently introduced by many businesses for efficient use of office space, a number of desks that all users can use in common are set up, and users can freely occupy any desk when they go to work. In a space sharing environment where a user wants to use a desk phone (SIP terminal) of a desk that arbitrarily occupies an extension number assigned to the user, the user ID, authentication ID, and authentication password set in the extension number assigned to the user are entered every time the desk is occupied. There is a problem in that the user does not use his/her extension number or uses the user's portable terminal because of the inconvenience of newly registering the desk phone (SIP terminal) assigned to the desk.

The present disclosure can provide a system and method for enabling use of a SIP terminal by automatically setting an extension number of a SIP terminal in a PBX cloud device using the SIP terminal.

According to an embodiment of the present disclosure, a method of setting an extension number of a Session Initiation Protocol (SIP) terminal may be disclosed. A method according to an embodiment includes, in a seat reservation terminal, requesting user information about a user based on login information associated with a user of a SIP terminal; In a seat reservation terminal, receiving user information from a management server that manages a plurality of user information; Requesting, at the seat reservation terminal, connection of the SIP terminal to a PBX (Private Branch eXchange) cloud device based on user information; and allowing access of the SIP terminal based on user information according to a connection request in the PBX cloud device.

In one embodiment, the user information may include the extension number and MAC address of the SIP terminal.

In one embodiment, the step of permitting access of the SIP terminal in response to the request of the seat reservation terminal includes checking user information and sending a first request message for requesting refresh of provisioning data corresponding to the user information. Transmitting to a SIP terminal; Receiving a second request message requesting provisioning data from the SIP terminal; Transmitting provisioning data corresponding to user information to the SIP terminal based on the second request message; Receiving a third request message requesting access of the SIP terminal from the SIP terminal; and allowing access of the SIP terminal based on the third request message.

In one embodiment, provisioning data may include a user ID, an authentication ID, and an authentication password.

In one embodiment, the user ID, authentication ID and authentication password may be encrypted.

According to another embodiment of the present disclosure, a system for setting an extension number of a SIP terminal may be disclosed. The system according to an embodiment is connected to a management server that manages a plurality of user information, based on login information associated with a user of a SIP terminal, requests user information about a user to the management server to receive user information, A seat reservation terminal requesting connection of the SIP terminal based on user information; and a PBX cloud device connected to the seat reservation terminal and the SIP terminal and permitting access of the SIP terminal based on user information according to a connection request from the seat reservation terminal.

In one embodiment, the user information may include the extension number and MAC address of the SIP terminal.

In one embodiment, the PBX cloud device checks user information, transmits a first request message corresponding to a request to refresh provisioning data corresponding to the user information to the SIP terminal, and sends a request message corresponding to the provisioning data request from the SIP terminal. Receives a second request message, transmits provisioning data corresponding to user information to the SIP terminal based on the second request message, receives a third request message requesting access of the SIP terminal from the SIP terminal, and receives the third request Based on the message, access of the SIP terminal may be allowed.

In one embodiment, provisioning data may include a user ID, an authentication ID, and an authentication password.

In one embodiment, the user ID, authentication ID and authentication password may be encrypted.

According to various embodiments of the present disclosure, an extension number of a SIP terminal may be automatically set in a PBX cloud device using the SIP terminal. Therefore, by automatically setting the extension number assigned to the user to the SIP terminal commonly used by a plurality of users so that the SIP terminal can be used, work can be done with the extension number assigned to the user under a flexible working environment such as a space share environment. environment can be created.

1 is a flowchart illustrating a method of setting an extension number of a Session Initiation Protocol (SIP) terminal.
2 is a block diagram schematically showing the configuration of an extension number setting system according to an embodiment of the present disclosure.
3 is a flowchart illustrating a method of setting an extension number of a SIP terminal according to an embodiment of the present disclosure.
4 is a flowchart illustrating a method for allowing access of a SIP terminal according to an embodiment of the present disclosure.

Embodiments of the present disclosure are illustrated for the purpose of explaining the technical idea of the present disclosure. The scope of rights according to the present disclosure is not limited to the specific description of the embodiments or these embodiments presented below.

All technical terms and scientific terms used in this disclosure have meanings commonly understood by those of ordinary skill in the art to which this disclosure belongs, unless otherwise defined. All terms used in this disclosure are selected for the purpose of more clearly describing the disclosure and are not selected to limit the scope of rights according to the disclosure.

Expressions such as "comprising", "including", "having", etc. used in this disclosure are open-ended terms that imply the possibility of including other embodiments, unless otherwise stated in the phrase or sentence in which the expression is included. (open-ended terms).

Expressions in the singular form described in this disclosure may include plural meanings unless otherwise stated, and this applies equally to expressions in the singular form described in the claims.

Expressions such as "first" and "second" used in the present disclosure are used to distinguish a plurality of elements from each other, and do not limit the order or importance of the elements.

The term "unit" used in the present disclosure means software or a hardware component such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" is not limited to hardware and software. A “unit” may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Thus, as an example, "unit" refers to components such as software components, object-oriented software components, class components and task components, processors, functions, properties, procedures, subroutines, It includes segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays and variables. Functions provided within components and “units” may be combined into fewer components and “units” or further separated into additional components and “units”.

As used in this disclosure, the expression "based on" is used to describe one or more factors that affect the act or operation of a decision, judgment, described in a phrase or sentence in which the expression is included, which expression It does not preclude additional factors that may affect the decision, the act of judgment, or the action.

In this disclosure, when an element is referred to as being “connected” or “connected” to another element, that element is directly connectable or connectable to the other element, or a new or different configuration. It should be understood that it can be connected or connected via an element.

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding elements are given the same reference numerals. In addition, in the description of the following embodiments, overlapping descriptions of the same or corresponding components may be omitted. However, omission of a description of a component does not intend that such a component is not included in an embodiment.

2 is a block diagram schematically showing the configuration of an extension number setting system according to an embodiment of the present disclosure. Referring to FIG. 2 , the extension number setting system 200 may include a seat reservation terminal 210 , a management server 220 , a PBX cloud device 230 and a SIP terminal 240 .

The seat reservation terminal 210 may be connected to the management server 220 and a PBX (Private Branch eXchange) cloud device. The seat reservation terminal 210 may receive login information from a user and request user information corresponding to the received login information from the management server 220 . In one embodiment, the login information is identification information for identifying the user of the SIP terminal 240 (hereinafter referred to as user identification information) and identification information for identifying the SIP terminal 240 (hereinafter referred to as SIP terminal identification information). referred to as) may be included. Also, the seat reservation terminal 210 may request connection of the SIP terminal 240 to the PBX cloud device 230 based on user information provided from the management server 220 .

In one embodiment, the seat reservation terminal 210 may include at least one of a fixed terminal or a mobile terminal capable of implementing a communication environment. For example, the fixed terminal includes a desktop PC, and the mobile terminal may include a smart phone, a hand-held PC, a tablet PC, a laptop computer, a PDA, a portable Internet terminal, and the like.

The management server 220 is connected to the seat reservation terminal 210 and may manage user identification information and user information corresponding to a plurality of users. For example, the user information may include an extension number to be used by the SIP terminal 240 (that is, assigned to a user of the SIP terminal 240) and a Media Access Control (MAC) address of the SIP terminal 240. In one embodiment, the management server 220 may include a storage unit (not shown) for storing user information corresponding to user identification information corresponding to each of a plurality of users. In addition, the management server 220 may transmit user information stored in the storage unit to the seat reservation terminal 210 in response to a request from the seat reservation terminal 210 .

The PBX cloud device 230 may be connected to the seat reservation terminal 210 and the SIP terminal 240 . The PBX cloud device 230 may generate a number for a SIP extension number and set a user ID, an authentication ID, and an authentication password required for access authentication. In addition, the PBX cloud device 230 may receive a connection request of the SIP terminal 240 from the seat reservation terminal 210 and allow access of the SIP terminal 240 in response to the received connection request.

In one embodiment, the PBX cloud device 230 may receive a message requesting connection of the SIP terminal 240 (hereinafter referred to as a SIP terminal connection request message) from the seat reservation terminal 210 . For example, the SIP terminal connection request message may include the extension number and MAC address of the SIP terminal 240 .

In one embodiment, the PBX cloud device 230 sends a request message requesting refresh of provisioning data (hereinafter, referred to as a first request message) based on the SIP terminal connection request message to the SIP terminal. (240). In one embodiment, provisioning data may include a user ID, an authentication ID, and an authentication password.

In one embodiment, the PBX cloud device 230 may transmit provisioning data to the SIP terminal 240 in response to a request for provisioning data from the SIP terminal 240 . For example, the user ID, authentication ID, and authentication password of the provisioning data may be encrypted and transmitted to the SIP terminal 240 .

In one embodiment, the PBX cloud device 230 may receive a registration request from the SIP terminal 240 and allow access of the SIP terminal 240 in response to the received registration request.

The SIP terminal 240 may be connected to the PBX cloud device 230 . The SIP terminal 240 receives a first request message from the PBX cloud device 230, and sends a request message requesting provisioning data (hereinafter, referred to as a second request message) based on the first request message to the PBX cloud device ( 230). In addition, the SIP terminal 240 receives provisioning data corresponding to the second request message from the PBX cloud device 230, and based on the received provisioning data, a message requesting registration of the SIP terminal 240 (hereinafter, referred to as a third request message) may be transmitted to the PBX terminal 230. In one embodiment, the third request message may include a user ID, an authentication ID, and an authentication password. For example, the user ID, authentication ID, and authentication password may be encrypted and transmitted to the PBX cloud device 230 .

In one embodiment, the SIP terminal 240 may periodically transmit a third request message to the PBX cloud device 230 in order to maintain the registration state even after the normal registration procedure is completed.

Although process steps, method steps, algorithms, etc. are described in a sequential order in the flowcharts shown in this disclosure, such processes, methods and algorithms may be configured to operate in any suitable order. In other words, the steps of the processes, methods, and algorithms described in various embodiments of this disclosure do not have to be performed in the order described in this disclosure. Also, although some steps are described as being performed asynchronously, in other embodiments some of these steps may be performed concurrently. Further, illustration of a process by depiction in a drawing does not mean that the illustrated process is exclusive of other changes and modifications thereto, and that any of the illustrated process or steps thereof may be one of various embodiments of the present disclosure. It is not meant to be essential to one or more, and it does not imply that the illustrated process is preferred.

3 is a flowchart illustrating a method of automatically setting an extension number of a SIP terminal according to an embodiment of the present disclosure. Referring to FIG. 3 , in step S302 , the seat reservation terminal 210 may request user information from the management server 220 based on login information from the user. In one embodiment, when the user's login information is received, the seat reservation terminal 210 may request user information from the management server 220 based on user identification information and SIP terminal identification information of the received login information.

In step S304, the seat reservation terminal 210 may receive user information from the management server 220. In one embodiment, the user information may include a SIP terminal extension number and a SIP terminal MAC address corresponding to user identification information and SIP terminal identification information of login information.

In step S306, the seat reservation terminal 210 may transmit a SIP terminal connection request message requesting connection of the SIP terminal 240 to the PBX cloud device 230 based on the received user information. In one embodiment, the SIP terminal connection request message may include user information, that is, the extension number of the SIP terminal and the MAC address of the SIP terminal.

In step S308, the PBX cloud device 230 may allow the SIP terminal 240 to access based on the SIP terminal connection request message from the seat reservation terminal 210. In one embodiment, the PBX cloud device 230 sends a SIP terminal 240 based on a SIP terminal connection request message (SIP terminal extension number and SIP terminal MAC address) and provisioning data (user ID, authentication ID, and authentication password). ) can be accessed.

4 is a flowchart illustrating a method for allowing access of a SIP terminal according to an embodiment of the present disclosure. Referring to FIG. 4 , in step S402 , the PBX cloud device 230 may receive a SIP terminal connection request message from the seat reservation terminal 210 and check user information from the received SIP terminal connection request message.

In step S404, the PBX cloud device 230 may transmit a first request message requesting a refresh of provisioning data to the SIP terminal 240 based on the SIP terminal connection request message. In one embodiment, the provisioning data is refreshed in a state in which the SIP terminal 240 cannot recognize the user's login change due to reasons such as power not being connected to the SIP terminal 240 or network failure when the user logs in. It may be performed in some cases, but is not necessarily limited thereto.

In step S406, the PBX cloud device 230 may receive a second request message requesting provisioning data from the SIP terminal 240. In one embodiment, the user ID, authentication ID, and authentication password of the second request message may be encrypted.

In step S408, the PBX cloud device 230 may transmit provisioning data to the SIP terminal 240 based on the second request message. In one embodiment, the user ID, authentication ID, and authentication password of provisioning data may be encrypted.

In step S410, the PBX cloud device 230 may receive a third request message requesting registration of the SIP terminal 240 from the SIP terminal 240. In one embodiment, the user ID, authentication ID, and authentication password of the third request message may be encrypted.

In step S412, the PBX cloud device 230 may permit access of the SIP terminal 240 based on the third request message. In one embodiment, the PBX cloud device 230 may automatically set the extension number of the SIP terminal 240 based on the third request message and allow the SIP terminal 240 to access.

Although the above method has been described through specific embodiments, it is also possible to implement the above method as computer readable code on a computer readable recording medium. A computer-readable recording medium includes all types of recording devices in which data that can be read by a computer system is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices. In addition, the computer-readable recording medium is distributed in computer systems connected through a network, so that computer-readable codes can be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing the above embodiments can be easily inferred by programmers in the art to which the present disclosure belongs.

Although the technical spirit of the present disclosure has been described by examples shown in some embodiments and the accompanying drawings, those skilled in the art can understand the technical spirit and scope of the present disclosure to which the present disclosure belongs. It will be appreciated that various substitutions, modifications and alterations may be made within the range. Moreover, such substitutions, modifications and alterations are intended to fall within the scope of the appended claims.

110, 230: PBX cloud device 120, 240: SIP terminal
200: extension number setting system 210: seat reservation terminal
220: management server

Claims (10)

As a method of setting an extension number of a SIP (Session Initiation Protocol) terminal,
Requesting user information for the user, at the seat reservation terminal, based on login information associated with the user of the SIP terminal;
In the seat reservation terminal, receiving the user information from a management server that manages a plurality of user information;
Requesting, in the seat reservation terminal, connection of the SIP terminal to a PBX (Private Branch eXchange) cloud device based on the user information; and
Allowing, in the PBX cloud device, access of the SIP terminal based on the user information according to the connection request
including,
The step of allowing the access of the SIP terminal
checking the user information and transmitting a first request message requesting a refresh of provisioning data corresponding to the user information to the SIP terminal;
Receiving a second request message requesting provisioning data corresponding to the user information from the SIP terminal;
Transmitting provisioning data corresponding to the user information to the SIP terminal based on the second request message;
Receiving a third request message requesting access of the SIP terminal from the SIP terminal; and
Allowing access of the SIP terminal based on the third request message
How to include. The method of claim 1, wherein the user information includes an extension number and a MAC address of the SIP terminal. delete The method of claim 1 , wherein the provisioning data includes a user ID, an authentication ID, and an authentication password. The method of claim 4, wherein the user ID, the authentication ID, and the authentication password are encrypted. As a system for setting the extension number of the SIP terminal,
It is connected to a management server that manages a plurality of user information, and based on login information associated with the user of the SIP terminal, requests user information about the user to the management server to receive the user information, and to receive the user information Seat reservation terminal requesting connection of the SIP terminal based on; and
A PBX cloud device that is connected to the seat reservation terminal and the SIP terminal and allows access of the SIP terminal based on the user information according to a connection request from the seat reservation terminal.
including,
The PBX cloud device,
Checking the user information and transmitting a first request message corresponding to a refresh request of provisioning data corresponding to the user information to the SIP terminal;
Receiving a second request message requesting provisioning data corresponding to the user information from the SIP terminal;
Transmitting provisioning data corresponding to the user information to the SIP terminal based on the second request message;
Receiving a third request message requesting access of the SIP terminal from the SIP terminal;
A system allowing access of the SIP terminal based on the third request message. The system of claim 6, wherein the user information includes an extension number and a MAC address of the SIP terminal. delete 7. The system of claim 6, wherein the provisioning data includes a user ID, an authentication ID, and an authentication password. The system according to claim 9, wherein the user ID, the authentication ID, and the authentication password are encrypted.

Images