System and method for processing a plurality of requests for a plurality of multi-media services

0001This application is a continuation of U.S. Ser. No. 11/735,858 filed Apr. 16, 2007, (now U.S. Pat. No. 7,411,943), which is a continuation of U.S. Ser. No. 10/298,484 filed Nov. 18, 2002, (now U.S. Pat. No. 7,206,307), where each of the above cited applications is herein incorporated by reference in their entirety.

FIELD OF THE INVENTION

0002The present invention relates generally to a system and method for processing a plurality of requests for a plurality of multi-media services and, more specifically, to a system and method for processing a plurality of requests for a plurality of multi-media services by selectively directing the requests to predetermined service processors for processing based on predetermined attributes of the requests.

BACKGROUND

0003Present day providers of multi-media services, such as AT&T, can provide a number of basic services to customers operating various communication devices. For example, some of the basic multi-media services can include Software Defined Network (SDN) telecommunication service and/or toll-free dialing service, which services are communicated over Internet-Protocol (“IP”) Networks to users of IP-based communication devices. Typically, each request for a basic service offering received over the IP Network from one or more of the IP-based communication devices is directed by a switching system to one of a number of different Service Control Points (“SCPs”) or service processors for processing each of the requests.

0004As providers of multi-media services migrate basic multi-media services from the Legacy 4ESS Switched Network to a Voice over IP architecture, there is a need to support multiple IP-SCPs, which provide a number of multi-media services over the IP architecture. The multiple IP-SCPs each include an IP interface, which is adapted to provide a communication interface to customer logic that provides service processing on a per-call basis for each service request. Further, there is a need to provide an IP-compatible switching device that can support the multiple IP-SCPs and direct the number of requests to any one of the multiple IP-SCPs for processing.

SUMMARY OF THE INVENTION

0005In accordance with principles of the present invention, a system and method for processing a plurality of requests for a plurality of multi-media services received at a multi-media services provider system is set forth. The system processes the plurality of requests for the plurality of multi-media services by selectively directing the requests to predetermined service processors, which are located on the multi-media services provider system, for processing based on predetermined attributes of the requests.

0006In one aspect of the present invention, the multi-media services provider system includes an IP-compatible switching device adapted to receive and process the plurality of requests for multi-media services to generate a plurality of first processed requests for multi-media services. In one aspect, the IP-compatible switching device can include a Private Service Exchange. The system further includes at least one IP Segmentation Directory, which is coupled to the switching device. The IP Segmentation Directory is adapted to receive and process the plurality of first processed requests for multi-media services to generate a plurality of second processed requests for multi-media services.

0007The system additionally includes a plurality of IP Service Control Points, which are coupled to the at least one IP Segmentation Directory and to the switching device. The IP Segmentation Directory is operative to communicate at least one of the plurality of second processed service request messages to at least one predetermined IP Service Control Point of the plurality of IP Service Control Points for service processing based on predetermined attributes of the at least one of the plurality of second processed service request messages. For example, the predetermined attributes of the at least one of the plurality of second processed service request messages may include predetermined information associated with requesting Software Defined Network services. In another example, the predetermined attributes of the at least one of the plurality of second processed service request messages may include predetermined information associated with requesting Toll-Free services.

0008In one aspect, the plurality of first processed requests for multi-media services may include a plurality of first Info_Collected messages. In another aspect, the plurality of second processed requests for multi-media services may include a plurality of second Info_Collected messages.

0009In another aspect of the present invention, the method for processing the plurality of requests for the plurality of multi-media services received at the multi-media services provider system includes receiving at least one service request message having a request for a predetermined service at an IP-compatible switching device located on the system. The method further includes processing the at least one service request message at the switching device for generating a first processed service request message having the request for the predetermined service. The first processed service request message is further communicated to an IP Segmentation Directory, which is also located on the system. The IP Segmentation Directory processes the first processed service request message for generating a second processed service request message having the request for the predetermined service. In addition, the IP Segmentation Directory communicates the second processed service request message to at least one predetermined IP Service Control Point of a plurality of IP Service Control Points located on the system for processing the predetermined service.

