Internet protocol voice logger

BACKGROUND OF THE INVENTION

00011. Field of the Invention

0002The present invention generally relates to Internet Protocol voice communication, and more particularly to Internet Protocol voice logger.

00032. Description of the Prior Art

0004Packet switch voice communication is getting more and more popular in this Internet age. However, due to many reasons, such as regulations, law enforcement, and national security, legal interception of voice communication is required for wide area voice communication.

0005Conventionally, it is required to have a top application layer processing mechanism to filter, monitor, and/or record voice stream through the backbone or trunk communication wires. Normally the legal interception requires heavy burden on the central packet switches and/or routers since all packets have to be parsed and compared with a list of filter, monitor, and/or record conditions. When one more condition is added into the list, there would be one more comparison on every packet. As the list grows, the limited computing power would be exhausted once.

0006Moreover, except for communication setup stage, packet voice communication over IP (Internet Protocol) is based on end-to-end communication. In practical, it is very difficult to intercept all possible routing paths between one end and another end. Hence, there exists a need of a IP voice logger system and method for wide area network.

SUMMARY OF THE INVENTION

0007Therefore, in accordance with the previous summary, objects, features and advantages of the present disclosure will become apparent to one skilled in the art from the subsequent description and the appended claims taken in conjunction with the accompanying drawings.

0008The present invention provides a communication system, which comprising a plurality of user agents, a media relay gateway, a command center, and a session controller. Each user agent is capable of exchanging media stream with another user agent. The media relay gateway is used for receiving and forwarding media stream among said plurality of user agents. Moreover, the command center is used for receiving forwarded media stream from the media relay gateway. And the session controller re-directs and associate exchanged media streams between the plurality of user agents to said media relay gateway according to a monitor command of said command center.

0009The session controller re-directs exchanged media streams between said plurality of user agents by the following steps: at first receiving a call invitation, by said session controller, from a caller of said plurality of user agents; sending a first set relay message, by said session controller, to said media relay gateway; receiving a first relay message identification, by said session controller, from said media relay gateway with a first media IP (Internet Protocol) address and a first port number of said media relay gateway; sending a first invitation to a callee of said plurality of user agents, by said session controller, with said first media IP address and said first port number of said media relay gateway; receiving a first okay message from said callee; sending a second set relay message, by said session controller, to said media relay gateway; receiving a second relay message identification, by said session controller, from said media relay gateway with a second media IP (Internet Protocol) address and a second port number of said media relay gateway; sending a invitation response to said caller, by said session controller, with said second media IP address and said second port number of said media relay gateway; and sending an associate relay message, by said session controller, to said media relay gateway with said first and said second relay message identifications.

0010The present invention provides a communication log method, which comprises providing a communication system, which comprising a plurality of user agents, a media relay gateway, a command center, and a session controller. Each user agent is capable of exchanging media stream with another user agent. The media relay gateway is used for receiving and forwarding media stream among said plurality of user agents. Moreover, the command center is used for receiving forwarded media stream from the media relay gateway. And the session controller re-directs and associate exchanged media streams between the plurality of user agents to said media relay gateway according to a monitor command of said command center.

0011Moreover, the communication log method comprising the following steps: at first receiving a call invitation, by said session controller, from a caller of said plurality of user agents; sending a first set relay message, by said session controller, to said media relay gateway; receiving a first relay message identification, by said session controller, from said media relay gateway with a first media IP (Internet Protocol) address and a first port number of said media relay gateway; sending a first invitation to a callee of said plurality of user agents, by said session controller, with said first media IP address and said first port number of said media relay gateway; receiving a first okay message from said callee; sending a second set relay message, by said session controller, to said media relay gateway; receiving a second relay message identification, by said session controller, from said media relay gateway with a second media IP (Internet Protocol) address and a second port number of said media relay gateway; sending a invitation response to said caller, by said session controller, with said second media IP address and said second port number of said media relay gateway; and sending an associate relay message, by said session controller, to said media relay gateway with said first and said second relay message identifications.

BRIEF DESCRIPTION OF THE DRAWINGS

