WO2017035643A1

WO2017035643A1 - Call connection management system and method, and automated call billing management system and method associated therewith

Info

Publication number: WO2017035643A1
Application number: PCT/CA2016/051020
Authority: WO
Inventors: Benoit LALIBERTE
Original assignee: Investel Capital Corporation
Priority date: 2015-09-01
Filing date: 2016-08-29
Publication date: 2017-03-09
Also published as: CA2902609A1

Abstract

Described are various embodiments of a call connection management system and method, and automated call billing management system and method associated therewith. In one embodiment, an automated method for managing connection of a call initiated via a calling device to a call destination is disclosed. The method comprises receiving a call request initiated from the calling device identifying the call destination; initiating a call setup sequence to the call destination via a communication network; processing a successful call connection signal issued via the communication network indicating a successful call connection; relaying an automated call initiation message to the calling device; initiating a timer having a preset timer duration; and applying a call service delivery accounting metric to an account associated with the call request unless the call is cancelled via the calling device before expiry of the preset timer duration as indication of an inadequate call connection.

Description

CALL CONNECTION MANAGEMENT SYSTEM AND METHOD, AND

AUTOMATED CALL BILLING MANAGEMENT SYSTEM AND METHOD

ASSOCIATED THEREWITH

FIELD OF THE DISCLOSURE [0001] The present disclosure relates to telephony, and in particular, to a call connection management system and method, and automated call billing management system and method associated therewith.

BACKGROUND

[0002] The establishment of a telephone call between a calling device and a destination can succumb to various technical and administrative challenges, particularly when the call is established over low quality networks, or again, via inadequately configured hardware. As a result, poor call quality, inaccurate billing and/or unsuccessful connections may ensue to the detriment and frustration of the calling party.

[0003] False answer supervision (FAS) is one example of such challenges, and is generally understood as a misconfiguration of telecommunication equipment, by negligence or design, which causes a caller to be billed or overbilled for a call placed using this equipment. For example, in some configurations, billing may start as soon as the called device begins ringing, even if the call ultimately returns a busy signal or is never in fact answered. Where the call is answered, the calling party is nevertheless overbilled for the call as charges are applied to the call before the call is even answered. While these charges may be subtle in some circumstances, they may in other situations result in significant customer dissatisfaction, for example where a caller repeatedly attempts to make a call without success while still being charged for each attempt.

[0004] Generally, FAS occurs when the telephony switch for the called party sends an answer signal although the called party has not answered. The FAS behavior by the switch bills the calling party incorrectly. For the VoIP industry, the widespread issue of FAS results in a loss of millions of dollars in revenue, dents profit margins, and damages relationships with customers.

[0005] For example, consider the occurrence of FAS in a VoIP call between peer gateways. The switch for a VoIP network is commonly known as VoIP gateway, or simply gateway in the context of a VoIP network. The calling party uses an originating gateway to originate the call, and the called party receives the call via a terminal gateway. The originating gateway signals to the terminal gateway to setup a call. When properly configured, the terminal gateway will only respond with an answer signal upon the call being successfully initiated, at which point, the originating gateway will initiate an appropriate billing meter to apply an appropriate charge for the call duration. However, in some situations, the terminal gateway responds with an answer signal before the call is answered, thus inducing the originating gateway to incorrectly bill the calling party for time preceding call answer. Occasionally, the violation is more severe. For instance, the terminal gateway may respond to the originating gateway with an early answer signal and start the billing, while then seeking to establish the call to the called party via a public switched telephone network (PSTN) only to find that the called party is busy and start playing the busy tone. Nevertheless, the calling party is billed for the entire call duration even though the call was never answered.

[0006] As noted above, FAS may be unintentional or malicious. For example, false answer supervision may be unintentionally experienced when there is no or improper synchronization between a VoIP gateway and a PSTN segment of the used network.

When the call reaches the gateway from the VoIP network, the gateway attempts to establish a connection, but due to incorrect configuration, the gateway inaccurately detects the states of the call that are advertised by the PSTN network (e.g., "called party ringing," and "called party connected"), and forces the "CONNECT" state. The gateway connects the call and begins billing according to settings for the gateway and not according to the actual state of the call.