0010The method further includes determining to communicate the second processed service request message to the at least one predetermined IP Service Control Point of the plurality of IP Service Control Points for service processing based on predetermined attributes of the predetermined service. In one aspect, the method includes determining that the request for the predetermined service includes a request for a Software Defined Network service. In another aspect, the method includes determining that the request for the predetermined service includes a request for toll-free service.

0011In one aspect, generating the first processed service request message includes generating a first Info_Collected message. Furthermore, communicating the first processed service request message may include communicating the first Info_Collected message to the IP Segmentation Directory. In another aspect, generating the first processed service request message may include generating an Info_Analyze message and communicating the Info_Analyze message to the IP Segmentation Directory.

0012In another aspect, generating the second processed service request message may include generating a second Info_Collected message. Furthermore, communicating the second processed service request message may include communicating the second Info_Collected message to the at least one predetermined IP Service Control Point.

BRIEF DESCRIPTION OF THE DRAWING

0013The foregoing and other objects of this invention, the various features thereof, as well as the invention itself, can be more fully understood from the following description when read together with the accompanying drawings, in which:

0014<figref idref="DRAWINGS">FIG. 1</figref> is an exemplary high-level schematic block diagram of a system for providing multi-media communications between a plurality of communication devices according to the present invention; and

0015<figref idref="DRAWINGS">FIG. 2</figref> is a high-level flow chart illustrating process steps executable on the system of <figref idref="DRAWINGS">FIG. 1</figref>.

DETAILED DESCRIPTION OF THE INVENTION

0016Referring to <figref idref="DRAWINGS">FIG. 1</figref>, shown is an exemplary communication network <b>10</b> for providing multi-media communications between at least first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices of a plurality of communication devices, in accordance with the present invention. The communication network <b>10</b> includes a multi-media provider system <b>10</b><i>a</i>, which is operative to provide a plurality of multi-media services to the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices, as well as to a plurality of other communication devices not specifically shown herein.

0017The system <b>10</b><i>a </i>includes a centrally located Softswitch/Gatekeeper or Private Service Exchange <b>24</b> (hereinafter referred to as “PSX”), at least one Internet-Protocol Segmentation Directory (“IP-SD”) <b>30</b> and a plurality of Internet-Protocol Service Control Points <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>(hereinafter referred to as “IP-SCPs”). The PSX <b>24</b> is coupled to at least one network gateway <b>26</b>, as well as to at least a first <b>28</b><i>a </i>router (e.g. ingress access gateway) and a second <b>28</b><i>b </i>router (e.g. egress access gateway) of a plurality of routers. The PSX <b>24</b> is further coupled to the at least one IP-SD <b>30</b> and to the plurality of IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c</i>. The IP-SD <b>30</b> is also coupled to the number of IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c. </i>

0018In the exemplary embodiment, the first router <b>28</b><i>a </i>is coupled to the first communication device <b>22</b><i>a </i>via a first IP-Private Branch Exchange <b>34</b><i>a </i>(hereinafter referred to as “IP-PBX”). Further, the second router <b>28</b><i>b </i>is similarly coupled to a second communication device <b>22</b><i>b</i>, via a second IP-PBX <b>34</b><i>b. </i>