0012The accompanying drawings incorporated in and forming a part of the specification illustrate several aspects of the present invention, and together with the description serve to explain the principles of the disclosure. In the drawings:

0013<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrates an IP voice logger system of an embodiment in accordance with the present invention;

0014<figref idref="DRAWINGS">FIG. 2</figref> is a sequence diagram depicts a standard call flow between both user agents shown in the <figref idref="DRAWINGS">FIG. 1</figref>;

0015<figref idref="DRAWINGS">FIG. 3</figref> is a sequence diagram shows a static voice log call flow between the both user agents shown in the <figref idref="DRAWINGS">FIG. 1</figref>;

0016<figref idref="DRAWINGS">FIG. 4</figref> is a sequence diagram shows a static monitor and un-monitor call flow <b>400</b> of an embodiment in accordance with the present invention; and

0017<figref idref="DRAWINGS">FIG. 5</figref> is a sequence diagram shows a dynamic monitor call flow of another embodiment in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0018The present disclosure can be described by the embodiments given below. It is understood, however, that the embodiments below are not necessarily limitations to the present disclosure, but are used to a typical implementation of the invention.

0019Having summarized various aspects of the present invention, reference will now be made in detail to the description of the invention as illustrated in the drawings. While the invention will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed therein. On the contrary the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the invention as defined by the appended claims.

0020It is noted that the drawings presents herein have been provided to illustrate certain features and aspects of embodiments of the invention. It will be appreciated from the description provided herein that a variety of alternative embodiments and implementations may be realized, consistent with the scope and spirit of the present invention.

0021It is also noted that the drawings presents herein are not consistent with the same scale. Some scales of some components are not proportional to the scales of other components in order to provide comprehensive descriptions and emphasizes to this present invention.

0022Please refer to <figref idref="DRAWINGS">FIG. 1</figref>, which shows an IP voice logger system <b>100</b> of an embodiment in accordance with the present invention. This IP voice logger system <b>100</b> comprises a SIP (Session Initiation Protocol) proxy <b>110</b>, a session controller <b>120</b>, a voice log command center <b>130</b>, a voice log database <b>140</b>, a media relay gateway <b>150</b>, and a plurality of user agents <b>160</b>. In this embodiment, two user agents, UA<b>1</b><b>161</b> and UA<b>2</b><b>162</b>, of the plurality of user agents are intended to communicate to each other in some kinds of RTP (Real-Time Protocol). The session controller <b>120</b> and the media relay gateway <b>150</b> are packet reachable by the both user agents, UA<b>1</b><b>161</b> and UA<b>2</b><b>162</b>. Please note that the number of the SIP proxy <b>110</b>, the session controller <b>120</b>, and the media relay gateway <b>150</b> of the IP voice logger system <b>100</b> is not restricted. In other words, there could be more than one SIP proxy <b>110</b>, session controller <b>120</b>, and media relay gateway <b>150</b> in the system <b>100</b>.

0023Now please refer to <figref idref="DRAWINGS">FIG. 2</figref>, which shows a standard call flow <b>200</b> between both user agents shown in the <figref idref="DRAWINGS">FIG. 1</figref>. In case the UA<b>1</b><b>161</b> wants to set up a call to the UA<b>2</b><b>162</b>, the UA<b>1</b><b>161</b> sends an invitation to the session controller <b>120</b> with a SIP address of the UA<b>2</b><b>162</b>, the media address, and port of the UA<b>1</b><b>161</b> in a step <b>202</b>. After receiving the invitation, the session controller <b>120</b> forwards this invitation to the registered address of the UA<b>2</b><b>162</b> in a consequent step <b>204</b>. In step <b>206</b>, the UA<b>2</b><b>162</b> returns an okay message to the session controller <b>120</b> with its own media address and port. Once receiving the okay message of the UA<b>2</b><b>162</b>, the session controller <b>120</b> relays it to the UA<b>1</b><b>161</b> in a following step <b>208</b>. Once more, the session controller <b>120</b> forwards the acknowledgement message from the UA<b>1</b><b>161</b> to the UA<b>2</b><b>162</b> in step <b>210</b> and <b>212</b>. After the call setup flow <b>200</b>, the media streams exchanged between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> are not passed through the session controller <b>120</b>. Hence, it is impossible to monitor and record the exchanged media streams.