[0007] In other cases, however, some route vendors may intentionally route a percentage of the traffic or calls directed through them to a fraud-based FAS module that applies FAS to otherwise well-synchronized systems. For example the FAS module may fraudulently communicate a "connected" signal to an originating gateway to initiate billing while waiting to complete the call. Other services are also available to vendors to exploit FAS and increase their profits. One such service simulates calls to numbers that are out of mobile network coverage and provides false billable airtime to a calling party. This service pretends to be a real mobile carrier and plays back real mobile carrier service messages (e.g., "the number you are calling is not reachable at the moment, please, call back later") while charging the calling party.

[0008] Regardless of the source or nature of FAS, the originating gateway's subscriber, the calling party, may detect FAS when reviewing billing details and demand cancellation of the charge. Billing prematurely answered calls may also result in loss of goodwill that can adversely impact the business for the originating gateway's service provider. Responding to false answer supervision complaints consumes a great deal of resources for system operators.

[0009] Using information provided by customers in false answer supervision complaints or trouble tickets, false answer supervision can be detected by placing calls to fake numbers that should not connect and seeing if the calls are billed as connected calls. This is reactive false answer supervision detection because detection relies on customers first complaining of a problem. As an indicator of false answer supervision, reacting to customer complaints is wholly inadequate because not every customer complains. Further, false answer supervision tends to be a transient problem, often disappearing before one can react to the problem, only to reappear at a later time and/or location in a system operator's network.

[0010] In contrast, detecting false answer supervision in a proactive manner is much harder to execute, and generally involves the analysis of various call routing metrics and measures. For example, U.S. Patent No. 8,369,503 describes a false answer supervision detection and management system in which a combination of multiple conditions associated with call initiation, call disposition, call duration, and call billing events are automatically analyzed to identify and seek to remedy suspect illegitimate call events, such as FAS call events and poor audio quality call events. U.S. Patent Application Publication No. 2011/0033032 also discloses a method and corresponding apparatus to detect false answer supervision by determining false answer supervision either as a function of a number of completed calls of short duration and/or as a function of a distribution of differences between timestamps of alert signals and timestamps of connect signals used to complete calls.

[0011] This background information is provided to reveal information believed by the applicant to be of possible relevance. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art.

SUMMARY

[0012] The following presents a simplified summary of the general inventive concept(s) described herein to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is not intended to restrict key or critical elements of the invention or to delineate the scope of the invention beyond that which is explicitly or implicitly described by the following description and claims.

[0013] A need exists for a call connection management system and method, and automated call billing management system and method associated therewith, that overcome some of the drawbacks of known techniques, or at least, provides a useful alternative thereto. Some aspects of this disclosure provide examples of such systems and methods.

[0014] In accordance with one aspect, there is provided an automated method for managing connection of a call initiated via a calling device to a call destination, the method comprising: receiving a call request initiated from the calling device identifying the call destination; initiating a call setup sequence to the call destination via a communication network; processing a successful call connection signal issued via said communication network indicating a successful call connection; relaying an automated call initiation message to the calling device; initiating a timer having a preset timer duration; and applying a call service delivery accounting metric to an account associated with said call request unless the call is cancelled via the calling device before expiry of said preset timer duration as indication of an inadequate call connection.

[0015] In accordance with one embodiment, the automated call initiation message informs a user of the calling device as to said preset timer duration and that the call must be terminated before expiry of said preset timer duration to avoid application of said call service delivery accounting metric should the user be dissatisfied with a quality of the call so initiated.

[0016] In accordance with one embodiment, the call service delivery accounting metric is applied effective as of processing of said successful call connection signal.

[0017] In accordance with one embodiment, the call is cancelled upon the call being expressly terminated by a user of said calling device.

[0018] In accordance with one embodiment, the calling device is a telephone, and wherein the user terminates the call by hanging up the telephone. [0019] In accordance with one embodiment, the call is cancelled upon receipt of a user selection initiated online via the calling device.

[0020] In accordance with one embodiment, the user selection comprises selection of a redial function, and wherein the method further comprises, upon receipt of said user selection, terminating the call and automatically reinitiating said call setup sequence. [0021] In accordance with one embodiment, the reinitiating comprises selection of an alternate communication network.