0019The PSX <b>24</b>, for example, can be provided by Sonus Networks of Westford, Mass. The PSX <b>24</b> is adapted to serve as a proxy server for multi-media service requests received from the first <b>22</b><i>a </i>and/or second <b>22</b><i>b </i>communication devices. Furthermore, the PSX <b>24</b> supports a predetermined set of communication protocols or formats. In one embodiment, the predetermined set of communication protocols or formats includes an Artificial-Intelligence-Network Transactions Capabilities protocol or format (i.e. “AIN TCAP format,” which is referred to hereinafter as “TCAP”) which includes triggers that filter Policy Query in order for the PSX <b>24</b> to initiate TCAP queries to the IP-SD <b>30</b> when predefined conditions are met. The TCAP triggers defined at the PSX <b>24</b> adhere to the triggers defined at a Service Switching Point (“SSP”) of an AIN Call model. The PSX <b>24</b> may have triggers, for example, that are activated by specific digit strings of the destination address of a destination communication device, such as the second communication device <b>22</b><i>b</i>. Furthermore, the PSX <b>24</b> may also set triggers on the origination address, such as the charge number, which may be associated with the calling or first communication device <b>22</b><i>a</i>, for example. In addition, before a call encounters any of the above-described triggers, the PSX <b>24</b> may provide pre-query screening.

0020In the exemplary embodiment, the network gateway <b>26</b> can be provided by Sonus Networks of Westford, Mass. and is referred to hereinafter as “GSX <b>26</b>.” In one embodiment, the GSX <b>26</b> relies on using an H.323 protocol for establishing Multi-Media sessions between the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices.

0021The IP-SD <b>30</b>, in the exemplary embodiment, can be provided by Lucent Corporation of Murray Hill, N.J. The IP-SD <b>30</b> includes a centralized Service Processor directory (not shown) that is adapted to perform an Automatic Number Identification (ANI) (a.k.a the charge number), and the Dialed Number (DN), and table lookups based on the information received in an AlN TCAP Info_Collected message, for example, or other messages, which are provided to the IP-SD <b>30</b> by the PSX <b>24</b>. The IP-SD <b>30</b> is further adapted to process the Info_Collected message or other messages (e.g. Info_Analyze message) and to selectively redirect the Info_Collected message or other messages to a predetermined IP-SCP <b>32</b><i>a</i>, <b>32</b><i>b</i>, or <b>32</b><i>c </i>of the plurality of IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>for feature processing, which will also be described below in further detail.

0022The first router <b>28</b><i>a </i>and the second router <b>28</b><i>b </i>can each include a conventional router, such as a “Cisco 12000,” available from Cisco Corporation of San Jose, Calif. The routers <b>28</b><i>a </i>and <b>28</b><i>b </i>are adapted to receive a plurality of requests for multi-media services from the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices, respectively, and to redirect the requests to the PSX <b>24</b> for further processing, which will be described below in further detail.

0023In the exemplary embodiment, the IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>can each include a conventional computer server, such as an “NT-Server,” which can be provided by Microsoft of Richmond, Wash. or a “Unix Solaris Server,” which can be provided by Sun Micro Systems of Palo Alto, Calif. These IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>can be programmed with conventional Web-page interface software such as: “Visual Basic,” “Java,” “JavaScript,” “HTML/DHTML,” “C++,” “J+,” “Perl,” or “Perlscript,” and “ASP.” These IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>can further be programmed with an operating system, Web server software and Web Application software, such as an e-commerce application and computer network interface software. In addition, the IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>can each be programmed with multi-media service software adapted to provide a plurality of multi-media services, as is known, such as 115DN telecommunication service, “Click-to-Dial,” “Video Conferencing,” “Virtual Private Networks,” and “Toll-Free Calling or 800-Service.”

0024Each of the databases <b>32</b><i>a</i>′, <b>32</b><i>b</i>′, <b>32</b><i>c</i>′, which are respectively associated with each of the IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c</i>, contain a service intelligence layer adapted for providing the plurality of multi-media services described above. The intelligence layer may include customer logic and data, as well as common logic and data that is used by all communication devices or customers.