0024Now please refer to <figref idref="DRAWINGS">FIG. 3</figref>, which shows a static voice log call flow <b>300</b> between the both user agents shown in the <figref idref="DRAWINGS">FIG. 1</figref>. When administrator needs to monitor any call issued by the UA<b>1</b><b>161</b>, the voice log command center <b>130</b> would issue a command to the session controller <b>120</b> for adding UA<b>1</b><b>161</b> in an attention list. In a step <b>302</b> similar to the step <b>202</b>, the UA<b>1</b><b>161</b> sends an invitation to the session controller <b>120</b> with a SIP address of the UA<b>2</b><b>162</b>, the media address, and port of the UA<b>1</b><b>161</b>. After receiving this invitation, the session controller <b>120</b> loops up the caller, UA<b>1</b><b>161</b>, in the attention list. In case the UA<b>1</b><b>161</b> is found in the attention list, the session controller <b>120</b> issues a set relay message to the media relay gateway <b>150</b> in a step <b>304</b>. Within this set relay message, an optional parameter, logtofile, could be denoted to command the message relay gateway <b>150</b> to log the relayed media stream. Once receiving the set relay message, the media relay gateway <b>150</b> returns an okay message to the session controller <b>120</b> with a first relay message identification, a first IP address “ relay_to_ip”, and a first port “relay_to_port” in a step <b>306</b>. In response of the optional parameter of the set relay message, the media relay gateway <b>150</b> may return a file name of the logged media stream. In this regards, instead of forwarding the media address and port of the UA<b>1</b><b>161</b> to the registered address of the UA<b>2</b><b>162</b>, the session controller <b>120</b> sends an invitation to the UA<b>2</b><b>162</b> with the first relay_to_ip and the first relay_to_port media parameters in a step <b>308</b>.

0025Similar to the step <b>206</b>, the UA<b>2</b><b>162</b> returns an okay message to the session controller <b>120</b> with its own media address and port in a step <b>310</b>. Once receiving the okay message of the UA<b>2</b><b>162</b>, the session controller <b>120</b> issues a second set relay message with an optional parameter “logtofile” to the media relay gateway <b>150</b> again in a step <b>312</b>.

0026Also similar to the step <b>306</b>, the media relay gateway <b>150</b> returns an okay message to the session controller <b>120</b> with a second relay message identification, a second IP address “relay_to_ip”, and a second port “relay_to_port” in a step <b>314</b>. Next, processing a step <b>316</b>, the session controller <b>120</b> returns an okay message to the UA<b>1</b><b>161</b> with the second relay_to_ip, and the second relay_to_port as media parameters. Finally, the session controller <b>120</b> forwards the acknowledgement message from the UA<b>1</b><b>161</b> to the UA<b>2</b><b>162</b> in step <b>318</b> and <b>320</b>. At last, since the session controller <b>120</b> collected two relay message identifications in step <b>306</b> and <b>314</b>, the session controller <b>120</b> issues an associate relay command to the media relay gateway <b>150</b> with these two relay message identifications in step <b>322</b>. After receiving these two relay message identifications, the media relay gateway <b>150</b> could associate the media streams together by returning an okay message in step <b>324</b>.

0027After executing static voice log call flow <b>300</b>, the media stream between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> would be sent to and processed by the media relay gateway <b>150</b>. Therefore the media relay gateway <b>150</b> could forward the processed media stream to the voice log command center <b>130</b> and/or the voice log database <b>140</b> for real-time monitor or storage.

0028Please refer to <figref idref="DRAWINGS">FIG. 4</figref>, which shows a static monitor and un-monitor call flow <b>400</b> of an embodiment in accordance with the present invention. When the media stream between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> is already processed by the media relay gateway <b>150</b>, the command center <b>130</b> could issue a monitor_call command to the session controller <b>120</b> to retrieve a call list in a step <b>402</b>. Next, in a step <b>404</b>, the session controller <b>120</b> returns a call_info message to the command center <b>130</b> with a call list in response of the monitor_call command. The call list is composed by call records, which at least denotes a call identification, a caller identification, and a callee identification. In this regards, the command center <b>130</b> issues a monitor_media command to the session controller <b>120</b> with a chosen call identification, and the media IP address and port of the command center <b>130</b> in a step <b>406</b>.