[0022] In accordance with one embodiment, the method further comprises tracking a service delivery quality metric associated with said communication network as a function of a number of calls cancelled before expiry of said preset duration, wherein selection of said selected communication network form multiple available networks is at least in part made as a function of said tracking. [0023] In accordance with one embodiment, an output of said tracking is operatively accounted for by a lowest cost routing application operable to select said selected communication network.

[0024] In accordance with one embodiment, the communication network comprises a communication link to a destination public switch telephone network (PSTN) provided via a selected destination network service access provider.

[0025] In accordance with one embodiment, the call request is initiated via an originating gateway and relayed via VoIP to a terminal gateway of said selected destination network service access provider having communicative access to said call destination via said destination PSTN, and wherein said successful call connection signal is received from said terminal gateway for processing.

[0026] In accordance with one embodiment, the call service delivery accounting metric comprises at least one of a basic call initiation fee, a destination-specific call initiation fee, an incremental call duration fee, and a call duration rate. [0027] In accordance with one embodiment, the account comprises at least one of a user calling card balance, a user telephone service delivery plan, a user telephone long distance service plan, a cellular telephone plan and an public pay phone access payment balance.

[0028] In accordance with one embodiment, the inadequate call connection is a result of false answer supervision.

[0029] In accordance with another aspect, there is provided a computer-readable medium having statements and instructions stored thereon for implementation by a processor to manage initiation of a call from a calling device to a call destination by: tracking a call setup sequence to the call destination initiated via a selected communication network in response to a call request received from the calling device identifying the call destination; detecting a successful call connection signal issued via said selected communication network indicating that said call setup sequence resulted in a successful connection to the call destination; causing an automated call initiation message to be relayed to the calling device; setting a timer having a preset timer duration; and causing a call service delivery accounting metric to be applied to an account associated with said call request unless a call termination signal is received in response to the call being cancelled via the calling device before expiry of said preset timer duration.

[0030] In accordance with one embodiment, the call service delivery accounting metric is applied effective as of detection of said successful call connection signal.

[0031] In accordance with one embodiment, the call termination signal comprises a user-initiated redial signal, and the statements and instructions further for causing termination of the call and automatically reinitiating said call setup sequence upon receipt of said redial signal.

[0032] In accordance with one embodiment, the reinitiating comprises selection of an alternate communication network.

[0033] In accordance with one embodiment, the statements and instructions are further for tracking a service delivery quality metric associated with said selected communication network as a function of a number of calls cancelled before expiry of said preset duration, wherein selection of said selected communication network is at least in part made as a function of said tracking.

[0034] In accordance with one embodiment, the statements and instructions are integrated within an originating gateway comprising the processor and configured to receive said call request and initiate said call setup sequence.

[0035] In accordance with another aspect, there is provided a call connection monitoring device to monitor a call connection made over a communication network between a calling device and a call destination, the device comprising: a network interface to the communication network to monitor a call setup sequence initiated over the communication network between the calling device and the call destination, and identify a successful call connection signal issued as a result of said call setup sequence; a timer having a preset duration; and a processor that, in response to said successful call connection signal: causes an automated call initiation message to be relayed to the calling device; initiates said timer; and causes a call service delivery accounting metric to be applied to an account associated with the calling device unless a call termination signal is received in response to the call being cancelled via the calling device before expiry of said preset timer duration. [0036] In accordance with one embodiment, the device is operatively associated with a call-originating gateway to the communication network.

[0037] In accordance with one embodiment, the call-originating gateway receives a call request from the calling device and initiates said call setup sequence over the communication network. [0038] In accordance with one embodiment, the communication network comprises a destination gateway to the call destination.

[0039] In accordance with one embodiment, at least one of the originating gateway and the destination gateway interface with a public switch telephone network (PSTN).

[0040] In accordance with another aspect, there is provided a Voice-over-IP (VoIP) gateway for managing a call between a calling device and a call destination, the gateway comprising: an originating network interface to receive a call request from the calling device identifying the call destination; a destination network interface to manage a call setup sequence to the call destination over an available communication network and receive a successful call connection signal issued as a result thereof; a timer having a preset duration; and a processor that, in response to said successful call connection signal: causes an automated call initiation message to be relayed to the calling device; initiates said timer; and causes a call service delivery accounting metric to be applied to an account associated with the calling device unless a call termination signal is received in response to the call being cancelled via the calling device before expiry of said preset timer duration.