0025The IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>may each be defined as a Session Initiate Protocol (“SIP”) Server because the IP-SCPs <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c </i>each receive requests from the PSX <b>24</b> via the IP-SD <b>30</b>. In this capacity, the PSX <b>24</b> serves as a proxy server and provides multi-media service processing as requested by the first <b>22</b><i>a </i>and/or second <b>22</b><i>b </i>or communication devices. The IP-SCP <b>32</b><i>a</i>, <b>32</b><i>b</i>, <b>32</b><i>c</i>, each acting as the SIP server, can receive a service request message from the PSX <b>24</b>, as described above, and thereafter can access the appropriate logic to provide multi-media services to the requesting communication device <b>22</b><i>a </i>or <b>22</b><i>b </i>which initiated the request for predetermined multi-media services.

0026The first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices can include a plurality of SIP-enabled devices, such as telephones, personal computers, IP-Private Branch Exchanges (“IP-PBXs”). In addition, the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices can include a plurality of SIP-enabled wireless devices, such as cellular telephones, pagers and personal digital assistants (“PDAs”).

0027Referring again to <figref idref="DRAWINGS">FIG. 1</figref> and further to <figref idref="DRAWINGS">FIG. 2</figref>, which shows an exemplary call flow diagram for executing the method <b>100</b> on the system <b>10</b> of <figref idref="DRAWINGS">FIG. 1</figref> to provide multi-media services between the first and second communication devices <b>22</b><i>a</i>, <b>22</b><i>b</i>, in accordance with the present invention. The method commences by a user of the calling or first communication device <b>22</b><i>a</i>, for example, dialing an SDN On-Net or Off-Net number, which first arrives at the PBX <b>34</b><i>a</i>. Based on the signaling interface, such as Channel Associated Signaling (CAS) or Integrated Service Digital Network Primary Rate Interface (ISDN-PRI), which provides transparent end-to-end digital connectivity to the first PBX <b>34</b><i>a</i>, the first PBX <b>34</b><i>a </i>can route the call to any one of a plurality of locations.

0028For example, if the call arrives at the first PBX <b>34</b><i>a </i>in the CAS interface, the first PBX <b>34</b><i>a </i>routes the call to the first router <b>28</b><i>a</i>, which is hereinafter defined as an ingress Access Gateway (“AGW”) or IP network router. The call arrives at the ingress AGW <b>28</b><i>a </i>with the Called Party Number, which can be associated with the second communication device <b>22</b><i>b</i>, for example, along with other various information received in the call or inband-signaling message. The ingress AGW <b>28</b><i>a </i>processes the call by stripping any dialed number prefix, such as 011, and transforms this information into a RAS (Register, Admission, and Status) ARQ message.

0029Alternatively, if the call arrives at the first PBX <b>34</b><i>a </i>in the ISDN-PRI interface, the first PBX <b>34</b><i>a </i>routes the call to the IP network by sending a Q.931 Setup message to the GSX <b>26</b>, which contains Bearer Capability (e.g. 3.1 kHz audio), Channel Identification, and the Called Party Number. The Called Party Number may include predetermined information, such as Type of Number/Numbering Plan with any dialed prefix removed, such as 011. The Setup message may also include Network-Specific Facilities and a Calling Party Number (including presentation indicator) which is associated with the first communication device in the exemplary embodiment.

0030Furthermore, the ingress AGW <b>28</b><i>a </i>formulates an ARQ message with relevant data (e.g., Calling Party Number, Called Party Number) and sends the ARQ message to the PSX <b>24</b>. Upon receipt of the ARQ message at the PSX <b>24</b>, the PSX <b>24</b> sends an H.323 ACF message to the ingress AGW <b>28</b><i>a </i>directing the ingress AGW <b>28</b><i>a </i>to route the call to the GSX <b>26</b>, which is associated with the second communication device <b>22</b><i>b</i>. Upon receiving the ACF message at the ingress AGW <b>28</b><i>a</i>, the ingress AGW <b>28</b><i>a </i>sends an H.225 Setup message (requesting Fast Start) to the GSX <b>26</b> with the appropriate parameters. In response to receipt of the H.225 Setup message, the GSX <b>26</b> sends an appropriate Query message to the PSX <b>24</b> with all relevant data mapped from the Setup message, which was previously received from the ingress AGW <b>28</b><i>a. </i>

