CN1415159A - Flexible communications system - Google Patents
Flexible communications system Download PDFInfo
- Publication number
- CN1415159A CN1415159A CN00801439A CN00801439A CN1415159A CN 1415159 A CN1415159 A CN 1415159A CN 00801439 A CN00801439 A CN 00801439A CN 00801439 A CN00801439 A CN 00801439A CN 1415159 A CN1415159 A CN 1415159A
- Authority
- CN
- China
- Prior art keywords
- client
- server
- node
- gateway
- communication
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1033—Signalling gateways
- H04L65/104—Signalling gateways in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1023—Media gateways
- H04L65/103—Media gateways in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1106—Call signalling protocols; H.323 and related
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1285—Details of finding and selecting a gateway for a particular call
Abstract
A system that supports audio, video, data, and fax communications between a source personal computer and an audio communications device, such as a telephone or a destination personal computer. The system provides for communications first with an entry node, which selects an intermediate server. The selected intermediate server selects an ITSP gateway, for example, which provides access to the audio communications device. The selected intermediate server initiates voice or video communications using for example, the H.323 standard, with the ITSP gateway. The selected intermediate server then informs the source personal computer to communicate directly with the ITSP gateway. Thereby, the system scaleably supports voice or video communications in a ''thin-client'' environment.
Description
Background
1. invention field
The present invention relates to a kind of method and apparatus be used to video and voice communication are provided.
2. correlation technique discussion
VoIP (voice on the Internet protocol (IP)) has described one group of equipment, be used for to use public internet or private intranet or network rather than use public switch telephone network (PSTN) based on the custom circuit agreement, the transmission of Managing speech information. The major advantage of VoIP and Internet Protocol telephone is that it has been avoided by the business telephone service provider such as MCITMOr AT﹠TTMThe expense of collecting (toll).
H.323 VoIP derives from ITU-T, H.323 is a kind of standard that is proposed by VoIP forum. H.323 standard definition use IP on public internet and in-house network to send the form of audio frequency, video, data or fax. Except IP, VoIP also uses known real-time protocol (RTP) (RTP) to guarantee that communication is provided in real time, has avoided the obvious time-out in voice or the video communication. Use public internet, currently be difficult to control the stand-by period. By enterprise or by the dedicated network that internet telephone service provider (ITSP) manages preferably service can be arranged.
Support the routine techniques of VoIP communication huge software need to be downloaded in user's the personal computer. For the communication link of low speed, the user need to download software for a long time. For the personal computer with low memory storage capacity such as personal digital assistant (PDA), consider the capacity of required software, VoIP communication may not be practicable.
Invention is summed up
According to embodiments of the invention, a kind of system is provided, allow at least personal computer and such as the voice communication between the audio communication device of phone. Also can support video, data and facsimile.
In one embodiment of the invention, the communication between personal computer and the audio communication device is supported by at least one intermediate equipment. For the communication between personal computer and the audio communication device, personal computer is communicated by letter with an Ingress node, and this node is selected an intermediate server. Personal computer is then communicated by letter with selecteed intermediate server, and this intermediate server is selected the ITSP gateway. Then, personal computer and ITSP gateway communication. The ITSP gateway is provided to the access of PSTN, and PSTN is provided to the access of purpose audio communication device. Personal computer is communicated by letter with the purpose audio communication device thus.
The advantage of this embodiment is that the software that downloads to personal computer is less than the situation that personal computer must be selected an ITSP and communicate by letter with described ITSP foundation.
Another advantage of this embodiment is to support that the architecture of VoIP communication is telescopic, thereby can carry out a large amount of VoIP communication.
Another advantage of this embodiment is that it can use the H.323 standard of many types to be used for VoIP communication.
In one embodiment, for the communication of client computer to remote client, the communication between client computer and the remote client is led directly to. In this embodiment, client computer is communicated by letter with remote client does not need to support H.323 client computer. So avoided a large amount of software storages.
By detailed description with reference to the accompanying drawings, will more fully understand various embodiments of the invention.
The accompanying drawing summary
Fig. 1 simply shows one embodiment of the present of invention, and one of them system is used to provide the communication between any client computer and any purpose audio communication device.
Fig. 2 shows according to the embodiment of the invention, concerns example between the ITSP gateway of ITSP network and the system.
Fig. 3 shows the more details drawing according to the system of the embodiment of the invention;
Fig. 4 shows the process chart according to the embodiment of the invention;
Fig. 5 simply shows according to the embodiment of the invention during the processing of Fig. 4, the message of communicating by letter between client computer, Ingress node, selected intermediate server and the selected ITSP gateway;
Fig. 6 shows the appropriate action flow chart according to the processing of embodiment of the invention Fig. 4;
Fig. 7 shows the sample site measure that uses in one embodiment according to the embodiment of the invention;
Fig. 8 shows the appropriate action flow chart according to the processing of embodiment of the invention Fig. 4;
Fig. 9 shows the appropriate action flow chart according to the processing of embodiment of the invention Fig. 4;
Figure 10 simply shows according to the relation between embodiment of the invention multi-client and the database.
The use of attention same numeral in different figure represents same or analogous parts.
Describe in detail
The data of quoting
Following table provides title and the data relevant with these titles. Here the data of quoting refers to the whole of them.
Title | Data |
UDP/IP | Internet Engineering task team (IETF) Request for Comment (Request for Comments) 768 |
TCP/IP | " TCP/IP and related protocol; about the McGraw-Hill series of compunication " third edition, Ulysses D.Black, mcgraw-hill, inc, 1997, ISBN:0079132820, " the TCP/IP example first volume: agreement ", W.Richard Stevens, Addison-Wesley, 1994. |
H.323 with the correlator agreement, such as RTP | " digital subscriber signaling system No.1 Internet-be used for isdn user-network interface layer 3 explanation of basic call control " (Q.931 ITU-T advise) and " circuit of non-telephone signal transmits "-for the control protocol (H.245 ITU-T advises) of multimedia communication |
Client computer is to the purpose communication equipment
General introduction
Fig. 1 has schematically illustrated one embodiment of the present of invention, and wherein system 100 is used to provide any client computer 105-1 to 105-N and any purpose audio communication device 150-1 to 150-Z such as the voice communication between the routine call. In this embodiment, any client computer 105-1 to 105-N is by public or private network such as internet access system 100. Below, if not otherwise specified, any one client computer 105-1 to 105-N of client computer 105 fingers. Below, if not otherwise specified, any one purpose audio communication device 150-1 to 150-Z of purpose audio communication device 150 fingers.
Fig. 2 shows the example that concerns of the ITSP gateway 145-1 to 145-N of an ITSP network 140 and system 100. ITSP network 140 is dedicated networks, and it generally includes a plurality of ITSP gateway 145-1 to 145-N. Usually each ITSP gateway has unique address such as the IP address. For example, the ITSP network is by IDT and the Qwest of New JerseyTMProvide. Each gateway is coupled at least one public switch telephone network (PSTN) 148. PSTN is provided to telephone unit such as the wired or wireless access of any one purpose audio communication device 150-1 to 150-Z. The back, if not otherwise specified, any one ITSP gateway 145-1 to 145-N of ITSP gateway 145 fingers.
Usually, H.323 each ITSP gateway uses agreement independently to realize supporting communication.
Interface between client computer 105 and the system 100
The example embodiment of client computer 105 is conventional personal computers (PC). A suitable PC comprises: input/output adapter, CPU (for example, microprocessor) and memory. The PC that is fit to for example is IBM PS/2 personal computer, Apple computer, based on the work station of UNIX or such as 3comTMThe PDA of use Palm VII. PC further comprises such as the display of the computer monitor of super VGA class or other visual display device.
The pc user of accessing Internet or dedicated network can use web browser such as Microsoft Internet ExplorerTMOr Netscape NaviagtorTMHave access to the webpage of graphic contents. In order to specify a website, user input shows the two resource locator (URL) of requested server and particular data (" webpage "). URL can specify a HTTP (HTTP) or another host-host protocol for the communication between server and the browser. Use the internet, URL is sent to the master server of the storage information corresponding with URL.
In one embodiment, client computer 105 is used the website access subsystem 100 that is stored in the network 110. As the conventional Website server supervisor of the part of network 110 website by client computer 105 accesses. Suitable Website server for example is Sun MicrosystemTMThe SPARC server that can provide, and use the NT4.0 of Microsoft, IIS or UNIX operating system.
The example of website will be described in conjunction with Fig. 7 in the back. The Website server support provides the request of feature from the user's by the website.
Fig. 3 provides the more detailed figure of system 100. System 100 comprises Ingress node 120, and this Ingress node uses public or private network such as internet to communicate by letter with at least one intermediate server 130-1 to 130-X. Each intermediate server 130-1 to 130-X can use public or private network such as internet to communicate by letter with each ITSP gateway 145-1 to 145-N. Certainly, additional Ingress node 120 can be used for supporting more communication session.
The Ingress node 120 of Fig. 3 monitors the action of intermediate server, and selects an intermediate server support from the voice communication of a separate customer machine 105 such as client computer 105-1. Example embodiment and the Website server of Ingress node 120 are similar. Select an ITSP gateway by managing successively of selecting of Ingress node 120 from the intermediate server of the voice communication of client computer 105, the ITSP gateway is provided to the access of PSTN, and PSTN provides and the communicating by letter of purpose audio communication device 150. Each intermediate server 130-1 to 130-X is similar to Website server. The back, if not otherwise specified, any one intermediate server 130-1 to 130-X of intermediate server 130 fingers.
Database server
In one embodiment, a separate database server (not shown) uses " log database " to store each user's information, and processes the information request about client computer 105 or specific user. Suitable database server is a General Server. The communication of database server and the example of communicating by letter from database server are provided in appendix B.
Software is realized general introduction
Appendix A has been described the code segment of being carried out by the client computer 105 among this embodiment, Ingress node server 120 and intermediate server 130-1 to 130-X as part of the present disclosure. Code segment is used for the process 400 of execution graph 4, communicates by letter between client computer 105 and purpose audio communication device.
In the action 405 of process 400, client computer 105 contact (contact) Ingress nodes 120 are to bring into use system 100. Provide with reference to Fig. 6 and to have moved 405 detailed description.
In action 410, Ingress node 120 is selected an intermediate server 130 that is fit to. Then Ingress node is the selected intermediate servers 130 of client computer 105 signs. The detailed description of action 410 is provided with reference to Fig. 8.
In action 415, the communication channel of selected intermediate server 130 selections and foundation and ITSP gateway 145, and be the selected ITSP gateways of client computer 105 signs. Then, client computer 105 and 145 direct communications of ITSP gateway. As previously described, ITSP gateway 145 is communicated by letter with the PSTN that communicates by letter with purpose audio communication device 150 is provided. Use ITSP gateway 145, client computer 105 is communicated by letter with purpose audio communication device 150. The detailed description of action 415 is provided with reference to Fig. 9.
In action 420, client computer 105 finishes the audio frequency communication session. The below provides the detailed description of action 420.
The advantage of this embodiment is that the communication between client computer 105 and the purpose audio communication device 150 is segmented, so that use Ingress node 120 and intermediate server 130 to carry out selection and the foundation of the communication channel between client computer 105 and the ITSP gateway 145. Thereby the software that downloads to client computer 105 is less than client computer must be selected and the situation about being connected (said " thin client computer " environment) of foundation with the ITSP gateway.
Message examples
Fig. 5 has schematically illustrated during the exemplary operations of the action 405 to 420 of process 400, the message of communication between client computer 105, Ingress node 120, selected intermediate server 130 and the selected ITSP gateway 145. Appendix D provides and has been used for the description of proper protocol of message transfer and the description of other message.
Action 405
Fig. 6 provides the appropriate procedure figure of action 405 (Fig. 4). In action 610, the user uses the figure web browser to provide resource locator (URL) such as Netscape omniselector or Microsoft's browser, or uses the hyperlink access one functional website that comprises according to the embodiment of the invention. For example express with HTML the website, and comprise potential several webpages, and each uses the link of HTML code.
For example, Fig. 7 has described a sample site measure 700. Website 700 comprises: figure touch panel 702, and can input character by this touch panel; Field (field) can be at this input character; Title " address book " 706 for example accesses a phone directory; With 708 the conventional logotype in the position.
In another embodiment, website 700 is provided to user's access of Email, voice mail message and fax. The website that is provided to user's access of Email, voice mail message and fax is known, for example referring to Hotmail.comTM,Excite.com
TM,jfax.com
TM So in this embodiment, website 700 and system 100 allow user voice voice responsive mail message, Email or fax.
In action 610, after appointed website is connected, Website server is uploaded (upload) executable file to the PC of client computer 105, and described executable file consists of " strtp.dll ", " stnet.dll ", " vscp.dll " and " tsd2.dll ". These files and these*.dll be listed in the appendix A.
With reference to Fig. 6, in action 620, the user in the website 700 field 704 for example input a purpose telephone number.
In one embodiment, when the title " address book " 706 of website 700 is selected, phone directory is offered the user. In this phone directory, select a telephone number startup to the call of purpose audio communication device 150.
In one embodiment, phone directory in database, will be described the order to database with aforesaid database server stores in more detail in appendix B.
In the position 708, show conventional logotype advertisement. For example use the available service of " Doubleclick ofNew York, New York " can arrange advertisement. Advertisement can be followed user's interest. By the advertisement for the specific user is provided, can make the advertising income maximization. In this embodiment, advertising income can be used for the communication cost of Zhi Fuyu purpose audio communication device 150.
Certainly, by being engaged in the logotype advertisement, the user can buy product or the service of advertising.
In action 630, client computer for example uses ICP/IP protocol to be connected to Ingress node 120. Action 630 is the message of " TCP connects (TCP Connect) " 502 (Fig. 5) corresponding to title. The IP address of Ingress node 120 and port numbers are preconfigured in the file of downloading in the action 610. In action 630, client computer to major general's purpose telephone number, ID, password and session id passes to Ingress node 120. ID identifying user and sign such as that in appendix B, describe and user-dependent message in database server stores. Password is used to determine whether to allow the user profile to from database to access by Website server. Session id is used for following the tracks of the state of voice communication.
In action 640, Ingress node 120 for example uses ICP/IP protocol that the contact details of selected intermediate server 130 are provided to client computer 105. With reference to Fig. 5, action 640 is the message of " VEGA server (VEGA Server) " 504 corresponding to table title. In this embodiment, contact details comprise IP address and the port numbers of selected intermediate server. In this embodiment, the IP address is 4 byte Ipv4 addresses (IP version 4) of selected intermediate server 130, and port numbers is that selected server monitoring is in the future from 2 byte port numbers of the communication of client computer 105.
In this embodiment, Ingress node 120 keeps the table of potential intermediate server 130 and the percentage that intermediate server 130 is remained valid and communicated by letter. Appendix C provides the description of suitable technology as the part of the disclosure, thereby Ingress node 120 monitors the activity grade of intermediate servers 130. In this embodiment, Ingress node 120 select the to have minimum movable percentage intermediate server 130 of (for example, by the active session number divided by the max-session number). If all potential intermediate servers 130 are idle to a certain extent, Ingress node selects to have the intermediate server 130 of minimum correlated identities number. Can use other system of selection such as selecting at random.
Fig. 8 provides the suitable flow chart of action 410 (Fig. 4). Appendix A provides the description of the program of using in action 410.
In action 810, client computer 105 is used for example TCP/IP, utilizes IP address and the port numbers of previous appointment in action 610 to be connected to selected intermediate server 130. In the example of Fig. 5, action 810 is corresponding to (occurring for the second time) " TCP connection " 506.
In action 820, client computer 105 is for example used TCP/IP, (startup is connected with selected intermediate server 130 for clauses and subclauses 508, message Fig. 5) for " VSCP sets up (VSCP SETUP) " by for example sending title to selected intermediate server 130. Message " VSCP foundation " starts any communication between client computer 105 and the selected intermediate server 130. Following table provides the description of the field of using in message " VSCP foundation ".
Field name | Decimal system word section | Summary |
ID | ||
1 to 8 | | |
Password | ||
9 to 16 | Password string | |
Client-side medium transmission address style | 17 to 18 | The type of medium transmission address. Support IPv4, although can use other agreement. |
Client-side medium transmission address | 19 to 22 | The client-side IP address that is used for medium transmission. |
Client-side medium transmission port numbers | 23 to 24 | The client-side port numbers that is used for medium transmission. |
| 25 to 26 | The length of caller number. |
Caller number | 27 to N, wherein N is the length of called party number | Called party number length (E.164-maximum 128). |
Called party number length | N is to N+1 | Called party number length (word). |
Called party number | N+2 is to M, and wherein M is the length of called party number | Called party number (E.164-maximum 128). |
The client-side protocol type | M is to M+1 | The protocol type that MEDIA FLOW is used. Support RTP, although can use other agreement. |
The client-side media type | M+2 is to M+3 | Referring to following |
The client-side PT Payload Type | M+4 is to M+5 | Referring to following |
The maximum frame of client-side payload | M+6 is to M+7 | The heap(ed) capacity of payload |
The client-side silence detect enables | M+8 | Silence detect enables |
The elimination of client-side echo enables | M+9 | Echo elimination enables |
Field client-side media type represents the media type that is transmitted.
Media | Value |
Voice | |
0×0001 | |
| 0×0002 |
| 0×0003 |
| 0×0004 |
Field client-side PT Payload Type represent the to encode type of selected media type such as voice, video or data compression algorithm. Current, support the encoded voice payload.
PT Payload Type | Value |
Non-standard | 0×0001 |
G.711A- | 0×0002 |
G.711A- | 0×0003 |
G.711u- | 0×0004 |
G.711u- | 0×0005 |
G.722 | 0×0006 |
G.722 | 0×0007 |
G.723.1 | 0×0008 |
G.728 | 0×0009 |
G.729 | 0×000a |
G.729 | 0×000b |
IS11172 |
0× |
IS13818 | |
0×000d | |
G.729 | 0×000e |
G.729 appendix | 0×000f |
G.723.1 | 0×0010 |
The GSM | 0×0011 |
The | 0×0012 |
GSM improves | 0×0013 |
In action 830, selected intermediate server 130 determines whether to allow client computer 105 beginnings based on the communication of voice or video. Selected intermediate server 130 is carried out checking, comprises the selected intermediate server 130 of client computer 105 uses that determines whether to allow to have specific user ID and password.
If do not allow client computer 105 to use, selected intermediate server 130 sends " discharging (RELEASE) " message (not shown among Fig. 5) to client computer 105. The back will be described message " release " in detail. Do not allow the reason example of client computer 105 to comprise unknown ID, incorrect password and the telephone number of not supporting. Referring to following description to message " release ".
If allow client computer 105 to use, then in action 840, selected intermediate server 130 is selected ITSP gateway (back claims " selected ITSP gateway "). The way of example of selecting an ITSP gateway is to determine the effective route of minimum cost of purpose telephone number. Selecting another way of example of an ITSP gateway 145 is the working load balance method, thereby selects to have the ITSP gateway 145 of minimal amount active session. Load balance has advantageously reduced the impact of single ITSP gateway 145 failures. Select another way of example of ITSP gateway 145 to be based on general structure choice ITSP gateway. Selected ITSP gateway 145 is connected with PSTN 148, connects the purpose telephone number by PSTN 148. Selected ITSP gateway is by the IP address designation.
In action 850, selected intermediate server 130 is communicated by letter with selected gateway 145. The suitable utilization that is connected with selected ITSP gateway 145 is agreement H.323, and the two is known for those skilled in the art. Q.931 and H.245 in action 850, agreement is conventional, and is H.323 describing in the agreement. Referring to for example " digital subscriber signaling system No.1 Internet-be used for isdn user-network interface layer 3 explanation of basic call control " (Q.931 ITU-T advises) and " circuit of non-telephone signal transmits-be used for the control protocol (H.245 ITU-T advises) of multimedia communication ", these are in this reference that all is cited.
Because each ITSP gateway 145 can use stand-alone mode H.323, selected intermediate server 130 advantageously can be supported each stand-alone mode H.323. Do not use selected intermediate server 130, client computer 105 has to support each stand-alone mode H.323, and this support may need huge software is uploaded to client computer 105.
Fig. 9 has been shown in further detail and has moved 850 operation. In this embodiment, ICP/IP protocol is used in the communication of action 850.
In action 910, foundation is connected with specific purpose audio communication device 150. In one embodiment, action 910 further comprises action 910-1 to 910-7.
In action 910-1, selected intermediate server 130 uses by the message of " setting up (SETUP) " of the routine of protocol definition Q.931, provides purpose pstn telephone number to selected ITSP gateway 145. Q.931, action 910-1 is corresponding to 510 " setting up " of Fig. 5.
In action 910-1, selected intermediate server 130 then to client computer initiate a message " (CALLPROCEED) carried out in calling " (clauses and subclauses 512, Fig. 5). " calling is carried out " message is delivered to client computer 105, and current call request is in treatment state at present. In this embodiment, message " calling is carried out " comprises 8 byte values that identify described calling. Message " calling is carried out " comprises for example unique Call Reference Value of 8 bytes, and it identifies specific communication session. Selected intermediate server 130 keeps the state of each ongoing session.
In action 910-2, selected ITSP gateway 145 dialing purpose pstn telephone numbers. Action 910-2 is corresponding to 514 " dialing (Dial) " of Fig. 5.
In action 910-3, PSTN signals to selected ITSP gateway 145, shows that purpose audio communication device 150 notifying the purpose user that one input voice communication is arranged. Action 910-3 is corresponding to 516 " ring-back (Ringback) " of Fig. 5.
In action 910-4, selected ITSP gateway 145 uses by the routine of protocol definition " alarm (ALERT) " message Q.931, replys the notice to the purpose audio communication device by PSTN to selected intermediate server 130. Action 910-4 is corresponding to 518 " the Q.931 alarms " of Fig. 5.
In action 910-5, selected intermediate server 130 sends signal to client computer, shows the purpose user by alarm, and " Call Reference Value " described later be provided. Action 910-5 is corresponding to 520 " VSCP alarm (the VSCP ALERT) " of Fig. 5.
In action 910-6, PSTN passes on the purpose audio communication device to permit communication to selected ITSP gateway. Action 910-6 is corresponding to 522 " answering (Answer) " of Fig. 5.
In action 910-7, selected ITSP gateway 145 uses by the routine of protocol definition Q.931 and connects signal, passes on the purpose audio communication devices to permit communication to selected intermediate server 130. Connect 910-7 corresponding to 524 " Q.931 connecting (CONNECT) " of Fig. 5.
In action 920, set the communication standard between selected intermediate server 130 and the selected gateway 145. In one embodiment, action 920 comprises action 910-1 to 920-2.
In action 920-1, selected intermediate server 130 uses conventional terminal capacity set (the terminal capability set that defines in agreement H.245, TCS) message, (for example pass on the compress technique of appointments in action 820 and media type to selected ITSP gateway 145, voice, video, data or fax). Action 920-1 is corresponding to 526 " the H.245 TCS " of Fig. 5.
In action 920-2, selected ITSP gateway 145 uses the conventional TCS ACK message that defines in agreement H.245, and signaling to selected intermediate server 130 shows the TCS message that receives action 935. Action 920-2 is corresponding to 528 " the TCS ACK " of Fig. 5.
In action 930, between selected intermediate server 130 and selected ITSP gateway 145, set up correspondence. In one embodiment, action 930 comprises action 930-1 to 930-3.
In action 930-1, selected intermediate server 130 uses the conventional principal and subordinate who defines in agreement H.245 to determine (MSD) message, and it oneself is caller to selected ITSP gateway 145 signs. Action 930-1 is corresponding to 530 " the H.245 MSD " of Fig. 5.
In action 930-2, selected ITSP gateway 145 is by being sent in the conventional MSD ACK message that defines in the agreement H.245, and signaling to selected intermediate server 130 shows the MSD that receives action 945. Action 930-2 is corresponding to 532 " the H.245 MSD ACK " of Fig. 5.
In action 930-3, selected intermediate server 130 uses the conventional main MSD message that defines in agreement H.245, and signaling to selected ITSP gateway 145 shows that principal and subordinate's process finishes. Action 930-3 is corresponding to 534 " the H.245 MSD ACK " of Fig. 5.
In action 940, between selected intermediate server 130 and selected ITSP gateway 145, set up voice channel. In one embodiment, action 940 comprises action 940-1 to 940-4.
In action 940-1, selected intermediate server 130 uses the conventional open logic channel (OLC that defines in agreement H.245, open logic channel), send signal to selected ITSP gateway 145, with open voice channel from selected intermediate server 130 to selected ITSP gateway 145. Action 940-1 is corresponding to 536 " the H.245 OLC " of Fig. 5.
In action 940-2, the conventional OLC ACK that H.245 selected ITSP gateway 145 uses shows the TCS that receives action 965 to selected intermediate server 130 signallings. Action 940-2 is corresponding to 538 " the H.245 OLC ACK " of Fig. 5.
In action 940-3, the conventional open logic channel (OLC) that selected ITSP gateway 145 uses as defines in H.245 sends signal to selected intermediate server, with open voice channel from selected ITSP gateway to selected intermediate server 130. Action 940-3 is corresponding to 540 " H.245OLC " of Fig. 5.
In action 940-4, the conventional OLC ACK that selected intermediate server 130 uses as defines in H.245 shows the OLC that receives action 975 to selected ITSP gateway signalling. Action 940-4 is corresponding to 542 " the H.245 OLC ACK " of Fig. 5.
With reference to Fig. 8, in action 860, selected intermediate server 1 30 connects to the client computer notification call by sending " connection " message corresponding to 544 " the VSCP connections " of Fig. 5, and following table provides the description of " connection ".
Field name | Decimal system sequence number | ||
| 1 to 8 | Formerly provide Call Reference Value in " alarm " message. | |
Server side medium | 9 to 10 | The medium transmission address style. Ipv4 is supported, although can use other agreement. | |
Server side medium transmission address | 11 to 14 | The address of selected ITSP gateway (being the IP address in this embodiment) | |
Server side medium transmission port numbers | 15 to 16 | The port numbers of selected ITSP gateway | |
Called party number length | 17 to 18 | Called party number length | |
Called party number | 19 to N, wherein N is called party number length | Called party number (E.164-maximum 128) | |
The server side protocol type | N is to N+1 | The agreement that MEDIA FLOW is used. RTP is used, although other agreement can be used. | |
The server side media type | N+1 is to N+2 | Be similar to previously described client-side media type | |
The server side PT Payload Type | N+3 is to N+4 | Be similar to previously described client-side PT Payload Type | |
The maximum frame of server side | N+ | 5 is to N+6 | The heap(ed) capacity of payload |
The server side silence detect enables | N+7 | Silence detect enables | |
The elimination of server side echo enables | N+8 | Echo elimination enables |
Action 415
In action 415 (Fig. 4), client computer 105 for example uses Real-time Transport Protocol to communicate by letter with selected ITSP gateway 145. RTP is the separate standards agreement for coding and transmitting multimedia MEDIA FLOW known to a person of ordinary skill in the art. Action 415 546 " RTP data (RTP Data) " corresponding to Fig. 5. Certainly, except RTP, can use other agreement, such as any proprietary MEDIA FLOW agreement.
According to the RTP standard, the program of describing in appendix A " strtp.dll " provides the transmission of encoded voice. The example technique of Code And Decode voice can be used " DSP Group of Santa Clara, CA's ". In this embodiment, program " tsd2.dll " comprises the example technique of Code And Decode voice.
So, voice flow direct communication between client computer and selected ITSP gateway. This direct communication has reduced the delay of packets of voice communication. This delay causes postponing significantly in the voice communication.
In one embodiment, before the beginning voice communication, by the loudspeaker of client computer 105, can provide brief audio advertisement to the user. Audio advertisement produces income, can be used for subsidizing the cost with purpose audio communication device 105.
Action 420
In action 420 (Fig. 4), voice communication finishes. For example, when the user wished to wind up a talk, client computer 105 was sent release (Fig. 5,548) to selected intermediate server 130. Equally, when calling receiver wished to wind up a talk, selected intermediate server 130 for example used TCP/IP to send " release " to client computer 105. In this embodiment, in action 420, use " the VEGA server source file " in appendix A, described.
A way of example that finishes voice communication is as follows. Selected intermediate server 130 for example uses the H.245 ESC message that defines in standard H.245, send H.323 session of signal ended (referring to 550 " the H.245 ESC " of Fig. 5) to selected ITSP gateway 145. Then selected ITSP gateway 145 for example uses the H.245 ESC message that defines in standard H.245, sends H.323 session of signal ended (referring to 552 " the H.245 ESC " of Fig. 5) to selected intermediate server 130. Then, selected ITSP gateway 145 sends the on-hook order to PSTN, to disconnect session (hanging up (Hangup) referring to 554 of Fig. 5). Then, selected intermediate server 130 for example uses the Q.931 disconnection message that defines in agreement Q.931, passes on end sessions (referring to 556 " Q.931 disconnecting (disconnect) " of Fig. 5) to selected ITSP gateway 145.
After this, selected intermediate server 130 discharges such as the resource for other the interim data structure of distributing that is moved to end session and is used for other session. In addition, log database is charged in the end that will call out of selected intermediate server 130. Log database recording start time, concluding time, success/failure, caller, callee's telephone number. The database server stores that log database is described by front and appendix B.
DTMF supports
When the user by being pressed in numeral on the website 700 when (for example, being used for voice mail (voice mail)), client computer 105 uses the DTMF message to send numeral to selected intermediate server 130. Then, H.245 selected intermediate server 130 uses message to selected ITSP gateway passes DTMF message.
Following table provides the parameter of DTMF message.
Field name | Decimal system sequence number | Short Description |
| 1 to 8 | Describe such as the front. |
The | 9 to 10 | The DTMF string length. |
The DTMF string | 11 to N, wherein N is the length of DTMF string | The DTMF character. The maximum length of DTMF string for example is 128 bytes. |
Communication stops
At any time, can produce communication by client computer, selected intermediate server 130 or any one use of remote client " VSCP discharges (VSCP REALEASE) " stops. For example, some communication between client computer and selected intermediate server 130 or the remote client or message must receive within the time of distributing. If communication or message can not receive within the distribution time, receiver sends release message to the communications/messages transmitter, to disconnect any communication in the session that starts or activate.
" release " message is used for finishing TCP and connects. For example, if selected intermediate server or client computer do not receive the message such as " foundation ", " calling is carried out ", " alarm " or " connection " within the distribution time, use " release " message. Following table provides the parameter of " release " message.
Field name | Decimal number |
Call Reference Value | 1-8 |
Reason | 9-10 |
The specific communication session of Call Reference Value field identification. Following table provides potential value and the related meanings of each cause field.
Reason | Value |
| 0×0001 |
Do not allow | 0×0002 |
Do not arrive the | 0×0003 |
The | 0×0004 |
The | 0×0005 |
Client computer is to remote client
In remote client communication, this client computer and remote client are used internet or dedicated network direct communication in client computer. Message " TCP connection ", " VSCP foundation ", " VSCP calls out and carries out ", " VSCP connection ", " RTP data ", " VSCP release " communication that client computer uses the front to describe with reference to Fig. 5 at least. So in this embodiment, each client computer and remote client are only used " the client-side program " described in appendix A. Client computer use the assigned ip address be connected with the remote client port " TCP connection " message initiated with the communicating by letter of remote client. So for example each client computer and remote client are by IP address and port numbers sign.
Advantageously, each client computer does not need to support all H.323 agreement that this will be needed with the ITSP gateway communication. Yet, for the communication of client computer to remote client, only need to support RTP. So the software that each client computer needs is minimized. If client requests is communicated by letter with the purpose audio communication device, any independent realization of selected intermediate server support and the needed H.323 agreement of any ITSP gateway communication.
Improve
The above embodiment of the present invention is exemplary, is not restriction. Obviously, for those skilled in the art under the premise of not departing from the present invention, can make amendment aspect wider and improve. For example, system 100 can easily support video, data or facsimile. Therefore, claims comprise all these changes and improvements that drop in the true scope of the present invention.
Appendix A
The Ingress node program
Program " vgk.c " is carried out by Ingress node 120, to support the communication between intermediate server and any client computer. Program " vgk.c " is used (Fig. 4 and 8) in action 405.
The client-side program
" client-side program " carried out by client computer 105, and supports any to client computer 105 and communicating by letter from client computer 105. Put together, the client-side program is used in action 610 and 620 Fig. 6's. In this embodiment, the title that provides in table is that the code segment of " Java file ", " Resource file ", " Microsoft COM Wrapper Class (only Internet browser) ", " Microsoft COM (the Common Object Model) associated documents that are used for Internet-browser ", " the Netscape Plugin associated documents that are used for the Netscape communicator ", " C++ compiler (Microsoft Visual C++6.0) associated documents ", " C++/Header file " and " External Dependencies " is uploaded to client computer.
Program " vegacomm.cpp ", " vegacomm2.cpp " and " vegacomm.h " are by the main client-side application program of together compiling formation.
All code segments that are listed under the C++/Header file table consist of " vscp.dll " together. The compiling of performing a programme " vscp.dsw " beginning " vscp.dll ".
The Java file is used for setting up java applet. It is the main modular of client applications. All end users mutual (interaction) and user interface are realized in these files.
Source file comprises user interface and multimedia object definition.
COM as java applet and*.dll the interface between the file.
Netscape Plugin file allows control java program, with the control sound card. The Netscape Plugin file that is used for Netscape plays a part identical with the COM module that is used for microsoft the Internet explorer.
File " strtp.dll " is supported RTP communication and the audio coding/decoding function between client computer 105 and any destination device (for example PC is to telephone communication) or any remote client (for example, PC is to PC communication).
The Java file | ||
File | Explanation | Note |
AnswerDialog.java | Be/no message conversation class | |
BrowserType.java | For detection of the class of browser type on every side |
ContactInfo.java | The personal information and the positional information that contain client computer | |
DialDialog.java | The dialing conversational class | |
DialDialogEvent.java | Dialing dialogue event class | |
MySocket.java | Receptacle utility program class | |
MyUtil.java | Be used for the often utility program class of the method for use | |
VegaCommEvent.java | The VegaCommEvent class | |
VegaCommWrapper.java | The browser associated class that is used for inner vscp method | |
Web2PhoneApplet.java | The main java applet class of communicating by letter with vscp engine (Plugin or COM) with browser | |
Web2PhoneHelper.java | The front end class that is used for the Web2PhoneApplet class |
The Resource file | ||
File | Describe | Note |
vscp.rc | Vscp dll From Template comprises version information and source data | |
VegaComm.rgs | Be used for registration Vegacomm COM class to the registral source file of Windows | |
busy.wav | Busy tone | The PCM 8000Hz of Microsoft, 8, the monophonic form |
dialtone.wav | Dial tone | The PCM 8000Hz of Microsoft, 8, the monophonic form |
ringback.wav | Ring sound | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone0.Wav | The sound of button 0 | The PCM 8000Hz of Microsoft, 8 |
The position, the monophonic form | ||
Tone1.wav | The sound of button 1 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone2.Wav | The sound of button 2 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone3.wav | The sound of button 3 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone4.wav | The sound of button 4 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone5.wav | The sound of button 5 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone6.wav | The sound of button 6 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone7.wav | The sound of button 7 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone8.wav | The sound of button 8 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tone9.wav | The sound of button 9 | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tonestar.wav | The button asterisk (*) sound | The PCM 8000Hz of Microsoft, 8, the monophonic form |
Tonepnd.wav | Button pound (pound) sound (#) | The PCM 8000Hz of Microsoft, 8, the monophonic form |
The COM Wrapper Class of Microsoft (only Internet-browser) | ||
File | Describe | Note |
IvegaCommEvent.java | The IvegaCommEvent wrapper that is used for the Java of Microsoft | Produced from vscp.dll by Microsoft Visual J++COM Wrapper |
IvegaComm.java | Be used for the Java's of Microsoft | Produce from vscp.dll |
IvegaComm wrapper | ||
TagCodecConstants.java | Encoding and decoding constant definition class | Produce from vscp.dll |
TagStatusConstants.java | Case constant definition class | Produce from vscp.dll |
VegaComm.java | The VegaComm wrapper that is used for the Java of Microsoft | Produce from vscp.dll |
Microsoft COM (the Common Object Model) associated documents that are used for Internet-browser | ||
File | Describe | Note |
vscp.idl | IDL (Interface Definition Language, the IDL) file of the com interface of outside java class is presented in definition | |
VscpCP.h | The C stub file that is used for COM tie point interface | Produce from vscp.idl |
vscp.h | The stub file that is used for com interface | Produce from vscp.idl |
vscp_i.c | Has the C source file for the statement (declaration) of IDD (interface ID) and CLSID (class ID) | Produce from vscp.idl |
vscp_p.c | Comprise the C source file for the proxy stub code of distribution COM | Produce from vscp.idl, do not use |
The Netscape Plugin associated documents that are used for the Netscape communicator | ||
File | Describe | Note |
npvscp.cpp | File realized in the C language that is used for basic Netscape Plugin method, VegaPlugin method, VegaCommEvent method | The inner COM that uses |
npwin.cpp | The Win32 interface that is used for Netscape Plugin | From Netscape PluginSDK source |
Stubs.c | Be used for Netscape |
The stub file of LiveConnect (Java is to Plugin communication) technology | ||
VegaPlugin.java | Methods for Netscape Plugin JRI (Java Raw Interface, Java Raw interface) declaration file | |
VegaCommEvent.java | Events for status updates JRI (Java raw interface) declaration file | |
com_serome_VegaComm Event.c | Call an external Java classes for status Update event method Cross-language interface files | |
com_serome_VegaComm Event.h | Call an external Java classes for status Update event method header file | From VegaCommEvent.java Produce |
com_serome_VegaPlugin .c | Invoked by an external Java classes for Netscape Plugin methods Cross-language interface files | Produced from VegaPlugin.java Raw |
com_serome_VegaPlugin .h | Invoked by an external Java classes for Netscape Plugin methods The header file | Produced from VegaPlugin.java Raw |
SinkObj.h | JRI COM communications (CsinkObj) |
C + + compiler (Microsoft Visual C + +6.0) Related Documents | ||
File | Description | Note |
vscp.def | With COM and Netscape Plugin DLL output function is used in conjunction with | |
vscp.clw | C language class information file | MSVC internal |
vscp.dsp | Project File Information | |
vscp.dsw | Project workspace information | |
stdafx.cpp | AFX files for standard features | MSVC internal |
C + + / Header File | ||
File | Description | Note |
VegaComm.cpp | Key features for the implementation file (CvegaComm) | Master File |
VegaComm2.cpp | Key features for the implementation file (CvegaComm) | |
VegaComm.h | For vegaComm.cpp, vegaComm2.cpp header file | |
WaveCtrl.cpp | Manipulate the microphone and speaker hardware devices Equipment (CwaveCtrl.cpp) | Recording or playback |
WaveCtrl.h | Header text for WaveCtrl.cpp Item | |
stvscp.cpp | Frames / deframing (deframe) VSCP grouping | |
stvscp.h | VSCP header file | |
vscp.cpp | dll master file | |
vscp.h | dll main header file |
Extemal Dependencies | ||
File | Description | Note |
stnet.h | Note... | |
stnet.dll | Note... | |
sterror.h | Stnet defined error | |
strtp.h | Stnet defined error... | |
strtp.dll | RTP DLL | Stnet defined error... |
stg711.h | G.711, G.723 codec DLL header file | |
Tsd2.dll | G.711, G.723 codec DLL |
Intermediate server program
Intermediate server program...
Intermediate server program... | ||
File | Description | Note |
Child.c | Main sub-processing routines and processes each Calling line routine | |
h323stub.c | VEGA server for H.323 Stack calling routine | |
Sendvscp.c | VSCP packet transmission routine | |
Utils.c | Miscellaneous routines | |
Vserver.c | Miscellaneous routines... | |
Stdb.c | Miscellaneous routines... | |
Stdebug.c | Debugging / logging tool |
H.323 Cheng Library
H.323 Cheng Library...
H.323 Stack Packages | ||
H.323 Cheng Library... | Description | Note |
Stasn | Using OSS ASN.1 ASN.1 tools package | |
sth245 | H.245 Abstraction Layer (session management) | |
sth323m | H.323 multi-session (ToplevelAPI) | |
Stnet | TCP / IP extraction layer | |
stq931 | Q.931, and H.225.0 abstraction layer (call (call) Signaling) | |
Stras | RAS abstraction layer (registration, admission, and status) | |
Strtp | Extraction layer RTP (Real Time Protocol) | |
Stwin32 | Extraction layer RTP (Real Time Protocol)... |
Extraction layer RTP (Real Time Protocol)...
| Program | |
405,410,415,420 | Program... | |
415 | External Dependencies | |
Program... | Intermediate server source files | |
850 | H.323 Stack Packages |
Appendix B: Database
The following command from the web server to the database server issues. Described here is used by the database server
The response stated response. Figure 10 schematically illustrates a client 105-i and 105-i, and between database 1000
Relationship. In one embodiment, the use of TCP / IP to send commands.
The following command from the web server to the database server issues. Described here is used by the database server
The response stated response. Figure 10 schematically illustrates a client 105-i and 105-i, and between database 1000
Relationship. In one embodiment, the use of TCP / IP to send commands....
The following command from the web server to the database server issues. Described here is used by the database server
The response stated response. Figure 10 schematically illustrates a client 105-i and 105-i, and between database 1000
Relationship. In one embodiment, the use of TCP / IP to send commands....
Command ... | Command ... |
LOGIN
REGISTER
LOGOFF
GETSTATUS
UNREGISTER
ADDUSER
DELETEUSER
MODIFYUSER
GETUSER
ADDCONTACT
DELETECONTACT
MODIFYCONTACT
| 0×10 0×11 0×12 0×13 0×14 0×20 0×21 0×22 0×23 0×30 0×31 0×32 0×33 0×34 0×50 |
Return code
The following table shows the return codes and associated values. Return code in response to a command generation.
Command | Value |
RETCODE_SUCCESS
RETCODE_INVALID_USERID
| 0×00 0×01 0×02 0×03 0×04 |
RETCODE_INVALID_IPADDRESS
RETCODE_INVALID_PORT
RETCODE_SERVER_ERROR
RETCODE_ALREADY_EXIST
RETCODE_INVALID_FOLDERID
RETCODE INVALID_FOLDERNAME
RETCODE_LOGIN_FIRST
RETCODE_INVALID_SESSIONID
RETCODE_ALREADY_CONNETED
|
0×05
0×06
0×07
0×08
0×09
0× |
LOGIN
LOGON command is to log on to the selected server's command center. LOGON command format is as follows.
Field name | Field name... | Field name... |
Command User name Password ... | 1 2-11 12-21 | Command User name Password ... |
The response for LOGIN
The response for LOGIN...
The response for LOGIN... | Decimal number |
Return | 1 2-33 |
Return code is in any one of the following: RETCODE_SUCCESS,
RETCODE_INVALID USERNAME, RETCODE_INVALID_PASSWORD, or
RETCODE_SERVER_ERROR. Session ID previously been described.
REGISTER
Return code is in any one of the following: RETCODE_SUCCESS,
RETCODE_INVALID USERNAME, RETCODE_INVALID_PASSWORD, or
RETCODE_SERVER_ERROR. Session ID previously been described....
Return code is in any one of the following: RETCODE_SUCCESS, RETCODE_INVALID USERNAME, RETCODE_INVALID_PASSWORD, or RETCODE_SERVER_ERROR. Session ID previously been described.... | Decimal number |
Command
Session ID
IP addresses
Port | 1 2-33 34-37 38-39 40 |
Command: 0 × 11
Command: 0 × 11...
Command: 0 × 11...
Port number: The port number selected intermediate server
Override flag is one of the following
NO_OVERRIDE (0 × 0): If you do not replace the information already exists
OVERRIDE (0 × 01): If you already have replacement information
The response for the REGISTER
The response to the REGISTER command format is as follows.
Field name | Decimal |
Return code | |
1 2-5 | |
Return code... |
Return code...
The user ID has been described previously.
LOGOFF
LOGOFF command to specify which session to end. LOGOFF command format is as follows.
Field name | Decimal number | A brief description of |
A brief description of... | 1 2-33 | A brief description of... |
The response on the LOGOFF
No response.
GETSTATUS
No response....
No response.... | Decimal number | A brief description of |
Command
User | 1 2-5 6-15 | 0 × 13 Has been described previously Has been described previously |
0 × 13
Has been described previously
Has been described previously...
0 × 13
Has been described previously
Has been described previously...
Field name | Decimal number |
Return code
Status
IP addresses
| 1 2 3-6 7-8 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_USERID, RETCODE_INVALID_USERNAME, or
RETCODE_SERVER_ERROR.
Status is any of the following:
STATUS_NOTCONNECTED (0 × 00): not registered user clients;
STATUS_CONNETED (0 × 01): Registered user client.
IP address has already been described.
Port number has been described previously.
UNREGISTER
UNREGISTER command is a request to unregister from the database client IP address / port information.
UNREGISTER command format is as follows.
Field name | Decimal number | |
Command
User | 1 2-5 6-15 | 0 × 14 Has been described previously Has been described previously |
The response on the UNREGISTER
No response.
ADDUSER
ADDUSERCommand is to add a new user to the database request, and provide a new user-related
Information.ADDUSERCommand format is as follows.
Field name | Decimal number | A brief description of |
Command
User name
| 1 2-11 12-21 22-41 42-81 82-121 122-141 142-143 144-153 154-173 174-193 194-213 214-277 278-287 288 | 0 × 20 Has been described previously Open option, '0 'in the public eye Public record user information, 'N' Does not expose the user information ... |
0 × 20
Has been described previously
Open option, '0 'in the public eye
Public record user information, 'N'
Does not expose the user information
...
ToADDUSERCommand response is the following format.
Field name | Decimal |
Return code | |
1 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_USERNAME, RETCODE_INVALID_PASSWORD,
RETCODE_ALREADY_EXIST, or RETCODE_SERVER_ERROR.
DELETEUSER
DELETUSERCommands are deleted from the database user's request.DELETUSERCommand Format
Below.
A brief description of | ||
| 1 | 0×21 |
Session ID | 2-33 | Has been described previously |
The response on DELETEUSER
On DELETEUSER command response is the following format.
Decimal | |
Return code | |
1 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, or RETCODE_SERVER_ERROR.
MODIFYUSER
MODIFYUSERCommand is to modify the database user information requests.MODIFYUSERCommand format is as follows. Any change in the field is 0 × 00.
Decimal number | A brief description of | |
| 1 | 0×22 |
User name | 2-11 | |
Name | 12-22 | |
Surname | 22-41 |
| 42-81 | |
Address 2 | 82-121 | |
City | 122-141 | |
State | 142-143 | |
State... | 144-153 | |
State... | 154-173 | |
Phone 2 | 174-193 | |
Fax | 194-213 | |
214-277 | ||
Password | 278-287 | Has been described previously |
Has been described previously... | 288 | Has been described previously... |
The response on MODIFYUSER...
The response on MODIFYUSER...MODIFYUSERCommand response format is as follows.
Decimal | |
Return code | |
1 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, or RETCODE_SERVER_ERROR.
GETUSERINFO
GETUSERINFOCommand to retrieve user information from the database requests.GETUSERINFOCommand format is as follows.
Decimal number | A brief description of | |
| 1 2-33 | Command Session ID... |
Command
Session ID...
ToGETUSERINFOCommand response format is as follows.
Decimal number | A brief description of | |
| 1 | |
User name | 2-11 | |
Name | 12-22 | |
Surname | 22-41 | |
| 42-81 | |
Address 2 | 82-121 | |
City | 122-141 | |
State | 142-143 | |
ZIP Code | 144-153 | |
| 154-173 | |
| 174-193 | |
| 194-213 | |
214-277 | ||
Password ... | 278-287 | Password ... |
Public Option ... | 288 | Public Option ... |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, or RETCODE_SERVER_ERROR.
ADDCONTACTINFO
ADDCONTACTINFOCommand is to add a new contact to the contact list is stored in the user database
Medium.ADDCONTACTINFOCommand format is as follows.
Decimal number | A brief description of | |
| 1 | 0×30 |
Session ID | 2-33 | Has been described previously |
Folder ID | 34-35 | 2-byte identifier folder |
User name | 36-45 |
Name | 46-65 | |
Surname | 66-85 | |
| 86 | Described below |
| 87-106 | |
| 107 | |
Phone 2 | 108-127 | |
Telephone three types | 128 | Described below |
Phone 3 | 129-148 | |
| 149 | Described below |
| 150-169 | |
170-233 |
Phone type is any of the following:
HOME_PHONE: Home Phone Number
WORK_PHONE: Work Phone Number
CELL_PHONE: cellular (cell) phone number
PAGER_PHONE: pager number
OTHER_PHONE: Other Number
The response on ADDCONTACTINFO
ToADDCONTACTINFOCommand response format is as follows.
Decimal number | |
Return | 1 2-5 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, RETCODE_INVALID_USERNAME,
RETCODE_ALREADY_EXIST, or RETCODE_SERVER_ERROR.
Contact ID is a 4-byte connection identifier.
DELETECONTACTINFO
DELETECONTACTINFOCommands are stored in the database from the contact list of the user deleted
In addition to contact information requests.DELETECONTACTINFOCommand format is as follows.
Decimal number | A brief description of | |
| 1 | 0×31 |
Session ID | 2-33 | Has been described previously |
Contact ID | 34-37 | Has been described previously |
Has been described previously...
Has been described previously...DELETECONTACTINFOCommand response format is as follows.
8 7 6 5 4 3 2 1 | Decimal |
Return code | |
1 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, RETCODE_INVALID_CONTACTID,
RETCODE_NO_OWNER, or RETCODE_SERVER_ERROR.
MODIFYCONTACTINFO
MODIFYCONTACTINFOCommands are stored in the database to modify the user mailing list
The link request.MODIFYCONTACTINFOCommand format is as follows.
Decimal number | A brief description of | |
| 1 | 0×32 |
Session ID | 2-33 | |
Contact ID | 34-37 | |
Folder ID | 38-41 | |
User name | 42-51 | |
Name | 52-71 | |
Surname | 72-91 | |
| 92 | |
| 93-112 |
Phone 2 types | 113 | |
Phone 2 | 114-133 | |
Telephone three types | 134 | |
Phone 3 | 135-154 | |
| 155 | |
| 156-175 | |
176-239 |
The response on MODIFYCONTACTINFO
ToMODIFYCONTACTINFOTo...
To...
GETCONTACTLIST
GETCONTACTLISTCommand based on the provided search criteria, the request from the user contact list contact
Tables.GETCONTACTLISTCommand format is as follows.
Decimal number | A brief description of | |
| 1 | 0×33 |
Session ID | 2-33 | |
Folder ID | 34-35 | |
Starting index | 36-37 | Parts that meet your search criteria link Will have to be smaller than the starting index Retrieve contact discarded. |
Parts that meet your search criteria link Will have to be smaller than the starting index Retrieve contact discarded.... | 38-39 | Parts that meet your search criteria link Will have to be smaller than the starting index Retrieve contact discarded.... |
The first index characters | 40 | Search with the first and last word Characters beginning with the letter between the users Name of contact. |
Finally index characters | 41 | Search with the first and last word |
Characters beginning with the letter between the users Name of contact. | ||
Search string | 87-150 | Match search for the contact list String. |
Sorting options | 151 | Category option is any of the following: SORT_LASTNAME_ASC, SORT_LASTNAME_DES, SORT_FIRSTNAME_ASC, SORT_FIRSTNAME_DES, SORT_USERNAME_ASC Or SORT_USERNAME_DES. |
The response on GETCONTACTLIST
ToGETCONTACTLISTThe response header followed by multiple contact entry.
Header
Decimal number | |
Decimal number... | 1-2 3-4 |
Decimal number...
Decimal number | A brief description of | |
Contact ID | 1-4 | 4 bytes contact |
Contact User ID | 5-8 | |
Name | 9-28 | |
Surname | 29-48 | |
|
49 | |
|
50-69 | |
Phone 2 types | 70 | |
Phone 2 | 71-90 |
Telephone three types | 91 | |
Phone 3 | 92-111 | |
|
112 | |
|
113-132 | |
133-196 | Null-terminated ASCII string |
Phone type is any of the following:
HOME_PHONE (home phone number),
WORK_PHONE (work phone number),
CELL_PHONE (cellular telephone number),
PAGER_PHONE (pager number),
PAGER_PHONE (pager number),...
GETCONTACTINFO
GETCONTACTINFOPAGER_PHONE (pager number),...
GETCONTACTINFOCommand format is as follows.
...
Command format is as follows. ... | A brief description of | |
| 1 | 0×34 |
Session ID | 2-33 | |
User ID | 34-37 | |
Contact ID | 38-41 |
The response on GETCONTACTINFO
ToGETCONTACTINFOCommand response format is as follows.
Decimal number | A brief description of | |
| 1 | |
Contact User ID | 2-5 | |
Name | 16-35 | |
Surname | 36-45 | |
| 46 | |
| 47-76 |
Phone 2 types | 77 | |
Phone 2 | 78-97 | |
Telephone three types | 98 | |
Phone 3 | 99-118 | |
| 119 | |
| 120-139 | |
140-203 |
Return code is any of the following: RETCODE_SUCCESS,
RETCODE_INVALID_SESSIONID, RETCODE_INVALID_USERID,
RETCODE_INVALID_CONTACTID, RETCODE_NO_OWNER,
RETCODE_SERVER_ERROR.
Phone type is any of the following:
HOME_PHONE (home phone number),
WORK_PHONE (work phone number),
CELL_PHONE (cellular telephone number),
PAGER_PHONE (pager number),
OTHER_PHONE (other numbers).
FINDUSERNAME
FINDUSERNAMECommand is a request matches surname, first name and email user table.FINDUSERNAMECommand format is as follows.
Decimal number | A brief description of | |
| 1 | 0×50 |
Name | 2-21 | |
Surname | 22-41 | |
42-105 |
The response on FINDUSERNAME
ToFINDUSERNAMECommand response includes a header followed by multiple contact entry.
8 7 6 5 4 3 2 1 | Decimal number |
Entrance # | 1-2 |
Each user entry
8 7 6 5 4 3 2 1 | Decimal number |
User name Name Surname | 1-10 11-30 31-50 |
Each user name, first name, last name is null-terminated ASCII string.
Appendix C
Entry node to maintain the IP address, port number, and the selected intermediate server status information, the ingress node
Further according to the state information of the client's call request is routed to an intermediate server.
Entry node can be used to disable or enable an intermediate server. In the middle of the selected server failure situation
State, the backup server can be easily replaced middle intermediate server failure.
Entrance to keep all intermediate server node information table. Entrance to the intermediate node periodically Services
Is spread REPORT_REQUEST packet, and all intermediate servers grouped according to registration / report it
Their information. Because REPORT_REQUEST packet is periodically transmitted, a new intermediate server can
Enough is added, there is no need to restart the entry node. In the present embodiment, the IP on the UDP (with
User datagram protocol) transmission REPORT_REQUEST.
REPORT_REQUEST packet including the IP address and port number. IP address, for example, the entry node
4-byte IPv4 address. Ingress port number, for example, a 2-byte receive a response the port number.
Intermediate server response REPORT_REQUEST, send SERVER_REPORT groupings. It
Contains the IP address / port information and intermediate server 130 loading information. In this embodiment, the use of
UDP / TCP / IP transport SERVER_REPORT.
The following table describes the fields in SERVER_REPORT grouping.
Field name | Decimal number |
IP addresses Port number Activation Sessions Maximum number of sessions | 1-4 5-6 7-8 9-10 |
IP address, for example, 4 bytes of respective intermediate server IPv4 address. Port number, for example, in the corresponding
Answering a server from the client to communicate two-byte port number. Once the port number from the entry node
The request is passed to the client. Activate the corresponding intermediate server sessions is the number of calls being processed. That
Information from the entrance used to assign client node uses the call request. The maximum number of sessions the corresponding intermediate server
Services can handle the maximum number of concurrent calls.
Appendix D: Message
Message Transfer Protocol
Provide information suitable transmission topology description. In this embodiment, the message using the TCP / IP transport.
The following Conventional TCP header is used to transmit all messages.
Field name | Decimal number |
Protocol discriminator (high byte) | 1 |
Protocol discriminator (low byte) | 2 |
Content length (high byte) | 3 |
Content length (low byte) | 4 |
Protocol discriminator specified byte order. Byte sequence is used to form a "word" in this order. Some flat
Taiwan first to use high byte, low byte first used some platforms. For example, to express the number "1",
On some systems, it is 0001, on other systems is 0100. Byte order on different CPU platforms
Is different. For example, Sun SPARC and Intel use different byte order. For network applications,
Which typically pass data to other different types of systems, so that the remote party to know the word is being used
Section sequence program is important.
In this embodiment, the protocol discriminator is 0 × 5354. Content-Length header that indicates a packet and message
The total length of the content together.
Message header
The following is the message header.
Field name | Decimal number |
Message type (high byte) | 1 |
Message type (low byte) | 2 |
Version Information - Main (high byte) | 3 |
Version Information - Major (low byte) | 4 |
Version Information - secondary (high byte) | 5 |
Version Information - minor (low byte) | 6 |
Message Type field specifies the type of message. The following table provides the correlation values and messages.
Message type | Value |
Establish | 0×0001 |
| 0×0002 |
| 0×0003 |
| 0×0004 |
| 0×0005 |
| 0×0006 |
| 0×0007 |
Version Information field specifies the version number of the message. Because the message protocol definition by using the version information
Can be changed in the future. If it is higher than the version supported by the receiver, the receiver can reject the message.
Version messages
Version messages...
Version messages...
Field name | Decimal number |
Call reference value | 1-8 |
Status | 9-10 |
Status...
Claims (20)
- Status...Access to a Web site;Supplied to the entry node of the link information;Supplied to the intermediate node, the link information;Access intermediate nodes;Providing a link to the gateway node information; andAccess Gateway Node.
- Access Gateway Node....
- Access Gateway Node....
- 4, as claimed in claim 1, wherein said gateway node comprises ITSP gateway.
- 5, as claimed in claim 1, further comprising using the receiver associated with the audio object PSTN.
- 6, as claimed in claim 5, wherein said audio receiver comprises a remote client object Machine.
- 7, as claimed in claim 1, wherein said intermediate node and the gateway node to establish H.323-based communications.
- 8, as claimed in claim 1, wherein said web site providing advertising, and wherein Communication can choose any user.
- 9, A method for providing a client and the destination communication between the audio receiver means, said apparatus comprising:At least one gateway server can communicate with the destination audio receiver;At least one intermediate server, with said at least one gateway server communication;Entry node, with said at least one intermediate server and the client communicate, whereinThe client node sends signals to said inlet choose an intermediate server;Select said selected intermediate server gateway server;Said selected intermediate server starts communication with the gateway server, andThe audio receiver and the destination client without using an entry node to communicate.
- 10, as claimed in claim 9, wherein said object includes a distal passenger audio receiver Client.
- 11, as claimed in claim 9, wherein said means provided to the client through the advertisement, Provide the client and purpose between audio receiver free (free) audio communication.
- 12, as claimed in claim 11, wherein said advertisement includes video ads.
- 13, as claimed in claim 11, wherein said advertisement comprises an audio advertisement.
- 14, as claimed in claim 9, wherein said object includes a distal passenger audio receiver Client.
- 15 A to provide customers with free audio communication method including the steps of:To provide users with advertising;The purpose of providing audio receiver identifier; andPurpose audio receiver identifier provides the signal path for audio communication.
- 16, as claimed in claim 15, wherein said providing advertisement further comprises: using Website provides visual advertising.
- 17, as claimed in claim 15, wherein said providing advertisement further comprises: generating Audio Ads.
- 18, as claimed in claim 15, wherein said providing signal path further comprises:Supplied to the entry node of the link information;Supplied to the intermediate node, the link information;Access to said intermediate node;Providing a link to the gateway node information;Accessing the gateway node.
- 19, as claimed in claim 15, wherein said object includes a distal passenger audio receiver Client.
- 20, as claimed in claim 19, wherein said destination identifier comprises audio receiver The IP address of the remote client.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US40189899A | 1999-09-24 | 1999-09-24 | |
US09/401,898 | 1999-09-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
CN1415159A true CN1415159A (en) | 2003-04-30 |
Family
ID=23589696
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN00801439A Pending CN1415159A (en) | 1999-09-24 | 2000-09-06 | Flexible communications system |
Country Status (8)
Country | Link |
---|---|
EP (1) | EP1190550A2 (en) |
JP (1) | JP2003530732A (en) |
KR (1) | KR20010050717A (en) |
CN (1) | CN1415159A (en) |
AU (1) | AU7983000A (en) |
BR (1) | BR0006923A (en) |
CA (1) | CA2343754A1 (en) |
WO (1) | WO2001024478A2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1893426B (en) * | 2005-07-08 | 2010-08-04 | 中国电信股份有限公司 | Method and system for realizing pass-through of fire-wall at personal network video signals |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005502228A (en) * | 2001-04-27 | 2005-01-20 | ザ ボーイング カンパニー | Data communication processing method, computing device, and computer-readable medium |
WO2006010193A1 (en) * | 2004-07-30 | 2006-02-02 | Cockatu Pty Limited | Voice calls over the internet |
GB2443889A (en) | 2006-11-20 | 2008-05-21 | Skype Ltd | Method and system for anonymous communication |
GB0623621D0 (en) | 2006-11-27 | 2007-01-03 | Skype Ltd | Communication system |
GB0623622D0 (en) | 2006-11-27 | 2007-01-03 | Skype Ltd | Communication system |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6430282B1 (en) * | 1995-09-29 | 2002-08-06 | Nortel Networks Limited | Methods and apparatus for originating voice calls |
JP3517052B2 (en) * | 1996-03-19 | 2004-04-05 | 富士通株式会社 | Gateway selection control system in voice communication system |
US6031836A (en) * | 1996-09-13 | 2000-02-29 | Lucent Technologies Inc. | Web-page interface to telephony features |
GB9711788D0 (en) * | 1997-06-06 | 1997-08-06 | Northern Telecom Ltd | Method and interface for connecting communication traffic between narrowband and broadband networks |
JPH114292A (en) * | 1997-06-12 | 1999-01-06 | Hitachi Ltd | Communication system |
JP3263339B2 (en) * | 1997-07-18 | 2002-03-04 | 日本電信電話株式会社 | Internet / telephone network integrated utilization method and system |
JPH1155327A (en) * | 1997-08-05 | 1999-02-26 | Matsushita Electric Ind Co Ltd | Connection control server for substitute server and substitute server and network control method |
JP2001517034A (en) * | 1997-09-16 | 2001-10-02 | トランスネクサス エルエルシー | Internet telephone call routing engine |
-
2000
- 2000-09-06 CN CN00801439A patent/CN1415159A/en active Pending
- 2000-09-06 BR BR0006923-0A patent/BR0006923A/en not_active Application Discontinuation
- 2000-09-06 WO PCT/US2000/024485 patent/WO2001024478A2/en not_active Application Discontinuation
- 2000-09-06 CA CA002343754A patent/CA2343754A1/en not_active Abandoned
- 2000-09-06 AU AU79830/00A patent/AU7983000A/en not_active Abandoned
- 2000-09-06 JP JP2001527532A patent/JP2003530732A/en active Pending
- 2000-09-06 EP EP00970450A patent/EP1190550A2/en not_active Withdrawn
- 2000-09-22 KR KR1020000057145A patent/KR20010050717A/en not_active Application Discontinuation
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1893426B (en) * | 2005-07-08 | 2010-08-04 | 中国电信股份有限公司 | Method and system for realizing pass-through of fire-wall at personal network video signals |
Also Published As
Publication number | Publication date |
---|---|
KR20010050717A (en) | 2001-06-15 |
CA2343754A1 (en) | 2001-04-05 |
WO2001024478A3 (en) | 2002-01-17 |
WO2001024478A2 (en) | 2001-04-05 |
JP2003530732A (en) | 2003-10-14 |
BR0006923A (en) | 2002-04-30 |
EP1190550A2 (en) | 2002-03-27 |
AU7983000A (en) | 2001-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1171427C (en) | System and method for providing value-added services (VAS) in integrated telecom network using session initiation protocol (SIP) | |
CN1163029C (en) | Method for making data interchange by data network user and its network system | |
CN1154298C (en) | Distributed network computing system and information exchanging device and method for said system | |
CN1226885C (en) | Wireless communication apparatus and method with application programming interface and method between subscriber application program and telephone program | |
CN1227862C (en) | Multimedia information communication system | |
CN1178450C (en) | Method and system for extended addressing plans | |
CN1228942C (en) | System and method for providing group communication services | |
CN1172506C (en) | Method for managing multimedia data transmission via Internet and smart card thereof | |
CN1656785A (en) | Terminal connection device, connection control device, and multi-function telephone terminal | |
CN1578221A (en) | Communication terminal, control method of communication terminal, and control program of communication terminal | |
CN1484423A (en) | communication terminal unit and method for control of same | |
CN1711784A (en) | System and method for sending SMS and text messages | |
CN1846420A (en) | Transmission of embedded information relating to a quality of service | |
CN1423201A (en) | Address changing device, message treatment method and apparatus | |
CN1674577A (en) | Router and SIP server | |
CN1874328A (en) | Method and system for implementing intercommunication of operation | |
CN1625907A (en) | Packet mode speech communication | |
CN1661990A (en) | Protocol translator | |
CN101047628A (en) | System and method for implementing block service of circuit field terminal access packet network | |
CN1653790A (en) | Application program interface | |
CN1312635A (en) | Multi-business communication system and method thereof | |
CN1523868A (en) | Network phone system and method having dynamic gain control function | |
CN101040543A (en) | Method for transmitting application-specific registration or de-registration data and system, server and communication terminal therefor | |
CN1250564A (en) | User registration in a telecommunication network | |
CN101076198A (en) | Method for multimedium color-image service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
WD01 | Invention patent application deemed withdrawn after publication |