[0041] In accordance with one embodiment, the available communication network comprises a destination gateway to the call destination. [0042] In accordance with one embodiment, at least one of said originating network interface and said destination network interface interfaces with a public switch telephone network (PSTN).

[0043] In accordance with another aspect, there is provided a call connection monitoring device to monitor a call connection made over a communication network between a calling party's calling device and a call destination, the device comprising: means for tracking a call setup sequence to the call destination; means for detecting a successful call connection signal; means for causing a message to be relayed to the calling device related to said detected signal; means for timing a preset duration; and means for having a charge directed the calling party unless the call connection is terminated before expiry of said preset duration.

[0044] Other aspects, features and/or advantages will become more apparent upon reading of the following non-restrictive description of specific embodiments thereof, given by way of example only with reference to the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

[0045] Several embodiments of the present disclosure will be provided, by way of examples only, with reference to the appended drawings, wherein:

[0046] Figure 1 is a high level diagram of a call connection management system and method in accordance with one embodiment; and

[0047] Figure 2 is a flow diagram of a call connection management method, and automated call billing management method associated therewith, in accordance with an illustrative implementation of the embodiment of Figure 1.

DETAILED DESCRIPTION [0048] The embodiments described herein provide different illustrative examples of a call connection management system and method, and automated call billing management system and method associated therewith. In particular, in some embodiments, a caller is automatically extended some control or influence on the detection of FAS, and thus, may have some control or influence on improper, inaccurate and/or fraudulent automated billing practices that they may otherwise be exposed to. Similarly, the user may be extended some automated control over billing for inadequate or low quality call connections. Unlike the FAS detection techniques described above, some of the embodiments proposed herein allows for an automated real-time or near real-time solution to FAS or low quality call detection, whereby a caller identifying or suspecting FAS or low call quality may be provided the option of terminating the call early at their end thereby forgoing any charges that may have otherwise been inaccurately applied to their account.

[0049] For instance, and as noted above, FAS detection has heretofore been predominantly executed automatically without user input or influence, traditionally leaving users with little to no control over the quality of the delivered service and/or the rates/charges ultimately applied to them in accessing such services, often resulting at best in mediocre user satisfaction, and in many cases, in routine overbilling, poor service quality delivery, and user dissatisfaction. By empowering the user via implementation of a user-mediated call connection management system and method, overall service delivery integrity and compliance with standard good business practices may be enhanced, as can user satisfaction be increased with minimal cost to the call delivery service operator. Such user-mediated solutions may also, in some embodiments, reduce operator liability and exposure to user complaints and requests for reimbursements where lower quality services are ultimately rendered.

[0050] With reference to Figure 1, and in accordance with one embodiment, an automated call connection monitoring device 102 will now be described within the context of a general voice over data network system, such as Voice over IP (VoIP) network system 100, in providing an automated user-assisted process for call connection quality or accuracy monitoring and/or management. In this example, the monitoring device 102 interfaces with the VoIP network system 100 to monitor an illustrative call made over an available communication network(s) 101 between a calling device 104 and a call destination 106. [0051] In this high level example, a call request is directed to an originating gateway 108 by the calling device 104 over an originating communication network link 110 so to initiate a call setup sequence and ultimately relay a call to the call destination 106 via a communicatively accessible destination gateway 112 and destination network link 114. It will be appreciated that multiple destination gateways 112 may be available to the originating gateway 108 to complete the call, and that selection of such gateway, and associated destination service provider may be based on different parameters and criteria, such as network access costs and fees, compatibility, reliability, existing business relationships or incentives between interfacing parties, etc.