0031At step <b>110</b> of <figref idref="DRAWINGS">FIG. 2</figref>, the GSX sends the Query message to the PSX <b>24</b>, which includes the request for the predetermined service. At step <b>120</b>, in response to receipt of the Query message at the PSX <b>24</b>, the PSX <b>24</b> processes the Query message including the request for the predetermined service and generates a first processed request for the predetermined service. In the exemplary embodiment, the first processed request for the predetermined service is defined herein as a “first Info_Collected message.”

0032The PSX <b>24</b> processes the Query message by performing pre-query processing on the Called Party Number, including validating the dialed number and checking for escape codes. For example, the PSX can be configured to block predefined numbers, such as 900 and/or 411. In this exemplary embodiment, the call passes number validation and does not escape. If the number is 7 digits, the PSX <b>24</b> sets the collected address parameter in the first Info_Collected message, which is generated by the PSX <b>24</b>, as NPT=ISDN and NoN=Subscriber Number, where NPT is defined herein as a Numbering Plan Type and NoN is defined herein as a Nature of Number. If the number is ten digits, then the NPT=ISDN and the NoN=National, and if the prefix is 011, then the NoN=International and the NPT=ISDN.

0033The PSX <b>24</b> further processes the Query message by mapping the collected parameters and provisioned data (e.g., Called Party Number, as described above) into the first Info_Collected message. After formulating the first Info_Collected message at the PSX <b>24</b>, as described above, the PSX <b>24</b> routes the first Info_Collected message to the IP-SD <b>30</b>. In the exemplary embodiment, the first Info_Collected message can include the following information: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0034">Package Type=Query with Permission to Release</li><li id="ul0002-0002" num="0035">Component Type=Invoke(Last) <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0036">Operation=infoCollected</li><li id="ul0003-0002" num="0037">Parameters</li></ul></li><li id="ul0002-0003" num="0038">ChargeNumber</li><li id="ul0002-0004" num="0039">CallingPartyID</li><li id="ul0002-0005" num="0040">Carrier</li><li id="ul0002-0006" num="0041">CollectedAddressInfo</li></ul></li></ul>

0042In response to receiving the first Info_Collected message at the IP-SD <b>30</b>, at step <b>130</b>, the IP-SD <b>30</b> processes the first Info_Collected message to generate a second Info_Collected message, at step <b>140</b>, which may be redirected to a predetermined IP-SCP <b>32</b><i>a</i>, <b>32</b><i>b </i>or <b>32</b><i>c </i>for service processing based on attributes of the requested service. In order to formulate the second Info_Collected message at the IP-SD <b>30</b>, the IP-SD <b>30</b> processes the first Info_Collected message by subjecting the first Info_Collected message to a Directory Function Server (“DFS”) (not shown), which is included on the IP-SD <b>30</b>. Based on the information received in the first Info_Collected message, the DFS accesses a predetermined application included on the IP-SD <b>30</b>, which is operative to execute any one of a number of IP-SD functions. The IP-SD functions include correlating data previously stored in the IP-SD <b>30</b> with data included in the first Info_Collected message, such as an Automatic Number Identification (ANI) or Dial Number (DN), to determine if the call is permitted. After processing the first Info_Collected message, as described above, the first Info_Collected message is redefined as a second processed request for a predetermined multimedia service. In the exemplary embodiment, the second processed request for the predetermined multi-media service is defined herein as a “second Info_Collected message.”