0029Once receiving the monitor_media command, the session controller <b>120</b> issues two monitor_relay commands to the media relay gateway <b>150</b> in order to duplicate relayed media stream to the command center <b>130</b> in step <b>408</b> and <b>412</b>. In step <b>408</b>, a first monitor_relay command brings the first relay message identification, which is issued by the media relay gateway <b>150</b> beforehand, and the media IP and port of the command center <b>130</b> to the media relay gateway <b>150</b>. Hence, in a step <b>410</b>, an okay message with the first relay message identification is returned to the session controller <b>120</b>. Similarly, in step <b>412</b>, a second monitor_relay command brings the second relay message identification, which is issued by the media relay gateway <b>150</b> beforehand, and the media IP and port of the command center <b>130</b> to the media relay gateway <b>150</b>. Hence, in a step <b>414</b>, an okay message with the first relay message identification is returned to the session controller <b>120</b>. Please notify that the present invention does not restrict the order of these two monitor_relay commands. At last, the session controller <b>120</b> gives the command center a successful return value of previous monitor_media command in a step <b>416</b>. After that, all relayed media stream between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> would be duplicated and sent to the command center <b>130</b> by the media relay gateway <b>150</b>. Therefore, the command center <b>130</b> could decode, replay, record, forward, and/or do any possible processing of the forwarded media stream.

0030As shown in the <figref idref="DRAWINGS">FIG. 4</figref>, in case the command center <b>130</b> wants to cease monitoring, the command center <b>130</b> issues a un-monitor_media command to the session controller <b>120</b> with the call identification in a step <b>418</b>. The call identification is used in the monitor_media command of the previous step <b>406</b>. Once receiving the un-monitor_media command, the session controller <b>120</b> issues two un-monitor_relay commands to the media relay gateway <b>150</b> in order to cease duplicating relayed media stream to the command center <b>130</b> in step <b>408</b> and <b>412</b>. In a step <b>420</b>, a first un-monitor_relay command brings the first relay message identification, which is issued by the media relay gateway <b>150</b> beforehand, to the media relay gateway <b>150</b>. Hence, in a step <b>422</b>, an okay message with the first relay message identification is returned to the session controller <b>120</b>. Similarly, in a step <b>424</b>, a second un-monitor_relay command brings the second relay message identification, which is issued by the media relay gateway <b>150</b> beforehand, to the media relay gateway <b>150</b>. Hence, in a step <b>426</b>, an okay message with the second relay message identification is returned to the session controller <b>120</b>. At last, the session controller <b>120</b> gives the command center a successful return value of previous un-monitor_media command in a step <b>428</b>. After that, all relayed media stream between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> would not be duplicated and sent to the command center <b>130</b> by the media relay gateway <b>150</b>.

0031In an example of the embodiment shown in the <figref idref="DRAWINGS">FIG. 4</figref>, the command center <b>130</b> could issue the monitor_media command with the media IP and port of the voice log database <b>140</b> in the step <b>406</b>. Therefore the relayed media stream would be forwarded to the voice log database <b>140</b> by the media relay gateway <b>150</b> for recording and/or post processing. In another example of the embodiment, the command center <b>130</b> could re-forward the received media stream to the voice log database <b>140</b> and/or any machines.

0032In the embodiment shown in the <figref idref="DRAWINGS">FIG. 4</figref>, the command center <b>130</b> could monitor the relayed media stream merely. However, the command center <b>130</b> could dynamically monitor media stream in another embodiment shown in the <figref idref="DRAWINGS">FIG. 5</figref>.