[0052] The known complexities of call circuit selection criteria and implementations may invoke, in some embodiments, the execution of known least-cost routing (LCR) processes and techniques. For instance, LCR is generally associated with the process of selecting the path of outbound communication traffic based on cost. A telecommunication carrier may, for example, employ a LCR team that periodically (monthly, weekly or even daily) chooses between routes from several or even hundreds of carriers for destinations across the world. This process can otherwise be automated by a device or software program known as a Least Cost Router, or the like. For example, a dedicated LCR application software can be operated to automatically load price schedules and code tables, keep control of volume commitment and available capacity with selected local and/or foreign carriers, correctly compare dial codes, convert a carrier's name-based price schedule into a dial code-dependent termination cost schedule, put costs in order, incorporate quality considerations, produce costing and routing schedules in a format suitable for pricing analysts and engineering, generate automatic orders to network switches, and transfer data into a related billing system. LCR application platforms can vary from basic homegrown applications to commercial products offering integration with switch and billing systems, for example.

[0053] With VoIP becoming a predominate carrier messaging system, routing becomes available from standalone products and hosted services. Standalone LCR systems in this context can integrate many powerful routing features such as jurisdictional routing, profit margin protected routing, standard LCR, and the like, as will be readily appreciated by the skilled artisan.

[0054] In any event, the call connection management systems and methods considered herein may be employed alone or in concert with the above or other such call routing techniques to deliver improved services while mitigating unnecessary operating losses. In the present example, an LCR application could, for instance, form part of, or be associated and/or interface with the call connection monitoring device 102 shown in Figure 1 to benefit from logged quality metrics output therefrom, for example, or again operate independently in routing call circuit selections. In any event, and as will be discussed in greater detail below, selection of an appropriate communication network, or destination gateway 112 in this example, may at least in part be impacted by implementation of the monitoring device 102 and a number or frequency of previously logged rejected call connections associated with such networks.

[0055] The calling device 104 may consist of, but is not limited to, a traditional telephone communicating over a standard public switch telephone network (PSTN) link, a cellular telephone communicating over a local cellular communication network link, a VoIP phone or softphone communicating over an available data network link (e.g. Internet connection such as a dial-up, DSL, cable and/or optical fibre connection), and the like. The call destination 106, much like calling device 104, may consist of different types of communication devices operating over an appropriate communication network link, or the like.

[0056] In this example, the monitoring device 102 is operatively associated with the originating gateway 108 so to actively monitor a call connection made via the originating gateway 108 between the calling device 104 and call destination 106. For the sake of illustration, the monitoring device 102 is shown as a separate device or hardware box interfacing with the communication network via the originating gateway 108. It will, however, be appreciated that the monitoring device 102 may also form part of the gateway 108, either as a fully or partially integrated or embedded hardware and/or software component, for example, to achieve a similar result. Alternatively, the monitoring device 102 may be interposed within the communication network to monitor communications relayed thereon and interface with a call service server 116 (introduced below) without requiring an active interface to the gateway 108, but rather probe the communication network without interference or disruption to existing or legacy equipment. In any event, the monitoring device 102 may be configured to monitor/track call setup signals, traffic, data and the like (commonly referred to herein as signals for simplicity) and automatically call upon an operator of the calling device 104 to participate in the validation of a call connection ultimately resulting therefrom. For instance, and in accordance with one embodiment, the monitoring device 102 can interface with the communication network via originating gateway 108 to detect a successful call connection signal issued through the call setup sequence, and as a result, cause implementation of an automated user-assisted call connection confirmation process, for example, to validate a billing metric to be applied for the call.

[0057] Namely, and as illustrated in the embodiment of Figure 1, the monitoring device 102 may be operated by a VoIP or other call service provider, such as a local, regional, national and/or international call service provider in order to provide greater assurance to their customers that billing metrics to be applied in respect of calls initiated via their services are appropriately applied. In this example, the call service provider is illustrated as operating a network-accessible call service server 116 or the like to manage and operate the originating gateway 108 in placing requested calls to multiple destinations around the globe and managing accounts associated with users making these calls, be they regular call service subscribers, pay-per-use subscribers, calling card users or the like.

[0058] In one particular example and with added reference to Figure 2, a call setup sequence, generally referred to using the numeral 200, will now be described. In this particular example, illustrative interactions and communications relayed between a calling device 104, an originating gateway 108 and/or call service server 116, a monitoring device 102 and destination gateway 112 are presented in illustrating one possible implementation of the herein-disclosed systems and devices. As will be appreciated by the skilled artisan, different components may be called upon to perform these or related actions, and in some embodiments in different order, to achieve similar results. Accordingly, such alternative configurations are intended to fall within the general scope and nature of the present disclosure.