0043Further, the IP-SD <b>30</b> populates the appropriate fields of the second Info_Collected message with predetermined routing information. Thereafter, the IP-SD <b>30</b> routes the second Info_Collected message to the predetermined IP-SCP <b>32</b><i>a</i>, <b>32</b><i>b </i>or <b>32</b><i>c </i>for service processing, at step <b>150</b>. In the exemplary embodiment, the IP-SD <b>30</b> routes the second Info_Collected message to the IP-SCP <b>32</b><i>a </i>for service processing because IP-SCP <b>32</b><i>a </i>includes logic for providing SDN services. It should be understood that the IP-SD <b>30</b> can also route the second Info_Collected message to the IP-SCPs <b>32</b><i>b</i>, <b>32</b><i>c </i>or others not specifically shown herein depending on the requested service processing or feature processing initially requested by the user of the first communication device <b>22</b><i>a. </i>

0044Upon receipt of the second Info_Collected message at the IP-SCP <b>32</b><i>a</i>, the IP-SCP <b>32</b><i>a </i>executes the appropriate customer logic, which applies predetermined screening and feature processing for the second Info_Collected message. The IP-SCP <b>32</b><i>a </i>further processes the second Info_Collected message by accessing the ANI translation table, which is included in the second Info_Collected message, to read and map a charge number to a user or customer record ID. Using the customer record ID from the ANI translation table, the IP-SCP <b>32</b><i>a </i>executes an application that accesses the customer record and further executes customer logic to formulate an AIN TCAP Analyze_Route message, which includes an Analyze_Route operation and a Furnish_AMA operation. The IP-SCP <b>32</b><i>a </i>sends the Analyze_Route message with the routing and recording instructions to the PSX <b>24</b>. In the exemplary embodiment, the Analyze_Route message can include the following information: <ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0000"><ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0045">Package Type=Conversation with Permission to Release</li><li id="ul0005-0002" num="0046">Component Type=Invoke (Last) <ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0047">Operation=AnalyzeRoute</li><li id="ul0006-0002" num="0048">Parameters</li></ul></li><li id="ul0005-0003" num="0049">ChargeNumber</li><li id="ul0005-0004" num="0050">CallingPartyID</li><li id="ul0005-0005" num="0051">CalledPartyID</li><li id="ul0005-0006" num="0052">Carrier</li><li id="ul0005-0007" num="0053">CollectedAddressInfo</li><li id="ul0005-0008" num="0054">AMAsIpID</li><li id="ul0005-0009" num="0055">Component Type=Invoke (last) <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0056">Operation=Furnish_AMA</li></ul></li></ul></li></ul>

0057The PSX <b>24</b> receives the Analyze_Route message from the IP-SCP <b>32</b><i>a </i>and uses the CalledPartyID included therein to determine the route to the egress AGW <b>28</b><i>b </i>and the digit manipulation rule (delete and prefix on the Called Party Number) associated with the route. If the Called Party Number was signaled in the PSX <b>24</b> query, the PSX <b>24</b> will populate the Called Party Number signaled into the appropriate Response message provided to the GSX <b>26</b> along with the information the PSX <b>24</b> received in the Analyze_Route message. Since the destination is an IP endpoint (e.g. the second communication device <b>22</b><i>b</i>), the PSX <b>24</b> will include the translated and modified Called Party Number in the Response message provided to the GSX <b>26</b>.

0058Upon receiving the information from the GSX <b>26</b>, the GSX <b>26</b> sends an H.225 Setup (requesting Fast Start) with appropriate parameters mapped from the Response message to the egress AGW <b>28</b><i>b</i>. The Setup message can include the modified Called Party Number, which was previously modified at the PSX <b>24</b> during execution of the above-described digit manipulation rule at the PSX <b>24</b> (e.g., delete and prefix on the Called Party Number). Upon receiving the H.225 Setup message at the egress AGW <b>28</b><i>b</i>, the egress AGW <b>28</b><i>b </i>sends an H.323 ARQ message to the PSX <b>24</b> to determine whether the egress AGW <b>28</b><i>b </i>has permission to set up the call.