0033Please refer to the <figref idref="DRAWINGS">FIG. 5</figref>, which shows a dynamic monitor call flow <b>500</b> of another embodiment in accordance with the present invention. As the same as the embodiment shown in the <figref idref="DRAWINGS">FIG. 4</figref>, the command center <b>130</b> could issue a monitor_call command to the session controller <b>120</b> to retrieve a relayed call list in a step <b>502</b>. Next, in a step <b>504</b>, the session controller <b>120</b> returns a call_info message to the command center <b>130</b> with the call list in response of the monitor_call command. In this regards, the command center <b>130</b> issues a monitor_media command to the session controller <b>120</b> with a chosen call identification, and the media IP and port of the command center <b>130</b> in a step <b>506</b>.

0034Since the media stream between the UA<b>1</b><b>161</b> and the UA<b>2</b><b>162</b> does not pass through the media relay gateway <b>150</b>, the session controller <b>120</b> has to redirect the media stream at first. Similar with the step <b>304</b> and <b>306</b>, the session controller <b>120</b> issues a set relay message to the media relay gateway <b>150</b> in a step <b>508</b>. Once receiving the set relay message, the media relay gateway <b>150</b> returns an okay message to the session controller <b>120</b> with a first relay message identification, a first relay_to_ip, and a first relay_to_port in a step <b>510</b>. In this regards, the session controller <b>120</b> sends an invitation to the UA<b>1</b><b>161</b> with the first relay_to_ip and the first relay_to_port media parameters in a step <b>512</b>. In response of the invitation, the UA<b>1</b><b>161</b> returns an okay message to the session controller <b>120</b> in a step <b>514</b>. Furthermore, the session controller <b>120</b> returns an acknowledgement of the okay message back to the UA<b>1</b><b>161</b> in a step <b>516</b>.

0035After negotiating with the UA<b>1</b><b>161</b> from step <b>508</b> to <b>516</b>, the session controller <b>120</b> deals with the UA<b>2</b><b>162</b> from step <b>518</b> to <b>526</b> in the same way. The session controller <b>120</b> issues a set relay message to the media relay gateway <b>150</b> in a step <b>518</b>. Once receiving the set relay message, the media relay gateway <b>150</b> returns an okay message to the session controller <b>120</b> with a seoncd relay message identification, a seoncd relay_from_ip, a seoncd relay_from_port, a seoncd relay_to_ip, and a seoncd relay_to_port in a step <b>520</b>. In this regards, the session controller <b>120</b> sends an invitation to the UA<b>2</b><b>162</b> with the seoncd relay_to_ip and the seoncd relay_to_port media parameters in a step <b>522</b>. In response of the invitation, the UA<b>2</b><b>162</b> returns an okay message to the session controller <b>120</b> in a step <b>524</b>. Furthermore, the session controller <b>120</b> returns an acknowledgement of the okay message back to the UA<b>2</b><b>162</b> in a step <b>526</b>.

0036Similar to the step <b>322</b> and <b>324</b> shown in the <figref idref="DRAWINGS">FIG. 3</figref>, the session controller <b>120</b> issues an associate relay command to the media relay gateway <b>150</b> with these two relay message identifications in step <b>528</b>. After receiving these two relay message identifications, the media relay gateway <b>150</b> could associate the media streams together by returning an okay message in step <b>530</b>. Finally, the session controller <b>120</b> returns an okay message to the command center <b>130</b> in step <b>532</b>.

0037The present invention does not only apply on the SIP application, but also on any other suitable packet switch communication protocol. The mentioned media stream may comprise voice, video, and/or any other types of data. In the present invention, the communication between any components in this system <b>100</b> may be encrypted, compressed, and/or certificated. For example, the command center <b>130</b> may be certificated in prior to sending commands to the session controller <b>120</b>.

0038The foregoing description is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obvious modifications or variations are possible in light of the above teachings. In this regard, the embodiment or embodiments discussed were chosen and described to provide the best illustration of the principles of the invention and its practical application to thereby enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the inventions as determined by the appended claims when interpreted in accordance with the breath to which they are fairly and legally entitled.

0039It is understood that several modifications, changes, and substitutions are intended in the foregoing disclosure and in some instances some features of the invention will be employed without a corresponding use of other features. Accordingly, it is appropriate that the appended claims be construed broadly and in a manner consistent with the scope of the invention.