[0059] In the illustrated example, a call request 202 is directed by the calling device 104 to the originating gateway 108 and/or servicer provider's online server 116 that initiates a call setup sequence 204 with a selected destination gateway 112 having communicative access to the requested call destination. The monitoring device 102, in this example, is triggered at the onset of the call setup sequence to monitor traffic associated therewith (step 208). [0060] In a properly configured network, the destination gateway 112 relays the call to the call destination at step 206 via link 210, and returns relevant call status signals back to the originating gateway 108 while the call is being established. For example, in one embodiment, a call signaling interface, such as SIP (Session Initiation Protocol) or H.323 (International Telecommunications Union standard H.323 on audiovisual conferencing on data networks) may be implemented across network components to ensure that the necessary signals are sent to allow the call to comply with these standards. Using SIP as an example, the destination gateway 112 could thus issue a "180 RINGING" response to indicate that the call destination has been reached and is being alerted of the call placement. Likewise, one or more client, server or global failure responses (e.g. BUSY, DECLINED, UNAVAILALBE, etc.) may be issued where the call request ultimately fails. In proper operation, the one or more call service providers involved in the call setup sequence will process these responses and await confirmation of a successful connection (e.g. upon receipt of a "200 OK" signal) before applying predefined calling service fees to the call (e.g. connection fee, long distance rates, call duration fees, etc.). During this time, the communication line may nonetheless be open allowing the calling party to hear ring tones pending connection of the call, for example, and ultimately hear the called party answer the call (e.g. voice or message) or hear a busy signal, for example.

[0061] Alternatively, a network connection at or associated with the destination gateway 112, for example, may be intentionally or unintentionally misconfigured to issue a successful call connection signal (e.g. "200 OK" signal) before the call is actually answered, and thus, irrespective of whether this call is in fact ever successfully answered at the call destination. For example, a destination gateway 112 may illegally direct the call through an FAS module to purposefully trigger the inaccurate connection signal and induce improper fees to be billed to the calling party. Despite the line being potentially open to the calling party during this process, the calling party may nonetheless remain unaware that these transactions are being placed while they wait for the called party to answer, thus potentially being charged for dead airtime, and possibly for a call that ultimately never actually connects. This may be particularly problematic where the calling party is being charged for a connection fee, or significant air time fees without actually benefiting from the calling service they are trying to utilize, at times forcing them to reinitiate the calling request and, possibly, being exposed to the same inaccurate billing scenario.

[0062] In the example of Figure 2, irrespective of where or how the successful "call connected" signal is issued at step 210, this signal is detected at step 212 by the monitoring device 102 as the originating gateway 108 and/or server 116 logs the call connection at step 214. To verify the accuracy/veracity of the signalled connection success, the monitoring device 102 causes a call initiation message 216 to be relayed to the calling device 104 (e.g. directly and/or via the originating gateway and/or server). The receipt of this message at step 218 indicates to the calling party that a successful connection signal has been issued over the selected communication network and was logged by the service provider, and thus allows the calling party to validate/confirm the accuracy of this signal. Where the call connection status is inaccurate, or present an inadequate connection quality, the calling party is invited via the call initiation message to terminate the call within a preset time period, and thereby void any charges that would have otherwise been applied to their account for the call. For example, the relayed message may recite: "The call has been connected. Should you be dissatisfied with this connection, please hang up within the next 10 seconds to avoid charges being applied to your account for this call." [0063] Concurrently, a timer is initiated at step 220 by the monitoring device 102, and set to expire after a predetermined duration, such as 10 seconds in the example noted above. Upon the calling party terminating the call at step 222 (e.g. hang up the phone or actively terminate a VoIP session), the call disconnection is logged by the originating gateway/server at step 224 and relayed to the destination gateway 112 to disconnect the call at step 226 with the call destination (if ever in fact connected). Meanwhile, the monitoring device 102 determines whether the call was terminated after expiry of the timer at step 228. If so, the service provider presumes that the calling party was satisfied with the call connection and applies at step 230 an appropriate accounting metric to an account associated with the call (e.g. account associated with the calling device and/or the user thereof, calling card account, etc.). However, where the call was terminated before expiry of the timer, the service provider will automatically interpret that the calling party was not satisfied with the call connection and will ultimately log the call as a rejected call connection at step 232. Consequently, no charges will be applied to the call, and in one embodiment, the service provider may further analyse logged call rejections to ascertain potential causes therefor.