0059In the exemplary embodiment, the PSX <b>24</b> recognizes that the ARQ message has been sent from the egress AGW <b>28</b><i>b </i>requesting permission to set up the call. In response, the PSX <b>24</b> sends an ACF message back to the egress AGW <b>28</b><i>b </i>indicating that it can proceed with the call. Thereafter, the egress AGW <b>28</b><i>b </i>sends the call to the called entity, which is the second communication device <b>22</b><i>b</i>, in this example, using the appropriate inband protocol or Setup message with the modified Called Party Number, if available, for ISDN PRI.

0060The egress AGW <b>28</b><i>b </i>further sends an H.225 Alerting message to the GSX <b>26</b>. The Real Time Transport Protocol (RTP), which carries the media such as audio/video channel, is opened between the egress AGW <b>28</b><i>b </i>and the GSX <b>26</b>. Upon receipt of the H.225 Alerting message from the egress AGW <b>28</b><i>b</i>, the GSX <b>26</b> sends an H.225 Alerting message to the ingress AGW <b>28</b><i>a</i>. The RTP/RTCP channel is opened between the ingress AGW <b>28</b><i>a </i>and the GSX <b>26</b>. Thereafter, the egress AGW <b>28</b><i>b </i>can detect if the called entity or user of the second communication device is off-hook (e.g. ready to commence a multi-media session). Furthermore, the egress AGW <b>28</b><i>b </i>sends a first H.225 Connect message to the GSX <b>26</b>. In response to receipt of the first Connect message, the GSX <b>26</b> generates a Start Call Detail Record (CDR). The GSX <b>26</b> further sends a second H.225 Connect message to the ingress AGW <b>28</b><i>a</i>. At this instant and in accordance with step <b>160</b>, a multi-media communications link is formed between the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices, via the ingress AGW <b>28</b><i>a </i>and the egress AGW <b>28</b><i>b </i>(RTP end-to-end), which includes the requested multimedia service.

0061Although not specifically shown in the figures, the user or calling party at the first communication device <b>22</b><i>a</i>, for example, can disconnect the multi-media communications formed with the second communication device <b>22</b><i>b </i>by hanging-up or going on hook. In this instance, the ingress AGW <b>28</b><i>a </i>sends a first H.225 Release Complete message to the GSX <b>26</b>. Upon receiving the first H.225 Release Complete message from the ingress AGW <b>28</b><i>a</i>, the GSX <b>26</b> sends a second H.225 Release Complete message to the egress AGW <b>28</b><i>b</i>. The GSX <b>26</b> further generates a Stop CDR instruction for stopping the CDR associated with the GSX <b>26</b>.

0062Furthermore, the Data Stream Integrator (DSI) (not shown) located on the GSX <b>26</b> uses the Stop CDR instruction as a trigger to generate an Automatic Message Accounting (AMA) record. The ingress AGW <b>28</b><i>a </i>sends an H.323 DRQ message to the PSX <b>24</b>. The PSX <b>24</b> sends a Disconnect Confirm message, such as an H.323 DCF, back to the ingress AGW <b>28</b><i>a </i>acknowledging the disconnect. The egress AGW <b>28</b><i>b </i>sends an H.323 DRQ message to the PSX <b>24</b> and the PSX <b>24</b> sends an H.323 DCF back to the egress access gateway <b>28</b><i>b </i>acknowledging disconnect. At this instant, the multi-media communications link previously formed between the first <b>22</b><i>a </i>and second <b>22</b><i>b </i>communication devices is disconnected.

0063Having thus described at least one illustrative embodiment of the invention, various alterations, modifications and improvements will readily occur to those skilled in the art. Such alterations, modifications and improvements are intended to be within the scope and spirit of the invention. Accordingly, the foregoing description is by way of example only and is not intended as limiting. The invention's limit is defined only in the following claims and the equivalents thereto.