[0064] For example, where calls placed to a given destination area or using a given selected communication network service provider results in significantly more frequent connection rejections, the originating service provider may establish that the selected destination service provider intentionally or unintentionally employs misconfigured equipment, and chose to avoid this particular destination service provider on subsequent calls directed to that destination area. Logged rejections may also be used to isolate unintentionally misconfigured equipment and trigger maintenance or upgrades to his equipment to avoid future rejections. [0065] Similarly, analysis of the rejected connections log may rather identify abusive users that seek to take advantage of the connection confirmation service by placing successive or routine short-duration calls to a given destination to avoid paying for the service, for example, by talking over the call initiation message when a call was in fact successfully connected and timing their call accordingly to relay a quick message to the called party without appropriate payment. [0066] These measures may also be combined with other known measures to further expand call quality metrics and assist in the selection and assignment of appropriate communication networks going forward, for example, in loading pre-established call quality metrics within a designated LCR application, platform or router. For example, a given call route may be characterized by measures, such as number of completed calls, number of attempted calls (i.e., completed calls + hang-ups), duration of calls, and other quality measures or metrics, such as answer-seizure ratio (ASR = number of call attempts answered / number of call attempts, also known as a Call Completion Rate or Ratio) and Average Call Duration (ACD = total duration of calls / total number of completed calls or "Connects"). These and other call quality metrics will be readily known to the skilled artisan, and are thus considered to fall within the general scope and nature of the present disclosure.

[0067] While the present disclosure describes various exemplary embodiments, the disclosure is not so limited. To the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the general scope of the present disclosure.

Claims

What is claimed is: 1. An automated method for managing connection of a call initiated via a calling device to a call destination, the method comprising:

receiving a call request initiated from the calling device identifying the call destination;

initiating a call setup sequence to the call destination via a communication network;

processing a successful call connection signal issued via said communication network indicating a successful call connection;

relaying an automated call initiation message to the calling device;

initiating a timer having a preset timer duration; and

applying a call service delivery accounting metric to an account associated with said call request unless the call is cancelled via the calling device before expiry of said preset timer duration as indication of an inadequate call connection.

2. The method of claim 1, wherein said automated call initiation message informs a user of the calling device as to said preset timer duration and that the call must be terminated before expiry of said preset timer duration to avoid application of said call service delivery accounting metric should the user be dissatisfied with a quality of the call so initiated.

3. The method of claim 1 or claim 2, wherein said call service delivery accounting metric is applied effective as of processing of said successful call connection signal.

4. The method of any one of claims 1 to 3, wherein the call is cancelled upon the call being expressly terminated by a user of said calling device.

5. The method of claim 4, wherein the calling device is a telephone, and wherein the user terminates the call by hanging up the telephone.

6. The method of any one of claims 1 to 3, wherein the call is cancelled upon receipt of a user selection initiated online via the calling device.

7. The method of claim 6, wherein said user selection comprises selection of a redial function, and wherein the method further comprises, upon receipt of said user selection, terminating the call and automatically reinitiating said call setup sequence.

8. The method of claim 7, wherein said reinitiating comprises selection of an alternate communication network.

9. The method of anyone of claims 1 to 8, the method further comprising tracking a service delivery quality metric associated with said communication network as a function of a number of calls cancelled before expiry of said preset duration, wherein selection of said selected communication network form multiple available networks is at least in part made as a function of said tracking.

10. The method of any one of claims 1 to 9, wherein said communication network comprises a communication link to a destination public switch telephone network (PSTN) provided via a selected destination network service access provider.

11. The method of claim 10, wherein said call request is initiated via an originating gateway and relayed via VoIP to a terminal gateway of said selected destination network service access provider having communicative access to said call destination via said destination PSTN, and wherein said successful call connection signal is received from said terminal gateway for processing.

12. The method of any one of claims 1 to 11, wherein said call service delivery accounting metric comprises at least one of a basic call initiation fee, a destination- specific call initiation fee, an incremental call duration fee, and a call duration rate.

13. The method of any one of claims 1 to 12, wherein said account comprises at least one of a user calling card balance, a user telephone service delivery plan, a user telephone long distance service plan, a cellular telephone plan and an public pay phone access payment balance.

14. The method of any one of claims 1 to 13, wherein said inadequate call connection is a result of false answer supervision.

15. A computer-readable medium having statements and instructions stored thereon for implementation by a processor to manage initiation of a call from a calling device to a call destination by:

tracking a call setup sequence to the call destination initiated via a selected communication network in response to a call request received from the calling device identifying the call destination;

detecting a successful call connection signal issued via said selected

communication network indicating that said call setup sequence resulted in a successful connection to the call destination;

causing an automated call initiation message to be relayed to the calling device; setting a timer having a preset timer duration; and

causing a call service delivery accounting metric to be applied to an account associated with said call request unless a call termination signal is received in response to the call being cancelled via the calling device before expiry of said preset timer duration.

16. The computer-readable medium of claim 15, wherein said call service delivery accounting metric is applied effective as of detection of said successful call connection signal.

17. The computer-readable medium of claim 15 or claim 16, wherein said call termination signal comprises a user-initiated redial signal, and the statements and instructions further for causing termination of the call and automatically reinitiating said call setup sequence upon receipt of said redial signal.

18. The computer-readable medium of claim 17, wherein said reinitiating comprises selection of an alternate communication network.

19. The computer-readable medium of any one of claims 15 to 18, the statements and instructions further for tracking a service delivery quality metric associated with said selected communication network as a function of a number of calls cancelled before expiry of said preset duration, wherein selection of said selected communication network is at least in part made as a function of said tracking.

20. The computer-readable medium of claim 19, wherein an output of said tracking is operatively accounted for by a lowest cost routing application operable to select said selected communication network.

21. The computer-readable medium of any one of claims 15 to 19, wherein said statements and instructions are integrated within an originating gateway comprising the processor and configured to receive said call request and initiate said call setup sequence.

22. A call connection monitoring device to monitor a call connection made over a communication network between a calling device and a call destination, the device comprising:

a network interface to the communication network to monitor a call setup sequence initiated over the communication network between the calling device and the call destination, and identify a successful call connection signal issued as a result of said call setup sequence;

a timer having a preset duration; and

a processor that, in response to said successful call connection signal: causes an automated call initiation message to be relayed to the calling device;

initiates said timer; and

causes a call service delivery accounting metric to be applied to an account associated with the calling device unless a call termination signal is received in response to the call being cancelled via the calling device before expiry of said preset timer duration.

23. The call connection monitoring device of claim 22, wherein the device is operatively associated with a call-originating gateway to the communication network.

24. The call connection monitoring device of claim 23, wherein the call-originating gateway receives a call request from the calling device and initiates said call setup sequence over the communication network.

25. The call connection monitoring device of claim 24, wherein the communication network comprises a destination gateway to the call destination.

26. The call connection monitoring device of claim 25, wherein at least one of the originating gateway and the destination gateway interface with a public switch telephone network (PSTN).

27. A Voice-over-IP (VoIP) gateway for managing a call between a calling device and a call destination, the gateway comprising:

an originating network interface to receive a call request from the calling device identifying the call destination;

a destination network interface to manage a call setup sequence to the call destination over an available communication network and receive a successful call connection signal issued as a result thereof;

a timer having a preset duration; and

initiates said timer; and

28. The VoIP gateway of claim 27, wherein said available communication network comprises a destination gateway to the call destination.

29. The VoIP gateway of claim 28, wherein at least one of said originating network interface and said destination network interface interfaces with a public switch telephone network (PSTN).

30. A call connection monitoring device to monitor a call connection made over a communication network between a calling party's calling device and a call destination, the device comprising:

means for tracking a call setup sequence to the call destination;

means for detecting a successful call connection signal;

means for causing a message to be relayed to the calling device related to said detected signal;

means for timing a preset duration; and

means for having a charge directed the calling party unless the call connection is terminated before expiry of said preset duration.